Using ICD2 to Program from inside the IDE
Moderators: David Barker, Jerry Messina
Using ICD2 to Program from inside the IDE
Here is a command line utility that will drive the ICD2!
Seems to work pretty good.
http://piklab.sourceforge.net/
It does require this lib to function...
http://libusb.wiki.sourceforge.net/
then, just add a new programmer into SF IDE (ie. Microchip ICD2)
program name: piklab-prog.exe
parameters: -p icd2 -d $target-device$ -t usb -c program $hex-filename$
I know it doesn't support debugging, but, it saves time so that I no longer have to switch to MPLAB to import the hex file and then program it.
enjoy
Seems to work pretty good.
http://piklab.sourceforge.net/
It does require this lib to function...
http://libusb.wiki.sourceforge.net/
then, just add a new programmer into SF IDE (ie. Microchip ICD2)
program name: piklab-prog.exe
parameters: -p icd2 -d $target-device$ -t usb -c program $hex-filename$
I know it doesn't support debugging, but, it saves time so that I no longer have to switch to MPLAB to import the hex file and then program it.
enjoy
Hi dman776,
For development purpose, the piklab's ICD2 utility works fine, but you must be carefull: with some PICs, some users on forums reported having CONFIG word wrongly programmed. This is especially important for PROTECTION FUSES
If I had to recommand a programmer, if you do not need debug possibility, is to buy instead a PikKit2 from Microchip. It costs less than 30 euros, and Microchip provides a command line utility to manage it. It's also very well supported and integrated in MPLab, and it uses the same connectors as ICD2 (if you need later to use this one to debug final program).
Regards
octal
For development purpose, the piklab's ICD2 utility works fine, but you must be carefull: with some PICs, some users on forums reported having CONFIG word wrongly programmed. This is especially important for PROTECTION FUSES
If I had to recommand a programmer, if you do not need debug possibility, is to buy instead a PikKit2 from Microchip. It costs less than 30 euros, and Microchip provides a command line utility to manage it. It's also very well supported and integrated in MPLab, and it uses the same connectors as ICD2 (if you need later to use this one to debug final program).
Regards
octal
- David Barker
- Swordfish Developer
- Posts: 1214
- Joined: Tue Oct 03, 2006 7:01 pm
- Location: Saltburn by the Sea, UK
- Contact:
Dave... This is great news!David Barker wrote:Work in progress...
http://www.sfcompiler.co.uk/wiki/upload ... /mplab.gif
http://www.sfcompiler.co.uk/wiki/uploads/debug/isis.gif
Warren
OK...downloaded the new SF version 2.1.0.0...followed Wiki instructions to set up in MPLab...builds, programs and run OK using MPLAB and ICD 2...but can't get the breakpoints to work in the .bas file listing, just the .asm file listing. It would be nice to have them working on the .bas listing.
Also, I can see what the basic variables are in the Watch window along with the "raw" assembler variables - I haven't had a problem with not finding a variable but it's just unexpected.
Any suggestions? I'm using MPLab 8.1, 18F66J16 (which requires no RAM space to be reserved). I tried it with a program that uses 96K of program space and another that used 10K.
-Tom
Also, I can see what the basic variables are in the Watch window along with the "raw" assembler variables - I haven't had a problem with not finding a variable but it's just unexpected.
Any suggestions? I'm using MPLab 8.1, 18F66J16 (which requires no RAM space to be reserved). I tried it with a program that uses 96K of program space and another that used 10K.
-Tom
- David Barker
- Swordfish Developer
- Posts: 1214
- Joined: Tue Oct 03, 2006 7:01 pm
- Location: Saltburn by the Sea, UK
- Contact:
- David Barker
- Swordfish Developer
- Posts: 1214
- Joined: Tue Oct 03, 2006 7:01 pm
- Location: Saltburn by the Sea, UK
- Contact:
Your need to take a look at the following post
http://www.sfcompiler.co.uk/forum/viewtopic.php?t=721
particularly with reference to:
http://www.sfcompiler.co.uk/forum/viewtopic.php?t=721
particularly with reference to:
Also note:The problem is with your "TLSFBasic.ini" file, which is documented here:
http://www.sfcompiler.co.uk/wiki/pmwiki ... r.MPLABICD
under "Swordfish as a Language Toolsuite". In short, you need to download the new files from here
http://www.sfcompiler.co.uk/wiki/pmwiki ... User.MPLAB. Copy to your MTC folder and verify that "TLSFBasic.ini" now has "Debug=COF" AND NOT "Debug=COD"
Let me know how it goes...David, I got it to work. I had to run Swordfish.reg again after updating the .ini & .mct files