On Fri, Sep 11, 2020 at 10:24 AM Gregory Nutt <spudan...@gmail.com> wrote: > > > > I actually just got one of these FeatherWing boards. I was thinking > > about using it with the nRF52 Bluefruit LE - nRF52832. Seemed like a > > cool way to add a UX for interacting with the bluetooth stuff. > > Cool! That could be useful if you need a complete handheld UI. There are > already an ILI9341 and STMP811 drivers. I suppose it will need a custom > keyboard driver over I2C. There is also a GPIO expander, Neopixel, > microSD. I don't know which GPIO expander is on the board. GPIO > expanders are a nuisance because you can't get off the ground without > first having the GPIO exander. The LCD backlight, touchscreen, microSD > and keyboard all depend on the GPIO expander. Not for people who need > immediate gratification.
It looks to me like they dropped the SAM20 in there to kind of hide the IO expander logic behind a i2c keyboard interface, so it might actually be easier in some ways. At least via polling the FIFO to start with. https://www.solder.party/docs/keyboard-featherwing/schematics_keyboard_featherwing_keyboard.png But yeah all the touch screen and backlight logic is behind the STMP811 touch/gpio expander. https://www.solder.party/docs/keyboard-featherwing/schematics_keyboard_featherwing.png With support for something like this how do you think it is best organized in the board folder layout and do you think it would make sense to have a logical block for this that could be shared with other feather boards? --Brennan
