Getting WFI Working on TF3xx with ESP Module

[alenppc]

nice work. :) This is exactly what i had in mind when i put the ESP header on there.

I have ordered some of these modules also. It will be a while till I get them but I am curious to try. Thanks for all the effort.

[matt020]

An ESP8266 arrived today, but I have a problem.

I can flash it, with both .bin files, and when I remove GND from GPIO0, well, not much more happens after that. The blue light isnt on, I cant telnet to it using slattach in linux.

Im using WIndows to flash it. Esptool doesnt like the parameters I give (Im using the example provided here https://github.com/martin-ger/esp_slip_ ... d-flashing).

But I can write the firmware to it (more than once) and it flashes and whirrs during this process. But then, no activity.

Any help or suggestions?

[terriblefire]

Any help or suggestions?

Only flashes when it powers on.

[matt020]

Along with grounding GPIO0, is anyone having to ground RST (reset) on the ESP8266 to program/flash it?

[terriblefire]

Along with grounding GPIO0, is anyone having to ground RST (reset) on the ESP8266 to program/flash it?

I used a USB programmer with a switch to put it into programming mode. It needs to be started up with it switched in that mode and then powered down and started again in non-programming mode

[matt020]

Ok,

I am in fear of this becoming a one sided thread, but Im not getting any response from the ESP8266 after I flash it and this is what I have done:

Flashed the ESP8266 with both 0x00000.bin at addresss 0x00000, and 0x10000.bin at address 0x10000
I did this in Windows and appear to have been successful.

I then move to Debian linux, and do this:
sudo slattach -L -p slip -s 115200 /dev/ttyUSB0&
sudo ifconfig sl0 192.168.240.2 pointopoint 192.168.240.1 up mtu 1500

and no errors. But I telnet to 192.168.240.1 7777 and I get "Connection time out".

I can't ping 192.168.240.1, 100% packet loss.

When I plug in the ESP8266 and FTDI module via USB cable, I get flickers of lights on both devices, for a second or so. Then no more activity is ever seen on the ESP8266.

If the advice is to flash the ESP in Linux..... Esptool in Debian just does not like the parameters I throw at it, using the examples on https://github.com/martin-ger/esp_slip_router and the basic how-to guide on A1K.org. I get told there is an addressing error with the 0x00000 and 0x10000

Thoughts, opinions, etc?

[terriblefire]

In windows... connect to the serial port at 115200 with the ESP module removed from the header using putty or whatever is to hand..

Plug it in live..

You should see about 500 bytes of garbage if its programmed correctly.

[theq]

@matt020 Did you program the ESP in DOUT-mode and verified that it successfully uploaded the firmware?

[matt020]

@matt020 Did you program the ESP in DOUT-mode and verified that it successfully uploaded the firmware?

DOUT? Nah I was using defaults... one app had DIO as default (ESP8266 DOWNLOAD TOOL V3.6.8) and the other QIO (NodeMCU).
Im guessing I should change to DOUT huh :) Not sure how to verify with each of those apps however.

[dalek]

I then move to Debian linux, and do this:
sudo slattach -L -p slip -s 115200 /dev/ttyUSB0&
sudo ifconfig sl0 192.168.240.2 pointopoint 192.168.240.1 up mtu 1500

and no errors. But I telnet to 192.168.240.1 7777 and I get "Connection time out".

...
Thoughts, opinions, etc?

Sounds like you are still in boot/programming mode. When reconnecting the device from windows to linux, do you remove the connection from GND to GPIO0?

What module do you have? ESP-01S?

I just programmed two in ubuntu using the "esptool.py --port /dev/ttyUSB0 write_flash -fs 8m 0x00000 firmware/0x00000.bin 0x10000 firmware/0x10000.bin" command with esptool.py v2.8. slattach worked fine after unplugging, removing the GPIO0 pulldown and reconnecting.

Do you also have CH_PD pulled high?