Part Number: PROCESSOR-SDK-AM62X
Tool/software:
I have recently acquired the AM62x-sk-lp board from TI. When the boot over UART steps (https://software-dl.ti.com/mcu-plus-sdk/esd/AM62AX/latest/exports/docs/api_guide_am62ax/GETTING_STARTED_FLASH.html) to flash the prebuilt `default_sbl_ospi_nand_linux_hs_fs.cfg` to the device I encounter the following error on startup:
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 : 182 KB
[BOOTLOADER_PROFILE] Cores present :
m4f0-0
r5f0-0
[BOOTLOADER PROFILE] System_init : 33567us
[BOOTLOADER PROFILE] Board_init : 0us
[BOOTLOADER PROFILE] Drivers_open : 205us
[BOOTLOADER PROFILE] Board_driversOpen : 10703us
[BOOTLOADER PROFILE] Sciclient Get Version : 10204us
[BOOTLOADER PROFILE] App_waitForMcuPbist : 1172us
[BOOTLOADER PROFILE] App_waitForMcuLbist : 7689us
[BOOTLOADER PROFILE] App_loadImages : 3969us
[BOOTLOADER PROFILE] App_loadSelfcoreImage : 7337us
[BOOTLOADER_PROFILE] SBL Total Time Taken : 74850us
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 : 1043 KB
[BOOTLOADER_PROFILE] Cores present :
hsm-m4f0-0
r5f0-0
a530-0
[BOOTLOADER PROFILE] System_init : 2886us
[BOOTLOADER PROFILE] Board_init : 1us
[BOOTLOADER PROFILE] Drivers_open : 261us
[BOOTLOADER PROFILE] Board_driversOpen : 47266us
[BOOTLOADER PROFILE] Sciclient Get Version : 10232us
[BOOTLOADER PROFILE] App_loadImages : 2189us
[BOOTLOADER PROFILE] App_loadSelfcoreImage : 7662us
[BOOTLOADER PROFILE] App_loadLinuxImages : 40020us
[BOOTLOADER_PROFILE] SBL Total Time Taken : 110521us
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
It appears the first few stages are operating correctly however, when I am passing over to the Linux and FreeRTOS based applications, it is encountering som error in Linux. I cannot find anything regarding this online but please point me in the correct direction. More simple applications such as the EVM setup are booting correctly.
It should be noted that the MCU+SDK core is being built correctly in a Ubuntu 22.04 environment.
