exxos's Atari, Amiga & retro forum

It may be because you need to change the Baud rate to 115200 on the Amiga side to match the EPS8266 (Default 115200)
So open a text editor and go to to> ENVARC:Sana2/slip0.config, just open it with a text editor to change it to 115200

Also if you flashed the ESP2866 correctly ? because when you boot the CD32 the Blue LED will stay on permenantly, but when you have telneted into it and have put your router details in and connected to the wifi , then when you boot the CD32 the blue LED will stay on for a few seconds then go out

supaduper wrote: 18 Jun 2020 10:05 It may be because you need to change the Baud rate to 115200 on the Amiga side to match the EPS8266 (Default 115200)
So open a text editor and go to to> ENVARC:Sana2/slip0.config, just open it with a text editor to change it to 115200

I am assuming that he's run my script? no?

terriblefire wrote: 18 Jun 2020 10:36

supaduper wrote: 18 Jun 2020 10:05 It may be because you need to change the Baud rate to 115200 on the Amiga side to match the EPS8266 (Default 115200)
So open a text editor and go to to> ENVARC:Sana2/slip0.config, just open it with a text editor to change it to 115200

I am assuming that he's run my script? no?

Hopefully Steve but I know some people have got the earler unrevised script, so I am just putting this info out there for them to check thats all

Mark

terriblefire wrote: 18 Jun 2020 08:27 the telnet should be to 192.168.240.1 7777 not 192.168.240.1,7777

If he is using DC Telnet to telnet into the ESP module, it needs a comma between IP and port number...

matt020 wrote: 18 Jun 2020 11:25

terriblefire wrote: 18 Jun 2020 08:27 the telnet should be to 192.168.240.1 7777 not 192.168.240.1,7777

If he is using DC Telnet to telnet into the ESP module, it needs a comma between IP and port number...

I had assumed everyone would use the amitcp telnet client but ok. i've seen clientstry to resolve "192.168.240.1,7777" which would be bad.

For me on the TF360.. flashed firmware, install roadshow, ran script, ping 192.168.240.1 ... works. Dont know how it could be made easier.

terriblefire wrote: 18 Jun 2020 11:30

matt020 wrote: 18 Jun 2020 11:25

If he is using DC Telnet to telnet into the ESP module, it needs a comma between IP and port number...

I had assumed everyone would use the amitcp telnet client but ok. i've seen clientstry to resolve "192.168.240.1,7777" which would be bad.

For me on the TF360.. flashed firmware, install roadshow, ran script, ping 192.168.240.1 ... works. Dont know how it could be made easier.

Yeah, well we dont know what he is using, but when you see someone add a comma between the IP and the port, its often a DC Telnet thing.

You just know he's gunna say he's not using DC Telnet now and prove me totally wrong....

I've pretty much copied my TF330 settings to TF360 but stepped down thenbaud rate to 115200. Will probably try to step it down a bit more since if I try to browse or use wget it locks up and crashes in seconds. Might try another PSU too.

Used script (did not have to comment out anything unlike on the Getting CD32 online Guide).
Blue light (ESP) flickers on initial CD32 power on then goes out.
Using DC Telnet.
Ping results - 12 packets sent, none recieved.
Firmware flashing on my ESP-01S the issue? I can try via the wife's linux laptop.
Thanks

Higgy wrote: 18 Jun 2020 13:39 Used script (did not have to comment out anything unlike on the Getting CD32 online Guide).
Blue light (ESP) flickers on initial CD32 power on then goes out.
Using DC Telnet.
Ping results - 12 packets sent, none recieved.
Firmware flashing on my ESP-01S the issue? I can try via the wife's linux laptop.
Thanks

Like I said a few posts back, if you have flashed the ESP8266 correctly then when you boot it on the CD32 the blue led will stay on permanently, only when you have entered your router details will the Blue led come and go out after a few seconds on boot

Most problems from what I see is not installing the software , but flashing the EPS8266 correctly, that`s why I use a raspberry pi and a dedicated ESP-01 programmer as there are some programmers out there that you have to hack for it to work

Higgy wrote: 18 Jun 2020 13:39 Used script (did not have to comment out anything unlike on the Getting CD32 online Guide).
Blue light (ESP) flickers on initial CD32 power on then goes out.
Using DC Telnet.
Ping results - 12 packets sent, none recieved.
Firmware flashing on my ESP-01S the issue? I can try via the wife's linux laptop.
Thanks

After flashing the firmware, the blue light on the ESP should be on solid... until WiFi settings are put in, then it all changes.

Once flashed correctly, and wifi settings are set on the ESP, the blue light will remain on for a couple of seconds until it connects to the WiFi access point, then the blue light goes out.

If you flash the firmware, and are getting a quick flicker of blue light only, something didn't go right with the flash