WLED icon indicating copy to clipboard operation
WLED copied to clipboard

ESP32 reboots (LoadProhibited)

Open RiverRaid opened this issue 1 year ago • 10 comments

What happened?

Hy! I have 2 ESP32, both with the newest WLED Version v.0.13.3 "Toki"

Both do a randomly reboot every 60 seconds to a few minutes. I did try also erase and new install => no change

To Reproduce Bug

Apply Power

Expected Behavior

No reboot

Install Method

Binary from WLED.me

What version of WLED?

v.0.13.3 "Toki"

Which microcontroller/board are you seeing the problem on?

ESP32

Relevant log/trace output

Guru Meditation Error: Core  0 panic'ed (LoadProhibited). Exception was unhandled.
Core 0 register dump:
PC      : 0x40158db4  PS      : 0x00060530  A0      : 0x8015979a  A1      : 0x3ffd70b0  
A2      : 0x00000000  A3      : 0x00000010  A4      : 0x000000cb  A5      : 0x3ffdd390  
A6      : 0x3ffddb51  A7      : 0x3ffddc1c  A8      : 0x801588ce  A9      : 0x3ffd7090  
A10     : 0x00000001  A11     : 0x3ffddb51  A12     : 0x000000cb  A13     : 0x00000001  
A14     : 0x00060123  A15     : 0x00000010  SAR     : 0x00000010  EXCCAUSE: 0x0000001c  
EXCVADDR: 0x00000004  LBEG    : 0x4000c349  LEND    : 0x4000c36b  LCOUNT  : 0x00000000  

ELF file SHA256: 0000000000000000

Backtrace: 0x40158db1:0x3ffd70b0 0x40159797:0x3ffd7130 0x401597f7:0x3ffd7160 0x4008b506:0x3ffd7190

Rebooting...
ets Jun  8 2016 00:22:57

rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DOUT, clock div:2
load:0x3fff0018,len:4
load:0x3fff001c,len:1044
load:0x40078000,len:10124
load:0x40080400,len:5828
entry 0x400806a8
Ada

Anything else?

No response

Code of Conduct

  • [X] I agree to follow this project's Code of Conduct

RiverRaid avatar Sep 06 '22 08:09 RiverRaid

are you by chance using an ESP32 module with both WiFi and ethernet? i got those messages in both 0.13.1 and 0.13.3 if i had both wifi and ethernet enabled. I after a reset I only configured/turned one of the other its would be fine.

briodan avatar Sep 06 '22 14:09 briodan

are you by chance using an ESP32 module with both WiFi and ethernet? i got those messages in both 0.13.1 and 0.13.3 if i had both wifi and ethernet enabled. I after a reset I only configured/turned one of the other its would be fine.

Sorry no, just WiFI

This one are the ones i bought: https://www.amazon.de/gp/product/B08BZGC22Q/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1

RiverRaid avatar Sep 06 '22 17:09 RiverRaid

I bought a new ESP32 from another manufacturer https://www.amazon.de/gp/product/B07VJ34N2Q/ref=ppx_yo_dt_b_asin_title_o02_s00?ie=UTF8&psc=1

Exactly the same issue

Edit I tried this ones as well: https://www.amazon.de/gp/product/B08BTLYSTM/ref=ppx_yo_dt_b_asin_title_o03_s00?ie=UTF8&psc=1

On ESP8266 (Wemos D1 Mini) no reboots

They also keep rebooting

RiverRaid avatar Sep 07 '22 13:09 RiverRaid

might help if you erase the chip first, then re-install a WLED bootloader, then re-install WLED. Sometime the bootloader installed by the device manufacturers does crazy things and then crashes, or the 'stock' FLASH partition table is not compatible with WLED so you need to erase it and start fresh.

  • esptool.py erase_flash
  • esptool.py write_flash 0x0 ./esp32_bootloader_v4.bin
  • esptool.py write_flash 0x10000 ./WLED__XXX_.bin

https://kno.wled.ge/basics/install-binary --> Flashing method 2: esptool

softhack007 avatar Sep 07 '22 14:09 softhack007

might help if you erase the chip first, Hi,

of ourse i tried this already several times :)

RiverRaid avatar Sep 07 '22 16:09 RiverRaid

The error above usually means null pointer. As a lot of testing has been done that would possibly mean unusual set-up. Please post your cfg.json and, if applicable, preset in question.

blazoncek avatar Sep 07 '22 17:09 blazoncek

@blazoncek Thank you for your reply! I have attached the cfg json as zip

Thank yoU! cfg.zip

RiverRaid avatar Sep 07 '22 19:09 RiverRaid

nothing unusual. almost same as my test set-up.

blazoncek avatar Sep 07 '22 20:09 blazoncek

Ok, I did further testing and found the following:

As long, as the esp32 with wled is not connected to my WiFi, it works like a charm. As soon, as its connected, the reboots occur every 60 seconds.

I created a second SSID and PWD for WLED, proplem persists.

So I guess, there is something in my network that causes this... the funny thing, all esp8266 work without any Problems, it is strictly only on the esp32 (different vendors)

My Network consists of a FritzBox 7490 (not changeable, issued by my Provider) and UniFi APs.

Is there any way for me to find out what causes the Problems? I would really like to change from the esp8266 to esp32...

Thanks :)

Edit: I orderer complete new ESP32, did the flash via ESptool from a different Laptop which was never used foe WLED before. I did no Inputs/changes whatsoever, everything works without any problems. As soon as I connect it to my network, the reboots begin. So it has to be that the ESP32 receives something it doesnt like and starts rebooting.

Any idea how i could further investigate this?

RiverRaid avatar Sep 17 '22 13:09 RiverRaid

Use debug build and monitor serial output. If you have any "smart" devices on your network try disconnecting them. HA was known to cause issues in certain configurations.

blazoncek avatar Sep 21 '22 19:09 blazoncek

Any progress?

blazoncek avatar Nov 01 '22 07:11 blazoncek

No, for the time no progress :( I changed to Wemos D1 and will try again in a few months

RiverRaid avatar Nov 07 '22 21:11 RiverRaid

Then I am going to close this issue. If the problem persists in 0.14 (when it is released) open a new issue.

blazoncek avatar Nov 08 '22 06:11 blazoncek

I do have the same issue. I am having two of these: https://shop.codm.de/automation/pixel/30/wlan-pixel-controller-wled And both have this issue. Either separate or at the same time, both have the issue (reboot every 60 seconds) It is notable, that they first worked fine. I don't really know what caused this behaviour because I do not remember any change recently. I have the current beta release installed.

DeepflashX avatar Apr 01 '23 16:04 DeepflashX

Please attach crash dumps from debug build of WLED. Please use WLED forum or Discord for help and support questions.

blazoncek avatar Apr 02 '23 05:04 blazoncek

And where do I find that debug build?

Am So., 2. Apr. 2023 um 07:22 Uhr schrieb Blaž Kristan < @.***>:

Please attach crash dumps from debug build of WLED. Please use WLED forum https://wled.discourse.group or Discord for help and support questions.

— Reply to this email directly, view it on GitHub https://github.com/Aircoookie/WLED/issues/2774#issuecomment-1493227203, or unsubscribe https://github.com/notifications/unsubscribe-auth/A4BGEXTJ2JSSU5IHZR2WAO3W7EEKBANCNFSM6AAAAAAQFTHACE . You are receiving this because you commented.Message ID: @.***>

DeepflashX avatar Apr 03 '23 08:04 DeepflashX

Please use WLED forum or Discord for help and support questions.

blazoncek avatar Apr 03 '23 09:04 blazoncek

Just referencing #2932 as the problem still persists.

@DeepflashX the problem is - as far as we know - since Fritz!OS 7.50 and only when using AVM Repeaters with mesh. Please correct me if I'm wrong.

@RiverRaid can not reproduce with Fritz 6590 and UniFi-AP's, AVM Wifi off. Neither with 0.13.3 nor 0.14b.

codmpm avatar Oct 04 '23 13:10 codmpm