https://open-source-silicon.dev logo
Join Slack
Powered by
Hi, I want to start implementing my design using s...
# sky130
s
Hi, I want to start implementing my design using skywater-pdk and synopsys tools (DC and ICC1). Has anyone experience in this and could share?
I am using 2013.03 synopsys tools . I tried us ing the scripts at https://github.com/20Mhz/skywater-pdk/tree/synopsys_pull/vendor/synopsys . But I faced errors in generating db on some attribute defination like Error: Line 32, The 'clk_width' attribute, which expects values of string type, is being supplied a value of floating-point type. (LBDB-53) Error: Line 48812, Cell 'sky130_fd_sc_hd__dfbbn_1', pin 'CLK_N', The 'violation_delay_degrade_pct' attribute, which expects values of string type, is being supplied a value of floating-point type. (LBDB-53) Error: Line 48852, Cell 'sky130_fd_sc_hd__dfbbn_1', pin 'D', The 'violation_delay_degrade_pct' attribute, which expects values of string type, is being supplied a value of floating-point type. (LBDB-53) Error: Line 48872, Cell 'sky130_fd_sc_hd__dfbbn_1', pin 'D', The 'violation_delay_degrade_pct' attribute, which expects values of string type, is being supplied a value of floating-point type. (LBDB-53) Error: Line 49307, Cell 'sky130_fd_sc_hd__dfbbn_1', pin 'RESET_B', The 'violation_delay_degrade_pct' attribute, which expects values of string type, is being supplied a value of floating-point type. (LBDB-53) and then the tool crash
And for creating milky-way by gds and tf file, The Fram view couldn't be created.I tried using lef but it gives error, so is there another way?
@20Mhz
u
Hi Sarah, I think there was a problem with some attributes on earlier versions of the .libs... those were probably missing some “”. Are you using latest checkin?
s
For the db, I changed the type of attribute to float instead of string and the error is solved.... Only other libs that have ccsn attribute still have errors(not checked yet)... I think I am using the latest could check again
Only for milky-way creation.... The Fram view couldn't be created by gds... Are the pins info in gds or not?. It appears during running milky-way tool in commands of auExtractBlockagePinVia
u
I believe BPV extraction is looking at overlap between text and layer for deriving pin info. In any case 2013 is 7 years old, is there a particular reason to use? We tested everything on 2019.12
*text and drawing for each metal
s
2013 is the available version for me now . If I want to try to use lef instead of gds , Do the lef have enough info to create the milkyway with the techlef file?
u
please post the error you’re getting
s
If I use read_gds, The gds will be read successfully but formOK "Extract Blockage" will not be executed to create fram view
read_gds.txt
And if I use read_lef , Fram view will be created but errors appeared during read_lef
read_lef.txt
u
I believe the problem is that that option on BPV should not be used and it may be default on on your specific release, can you try:
Copy code
scheme setToggleField "Extract Blockage" "transfer pin on layer" "m2" 0
Please try m2 to m12 to make sure all boxed are unchecked. That should be added just before
Copy code
scheme formOK "Extract Blockage"
s
No, they are unchecked already. I think the trial with read_lef will work, only there were no "END Library" at the end of lef file. I downloaded the latest version and it has this line in lef files.
But which lef to use mgic.lef or normal lef ? Another thing the welltap normal lef is 5.5 version and "CLASS CORE WELLTAP", the milkyway tool has error as this class type "WELLTAP" starts in version 5.6
Also the version of magic.lef is 5.7 not 5.5 like normal lef
u
you will hit more issues, one of the reasons I created my own abstract was because of missing substrate layers on LEF, not sure if they added layer
I strongly suggest you update your toolchain
Open in Slack
PreviousNext
Powered by