About linker and debug

In the MPLAB X documentation there's a section about resources reserved by the debugger. The linker scripts are set up to avoid the reserved memory regions when debugging. The debug exception vector is used by the EJTAG interface.

Thanks for reply
 
So, I find in the documentation ,that resource are:
1FC00_0480 -1FC00_0487
1FC00_2000 -1FC00_2FF0
and also a part of RAM 0000 -01FC
 
Now, comparing the 2 linker sript, i can see this:
 
a) in both linker ,there is in MEMORY command section:
debug_exec_mem              : ORIGIN = 0xBFC02000, LENGTH = 0xFF0
  This seems clear...Declare this area whit a name for debug
 
b) In the debug linker i find:
 kseg0_program_mem     (rx)  : ORIGIN = 0x9D000000, LENGTH = 0x80000
and in the release :
kseg0_program_mem     (rx)  : ORIGIN = (0x9D000000+0x1000+0x490), LENGTH = (0x80000-(0x1000+0x490)-8) /* the last 8 byte are reserved to checksum */
 
This is not clear.???
Kseg0 PMem start from 9D00_0000. Why in release change ??
 
Same question on  
kseg0_boot_mem              : ORIGIN = 0x9FC00490, LENGTH = 0x970
 
 
Thanks and excuse for long question
 
Roberto
 

 
 
 

Excuse me.. I belive I did a mistake.
 
The linker file i posted are modified by ex collegue...I belive was the original file.
 
Again excuse.
 
So, where is the linker used for debug, and linker used for release.
In this path :
 
C:\Program Files (x86)\Microchip\xc32\v2.30\pic32mx\lib\proc\32MX320F128L
 
i find some linker script, but no mention about who is used for what.
 
Simple question remain what area the debug use , that i must avoid to touch in debug mode.
 
Thnaks Again
 
Roberto
 

You don't need a separate linker script for debugging; the one you found in the XC32 directory will handle both. If you're trying to make a custom linker script, then don't mess with the stuff with "debug" in their names and you should be fine.