ESP8266 Community Forum

- Thu Jun 25, 2020 11:15 am #87652 I recently updated an existing design from using the ESP-WROOM-02 (with the standard built in antenna to the ESP-WROOM-02U with the UFL antenna connector. The circuit design is the same, no change there. This module is the 4MB (32-Mbit) module. The new module is a Mouser:

https://www.mouser.com/ProductDetail/Es ... 49Ra8MQ%3D

The original module works great on the previous version of my assembly, the new assembly with the Mouser part does not show an SSID with a tested, working external UFL antenna attached. I originally loaded the AT non-OS firmware version 1.6.1 on the original board and upgraded it to version 1.7.4 recently released and it works fine. I loaded the 1.7.4 version on the new assembly and no SSID shows in my network list. The firmware loads fine with the ESP8266 Download Tool version 3.8.5 Here are my settings

ESP8266_NonOS_AT_Bin_V1.7.4\bin\boot_v1.7.bin 0x00000
ESP8266_NonOS_AT_Bin_V1.7.4\bin\at\1024+1024\user1.2048.new.5.bin 0x01000
ESP8266_NonOS_AT_Bin_V1.7.4\bin\blank.bin 0xFE000
ESP8266_NonOS_AT_Bin_V1.7.4\bin\blank.bin 0x3FB000
ESP8266_NonOS_AT_Bin_V1.7.4\bin\esp_init_data_default_v08.bin 0x3FC000
ESP8266_NonOS_AT_Bin_V1.7.4\bin\blank.bin 0x3FE000

Select SPIDownload Tab

SpiFlashConfig Section
CrystalFreq: 26M
SPI Speed: 40MHz
SPI Mode: QIO
Flash Size: 32Mbit-C1

Download Panel Section
COM: Applicable COM port for TTL USB-Serial Adapter (COM9)
BAUD: 115200

Along with the SSID not showing in my network list after rebooting (removing the jumper for the boot option) I connect to the module using Tera Term and when rebooting receive a bunch of random looking characters, but no READY prompt to accept AT commands. I get the READY prompt with the original assembly design with the non UFL ESP-WROOM-02 module but not with the new one. Again, the circuit design is identical. Here are the characters I get when connected to Tera Term with the new UFL module. Perhaps someone will recognize these characters and now what is going on.

ürlØrß
#âà


ìp
|?ßìxoÜälp

ònnä;ònä

ç$ rrpònàÃÜ
àÇÀl


bÀnâãnÀÄl

bÄ>~ònîÄÁ
?l`üÜ#nrnr?;À
âpònàÜ
àÇÀ



bnâãnÀp

ònnîÄð
r#nÀrnr?;À
?â;pònàÜ
àÇÀ



bÀnâãnp

ònnîÄÀ
rÜ#nÀ?rnr?ß;ÄÀ
?âÜrßÛnÀ?àÜ`ä8?ß;ÄßÄ`rßÿÉwnâbp

I appreciate any help or any information provided. I am thinking the module is failed in some way, but it flashes fine every time.

Thank you .

Jerry Hubbell

- Thu Jun 25, 2020 1:01 pm #87654 I changed the baud rate to 74880 because the module is running at 26 Mhz and the string of text shown during the boot process using Tera Term shows a bit more structure, although the text is shown in greek characters. Here is the translation.


ets Jan 8 2013,rst cause:1, boot mode:(3,6)

load 0x40100000, len 2592, 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

Perhaps the checksum error is a clue to what is going on.

Is there significance to the date Jan 8 2013? Is this just a very old module that I need to load early firmware on?

Thanks

- Thu Jun 25, 2020 1:22 pm #87655 It seems that after some more research, this checksum error is related to the flash size. This module should be a 4MB (32-Mbit) module but it doesn't appear to be. The Mouser link in the first message on this thread shows it as a 4MB module. I will try different flash sizes to see if I can get it to work.

Jerry Hubbell

- Thu Jun 25, 2020 1:40 pm #87656 I have tried every different flash size 8, 16, and 32-Mbit and I get the same response on boot up


ets Jan 8 2013,rst cause:1, boot mode:(3,6)

load 0x40100000, len 2592, 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

Thanks for taking a look at this.

Jerry Hubbell