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.

SK-AM64B: SD Card Boot Failed with the Default RT Linux Image

Part Number: SK-AM64B

Hi TI Experts,

Customer is working on SK-AM64B SDK9.2.

They used SD card boot, and used the below default image of SDK9.2 RT Linux SDK.

After the HW setup, when they boot this default image, they will see the below error.

U-Boot SPL 2023.04-ga97ca328b3 (Jan 08 2024 - 08:11:13 +0000)
EEPROM not available at 0x50, trying to read at 0x51
Resetting on cold boot to workaround ErrataID:i2331
Please resend tiboot3.bin in case of UART/DFU boot
resetting ...

Please see the picture of this chip below, I think this should be the HS device right so no need to change the tiboot3.bin?

We also have tried and followed the below guide to change the gp.bin to tiboot3.bin to make it as a GP board boot.

However, this time, after this single change, there is no log in the booting anymore.

We doubted this might be a bug for SDK9.2 RT Linux SDK image, so we have also tried the RT Linux SDK image in SDK8.6.

But we faced the same issue in SDK8.6 also.

Could you provide us any advice please?

Thanks a lot!

Kevin

  • Hi TI Experts,

    We thought this problem might related the rt-linux default image, so we tested and used non-rt linux default image in SDK9.2, but facing the same problem discussed above.

    Please help on this, thanks!

    Kevin

  • Hi TI Experts,

    We have double confirmed that our AM64B-SK is the HS device, so we do not need to do anything about the default tiboo3.bin. But we do not know why still face the problem here.

    U-Boot SPL 2023.04-ga97ca328b3 (Jan 08 2024 - 08:11:13 +0000)
    EEPROM not available at 0x50, trying to read at 0x51
    Resetting on cold boot to workaround ErrataID:i2331
    Please resend tiboot3.bin in case of UART/DFU boot
    resetting ...

    I have found a previous regarding to this same problem shown below, but it is based on SDK9.1.

    https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1314269/sk-am64b-sk-am64b-cannot-boot

    Based on the discussions in this thread, I think we should have solved this problem in SDK9.2 already, so not sure why still having this problem.

    Thanks for your help!

    Kevin

  • I'm attaching the working boot log with AM64x SDK 9.2 on SK-AM64B (PROC100A)
    Best,
    -Hong

    U-Boot SPL 2023.04-ga97ca328b3 (Jan 08 2024 - 08:11:13 +0000)
    EEPROM not available at 0x50, trying to read at 0x51
    Resetting on cold boot to workaround ErrataID:i2331
    Please resend tiboot3.bin in case of UART/DFU boot
    resetting ...
    
    U-Boot SPL 2023.04-ga97ca328b3 (Jan 08 2024 - 08:11:13 +0000)
    EEPROM not available at 0x50, trying to read at 0x51
    SYSFW ABI: 3.1 (firmware rev 0x0009 '9.1.8--v09.01.08 (Kool Koala)')
    SPL initial stack usage: 13384 bytes
    Trying to boot from MMC2
    Authentication passed
    Authentication passed
    Loading Environment from MMC... MMC Device 0 not found
    *** Warning - No MMC card found, using default environment
    
    Authentication passed
    Authentication passed
    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: 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-ga97ca328b3 (Jan 08 2024 - 08:11:13 +0000)
    SYSFW ABI: 3.1 (firmware rev 0x0009 '9.1.8--v09.01.08 (Kool Koala)')
    Trying to boot from MMC2
    Authentication passed
    Authentication passed
    
    
    U-Boot 2023.04-ga97ca328b3 (Jan 08 2024 - 08:11:13 +0000)
    
    SoC:   AM64X SR2.0 HS-FS
    Model: Texas Instruments AM642 SK
    Board: AM64B-SKEVM rev A
    DRAM:  2 GiB
    Core:  70 devices, 33 uclasses, devicetree: separate
    NAND:  0 MiB
    MMC:   mmc@fa00000: 1
    Loading Environment from nowhere... OK
    In:    serial@2800000
    Out:   serial@2800000
    Err:   serial@2800000
    Net:   Could not get PHY for ethernet@8000000port@1: addr 0
    am65_cpsw_nuss_port ethernet@8000000port@1: phy_connect() failed
    eth1: ethernet@8000000port@2
    Hit any key to stop autoboot:  2  0 
    => md.l 0x43000030 1
    43000030: 00000243                             C...
    => 

  • Hi Hong,

    I have tested it on my end also, we found that this is related to the SD card problem.

    We found that below SD card could work.

    The below SD cards could not work.

    I have suggested customers to install the put up 10k resistor as suggested in this guide.

    https://www.ti.com/lit/ug/spruiy9b/spruiy9b.pdf?ts=1708916097961&ref_url=https%253A%252F%252Fe2e.ti.com%252F

    Kind Regards,

    Kevin