Is it necessary to remove SEGGER_RTT_printf() at release?

In the software development for the nRF52832, the SEGGER_RTT_printf() function is called throughout the code for debugging and problem analysis.

Would there be any particular problems if we leave these in and apply them to mass production?

Parents
  • Hi,

    RTT works by writing to a RAM buffer that is subsequently read via SWD. The only significant downside by keeping is that that means that you will spend CPU time and energy on processing logs that are never read, but other than that it should be OK.

    One additional detail is that the RTT mode should not be SEGGER_RTT_MODE_BLOCK_IF_FIFO_FULL, as that would cause code to halt when the buffer is full (the default mode is  CONFIG_SEGGER_RTT_MODE_NO_BLOCK_SKIP, so this should not be a problem, but I mention it just in case).

Reply
  • Hi,

    RTT works by writing to a RAM buffer that is subsequently read via SWD. The only significant downside by keeping is that that means that you will spend CPU time and energy on processing logs that are never read, but other than that it should be OK.

    One additional detail is that the RTT mode should not be SEGGER_RTT_MODE_BLOCK_IF_FIFO_FULL, as that would cause code to halt when the buffer is full (the default mode is  CONFIG_SEGGER_RTT_MODE_NO_BLOCK_SKIP, so this should not be a problem, but I mention it just in case).

Children
No Data
Related