Search Result

256 results found on Nordicsemi

Article 12 | News 206 | Product 38 | All results

9534 results found on DevZone

NordicSemi

nRF9160

Low power SiP with integrated LTE-M/NB-IoT modem and GNSS

Product

nRF9160 DK

Cellular IoT development kit for LTE-M, NB-IoT, GNSS and Bluetooth LE

Product

Nordic nRF9160-powered asset tracker monitors location and position of valuable shipments via Wi-Fi, cellular signals, and GPS, and offers multi-year battery life

Crosby Technologies’ ShipSafe offers Wi-Fi based 10-meter positional accuracy and uses Nordic nRF9160 SiP’s powerful application processor and LTE-M connectivity to support asset tracking application with two years of battery life from a 3200mAh LiPo battery

Tags: nRF9160, LTE-M, NB-IoT, Transportation, nRF91 Series

News

9/10/2020

Nordic nRF9160 SiP enters final volume production phase having passed all major certifications required for end-product deployment

The nRF9160 System-in-Package (SiP) is ready for mass deployment in both LTE-M and NB-IoT cellular networks and cellular IoT product applications around the globe

Tags: nRF9160, LTE-M, NB-IoT, nRF91 Series

News

7/4/2019

DevZone - first 10 hits

Actinius Icarus board V2, update through NOR

Hi, Is there a sample project about it? When I develop software emulator still work on flash? Correct? How it works that at startup it mcuboot does not copy the nor in flash? Is there a configuration for debugging? Thanks

forum

2/15/2025

SecureFault on NRF9160 after upgrading to HW model v2 and NCS 2.9.0

I have upgraded nRF Connect SDK from v2.6.0 to v2.9.0 and also upgraded custom board definition to the HW model v2 according to the nrf9160dk board files. After compiling and uploading code to the board, I'm getting error: FATAL ERROR: SecureFault . I have also tried downgrading SDK to v2.7.0 and v2.8.0, but the result was the same. Am I missing something? I have also spotted, that nrf9160dk_nrf9160_ns.dts defines zephyr,sram = &sram0_ns; , but nrf9161dk_nrf9161_ns.dts defines zephyr,sram = &sram0_ns_app; . Which one is correct, or does it matter? Minimal project: devzone.nordicsemi.com/.../cm01test.zip CMake log: /usr/bin/cmake --preset cm-01 -S /home/martinv/Projekty/nextdrop/unified-fw_cm01test -B /home/martinv/Projekty/nextdrop/unified-fw_cm01test/cmake-build-cm-01 Loading Zephyr default modules (Zephyr base).Preset environment variables: BOARD="cm01/nrf9160/ns" GNUARMEMB_TOOLCHAIN_PATH="/usr" ZEPHYR_BASE="/home/martinv/Repos/ncs/zephyr" ZEPHYR_TOOLCHAIN_VARIANT="gnuarmemb" -- Application: /home/martinv/Projekty/nextdrop/unified-fw_cm01test -- CMake version: 3.30.7 -- Found Python3: /usr/bin/python (found suitable version "3.13.2", minimum required is "3.8") found components: Interpreter -- Cache files will be written to: /home/martinv/.cache/zephyr -- Zephyr version: 3.7.99 (/home/martinv/Repos/ncs/zephyr) -- Found west

forum

2/14/2025

nrf_cloud_coap_connect() possible memory leak

Hello I am using a custom board, based on nRF9160. I'm using SDK 2.7.0 and modem firmware 1.3.6. After a bug in production where a device stopped sending data, I tracked down the issue to this function nrf_cloud_coap_connect(). In my specific case, after 55 successful calls, the function ends up returning -12 (ENOMEM 12 /* Not enough space */). Any call after that returns the same error. I guess the number of call depends on the firmware. Compiler states that my project uses ~33% of the available RAM, or 70kB. The issue was seen a few times in production (deplyed devices) and I managed to reproduce with the following piece of code : // General init // Connect to LTE-M network for(i=0;i<100;i++) { DEBUG_PRINT("Attempt %d\r\n", i); // Ensure there is no remaining stuff opened nrf_cloud_coap_disconnect() ; // Create new connexion err = nrf_cloud_coap_connect(NULL) ; } This not due a network

forum

2/14/2025

lte_ble_gateway no go from v270 to v290

Hello, lte_ble_gateway works ok using dk91 or thingy:91 on, v251 - ok *** Booting nRF Connect SDK v2.5.1 *** [00:00:00.398,284] lte_ble_gw: LTE Sensor Gateway sample started [00:00:00.398,468] lte_ble_gw: Initializing Bluetooth.. [00:00:00.607,025] lte_ble_gw: Establishing LTE link (this may take some time) ... [00:00:01.095,214] bt_hci_core: opcode 0x0000 pool id 3 pool 0x2000cf78 != &hci_cmd_pool 0x2000cfe0 [00:00:01.136,840] bt_hci_core: HW Platform: Nordic Semiconductor (0x0002) [00:00:01.136,871] bt_hci_core: HW Variant: nRF52x (0x0002) [00:00:01.136,901] bt_hci_core: Firmware: Standard Bluetooth controller (0x00) Version 197.47763 Build 2370639017 [00:00:01.145,263] bt_hci_core: Identity: C3:DC:72:5F:61:E7 (random) [00:00:01.145,294] bt_hci_core: HCI: version 5.4 (0x0d) revision 0x1102, manufacturer 0x0059 [00:00:01.145,324] bt_hci_core: LMP: version 5.4 (0x0d) subver 0x1102 [00:00:01.145,355] lte_ble_gw: Bluetooth ready [00:00:01.152,587] lte_ble_gw: Scanning... v262 - ok *** Booting nRF Connect SDK v3.5.99-ncs1-3 *** [00:00:00.393,005] lte_ble_gw: LTE Sensor Gateway sample started [00:00:00.393,218] lte_ble_gw: Initializing Bluetooth.. [00:00:00.603,454] lte_ble_gw: Establishing LTE link (this may take some time) ... [00:00:01.090,332] bt_hci_core: opcode 0x0000 pool id 3 pool 0x2000d01c != &hci_cmd_pool

forum

2/14/2025

nRF Cloud Authentication Issue

Hi, I have several deployed devices that have been running for a while, using the nRF Cloud A-GNSS system with the nRF Location library. These devices were successfully provisioned with nRF Cloud, and their public keys were uploaded. They had been functioning properly for about a month, but starting a few days ago, I suddenly began receiving authentication errors. There have been no changes to the firmware or nRF Cloud configurations. My NCS version is 2.6.0 , and the modem firmware version is 1.3.6 . I used the AT%KEYGEN command to generate credentials and uploaded the decoded credentials to nRF Cloud, following the official tutorial. Is there an issue with nRF Cloud that could be causing this problem? [00:00:17.189,361] rest_client: rest_client_http_response_cb: HTTP: All data received (content/total: 51/287), status: 401 Unauthorized [00:00:17.189,392] rest_client: rest_client_request: API call response len: http status: 401, 51 bytes [00:00:17.189,392] rest_client: rest_client_close_connection: Socket with id: 0 was

forum

2/13/2025

nRF9160 MBedTLS socket connect() over LTE-M eventually fails with error 11 EAGAIN

I have working HTTP(S) client program in my app that makes a GET request about every 30 seconds. Recently our data endpoint has changed to a server that requires TLS 1.2/1.3 with RSA (2048B) certificates. The data payload is usually too large for the nRF9160 modem's secure socket buffer, so I've implemented MBedTLS to handle the secure side of the sockets. I'm using NCS 2.9.0 (MBedTLS logging doesn't work in 2.8.0) and the required TLS cipher suite is TLS-ECDHE-RSA-WITH-AES-128-GCM-SHA256. Everything seems to work with my implementation and configurations, but after some number of socket creation/connects/transfer/close cycles I end up with errorno 11 (EAGAIN) "No more processes" when attempting to call zsock_connect(). I have tried changing many configuration values and the HTTP(S) client code, but I haven't found any debug logs that appear to point out why I'm running out of processes. Here is a log of the failure occurring: D:

forum

2/13/2025

Issues when powering thingy:91 from solar panel

Hi! I am trying to power the thingy:91 from solar panels and have some issues with the thingy:91 restarting when the solar panel receives a medium amount of light. The solar panel charges the device properly in full sun and does not interfere with the device when there is no sun. However, it starts rebooting when there is some light. I assume that this is because the USB solar panel outputs a voltage lower than 5V, but high enough that the regulators turn on so that the nrf9160 is supplied with too low voltage. I have tried with multiple USB-solar panels which most often are used to charge surveillance cameras. Do you have any tips on how to run the thingy:91 from a USB solar panel properly? Best regards, Jonathan

forum

2/13/2025

nrf9160 nrf_cloud_rest_fota sample error in SDK2.9.0

I have develop a FOTA code in SDK2.5.0 base on \nrf\samples\cellular\nrf_cloud_rest_fota example, everything work. and recently I try to update to SDK2.9.0, and first testing \nrf\samples\cellular\nrf_cloud_rest_fota example, it has compile error without any change after install is there any idea or error in this SDK? Best Regards Dannis

forum

2/13/2025

What's the Maximum Uplink payload in nRF9160 to the cloud?

Hi Nordic Asking this question to Nordic AI (right-down window), below was the answer. The nRF9160 is a cellular IoT device, and its MTU size depends on the protocol being used. For MQTT publishing, which is a common use case for IoT devices: When not publishing in datamode, the maximum publish size is 1024 bytes. When publishing in datamode, the maximum size is limited by the datamode ring buffer size, which is 4KB (4096 bytes). However, it's important to note that there's a TLS secure socket buffer size limitation of 2KB (2048 bytes) according to the modem firmware release notes. We had a new nrf91 projec t which required packet payload over 4KB. And, bigger is better. Q1. As AI said, MQTT TLS, max payload is 2KB. At ncs/mqtt sample, is there any way to increase max payload? If yes, how to do? Q2. How about max payload for HTTPs

forum

2/13/2025

NRF9160DK i2c device no response

Evaluating direct access I2C operation with the NRF9160DK. I have a INA219 connected to pin 30 & pin 31. I am aware that there is a zephyr driver for the INA219, but I want to test direct I2C operation until the replacement device can be implemented. I am only trying to read register 0x00, which should provide the output of 0x39, 0x9F. I have tried different variations of the i2c read/write (i2c_write_read_dt, and separate write/read functions) and all return an error code -5. To ensure that data is being transmitted to the INA219 (to eliminate connection issues) I am monitoring the SCL & SDA data lines using a DIGILENT Device to see what data is transmitted. I am also able to send I2C data to the INA219 to verify proper device operation. When sending data from the DIGILENT device I get the proper response and the proper returned data. Below

forum

2/12/2025