This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

MSP432P401R: capture mode function of request interrupt

Part Number: MSP432P401R

What's the difference between PM_TA0.1 pin and lead TA2.4 without PM name using the capture mode function of request interrupt?The same configuration method TA2.4 can be used frequently, and PM_TA0.1 can not be used.

  • I am not sure I understand the question.  Are you seeing an issue that is described in errata PORT34?  Let me know if this is not the issue.  Functionally the capture mode is consistent across all of the timerA instances.

    Regards,
    Chris

  • PM_TA0.1 selects timer_A0, why there is a PM name in front of it, plus the PM name in the Port Mapper class, most of it does not add in the Timer class, whether the use of capture mode is different between the two classes, I configure the same mode, capture the waveform with capture mode, the same waveform timer_A2 and timer_A3 capture the waveform to get The interrupt counter value is correct, the interrupt counter value obtained by timer_A0 is relatively large, and the value obtained is constantly changing.

  • Since the motor PWM signal is TimerA0, TimerA0 can no longer be used as capture mode, can not be used at the same time. During the debugging process, it is found that when the motor does not start, the remote control key value is normal, it can also be switched over normally. When the motor starts to rotate, the remote control key value is confused.
  • The port mapper only maps the output to the port pins. It is not related to nor impacts the peripheral. It is possible to port map (PM) the same signal to several pins.

    To confirm, the difference in performance in the TimerA0 is because it is also being used to generate a PWM. The TimerA has 5 capture compare registers (CCR) but only one timer control register. The timer control register is typically set to 'UP' mode for PWMs (compare mode) where CCR0 determines the period of the PWM and another CCR (1-4) determines the duty cycle. The capture mode simply takes a snapshot of the timer counter, which if being used with UP mode will only provide values between 0 and CCR0. The meaning of that value requires knowledge of how many times the timer has reached CCR0 and rolled back over to 0.

    How are you configuring TimerA0 to provide both capture and compare? How are you accounting for roll-overs and timer overflows?

    Regards,
    Chris
  • Hopefully you have been able to resolve your issue. Please reply if you have additional questions or issues.

    Regards,
    Chris

**Attention** This is a public forum