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.

Question about com.ti.debug.engine.scripting.Memory.saveRaw

Hi,

I use a DDS script with CCS v4.2.4 to program or dump the content of the SPI flash of the DA830 DSK BOARD via a command-line tool. To dump memory I use the ti.debug.engine.scripting.Memory.saveRaw function with "nTypeSize" set to 8 for byte access. However when I try to dump the memory always four times of "nLength" bytes are written to the file. I still have to verify whether the same is true also for the ti.debug.engine.scripting.Memory.loadRaw function.

An additional problem is the performance of the function or the emulator; I get about 4.1 KiB/s via EMBED USB (XDS510USB) of the EVM. I know the XDS510USB is not very fast and we are thinking about purchasing faster emulators if the processor will be used for a future project: what performance improvement can I expect from these emulators? We currently reach transfer rates of far more than 100 KiB/s with our current platform based on the processor of a competitor.

  • Simon Tomschik said:
    To dump memory I use the ti.debug.engine.scripting.Memory.saveRaw function with "nTypeSize" set to 8 for byte access. However when I try to dump the memory always four times of "nLength" bytes are written to the file. I still have to verify whether the same is true also for the ti.debug.engine.scripting.Memory.loadRaw function.

    nLength is the number of words you wish to save

    Simon Tomschik said:
    I know the XDS510USB is not very fast and we are thinking about purchasing faster emulators if the processor will be used for a future project: what performance improvement can I expect from these emulators?

    I would an XDS560 class emulator. The performance is quite good. More details are here:

    http://processors.wiki.ti.com/index.php/XDS560

    Thanks

    ki