SDAA028 June   2025 MSPM0C1104 , MSPM0C1105 , MSPM0C1106 , MSPM0G1106 , MSPM0G1107 , MSPM0G1506 , MSPM0G1507 , MSPM0G1518 , MSPM0G1519 , MSPM0G3106 , MSPM0G3106-Q1 , MSPM0G3107 , MSPM0G3107-Q1 , MSPM0G3506 , MSPM0G3506-Q1 , MSPM0G3507 , MSPM0G3507-Q1 , MSPM0G3518 , MSPM0G3518-Q1 , MSPM0G3519 , MSPM0G3519-Q1 , MSPM0H3216 , MSPM0L1306

 

  1.   1
  2.   Abstract
  3.   Trademarks
  4. 1Introduction to MSPM0 Timer Capture and Compare Module
  5. 2Implementations for Capturing 0% or 100% Duty Cycle
    1. 2.1 Application Conditions
    2. 2.2 Implementation Introduction
      1. 2.2.1 Use COMP Detect High or Low
      2. 2.2.2 Use ADC Detect High and Low
      3. 2.2.3 Use GPIO Detect High or Low
  6. 3Demo Code Running
  7. 4Summary
  8. 5References

2.2.3 Use GPIO Detect High or Low

If the implementations above cannot be used in the application, then use GPIO to detect for 0% or 100% duty cycle high or low. This implementation needs an additional GPIO to detect PWM. The internal connection can be connected as shown in the demo code.

GPIO Implementation Connection in the Demo Figure 2-6 GPIO Implementation Connection in the Demo

Although IOMUX has the input mux module, TI recommends to use one GPIO as the capture input of the timer and the GPIO input for 0% or 100% duty cycle high or low. There can be one missing PWM cycle if there is a non-0% or non-100% duty cycle PWM when the IO mux stays in GPIO mode, and can also have some glitches when changing back to the capture mode of the timer. This implementation of using two GPIOs can avoid these issues.