logo elektroda
logo elektroda
X
logo elektroda

Software upload addresses and ESP8266 esp-12 E unresponsive on AT

robo1973 1926 26
ADVERTISEMENT
Treść została przetłumaczona polish » english Zobacz oryginalną wersję tematu
  • #1 18179293
    robo1973
    Level 15  
    Hello !!!

    I have two problems
    The first is at which address to upload the software /first two addresses in the name/.

    0x00000.bin
    0x10000.bin
    blank.bin
    esp_init_data_default.bin
    nodemcu_integer_0.9.5_20150318.bin

    The other thing is the module has 4 MB Flash/ ?
    Either I am uploading the wrong software and to the wrong addresses or something else. The soft seems to load with ESP8266Flasher.exe but I have no response from the module in the terminal on AT ?
    Can you please provide some proven soft and addresses where to upload ?
    Thank you
  • ADVERTISEMENT
  • #2 18179298
    khoam
    Level 42  
    robo1973 wrote:
    but I don't have the module's AT response in the terminal ?
    .
    If you don't upload AT firmware, then there will be no AT response in the terminal. In my footer you have a link to a post where you can find where to download the AT firmware for the ESP8266 (version 1.7 for 4MB flash).

    robo1973 wrote:
    The other thing is the module has 4 MB Flash/ ?
    .
    Usually ESP-12Es have a flash size of 4 MB unless you have come across some "economy" version.
  • #3 18179339
    robo1973
    Level 15  
    Which addresses to upload to?
  • Helpful post
    #4 18179343
    khoam
    Level 42  
    0x00000 boot_v1.7.bin
    0x01000 user2.2048.new.5.bin
    0x3fc000 esp_init_data_default_v08.bin
    0xfe000 blank.bin
    0x3fe000 blank.bin

    First, of course, you need to unpack the firmware package.
  • ADVERTISEMENT
  • #6 18179373
    khoam
    Level 42  
    Please show a screenshot of the flasher with the settings.
    What speed do you have set in the serial terminal?
  • #7 18179389
    robo1973
    Level 15  
    Software upload addresses and ESP8266 esp-12 E unresponsive on AT Software upload addresses and ESP8266 esp-12 E unresponsive on AT .

    terminal 115200

    Software upload addresses and ESP8266 esp-12 E unresponsive on AT .
  • ADVERTISEMENT
  • #8 18179397
    khoam
    Level 42  
    The settings of the individual sections in the flasher look OK.
    I was referring to the speed setting in the terminal. Which one are you using?
  • #9 18179401
    robo1973
    Level 15  
    you have above Realterm
  • #10 18179407
    khoam
    Level 42  
    Do you have the COM port to the flasher and terminal open at the same time i.e. is the flasher closed as you use the terminal?
    You need to reboot the ESP after uploading the firmware.

    Added after 3 [minutes]: .

    Please still show what you have in the flasher logs after uploading the firmware.
  • #11 18179439
    robo1973
    Level 15  
    I disconnect the TTL converter from the USB laptop, disconnect the I00 from the ground and reconnect the converter to the USB
  • #12 18179444
    khoam
    Level 42  
    robo1973 wrote:
    I unplug the TTL converter from the laptop USB , disconnect the I00 from ground and plug the converter back into the USB
    .
    For the reset you only need :) .
    Do you have GPIO 0 and GPIO 2 connected with a 10k resistor to the 3V3 supply?

    Software upload addresses and ESP8266 esp-12 E unresponsive on AT
  • ADVERTISEMENT
  • #13 18179468
    robo1973
    Level 15  
    I've got,mum Only gripo15 us to ground without resistor
    My guess is that there is something wrong with my E 12 software.
    Simply after uploading the software, the module does not stand up / does not transmit wifi / Either bad software or addresses, because on another without AT at least transmits wifi
  • #14 18179474
    khoam
    Level 42  
    robo1973 wrote:
    I bet there is something soft wrong with my E 12 version
    .
    I don't think unless it has less than 4 MB. You have not yet shown the flasher logs after uploading the firmware to the esp.
  • #15 18179483
    robo1973
    Level 15  
    Note:P program flash success.
    Note:P program flash success.
    Note:P flash program success.
    Note:P flash program success.
    Note:P flash program success.
    Note:P flash program success.
    Note:P flash program success.
    Note:P flash program success.
    Note:P flash program success.
    Note:P flash program success.
    Note:P flash program success.
    Note:P flash program success.
    Note:P flash program success.
    Note:P flash program success.
    Note:P flash program success.
    Note:P flash program success.
    Note:Set base address success.
    Note:P flash program success.
    Note:Set base address success.
    Note:P flash program success.
    Note:P flash program success.
    Note:P flash program success.
    Note:P flash program success.
    Note:Set base address success.
    Note:P flash program success.
    Note:P flash program success.
    Note:P flash program success.
    Note:P program flash success.
    Note:Serial port disconnected.
  • #16 18179489
    khoam
    Level 42  
    robo1973 wrote:
    Simply after uploading the software the module does not stand up / does not sow wifi/ Either bad software or addresses because on another without AT at least wifi sows
    .
    The AT firmware will not "sow" wifi after boot until you issue the appropriate AT commands.
    The AT firmware you downloaded is from the manufacturer, and I have not had it fail to work on a working ESP-12 or ESP-07. You can, of course, still try with version 1.6.2.
    Either there is something wrong with the serial terminal configuration, or with the ESP-12 connections themselves.
  • #17 18181068
    robo1973
    Level 15  
    It's I don't know what it is I'm uploading according to the addresses what you gave I have two modules and it's the same on two of them. With both the converter and the adrurino I cannot communicate over AT
  • #18 18181258
    khoam
    Level 42  
    You can still try the alternative settings for version 1.7:
    Code: Ini
    Log in, to see the code
    .
  • #19 18181548
    kaczakat
    Level 34  
    In the schematic GPIO16 is connected to RST permanently, it should be a diode in the direction to GPIO16, such a connection makes it impossible to upload the firmware properly, unless you disconnect this jumper while uploading. If there is to be a resistor on GPIO15 then give a resistor - it is always better to do exactly with the instructions to start with.
    I always uploaded the AT firmware stating I had 1MB flash, even when I had 4, same settings for ESP12F/12E and 1MB ES01S:
    Software upload addresses and ESP8266 esp-12 E unresponsive on AT .
    and as you can see with another program.
    If it doesn't work I reduce QIO, QOUT, DIO and finally DOUT in turn.
    Newer firmware has the AT connection at 115200, older ones had 9600, I always check both.
    Upload a sample sketch from the Arduino that prints something to Serial and see if it works properly.
    When you connect the ESP to the PC set the terminal to 74k and do a reset, paste the boot message here - it says what is uploaded and what mode it boots into, maybe something is not connecting and despite using the switch it still only boots into flash upload mode.
    Helpful post? Buy me a coffee.
  • #20 18181678
    robo1973
    Level 15  
    Thank you for your help tonight I protest
    when uploading you have BAUD 921600 or so set ?
  • #21 18181824
    khoam
    Level 42  
    robo1973 wrote:
    during upload you have BAUD 921600 or so set ?
    .
    Better not. This will limit the number of potential sources of problems when uploading.

    Added after 8 [minutes]:fd5bbfb20

    kaczakat wrote:
    In the schematic GPIO16 is connected to RST permanently, it should be diode in the direction to RST, such a connection prevents uploading the firmware correctly
    .
    During programming, GPIO16 does not need to be connected to anything at all. In the schematic it is connected to the RST to wake up the ESP from deep-sleep.

    Added after 10 [minutes]:fd5bbfb20

    It would also be a good idea for you to use the Flash Download Tool for loading firmware mentioned by a colleague @kaczakat .
    Link to post with attached program version 3.6.7:
    https://www.elektroda.pl/rtvforum/topic3415731.html
  • #22 18182139
    kaczakat
    Level 34  
    Thanks to the diode from RST to GPIO16, it is possible not to move this connection any more and to have a permanent connection for wake-up, while at the same time flash uploading works. As someone doesn't intend to use sleep it is of course possible not to connect at all.
    I set the speed to 900k as everything is OK, sometimes I need to reduce it to 115200, and there were times when I had to upload 9600, it depends on which cable and which module, which UART converter.
    Helpful post? Buy me a coffee.
  • #23 18182561
    robo1973
    Level 15  
    kol kaczakat in the picture you shared is user1.1048.new.5.bin and in the package is user1.2048.new.5.bin ?
    The second issue I understand the diode strip for the RST ?
  • #24 18182634
    kaczakat
    Level 34  
    Led is a special case of a light-emitting diode, I am writing about a schottky diode or ordinary silicon diode of 0.6V, towards GPIO16 )there above I wrote wrong):
    Software upload addresses and ESP8266 esp-12 E unresponsive on AT .

    Attached is what I uploaded.
    PS:
    For the AT I don't see the point of connecting GPIO16 to the RST in any way, this is used to wake up every certain time with a code from the ESP level, that is when there is no other device controlling it.
    Helpful post? Buy me a coffee.
  • #25 18182877
    robo1973
    Level 15  
    After uploading your package, the terminal shows the following when connected to WiFi
    +STA_CONNECTED:"a4:50:46:d5:88:e6"

    +DIST_STA_IP:"a4:50:46:d5:88:e6","192.168.4.2"


    After the AT+GMR command, it responds with AT+GMR
    Strange that it responds to the command with the same /.

    user1.1048.new.5.bin and user 2 are uploaded to the addresses you specified

    while user1.2048.new.5.bin just uploads after 0c1000 and also wifi gets up

    Strange, because uploading ESP8266_AT_Bin_V1.7 to the same addresses causes wifi not to work
  • #26 18183291
    kaczakat
    Level 34  
    After uploading everything, firing up the terminal at 115200 and pressing RST, the 74k speed rubbish should fly through first, followed by the READY text.
    AT commands can now be typed in.
    Configuration uploaded to a Wemos board with ESP12E and 4MB flash:
    Software upload addresses and ESP8266 esp-12 E unresponsive on AT .
    Post-GMR response:
    Spoiler:
    AT+GMR
    AT version:1.6.2.0(Apr 13 2018 11:10:59)
    SDK version:2.2.1(6ab97e9)
    compile time:Jun 7 2018 19:34:29
    Bin version(Wroom 02):1.6.2
    OK
    .
    Soft 1.71 is a bit more messed up, it worked in this setting:
    Software upload addresses and ESP8266 esp-12 E unresponsive on AT .
    Spoiler:
    AT+GMR
    AT version:1.7.1.0(Jul 15 2019 16:58:04)
    SDK version:3.0.1(78a3e33)
    compile time:Jul 15 2019 18:12:41
    Bin version(Wroom 02):1.7.1
    OK
    .
    I downloaded the soft from here: Link .
    Helpful post? Buy me a coffee.
  • #27 18184700
    robo1973
    Level 15  
    The case is as follows I have uploaded the soft ESP8266_AT_Bin_V1.7 and ESP8266_NonOS_AT_Bin_V1.7.1 according to the settings in the last picture for Soft 1.71
    Soft loaded, I can see the network from the card . After a reset REDY.
    Terminal responds correctly after setting in ardurino : Both NL and CR

    Thank you !!!!

Topic summary

The discussion revolves around issues related to uploading firmware to the ESP8266 ESP-12E module and achieving a responsive AT command interface. Users inquire about the correct memory addresses for uploading various firmware files, including AT firmware, and express concerns about the module's unresponsiveness. Key addresses for uploading firmware are provided, such as 0x00000 for bootloader and 0x01000 for user firmware. Users also discuss the importance of proper serial terminal settings, including baud rates, and the necessity of rebooting the ESP after firmware uploads. Troubleshooting steps include checking GPIO connections and ensuring the correct firmware version is used. Successful configurations are shared, highlighting the need for specific wiring and settings to establish WiFi connectivity and AT command responsiveness.
Summary generated by the language model.
ADVERTISEMENT