We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
esp32 wroom
mp 1.22.2
At the moment, I cannot reproduce the fault.
program running
I have a complex application, developed over months and tested on esp8266, esp32 and rp2.
Today for the first time on a esp32 wroom board I get this error:
Guru Meditation Error: Core 1 panic'ed (LoadStoreError). Exception was unhandled. Core 1 register dump: PC : 0x400a93df PS : 0x00060230 A0 : 0x800df1aa A1 : 0x3ffce510 A2 : 0x3ffda370 A3 : 0x00000007 A4 : 0x3ffe4c00 A5 : 0x3ffd5cb0 A6 : 0x3ffd8d70 A7 : 0x3f418cbc A8 : 0x800a945e A9 : 0x3ffce4e0 A10 : 0x40000000 A11 : 0x0001b400 A12 : 0x000000ef A13 : 0xfffffffa A14 : 0x00000004 A15 : 0x3ffd9920 SAR : 0x00000008 EXCCAUSE: 0x00000003 EXCVADDR: 0x40000000 LBEG : 0x400e40d5 LEND : 0x400e40dd LCOUNT : 0x00000000 Backtrace: 0x400a93dc:0x3ffce510 |<-CORRUPTED ELF file SHA256: 51aa7525e37c5ea9 Rebooting... ets Jul 29 2019 12:21:46 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:DIO, clock div:2 load:0x3fff0030,len:4728 load:0x40078000,len:14888 load:0x40080400,len:3368 entry 0x400805cc
Guru Meditation Error: Core 1 panic'ed (LoadStoreError). Exception was unhandled.
Core 1 register dump: PC : 0x400a93df PS : 0x00060230 A0 : 0x800df1aa A1 : 0x3ffce510 A2 : 0x3ffda370 A3 : 0x00000007 A4 : 0x3ffe4c00 A5 : 0x3ffd5cb0 A6 : 0x3ffd8d70 A7 : 0x3f418cbc A8 : 0x800a945e A9 : 0x3ffce4e0 A10 : 0x40000000 A11 : 0x0001b400 A12 : 0x000000ef A13 : 0xfffffffa A14 : 0x00000004 A15 : 0x3ffd9920 SAR : 0x00000008 EXCCAUSE: 0x00000003 EXCVADDR: 0x40000000 LBEG : 0x400e40d5 LEND : 0x400e40dd LCOUNT : 0x00000000
Backtrace: 0x400a93dc:0x3ffce510 |<-CORRUPTED
ELF file SHA256: 51aa7525e37c5ea9
Rebooting... ets Jul 29 2019 12:21:46
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:DIO, clock div:2 load:0x3fff0030,len:4728 load:0x40078000,len:14888 load:0x40080400,len:3368 entry 0x400805cc
The last action: a tcp client connecting to a tcp socket listening on the esp32.
I cannot say if the client connecting to the esp32 was the cause of the fault, or just a coincidence.
From the provided "guru meditation" dump, is it possible to grok something?
No, I've provided everything above.
Yes, I agree
The text was updated successfully, but these errors were encountered:
I apologize. The cause is a buffer overflow in a viper function.
Sorry, something went wrong.
No branches or pull requests
Port, board and/or hardware
esp32 wroom
MicroPython version
mp 1.22.2
Reproduction
At the moment, I cannot reproduce the fault.
Expected behaviour
program running
Observed behaviour
I have a complex application, developed over months and tested on esp8266, esp32 and rp2.
Today for the first time on a esp32 wroom board I get this error:
The last action: a tcp client connecting to a tcp socket listening on the esp32.
I cannot say if the client connecting to the esp32 was the cause of the fault, or just a coincidence.
From the provided "guru meditation" dump, is it possible to grok something?
Additional Information
No, I've provided everything above.
Code of Conduct
Yes, I agree
The text was updated successfully, but these errors were encountered: