logo elektroda
logo elektroda
X
logo elektroda

ESP8266-01 firmware update but no response to connection

kamarol1 1761 27
ADVERTISEMENT
Treść została przetłumaczona polish » english Zobacz oryginalną wersję tematu
  • #1 17659136
    kamarol1
    Level 7  
    Hello, The firmware updates, screenshot attached), however when trying to connect the chip does not respond. I've tried changing the switch setting, but it doesn't do anything. Maybe some of you have used an adapter like me and know how to solve the problem?
    ESP8266-01 firmware update but no response to connection ESP8266-01 firmware update but no response to connection ESP8266-01 firmware update but no response to connection ESP8266-01 firmware update but no response to connection .

    ESP8266-01 firmware update but no response to connection .

    ESP8266-01 firmware update but no response to connection .

    ESP8266-01 firmware update but no response to connection .
  • ADVERTISEMENT
  • #2 17659243
    khoam
    Level 42  
    kamarol1 wrote:
    while when trying to connect, the chip does not respond.
    .
    And what specific code were you uploading, or trying to upload to esp, for this to work with the Serial Monitor in the Arduino IDE?
    If you simply loaded AT firmware, then you have the esp in the role of a WiFi modem, which you can control over RX/TX.
  • #3 17659261
    kamarol1
    Level 7  
    I loaded something like this: ESP8266 v0.9.5.0 AT Firmware.bin (attachment).
    In ESPlorer I have something like the picture. ESP8266-01 firmware update but no response to connection .

    Namely, this light should be green and has red, which I perceived as no connection. Later on the internet I searched for information that you can also connect to the ESP using the Arduino IDE (Electroconductor) which I did, but after typing 'AT' nothing pops up for me, which I guess it should.

    Forgive me if the questions are trivial, but this is the first time I've had an ESP8266 in my hands ;) .
  • #4 17659270
    khoam
    Level 42  
    kamarol1 wrote:
    Later on the internet I searched for information that it is also possible to connect to the ESP using the Arduino IDE (Electric Guide)
    .
    You can test the esp this way, but the default baud rate (after loading the new AT firmware). is 115,200, not 9,600.

    Added after 4 [minutes]:

    kamarol1 wrote:
    I uploaded something like this: ESP8266 v0.9.5.0 AT
    .
    This is a very old version of the firmware. Load yourself version 1.6.2 from here (but not higher).

    Added after 4 [minutes]: .

    kamarol1 wrote:
    Would you describe so more exactly what I need to do to make it work?
    .
    You are very welcome to:
    1. download and load version 1.6.2 of the AT firmware. I have already given you the link.
    2. When you open Serial Monitor in the Arduino IDE, set the speed to 115 200 (bottom right corner of the window).
  • ADVERTISEMENT
  • #5 17659289
    kamarol1
    Level 7  
    Would you still write which file I should upload?
    ESP8266-01 firmware update but no response to connection
  • #6 17659298
    simw
    Level 27  
    The default transmission for ESP8266s, such as those from ali, is 115200, and in your case I see 9600 when uploading as well as trying to read. This way you are probably fuzzing the firmware and that's why it doesn't work.
  • #7 17659299
    khoam
    Level 42  
    kamarol1 wrote:
    Would you still like to tell me which file I should upload?
    I would like to know.

    0x00000 boot_v1.7.bin
    0x01000 user1.1024.new.2.bin (from folder "at")
    0xfc000 esp_init_data_default_v08.bin
    0x7e000 blank.bin
    0xfe000 blank.bin

    Added after 2 [minutes]: .

    simw wrote:
    This way you probably mess up the firmware and that's why it doesn't work.

    Nothing can be "blurred" in this way.
  • #8 17659314
    simw
    Level 27  
    khoam wrote:
    Nothing can be "blurred" that way.

    If it gives "bushes" when transmitting badly it will not be saved?
  • ADVERTISEMENT
  • #9 17659321
    khoam
    Level 42  
    simw wrote:
    If, with a bad transmission, it gives "bushes" it will not be saved?
    .
    At the moment there is no connection to esp at all after RX/TX since esp does not respond to AT commands.
    The firmware update tool that the author used to upload the firmware sets itself an arbitrary speed during boot, but only for the duration of the firmware upload. After a reset, the esp gets up at the default speed stored in the flash, in this case probably 115,200.
  • #10 17659331
    simw
    Level 27  
    khoam wrote:
    simw wrote:
    If, with a bad transmission, it gives "bushes" then they will not be saved?
    .
    At the moment there is no connection at all with the esp after RX/TX since the esp is not responding to AT commands.

    The author of the thread wrote that it "updates" but when trying to connect the circuit does not work.
    As for me, he "uploaded bushes" after 9600 and the module doesn't start for him, that's why there is no connection via AT commands afterwards.

    In my opinion, he should upload again, preferably firmware 2.2.1 using flash tool downloader version V3.6.4, setting the jumper appropriately - and not on a "hunch".
    I have a similar programmer, except that I "made up" the jumper because it had no upload option.
  • #11 17659337
    khoam
    Level 42  
    simw wrote:
    The author of the thread wrote that it "updates" but when trying to connect the circuit does not work.
    .
    I've factualised my statement a post above and will repeat it:

    The firmware update tool that the author used to upload the firmware sets itself an arbitrary speed during boot, e.g. 9600 but only for the duration of the firmware upload. After a reset, the esp gets up with the default speed stored in the flash, in this case probably 115,200.

    In other words, what speed the firmware was updating at and what the default esp will run at afterwards are two different things.
  • #12 17659340
    kamarol1
    Level 7  
    khoam wrote:
    kamarol1 wrote:
    Would you still like to know which file I should upload?


    0x00000 boot_v1.7.bin
    0x01000 user1.1024.new.2.bin (from folder "at")
    0xfc000 esp_init_data_default_v08.bin
    0x7e000 blank.bin
    0xfe000 blank.bin

    Added after 2 [minutes]: .

    simw wrote:
    This way you probably mess up the firmware and that's why it doesn't work.

    Nothing can be "fuzzed" this way.


    I have uploaded this, but it still does not respond, neither in the Arduino IDE nor in ESPlorer.

    Could this have an impact ? Because 'difoltically' it is indicated, while I do not use any Arduino board.
    ESP8266-01 firmware update but no response to connection .
  • ADVERTISEMENT
  • #13 17659345
    khoam
    Level 42  
    kamarol1 wrote:
    I uploaded it, but it still doesn't respond, neither in the Arduino IDE
    .
    And what baud rate do you have set in Serial Monitor?

    kamarol1 wrote:
    Could this have an effect ? Because 'difoltly' it is ticked, while I don't use any Arduino board.
    .
    In this case, it doesn't matter at all. What matters is the correct port and baud rate setting.
  • #15 17659353
    simw
    Level 27  
    khoam wrote:
    The firmware update tool that the Author used to upload the firmware sets itself an arbitrary speed during boot, e.g. 9600 but only for the duration of the firmware upload. After a reset, the esp gets up with the default speed stored in the flash, in this case probably 115,200.

    In other words, what speed the firmware was updating at and what speed the default esp will run at later are two different things.


    Well according to me the tool doesn't know how to set the correct baudrate value, and this must be 115200 in both cases. Selecting 9600 causes the bootloader (or a similar mechanism sewn into the ESP in firmware upload mode) to load "bushes" which causes the chip to fail to boot properly after a reboot in "user" mode and therefore there is no connection to it on the uart.
    I'll check this out soon...
  • #16 17659356
    khoam
    Level 42  
    I understand that after typing the AT command, you press the "Send" button?
    If so, check further with the speeds: 9600 and 57600.

    Added after 1 [minute]: .

    simw wrote:
    Well according to me the tool can't set the correct baudrate value,
    .

    "Baudrate of 74880 Bd is ESP's 'native' baud rate for sending debug messages generated automatically by the system itself during the boot in case there is 26 MHz instead of 40 MHz crystal used on board - and as we can see, mostly that is the case.
    With 40 MHz crystal the baudrate would be as expected (115200) but with 26 MHz crystal instead, baudrate is 115200 * 26/40 = 74880.
    Later after bootloader ends baudrate is controlled in other way so that's why you have two different baudrates - the first is the default one (74880) and the second is the one that is active later (the one you can set)."
  • #17 17659367
    kamarol1
    Level 7  
    At no speed does it respond to the AT command.
    There is a switch on the programmer, you can see it in the first post in the picture. There are Prog and UART positions. I did all the operations on Prog, while on the UART position it doesn't show the COM2 port, but that doesn't matter at this point either?
  • #18 17659371
    khoam
    Level 42  
    kamarol1 wrote:
    I did all the work on Prog,
    .
    Should be UART when you want to commune with esp. and "Prog" when you upload firmware.

    kamarol1 wrote:
    on the UART item it doesn't show the COM2 port, but that doesn't matter at this point either?
    .
    Unfortunately it does matter. Switching is best done with the programmer removed from the USB ;) .
  • #19 17659378
    kamarol1
    Level 7  
    However, it already shows COM2 but still no connection on the UART ;/.
  • #20 17659382
    khoam
    Level 42  
    kamarol1 wrote:
    However, it already shows COM2, but still no connection ;/
    .
    At any of the speeds I gave you earlier?
    If not, show a picture of the firmware upload tool where you had the addresses of the various firmware blocks set up.
  • #21 17659385
    kamarol1
    Level 7  
    Does not work at any speed.
    ESP8266-01 firmware update but no response to connection ESP8266-01 firmware update but no response to connection .

    first is boot _1.7
    second user 1.1024.new.2
    third esp_init_data_default_v08
    fourth and fifth blank
  • #22 17659389
    khoam
    Level 42  
    SPI mode should be "QIO" for the ESP-01, not "DIO".
  • #23 17659395
    kamarol1
    Level 7  
    I have uploaded the firmware again, according to the instructions, but still nothing ;/
  • #24 17659407
    khoam
    Level 42  
    In this situation, I suggest that you use some kind of serial terminal such as putty instead of the Arduino IDE to issue AT commands in UART mode.

    In my case, the settings are as follows:

    ESP8266-01 firmware update but no response to connection .
  • #25 17659419
    simw
    Level 27  
    khoam wrote:
    "Baudrate of 74880 Bd is ESP's 'native' baud rate for sending debug messages generated automatically by the system itself during the boot in case there is 26 MHz instead of 40 MHz crystal used on board - and as we can see, mostly that is the case.
    With 40 MHz crystal the baudrate would be as expected (115200) but with 26 MHz crystal instead, baudrate is 115200 * 26/40 = 74880.
    Later after bootloader ends baudrate is controlled in a different way so that's why you have two different baudrates - the first is the default one (74880) and the second is the one that is active later (the one you can set)."
    .

    Well and I checked, with the software I have (nodemcu firmware programmer) when uploaded with the speed set to 115200 everything works fine.
    When I set 9600 it firstly goes much slower, which of course is understandable, but still after a longer while everything is uploaded and there is communication over uart, so I was wrong :) .
    Here are my settings, in the attachment I still upload the firmware 2.2.1 maybe this will help the author of the thread.

    In addition I recommend RealmTerm for communication with ESP, it makes things easier, for me the serial monitor with Arduino is too simple a tool.

    ESP8266-01 firmware update but no response to connection .
    ESP8266-01 firmware update but no response to connection .

    ESP8266-01 firmware update but no response to connection .
  • #26 17659441
    khoam
    Level 42  
    simw wrote:
    attachment I still upload firmware 2.2.1 maybe this will help the thread author.
    .
    Out of curiosity I looked inside this zip - this firmware is a bit older than what the Author uploaded, but maybe it will help :)

    boot_v1.2.bin
    esp_init_data_default_v05.bin
    user1.1024.new.2.bin
  • #27 17724787
    kamarol1
    Level 7  
    I know it's late, but maybe someone else will benefit. The above advice, was good. Everything works for me on the NodeMCU_v2. I conclude that the switch in the converter is broken. Thanks for all the advice ;) .
  • #28 18251207
    Deaf200
    Level 11  
    This programmer does not support flashing ... when it is without the additional button which in the top photo 3 from the top is covered by a black field 8)

    Solder a bridge between 3v3 - EN
    Solder a tac switch between io0 - GND

    https://zapodaj.net/97a860e2a079f.gif.html here how to solder it

    1) you insert into the port a programmer with a switch to serial YOU HAVE SERIAL IN THE CONSOLE e.g. putty
    2) you insert the programmer with the serial switch into the port and at the same time press the soldered button, after inserting it you can release it and all programs will go away, finally your ESP
    3) you insert the programmer with the switch to PROG into the port, you can load sketches e.g. from Ardurino of course without pressing ...

    The jumper does not interfere with anything

    Thank you all very much for the comprehensive description of the flash upload procedure in the above programs together with the supply of binaries

    KUDOS TO

Topic summary

The discussion addresses issues with updating firmware on the ESP8266-01 module and subsequent lack of response to AT commands via serial connection. The original firmware version used was outdated (v0.9.5.0), and the baud rate mismatch during firmware upload and serial communication caused corrupted firmware flashing ("bushes") and failure to boot properly. The default baud rate after flashing AT firmware should be 115200, not 9600. Proper flashing requires setting the correct SPI mode ("QIO" for ESP-01), using compatible firmware versions (recommended 1.6.2 or 2.2.1 AT firmware), and ensuring the programmer switch is set to "Prog" during flashing and "UART" during communication. The programmer used lacked a necessary button for entering flash mode, which can be resolved by soldering a bridge between 3.3V and EN and a tactile switch between GPIO0 and GND to manually enter programming mode. Using serial terminal software like PuTTY or RealTerm instead of Arduino IDE's Serial Monitor is advised for better communication. The final resolution was that the converter switch was faulty, preventing proper mode switching and communication. The NodeMCU v2 board was confirmed to work correctly with the same firmware and settings.
Summary generated by the language model.
ADVERTISEMENT