Many thanks, I`ll give these a try
Cheers Pete
MPLAB can be your friend here!
First, set Configure | Set Device to the PIC you use.
Next, load your hex file into it via File | Import.
Now, you get the hex checksum top left corner. To insure the "fuse bits" are correct, drill down Configure | Configuration Bits and have a look at them.
I've used Digi-Keys programming service a few times, they also require the config bits to be sent, I screen-shot them right from MPLAB.
Hi All
OK I imported the hex file into MPLAB and it generated the check sum fine. Sent the hex file plus the checksum to Microchip but it failed to pass. Heres the relevent part of the message from microchip:
The Programming Team advises the Checksum value submitted: "de73" does not match the actual Checksum value of the program.
The file submitted is in non-MPLAB standard format. Headers within the file are uniquely different than those produced by MPLAB and the memory map is incomplete.
Its generated using Microcode studio and PBP. I compile using the PBP compiler. Any clues whats wrong here?.
Cheers Pete
Interesting. Try this:
Change the MCS View | Compile and Program | Assembler Options tab to have it use MPASM as the assembler. That way, you have a Microchip product generating your hex code.
I bet that will help some.
Hi
Altered MCS to use MPSM and I get an error on my code which isnt there when I compile through MCS without MPSM. Seems to dislike this line:
@ device protect_on, pwrt_off, bod_off, INTRC_OSC_NOCLKOUT
particulary the error states protect_on to be illegal opcode. Device is 16F648A
Cheers Pete
Do a search in the FAQ for a thread name "How to set Config fuse" or something like that.
MPASM don't use the same Directive as PM.
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
Bookmarks