• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 99 subscribers
  • Views 254 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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: How to test ipc_test app on QNX

youngwoo lee
Intellectual 550 points
Part Number: TDA4VM

Hi.

expert.

I try to run ipc_test app on QNX.

I use SDK7_1, QNX700.

When I just run tibin/ipc_test, I got a console message below.

and then I refer to https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1015234/faq-tda4vm-ipc_test-on-psdk-qnx-7-2-psdk-qnx-7-3

Q1. I builded with build command, but I get a error message on SDK7_1. on SDK7_3 building is ok.

cd <PSDK_RELEASE>/psdkqa/qnx
make all VISION_APPS_BUILD_FLAGS_MAK=0

Q2. Could you check my development version(SDK7.1 / QNX700)?

Do PSDK QNX 7.2 and PSDK QNX7.3 mean QNX720 and QNX710?

Is not QNX700 supported?   

Thank you

  • 0
    TI__Guru** 110651 points

    Hi,

    Regarding Q1:

    Please provide full build log, when running below commands from release_71/ti-processor-sdk-rtos-j721e-evm-07_01_00_11/psdkqa/qnx.   No build errors are expected. 

    make clean;

    make all

    Regarding Q2:

    The TI SDK numbering convention, and QNX SDP numbering convention are not related, but do need to be understood.

    The latest publicly available QNX Software Development Platform (SDP), is QNX SDP 7.1.  

    When TI releases an SDK, it will specify which QNX SDP the release(s) were tested against, and supports.   This can be seen in the TI SDK release notes.  For example  the PSDK QNX 7.2 release notes ( 3.1. Release notes - 07_02_00 — Processor SDK QNX (ti.com))  specify the dependencies if using QNX SDP 7.0, or if using QNX SDP 7.1. 

    Regards,

    kb

  • 0 in reply to KB
    Intellectual 550 points

    Hi,

    KB said:
    Please provide full build log, when running below commands from release_71/ti-processor-sdk-rtos-j721e-evm-07_01_00_11/psdkqa/qnx.   No build errors are expected. 

    Error occured. 

    boot log.

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    NOTICE: BL31: v2.2(release):Temp_0.0.0.3-2-gdba7d0950-dirty
    NOTICE: BL31: Built : 14:32:08, Mar 23 2022
    I/TC:
    I/TC: OP-TEE version: Temp_0.0.0.3-2-gdba7d0950-dev (gcc version 9.2.1 20191025 (GNU Toolchain for the A-profile Architecture 9.2-2019.12 (arm-9.10))) #1 2022. 03. 23. (수) 05:32:11 UTC aarch64
    I/TC: Initialized
    MMFLAGS=19
    Welcome to QNX Neutrino 7.0 on the ADAS_PRK 2 Board
    Mailbox_plugInterrupt: interrupt Number 489, arg 0x1011EEB0
    Mailbox_plugInterrupt: interrupt Number 490, arg 0x1011F050
    Mailbox_plugInterrupt: interrupt Number 491, arg 0x1011F1F0
    Mailbox_plugInterrupt: interrupt Number 492, arg 0x1011F390
    Mailbox_plugInterrupt: interrupt Number 493, arg 0x1011F530
    Starting TI IPC Resmgr
    suggested mask to set for EL0 timer access: 0x303
    cntkctl_el1: setting bits 0x303, new value 0x303
    suggested mask to set for EL0 timer access: 0x303
    cntkctl_el1: setting bits 0x303, new value 0x303
    Path=0 - am65x
    target=0 lun=0 Direct-Access(0) - SDMMC: S0J56X Rev: 1.0
    eMMC Filesystem partitionA mount!!
    startup.sh start!!
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    I tried to build as below.(SDK7.1, QNX700) result is same(ipc_test)

    1. skip "make all VISION_APPS_BUILD_FLAGS_MAK=0" because of building error. <- Q1. Is this process necessary on SDK7.1? 

    2. build remote cores

    make BUILD_PROFILE=release BOARD=j721e_evm TREAT_WARNINGS_AS_ERROR=no DISABLE_RECURSE_DEPS=no CORE=mcu1_1 ex02_bios_multicore_echo_test
    make BUILD_PROFILE=release BOARD=j721e_evm TREAT_WARNINGS_AS_ERROR=no DISABLE_RECURSE_DEPS=no CORE=mcu2_0 ex02_bios_multicore_echo_test
    make BUILD_PROFILE=release BOARD=j721e_evm TREAT_WARNINGS_AS_ERROR=no DISABLE_RECURSE_DEPS=no CORE=mcu2_1 ex02_bios_multicore_echo_test
    make BUILD_PROFILE=release BOARD=j721e_evm TREAT_WARNINGS_AS_ERROR=no DISABLE_RECURSE_DEPS=no CORE=mcu3_0 ex02_bios_multicore_echo_test
    make BUILD_PROFILE=release BOARD=j721e_evm TREAT_WARNINGS_AS_ERROR=no DISABLE_RECURSE_DEPS=no CORE=mcu3_1 ex02_bios_multicore_echo_test
    make BUILD_PROFILE=release BOARD=j721e_evm TREAT_WARNINGS_AS_ERROR=no CORE=c66xdsp_1 ex02_bios_multicore_echo_test
    make BUILD_PROFILE=release BOARD=j721e_evm TREAT_WARNINGS_AS_ERROR=no CORE=c66xdsp_2 ex02_bios_multicore_echo_test
    make BUILD_PROFILE=release BOARD=j721e_evm TREAT_WARNINGS_AS_ERROR=no CORE=c7x_1 ex02_bios_multicore_echo_test
    make BUILD_PROFILE=release BOARD=j721e_evm TREAT_WARNINGS_AS_ERROR=no DISABLE_RECURSE_DEPS=no CORE=mcu1_0 ex02_bios_multicore_echo_testb

    3. copy remote cores image

    cp ${PDK_INSTALL_PATH}/ti/binary/ex02_bios_multicore_echo_test/bin/j721e_evm/ex02_bios_multicore_echo_test_c7x_1_release.xe71 ${ROOTFS}/lib/firmware/j7-c71_0-fw
    cp ${PDK_INSTALL_PATH}/ti/./binary/ex02_bios_multicore_echo_test/bin/j721e_evm/ex02_bios_multicore_echo_test_c66xdsp_2_release.xe66 ${ROOTFS}/lib/firmware/j7-c66_1-fw
    cp ${PDK_INSTALL_PATH}/ti/./binary/ex02_bios_multicore_echo_test/bin/j721e_evm/ex02_bios_multicore_echo_test_c66xdsp_1_release.xe66 ${ROOTFS}/lib/firmware/j7-c66_0-fw
    cp ${PDK_INSTALL_PATH}/ti/./binary/ex02_bios_multicore_echo_test/bin/j721e_evm/ex02_bios_multicore_echo_test_mcu3_1_release.xer5f ${ROOTFS}/lib/firmware/j7-main-r5f1_1-fw
    cp ${PDK_INSTALL_PATH}/ti/./binary/ex02_bios_multicore_echo_test/bin/j721e_evm/ex02_bios_multicore_echo_test_mcu3_0_release.xer5f ${ROOTFS}/lib/firmware/j7-main-r5f1_0-fw
    cp ${PDK_INSTALL_PATH}/ti/./binary/ex02_bios_multicore_echo_test/bin/j721e_evm/ex02_bios_multicore_echo_test_mcu2_1_release.xer5f ${ROOTFS}/lib/firmware/j7-main-r5f0_1-fw
    cp ${PDK_INSTALL_PATH}/ti/./binary/ex02_bios_multicore_echo_test/bin/j721e_evm/ex02_bios_multicore_echo_test_mcu2_0_release.xer5f ${ROOTFS}/lib/firmware/j7-main-r5f0_0-fw
    cp ${PDK_INSTALL_PATH}/ti/./binary/ex02_bios_multicore_echo_test/bin/j721e_evm/ex02_bios_multicore_echo_test_mcu1_1_release.xer5f ${ROOTFS}/lib/firmware/j7-mcu-r5f0_1-fw
    cp ${PDK_INSTALL_PATH}/ti/./binary/ex02_bios_multicore_echo_testb/bin/j721e_evm/ex02_bios_multicore_echo_testb_mcu1_0_release.xer5f ${ROOTFS}/lib/firmware/j7-mcu-r5f0_0-fw

    but this succeeded

    cd vision_apps

    make sdk

    make qnx_fs_create_sd

    [target] $ ./vx_app_qnx_arm_ipc.out

    Thank you.

  • 0 in reply to youngwoo lee
    TI__Guru** 110651 points

    Hi,

    Thank for the logs and description.  Are (a) to (c) an accurate summary of current status: 

    a) TI SDK 7.1 is under test

    b) Vision Apps vx_app_qnx_arm_ipc.out works.

    c) Running ipc_echo test does not work.

    Regarding (c), the ipc_echo_test binary that runs on the A72, is dependent on the proper images being in place on the C7/C6/R5 cores.  All cores must be built to recognize the memory space being used by IPC.   In your step (3), it appears that the required images are built and copied to an SD card, so the missing piece is likely the A72 binaries that are being run.

    In installing SDK 7.1 locally was able to build and ipc_test with below log generated.

    7801.log.txt
    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    U-Boot SPL 2021.01-g15769936a5 (Dec 20 2021 - 17:09:03 +0000)
    Model: Texas Instruments K3 J721E SoC
    Board: J721EX-PM2-SOM rev E6
    SYSFW ABI: 3.1 (firmware rev 0x0015 '21.9.1--v2021.09a (Terrific Lla')
    Trying to boot from MMC2
    Starting ATF on ARM64 core...
    NOTICE: BL31: v2.5(release):08.01.00.006-dirty
    NOTICE: BL31: Built : 16:34:52, Dec 20 2021
    U-Boot SPL 2021.01-g15769936a5 (Dec 20 2021 - 16:36:05 +0000)
    Model: Texas Instruments K3 J721E SoC
    Board: J721EX-PM2-SOM rev E6
    SYSFW ABI: 3.1 (firmware rev 0x0015 '21.9.1--v2021.09a (Terrific Lla')
    Detected: J7X-BASE-CPB rev E3
    Detected: J7X-VSC8514-ETH rev E2
    Trying to boot from MMC2
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    In step (3) of (+) [FAQ] TDA4VM: IPC_Test on PSDK QNX 7.2 / PSDK QNX 7.3 - Processors forum - Processors - TI E2E support forums, it indicates that the A72 binaries must be rebuilt from the psdkqa/qnx directory.

    In your build environment, please try the following:

    cd psdkqa/qnx

    make clean

    make 

    cd ../vision_apps

    make qnx_fs_install_sd

    The intent is to ensure that the A72 binaries are built correctly, and copied to the SD card.   

    Regards,

    kb