On Mon, May 05, 2014 at 01:16:39AM -0700, Bob Axtell wrote:
> This file (PK2V023200.hex) has a recent version. Anybody have it? it has=
=20
> PIC16F1946/-47 in its device list.
>=20
> I wish I hadn't lost my last HD....
>=20
> --Bob A

Bob,

The lack of updates to the PK2DeviceFile.dat has been the bane of my
existence for the last 3 years or so. I've been using pk2cmd on my Linux
box for programming and getting updated chips has been a real problem.

I finally solved it when I found the pk2dft decompiler/compiler:

http://dangerousprototypes.com/forum/viewtopic.php?f=3D56&t=3D5304

It unbundles the device file binary into a set of text files. You can edit
and add to them, then recompile back into the binary.

I've used pk2dft to add multiple 16F1XXX and 24FV parts that I've used in t=
he
last couple of years. I didn't do a 16F1947 simply because I didn't
have easy access to 64 pin parts. But IIRC it's simply a repacked
16F1938/1939 which I do have.=20

I would suggest trying to get the tool going. But in the meantime I'll be
glad to add a 16F1947 and send you the file if you like.

Just let me know.

BAJ

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

--=20
Byron A. Jeff
Chair: Department of Computer Science and Information Technology
College of Information and Mathematical Sciences
Clayton State University
http://faculty.clayton.edu/bjeff
--=20
http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.