SLAAEL2 August   2025 MSPM0G1106 , MSPM0G1107 , MSPM0G1506 , MSPM0G1507 , MSPM0G1518 , MSPM0G1519 , MSPM0G3106 , MSPM0G3106-Q1 , MSPM0G3107 , MSPM0G3107-Q1 , MSPM0G3506 , MSPM0G3506-Q1 , MSPM0G3507 , MSPM0G3507-Q1 , MSPM0G3518 , MSPM0G3518-Q1 , MSPM0G3519 , MSPM0G3519-Q1 , MSPM0L1306

 

  1.   1
  2. 1Description
  3. 2Required Peripherals
  4. 3Design Steps
  5. 4Design Considerations
  6. 5Software Flow Chart
  7. 6Application Code
  8. 7Results
  9. 8Additional Resources
  10. 9E2E

Design Considerations

  1. Race conditions: To avoid the possibility of missing a button press, the application code quickly sets flags within the respective interrupt handler. This allows the processor to get-in-get-out and minimize the time frame that another triggered interrupt needs to be pending.
  2. Debouncing: Debouncing of the buttons can cause unintended interrupts to affect the way the application code runs. To prevent this from happening, the interrupt is disabled inside of the interrupt handler that is triggered. A timer is utilized to re-enable any disabled interrupts about 10ms after entering the interrupt handler.