How to specify your own user passkey

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.
hinu_4327176
Level 3
Level 3

Hello

Sorry, please resume the discussion below.
<https://community.cypress.com/thread/51536>


I tried passkey pairing with 43438 as Central using a device with a control to set a fixed passkey on the peripheral side, but it did not work properly.
(Peripheral equipment has a track record of operation.)

After (Bluetooth status events: BTM_PASSKEY_REQUEST_EVT) is issued, event issuance stops and (Bluetooth status events: BTM_PAIRED_DEVICE_LINK_KEYS_UPDATE_EVT) is not issued.

Is there no problem with the usage in the attached source code?

0 Likes
1 Solution

Hi @hiroaki nunome San,

​Unfortunately this passkey reply timeout issue is on WICED 6.1 and 6.4.

The issue is not seen in WICED 6.2 SDK version. I tested and its working for me.

I will report this issue internally .

Meanwhile can you please try with SDK 6.2 (  WICED Studio Wi-Fi/Combo Docs &amp; Downloads  ) and confirm if this issue is fixed?

Thanks,
Anjana

View solution in original post

11 Replies
AnjanaM_61
Moderator
Moderator
Moderator
5 comments on KBA First comment on KBA 5 questions asked

Hello ,

Can you please confirm if BTM_PAIRING_COMPLETE_EVT triggered after passkey reply or not? If yes, what was the status?

On the peer side , can you check if you are getting passkey reply ?

Which peer device or app are you using?

Just for testing purpose , can you just try calling the passkey reply API directly in the BTM_PASSKEY_REQUEST_EVT and try?

case BTM_PASSKEY_REQUEST_EVT:

    uint32_t passkey = 123456;

            wiced_bt_dev_pass_key_req_reply(WICED_BT_SUCCESS,p_event_data->user_passkey_request.bd_addr , passkey);

break;

Thanks,
Anjana

Hello

Can you please confirm if BTM_PAIRING_COMPLETE_EVT triggered after passkey reply or not? If yes, what was the status?
  -> yes
     The status is (Response timeout).
     The output information is as follows.
         p_event_data->pairing_complete
                     .bd_addr
                     .transport : 2
                     .pairing_complete_info
                       .br_edr
                       .ble
                         .status : WICED_BT_NOT_AUTHORIZED
                         .reason : 22      (Response timeout)
                         .sec_level : 0
                         .is_pair_cancel: WICED_FALSE
                         .resolved_bd_addr
                         .resolved_bd_addr_type : 0
                         .bonding_status : WICED_SUCCESS

On the peer side , can you check if you are getting passkey reply ?
  -> It is difficult to check with the app.
      There is no API to get.

Which peer device or app are you using?
  -> It is an application of our product (in-house development).


In addition to this problem, the following problems have also occurred.
  ・Cannot reconnect after bonding.
      <<https://community.cypress.com/thread/51417>>
  ・Whitelist does not work properly.

Could it be the same cause?

0 Likes

Hi @hinu_4327176

I was able to reproduce your issue . We are trying to find out the root cause.

We will update you asap.

Meanwhile if you have any airlogs , please share .

Regards,
Anjana

0 Likes

Hi @hiroaki nunome San,

​Unfortunately this passkey reply timeout issue is on WICED 6.1 and 6.4.

The issue is not seen in WICED 6.2 SDK version. I tested and its working for me.

I will report this issue internally .

Meanwhile can you please try with SDK 6.2 (  WICED Studio Wi-Fi/Combo Docs &amp; Downloads  ) and confirm if this issue is fixed?

Thanks,
Anjana

Hello

Tried with WICED 6.2 SDK version.

After returning the passkey, BTM_PAIRING_COMPLETE_EVT was triggered and pairing was completed successfully.

However, after that, the phenomenon of disconnection occurred.
Did the same phenomenon occur when the reproduction was successful?


Currently, development is progressing with the WICED 6.4 SDK version, so it is difficult to return to the WICED 6.2 SDK version.
Is there a way to solve the problem with the WICED 6.4 SDK version?

Thanks

0 Likes

Hi @hiroaki nunome San,

I will check internally if this can be fixed on SDK 6.4

Q) However, after that, the phenomenon of disconnection occurred.

=> Can you please let me know what was the disconnection reason ?

Thanks,

Anjana

Hello

Sorry, I don't know the detailed situation.

In case of using WICED 6.4 SDK version.
There is a phenomenon that disconnection occurs after successful pairing without a passkey.
In this case, you have been disconnected from the peer device.

I don't know why it was disconnected and asked if a similar problem occurred.

We are very grateful for your assistance in solving the problem.

Thanks

0 Likes

Hi @hiroaki nunome San,

I am sorry I didn't get you . Have you tested with WICED 6.2? Are you seeing any issues on 6.2 with your application?

Regards,

Anjana

Hello

Sorry for the ambiguous answer.

Tested with WICED 6.2.

During the development process, the problem of disconnection no longer occurred.

Tested with WICED 6.2, the problem no longer occurs.

The exact cause has not been determined.

Currently, this disconnection is pending.
If it does not occur in the future, there is no problem.

Thanks

0 Likes

Ok, Hope the issue is resolved by using WICED 6.2.

Please use WICED 6.2 , if you want to use Central role with Keyboard IO capability.

Regards,

Anjana

Takashi_M
Moderator
Moderator
Moderator
1000 replies posted 500 solutions authored 750 replies posted

This thread continues in another thread.

How to specify your own user passkey

(thread#224025)

0 Likes