Re: Retained Register Interface (also, hi!)

I like that idea. I'll start implementing for the NRF with something like that, we can come up with the name in the meantime. How about something with nonvolatile like hal_nvreg? I guess they are volatile with a hard reset though... Alvaro On Tue, Apr 3, 2018 at 11:59 AM, marko kiiskila

Re: Retained Register Interface (also, hi!)

Hi Alvaro, I’d recommend a new API in HAL. One where register contents will survive reset, depending on the type of reset. Have #define HAL_RETAIN_REG_MAX XXX in some MCU specific header file. And then in hal/hal_retain_reg.h #ifnfdef HAL_RETAIN_REG_MAX #define HAL_RETAIN_REG_MAX 0 #endif

Retained Register Interface (also, hi!)

Hello, My name is Alvaro. I'm a firmware/hardware engineer and I've been playing with mynewt at home and at work for a few months now. I mostly hang out in the mynewt slack, but I've been advised to come here for hal and other source change discussions. The one today has to deal with a hal

Re: CBOR encoding problems.

Never mind, I think I got it working. The problem it seems is that the Array has to be a const or declared inside the method. Even though the compiler doesn’t throw a warning / error, thats what it needs. PS, doing a os_mbuf_clear_chain and then doing os_mbuf_get is that an efficient way to

Re: [RFC] Mesh uses multi advertising instances.

Hi Aditya, Please set BLE_MESH: 1 and BLE_MESH_SHELL: 1 and you should be able to use both btshell and mesh shell. Let us know how that works for you. Best regards Michał 2018-04-03 7:56 GMT+02:00 Aditya Xavier : > Hi Łukasz, > > Any pointers, as to what needs to be