Passkey is not working

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

cross mob
Anonymous
Not applicable

In WICED_SMART_SDK 2.1.0, I use 2 boards which are hello_sensor and hello_client.

I uncommented PASSKEY for both.

Default pass key is 123456 and I changed passkey as 57920 in hello_sensor.

But hello_sensor and hello_client can be connected well.

As far as I understand, both devices can not be connected if passkey is different.

The message of hello_sensor is following.

/////////////////////////////////////////////////////////////////////////

14:46:34 -

14:46:34 - NVRAM write:0009

14:46:34 -

14:46:34 - hello_sample, encryption changed 20736a1c8cca

14:46:34 -

14:46:34 -

14:46:34 -  permission check retCode = 00

14:46:34 -

14:46:34 -  permission check retCode = 00

14:46:34 - EncOn 20736a1c8cca client_configuration:0000 blinks:0

14:46:34 -

14:46:34 -

14:46:34 - l2cap Tx:

14:46:34 - 402010000c0005001201080050009001

14:46:34 - 0000bc02

14:46:34 - Tx buffer = 14

14:46:34 -

14:46:34 - blecm evt handler:

14:46:34 - 0e04010a200c

14:46:34 -

14:46:34 - blecm evt handler:

14:46:34 - 0e04010a200c

14:46:34   Connection is UP.

14:46:34   profile idle timer stop

14:46:34   connUp

14:46:34   noAdv

14:46:34   BLE_idleconn:timer(120)

14:46:34   noAdv

14:46:34   profile idle timer stop

14:46:34   BUZBeep(0)

14:46:34 -

14:46:34 - l2cap Rx:

14:46:34 - 4020090005000400122b000100

14:46:34 -

14:46:34 - Checking readable attribute 002b

14:46:34 -

14:46:34 -  permission check retCode = 00

14:46:34 - hello_sensor_write_handler: handle 002b

14:46:34 -

14:46:34 - hello_sensor_write_handler: client_configuration 0001

14:46:34 -

14:46:34 - hello_sensor_write_handler: NVRAM write:0009

14:46:34 -

14:46:34 -

////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

0 Likes
1 Solution

eyan,

I've been able to reproduce the issue and have confirmed with the developers that this appears to be a bug. Unfortunately, I do no have an ETA on when the problem will be resolved. Shall keep you posted with the updates. arvindsboont

View solution in original post

7 Replies