Hi Prasad,
On Fri, Feb 15, 2019 at 1:24 PM prasad wrote:
> Hi Chris,
>
> Currently I have been able to develop an app which is able to store bond
> information in NVS flash. If my device (ESP32) based on NIMBLE stack is
> rebooted, the bond remains intact. But if the other device is rebooted
>
Hi Chris,
Currently I have been able to develop an app which is able to store bond
information in NVS flash. If my device (ESP32) based on NIMBLE stack is
rebooted, the bond remains intact. But if the other device is rebooted
the ` key_sec->peer_addr.val` gets changed based on
Hi Chris,
Thank you for your response. As I build my understanding from your response,
The `idx` field most probably is useful in searching the case where
`key.sec.peer_addr = *BLE_ADDR_ANY`, which most probably is useful to
search our security keys. Correct me if I am wrong.
The reason
Hi Prasad,
On Wed, Feb 13, 2019 at 03:13:26PM +0530, prasad wrote:
> Hi all,
>
> As it happens, I fixed the bug in my code. It now correctly retrieves
> LTKs and bond is maintained even after reboot.
>
> Apart from this I just wanted to understand reason behind including
> 'idx' in structure
Hi all,
As it happens, I fixed the bug in my code. It now correctly retrieves
LTKs and bond is maintained even after reboot.
Apart from this I just wanted to understand reason behind including
'idx' in structure 'ble_store_key_sec'. Could you please help me
understand use-case behind
Hi all,
With further debug effort the disconnect happens with HCI error 0x3d:
BLE_ERR_CONN_TERM_MIC.
Once the connection is establish, if we disconnect and try to reconnect
it is disconnecting with said reason.
I am attaching logs with additional prints. Please help me to know if I
am
Hi all,
Are there any pointers/documentation for storing NIMBLE bond information
in NVS memory?
I tried to quickly implement simple application by modifying
'*ble_store_ram.c*'. I modified
/ble_hs_cfg.store_read_cb/store_write_cb/store_delete_cb/ callbacks
according to the requirement. I
