Usually flash drivers/controllers doesn't check whether what was requested to be write was written. As flash driver API implements just write, it doesn't mean that corruption of written data will be d

NFFS support will be removed from the zephyr-project codebase. It was decided to take such action as NFFS has few serious issue which made it unreliable (Such issues were not fixed since a long time,

Hi Q1 – no, this mens that higher part of BLE stack runs on HCI client which has no access to nRF52840 flash at all. Q2 – mcuboot serial recovery or your proprietary protocol which can share common ua

#hci #nrf52480 #ble #uart #samples

HI all, As you know, the Zephyr Dev-review meeting takes place on Thursday 9AM-10AM (PDT) (18h-19h (CEST)). We want to cover topics related to the settings pattern load PR: https://github.com/zephyrpr

So while loading settings subsystem loads all available in storage kay-value pairs. Guaranteed are that it will load the most recently values as the last and then h_commit handler will be executed. Se

Hi I’m unable to reproduce this problem – I mean that I did not encounter problem compiling usbd along with newlibc. Can you point prj.conf you used, or even the project?

I think you can start form looking at the ticket Nordic PCA10059 support without additional Seeger debugger https://github.com/zephyrproject-rtos/zephyr/issues/9055 and related PRs As you can see what

I found a solution in increasing CONFIG_NFFS_FILESYSTEM_MAX_AREAS to 128 64 is exactly what you need as you use 64 flash pages of nRF52. You can try to use nffs build in statistic to garb some info On

I think it was possible that you encounter lack of BLOCK representation in RAM (this is what -12 -ENOMEM stand for). Try to increase CONFIG_FS_NFFS_NUM_BLOCKS until success. Looks like GC was unable t

Hi As you notice right now it is impossible to use both NVS and FCB out of the box. So you need a hack. I think finally this problem should be resolved by introduction of dedicate flash slot which are

#nvs #fcb #bluetoothmesh

Hi. I Think it will be possible – (but can’t be sure). At last Jehudi Maes (the NVS author) is considering right now ho to provide nvs-back-end for the setting (I’m in touch with him). Andrzej

#fcb #nvs #bluetoothmesh

I also see that error cods defined in <errno.h> are insufficient. I think definition value-space for module specific codes are good idea in general. But I'm afraid we can go down the road in case we r

Hi So you must have supplied nRF52840 from VDDH pin – so it power regulator circuit works in high voltage mode. Then internal regulator generate the GPIO output voltage: You need to set UICR->REGOUT0

> I request Zephyr OS maintainer to create & add following attached main.c under $zephyr_base/samples/boards/nrf52/nffs/src & prj.conf under $zephyr_base/samples/boards/nrf52/nffs/ on Github. Great, s

Add configuration CONFIG_MPU_ALLOW_FLASH_WRITE=y to the project (or select via Kconfig). This should help. Andrzej

NFFS Is supported since 1.10 release: https://www.zephyrproject.org/releases/1-10-release-december-2017/ Andrzej From: zephyr-devel-bounces@... [mailto:zephyr-devel-bounces@...

Can you chech whether is it similar to previous mail-list thread topic: NRF5x I2C driver and the sensor/th02 example (on https://lists.zephyrproject.org/pipermail/zephyr-devel/2017-November/thread.htm

Hi Tiaga I think you can take good enough Interrupt driven serial adapter form mcuboot repository here: https://github.com/runtimeco/mcuboot/blob/master/boot/zephyr/serial_adapter.c https://github.com

Hi. For nRF52840 I2C driver is zephyr. All its option are in general i2c Kconfig file. I attached configuration I had used to compile example you mentioned. BR Andrzej

> Well, board configuration is different, different pins are used for LEDs, buttons and UART, but from BLE point of view everything should be the same, correct? Can you check how you configured UART f