• State
  • Locked Locked
  • Replies 14 replies
  • Subscribers 99 subscribers
  • Views 529 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.

SK-AM68: Board is looping while trying to boot up.

Rishad KP
Prodigy 40 points
Part Number: SK-AM68
Other Parts Discussed in Thread: AM68

Tool/software:

Greetings TI team,

We recently purchased SK-AM68 development board to design and develop a security surveillance system. We flashed the latest image (https://dr-download.ti.com/software-development/software-development-kit-sdk/MD-O34VjGn5mM/09.02.00.05/tisdk-edgeai-image-j721s2-evm.wic.xz) loaded through SD card on the board for testing. Initially the testing was going fine but to our surprise the board suddenly stopped working , we noticed this through the peripherals (Hdmi and other ports were not taking power). While checking through the serial terminal we noticed that board was not booting up properly (serial port log is attached below), We've already tried re-flashing the image to SD card but it was of no use. As I'm new to this system and also very much of beginner in embedded Linux could you please help us to debug this issue? Any sort of help and guidance from the expert team will be of a mammoth help for our team.

Looking forward for your responses,

Rishad

SK-AM68 Serial log is given below:

U-Boot SPL 2023.04-ti-gf9b966c67473 (Mar 19 2024 - 20:31:40 +0000)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.4--v09.02.04 (Kool Koala)')
EEPROM not available at 0x50, trying to read at 0x51
SPL initial stack usage: 13472 bytes
Trying to boot from MMC2
Authentication passed
Authentication passed
Authentication passed
Loading Environment from nowhere... OK
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
I/TC:
I/TC: OP-TEE version: 4.1.0-51-g012cdca49 (gcc version 11.4.0 (GCC)) #1 Tue Jan 30 10:48:03 UTC 2024 aarch64
I/TC: WARNING: This OP-TEE configuration might be insecure!
I/TC: WARNING: Please check optee.readthedocs.io/.../porting_guidelines.html
I/TC: Primary CPU initializing
I/TC: GIC redistributor base address not provided
I/TC: Assuming default GIC group status and modifier
I/TC: SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.4--v09.02.04 (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-ti-gf9b966c67473 (Mar 19 2024 - 20:31:40 +0000)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.4--v09.02.04 (Kool Koala)')
Trying to boot from MMC2
Authentication passed
Authentication passed


U-Boot 2023.04-ti-gf9b966c67473 (Mar 19 2024 - 20:31:40 +0000)

SoC:   J721S2 SR1.0 HS-FS
Model: Texas Instruments AM68 SK
Board: AM68-SK-SOM rev E2
DRAM:  2 GiB (effective 16 GiB)
Core:  74 devices, 32 uclasses, devicetree: separate
Flash: 0 Bytes
MMC:   mmc@4fb0000: 1
Loading Environment from nowhere... OK
In:    serial@2880000
Out:   serial@2880000
Err:   serial@2880000
am65_cpsw_nuss ethernet@46000000: K3 CPSW: nuss_ver: 0x6BA02102 cpsw_ver: 0x6BA82102 ale_ver: 0x00293904 Ports:1 mdio_freq:1000000
Net:   eth0: ethernet@46000000port@1                                                                                                                                                                     

Hit any key to stop autoboot:  0

NOR | Minicom 2.8 | VT102 | Offline | ttyUSB2

  • 0
    TI__Guru**** 163290 points

    Hi,

    Before I loop in our board expert. Can you answer the below questions:

    • Is the hang consistently after the "Hit any key to stop autoboot: 0"?
    • How about the LEDs on board do they stop glowing as well?
    • Can you press enter after that "Hit any key to stop autoboot: 0"?

    - Keerthy

  • 0
    Prodigy 40 points

    Hi ,

    • After "Hit any key to stop autoboot: 0" the system loads the bootloader again and it continously loops again.
    • The leds are working fine.
    • If any keys are pressed i can run the uboot commnds.

    Regards,

    Rishad

  • 0 in reply to Rishad KP
    TI__Guru**** 163290 points

    Hi Rishad,

    Can you halt at U-Boot prompt and just manually type:

    boot

    See if we still see a reboot? If you see more traces from kernel please share them. 

    Best Regards,

    Keerthy 

  • 0 in reply to Keerthy J
    Prodigy 40 points

    Hi Keerthy,

    When entering boot into u-boot prompt nothing happens, the board is still looping in booting stage. The log is given below.

    Regards,

    Rishad

    U-Boot SPL 2023.04-ti-gf9b966c67473 (Mar 19 2024 - 20:31:40 +0000)
    SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.4--v09.02.04 (Kool Koala)')
    EEPROM not available at 0x50, trying to read at 0x51
    SPL initial stack usage: 13472 bytes
    Trying to boot from MMC2
    Authentication passed
    Authentication passed
    Authentication passed
    Loading Environment from nowhere... OK
    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
    I/TC:
    I/TC: OP-TEE version: 4.1.0-51-g012cdca49 (gcc version 11.4.0 (GCC)) #1 Tue Jan4
    I/TC: WARNING: This OP-TEE configuration might be insecure!
    I/TC: WARNING: Please check optee.readthedocs.io/.../architecturel
    I/TC: Primary CPU initializing
    I/TC: GIC redistributor base address not provided
    I/TC: Assuming default GIC group status and modifier
    I/TC: SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.4--v09.02.04 (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-dirty (Jul 03 2024 - 17:21:57 +0530)
    SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.4--v09.02.04 (Kool Koala)')
    Trying to boot from MMC2
    Authentication passed
    Authentication passed


    U-Boot 2023.04-dirty (Jul 03 2024 - 17:21:57 +0530)

    SoC: J721S2 SR1.0 HS-FS
    Model: Texas Instruments AM68 SK
    Board: AM68-SK-SOM rev E2
    DRAM: 2 GiB (effective 16 GiB)
    Core: 74 devices, 32 uclasses, devicetree: separate
    Flash: 0 Bytes
    MMC: mmc@4fb0000: 1
    Loading Environment from nowhere... OK
    In: serial@2880000
    Out: serial@2880000
    Err: serial@2880000
    am65_cpsw_nuss ethernet@46000000: K3 CPSW: nuss_ver: 0x6BA02102 cpsw_ver: 0x6BA0
    Net: eth0: ethernet@46000000port@1
    Hit any key to stop autoboot: 0
    => boot

    U-Boot SPL 2023.04-ti-gf9b966c67473 (Mar 19 2024 - 20:31:40 +0000)
    SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.4--v09.02.04 (Kool Koala)')
    EEPROM not available at 0x50, trying to read at 0x51
    SPL initial stack usage: 13472 bytes
    Trying to boot from MMC2
    Authentication passed
    Authentication passed
    Authentication passed
    Loading Environment from nowhere... OK
    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
    I/TC:
    I/TC: OP-TEE version: 4.1.0-51-g012cdca49 (gcc version 11.4.0 (GCC)) #1 Tue Jan4
    I/TC: WARNING: This OP-TEE configuration might be insecure!
    I/TC: WARNING: Please check optee.readthedocs.io/.../architecturel
    I/TC: Primary CPU initializing
    I/TC: GIC redistributor base address not provided
    I/TC: Assuming default GIC group status and modifier
    I/TC: SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.4--v09.02.04 (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-dirty (Jul 03 2024 - 17:21:57 +0530)
    SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.4--v09.02.04 (Kool Koala)')
    Trying to boot from MMC2
    Authentication passed
    Authentication passed


    U-Boot 2023.04-dirty (Jul 03 2024 - 17:21:57 +0530)

    SoC: J721S2 SR1.0 HS-FS
    Model: Texas Instruments AM68 SK
    Board: AM68-SK-SOM rev E2
    DRAM: 2 GiB (effective 16 GiB)
    Core: 74 devices, 32 uclasses, devicetree: separate
    Flash: 0 Bytes
    MMC: mmc@4fb0000: 1
    Loading Environment from nowhere... OK
    In: serial@2880000
    Out: serial@2880000
    Err: serial@2880000
    am65_cpsw_nuss ethernet@46000000: K3 CPSW: nuss_ver: 0x6BA02102 cpsw_ver: 0x6BA0
    Net: Could not get PHY for ethernet@46000000port@1: addr 0
    am65_cpsw_nuss_port ethernet@46000000port@1: phy_connect() failed
    No ethernet found.

    Hit any key to stop autoboot: 0

    U-Boot SPL 2023.04-ti-gf9b966c67473 (Mar 19 2024 - 20:31:40 +0000)
    SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.4--v09.02.04 (Kool Koala)')
    EEPROM not available at 0x50, trying to read at 0x51
    SPL initial stack usage: 13472 bytes
    Trying to boot from MMC2
    Authentication passed
    Authentication passed
    Authentication passed
    Loading Environment from nowhere... OK
    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
    I/TC:
    I/TC: OP-TEE version: 4.1.0-51-g012cdca49 (gcc version 11.4.0 (GCC)) #1 Tue Jan4
    I/TC: WARNING: This OP-TEE configuration might be insecure!
    I/TC: WARNING: Please check optee.readthedocs.io/.../architecturel
    I/TC: Primary CPU initializing
    I/TC: GIC redistributor base address not provided
    I/TC: Assuming default GIC group status and modifier
    I/TC: SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.4--v09.02.04 (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-dirty (Jul 03 2024 - 17:21:57 +0530)
    SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.4--v09.02.04 (Kool Koala)')
    Trying to boot from MMC2
    Authentication passed
    Authentication passed


    U-Boot 2023.04-dirty (Jul 03 2024 - 17:21:57 +0530)

    SoC: J721S2 SR1.0 HS-FS
    Model: Texas Instruments AM68 SK
    Board: AM68-SK-SOM rev E2
    DRAM: 2 GiB (effective 16 GiB)
    Core: 74 devices, 32 uclasses, devicetree: separate
    Flash: 0 Bytes
    MMC: mmc@4fb0000: 1
    Loading Environment from nowhere... OK
    In: serial@2880000
    Out: serial@2880000
    Err: serial@2880000
    am65_cpsw_nuss ethernet@46000000: K3 CPSW: nuss_ver: 0x6BA02102 cpsw_ver: 0x6BA0
    Net: Could not get PHY for ethernet@46000000port@1: addr 0
    am65_cpsw_nuss_port ethernet@46000000port@1: phy_connect() failed
    No ethernet found.

  • 0
    TI__Guru**** 163290 points

    Hi Rishad,

    Rishad KP said:
    We've already tried re-flashing the image to SD card but it was of no use

    Can you reflash the image to a new SD card? Just to make sure SD card is not the issue. If that fails I will loop in our board expert to check.

    - Keerthy

  • 0
    Prodigy 40 points

    Hi Keerthy,

    We've re-flashed another SD card also but still the results are the same.

    Regards,

    Rishad

  • 0 in reply to Rishad KP
    TI__Guru**** 163290 points

    Hi Rishad,

    I will loop in our hardware expert.

    - Keerthy

  • 0 in reply to Keerthy J
    TI__Guru 52335 points

    What size power supply are you using?  Any other connected peripherals (other than PC for terminal access and SD card for booting)?

  • 0
    Prodigy 40 points

    Hi Robert,

    We're using a HP laptop charger with specified power requirement (20V - 3.25A - 65W)

    -Rishad

  • 0 in reply to Rishad KP
    TI__Guru 52335 points

    Since there is no error provided in the log - I'm guessing there is a power issue of some kind.   Can you try removing and re-installing the small processor board?  Maybe its not making good connection.

  • 0 in reply to Robert Eschler
    Prodigy 40 points

    Hi Robert,

    We tried removing and re-installing and came across to new errors while trying to boot device. these logs are attached below.

    - Rishad

  • 0 in reply to Rishad KP
    TI__Guru 52335 points

    Again - it looks like the board is not making good connection.  Can you try re-seating a few times? 

  • 0 in reply to Robert Eschler
    Prodigy 40 points

    When using another sd card with a previous version the board got booted up. But CSI ports are not detecting cameras connected. cameras we're using are IMX219.

    - Rishad

  • 0 in reply to Rishad KP
    TI__Guru**** 163290 points

    Hi Rishad,

    What you mean by SD card with a previous version? Is that previous version of sd card or previous version of SDK?

    Also please share the logs as a text attachment.

    Best Regards,

    Keerthy