How to force CCS not to include Config. Words in .hex file

[sirius]

MCU - PIC18F65J10, Compiler version 4.084

From document: "PIC18FxxJxx family devices do not have per-
sistent configuration memory, the top four words of
on-chip program memory are reserved for configuration
information. On Reset, the configuration information is
copied into the Configuration registers."


Is there any way(any directive?) to force compiler not to generate Configuration Words in output HEX file. Configuration Words are programmed initially by Bootloader application, so I don't need to do it again, actually it's undesirable.

#Fuses are not used in the CCS project, but still the compiler(obviously "by default") generates Config Words on address 7FF8 - 7FFF.

Thanks!

[Ttelmah]

Seriously they should always be the same in the compiled code as the bootloader. Many bootloaders won't write configuration bytes (best solution), since otherwise a value could be written that stops them working....
Make you booloader ignore bytes in this range.

Best Wishes

[sirius]

Actually this is an update of a project, that uses non-J-part(MCU), where Config. Words are at address 300000h. On J-parts Configuration Words are part of the on-chip flash program memory ("user flash"). That's why I prefer not to eliminate thе possibility to write the whole "user flash", including Configuration Words.
So, as I understand, there's no way to stop compiler doing this?
Now I edit manually hex-file, but it's a tedious job.

[Ttelmah]

Load the file into MPLAB (import). Then hit export, and un-tick the 'configuration bits' tickbox.

Best Wishes

[jeremiah]

I haven't checked in a long time, but I believe

[Ttelmah]

Well spotted Jeremiah.

Best Wishes

[sirius]