Thanks all for the feedback. We seem to have a slim consensus on “settings” so I will go for that. Regards, Carles

Hi All, A couple of hours ago I issued a pull request [1] introducing a new external library providing a framework to create GUIs. While doing so I encountered some issues: 1) The library is licensed

I like settings. Do not thing it is long, sett just makes it ugly. Anas

The advantage of “settings” is that it matches what other people mean by those: https://support.apple.com/en-us/HT201274 The disadvantage is that it is a bit longJ “sett_” perhaps as a

I actually like "settings", I find it carries well the idea of run time configuration

Hi Sterling, Thanks for the feedback.

Hi Jukka, Thanks for the feedback.

I like syscfg mentioned below.

Hi Erwan, Thanks for the feedback. I did think about using “marshalling”, but I thought it was less common than “serialization” so I went for the “s11n” abbreviation. I would

Hi Carles, as this seems to be about configuration settings, why not settings cfgdb or something like that. Why do we need to mention the serialization at all in the function names, that sounds

Hi Carles, Serialization is also sometime called marshalling, so an alternative could be "marshal"/"cfg_marshal"/"rtcfg_marshal" Cheers Erwan

Hi all, Andrzej from Nordic has just ported the *run-time* configuration system from Mynewt into Zephyr [1]. This is essentially a system-wide way of loading and storing all state from and to

Yes, I had to increate both stacks’ size, current configuration is: CONFIG_MAIN_STACK_SIZE=640 (from 512) CONFIG_BT_RX_STACK_SIZE=1450 (from 1100) Regards, Kai

Thanks Kai. Glad to know you have PB-GATT sans micro:bit display, working. Did you have to increase the STACK_SIZE(s)? if so, which ones? Regards, Vinayak

Hi, If #BluetoothMesh DEVICE ECDH-public key (oob public key) is exchanged over OOB channel then what is further need of authentication using input-OOB or output-OOB or static-OOB ? Thanks,

Hi, I think we can do OOB pairing, even if Device doesn't have display to share Passkey with user App. 1. Create ECDH public-private key pair (only once in Device life) 2. Read ECDH-Public key via

Hi Vinayak, I followed your instruction to disable some features above Bluetooth core spec v4.0, like 4.1, 4.2 and 5.0 as follow: #Controller #5.0

I'm attempting to port over a custom board (NRF52832) and I'm a little confused by which config files are still being used (CMAKE build). Should I be putting my configurations in <board>_defconfig,

Hi Ken, As the faulting instruction address is in RAM, I suspect an overflow of some thread call stack. The PB-GATT may not have been tested on micro:bit due to restricted amount of RAM. But,

Hi Johan, Thank you for the proposal, I've tested it. I copied microbit_gatt.conf and reduced CONFIG_BT_L2CAP_TX_BUF_COUNT to 2, RAM usage is 99.93%, which can make it fit micro:bit RAM size, but