Blog Archives - All Comments

RE: iBasis Global Access for Things Frequently Asked Questions (FAQ)

SILVANO CERINI — Fri, 29 Apr 2022 15:15:08 GMT

Ibasis doesn't work in Italy. Can I activate a 1nCE sim instead of ibasis ?

RE: iBasis Global Access for Things Frequently Asked Questions (FAQ)

Matthew C Clark — Wed, 06 Apr 2022 21:23:33 GMT

I lost my iBASIS sim. What number do I call in the USA to get another? "Nordic Sales" is a terribly vague term.

RE: iBasis Global Access for Things Frequently Asked Questions (FAQ)

Konstantinos Papadopoulos — Fri, 10 Dec 2021 21:45:48 GMT

I only have problems with the iBASIS SIM card. When I tried the SIM card inckuded with the Thingy:91, during activation I got the message the SIM is expired. Get in touch with the support for replacement. I got a new one after almost a week, during activation I get the message "Vendor for 89.......... not found!." I can't activate the new SIM card. What a waste of time and money!!!!!!!!!!

RE: External GPS antenna on nRF9160 DK

KarlPeters — Thu, 04 Feb 2021 13:14:11 GMT

Hi Guys, just wanted to check if anyone had any recommendations for a smaller GPS antenna suitable for nrf9160 than the ones mentioned in the first post of this thread? Looking to fit it inside the enclosure we're designing for a nrf9160 based product.

RE: External GPS antenna on nRF9160 DK

Chandra2sekhar — Thu, 03 Dec 2020 17:21:54 GMT

Hello,
While thinking Active antenna can be easy to use, we have used M20057-1 antenna from antennova, tuning is really a messy task,and from 2 months trying, unable to get the gps fix using the gps example...does any one can help in this matter,

RE: iBasis Global Access for Things Frequently Asked Questions (FAQ)

Brian Kim — Tue, 10 Nov 2020 13:19:55 GMT

Thanks for up-to-dated information from iBasis... [emoticon:c4563cd7d5574777a71c318021cbbcc8]

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

sanjay kumar — 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

kk2mkk — 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

Mahendra Tailor — 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

RAlexeev — 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: External GPS antenna on nRF9160 DK

Simejis — Wed, 01 Jul 2020 12:54:55 GMT

Woudl the internal GPS antena wwork on this rev? THe related errata only mentions v0.7.0 and v0.8.2 ?

RE: External GPS antenna on nRF9160 DK

Simejis — Wed, 01 Jul 2020 12:53:25 GMT

Hello, one of our customers purchased this Dev Kit and received rev 0.8.3, which is not mentioned above in conjunction with the GPS antenna.

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

ReneDelgado — 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

erik — 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

Bjorn191023 — 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?