WiFi LoRa 32 (V2) Interrupt wdt timeout on CPU1

[SteveMcAnena]

Hello,

We’ve purchased several WiFi LoRa 32 (v2) 433Mhz boards and have found the same issue on all boards.

Using the LoRaMultipleCommunications example (actually this issue occurs on most examples).

Following the onReceive(LoRa.parsePacket()); an error occurs randomly if the packetsize is >0…

Guru Meditation Error: Core 1 panic’ed (Interrupt wdt timeout on CPU1)
Core 1 register dump:
PC : 0x4008b05c PS : 0x00060e34 A0 : 0x8008a17f A1 : 0x3ffbe7f0
A2 : 0x3ffb8e3c A3 : 0x3ffb8074 A4 : 0x00000001 A5 : 0x00000001
A6 : 0x00060e23 A7 : 0x00000000 A8 : 0x3ffb8074 A9 : 0x3ffb8074
A10 : 0x00000018 A11 : 0x00000018 A12 : 0x00000001 A13 : 0x00000001
A14 : 0x00060e21 A15 : 0x00000000 SAR : 0x0000000e EXCCAUSE: 0x00000006
EXCVADDR: 0x00000000 LBEG : 0x4000c2e0 LEND : 0x4000c2f6 LCOUNT : 0x00000000
Core 1 was running in ISR context:
EPC1 : 0x40089612 EPC2 : 0x00000000 EPC3 : 0x00000000 EPC4 : 0x4008b05c

ELF file SHA256: 0000000000000000000000000000000000000000000000000000000000000000

Backtrace: 0x4008b05c:0x3ffbe7f0 0x4008a17c:0x3ffbe810 0x40088c2b:0x3ffbe830 0x400d5b5d:0x3ffbe870 0x400d414d:0x3ffbe890 0x400d3258:0x3ffbe8c0 0x400d3290:0x3ffbe8e0 0x400d3849:0x3ffbe900 0x400d38a2:0x3ffbe920 0x4008122d:0x3ffbe940 0x400820ed:0x3ffbe960 0x400d5bd8:0x3ffb1d20 0x400d414d:0x3ffb1d40 0x400d3258:0x3ffb1d70 0x400d3290:0x3ffb1d90 0x400d365c:0x3ffb1db0 0x400d2a89:0x3ffb1dd0 0x400d65e1:0x3ffb1fb0 0x40087f41:0x3ffb1fd0

Core 0 register dump:
PC : 0x40089612 PS : 0x00060034 A0 : 0x80089e24 A1 : 0x3ffbe2e0
A2 : 0x3ffbdd48 A3 : 0x0000cdcd A4 : 0xb33fffff A5 : 0x00000001
A6 : 0x00060021 A7 : 0x0000abab A8 : 0x0000abab A9 : 0x3ffbe2e0
A10 : 0x00000003 A11 : 0x00060023 A12 : 0x00060021 A13 : 0x00000001
A14 : 0x00060520 A15 : 0x00000000 SAR : 0x0000001b EXCCAUSE: 0x00000006
EXCVADDR: 0x00000000 LBEG : 0x00000000 LEND : 0x00000000 LCOUNT : 0x00000000

ELF file SHA256: 0000000000000000000000000000000000000000000000000000000000000000

Backtrace: 0x40089612:0x3ffbe2e0 0x40089e21:0x3ffbe310 0x4008802f:0x3ffbe330 0x4008ad29:0x3ffbe350 0x400820f6:0x3ffbe360 0x400eff73:0x3ffbc240 0x400da7f7:0x3ffbc260 0x40089dee:0x3ffbc280 0x40087f41:0x3ffbc2a0

Is there a known reason for this? and is there a fix in the libraries? I appear to have the latest installed…

Best Regards
Steve McAnena

[Supporter]

Did you mean the board on your hand rebooting all the time?

[coffee]

Hi, Any up date on this issue?

[Supporter]

You can refer to this documents:
https://docs.heltec.cn/#/en/faq/heltec_esp_series_common_problem_summary?id=system-reset-all-the-time

Byteduino hardware cosigner wallet crashing

Hi there According to the situation we have collected so far, the most likely to cause a constant reset problem may have two reasons: Power supply problem: please make sure the voltage of USB ≥ 4.7V, 300mA; You chose an error board: because each type of board may have a different FLASH size, and they have a different partition map, it will cause the internal logic error.

[Patsryk]

he board on your hand rebooting all the time?

I am having the same problem on interrupt based examples.

[sav59]

Try to use ESP32 Exeption Decoder
https://github.com/me-no-dev/EspExceptionDecoder
to find the error in the source code

[RicardoVR]

HI steveMcAnena

I faced the same problem…

I use HELTEC ESP32 LORA V2 868.
Board selected in arduino HELTEC WIFI LORA 32 (V2)

My firmware works fine, but same firmware one year later the esp32 start to reset in the interrupt.

the message in the terminal

Guru Meditation Error: Core 1 panic’ed (Interrupt wdt timeout on CPU1).

I checked the :
1.- Watch dog, it did not work
2.- Decrease the program inside the interrupt, it did not work.

Finally, the solution WAS…

Downgrade the Esp32 by expressive system library from 2.0.6 to 2.0.3 (in arduino IDE)

I hope it be useful
Bye