-
Notifications
You must be signed in to change notification settings - Fork 13.3k
No Poison after the block Error in Smartconfig #3494
New issue
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
Comments
@me-no-dev need your help on this. |
I got this a few times, I also get wdt resets using 2.4.0
and release
|
I got this error message too. Could anyone help us? |
this error is probably caused due to corrupt flash memory. In order to completely format flash use following code. Hope it will solve your problem. |
@Khizer-Jan it did not solved the problem.
|
Well! it did for me. If you find any other solution ,kindly tell me about that. |
Smartconfig is delivered by Espressif as a binary blob from the SDK. There's nothing in our current code base which produces the error message quoted, so I would have to guess it's coming from inside that blob. Nothing for us to do here. |
我也遇到了这个问题,相同的代码使用linux可行,windows11不行 tart... Abort cal |
The umm_poison logic runs outside the UMM_CRITICAL_* umbrella. When interrupt routines do alloc calls, it is possible to interrupt an in-progress allocation just before the poison is set, with a new alloc request resulting in a false "poison check fail" against the in-progress allocation. The SDK does mallocs from ISRs. SmartConfig can illustrate this issue, see #3494 (comment) Other Sketches built with Debug: "Serial," that use the SDK's Promiscuous callbacks are also likely to encounter problems. The SDK support for "Promiscuous Receive" allocates memory from an ISR context, occasionally interrupting the poison wrapper code before it finishes setting the poison fences resulting in a false poison failed event.
The umm_poison logic runs outside the UMM_CRITICAL_* umbrella. When interrupt routines do alloc calls, it is possible to interrupt an in-progress allocation just before the poison is set, with a new alloc request resulting in a false "poison check fail" against the in-progress allocation. The SDK does mallocs from ISRs. SmartConfig can illustrate this issue, see esp8266#3494 (comment) Other Sketches built with Debug: "Serial," that use the SDK's Promiscuous callbacks are also likely to encounter problems. The SDK support for "Promiscuous Receive" allocates memory from an ISR context, occasionally interrupting the poison wrapper code before it finishes setting the poison fences resulting in a false poison failed event.
Basic Infos
Hardware
Hardware: ESP-12E
Core Version: 2.1.0-rc2
Description
Downloaded the latest Smartconfig SDK on iOS/android. The smartconfig works perfectly fine for the first few times. During the testing i was repeatedly trying the smartconfig even if it is connected to WIFI and the ESP got a crash with poison block error mentioned below after 4th or 5th attempt. It happens randomly. Is it not advisable to repeatedly use smartconfig even if the device is connected to WIFI ? or is there any workaround for this ?
Settings in IDE
Module: Generic ESP8266 Module
Flash Size: 4MB/1MB
CPU Frequency: 80Mhz
Flash Mode: qio
Flash Frequency: 40Mhz
Upload Using: SERIAL
Reset Method: ck
Sketch
Debug Messages
The text was updated successfully, but these errors were encountered: