There is a macro called GPIO_ID_PIN() which, when called with a logical pin number (eg. 14 for GPIO14) is supposed to return a value we can pass into the SDK APIs. However, examining the header file, I find that GPIO_ID_PIN(x) == x ... so effectively, this macro returns its own numeric parameter. This then begs the question ... is GPIO_ID_PIN() needed? Are we "future proofing" ourselves from some dramatic architecture change in the future? What is the thinking behind asking us to use this macro?
Neil
Do we still need to code GPIO_ID_PIN()?
Who is online
Users browsing this forum: No registered users and 86 guests
Login
Newbies Start Here
Are you new to ESP8266?
Unsure what to do?
Dunno where to start?
Start right here!
Latest SDK
Documentation
Complete listing of the official ESP8266 related documentation release by ESPRESSIF!
Must read here!
- All times are UTC+08:00
- Top
- Delete all board cookies
About Us
Espressif Systems is a fabless semiconductor company providing cutting-edge low power WiFi SoCs and wireless solutions for wireless communications and Internet of Things applications. We are the manufacturer of ESP8266EX.