Jump to content

Search the Community

Showing results for tags 'SIO'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Atari Systems
    • Atari General
    • Atari 2600
    • Atari 5200
    • Atari 7800
    • Atari Lynx
    • Atari Jaguar
    • Atari VCS
    • Dedicated Systems
    • Atari 8-Bit Computers
    • Atari ST/TT/Falcon Computers
  • Classic Consoles
  • Classic Computing
  • Modern Consoles
  • Gaming General
  • Marketplace
  • Community
  • Community
  • Game Programming
  • Site
  • PC Gaming
  • The Club of Clubs's Discussion
  • I Hate Sauron's Topics
  • 1088 XEL/XLD Owners and Builders's Topics
  • Atari BBS Gurus's Community Chat
  • Atari BBS Gurus's BBS Callers
  • Atari BBS Gurus's BBS SysOps
  • Atari BBS Gurus's Resources
  • Atari Lynx Programmer Club's CC65
  • Atari Lynx Programmer Club's ASM
  • Atari Lynx Programmer Club's Lynx Programming
  • Atari Lynx Programmer Club's Music/Sound
  • Atari Lynx Programmer Club's Graphics
  • The Official AtariAge Shitpost Club's Shitty meme repository
  • The Official AtariAge Shitpost Club's Read this before you enter too deep
  • Arcade Gaming's Discussion
  • Tesla's Vehicles
  • Tesla's Solar
  • Tesla's PowerWall
  • Tesla's General
  • Harmony/Melody's CDFJ
  • Harmony/Melody's DPC+
  • Harmony/Melody's BUS
  • Harmony/Melody's General
  • ZeroPage Homebrew's Discussion
  • Furry Club's Chat/RP
  • PSPMinis.com's General PSP Minis Discussion and Questions
  • PSPMinis.com's Reviews
  • Atari Lynx 30th Birthday's 30th Birthday Programming Competition Games
  • 3D Printing Club's Chat
  • Drivers' Club's Members' Vehicles
  • Drivers' Club's Drives & Events
  • Drivers' Club's Wrenching
  • Drivers' Club's Found in the Wild
  • Drivers' Club's General Discussion
  • Dirtarians's General Discussion
  • Dirtarians's Members' Rigs
  • Dirtarians's Trail Runs & Reports
  • Dirtarians's Wrenching
  • The Green Herb's Discussions
  • Robin Gravel's new blog's My blog
  • Robin Gravel's new blog's Games released
  • Atari Video Club's Harmony Games
  • Atari Video Club's The Atari Gamer
  • Atari Video Club's Video Game Summit
  • Atari Video Club's Discsuuions
  • Star Wars - The Original Trilogy's Star Wars Talk
  • PlusCart User's Bug reports
  • PlusCart User's Discussion
  • DMGD Club's Incoming!
  • DASM's General
  • AtariVox's Topics
  • Gran Turismo's Gran Turismo
  • Gran Turismo's Misc.
  • Gran Turismo's Announcements
  • The Food Club's Food
  • The Food Club's Drinks
  • The Food Club's Read me first!
  • The (Not So) Official Arcade Archives Club's Rules (READ FIRST)
  • The (Not So) Official Arcade Archives Club's Feedback
  • The (Not So) Official Arcade Archives Club's Rumor Mill
  • The (Not So) Official Arcade Archives Club's Coming Soon
  • The (Not So) Official Arcade Archives Club's General Talk
  • The (Not So) Official Arcade Archives Club's High Score Arena
  • Adelaide South Australia Atari Chat's General Chat & Welcome
  • Adelaide South Australia Atari Chat's Meets
  • Adelaide South Australia Atari Chat's Trades & Swaps
  • KC-ACE Reboot's KC-ACE Reboot Forum
  • The Official Lost Gaming Club's Lost Gaming
  • The Official Lost Gaming Club's Undumped Games
  • The Official Lost Gaming Club's Tip Of My Tounge
  • The Official Lost Gaming Club's Lost Gaming Vault
  • The Official Lost Gaming Club's Club Info
  • GIMP Users's Discussion


There are no results to display.

There are no results to display.


  • AtariAge Calendar
  • The Club of Clubs's Events
  • Atari BBS Gurus's Calendar

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start










Custom Status



Currently Playing

Playing Next

Found 19 results

  1. Hi, Pretty much all of the logic level shifters I have seen can shift 4 signals, and also connect Ground and +5volts (so 6 connections in total). The diagrams for the designs I have seen also connect Data In, Data Out and Command, but that leaves 1 signal unused. Has any made a mod/interface which connects up an additional SIO connector pin, e.g. Audio In, etc.?
  2. Hi, I have written a short assembler routine that allows BASIC programs to use SIO. The SIO Device Control Block at $300 needs to be set up correctly in BASIC, then the assembler routine called with a USR statement. I've made a GitHub repo for it at https://github.com/e474/USRSIO - this also includes an ATR with the assembled code, and a short BASIC program showing how to load and use the assembler. This is the first git repo I have worked with/published, so I am not 100% sure I have done so correctly, though I haven't found any bugs with it yet. Please let me know if you have any feedback. The code was written with the help of WUDSN and ATASM on Linux. Hope this helps anyone interested in this subject.
  3. Hi All, I'd struggled to find a good or decent cable (not to stiff, and not too thin copper conductors) for a home made SIO cable. I had 3d printed a couple of SIO connectors and I also have a couple of PCBs for a poorman SIO version, but no luck to find a cable with 13 conductors (I don't need 100m) Do you recommend something you guys have used before?.. obviously good price (for someone in US). Thanks a lot
  4. I've been having a weird SIO problem that I'm hoping someone might have some insight into. The symptom of the problem is this. The Atari will attempt to read a sector (or some other SIO operation). There is about a 70% chance that it will succeed, but the other 30% it will sit for the timeout period (a few seconds) and then retry the sector read. I've seen a sector fail to read 3-4 times in a row before it succeeds and then a bunch will succeed in a row. The aspeqt log looks like this: [Disk 1] Get status. [Disk 1] Read sector 1 (128 bytes). [Disk 1] Read sector 2 (128 bytes). [Disk 1] Read sector 3 (128 bytes). [Disk 1] Read sector 4 (128 bytes). [Disk 1] Read sector 5 (128 bytes). [Disk 1] Read sector 6 (128 bytes). [Disk 1] Read sector 7 (128 bytes). [Disk 1] Read sector 8 (128 bytes). [Disk 1] Read sector 9 (128 bytes). [Disk 1] Read sector 10 (128 bytes). [Disk 1] Read sector 11 (128 bytes). [Disk 1] Read sector 12 (128 bytes). [Disk 1] Read sector 13 (128 bytes). [Disk 1] Read sector 14 (128 bytes). <-- this is the failed command [Disk 1] Read sector 14 (128 bytes). [Disk 1] Read sector 15 (128 bytes). ...etc... So aspeqt isn't noticing a problem; rather the system just isn't seeing the sector come in for some reason. Here's the history of the problem. It all started when I dropped in a PAL ANTIC for playing some PAL games. At the time I figured the occasional glitch might be due to timing differences so I didn't think anything of it. After a few weeks of not using my system, I received and installed one of mega-hz's stereo boards (in the process I moved my OS ROM IC to the BASIC spot and removed BASIC, because in a 600XL the board doesn't quite fit). I booted up and everything seemed to work great on the first try, *except* that this SIO problem was still there and in fact was quite a bit worse than it was before! Figuring I had banjaxed something (SIO = POKEY = seems like it might have been related to the stereo board install), I tried reverting the upgrade and there was no change - the SIO problem was definitely still there. I swapped my ANTIC out for the original NTSC one again hoping that this would resolve the issue but it did not. I checked and rechecked the board for broken traces along every path I could find, even tried different POKEYs to no avail. Then I made a quite interesting discovery. If I boot in Aspeqt using the "boot XEX" feature, it consistently works fine (after it loads the initial few sectors containing the boot loader). This is interesting to me because the OS loads sectors at 19200 bps, but the Aspeqt XEX booter uses 57600 bps (I believe) to transmit the XEX data. So maybe the problem is actually in the OS ROM somehow, though I don't see how since it passes self-test which I think does a checksum test. My other thought is that maybe IRQs are not being handled right somehow since (I think) the OS SIO routine is IRQ-driven, whereas high-speed boot loaders aren't? Anyone have any thoughts about what I should try next? I was thinking about writing a test program pair for the atari and linux which transmits a data stream and checks for problems, and maybe just swapping ICs (SALLY gets a little warm but I think that's her normal behavior).
  5. I know this is such a stretch but would there be any possible way to connect my Atari XF551 floppy disk drive to my Windows XP computer? I'd like to transfer Atari files to and from my PC. I really can't get an internal 5 1/4 floppy drive for the XP because they are just too pricey.
  6. AbeOwitz

    SIO Latch Open

    From the album: AbeOwitz's Stuff

    Errors in SIO protocol when latch is open during DIR command.
  7. Does anyone know how rigidly the SIO timing specifications in the OS manual are followed in practice? I'm working on a high-speed SIO routine and am trying to determine what delays are required, since some of the delays are annoying to hit with variable DMA involved. The one I'm particularly interested in is the t2 delay from last command byte to command line deassert. This is specced as 650-950 microseconds, but it looks like the OS routine violates this by only waiting 400us: T-0.000403 | A=00 X=FE Y=00 S=F2 P=32 | EAA7: F0 F5 BEQ $EA9E + IRQ interrupt ... T-0.000002 | A=A0 X=FE Y=31 S=F0 P=B0 | EB11: A9 3C LDA #$3C T+0.000000 | A=3C X=FE Y=31 S=F0 P=30 | EB13: 8D 03 D3 STA PBCTL The actual delay is even lower in a gr.4 (IR mode screen, only 300us. I was tempted to use timers 1+2 in 15KHz for timeouts as it's easier to set up than OS timer 1 and I can hit delays up to four seconds that way, but now I'm not even sure I need to be that precise with the delays.
  8. I have been reading about all of the options for SIO and Cartridges. I have an SIO2PC-USB and it is great, but I have to switch back and forth between the Atari and my PC to change disks when needed. The carts have their own menus. I just had a thought. Could a cart be made with a cable connection to the SIO port so the combination could handle all file types and be totally controlled by the Atari? Pressing a button on the cart would bring up the menu to mount another file or load a .car file into the cart. Then exit back to your program to load the file or reset to run the .car. So, totally weird and not possible?
  9. Hello AtariAge community, I am hoping some of you could provide some insight into a problem I am having with my Atari 1050 floppy disk drive. For years the drive has worked seamlessly with my Atari 800 XL... but when I pulled it out and started it up just recently, I only got one successful boot out of it, and it hasn't worked since. I know this is rather open-ended, so I will provide some information on what I have tried so far. I cleaned the reader heads, so no problem there. I heard that the read arm is supposed to travel the full length of the read track upon initialization of the device. Whether this is correct or not, my device does not do this. It travels maybe a fourth of the way and then back. I tried the following program which I grabbed off of another forum: 5 GOSUB 1000 10 POKE 769,1 20 POKE 770,33 30 POKE 772,0:POKE 773,64 40 Z=USR(1536,58451) 50 ? "FORMAT STATUS ";Z 60 FOR R=1 TO 30 : POKE 778,R : POKE 779,0 70 POKE 772,0:POKE 773,64 80 POKE 770,82 90 Z=USR(1536,58451) 100 ? "READ SECTOR ";R;" STATUS ";Z 190 NEXT R 999 END 1000 A=1536:TRAP 1030 1010 DATA 104,104,133,213,104,133,212,32,17,6,132,212,169,0,133,213,96,108,212,0,-1 1020 READ D:POKE A,D:A=A+1:GOTO 1020 1030 RETURN This program formats the disk, then gives a status number in return. It then checks individual sectors from 1 to 30, and gives the read status. During the formatting process, the arm moved the full length of the floppy disk and appeared to be doing exactly what it should, however during the read phase, the disk drive reader arm did not move at all until the 21st sector or so, where it began to twitch with each sector read. Still every transaction with the drive returned a status of 144, which is a "Device Done Error" according to this website: http://page6.org/archive/issue_22/page_10.htm. "This error occurs when you have issued a valid command to the peripheral but the device is unable to carry it out" the page says. I have received a request from a friend to replace all electrolytic capacitors, because even if they do not burst, they are prone to drying up over time. Does anyone want to support or deny that statement? If so, is it possible that the caps dragged other more important (and harder to diagnose) components with them? Sorry for the load of information, but any help on where to start with this is greatly appreciated. Thanks, BitFracture
  10. When I turn on my machine now, I get a "bizzzz" sound about once every 3 seconds, and I assume, a blue screen (I say assume because the no-signal screen is blue on my TV as well) Other than blown capacitors, does anyone have suggestions on troubleshooting?
  11. The documentation for the 65C816 XL/XE OS shows a high-speed bit in the CIO table but I don't get whether it can be set up to support high-speed SIO like the Hiassoft patch, MyBios, etc., to allow faster booting and disk access with a SIO2SD when using regular DOS, LOAD, SAVE, etc. commands. Any ideas?
  12. From the album: AbeOwitz's Stuff

    SIO First command on startup. It requests status from disk D1:
  13. I know these cables are "easy" to make... but I'm not so skilled at that sort of stuff.... I've an 850 w/printer cable (no PS) up for trade?? Well... I bought a kit and made a splitter. Looks and works great.
  14. I am interested in making my own SIO2PC. I came across the FTDI Friend from Adafruit for $14.75. Would that board work? I see the signal logic level is 3.3V by default, but I think the Atari SIO port is 5V. If the logic levels are okay, then I should just be able to use jumper wire to connect the headers directly to pins on the SIO port, right?
  15. From the album: AbeOwitz's Stuff

    First set is status request. Second set asks for sector 1.
  16. Hi Everyone, I'm ~30 years late to the party but I finally bought my first Atari computer this week, the 800XL!! As a complete beginner to Atari and this whole scene I'm excited but also a little confused and would love some advice. The computer came with a 1010 Cassette deck (I've replaced the belts) and about 8 games on cassette - the computer and tape deck work fine but unfortunately none of the games load, I keep getting BOOT ERROR - so I haven't been been able to do anything on it yet The main purpose of this is for games, programming (basic and assembly) and the general fun of discovering what this thing can do. I have seen many great looking devices such as: sio2pc, sio2bt, sio2sd, Ultimate 1MB, Side2, Pokey Stereo Sound Where do I start, what should I get? importantly, who should I get these things from and what should I avoid? Please tell me which devices you have yourself, what you found the most and least useful and your recommendations. Thanks to everyone in advance - hopefully this post can help future noobs like me. All the best - I look forward to some good advice!
  17. I'm trying to get OSX 10.9 (mavericks) to recognize the SIO2PC/10502PC Dual device. The kext file is present, but not loaded after boot. I can load it. However I cannot seem to get OSX to create the /dev/tty.usbserial so the AspeQt, SIO2OSX, or SIOServer programs can use it. If I look in System Profiler I see the device on one of the USB ports. Whats the trick to getting OSX to see the device correctly?
  18. There is a new hardware for A8: SIO_FIFO. This device allows data transmission with up to 127kbps speed. Here is the movie with copying disk using this hardware, "US SECTOR COPIER 4" by E.Reuss and AspeQT emulator. SDX, IDE+ loader etc. also working at this baud rate. Form of device is small PCB between POKEY and mainboard. No cables, no solder (if there is a socket for POKEY on the MB). The device is yet in testing phase but will be available soon.
  19. While archiving my collection it hit me: That Banana Pi I use at the bi monthly Retro meeting here in the Netherlands can also make use of the trick that The Montezuma used to connect a Raspberry Pi as a disk drive for the Atari. Up until now I dragged along SIO2PC device(s). With the Raspberry Pi craze, several parties also wanted a piece of the pie. LeMaker came up with the Banana Pi, also a SoC, but with a little beefier specs, like gigabit ethernet, more RAM and a power switch. Another thing the Banana Pi has more of than the Raspberry Pi is four(!) UART interfaces. So, plenty of ways to connect to the SIO port. I picked the UART1, located on J12, as on the same row there is 3.3V and GND available, making it very easy to use a 4 pin connector I had lying around (an old CD Rom sound cable). The PinOut of the Banana Pi, as you can see J12 consist of 2 rows with 4 GPIO pins, the top four (2,4,6, being 3.3V, RXD, TXD, GND: Details of all pins: I haven't created a nice graphic representation of the connections, but the text version looks like this: Connect Banana Pi J12 pins 2,4,6,8 to a level converter at its LV side. On the HV side of the level converter, connect a 1N581[789] Diode between the level converter and pin 3 of the SIO port. The connections should match below matrix: *** Atari TO Level Shifter SIO 3 (Data IN) - DIODE (1N581?) - HV1 * Via diode (for example 1N581[789]) direction from Atari to the level shifter * SIO 5 (Data OUT) - HV2 SIO 10 (+5V) - HV SIO 4 (GND) - GND *** Level Shifter TO Banana Pi LV1 - J12 Pin 6 (TxD) LV2 - J12 Pin 4 (RxD) LV - J12 Pin 2 (+3,3V) GND - J12 Pin 8 (GND) As you may notice, I did not connect SIO 7 (COMMAND), it should not be needed when you use sio2bsd or Respeqt. You can use the software attached to these posts on the Banana Pi as well. Depending on the linux distribution you use, it could be that your UART is connected to something other than ttyS3, to be sure, put an ATR on the SD card and use the following script to check 1. whether your cable works, 2. what terminal the J12 UART is connected to: ### Note: this runs as user root. If you are not running as root user, run 'sudo su -' first. for DEV in {0..3}; do echo -e "\nTesting connection on ttyS${DEV}\n\n" sio2bsd -s /dev/ttyS${DEV} -f /root/atari/disks/demo/numen.atr done The output should be something like: Testing connection on ttyS0 D1: 769 sectors, 196480 bytes total, mounted on /root/atari/disks/demo/numen.atr PERCOM: trk 1, step 3, spt 769, heads 1, bps 256, flags 04 (SMALL-MFM-5.25INCH) PCLink directory filter allows lower case names Serial port: /dev/ttyS0 POKEY quartz 1781618.500000 Hz and HS Index 0 constant 7.186100 is assumed Default speed: HSINDEX=40 (19200 bits/sec.) Default turbo: HSINDEX=0 (123963 bits/sec.) User selected: HSINDEX=0 (123963 bits/sec.) Next, power on the Atari connected to the Banana Pi. If your cable works and the script arrived at the correct terminal, you should see something like: 0 -> 'S': $31, $53, $0000 ($84) ... 3 -> 'R': $31, $52, $0003 ($86) If not, on the Banana Pi terminal, press CTRL+C and reset the atari from the Self Test screen (at the READY prompt, type 'BYE' and at the green screen press RESET). If your machine doesn't boot for the selected floppy, check the connections between the Pi and the Atari, verify if the floppy file on the Banana Pi exists and can be accessed (sio2bsd will display an error if it can't open the .atr file). If you want to be really fancy, create a second cable and connect it to another UART and use the banana pi as a terminal for bbs access at the same time. Hope that you too can put that Banana Pi to good use now.
  • Create New...