Getting WFI Working on TF3xx with ESP Module

[PhilC]

Thank you @E-Penguin , i'll look forward to the guide.

[terriblefire]

After spending a long evening on this yesterday I finally got it working. I'm going to write up a guide. I'll share it here.

one thing; the below line isn't needed with Roadshow (v1.12 at least) and causes an error. It still works, but should be removed

Code: Select all

echo >>Devs:NetInterfaces/Slip "interface=Slip"

Compare with the other examples in NetInterfaces; they don't have the "interface=" line.

My version broke without this line. Latest version.

[E-Penguin]

My version broke without this line. Latest version.

I get 'unknown keyword "interface"' when I leave it in. Ordinarily this occurs during boot so you don't see it.

Untitled.png

Just checked, I'm actually on Roadshow 1.13. As it still works I guess it's not a big deal either way.

[E-Penguin]

Thank you @E-Penguin , i'll look forward to the guide.

Wait no longer, here it is!



I've given this thread a credit as the main source of inspiration. If I've missed anything or more info is needed somewhere please let me know

[matt020]

Reading through the how-to guide and it looks good!

As you will read on the previous 2-3 pages here on this forum, I had big issues installing firmware onto the device. So far, that has been the greatest challenge. Where I got stuck was: downloading the two .bin files from git hub by right clicking and "Save as", this didnt work. As Stephen pointed out, I had to download the repo as a lot, a package, extract the zip and in there were two bin files of different sizes.

Secondly, esptool was unsucessful, even when using the correct bin files. In the end, I used NodeMCU and selected DOUT as suggested on a previous page. Only then did the flash work for me.

I would also add after flashing what to expect from the ESP8266. In my case, I could tell the flash finally worked because when I powered it up, the blue LED was on solid. Once I set the SSID and password, after half a min and it connected to the wifi network at home, the LED light goes out. I would cover off on this, so the user knows what to expect, so they know when theyve had a successful flash.

I think a user guide either aims at dummies or experts, and not in between. If its in between (and cuts out small points) you lose the dummies, and you bore the experts.

I really must say, this is not a criticism by any means! You've done what I only wish I could do (make user guide), I just think, a few things could be added. Think of the person who has zero experience and is using your guide during their *very experience* with the ESP and flashing.....

Cover off:
* Correct downloading of bin files.
* If using esptool, how do you use it in Windows? What the heck is Python?
* LED lights on the ESP, what do i expect if the flash is sucessfull?

Cheers,
Matt.

[E-Penguin]

Thanks, good points. I'll make an update!

On the topic of downloading, you can't use save-as in the browser but there's a download button that would let you just get the esp firmware. I'll elaborate this evening.

[matt020]

Thanks, good points. I'll make an update!

On the topic of downloading, you can't use save-as in the browser but there's a download button that would let you just get the esp firmware. I'll elaborate this evening.

Yep, but I didnt know this (I dont think its mentioned *anywhere* except by Stephen!!) and this caused me massive issues! massive!

[matt020]

Update, with a problem.

In a WinUAE set up, I have installed MiamiDX, and have a connection. I can ping and connect to anything in my home network (10.0.0.x)

But I can't ping or talk to anything outside of my home connection. I get no ping replys. I get no connections. Nada.

If i use the term "double NAT", am I on the right path as to what a problem might be? My broadband modem is doing NAT, then the ESP is doing NAT, and this could be why i cant access the outside world?

This is all within WinUAE at the moment...

[terriblefire]

Update, with a problem.

In a WinUAE set up, I have installed MiamiDX, and have a connection. I can ping and connect to anything in my home network (10.0.0.x)

But I can't ping or talk to anything outside of my home connection. I get no ping replys. I get no connections. Nada.

If i use the term "double NAT", am I on the right path as to what a problem might be? My broadband modem is doing NAT, then the ESP is doing NAT, and this could be why i cant access the outside world?

This is all within WinUAE at the moment...

There are so many possibilities. Its most likely to be a route issue but who knows.

This thread is pretty much about Roadshow and a TF3xx, not WinUAE + MiamiDx.

[supaduper]

LoL If I can do it then anyone can do it, finally got my TF330 on line :)

Used the info from Steve and Penquins guides, but I had to some hiccups it would not run the Steves script it stopped at lha error so the way round it was to unLHA the file beforehand and dump it in RAM and remove the LHA line in the script and it would run the script then

Also I used DCtel_15 from aminet to telnet into the esp device and I found that can be a flakey program, and beware you must hit the spacebar once before inputting any commands at the CMD prompt..so basically one space after the CMD> .

Also had a little problem at first programming the esp and found it was the shite programmer I bought luckily I had also bought a switchable one so no mistakes, just set it to prog and your done :)

And last , watch out for some of these esp boards as the first one was duff again I always buy a few incase of bad ones, that`s how I found it was faulty, replaced with another, flashed it on the trusty raspberrypi and away with the mixer.happy days ! :)

TF330 online.jpg