What's the LVP status ? Pickit3 sometimes requires reconnection when there
is a malfunction. Did you try powering via PICkit ?

Did something go wrong with the board in between ?

Sunish


On Fri, Dec 27, 2013 at 5:21 PM, Joep Suijs <[email protected]> wrote:

> Hi Rob,
>
> No experience with these chips; I've only used vintage PICs ;)
> Nevertheless I had a look at the datasheet. At first glance there are
> some differences since 18f6722/23 has a 'C compiler optimized architecture'
> while 18f6680 is are source code compatible with pic16f and pic17
> instruction sets. This does not explain why you have issues with 18f6722/23
> (one would expect the other way around) and why the 18f6722 has worked in
> the past. A quick comparison of the instruction set learns that there is no
> (obvious) difference between the two families.
>
> So not very helpful :(
>
> One suggestion left is to look what has changed. Board modifications?
> Power supply? Compiler version? Device files?
> Another suggestion is to look into the pickit3 programming issue (which
> points toward hardware since the wisp works okay). Power supply okay? No
> LVP issues? Properly connected?
>
> Joep
>
>
>
> 2013/12/27 Rob Hamerling <[email protected]>
>
>>
>> Hi guys,
>>
>> I wanted to test a blink-a-led sample for a new 18f6723.
>> Programming with the wisp648 and xwisp2 worked fine, but the led didn't
>> blink. Then I took a 18f6722, which I'm sure worked in the past: same
>> story! But with 18F6680 the led blinks!  All with the same test board, only
>> a different PIC (each on its own plugin daughterboard).
>>
>> Then I tried to program the 18f6723 with a Pickit3, but now the PIC is
>> not even recognized, while it was correctly recognized by the wisp648. It
>> got a device ID 0x0 in stead of the expected 0x1400.
>> Same with the 18f6722 and 16f6680 (bot deviceID 0x0).
>>
>> Any suggestion where to search for the cause?
>>
>> Regards, Rob.
>>
>>
>> --
>> R. Hamerling, Netherlands --- http://www.robh.nl
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "jallib" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> To post to this group, send email to [email protected].
>> Visit this group at http://groups.google.com/group/jallib.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>  --
> You received this message because you are subscribed to the Google Groups
> "jallib" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at http://groups.google.com/group/jallib.
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/jallib.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to