port privacy feature. Please let me know your
take on this.
Regards,
Prasad
From: Andrzej Kaczmarek
Sent: Thursday, January 30, 2020 6:09 PM
To: dev@mynewt.apache.org
Cc: Hrishikesh Dhayagude
Subject: Re: NimBLE: Host based privacy support
Hi Prasad,
On Thu,
g, check if the peer is RPA, check if it is resolvable
by any entry from "peer records", get entry from "resolving list" corresponding
to it and we are done with the reconnection.
Please let me know if this is an acceptable approach for mynewt nimble.
Regards,
Prasad
the
option configurable (syscfg ?) and how to maintain upstream `mbedTLS` in
mynewt framework (submodule ?) would be really helpful.
Regards
Prasad
or the numbers are as expected ?
Regards
Prasad
On 21/05/19 8:00 PM, Prasad wrote:
Hi all,
After spending some time, I figured out a way to write continuously
using `ble_gattc_write_no_rsp_flat`. I created different task and
added 1 sec delay. But with MTU = 512 and delay = 1sec, throughput
seems
ket
'BLE_HCI_EVCODE_NUM_COMP_PKTS,'. Please feel free to share any pointers
which may help me build my understanding further.
Regards
Prasad
Regards
Prasad
On 17/05/19 4:35 PM, prasad wrote:
Hi all,
Is it possible to continuously write GATT CHAR value using
`ble_gattc_write_no_rsp_flat`
wanted to understand if there is any way we can use this function
to continuously write to GATT characteristic ?
Regards
Prasad
dr.val` field has been changed.
`
if (ble_addr_cmp(_sec->peer_addr, BLE_ADDR_ANY)) {
if (*ble_addr_cmp(>peer_addr, _sec->peer_addr*)) {
continue;
`
Regards
Prasad
On 14/02/19 11:53 AM, prasad wrote:
Hi Chris,
Thank you for your response. As I build my und
m;
out_key->ediv_rand_present = 1;
*o**ut_key->idx = 0;* // /This made me wonder why we need to search
based on this criteria./
}
Thank you for response anyways. Really helpful.
Regards
Prasad
On 13/02/19 9:44 PM, Christopher Collins wrote:
Hi Prasad,
On Wed, Feb 13, 2019 at
including 'idx'?
/** Number of results to skip; 0 means retrieve the first match. */
uint8_t idx;
Regards
Prasad
On 12/02/19 7:35 PM, prasad wrote:
Hi all,
With further debug effort the disconnect happens with HCI error 0x3d:
BLE_ERR_CONN_TERM_MIC.
Once the connection is establish
making any obvious mistake.
Regards
Prasad
On 11/02/19 7:10 PM, prasad wrote:
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
equired_size = sizeof(struct ble_store_value_sec);
err = nvs_set_blob(nimble_handle, "our_sec", >sec,
required_size);
/* NVS Commit */
err = nvs_commit(nimble_handle);
if (err != ESP_OK) return err;
/* NVS Close */
nvs_close(nimble_handle);
return 0;//
Regards
Prasad
11 matches
Mail list logo
