abort() was call at core 0 after Lopy 4 wake up after deep sleep
I have the newest firmware from pycom and this happen after enter and exit machine.deepsleep for a few times. Anyone have any similar problem ?
full output :
rst:0xc (SW_CPU_RESET),boot:0x12 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
mode:DIO, clock div:1
abort() was called at PC 0x400814cc on core 0
Backtrace: 0x4008f1a7:0x3ffe3c80 0x4008f1d8:0x3ffe3ca0 0x400814cc:0x3ffe3cc0 0x400a0548:0x3ffe3ce0 0x400a066d:0x3ffe3e70 0x40007c31:0x3ffe3eb0 0x4000073d:0x3ffe3f20
Backtrace: 0x4008e8cf:0x3ffe38c0 0x4008d7c9:0x3ffe38e0 0x4008f73b:0x3ffe3910 0x4008fa7a:0x3ffe3ae0 0x4008f434:0x3ffe3b20 0x4008f5c4:0x3ffe3ba0 0x4008349a:0x3ffe3bc0 0x4008f1a4:0x3ffe3c80 0x4008f1a4:0x3ffe3ca0 0x400814cc:0x3ffe3cc0 0x400a0548:0x3ffe3ce0 0x400a066d:0x3ffe3e70 0x40007c31:0x3ffe3eb0 0x4000073d:0x3ffe3f20
Re-entered core dump! Exception happened during core dump!
@Vinicius-Pinhatari-campos What version of the firmware are you using? How are you powering the LoPy4? Problems on boot are often related to a power source which can't provide enough current for the peaks which happen during boot or wake up.
have you fix it? same problem here