Stats

  • Locked Locked
  • Replies 6
  • Subscribers 125
  • Views 17314
  • 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 stream version

AnnaP

Hi,

 What specific differences are there between the GDS stream version 6 and 3, or 5?

 For instance,

% od -x proj_1.gds | head -1

0000000 0006 0002 0003 001c 0102 006c 0006 000a %          stream version 0003

versus the

        % od -x tproj_2.gds | head -1

0000000 0006 0002 0006 001c 0102 006c 0005 0005                  stream version 0006

Thanks.           

Parents

  • Well, first of all, the stream format was originally created by Calma. It was then picked up by Valid, and that in turn became part of Cadence. So the format is owned (at least I believe it still is) by Cadence, and that's why the format is documented in those documents. It does not mean that there is a Cadence-specific flavour of stream format - it has not been changed for an extremely long time.

    As for issues with reading it into Laker, it's a bit odd posting such questions to a forum on the Cadence web site, given that Laker is nothing to do with Cadence. If you don't see info on the version from Laker, that's something to raise with Springsoft, I'd have thought. I cannot tell by looking at a sequence of a small number of bytes (or even a large number of bytes!) which tool wrote it out. In fact there is a record, LIBNAME, which is sometimes (but not always used) to give some indication of the tool used to write the data, but even that's no guarantee. Regardless of this, it really shouldn't matter what tool wrote it, or even what version it was.

    Regards,

    Andrew.

Reply

  • Well, first of all, the stream format was originally created by Calma. It was then picked up by Valid, and that in turn became part of Cadence. So the format is owned (at least I believe it still is) by Cadence, and that's why the format is documented in those documents. It does not mean that there is a Cadence-specific flavour of stream format - it has not been changed for an extremely long time.

    As for issues with reading it into Laker, it's a bit odd posting such questions to a forum on the Cadence web site, given that Laker is nothing to do with Cadence. If you don't see info on the version from Laker, that's something to raise with Springsoft, I'd have thought. I cannot tell by looking at a sequence of a small number of bytes (or even a large number of bytes!) which tool wrote it out. In fact there is a record, LIBNAME, which is sometimes (but not always used) to give some indication of the tool used to write the data, but even that's no guarantee. Regardless of this, it really shouldn't matter what tool wrote it, or even what version it was.

    Regards,

    Andrew.

Children
No Data

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.