Bootloader/Main start address, different for debug/release?

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Bootloader/Main start address, different for debug/release?

675 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by daveczeta on Tue Nov 17 03:23:14 MST 2015
Hi,

I have firmware that is split into boot-loader and main.  I am changing the start location in flash for each via http://support.code-red-tech.com/CodeRedWiki/EnhancedManagedLinkScripts

I can only successfully use the JTAG debugger if my code does not have another program like the boot-loader already on chip otherwise its flaky and makes it harder to debug.  So in release builds of main program it'll normally start at a different address than if I build the same code in debug.  In the latter I may want the program to start at 0 to aid debugging.  Debug builds are only at my desk and not in-field.

However, they've implemented the settings in an odd way.  It seems to be per project and not per-configuration which means both my debug and release builds of the same project have the same start address and changing it affects both.  Without going fully bareback with my own linker script is there anyway to customise the start address from settings in the linker which are active configuration dependent?

Regards

dc
0 Kudos
Reply
1 Reply

633 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Tue Nov 17 03:48:54 MST 2015
The MCU settings are indeed per project.

For an alternative approach, please see: https://www.lpcware.com/content/forum/mcu-settings-should-be-configuration-dependent-and-not-same-ac...

PS : I would suggest reading the following Linker script FAQ instead of the old Code Red one you quote: https://www.lpcware.com/content/faq/lpcxpresso/own-linker-scripts

Regards,
LPCXpresso Support
0 Kudos
Reply