I would like to advertise and scan ONLY on one bluetooth channel (for example channel 37). Is there any way to do this in Zephyr? I tried to search parametr responsibles for it in this structure: stru

#bluetooth #ble #nrf52832

Hi all, I would like to know the status of WINC1500 driver in zephyr. Is this fully tested? We are currently working on a product that uses Nordic's nRF52832 with WINC1500 over SPI. For our developmen

#spi #driver #WINC1500 #nrf52832

Hi Zephyr developpers ! To sum up i'm using nrf52833 DK, with new ncs sdk. I can do OTA with mobil App nRFConnect, but not with nRFToolbox. We want now to code OTA/DFU feature into our own app. I'm us

#nrf52832 #ble #bluetooth #mcumgr

Hello Zephyr Users, I have inherited a Zephyr project using nRF52832 from another developer and am having an issue migrating from 2.0.0 to 2.1.0. Its probably something simple but I'm fairly new to th

#nrf52832

I just realized I responded to you privately by accident, Lawrence. Sorry about that. I will copy the message I sent to you to the group so that the discussion is up to date. The suggestion regarding

#gpio #nrf52832

Hi Brian: You can always test the value of the GPIO with gpio_pin_read() in the callback, if it is 1, then the cause is a rising edge, and if it is 0 the cause was a falling edge. Unfortunately if the

#gpio #nrf52832

Hello, I hope I am posting this question in the correct place. I have an interrupt handler which can be configured to trigger on either edge. This is working perfectly, but I want to perform a differe

#gpio #nrf52832

I think you need a few more things turned on in your config file. To figure out what you need turned on I always use the menuconfig tool and diff the old and new .config files, then I take the changes

#dts #nrf52832

Hi I had a question to setup the MCP2515 driver in the zephyr project. We made a custom board for the decawave DWM1001 module, which uses a nRF52832 chip. They have a device tree file in the zephyr pr

#dts #nrf52832

Does the application work without the debugger attached? (i.e., did it get programmed into flash correctly?) I’ve seen weird behavior if you leave the GDB client executable at the default. Try changin

#nrf52832 #jlink #debugging #eclipse

Hi, i am trying to set up eclipse, gdb and jlink for debugging NRF52832. I am using a PCA10040 board with an integrated Jlink debugger. I have a simple project with a single main.c file. My prj.conf a

#nrf52832 #jlink #debugging #eclipse

Hi there, There was recently a similar question on Slack. Take a look at https://github.com/zephyrproject-rtos/zephyr/blob/master/subsys/bluetooth/mesh/crypto.c BLE Mesh has a similar requirement to e

#bluetooth #nrf52832 #bt

Hi, all. I am encrypting the UUID of my beacon and wants to decrypt it at the scanner's end. But the problem is that the docs say only about encryption function bt_encrypt_be(). How do I decrypt my UU

#bluetooth #nrf52832 #bt

Hi Alexander, I don’t know if this is the cause of your issue, but it implies that you have something in flash (the storage partition) that the application doesn’t expect. Before investigating further

#bluetoothmesh #nrf52832

Trying to get the Bluetooth mesh onoff-app sample working on a nrf52_pca10040 it compiles and runs on the board but when it try to provision it using the meshctl tool it freezes and I cant type after

#bluetoothmesh #nrf52832

Hello, I just started working on a new project and giving zephyr a try. I have came to a problem that I can't seem to easily root cause. I'm using nRF52832 with BLE running and also running a seperate

#nrf52832

Hi, Is there any way to use the I2S interface on a Nordic nRF with Zephyr? Link to github issue: https://github.com/zephyrproject-rtos/zephyr/issues/11702

#nrf52832

I tried this with v1.2.0 of mcuboot, as well as the latest master code.

#nrf52832

I've made some progress. Once I get the device in serial mode I am able to start the mcumgr upload, but it constantly times out. The RTT output from the dev board: ***** Booting Zephyr OS zephyr-v1.13

#nrf52832

Thanks Andrzej and Carles. I tried these steps but had some compiler errors with CONFIG_SOC_NRF52840_QIAA=y enabled. Once I disabled this, the code successfully compiled. I then proceeded to add a ser

#nrf52832