Hi, so you have FW update solved, using boot_request_upgrade(BOOT_UPGRADE_TEST), mcuboot swaps the data between slots and starts your new FW? And then you want to rollback? Then I think you should che

#mcumgr #mcuboot #fota

Hi, why do you want to compile it with offset of slot1? Normaly you compile image for slot0, upload it to slot1 and MCUboot will swap them after reboot. Martin Dne 25.10.2021 v 13:40 Brenton Chetty na

#mcuboot

Hi, may be you forgot to sign the image? west sign -t imgtool -- --key path_to_mcuboot\root-rsa-2048.pem (or other key that mcuboot is using) west flash --skip-rebuild -- --hex-file build/zephyr/zephy

#mcuboot

Hello, does anybody have working example of using LPCOMP in NRF52832 to wakeup MCU from sleep mode (when input voltage gets above setup voltage) and then read somewhere that it has been woken by LPCOM

Hi, I am trying to figure out how to make the binary for nrf52dk_nrf52832 smaller, so I tried to look at zepyr.map with AMap and I am seeing so much .debug_info, .debug_line etc stuff in .map file. I

Hi Mohamed, i think #include <drivers/sensor.h> with standard #include <zephyr.h> etc should work. Martin Dne 02.11.2020 v 9:37 Mohamed Belaroussi napsal(a):

#nrf5340

Hi, try this, I hope it will work #define TEMP_SENSOR_NAME "TEMP_0" int valid = 0; const struct device *tempSensor device_get_binding(TEMP_SENSOR_NAME); sensor_value sensor_val; int rc = sensor_sample

#nrf5340

Hi, I would recommend looking at samples\bluetooth\peripheral_ht\src I managed to create my code for nrf52832 based on that sample. If you have problems with that sample, I can paste some code here. M

#nrf5340

Hi, this is how my overlay looks like (and it's working) - I wanted to make storage partition smaller and add 2 more partitions. Since I didn't change image0,1 and scratch size, I didn't have to use o

Hello, I have defined characteristic, which can be read, it's user_data is pointing to buffer1. Now when I want to read the data by central, Characteristic Attribute read callback is called. In this c

Dne 06.01.2020 v 18:31 Andy Ross napsal(a): is it 1000ms timeout = 33 cycles, or 1ms timeout = 33 cycles? This is acceptable for short-term timeouts. When this gets into 2.2, can I use "k_uptime_ticks

#nrf52-pca10040

Hi, I understand that there are some problems because of 32768Hz RTC (I am now using NRF52-DK and want to use NRF52832 in my new HW) as referenced here: https://github.com/zephyrproject-rtos/zephyr/is

#nrf52-pca10040

Hi, I understand that there are some problems because of 32768Hz RTC with NRF52832 as referenced here: https://github.com/zephyrproject-rtos/zephyr/issues/9904 , there are some already merged PRs (lik

#nrf52-pca10040