Open d-m-bailey opened 1 year ago
Looks like the met2 wires have variable extensions. Does magic handle wires with variable extensions?
Yes, the wire extension is being read in correctly. This is the type of issue that I think "extract do labelcheck" was supposed to handle---the metal pin sits by itself but connects downward and across in the hierarchy. I don't know whether it got broken recently due to all the changes in the extraction code, or if it's just a situation that was never being handled. But I can investigate. The layout is pretty simple, which makes it easier.
I think that this is caused by the use of an array, and there may be something in the extraction code that doesn't anticipate the use of arrays. My gut feeling is that if you replace the array of six devices in the middle with six individual instances, it will extract correctly.
I also get "Number of subscripts doesn't match" errors when extracting, which is a bit weird as I don't recall having seen that before. That suggests that the extraction failed because it failed to correctly count the number of instances in the array, which might be caused by something like the brackets in the cell name.
This occurs in slot-031 of mpw-8.
The reram array has a met2 strap to
SEL
in the basecell_1t1r_lv
reram cell. In neighboring placements of thecell_1t1r_lv
cells insubRA_2R2C
,SEL<0:1>
are connected correctly.However, in neighboring placements of
subRA_2R2C
insubRA_2R16C
, the lower level met2 layer connectivity is broken.The right 2 instances
XNJ_YH_subRA_2R2C_0_0[5]
andXNJ_YH_subRA_2R2C_0 N<14>
are connected as expected, but the left 6 instances have unconnected hierarchical nets such asNJ_YH_subRA_2R2C_1/SEL<0>
.Bottom level
Middle level (*one level down)
Top level
Executing
./run_ext
in the attached tarball should recreate the problem. sel_connect.tgz