• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 53 subscribers
  • Views 533 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.

CCS 5.5 Project Properties Dialog question + Debugging question

Stephen Phillips1
Expert 1250 points

1  project properties->Debug->msp430 properties has

  1. Erase Main memory Only
  2. Erase Main memory and information Memory
  3. Erase Main memory information Memory and Protected Information memory
  4. Erase and Download necessary segments only (differential download)
  5. Replace Written memory locations, retain unwritten memory locations

I normally use 1 however, I have a section of flash I would like not erased and I am trying to figure out how to prevent it from erasing each time I run the debugger. 4 seems like a possible candidate but ... anyhow I am puzzled how to selectively erase the flash memory space. So how does one do this? IE selectively erase / program sections of the msp430 flash. Do I edit the lnk file (seems a dubious method)?

2  I would prefer not to have to reprogram the entire chip each time I start the debugger, is their a way to just RUN the debugger if nothing has changed in the code, I suppose it has no way of knowing the contents of the chip unless it does a compare (hmm) just curious if I missed something.

  • 0
    TI__Guru**** 161585 points

    The differential download option will only erase and program the flash segments that have actually changed since the last build.

    Alternatively if you are sure nothing has changed you can launch the debugger and load the symbols without touching the memory.  I usually do that by opening the Target Configurations view from the View menu.  Expand your project and select the ccxml file (likely in the targetConfigs folder).  Right click on it and select launch selected configuration.  This will launch the debugger for that hardware configuration.  You can then click on the connect button to connect to the device.  Then go to the drop down arrow beside the program load button and select load symbols.  Select the .out for your project.

    Regards,

    John

  • 0 in reply to JohnS
    Expert 1250 points

    JohnS said:

    The differential download option will only erase and program the flash segments that have actually changed since the last build.

    Alternatively if you are sure nothing has changed you can launch the debugger and load the symbols without touching the memory.  I usually do that by opening the Target Configurations view from the View menu.  Expand your project and select the ccxml file (likely in the targetConfigs folder).  Right click on it and select launch selected configuration.  This will launch the debugger for that hardware configuration.  You can then click on the connect button to connect to the device.  Then go to the drop down arrow beside the program load button and select load symbols.  Select the .out for your project.

    Regards,

    John

    Ok so I'll have to just live with how it handles reprogramming things in that regard.

    For question #2, does the entire flash memory require erasure each time you reprogram? I want to have a section of flash to store information that is similar to the INFO sector usage. IE serial # calibration information etc. Suggestions welcome.


    Stephen