u-boot/board/keymile
Simon Glass 984639039f Rename CONFIG_SYS_TEXT_BASE to CONFIG_TEXT_BASE
The current name is inconsistent with SPL which uses CONFIG_SPL_TEXT_BASE
and this makes it imposible to use CONFIG_VAL().

Rename it to resolve this problem.

Signed-off-by: Simon Glass <sjg@chromium.org>
2022-10-31 11:01:31 -04:00
..
common Rename CONFIG_SYS_TEXT_BASE to CONFIG_TEXT_BASE 2022-10-31 11:01:31 -04:00
km83xx powerpc: remove support for kmtergr1 and MPC8309 2022-08-20 22:45:00 -04:00
kmcent2 event: Convert misc_init_f() to use events 2022-03-10 08:28:36 -05:00
pg-wcom-ls102xa event: Convert misc_init_f() to use events 2022-03-10 08:28:36 -05:00
scripts board/km: remove kirkwood boards 2022-10-06 10:13:38 +02:00
secu1 board/km: update MAINTAINERS files 2021-10-14 19:45:07 -04:00
Kconfig board/km: remove kirkwood boards 2022-10-06 10:13:38 +02: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.