pic30 / xc16的objcopy-哪里可以找到，类似物

Question

I am working with a non-standalone project on PIC24 which requires a bootloader and I want to debug it with a bootloader. I am able to produce an .hex file that contains the application code with the bootloader, registering a custom script that executes after compilation.

If I now select "Launch Debugger Main Project" in the menu, the debugger normally executes the summary code and even reaches the the application startup, but does not display debug information, because it is not contained in .hex file. But if I choose "Debug Main Project", debugger is loading .elf file that contains debugging information but does not contain loader code instead of manufactured .hex file.

Is there a way to force the debugger to load debug information from one file and executable code from another file? Or is there a way to add a section in compiled .elf file or completely replace the code within it ? There is no 'objcopy' utility neither for pic30, nor for xc16, are there any analogs?

These are pictures for question:

[1] https://s15.postimg.cc/59jynpikr/2018-06-27-0001.png

[2] https://s15.postimg.cc/kv1a7q7ej/2018-06-27-0002.png

[3] https://s15.postimg.cc/idpj0hid7/2018-06-27-0003.png

[4] https://s15.postimg.cc/8t5wdm0qz/2018-06-27-0004.png

[5] https://s15.postimg.cc/np4fl7rl7/2018-06-27-0005.png

[6] https://s15.postimg.cc/xz6ukgwwb/2018-06-27-0006.png

[7] https://s15.postimg.cc/bn91r35i3/2018-06-27-0007.png

Answer 1

When two HEX files are combined with the method you described all of the symbolic debug information is lost.

Starting a debug session from MPLABX will download the combined image but only the symbolic information from the "active" project is loaded for the debug session.

A work around is to create a "special" project that builds both the bootloader and application as one HEX file will put all of the symbolic information in one name space.

This tends to be tricky and requires the creation of a custom linker script file.