Debug nRF9160 designs from master branch of nRF Connect SDK with SES

[bojan]

Hello there!

So far we were using v1.1.0 branch of nRF Connect SDK. However, we would like to experiment with the AWS IoT library so we were forced to move to the latest master branch of the nRF Connect SDK. Here is how I moved to the master branch:

 cd ncs/nrf
 git checkout master
 git pull
 west update

Here is what happens after west update command:

C:\Nordic\ncs\nrf>west update
=== updating zephyr (zephyr):
--- zephyr: checked out 924b7938af13d22feb5ee52b08ce807c788b5317 as detached HEAD
=== updating segger (modules\debug\segger):
--- segger: checked out 6fcf61606d6012d2c44129edc033f59331e268bc as detached HEAD
=== updating mbedtls (modules\crypto\mbedtls):
--- mbedtls: checked out 3776c158fe138a72c97c187e4d31c81c37884be9 as detached HEAD
=== updating mcuboot (bootloader\mcuboot):
--- mcuboot: checked out d0c2fbefd26e830ddff08b3060d7f16af5eccd26 as detached HEAD
=== updating mcumgr (modules\lib\mcumgr):
--- mcumgr: checked out 1afd6bbbfed0137b3156349f968634bbd8fc6fff as detached HEAD
=== updating tinycbor (modules\lib\tinycbor):
--- tinycbor: checked out 0fc68fceacd1efc1ce809c5880c380f3d98b7b6e as detached HEAD
=== updating ci-tools (tools\ci-tools):
--- ci-tools: checked out e869d2524d1344d80063bf2898095faf9228f7b5 as detached HEAD
=== updating net-tools (tools\net-tools):
--- net-tools: checked out 30b7efa827b04d2e47840716b0372737fe7d6c92 as detached HEAD
=== updating nrfxlib (nrfxlib):
--- nrfxlib: checked out 587634674ac33f719aab1a9b990cab0e835d49ee as detached HEAD
=== updating cmock (test\cmock):
--- cmock: checked out c243b9a7a7b3c471023193992b46cf1bd1910450 as detached HEAD
=== updating unity (test\cmock\vendor\unity):
--- unity: checked out 031f3bbe45f8adf504ca3d13e6f093869920b091 as detached HEAD
=== updating mbedtls-nrf (mbedtls):
--- mbedtls-nrf: checked out 04a049bda1ceca48060b57bc4bcf5203ce591421 as detached HEAD
=== updating civetweb (modules\lib\civetweb):
--- civetweb: checked out 99129c5efc907ea613c4b73ccff07581feb58a7a as detached HEAD
=== updating edtt (tools\edtt):
--- edtt: checked out dd4dd502ef2fbeced6ef7faaba562a7ddca45632 as detached HEAD
=== updating fatfs (modules\fs\fatfs):
--- fatfs: checked out 9ee6b9b9511151d0d64a74d532d39c6f2bbd4f16 as detached HEAD
=== updating hal_nordic (modules\hal\nordic):
--- hal_nordic: checked out 12d7647870888e4cb0e421f2b26884c2e76915ac as detached HEAD
=== updating hal_st (modules\hal\st):
--- hal_st: checked out fa481784b3c49780f18d50bafe00390ccb62b2ec as detached HEAD
=== updating libmetal (modules\hal\libmetal):
--- libmetal: checked out 45e630d6152824f807d3f919958605c4626cbdff as detached HEAD
=== updating loramac-node (modules\lib\loramac-node):
--- loramac-node: checked out 29e516ec585b1a909af2b5f1c60d83e7d4d563e3 as detached HEAD
=== updating lvgl (modules\lib\gui\lvgl):
--- lvgl: checked out 74fc2e753a997bd71cefa34dd9c56dcb954b42e2 as detached HEAD
=== updating nrf_hw_models (modules\bsim_hw_models\nrf_hw_models):
--- nrf_hw_models: checked out fec69703cb1ca06fcdab6d5fde01274f0fc5c759 as detached HEAD
=== updating open-amp (modules\lib\open-amp):
--- open-amp: checked out 9b591b289e1f37339bd038b5a1f0e6c8ad39c63a as detached HEAD
=== updating openthread (modules\lib\openthread):
--- openthread: checked out 3c6191eb4e8ca44b5f4eeaa696837bce14e83c69 as detached HEAD
=== updating littlefs (modules\fs\littlefs):
--- littlefs: checked out fe9572dd5a9fcf93a249daa4233012692bd2881d as detached HEAD
=== updating mipi-sys-t (modules\debug\mipi-sys-t):
--- mipi-sys-t: checked out baf51863f19f009b92e762115ba5572a5b996b92 as detached HEAD
=== updating canopennode (modules\lib\canopennode):
--- canopennode: checked out 5c6b0566d56264efd4bf23ed58bc7cb8b32fe063 as detached HEAD

After that, I tried to run some nRF Connect SDK projects from SES that were working under the branch v1.1.0. However, when I tried to debug the projects with Debug->Go from SES, here is what I get:

When I accept to build the project before debugging, here is what I get:

Do you have any idea of what the issue could be?

According to this thread from 11 months ago, something was wrong when building the projects from master branch with SES. Is this issue resolved ?

I also tried to build the project and flash nRF9160-DK board with the west tool:

west build -b nrf9160_pca10090ns -d build
west flash -d build

I used LTE Monitor app to see what is going on and here is what I get:

Do you guys have any idea what went wrong here? Can I use SES for building and debugging projects from master branch?

Thanks in advance for your time and efforts!

Sincerely,

Bojan.

[Heidi]

Hi!

There has been a reported bug using the debug function with SES on the master branch. So until this is fixed you won't be able to debug using SES while on the NCS master branch, unfortunately. 

Best regards,

Heidi

[bojan]

Hi Heidi.

Thanks for the update. No worries, we can survive and use LTE Monitor terminal for debugging. Please confirm that we can build from SES and debug using LTE Monitor terminal in master branch.

I tried to re-generate Hello World project from nRF Connect SDK tutorial within master branch and here is what I get:

1> Compiling ‘main.c’
1> ../src/main.c:2:10: fatal error: misc/printk.h: No such file or directory
1> compilation terminated.
Build failed

What changed in master branch that stops us to use misc/printk.h?

More imortant, is there any way we can benefit from AWS IoT library from within v1.1.0 branch?

Sincerley,

Bojan.

[bojan]

I figured out how to use printk() or printf() function in master branch. It is necessary to include

#include <stdio.h>
#include <sys/printk.h>

I can also confirm that LTE Monitor app can be used for debugging.

I will now see how can I benefit from AWS IoT library. One more question before I close this topic:

Which existing sample can I use to experiment with AWS IoT library (communicate with AWS IoT Cloud over MQTT)? Is mqtt_simple example appropriate for that?

Sincerely,

Bojan.

[Heidi]

You can use the Cloud Client example in nrf/samples/nrf9160, just change the CONFIG_CLOUD_BACKEND to use the AWS IoT library.