Jump to content
netbeui

SIO2USB with a FTDI basic breakout board

Recommended Posts

Hi everyone,

 

I'm trying to create a simple SIO2USB cable based on the instructions on this website:

 

http://www.stephens-home.com/sio2usb/

 

I recently purchased a FTDI Basic Breakout board (http://www.sparkfun.com/products/9716) and now discovered that my board is slightly different than the one on Stephen's website. On Stephen's site it instructs you to connect the Atari SIO cable to 4 headers: TX, RX, GND and RI (Transmit, Receive, Ground, Command). The board I purchased has inputs for GND, CTS, POWER, TXO, RXI and DTR.

 

I'm guessing the mapping would be as follows:

 

TX --> TXO

RX --> RXI

GND --> GND

RI --> ?

 

Does that sound correct and does anyone know what the RI (Command) would map to on my board?

Share this post


Link to post
Share on other sites

After looking at the board at SF, your breakout brd doesn't have RI from the chip pinned out. It does bring out CTS, which I do belive you can configure as the command line in some(all) SIO2PC SW. I'm pretty sure that Win810 allows you to set up the command line and AspeQt does (?). But you could also mod the board, by jumping pin 6(RI) to the header, but SSOP pins are SO very small! Proceed at your own risk :)

Van

Share this post


Link to post
Share on other sites

Thanks Van! I will definitely give AspeQt a shot. Looks like it should work, I downloaded it and found there are CTS and DTR handshake options in the preferences.

Share this post


Link to post
Share on other sites

maybe crossing the TX and RX line would be a good idea...

 

and AspeQt is all i ever use... (nothing wrong with APE, except it doesnt run on linux ;')

 

sloopy.

Share this post


Link to post
Share on other sites

TxO (from PC) => Atari Rx; RxI(from PC) <= Atari Tx. AspeQt can use RI, CTS or DSR (not DTR, its out from PC).

Van

Share this post


Link to post
Share on other sites

sloopy - I see the confusion. My mapping wasn't from the Atari to PC it was from the ports described on Steve's website to the ports avaiable on the board I purchased. I'm assuming Steve already crossed the lines as needed...

 

Van - thanks again for the quick response and clarification. I'm sure it will work once I've configured Aspeqt to use CTS as the handshake method

Share this post


Link to post
Share on other sites

sloopy - I see the confusion. My mapping wasn't from the Atari to PC it was from the ports described on Steve's website to the ports avaiable on the board I purchased. I'm assuming Steve already crossed the lines as needed...

 

Van - thanks again for the quick response and clarification. I'm sure it will work once I've configured Aspeqt to use CTS as the handshake method

 

without going into a lengthy explaination, the TX and RX labels can be referenced by a couple different methods (google: DCE DTE if you want more info) but i have some usb board that i chave to connect TX-TX and RX-RX and others that have to be done TX-RX and RX-TX...

 

never assume (etc...)

 

sloopy.

Share this post


Link to post
Share on other sites

for anyone else considering this... use this board from sparkfun...

 

http://www.sparkfun.com/products/718

(has proper connections for RI, and has been tried and verified working by people)

 

sloopy.

  • Like 1

Share this post


Link to post
Share on other sites

I've wired up the original board listed in Stephens' instructions using "CTS" before and it worked fine that way as well, using AspeQt.

Share this post


Link to post
Share on other sites

Though this doesn't apply to your board netbeui; the other SF board, the 718, ships set for 3.3V IO, which could cause a problem for the Atari's Rx (a TTL level of '1' = >2.5V but for 3.3V logic a '1' = 2.7V typ. Plus the drive current is 1mA @ 3.3V; where as, at 5V the chip will drive @ 2mA. This may be an issue for the Atari). There is a forum post at Spark Fun that describes resetting for 5V IO, http://forum.sparkfun.com/viewtopic.php?f=15&t=21234

Van

Share this post


Link to post
Share on other sites

Is it only me, or are more people getting rather confused by different interfaces with the same name?

 

Since 2007 Sio2USB is an interface created by ABBUC/RAF.

Now there is this Sio2USB from that side the topicstarter writes about.

Then there is Sio2PC with USB connector ... some people also do call that Sio2USB.

 

In my opinion this s*cks.

 

In my opinion the ABBUC/RAF version is the only REAL Sio2USB since that one is indeed SIO to USB (stick).

 

All other versions are still a Sio2PC where the pc connection is USB.

 

An original Sio2PC isn't called a Sio2RS232 right? So why would we call a Sio2PC with USB connection suddenly a Sio2USB?

 

The word after the "2" should refer to the (storage)device.

 

Sio2IDE -> the Sio is talking to an IDE drive.

Sio2SD -> the Sio is talking to a SD drive.

Sio2USB -> the Sio is talking to an USB drive.

Sio2PC -> The sio is talking to a PC.

 

That all makes sense.

  • Like 5

Share this post


Link to post
Share on other sites

TxO (from PC) => Atari Rx; RxI(from PC) <= Atari Tx. AspeQt can use RI, CTS or DSR (not DTR, its out from PC).

Van

 

In my experience, DSR is more reliable than using RI. The load .xex option of Aspect didn't work in high-speed (normal speed was OK) using RI, but it worked without problems with DSR.

 

I did not get APE to work with the FTDI chip. Has someone experience with APE and FTDI chip USB->serial communication?

 

Robert

Share this post


Link to post
Share on other sites

Is it only me, or are more people getting rather confused by different interfaces with the same name?

 

Since 2007 Sio2USB is an interface created by ABBUC/RAF.

Now there is this Sio2USB from that side the topicstarter writes about.

Then there is Sio2PC with USB connector ... some people also do call that Sio2USB.

 

In my opinion this s*cks.

 

In my opinion the ABBUC/RAF version is the only REAL Sio2USB since that one is indeed SIO to USB (stick).

 

All other versions are still a Sio2PC where the pc connection is USB.

 

An original Sio2PC isn't called a Sio2RS232 right? So why would we call a Sio2PC with USB connection suddenly a Sio2USB?

 

The word after the "2" should refer to the (storage)device.

 

Sio2IDE -> the Sio is talking to an IDE drive.

Sio2SD -> the Sio is talking to a SD drive.

Sio2USB -> the Sio is talking to an USB drive.

Sio2PC -> The sio is talking to a PC.

 

That all makes sense.

 

personally i call it a sio2pc-usb, just to differentiate it from the rs-232 version, and if i need to specify the RS-232 then i refer to it as sio2pc-serial.

 

and if you ever see me call it sio2usb, you have full right to whack my knuckles with a ruler as i have done so to people who call a sio2pc-usb a sio2usb...

 

oh, yeah and sometimes i call them 'Pac-Man'! ;')

SIO2PCusb.png

 

sloopy.

Share this post


Link to post
Share on other sites

I might have to get me one of these breakout boards to fit in my 1064 case.

Some people put it into a SIO plug. -> http://www.abbuc.de/phpBB3/viewtopic.php?f=15&t=6102

 

Just to add: it works perfect at POKEY divisor 0 with my A8s and SDX, IDE V2 or any other A8 boot disk image from AspeQt. For historical reasons I connected to RI.

 

THIS:

post-16281-0-15024500-1313051069_thumb.jpg

 

.....from the abbuc page you linked to above, is one of the coolest Atari things I've seen! HA HA!

 

Now I want the entire Sdrive to fit in there, and have a micro-SD slot in the end of the SIO plug, where the USB connector is, on this one!

Share this post


Link to post
Share on other sites

Nice! I can see this completely replacing any other solution currently on the market.

If somebody doesn't own a SIO2PC in any form, yes, this is the currently most recommendable solution. If you already have a PBI driven harddrive etc., this is nice to have but no need to have.

 

The real put through of data is not much more than using a standard SIO2PC with 3xSIO speed. POKEY 0 is 10KByte/s raw transfer and ca. 8.9KByte/s real transfer on 512 byte images with DMA OFF. DMA ON and 256 byte sectors are slower of course. Depending on the settings PBI IDE is 10 to 15 times faster.

 

What I admire most is the integration of real SIO high speed into SDX.

Edited by GoodByteXL

Share this post


Link to post
Share on other sites

just to mention it:

 

SpartaDOS X users do not need anything else to take advantage of these FTDI breakout modules.

 

SDX generally allows SIO2PC connections down to POKEY divisor 3.

 

Additionally utilizing the KMK/JZ IDE v. 2.0 Plus enables the user to run the connection at POKEY divisor 0 when using the onboard SIO driver.

 

Depending on your customized hardware the limit might be different.

Edited by GoodByteXL

Share this post


Link to post
Share on other sites

Nice! I can see this completely replacing any other solution currently on the market.

 

Nice, but not quite enough to replace other solutions, some people still use PCs with serial ports, just like we still use our Ataris ;)

Share this post


Link to post
Share on other sites

Is it only me, or are more people getting rather confused by different interfaces with the same name?

 

Since 2007 Sio2USB is an interface created by ABBUC/RAF.

Now there is this Sio2USB from that side the topicstarter writes about.

Then there is Sio2PC with USB connector ... some people also do call that Sio2USB.

 

In my opinion this s*cks.

 

In my opinion the ABBUC/RAF version is the only REAL Sio2USB since that one is indeed SIO to USB (stick).

 

All other versions are still a Sio2PC where the pc connection is USB.

 

An original Sio2PC isn't called a Sio2RS232 right? So why would we call a Sio2PC with USB connection suddenly a Sio2USB?

 

The word after the "2" should refer to the (storage)device.

 

Sio2IDE -> the Sio is talking to an IDE drive.

Sio2SD -> the Sio is talking to a SD drive.

Sio2USB -> the Sio is talking to an USB drive.

Sio2PC -> The sio is talking to a PC.

 

That all makes sense.

 

I believe this SIO2USB is the one you are referring to. i'd like one, but can't afford it.sio2usb.jpg

Edited by Defender II

Share this post


Link to post
Share on other sites

Is it only me, or are more people getting rather confused by different interfaces with the same name?

.....

 

The word after the "2" should refer to the (storage)device.

 

Sio2IDE -> the Sio is talking to an IDE drive.

Sio2SD -> the Sio is talking to a SD drive.

Sio2USB -> the Sio is talking to an USB drive.

Sio2PC -> The sio is talking to a PC.

 

That all makes sense.

 

If that's the case what do you call an SIO based interface that talks to ANY USB device?. IMO SIO2USB should be a general name indicating "Interface from Atari SIO to a USB device" (whether such interface exists or not), much like the USB interface on a PC. So Abbuc's device should have really been called SIO2USBS (USB Stick) or SIO2USBF (USB Flash drive) instead of monopolizing (perhaps unintentionally) the acronym SIO2USB.

  • Like 1

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...