Tool/software:
Hi Support Team,
I am trying to update my bsp from PROC-SDK-09.01.00.08 to PROC-SDK-09.02.01.10.
CONFIG_SPL_VIDEO is "y" by default in am62x_evm_a53_defconfig file. I have a .patch related to enable backlight splash screen in u-boot which is working without error in the previous bsp. It removes CONFIG_SPL_VIDEO from the defconfig file.
When I apply the patch file to the newer bsp and try to compile I see this error:
CC spl/drivers/clk/clk-uclass.o
/home/berkay/ti-processor-sdk-linux-am62xx-evm-09.02.01.10/board-support/ti-u-boot-2023.04+gitAUTOINC+8366064208/common/fdt_support.c:1982:15: error: ‘gd_t’ {aka ‘volatile struct global_data’} has no member named ‘video_bottom’
1982 | if (gd->video_bottom == gd->video_top)
| ^~
/home/berkay/ti-processor-sdk-linux-am62xx-evm-09.02.01.10/board-support/ti-u-boot-2023.04+gitAUTOINC+8366064208/common/fdt_support.c:1982:35: error: ‘gd_t’ {aka ‘volatile struct global_data’} has no member named ‘video_top’
1982 | if (gd->video_bottom == gd->video_top)
| ^~
/home/berkay/ti-processor-sdk-linux-am62xx-evm-09.02.01.10/board-support/ti-u-boot-2023.04+gitAUTOINC+8366064208/common/fdt_support.c:1986:23: error: ‘gd_t’ {aka ‘volatile struct global_data’} has no member named ‘video_bottom’
1986 | mem.start = gd->video_bottom;
| ^~
/home/berkay/ti-processor-sdk-linux-am62xx-evm-09.02.01.10/board-support/ti-u-boot-2023.04+gitAUTOINC+8366064208/common/fdt_support.c:1987:21: error: ‘gd_t’ {aka ‘volatile struct global_data’} has no member named ‘video_top’
1987 | mem.end = gd->video_top - 1;
| ^~
/home/berkay/ti-processor-sdk-linux-am62xx-evm-09.02.01.10/board-support/ti-u-boot-2023.04+gitAUTOINC+8366064208/scripts/Makefile.build:256: recipe for target 'spl/common/fdt_support.o' failed
I also tried to change file like it does not remove CONFIG_SPL_VIDEO from the defconfig file, I was able to compile u-boot succesfully but, I was not able to boot with these u-boot images. The error is like this:
U-Boot SPL 2023.04-00004-gb771e0f0-dirty (Jun 27 2024 - 08:47:56 +0300)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.8--v09.02.08 (Kool Koala)')
SPL initial stack usage: 13408 bytes
Trying to boot from MMC2
mmc_load_image_raw_sector: mmc block read error
Authentication passed
Authentication passed
Authentication passed
Authentication passed
Authentication passed
Starting ATF on ARM64 core...
NOTICE: BL31: v2.10.0(release):v2.10.0-367-g00f1ec6b87-dirty
NOTICE: BL31: Built : 16:09:05, Feb 9 2024
U-Boot SPL 2023.04-00004-gb771e0f0-dirty (Jun 27 2024 - 08:48:07 +0300)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.8--v09.02.08 (Kool Koala)')
SPL initial stack usage: 1856 bytes
Error: inflate() returned -5
There is no valid bmp file at the given address
Trying to boot from MMC2
mmc_load_image_raw_sector: mmc block read error
Authentication passed
Authentication passed
U-Boot 2023.04-00004-gb771e0f0-dirty (Jun 27 2024 - 08:48:07 +0300)
SoC: AM62X SR1.0 HS-FS
Model: Texas Instruments AM625 SK
EEPROM not available at 80, trying to read at 81
Reading on-board EEPROM at 0x51 failed -121
DRAM: no bloblist found!1 GiB
Core: 71 devices, 32 uclasses, devicetree: separate
MMC: mmc@fa10000: 0, mmc@fa00000: 1
Loading Environment from nowhere... OK
"Synchronous Abort" handler, esr 0x96000044
elr: 0000000080859a24 lr : 00000000808599c0 (reloc)
elr: 00000000bff5ea24 lr : 00000000bff5e9c0
x0 : 00000000bdefb610 x1 : ffffffffff700000
x2 : ffffffffff958000 x3 : 0000000000000000
x4 : 0000000000000000 x5 : 0000000000000000
x6 : 00000000bdefb610 x7 : 0000000000000000
x8 : 00000000bded67a0 x9 : 0000000000000008
x10: 0000000000002004 x11: 00000000bded5adc
x12: 0000000000001fd0 x13: 0000000000000000
x14: 00000000bded67a0 x15: 0000000000000002
x16: 00000000bff5ea54 x17: 00000000bdefb9d0
x18: 00000000bdee5d80 x19: 0000000000000000
x20: 00000000bdee9530 x21: 00000000bded5dd0
x22: 0000000000007fff x23: 00000000deadbeef
x24: 0000000000000008 x25: 0000000000000000
x26: 00000000800ce6b4 x27: 0000000000000000
x28: 0000000000000000 x29: 00000000bded5d70
Code: f9401001 8b020022 eb02003f 54fffec2 (b8004433)
Resetting CPU ...
resetting ...
It keeps resetting. Do you have any advice for solution of this issue?