ESP-01 (1MB) flashing problems #650
Comments
|
For another issue-thread I created these test builds yesterday: https://www.dropbox.com/s/tr2w99jw6hfgdph/ESPeasy_issue640_test_20171220.rar?dl=0 |
|
thanks for sharing the build, tried that, but same issue, please see following output ets Jan 8 2013,rst cause:2, boot mode:(3,1) load 0x4010f000, len 1384, room 16 INIT : Booting version: ets Jan 8 2013,rst cause:2, boot mode:(3,1) load 0x4010f000, len 1384, room 16 INIT : Booting version: |
|
Just to verify it is not a broken ESP device, can you also test another version, like the 'old' v120: http://www.letscontrolit.com/downloads/ESPEasy_R120.zip It kind of looks like you cannot write to parts of the flash. Edit: |
|
I have tried flashing "ESPEasy_R120_1024" and it works, however, the tasks do not function correctly, for example, I am unable to read DHT-11. I have also tried flashing sketches that perform various functions (DHT, MQTT etc) and they appear to be working normally, however when I flash any recent version of easyesp (ESPEasy_R147_RC8 and upwards) I run into the same restart issues. I'm certain it's a 1MB version (the table mentions below with ** that amount of flash size may vary with board models), I have verified the same using esptool, output follows flash_id outputesptool.py v2.2 chip_id outputesptool.py v2.2 |
|
which .bin file of 2.0.0-dev12 did you flash? |
|
Hi, The working ESP-01 report as flash_id: and the new ones that are not working: Any idea how to get the new one working ? |
|
Apparently, that is the GIGADEVICE_GD25LQ80 flash chip. (taken from here: https://code.coreboot.org/p/flashrom/source/tree/HEAD/trunk/flashchips.h ) |
|
ESP core 2.4.0 also cannot handle this chip yet. I also created an issue for that. Maybe we can only wait for them to analyze and support this new flash. |
|
Can anyone with this problem try to burn with DOUT mode (https://github.com/espressif/esptool/wiki/SPI-Flash-Modes)? |
|
Hi Pablo, |
|
Still does not work. Also not with DOUT. But to have this clear: everything is working fine. The firmware runs but only SPIFFS is not working with the news flash |
|
So making changes to the settings is not possible? |
|
How are you actually supposed to get it working for the first time. As far as I understood ESPEasy, you have to flash it and when you do the initial configuration, the firmware has to write to the flash, right? Also in the meantime, it looks like it's hard to predict which chip you will get when you buy a ESP-01 from an online show. Does anyone have a suggestion where I can buy the old modules? |
|
But ESPEasy_R147_1024.bin works fine. |
|
hi, r147, r148 ok, but above them nothing is working properly, ets Jan 8 2013,rst cause:2, boot mode:(3,6) load 0x4010f000, len 1384, room 16 INIT : Booting version: v2.0.0-dev12 PID:0 Exception (0): ctx: cont
|
psy0rz
added
Type: Bug
|
strange..normally a reset should format the SPIFFS and everything should be fine. From the logs above: Those errors while writing are the cause of all the problems: If that steps fails, your ESPEasy is unusable. It kinda works but it cannot save files. I think there where other issues with the same problems? Didn't it have to do with the flash-mode of the flash tool or something? |
|
|
Could it be that those other versions (Tasmota, Espurna, ESPeasy R148) have a sketch size < 512 kB? |
|
I think so, since mega was especially for >=1M devices only. if that is the problem in this case, we might need to build in a extra flash-size check that warns and stops the boot process? |
|
It looks like it is a 1 MB flash. But if I remember correctly, the ESP8266EX will load up to 1 MB into memory, which means the sketch may never be more than 1 MB. |
|
can anyone build a testversion wich is alittle bit smaller to test with this devices? working: not working: maybe thats the solution? |
|
I think we can disable the OLED framed module? That one is quite big with its font embedded. |
|
Good Idea; Let's try; I can't compile it myself yet; can anybody do it? |
|
@HarryHase11 so your module only has 512kb flash? |
|
i bought it with 1MB, but not sure what wrong; and that problem some other user have the same issue. http://fs1.directupload.net/images/180110/4uq4edt6.jpg P25Q80H |
|
ah k thx |
|
found some hints in the internet that this flash chip have only 512KB size. |
|
Hi @TD-er. This is why I asked for people who don't have PUYA chipped module to comment in #748. All the back and forth with long posts that get nowhere just makes the thread hard to follow and so long most people just wouldn't bother to make sense of it. I am absolutely dumbfounded by the lack of urgency shown by the supposed gurus in the 8266 community in relation to this issue. This issue was raised 3 weeks ago that I know of maybe more. I warned that it was going to quickly become widespread 2 weeks ago. There are now at least 4 current threads on this issue. And still nothing concrete has been done. I know you're trying to help, but no-one's suggestions have been helpful to date. Even @igrr got me to try a number of modified esp.cpp's to nail it down, but all to no avail. And now, he's just left me hanging as if he's just put it in the too hard basket. If he can't find the problem without a PUYA chipped module in hand I seriously doubt that anyone can. This isn't a minor issue and it's going to spread exponentially as these PUYA chips are being used by a growing number of manufacturers and I can't see it being restricted to the esp-01 module for long. Someone who knows what they're doing needs get one of these modules urgently so this issue can be resolved as quickly as possible. |
|
That's why I want to get my hands on them. |
|
I got mine from the following link Delivered in 3 weeks |
|
@TD-er, this is where I bought one of the batches(20) from and they all had the PUYA flash chip. If you want to receive them more quickly you must choose 'ePacket' from the drop down list of postage options. |
|
I will send TD-er one of this esp-01 at the weekend, maybe he can solve this puya problem |
|
any news? |
|
Yep, there is a solution, but we still have to build it. The problem is in the Arduino ESP8266 core library. The problem is the implementation of SPIFFS which does rely on a very typical property of flash memory. So the SPIFFS implementation relies on this by not erasing, but just writing to the flash. But with the PUYA chips, the byte written is actually stored the same way as it is offered to the flash memory. Adding a small piece of code to the write flash function, should be enough to fix all SPIFFS issues. Thing is, you don't want this on other chips. So it is not a general solution, so we have to split it into several builds, one specific for PUYA chips. @psy0rz is looking into building the core lib to be used with PUYA builds. |
|
i just tested this on my PUYA chips: writing now seems slow as hell? or is it always slower on ESP01s chips? trying to get it to build via travis now, so hopefully we'll have a extra PUYA binary in the next nightly. |
|
ok its building, i'm going to sleep, with some luck both nightly builds will now have a dev_ESP8266PUYA_1024 version. keep in mind its slow and wears your flash fast. there is still hope the upstream guys figure out a way to reconfigure the chip so it behaves normally. |
|
Have got my own PUYA :)
|
|
is there a binary downoad avaible for testing? |
|
Yep, but there were some reports of non functional Advanced view. |
|
I have an ESP01 with a Puya IC, and I've tried to upload the latest I don't remember it if was on the mega or v2.0. branches (.. well... #997), but it has totally failed : The boot log loops after failing to do something certainly related to the SPIFF partition. I've always flash_erase using esptool.py before flashing the firmware, but it always ends up crashing after some ESPEASY boot logs , and keeps rebooting. Is there anything else i should take care of, or is my board simply fried (totally credible) ? I'm gonna receive new (certainly PUYA equipped) ESP01 modules from AliExpress, but it takes time, and for sure I will report further success or not. |
|
@soif try my patch v2 for puya, it will detect if flash is puya and use workaround if necessary. |
|
here: esp8266/Arduino#4061 |
|
Well OK, understood. But i'm currently on the 2.4 version and patching pio components is not something I want to experiment/maintain until it is officially merged. Hence MANY thanks for your efforts 🎉 I now quess that I just have to wait for a potentially fast merge into the Espressif-arduino framework, for the PUYA IC to be supported. I'm pretty sure that they will merge it ASAP: |
|
I just see noone it testing it there. |
|
i'm quite new to the ESP and ESPeasy, could someone help me choosing a flash chip to change the PUYA ones with? i had a Microchip 25PF020B80-4C-S and a SST 25VF040B at hand but both seem to not work with the ESP. i'd especially appreciate hints as to make & model and where to buy in germany ;) thanks =) |
|
find w25q32 :) |
|
From the ESP-easy site: At this time ESP-01S are sold with a flash chip marked "PUYA". These flash chips have a problem with using SPIFFS memory and do not work with ESP Easy. The problem is under investigation. At this time there is no given solution besides using other ESP-01 if available or changing the flash chip on the ESP-01S. UPDATE: A fix seems to be on the horizon. Stay tuned! When to expect the new firmware for the ESP-01s boards? Regards, Bram |
|
It is available in mega/v2 releases. |
|
Thanks, which one should I use, the PUYA_1024.bin or the PUYA_1024_VCC.bin? |
|
PUYA_1024, when you don't use analog-input or use analog from external |
|
Hello, I struggled some hours around with an ESP-07 board with 1M... with the PUYA-Version from 20180714 it worked at least to boot. Now I will start testing :). greets Christian |
Steps to reproduce
Flash a fresh esp-01 module (black) with any 1MB bin
Does the problem presist after powering off and on? (just resetting isnt enough sometimes)
yes
Expected behavior
Tell us what should happen?
Should start normally
Actual behavior
Tell us what happens instead?
board keeps resetting and complaining about the same problem. I have tried flashing with different baud rates and modes, but nothing works. The same firmware works great on wemos d1r2.
System configuration
Hardware:ESP-01 1MB version
Software or git version: v2.0.0-dev12
here''s the output from the serial interface
RESET: Warm boot, reset count: 1
RESET: formatting...
RESET: formatting done...
FS : Error while reading/writing config.dat in 878
FS : Error while reading/writing security.dat in 878
FS : Error while reading/writing notification.dat in 878
FS : Error while reading/writing config.dat in 922
FS : Error while reading/writing config.dat in 895
RESET: Succesful, rebooting. (you might need to press the reset button if you've justed flashed the firmware)
ets Jan 8 2013,rst cause:2, boot mode:(3,2)
load 0x4010f000, len 1384, room 16
tail 8
chksum 0x2d
csum 0x2d
v09826c6d
~ld
⸮U
INIT : Booting version: v2.0.0-dev12
INIT : Warm boot #2
FS : Mounting...
FS : Mount successful, used 1255 bytes of 113201
RESET: Resetting factory defaults...
RESET: Warm boot, reset count: 2
RESET: formatting...
RESET: formatting done...
FS : Error while reading/writing config.dat in 878
FS : Error while reading/writing security.dat in 878
FS : Error while reading/writing notification.dat in 878
FS : Error while reading/writing config.dat in 922
FS : Error while reading/writing config.dat in 895
RESET: Succesful, rebooting. (you might need to press the reset button if you've justed flashed the firmware)
ets Jan 8 2013,rst cause:2, boot mode:(3,2)
load 0x4010f000, len 1384, room 16
tail 8
chksum 0x2d
csum 0x2d
v09826c6d
~ld
⸮U
INIT : Booting version: v2.0.0-dev12
INIT : Warm boot #3
FS : Mounting...
FS : Mount successful, used 1255 bytes of 113201
RESET: Resetting factory defaults...
RESET: Warm boot, reset count: 3
RESET: Too many resets, protecting your flash memory (powercycle to solve this)
FS : Error while reading/writing config.dat in 922
PID:0
Version:0
INIT : Incorrect PID or version!
RESET: Resetting factory defaults...
RESET: Warm boot, reset count: 3
RESET: Too many resets, protecting your flash memory (powercycle to solve this)
Exception (0):
epc1=0x40106f19 epc2=0x00000000 epc3=0x00000000 excvaddr=0x00000000 depc=0x00000000
ctx: cont
sp: 3fff3500 end: 3fff3770 offset: 01a0
The text was updated successfully, but these errors were encountered: