• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 59 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

MSP432E401Y: How to debug via CCS with XDS110 without erasing Bootloader

Harsha SK
Prodigy 20 points
Part Number: MSP432E401Y
Other Parts Discussed in Thread: UNIFLASH

Tool/software:

Hi,

Is there any possibility to debug the application code via CCS with XDS110 without any effect on/ without erasing Bootloader / any specific memory location. If yes please guide the proper steps.

Because the problem we are facing is - when bootloader is flashed via Uniflash and then XDS110 debugger is connected for application debug , where we have to get the bootloader version saved in specific memory location is getting erased when connected.

Thanks 

  • 0
    TI__Guru**** 191066 points
    Harsha SK said:
    where we have to get the bootloader version saved in specific memory location is getting erased when connected.

    When XDS110 is connected, it will not erase the flash. It must be under user's control to issue either an erase operation or loading a new program. Normally, the bootloader resides at 0x0 and your application is at some higher address such as 0x4000. If you are reloading a new application image, it will by default erase the entire flash which includes the bootloader at 0x0. To prevent the bootloader at 0x0 from getting erased, you can select 'Necessary Pages Only" for the Erase option. The programmer in CCS will know to only erase the flash pages for which the application will occupy, not the flash bootloader at 0x0.