Hi Jan, There are many things that can go wrong here. I would start by checking that what is in the qspi flash is equal to what you want. How do you write the program to the flash ? Kind regards, Jehu

Hi Kees and Jan, Zephyr links the code for a code partition specified in the dts as shown above by Jan by specifying in the proj.conf file: CONFIG_HAS_FLASH_LOAD_OFFSET=y CONFIG_USE_CODE_PARTITION=y K

Hi Vikrant, The dts changes you propose might work, but there are some disadvantages with it: if you are overlapping the scratch area with NVS you will loose the data in NVS persistent storage after F

Hi Ulf and Carles, Thanks for the response. It seems that it is not possible to do what I want directly, no problem. I will compare SET_NVS_SECTOR_SIZE with FLASH_ERASE_BLOCK_SIZE in my code to verify

Hi, I am working on a subsystem and I have some problem with Kconfig. I would like to define a configuration setting: SET_NVS_SECTOR_SIZE and apply a default equal to the define FLASH_ERASE_BLOCK_SIZE

Hi Vikrant, I think it is a bad idea to have this kind message to put the device back into unprovisioned state. Anyone who is using this app with your devices could take over all your devices by using

Hi, In the settings part of bt there seems to be a cool way to generate a list of settings with their set, commit and export handlers. Items are added to this list by a macro BT_SETTINGS_DEFINE() and

Hi Vikrant, At the moment the default settings for NVS and FCB are indeed overlapping; you cannot use them at the same time. To use NVS and FCB together my advice would be to look at the board dts fil

#nvs #fcb #bluetoothmesh

Hi, Bluetooth mesh has a replay protection list that basically keeps a link between a address and a sequence counter to protect against replay attacks. It checks if messages are ok by making checking

For bluetooth mesh it would be good to save the replay protection list to a dedicated flash page. This save would only be done in the case of a powerfail or a reboot. nrf51/nrf52 have a powerfail warn

Hello Zephyr Developers, I recently had a request to change the error codes in a zephyr module to use the standard supplied error codes. Doing so would reduce the descriptiveness of the error codes so

Hi Carles, I will add the lifetime calculation to the documentation of NVS. Regarding the comparison between FCB and NVS: FCB would need an additional layer to be able to get this functionality (which

Hi, As the author of NVS (PR6391 https://github.com/zephyrproject-rtos/zephyr/pull/6391) I am probably a bit biased. NVS as is can be used directly for managing persistent data. I am looking into addi

Hi Vikrant, NFFS file system might not be a good choice to store frequently changing data. For this case I have created a library called sfcb that you can find in my zephyr project fork: https://githu

Hi Johan, Thanks for the reply. It is clearly not possible to reduce the stack usage of tinycrypt. Regarding the coexisting of network state and provisioning state, would it be possible to use the con

Hi, Sometimes I run into the situation where a hard fault is triggered (e.g. a bluetooth mesh node with a BT_RX_STACK_SIZE that is set to small). The result of this is a system hang. I can correct thi

Hi, On a zephyr device with bluetooth mesh tinycrypt-ecc is used to generate the ecdh key. Tinycrypt uses a stack of 1kb which is quite large on small ram (16kb) devices. Is it possible to precalculat

Hi, I have been thinking about different ways to add persistent storage to bluetooth mesh. I would like to add this with as few changes to the library as possible. I would store the data in flash usin

Hi Johan, Setting CONFIG_BT_MESH_ADV_BUF_COUNT to 7 solved the issue. Thanks, Jehudi 2017-10-17 12:26 GMT+02:00 Johan Hedberg <johan.hedberg@...>:

Hi Johan, Thanks for the response. I couldn't find CONFIG_BT_MESH_TX_SEG_COUNT as configuration option, but I tried changing CONFIG_BT_MESH_TX_SEG_MSG_COUNT which defaults to 1. I changed it to 10 but