This section describes the architecture Selection for Spartan UltraScale+ devices.
Default Architecture
When using Spartan UltraScale+ devices, the system uses the default architecture configuration: Spartan UltraScale+ (SU45P/SU60P/SU65P/SU100P/SU150P/SU200P).
Note: Secondary boot devices are not applicable for Spartan
UltraScale+ architecture.
ID Code Override Behavior
The tool automatically detects and overrides the Spartan UltraScale+ architecture based on the ID code specified in the BIF (Boot Image Format) file.
Important: When any of the following ID codes
are specified in the BIF file, the Spartan UltraScale+ architecture automatically switches from the
default configuration to the SU10P, SU25P, and SU35P architecture.
| ID Code | Effect |
|---|---|
| 0x04E81093 | Spartan UltraScale+ (SU10/25/35P) |
| 0x04E82093 | Spartan UltraScale+ (SU10/25/35P) |
| 0x04E80093 | Spartan UltraScale+ (SU10/25/35P) |
See Spartan UltraScale+ devices and JTAG IDCODEs in Spartan UltraScale+ FPGAs Configuration User Guide (UG860) for more information.
Critical User Notes
CAUTION:
You must be aware of the following:
- Default Behavior
- Without specifying an ID code, all Spartan UltraScale+ devices use the default architecture configuration, that is, (SU45P/SU60P/SU65P/SU100P/SU150P/SU200P)
- Automatic Override
- Specifying any of the supported ID codes in your BIF automatically changes the target architecture configuration. In case you do not specify any ID codes or unsupported ID code, the Bootgen generate PDI for default architecture configuration.
BIF File Example
// Default behavior - uses default architecture
new_bif:
{
boot_config {smap_width=32}
image
{
name = pmc_subsys
id = 0x1c000001
partition
{
id = 0x01
type = bootloader
file = gen_files/plm.elf
}
partition
{
id = 0x09
type = pldata
file = pl_data.rcdo
}
}
}
// Override behavior - switches to alternative architecture
new_bif:
{
id_code = 0x04E81093 // Forces alternative family category in spartanup
boot_config {smap_width=32}
image
{
name = pmc_subsys
id = 0x1c000001
partition
{
id = 0x01
type = bootloader
file = gen_files/plm.elf
}
partition
{
id = 0x09
type = pldata
file = gen_files/pl_data.rcdo
}
}
}
Note: Ensure your target device and tool chain support the
architecture configuration that is selected based on your ID code
specification.