In our sensor firmware images we would like to use two copies of u-boot. During the image update only one copy of u-boot shall be flashed.
As stated in BCT Overview the NVIDIA Tegra provides up to 4 bootloader informations in the BCT.
In the case something would went wrong during the u-boot update the boot mechanism could then fall back to the still working u-boot copy.
The Apalis Linux BSP v2.7Beta1 contains one single BTC file (PM375_Hynix_2GB_H5TC4G63AFR_RDA_924MHz.bct).
Does the BCT file support redundant bootloaders?
What would we have to configure (e.g. location, size, load address, execution address, etc.)?
How would we have to configure these values?
We looked into the BCT file using “bct_dump” and wondered about a string stating that 0 of 4 bootloaders are used (‘# Bootloader used = 0; # Bootloaders max = 4;’)?
We could also not find the regions in the file which address the bootloader. Where can we find that info and what does it contain?
For the case that the contained BCT files does not support redundant bootloaders could we create the BCT ourself?