• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 30 subscribers
  • Views 182 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

MSPM0L1305: ODIO input configuration impacted by DOUT

Munan Xu
Expert 4950 points
Part Number: MSPM0L1305

Tool/software:

Hello,

I have a customer who's trying to configure the ODIO on PA0/1 as an input. What they're finding is that even with an external 100k pull up resistor the GPIO does not go to a full VDD voltage unless they also set the DIO value to "1".

Their IOMUX configuration is as follows:

IOMUX->SECCFG.PINCM[PIN_X] =IOMUX_PINCM_HYSTEN_ENABLE|IOMUX_PINCM_INENA_ENABLE|IOMUX_PINCM_PC_CONNECTED|0x1;

Is there a requirement that they need to set the DIO register for these IO's? I thought if these were configured as input writing the DIO register would not have an effect and that's what the customer's experience is for every other IO.

Munan

  • 0
    TI__Mastermind 39775 points

    What is the DIO mean? DIO in the DOUT? I can't find it on the TRM.

    Does customer has any test result? What is their concern? 

  • 0 in reply to Eason Zhou
    TI__Expert 4950 points

    Hi Eason,

    DIO = Digital IO, so yes they were seeing that they needed to set DOUT to 1 for the pins to be truly pulled up to VDD.

    So I did some bench testing on my side with the launchpad and I didn't see the same behavior, one thing this suggests is maybe the 100k pull up is not strong enough.

    So I think this is closed for now, but seems odd.

    Munan