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.

Saving Memory greater than 32k words to a file?

Guru 15580 points

CCSv5.3

C5515

I am trying to save a block of 57k words of memory while in a debug session. However, when I use Save Memory, and use a start address of 0x8002 and a length of 57000, type size=16 bits., I get a file with zeros starting at 32768 and going to 65535. From 65535 to the end of the file appears to be correct. When viewing the actual memory in CCS, I can see the correct data where the zeros appear in the file.

What could be causing this 32k word hole in the file? FYI, I am compiling with a huge memory model.

  • Mike,

    By looking at your other posts I imagine you are talking about a C5515, right? If so, I was able to dump both data and program memory without a gap on my C5515 USBSTK. However I am using TI Emulators package release 5.1.73.0 (check menu Help --> About Code Composer Studio, tab Installation Details), which may make a difference (a bug fixed, perhaps).

    If the target is different, would you mind sending it so I can try to reproduce this?

    Regards,

    Rafael

  • Rafael,

    Yes (notice at the top of my post) I am using the C5515 and CCSv5.3. So hopefully there are no new bugs in my version of CCS.

    My target is a custom board. I am using a XDS560V2 STM emulator probe which communicates directly to the C5515 via JTAG pins. The gap appears in both the internal RAM memory dump, as well as a dump from my external flash memory (parallel using EMIF).

    When you say you are using TI EMulators package, does this mean you do not have a hardware emulator?

  • Mike,

    MikeH said:

    Yes (notice at the top of my post) I am using the C5515 and CCSv5.3. So hopefully there are no new bugs in my version of CCS.

    Duh. Sorry, I haven't got much sleep lately...

    The memory dump function is very basic, thus the emulator shouldn't matter - however, I have some news: I thought I was running CCSv5.3 but I was in fact running 5.4. Doing the same operation in CCSv5.3 I can see the issue happening (zeros starting at address 0x8000 through 0x10000).

    Therefore it is fixed in the new release - would you mind giving this new version a try? I would strongly recommend installing it in a different directory and opening a new workspace (this avoids any disruption in your current development environment).

    MikeH said:

    When you say you are using TI EMulators package, does this mean you do not have a hardware emulator?

     
    The TI emulators package is the software component of CCS that contains all the emulation device drivers, which can influence in the interaction with the hardware.
     
    Regards,
     
    Rafael
  • Rafael,

    Thanks for tracking this down. I will give it a try later. Upgrading in the midst of a product release is a bit of a bad idea....:)

  • Mike,

    I hear you; I tried to dump memory using other methods such as GEL functions and scripts, but the issue persists.

    I apologize for the inconvenience,

    Rafael

  • I'm just glad you found it.

    THanks!