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.

MPMCL remoteproc0 trace not created for application which build with IPC version 3_43_01_03

Dear TI Experts,


I recently changed IPC version from "3_40_01_08" to "3_43_01_03" for resolving GateMP API's issue on my application.

Build went fine. But after loading and running this built DSP image using MPMCL command on TCI6638K2K board, I not found "trace0" under "/sys/kernel/debug/remoteproc/remoteproc0/" path.

In all earlier release versions from 3.35 to 3.40, trace0 has appeared and able to see all the System_printf's on ARM side Linux console.

Please provide any solution for using this latest IPC version of 3.43 to get proper trace message.

Regards,

Hemanth, P

  • Hi Hemant,

    This has been forwarded to the TCI66x team. Their feedback will be posted directly here.

    Best Regards,
    Yordan
  • Hi Yordan,
    Still not got any response from your TCI66x team.

    Regards,
    Hemanth, P
  • Hey Hemanth,

    If the trace0 is not showing up, that makes me think that there is a problem with loading.  Is your program actually running?  Do you have the log from the console when you try to load and run?  Additionally, are you able to run any of the examples that come with the IPC package?  Did you say that this code ran on earlier builds?  Or were you changing builds to try to fix a problem that had prevented it from running?

    Regards,

    John

  • Hi John,

    Thanks for your prompt reply.

    Initially, I built and ran the IPC demo example which came along with MCSDK_BIOS package on TCI6638K2K board with the following IPC and XDC tool package version:

    IPC: 3_35_01_07

    XDC: xdctools_3_30_04_52_core

    Here, I am getting DSP trace msgs on Linux console after doing the following commands:

    root@vpx-d16a4-pcie:~# mpmcl load dsp0 image_processing_evmtci6638k2k_slave.out
    load succeeded
    root@vpx-d16a4-pcie:~# mpmcl run dsp0
    run succeeded

    root@vpx-d16a4-pcie:~# cat /sys/kernel/debug/remoteproc/remoteproc0/trace0
    3 Resource entries at 0x800000
    registering rpmsg-proto service on 61 with HOST
    Hello
    DDR_MEM_MGMT: created MessageQ: SLAVE_DDR_CORE0; QueueID: 0x10080
    Awaiting message from host...
    Start core task
    Core_Task: created MessageQ: core1_queue; QueueID: 0x10081
    Waiting for message from master

    After this, I again rebuilt the IPC demo example with the following IPC and XDC tool version:

    IPC: 3_43_01_03

    XDC: xdctools_3_31_03_43_core

    Here, build went success and after loading this .out image and run as mentioned below:

    root@vpx-d16a4-pcie:~# mpmcl load dsp0 image_processing_evmtci6638k2k_slave.out
    load succeeded
    root@vpx-d16a4-pcie:~# mpmcl run dsp0
    run succeeded
    root@vpx-d16a4-pcie:~# cat /sys/kernel/debug/remoteproc/remoteproc0/trace0
    cat: can't open '/sys/kernel/debug/remoteproc/remoteproc0/trace0': No such file or directory
    root@vpx-d16a4-pcie:~#

    Here, trace0 not created.

    Please suggest me if I missed anything when I switched IPC version from 3.35 to 3.43.

    Regards,

    Hemanth, P

  • Hi John,
    Still, I did not get any reply from your side.
    Please suggests me if I miss anything here to get trace.

    Regards,
    Hemsbond.
  • Hey Hemsbond,

    I believe that the latest IPC may not work with the older MCSDK releases.  Which MCSDK release and kernel version are you using?  Would you be able to transition to PROCSDK?

    Best,

    John