Hi Joseph,
On Sat, Apr 20, 2019 at 09:55:27AM +0200, joseph reveane wrote:
> Hi,
>
> I'm looking for examples on how to build split and single images for NRF52
> based devices.
> The goal is obviously to get more FLASH room for the application.
> I didn't find any example to build a single image
Hi Amr,
I would call it on gap connected event. Then OOB data are stored and SM can
present/use OOB flag during pairing.
Best
Lukasz
On Fri, Apr 26, 2019, 18:57 Amr Bekhit wrote:
> Hi Łukasz,
>
> Thanks for your reply. Where and when should the call to ble_sm_inject_io
> take place? In my
Hi Łukasz,
Thanks for your reply. Where and when should the call to ble_sm_inject_io
take place? In my current setup, I had configured my device to use passkey
pairing, but for testing purposes, was hardcoding the passkey. The BLE
stack was requesting the passkey by calling the GAP event
Hi Amr,
Nimble does support OOB for Legacy and Secure Connections Pairing.
In both cases you just need to provide OOB (TK) data exchanged by other
means e.g. NFC to the NimBLE stack using "int ble_sm_inject_io(uint16_t
conn_handle, struct ble_sm_io *pkey)".
For Secure Connection make sure to
