Stats

Locked Locked
Replies 13
Subscribers 125
Views 17910
Members are here 0

This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

gds streamins in CDB and OA, interchangeably

Hi all,

We have designs in CDB as well as in OA (Cadence 6.15) and for some reason we could not use the conversion scripts between databases. Instead we wanted to stream out OA design as gds and read in (stream in back) in CDB for top level integration.

However it has problems and it reports to specify the rod directory, so,

During gds streamout from OA it reports a warning among other translation info :

WARNING (XSTRM-154): The object map file does not contain any mapping for the OpenAccess object 'Marker' and the sub-object 'annotation'. Therefore, these objects in the design will not be translated. To enable the translation of these objects in the Stream file, provide a valid mapping in the object map file. For details on the format of object map file, refer to the "Design Data Translator's Reference" guide for XStream.

So this gds (made above) is the streamed in back to CDB, where it reports the follwing message after translating a few basic cells (gates etc.)

WARNING (315): ROD directory used during Stream In is not the same as the directory defined in the input Stream file. Some information might get lost.

Could anyone give a clue about a possible solution ?

Regards,

Aamir

Andrew Beckett over 11 years ago

I'll check again what the root cause is because it cannot have been broken for that long (your release would have been more than 2 update releases before it was broken which was many months). So hopefully there's a workaround.
More later once I get to work.
Andrew
Cancel
Vote Up 0 Vote Down

Cancel
raul7 over 11 years ago

ok, thanks
Cancel
Vote Up 0 Vote Down

Cancel
Andrew Beckett over 11 years ago

I think it is sensitive to exactly how the stream file was generated in the first place. There seem to be a variety of different reasons, but none of the cases I found mention of were very clear as to the precise cause. It's hard to debug something that was fixed over 5 years ago though. So the best thing would really be to install a newer hotfix of IC5141 as I suggested.
Regards,
Andrew.
Cancel
Vote Up 0 Vote Down

Cancel

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.