Replies: 1 comment 3 replies
-
|
The major problem is that we didn't 1:1 simulate the physical and link layers. Link-layer spec of Bluetooth is quite complicated, so we made some trade-off to simplify the emulator implementation, but such changes cannot be applied to log based on the standard spec, or they cannot be properly parsed by viewers. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Motivation
Currently, Bumble provides a powerful software-based Bluetooth stack with support for virtual controllers, link simulation, and rich debugging logs (including LL PDUs and HCI events).
However, there is no built-in way to export traces in a format that can be opened by external Bluetooth protocol analyzers such as Ellisys Bluetooth Analyzer.
In contrast, simulation frameworks such as BabbleSim (bbsim) are able to export traces compatible with Ellisys tools, which is extremely useful for:
Proposal
Add a trace exporter module to Bumble that can output captured link-layer and HCI activity into an Ellisys-compatible trace format (or an intermediate format that can be converted).
The exporter should:
Beta Was this translation helpful? Give feedback.
All reactions