EVB with hello_client can't pair with Win10 PC

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
lock attach
Attachments are accessible only for community members.
YufengP_26
Employee
Employee
50 sign-ins First solution authored 25 sign-ins

SDK Version:WICED-Smart-SDK-2.2.3

Module: 20736, 20737

Customer needs an application with Piconet feature to work as slave to pair Win10 PC. Customer found the SDK application hello_client on EVB can't work as slaver to pair Win10 PC. As I tested hello_client on EVB, it can work as Piconet mode, but it can’t be paired with Win10 PC. The steps are below. Do you have the suggestions to make hello_client worked as slave mode to pair win10 PC? Or do you have the suggested sample application to match customer application?

1.download hello_client application to 20736 or 20737 EVB and reset the EVB

2 go to the Bluetooth searching UI on Win10 PC once the tested EVB was found,  pair it

3.then the dialog (password is invalid) will pop,

4.The failure information can be found below, the whole log named win10-helloclient-connect-log.log is attached, would you please analyze the failed reason?

get pairing request

Bond Request

l2cap Rx:

40 20 0a 00 06 00 05 00 13 01 02 00 00 00

blecm evt handler:

0e 0c 01 18 20 00 74 8c 9d b7 28 86 53 16

blecm evt handler:

0e 0c 01 18 20 00 3e ae 57 20 6b 44 83 75

@$*#04FF0EF700920101008004D61D01000000

l2cap Rx:

40 20 15 00 11 00 06 00 03 03 0d 04 91 14 08 8a

13 e7 f2 67 0f f1 20 02 6e

l2cap Tx:

40 20 15 00 11 00 06 00 04 74 8c 9d b7 28 86 53

16 3e ae 57 20 6b 44 83 75

Get S_Conf.

blecm evt handler:

13 05 01 40 00 01 00

@$*#04FF0EF7009201010080041A1D00000000

l2cap Rx:

40 20 06 00 02 00 06 00 05 07

Pairing failed

0 Likes
1 Solution
ZhaohuaS_76
Employee
Employee
25 sign-ins 10 questions asked 10 sign-ins

Hi Yufp,

The root cause is 20736 made an incorrect SMP role in connection.

If as a BLE salve, 20736 will be SMP responder role; if as a BLE master, 20736 will be SMP initiator. In default SMP role is responder, will be set to a SMP initiator in calling blecen_Create. So we must set the SMP role manual by function lesmp_setSMPRole.

BR,

Ocean

View solution in original post

6 Replies
BoonT_56
Employee
Employee
500 likes received 250 likes received 100 likes received

Which SW in Win10 did you use to connect your hello_client? From your logfile, the disconnection was initiated by the PC.

You can try again using hello_sensor (slave) instead.

You may also want to install Widcomm BT Software for Win from the below link.

https://www.broadcom.com/support/bluetooth

zhaohua

YufengP_26
Employee
Employee
50 sign-ins First solution authored 25 sign-ins

Hi Boont,

Yes, hello_sensor work well to pair Win10 PC.

For hello_client application: When removing  blecen_Create()  from hello_client_create(), hello_client can pair Win10 PC, however the Master role can't work anymore.

0 Likes
ZhaohuaS_76
Employee
Employee
25 sign-ins 10 questions asked 10 sign-ins

Hi Yufp,

The root cause is 20736 made an incorrect SMP role in connection.

If as a BLE salve, 20736 will be SMP responder role; if as a BLE master, 20736 will be SMP initiator. In default SMP role is responder, will be set to a SMP initiator in calling blecen_Create. So we must set the SMP role manual by function lesmp_setSMPRole.

BR,

Ocean

A helpful note for others reading this. To modify hello_client.c to work with WINDOWS 10, add the lesmp_setSMPRole() call in the position shown here:

   ....

    lesmp_regSMPResultCb((LESMP_SINGLE_PARAM_CB) http_client_smp_bond_result);

    // set the role for SMP.

    lesmp_setSMPRole(LESMP_ROLE_RESPONDERS);

    lesmp_setPairingParam( ...

Thanks bobcat

0 Likes
YufengP_26
Employee
Employee
50 sign-ins First solution authored 25 sign-ins

thanks, this is okay.

0 Likes