• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 78 subscribers
  • Views 214 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

MSP430FR2675: CapTIvate Timer Usage

pcpro178
Intellectual 365 points
Part Number: MSP430FR2675

I am developing a firmware application based on the demo code for the BOOSTXL-CAPKEYPAD.  I have implemented a PWM driver using timer output TA0.1.  I added conditional compiles to optionally disable the cap-sense keypad code because it tends to generate spurious interrupts that make debugging of other subsystems difficult.  I noticed that the PWM output is very stable when I have the keypad disabled.  However, when the keypad is enabled, the PWM output becomes erratic.  A cursory review of the keypad driver code indicates that some timer is being used.  However, since it's calling into a compiled library, I'm unable to investigate further.  How do I figure out which timer the cap-sense keypad driver is using and modify it to use another timer module?

  • 0
    TI__Mastermind 28286 points

    Hi Pcpro,

    The timer of CapTIvate IP inside, this don't use general timer, thus this should not affect your PWM function.

    Is there some details about your issue? like abnormal waveform?

    Thanks!

    Best Regards

    Johnson

  • 0 in reply to Johnson He
    Intellectual 365 points

    It's still a square wave.  Could it be that the timer is getting pseudo-randomly stopped and started?  It is hard to tell.  I am using TA0.1 on P1.1 to generate the PWM waveform.  Here's what my waveform looks like when the keypad driver is disabled.  This is 20Hz, 25% duty cycle.

    This is what I get when I enable the CapTIvate keypad driver.

    It is critical that we get this resolved.  Does the CapTIvate keypad driver OR demo code in any way interact with P1.1 or Timer_A?  If we open a support ticket, would you be willing to look at my project?

  • 0 in reply to pcpro178
    TI__Mastermind 28286 points

    Hi Pcpro,

    It seems that very strange, for CapTIvate code, does this generate by our GUI?

    And did you try other pin for PWM output?
    Thanks!

    Best Regards

    Johnson

  • 0 in reply to Johnson He
    Intellectual 365 points

    It is odd.  I tried using TA1.1 (P1.5), and the waveform is generated as I would expect, even with the CapTIvate keypad driver enabled.  It appears very stable.  Since our design prevents us from using a timer output, other than TA0.1 (P1.1) for PWM generation, we really need to get to the bottom of the conflict that is introduced by the TI CapTIvate keypad driver.  Have you been able to reproduce this problem on your end?

  • 0 in reply to pcpro178
    TI__Mastermind 28286 points

    Hi Pcpro,

    I will try to reproduce this issue in my side and get back.

    Thanks!

    Best Regards

    Johnson

  • +1 in reply to Johnson He
    Intellectual 365 points

    This issue has been resolved.  The conflict was coming from another part of the code base that was developed for an earlier version of the hardware and wasn't properly guarded.  Thank you so much for your attention to this matter.

**Attention** This is a public forum