Search Result

Hello, I was able to compile lorawan class_a module for nrf52832 by adding the overlay file and CONFIG options for the sx1262 IC. I tried to compile it for nrf9160 but, I got errors. I found a lorawan repository, and they use a dual overlay file named nrf9160_nrf9160DK_ns.overlay and nrf9160_nrf9160DK.overlay (because of the trust-zone I believe), and I was able to compile their module for nrf9160. There is no difference for these overlay files, these are the same. Do you have any document explaining why the use of the non "ns" overlay file? Regards

To everyone who is interested in this ticket. I'm using the nRF9160DK and nRF7002DK. I'm currently trying to scan Wifi using the nRF9160DK. I'm referring to another ticket for that question, but it hasn't been successful. Connecting nRF9160DK and nRF7002DK I've linked the pin to be the same as that ticket. Board nRF9160-DK(P3 & P4) nRF7002-DK (P24) SPI CLK P0.13 P0.17 SPI CS P0.10 P0.18 SPI MOSI P0.11 P0.13 SPI MISO P0.12 P0.14 HOST-IRQ P0.07 P0.23 IOVDD-CTR P0.00 P0.31 BUCKEN P0.01 P0.12 I used sample on nordic. "nrf/samples/wifi/shell" and i used west build -b nrf9160dk_nrf9160_ns -- -DSHIELD=nrf7002ek This is the result of checking through the console. this .7z is my file for this function. devzone.nordicsemi.com/.../shell.7z Any help is appreciated. Thank you!

Hi I am starting with nRF9160. I build and program "nrf91_simple_tracker," but while running, I got the following terminal output: *** Booting Zephyr OS build v3.3.99-ncs1 *** [00:00:00.254,028] .[0m Cellfund_Project: The nRF91 Simple Tracker Version 0.2.1 started .[0m [00:00:00.254,058] .[0m Cellfund_Project: Initializing modem library.[0m [00:00:02.050,842] .[1;31m lte_lc: Could not send AT command, error: 65536.[0m [00:00:02.050,872] .[1;31m lte_lc: Could not set system mode, error: -14.[0m [00:00:02.050,872] .[1;31m Cellfund_Project: Failed to initialize LTE link control library, error: -14.[0m [00:00:02.050,903] .[1;31m Cellfund_Project: Failed to configure the modem.[0m I am using nRF Connect SDK v2.7.0 with VSC using SparkFun nRF9160 Thing Plus. Any hints?

Hi, I am developing a product based on the nRF9160 using the LwM2M client. I successfully have this working using PSK, but want to use X509. I am calling lwm2m_security_set_certificate() where I previously called lwm2m_security_set_psk() and have client certificate, client key, and server root CA certificate in PEM form created by following the guidance from dejans and SeppoTakalo in this other post: LWM2M Client With X.509 Certificate The LwM2M library reports the following [00:01:19.463,531] net_lwm2m_engine: Cannot connect UDP (-111) [00:01:19.474,121] net_lwm2m_engine: lwm2m_engine_start lwm2m_socket_start() returned -111 ...which is 'connection refused' I have taken a modem lib trace of an attempt to connect to the leshan public server, and looking at this in Wireshark, the client DTLS handshake response to the server's 'Certificate Request' contains a zero length certificate, followed by the server returning a 'Bad Certificate' fatal error (which I'm assuming results in the -111 in the modem DTLS handling). I

Hi, I am trying to test the ICM42670 sensor using nRF9160 with Zephyr V2.6.0 and I am getting an errors when I init the sensor: unexpected RESET_DONE_INT value, 0 ICM42670 Sensor is not ready device tree: &spi3 { compatible = "nordic,nrf-spi"; pinctrl-0 = ; pinctrl-1 = ; pinctrl-names = "default", "sleep"; cs-gpios = ; status = "okay"; overrun-character = ; // IMU Sensor icm42670: icm42670@0 { compatible = "invensense,icm42670"; reg = ; spi-max-frequency = ; accel-hz = ; accel-fs = ; gyro-hz = ; gyro-fs = ; }; }; icm_sensor.c file const struct device *const icm_dev = DEVICE_DT_GET_ANY(invensense_icm42670); int icm_init(void) { if (icm_dev == NULL) { LOG_ERR("ICM42670 Sensor Not found"); return INIT_ERR; } if (!device_is_ready(icm_dev)) { LOG_ERR("ICM42670 Sensor is not ready"); return INIT_ERR; } LOG_INF("Sensor %s is ready", icm_dev->name); k_sleep(K_MSEC(1000)); return INIT_OK; } void get_icm_data(void) { static unsigned int count; struct sensor_value accel[3]; const char *overrun = ""; int rc

Good day I have the NRF_desktop keyboard application running on the NRF52840 Dongle, Zephyr 2.6.1. I would like to us the nrf52840 ProMicro as it has a battery charger build in. I have modified rows and columns accordingly. All my buttons are working except P1.00. I can use any other pin for col 2 and it will work but for some reason not P1.00. It does not appear to be used anywhere else, and I don't get any warnings. Below is my Button_def.h and App.overlay files. I do need to use P1.00 as its the Keypad membrane header col 2. Any suggestions would be welcomed. Thanks in advance app.overlay / { chosen { nordic,pm-ext-flash = &mx25r64; }; }; / { chosen { /* * In some default configurations within the nRF Connect SDK, * e.g. on nRF52840 and nRF9160, the chosen zephyr,entropy node * is &cryptocell. This devicetree overlay ensures

Hello, Developing a custom board with nRF9160 as application CPU and nRF52810 as BLE Controller. Connected via SPI + reset + irq lines to the 52810. The design is a copy of the manual's reference design for the 52810, with an external antenna to an u.FL connector. Host code is based on peripheral_hr and Controller code is plain hci_spi without modifications: https://github.com/zephyrproject-rtos/zephyr/blob/zephyr-v3.4.0/samples/bluetooth/hci_spi/src/main.c The host says it's advertising and output when it's working normally is as belows, however using e.g. "BLE Scanner" on iPhone, it's not showing a device named "Zephyr Heartrate Sensor". 32 MHz Xtal: https://jlcpcb.com/partdetail/YangxingTech-XL7EL89CKI_111YLC32M/C2965582 12pf caps (5% instead of 2%, maybe that's a problem): https://jlcpcb.com/partdetail/1899-0402CG120J500NT/C1547 Host output: *** Booting nRF Connect SDK v2.5.2 *** [00:00:00.460,021] hwtest: bluetooth: initializing [00:00:00.465,759] bt_conn: bt_conn_prepare_events: ...repeats 19 times... [00:00:01.920,776] bt_smp: bt_smp_init: LE SC enabled [00:00:01.927,429] bt_conn: bt_conn_prepare_events: [00:00:[00:00:01.934,539] bt_hci_core: Identity: DC:9C:F0:BA:35:43 (random) [00:00:01.941,864] bt_hci_core: HCI: version 5.4 (0x0d) revision 0x1168, manufacturer 0x0059

BT_DRV_RX_STACK_SIZE is too small and can't be configured. It needs to be more than 512 bytes in released versions of Zephyr, or 640 bytes, on the main branch. Note: I'm using the nRF SDK v2.5.2, which is not the latest, but the driver hasn't changed in any meaningful way since. zephyr,bt-hci-spi on a nRF9160 to a zephyr,bt-hci-spi-slave on a nRF52810. bt_spi_rx_thread() in spi.c causes segfault on the host (nRF9160) because of stack overflow. I can nail it down to the call to bt_spi_transcieve(). Increasing the value in Kconfig to 1024 seems to work. The rest of my configuration is irrelevant since this is isolated to a specific thread and its task size. (previously posted to https://github.com/zephyrproject-rtos/zephyr/issues/80109 who refers to Nordic Semi)

Hi , I 'm trying to send and receive on a websocket. Sending works fine and is received on the backend, but when I try to receive I just get garbage in my buffer. I sanity tested the websocket message with both Postman and Python Websockets library, and the response looks correct in both examples. Exactly like this: {"status":"Checking for new logs.","messageType":"requestCommRules","packets":["[192, 1, 0, 0, 3, 0, 208, 209]"]} but as you can see in the trace output below, I just get something back that looks encrypted. My code is extremely similar to the websocket client example: (I removed irrelevant or sensitive parts of the code, hence why there are configs that seem unrelated to the websockets issue) BOARD: nrf9160dk/9160/ns CONFIG: # General CONFIG_HEAP_MEM_POOL_SIZE=4096 CONFIG_MAIN_STACK_SIZE=4096 # Logging CONFIG_LOG=y CONFIG_MODEM=y CONFIG_LOG_MODE_IMMEDIATE=y # CONFIG_NRF_MODEM_LIB_TRACE=y CONFIG_MODEM_LOG_LEVEL_DBG=y CONFIG_NET_LOG=y CONFIG_NET_SOCKETS_LOG_LEVEL_DBG=y CONFIG_NET_HTTP_LOG_LEVEL_DBG=y CONFIG_NET_WEBSOCKET_LOG_LEVEL_DBG=y CONFIG_NET_CONTEXT_LOG_LEVEL_DBG=y CONFIG_NET_TCP_LOG_LEVEL_DBG=y CONFIG_LOG_BACKEND_UART=y # Network CONFIG_NETWORKING=y CONFIG_NET_TCP=y CONFIG_NET_SOCKETS=y CONFIG_NET_SOCKETS_POSIX_NAMES=y CONFIG_NET_IPV4=y CONFIG_NET_CONNECTION_MANAGER=y CONFIG_NET_CONNECTION_MANAGER_MONITOR_STACK_SIZE=1024 CONFIG_NET_BUF_DATA_SIZE=4096

Dear community, I am using the nRF9160 chip, and I have the issue of occasionally unreliable positioning. Depending on the network, positioning happens quickly and is accurate. On another network, I have inaccurate positioning. I suspect the interplay of eDRX and LTE connection seems to be at fault. Each carrier seems to have its quirks. I was considering storing a set of favorable eDRX settings and querying the network with "+CEDRXS?". Based on the response, I would take the most preferred eDRX setting or notify that LTE and GPS are not compatible on this network. Does this make sense? Does someone have some advice for handling the LTE settings of different, mainly European (Swiss and German to be specific), network operators? Thank you in advance for any tips! Kind regards, Brian