Syntax
- For Zynq devices and Zynq UltraScale+ MPSoC:
[boot_device] <options> - For Versal adaptive
SoC:
boot_device { <options>, address=<address> }
Description
Note: This attribute is required in BIF targeted for
primary boot Image (PDI in case of Versal device.)
Specifies the secondary boot device. Indicates the secondary boot device on which the partition is present.
Arguments
Options for Zynq and Zynq UltraScale+ MPSoC devices:
- qspi32
- qspi24
- nand
- sd0
- sd1
- sd-ls
- mmc
- usb
- ethernet
- pcie
- sata
- ufs (applicable only for Versal AI Edge Series Gen 2 and Versal Prime Series Gen 2)
The address field specifies the offset of the image in the given flash device.
For emmc/mmc device the address field does not indicate a direct address on flash device. The bits in emmc/mmc address are interpreted as following by PLM:
- 0-15: file number
- 16-19: logical drive number/ file system index
Options for Versal adaptive SoC:
- qspi32
- qspi24
- sd0
- sd1
- sd-ls (SD0 (3.0) or SD1 (3.0))
- mmc
- usb
- pcie
- ospi
- smap
- sbi
- sd0-raw
- sd1-raw
- sd-ls-raw
- mmc1-raw
- mmc0
- mmc0-raw
- imagestore
Example
Note: The following examples are for BIF for primary boot
image.
- For example Zynq devices and Zynq UltraScale+ MPSoC:
all: { [boot_device]sd0 [bootloader,destination_cpu=a53-0]fsbl.elf } - For example Versal adaptive
SoC:
new_bif: { id_code = 0x04ca8093 extended_id_code = 0x01 id = 0x2 boot_device { mmc, address=0x10000 } image { name = pmc_subsys, id = 0x1c000001 { id = 0x01, type = bootloader, file = plm.elf } { id = 0x09, type = pmcdata, load = 0xf2000000, file = pmc_data.cdo } } image { name = lpd, id = 0x4210002 { id = 0x0C, type = cdo, file = lpd_data.cdo } { id = 0x0B, core = psm, file = psm_fw.elf } } image { name = pl_cfi, id = 0x18700000 { id = 0x03, type = cdo, file = system.rcdo } { id = 0x05, type = cdo, file = system.rnpi } } image { name = fpd, id = 0x420c003 { id = 0x08, type = cdo, file = fpd_data.cdo } } }