Aleksandar Gerasimovski 987b182830 km/ls102xa: use unused scratchrw4 address for post word vor 2 Jahren
..
common efe19295a5 km: common: implement field fail-safe u-boot update vor 2 Jahren
km83xx 35b2b5f04c board/km: update MAINTAINERS files vor 2 Jahren
km_arm 35b2b5f04c board/km: update MAINTAINERS files vor 2 Jahren
kmcent2 e4c3ce7e28 CONFIG_SYS_CLK_FREQ: Consistently be static or get_board_sys_clk() vor 2 Jahren
pg-wcom-ls102xa 987b182830 km/ls102xa: use unused scratchrw4 address for post word vor 2 Jahren
scripts fbb0e15a42 km/scripts: fix saveenv command syntax vor 3 Jahren
secu1 35b2b5f04c board/km: update MAINTAINERS files vor 2 Jahren
Kconfig efe19295a5 km: common: implement field fail-safe u-boot update vor 2 Jahren
README efe19295a5 km: common: implement field fail-safe u-boot update vor 2 Jahren

README

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.