Search Result

271 results found on Nordicsemi

Article 12 | News 223 | Product 36 | All results

8981 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

DevZone - first 10 hits

Socket poll in eDRX mode not generating events correctly

Good afternoon, I am debugging the nRF9160 in a product, and what we are noticing is that the socket "poll" events do not appear to be generated when the system is in eDRX mode. Apologies that the software in this device is much older (NCS 1.8.0 and mfw_nrf9160_1.3.1), so it is likely missing many bug fixes, etc. At a high level, the system keeps an AWS IoT connection established using periodic pings and uses eDRX to help save some power. When my application sleeps, it calls the poll function to wait on incoming data from the network in the event that the server has something to send asynchronously. Currently, the eDRX settings are as follows: eDRX: 5 . 120000s PTW: 1.28 I receive this message through the LTE_LC_EVT_EDRX_UPDATE callback, so this is what the network (T-Mobile) is setting as well. The issue that I am seeing is that when eDRX

forum

7/11/2024

Level-triggered GPIO interrupt with NCS 2.7 on nRF9160

Hi, after upgrading to NCS v2.7.0, I have some trouble with an increased sleep power consumption of our device when I use Zephyr's gpio-keys for the button input. I was using NCS v2.5.2 before. Initially after upgrading, the button would not work any more at all, when I would compile with `CONFIG_PM_DEVICE` and `CONFIG_PM_DEVICE_RUNTIME`. That could be resolved by calling `pm_device_runtime_get()` on the gpio-keys device during initialization. Now the button would work, but the sleep power consumption would increase by around 15 μA. With NCS v2.5.2, I also had an increase of the power consumption by about 15 μA when I added the button with gpio-keys to my software and enabled CONFIG_INPUT. According to this (old) thread on devzone , the nRF9160 would require the use of level-, not edge-triggered GPIO interrupts, for low power consumption. I then applied a small fix to the Zephyr gpio-keys driver, to use level-triggered

forum

7/11/2024

AssetTrackerV2 with CONFIG_TFM_PROFILE_TYPE_SMALL=y gives configuration error

Dear Nordic-Support, as I got a configuration error in my project when configuring CONFIG_TFM_PROFILE_TYPE_SMALL=y I tried to reproduce this with the AssetTracker_v2 application. The same issue occurs here. I am using the nrfConnect SDK v2.5.0. When I add the line CONFIG_TFM_PROFILE_TYPE_SMALL=y to the prj.conf I get this CMake error: CMake Error at config/check_config.cmake:20 (message): INVALID CONFIG: TFM_PROFILE = profile_small AND CONFIG_TFM_SPM_BACKEND_IPC Call Stack (most recent call first): config/check_config.cmake:107 (tfm_invalid_config) CMakeLists.txt:82 (include) From the table here https://trustedfirmware-m.readthedocs.io/en/latest/configuration/profiles/index.html#tf-m-profiles I understand that the CONFIG_TFM_SPM_BACKEND should be SFN, but I would expect the configuration system to set this correctly. Thanks Stefan

forum

7/11/2024

nRF9160 not registering with cellular network in India

Hi, I am facing a problem with connecting nRF9160-DK to the cellular network. waited for more than hour for connection but always showing "Not registered, attaching or searching" in cellular Monitor Application. Details: - Application: - asset tracker example from nRF connect Application (flashed using nRF connect) SIM: - AT&T SIM’s with internation plan. Error message: - +CEREG: 2,"C07E","0016AD91",9,0,19 Attached a trace log from Device. devzone.nordicsemi.com/.../trace_2D00_2024_2D00_07_2D00_10T13_2D00_55_2D00_33.269Z.mtrace

forum

7/11/2024

Cannot activate 9161 on Verizon Thingspace IoT network

Dear Nordic, I'm unable to register an nRF9161 device on the Verizon Thingspace IoT Network. They have a web UI which allows one to enter an IMEI, ICCID pair. When I enter a valid pair for an nRF9160 device, the device activates. However, when the IMEI is a 9161 IMEI I get the message " Device not found in DMD ". Is there a workaround? The IMEI of one of my 9161 device is 358299840007435. Thank you. Peter

forum

7/10/2024

nRFCloud, device self-assign to a group

Hello, I am using nRFCloud with nRF9160 custom board sending data via CoAP. I have a single firmware on my board, that will behave differently depending on the value of the rotary coded switch that is mounted on the board. Basically, using the same firmware, my device can be either a temperature sensor, a presence sensor, a light sensor, etc. I call that "device type" In nRFCloud, I would like to use the group feature, and group my fleet by "device type". This is doable using the API or the nRFCloud dashboard. However, it would be much easier if this could be done remotely : the device sending the name of the group it want to be in. Is this possible ? If so, how ? If not, is there any plan to have this feature in the near future ? Thanks !

forum

7/10/2024

Communication between nrf52840 and nrf9160 with connectivity bridge on Thingy:91

Hello, I'm experiencing an issue with communication between the nRF52840 and nRF9160 on the Thingy platform using the connectivity bridge. I successfully established communication between the two devices using UART1 without employing the connectivity bridge sample, and I was able to visualize the logs using SEGGER. However, after integrating my working sample with the connectivity bridge sample, the communication fails, when I transmit a message from the nRF9160 to the nRF52840, the transmission appears successful, but no message is received on the nRF52840. I will provide the two applications I used to communicate successfully without the connectivity bridge. Could someone guide me on how to merge these applications with the connectivity bridge sample? Thank you! devzone.nordicsemi.com/.../0068.uart_5F00_nrf9160.zip devzone.nordicsemi.com/.../5488.uart_5F00_nrf52840.zip And here is my connectivity bridge application modified : devzone.nordicsemi.com/.../connectivity_5F00_bridge_5F00_modified.zip Best Regards, Youssef

forum

7/10/2024

9160dk external flash operation address length issue

The default setting for the external flash chip of 9160dk appears to be 64m, but when used, the log display only shows 8m, and only the part within 8m can be used, mx25r64: mx25r6435f@1 { compatible = "jedec,spi-nor"; status = "disabled"; reg = ; spi-max-frequency = ; jedec-id = [c2 28 17]; sfdp-bfp = [ e5 20 f1 ff ff ff ff 03 44 eb 08 6b 08 3b 04 bb ee ff ff ff ff ff 00 ff ff ff 00 ff 0c 20 0f 52 10 d8 00 ff 23 72 f5 00 82 ed 04 cc 44 83 48 44 30 b0 30 b0 f7 c4 d5 5c 00 be 29 ff f0 d0 ff ff ]; size = ; has-dpd; t-enter-dpd = ; t-exit-dpd = ; }; spi_nor: mx25r6435f@1: 8 MiBy flash Then I set the chip size to 8 times that of 64m in order

forum

7/10/2024

Problems in adding FOTA support

Hello, I'm working on a project in which we are adding FOTA functionality based on application_update example. As soon as I add CONFIG_BOOTLOADER_MCUBOOT=y I see Changed board to secure xxxyyyyzzz_nrf9160 (NOT NS) in the build log, and soon after that these warnings: warning: NRF_MODEM_LIB_NET_IF (defined at /opt/nordic/ncs/v2.6.1/nrf/lib/nrf_modem_lib/lte_net_if/Kconfig:6) was assigned the value 'y' but got the value 'n'. Check these unsatisfied dependencies: NET_SOCKETS_OFFLOAD (=n), NRF_MODEM_LIB_ON_FAULT_APPLICATION_SPECIFIC (=n), NRF_MODEM_LIB (=n). See http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_NRF_MODEM_LIB_NET_IF and/or look up NRF_MODEM_LIB_NET_IF in the menuconfig/guiconfig interface. The Application Development Primer, Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be helpful too. warning: AT_HOST_LIBRARY (defined at /opt/nordic/ncs/v2.6.1/nrf/lib/at_host/Kconfig:7) was assigned the value 'y' but got the value 'n'. Check these unsatisfied dependencies: NRF_MODEM_LIB (=n). See http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_AT_HOST_LIBRARY and/or look up AT_HOST_LIBRARY in the menuconfig/guiconfig interface. The Application Development Primer, Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be

forum

7/10/2024

nRF9160 PSM Sleep for Longer than 8 Hours

With TAU set to 24 hours, when we wake up every 8 hours, everything works fine. When we extend to 12 hours, it takes longer than 10 seconds for a connection to be established. And when we try, we get the following errors waiting for the connection to come online: Waiting for LTE [12:01:04.373,016] lte_lc: Connection evaluation failed with reason: 5 LTE Connected [12:01:04.772,155] lte_lc: Connection evaluation failed with reason: 4 lte_lc_conn_eval_params_get, error: 4 While it shows connected (semaphore obtained), the data isn't sent. It's only after we send 3 UDP messages that we get the following "RRC mode: Connected." What would cause the modem to disconnect from the network after 12 hours vs 8 hours? bool lteConnected(int m_secs) { bool connected = false; struct lte_lc_conn_eval_params params = {0}; int err; printk("Waiting for LTE\n"); err = lte_lc_conn_eval_params_get(&params); if (!err) { if (params.rrc_state == LTE_LC_RRC_MODE_CONNECTED) { printk("Already connected\n"); return true; }

forum

7/10/2024