Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compatibility with ESP32S3 #123

Open
wants to merge 17 commits into
base: proto5
Choose a base branch
from
Open

Conversation

DieKatzchen
Copy link

I've made changes necessary to work with ESP32S3 boards, primarily the Fae Mod board. It provides the option to use BLE serial (implemented using the Nordic UART Service standard), and it switches out ESP32Servo for ESP32-ESP32S2-AnalogWrite, because ESP32Servo can only control one servo on the ESP32S3.

This firmware will compile and run on an ESP32-S3 board, such as the Fae Mod design. Currently outputs error messages to the integrated USB serial and motion data to the UART pins
Implemented BLE communications using the Nordic UART Service standard
Added the define to workaround the bootloop error
Had to change servo library for compatibility with ESP32S3, also had been passing the string incorrectly on incoming messages
Splitting back to proto5 and reverting settings changes to the default
@DieKatzchen DieKatzchen changed the title Proto5 Compatibility with ESP32S3 Apr 1, 2024
Somehow this got lost between versions of the code
Somehow this got lost between versions of the code
The for loop copying rawFingers[] to fingerPos[] was bailing out early, so the splay data wasn't being sent.
EEPROM.h was loading when it shouldn't, setting all the values to 0. EEPROM.h is deprecated anyway, so I replaced it with Preference.h which is the new recommended method.
The for loop copying rawFingers[] to fingerPos[] was bailing out early, so the splay data wasn't being sent.
EEPROM.h was loading when it shouldn't, setting all the values to 0. EEPROM.h is deprecated anyway, so I replaced it with Preference.h which is the new recommended method.
Got bored, so I threw together some code to make a WS2812 (such as the one on the Fae Mod board) work as the debug board. Red means it's started up but BLE isn't running (you should never actually see this), blue means BLE is running but not connected, green means connected.
Added a preconfigured file for the FaeMod specifically
Add a check to make sure that we don't try to load these values if we aren't using mixing. The saved values persist between flashes, so they could be from a previous flashing.
Change the `\\` to `//`. That'll teach me to work directly in the Github editor
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant