trdx-image-fstype: implement migration to V2.4

The migration to BSP V2.4 is somewhat more complex due to ECC level
change. The scripts detect whether we are on a new or old module by
checking the NAND driver type (which probably reflects best which
ECC level has been used). In case the NAND driver has the old name
(fsl_nfc), then the script assumes that migration is required:
The migration script runs in two stages:
- The first part updates U-Boot, erases the root file system and
loads the config block into memory (upgrade_part1).
- After reboot, the second stage runs with the new U-Boot version.
The script update the boot configuration block (BCB), restores the
config block from memory and U-Boot is written again using the
new ECC level. Then, the script erases the UBI partition (which
contains the root filesystem) and recreates it using the new ECC
level too (upgrade_part2).

Since we keep the config block temporarly in RAM, the whole update
process should not be interrupted! In case it did, the new U-Boot
version is able to restore the configuration block from command
line.

In contrast to older update scripts, the standard upgrade procedure
does not erase the whole UBI partition anymore. This makes sure that
wear-leveling information can be preserved.

1 files changed, 0 insertions, 0 deletions

diff --git a/recipes/images/files/colibri-vf/colibri-vf_bin/flash_blk.img b/recipes/images/files/colibri-vf/colibri-vf_bin/flash_blk.img
index 488a844..8141bad 100644
--- a/recipes/images/files/colibri-vf/colibri-vf_bin/flash_blk.img
+++ b/recipes/images/files/colibri-vf/colibri-vf_bin/flash_blk.img