MSPM0G3519: MSPM0G3519 LaunchPad flash erase and reprogram

Hi,

I am using CCS version 20.4. my workspace looks like this. I am not getting the option mass erase script. please help me out

4

Hi, 

Thanks, I got it. I erased. After that again I started debugging, now the debugger is started, but it is not stopping at the break point and the RGB LED also not blinking. It seems debugging is not working now. But Flashing the code is working fine. Where I did the mistake please guide me

Hi, 

Thanks, I got it. I erased. After that again I started debugging, now the debugger is started, but it is not stopping at the break point and the RGB LED also not blinking. It seems debugging is not working now. But Flashing the code is working fine. Where I did the mistake please guide me

As I am new to this, I want to test some codes, how they are working and I want to familiar with this IDE. So, I don't want the code to flash everytime. Is it possible? like earlier I used PIC from Microchip, there debugging means it will simply debug , it won't flash it. So, whenever I switch it ON, the chip is empty only untill unless I am not flashing the code in that.

Dibyarekha Maharana said:

it is not stopping at the break point and the RGB LED also not blinking.

I can find the root cause based on the information you provided.

Because of the optimization, you can not add BKPT to some function.

Two method here:

Add __NOP(); and add breakpoint here.

Add __BKPT(0); as a breakpoint, but you can't disable it during debug, unless you download a new firmware without __BKPT(0);

There are limited hardware breakpoint supported in Arm Cortext M0+ core.

Dibyarekha Maharana said:

As I am new to this, I want to test some codes, how they are working and I want to familiar with this IDE. So, I don't want the code to flash everytime. Is it possible? like earlier I used PIC from Microchip, there debugging means it will simply debug , it won't flash it. So, whenever I switch it ON, the chip is empty only untill unless I am not flashing the code in that.

No, doesn't support to run it from RAM in CCS.

It's OK to program it, Flash support 100k erase cycles if your firmware is not large (<32kB).

You can request a new LaunchPad when the Flash is dead after 100k cycles.

Add __NOP(); and add breakpoint here.

Add __BKPT(0);  where to add these lines?

Ohh, So, Erasing also I have to take care. I can't erase randomly. After closing and opening the IDE, now the breakpoint is working.

One More thing. I want to test the EEPROM Emulation, I am not understanding anything. Which code to import and how to test it. Is it only 16KB available for EEPROM Emulation? I want to store my data and retrieve at power on. Is it possible with this?

Ohh. Okay . Thanks a lot. Your support helped me a lot. Enjoy the New Year. 

Happy New Year.

1. EEPROM
   1. Type A
      1. https://www.ti.com/lit/pdf/slaaen2
      2. C:\ti\mspm0_sdk_2_07_00_05\examples\nortos\LP_MSPM0G3507\eeprom\eeprom_emulation_type_a
   2. Type B
      1. https://www.ti.com/lit/pdf/slaaen3
      2. C:\ti\mspm0_sdk_2_07_00_05\examples\nortos\LP_MSPM0G3507\eeprom\eeprom_emulation_type_b

You can put EEPROM to both Flash bank 0 and 1 or databank.

EEPROM mechanism is quite complex, it's better to learn the Flash first if you want to learn details of EEPROM.

Okay. I will try to learn in these 7 Days. I will wait for the support team at your end

There will be another team member to support you next week.

But this week... it's new year holiday~ hahaha