Flashing Customization

This topic provides guidance on customizing flashing for:
Bootburn
Kernel
Prebuilt binaries
Offline binaries

Select Boot Chain Platform Configuration

Within the board support package (BSP) with Virtualization support the top-level configuration file (global_storage_qspi.cfg) defines the sub configuration file used to create the target BSP. Currently, this defaults to boot_chain_storage_qspi.cfg. As an example, if you run the bind command:
make -f Makefile.bind PCT=qnx BOARD=e3550b03-t194 … [OPTIONS]
the resulting boot chains are:
[partition]
name=A_qspi_chain
allocation_policy=sequential
filesystem_type=basic
size=0x1EC0000
partition_attribute=0x40000002
sub_cfg_file=boot_chain_storage_qspi.cfg
virtual_storage_ivc_ch=0x84803A77
[partition]
name=B_qspi_chain
allocation_policy=sequential
filesystem_type=basic
size=0x1EC0000
partition_attribute=0x40000002
sub_cfg_file=boot_chain_storage_qspi.cfg
virtual_storage_ivc_ch=0x84803576
The virtual_storage_ivc_ch depends on the VSC server and may be different than above. If you would like to use a custom sub config file for the platform rather than the default boot_chain_storage_qspi.cfg for either chain A or chain B, then use the make option CHAIN_A_CONFIG or CHAIN_B_CONFG to override the default sub config values. As an example, if you wish to change chain A storage to a custom configuration /tmp/myconfig.cfg issue the following command:
make -f Makefile.bind PCT=qnx BOARD=e3550b03-t194 CHAIN_A_CONFIG=/tmp/myconfig.cfg … [OPTIONS]
The resulting configuration is:
[partition]
name=A_qspi_chain
allocation_policy=sequential
filesystem_type=basic
size=0x1EC0000
partition_attribute=0x40000002
sub_cfg_file=/tmp/myconfig.cfg
virtual_storage_ivc_ch=0x84803A77
[partition]
name=B_qspi_chain
allocation_policy=sequential
filesystem_type=basic
size=0x1EC0000
partition_attribute=0x40000002
sub_cfg_file=boot_chain_storage_qspi.cfg
virtual_storage_ivc_ch=0x84803576
Use an absolute path to the configuration file if it does not reside in the virtualization folder for the given target and platform. The file is not checked to be valid or that the path exists. If the path is invalid, an error is thrown during the flashing process.