• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 680 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.

Original question:

TDA4VM: TDA4 support Selinux?

TDA4VM: MCU2_0 IPC ​fails after booting through SBL

Zi Wang
Intellectual 415 points
Part Number: TDA4VM

Hello,

The SBL I made by this https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-jacinto7/07_03_00_07/exports/docs/pdk_jacinto_07_03_00_29/docs/userguide/jacinto/boot/boot_k3.html#building-the-sbl-and-its-components

The system can be successfully started

The following is the boot/sbl/tools/combined_appimage/config.mk used to make SBl

HLOS_BOOT ?= development
ATF_IMG ?= mpu1_0,$(HLOS_BIN_PATH)/bl31.bin,0x70000000,0x70000000
OPTEE_IMG ?= load_only,$(HLOS_BIN_PATH)/bl32.bin,0x9e800000,0x9e800000
KERNEL_IMG ?= load_only,$(HLOS_BIN_PATH)/../linux-5.10.41+gitAUTOINC+4c2eade9f7-g4c2eade9f7/arch/arm64/boot/Image,0x80080000,0x80080000
DTB_IMG ?= load_only,$(mkfile_dir)bin/$(BOARD)/base-board.dtb,0x82000000,0x82000000
SPL_IMG ?= load_only,$(HLOS_BIN_PATH)/../u-boot_build/a72/spl/u-boot-spl.bin,0x80080000,0x80080000
......
IMG1 ?= mcu1_0,$(PDK_INSTALL_PATH)/ti/binary/ipc_echo_testb_freertos/bin/$(BOARD)/ipc_echo_testb_freertos_mcu1_0_release_strip.xer5f
IMG2 ?= mcu2_0,/home/wangzi/workspace/Tempo/RTOS/targetfs/lib/firmware/vision_apps_evm/vx_app_rtos_linux_mcu2_0.out
But MCU2_0 IPC can't run
What is the cause of this problem？
log:
root@j7-evm:~# source /opt/vision_apps/vision_apps_init.sh
root@j7-evm:~# [MCU2_0] 1.802800 s: CIO: Init ... Done !!!
[MCU2_0] 1.802852 s: ### CPU Frequency = 1000000000 Hz
[MCU2_0] 1.802884 s: APP: Init ... !!!
[MCU2_0] 1.802900 s: SCICLIENT: Init ... !!!
[MCU2_0] 1.803106 s: SCICLIENT: DMSC FW version [21.5.0--v2021.05 (Terrific Llam]
[MCU2_0] 1.803142 s: SCICLIENT: DMSC FW revision 0x15
[MCU2_0] 1.803166 s: SCICLIENT: DMSC FW ABI revision 3.1
[MCU2_0] 1.803190 s: SCICLIENT: Init ... Done !!!
[MCU2_0] 1.803209 s: UDMA: Init ... !!!
[MCU2_0] 1.804240 s: UDMA: Init ... Done !!!
[MCU2_0] 1.804284 s: MEM: Init ... !!!
[MCU2_0] 1.804315 s: MEM: Created heap (DDR_SHARED_MEM, id=0, flags=0x00000004) @ e1000000 of size 16777216 bytes !!!
[MCU2_0] 1.804365 s: MEM: Created heap (L3_MEM, id=1, flags=0x00000000) @ 3600000 of size 262144 bytes !!!
[MCU2_0] 1.804408 s: MEM: Created heap (DDR_NON_CACHE_ME, id=5, flags=0x00000000) @ d8000000 of size 16777216 bytes !!!
[MCU2_0] 1.804449 s: MEM: Init ... Done !!!
[MCU2_0] 1.804467 s: IPC: Init ... !!!
[MCU2_0] 1.804513 s: IPC: 6 CPUs participating in IPC !!!
[MCU2_0] 1.804559 s: IPC: Waiting for HLOS to be ready ... !!!
tiboot3.bin:pdk_jacinto_08_00_00_37/packages/ti/boot/sbl/binary/j721e_evm_hs/mmcsd/bin/sbl_mmcsd_img_hlos_mcu1_0_release.bin
tifs.bin:./pdk_jacinto_08_00_00_37/packages/ti/drv/sciclient/soc/V1/tifs.bin
SDK: linux&RTOS 8.0
  • 0 in reply to Zi Wang
    TI__Guru** 111195 points

    Hi Zi,

    I see you are using SBL to load Linux. Are you going through the regular A72 U-Boot or directly jumping to kernel from ATF/OPTEE?

    The regular Vision SDK firmware images uses a different memory map that is typically added through an overlay applied at U-Boot prompt. The IPC regions used on Vision SDK firmware images is different compared to regular PDK firmware images.

    If you are directly jumping to kernel, you need to ensure the dtb you are using reflects the changes from the Vision Apps overlay.

    Alternatively, you can verify the IPC functionality without any modifications if you use the PDK ipc_echo_test firmware images for all cores other than MCU1_0.

    regards

    Suman

  • 0 in reply to Suman Anna
    Intellectual 415 points

    Hello，Suman

    I'm going through the regular A72 U-Boot 

    and loaded k3-j721e-vision-apps.dtbo in u-boot

    In this situation,The image of the MCU2_0 uses the IMG?= in boot/sbl/tools/combined_appimage/config.mk or /rootsf/lib/firmware/j7-main-r5f0_0-fw

  • 0 in reply to Zi Wang
    TI__Guru** 111195 points

    Hi Zi,

    If you are relying on U-Boot to load your remoteproc binaries, then U-Boot relies on ELF firmware files present on the rootfs /lib/firmware folder.

    You can skip building all the other remoteproc firmwares like MCU2_0, MCU2_1, MCU3_0, MCU3_1, C66x and C71x DSPs etc.

    regards

    Suman