Flashing Customization

Select Boot Chain Platform Configuration

Within the board support package (BSP) with Virtualization support the top-level configuration file global_storage.cfgdefines the sub configuration file used to create the target BSP. Currently, this defaults to boot_chain_storage.cfg. As an example, if you run the bind command:

the resulting boot chains are:

[partition]
name=A_qspi_chain
allocation_policy=sequential
filesystem_type=basic
size=0x840000
partition_attribute=0x40000002
virtual_storage_ivc_ch=0x83802762
sub_cfg_file=boot_chain_storage.cfg
[partition]
name=B_qspi_chain
allocation_policy=sequential
filesystem_type=basic
size=0x840000
partition_attribute=0x40000002
virtual_storage_ivc_ch=0x83802863
sub_cfg_file=boot_chain_storage.cfg

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.cfg for either chain A or chain B, then replace cfg file path of sub_cfg_file=boot_chain_storage.cfg in global_storage.cfg file to your config file and run the bind command again. For instance, edit to sub_cfg_file=/tmp/myconfig.cfg under name=A_qspi_chain partition and execute the bind command.

The resulting configuration is:

[partition]
name=A_qspi_chain
allocation_policy=sequential
filesystem_type=basic
size=0x840000
partition_attribute=0x40000002
virtual_storage_ivc_ch=0x83802762
sub_cfg_file=/tmp/myconfig.cfg
[partition]
name=B_qspi_chain
allocation_policy=sequential
filesystem_type=basic
size=0x840000
partition_attribute=0x40000002
virtual_storage_ivc_ch=0x83802863
sub_cfg_file=boot_chain_storage.cfg
       

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.