a8isa1

Loading CONFIG.BAS externally wasn't successful. Timeout error communicating with #fujinet. Do I need an earlier firmware for this test? C version of SCANWIFI did work! However, wifi sensitivity must be low. Only found the two routers in the house. @tschak909, scanning gets stuck in a loop. It repeats the last access point in the list about every 2 minutes. Can't re-scan from that condition. I don't know how to troubleshoot what's going wrong with the disk boot function. Any suggestions? -SteveS

Are the messages flushed from the buffer at the start? I mean could they be queued to send as soon as the Atari connects? -SteveS

Thanks. I seem to be getting garbage sectors but don't have a means to intercept them. I either get lots of sectors in a steady stream but Antic goes crazy *OR* I get 2 I/O bleeps and then one weird sound and crash. The weird sound resembles one bang on bongo drums. (Yes, I know how crazy and pointless that description is but it is somewhat amusing to hear). It seems somehow I simply am getting incorrect boot sectors. My plan is to leave AUTORUN.ATR out of the build, run the wifi scanner from another source, plug in the #fujinet (homebrew) and see if it responds then. Can my problems stem from my insistence to stick with GPIOs 1 and 3? [EDIt] I do disable Serial.Swap() in the source. -SteveS

tschak909, could you please re-post your BASIC version of your wifi scanner on github or alter the C version to re-scan at the press of a key. I need to be able to try multiple times without cycling power or doing a RESET. I don't think I can use the one posted in [EDIT] in your #atariwifi thread. Line 290 has embedded ATASCII characters in the USR() parameters. -SteveS

tnfswrite works slightly better for loading disks. Sectors still load in spurts. k-disks (Ken Siders) don't work at all. I discovered MaPa's Millionaire game loads smooth as glass. No pauses after the transfers start. I think it's disabling Antic's DMA as the screen goes blank during loading. Perhaps this is a telling clue to my problems. I created a MyDOS 4.53/4 image. I was not able to save DOS files or other files. Error 163. -SteveS

all wifi here (unfortunately) -SteveS

hmm. I wonder... What might keep IP packets from being delivered? -SteveS

looks like I still have timing issues. Tail of Beta Lyrae took about 10 minutes to load. -SteveS

Got it working (with caveats). Changed DELAY_T5 to 1600 Works great with most ATRs (only 6 or 7 so far). Caveats: - Hates Ken Siders' 'k' disks. Three tried so far. 3 sectors, pause, 3 sectors then nothing. - for some other disks there's a long pause, 3 sectors transfer, longer pause, then the remaining sectors all transfer smoothly. - Other times 3 sectors transfer immediately, then long pause, 3 more sectors, then very long pause (maybe 15 seconds), then remaining sectors go quickly. -SteveS

Works when DEBUG is enabled but slowly compared to the tschak909's videos. Not at all when not enabled. No sectors transferred. Just *Atari raspberry* and then Self Test. -SteveS

No luck changing delayMicrosecond() values How important are the inline resistors? -SteveS

I have a new problem. Yesterday, I watched tschak909's latest video and realized my transfers are much slower, perhaps only 1/3 the speed. Trying to troubleshoot my earlier problem I enabled the debugging. When it occured to that I have no way to read data from GPIO 2. I tried to connect the USB cable. I didn't think I'd be able to see anything legible but I wanted to see if anything was happening. As you already know I did find something and it led to a solution. Back to my slow disk reads... I had forgotten to disable debugging. That's why it's running slow. However, I did finally disable it the disk loading doesn't work at all. Just Atari *raspberries*. Same results with two separate dev boards. When I re-enable debugging it starts working again. Any Suggestions? -SteveS

every one of mine were glued/cemented/or molded in I tried to dremel one out but my hands aren't steady enough. cut more metal than plastic =? -SteveS

Yep. Needed it. I'm using an older v0.9 NodeMCU dev board with 4MB of flash memory. The PCB is the size that was annoying for people with small breadboards. It's not bizarre only anticipated for a long, long time. Thanks to you and mozzwald for getting the ball rolling. Not to forget Espresif and Arduino IDE people. The hardware and the tool chains are amazing. -SteveS

Problem solved! Karateka booted! We have WiFi! I made this change to test #7 sketch. void ICACHE_RAM_ATTR sio_isr_cmd() -SteveS

Yep. I found it after I found the correct sketch I'm not having success. I don't understand what I'm seeing. I get this output from tnfsd (64-bit linux daemon) 192.168.1.221 is the address for my Nodemcu devboard If I use the USB cable this is what is appearing (at 19200 bps) Are there any special settings in the Arduino IDE that I need to make? -SteveS

Yes, mine has non-keyed card edge connectors. Back in 1983-1984 I made my own cables. Most of the IDC connectors I needed were obtainable at Radio Shack (which doesn't help you now). The 36-pin connector was a bit of trouble to find as was the ribbon cable. My floppy cable eventually failed due to my swapping it often between 3 pairs of floppy drives. In my parts pin I found an old PC AT (Clone) set of cables that were un-keyed. I unflipped the twist in the cable and reused the connector. I recently saw the 34-pin card connectors (non-keyed) on Ebay but didn't order any. I probably should. Here are a pair. Notes mention non-keyed. -SteveS

quick question. well 2 actually. no 3! Are Proceed and Interrupt needed for test #6? Will the project work with GPIOs 1 and 3 if I use Serial.swap()? My test setup currently is hardwired for those pins. TNFS? I need pointing in the right direction. I've been world's longest running linux n00b! -SteveS

It's actually odd that SWP would provide that SIO cable figure. Most people would use a normal Atari SIO cable, all 13 wires connected. I guess the description is in the manual for thoroughness. It's a long shot but the RAM and EPROM are socketed in the ATR8000 you might try reseating them. I wish I could offer more troubleshooting tips. Mine has never actually failed. I thought it did but those times were more examples of how the ATR8000 doesn't like to play nice with other SIO devices. -SteveS

As I said earlier the response to LPRINT should be simply "READY" With a disk drive connected and powered when you start the ATR8000 the head should cycle. If those aren't happening something is wrong with your cable or your ATR8000 TERM mode is for using a dumb terminal, a Lear Siegler ADM-31 or compatible as the console of the ATR8000, instead of using the ATARI. When an Atari is connected there's no need to change the jumpers. A special terminal emulator is used for running CP/M on the ATR8000 with the Atari being the console. Autoterm was supplied with the ATR8000. Claus Bucholz' (sp?) DT-80 can also be used. Omnivew/Omniview XE Operating System replacements have a built-in terminal emulator for the ATR8000. There was also an Autoterm-80. I can't recall if that became available through SWP or not. All terminal emulators for the ATR8000, except the original Autoterm, use software 80 column mode. -SteveS

I've done this once or twice but IDC connectors aren't meant to be reused. The cable will be weak where the connector was formerly attached. I think my current ATR8000 is such a cable. I didn't have many non-keyed connector lying around. I couldn't remove the key tabs from the keyed connectors. Check the drive in your XF551. If the connector is non-keyed you'll have to deal with the problem. -SteveS

The ATR8000 cannot access SIO based Atari disk drives, so no, you can't use an XF551 to boot CP/M. Also, no one has managed to make usable ATR8000 boot disks from image files, such as those from 22disk and teledisk. I believe one sector on one track is shorter than the other sectors, making copying problematical on a personal computer. ricortese (and others) documented the issue. However, once you have booted CP/M, with the necessary support files one can access data disks created from imaged created by the above mentioned utilities. The generated disks may work as is or a new disk definition may be required. I no longer remember how this done but it is part of the CP/M basics. Instructions should be easy to find. I believe, there was an addendum sheet to the ATR8000 CP/M Supplement. Fortunately for all ATR8000 owners sup8pdct (sp?) provided a workaround for not having CP/M bootdisks here. Now ATR8000 owners can create a boot disk and copy files over to it, and reconstruct a complete system disk. -SteveS

Lastic, congratulations on getting an ATR8000. (Sorry to hear about the travel adapter) I noticed your ATR8000 has one difference from mine. The card edge connectors on yours are keyed. There's a partial test you can do if you don't have disk drives connected. A printer is not necessary. In Atari BASIC type LPRINT. If you get a timeout error (138) then the ATR8000 is not responding. If you simply see "READY" then the print spooler function of the ATR8000 is running.

This appears to be the screen for which I had tweaked a driver but I never came across the white screen problem so perhaps there are differences. In case you missed it you'll find the driver here. Good luck with it! -SteveS

Gort -SteveS a8isa1_gort.xex