Facebook
Google
GitHub
Linkedin
Anyone have a link or reference to using Pickit 3 and MPLAB IDE to Pgm using a HEX file only?
Max.
Max.
MPLAB IDE hex file
- Thread starter MaxHeadRoom
- Start date
(Assuming MPLAB, not MPLAB X) Start MPLAB with no project loaded. Select target processor, and select and configure programmer. In File menu, select "Import..." Navigate to the .hex file you want and click Open. Then proceed to program.
That's my recollection, anyway. I last did it quite a while ago, but I think that's all there is to it.
That's my recollection, anyway. I last did it quite a while ago, but I think that's all there is to it.
I don't usually use my PK3, as I have an ICD3. However, I just programmed a 12F1840 using only a hex code and the PK3. It worked fine with only one little glitch. PK3 gave a warning about the configuration, but it also said it could be ignored. I ignored it, and the programming went fine. ICD3 didn't give that warning.
I used the MPLab "File" dialog to import the hex code, rather than any dialog associated with the programmer drop-down.
What chip are you using?
John
I used the MPLab "File" dialog to import the hex code, rather than any dialog associated with the programmer drop-down.
What chip are you using?
John
I will try that.
John, I am using 12f1822.
But I have found out I may have to use the stand alone MPLAB IPE loaded with MPLABX.
It's too bad this chip is not supported by the Pickit 2 stand alone pgm.
Max.
Max,
You said PK3 in the original post. The PK2 apparently does not support that chip. There may be some clandestine way around that, but so far, MPLab has caught me every time I have tried to fool it.
Asked a similar question on the Microchip forums and got a "no way" response for programming a chip that MPLab says is not supported by a particular programmer. It seems odd to me that MC would have that many different programming specifications for similar chips, but I guess that it does.
John
You said PK3 in the original post. The PK2 apparently does not support that chip. There may be some clandestine way around that, but so far, MPLab has caught me every time I have tried to fool it.
Asked a similar question on the Microchip forums and got a "no way" response for programming a chip that MPLab says is not supported by a particular programmer. It seems odd to me that MC would have that many different programming specifications for similar chips, but I guess that it does.
John
The mplab_ipe application was designed for this.
