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

AIROC™ Bluetooth

TaYa_4777276
Level 2
First solution authored 25 sign-ins 10 replies posted
Level 2

I tried whitelist feature in two CYBT353027-02 EVB (v1.2.29), but I could not see an expected behavior.

1st, in Peripheral side, set whitelist filter policy (SSP,F=01) 

  and regist Bluetooth address of Central side in whitelist (/WLA,A=DCD45412D3D1).

TaYa_4777276_0-1642741882979.png

 

Next, in Central side,

  execute the Scan (/S), then the peripheral side is appeared in scan list. Is this behavior correct?

  Execute the Connection (/C), then the connection is successful. is this behavior correct?

TaYa_4777276_1-1642741901285.png

 

If above operation is not appropriate, please let me know right operation.

Best regards,

Yasui @ TED

 

0 Likes
1 Solution
BragadeeshV
Moderator
Moderator First question asked 1000 replies posted 750 replies posted
Moderator

Hi @TaYa_4777276 ,

Whitelisting feature is not supported for filtering the advertisement packets.  This is documented in the gap_start_scan() section of the user guide.

BragadeeshV_0-1644248820503.png

I have filed an internal request for this. Thanks for your interest with our products.

Regards,
Bragadeesh

View solution in original post

0 Likes
8 Replies
BragadeeshV
Moderator
Moderator First question asked 1000 replies posted 750 replies posted
Moderator

Hi @TaYa_4777276 ,

yes, I do not see any issues in the behavior. When you add the the central device's MAC address to the whitelist of the peripheral device,  it means that this particular peer central device can receive the scan response packets from the peripheral and can connect to this peripheral device. Do you have any specific questions in this behavior?

Do you want the peer device's connection request be rejected by the peripheral device?

Also, gap_set_scan_parameters() - SSP is for configuring the scan parameters at the central side and should not be used at the peripheral side. 

Regards,
Bragadeesh
0 Likes
TaYa_4777276
Level 2
First solution authored 25 sign-ins 10 replies posted
Level 2

Hi Bragadeesh,

Sorry for my miss-understanding. I tried whitelist test again.

In peripheral side, set and get WLA as "/WLA,A=DCD45412D3D1" and "/QWL".

In central side, set whitelist filter policy as "SSP,F=1". Then start Scan as "/S,D=1,O=5".

But scan device is not listed.I think peripheral device should be listed.

(If SSP,F=0, peripheral BT address is listed.)

If my understanding or my operation is not correct, could you please advise me?

TaYa_4777276_0-1643172613976.pngTaYa_4777276_1-1643172645321.png

 

Thanks,

Yasui

0 Likes
BragadeeshV
Moderator
Moderator First question asked 1000 replies posted 750 replies posted
Moderator

Hi @TaYa_4777276 ,

You need to update the whitelist of the central side by adding the peripheral BT address. In the central side, you need to use WLA command to add the BT address of the peripheral device to the centrals whitelist. Then only you will be able to see  the advertising packets of the peripheral device. If you don't add, it will be filtered out by the central.

Regards,
Bragadeesh
0 Likes
TaYa_4777276
Level 2
First solution authored 25 sign-ins 10 replies posted
Level 2

Hi Bragadeesh,

I tried your advice as follows.

1) In central side, set WLA as "/WLA,A=peripheral BT address,T=1". Start Scan as "/S,D=1,O=5". The result is a many peripheral devices are listed.

2) In central side, set WLA as "/WLA,A=peripheral BT address,T=1". Set whitelist filter policy as "SSP,F=1" and start Scan as "/S,D=1,O=5". The result is no peripheral device is listed.

Is this behaviors are correct?

TaYa_4777276_0-1643870310753.png

 

My understanding about whitelist feature as below. If it's not correct, please let me know. And can you see your test logs?

Setting : "Add peripheral BT Address to central whitelist by WLA API command" and "Set the filter policy in central by SSP API command".

Behavior : Central performs Scan by /S, then only peripheral device which is registered in whilelist is listed.

Thanks,

Yasui

0 Likes
BragadeeshV
Moderator
Moderator First question asked 1000 replies posted 750 replies posted
Moderator

Hi @TaYa_4777276 , I'm observing a similar behavior. We are checking with our firmware team on this. We will get back to you shortly.

Regards,
Bragadeesh
0 Likes
BragadeeshV
Moderator
Moderator First question asked 1000 replies posted 750 replies posted
Moderator

Hi @TaYa_4777276 ,

Whitelisting feature is not supported for filtering the advertisement packets.  This is documented in the gap_start_scan() section of the user guide.

BragadeeshV_0-1644248820503.png

I have filed an internal request for this. Thanks for your interest with our products.

Regards,
Bragadeesh
0 Likes
TaYa_4777276
Level 2
First solution authored 25 sign-ins 10 replies posted
Level 2

Hi Bragadeesh,

Thanks for your confirmation.

I would like to confirm just in case. Do you mean CYW2070x-based Module does not support Whitelisting feature? If yes, do you have a plan to support this features?

Thanks,

Yasui

0 Likes
BragadeeshV
Moderator
Moderator First question asked 1000 replies posted 750 replies posted
Moderator

Hi @TaYa_4777276 ,

Yes, your understanding is correct. Whitelist feature is not implemented in the Ez serial FW. Can you please let us know your use case so that we can submit a feature request support to the development team?

Regards,
Bragadeesh
0 Likes