Getting PicKit2 working in OSX
Download:
PicKit2-Programmer-GUI-1.2-OSX.zip
Extract files
Installation:
- Mac OSX 10.5 is required to run it along with the latest version of Java.
- You need to copy pk2cmd and PK2DeviceFile.dat files into /bin folder, even if you have manually installed pk2cmd before.
- To do that, open a Finder window and press CMD+SHIFT+G then type in “/bin” (without the ” “).
- Drag and drop the 2 files, enter your admin password and you’re done.
Or by terminal:
- copy pk2cmd to /bin
- # sudo cp pkcmd /bin
- Copy PK2DeviceFile.dat to /bin
- # sudo cp PK2DeviceFile.dat /bin
Plugin your USB PicKit2
Run PicKit2-Programmer
If you get the message that the PK2DeviceFile.dat can not be found then run the following command.
# sudo chmod 777 /bin/PK2DeviceFile.dat
sleepingsucks 
Question (if you are still keeping this up). I’m coming at this from a very non-engineering standpoint, so my understanding of the Pickit2 device is very limited — entirely non-existent, actually. I have finally gotten your Pickit2.app working on Mac OS Sierra, however I’m not certain it’s functioning, or perhaps I am doing something wrong. It recognizes that there is a Pickit2 Programmer attached via USB, as the FW shows:
Checking PicKit2 Version …
Executable Version: 1.20.00
Device File Version: 1.62.00
OS Firmware Version: 2.32.00
The light on the Pickit2 shows power, and the Target light lights up, and the Busy light Blinks when I tell click on “write HEX”, however I get this message onto the log:
Operation Succeeded
Writing HEX on PIC…
Auto-Detect: No known part found.
I’m not certain how I can confirm that the .hex is on the device (at least not until I plug it into the device that I am attempting to update, in this particular case a Eurorack Module called a Stillson Hammer mk2 by Industrial Music Machines and either it will update or it wont).
Is there any information you can provide as to what the “auto-detect” message means?
Great that you offered this – updating this Eurorack Module is a bit of a pain and a bit of a time consuming one at that.
Thank you!
Thanks for stopping by..I don’t use this blog often as I moved all my music related stuff to http://music.codydeschenes.com To tell you the truth the last update to Sierra broke my PicKit2 app yet again and I decided to just move it all to my shop PC which is Windows 10. I hate the defeat but I really needed to keep burning chips. In the app are you able to manually set what PIC you are putting on the witter?
I’ll see if I can get the PicKit2 app working again on my Macbook and see if I can help.
Yea, I’ve been noticing that Apple’s “Rootless” is feeling more “Ruthless” when I want to get something odd done, and each incarnation gets progressively more and more locked down.
Again, I’m not fluent in this world of “PIC” so I’ll do my best to answer: When I click “Show connected PIC” I receive this message:
Searching for your PIC on board …
Auto-Detect: No known part found.
However, there is activity lights blinking on the PIC device that is attached to USB. I don’t know if this matters or not, but I bought this off of eBay assuming that it was a Pickit2 as it was advertsed as such. I figured that if they are able to be built as a DIY, then it shouldn’t directly matter. The chip on it has a Microchip “M” stamp, however I can’t imagine that would be hard to do, especially from China.
Here is the log from all the messages from the app, from all the available buttons — I don’t know if it’s helpful or not.
Logs cleared
File stillsonFW18.hex successfully loaded
Checking PicKit2 Version …
Executable Version: 1.20.00
Device File Version: 1.62.00
OS Firmware Version: 2.32.00
Operation Succeeded
Searching for your PIC on board …
Auto-Detect: No known part found.
Writing HEX on PIC…
Auto-Detect: No known part found.
Running HEX …
Auto-Detect: No known part found.
Erasing aborded
Testing HEX integrity …
This might take a while
Auto-Detect: No known part found.
Erasing your PIC … (Don’t panic !)
Auto-Detect: No known part found.