Hi again.

A third question... :-)

3. How does *other* ICSP=20
programmers handle this ?

There seems to be a general problem if the=20
power to=20
the target is "on" all the time, right ?

Jan-Erik.




>=20
-----Original Message-----
> From: piclist-bounces@mit.edu=20
> [mailto:
piclist-bounces@mit.edu]On Behalf
> Of Jan-Erik Soderholm
> Sent: den=20
22 juli 2005 00:36
> To: piclist@mit.edu
> Subject: [PIC]: Wisp628 and=20
internal MCLR.
>=20
>=20
> Hi !
> I just had a Wisp628 customer (I re-sell=20
Wisp628
> localy in Sweden)=20
> mailing me about programming
> problems=20
with a 12F675.
>=20
> They programs=20
> once and then get all sorts of
>=20
problems (both with XWisp and XWisp2).
>=20
> I verified that I got the=20
same "problems" using
> my own Wisp628 and a=20
> 12F675.
>=20
> Of course=20
this was due to the "internal MCLR"
> problem as=20
> descibed on=20
Wouter's Wisp628 page.
>=20
> Blink-a-LED file b675-1.hex=20
> (*external*=20
MCLR) works
> just fine.
>=20
> Blink-a-LED file b675i-1.hex=20
>=20
(*internal* MCLR) shows
> this problem.
>=20
> I happend to have a=20
"dongle"=20
> made according
> to the description on Wouter's page=20
(actualy
> I think it=20
> was *made* by Wouter), and with that
>=20
connected between the Wisp628 and=20
> the programming
> cable, re-
programming of HEX files using internal
> MCLR=20
> works just OK.
>=20
>=20
Now, two questions.
>=20
> 1. How does the "Wisp628=20
> community" handle=20
this in general ?
>=20
> 2. Will this, in any way, be=20
> different in the=20
new Wisp628
> firmware that is currently under=20
> development ?
>=20
>=20
Best Regards,
> Jan-Erik S=F6derholm.




--=20
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist