On 7/22/05, Jan-Erik Soderholm <jan-erik.soderholm@telia.com> wrote:
> Hi !
> I just had a Wisp628 customer (I re-sell Wisp628
> localy in Sweden) 
> mailing me about programming
> problems with a 12F675.
> 
> They programs 
> once and then get all sorts of
> problems (both with XWisp and XWisp2).
> 
> I verified that I got the same "problems" using
> my own Wisp628 and a 
> 12F675.
> 
> Of course this was due to the "internal MCLR"
> problem as 
> descibed on Wouter's Wisp628 page.
> 
> Blink-a-LED file b675-1.hex 
> (*external* MCLR) works
> just fine.
> 
> Blink-a-LED file b675i-1.hex 
> (*internal* MCLR) shows
> this problem.
> 
> I happend to have a "dongle" 
> made according
> to the description on Wouter's page (actualy
> I think it 
> was *made* by Wouter), and with that
> connected between the Wisp628 and 
> the programming
> cable, re-programming of HEX files using internal
> MCLR 
> works just OK.
> 
> Now, two questions.
> 
> 1. How does the "Wisp628 
> community" handle this in general ?

  No ideea, this is a common problem only on Wisp628 and see on the
list, ICD2 too, a standard parallel programmer never do this because
timing delays could be hardware adjusted easily and does not depend by
the software source.

> 
> 2. Will this, in any way, be 
> different in the new Wisp628
> firmware that is currently under 
> development ?

 wait for this answer about 8 days.

greetings,
Vasile

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