Stats

  • Locked Locked
  • Replies 2
  • Subscribers 125
  • Views 13368
  • 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

SPECTRE_RF_POSTLAYOUT_EAP Environment Variable

jslaton

In the "Getting The Most Out Of Spectre APS" application note, slide 11 recommends

"For RF analyses – If Spectre 17.1 ISR11 or newer, use HPA and setthe environment variable SPECTRE_RF_POSTLAYOUT_EAP to 1 – For older versions of Spectre, use Legacy-RF RCR"

I have confirmed that I am using Spectre 17.1 ISR11 (specifically that release); should I be able to query this environment variable from the CIW with getShellEnvVar("SPECTRE_RF_POSTLAYOUT_EAP")?

Also, is setShellEnvVar("SPECTRE_RF_POSTLAYOUT_EAP=1") in the CIW the correct way to set this?

Lastly, what does this environment variable do and is it a recommendation or required to use the new +postlayout with SpectreRF?

  • Andrew Beckett

    Actually, it's a mistake. If using that version of spectre and later, you do not need to set the environment variable. That was needed in Spectre versions before SPECTRE17.1 ISR11 (and then you just needed the env var setting before spectre was launched). However, my recommendation would be to use SPECTRE17.1 ISR11 or later, or SPECTRE18.1

    The env var was needed to control access to a pre-release (early access partner) capability. It's now fully released, which is why we've removed the env var to control access.

    Regards,

    Andrew.

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.