Hi Jason, Thank you for your reply. It was helpful. I created a new local Kconfig file in my project folder and added the following lines, menu "MyDevice Settings" config DEBUG_PORT_ACCESS bool "Allow

#nrf52832

Dear All, I'm using the nRF Connect SDK and try to do a FOTA upgrade to my nRF52832, with MCUboot installed. After I downloaded the binary via nRF Connect Android App to the device, i get "<wrn> mcubo

#nrf52832 #mcuboot #fota

Does zephyr only supports PSK for the DTLS (e.g echo client, lwm2m client). I haven't seen anything about RPK using ECC.

#ble #crypto #nrf52832

Ok, found the issue: It was do to pin mapping naming. I was assuming that the pinmaps in Arduino D5, D6, and so on, corresponded to a direct GPIO map, so D5->GPIO_5 and so on... and that's not true. A

#gpio #nrf52832

Hi Krzysztof, I thought that the use of one of the counters would be considered due to its presence in the device-tree. So from what I understood, every instance from the device-tree must be enabled,

#nrf52832

Hello everyone, Now, I am implementing a Flash-map application for nRF52832. I have already included <storage/flash_map.h> and called flash_area_open() function, but I got an error when compile: undef

#driver #api #flash #nrf52832

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

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

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 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 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

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

Vinayak, That is ok. I will open the issue on github. After removing the code directly on the system_nrf52.c the board had stopped to answer the nrfjprog. I thought that was independent of the traceda

#nrf52832 #customboard

Hi Joe, thanks again for your fast answer. I tried to run spi_loopback/spi.c on nrf52840_pca10056 but i am still running into problems. I will explain the problem, if someone has the time to take a sh

#nrf52832