• State Resolved
  • Replies 4 replies
  • Subscribers 98 subscribers
  • Views 99 views
  • Users 0 members are here
Support feedback
Options
Options
Related

AM67: am67evm boot failed

Will Tsai
Prodigy 60 points
Part Number: AM67

Tool/software:

Hi

I was following the TI official guideline to install sdk and load a prebuilt image on the SD card.

Here is my workflow could you help me review if anything wrong steps that will cause the EVM can't boot up?

Enviroment

Ubuntu 22.04

Device: xj722s5a amw(am67 EVM)

Build & Load image step

  1. sudo -s
  2. install sdk under /opt/
  3. ./setup.sh
  4. make 
  5. make linux
  6. cd bin 
  7. ./create-sdcard.sh(the sd card include root and boot pattion
    i try using command line and also balena to create sd card
    And the image i use : tisdk-default-image-j722s-evm.rootfs.tar.xz
  8. use pinconcom 
  9. sudo picocom -b 115200 -r -l /dev/ttyUSB0(to see the log and it stuck in the boot flow
    it's keep repeat the first inital didn't enter to next step
    And i double check the boot folder include tiboot3.bin/ tispl.bin  / u-boot.img

-----------------------

error log

seamus@Linux-PC:/opt/ti-processor-sdk-linux-am67-sk-11_00_10_01/board-support/prebuilt-images$ sudo picocom -b 115200 -r -l /dev/ttyUSB0
[sudo] password for seamus:
picocom v3.1

port is : /dev/ttyUSB0
flowcontrol : none
baudrate is : 115200
parity is : none
databits are : 8
stopbits are : 1
escape is : C-a
local echo is : no
noinit is : no
noreset is : yes
hangup is : no
nolock is : yes
send_cmd is : sz -vv
receive_cmd is : rz -vv -E
imap is :
omap is :
emap is : crcrlf,delbs,
logfile is : none
initstring : none
exit_after is : not set
exit is : no

Type [C-a] [C-h] to see available commands
Terminal ready
Sciserver Testapp Built On: Mar 19 2025 10:50:19
Sciserver Version: 11.0.0-REL.MCUSDK.11.00.00.05+
RM_PM_HAL Version: v11.00.09
Starting Sciserver..... PASSED
[IPC RPMSG ECHO] Version: REL.MCUSDK.09.00.00.16 (Mar 19 2025 10:50:35):
Sciserver Testapp Built On: Mar 19 2025 10:50:19
Sciserver Version: 11.0.0-REL.MCUSDK.11.00.00.05+
RM_PM_HAL Version: v11.00.09
Starting Sciserver..... PASSED
[IPC RPMSG ECHO] Version: REL.MCUSDK.09.00.00.16 (Mar 19 2025 10:50:35):
Sciserver Testapp Built On: Mar 19 2025 10:50:19
Sciserver Version: 11.0.0-REL.MCUSDK.11.00.00.05+
RM_PM_HAL Version: v11.00.09
Starting Sciserver..... PASSED
[IPC RPMSG ECHO] Version: REL.MCUSDK.09.00.00.16 (Mar 19 2025 10:50:35):
Sciserver Testapp Built On: Mar 19 2025 10:50:19
Sciserver Version: 11.0.0-REL.MCUSDK.11.00.00.05+
RM_PM_HAL Version: v11.00.09
Starting Sciserver..... PASSED
[IPC RPMSG ECHO] Version: REL.MCUSDK.09.00.00.16 (Mar 19 2025 10:50:35):
Sciserver Testapp Built On: Mar 19 2025 10:50:19
Sciserver Version: 11.0.0-REL.MCUSDK.11.00.00.05+
RM_PM_HAL Version: v11.00.09
Starting Sciserver..... PASSED
[IPC RPMSG ECHO] Version: REL.MCUSDK.09.00.00.16 (Mar 19 2025 10:50:35):
Sciserver Testapp Built On: Mar 19 2025 10:50:19
Sciserver Version: 11.0.0-REL.MCUSDK.11.00.00.05+
RM_PM_HAL Version: v11.00.09
Starting Sciserver..... PASSED
[IPC RPMSG ECHO] Version: REL.MCUSDK.09.00.00.16 (Mar 19 2025 10:50:35):
Sciserver Testapp Built On: Mar 19 2025 10:50:19
Sciserver Version: 11.0.0-REL.MCUSDK.11.00.00.05+
RM_PM_HAL Version: v11.00.09
Starting Sciserver..... PASSED

  • 0
    TI__Prodigy 580 points

    Hi Will,

    Will Tsai said:
    ./create-sdcard.sh(the sd card include root and boot pattion

    Did you select option 1 ("Install pre-built images from SDK") when running create-sdcard.sh? If not, could you try running the script again from the bin folder in the SDK and choose option 1 when prompted. Let me know if this helps

    https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67/11_00_10_01/exports/docs/linux/Overview/Processor_SDK_Linux_create_SD_card.html#create-sd-card-with-default-images-using-script

    Regards,
    Johnson

  • 0
    TI__Prodigy 60 points

    Hi Johnson,

    Yes, i select the option 1 and it directly pass me to the filesystem folder.

    And i choose tisdk-default-image-j722s-evm.rootfs.tar.xz as a image in the SD card.

    What i know this image is provide from ti even i do make command, that should be nothing change for this image.

    Is it correct? or if i do anything action will change this default image?

    THX 

    Will 

  • 0 in reply to Johnson John
    TI__Prodigy 60 points

    Hi Johnson,

    Good news, after i load the wic image into the device, it finally shows some information as below.

    For this log, it seems like the SPL was successful initially, because of the version of fw was different.

    So, how do we find the correct tispl, boot tuboot , tiboot3.no.

    U-Boot SPL 2023.04-ti-gd2612223375a (Mar 13 2024 - 19:15:42 +0000) SYSFW ABI: 3.1 (firmware rev 0x0009 '9.0.6--w2023.01-j722s (Kool Koa') Trying to boot from MMC2 U-Boot SPL 2023.04-ti-gd2612223375a (Mar 13 2024 - 19:15:42 +0000) SYSFW ABI: 3.1 (firmware rev 0x0009 '9.0.6--w2023.01-j722s (Kool Koa') SPL initial stack usage: 17064 bytes Trying to boot from MMC2 Authentication passed Authentication passed Authentication passed 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 NOTICE: Upgrade Firmwares for Power off functionality ERROR: Failed to get response (-19) ERROR: Transfer send failed (-19) ERROR: Unable to query firmware capabilities (-19) U-Boot SPL 2023.04-ti-gd2612223375a (Mar 13 2024 - 19:15:42 +0000) SYSFW ABI: 3.1 (firmware rev 0x0009 '9.0.6--w2023.01-j722s (Kool Koa') Trying to boot from MMC2 U-Boot SPL 2023.04-ti-gd2612223375a (Mar 13 2024 - 19:15:42 +0000) SYSFW ABI: 3.1 (firmware rev 0x0009 '9.0.6--w2023.01-j722s (Kool Koa') SPL initial stack usage: 17064 bytes Trying to boot from MMC2 Authentication passed Authentication passed Authentication passed 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 NOTICE: Upgrade Firmwares for Power off functionality ERROR: Failed to get response (-19) ERROR: Transfer send failed (-19) ERROR: Unable to query firmware capabilities (-19)

  • +1
    TI__Prodigy 60 points

    Hi Johnson,

    Thanks for your support. i missed the voltage input spec 60w 3A is required.

    After i switch the u-boot.img/tiboot3.bin/tispl.bin in the boot partition, and with the correct input current.

    it finally success.

    Thx

    Will