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.

66AK2H12: DSP application with JTAG using rtos/linux package form mcsdk vs pdk

Part Number: 66AK2H12

Hi Everyone,

We are using k2h board,

ARM is running on latest processor SDK, earlier ARM was running on mcsdk Linux but now we have migrated to pdk Linux 

DSP is running on mcsdk rtos and as per the following link this should work theoretically,

https://e2e.ti.com/support/processors/f/791/t/878655

When we try to run DSP from JTAG following things are observed and DSP load is not running fine,

  • With mcsdk rtos DSP build and ARM on  mcsdk Linux 
  • when we connect JTAG, we used to see the DSPs pointing to some address 0x20BXXXX
  • With mcsdk rtos DSP build and ARM on PDK Linux

    • when we connect JTAG, we used to see the DSPs pointing to some address  0xA0BXXXX
    • But here also if I do a soft reset through JTAG, then it shows 0x20BXXXX as the address, but the ARM Linux console gets hung.

Regards,

Snehal

  • Hi,

    In the older thread https://e2e.ti.com/support/processors/f/791/t/878655 showed that: PRSDK Linux on ARM + MCSDK DSP still worked. Where is the PC if you just connect the JTAG before loading the DSP code? Is it in bootrom?

    In this thread showed that Linux already downloaded something into DSP and DSP is running. Is there any kernel script doing this or how this can be automated?

    Also, 0xA0BXXXX ======> This is not a valid memory address, did you miss one digit? Is it is DDR3?

    0x20BXXXX =======> This is not a valid memory address in BOOTROM,  did you miss one digit? It should be 0x20bx_xxxx.

    Regards, Eric

     

  • Hi Eric,

    In the older thread, we are able to resolve the DSP application halting issue (DSP was not up and running),

    Currently, we are seeing a difference in performance between when we load and run the DSP binaries through JTAG Vs when we run through mpmcl utility of ARM. Mpmcl run looks better (except trace buffer debug log through remoteproc not working), JTAG run has issues.

    Yes, I miss one digit my mistake, please find below CCS screens.

    MCSDK and CCS:

    PDK and CCS:

    Regards,

    Snehal

  • Hi,

    Using mixed PRSDK Linux + MCSDK DSP is expected to work but it is not tested. I recommend to use PRSDK for both ARM and DSP. If you saw PC is inside DDR3 memory already, you need to see what application is downloaded to DSP. Did you do this?

    Regards, Eric