Pic programming help, (be gentle)

Hi all, First off I know nothing about programming pics, so please be gentle. I took over this project that has a pic (P16F886 if that matters.) I've programmed a bunch of these previously... following a cook book recipe that I wrote down. Now it's not working and I'm stuck.

I'm working in a with a MPLAB ICD2. There is a project file that I open

*.mcp. And then I click a few buttons and it's done. The problem I see now is that when I start this the checksum is not the right number.

So some silly questions, What is the checksum, and does the wrong number mean I need to recompile the program? Or something else.

Help! TIA George H.

Reply to
George Herold
Loading thread data ...

OK never mind... I "rebuilt" the whole thing and it seems to be happy now. (Grumble, I hate the feeling of not knowing what I'm doing.)

George H.

Reply to
George Herold

For production I just use the hex file. You can open MPLAB, select the programmer(ICD2), Select the device, then File->Import the HEX File, then program.

That way there is no chance the code can be changed and it's stored in a safe place.

Cheers

Reply to
Martin Riddle

Huh, OK that worked too. What's weird is the only hex file in the development space is the one I just created with my "build all" command. (I saved the file with a different name before building.. not knowing what I'm doing I save early and often.)

Thanks George H.

Reply to
George Herold

Somewhere on the Microchip website there is a standalone programming environment (IPE). So you don't mess with projects etc. But I think it's only MPLAB X.

Cheers

Reply to
Martin Riddle

We used MPLAB X (upgraded) in an earlier job. It was very buggy, so we reverted back

Reply to
Klaus Kragelund

I still use 8.84. It produces repeatable results, which is a good thing.

The IPE is part of X, unfortunatly.

Cheers

Reply to
Martin Riddle

You *can* have both, but you end up with things like the "driver switcher".

--
Les Cargill
Reply to
Les Cargill

ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.