[Coco] What would your ideal CoCo cartridge do?

[Matthew Stock]

Aaron,

I think you'll like this.  Just a prototype, but...
https://drive.google.com/file/d/0B-pVCwODbx7MaVNDU2tWNTNtU00/edit?usp=sharing

Mark, the WizNet chip that this module is based on takes care of a lot of
the TCP/IP/phy stack on-chip.  It can handle a few connections at a time,
and can both listen and initiate connections.  It does not have DHCP
in-chip however, and so if you didn't have a static IP defined, that code
would need to live on the Coco somewhere.

The connection to the host device is pretty simple - it uses a simple
serial interface to communicate (SPI) and has a memory range with
registers, etc.  The Coco interface I was imagining was two of the SCS
bytes - one of byte in/out (to pass to the WizNet chip), and a second for
control/status.  Interacting with that port would need to be handled by a
Coco driver however.
  -Matt



On Sun, Oct 27, 2013 at 8:58 PM, Mark J. Blair <nf6x at nf6x.net> wrote:

>
> On Oct 27, 2013, at 17:41 , Aaron Wolfe <aawolfe at gmail.com> wrote:
> > Ethernet
>
> How would the ethernet be used? Is there a TCP/IP stack that can work on a
> CoCo, or would this be something with an embedded ethernet stack and a
> serial-like interface to the CoCo?
>
> > The items in your list already exist in various forms, fwiw.
>
> Yup. I don't think I've come up with anything truly original at all here.
> I'm just discussing what features might be nice to combine in a single
> cartridge. Especially combinations that don't presently exist in one
> cartridge, and/or things that are hard to obtain nowadays.
>
>
> --
> Mark J. Blair, NF6X <nf6x at nf6x.net>
> http://www.nf6x.net/
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>