Extended connectable Advertising and Scan Response Data Setup Failed

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

Extended connectable Advertising and Scan Response Data Setup Failed

ソリューションへジャンプ
3,624件の閲覧回数
nidhintomy
Contributor IV

I am using 'frdmkw38_adv_ext_peripheral_bm' example.

I tried to add scanresponse data in connectable advertising. But returns 'gAdvertisingCommandFailed_c'.

How to implement scan response data with connectable advertising in extended advertising feature ?

Best Regards,                                                                                                                                                 Nidhin

ラベル(2)
タグ(2)
0 件の賞賛
返信
1 解決策
3,586件の閲覧回数
EduardoZamora
NXP TechSupport
NXP TechSupport

Hello,

Your understanding is correct. According to the Bluetooth 5.0 Specification, advertising cannot be scannable and connectable at the same time for this type of advertisement.

EduardoZamora_0-1667238794182.png

Regards,
Eduardo.

 

元の投稿で解決策を見る

0 件の賞賛
返信
4 返答(返信)
3,611件の閲覧回数
EduardoZamora
NXP TechSupport
NXP TechSupport

Hello,

gAdvertisingCommandFailed_c event is received when advertising could not be enabled or disabled. Reason should be contained in gapAdvertisingEvent_t.eventData.failReason.

Also, please take a look at the Bluetooth Low Energy Demo Application User's Guide, section 5.15 Extended Advertising Peripheral and Extended Advertising Central; and Bluetooth Low Energy Application Developer's Guide, section 4.2.1 Advertising (Peripheral setup). You can find these documents inside the KW38 SDK doc folder > docs > wireless > Bluetooth.

Regards,
Eduardo.

0 件の賞賛
返信
3,606件の閲覧回数
nidhintomy
Contributor IV

Hi @EduardoZamora 

I think i found the answer.

 

 

 

bleResult_t Gap_SetExtAdvertisingData
(
uint8_t handle,
gapAdvertisingData_t* pAdvertisingData,
gapScanResponseData_t* pScanResponseData
);

 

 

 

Either of the pAdvertisingData or pScanResponseData parameters can be NULL, but not both. For extended advertising (BIT4 = 0) only one must be different than NULL – the scannable advertising bit (BIT1) indicates whether pAdvertisingData (BIT1 = 0) or pScanResponseData (BIT1 = 1) is accepted. The total amount of Advertising Data shall not exceed 1650 bytes.
Application should wait for a gExtAdvertisingDataSetupComplete_c event in the Generic Callback.

So it is either connectable advertising or scannable advertising.

Also from BLE SIG V5.3 Doc i found this->

Screenshot (69).png

So What i understand is we can't use both connectable and scannable in BLE Extended advertising.

Could you please confirm this ?

 

Best Regards,

Nidhin

 

0 件の賞賛
返信
3,587件の閲覧回数
EduardoZamora
NXP TechSupport
NXP TechSupport

Hello,

Your understanding is correct. According to the Bluetooth 5.0 Specification, advertising cannot be scannable and connectable at the same time for this type of advertisement.

EduardoZamora_0-1667238794182.png

Regards,
Eduardo.

 

0 件の賞賛
返信
3,576件の閲覧回数
nidhintomy
Contributor IV

Hi @EduardoZamora 

Thanks for confirming.

 

Best Regards,

Nidhin

 

0 件の賞賛
返信