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.

Tda2ex ipc upload problem

Hello!

I use TDA2Ex board with qnx. I don't have jtag emulator and i use ipc ti util for uploading compiled code on dsp or ipu. 

I try to execute examples from ipc. But it returns error:

MessageQApp
Using numLoops: 100; procId : 1
Entered MessageQApp_execute
Local MessageQId: 0x80
Error in MessageQ_open [-6]
Leaving MessageQApp_execute

So I have questions:

Is it possible to use ipc for uploading compiled code?

How can I check, that dsp doesn't return any error?

if it's not possible to upload code by ipc, where can I find list of jtag emulators(low cost preffered)?

  • Hi, Maxim,

    I have moved this thread to the TDAx forum for more appropriate support.

    Regards,
    Mariya
  • Maxim,
    I have notified experts to comment here.

    Regards,
    Mariya
  • Thank you, Mariya.

    Two more question.

    I found that for sitara processes mpmcl utility could be used for uploading image. 

    1)Could you tell me, is there processor sdk for jacinto family? if yes, where can I download it.(I didn't find it on ti site)

    2)what can i use instead of mpmcl for uploading image to dsp without jtag?

  • Hello,

    For Jacinto6Eco/TDA2Ex, having QNX running on A15 core, we can use the IPC utility which is provided as part of the QNX IPC release. The QNX IPC is available as part of the QNX SDK release. So please contact your TI representative to get access to this release.

    >Is it possible to use ipc for uploading compiled code?

    Yes, Using "IPC" utility provided  by IPC release, it is possible to  load the compiled firmware image to the remote cores (IPU and DSP) form the A15 running QNX.

    >How can I check, that dsp doesn't return any error?

    Any error occurred during loading of the DSP image is immediately reported by the IPC utility. Any run-time error can be captured using the ipc_trace_deamon utility provided.

    regards,

    Praveen