I am sorry for the delay in getting in touch. How are things progressing with the project?

I look forward to hearing from you.

John.

David,

All fine with me. That is the point of Collaborative Projects, to work on potential IP and design exploration. Let's keep working it up on the Collaborative Project and when we feel it is refined and hardened then we can bring it into a reference design revision.

John. 

This project has no milestones not even a Getting Started. Yet the basis of milestones are outline above:

'Refactored Codebase' says we have started the Milestone Getting Started

'Producing a Specification' says we have started the Milestone Architectural Design

There are statements in 'Adoptability' that says we have started the Milestone IP selection

'Development of Verification Strategy' says we have started the Milestone Verification Methodology

Hope this helps set these milestones started...

It would be really good if you could update the project status and the milestones to reflect the work you shared with us in December 2025 and also where you have progressed in the first quarter of 2026.

As you update the milestones it would tidy things up if you remove the old autogenerated milestones and make new ones based on the appropriate workflow stages.

Let us know if you need any help.

John.

Hi,

Is there a target tape out for this IP?

John.

Is this project still in Request of Collaboration state?

John.

Can you add your Behavioural Design milestone.

John.

Thanks for the updated Milestones.

John.

Great to see the updated Milestones with what has been done. It would be good next to put in some milestones for the work to be done in the future and to plan out the next steps for the project. If you need any help in this please let us know.

John.

Hi,

I see that you added the Memory generators design flow to your interests. We have recently added some very basic information on the Skywater 130 process but it needs adding to in order to be more useful to people I feel. It would be great to get any feedback on what you might need here.

There is a statement in the paragraph above the Sky 130 drop down info box which says:   “… which can provide reasonable area, energy, and timing estimates …”.  We have not provided a clear breakdown of how this might be achieved for a simple nanoSoC implementation. Having a nanoSoC specific set of info on this page I feel would help. Would you find this helpful?

Other projects have asked us how the memory would be laid out.  The page says:  “SRAM generators or memory compilers are used to generate arrays of optimised custom bitcells in the required size of row and column configuration to best meet the needs of the SoC design.” So again answering this for nanoSoC might help even though it is might be obvious to others what attributes you provide to the generator. What do you think?

The difference between the Free 130 SRAM cells and the paid for commercial cells is explained in the paragraph starting:  “Foundries are able optimise their custom bit cells and SRAM generators…” 

I am guessing that even given such information, it might be helpful to have an example of how this information might be used to plan the memory requirement for the nanoSoC project?

It would be great to hear your thoughts on this.

John.