Hi all, I recently watched the February 2nd webina...
# caravan
d
Hi all, I recently watched the February 2nd webinar which is posted in #announcements. Since the webinar was focused on digital design, I am wondering are there any significant differences in precheck and MPW submission for caravan vs caravel?
t
There are some differences, but not many. For the moment, we have fewer checks on the source files since we don't have in mind any specific analog or mixed-signal flow. Ultimately, all you need is a GDS file for the wrapper, although if you are missing sources then you are breaking the intent of the open source requirement, which is frowned upon (missing sources is not necessarily intentional. I think a lot of analog designers are creating cells and layout with their own flows and then copying the result into the caravan project, or making a symbolic link, neither of which will end up with the source files in the user project repository). The layout must pass the manufacturing rule DRC deck in klayout. There is an XOR check against the empty wrapper like there is for caravel, although the wrapper is much simpler, so this really only checks that the user design does not extend outside the given boundary.
d
Okay! sounds good. Just to confirm, is the same Caravel board used "Caravan" designs as well?
A few other questions too: The Efabless Open MPW FAQ page says "All projects must use the Caravel test harness padframe." So is Caravan padframe available for MPW? If so, does Efabless determine which padframe I want by parsing my project repo I submit? Efables page also says an
info.yaml
file is required for the project, but I can't find much info about it.
t
Yes, we're using the same board design for both Caravel and Caravan. All the analog pins that are swapped out from GPIO pins are only going straight to header pins on the development board.
Yes, the Caravan chip and padframe are available for the MPW runs. Per the instructions, you will be cloning either the
caravel_user_project
or
caravel_user_project_analog
repository. The intended chip will be determined from the name of the wrapper layout cell used. I don't think the
info.yaml
file is required any longer.
d
Okay! Thank you!