logo elektroda
logo elektroda
X
logo elektroda

Wemos D1 Mini ESP-12F Not Responding to AT Commands After Firmware Update

shel82 1500 18
ADVERTISEMENT
Treść została przetłumaczona polish » english Zobacz oryginalną wersję tematu
  • #1 17833040
    shel82
    Level 18  
    Hi, maybe someone can give a hint - the ESP8266 chip in the ESP-12F version on the Wemos D1 mini PCB is not responding to AT commands.

    Uploaded ESP8266_NONOS_SDK-1.5.4 firmware (works at 74880), the chip works fine, you can upload a program to it and execute, but it doesn't respond to AT commands sent (maybe I'm doing something wrong or misconfiguring the terminal)?

    I would like to add that I have tried on different terminals with CR=CR+LF transmission enabled, Handshaking - none, etc., while receiving data that is what the chip sends correctly displays on the terminal....
  • ADVERTISEMENT
  • #3 17833232
    shel82
    Level 18  
    Confusion with confusion with these firmwares - at least for a beginner, or is there somewhere reasonably accessible to describe it?

    ~khoam
    Please confirm yet if I understand the offset addresses for the ESP-12F (32Mbit) in #BOOT MODE correctly
    boot_v1.2+.bin 0x00000
    user1.2048.new.5.bin 0x01000
    esp_init_data_default.bin 0x3fc000
    blank.bin 0xfe000 & 0x3fe000
  • ADVERTISEMENT
  • #4 17833260
    khoam
    Level 42  
    shel82 wrote:
    Confirm further please if I understand the offset addresses for the ESP-12F (32Mbit) in #BOOT MODE
    .

    Good reasoning. Exactly as in the README.md file :) .

    Added after 1 [minute]:

    shel82 wrote:
    Are there any reasonably accessible descriptions of this somewhere?
    .
    In the manufacturer's documentation ;) .
    https://www.espressif.com/en/support/download/overview?keys=&field_type_tid%5B%5D=14
  • #5 17833270
    shel82
    Level 18  
    khoam wrote:
    br/>
    shel82 wrote:
    Confirm yet please if I understand the offset addresses for the ESP-12F (32Mbit) in #BOOT MODE
    .

    Good reasoning. Exactly as in the README.md file :)


    Hmm, so I uploaded and it still doesn't work, and in the terminal it looks like this:
    ets Jan  8 2013,rst cause:2, boot mode:(3,6)
    
    
    
    load 0x40100000, len 2592, room 16 
    
    tail 0
    
    chksum 0xf3
    
    load 0x3ffe8000, len 764, room 8 
    
    tail 4
    
    chksum 0x92
    
    load 0x3ffe82fc, len 676, room 4 
    
    tail 0
    
    chksum 0x22
    
    csum 0x22
    
    
    
    2nd boot version : 1.7(5d6f877)
    
    SPI Speed : 40MHz
    
    SPI Mode : DIO
    
    SPI Flash Size & Map: 32Mbit(512KB+512KB)
    
    jump to run user1 @ 1000
    
    
    
    mismatch map 5,spi_size_map 4
    
    system_partition_table_regist fail
    .
  • #6 17833285
    khoam
    Level 42  
    shel82 wrote:
    Hmm, so I uploaded
    .

    But what specific firmware version did you upload?
  • ADVERTISEMENT
  • #7 17833303
    shel82
    Level 18  
    khoam wrote:
    shel82 wrote:
    Hmm, so I uploaded
    .

    But what specific firmware version did you upload?
    .

    ESP8266_AT_Bin_V1.7
  • #8 17833306
    khoam
    Level 42  
    shel82 wrote:
    ESP8266_AT_Bin_V1.7


    This could not work because you have:

    shel82 wrote:
    SPI Flash Size & Map: 32Mbit(512KB+512KB)
    .

    So you can at most use the ESP8266 AT Bin version V1.6.2
    For this version there is:

    0x00000 boot_v1.7.bin
    0x01000 user1.1024.new.2.bin
    0xfc000 esp_init_data_default_v08.bin
    0x7e000 blank.bin
    0xfe000 blank.bin
  • #9 17833319
    shel82
    Level 18  
    khoam wrote:
    shel82 wrote:
    ESP8266_AT_Bin_V1.7
    .

    This could not work because you have:

    shel82 wrote:
    SPI Flash Size & Map: 32Mbit(512KB+512KB)
    .

    So you can at most use the ESP8266 AT Bin version V1.6.2
    For this version there is:

    0x00000 boot_v1.7.bin
    0x01000 user1.1024.new.2.bin
    0xfc000 esp_init_data_default_v08.bin
    0x7e000 blank.bin
    0xfe000 blank.bin
    .

    In the meantime I have uploaded ESP8266_AT_Bin_V1.5.1 and it doesn't work either:
    ets Jan  8 2013,rst cause:2, boot mode:(3,7)
    
    
    
    load 0x40100000, len 816, room 16 
    
    tail 0
    
    chksum 0xef
    
    load 0x00000000, len 0, room 8 
    
    tail 0
    
    chksum 0xef
    
    load 0x00000000, len 0, room 0 
    
    tail 0
    
    chksum 0xef
    
    csum 0xef
    
    csum err
    
    ets_main.c  
    .

    Added after 2 [minutes]: .

    "SPI Flash Size & Map: 32Mbit(512KB+512KB)". - and isn't this value taken/written from the firmware I'm uploading, and is it unlikely to be used?
  • #10 17833335
    khoam
    Level 42  
    shel82 wrote:
    In the meantime, I uploaded ESP8266_AT_Bin_V1.5.1 and it doesn't work either:
    .
    What addresses did you provide for the individual binaries? Without this information it is difficult to answer, but it looks like you have entered the wrong ones.

    You should, regardless of AT firmware version, take those addresses that are in the "32Mbit(512KB+512KB)" section. - at least that's what the logs for your board show. There are other addresses in other sections and the operation will fail.

    Added after 5 [minutes]: .

    shel82 wrote:
    "SPI Flash Size & Map: 32Mbit(512KB+512KB)" - and isn't this value taken/written from the firmware I'm uploading and rather shouldn't be suggested?

    Rather not, as you tried to upload firmware that required 1024KB+1024KB the first time.
    Just in case, you can check this with the command esptool .
  • #11 17833352
    shel82
    Level 18  
    khoam wrote:
    shel82 wrote:
    In the meantime I have uploaded ESP8266_AT_Bin_V1.5.1 and it doesn't work either:
    .
    What addresses did you provide for the individual binaries? Without this information it is difficult to answer, but it looks like you have entered the wrong ones.

    You should, regardless of AT firmware version, take those addresses that are in the "32Mbit(512KB+512KB)" section. - at least that's what the logs for your board show. There are other addresses in other sections and the operation will fail.

    Added after 5 [minutes]: .

    shel82 wrote:
    "SPI Flash Size & Map: 32Mbit(512KB+512KB)" - and isn't this value taken/written from the firmware I'm uploading and rather shouldn't be suggested?

    Rather not, as you tried to upload firmware that required 1024KB+1024KB the first time.
    Just in case, you can check this with the command esptool .
    .
  • ADVERTISEMENT
  • #13 17833390
    shel82
    Level 18  
    khoam wrote:
    The original Wemos D1 mini has 4MB Flash = 32Mbit, 512+512 and the manufacturer recommends uploading AT firmware like this:
    https://wiki.wemos.cc/tutorials:get_started:revert_to_at_firmware
    .

    Shrinks and that's what I'm doing, photo below, reply after uploading ESP8266_AT_Bin_V1.5.1:
    ets Jan  8 2013,rst cause:2, boot mode:(3,7)
    
    
    
    load 0x40100000, len 816, room 16 
    
    tail 0
    
    chksum 0xef
    
    load 0x00000000, len 0, room 8 
    
    tail 0
    
    chksum 0xef
    
    load 0x00000000, len 0, room 0 
    
    tail 0
    
    chksum 0xef
    
    csum 0xef
    
    csum err
    
    ets_main.c 
    .
  • #14 17833458
    khoam
    Level 42  
    You forced me to "dust off" my wemos d1 mini :) .
    So, I uploaded the AT software version ESP8266_AT_Bin_V1.5.1:

    esptool --port /dev/ttyUSB1 write_flash -fm qio 0x00000 boot_v1.6.bin
    Code: Bash
    Log in, to see the code
    .

    esptool --port /dev/ttyUSB1 write_flash -fm qio 0x01000 user1.1024.new.2.bin
    Code: Bash
    Log in, to see the code
    .

    esptool --port /dev/ttyUSB1 write_flash -fm qio 0x3fc000 esp_init_data_default.bin
    Code: Bash
    Log in, to see the code
    .

    esptool --port /dev/ttyUSB1 write_flash -fm qio 0x7e000 blank.bin
    Code: Bash
    Log in, to see the code


    esptool --port /dev/ttyUSB1 write_flash -fm qio 0xfe000 blank.bin
    Code: Bash
    Log in, to see the code


    I then rebooted wemos (unplugging and plugging in the USB). I connected the serial port monitor with the speed set and I have:
    Code: Dos
    Log in, to see the code
    .

    Now find at least one difference ;) .
  • #15 17833497
    kaczakat
    Level 34  
    I recently uploaded version 2 from the attachment to Wemos and it works, in fact I even forgot to change the flash size and it stayed at 1MB, I previously uploaded 1.6 to ESP01. The UART is at 115200 and the upload program is also in the attachment
    Helpful post? Buy me a coffee.
  • #16 17833522
    khoam
    Level 42  
    kaczakat wrote:
    I recently uploaded version 2 from the attachment to Wemos and it works, in fact I even forgot to change the flash size and it stayed 1MB, I previously uploaded 1.6 to ESP01. The UART is at 115200 and the uploader is also attached
    .

    There is no version 2.0 for AT firmware for the ESP8266, the manufacturer knows nothing about it: https://www.espressif.com/en/support/download/at?keys=&field_type_tid%5B%5D=14
    What the colleague sent in the attachment is actually version 1.3.0 from 2016, an artefact.
    The documentation in Chinese is not very helpful either. I already provided a link to the official manufacturer's documentation in post #4.
  • #18 17833585
    khoam
    Level 42  
    kaczakat wrote:
    So now all you have to do is paste:
    .
    Yes, but you need to have the AT firmware version already uploaded, which is what the Author of this thread is trying to do.

Topic summary

The discussion revolves around issues faced by a user with the Wemos D1 Mini ESP-12F not responding to AT commands after a firmware update. The user uploaded the ESP8266_NONOS_SDK-1.5.4 firmware but encountered problems with AT command responses. Various suggestions were made, including uploading the correct AT firmware versions and ensuring proper binary addresses during the upload process. The conversation highlighted the importance of using the correct firmware version (e.g., ESP8266_AT_Bin_V1.6.2) and the correct memory mapping for the 32Mbit flash size. Users shared their experiences with different firmware versions and configurations, emphasizing the need for accurate settings to achieve successful communication with the ESP8266 chip.
Summary generated by the language model.
ADVERTISEMENT