Compile and Program help using PICKit2

[ozarkshermit]

At this point I agree. I have been pulling my hair out trying to get this to work - must be missing a - or $ or something.
Anyway, to h*** with it. I will stick to using the PICKit software - like you do and I have been doing.

LOVE Pic Basic Pro however !

Ken

[Archangel]

Ok this works, I just set mine up Thanks to Darrel Taylor:
http://www.picbasic.co.uk/forum/showthread.php?p=68368

[biggej]

Ken,
My settings are a bit different than Darrel's but may have required a download of a command processor from Microchip.
In the program filename box I have pk2cmd.exe
The path should point to your "pickit 2 v2" directory which is likely
C:\program files\microchip\pickit 2 v2
My parameters string is

-PPIC$target-device$ -F$hex-filename$ -E -M -Y -Y

This works with or without the PicKit program running as it brings up a batch programming window. The -Y -Y causes the verification to run twice just so you can see the results of programming before the batch window closes.
I usually run the PicKit program also so I can use its reset MCLR function to start the code running in the pic.
Hope this helps,
Jim

[ozarkshermit]

First of all - thanks to all who have responded and made suggestions on this.

I simply cannot get this to work -

I went so far as printing out the page that Darrel posted with his step - by - step instructions, and - as far as I know - after three times - followed them to the letter.

Obviously not - all that happens is the project compiles, there is a momentary screen flash after successful assembly - then nothing, just success at compiling. I tried Jim's code as well - same thing.

Also deleted previous attempts at selecting the programmer , so as to start from scratch -

At first MCS could not find the PICKit folder, - I changed to finding it automatically, it then found the PICkit folder - but still no success.

I also re-extracted all the PICKit2 Command Line Interface files from Microchip's site to the PICkit folder - . . .twice

Anyway - - thanks to all - - I do not intend to "beat this to death" - - I'm perfectly content to continue doing the extra step using PICkit software separately. It works fine, and that is basically all I want.

Thanks again

Ken

[Darrel Taylor]

I'm perfectly content to continue doing the extra step using PICkit software separately.

Bahhh, that's quiters talk.

Troubleshooting step #1.
Open a DOS window (Start | Run... | cmd).
Paste this line into the window (right click | paste) ...

"c:\program files\microchip\pickit 2 v2\pk2cmd.exe"
Include the quotes when pasting. Then press enter.

If the command line interface is in the correct place, it should fill your window with the HELP page.

If it does ... on to troubleshooting step #2.
<br>

[Chris Barron]

First of all - thanks to all who have responded and made suggestions on this.

I simply cannot get this to work - Thanks again

Ken

I haven't tried but it was something I have been meaning to do. Is everyone aware that you don't need to continually reload the software hex within pickit2, but that it does it automatically when you press the program button on the pickit hardware.

I normally compile using PBP, and when I get the 'complete' message at the bottom of Explorer window then press the button on the pickit2 hardware. You only have to open the pickit2 software and load the hex you're working with once per session.

I guess where it gets more complicated is if you're developing several different programs and want to pick the appropriate hex each time.

[ozarkshermit]

SUCCESS (I think)

I changed the "Programmer Filename" from pk2cmd.exe as was suggested to : PICkit2v2.exe - (which was described under PICkit2v2 Properties - version - Internal name) as PICkit2v2.exe. Now when I compile and program, after assembly is complete, the PICkit2 screen pops up, and I auto import the hex file and program. I'm not sure if the PICkit screen is supposed to pop up or not, It seems like an extra step - but then I'm not sure how it is SUPPOSED to work, but this eliminates exiting and going to that screen - - -

Ken

[Darrel Taylor]

No, that's not the way it works. Must have missed a few "Letters" in that printout.

Did you do the troubleshooting step?
<br>