Having the RTT viewer after DFU

RE: Having the RTT viewer after DFU

Amanda Hsieh — Mon, 15 Mar 2021 07:31:44 GMT

Hi Rajender,

Add .rtt region into flash_placement.xml as the figure

-Amanda H.

RE: Having the RTT viewer after DFU

umrsraj — Sat, 13 Mar 2021 05:44:15 GMT

Hi Amanda,

Since our project is ready to deploy in the location its very much important to conclude this issue ASAP

so i am requesting you to make this SES compatible ASAP.

Best Regards,

Raj.

RE: Having the RTT viewer after DFU

Amanda Hsieh — Thu, 11 Mar 2021 14:36:53 GMT

Hi Rajender,

That post was for GCC. After the modification, you can build the project under \armgcc to get the image by typing "make" in the command window. If you want to use segger, I will take time to look into how to set in the segger project.

-Amanda H.

RE: Having the RTT viewer after DFU

umrsraj — Wed, 10 Mar 2021 12:50:51 GMT

Hi Amanda,

I am still can't define that definition without error, and getting same error as before.

I am using nrf52840(pca10056), SDKv15.1.0, SEGGER Embedded Studio v5.20(with nordic free license).

and i have changed linker script files nrf5_common.ld, nrf52_common.ld as referred post suggested.

then do i need to move the RTT related definitions as suggested in the 3rd point, if yes please help me to understand it clearly(i am confusing what he suggesting to do).

Best Regards,

Raj.

RE: Having the RTT viewer after DFU

Amanda Hsieh — Wed, 10 Mar 2021 09:48:10 GMT

Hi Rajender,

Define the macros in your app/sdk_config.h:

#define SEGGER_RTT_ALIGNMENT 4
#define SEGGER_RTT_BUFFER_ALIGNMENT 4
#define SEGGER_RTT_SECTION ".rtt"

Allocate section in the linker script file. In nrf5x_common.ld as that post.

The corresponding sections in the linker file look like this:

SECTIONS
{
  . = ALIGN(4);
  .mem_section_dummy_ram :
  {
  }
  .log_dynamic_data :
  {
    PROVIDE(__start_log_dynamic_data = .);
    KEEP(*(SORT(.log_dynamic_data*)))
    PROVIDE(__stop_log_dynamic_data = .);
  } > RAM
  .fs_data :
  {
    PROVIDE(__start_fs_data = .);
    KEEP(*(.fs_data))
    PROVIDE(__stop_fs_data = .);
  } > RAM
  
  .rtt :
  {
    KEEP(*(.rtt))
  } > RAM

  
} INSERT AFTER .data;

After updating with the app via DFU, reconnect to RTT view. You will see the log of the application. You might need to adjust the ram size as that post indicate.

-Amanda H.

RE: Having the RTT viewer after DFU

umrsraj — Tue, 09 Mar 2021 12:04:39 GMT

I am using SDK 15.1.0

RE: Having the RTT viewer after DFU

Amanda Hsieh — Tue, 09 Mar 2021 11:44:26 GMT

Hi Rajender,

What SDK version you are using?

-Amanda H.

RE: Having the RTT viewer after DFU

umrsraj — Tue, 09 Mar 2021 06:00:19 GMT

Hi Amanda,

I am Very sorry for the late replay,

but i have tried very much to implement same thing in my code as you suggested in the reference link,

but still i am having compilation errors to implement those steps like adding

#define SEGGER_RTT_SECTION ".rtt"

so please give me more explanation that where we need to add these steps,(sorry for requesting very basic procedure)
and then i will start testing in my code.

Best Regards,
Raj.

RE: Having the RTT viewer after DFU

Amanda Hsieh — Thu, 04 Mar 2021 14:12:18 GMT

Hi Rajender,

It happens because the bootloader and application have placed the RTT buffer in different sections in RAM and Jlink doesn't know this. It expects it to stay at the same address. The solution is to configure the linker settings so that both the bootloader and app places the buffer at the same place in RAM. Here is the example https://devzone.nordicsemi.com/f/nordic-q-a/30310/easy-way-to-merge-bootloader-and-application-rtt-output

-Amanda H.

RE: Having the RTT viewer after DFU

umrsraj — Thu, 04 Mar 2021 13:13:06 GMT

Hi Amanda,

Since we are ready to deploy our device at customer end we need solution for this RTT Log issue ASAP

so we are awaiting for your reply..

Best Regards,

Raj.

RE: Having the RTT viewer after DFU

umrsraj — Wed, 03 Mar 2021 12:25:00 GMT

Hi Amanda,

--> Yes i Enabled NRF_LOG_ENABLED and NRF_LOG_BACKEND_RTT_ENABLED in sdk_config.h and i can see my LOG output in RTT viewer(j-link RTT viewer) when i program my board other than DFU(segger- Build and Run)

--> just for the clarity i am telling you again that - my problem is to see log data while application is running after i do DFU,

That means i have written my NRF_LOG_INFO() in the Application program

--> Iam using secure_bootloader(ble) as the base not secure_bootloader(ble_debug) for the Bootloader of my Application, (when i was testing the secure bootloader firstly i have tried with secure_bootloader_ble_debug only and it was worked fine with RTT Log data)

Best Regards,

Rajender.

RE: Having the RTT viewer after DFU

Amanda Hsieh — Tue, 02 Mar 2021 08:49:44 GMT

Hi Rajender,

Do you enable NRF_LOG_ENABLED and NRF_LOG_BACKEND_RTT_ENABLED in the sdk_config.h? You can refer to the sdk_config.h in the _debug project.

Do you use secure_bootloader(ble_debug) as the base? Are you able to use the secure_bootloader(ble_debug) for the test? Could you see the log from RTT viewer while only loading the secure_bootloader(ble_debug)? Does it advertise with the advertising name?

-Amanda H.

RE: Having the RTT viewer after DFU

umrsraj — Mon, 01 Mar 2021 16:26:57 GMT

Hi Amanda,

Thanks for the replay,

I'm using modified code of ble_app_uart example, Buttonless DFU, and secure_bootloader(ble).

when i program my Custom board without bootloader(using j-link of DK board) the RTT viewer works fine, but when i program using DFU method(using bootloader) it wont work, i.e., when i try to connect in RTT viewer app the BLE disconnects and program stops working.

Best Regards,

Rajender.

RE: Having the RTT viewer after DFU

Amanda Hsieh — Mon, 01 Mar 2021 13:35:50 GMT

Hi Rajender,

Are you using the bootloader example? If so, there are two types of examples and only the bootloaders with debug version provide the RTT log function.

May I know which example/code/image are you using?

-Amanda H.