Loading Device Tree to 8fb8a000, end 8fb9cedd. Loading Ramdisk to 8fb9d000, end 8ffff7cc. Uboot_overlays: add to /boot/uEnv.txt to enable. Uboot_overlays: disabling as dtb=xxxxx.dtb is set in /boot/uEnv.txt. Uboot_overlays: dtb=xxxxx.dtb is set in /boot/uEnv.txt, unable to use. Press SPACE to abort autoboot in 2 secondsĬhecking if uname_r is set in /boot/uEnv.txt. Reset Source: Power-on reset has occurred.īeagleBone: cape eeprom: i2c_probe: 0x54:īeagleBone: cape eeprom: i2c_probe: 0x55:īeagleBone: cape eeprom: i2c_probe: 0x56:īeagleBone: cape eeprom: i2c_probe: 0x57: ** Unable to read "/boot/uboot.env" from mmc0:1 ** What do you suggest to debug this? Is there a way to specify a default board id to load from EEPROM if a problem is encountered reading the EEPROM?
#U BOOT ENABLE DEBUG MESSAGES CODE#
Unfortunately I don’t see a reason in the new code why my board would not be loaded. Why would the older U-Boot load and the newer U-Boot fail? My thoughts right now is that the EEPROM is either empty or contains a board id that U-Boot doesn’t recognize, and either way U-Boot has had changes between these two versions that don’t provide a fallback.ĭiff’s between board/ti/common/board_detect.c show changes to the i2c eeprom read that could be causing this behavior, specifically the removal of method ti_i2c_set_alen. After booting once from U-Boot 2018.09 and powering off, the sd card with U-Boot 2019.04 loads as expected, displays splash message and boots from sd card.U-Boot SPL from 2018.09 loads as expected, displays splash message and boots image from sd card.U-Boot SPL from 2019.04 produces no splash message and appears to not load at all.
I’m having issues loading U-Boot SPL on a custom board based on :
0 kommentar(er)
