Yes, that is exactly it. In that case I am not sure about the issue. Perhaps Johan can bring some light into it. Carles From:"Li, Jun R" <jun.r.li@...> Date: Thursday, 14 June 2018 at

Yes, every time when I did the tests, I let iPhone “forget the device”, which I suppose to erase the bond info, right? Regards, Jun From: "Cufi, Carles" <Carles.Cufi@...> Date:

Hi there, Have you tried erasing the bond from iOS settings? I find that sometimes bonding fails if the device is already bonded, for whatever reason. Regards, Carles

Hi everyone, I’m trying to test the secured pairing with a NRF51 device by using an iPhone 6 and 7, and noticed different behaviors on different phones: iPhone 7: secured pairing is always

Hi, I am currently trying to map our current BLE GAP API to Zephyr BT API, but I find it a little bit unclear how the pairing/bonding flow is supposed to work on the slave side. From the

Thank you, however it is not ideal that one should read/understand the SMP to understand when a given CB is expected to occour. I have submitted the issue on GitHub. \Theis

Hi Theis, They map directly to the authentication methods from the Security Manager protocol. The lack of documentation for these is indeed an oversight. Could you open a github issue so we can

Hi, I am trying to understand the GAP API for Zephyr Bluetooth Stack, and came across bt_conn_auth_cb(…). This callback function seems to be completely undocumented. Anyone who know what the

As far as I am able to understand your description, this is expected to work. Perhaps you could share a minimal patch to an existing sample to demonstrate when the linker error

Thanks a lot for your help. I have tried your suggested solution with the CMakeList. Unfortunately, this did not work for me. I got the linker errors as described in my initial mail. Let me try to

Hi Rajat, This could be helpful https://devzone.nordicsemi.com/b/blog/posts/nrf-blinky-compatible-firmware-using-zephyr-blueto You've to make changes as per your Board design. regards, vikrant

Hi Jun, The second one is a bit ambiguous, since it'll also be called for subsequent connections when the connection gets encrypted, even though pairing is not in progress (it already happened over

Hi, I am getting this error. -- Selected BOARD nrf52840_pca10056 Zephyr version: 1.12.99 Parsing Kconfig tree in /home/vikrant/projects/zephyr/zephyr/Kconfig Using

Hi, In my BLE project, a passkey is required to access the NRF51 device; thus the callback functions of “struct bt_conn_auth_cb” were implemented to achieve secured paring. What I observed is

Hi Johan, Which app you used for testing ? Is it samples/boards/nrf52/mesh/onoff-app by adding persistent storage support ? Could you please test it for PR:8296 by removing NVS from it ? Thanks!!

That is true, this way doesn't support adding a driver module into the application since the app doesn't directly call anything from the driver. I'm wondering why driver modules in zephyr directory

"Li, Jun R" <jun.r.li@...> wrote: Well, this way of doing bears a whole of problems in some conditions. While it works in probably most cases, including drivers in such a library won't work.

Hi Patrick, If you still want to keep your library (module), another way you can do is to add your library as the link dependency for the application library (app) by the

Hi Vikrant, I understood what you meant. And those are the steps I followed. I used Nordic's new iOS mesh app and used its "node reset" feature. Then I reprovisioned and after that did a power-cycle.

Hi Johan, I've completely removed NVS from my local project. Even after that facing same issue. If you provision & configure -> reset the board -> then it work as expected. But I'm not talking