NRF_LOG not working on Segger Embedded Studio

RE: NRF_LOG not working on Segger Embedded Studio

Matevz B — Wed, 30 Dec 2020 21:43:54 GMT

Thank you @Mauricio Farina, @SEGGER - Johannes and @awneil for bringing this issue up and solving it.

I hereby confirm that:

nordic RTT logging in Segger studio does not work

while in RTT Viewer it works and this is the case the last v17.0.2 SDK.

The fix is, as already written, set NRF_FPRINTF_FLAG_AUTOMATIC_CR_ON_LF_ENABLED 0 in sdk_config.h

I am repeating this as this has to be somehow brought up as the first search result in Google, and please Nordic, resolve it. I (and probably many others) have just lost several hours thinking it was my problem somewhere as it appeared while migrating from nrf5_SDK_for_Mesh_v4.0.0 to the last nRF5_SDK_17.0.2.

RE: NRF_LOG not working on Segger Embedded Studio

awneil — Fri, 16 Oct 2020 17:05:44 GMT

nRF5 SDK v17.0.2 is still getting this wrong in examples:

https://devzone.nordicsemi.com/f/nordic-q-a/67308/nrf5-sdk-v17-0-2-rtt-output-does-not-work-with-specified-ses-version

The fix remains to disable NRF_FPRINTF_FLAG_AUTOMATIC_CR_ON_LF_ENABLED:

that option is under 'nRF_Libraries'

RE: NRF_LOG not working on Segger Embedded Studio

Beldramma — Tue, 25 Aug 2020 09:56:54 GMT

Hi !

Usually my Debugger works but when I execute a function which returns a error message, i cannot see messages from NRF_LOG anymore.

uint32_t ble_cos_char_add(uint16_t                        service_handle,
                           ble_uuid_t                      uuid,
                           ble_cos_init_params             char_params,
                           ble_gatts_char_handles_t      * p_handles)
{
    // uuid type starts at 0x02, this is the index of the first base UUID we add. 0x03 will be the index of the second base UUID we add and etc
    // About exponent : actual value = Characteristic Value * 10^Exponent
    // About CPF description : WIKA number
    // About Namespace : SIG number or not
    if((uuid.type <= BLE_UUID_TYPE_UNKNOWN) || (uuid.type > (1 + NRF_SDH_BLE_VS_UUID_COUNT))
    || (char_params.read_access > SEC_SIGNED_MITM) || (char_params.read_access < SEC_NO_ACCESS) 
    || (char_params.write_access > SEC_SIGNED_MITM) || (char_params.write_access < SEC_NO_ACCESS) 
    || (char_params.cpf.format > BLE_GATT_CPF_FORMAT_STRUCT) || (char_params.cpf.format < BLE_GATT_CPF_FORMAT_BOOLEAN)
    || (char_params.cpf.name_space < BLE_GATT_CPF_NAMESPACE_DESCRIPTION_UNKNOWN) || (char_params.cpf.name_space > BLE_GATT_CPF_NAMESPACE_BTSIG) 
    /*|| (char_params.cpf.desc != WIKA_NUMBER)*/
    /*|| (char_params.cpf.unit < BLE_GATT_UNIT_UNITLESS)|| (char_params.cpf.unit > BLE_GATT_UNIT_CONCENTRATION_PARTS_PER_BILLION)*/)
    {
        NRF_LOG_INFO("Info: Unable to add characteristic to COS Service, invalid parameter");
        NRF_LOG_ERROR("Error: Unable to add characteristic to COS Service, invalid parameter");
        NRF_LOG_DEBUG("Debug: Unable to add characteristic to COS Service, invalid parameter");

        return NRF_ERROR_INVALID_PARAM;
    }

    if((char_params.len == 0) || (p_handles == NULL))
    {
        NRF_LOG_INFO("Info: Unable to add characteristic to COS Service, NULL parameter");
        NRF_LOG_ERROR("Error: Unable to add characteristic to COS Service, NULL parameter");
        NRF_LOG_DEBUG("Debug: Unable to add characteristic to COS Service, NULL parameter");
        return NRF_ERROR_NULL;
    }

    ble_add_char_params_t add_char_params;

    //APP_ERROR_CHECK_BOOL(char_params.p_value != NULL);
    //APP_ERROR_CHECK_BOOL(char_params.len > 0);

    memset(&add_char_params, 0, sizeof(add_char_params));

    add_char_params.uuid_type       = uuid.type;
    add_char_params.uuid            = uuid.uuid;
    add_char_params.max_len         = char_params.len;
    add_char_params.init_len        = char_params.len;

    if(char_params.p_value != NULL) add_char_params.p_init_value = char_params.p_value;
    else add_char_params.p_init_value = NULL;

    add_char_params.char_props.read = (char_params.read_access == 0) ? 0 : 1;
    add_char_params.read_access     = char_params.read_access;
    add_char_params.char_props.write = (char_params.write_access == 0) ? 0 : 1;
    add_char_params.write_access     = char_params.write_access;
    //add_char_params.p_presentation_format = &char_params.cpf;

    return characteristic_add(service_handle, &add_char_params, p_handles);
}

For example I have this function, and for now due to my parameters it returns NRF_ERROR_INVALID_PARAM. Thuis error code is given to the APP_ERROR_CHECK() MACRO. So when I have a function like that, I would like to see fastly where is the mistake, that's why I have put some nrf_log.

Do you have any ideas why it doesn't work ?

RE: NRF_LOG not working on Segger Embedded Studio

Gerrikoio — Sun, 02 Aug 2020 21:11:07 GMT

Following some beginner trial and error, I discovered that the solution (i.e. setting NRF_FPRINTF_FLAG_AUTOMATIC_CR_ON_LF_ENABLED to 0) does in fact work, but I needed to always manually connect the j-link target before going into a debug session... I think that was suggested by someone else on this post too.

EDIT. As a novice, I also noticed that there is some "buffering" or equivalent going on as the output is not always immediate. As in, if stepping into or out of code manually in debugging mode it does not always produce an immediate output response (both on UART and Debug). So, it looks as if something is not working but when in run mode you do see the output.

RE: NRF_LOG not working on Segger Embedded Studio

Gerrikoio — Sun, 02 Aug 2020 19:37:27 GMT

I'm using a PC with Linux OS (Ubuntu 18.04).

I've just installed SES Release 4.52c Build 2020051500.42136 (Linux x64).

I decided to use nRF5 SDK v16.0.0 and s113 (using nRF52811 chipset).

My very first example opened was "ble_app_uart_pca10040e..."

Using another document for guidance, I was able to configure, build, upload and initiate a debug session without issue.

However, I could not see the NRF_LOG_INFO output in the SES output terminal.

I searched online on the Segger Forum for any similar incidents.

This is the first one I found which looked similar: https://forum.segger.com/index.php/Thread/6589-SOLVED-No-RTT-Output-in-Debug-Terminal-on-MacOS/

Within this feed was a link to this Nordic Forum post, claiming that there was a solution.

I tried the suggested solution but it did not work ( NRF_FPRINTF_FLAG_AUTOMATIC_CR_ON_LF_ENABLED 0 )

Scrolling through the comments, it appears that this is an ongoing intermittent issue and that the solution is not 100% successful.

Considering that this issue was first raised on this forum over 1 year ago, is there any official solution to this problem.

As a complete novice to both SES and Nordic SDK's (on my very first example), the most likely scenario in my case is that I need to change some other default settings - maybe a reboot of SES is required, by way of example. Who knows.

Please could someone advise.

Thanks.

RE: NRF_LOG not working on Segger Embedded Studio

ethank — Sun, 26 Apr 2020 16:24:02 GMT

thanks, my segger is 4.50 with the following works for me.

NRF_LOG_BACKEND_RTT_ENABLED 1
NRF_FPRINTF_FLAG_AUTOMATIC_CR_ON_LF_ENABLED 0

RE: NRF_LOG not working on Segger Embedded Studio

Spegs21 — Tue, 17 Dec 2019 19:57:45 GMT

Thanks! This has been a huge PITA for awhile. I got so used to it I just gave up looking for a solution. I'd run J-Link Control Panel, Debug Viewer, and RTT Viewer just to pick up whatever I could on each. Should have looked again sooner.

RE: NRF_LOG not working on Segger Embedded Studio

EricDelangis — Fri, 15 Nov 2019 22:52:39 GMT

Line 7543 in 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 // Eric was 1
#endif

RE: NRF_LOG not working on Segger Embedded Studio

Jagbir — Fri, 15 Nov 2019 21:15:37 GMT

Eric,

I am having the exact problem with the ble_app_uart_c example.Where is the "NRF_FPRINTF_FLAG_AUTOMATIC_CR_ON_LF_ENABLED" re-defined in the sdk_config.h

Thanks

RE: NRF_LOG not working on Segger Embedded Studio

jonovos — Mon, 04 Nov 2019 16:03:58 GMT

This worked for me !!! ~~~~ Be careful, Johannes. You have a typographical error above. The flag referenced should be for "FPRINTF", not for "PRINTF".

I wasted an entire day last week, uninstalling, re-installing, trying two other computers, with no solution, until I *FOUND* this post!!!

RE: NRF_LOG not working on Segger Embedded Studio

EricDelangis — Fri, 01 Nov 2019 18:00:13 GMT

Problem solved for SES V4.30. Searched include files and found redefinition in sdk_config.h file. Changed that #definition and solved problem.

RE: NRF_LOG not working on Segger Embedded Studio

EricDelangis — Fri, 01 Nov 2019 17:41:23 GMT

I am having this problem still! The issue is intermittent. For some reason it will work for a few days or weeks then stops working for no apparent reason. I've followed ALL of the suggestions and settings in all of the reported cases I can find. As it stands now, I haven't been able to get any output on my Debut Terminal window for weeks. This makes my ability to develop anything severely limited.

Most recently, I tried updating my Segger SES version to 4.30 as well as rolling it back to 4.10. Nothing works. I get a blank window.

Please advise!

RE: NRF_LOG not working on Segger Embedded Studio

EricDelangis — Wed, 30 Oct 2019 18:04:44 GMT

I've been having this same problem. The debug terminal has been working intermittently. But now, it hasn't been working for weeks and I can't get it to work again. I've tried all the suggestions listed in all the threads, including this one, and no luck. I am currently running:

OS: Windows 10

Board: NRF52-DK

SDK: 15.3.0

Example: ble_app_uart_c

IDE: Segger Embedded Studio 4.30 (I was running 4.18 but tried upgrading to see if it solved the problem. It didn't)

I haven't tried rolling back to an earlier version of SES because I haven't found any info that definitively states which one should work.

To be clear... The debug terminal window shows the right hand scroll bar descending down the window as if it is displaying text but the window is blank.

Please advise.

RE: NRF_LOG not working on Segger Embedded Studio

awneil — Mon, 07 Oct 2019 16:37:33 GMT

[quote userid="18223" url="~/f/nordic-q-a/45985/nrf_log-not-working-on-segger-embedded-studio/182742"]In ES (V4.16) this clears the current line and does a line break.[/quote]

It seems this was a new feature in the Debug Viewer in SES v4.16:

https://forum.segger.com/index.php/Thread/6546-Debug-Terminal-broken-v3-40-v4-22/?postID=24051#post24051

So the problem didn't show up when using the Debug Viewer in earlier SES versions.

See: https://forum.segger.com/index.php/Thread/6546-Debug-Terminal-broken-v3-40-v4-22/

RE: NRF_LOG not working on Segger Embedded Studio

Collin — Thu, 15 Aug 2019 18:43:04 GMT

FWIW, I have found that, in GNUARMEclipse, if I stop a debug session with RTT viewer connected, the viewer will not show messages, even if I disconnect and reconnect. I have to close and reopen RTT Viewer, then connect, if I have had RTT Viewer connected when stopping a debug session.

RE: NRF_LOG not working on Segger Embedded Studio

JWCode — Thu, 15 Aug 2019 15:53:24 GMT

Figured it out. If I continually restart the debugger rather than simply press the play button, the debug terminal works. Thanks for the help

RE: NRF_LOG not working on Segger Embedded Studio

JWCode — Thu, 15 Aug 2019 15:52:07 GMT

No re-definitions to my knowledge. Debug terminal appears to only work sometimes. I either get a few outputs or the screen remains blank... any ideas?

RE: NRF_LOG not working on Segger Embedded Studio

kirkus — Thu, 15 Aug 2019 15:47:32 GMT

Did you double-check it's not getting re-defined further down the file?

RE: NRF_LOG not working on Segger Embedded Studio

JWCode — Thu, 15 Aug 2019 15:42:31 GMT

For some reason, this hasn't worked for me. Here is the start of my sdk_config.h file.

#define NRF_FPRINTF_FLAG_AUTOMATIC_CR_ON_LF_ENABLED 0
#define NRF_LOG_BACKEND_RTT_ENABLED 1
#define NRF_LOG_BACKEND_UART_ENABLED 0
#define NRF_LOG_ENABLED 1
#define NRF_LOG_DEFERRED 1

Am I forgetting something?

RE: NRF_LOG not working on Segger Embedded Studio

Joakim Jakobsen — Tue, 23 Apr 2019 08:58:57 GMT

Thanks for the input on this Johannes!

RE: NRF_LOG not working on Segger Embedded Studio

jacky4566 — Sun, 21 Apr 2019 16:39:51 GMT

I just struggle with this for a while..

This flag is already defined as NRF_FPRINTF_FLAG_AUTOMATIC_CR_ON_LF_ENABLED so trying to redefine NRF_PRINTF_FLAG_AUTOMATIC_CR_ON_LF_ENABLED wasn't working.

Anyway. got the RTT terminal working now. Just had to change the existing sdk_config flag line.

RE: NRF_LOG not working on Segger Embedded Studio

kirkus — Thu, 18 Apr 2019 13:58:25 GMT

this fixed the issue for me, thank you!

RE: NRF_LOG not working on Segger Embedded Studio

SEGGER - Johannes — Thu, 18 Apr 2019 13:02:16 GMT

Hi,

There is an issue in the SDK, which adds \r\r\n instead of \r\n to the output message.
postfix_process() wants to add \r\n, but nrf_printf() also explicitly adds \r before \n without checking if it is already present.

In ES (V4.16) this clears the current line and does a line break.

You can work around this by adding #define NRF_FPRINTF_FLAG_AUTOMATIC_CR_ON_LF_ENABLED 0 to your sdk_config.h

Best regards
Johannes

RE: NRF_LOG not working on Segger Embedded Studio

Joakim Jakobsen — Fri, 12 Apr 2019 09:21:51 GMT

Hi.

I can confirm that I'm seeing the same as you, although I'm not quite sure why yet.

However, if you take a look at the nRF5 SDK v.15.3.0 release notes you can see that the version of SES supported by this version of the SDK, is SES v.4.12.

If you downgrade to the previous version of SES, you should be able to see the output in the Debug Terminal.

Best regards,
Joakim Jakobsen.