Hi Rob

Yes this works for me with the 18F183xx family using the pickit3 program at
least. If you don't have the PicKit3 program, it can be downloaded from a
link on https://microchipdeveloper.com/pickit3:scripttool. I find this more
useful than MPLABX IPE as you can actually see what gets programmed, and
when you read back from the chip you can actually see what's been written
into the EEPROM.
The PK2 Device File Editor looks interesting so I'll download that and have
a play when I have time.

Cheers

Fraser


On Sat, 25 Apr 2020 at 09:48, Rob CJ <[email protected]> wrote:

> Hi Fraser,
>
> I found an editor for this file at:
> https://sites.google.com/site/pk2devicefileeditor/home
> <https://sites.google.com/site/pk2devicefileeditor/home>
> PK2 Device File Editor - Google
> <https://sites.google.com/site/pk2devicefileeditor/home>
> PICkit 2 Device File Editor Application Download Page. Downloads . If you
> already have the .NET 2.0 framework and the VC9 redistributable dll files
> installed (either in the windows\system32 directory, or in the same
> directory of this program) you can just download the exe and dll files and
> the program should run.
> sites.google.com
>
> So maybe you can add your missing devices. I have no experience with this
> program. I only saw that is able to read the file you had sent and it shows
> indeed the presence of the 18F4455, see screenshot below.
>
>
>
> Is this file used by the stand-alone PICkit3 programming software? I could
> not find the file in any of the MPLABX directories.
>
> Kind regards,
>
> Rob
>
> ------------------------------
> *Van:* [email protected] <[email protected]> namens Fraser
> Smith <[email protected]>
> *Verzonden:* zaterdag 18 april 2020 18:07
> *Aan:* [email protected] <[email protected]>
> *Onderwerp:* Re: [jallib] Re: SNAP
>
> I should have said that the file is for the pickit3. Investigation has
> revealed that it came from Anobium in their git repository.
>
> Fraser
>
> On Sat, 18 Apr 2020, 10:22 Fraser Smith, <[email protected]> wrote:
>
> I got an updated definitions file from somewhere a while back that
> includes the newish 16F183xx chips I'm using and I also see the 18F4455 in
> its ( binary) file. I wish I could remember where it came from. Anyway it's
> attached here. It needs renaming back to pk2devicefile.dat. Worth a try.
>
> Cheers
>
> Fraser
>
> On Tue, 7 Apr 2020, 16:40 Rob CJ, <[email protected]> wrote:
>
> Correct.
>
> I only purchased a SNAP because I could not program the newest devices
> with my Pickit3 even not in LVP mode. The Pickit3 like the Pickt4 support
> both LVP and HVP but apparently the Pickit3 does no longer support all new
> devices not in LVP and not in HVP.
>
> So if your plan is to only use devices that understand LVP then a SNAP
> would be sufficient.
>
> The only confusing part is your PIC18F4455 since in the device file you
> see LVP that can be enabled but apparently the older LVP is not the same as
> the newer LVP or Microchip has decided just simply not to support your PIC
> with SNAP like they do not support my newer PIC with Pickit3.
>
> Kind regards,
>
> Rob
>
> ------------------------------
> *Van:* [email protected] <[email protected]> namens Rob
> Hamerling <[email protected]>
> *Verzonden:* dinsdag 7 april 2020 09:29
> *Aan:* [email protected] <[email protected]>
> *Onderwerp:* Re: [jallib] Re: SNAP
>
>
> Hi Peter,
>
> On 2020/04/06 23:30, Ptr wrote:
>
>
>
> Strange: you have to buy two programmers. SNAP for LVP and Pickit4 for HVP.
>
> So I don’t have to look for updates for the SNAP. It’s impossible.
>
> That is not quite correct. Pickit4 supports both HVP and LVP. So if you
> buy a Pickit4 you don't need a Snap.
>
> Regads, RobH.
>
>
> --
> *Rob H*amerling, Vianen, 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/jallib/8a71b478-5815-f171-4646-b45b5eab0e28%40gmail.com
> <https://groups.google.com/d/msgid/jallib/8a71b478-5815-f171-4646-b45b5eab0e28%40gmail.com?utm_medium=email&utm_source=footer>
> .
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/jallib/DB7PR07MB54018462AB57A643BBC3F212E6C30%40DB7PR07MB5401.eurprd07.prod.outlook.com
> <https://groups.google.com/d/msgid/jallib/DB7PR07MB54018462AB57A643BBC3F212E6C30%40DB7PR07MB5401.eurprd07.prod.outlook.com?utm_medium=email&utm_source=footer>
> .
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/jallib/CAN856gh%2Bz3PE9TL2Kw4YAt10nT7Fnm%2BL%3DOEXBwJzX1UDRFnZOw%40mail.gmail.com
> <https://groups.google.com/d/msgid/jallib/CAN856gh%2Bz3PE9TL2Kw4YAt10nT7Fnm%2BL%3DOEXBwJzX1UDRFnZOw%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/jallib/DB7PR07MB5401C44DAE9D2A42B4162A6DE6D10%40DB7PR07MB5401.eurprd07.prod.outlook.com
> <https://groups.google.com/d/msgid/jallib/DB7PR07MB5401C44DAE9D2A42B4162A6DE6D10%40DB7PR07MB5401.eurprd07.prod.outlook.com?utm_medium=email&utm_source=footer>
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/CAN856giR_-qb6Zz_rFfsW91COvOc0BHF4D7AzuGtoSVPNhrevA%40mail.gmail.com.

Reply via email to