Bootgen Changes from 2016.4 to 2017.1
Bootgen Changes from 2016.4 to 2017.1
Below is the list of deprecation options and their correct usage. You can also check bootgen -help or bootgen -bif_help <bif_option> for information on the usage.1. [fsbl_config] a53_x64 | a53_x32 | r5_single | r5_dual will be deprecated.
Please use 'destination_cpu' attribute of bootloader partition.
Note: For a53 32 bit, bootgen takes from the elf directly. User just need to specify as a53-0 for both 64 and 32 bit.
Example:
deprecated usage:
the_ROM_image:
{
[fsbl_config] a53_x64
[bootloader] fsbl.elf
[destination_cpu=a53-0] hello.elf
}
new usage:
the_ROM_image:
{
[bootloader,destination_cpu=a53-0] fsbl.elf
[destination_cpu=a53-0] hello.elf
}
2. [fsbl_config] bi_integrity_sha3 will be deprecated.
Please use 'checksum=sha3' attribute of bootloader partition.
Example:
deprecated usage:
the_ROM_image:
{
[fsbl_config] bi_integrity_sha3
[bootloader] fsbl.elf
[destination_cpu=a53-0] hello.elf
}
new usage:
the_ROM_image:
{
[bootloader,checksum=sha3] fsbl.elf
[destination_cpu=a53-0] hello.elf
}
3. '-debug' option will be deprecated.
Please use '-log' option.
Example:
deprecated usage:
bootgen -arch zynqmp -image boot.bif -w on -o boot.bin -debug
new usage:
bootgen -arch zynqmp -image boot.bif -w on -o boot.bin -log trace
bootgen -arch zynqmp -image boot.bif -w on -o boot.bin -log error
4. BIF attribute 'destination_device=pmufw' will be deprecated.
Please use 'destination_cpu=pmu'.
Example:
deprecated usage:
the_ROM_image:
{
[bootloader] fsbl.elf
[destination_device=pmufw] pmu.elf
}
new usage:
the_ROM_image:
{
[bootloader] fsbl.elf
[destination_cpu=pmu] pmu.elf
}
5. BIF attribute 'destination_device=xip' will be deprecated.
Please use the attribute 'xip_mode'. For more info, use 'bootgen -bif_help xip_mode'.
Example:
deprecated usage:
the_ROM_image:
{
[bootloader,destination_device=xip] fsbl.elf
[destination_cpu=a53-0] hello.elf
}
new usage:
the_ROM_image:
{
[bootloader,xip_mode] fsbl.elf
[destination_cpu=a53-0] hello.elf
}
Related Links
© Copyright 2019 - 2022 Xilinx Inc. Privacy Policy