Hi Nagesh, USB device re-enumeration is a known issue for RCP and OTBR. The topic is still quite fresh in terms of Zephyr, as we do not implement “software” reset OTBR required so far. There’ve been s

#nrf52480

Hi All, Issue Description: I am trying to flash and run openthread rcp sample as explained in the link: https://docs.zephyrproject.org/latest/samples/net/openthread/coprocessor/README.html. I am able

#nrf52480

I need to connect the HC-SR04 ultrasonic sensor to the particle argon board and use it for distance measurement with Zephyr. What is the device binding that needs to be done in zephyr for this? Are th

#nrf52480

Hi, I am trying to figure out how to make a HCI USB Bluetooth host adapter with device management on a nRF52840 Dongle. My approach is to make a USB composite device consisting of the Bluetooth device

#nrf52480 #mcumgr #hci #usb

Hello everybody, I would like to ask you if it is safe to use these functions in order to store and get DTLS credentials on the device? I would like to make over the air update so I would like the tra

#networking #flash #dtls #nrf52480

Hi, I have a set up consing of an nrf52840, a Raspberry pi and a Linux workstation, which communicate over IPSP following the IPSP sample. The nrf52840 is a UDP/CoAP client, the Raspberry pi is a bord

#coap #ipsp #nrf52480

Hi all, I have a set up consisting of nRF52840 and Raspberry Pi4 communicating over IPSP. The nRF52840 application needs to send data with 6,4KByte/s. My nRF52840 prj.conf is: # Thread Priorities CONF

#ble #nrf52480

Hello, after all I am flashing the base firmware (first app) into 0x0 address and then using the CONFIG_FLASH_LOAD_OFFSET=0x20000 to the proj.conf of the second app I am flashing the second firmware i

#flash #nrf52480

Hi Erik, FYI, pyocd is Zephyr-aware and Nordic’s J-Link OBs can be reflashed with pyocd-compatible firmware: https://www.nordicsemi.com/Software-and-tools/Development-Kits/nRF52-DK/Download#infotabs A

#debugging #gdb #nrf52480 #ztest #bluetoothmesh

Hi, We are looking for direction on how best to improve our (multi-threaded) debugging capability. Current setup: host ---NRF52_dev_board (onboard jLink) -- custom Nordic-SoC board where host is macOS

#debugging #gdb #nrf52480 #ztest #bluetoothmesh

Hello, Update: I just want to change the boot address (or slot) before the reboot, without using MCUboot. I am looking on zephyr documentation for a mechanism like this but I can not find any utility.

#flash #nrf52480

Thank you Carles, I would prefer not to use MCUboot. However, I have already checked MCUboot code in order to take some ideas. I am looking for something MCUboot interdependent. For example a function

#flash #nrf52480

Hi Nikos, Maybe you want to look at MCUboot, which supports this out of the box and is integrated with Zephyr? https://mcuboot.com/ https://docs.zephyrproject.org/latest/reference/kconfig/CONFIG_BOOTL

#flash #nrf52480

Hello, I am using nrf52840-dk module (this is not really important). I would like to write two different firmwares in my device in different addresses (slots). Lets say the first firmware is located a

#flash #nrf52480

Hi, Iam using nrf52840 DK as a BLE controller. So i compiled a hex file and loaded into it. There after when we power on am getting the bdaddr of the device as 00:00:00:00:00:00, But when i check the

#bluetooth #nrf52480 #usb #ble

My environment : Debian 10 zephyr SDK 0.10.3 zephyr 2.1.0-rc2 I'm Interfacing Max44009 with nrf52840 on a custom make board in zephyr. I'm using the sample sensor program for MAX44009. Configured with

#nrf52480 #sensor

Hi, I have interfaced "ENC28J60" to "PCA10056"(NRF52840) through SPI. Made necessary configurations in order to reflect hardware changes in software. Flashed sample application, "dumb_http_server" to

#nrf52480

I created a Github issue for the above incompatibility: https://github.com/zephyrproject-rtos/zephyr/issues/16240 It looks like DFU cannot be used at the same time as Bluetooth HCI in v1.14 or master

#nrf52480 #ble

Whenever the USB DFU driver and the USB BLE HCI driver are both enabled, neither works as expected . BLE HCI over USB works when the DFU USB driver is disabled via prj.conf (CONFIG_USB_DFU_CLASS=n). D

#nrf52480 #ble

Hi Fabien, My guess is that this is in great part caused by the UART not being shut down. There is currently a PR to address this: https://github.com/zephyrproject-rtos/zephyr/pull/7034 I have copied

#nrf52480