^
Advanced Search

AR# 50489 7 Series - ERROR:Bitgen:145 - Why are RS0 and RS1 pins persisted if the design is not using Multiboot and the bitgen ConfigFallback option is not set?

Description


Why are RS0 and RS1 pins persisted if the design is not using Multiboot and the bitgen ConfigFallback option is not set?

I tried to use these pins outside configuration, however I received bitgen errors as follows:

ERROR:Bitgen:145 - Pin AD31 is a persistent pin, which means the configuration
logic retains control of this pin after configuration. However, a design
component exists in its' IOB. To ensure that design components are not
placed in these IOB's, please rerun par with the persistent pins prohibited
from use.
ERROR:Bitgen:145 - Pin AD30 is a persistent pin, which means the configuration
logic retains control of this pin after configuration. However, a design
component exists in its' IOB. To ensure that design components are not
placed in these IOB's, please rerun par with the persistent pins prohibited
from use.

Solution

Even though the design does not use Multiboot and the bitgen ConfigFallback option is not set, if the RS0 and RS1 pins are associated with the configuration interface being used, they will be persisted if the Persist bitgen option is set. For a full list of pins affected by the -g Persist option, refer to (Xilinx Answer 51473).

Actions

AR# 50489
Date Created 09/27/2012
Last Updated 09/27/2012
Status Active
Type
Devices
  • Kintex-7
  • Artix-7
  • Virtex-7
Feed Back