• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 52 subscribers
  • Views 361 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.

Original question:

CC2651R3SIPA: GPIO Bug

CC2651R3SIPA: Bluetooth forum

D.V.L.
Prodigy 55 points

Part Number: CC2651R3SIPA

Oh my god.

Hello TI experts. Sorry for my ignorance. But What does "Supports only peripheral functionality" exactly means? When I was designing my hardware, a Data Ready from an ADC, looked to me like a peripheral functionality.

It seems I will need to redesign my board. Is it true?

Why the datasheet don't indicate it as a reserved pin, as "do not connect", or something like that? It's a perfect bait for confusion.

What happens if I try to configure this pin by code? It will just not work, or will it conflict with something?

Thank you for your support.

Diego Loss

  • 0
    TI__Mastermind 21630 points

    Hi, 

    I am afraid this pin can only be used if configured for a peripheral as stated in the datasheet Table 7-1.
    The configuration as a GPIO in the register filed  IOCFG31.PORT_ID in Table 13-61 is not supported for SIP module.

    Regards


  • 0 in reply to FI
    Prodigy 55 points

    Hi FI,

    Yes. The GPIO_31 don't answare when configured as an input. I was obligates to isolate the TDI (JTAG) signal (usless), to receive the flag from the external ADC. OK the first version always has this kind of time consumpting events.


    Regards,

    Diego