On Wednesday 28 May 2003 01:50, Wouter van Ooijen scribbled:
> Default is to power Wisp628 from the target. Some extra circuitry is
> needed for chips that configure thier /MCLR as input, because in that
> case the programmer must briefly remove (short!) the power, while still
> running itself.

That's good then.  I found that the Tait could not do this -- it required=
=20
control over the Vdd line.  I always have MCLR setup with a resistor and=20
diode as such...
     Vdd O----|>|-----./\/\/'----- MCLR



> > So I can program my pics with a Palm-pilot?  Not as useless
> > as it sounds,
> > cause I've been doing mostly automotive PIC applications.
>
> I don't know. Does a PP have Python? (It probably will if it has a
> decent (=3D 32 bit) C compiler). Does the Python have access to the ser=
ial
> port?

Yes it supposedly does, though I'm not sure how much has been whittled ou=
t (as=20
would be expected).


> > One thing that disappointed me about the Wisp is that although it has
> > flash-upgradeable firmware, and it has ICSP capabilities, the target
> > programming clip cannot be put on it's own firmware F628 to
> > upgrade itself.
> > Wat up with dat, Wouter!?!? :-) :-) :-)
>
> Actually I have been thinking about two options:
> - use a PIC that can self-program, but those are more expensive than th=
e
> F628 used now
> - (for a future USB version) upgrade via the bit-bang mode of the FT
> chip (using LVP).
> But neither will apply to the current Wisp628...

Well I was actually kidding.  I'll always have another programmer on hand=
 so=20
definitely not an issue.


Cheers,
-Neil.

--
http://www.piclist.com hint: The list server can filter out subtopics
(like ads or off topics) for you. See http://www.piclist.com/#topics