blazoncek
commented
2 years ago @Aircoookie I am not seeing any resets no matter how fast I hit WLED with /json requests on my fork.
I have tried as fast as 10 reloads/s while simultaneously running a playlist with 600 LEDs attached and playlist switching presets every few seconds.
I did rewrite preset loading logic and optimized JSON buffer usage so that hardly anything serious happen in network callbacks (apart from ArduinoJson handling).
My build environment is:
[env:wemos_d1_mini32]
board = esp32dev
platform = espressif32@3.4.0
board_build.partitions = tools/WLED_ESP32_4MB_1MB_FS.csv
board_build.filesystem = littlefs
build_unflags = ${common.build_unflags}
build_flags = ${common.build_flags_esp32} -D WLED_RELEASE_NAME=ESP32
-D WLED_DISABLE_BLYNK
-D WLED_DISABLE_CRONIXIE
-D WLED_DISABLE_HUESYNC
-D WLED_DISABLE_LOXONE
-D USERMOD_DALLASTEMPERATURE
-D TEMPERATURE_PIN=23
-D LEDPIN=16
-D RLYPIN=19
-D BTNPIN=17
-D IRPIN=18
-D USERMOD_FOUR_LINE_DISPLAY
-D USE_ALT_DISPlAY
-D USERMOD_AUTO_SAVE
;-D USERMOD_ANIMATED_STAIRCASE
-D USERMOD_PIRSWITCH
-D PIR_SENSOR_PIN=26
-D USERMOD_MULTI_RELAY # 14, 15, 32
-D MULTI_RELAY_MAX_RELAYS=3
-UWLED_USE_MY_CONFIG
lib_deps = ${esp32.lib_deps}
U8g2@~2.28.8
paulstoffregen/OneWire@~2.3.6
Wire
[env:wemos_d1_mini32_debug]
extends = env:wemos_d1_mini32
build_flags = ${common.build_flags_esp32} -D WLED_RELEASE_NAME=ESP32
-D WLED_DEBUG
-D LEDPIN=16
-D RLYPIN=19
-D BTNPIN=17
-D IRPIN=18
-D USERMOD_DALLASTEMPERATURE
-D TEMPERATURE_PIN=23
-D USERMOD_FOUR_LINE_DISPLAY
-D USERMOD_ROTARY_ENCODER_UI
-D USE_ALT_DISPlAY
-D USERMOD_AUTO_SAVE
-D USERMOD_PIRSWITCH
-D PIR_SENSOR_PIN=36
-D USERMOD_MULTI_RELAY # 14, 15, 32
-D MULTI_RELAY_MAX_RELAYS=3
-D STATUSLED=-1
-D WLED_DISABLE_BROWNOUT_DET
-UWLED_USE_MY_CONFIG
Aircoookie
Jason2866
s-hadinger
Makuna
kroimon
Kyry11
fallspectrum
stale[bot]
softhack007
13bporter
What happened?
WLED frequently resets upon network requests (e.g. to
/jsonwhile loading main UI, applying presets...) while (SK6812) LEDs are on.To Reproduce Bug
Compile WLED with the custom IDF 4.4 + arduino 2.0.2 platform courtesy of Tasmota (this branch). The LITTLEFS library by lorol is replaced by the built-in LittleFS in the 2.x.x arduino core.
The reset reason is the low level RMT interrupts failing during a network request, although I don't yet understand the exact cause. Exception decoder trace below.
This has been reproduced on ESP32 and ESP32-S2 and the platforms:
Expected Behavior
No resets
Install Method
Self-Compiled
What version of WLED?
arduinocore2 branch
Which microcontroller/board are you seeing the problem on?
ESP32
Relevant log/trace output
Anything else?
@Jason2866 I suspect that this issue is due to a programming error on my end surfacing with the newer IDF/Arduino releases or possibly with the exchanged LittleFS library. Still, if you know what could be a likely cause, I'd be super happy to know as I see you did quite a few changes to sdkconfig (which I really like, as it drastically reduces binary size!)
My first guess was that the issue was due to
CONFIG_DISABLE_HAL_LOCKSbeing set in 2.0.2.1, however the issue is also present inhttps://github.com/tasmota/platform-espressif32/releases/download/v2.0.2/platform-tasmota-espressif32-2.0.2.zip, where that option was unset as far as I can tell.Code of Conduct