Hi,

Now that you have added the milestones you need to add content about what you are going to do for this milestone. If you read the page in the design flow section for the milestone it will help you know what actions are needed.  Also look at other projects for inspiration such as the project on sensing by Sydney.

You should set a Target Date by which you expect to complete the tasks. This is only an estimate and you will learn how to estimate how long things will take as you work through your project. It is a good engineering discipline to develop a cycle of estimating tasks and comparing how you did, just like athletes compare their times.  

For the milestone Architectural Design there are some tasks in the main page and also a sequence of sub-tasks, each of these is a milestone. Of course you don't have to stick to the design flow milestones and can add your own free text milestones if you find these more helpful.

In the Introduction it mentions the three reference designs and looking at the project scope using ECG data then it would seem the choice of the nanoSoC can be made and you simply add that as the text in the milestone. The team should be able to help you with any questions on other topics such as under separation of concerns, where you look to be developing your IP block by 'defining unique sub-system'.

As you can see with the discussion above, you already have a lot to add to your initial milestone.

John. 

Hi,

It is quite some time since you added the initial getting started milestone to your project.  You need to add content about what you are going to do for the milestones. If you read the page in the design flow section for the milestone it will help you know what actions are needed.  Also look at other projects for inspiration such as the project on sensing by Sydney.

You should set a Target Date by which you expect to complete the tasks. This is only an estimate and you will learn how to estimate how long things will take as you work through your project. It is a good engineering discipline to develop a cycle of estimating tasks and comparing how you did, just like athletes compare their times.  

For the milestone Architectural Design there are some tasks in the main page and also a sequence of sub-tasks, each of these is a milestone. Of course you don't have to stick to the design flow milestones and can add your own free text milestones if you find these more helpful. You have outlined a collection of project milestones in the project above so please can you add these as you start them.

In the Introduction to Architectural Design it mentions the three reference designs and looking at the project scope we seem to have made the choice of the nanoSoC, you simply add that as the text in the milestone. The team should be able to help you with any questions on other topics such as under separation of concerns, where you look to be developing your IP block by 'defining unique sub-system'.

As you can see with the discussion above, you already have a lot to add to your initial milestone as text.

The getting started milestone has some things you need to set up such as version control, eg. Git repo. Again the Sydney project example is a good one to help you start to develop a disciplined Project Management approach that will help you make better progress with your project.

John. 

John. 

Hi,

It was goo to hear yesterday that you now have your Synopsys flow in place with your new development server operational and all the licenses via Europractice established. Hopefully we are close to overcoming the issue we have being trying to debug in terms of the variance between the Gate Level Simulations and the golden RTL model verification. 

Can you lay out the final stages to get to tape out so we can complete the necessary milestones and finally get this project to tape out.

John.

Hi,

Welcome to SoC Labs. Looking forward to how we can help with your project.

John.

Hi,

Thanks for adding the project and your completed milestones. It looks like you are making good progress. Do you have any plan for future milestones. Perhaps some of the design flow milestones can give you some ideas? I am sure David and Malik can help.

John.

Thank you for signing up to SoC Labs. We are keen to understand your interests and how we can help collaborate in any way. I see you have stated a  Research Area in Architecture. If you can let us know a little more that would be most helpful.

Kind regards,

John.

What a brilliant Milestone report from The Anh Nguyen for the project An Efficient Hardware-based Spike Train Repetition for Energy-constrained Spiking Neural Networks. It really brings to life the generic information we have in this stage page. 

The page could now do with some more SoC Labs reference design specific implementation material to do the same and make the flow step grounded in the specific SoC designs we have here within SoC Labs.

John.

Hi,

I think the information you have provided in your project Milestone updates is excellent. How is the project progressing? Is there anything we can help you with?

Look forward to hearing from you,

John.

These some of these design considerations are really earlier in the flow. I think these are design decisions that come from the Technology Selection point.

Which fabrication path and the process and timing of getting something on to an MPW service, should be considered then. The timing should be affected by the planned milestones for the Physical Design stage. 

While in any phase of the design you should be spending some time planning the next phase. 

Hi Lewis,

Following up on our regular teams call today you mentioned how you might change/update the project as the scope has shifted a little during the project. This is not unusual and as I said many projects change scope. I think it helps more to reflect the change than to rewrite the project ignoring the original scope. 

I would add a simple sentence at the start something like:

Sensing for Precision Agriculture

Our initial aim was to develop a complete system of sensor-based devices. As the project has progressed we have focused the scope towards the on-chip components and specifically the implementation of the ADC sub-system within nanoSoC. 

You can then add updates to the teams

Digital Team Update

2026 update:

Dan: nanoSoC  synthesis, 

Ben: nanoSoC design and test case development

Lewis: integration work flow, ...

...

Analog Team

2026 update:

Erick: ADC Comparator, analog block layout, ...

Hee: ADC Capacitive Array, ... 

Jaime: Filtering, ...

Leave everything else and then after the section you have on:

Analog Front End and Sensors

Add a new section to cover the most recent ADC developments.

Hope that helps and hopefully not too much of an effort to update?

John.