• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 78 subscribers
  • Views 349 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.

MSP430FR2111: TB affection both P1.6 and P2.0

Terry Deng
Intellectual 2485 points
Part Number: MSP430FR2111

Hi All

Customer meet a issue that when P1.6 select to TB function and firmware change its setting from TB0.1 to TB0.CCI1A, the P2.0 GPIO output will change from high to Low by device itself.

I double check the register setting on watch window, and confirm P1SEL.6 = 10 (P1.6 is TB function), P1DIR.6 = 1 (P1.6 is TB0.1 function); P2SEL.0 = 00 (P2.0 is GPIO function), P2DIR.0 = 1 (P2.0 is output). and SYSCFG3.TBRMP = 0 (CCI1A set to P1.6). In this case,  we test P2OUT.0 set to 0 or 1, the P2.0 can measure output low or high by normally. 

However once we change P1DIR.6 from 1 to 0 (P1.6 set to TB0.CCI1A), the P2.0 will measure keep low level no matter P2OUT.0 is 0 or 1. May I get your help advice?   

Another question Customer use P1.6 as TB0.CCI1A to capture external pulse, however P1.6 in FR2111 has not wake up function, so customer connect P1.6 and P1.0 together, use P1.0 to wake up FR2111 from LP3 mode and P1.6 to capture by same external pulse. Do you think if it is ok for such usage?   

     

  • 0
    TI__Genius 17960 points

    Hi,

    could you please send me the test code, which you used to generate the above behavior? Many thanks in advance.

    On the connection of GPIOs with wake-up functionality with GPIOs without this functionality I need to double check with our designers.

    Best regards

    Peter

  • 0 in reply to Peter Spevak
    TI__Intellectual 2485 points

    Hi Peter

    a) For question 1, the basic setting as:

    P1SEL.6 = 10 (P1.6 is TB function), P1DIR.6 = 1 (P1.6 is TB0.1 output function); P2SEL.0 = 00 (P2.0 is GPIO function), P2DIR.0 = 1 (P2.0 is output). and SYSCFG3.TBRMP = 0 (CCI1A set to P1.6).

    TB configuration as : TASSEL__SMCLK + MC__CONTINUOUS;  CM_FALLING + SCS_1 + CCIS_CCIA + CAP + CCIE

    Once change P1DIR.6 from 1 to 0 (TB0.OUTPUT change to TB0.CCI1A), the P2.0 will be affected to pull low, even if P2.0 set as GPIO function and output high.

    b) For question 2, we found the TB capture sometime unstable:

    Just configure and startup TB as above setting to capture external pulse signal by P1.6 or P1.7,  and toggle P2.7 in capture interrupt function as indication.

    If setup All others GPIO as input, the P2.7 will toggle after each external pulse falling edge, it means capture work well

    If setup P2.0 or P2.1 as GPIO output function, no matter output high or low, the P2.7 sometime will miss toggle after external pulse falling edge, it has 1/50 around opportunity for such issue

  • 0 in reply to Terry Deng
    TI__Genius 17960 points

    Hello Terry,

    it would be a duplication of effort and risking not having the same code, if I would try to replicate your case my self just based on your verbal description. That's the reason, why I requested the test code you have been using.

    Thus I am repeating my request, please send me the test code you have used, when experiencing the problem. Many thanks in advance.

    Best regards

    Peter

  • 0 in reply to Peter Spevak
    TI__Genius 17960 points

    Hello Terry,

    in case you still need support on this, please let us know. For now I am closing this thread due to inactivity.

    Best regards

    Peter

**Attention** This is a public forum