PASSKEY

RE: PASSKEY

bjorn-spockeli — Thu, 17 Jan 2019 15:37:13 GMT

Is possible for you to upload the ble_app_hrs_c as well as the ble_app_hrs example folders that you have modified?

RE: PASSKEY

katyon — Tue, 04 Sep 2018 13:30:30 GMT

just to clarify: all work (read+write) from central -only if peripheral is configured without a passkey .

if peripheral contains passkey then read returns a zero length.

in that case: BLE_GAP_EVT_AUTH_KEY_REQUEST event never happens.

Yona

RE: PASSKEY

katyon — Mon, 03 Sep 2018 15:21:01 GMT

Sorry Sorry Sorry

of course I mean ble_app_hrs_c.

I understood where to find my advertised peripheral services and how to read/write to the characteristics.

RE: PASSKEY

bjorn-spockeli — Mon, 03 Sep 2018 15:14:30 GMT

But you do understand that the ble_app_hrs is a peripheral example and that it cannot communicate with your custom peripheral unless you add the central role to this example? You need to modify the ble_app_hrs_c example( found in nRF5_SDK_11.0.0_89a8197\examples\ble_central\ble_app_hrs_c) if you want to communicate with your custom peripheral

RE: PASSKEY

katyon — Mon, 03 Sep 2018 15:08:25 GMT

as I realized that I would need to use BLE_GAP_IO_CAPS_KEYBOARD_ONLY /BLE_GAP_IO_CAPS_KEYBOARD_DISPLAY for the passkey issue,

It seemed much closer (from answers on these pages)- to use ble_app_hrs, so I switched to that project.

I can Read/Write to (my)peripheral BLE that dosnt include a passkey.

Yona

RE: PASSKEY

bjorn-spockeli — Mon, 03 Sep 2018 14:56:41 GMT

Your original post was this:

me again, new issue

now that a peripheral BLE is working (including the passkey), I'm requested to develop a tester for that unit.

For that I need A BLE central .

so I started with nRF5_SDK_11.0.0_89a8197\examples\ble_central\ble_app_multilink_central .

all is fine.the only issue is again: how to operate the passkey (as a central unit)

thanks

Yona

So first question are you still using the ble_app_multilink_central as the central example for your tester? If yes, have you set the IO capabilities in this example as BLE_GAP_IO_CAPS_KEYBOARD_ONLY or BLE_GAP_IO_CAPS_KEYBOARD_DISPLAY?

RE: PASSKEY

katyon — Mon, 03 Sep 2018 14:16:16 GMT

Sorry.

It seems I dont understand how exactly to configure the central-other then what I already did.

could you please show me how to do this configuration

thanks

Yona

RE: PASSKEY

bjorn-spockeli — Mon, 03 Sep 2018 14:09:22 GMT

Yes, i am aware of that but you stated that you're using the ble_app_hrs example which is a peripheral example. Hence, I am asking if you have configured the CENTRAL example to have one of the two mentioned IO capabilities?

RE: PASSKEY

katyon — Mon, 03 Sep 2018 13:38:28 GMT

please note the lines:

#define SEC_PARAM_IO_CAPABILITIES BLE_GAP_IO_CAPS_KEYBOARD_DISPLAY

the function dealing with these defines is device_manager_init()

after it filles the params- it calls dm_register()

I've wrote these lines in my question

Yona

RE: PASSKEY

bjorn-spockeli — Mon, 03 Sep 2018 13:35:00 GMT

But have you set the IO params in the central to BLE_GAP_IO_CAPS_KEYBOARD_ONLY or BLE_GAP_IO_CAPS_KEYBOARD_DISPLAY ? It is the central that will send the AUTH_KEY_REQUEST to the peripheral.

RE: PASSKEY

katyon — Mon, 27 Aug 2018 15:53:06 GMT

ever so sorry- still fail to receive the event BLE_GAP_EVT_AUTH_KEY_REQUEST anywhere

I'm using the project ble_app_hrs (nRF5_SDK_11.0.0_89a8197)

some of the code:

#define SEC_PARAM_BOND 1
#define SEC_PARAM_MITM 1
#define SEC_PARAM_IO_CAPABILITIES BLE_GAP_IO_CAPS_KEYBOARD_DISPLAY //
#define SEC_PARAM_OOB 0
#define SEC_PARAM_MIN_KEY_SIZE 7
#define SEC_PARAM_MAX_KEY_SIZE 16
#define SEC_PARAM_LESC 0 /**< LE Secure Connections not enabled. */
#define SEC_PARAM_KEYPRESS 0 /**< Keypress notifications not enabled. */

the function dealing with these defines is device_manager_init()

after it filles the params- it calls dm_register()

can you please guide me to what I'm doing wrong?

thanks again

Yona

RE: PASSKEY

bjorn-spockeli — Wed, 22 Aug 2018 12:13:01 GMT

You will have to add it as a case in on_ble_evt and respond as shown in the Bonding: Passkey Entry, User Inputs on Central or OOB. Note you also have to set the IO params in the central to BLE_GAP_IO_CAPS_KEYBOARD_ONLY or BLE_GAP_IO_CAPS_KEYBOARD_DISPLAY.

RE: PASSKEY

katyon — Wed, 22 Aug 2018 10:50:26 GMT

thanks for your reply

I fail to find the received event BLE_GAP_EVT_AUTH_KEY_REQUEST

in the functions : on_ble_evt (main.c)

ble_conn_state_on_ble_evt,ble_conn_params_on_ble_evt (ble_conn_params.c)

could you please tell me where to expect this event

also looked in your other links, cant make out- where to expect,how to respond

thanks again

Yona

RE: PASSKEY

bjorn-spockeli — Wed, 22 Aug 2018 08:20:25 GMT

HI Yona,

you need to reply to the BLE_GAP_EVT_AUTH_KEY_REQUEST with sd_ble_gap_auth_key_reply with the passkey as a parameter, see the Bonding: Passkey Entry, User Inputs on Central or OOB MSC.

You can also take a look at this post.

Best regards

Bjørn

RE: PASSKEY

katyon — Wed, 22 Aug 2018 06:39:57 GMT

me again, new issue

now that a peripheral BLE is working (including the passkey), I'm requested to develop a tester for that unit.

For that I need A BLE central .

so I started with nRF5_SDK_11.0.0_89a8197\examples\ble_central\ble_app_multilink_central .

all is fine.the only issue is again: how to operate the passkey (as a central unit)

thanks

Yona

RE: PASSKEY

bjorn-spockeli — Wed, 25 Jul 2018 16:12:32 GMT

If you do not want the ble_app_hrs example to go to SYSTEM OFF, then simply comment out the sleep_mode_enter(); call under the BLE_ADV_EVT_IDLE case in on_adv_evt() and under the BSP_EVENT_SLEEP case in bsp_event_handler().

Best regards

Bjørn

RE: PASSKEY

katyon — Wed, 18 Jul 2018 08:12:29 GMT

one more thing:

I've tried using nRF5_SDK_15xxxxx package with ble_app_hrs example project.

its way too heavy . too many elements to remove (and than it gives some internal error).

so I still need your help regarding the resets/BLE dying .

I'd prefer not to call sd_power_system_off if I can avoid it

Thanks

Yona

RE: PASSKEY

katyon — Wed, 11 Jul 2018 11:16:15 GMT

I tried to advertise manufacturer data. even coping a full function from Nordic help. for some reason- didn't work .

the application(cellphone) guy didn't like the appearance because he would have to preform a READ to get that info.

then I realized that the advertised Service isn't a real functional service. so advertising in is actually

"for free".

the app guy didn't object so that's how we solved that.

so now a new issue.hope you still have some more patience left for my questions.

when trying to make the passkey work- you recommended to use ble_app_hrs example project .

(I'm using nRF5_SDK_11.0.0_89a8197 packege).

I've noticed but didn't pay attention to it then: the SW RESETS every some time (~ 4 minutes) due to an error : NRF_ERROR_SOC_POWER_OFF_SHOULD_NOT_RETURN returned by function sd_power_system_off (called from sleep_mode_enter).

if I remove this function all together then the SW will not reset- BUT the BLE goes dead after the same time (~4 minutes).

meanwhile the SW is still running and the application timers are still on ( timers resulting from app_timer_create).

coming out of this situation - by resetting the HW/SW .

what would you say ?

thanks again

Yona

RE: PASSKEY

Vidar Berg — Mon, 02 Jul 2018 17:01:58 GMT

Hi,

It's not possible to update Services and characteristics on the fly. You need to disable then enable the softdevice and re-initialize the new BLE services. However, you can update your advertisement payload using ble_advdata_set() regardless of what services/characteristics you have. Also, the appearance may be included in the advertisement packet: ble_advdata_t::include_appearance

RE: PASSKEY

katyon — Thu, 28 Jun 2018 09:01:39 GMT

Hi again.

new issue:

the guys writing the application on the cell phone are bringing this up.

I might have 1-20 BLE devices in a given location. all of them would be seen by the cellphone application.

each of my BLE devices has a different TYPE (say up to 10 types ).

the TYPE of a given device might change (not very often) .

the application "would like" to search all devices ,sort only my devices, show a list of them, each with an icon. the icon is the TYPE of the device.

my suggestion was to use appearance.

so every time my TYPE changed- I'll use sd_ble_gap_appearance_set to change it.

their complaint is that in order for them to know all TYPES, they need to READ the appearance characteristic for each of my devices, and that would take them too long.

their suggestion is to have a service that its uuid will be a function of the device's TYPE.

in that way- I'll will have one (an empty) service that its uuid will a function of the TYPE.

in that way- all that's needed from them is to scan services , sort those that belong to me , and understand (from the uuid ) there TYPES.AVOIDING the need to actually preform a READ into these services (characteristics).

the thing is- I don't see a function for service delete,characteristic delete, change of uuid.

How can I solve this? what would you do?

thanks

yona

RE: PASSKEY

Vidar Berg — Mon, 18 Jun 2018 06:00:51 GMT

No worries, thanks for letting me know.

Vidar

RE: PASSKEY

katyon — Mon, 18 Jun 2018 05:56:08 GMT

sorry sorry sorry.

my mistake was somewhere else.

thanks again for your patience.

YONA

RE: PASSKEY

Vidar Berg — Mon, 18 Jun 2018 05:29:29 GMT

Hi,

It sounds like you're doing it correctly. sys_evt=2 means NRF_EVT_FLASH_OPERATION_SUCCESS, so it should have worked. Did you make sure to read out the flash content after the NRF_EVT_FLASH_OPERATION_SUCCESS event?

RE: PASSKEY

katyon — Sun, 17 Jun 2018 13:40:08 GMT

Hi again

eventually I found the variable m_connection_table[0].state

it contains the connection state- so if passkey not cleared - I can avoid notifys.

now if I may- a new issue: sd_flash_write,sd_flash_page_erase

calling sd_flash_write returns (after 20uS) 0x00 (probably NRF_SUCCESS)

than (after 2870uS) at sys_evt_dispatch i receive sys_evt=2 ( probably NRF_EVT_FLASH_OPERATION_SUCCESS)

STILL nothing is written to flash.

maybe you have a clue to what I'm doing wrong.

using nRF5_SDK_11.0.0_89a8197 SW package.

thanks again

YONA

RE: PASSKEY

Vidar Berg — Tue, 05 Jun 2018 07:49:18 GMT

Hi,

Notifications are enabled by writing to the 0x2 to the CCCD so it is the write operation that should require authentication. It's not possible to require authentication for reading of the CCCD, and that is why the softdevice returns the invalid param error. Note that CCCD only contains the configuration value, not the characteristic value. Also worth noting that this configuration is persistent across connections when the devices are bonded.

The characteristic value permissions are set on attr_md.read_perm and attr_md.write_perm if you use ble_hrs.c::heart_rate_measurement_char_add()as reference.