configuration word location in hex file

[john bougs]

when I compile the code for a PIC10F206 I get the following at the end of my file. the ":0205FE00EB0F01" which is the configuration word, but has the wrong address.

The config address for the 10f206 is at address 3ffh and michrochip says "By convention the Configuration Word register is stored at the logical address location of 0xFFF within the hex file generated for the PIC10F200/202/204/206. This logical address location may not reflect the actual physical address for the part itself. It is the responsibility of the programming software to retrieve the Configuration Word register from the logical address within the hex file and translate the address to the proper physical location when programming."

so why does the CCS compiler use use a third address of 2ffh (5feh) for the configuration word location? Is there a way to change this so it works with Microchip PICkit Baseline Flash / BFMP programers?

[PCM programmer]

I don't have PCW or PCWH, so I don't know for sure, but this screenshot
of the Device Editor doesn't appear to let you set the Config bits address.
http://www.ccsinfo.com/pix/Device%20Editor.gif
I think you'll have to tell CCS support about it and wait for an update.

[Ttelmah]

Only thing is that without seeing the rest of the hex file, you cannot tell where this is actually loading!.
There may well be an extended offset field loaded first (I'd expect this), which will then take the address in this record, and add it to the extended field, to give the actual load address. Look for an extended field in front of this (will have an '04' in the fourth byte), and see where the data is actually being put.

Best Wishes

[john bougs]

there are no extended records in the hex file.

[theMagni]

It's broken.

That's the only thing I've got to say about it. We're using the 10F20X for some of our work, and the problem is with the compiler. They said it was fixed in the most recent version, but this is not the case.

According to Tech-Tools,

"CCS should be specifying an address of 07FEh(3FFh) for the 10F202/206 and address 03FEh(1FFh) for the 10F200/204. In your example, they have specified an address of 05FEh(2FFh) which is not valid for any of the 10F devices. "

What that means is that CCS put the configuration word in the wrong spot. I have done a few quick tests today. So far, it looks like they have not repeat NOT fixed the problem in version 3.224. Once I get a definitive answer, I'll let them know.

Edit to match your code. I had a really simple file without the burntime lines, and I posted without checking your code out.
The last bit of your code is:

[guest]

don't you just hate it when this happens :(

[PCM programmer]

You can't just edit the 5 and change it to a 7, because there's a checksum
on the end of each line. If you try to import it into MPLAB, you get
an error message regarding a corrupted HEX file.

[djpark]