debug terminal does not appear in Segger Embedded Studio

[leejh]

Hello, Nordic.

A while ago, debug terminal do not appear in Segger Embedded Studio, and nothing happens when I click View -> debug terminal in the tab bar.

Currently in use

- SEGGER Embedded Studio V4.30c

- JLINK V6.54c

It doesn't work suddenly while using well. The same thing happens if I try to reinstall or downgrade SES. When I run JLINK-VIEWER, the log is displayed intermittently.

I would like to check inside SES as before rather than seeing it in other viewers via SEGGER_RTT_print/writeString.

Is there a way?

Thanks.

[Jimmy Wong]

You only need to change NRF_FPRINTF_FLAG_AUTOMATIC_CR_ON_LF_ENABLED from 1 to 0 inside the sdk_config.h

// <q> NRF_FPRINTF_FLAG_AUTOMATIC_CR_ON_LF_ENABLED - For each printed LF, function will add CR.

#ifndef NRF_FPRINTF_FLAG_AUTOMATIC_CR_ON_LF_ENABLED
#define NRF_FPRINTF_FLAG_AUTOMATIC_CR_ON_LF_ENABLED 0
#endif

[leejh]

Hello, Jimmy Wong.

I don't have NRF_FPRINTF_FLAG_AUTOMATIC_CR_ON_LF_ENABLED in sdk_config.h

  // <q> NRF_FPRINTF_ENABLED - nrf_fprintf - fprintf function.

#ifndef NRF_FPRINTF_ENABLED
#define NRF_FPRINTF_ENABLED 1
#endif

Add what you say below the above (I used ble_app_uart_c).

But debug terminal still does not work.

[Jimmy Wong]

Hi,

which sdk verison do you use?  this option is added after the SDK 15.0 or later.

you can try my example

https://github.com/jimmywong2003/SES-Project-For-NRF51/tree/master/ble_app_uart_bas_baseline (SDK 12.3)

or 

https://github.com/jimmywong2003/nrf52-ble-range-estimator (SDK15.3)

[leejh]

I currently use SDK15.0.0 version. I can't find NRF_FPRINTF_FLAG_AUTOMATIC_CR_ON_LF_ENABLED

[Einar Thorsrud]

Hi,

I believe NRF_FPRINTF_FLAG_AUTOMATIC_CR_ON_LF_ENABLED was introduced in SDK 15.3, so it does not seem relevant in this case where you use SDK 15.0, even though that was my first thought as well.

Other possible explanations include:

• J-Link Viewer opens at the same time as SES. Could that be the case?
• Incompatible older SES/J-Link library. Can you try to reinstall both SES and the J-Link driver package? If you install SES first, then the J-Link installer should ask you if you want to update the J-Link DLL in SES as part of the install process.

[leejh]

Hi Einar Thorsrud.

I've tried reinstalling, deleting and downgrading both SES and J-LINK. However, none of methods allowed the debug terminal to appear.

Maybe, my "SEGGER Embedded Studio V4.30c" and "JLINK V6.54c" are incompatible or unstable?

Let me know each version that has been verified, I will change it.

Finally, I don't know what you saying that J-Link Viewer opens at the same time as SES.

[Einar Thorsrud]

Hi,

I do not recall any issue with RTT due to incompatibilities, but it is possible. Do you use a .zip distribution of SES, or an installed one? If you use an installed one, then you just need to install the latest J-Link package and select that you want to update the J-Link DLL in SES as well. Then you know you have the latest version in SES.

Regarding the RTT Viewer, my question is if you have that open at the same time as you have SES open? In that case, only one of them will actually be able to display the RTT data (or you sill see some incomplete pieces of data on both) since both will update the pointers in the circular RTT buffer when reading.

If none of the above seems to help, I wonder if you could test with an unmodified SDK example that uses RTT logging, and see if that works for you. For instance, from \examples\crypto\nrf_crypto\hmac\, since that has RTT logging enabled by default. Does that work if you test the precompiled hex file and test with the RTT Viewer? What if you build yourself and test with RTT Viewer? And what when you try to display the log in SES?