mirror of
https://github.com/AsahiLinux/u-boot
synced 2024-12-04 02:20:25 +00:00
8b71b20e0e
When the TAMP register 20 have an invalid value (0x0 for example after
TAMPER error) the "boot_device" U-Boot env variable have no value and
no error is displayed in U-Boot log.
The STM32MP boot command bootcmd_stm32mp failed with strange trace:
"Boot over !"
and the next command in bootcmd_stm32mp failed with few indication:
if test ${boot_device} = serial || test ${boot_device} = usb;
then stm32prog ${boot_device} ${boot_instance};
As it is difficult to investigate, the current patch avoids this issue:
- change the debug message to error: "unexpected boot mode" is displayed
- display trace "Boot over invalid!" in bootcmd_stm32mp
- execute "run distro_bootcmd" to try all the possible target
Signed-off-by: Patrick Delaunay <patrick.delaunay@foss.st.com>
Reviewed-by: Patrice Chotard <patrice.chotard@foss.st.com>
|
||
|---|---|---|
| .. | ||
| cmd_stm32prog | ||
| include/mach | ||
| boot_params.c | ||
| bsec.c | ||
| cmd_stm32key.c | ||
| config.mk | ||
| cpu.c | ||
| dram_init.c | ||
| fdt.c | ||
| Kconfig | ||
| Makefile | ||
| psci.c | ||
| pwr_regulator.c | ||
| spl.c | ||
| syscon.c | ||