• State Verified Answer
  • Replies 2 replies
  • Subscribers 73 subscribers
  • Views 601 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 247169
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

SDK 16.0 output LOGs

Pablo G

Hi there,

Please, if someone can help me (or let me know of other people answered questions), I have multiple questions regarding Nordic's SDK 16.0. My board is nRF DK for nrf52832, and right now I am developing with terminal (my next step is to use a proper IDE,but for the moment I'm trying to figure out how to make it work with command line tools).

1. Why is RTT not included in the SDK? I was looking for it, but seems like it is not included. I manually included as I'm going to use it to debug, but is there a reason of why RTT was not within the SDK's components?


2. NRF_LOG or RTT commands? Which have you used for debug, which one you recommend?


3. I'm not able to see the NRF_LOGs with RTT Viewer. As I see, seems like the sdk_config.h should contain a field saying something like LOG_ENABLE_RTT or similar(to enable LOGs over UART or RTT). I'm looking into /examples/peripheral/uart/pca10040/blank/config/sdk_config.h. Do you know where can I find this option? I have the feeling that the project is trying to use UART for LOGs...

4. How can I debug using UART module using NRG_LOG via usb? Whenever I run the uart example, I connect the board to my Ubuntu PC and try to open a port, but I can only find the JLink interfac

df -h displays:

Filesystem      Size  Used Avail Use% Mounted on
udev            3,8G     0  3,8G   0% /dev
tmpfs           783M  1,7M  781M   1% /run
/dev/sda1       229G  123G   95G  57% /
tmpfs           3,9G   85M  3,8G   3% /dev/shm
tmpfs           5,0M  4,0K  5,0M   1% /run/lock
tmpfs           3,9G     0  3,9G   0% /sys/fs/cgroup
/dev/loop2      3,8M  3,8M     0 100% /snap/gnome-system-monitor/135
/dev/loop1      203M  203M     0 100% /snap/vlc/1397
/dev/loop5       15M   15M     0 100% /snap/gnome-characters/399
/dev/loop4      4,3M  4,3M     0 100% /snap/gnome-calculator/544
/dev/loop0       92M   92M     0 100% /snap/core/8689
/dev/loop7      225M  225M     0 100% /snap/wine-platform-runtime/94
/dev/loop6       92M   92M     0 100% /snap/core/8592
/dev/loop8      443M  443M     0 100% /snap/clion/103
/dev/loop9      3,8M  3,8M     0 100% /snap/gnome-system-monitor/127
/dev/loop3       15M   15M     0 100% /snap/gnome-characters/495
/dev/loop11     4,4M  4,4M     0 100% /snap/gnome-calculator/704
/dev/loop10     4,0M  4,0M     0 100% /snap/notepad-plus-plus/225
/dev/loop12      49M   49M     0 100% /snap/gtk-common-themes/1474
/dev/loop14     1,0M  1,0M     0 100% /snap/gnome-logs/81
/dev/loop13     143M  143M     0 100% /snap/slack/22
/dev/loop15      45M   45M     0 100% /snap/gtk-common-themes/1440
/dev/loop16     1,0M  1,0M     0 100% /snap/gnome-logs/93
/dev/loop17      55M   55M     0 100% /snap/core18/1705
/dev/loop18     444M  444M     0 100% /snap/clion/107
/dev/loop19      55M   55M     0 100% /snap/core18/1668
/dev/loop20     143M  143M     0 100% /snap/slack/21
/dev/loop21      74M   74M     0 100% /snap/wine-platform-3-stable/6
tmpfs           783M   92K  783M   1% /run/user/1000
/dev/loop22     227M  227M     0 100% /snap/wine-platform-runtime/104
/dev/loop23     4,0M  4,0M     0 100% /snap/notepad-plus-plus/227
/dev/loop24     161M  161M     0 100% /snap/gnome-3-28-1804/116
/dev/sdb         11M  128K   11M   2% /media/pablo/JLINK
.

How can I connect the uart from the nRF52 so I can open a COM port with Putty or similar?


Thank you for your time,
Pablo G

Parents
  • +1

    Hi Pablo,

    1. It's located in \nRF5_SDK_16.0.0_98a08e2\external\ because it's made by a third-party. Segger in this case.

    2. NRF_LOG because it offers more features and is already integrated into most of the SDK examples and modules. RTT is one of the supported logger backends. See Logger module for more details.

    3. The UART peripheral example does not use the logger module. To test RTT I suggest you try the \examples\peripheral\fpu_fft\pca10040\blank example and make sure the 'NRF_LOG_BACKEND_RTT_ENABLED' option is enabled in sdk_config.h

    4. It should show up as "ttyACMx" in /dev/ - ls /dev/ | grep ttyACM

    Best regards,

    Vidar

Reply
  • +1

    Hi Pablo,

    1. It's located in \nRF5_SDK_16.0.0_98a08e2\external\ because it's made by a third-party. Segger in this case.

    2. NRF_LOG because it offers more features and is already integrated into most of the SDK examples and modules. RTT is one of the supported logger backends. See Logger module for more details.

    3. The UART peripheral example does not use the logger module. To test RTT I suggest you try the \examples\peripheral\fpu_fft\pca10040\blank example and make sure the 'NRF_LOG_BACKEND_RTT_ENABLED' option is enabled in sdk_config.h

    4. It should show up as "ttyACMx" in /dev/ - ls /dev/ | grep ttyACM

    Best regards,

    Vidar

Children
Related
Terms of service