You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello guys. Thanks for your awesome job done here in implementing BLE satck in Rust.
Looks like I found an issue with the scan feature.
Some advertisment packets (LeAdvReport) are losing the last byte and previous one sometimes is corrupted in the .data on read. I haven't found any pattern when this happens, except if you build the code with cargo build ... --release and without it. And even with --release flag sometimes it doesn't work well, but for other Adv packet payloads
I am not quite sure that this bug is in embassy-rs/trouble or in the embassy-rs/bt-hci project.
Description
Hello guys. Thanks for your awesome job done here in implementing BLE satck in Rust.
Looks like I found an issue with the scan feature.
Some advertisment packets (
LeAdvReport
) are losing the last byte and previous one sometimes is corrupted in the.data
on read. I haven't found any pattern when this happens, except if you build the code withcargo build ... --release
and without it. And even with--release
flag sometimes it doesn't work well, but for other Adv packet payloadsI am not quite sure that this bug is in
embassy-rs/trouble
or in theembassy-rs/bt-hci
project.Example log without
--release
flag:Example log with
--release
flag:As you can see we lost
0
at the end and the49
became4B
Platofrm details
How to reproduce
Cargo.toml
src/bin/rpi_ble_scan_bug.rs
The text was updated successfully, but these errors were encountered: