exxos's Atari, Amiga & retro forum

I strongly recommend using slattach after you flash the ESP module and set your wifi settings from linux/macos.

Self-flagellation has taken place :o Mistake - schoolboy error downloading SLIP firmware. Now corrected. I was flashing cr*p before.

Next issue. My SSID is in capitals. This seemed to give DCTelnet a 'computer says no'. I was not going to change my SSID name so ended up using the other AMIGA telnet program Steven mentioned.
That accepted the implausible situation of having a SSID in capital letters :D (I guess there might be an installation error in DCTelnet, especially when everyone else tells me their SSID is in capitals and set ssid worked ok :oops: )

Any ho. Now I am on the web. Off to download some more 'Klondike card sets' :o ;) Cheeers 8-)

Mid-summer festivities are over so I had a chance to look at the TF360 wifi issue again. I got it to work at 38400 baud which is somewhat less than the 216000 baud the TF330 achieves. I tried different CD32s and CPUs and a bigger stack as well as alternative slip drivers. Perhaps I should try CPU caches or resolder the ESP header as I would imagine this means an issue with interrupts or a high error rate.

sugar wrote: 22 Jun 2020 09:54 Mid-summer festivities are over so I had a chance to look at the TF360 wifi issue again. I got it to work at 38400 baud which is somewhat less than the 216000 baud the TF330 achieves. I tried different CD32s and CPUs and a bigger stack as well as alternative slip drivers. Perhaps I should try CPU caches or resolder the ESP header as I would imagine this means an issue with interrupts or a high error rate.

My 360s all work fine at 115200. I've no intention of trying them with anything else.

terriblefire wrote: 22 Jun 2020 09:58

sugar wrote: 22 Jun 2020 09:54 Mid-summer festivities are over so I had a chance to look at the TF360 wifi issue again. I got it to work at 38400 baud which is somewhat less than the 216000 baud the TF330 achieves. I tried different CD32s and CPUs and a bigger stack as well as alternative slip drivers. Perhaps I should try CPU caches or resolder the ESP header as I would imagine this means an issue with interrupts or a high error rate.

My 360s all work fine at 115200. I've no intention of trying them with anything else.

Yes but my issue is that I can't get the TF360 to run at 115200 nor 57600 but only 38400 or under. The TF330 performance was just for comparison with the same hardware but a different TF.

sugar wrote: 22 Jun 2020 10:09

terriblefire wrote: 22 Jun 2020 09:58

My 360s all work fine at 115200. I've no intention of trying them with anything else.

Yes but my issue is that I can't get the TF360 to run at 115200 nor 57600 but only 38400 or under. The TF330 performance was just for comparison with the same hardware but a different TF.

There is no hardware difference for this part between TF330 and TF360.

terriblefire wrote: 22 Jun 2020 11:32

sugar wrote: 22 Jun 2020 10:09

Yes but my issue is that I can't get the TF360 to run at 115200 nor 57600 but only 38400 or under. The TF330 performance was just for comparison with the same hardware but a different TF.

There is no hardware difference for this part between TF330 and TF360.

Actually I was a bit imprecise with this. I can set up a network connection at 115200 and use ping and get network time but wget and Ibrowse freeze quickly at this speed. I'm using the latest Roadshow and a CF from Superduper.

That sounds like maybe a noisy line.. Clean the edge connector contacts and try again?

terriblefire wrote: 29 Jun 2020 19:32 That sounds like maybe a noisy line.. Clean the edge connector contacts and try again?

Gave them a rub and a rinse but didn't seem to change the behaviour. It's kinda quirky since I did a wget on a file that wasn't on aminet and it crashed after getting the 404.
I realized I see CF card access on my screen as dim noise. I guess I should try another CF card and recheck the PSU.

i'm not seeing it myself but im not doing masses with the network connection at the moment.