I have seen this before when users have not had enough power - too few mA from their power supply - to flash and use wifi at the same time (and the write still does not return an error). Now it is happening on devices that were fine before sdk v1.5.1 so I suspect that the new sdk is using more power than the old version.
To make it worse if you try to read the flash back to check the data is correct, it appears to come from the cache and so it looks fine (but if you use esptool.py to read the flash you can see it is bad). This means it is not possible to check the write worked at all!
Can you advise on how to fix this?
Instruction are in the readme.txt
I have tested the code with the new v1.5.2 sdk and the bug is still there. The flash write gets blocks of 0xff bytes (I assume these are erased, but not rewritten) in the middle of the file. This seems to happen on any sustained write, so I assume it will affect the sdk bootloader ota write just as much as as rBoot ota.
I wrote my own simpler test app to see if I can repro it with that. I can't so far. The key different being my test app isn't doing anything active with the network, so not drawing as much power.
Please have a try with the attachment based on ESP8266_NONOS_SDK_V1.5.2.
If your problem is still unsolved, please feel free to let us know.
- (58.02 KiB) Downloaded 300 times
Who is online
Users browsing this forum: No registered users and 3 guests
Newbies Start Here
Are you new to ESP8266?
Unsure what to do?
Dunno where to start?
Start right here!
We also have a RTOS version and a MESH version too!
Complete listing of the official ESP8266 related documentation release by ESPRESSIF!
Must read here!