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.

TDA4VM: Run vision_apps in SBL boot flow with combined_appImage on j721e

Part Number: TDA4VM

Hi,

 I try to run vision_apps in SBL boot flow with combined_appImage on j721e. The mcu1_0  app seems working,but Linux can’t boot sucessfully.  

Thanks.

The logs:

NOTICE: BL31: v2.8(release):v2.8-226-g2fcd408bb3-dirty
NOTICE: BL31: Built : 22:56:45, Mar 3 2023
ERROR: GTC_CNTFID0 is 0! Assuming 200000000 Hz. Fix Bootloader
I/TC:
I/TC: OP-TEE version: 3.20.0 (gcc version 9.2.1 20191025 (GNU Toolchain for the A-profile Architecture 9.2-2019.12 (arm-9.10))) #1 Fri Mar 3 22:59:24 UTC 2023 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: SYSFW ABI: 3.1 (firmware rev 0x0008 '8.6.3--v08.06.03 (Chill Capybar')
I/TC: HUK Initialized
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:59 Failed to get SA2UL device
E/TC:0 0 call_initcalls:43 Initcall __text_start + 0x00063c20 failed
I/TC: Primary CPU switching to normal world boot
E/TC:0 0
E/TC:0 0 Core data-abort at address 0x10 (translation fault)
E/TC:0 0 esr 0x96000005 ttbr0 0x9e894000 ttbr1 0x00000000 cidr 0x0
E/TC:0 0 cpu #0 cpsr 0x800003c4
E/TC:0 0 x0 000000009e867000 x1 0000000000000010
E/TC:0 0 x2 0000000000000000 x3 0000000000000000
E/TC:0 0 x4 0000000000000001 x5 0000000000ffffff
E/TC:0 0 x6 0000000000000002 x7 000000009e89c190
E/TC:0 0 x8 000000009e89c190 x9 000000009e884d70
E/TC:0 0 x10 0000000000000000 x11 0000000000000000
E/TC:0 0 x12 000000009e89c100 x13 000000000000000a
E/TC:0 0 x14 00000000ffffffff x15 0000000000000020
E/TC:0 0 x16 000000009e813c40 x17 0000000000000000
E/TC:0 0 x18 0000000000000000 x19 000000009e89eca0
E/TC:0 0 x20 000000009e89eca8 x21 0000000000000007
E/TC:0 0 x22 000000009e873000 x23 000000009e8736a0
E/TC:0 0 x24 0000000100000000 x25 0000000000000000
E/TC:0 0 x26 0000000000000000 x27 0000000000000000
E/TC:0 0 x28 0000000000000000 x29 000000009e89ec30
E/TC:0 0 x30 000000009e80e3ac elr 000000009e80e3cc
E/TC:0 0 sp_el0 000000009e89ec30
E/TC:0 0 TEE load address @ 0x9e800000
E/TC:0 0 Call stack:
E/TC:0 0 0x9e80e3cc
E/TC:0 0 Panic 'unhandled pageable abort' at core/arch/arm/kernel/abort.c:572 <abort_handler>
E/TC:0 0 TEE load address @ 0x9e800000
E/TC:0 0 Call stack:
E/TC:0 0 0x9e8087dc
E/TC:0 0 0x9e81506c
E/TC:0 0 0x9e807fd8
E/TC:0 0 0x9e805520

  • Hi,

    May I know which app are you running on MCU1_0?

    Is this a standard IPC echo test app available in the SDK?

    Regards,

    Nikhil

  • I running the sbl_baremetal_boot_test_j721e_evm_mcu1_0TestAPP on MCU1_0.

    Thanks.

  • Hi,

    Could you please let me know if the linux is booting up when you use ipc_echo_testb_freertos_mcu1_0_release_strip.xer5f app in MCU1_0.

    I would like to identify if it is an issue with the app.

    Regards,

    Nikhil

  • Hi,

    Thanks for your reply. When I use ipc_echo_testb_freertos_mcu1_0_release_strip.xer5f app in MCU1_0,the linux can booting up successfully. But when I change the MCU1_0 app it boot failed. What do I need to do if  change the MCU APP?

  • Hi,

    You just have to replace the app path in config.mk for mcu1_0 and rebuild combined_app image.

    I was able to run $(PDK_INSTALL_PATH)/ti/binary/UART_TestApp_freertos/bin/j721s2_evm/UART_TestApp_freertos_mcu1_0_release_strip.xer5f along with Linux by replacing ipc_echo_test app in config.mk 

    May i know why are you trying to run a baremetal application on MCU1_0?

    Regards,

    Nikhil

  • Hi,

    Thanks for your reply. I just have a baremetal application need to run on MCU1_0. I used my app and encountered the problem. I changed my app with sbl_baremetal_boot_test_j721e_evm_mcu1_0TestAPP on MCU1_0 and encountered the same problem. May I know the app must be with RTOS? And can't be baremetal application? 

  • Hi,

    Sorry for the delayed response.

    I believe, the sbl_baremetal_boot_test_j721e_evm_mcu1_0TestAPP  does not have the SciServer integrated, because of which, if this app is being used as DM, then the SCI commands would not be passed through.

    Please refer the ipc echo test app and integrate the SciServer. This should resolve the issue.

    Regards.

    Nikhil