ESP-12(E?) On NodeMcu, wifi works on SDK NONOS until 1.3.0, doesn't work on 1.4.0 and higher

cranphin
Posts: 8
Joined: Sun May 22, 2016 7:52 am

ESP-12(E?) On NodeMcu, wifi works on SDK NONOS until 1.3.0, doesn't work on 1.4.0 and higher

Postby cranphin » Sun May 22, 2016 8:12 am

Hi!

I bought this:
http://www.ebay.com/itm/201542946669 (NodeMcu 1.0 with a esp-12E, I think).
The exact ESP-12 type isn't mentioned, but it looks like an E to me.

With any firmware built with SDK <= 1.3.0 wifi works fine on it (this includes NodeMcu 0.9.5, AT 1.3.0, and custom built firmwares).
With any firmware built with SDK >= 1.4.0, wifi doesn't work, I usually don't get a list of AP's, and usually I can't connect to an AP (this includes NodeMcu 1.4.0, AT 1.4.0, 1.5.2, 1.5.4, and custom firmwares).

I've spent two days reproducing this, it's quite well reproducible :)

For testing I've mainly been using the AT firmwares.
I've tried all the flashing tools, but mostly esptool.py. Using that I've repeatedly erased the whole flash.
For the AT firmwares, I use the exact settings/addresses/files from the readme.

Does anyone have an idea why this could be, or how I could fix it?
Help? :)
Feel free to ask for more details!

Details below:

Example 1.3.0 AT firmware:

Code: Select all

ready
AT+GMR

AT version:0.40.0.0(Aug  8 2015 14:45:58)
SDK version:1.3.0
compile time:Aug  8 2015 17:19:38
OK
AT+CWMODE=1


OK
AT+CWLAP

+CWLAP:(4,"Milkrun",-73,"c8:0e:14:5f:9f:fc",1,-19)
+CWLAP:(3,"H369A277883_RPT",-88,"9c:5c:8e:c6:06:b0",3,-16)
+CWLAP:(4,"H368N9159BB",-91,"ec:8a:4c:91:59:bb",3,8)
+CWLAP:(4,"H220N8611B1",-74,"fc:c8:97:86:11:b1",6,-7)
+CWLAP:(0,"KPN Fon",-71,"5a:c8:97:86:11:b2",6,-7)
+CWLAP:(3,"TREES-PC_Network",-82,"14:d6:4d:2f:99:b2",6,-24)
+CWLAP:(3,"UPC248562381",-92,"5c:a3:9d:82:d6:58",11,-57)

OK
AT+CWJAP="Milkrun","mypass"

WIFI CONNECTED
WIFI GOT IP

OK


Example AT 1.5.4 firmware:

Code: Select all

ready
AT+GMR

AT version:1.1.0.0(May 11 2016 18:09:56)
SDK version:1.5.4(baaeaebb)
compile time:May 20 2016 15:31:17
OK
AT+CWMODE=1


OK
AT+CWLAP


OK
AT+CWJAP="Milkrun","mypass"

WIFI DISCONNECT
+CWJAP:3

FAIL


ESP details from esptool.py:

Code: Select all

MAC address from OTP ROM:
esptool.py v1.0.2-dev
Connecting...
MAC: 18:fe:34:d3:94:93

Chip ID from OTP ROM:
esptool.py v1.0.2-dev
Connecting...
Chip ID: 0x00d39493

SPI flash manufacturer and device ID:
esptool.py v1.0.2-dev
Connecting...
Manufacturer: e0
Device: 4016

ESP_Faye
Posts: 1642
Joined: Mon Oct 27, 2014 11:08 am

Re: ESP-12(E?) On NodeMcu, wifi works on SDK NONOS until 1.3.0, doesn't work on 1.4.0 and higher

Postby ESP_Faye » Tue May 24, 2016 11:30 am

Hi,

Please download the bin files into flash using ESP Flash Download Tool.

If your problem is still unsolved, please provide the captured picture of ESP Flash Download Tool while downloading.

Thanks for your interest in ESP8266 !

cranphin
Posts: 8
Joined: Sun May 22, 2016 7:52 am

Re: ESP-12(E?) On NodeMcu, wifi works on SDK NONOS until 1.3.0, doesn't work on 1.4.0 and higher

Postby cranphin » Tue May 24, 2016 11:17 pm

Hi!

Thank you for your attention :)

I have done as you requested (of course I have tried this before ;) ), and it did not resolve the problem sadly..

Screenshots as requested:
flash1.jpg

flash2.jpg

flash3.jpg


Log after flashing:

Code: Select all

ready
AT


OK
AT+GMR

AT version:1.1.0.0(May 11 2016 18:09:56)
SDK version:1.5.4(baaeaebb)
compile time:May 20 2016 15:31:17
OK
AT+CWMODE?

+CWMODE:2

OK
AT+CWMODE=1


OK
AT+CWLAP


OK
AT+CWJAP?

No AP

OK
AT+CWJAP="Milkrun","mypass"

WIFI DISCONNECT
+CWJAP:3

FAIL

ESP_Faye
Posts: 1642
Joined: Mon Oct 27, 2014 11:08 am

Re: ESP-12(E?) On NodeMcu, wifi works on SDK NONOS until 1.3.0, doesn't work on 1.4.0 and higher

Postby ESP_Faye » Fri May 27, 2016 11:09 am

Hi,

I tested it as your way, but I can not reproduce your problem.

Could you test it with another hardware module ?

cranphin
Posts: 8
Joined: Sun May 22, 2016 7:52 am

Re: ESP-12(E?) On NodeMcu, wifi works on SDK NONOS until 1.3.0, doesn't work on 1.4.0 and higher

Postby cranphin » Fri May 27, 2016 11:42 pm

Hi!

I have two plain ESP-12's on simple breakout boards, I've run the same tests on those, and they don't show this symptom.
I only see this problem on the NodeMcu 1.0 which likely has a ESP-12E on it.

I think it might not be 'just' a faulty module though, because version 1.3.0 and lower SDK works fine, only 1.4.0 and higher SDK give an issue.
So some change in the SDK 1.4.0 (and higher) is triggering this, in combination with this specific hardware.
And it suggests that this could be solved with just a software fix :)

I've tested adding capacitors to the power supply lines, and different power supplies, so I don't think it's a power issue.

Is there anything I can test/log/debug that would help to figure out where this issue comes from? :)

Who is online

Users browsing this forum: No registered users and 2 guests