Connecting programmer to MicroCode Studio

[tcbcats]

Darrel,
I set up my programmer as you directed and still get the same results...
The PICkit2 application starts and and just shows that it found the connected PIC... thats all. I have to manually click the putton and then select the hex to get it to program the target PIC.
Just before the application starts the programmer shows activity but that is maybe just reading the target PIC to confirm a connection.
I tried many of the other commands in the readme file with no luck.
It looks like the command never actually runs or has some other error.
The PICkit2 application gets started from the programmer path you enter in the IDE so its the script that is not working.
My new USB U2 came today and it works with the script... so I guess I will scrap the PICkit... too bad the price is right and it does work if manually directed. It also works as stand alone.
Maybe MEL has some other info on how to get the PICkit2 to work with the script.

[Darrel Taylor]

Are you sure you entered pk2cmd.exe as the Programmer Filename.
It opens a DOS window, not the PICkit2 GUI program.

If it's opening the GUI, something's definitely not right.
<br>

[iw2fvo]

Hi to you all !
I do have to launch the MPLAB in order to programm the PIC directly from the MCS. At the moment I use the MCS and MPASM and then i call the MPLAB to program the chip. I will like to do it in a single action.
Thanks for any suggestion .
Regards,
Ambrogio
IW2FVO
North Italy

[rmteo]

See posts #8,12,14,17.

[tcbcats]

Darrel,
I changed the programmer exe and now I get a dos window for a short instant... then it goes away... It is so fast that I cnnot see anything in the window.... programmer does nothing and target PIC is not read or programmed.
So...the dos is starting but not reading any script.

Are you actually using the script and one click programming from the IDE?
I have configured my IDE to place my compiled code in the PICkit2 folder.

[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.