Blog Archives - All Comments

RE: nRF Connect SDK Tutorial - Part 3 | NCS v1.3.0

user94403 — Thu, 29 Oct 2020 09:44:17 GMT

I am not able to use debug window using printk() function, its empty

RE: nRF Connect SDK Tutorial - Part 3 | NCS v1.2.0

user78215 — Tue, 08 Sep 2020 09:32:38 GMT

I think for custom board the following two modifications are not needed any more

[embed:dc8ab71f-3b98-42d9-b0f6-e21e02a0f8e2:4892b8dc-4be7-46f4-be38-b3bdeb4a1f9c:type=text&text=include%28%24ENV%7BZEPHYR_BASE%7D%2F..%2Fnrf%2Fcmake%2Fboilerplate.cmake%29]

[embed:dc8ab71f-3b98-42d9-b0f6-e21e02a0f8e2:7517bf58-353d-423f-8e47-9dc128570e9e:type=text&text=set%28nonsecure_boards_with_ns_suffix%0D%0A%20%20%20%20%3A%0D%0A%20%20%20%20%3A%0D%0A%20%20%20%20nrf9160_testns%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%23Added%20this%0D%0A%20%20%20%20%3A%0D%0A%29]

regards

RE: nRF Connect SDK Tutorial - Part 2 | NCS v1.3.0

user2241 — Tue, 01 Sep 2020 16:14:27 GMT

Hi

Add the ADC peripheral section needs to be updated when running on the 9160DK board because the code that needs to be copy and pasted for main.c is 5340 specific.

RE: nRF Connect SDK Tutorial - Part 1 | NCS v1.2.0

user91631 — Thu, 02 Jul 2020 15:33:09 GMT

When I followed this instruction on the stage of "Open nRF Connect SDK Project" I had an error:
[embed:dc8ab71f-3b98-42d9-b0f6-e21e02a0f8e2:e754a41a-157b-4ac7-b010-c7d863d0715e:type=text&text=CMake%20Error%20at%20%2Fhome%2Froman%2Fnordic%2Fncs%2Fnrf%2Fcmake%2Fboilerplate.cmake%3A12%20%28include%29%3A%0D%0A%20%20include%20could%20not%20find%20load%20file%3A%0D%0A%0D%0A%20%20%20%20%2Fboards%2Fdeprecated.cmake%0D%0ACall%20Stack%20%28most%20recent%20call%20first%29%3A%0D%0A%20%20CMakeLists.txt%3A2%20%28include%29%0D%0A%0D%0A%0D%0Anrf5340pdk_nrf5340_cpuapp.dts.pre.tmp%3A95.42-107.3%3A%20Warning%20%28unique_unit_address_if_enabled%29%3A%20%2Fsoc%2Fperipheral%4050000000%2Fflash-controller%4039000%3A%20duplicate%20unit-address%20%28also%20used%20in%20node%20%2Fsoc%2Fperipheral%4050000000%2Fkmu%4039000%29%0D%0Anrf5340pdk_nrf5340_cpuapp.dts.pre.tmp%3A369.19-375.3%3A%20Warning%20%28unique_unit_address_if_enabled%29%3A%20%2Fsoc%2Fperipheral%4050000000%2Fclock%405000%3A%20duplicate%20unit-address%20%28also%20used%20in%20node%20%2Fsoc%2Fperipheral%4050000000%2Fpower%405000%29%0D%0Anrf5340pdk_nrf5340_cpuapp.dts.pre.tmp%3A616.31-617.5%3A%20Warning%20%28unique_unit_address_if_enabled%29%3A%20%2Freserved-memory%2Fimage%4020000000%3A%20duplicate%20unit-address%20%28also%20used%20in%20node%20%2Freserved-memory%2Fimage_s%4020000000%29%0D%0A%20%20also%20defined%20at%20nrf5340pdk_nrf5340_cpuapp.dts.pre.tmp%3A636.14-638.3%0D%0A%0D%0Aerror%3A%20UART_0_NRF_UARTE%20%28defined%20at%20drivers%2Fserial%2FKconfig.nrfx%3A31%29%20is%20assigned%20in%20a%20configuration%0D%0Afile%2C%20but%20is%20not%20directly%20user-configurable%20%28has%20no%20prompt%29.%20It%20gets%20its%20value%20indirectly%20from%20other%0D%0Asymbols.%20See%20http%3A%2F%2Fdocs.zephyrproject.org%2Flatest%2Freference%2Fkconfig%2FCONFIG_UART_0_NRF_UARTE.html%0D%0Aand%2For%20look%20up%20UART_0_NRF_UARTE%20in%20the%20menuconfig%2Fguiconfig%20interface.%20The%20Application%20Development%0D%0APrimer%2C%20Setting%20Configuration%20Values%2C%20and%20Kconfig%20-%20Tips%20and%20Best%20Practices%20sections%20of%20the%20manual%0D%0Amight%20be%20helpful%20too.%0D%0A%0D%0ACMake%20Error%20at%20%2Fhome%2Froman%2Fnordic%2Fncs%2Fzephyr%2Fcmake%2Fkconfig.cmake%3A217%20%28message%29%3A%0D%0A%20%20command%20failed%20with%20return%20code%3A%201%0D%0ACall%20Stack%20%28most%20recent%20call%20first%29%3A%0D%0A%20%20%2Fhome%2Froman%2Fnordic%2Fncs%2Fzephyr%2Fcmake%2Fapp%2Fboilerplate.cmake%3A506%20%28include%29%0D%0A%20%20CMakeLists.txt%3A3%20%28include%29]

But when I removed all content in "prj.conf" and in "CMakeLists.txt" file I replaced
[embed:dc8ab71f-3b98-42d9-b0f6-e21e02a0f8e2:065ceb0d-1c21-423e-909e-55b7e910d4a5:type=text&text=include%28%24ENV%7BZEPHYR_BASE%7D%2F..%2Fnrf%2Fcmake%2Fboilerplate.cmake%29%0D%0Ainclude%28%24ENV%7BZEPHYR_BASE%7D%2Fcmake%2Fapp%2Fboilerplate.cmake%20NO_POLICY_SCOPE%29]
on
[embed:dc8ab71f-3b98-42d9-b0f6-e21e02a0f8e2:7f45c2f1-8b50-4913-aebb-e8c9e81da5a3:type=text&text=find_package%28Zephyr%20HINTS%20%24ENV%7BZEPHYR_BASE%7D%29]
then everything worked properly.

RE: nRF Connect SDK Tutorial - Part 2 | NCS v1.2.0

user90623 — Sat, 27 Jun 2020 22:21:45 GMT

Hello, I found this issue when try "west init -l hello_world", I installed the tools with the toolchain. Some suggestion?

RE: nRF Connect SDK Tutorial - Part 1 | NCS v1.2.0

user67192 — Sat, 09 May 2020 20:02:46 GMT

Great tutorial.

When attempting to Build and flash - using SEGGER Embedded Studio for nRF52840-pca10056 on macOS we ran into a couple of issues:

1. Unclear whether one should create a Segger .proj file. We assume one should point to directory created earlier in tutorial, however it doesn't have a .proj file, so we created a new one and added main.c. Unclear if ok to leave `Toolchain Root Directory = $(StudioDir)/gcc/$(GCCTarget)/bin` or need to change this.

(Note: When opening Segger, it initially pointed to a Hello world file that is located in same dir as the Segger application, however that sub dir doesn't have a CMakeLists.tx file, so didn't seem right either.)

2. After opening`File → Open nRF Connect SDK Project...` , configuring and pressing <ok> the project starts to build, but we got a CMake error. We determined there was an extra space in value for

Tools->Options->nRF Connect ->Additional CMake Options `-D WEST=/usr/local/bin/west`

(should be `-DWEST=...`

3. Once above was fixed, we were able to start building, however the build failed when compiling uart_nrfx_uarte.c. Several MACRO are undefined, including UARTE_CONFIG and DT_NORDIC_NRF_UARTE_UART_0_CURRENT_SPEED. Reported build error is

uart_nrfx_uarte.c:1396:9: error: 'DT_NORDIC_NRF_UARTE_UART_0_LABEL' undeclared here


4. To address this plunged into the Kconfig settings
Project->Configure nRF Connect .. which brings up a GUI for setting Kconfig
In top right corner entered UARTE in search box. In the displayed driver options
selected `Modules -> nrfx drivers ->Enable UARTE driver` and `Enable UARTE0 instance`
Hit configure and then rebuild. Even after this, we get same error and can't see 
any obvious Kconfig errors. 
Note: Segger editor shows which MACROs and #define that are true,
which is very useful when hunting down Kconfig problems.

At this point stumped on how to move forward....

RE: nRF Connect SDK Tutorial - Part 3 | NCS v1.2.0

user84466 — Fri, 08 May 2020 13:39:46 GMT

Regarding using Ozone as a debugger. We have a multi image build, meaning we cant load zephyr.elf. We have to load merged.hex, which does not include symbol information. Question is how to setup symbol/source information when loading a hex file?

RE: nRF Connect SDK Tutorial - Part 3 | NCS v1.2.0

user84466 — Fri, 08 May 2020 13:31:46 GMT

RE: nRF Connect SDK Tutorial - Part 2 | NCS v1.2.0

user25696 — Thu, 07 May 2020 18:32:22 GMT

FYI I used the nRF5340-PDK board for the light_controller solution.

For section 3.5 of the Tutorial Part 2, I used P2 pin 1 to connect to P0.04 and P1 pin 7 to connect to ground.

Rather than using a potentiometer I used a benchtop power supply and found that LED2 was brightest when P0.04 was driven to 0V and it went completely dark when P0.04 was driven to about 1.8V

RE: nRF Connect SDK Tutorial - Part 1 | NCS v1.2.0

user13946 — Mon, 04 May 2020 16:37:25 GMT

for those using the toolchain manger, you need to run all of your terminal commands using the git-bash.exe termianl in the NCS/toolchain folder.

RE: nRF Connect SDK Tutorial - Part 1 | NCS v1.2.0

user84645 — Wed, 26 Feb 2020 10:24:44 GMT

For those wondering how to build for Thingy91 (I prefer this little guy since it has awesome sensors on-board):

Include NRF boilerplate to your CMakeLists.txt, include($ENV{ZEPHYR_BASE}/../nrf/cmake/boilerplate.cmake)

E.g.:

[embed:dc8ab71f-3b98-42d9-b0f6-e21e02a0f8e2:05477a1d-da6a-46e1-addd-f3040bd6d0fb:type=c_cpp&text=cmake_minimum_required%28VERSION%203.13.1%29%0D%0Ainclude%28%24ENV%7BZEPHYR_BASE%7D%2F..%2Fnrf%2Fcmake%2Fboilerplate.cmake%29%0D%0Ainclude%28%24ENV%7BZEPHYR_BASE%7D%2Fcmake%2Fapp%2Fboilerplate.cmake%20NO_POLICY_SCOPE%29%0D%0Aproject%28NONE%29%0D%0Atarget_sources%28app%20PRIVATE%20src%2Fmain.c%29]

Then build using cmake directly (not sure how to set board directly with west, unless with environment variables):

cmake -GNinja -DBOARD=nrf9160_pca20035ns -DBOARD_DIR=%ZEPHYR_BASE%/../nrf/boards/arm/nrf9160_pca20035 -Bbuild

or if you are using bash/mingw/*nix:

cmake -GNinja -DBOARD=nrf9160_pca20035ns -DBOARD_DIR=$ZEPHYR_BASE/../nrf/boards/arm/nrf9160_pca20035 -Bbuild