Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Potential issue in GATT processing using Windows LE explorer #107

Closed
lulf opened this issue Sep 5, 2024 · 2 comments · Fixed by #301
Closed

Potential issue in GATT processing using Windows LE explorer #107

lulf opened this issue Sep 5, 2024 · 2 comments · Fixed by #301

Comments

@lulf
Copy link
Member

lulf commented Sep 5, 2024

Using Windows LE explorer is with trouble + esp32 is reported to hang. See esp-rs/esp-hal#1971 (comment) for a packet capture. Attempt to reproduce with other HCI controllers as well to see if it's esp-specific.

@lulf lulf added this to the 0.1 milestone Sep 23, 2024
@lulf lulf removed this from the 0.1 milestone Nov 20, 2024
@timokroeger
Copy link
Contributor

I see the same problem trouble running on a nrf52 device.
Any tool using the WinRT bluetooth API gets stuck when trying to discover services (that includes the Web Bluetooth API in Edge browser).

Here are the defmt logs of my device:

[host] filter accept list size: 8
[host] setting txq to 1, fragmenting at 255
[host] configuring host buffers (8 packets of size 255)
[host] initialized
[host] enabling advertising
[ble] advertising, interval: Duration { ticks: 656 }
[host] connection with handle ConnHandle(0) established to BdAddr([58, 72, 9a, 70, 3b, 2c])
[link][poll_accept] connection handle ConnHandle(0) in role Peripheral accepted
[host] agreed att MTU of 251
... nothing happening anymore ...
[host] disconnection event on handle 0, reason: Remote User Terminated Connection

Using Web Bluetooth API with chrome on android everything works fine.

@timokroeger
Copy link
Contributor

Windows:
Image

Android:
Image

timokroeger added a commit to timokroeger/trouble that referenced this issue Feb 26, 2025
This incorrect field prevented the WinRT Bluetooth API to work with
TrouBLE devices. Fixes embassy-rs#107.
@lulf lulf closed this as completed in #301 Feb 26, 2025
@lulf lulf closed this as completed in 1b5b70b Feb 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants