Skip to content
This repository was archived by the owner on Apr 16, 2021. It is now read-only.

Use of KvStore after 1.1.4 don't work #99

Open
Petorrr opened this issue Aug 15, 2020 · 3 comments
Open

Use of KvStore after 1.1.4 don't work #99

Petorrr opened this issue Aug 15, 2020 · 3 comments

Comments

@Petorrr
Copy link

Petorrr commented Aug 15, 2020

My application works fine with the 1.1.4 release for the NANO BLE. Updating to 1.1.5 results in a wire compilation error. Then updating to 1.1.6 results in a failing application. The activity on the board indicates a blinking LED_BUILTIN (PIN_LED) (13), 4 slow blinks, then 4 fast blinks.
The application I run successfully with the 1.1.4 release doesn't use this LED at all, so it must be some alert or panic indication coming out of the mbed?
Digging and debugging a little deeper it appears that the use of the mbed KvStore function call kv_get causes this panic indication on the Led;
res = kv_get("/kv/check_valid", KvBuf, sizeof(KvBuf), &actualSize);

Any thoughts?

@per1234
Copy link
Contributor

per1234 commented Aug 15, 2020

The meaning of that blink pattern is explained here: #90 (comment)

@Petorrr Petorrr changed the title Releases after 1.1.4 don't work Use of KvStore after 1.1.4 don't work Aug 15, 2020
@Petorrr
Copy link
Author

Petorrr commented Aug 15, 2020

The meaning of that blink pattern is explained here: #90 (comment)

Thanks and I can confirm it crashes in kv_get. Any thoughts on why the use of the KvStore fails in the 1.1.6 version and not in the 1.1.4 release? I use the KvStore to store parameter values due to the lack of an EEPROM on the Nano BLE boards. KvStore seemed to offer a nice alternative to create a sort of registry of values.

@manchoz
Copy link
Contributor

manchoz commented Aug 15, 2020

There a few similar issues already open in upstream mbed-os. They are related to the new mandatory SecureStore component dependency.

Someone proposed a fix but I wasn't able to replicate and get it working (at least on an external SPIFBlockDevice).

We will try to track the evolving issues and post updates - and a fix - as soon as they will be available.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants