Hi Community Members,
I am using RDB3 Board. I have my build image generated for RDB3.
I am not able to boot my custom build image for RDB3 board whose boot logs are :
////////////////////////////////////////////////////////////////////
U-Boot 2022.04+g5a6f62071f+p0 (Sep 06 2024 - 07:11:20 +0000)
SoC: NXP S32G399A rev. 1.0
CPU: ARM Cortex-A53 r0p4 @ max 1300 MHz
Model: NXP S32G399A-RDB3
DRAM: 3.5 GiB
Core: 306 devices, 25 uclasses, devicetree: board
MMC: FSL_SDHC: 0
Loading Environment from MMC... OK
s32cc_serdes_phy serdes@40480000: Using mode 0 for SerDes subsystem
pci_s32cc pcie@40400000: Configuring as RootComplex
pci_s32cc pcie@40400000: Failed to get link up
In: serial@401c8000
Out: serial@401c8000
Err: serial@401c8000
Board revision: RDB3 Revision E
Hit any key to stop autoboot: 0
=>
=>
=> fatls mmc 0:1
15753224 Image
60416 s32g399a-rdb3.dtb
5439424 Kernel-Image
3 file(s), 0 dir(s)
=> fatload mmc 0:1 0x80000000 Kernel-Image
5439424 bytes read in 230 ms (22.6 MiB/s)
=> bootelf 0x80000000
=>
=>
=>
/////////////////////////////////////////////////////////////////
After giving bootelf at address 0x80000000, it dose not print anything.
With the new u-boot dose the load-address changes ?
But the same image with same steps works with BSP34 and BSP37.
Any inputs would be really helpful.
Regards,
Vishal G
