• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 99 subscribers
  • Views 207 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.

SK-TDA4VM: IPC Echo test throws error

Deepankar maithani
Intellectual 316 points
Part Number: SK-TDA4VM

Following the instructions in the documentation QNX IPC, I built the firmware for the remote cores and  added them to the rootfs partition under /lib/firmware. Then i started the test on QNX by running ./ipc_test -s. I am getting the following output

Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
J7EVM@QNX:/ti_fs/tibin# ./ipc_test -s
IPC_echo_test (core : mpu1_0) .....
Creating thread 2 for Core mcu2_0
Creating thread 3 for Core mcu2_1
Creating thread 4 for Core mcu3_0
Creating thread 5 for Core mcu3_1
Creating thread 6 for Core C66X_1
Creating thread 7 for Core C66X_2
Creating thread 8 for Core C7X_1
waiting for thread 2
SendTask7: RPMessage_recv returned with code 0
SendTask3: RPMessage_recv returned with code 0
SendTask9: RPMessage_recv returned with code 0
SendTask8: RPMessage_recv returned with code 0
SendTask4: RPMessage_recv returned with code 0
SendTask7: RPMessage_recv returned with code 0
SendTask3: RPMessage_recv returned with code 0
SendTask9: RPMessage_recv returned with code 0
SendTask8: RPMessage_recv returned with code 0
SendTask4: RPMessage_recv returned with code 0
SendTask7: RPMessage_recv returned with code 0
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

It is not clear to me what should i make out of this output. What does returned with code 0 mean. What does  Ping- 10, pong - 10 completed mean.

  • 0
    TI__Mastermind 43812 points

    Hello Deepankar,

    Are all the remote core firmware images loaded properly? To confirm, can you share the full bootlog include messages from the bootloader?

    Thanks.

  • 0 in reply to Praveen Rao
    Intellectual 316 points

    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 2023.04-g71b8c840ca (Nov 27 2023 - 08:55:35 +0000)
    SYSFW ABI: 3.1 (firmware rev 0x0009 '9.1.2--v09.01.02 (Kool Koala)')
    Trying to boot from MMC2
    Warning: Detected image signing certificate on GP device. Skipping certificate d
    Warning: Detected image signing certificate on GP device. Skipping certificate d
    Warning: Detected image signing certificate on GP device. Skipping certificate d
    Warning: Detected image signing certificate on GP device. Skipping certificate d
    Warning: Detected image signing certificate on GP device. Skipping certificate d
    Loading Environment from nowhere... OK
    Starting ATF on ARM64 core...
    NOTICE: BL31: v2.9(release):v2.9.0-614-gd7a7135d32-dirty
    NOTICE: BL31: Built : 09:34:15, Aug 24 2023
    I/TC:
    I/TC: OP-TEE version: 4.0.0 (gcc version 11.4.0 (GCC)) #1 Fri Oct 20 18:29:31 U4
    I/TC: WARNING: This OP-TEE configuration might be insecure!
    I/TC: WARNING: Please check https://optee.readthedocs.io/en/latest/architecturel
    I/TC: Primary CPU initializing
    I/TC: SYSFW ABI: 3.1 (firmware rev 0x0009 '9.1.2--v09.01.02 (Kool Koala)')
    I/TC: HUK Initialized
    I/TC: Activated SA2UL device
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  • 0 in reply to Deepankar maithani
    Intellectual 316 points

    I see that there are some cores not loaded. I updated the rootfs folder again with new firmware and here is what i get now. It seems to work now.

    What does "RPMessage_recv returned with code 0". Where can i read more about the RPmessage API and source code?

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    J7EVM@QNX:/ti_fs/tibin# ./ipc_test -s
    IPC_echo_test (core : mpu1_0) .....
    Creating thread 2 for Core mcu2_0
    Creating thread 3 for Core mcu2_1
    Creating thread 4 for Core mcu3_0
    Creating thread 5 for Core mcu3_1
    Creating thread 6 for Core C66X_1
    Creating thread 7 for Core C66X_2
    Creating thread 8 for Core C7X_1
    waiting for thread 2
    SendTask3: RPMessage_recv returned with code 0
    SendTask4: RPMessage_recv returned with code 0
    SendTask7: RPMessage_recv returned with code 0
    SendTask5: RPMessage_recv returned with code 0
    SendTask9: RPMessage_recv returned with code 0
    SendTask8: RPMessage_recv returned with code 0
    SendTask6: RPMessage_recv returned with code 0
    SendTask3: RPMessage_recv returned with code 0
    SendTask4: RPMessage_recv returned with code 0
    SendTask7: RPMessage_recv returned with code 0
    SendTask5: RPMessage_recv returned with code 0
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  • 0 in reply to Deepankar maithani
    Intellectual 316 points

    Where can i see the source code for ti-ipc-mgr and shemallocator binaries

  • 0 in reply to Deepankar maithani
    TI__Mastermind 25379 points

    Hello Deepankar,

    The engineer is out of office until 5/8, please expect a ~1-2 day delay.

    -Josue

  • +1 in reply to Josue Zamitiz-Ayala
    TI__Mastermind 43812 points

    Deepankar maithani said:
    Where can i see the source code for ti-ipc-mgr and shemallocator binaries

    The source code for tiipc-mgr and sharedmemallocator modules can be found in the SDK install path.

    <PSDK_INSTALL_PATH>/psdkqa/qnx/resmgr/ipc_qnx_rsmgr/resmgr 

    <PSDK_INSTALL_PATH>/psdkqa/qnx/sharedmemallocator

    Thanks.