Add the following lines to msp430.dat to enable or modify the specific debug options.

MSP430 low-power debugging

msp430_lowpowerdebug=true

MSP430 programming and erase options for GDB

The BSL or the protected memory can be unlocked at the start of the session using the msp430_connectaction keyword.

msp430_connectaction=[unlockbsl] [unlockprotected] [<other connect options>]

If protected memory is unlocked, it is erased on download if the download erase option is set to erasefactory , erasemain , or erasemainandinfo , or if the download erase option is set to erasesegment and the download image includes protected memory data.

msp430_loadaction controls whether a reset is done before or after download and also configures erase options for download.

msp430_loadaction =[resetbefore] [resetafter] [erasefactory|erasemain|erasemainandinfo|eraseuser|erasesegment] [<other load options>]

Where:

erasefactory = MSP430_Erase(type = ERASE_TOTAL, ...) called at the start of each download

erasemain = MSP430_Erase(type = ERASE_MAIN, ...) called at the start of each download

erasemainandinfo = MSP430_Erase(type = ERASE_ALL, ...) called at the start of each download

eraseuser = MSP430_Erase(type = ERASE_USER, ...) called at the start of each download

erasesegment = MSP430_Erase(type = ERASE_SEGMENT, ...) called the first time that the segment is written to during each download

Another optional connect action is to reset or erase on connect:

msp430_connectaction=[reset] [erasefactory|erasemain|erasemainandinfo|eraseuser]

If this line is not present, the default is to not reset or erase on connect.

If the BSL or protected areas are unlocked, they are erased on connect if the erasefactory or erasemainandinfo options are set. They are erased on download if the erasefactory , erasemainandinfo , or erasesegment options are set and the image includes the BSL or protected segment.

No action is taken on the auto run or launch options as they are outside the scope of the GDB agent.

MSP430 verification options for GDB

msp430_loadaction includes a verify keyword. If this keyword is present, each write to flash is verified.

msp430_loadaction=[verify]

Add MSP430 breakpoints options for GDB

msp430_default_breakpoint = [software|hardware]

By default, the MSP430 GDB agent uses software breakpoints (type=BP_SOFTWARE) for all GDB break commands. If a software breakpoint fails, the GDB agent then attempts to set a hardware (type=BP_CODE) breakpoint. A hardware breakpoint can be set explicitly using the GDB hbreak command.

If the msp430_default_breakpoint option is set to hardware, the GDB agent uses type BP_CODE for all GDB breakpoints (both break and hbreak commands).