Hi Andrzej,
Thank you - that does indeed work.
I have another question. Bonding now works (i.e. using the nRF52
Connect app on Android, I connect to the advertising end device and
then bond with it to save the credentials), however I would also like
to configure the end device so that it
I've experimented some more. If I declare a characteristic with the
BLE_GATT_CHR_F_XXX_ENC flags, then accessing that characteristic
prompts me for a pin code, and if I connect from a previously bonded
profile, then no pin is requested (as expected). So this seems to work
fine, in that I can pin
Hi,
There is no such method to protect services from being discovered, but
this is "by design" as per Bluetooth Core spec [1]. As you said, you
can just protect access on characteristic level by combining
BLE_GATT_CHR_F_XXX_ENC (requires encryption, allows unauthenticated
key) and
I'm working with the BLE uart example and I have it working as is, but it's a
little hidden where the read and write data goes.
I want to do something simple, like write a BLE uart, string and then read a
BLE uart string. I need these functions in the main.c. What functions need
to be
Hi Jacob,
But Kevins code snippet brings up something im thinking about. In his
comments he has
CONFIG_NFFS: 1# Initialize and configure NFFS into the
system
I dont agree with that comment, whats thats actually doing is turning on
the config subsystem and telling it to create its
Are you referring to the host/services/bleuart package? Looking at the code
for that, it appears that there are no callbacks or hooks to allow you to
read and write data. The code appears hard coded to read and write data
from the console.
Regarding receiving data, looks like you'll need to
FYI: seems like it works fine if you enter passkey with leading zeroes
in Android (e.g. "001234" instead of "1234"). Not sure why it works
like this as passkey is handled as integer value during pairing
process, but Android is apparently full of surprises ;-)
Best,
Andrzej
On Mon, Jul 9, 2018 at
