Access Official Technical PDF

Share Summary:LinkedInEmail

Bluetooth diagnostics can be limited by a visibility gap between the operating system and the radio hardware. Host Controller Interface (HCI) logs show commands and events exchanged between a device’s host software and Bluetooth controller, but they do not necessarily reveal the lower-layer packets managed inside the controller or transmitted over the air. Research into Broadcom chip diagnostics demonstrated how certain off-the-shelf devices could provide an additional view of this activity, supporting protocol analysis without relying solely on a separate wireless sniffer.

For industrial automation engineers and system integrators, the distinction matters when evaluating Bluetooth-enabled equipment, investigating connection behavior or assessing firmware security. The diagnostic approach described here is specific to the Broadcom devices and software versions examined in the research; it is not a general capability of every Bluetooth product.

Why HCI logs do not tell the whole story

A Bluetooth system is divided between the host and the controller. The host runs the operating system’s Bluetooth stack and communicates with applications. The controller handles radio communication and lower-level connection management. HCI is the interface between these components, commonly carried over a serial connection such as UART.

Android’s BTSnoop logging, for example, captures HCI traffic. This can help trace host requests and controller responses, but it does not directly expose all Link Layer (LL) activity. In Classic Bluetooth, the Link Manager Protocol (LMP) handles link management; Bluetooth Low Energy (BLE) uses Link Layer Control Protocol (LCP) messages for related control functions. These exchanges are processed within the controller, beyond the view offered by ordinary HCI logs.

An external Bluetooth sniffer can capture packets over the air, but following a connection may require tracking its frequency-hopping sequence. Analyzing encrypted traffic can also depend on observing the initial pairing process. These requirements can make external capture difficult when an investigation begins after devices have already paired or when the setup is not available at the relevant time.

Bluetooth diagnostics for lower-layer analysis

Researchers investigating Broadcom firmware identified an undocumented diagnostic protocol within the Bluetooth controller. On supported devices, this interface could report lower-layer traffic from inside the chip, where the controller already has information about the connection and its protocol state. This changes the capture point: instead of reconstructing every detail from an external radio recording, an analyst can request diagnostic information from the controller itself.

The protocol supported several categories of diagnostic work, including:

  • Link Layer logging: capture sent and received LMP messages for Classic Bluetooth and LCP messages for BLE.
  • Connection statistics: retrieve transmission, reception and error information, including statistics for certain ACL connections.
  • Test functions: run supported tests and inspect basic completion information, such as transmitted and received test-packet counts.
  • Memory access: read or write selected memory locations and request a memory dump, subject to the diagnostic interface’s supported access types.

These capabilities serve different purposes. Packet traces help engineers inspect connection setup and control exchanges. Statistics can provide a summary of link activity without requiring continuous packet capture. Memory access is more specialized, helping firmware researchers observe changing values during debugging. It also carries greater risk: writing memory can alter controller behavior, so such operations should be confined to authorized, controlled testing.

What it takes to use the diagnostic interface

Finding a controller-side protocol is only part of the work. The host software must also allow diagnostic messages to pass between the operating system and controller. In the devices studied, the researchers modified Bluetooth drivers on selected Android versions and LineageOS to forward the additional message type. They then built a Wireshark dissector to interpret the diagnostic output in a readable form.

This integration illustrates a practical challenge for embedded analysis: protocol handling is often distributed across driver code, message formats and analysis tools. The Android versions examined did not all use the same architecture, and newer interfaces could make adding proprietary message types disruptive. Support observed on particular Broadcom-based phones, Raspberry Pi boards and evaluation hardware should not be assumed for other chipsets or software releases.

The diagnostic traces also required careful interpretation. Some fields were undocumented, and Broadcom’s reported packet lengths did not always match the length expected by existing protocol dissectors. Researchers had to identify those differences and adapt the decoding process. In other words, access to lower-layer data does not remove the need for protocol expertise; it gives analysts a different and potentially more direct source of evidence.

Security implications of inspecting Bluetooth firmware

Lower-layer visibility can help reveal implementation defects that host-level logs may miss. Using diagnostic access and packet injection on the examined Broadcom devices, the researchers identified two vulnerabilities associated with LMP handling. One involved insufficient opcode range checking in a vendor-specific handler; another involved the handling of an out-of-order encryption request during Secure Simple Pairing. The affected devices and firmware varied, and the findings should not be generalized to every Bluetooth implementation.

The broader engineering lesson is that conformance at the host interface does not guarantee robust handling inside controller firmware. Testing should consider how the controller parses and orders lower-layer messages, particularly when devices accept connections from nearby peers. The research also described a MAC-address-based filtering approach, while noting that filtering behavior could interact unexpectedly with a host Bluetooth stack. Protective changes therefore need testing across both controller and host behavior.

Practical takeaways for engineering teams

On-device Bluetooth diagnostics can complement HCI logs and external sniffers when investigating supported hardware. For teams working with connected sensors, peripherals or other Bluetooth-enabled equipment, the approach offers a way to examine controller-level exchanges and summarize radio-link activity in situations where conventional logs provide only a partial picture.

Before applying it, confirm that the device and firmware support the diagnostic interface, establish an authorized test environment, and account for driver changes and limitations in packet decoding. Treat memory writes and packet injection as active testing, not routine monitoring. Used with those controls, Bluetooth diagnostics can help make lower-layer behavior more observable—and provide a stronger basis for debugging, performance investigation and firmware security assessment.

Access Official Technical PDF

About The Author