[Coco] atari USB device

[jdaggett at gate.net]

David

I think we are sort of at the crawl before one starts to run stage. Anything and 
everything is still preliminary and still in early design and feasability stage. 

First off is to understand what the Atari groups has done and what needs to be done 
to adapt that work to the COCO. Even they are at only BETA level of their code. 
The USB chip that they are now using is flexable and simple to use. 

DECB would have to have some kind of patch to put any code in it. Best bets to be 
DECB compatible, there would have to be a rom in the cartridge containing the 
drivers. As for OS9 that would be a module that can be added to the boot list along 
with the descriptor. Most likely it would be under the SCF manager. 

As for USB drives or other storage devices that will take a bit  of time to investigate 
that aspect. Need to walk before we can run. 

james

 

On 17 Nov 2004 at 20:53, David Hazelton wrote:

Date sent:      	Wed, 17 Nov 2004 20:53:04 -0500
From:           	David Hazelton <davehazelton at access-4-free.com>
To:             	CoCoList for Color Computer Enthusiasts 
<coco at maltedmedia.com>
Subject:        	Re: [Coco] atari USB device
Send reply to:  	CoCoList for Color Computer Enthusiasts 
<coco at maltedmedia.com>
	<mailto:coco-
request at maltedmedia.com?subject=unsubscribe>
	<mailto:coco-
request at maltedmedia.com?subject=subscribe>

> James~
>  Not looking to deeply in it, Would you put code in a Rom that would
>  be
> read on startup to check for keyboard mouse and joystick on USB line
> and
>   if found would over take over the keyboard and joystick functions in
> DECB.  I would think that that would be adequate for DECB. In OS9 and
> Nitro different drivers would be loaded,  for those USB devices which
> are SCF type and that a RBF driver for USB drives (sort of like the
> CompactFlash)can be added....Did I miss any other type of USB device
> that  would be useful on a Coco?
> 
> ~David Hazelton
> 
> 
> jdaggett at gate.net wrote:
> > Mark 
> > 
> > You can do it two or three address spaces and a 256 byte receive and
> > transmit buffer to implement this. It can be done via a cartdtidge
> > or a memory mapped internal board.
> > 
> > You can do a flip flop like the old SAM chips where a write to the
> > odd address sets the "A0" line and a write to the even address
> > clears "A0" line. The third location is bidirectional address/data
> > to the SL811.
> > 
> > What impacts the glue logic will be how many bytes used to 
> > communicate to the chip. I suggest that an I/O mapping be used and
> > placed within the $FF00 to $FF7F range. 
> > 
> > james
> > 
> > 
> > On 17 Nov 2004 at 20:49, Mark McDougall wrote:
> > 
> > Date sent:      	Wed, 17 Nov 2004 20:49:12 +1100
> > From:           	Mark McDougall 
> > <msmcdoug at optushome.com.au>
> > Organization:   	Technetium Development Pty Ltd
> > To:             	msmcdoug at optushome.com.au,
> > 	CoCoList for Color Computer Enthusiasts 
> > <coco at maltedmedia.com>
> > Subject:        	Re: [Coco] atari USB device
> > Copies to:      	Send reply to:  	
> > msmcdoug at optushome.com.au,
> > 	CoCoList for Color Computer Enthusiasts 
> > <coco at maltedmedia.com>
> > 	<mailto:coco-
> > request at maltedmedia.com?subject=unsubscribe>
> > 	<mailto:coco-
> > request at maltedmedia.com?subject=subscribe>
> > 
> >>Mark McDougall wrote:
> >>
> >>
> >>>Surely cartridge space?
> >>
> >>Hmmm, only appears to use 2 bytes of address space!?!
> >>
> >>
> >>-- 
> >>|              Mark McDougall                | "Electrical Engineers
> >>do it | <http://members.optushome.com.au/msmcdoug> |   with less
> >>resistance!"
> >>
> >>-- 
> >>Coco mailing list
> >>Coco at maltedmedia.com
> >>http://five.pairlist.net/mailman/listinfo/coco
> > 
> > 
> > 
> > 
> 
> 
> 
> -- 
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco