Stats

  • Locked Locked
  • Replies 1
  • Subscribers 91
  • Views 13138
  • 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

Warning while loading the LEF file of an AMS (autriamicrosystems) RAM

Willbe

Dear All,

Í have a problem during the synthesis on my design with first encouter.  I'm using an Autriamicrosystems's RAM on my design. The problem i have is  that, while loading the LEF file of this RAM, some warning appear. I don't if i can ignore these warning, in case of no, how   i can attribute ANTENNADIFFAREA to these PINS.

Thanks,

Loading Lef file ../memory/cadence/RAMB16_S18_sram1024x18.lef...

**WARN: (SOCLF-200): Pin 'DO[5]' in macro 'RAMB16_S18_sram1024x18' has no ANTENNADIFFAREA attribute defined.

**WARN: (SOCLF-200): Pin 'DO[7]' in macro 'RAMB16_S18_sram1024x18' has no ANTENNADIFFAREA attribute defined.

**WARN: (SOCLF-200): Pin 'DO[9]' in macro 'RAMB16_S18_sram1024x18' has no ANTENNADIFFAREA attribute defined.

**WARN: (SOCLF-200): Pin 'DI[10]' in macro 'RAMB16_S18_sram1024x18' has no ANTENNAGATEAREA attribute defined.

**WARN: (SOCLF-200): Pin 'DI[12]' in macro 'RAMB16_S18_sram1024x18' has no ANTENNAGATEAREA attribute defined.

**WARN: (SOCLF-200): Pin 'WR' in macro 'RAMB16_S18_sram1024x18' has no ANTENNAGATEAREA attribute defined.

**WARN: (SOCLF-200): Pin 'DI[14]' in macro 'RAMB16_S18_sram1024x18' has no ANTENNAGATEAREA attribute defined.

**WARN: (SOCLF-200): Pin 'DI[16]' in macro 'RAMB16_S18_sram1024x18' has no ANTENNAGATEAREA attribute defined.

**WARN: (SOCLF-200): Pin 'DO[10]' in macro 'RAMB16_S18_sram1024x18' has no ANTENNADIFFAREA attribute defined.

**WARN: (SOCLF-200): Pin 'AD[1]' in macro 'RAMB16_S18_sram1024x18' has no ANTENNAGATEAREA attribute defined.

**WARN: (SOCLF-200): Pin 'DO[12]' in macro 'RAMB16_S18_sram1024x18' has no ANTENNADIFFAREA attribute defined.

**WARN: (SOCLF-200): Pin 'AD[3]' in macro 'RAMB16_S18_sram1024x18' has no ANTENNAGATEAREA attribute defined.

**WARN: (SOCLF-200): Pin 'DO[14]' in macro 'RAMB16_S18_sram1024x18' has no ANTENNADIFFAREA attribute defined.

**WARN: (SOCLF-200): Pin 'AD[5]' in macro 'RAMB16_S18_sram1024x18' has no ANTENNAGATEAREA attribute defined.

**WARN: (SOCLF-200): Pin 'DO[16]' in macro 'RAMB16_S18_sram1024x18' has no ANTENNADIFFAREA attribute defined.

**WARN: (SOCLF-200): Pin 'AD[7]' in macro 'RAMB16_S18_sram1024x18' has no ANTENNAGATEAREA attribute defined.

**WARN: (SOCLF-200): Pin 'DI[0]' in macro 'RAMB16_S18_sram1024x18' has no ANTENNAGATEAREA attribute defined.

**WARN: (SOCLF-200): Pin 'AD[9]' in macro 'RAMB16_S18_sram1024x18' has no ANTENNAGATEAREA attribute defined.

**WARN: (SOCLF-200): Pin 'RD' in macro 'RAMB16_S18_sram1024x18' has no ANTENNAGATEAREA attribute defined.

**WARN: (SOCLF-200): Pin 'DI[2]' in macro 'RAMB16_S18_sram1024x18' has no ANTENNAGATEAREA attribute defined.

**WARN: (SOCLF-201): *** Too many pins have no ANTENNAGATEAREA/ANTENNADIFFAREA defined. See log file for complete pin list. ***

 

regards,

Eric

  •  Hi Eric,

     I don't know if you compiled these RAMs yourself, or if someone else compiled them and delivered data to you, but usually there is an option in the compiler for outputting antenna information. That is the first thing I would check. It's possible you could ignore these (I have used RAM libraries that do not have antenna info), but you are taking a risk that process antenna violations will be created that you will not be aware of until final physical verification (DRC Antenna checks). If you can't get the compiler to output the antenna info, I would recommend running your DRC Antenna checks as soon as possible on your design to see if you have antenna violations on the RAMs. If you don't, then it's safe to ignore these warnings. If you are seeing violations, I would really press the RAM provider for this info. 

    Hope that helps,

     

    - Kari 

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.