#BL602 EVB on #NuttX supports one GPIO Input, one GPIO Output and one GPIO Interrupt ... And names them sequentially: "/dev/gpio0", "/dev/gpio1", "/dev/gpio2" ... Which gets super confusing because "/dev/gpio0" doesn't map to BL602 GPIO Pin 0 🤔
https://github.com/lupyuen/bl602_expander#bl602-evb-limitations
#BL602 GPIO Expander for Apache #NuttX RTOS ... Coming up next!
https://lupyuen.github.io/articles/touch?23#appendix-gpio-interrupt
Wonder why we must enable I2C Logging ... Or #PineDio Stack's Touch Panel Driver will fail 🤔
#PineDio Stack's display is rotated sideways ... But we can fix this!
https://lupyuen.github.io/articles/touch?20#screen-is-sideways
How #PineDio Stack's Touch Panel handles a Touch Down Event in #NuttX RTOS
https://lupyuen.github.io/articles/touch?18#touch-down-event
Our #NuttX App reads the data from #PineDio Stack's Touch Panel
https://lupyuen.github.io/articles/touch?17#read-touch-data-1
We prevent unnecessary I2C Reads in #PineDio Stack's Touch Panel Driver ... By checking whether the screen has been touched
Reading the Touch Data from #PineDio Stack's CST816S Touch Panel
https://lupyuen.github.io/articles/touch?12#get-i2c-touch-data
Here's the Touch Data returned by #PineDio Stack's CST816S Touch Panel
https://lupyuen.github.io/articles/touch?11#fetch-touch-data
Testing the GPIO Interrupt that's triggered ... When we tap #PineDio Stack's CST816S Touch Panel
https://lupyuen.github.io/articles/touch?10#test-gpio-interrupt
Initialising the Touch Panel Driver on #PineDio Stack #BL604
https://lupyuen.github.io/articles/touch?8#initialise-driver
IoT Techie and Educator / Apache NuttX PMC