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.

How to use DAP (TMS570 device) in GUI composer?

Other Parts Discussed in Thread: MOTORWARE

I built a GUI composer project, when I run it, I found that it slows down the CPU (TMS570 ARM cortex R4) response. (I toggle the LED using real time interrupts. Once GUI composer is running, I can see the LED toggling rate changes).

I think it is due to the CPU time used for exchanging data throught the debug port.

But this is not a problem in the motorware gui composer project (built in gui composer 1.6, not compatiable with today's version in CCS5.5). I remember that, in the motorware project, we use DAP to exchange data.

So, my quesiton is: How to use DAP to exchange the data in GUI composer (built in CCS5.5)?

Thanks,

Haixiao

  • Hi Haixiao,

    In the past, we uses the DAP as a workaround where the driver doesn't support reading/writing memory while the target is running. Now that the driver natively supports reading/writing through the DAP, we have removed this workaround in GUIComposer.

    As far as I know, the performance for GUIComposer is no difference than CCS. You should be able to reproduce the slowless by entering the variables in the Variables view and enable continuous refresh.

    Take a look at the appInitScript.js file in your GUI app, see if you have this line "session.options.setBoolean("UseLegacyStopMode", true);". You might want to comment it out if your target supports realtime access.

    Regards,
    Patrick 

  • session.options.setBoolean("UseLegacyStopMode", true);". is the rootcause.

    Thanks,

    Haixiao