[Coco] Including an SSC

[S Klammer]

I'd prefer to call it a "conversation" :)

And unless you have the "locking plate" firmly affixed, one wrong move and
you've blown almost everything :)

And in addtion to having the Teensy manage the SSC functionallity, give it
multiple buffers that the Coco could fill and switch between... but, I
digress ;)

I wonder if there are enough places on the existing CocoSDC where leads
could be affixed and routed to a header affixed wth epoxy? (did I really
just type that?)

Shain
On Oct 10, 2014 9:17 PM, "Nick Marentes" <nickma2 at optusnet.com.au> wrote:

> On 11/10/2014 10:27 AM, S Klammer wrote:
>
>> Some, myself being one, do not have a multi-pak or comfortable with a
>> hacked together Y cable.
>>
>
> I have one but it takes up my already limited desk space and with
> cartridges sticking up in the air, it doesn't allow me to slide the CoCo
> under the monitor stand anymore.
>
>  BTW, although I do not have a multi-pak, I already have a SSC and an
>> Orch90.
>>
>> Shain
>>
>>
> I too have both but rarely use them.
>
> The SCC cartridge is good although I don't think much of the speech side.
>
> TooooRobotiiiiicFooooorrrMeeeeee.   :)
>
> The sound chip is fine although it needs constant CPU intervention to have
> it play sophisticated sounds.
>
> Many of the 80's arcade machines used this very chip but most had a second
> CPU devoted to feeding the sound chip with data.
>
> That's why a modern microcontroller is ideal because it's a CPU and RAM
> and I/O in the one compact package (like my Teensey 3.1).
>
> The Teensey would interface easily. Over 70Mhz, 64K onboard RAM, USB, AD
> conversion in a package about the size of a 2764 eprom for $20 (or less).
>
> All that is missing is a header to connect to the CoCo bus....
>
> ... and now the argument has gone full circle.   :)
>
> Nick
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco
>