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

Hi, I’m not an expert in this by any means, but I’d like to point you to https://docs.zephyrproject.org/latest/reference/kconfig/index-all.html , which is a list of all of the config symbols as define

#nrf52832

Hi Mohamed, This look like a question related to Nordic’s nRF Connect SDK. Please ask this question in Nordic’s Devzone instead: https://devzone.nordicsemi.com/ Thanks! Carles

#nrf52832

Hello, I need help with Access Port Protection on nRF52833. I have added the line CONFIG_DEBUG_PORT_ACCESS=y in prj.conf file and now the project does not open in Segger Embedded Studio (SES). I am ge

#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

Have you done the initialization by running gpio_pin_configure with GPIO_OUTPUT_ACTIVE as third argument ? Just to be clear, you´re trying to set pin p0.05 ? That´s located on chip pin7 (QFN48 pkg) ?

#gpio #nrf52832

Hi, No MCUBoot. And yes, the board boots correctly and I can use GDB to debug. I can see the GPIO driver calls, the values that are set and so on. My prj.conf file is as simple as it can get: CONFIG_G

#gpio #nrf52832

Are you sure that your board boots correctly? ( debug through gdb or just simple serial output ) What version of the SDK are you using? Is MCUBoot activated in your prj.conf?

#gpio #nrf52832

Not sure if I'm going to have any help on this, but anyway: I've a standard NRF52832 module that has connected to pin 5 a red LED. If I flash the module (through JLink) with the Arduino framework, the

#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

Hi Diogo, As written before “Note that for other drivers enabling instances happens in Device Tree. Counter will be aligned to that at some point.”. We are going towards instances being enabled in DT

#nrf52832

Hi Diogo, CMake is complaining because even though COUNTER driver is enabled there is no COUNTER instance enabled. In the example there is a Kconfig (samples/drivers/counter/alarm/Kconfig) which enabl

#nrf52832

Hi there, I've started using Zephyr OS last week, so is better to advise that there might be a tiny chance of this question being dumb. I'm trying to use the Nordic's nRF52832 RTC clock, so wrote a sm

#nrf52832

Hi all, I want to test DTLS in IPv6 over BLE network. My set up looks as follows: BLE wifi wifi nrf52832 --------------------- Raspberry Pi Border router --------------- WIFI router --------------- PC

#ble #crypto #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