• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 72 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Original question:

AM620-Q1: Issue with Loading tispl.bin on AM62x(HS-FS) Custom Board Using SDK 8.06

AM623: Issues after loading tispl.bin_HS on sdk 8.6.4 via UART

Nikolay Tzankov
Prodigy 10 points
Part Number: AM623

Tool/software:

Hello,

We have been working on getting an HS part to boot, but without much success. This forum post is exactly the issue we have been experiencing.

AM620-Q1: Issue with Loading tispl.bin on AM62x(HS-FS) Custom Board Using SDK 8.06

Running on custom hardware, GP part of same type has been tested on the exact same hardware and is programmed just fine through UART.

Loading tiboot3.bin_hs works fine, but then hangs on the loading tispl.bin_hs on the Arm trusted firmware binary. This is only an issue with the HS part, the GP part on the exact same hardware runs fine.

Binaries were loaded through minicom with xModem for tiboot3.bin_hs and yModem for tispl.bin_hs

Build scripts are taken from this website and images are signed with default keys provided by TI. software-dl.ti.com/.../UG-General-Info.html

Here are the bootlogs:

02000000011a0000616d3632780000000000000048534653010001000100010002a6000000000000d68ecb2c055dff11ade95bd927e837d2a53bc23b0a2800cebce4f106bcf309df2213912d77a157C
U-Boot SPL 2021.01-00001-ga347ec164e-dirty (Jul 30 2025 - 15:12:57 -0600)                                             
SYSFW ABI: 3.1 (firmware rev 0x0008 '8.6.4--v08.06.04 (Chill Capybar')                                                
SPL initial stack usage: 13424 bytes                                                                                  
Trying to boot from UART                                                                                              
CCxyzModem - CRC mode, 7219(SOH)/0(STX)/0(CAN) packets, 7 retries                                                     
Loaded 923672 bytes                                                                                                   
init_env from device 7 not supported!                                                                                 
## No elf image at address 0x89000000                                                                                 
Starting ATF on ARM64 core...

Thank you in advance,

Nikolay

  • 0
    TI__Guru**** 168211 points

    Hi Nikolay,

    I know this won't directly answer your question, but is this a new project using AM623? Why you still use SDK8.6, which is already a few years old and no longer supported on this forums. Most importantly, due to the PLL sequencing issue (documented in Errata i2424), you should move to SDK10.0 or newer.

  • 0 in reply to Bin Liu
    Prodigy 10 points

    Hi Bin,

    No, this project has been in the works for at least 2 years now. It has been discussed to move to 9.x sdk, and even then the team has complained that this would can a lot of pain points, at least before the official release of the product.

    Any ideas about how what could be the cause here?

  • +1 in reply to Nikolay Tzankov
    Prodigy 10 points

    I was able to find a workaround to the problem. If I load tiboot3.bin_hs, then load the regular tispl.bin and u-boot.bin (meant for GP devices), the HS-FS part will still load the bootloaders. The issue appears to be with the image signing/reading of the ATF, OPTEE ,and IPC binaries.

    Here is a bootlog 

    U-Boot SPL 2021.01-00001-ga347ec164e-dirty (Jul 31 2025 - 08:59:41 -0600)
SYSFW ABI: 3.1 (firmware rev 0x0008 '8.6.4--v08.06.04 (Chill Capybar')
SPL initial stack usage: 13424 bytes
Trying to boot from SPI
Authentication passed
Authentication passed
Authentication passed
Warning: Did not detect image signing certificate. Skipping authentication to prevent boot failure. This will fail on Security Enforcing(HS-SE) devices
Warning: Did not detect image signing certificate. Skipping authentication to prevent boot failure. This will fail on Security Enforcing(HS-SE) devices
Starting ATF on ARM64 core...

NOTICE:  BL31: v2.8(release):v2.8-226-g2fcd408bb3-dirty
NOTICE:  BL31: Built : 05:33:19, Feb 24 2023

U-Boot SPL 2021.01-00001-ga347ec164e-dirty (Jul 31 2025 - 08:36:46 -0600)
SYSFW ABI: 3.1 (firmware rev 0x0008 '8.6.4--v08.06.04 (Chill Capybar')
Trying to boot from SPI
Warning: Did not detect image signing certificate. Skipping authentication to prevent boot failure. This will fail on Security Enforcing(HS-SE) devices
Warning: Did not detect image signing certificate. Skipping authentication to prevent boot failure. This will fail on Security Enforcing(HS-SE) devices


U-Boot 2021.01-00001-ga347ec164e-dirty (Jul 31 2025 - 08:36:46 -0600)

SoC:   AM62X SR1.0 HS-FS
Model: Texas Instruments AM625 SK - 1GB LPDDR4
DRAM:  1 GiB
Loading Environment from SPIFlash... SF: Detected s28hs01gt with page size 256 Bytes, erase size 256 KiB, total 128 MiB
OK
In:    serial@2800000
Out:   serial@2800000
Err:   serial@2800000
Net:   am65_cpsw_nuss_port ethernet@8000000port@1: can't parse phy-handle port 1 (-2)
eth0: ethernet@8000000port@1
Hit any key to stop autoboot:  0 
SF: Detected s28hs01gt with page size 256 Bytes, erase size 256 KiB, total 128 MiB
SF: Detected s28hs01gt with page size 256 Bytes, erase size 256 KiB, total 128 MiB
device 0 offset 0x5580000, size 0xa00000
SF: 10485760 bytes @ 0x5580000 Read: OK
device 0 offset 0x6980000, size 0x40000
SF: 262144 bytes @ 0x6980000 Read: OK
   Uncompressing Kernel Image
## Flattened Device Tree blob at 88000000
   Booting using the fdt blob at 0x88000000
   Loading Device Tree to 000000008fef0000, end 000000008fffffff ... OK

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]