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.

CCSV5 load memory

When I use CCSv5 with the C6678, I am trying to load the memory with a .dat file.   I do this by right clicking the memory browser in CCS and selecting load memory to the MSMC memory at 0x0C000000.  It seems to work in the beginning, but then I see there are large gaps in the memory I loaded.  Basically large spaces where there shouldn't be.  The load seems to skip regions of of the Memory.  Why does the "load memory" option in CCSv5 skip parts of the MSMC memory when I want all my data to be together to be all together. thanks Mike

  • Hi Michael,

    How was the *.dat file created in the first place? Did you use the save memory option from the memory browser when connected to the 6678 in the past?

    Also let me know what exact version of CCSv5 you are using. Provide the full version number (ex. 5.1.0.09000)

    Thanks

    ki

  • I'm using

    Version: 5.1.0.08020

    created the .dat file from the bin2ccs tools, but there is no gap in the data in the file from looking at it.  We have used this before and hasn't seemed to give us this issue when writing it in other parts of memory.

  • Could you provide the dat file? And are you using the dat header information in the file when you load it (do you even have header information in there)?

    Thanks

    ki

  • Hi ki,

           Could you please elaborate me about the Header information that need to be included?? We are facing a different issue..

    When i am trying to load memory with a dat file, It is straight away asking for Header information which is not present in the .dat file.

  • Hi Amirtha,

    Here is the information on the header:

    The header information for data files uses the following syntax:

    MagicNumber  Format StartingAddress PageNum Length

    MagicNumber:    Fixed at 1651.
    Format:    A number from 1 to 4, indicating the format of the samples in the file. This number represents a data format: hexadecimal, integer, long, or float.
    StartingAddress:    The starting address of the block that was saved.
    PageNum:    The page number the block was taken from.
    Length:    The number of samples in the block.

    All header values are assumed to be TI-style hexadecimal values.


    The following is an example of a Code Composer Studio data file:

    1651 1 800 1 10
    0x0000
    0x0000
    0x0000
    0x0000
    0x0000
    0x0000
    0x0000
    0x0000
    0x0000
    0x0000
    0x0000
    0x0000
    0x0000