ICD=TRUE and .lst file

[Herbert]

Hi,

I am trying to confirm the bootloader I have written, is functioning (yes I've unfortunately had to write my own because of the specifics of my application). some details : PCWH vers 4.079. A couple of questions come to mind -

1. With ICD=TRUE, does the .lst file generated from the compilation, actually list the bits of code the ICD inserts (or does it hide itself from the listing)? I presume the interrupt must have some additional code and I read somewhere in the forum that there is ICD code kept high in memory as well. If there is high ICD code, does this mean my final compiled code (with ICD=FALSE) will have a free area above it, that is only used by ICD when ICD=TRUE?

2. Using the PCWH interface, I notice I cannot get an update of what the contents of an area of program ROM might be. The "ROM" debugging window is not update-able and I suspect is generated from the .lst file. This makes it impossible to confirm the my bootloader is writing the correct program code to the correct area. Is there a way around this, other than writing support code to read back presumably changed areas of ROM and spitting them out of the serial port?

Cheers

Herbert

[FvM]

Are you referring to CCS ICD? With MPLAB and ICD-2 or PicKit, you can read back the ROM.

[Herbert]

Hi FvM,

Yes its CCS ICD. Are you saying it can't be done?

[FvM]

I'm rarely using CCS ICD, I don't know. But you can read back the ROM to a *.hex file with the ICD software and compare or disassemble it.