• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 100 subscribers
  • Views 595 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: ipc_test exception occured in version 7.03 RTOS+QNX

HONGRUN ZHAO
Intellectual 555 points
Part Number: TDA4VM

Reference to

https://software-dl.ti.com/jacinto7/esd/processor-sdk-qnx-jacinto7/07_03_00_02/exports/docs/qnx_sdk_components_j721e.html#example-application

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/modules/ipc.html#build

Follow steps are done to run ipc_test.

1. 

cd $/ ti-processor-sdk-rtos-j721e-evm-07_03_00_07/pdk_jacinto_07_03_00_29/packages/ti/build

make -s -j BUILD_PROFILE=release BOARD=j721e_evm CORE=mcu1_0 ex02_bios_multicore_echo_test

make -s -j BUILD_PROFILE=release BOARD=j721e_evm CORE=mcu2_0 ex02_bios_multicore_echo_test

make -s -j BUILD_PROFILE=release BOARD=j721e_evm CORE=mcu2_1 ex02_bios_multicore_echo_test

make -s -j BUILD_PROFILE=release BOARD=j721e_evm CORE=c66xdsp_1 ex02_bios_multicore_echo_test

make -s -j BUILD_PROFILE=release BOARD=j721e_evm CORE=c66xdsp_2 ex02_bios_multicore_echo_test

make -s -j BUILD_PROFILE=release BOARD=j721e_evm CORE=c7x_1 ex02_bios_multicore_echo_test

2.

cd $/ ti-processor-sdk-rtos-j721e-evm-07_03_00_07/pdk_jacinto_07_03_00_29/packages/ti/binary

cp ex02_bios_multicore_echo_test_c7x_1_release.xe71 /media/tda4/rootfs/lib/firmware/j7-c71_0-fw
cp ex02_bios_multicore_echo_test_c66xdsp_2_release.xe66 /media/tda4/rootfs/lib/firmware/j7-c66_1-fw
cp ex02_bios_multicore_echo_test_c66xdsp_1_release.xe66 /media/tda4/rootfs/lib/firmware/j7-c66_0-fw
cp ex02_bios_multicore_echo_test_mcu2_1_release.xer5f /media/tda4/rootfs/lib/firmware/j7-main-r5f0_1-fw
cp ex02_bios_multicore_echo_test_mcu2_0_release.xer5f /media/tda4/rootfs/lib/firmware/j7-main-r5f0_0-fw

3. Run EVM,  run ‘ipc_test -v’ 

Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
U-Boot SPL 2020.01-g2781231a33 (Apr 10 2021 - 01:08:23 +0000)
SYSFW ABI: 3.1 (firmware rev 0x0015 '21.1.1--v2021.01a (Terrific Lla')
Trying to boot from MMC2
Loading Environment from MMC... *** Warning - No MMC card found, using default environment
Starting ATF on ARM64 core...
NOTICE: BL31: v2.4(release):07.03.00.005-dirty
NOTICE: BL31: Built : 00:15:40, Apr 10 2021
U-Boot SPL 2020.01-g2781231a33 (Apr 10 2021 - 00:17:14 +0000)
SYSFW ABI: 3.1 (firmware rev 0x0015 '21.1.1--v2021.01a (Terrific Lla')
Detected: J7X-BASE-CPB rev E3
Detected: J7X-VSC8514-ETH rev E2
Trying to boot from MMC2
U-Boot 2020.01-g2781231a33 (Apr 10 2021 - 00:17:14 +0000)
SoC: J721E SR1.0
Model: Texas Instruments K3 J721E SoC
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

From log, ipc_test is not work.Then I modified $/ti-processor-sdk-rtos-j721e-evm-07_03_00_07/pdk_jacinto_07_03_00_29/packages/ti/drv/ipc/examples/common/src/ipc_setup.h

/* Vring start address for each device */
#ifdef SOC_AM65XX
#define VRING_BASE_ADDRESS 0xA2000000U
#elif defined (SOC_J7200)
#define VRING_BASE_ADDRESS 0xA4000000U
#elif defined (SOC_AM64X)
#define VRING_BASE_ADDRESS 0xA5000000U
#else
//#define VRING_BASE_ADDRESS 0xAA000000U
#define VRING_BASE_ADDRESS 0xB0000000U
#endif

Run EVM.

Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
U-Boot SPL 2020.01-g2781231a33 (Apr 10 2021 - 01:08:23 +0000)
SYSFW ABI: 3.1 (firmware rev 0x0015 '21.1.1--v2021.01a (Terrific Lla')
Trying to boot from MMC2
Loading Environment from MMC... *** Warning - No MMC card found, using default environment
Starting ATF on ARM64 core...
NOTICE: BL31: v2.4(release):07.03.00.005-dirty
NOTICE: BL31: Built : 00:15:40, Apr 10 2021
U-Boot SPL 2020.01-g2781231a33 (Apr 10 2021 - 00:17:14 +0000)
SYSFW ABI: 3.1 (firmware rev 0x0015 '21.1.1--v2021.01a (Terrific Lla')
Detected: J7X-BASE-CPB rev E3
Detected: J7X-VSC8514-ETH rev E2
Trying to boot from MMC2
U-Boot 2020.01-g2781231a33 (Apr 10 2021 - 00:17:14 +0000)
SoC: J721E SR1.0
Model: Texas Instruments K3 J721E SoC
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Failure occur and tiipc-mgr is killed.

1 . How to solve that?

2 . Form log, IPC function beteewn MPU and (mcu3_0、mcu3_1、mcu1_0、mcu1_1) can works, but in /media/tda4/rootfs/lib/firmware, there is no relevant firmware. Why is that?

And Then I follow 

TDA4VM: Ipc fail in qnx environment - Processors forum - Processors - TI E2E support forums

still fail.

Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
U-Boot SPL 2020.01-g2781231a33 (Apr 10 2021 - 01:08:23 +0000)
SYSFW ABI: 3.1 (firmware rev 0x0015 '21.1.1--v2021.01a (Terrific Lla')
Trying to boot from MMC2
Loading Environment from MMC... *** Warning - No MMC card found, using default environment
Starting ATF on ARM64 core...
NOTICE: BL31: v2.4(release):07.03.00.005-dirty
NOTICE: BL31: Built : 00:15:40, Apr 10 2021
U-Boot SPL 2020.01-g2781231a33 (Apr 10 2021 - 00:17:14 +0000)
SYSFW ABI: 3.1 (firmware rev 0x0015 '21.1.1--v2021.01a (Terrific Lla')
Detected: J7X-BASE-CPB rev E3
Detected: J7X-VSC8514-ETH rev E2
Trying to boot from MMC2
U-Boot 2020.01-g2781231a33 (Apr 10 2021 - 00:17:14 +0000)
SoC: J721E SR1.0
Model: Texas Instruments K3 J721E SoC
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  • 0
    Intellectual 555 points

    Then I verify ipc_test  in version 7.02 (RTOS+QNX). It works.

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    U-Boot SPL 2020.01-g2781231a33 (Apr 10 2021 - 01:08:23 +0000)
    SYSFW ABI: 3.1 (firmware rev 0x0015 '21.1.1--v2021.01a (Terrific Lla')
    Trying to boot from MMC2
    Loading Environment from MMC... *** Warning - No MMC card found, using default environment
    Starting ATF on ARM64 core...
    NOTICE: BL31: v2.4(release):07.03.00.005-dirty
    NOTICE: BL31: Built : 00:15:40, Apr 10 2021
    U-Boot SPL 2020.01-g2781231a33 (Apr 10 2021 - 00:17:14 +0000)
    SYSFW ABI: 3.1 (firmware rev 0x0015 '21.1.1--v2021.01a (Terrific Lla')
    Detected: J7X-BASE-CPB rev E3
    Detected: J7X-VSC8514-ETH rev E2
    Trying to boot from MMC2
    U-Boot 2020.01-g2781231a33 (Apr 10 2021 - 00:17:14 +0000)
    SoC: J721E SR1.0
    Model: Texas Instruments K3 J721E SoC
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    But  there is no SendTask between mpu and mcu1.  How to solve that?

  • 0 in reply to HONGRUN ZHAO
    TI__Guru** 111551 points

    Hi,

    Regarding ipc_test running on  PSDK 7.3, please see instructions on below link for the default installation, with no code modifications required:

    (+) [FAQ] TDA4VM: IPC_Test on PSDK QNX 7.2 / PSDK QNX 7.3 - Processors forum - Processors - TI E2E support forums

    Regarding MPU to MCU1 communication, as the MCU1 image is already running,  the "ipc echo test" firmware images have not been loaded.   Will update this thread with recommended steps to work around this.

    kb

  • 0 in reply to KB
    Intellectual 555 points

    Hi KB:

        Thank you for your reply.  

        From ipc_test example, known that MPU to MCU1 communication is not achieved in version 7.02 or 7.03.Also, system memory map is different from previous versions.

        From thread:

        TDA4VM: After builded MCU1_0, Run vision apps Demos for Display , IPC error occurs . - Processors forum - Processors - TI E2E support forums

        known that the Vision Apps generated firmware image for MCU1_0 with IPC enabled is not functional in version 7.03.

        1 .So how to prove out MCU1_0 and MPU IPC communication?

        2 .MPU to MCU1 ipc communication is a urgent task to be developed in our project. We try to use cddipc to achieve this requirement, but failed. 

           A successful ipc communication is necessary for reference using cddipc in our project . 

          I want to know if cddipc module is a avaliable way for MPU to MCU1 ipc communication? 

        3. If cddipc is not work ,in TI's recommendation, how to achieve MPU to MCU1 ipc communication ?

  • 0 in reply to HONGRUN ZHAO
    TI__Guru** 111551 points

    Hi,

    The issue is around the firmware image running on the MCU1.   For an IPC test to be successful, the MCU1 firmware image needs to:

    • Have IPC S/W running that is capable of responding to the particular test that is being run
    • Have a memory map that matches the rest of the system

    As per earlier response, TI will update this thread with recommended steps for a workaround.

    Regards,

    kb

  • 0 in reply to KB
    Intellectual 555 points

    Hi KB:

        Which version will realize MCU's ipc_test function?  Or which previous version that MCU's ipc_test works well?

  • +1 in reply to HONGRUN ZHAO
    TI__Guru** 111551 points

    Hi,

    In referencing the FAQ for PSDK QNX 7.1:

    (+) [FAQ] PROCESSOR-SDK-DRA8X-TDA4X: How to use IPC Example Application Echo Test on PSDKQA7.0 - Processors forum - Processors - TI E2E support forums

    The logs there show mcu1_0 responding to the IPC echo test:

    "SendTask1: mpu1_0 <--> mcu1_0, Ping- 10, pong - 10 completed"

    Regards,

    kb

  • 0 in reply to KB
    Intellectual 555 points

    Hi KB:

        Thank you for your reply.

        Follow your thread:

        (+) [FAQ] TDA4VM: IPC_Test on PSDK QNX 7.2 / PSDK QNX 7.3 - Processors forum - Processors - TI E2E support forums

        I got the same result as you. 

  • 0 in reply to HONGRUN ZHAO
    TI__Guru** 111551 points

    Hi,

    Patch PSDK_QNX_07_03_03_patch is available at PROCESSOR-SDK-QNX-J721E_07.03.00.02 | TI.com, the patch includes a readme with instructions. 

    When PSDK_QNX_07_03_03_patch is applied, and readme instructions followed, expectation is that the MCU1_0 communication for the ipc_echo test will function.

    Regards,

    kb