diff options
| author | Aleksandar Gerasimovski <aleksandar.gerasimovski@hitachienergy.com> | 2021-12-10 11:07:53 +0100 |
|---|---|---|
| committer | Priyanka Jain <priyanka.jain@nxp.com> | 2022-02-01 15:08:07 +0530 |
| commit | efe19295a59dae28c1af813486fe88f34378a980 (patch) | |
| tree | e750362b8dc09b974e1f97f7e432bb66e52326cc /include | |
| parent | de144d5ffe0c15c56e3bbd64832bc4b265bd663f (diff) | |
| download | u-boot-efe19295a59dae28c1af813486fe88f34378a980.zip u-boot-efe19295a59dae28c1af813486fe88f34378a980.tar.gz u-boot-efe19295a59dae28c1af813486fe88f34378a980.tar.bz2 | |
km: common: implement field fail-safe u-boot update
This patch provides possibility for field fail-safe u-boot updates.
The implementation can be used on all pg-wcom boards that are booting from
parallel NOR flash.
When used in a board design, provided check_for_uboot_update function will
start new u-boot at defined location if updateduboot envvar is set to yes.
With this implementation it is expected that factory programmed u-boot
will always stay as it is, and optionally new u-boot can be safely
programmed by embedded software when the unit is rolled out on the field.
It is expected check_for_uboot_update to be called early in execution
before relocation (*_f) once SoC is basically initialized and environment
can be read, with this possibilities to not be able to fix a u-boot bug by
a u-boot update are reduced to minimum.
Signed-off-by: Aleksandar Gerasimovski <aleksandar.gerasimovski@hitachienergy.com>
Reviewed-by: Priyanka Jain <priyanka.jain@nxp.com>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions