toggle quoted messageShow quoted text
Take a look at hci_core.c on how host uses the feature exchange to determine supported Bluetooth features.
Version exchange only helps in identifying a vendor/company and revision of their firmware. And useful to have/handle blacklisting/workaround application behaviors.
I would use HCI command to fetch remote version information. By spec, version exchange to be done only once and to be cached for a peer device. It is best handled by host issuing hci cmd and not have controller do it automatically.
On 18-Jul-2019, at 6:19 PM, Megan Bredes <mbredes@...
Well the current goal is to get the version exchange procedure to happen at all, but the end goal is to get it to happen twice so that I can verify that the peripheral that I am talking to responds correctly. I am trying to use zephyr to verify that a peripheral meets a number of bluetooth spec requirements.
The Version Exchange procedure is a Link Layer one performed automatically by the LL.
What are you trying to achieve exactly?
I have recently started experimenting with Zephyr and have been trying to alter one of the demo's (HR monitor central side) so that it would go through the version exchange procedure. I have found the code that seems like it would do this
(ctrl.c:event_vex_prep) but I have been unable to figure out how to get this function to be called. Does anyone have any suggestions on where I should be looking to adjust the code to make this happen?
This email and its attachments contain confidential
and/or privileged information of Sunrise Labs
and/or its clients. Any use of this information,
other than by the intended recipients, is prohibited.
If you have received this email in error,
please notify Sunrise Labs, Inc. about the error at
ITStaff@... and delete this message and all copies thereof.