This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

HCI_EXT_AdvEventNoticeCmd Questions

Other Parts Discussed in Thread: CC2640, CC2650

Regarding CC2640/CC2650 BLE HCI Vendor Specific command HCI_EXT_AdvEventNoticeCmd. As I understand it, this command allows generation of a user event when an advertiser's broadcast event has finished.

1) How many packets does this imply have been transmitted from the start of an advertisement to when the user event is generated? Just 1? Or 3 corresponding to the 3 advertisement frequencies? Or is it an interval based measurement?

2) Does this HCI command work for scanners/listeners as well.. e.g. once a scanner receives an advertisement packet, it generates a user event?

3) If the answer to 2 is no, is it possible to create custom HCI command to do this? Any tips on how this is accomplished? Do custom HCI commands have any limitations to their abilities (e.g. could i potentially create an HCI command to generate a user event via the sync packet like RATGPO1 or the packet received interrupt RX_DONE?)

thanks

  • Hi,
    1)This API generates an event for each ADV event. An ADV event can consist of all three frequencies if enabled, it should generate one event for all three frequencies.

    2) There is a different callback when scanning. See GAP_DEVICE_INFO_EVENT in simpleBLECentral.c which is callback event each time an ADV packet is received.
  • Thanks this is very helpful. If you don't mind, can you expand upon custom HCI commands a bit? I've seen them referenced on the forum but unsure what exactly they are capable of. Do they allow you to setup a command to write to the radio's CMDR register for example? Are there any good code examples of what's possible?
  • The vendor specific HCI commands are additional commands supported by our device in addition to the commands used for BLE operation defined by the BT SIG(group that define the BT standard). These vendor specific usually consist of device testing commands such as packet error rates and setting device specific RF output configurations such as setting TX power and setting the MAC address.
  • Thanks Zahid but I was more curious of the custom HCI commands that I've seen mentioned here. This forum post is an example of what I mean: e2e.ti.com/.../398315