TMDX654IDKEVM: TMDX654IDKEVM boot error CONFIG_SYS_SPL_MALLOC_SIZE

Hello,

I will see if I can replicate your observations over the next couple of days. Feel free to ping the thread if I have not replied by Thursday.

Regards,

Nick

Hello Pavle,

Apologies, looks like I lost your thread. Do you still require assistance here?

Regards,

Nick

Hi Nick,
I managed to boot TMDX654IDKEVM board flashing wic file on SD card provided for version 08.06.00.47. here:
https://dr-download.ti.com/software-development/software-development-kit-sdk/MD-diW9VClvQJ/08.06.00.47/tisdk-default-image-am65xx-evm.wic.xz

What I did I just replaced sysfw.itb with sisfw-am65xx-evm.itb on boot partition.

The issue still remains with the latest SDK version 09.01.00.01.
https://dr-download.ti.com/software-development/software-development-kit-sdk/MD-diW9VClvQJ/09.01.00.01/tisdk-default-image-am65xx-evm.wic.xz

I am not able to boot the board. The sisfw-am65xx-evm.itb is missing and there are sysfw-am65x_sr2-gp-evm.itb and sysfw-am65x_sr2-hs-evm.itb but with none of them TMDX654IDKEVM start u-boot.

Best regards, 
Pavle

Hello Pavle,

I will try to replicate your results tomorrow. I usually use BalenaEtcher to write the SD card, so I will use that SD card flashing method.

The board should boot the default filesystem out-of-the-box without modifying any of the files in it.

Please confirm what version of the AM65x IDK you are using. If you are not sure, feel free to take a picture and attach it here for me to check.

Regards,

Nick

Hi Nick, 

Thanks for the support. I also used BalenaEatcher tool to create the SD card. The board I am using was purchased few years ago. PCB REV is E3 and ASSM revision is 1.0.

Best regards, Pavle

Hello Pavle,

One thing to keep in mind is that the E3 board has AM65x Silicon Revision 1 (SR 1) instead of SR2. We do not support customers going to production with SR1.

When I test with an AM65x IDK with SR2, the default filesystem for Linux SDK 9.1 boots just fine:

U-Boot SPL 2023.04-gc1c2bdf272 (Nov 30 2023 - 18:17:44 +0000)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.1.8--v09.01.08 (Kool Koala)')
SPL initial stack usage: 1424 bytes
Trying to boot from MMC2
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Starting ATF on ARM64 core...

NOTICE:  BL31: v2.9(release):v2.9.0-614-gd7a7135d32-dirty
NOTICE:  BL31: Built : 09:34:15, Aug 24 2023
I/TC:
I/TC: OP-TEE version: 4.0.0 (gcc version 11.4.0 (GCC)) #1 Fri Oct 20 18:29:31 UTC 2023 aarch64
I/TC: WARNING: This OP-TEE configuration might be insecure!
I/TC: WARNING: Please check https://optee.readthedocs.io/en/latest/architecture/porting_guidelines.html
I/TC: Primary CPU initializing
I/TC: SYSFW ABI: 3.1 (firmware rev 0x0009 '9.1.8--v09.01.08 (Kool Koala)')
I/TC: HUK Initialized
I/TC: Activated SA2UL device
I/TC: Fixing SA2UL firewall owner for GP device
I/TC: Enabled firewalls for SA2UL TRNG device
I/TC: SA2UL TRNG initialized
I/TC: SA2UL Drivers initialized
I/TC: Primary CPU switching to normal world boot

U-Boot SPL 2023.04-gc1c2bdf272 (Nov 30 2023 - 18:17:44 +0000)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.1.8--v09.01.08 (Kool Koala)')
Trying to boot from MMC2
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted


U-Boot 2023.04-gc1c2bdf272 (Nov 30 2023 - 18:17:44 +0000)

SoC:   AM65X SR2.0 GP
Model: Texas Instruments AM654 Base Board
Board: AM6-COMPROCEVM rev B
DRAM:  4 GiB
Core:  119 devices, 31 uclasses, devicetree: separate
MMC:   mmc@4f80000: 0, mmc@4fa0000: 1
Loading Environment from nowhere... OK
In:    serial
Out:   serial
Err:   serial
am65_cpsw_nuss ethernet@46000000: K3 CPSW: nuss_ver: 0x6BA00102 cpsw_ver: 0x6BA80102 ale_ver: 0x00293904 Ports:1 mdio_freq:1000000
Detected: AM6-IDKAPPEVM rev A
Detected: SER-PCIE2LEVM rev A
Net:   eth0: ethernet@46000000port@1
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc1 is current device
SD/MMC found on device 1
Failed to load 'boot.scr'
574 bytes read in 25 ms (21.5 KiB/s)
Loaded env from uEnv.txt
Importing environment from mmc1 ...
## Error: "main_cpsw0_qsgmii_phyinit" not defined
20302336 bytes read in 241 ms (80.3 MiB/s)
66697 bytes read in 28 ms (2.3 MiB/s)
Working FDT set to 88000000
11685 bytes read in 27 ms (421.9 KiB/s)
2333 bytes read in 27 ms (84 KiB/s)
## Flattened Device Tree blob at 88000000
   Booting using the fdt blob at 0x88000000
Working FDT set to 88000000
   Loading Device Tree to 000000008feec000, end 000000008fffffff ... OK
Working FDT set to 8feec000

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[    0.000000] Linux version 6.1.46-g5da2f861d7 (oe-user@oe-host) (aarch64-oe-linux-gcc (GCC) 11.4.0, GNU ld (GNU Binutils) 2.38.20220708) #1 SMP PREEMPT Thu Nov 30 22:19:30
 UTC 2023
[    0.000000] Machine model: Texas Instruments AM654 Base Board
[    0.000000] earlycon: ns16550a0 at MMIO32 0x0000000002800000 (options '')
[    0.000000] printk: bootconsole [ns16550a0] enabled
[    0.000000] efi: UEFI not found.
.
.
.
am65xx-evm login: root
root@am65xx-evm:~# uname -a
Linux am65xx-evm 6.1.46-g5da2f861d7 #1 SMP PREEMPT Thu Nov 30 22:19:30 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux

However, when I pulled out an E3 board like you have, I was not able to get any response on the terminal with Linux SDK 9.1 or SDK 8.4.

If I recall properly, we stopped testing SR1 at some point with the AM65x SDK releases, but I cannot find any documentation about it in the SDK release notes to tell us exactly WHEN we stopped supporting that silicon revision. I will ask around to see if I can get some details.

Regards,

Nick