u-boot/board/keymile
Simon Glass 1744ceb66f Correct SPL use of TARGET_PG_WCOM_SELI8
This converts 1 usage of this option to the non-SPL form, since there is
no SPL_TARGET_PG_WCOM_SELI8 defined in Kconfig

Signed-off-by: Simon Glass <sjg@chromium.org>
Aleksandar Gerasimovski <aleksandar.gerasimovski@hitachienergy.com>
2023-02-10 07:41:40 -05:00
..
common Correct SPL uses of PG_WCOM_UBOOT_UPDATE 2023-02-10 07:41:40 -05:00
km83xx km/ppc832x: join config files 2023-02-06 13:04:53 -05:00
kmcent2 global: Migrate CONFIG_ENV_TOTAL_SIZE to CFG 2022-12-23 10:08:35 -05:00
pg-wcom-ls102xa Correct SPL use of TARGET_PG_WCOM_SELI8 2023-02-10 07:41:40 -05:00
scripts board/km: remove kirkwood boards 2022-10-06 10:13:38 +02:00
secu1 board/km/secu: migrate to use environment text files 2022-12-12 16:49:25 -05:00
Kconfig event: Correct dependencies on the EVENT framework 2023-01-18 12:46:13 -05:00
README km: common: implement field fail-safe u-boot update 2022-02-01 15:08:07 +05:30

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

Field Fail-Save U-boot Update
-----------------------------
Field Fail-Save u-boot update is a feature that allows save u-boot update
of FOX and XMC products that are rolled out in the field.

The feature is initially implemented for designs based on LS102x SoC, but in
theory can be used on all designs that are booting from parallel NOR flash.

The implementation expects redundant (secondary) u-boot image on a predefined
location in the NOR flash, u-boot execution will be transferred to the redundant 
(secondary) u-boot and redundant u-boot will be started if 'updateduboot' envvar
is set to 'yes'.
Update logic check_for_uboot_update() has to be invoked from the design early
before relocation just after SoC initialization, e.g from board_early_init_f or
misc_init_f functions.
By design it is expected that primary u-boot image is burned in the factory and
never updated, and in case u-boot update is required it can flashed and started
from secondary u-boot location.