Other Parts Discussed in Thread: CC1310
This seems to come up every few years.
I see that there are Pin and GPIO examples for button interrupts.
What are the differences between the API's? Which is "better"?
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.
This seems to come up every few years.
I see that there are Pin and GPIO examples for button interrupts.
What are the differences between the API's? Which is "better"?
Try to refer to Alan's reply in e2e.ti.com/.../529456
The post YK refers to is 4 years old.
As I understand it, the GPIO uses slightly less memory than the PIN driver. syscfg is also build to be a generic tool for a wide range of products and hence it's just support GPIO since the PIN driver is just covering a few products.
Some may find one of the drivers easier to use than the other. I also believe the PIN driver has implemented more of the possible settings described in the TRM for the DIOs.
So non of them is "best", it's more down to preference.
Thanks TER. All the answers I found were pretty long in the tooth. One thing I found is that there seems to be better interrupt control with the GPIO drivers - there is more granularity.
I am just starting a new project and wondered if there were any new developments.
The PIN and GPIO drives have not undergone too many changes over the years as far as I know. The CC1310 SDK is not regularly updated, just for major bug fixes. If you are familiar with one of the drivers from a previous project, use the same if you managed to do what you needed to do.