On Wed, Aug 14, 2002 at 03:06:07PM -0700, Brendan Moran wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> > I'll keep my summary short. You can check the archives for more
> > details.
> >
> > The unit comes with one socketed preprogrammed chip (P-socket), an
> > empty socket (S-socket), and an ICSP port (I-port?).  Development
> > can occur (via bootloader) to the P-socket chip, or the P-socket
> > chip can program another chip either via the S-socket or the
> > I-port. The S-socket has two functions: to allow for a dual 16
> > serial/18 series setup and to allow full access to the S-socketed
> > chip (i.e. it doesn't require a bootloader). The I-port is to
> > program offboard targets and odd sized (relative to the 40 pin P
> > and S socket) chips.
> >
>
> Byron,
>
> I've been supporting the idea of a two chip system for a while now,

I'm well aware. Alan's observation that it was the only mechanism to have
a 16F and 18F config is what finally swayed me.

> and I think this is getting pretty close to something that I'd like
> to see.  Would it be possible to have a hex file for the P-socket
> chip that would allow it to act in ICD mode on the S-Socket chip?

Not sure. Tackling writing our own ICD seems a daunting task.

> There's no LA, but I can still live with that.  One other idea: I
> like the principle of allowing for multiple oscillator configurations.

No problem with that for the S-socket. I do believe that the P-socket chip
will have to have a fixed oscillator config. Otherwise it may have a difficult
time communicating with the host.

>
> I just hope that this doesn't get too far into CUMP's territory (;

No chance. As I've said all along it's a universal demo board, not a universal
programmer.

BAJ

--
http://www.piclist.com hint: To leave the PICList
mailto:piclist-unsubscribe-request@mitvma.mit.edu