MSPM0G3507: Determining which interrupt interrupted

Hey Keith,

Keith Barkley said:

I am working with the flashctl_multiple_size_write example and just adding some extra erase and write commands, to get the feel of the thing. I don't know what is happening, but sometimes I end up in the "You didn't provide a handler, stupid!" while loop stub.

How do I determine what interrupt put me there? I don't have the flashctl interrupt enabled.

This is a very good question. 

For any device supported by the LP-MSPM0G3507, use the following code:

/*
* These are traps for debugging when you find that your code
* ends up in the default handler for some unknown reason.
* To keep the compiler from complaining, comment out the ones
* below if you already have a working handler for that vector.
*
*/
void NMI_Handler(void){ __BKPT(0);}
void HardFault_Handler(void){ __BKPT(0);}
void SVC_Handler(void){ __BKPT(0);}
void PendSV_Handler(void){ __BKPT(0);}
void SysTick_Handler(void){ __BKPT(0);}
void GROUP0_IRQHandler(void){ __BKPT(0);}
void GROUP1_IRQHandler(void){ __BKPT(0);}
void TIMG8_IRQHandler(void){ __BKPT(0);}
void UART3_IRQHandler(void){ __BKPT(0);}
void ADC0_IRQHandler(void){ __BKPT(0);}
void ADC1_IRQHandler(void){ __BKPT(0);}
void CANFD0_IRQHandler(void){ __BKPT(0);}
void DAC0_IRQHandler(void){ __BKPT(0);}
void SPI0_IRQHandler(void){ __BKPT(0);}
void SPI1_IRQHandler(void){ __BKPT(0);}
void UART1_IRQHandler(void){ __BKPT(0);}
void UART2_IRQHandler(void){ __BKPT(0);}
void UART0_IRQHandler(void){ __BKPT(0);}
void TIMG0_IRQHandler(void){ __BKPT(0);}
void TIMG6_IRQHandler(void){ __BKPT(0);}
void TIMA0_IRQHandler(void){ __BKPT(0);}
void TIMA1_IRQHandler(void){ __BKPT(0);}
void TIMG7_IRQHandler(void){ __BKPT(0);}
void TIMG12_IRQHandler(void){ __BKPT(0);}
void I2C0_IRQHandler(void){ __BKPT(0);}
void I2C1_IRQHandler(void){ __BKPT(0);}
void AES_IRQHandler(void){ __BKPT(0);}
void RTC_IRQHandler(void){ __BKPT(0);}
void DMA_IRQHandler(void){ __BKPT(0);}

Just in case anyone else stumbles on this thread looking for the same for devices supported by LP-MSPM0L1306. I'll add the equivalent for that device here:

/*
* These are traps for debugging when you find that your code
* ends up in the default handler for some unknown reason.
* To keep the compiler from complaining, comment out the ones
* below if you already have a working handler for that vector.
*
*/
void NMI_Handler(void){ __BKPT(0);}
void HardFault_Handler(void){ __BKPT(0);}
void SVC_Handler(void){ __BKPT(0);}
void PendSV_Handler(void){ __BKPT(0);}
void SysTick_Handler(void){ __BKPT(0);}
void GROUP0_IRQHandler(void){ __BKPT(0);}
void GROUP1_IRQHandler(void){ __BKPT(0);}
void TIMG1_IRQHandler(void){ __BKPT(0);}
void ADC0_IRQHandler(void){ __BKPT(0);}
void SPI0_IRQHandler(void){ __BKPT(0);}
void UART1_IRQHandler(void){ __BKPT(0);}
void UART0_IRQHandler(void){ __BKPT(0);}
void TIMG0_IRQHandler(void){ __BKPT(0);}
void TIMG2_IRQHandler(void){ __BKPT(0);}
void TIMG4_IRQHandler(void){ __BKPT(0);}
void I2C0_IRQHandler(void){ __BKPT(0);}
void I2C1_IRQHandler(void){ __BKPT(0);}
void DMA_IRQHandler(void){ __BKPT(0);}

Keith Barkley said:

Also, I keep getting "Sorry, you have too many breakpoints!" errors, when I have only specified one or two

I've encountered this as well, as the MSPM0 only has 4 hardware breakpoints. I've never done a full audit of where all of these can be used, but I know at least 2 of these may be used up by the debug settings. See below in your project properties/debug settings):

I expect that if you do the following, CCS should dump the location of all currently enabled breakpoints:

1. During a debug session, go to View->Scripting Console
2. Input the command eval("DEBUG_DumpBreakpoints()")

Best Regards,
Brandon Fisher