You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mynewt.apache.org by GitBox <gi...@apache.org> on 2018/04/23 09:37:40 UTC

[GitHub] sjanc commented on issue #44: Extended Advertisement Issues

sjanc commented on issue #44: Extended Advertisement Issues
URL: https://github.com/apache/mynewt-nimble/issues/44#issuecomment-383515423
 
 
   Hi,
   
   There seems to be some misunderstanding about on how extended advertising scan works.
   
   BLE_HCI_EVT_BUF_SIZE defines HCI event size taken from pool, by definition it cannot be larger than 257 (which is probably best value if you have extended scan enabled). 
   
   When you do ext scan and remote is sending big data you'll get fragmented data from nimble and you need to take care of this in your application. This is to avoid caching in stack and keep it simple (at least for time being). data_status field will tell you if more data is expected to come (BLE_HCI_ADV_DATA_STATUS_COMPLETE, BLE_HCI_ADV_DATA_STATUS_INCOMPLETE, BLE_HCI_ADV_DATA_STATUS_TRUNCATED ).
   
   Also, depending on BLE_HCI_EVT_BUF_SIZE or advertiser implementation, you may get data fragmented in any way, so you should make no assumptions about this.
   
   Also, could you please confirm if original issues reported here are fixed?
   
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services