MicroCode Studio and Microchip ICD3 Parameters

[geoffpeters]

Hello,

How do I configure the parameters for a Microchip ICD3 programmer? I installed using the icd3cmd.exe programmer filename. When I click compile & program the program compiles successfully but there is no indication that the programmer is actually running.

Any help appreciated

[tumbleweed]

Have you setup the commandline options for icd3cmd? They can be found in the MPLABX folder docs\Readme for RealICECMD_ICD3CMD.htm

See http://www.picbasic.co.uk/forum/showthread.php?t=23910 for some basic setup info

[geoffpeters]

No I haven't entered any command line options. That is what I'm lookin for. I had previously read the information in the link you provided but it only suggests parameters for the PK3.

I looked at the readme for the ICD3 in the MPLABX docs but I do not see the options explained.

I also looked at MPLAB ICD 3 In-Circuit Debugger User's Guide for MPLAB X IDE but still do not see the command line options.

Clearly I'm missing something...

[tumbleweed]

Did you look in the file "Readme for RealICECMD_ICD3CMD.htm", sections 8 (command line options) and 11 (examples)?

They're all pretty similar...

[geoffpeters]

OK, that is what I've been looking for. I'll try some of those and see how it goes. The information is a bit difficult to find so thanks for your help!

[geoffpeters]

Well, no joy here.

I have the ICD3 connected to the target 12F1612. The target is powered and the power LED on the ICD3 illuminates.

When I compile and program, the file compiles successfully, a blank black DOS window opens with no text and then closes.

The device appears to not be programmed.

I'd really like to make this work.

Does anyone have any suggestions on how to use MCS with the ICD3?

[tumbleweed]

For the MCS IDE, if you tack on a "-B" that puts it into batch mode and it should leave the command window open.
Here's an example command line:
-P$target-device$ -F$hex-filename$ -W -B

ICD3CMD doesn't offer a lot of display info, so I like to open a command prompt and run ICD3CMD manually when I first set it up.
That way you know what to expect (and if it works)

[geoffpeters]

Thank you for the detailed information. I'll try it this AM. What do you mean by starting ICD3 manually? I'm not sure how to do that.

[tumbleweed]

I meant to open a windows command prompt and run ICD3CMD.exe from the command line so you can play around with the various options and see what the results are.
As I said, you don't get much output for many of the operations, but at least you'll know what to expect.

[geoffpeters]

Right, I realized what you meant just after I posted my reply. I did that and was happy to see that the communication worked.

The setup I have working now is compile in MCS and program with MPLABX IPE.

Thanks for your help.

[Ioannis]

I found the ICD3 very unreliable and had to use the IPE to control it, which was not the easiest thing to do.

Anyway, now I use Pickit3, very much better, good power capabilities and not forced to use the Microchip IPE. Instead the standalone Pickit3 (or Pickit2, is the same) works great, developed by Evan at Pickitplus.co.uk saving me time and effort.

Ioannis

[geoffpeters]

Thanks for your input. What is working for me is to compile in MCS, open the hex file in MPLABX IPE, and program with the connected ICD3.
I did find that I must clear the hex file selection and load the new file in MPLABX IPE prior to programming.
The main drawback is that debugging is unavailable

[Ioannis]

The main drawback is that debugging is unavailable

It is not ICD3 problem rather than PBP.

Ioannis