• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 53 subscribers
  • Views 628 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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 optimize LoadRaw and saveRaw DSS functions?

Parameswaran L
Prodigy 190 points

Hi,

I am using loadRaw and saveRaw function in dss script to load and store raw frames from target.

The loadRaw function is taking around 22 seconds to load single raw frame of size 1.2 MB.

The saveRaw function is taking around 56 seconds to save 8 raw frames with total size of 2.1 MB.


Is there any way to optimize these functions?

  • 0
    TI__Guru**** 450031 points

    The load/save raw DSS APIs are probably the best APIs in terms of download performance. What debug probe are you using? If you are using one of the more slower probes (like XDS100), then upgrading your probe would have the biggest impact.

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 190 points

    Hi Ki,

    I am using XDS560V2 STM debug probe. Is there any way the performance can be increased by modifying the code?

  • 0 in reply to Parameswaran L
    TI__Guru**** 450031 points

    Parameswaran L said:
    I am using XDS560V2 STM debug probe.

    That is one of our highest performing debug probes.

    hmm... when you use the memory load/save feature in the Memory Browser view, is the performance faster?

  • 0 in reply to Ki
    Prodigy 190 points

    Yes, when I use the memory load/save feature in the Memory Browser view, the performance is significantly faster.

  • 0 in reply to Parameswaran L
    TI__Guru**** 450031 points

    hmm, that's interesting. I would think they both used similar calls under the hood. Can you:

    1) provide the part of your script where the APIs are called (I want to see what parameters are passed to the API)

    2) enable debug server logging to generate a debug server log, then run the script and zip up the log and attach to this thread? I might be a good idea to have a simplified script when all you do is start a debug session, connect to the target, and call the APIs. That will make it easier to analyze the log.

    Thanks

    ki