Getting started - All Comments

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

user115295 — 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)

user85992 — 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)

user111847 — 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: nRF9160 Developing for Production

user66115 — Mon, 18 Oct 2021 10:37:41 GMT

@Aziz

You can now decrypt the IP communication from the modem trace using the latest Trace Collector app in nRF Connect for Desktop which can be very helpful information when debugging your application

RE: Getting Started with nRF9160 DK

user104732 — Wed, 26 May 2021 09:35:27 GMT

Hello, thank you for your tutorial!

I followed all the steps of the tutorial, I was able to check all the points in the Getting started assistant. I use the NRF9160 DK. When i create an nrf connect sdk project I have an error that I don't understand. The terminal say :

[embed:dc8ab71f-3b98-42d9-b0f6-e21e02a0f8e2:4c42ea87-13b7-483a-b5ca-74e0bac323f2:type=text&text=Creating%20solution%20hello_world.emProject%0D%0AC%3A%2FProgram%20Files%2FCMake%2Fbin%2Fcmake.exe%20-GNinja%20-DBOARD%3Dnrf9160dk_nrf9160%20-DBOARD_DIR%3DD%3A%5Clogiciels%20stage%5CCode%20source%5Cncs%5Czephyr%5Cboards%5Carm%5Cnrf9160dk_nrf9160%20-BD%3A%5Clogiciels%20stage%5CCode%20source%5Cncs%5Czephyr%5Csamples%5Chello_world%5Cbuild_nrf9160dk_nrf9160%20-SD%3A%5Clogiciels%20stage%5CCode%20source%5Cncs%5Czephyr%5Csamples%5Chello_world%20-DZEPHYR_TOOLCHAIN_VARIANT%3Dgnuarmemb%20-DGNUARMEMB_TOOLCHAIN_PATH%3DC%3A%5Cgnuarmemb%5C9%202019-q4-major%20-DPYTHON_EXECUTABLE%3DC%3A%2FPython39%2Fpython.exe%20-DCMAKE_MAKE_PROGRAM%3DC%3A%2FProgramData%2Fchocolatey%2Fbin%2Fninja.exe%20-DDTC%3DC%3A%2FProgramData%2Fchocolatey%2Fbin%2Fdtc.exe%20-DEXTRA_KCONFIG_TARGETS%3Dmenuconfig_ses%20-DEXTRA_KCONFIG_TARGET_COMMAND_FOR_menuconfig_ses%3DD%3A%5Clogiciels%20stage%5Cemstudio%5Carm_segger_embedded_studio_v534a_win_x64_nordic%2Fhtml%2Fconfigure_nordic_project_menuconfig.py%0D%0A--%20Application%3A%20D%3A%2Flogiciels%20stage%2FCode%20source%2Fncs%2Fzephyr%2Fsamples%2Fhello_world%0D%0A--%20Zephyr%20version%3A%202.4.99%20%28D%3A%2Flogiciels%20stage%2FCode%20source%2Fncs%2Fzephyr%29%0D%0A--%20Found%20Python3%3A%20D%3A%2Flogiciels%20stage%2Fv1.5.1%2Ftoolchain%2Fopt%2Fbin%2Fpython.exe%20%28found%20suitable%20exact%20version%20%223.8.2%22%29%20found%20components%3A%20Interpreter%20%0D%0A--%20Found%20west%20%28found%20suitable%20version%20%220.9.0%22%2C%20minimum%20required%20is%20%220.7.1%22%29%0D%0A--%20Board%3A%20nrf9160dk_nrf9160%2C%20Revision%3A%200.7.0%0D%0A--%20Cache%20files%20will%20be%20written%20to%3A%20D%3A%2Flogiciels%20stage%2FCode%20source%2Fncs%2Fzephyr%2F.cache%0D%0A--%20Found%20dtc%3A%20C%3A%2FProgramData%2Fchocolatey%2Fbin%2Fdtc.exe%20%28found%20suitable%20version%20%221.5.0%22%2C%20minimum%20required%20is%20%221.4.6%22%29%0D%0A--%20Found%20toolchain%3A%20gnuarmemb%20%28C%3A%2Fgnuarmemb%2F9%202019-q4-major%29%0D%0A--%20Found%20BOARD.dts%3A%20D%3A%2Flogiciels%20stage%2FCode%20source%2Fncs%2Fzephyr%2Fboards%2Farm%2Fnrf9160dk_nrf9160%2Fnrf9160dk_nrf9160.dts%0D%0A--%20Generated%20zephyr.dts%3A%20D%3A%2Flogiciels%20stage%2FCode%20source%2Fncs%2Fzephyr%2Fsamples%2Fhello_world%2Fbuild_nrf9160dk_nrf9160%2Fzephyr%2Fzephyr.dts%0D%0A--%20Generated%20devicetree_unfixed.h%3A%20D%3A%2Flogiciels%20stage%2FCode%20source%2Fncs%2Fzephyr%2Fsamples%2Fhello_world%2Fbuild_nrf9160dk_nrf9160%2Fzephyr%2Finclude%2Fgenerated%2Fdevicetree_unfixed.h%0D%0A--%20Generated%20device_extern.h%3A%20D%3A%2Flogiciels%20stage%2FCode%20source%2Fncs%2Fzephyr%2Fsamples%2Fhello_world%2Fbuild_nrf9160dk_nrf9160%2Fzephyr%2Finclude%2Fgenerated%2Fdevice_extern.h%0D%0A--%20Configuring%20incomplete%2C%20errors%20occurred%21%0D%0AIncluding%20boilerplate%20%28Zephyr%20base%29%3A%20D%3A%2Flogiciels%20stage%2FCode%20source%2Fncs%2Fzephyr%2Fcmake%2Fapp%2Fboilerplate.cmake%0D%0A--%20Using%20NCS%20Toolchain%201.5.1%20for%20building.%20%28D%3A%2Flogiciels%20stage%2Fv1.5.1%2Ftoolchain%2Fcmake%29%0D%0Anrf9160dk_nrf9160.dts.pre.tmp%3A59.42-71.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%0Anrf9160dk_nrf9160.dts.pre.tmp%3A311.19-317.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%0ACMake%20Error%20at%20D%3A%2Flogiciels%20stage%2FCode%20source%2Fncs%2Fzephyr%2Fcmake%2Fkconfig.cmake%3A204%20%28message%29%3A%0D%0A%20%20File%20not%20found%3A%20D%3A%2Flogiciels%0D%0ACall%20Stack%20%28most%20recent%20call%20first%29%3A%0D%0A%20%20D%3A%2Flogiciels%20stage%2FCode%20source%2Fncs%2Fzephyr%2Fcmake%2Fapp%2Fboilerplate.cmake%3A534%20%28include%29%0D%0A%20%20D%3A%2Flogiciels%20stage%2FCode%20source%2Fncs%2Fzephyr%2Fshare%2Fzephyr-package%2Fcmake%2FZephyrConfig.cmake%3A24%20%28include%29%0D%0A%20%20D%3A%2Flogiciels%20stage%2FCode%20source%2Fncs%2Fzephyr%2Fshare%2Fzephyr-package%2Fcmake%2FZephyrConfig.cmake%3A35%20%28include_boilerplate%29%0D%0A%20%20CMakeLists.txt%3A5%20%28find_package%29%0D%0A%0D%0A%0D%0A%0D%0Aerror%3A%20cmake%20failed%0D%0Acreate_nordic_project.py%20failed%20%281%29]

Do you have any idea of the source of the problem?
Thank you in advance for your help

RE: nRF9160 Developing for Production

user104315 — Thu, 20 May 2021 19:32:22 GMT

As a developer, can I open the modem trace for my own debugging/troubleshooting? I see it is a binary file so I'm not sure how to understand it.

RE: How to get modem trace using “Trace Collector” in nRF Connect

user97306 — Mon, 22 Mar 2021 17:19:00 GMT

Step 2 informs to use SW5 but is that nowadays SW10?

RE: Thingy:91 Firmware Update using MCUboot

user16646 — Sat, 21 Nov 2020 01:21:47 GMT

When installing mcumgr, it's a good idea to use the -v verbose. Otherwise, you might get the impression that go has gone off into the weeds.

go get -v github.com/apache/mynewt-mcumgr-cli/mcumgr

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

user2124 — Tue, 10 Nov 2020 13:19:55 GMT

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

RE: How to get modem trace using “Trace Collector” in nRF Connect

user2124 — Fri, 30 Oct 2020 12:44:52 GMT

Updated description for Thingy:91. tested with mfw 1.2.1 and the latest official f/w(thingy91_fw_2020-09-23_b6ad40d0).

RE: Thingy:91 Firmware Update using MCUboot

user93510 — Wed, 28 Oct 2020 01:37:22 GMT

While running

west build -b nrf9160_pca20035ns

I am getting :

ERROR: Build directory C:\Users\parva\ncs\v1.3.1\nrf\applications\asset_tracker\build targets board thingy91_nrf9160ns, but board nrf9160_pca20035ns was specified. (Clean the directory, use --pristine, or use --build-dir to specify a different one.)
FATAL ERROR: refusing to proceed without --force due to the above error

so, I changed the board name to thingy91_nrf9160ns and then I was getting this error:

FATAL ERROR: command exited with status 1: 'C:\Program Files\CMake\bin\cmake.EXE' '-BC:\Users\parva\ncs\v1.3.1\nrf\applications\asset_tracker\build' '-SC:\Users\parva\ncs\v1.3.1\nrf\applications\asset_tracker' -GNinja

What to do about it?

RE: How to get modem trace using “Trace Collector” in nRF Connect

user89282 — Wed, 09 Sep 2020 02:29:50 GMT

Hey there it looks like this process isn't working with mfw 1.2.1

RE: Thingy:91 Firmware Update using MCUboot

user6610 — Thu, 27 Aug 2020 15:58:22 GMT

Does the same command apply to modem firmware dfu?

My target is running mfw_nrf9160_1.2.0 and I tried providing mfw_nrf9160_update_from_1.2.0_to_1.2.0-FOTA-TEST.bin as the <image>. It always fail with error 3.

RE: Announcing the nRF Connect for Cloud Device API Preview

user90926 — Thu, 30 Jul 2020 11:00:29 GMT

Is the source code of nRFCloud and APIs available on github?

Thanks

RE: How to get modem trace using “Trace Collector” in nRF Connect

user92019 — Thu, 30 Jul 2020 09:26:35 GMT

Where to write this prj.conf file in windows ?