???Originally Posted by Darrel Taylor
The Auto Import Hex from the PICKIT2 software already does this once the hex is selected.
|
???
The Auto Import Hex from the PICKIT2 software already does this once the hex is selected.
Dave
Always wear safety glasses while programming.
|
I've never tried it that way.
Perhaps it works fine ...
But I know the Command Line Interface gives one click from MicroCode Studio to PIC.
It's what I use for the PICkit2. I also have an EPIC, and a meLabs U2.
It's been awhile since the installation, I don't remember if it was automatic or if I had to figure it out.
But these are the parameters for the PICkit2 programmer.1Hr left this yearCode:-pPIC$target-device$ -f$hex-filename$ -M -R -T -h2
Well, In my time zone.
Happy new year!
Kiss someone next to you.
DT
|
When I use windows I just use the PICKIT2 soft ware.
On Linux I use this
http://www.cannasoftware.com/content/view/32/1
Both work well.
I am in the shop by myself, a real party animal1Hr left this year
Well, In my time zone.
Happy new year!
Kiss someone next to you.
HAPPY NEW YEAR!!!
Dave
Always wear safety glasses while programming.
|
PICkit2?
Darrel...
Did this give you the one click flash function from the IDE?
-pPIC$target-device$ -f$hex-filename$ -M -R -T -h2
I tried this and several variants with no luck.
The programmer application starts... no problem... but does not do it's thing without clicking the auto import button.
|
Then kiss your DrillPress.I am in the shop by myself, a real party animalHappy new year!
Kiss someone next to you.
HAPPY NEW YEAR!!!
I would if I had one ...
But, right now, the mop looks pretty good too.
tcbcats: Thru my blurry eyes tomorrow, I will attempt to verify the process.
It works, It's sweet.
Hflppy Neflear!
DT
|
Installing the PICkit2 Command Line Interface
Download the latest PICkit2 GUI, and the "PICKit2 Command Line Interface" from Microchip.
http://www.microchip.com/stellent/id...cName=en023805
Extract all files from PK2CMD to your "C:\Program Files\Microchip\PICkit 2 v2" folder.
It's the same folder as the PICkit2 programmer software.
In Microcode Studio View | Compile and Program Options... | programmer tab,
click Add New Programmer, select "Create a custom programmer entry" then click "Next".
Enter any name you wish to call it and click "Next".
Enter pk2cmd.exe as the "Programmer Filename" and click "Next".
Click the "Find Manually" button and point it to C:\Program Files\Microchip\PICkit 2 v2 and click "Next".
Enter this parameter line
-pPIC$target-device$ -f$hex-filename$ -M -R -T -h2
Then click Finished.
Pressing Compile and Program or F10 in MicroCode Studio will now do it all.
<img src="http://www.picbasic.co.uk/forum/attachment.php?attachmentid=3146" /><!---->
Descriptions of those, and additional command-line parameters can be found in the "Readme For PK2CMD.txt" file from the .zip above.
<br>
DT
|
PICkit2?
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.
Members who have read this thread : 0You do not have permission to view the list of names.
Posting Permissions
Bookmarks