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.

Try to run the DSP software on the emulator for debugging while running the A15 software from the SD card on the actual hardware

I had run our DSP software on the emulator for debugging while running the A15 software from the SD card on the actual hardware. It stopped working in this way. At this point,  I have to connect and run A15 software on the emulator first before I can run the DSP code on the emulator. I don’t know what has been changed. Could you help me to change back to what it used to be?

  • Hello,

    What device are you using?

    Thanks

    ki

  • Hello Ki,

    We are using TI EVM-572X board and Blackhawk emulator.

  • Thanks. I will bring this thread to the attention of the device experts. They can assist best.

    ki

  • Hi Joe,

    Please correct me if I am wrong, here is my understanding of the issue:

    Earlier you were running your A15 software using SD card and then you were loading your DSP software using emulator for debugging and then for some reason it stopped working in this way and now you are running A15 software using SD card as before, but before you can connect to DSP and load your software you need to connect to A15 first? Is that right?

    Regards,
    Parth

  • Hi Parth,

    Yes, you are correct.

    What I want is:  first turn on the power of the target hardware. This will run the A15 software in the SD card on the target hardware. Then connect and load the DSP software using emulator for debugging without needing to connect and load the A15 software on the emulator. 

    It had worked in this way, but now it does not somehow.

    Thanks for the help!

    Best Regards,

    Joe

  • HI Joe,

    Apologies for delay in response. 

    Is there any change in the software that you are running on A15 in the working and non-working case? Also, if possible can you please share what app are you running on A15?

    DSP core needs to be unlocked before we can connect to it. Generally, the GEL scripts that runs when we connect to A15 takes care of it when we use No-boot mode and that is why we need to connect to A15. In your case, it looks like your software was unlocking the DSP core in your working case and due to some change it is not doing so anymore. We'll need to check if there is any change in what you are running on A15.

    Regards,
    Parth 

  • The following message was sent to Parth 3 days ago via email. I am posting here for the record....

    We are using your 572X-EVM board, and our A15 software uses VxWorks as its operating system and communicates with the DSP core via shared memory. The DSP core uses your TI RTOS. There has been no changes in A15 and DSP software. Per your email, when we are connecting to the DSP core, does CCS run a GEL script? If so, is it possible to unlock the DSP core in that script?

  • Hi Joe,

    The following message was sent to Parth 3 days ago via email. I am posting here for the record....

    I am not sure which email you are referring to, I don't see any mail on my side. Please prefer using e2e over mails.

    Per your email, when we are connecting to the DSP core, does CCS run a GEL script? If so, is it possible to unlock the DSP core in that script?

    Yes, it does run some GEL scripts, but I don't think it is possible to unlock the DSP in that script. I can double check though, but I believe this has to be taken care by the software running on A15. 

    There has been no changes in A15 and DSP software.

    There has to be some change. How were you loading the DSP in the working case? Via debugger itself or some other method.

    Regards,
    Parth

  • 1. Yes, I will use e2e moving forward instead of replying email that I received after you posted your message.

    2. Please double check if it is possible to unlock the DSP in the DSP GEL script. 

    3. As I stated, I had been able to run A15 software on the target board and run DSP software via emulator for a while. For some reason, it does not work in this way any more. Same software and same hardware. That is why I need your help to get back to the old way. 

  • Hi Joe,

    Please double check if it is possible to unlock the DSP in the DSP GEL script. 

    No it is not possible to run the GEL script when some application is already running on A15.

    As I stated, I had been able to run A15 software on the target board and run DSP software via emulator for a while. For some reason, it does not work in this way any more. Same software and same hardware. That is why I need your help to get back to the old way. 

    Were you loading anything on DSP from A15? If yes, it might be the case that the firmware loading on DSP is crashing and that's why you are not able to connect now.

    Regards,
    Parth

  • We are not loading anything on DSP from A15. Our A15 software communicates with the DSP software via shared memory. 

  • Hi Joe,

    This mixed approach of using run a software of A15 and running DSP with emulator is not standard and has never been validated. The recommended approach is to either unlock the DSP from A15 when when using emulator,( which is not possible in this case as there is already a software running on A15) or load the DSP from A15 as done in SBL. I can find which instruction initializes the DSP before loading the binary on DSP in SBL, but you have to figure out a way to implement the same in VxWorks

    Regards,

    Parth

  • Hi Parth,

    The goal is to debug the DSP software using the emulator. The DSP software communicates with A15 via shared memory. The A15 Software runs on the target board and is working. It seems to be a generic use case, doesn't it? If not, how does the user typically do then?

    Regards,

    Joe

  • Hi Joe,

    Typically, the software running on A15 loads the DSP core, either SBL or the Linux (via remoteproc). Once the DSP is loaded, the DSP core can be connected from the emulator and user can load the symbols. From there on, you can debug using the debugger. Please see the documentation

    1) https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-jacinto7/07_03_00_07/exports/docs/psdk_rtos/docs/user_guide/ccs_setup_j721e.html#debugging-with-hlos-running-on-a72-linux-qnx

    2) https://software-dl.ti.com/processor-sdk-rtos/esd/docs/latest/rtos/index_how_to_guides.html#using-code-composer-studio

    Does your actual use case also includes loading the DSP via emulator? If not, can you please share how DSP will be loaded in the actual use case?

    Regards,
    Parth