<!channel>: I made an announcement in #caravel about how we're working on the next-generation Caravel design. The next-generation design is also going to have a significant component of analog and mixed-signal IP. We are starting to build out a library of components ourselves, but if we are going to run a test tapeout in April, we need a lot more components than we currently have, and we will need to lean on the community for what IP is publicly available, and what condition it's in. For that purpose, I have made a spreadsheet here: https://docs.google.com/spreadsheets/d/1qRphKqUIIBnthQYE25I7rgCai-NvdentKXkg2FoclQI that lists the components we (must have/need/want) for an April test run. If you have any of these designs, please let me know by adding comments to the spreadsheet to indicate the URL of the analog design source, and what state it's in (there's a color key at the bottom of the spreadsheet). Otherwise I will have to wade through thousands of project submissions, track down each website, and evaluate it for the condition it's in, and it will be April before I've even finished looking at them all. A big "thank you" to anyone who can help!

Re "Flash Array" - I have came across this one: https://github.com/BrandonOng22/caravel_user_project

@Tim Edwards do you have a similar spreadsheet for GF180?

No. We have no plans at the moment for a Caravel redesign for GF180, so no particular urgency for analog and mixed-signal block designs. We haven't even got the analog properly sorted out in the PDK yet. . .

https://github.com/lhrodovalho/sky130sbcs CMOS only current reference. There is also an undocumented low power CMOS only voltage reference there. Those circuits were submitted to MPW4.

@Tim Edwards shared with you a spreadsheet I put together by scrapping efabless.com:

Yes, this is for sky130. That's a good summary and is a lot easier to read through than the Efabless website, and maybe I'll pass it by the Efabless website developers as how they should be presenting the information. Still, what I need is for every project to have a clearly defined specification and measurement (from simulations, followed up by measurements from silicon) and a schematic and a layout, all in a very well-defined format (which is something that I'm working on, separately). But I don't think you can scrape that kind of information, although getting Gemini to process it all and spit out a summary might produce something useful.