GDS output broken???

28 views
Skip to first unread message

Bastian Koppelmann

unread,
Dec 9, 2019, 11:28:07 AM12/9/19
to openram-...@ucsc.edu

Hi Matt and all,

when I try to open the produced GDS from OpenRAM in a layout tool like Klayout, I get the following error:

ERROR: DATATYPE record expected (position=132788, record number=13780, cell=cell_6t)

The same goes for Calibre. Any idea why this is happening? Opening it in Virtuoso works fine. However it's nasty to import the design into Virtuoso and export it again for DRC. I designed the cell_6t in Virtuoso and exported it using:

strmout -topCell cell_6t -view layout -flattenVias -flattenPcells -strmFile ../gds_lib/cell_6t.gds

Cheers,

Bastian

Matthew Guthaus

unread,
Dec 9, 2019, 11:56:31 AM12/9/19
to openram-...@ucsc.edu
Which version are you using?

I did do some recent updates to support layer/purpose pairs. You may have to update any custom technology files to now have a purpose in addition to the layer.

--
https://openram.soe.ucsc.edu
---
You received this message because you are subscribed to the Google Groups "OpenRAM Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openram-dev-gr...@ucsc.edu.
To view this discussion on the web visit https://groups.google.com/a/ucsc.edu/d/msgid/openram-dev-group/11e19245-607e-b217-b316-0c300c5f0ff8%40mail.uni-paderborn.de.


--
Matthew Guthaus
Associate Dean of Graduate Studies
Professor, Computer Science & Engineering
Baskin School of Engineering
University of California Santa Cruz

Bastian Koppelmann

unread,
Dec 10, 2019, 6:54:40 AM12/10/19
to openram-...@ucsc.edu, Matthew Guthaus
Hi Matt,

On 12/9/19 5:56 PM, Matthew Guthaus wrote:
> Which version are you using?


I'm still on version 1.1.1 (git hash
c263cfaf8da1393235d44928899839af73cef22f)


>
> I did do some recent updates to support layer/purpose pairs. You may have
> to update any custom technology files to now have a purpose in addition to
> the layer.


I'll try updating to the newest version and see if that fixes the problem.

Cheers,

Bastian

Reply all
Reply to author
Forward
0 new messages