Wednesday, April 25th 2018, 12:59am UTC+2

You are not logged in.

  • Login
  • Register

Dear visitor, welcome to SEGGER Forum. If this is your first visit here, please read the Help. It explains how this page works. You must be registered before you can use all the page's features. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.



Date of registration: Mar 6th 2017

Posts: 1


Tuesday, March 7th 2017, 10:00am

[ABANDONED] RTT recommended procedure in bootloader use case


I have following use case:
- Bootloader is started with RTT support (RTT data is stored in separate RAM section, RAM section is cleared at startup)
- After some time bootloader starts application program with RTT and SystemView support (RTT data is in the same RAM section as in bootloader mode, RAM section is again cleared on application startup).

If I start my device (Power On) I can only see my Application program messages, my bootloader messages are not visible. If I do a startup via debugger I can see all messages (bootloader and application program). Is there a recommended procedure in such a case? The RTT RAM section start address is set on RTT dialog.

Thank you for your help.



Date of registration: Mar 8th 2017

Posts: 4


Wednesday, March 8th 2017, 7:35pm


Without knowing which development IDE you are using, it's hard to give specific help. Here is a general thought...

Is it possible to edit your linker configuration file and tell the linker that the memory range of your RTT RAM section is a "do not initialize" section?

In IAR, this would entail editing the processor's .icf file and creating a memory section for just RTT usage.

Hope this helps, and maybe sparks some ideas on how to preserve the RTT data.