Import Stream (GDSII) from Encounter: Routing is dropped. (XSTRM-58)

Hi bibjt

Encounter layer mapping file is slightly different from Virtuoso mapping file and should not be used directly. Please see the following COS solutions:

11429822 : How do I read in a Stream file generated by SOC Encounter into Virtuoso?
11314148 : How to save gds from Encounter with correct map file for viewing on dfII side?

Best regards
Quek

Hi Quek,

I cannot read these links since I am not account manager (our department buys the software). Is it possible that could you please paste the articles here, or send me a message? Thanks a lot for your helps.

Sincerely,

bjbit 

Hi bibjt

The idea is to have the appropriate mappings in both Encounter and Virtuoso mapping files. E.g.

=== Encounter ===
Metal1 via 1 0
Metal1 net 2 0
Metal1 spcnet 2 1
Name Metal1/Net 3 0

On the Virtuoso side, the layer name and gds mappings have to be correct. E.g. Metal1 in Encounter might correspond to M1 in Virtuoso. Hence the Virtuoso mapping file should be similar to:

M1 drawing 1 0
M1 drawing 2 0
M1 drawing 2 1
M1 label 3 0
...

Best regards
Quek

Hi Quek,

I rewrote the layer map file like the format you suggested, and the routes on metal and via layers work now. However, the last 3 lines of streamout.map is like:

==============================

 NAME COMP 127 0

COMP ALL 128 0

DIEAREA ALL 129 0

===============================

No matter whether I convert these lines, the translation returns same warnings like before:

=================================

 WARNING (XSTRM-58): Failed to create the new layer purpose pair 'DIEAREA:ALL'. It will be skipped and all the shapes on this LPP will be dropped.

WARNING (XSTRM-58): Failed to create the new layer purpose pair 'COMP:label'. It will be skipped and all the shapes on this LPP will be dropped.

WARNING (XSTRM-58): Failed to create the new layer purpose pair 'COMP:ALL'. It will be skipped and all the shapes on this LPP will be dropped.

WARNING (XSTRM-58): Failed to create the new layer purpose pair 'COMP:label'. It will be skipped and all the shapes on this LPP will be dropped.

WARNING (XSTRM-58): Failed to create the new layer purpose pair 'COMP:ALL'. It will be skipped and all the shapes on this LPP will be dropped.

WARNING (XSTRM-58): Failed to create the new layer purpose pair 'COMP:label'. It will be skipped and all the shapes on this LPP will be dropped.

WARNING (XSTRM-58): Failed to create the new layer purpose pair 'COMP:ALL'. It will be skipped and all the shapes on this LPP will be dropped.

Hi bjbit

"COMP" refers to component outlines so I think we can map this to prBoundary object. We should also map DIEAREA to prBoundary object. I think "NAME COMP" refers to text labels for component outlines. It should be ok not to map it since it is just labels. I am not sure what it should map to. : )


Best regards
Quek

Hi Quek,

I addressed them to

===================

prBoundary label 127 0

prBoundary drawing 128 0

prBoundary drawing 129 0 

===================

It seems working for me. At least no warnings. I guess I will just leave it be as long as no further problem is observed. Thanks again for your kindly helps.

Best regards,

bjbit 

Hi bjbit

Just to re-emphasize that the prBoundary gds layer should be mapped to prBoundary OA object and not simply to a "prBoundary" layer in Virtuoso.

Best regards
Quek

Hi Quek,

Does it mean I should map it to all purposes of prBoundary? like

=================

prBoundary label 127 0

prBoundary all 128 0

prBoundary all 129 0 

=================== 

Is "all" correct format in map file? Thanks.

Best regards,

bjbit 

Hi bjbit

That's not exactly what I meant.You can map them to prBoundary objects using the "Objects" tab in the stream-in form. Please see the picture below. The reason for this mapping is that we need the prBoundary to be created as an OA object in the database so that it can be recognized by various tools such as floorplanner, export-LEF, analog placer, etc. The prBoundary in IC5141 is simply a rectangle but this is no longer correct in IC61.

Best regards
Quek

Hi Quek,

I was able to do the encounter map file with reference to  foundry supplied layer map.  I was able to generate the gds, but the generated gds has labels on the internal wires/ non port nets.  How could I prevent the generation of the non port labels?

Regards,

Ram