You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
thx for mentioning the esp32_mouse_keyboard repository.
I had a quick look at your documentation and it seems the task of fitting your serial AT API into the ESP32 is not too hard.
In general, we are using this repository for an addon module to provide BLE HID to our assistive devices like FABI, FLipMouse and FLipPad. We also use a serial interface between these two parts, but we originally used Adafruit EZKey modules, so we kinda stuck to this API. Our BLE firmware implements 2 serial ports:
UART0 is the debugging/programming UART, which is connected to the USB-serial chips on all of the devboards.
UART1 is connected to FABI/FLipMouse/FLipPad
Necessary changes would be:
Remove the "test commands" and implement your AT api in the uart_console_task
Remove the uart_external_task (if you want to use the devboard's USB connection)
Theres some desire from developers for us to support the ESP32
See #29 in discussion and across the net around availability of nrf chipset being hard/expensive to source.
There's some prior art in this area -notably from @benjaminaigner & the asterics team on https://github.com/asterics/esp32_mouse_keyboard
I think that would be helpful to the project. Just need to weigh up the priority for us to do this and let the dust settle on the current nrf firmware
The text was updated successfully, but these errors were encountered: