[Solved] Problem flashing ESP (12E) with 4096k ESP Easy

Moderators: grovkillen, Stuntteam, TD-er

Post Reply
Message
Author
groovy
Normal user
Posts: 39
Joined: 14 Oct 2016, 11:32
Location: Chemnitz, Germany

[Solved] Problem flashing ESP (12E) with 4096k ESP Easy

#1 Post by groovy » 20 Oct 2016, 11:26

I'm facing a strange problem with my ESP 12E boards when using ESP Easy 4096k version.

Flashing itself succeeds, but after reboot, there is no AP called ESP_0, but an AP called something like ESP_FDBCF4, where the last 6 chars are the last 6 chars of the MAC address.
I can connect to that AP (there's no WPA key neccessary), and I even get an IP address (192.168.4.2) and can ping the device at 192.168.4.1.
But I can't open the web interface.

However, when I use a 512k image, I can see an AP named ESP_0, get an IP address and can successfully open the web interface in the browser and configure that device.
At the Main page, I can see that the "Flash Size" is indeed 4096k.

I tried several ESP 12E modules, all with the same behaviour. It also doesn't make a difference if I use a precompiled image or compile it myself.

Has someone any idea, what's wrong here?
Will I be able to use the 4096k displayed at the Main page, even if I used a 512k image?

Thanks in advance.
Last edited by groovy on 14 Nov 2016, 13:15, edited 1 time in total.

scarecrow2k6
New user
Posts: 6
Joined: 16 Oct 2016, 08:17

Re: Problem flashing ESP (12E) with 4096k ESP Easy

#2 Post by scarecrow2k6 » 21 Oct 2016, 00:22

I have faced exactly the same issue. I don't know what exactly is causing it but the way I "solved" it is by using a pc with wifi rather than a phone or a tablet. Even when I connected via pc, it didn't ask me for the initial "configesp" password, just went straight to the ssid/pass page. I am interested in knowing about this as well.

groovy
Normal user
Posts: 39
Joined: 14 Oct 2016, 11:32
Location: Chemnitz, Germany

Re: Problem flashing ESP (12E) with 4096k ESP Easy

#3 Post by groovy » 21 Oct 2016, 10:08

Thank you for your reply. Unfortunately, trying to connect with a PC doesn't work for me, I get a "connection refused".
I also tried scanning the device with nmap. It tells me that there is no port open at all:

Code: Select all

Starting Nmap 7.30 ( https://nmap.org ) at 2016-10-21 09:59 CEST
NSE: Loaded 142 scripts for scanning.
NSE: Script Pre-scanning.
Initiating NSE at 09:59
Completed NSE at 09:59, 0.00s elapsed
Initiating NSE at 09:59
Completed NSE at 09:59, 0.00s elapsed
Initiating ARP Ping Scan at 09:59
Scanning 192.168.4.1 [1 port]
Completed ARP Ping Scan at 09:59, 0.21s elapsed (1 total hosts)
Initiating Parallel DNS resolution of 1 host. at 09:59
Completed Parallel DNS resolution of 1 host. at 09:59, 5.50s elapsed
Initiating SYN Stealth Scan at 09:59
Scanning 192.168.4.1 [1000 ports]
sendto in send_ip_packet_sd: sendto(7, packet, 44, 0, 192.168.4.1, 16) => Operation not permitted
Offending packet: TCP 192.168.4.2:62470 > 192.168.4.1:1137 S ttl=49 id=47141 iplen=44  seq=1795656882 win=1024 <mss 1460>
sendto in send_ip_packet_sd: sendto(7, packet, 44, 0, 192.168.4.1, 16) => Operation not permitted
Offending packet: TCP 192.168.4.2:62470 > 192.168.4.1:1100 S ttl=54 id=64554 iplen=44  seq=1795656882 win=1024 <mss 1460>
sendto in send_ip_packet_sd: sendto(7, packet, 44, 0, 192.168.4.1, 16) => Operation not permitted
Offending packet: TCP 192.168.4.2:62470 > 192.168.4.1:3370 S ttl=47 id=3693 iplen=44  seq=1795656882 win=1024 <mss 1460>
sendto in send_ip_packet_sd: sendto(7, packet, 44, 0, 192.168.4.1, 16) => Operation not permitted
Offending packet: TCP 192.168.4.2:62470 > 192.168.4.1:9999 S ttl=51 id=31537 iplen=44  seq=1795656882 win=1024 <mss 1460>
sendto in send_ip_packet_sd: sendto(7, packet, 44, 0, 192.168.4.1, 16) => Operation not permitted
Offending packet: TCP 192.168.4.2:62470 > 192.168.4.1:2557 S ttl=45 id=46330 iplen=44  seq=1795656882 win=1024 <mss 1460>
sendto in send_ip_packet_sd: sendto(7, packet, 44, 0, 192.168.4.1, 16) => Operation not permitted
Offending packet: TCP 192.168.4.2:62470 > 192.168.4.1:5850 S ttl=55 id=20022 iplen=44  seq=1795656882 win=1024 <mss 1460>
sendto in send_ip_packet_sd: sendto(7, packet, 44, 0, 192.168.4.1, 16) => Operation not permitted
Offending packet: TCP 192.168.4.2:62470 > 192.168.4.1:1875 S ttl=37 id=15129 iplen=44  seq=1795656882 win=1024 <mss 1460>
sendto in send_ip_packet_sd: sendto(7, packet, 44, 0, 192.168.4.1, 16) => Operation not permitted
Offending packet: TCP 192.168.4.2:62470 > 192.168.4.1:7200 S ttl=48 id=56234 iplen=44  seq=1795656882 win=1024 <mss 1460>
sendto in send_ip_packet_sd: sendto(7, packet, 44, 0, 192.168.4.1, 16) => Operation not permitted
Offending packet: TCP 192.168.4.2:62470 > 192.168.4.1:1107 S ttl=38 id=23320 iplen=44  seq=1795656882 win=1024 <mss 1460>
sendto in send_ip_packet_sd: sendto(7, packet, 44, 0, 192.168.4.1, 16) => Operation not permitted
Offending packet: TCP 192.168.4.2:62470 > 192.168.4.1:1840 S ttl=50 id=14816 iplen=44  seq=1795656882 win=1024 <mss 1460>
Omitting future Sendto error messages now that 10 have been shown.  Use -d2 if you really want to see them.
Increasing send delay for 192.168.4.1 from 0 to 5 due to 203 out of 507 dropped probes since last increase.
Increasing send delay for 192.168.4.1 from 5 to 10 due to 39 out of 96 dropped probes since last increase.
Completed SYN Stealth Scan at 09:59, 17.89s elapsed (1000 total ports)
Initiating Service scan at 09:59
Initiating OS detection (try #1) against 192.168.4.1
adjust_timeouts2: packet supposedly had rtt of -98834 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -98834 microseconds.  Ignoring time.
Retrying OS detection (try #2) against 192.168.4.1
adjust_timeouts2: packet supposedly had rtt of -198850 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -198850 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -99720 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -99720 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -99732 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -99732 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -99652 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -99652 microseconds.  Ignoring time.
NSE: Script scanning 192.168.4.1.
Initiating NSE at 09:59
Completed NSE at 09:59, 0.00s elapsed
Initiating NSE at 09:59
Completed NSE at 09:59, 0.00s elapsed
Nmap scan report for 192.168.4.1
Host is up (0.00079s latency).
All 1000 scanned ports on 192.168.4.1 are closed
MAC Address: 1A:FE:34:FC:BD:D6 (Unknown)
Warning: OSScan results may be unreliable because we could not find at least 1 open and 1 closed port
Aggressive OS guesses: NodeMCU firmware (lwIP stack) (95%), 2N Helios IP VoIP doorbell (91%), Advanced Illumination DCS-100E lighting controller (91%), AudioControl D3400 network amplifier (91%), British Gas GS-Z3 data logger (91%), Denver Electronics AC-5000W MK2 camera (91%), Espressif WiFi system-on-a-chip (91%), Fatek FBs-CBEH PLC Ethernet communication board (91%), Grandstream GXP1105 VoIP phone (91%), LaSAT satellite receiver (91%)
No exact OS matches for host (test conditions non-ideal).
Network Distance: 1 hop

TRACEROUTE
HOP RTT     ADDRESS
1   0.79 ms 192.168.4.1

NSE: Script Post-scanning.
Initiating NSE at 09:59
Completed NSE at 09:59, 0.00s elapsed
Initiating NSE at 09:59
Completed NSE at 09:59, 0.00s elapsed
Read data files from: /usr/bin/../share/nmap
OS and Service detection performed. Please report any incorrect results at https://nmap.org/submit/ .
Nmap done: 1 IP address (1 host up) scanned in 26.94 seconds
           Raw packets sent: 1629 (73.744KB) | Rcvd: 3191 (129.524KB)

Drum
Normal user
Posts: 300
Joined: 07 Feb 2016, 11:56

Re: Problem flashing ESP (12E) with 4096k ESP Easy

#4 Post by Drum » 07 Nov 2016, 16:28

Have you tried serial terminal to see what it is doing?

groovy
Normal user
Posts: 39
Joined: 14 Oct 2016, 11:32
Location: Chemnitz, Germany

Re: Problem flashing ESP (12E) with 4096k ESP Easy

#5 Post by groovy » 14 Nov 2016, 12:22

I just tried again with the actual git version. Serial console gives this at boot, so there is definitely something wrong:

Code: Select all

PID:0
Version:0
INIT : Incorrect PID or version!
RESET: Cold boot
FLASH: Erase Sector: 105
FLASH: Erase Sector: 106
FLASH: Erase Sector: 107
FLASH: Erase Sector: 108
FLASH: Erase Sector: 109
FLASH: Erase Sector: 110
FLASH: Erase Sector: 111
FLASH: Erase Sector: 112
FLASH: Erase Sector: 113
FLASH: Erase Sector: 114
FLASH: Erase Sector: 115
FLASH: Erase Sector: 116
FLASH: Erase Sector: 117
FLASH: Erase Sector: 118
FLASH: Erase Sector: 119
FLASH: Erase Sector: 120
FLASH: Erase Sector: 121
FLASH: Erase Sector: 122
FLASH: Erase Sector: 123
FLASH: Erase Sector: 124
FLASH: Erase Sector: 125
FLASH: Erase Sector: 126
FLASH: Erase Sector: 127
FLASH: Settings saved
FLASH: Settings saved

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

load 0x4010f000, len 1384, room 16 
tail 8
chksum 0x2d
csum 0x2d
v09826c6d
~ld
I used this command to flash:

Code: Select all

python2 ../../esp8266/esptool-master/esptool.py --port /dev/ttyUSB0 write_flash 0x00000 ESPEasy.ino.generic.bin 
Connecting...
Erasing flash...
Writing at 0x00068800... (100 %)

Leaving...
Any idea? Do I have to use another address to flash to? I used 0x00000, which works for my ESP-01 modules.

groovy
Normal user
Posts: 39
Joined: 14 Oct 2016, 11:32
Location: Chemnitz, Germany

Re: Problem flashing ESP (12E) with 4096k ESP Easy

#6 Post by groovy » 14 Nov 2016, 13:15

Just investigated a bit further. When I add parameters explicit for flash-mode and flash-size, it works. Command then looks like this:

Code: Select all

python2 ../../esp8266/esptool-master/esptool.py --port /dev/ttyUSB0 write_flash -fm dio -fs 32m 0x00000 ESPEasy.ino.generic.bin 

Post Reply

Who is online

Users browsing this forum: No registered users and 118 guests