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

LAUNCHXL-CC1312R1: drivers/GPIO vs drivers/Pin

Keith Barkley
Guru 42035 points
Part Number: LAUNCHXL-CC1312R1

I see that the gpio interrupt example uses the GPIO driver while the EasylinkExhoTX example uses the Pin driver.

Is there any advantage to either one? Can you use them both in the same project. I was adding buttons to my EasyLink project and having both interfaces made it difficult to combine the projects.

  • 0
    TI__Guru**** 317180 points

    For the example you mentioned, we also have a pinInterrupt example.

    The short reason for both a GPIO and a PIN driver is that the  GPIO driver can be used for all the products in the simplelink family but PIN is only for CC13xx and CC26xx. GPIO is index based which require slightly less memory than the PIN implementation.

    For most cases it's down to which API you prefer. Since GPIO is generic, not all features for the CC13xx/ CC26xx DIOs are implemented , the pin driver contains better support for the DIO control for these devices. 

  • 0 in reply to TER
    Guru 42035 points

    Ah, so it sounds like the PIN driver is the way to go, since this will strictly be a CC13XX project.