ESP8266 Exception 28 (Adafruit Feather Huzzah) #34
Comments
|
I completely removed the entire WLED00 folder from my Arduino directory and re-extracted from the latest download. Placed everything back into place to confirm a fresh start, and the unit still crashes when trying to launch AP now with the same exact issue. This is after performing an esptool erase_flash command to ensure the entire unit was purged of all settings. |
|
Hi, awesome that you like my project! Would you mind trying the latest 0.7.0 version? The 0.5 in the bin-folder is no longer up to date, I use the releases page now: https://github.com/Aircoookie/WLED/releases . That said, even the old builds shouldn't insta-crash. If you experience the exception with the recent build also, I can help find the error. This might be linked to #11 , maybe. Once you get it up and running, there is an option to switch to RGBW mode in the LED settings, so don't worry, this issue is not related to your strip type. Thanks for your support! |
|
Thanks for the very prompt response! I have also tried building 0.7.0 myself, and installing the prebuilt binary. No luck. I WAS able to get 0.6.3 up and running without issue, and currently have it cycling in the home office right now. |
|
That is indeed very weird. I was not expecting 0.6.3 to work when 0.7.0 doesn't. I've just checked again and 0.7.0 works fine when compiling with DEBUG enabled for Adafruit Huzzah (compile settings: 80MHz, 4M (3M SPIFFS), baud 115200). Changing the WiFi credentials in the code should technically work, but how it's supposed to be is that you flash the sketch as-is. Then it will open the access point WLED-AP with password wled1234. You connect to that (IP 192.168.4.1) and then in the web interface, you put in the data for your home wifi! If you can send me the exception stacktrace for 0.7.0, i can work out where the issue is for you. For now, I'm happy for you that 0.6.3 seems to work :) Edit: for my exception decoder thing to work, we need exactly the same source. Let's say we enable debug, and for testing, you set the clientSSID and clientPass strings back to the default. |
|
I need to figure out how to pull the exception stacktrace for you. lol Any instructions? I'm a hardware guy, this code stuff is over my head. All WLED00 sketch settings are direct from github, fully reset at this time to defaults, including the SSID information within the sketch. |
|
No worries, it's just this exception stuff the ESP prints out to serial when crashing, like you pasted into your first comment. |
|
I'm home now and have a brand new Feather Huzzah sitting in front of me. I have it flashed to 0.6.3, and I have the 0.7.0 BIN on the system. I can update the unit to 0.7.0 using the BIN, or I can flash the 0.7.0 latest build directly from Arduino. What would you like me to do? |
|
Both should do the same thing. Try the BIN first. I'm personally using a modified version of Neopixelbus (https://github.com/svenihoney/NeoPixelBus) to compile the bins, but i also always test if it works with the current official versions. Do you know which version of ESP8266 arduino core you use? No worries if you don't know it. I just want you to be aware that i still develop for 2.3.0 since the sketch sizes with that version are smaller and it allows me to continue support the low-end ESP-01 that only has 512K storage. |
|
I'm also using 2.3.0, per the note you had put in the readme. I just updated the brand new test unit with 0.7.0 using the BIN. After the "Success" and reboot, it goes into the boot loop with Exception 28. I performed a flash erase with esptool, reflashed with the updater, then uploaded 0.6.3 and it came right back up and works as normal. Connected to my PC, performed a stock (no changes whatsoever) flash to 0.7.0 from the Arduino IDE and ran into the same issue as the BIN upgrade. It crashes and boot loops. |
|
That both really sucks and is quite strange, since we are both using the exact same software and probably the same hardware (only the flash amount and maybe pinout is different on various versions of the 8266). Can you give me the serial port exception 28 stacktrace for the 0.7.0 BIN like that in your first post? Without it I can't help with the problem since I can't reproduce it myself, unfortunately. Exception (28): ctx: cont stack>>> ets Jan 8 2013,rst cause:2, boot mode:(3,6) load 0x4010f000, len 1384, room 16 Exception 28 means the program is trying to load a piece of memory it has no access to, which is likely a programming error on my behalf that somehow doesn't surface with my hardware. Thanks for sticking with me :) |
|
It is I who should be thanking you... Rather than say "Go buy this exact hardware module cause I know it works", you are instead helping me out. That is very refreshing to see, and greatly appreciated! Here's the results from the Serial Monitor. ets Jan 8 2013,rst cause:2, boot mode:(3,6) load 0x4010f000, len 1384, room 16 Exception (28): ctx: cont
ets Jan 8 2013,rst cause:2, boot mode:(3,6) load 0x4010f000, len 1384, room 16 |
|
Thank you for the kind words :) I've changed some other things that might cause the exception in some recent development. You can try if the development version fixes it for you. If the dev version doesn't work, you can try the following:
If 0.7.0 then works, we have confirmed that the issue is with mDNS. However I'm happy that 0.6.3 works for you :) |
|
Ok, don't bother with the dev version! I was just able to reproduce the issue! I really need to extend my testing upon releasing versions, 0.7.0 works great when you are connected to a home wifi in 0.6 and updating to 0.7.0, but not when you do a fresh install of 0.7 or not connected to wifi. Dev version doesn't work either. Working on a fix :) |
|
So the Dev version does not work for me. Same issue as before. Something interesting I just discovered... I have several ESP units (All Adafruit Feather Huzzah) around the house with Pixels attached. I've updated several to 0.6.4 and they're working fine, except that using the web interface from one, controls the others. Hitting the power button to turn one off from it's own interface results in the others also turning off... That should be a bug report in and of itself. Attempting to update the unit to 0.7 after setting up the WiFi connection results in a page not found error and then the unit becomes non-responsive until many minutes after a reboot. Once it comes back up, I try the update again via the web interface (manual OTA update), and it goes non-responsive again. This may be related to the whole "all devices controlled by one" thing. |
|
Thanks for the report! I believe I have found the fix for the Exception 28 issue. In a few minutes I will push it to the dev branch and later today also finally release 0.7.1 which will address the issue. |
|
Ah HAH! I don't think I knew what the arrows meant in relation to multiple units. I'll test the dev branch out once you update it and confirm it is resolved on this end before you make the 0.7.1 push. :) |
|
Awesome! The dev branch is now updated with the fix! |
|
Dat Mobile UI... The unit boots without the boot loop or crash, and I am now able to successfully install and configure it. Thank you for such a prompt response and fix! |
…_Repair_Bad_Optimization "Unfixing" an optimization to the Art-Net header. The local "buffer" was shadowing the LED buffer (function parameter), so art-net would only send out headers but no LEDs.
What a great project! I'm coming over from the McLighting V2 project, trying to find something I can use standalone without relying on a WiFi signal (for our tent lights when camping), and discovered WLED00...
I'm running into an issue though. I'm using RGBW WS2812b LED strips. When flashing the OTA Updater sketch first, then uploading the pre-built 0.5 BIN, the units work beautifully, except for the coloring on the strips. The 0.5 image does not seem to support RGBW, or at least I can't find a way to specify the LED strip in the documentation or the sketch...
When I build the sketch myself, I leave everything as default except the SSID/PW for my home wireless (for my test units here), and enabling the serial debug.
I receive a constant Exception 28 reboot within half a second of the unit connecting to my wireless here at home.
`v3de0c112
~ld
Load EEPROM
CSSID: Den of SynUSING AP7
C_NC
C_NC
C_NC
C_NC
C_NC
C_NC
C_NC
C_NC
C_NC
C_NC
C_NC
C_NC
C_NC
C_NC
C_NC
Connected! IP address: 192.168.1.146
Exception (28):
epc1=0x4000bf80 epc2=0x00000000 epc3=0x00000000 excvaddr=0x0104a8c0 depc=0x00000000
ctx: cont
sp: 3fff3850 end: 3fff3ad0 offset: 01a0
ets Jan 8 2013,rst cause:2, boot mode:(3,6)
load 0x4010f000, len 1384, room 16
tail 8
chksum 0x2d
csum 0x2d
v3de0c112
~ld
Load EEPROM
CSSID: Den of SynUSING AP7
`
The text was updated successfully, but these errors were encountered: