I also would like to see missing functionality like Logic Equivalence checking (LEC) and DFT support (JTAG, MBIST, SCAN) added. My suggestion to the OpenROAD team is to have clear industry standard handoffs between each stage so that users can effectively use Open-Source EDA tools with commercial tools and Custom Scripts in their commercial projects. Main reason for the failure is that every company flow, project & user requirement are unique and each project needs some customization which cannot be easily mapped into a one single RTL to GDS flow. In my technical career I have noticed multiple commercial tool vendors developed an automated RTL to GDS flow and none of these were successful. I look forward to a successful commercial tape-out through the OpenLane flow and wish the OpenROAD team the very best for their innovation and mission in OpenEDA flows- in particular in enabling this design flow success as a unix and arduino initiative. Response to users in terms of tracking key GitHub issues and overall response time to fix is better than a commercial tool vendor support team. I am highly impressed by the OpenROAD team. I see a continuous improvement in the OpenLane tool over each MPW shuttle. Each of the VLSI design stages from RTL-GDSII flow needs specialized technology knowledge and in depth implementation strategy with coordinated effort and strategy. “I highly appreciate the time and effort taken by the OpenROAD team in developing a VLSI design flow based on open-source concepts. Life for a single mom in Los Angeles takes an unexpected turn when she allows three young guys to move in with her. Dinesh summarizes his usage experience of OpenROAD™ and OpenLane as below:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |