Connecting programmer to MicroCode Studio

[Darrel Taylor]

The -h2 parameter causes it to pause for 2 seconds before closing the window.
But since you didn't do the "Programmer Filename" step, I assume you didn't do the parameters either.

What I showed above was a series of steps that must be completed for it to work. ALL steps must be completed exactly as shown. Miss one, it won't work.

I have configured my IDE to place my compiled code in the PICkit2 folder.

Not sure how you did that. As far as I know, that's not an option in Microcode Studio.
You can set the default folder that comes up for a File|Save, but if you're saving everything in your PICkit2 folder, that's just plain silly.

[tcbcats]

I just set the IDE default file to the PICkit2 folder for my testing.... with a LED light blinker test program.
The -h2 does nothing I tried -h5 ....+ all combos etc with no change in the way the dos window flashes by.
I can only conclude that the script is not being read, is in the wrong place, or not constructed correctly.Is there something in the PICkit2 ini file that needs to be changed if you use the dos script vs the programer GUI?

It would help if I could get an actual screen copy of the working script from a working machine.

I assume that you are not actually using the PICkit2 with one click commands from the Microcode studio plus GUI.(that is the compile and program button)

The steps outlined in your post and confirmed in the IDE and programmer help files do not work on my system.

The example script files in the programmer help files are not in the same format as your example but I tried the examples and got the same results.

I was able to see that the dos popup displays an "\" and then quits in 1/2 second. There is no other text shown on the DOS screen... I assume I should see the script run and some delay before the dos screen closes.

[Darrel Taylor]

I'm sorry that you were unable to make it work.

Other than taking a video of me actually compiling a program and downloading with 1-click, I don't know how to convince you that it does work.

It's totally possible I've missed a step, but after deleting everything and going through the process from scratch, I see nothing that would help.

Best bet ... Use the instructions from posts #8,12,14,17.
<br>

[tcbcats]

Darrel,
I got it to work....
I had to remove the PICkit2 programmer from the IDE list of programmers and then re make the custom programmer again from scratch.
It seems that you cannot edit both the path and script without dumping the old setings.
It was an IDE problem.... If you have to edit the extsting path or programmer .exe, then you must dump the old programmer entry totally and start over.
Thanks for the help.....

[Darrel Taylor]

EXCELLENT!

That must be the Step I was missing.

Thanks tcbcats.