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

AM625: Am62x sk EVM Error while booting from SBL

Shathira Lakdilu
Prodigy 60 points
Part Number: AM625
Other Parts Discussed in Thread: UNIFLASH

Tool/software:

suddenly sd card boot mode was not working on the evm. So According to MCU+SDK i tried booting from OSPI bootmode.

https://software-dl.ti.com/mcu-plus-sdk/esd/AM62X/latest/exports/docs/api_guide_am62x/GETTING_STARTED_FLASH.html

first I changed the bootmode to UART and ran "sudo python3 uart_uniflash.py -p /dev/ttyUSB0 --cfg=sbl_prebuilt/am62x-sk/default_sbl_ospi_linux.cfg" and it executed sucesfully.

Then I changed the boot mode to OSPI and this is the log output

SYSFW Firmware Version 9.2.8--v09.02.08 (Kool Koala)
SYSFW Firmware revision 0x9
SYSFW ABI revision 3.1

[BOOTLOADER_PROFILE] Boot Media       : FLASH 
[BOOTLOADER_PROFILE] Boot Media Clock : 166.667 MHz 
[BOOTLOADER_PROFILE] Boot Image Size  : 184 KB 
[BOOTLOADER_PROFILE] Cores present    : 
m4f0-0
r5f0-0
[BOOTLOADER PROFILE] System_init                      :       4625us 
[BOOTLOADER PROFILE] Board_init                       :          0us 
[BOOTLOADER PROFILE] Drivers_open                     :        297us 
[BOOTLOADER PROFILE] Board_driversOpen                :       6940us 
[BOOTLOADER PROFILE] Sciclient Get Version            :      10203us 
[BOOTLOADER PROFILE] App_waitForMcuPbist              :       4834us 
[BOOTLOADER PROFILE] App_waitForMcuLbist              :       7689us 
[BOOTLOADER PROFILE] App_loadImages                   :       9323us 
[BOOTLOADER PROFILE] App_loadSelfcoreImage            :        883us 
[BOOTLOADER_PROFILE] SBL Total Time Taken             :      44797us 

Image loading done, switching to application ...
Starting MCU-m4f and 2nd stage bootloader

SYSFW Firmware Version 9.2.8--v09.02.08 (Kool Koala)
SYSFW Firmware revision 0x9
SYSFW ABI revision 3.1

[BOOTLOADER_PROFILE] Boot Media       : FLASH 
[BOOTLOADER_PROFILE] Boot Media Clock : 166.667 MHz 
[BOOTLOADER_PROFILE] Boot Image Size  : 1048 KB 
[BOOTLOADER_PROFILE] Cores present    : 
hsm-m4f0-0
r5f0-0
a530-0
[BOOTLOADER PROFILE] System_init                      :       2799us 
[BOOTLOADER PROFILE] Board_init                       :          1us 
[BOOTLOADER PROFILE] Drivers_open                     :        373us 
[BOOTLOADER PROFILE] Board_driversOpen                :      28109us 
[BOOTLOADER PROFILE] Sciclient Get Version            :      10233us 
[BOOTLOADER PROFILE] App_loadImages                   :        261us 
[BOOTLOADER PROFILE] App_loadSelfcoreImage            :       2490us 
[BOOTLOADER PROFILE] App_loadLinuxImages              :       4991us 
[BOOTLOADER_PROFILE] SBL Total Time Taken             :      49261us 

Image loading done, switching to application ...
Starting linux and RTOS/Baremetal applications
NOTICE:  BL31: v2.10.0(release):v2.10.0-367-g00f1ec6b87-dirty
NOTICE:  BL31: Built : 16:09:05, Feb  9 2024
ERROR:   Timeout waiting for thread SP_RESPONSE to fill
ERROR:   Thread SP_RESPONSE verification failed (-60)
ERROR:   Message receive failed (-60)
ERROR:   Failed to get response (-60)
ERROR:   Transfer send failed (-60)
ERROR:   Timeout waiting for thread SP_RESPONSE to fill
ERROR:   Thread SP_RESPONSE verification failed (-60)
ERROR:   Message receive failed (-60)
ERROR:   Failed to get response (-60)
ERROR:   Transfer send failed (-60)
ERROR:   Unable to query firmware capabilities (-60)
E/TC:0 0 k3_sec_proxy_verify_thread:108 Queue is busy
E/TC:0 0 k3_sec_proxy_recv:196 Thread SEC_PROXY_RESPONSE_THREAD verification failed. ret = -65523
E/TC:0 0 ti_sci_get_response:101 Message receive failed (-65523)
E/TC:0 0 ti_sci_do_xfer:150 Failed to get response (-65523)
E/TC:0 0 ti_sci_init:486 Unable to communicate with control firmware (-65523)
E/TC:0 0 call_initcalls:43 Initcall __text_start + 0x0006fae0 failed
E/TC:0 0 k3_sec_proxy_verify_thread:108 Queue is busy
E/TC:0 0 k3_sec_proxy_recv:196 Thread SEC_PROXY_RESPONSE_THREAD verification failed. ret = -65523
E/TC:0 0 ti_sci_get_response:101 Message receive failed (-65523)
E/TC:0 0 ti_sci_do_xfer:150 Failed to get response (-65523)
E/TC:0 0 k3_sec_proxy_verify_thread:108 Queue is busy
E/TC:0 0 k3_sec_proxy_recv:196 Thread SEC_PROXY_RESPONSE_THREAD verification failed. ret = -65523
E/TC:0 0 ti_sci_get_response:101 Message receive failed (-65523)
E/TC:0 0 ti_sci_do_xfer:150 Failed to get response (-65523)
E/TC:0 0 k3_sec_proxy_verify_thread:108 Queue is busy
E/TC:0 0 k3_sec_proxy_recv:196 Thread SEC_PROXY_RESPONSE_THREAD verification failed. ret = -65523
E/TC:0 0 ti_sci_get_response:101 Message receive failed (-65523)
E/TC:0 0 ti_sci_do_xfer:150 Failed to get response (-65523)
E/TC:0 0 tee_otp_get_hw_unique_key:97 Could not get HUK
E/TC:0 0 call_initcalls:43 Initcall __text_start + 0x0006fb08 failed
E/TC:0 0 k3_sec_proxy_verify_thread:108 Queue is busy
E/TC:0 0 k3_sec_proxy_recv:196 Thread SEC_PROXY_RESPONSE_THREAD verification failed. ret = -65523
E/TC:0 0 ti_sci_get_response:101 Message receive failed (-65523)
E/TC:0 0 ti_sci_do_xfer:150 Failed to get response (-65523)
E/TC:0 0 k3_sec_proxy_verify_thread:108 Queue is busy
E/TC:0 0 k3_sec_proxy_recv:196 Thread SEC_PROXY_RESPONSE_THREAD verification failed. ret = -65523
E/TC:0 0 ti_sci_get_response:101 Message receive failed (-65523)
E/TC:0 0 ti_sci_do_xfer:150 Failed to get response (-65523)
E/TC:0 0 sa2ul_init:106 Could not change TRNG firewall owner
E/TC:0 0 call_initcalls:43 Initcall __text_start + 0x0006fb10 failed
E/TC:0 0 
E/TC:0 0 Core data-abort at address 0x14 (translation fault)
E/TC:0 0  esr 0x96000005  ttbr0 0x9e8a1000   ttbr1 0x00000000   cidr 0x0
E/TC:0 0  cpu #0          cpsr 0x600003c4
E/TC:0 0  x0  000000009e874000 x1  0000000000000000
E/TC:0 0  x2  0000000000000000 x3  0000000000000000
E/TC:0 0  x4  00000000000003a0 x5  000000009e891d70
E/TC:0 0  x6  ffffffffffffffb0 x7  0000000000010cb0
E/TC:0 0  x8  000000009e891f80 x9  000000009e881070
E/TC:0 0  x10 0000000000000042 x11 0000000000000008
E/TC:0 0  x12 0000000000000000 x13 000000009e8a9050
E/TC:0 0  x14 0000000000000000 x15 0000000000000000
E/TC:0 0  x16 000000009e81c67c x17 0000000000000000
E/TC:0 0  x18 0000000000000000 x19 000000009e8a93d0
E/TC:0 0  x20 000000009e8a93d8 x21 000000009e874000
E/TC:0 0  x22 000000009e874000 x23 000000009e874ee0
E/TC:0 0  x24 000000009e873db0 x25 0000000000000000
E/TC:0 0  x26 0000000000000000 x27 0000000000000000
E/TC:0 0  x28 0000000000000000 x29 000000009e8a9360
E/TC:0 0  x30 000000009e816fcc elr 000000009e816fdc
E/TC:0 0  sp_el0 000000009e8a9360
E/TC:0 0 TEE load address @ 0x9e800000
E/TC:0 0 Call stack:
E/TC:0 0  0x9e816fdc
E/TC:0 0  0x9e807d24
E/TC:0 0  0x9e822148
E/TC:0 0  0x9e807e94
E/TC:0 0 Panic 'unhandled pageable abort' at core/arch/arm/kernel/abort.c:582 <abort_handler>
E/TC:0 0 TEE load address @ 0x9e800000
E/TC:0 0 Call stack:
E/TC:0 0  0x9e80801c
E/TC:0 0  0x9e81eb88
E/TC:0 0  0x9e807920
E/TC:0 0  0x9e804a98

Any guidance to get the board booting again?

  • 0
    TI__Genius 11435 points

    Hi,

    Could you please share the flashing logs to verify if the correct images are getting flashed?

  • 0 in reply to Meet Thakar
    Prodigy 60 points

    Hi,

    shathira@shathira-virtual-machine:~/ti/mcu_plus_sdk_am62x_09_02_01_00/tools/boot$ sudo python3 uart_uniflash.py -p /dev/ttyUSB0 --cfg=sbl_prebuilt/am62x-sk/default_sbl_null.cfg

Parsing config file ...
Parsing config file ... SUCCESS. Found 5 command(s) !!!

Executing command 1 of 5 ...
Found flash writer ... sending sbl_prebuilt/am62x-sk/sbl_uart_uniflash_stage1.release.tiimage
Sent flashwriter sbl_prebuilt/am62x-sk/sbl_uart_uniflash_stage1.release.tiimage of size 247105 bytes in 25.01s.                                                                                            

Executing command 2 of 5 ...
Command arguments : --file=../../examples/drivers/boot/sbl_uart_uniflash_multistage/sbl_uart_uniflash_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_uart_uniflash_stage2.release.appimage --operation=flash --flash-offset=0x0
Sending ../../examples/drivers/boot/sbl_uart_uniflash_multistage/sbl_uart_uniflash_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_uart_uniflash_stage2.release.appimage: 123480bytes [00:13, 10730.49byteSending ../../examples/drivers/boot/sbl_uart_uniflash_multistage/sbl_uart_uniflash_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_uart_uniflash_stage2.release.appimage: 123481bytes [00:13, 10730.49byteSending ../../examples/drivers/boot/sbl_uart_uniflash_multistage/sbl_uart_uniflash_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_uart_uniflash_stage2.release.appimage: 123482bytes [00:14, 10730.49byteSending ../../examples/drivers/boot/sbl_uart_uniflash_multistage/sbl_uart_uniflash_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_uart_uniflash_stage2.release.appimage: 123483bytes [00:14, 10730.49byteSending ../../examples/drivers/boot/sbl_uart_uniflash_multistage/sbl_uart_uniflash_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_uart_uniflash_stage2.release.appimage: 123484bytes [00:15, 10730.49byte                                                                                                                                                                                                           Sent ../../examples/drivers/boot/sbl_uart_uniflash_multistage/sbl_uart_uniflash_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_uart_uniflash_stage2.release.appimage of size 122784 bytes in 14.97s.
[STATUS] SUCCESS !!!

Executing command 3 of 5 ...
Command arguments : --operation=flash-phy-tuning-data
Sent flash phy tuning data in 3.11s.                                                                                                                                                                       
[STATUS] SUCCESS !!!

Executing command 4 of 5 ...
Command arguments : --file=sbl_prebuilt/am62x-sk/sbl_null.release.tiimage --operation=flash --flash-offset=0x0
Sent sbl_prebuilt/am62x-sk/sbl_null.release.tiimage of size 283457 bytes in 29.56s.                                                                                                                        
[STATUS] SUCCESS !!!

Executing command 5 of 5 ...
Command arguments : --file=../../examples/drivers/ipc/ipc_rpmsg_echo_linux/am62x-sk/r5fss0-0_freertos/ti-arm-clang/ipc_rpmsg_echo_linux.release.appimage --operation=flash --flash-offset=0xA00000
Sent ../../examples/drivers/ipc/ipc_rpmsg_echo_linux/am62x-sk/r5fss0-0_freertos/ti-arm-clang/ipc_rpmsg_echo_linux.release.appimage of size 145940 bytes in 16.7s.                                          
[STATUS] SUCCESS !!!

All commands from config file are executed !!!

  • 0 in reply to Shathira Lakdilu
    TI__Genius 11435 points

    Hi, 

    You have provided the flashing log where you are using default_sbl_null.cfg, in the problem description you mentioned that you faced an issue when you were using default_sbl_ospi_linux.cfg configuration file for flashing. Could you please recheck and provide the appropriate flashing logs. I suspect that in this case the DM is not up and running yet hence leading to this crash, that's why we need to verify if the correct images are getting flashed.