Closed FranseFrikandel closed 2 years ago
Looking at the errors that occur in serial monitor:
[ 83][E][Preferences.cpp:503] getBytesLength(): nvs_get_blob len fail: f NOT_FOUND
[ 173][E][Preferences.cpp:483] getString(): nvs_get_str len fail: n NOT_FOUND
[ 10914][E][Preferences.cpp:483] getString(): nvs_get_str len fail: i NOT_FOUND
These ID's appear to match ID's that are set in src/osw_config_keys.cpp
ID "f" is on line 75, "n" on line 44, "i" on line 23. Each of these seem like they should be set equal to config variables when looking into osw_config_keys.cpp. I believe these variables are also all configurable via the WiFi interface, and so presumably saved in flash memory. Is something going wrong here causing the variables to not exist yet in flash storage and thus causing them to not be found?
According to @simonmicro, errors are not related to the watch crashing, and this is simply insufficient power delivery causing the watch to crash as documented in https://open-smartwatch.github.io/resources/hardware/ under known problems.
What is not working?
Watch crashes when attempting to connect to WiFi.
How to reproduce this
With the watch connected to the PC, platform.io serial monitor running, following steps:
At this point, the watch appears to reset and dumps me back at the watchface. The platform.io serial monitor also crashes. The full log from the serial monitor after following these steps:
What should happen instead?
The WiFi to connect.
Environment
Additional context
Initial discussion in Discord: https://discord.com/channels/673521025593638932/701410676031225957/995727928635699200