zephyr: STM32WB09 fails during Bluetooth connectivity
Describe the bug It seems all common Bluetooth samples fail during Connect stage on a vanilla NUCLEO-WB09KE board — both in peripheral and central roles. Advertising itself works, scanning as well.
To Reproduce
- Install zephyr-4.1 using the usual steps
west blobs fetch hal_stm32- Compile ie.
peripheral_htsample for boardnucleo_wb09ke/stm32wb09& flash - Use helper tool on iOS or Android or Mac (ie. LightBlue) to inspect BLE devices
- Find the Nucleo board advertising itself as
Zephyr Temperature Sensor - Click connect
Expected behavior Board can be connected to and service/peripherals can be inspected.
Experienced behavior Connection stalls on the helper app and never completes. Nucleo logs show “connected” and “disconnected” events shortly after.
Logs and console output
*** Booting Zephyr OS build v4.1.0 ***
[00:00:00.009,000] <inf> bt_hci_core: Identity: 02:80:E1:00:00:00 (public)
[00:00:00.009,000] <inf> bt_hci_core: HCI: version 5.4 (0x0d) revision 0x1064, manufacturer 0x0030
[00:00:00.009,000] <inf> bt_hci_core: LMP: version 5.4 (0x0d) subver 0x0000
Bluetooth initialized
no temperature device; using simulated data
Advertising successfully started
Connected
Disconnected, reason 0x08
(logs with DBG below)
Environment:
- OS: MacOS
- Toolchain: Zephyr SDK
- Version: both
4.1branch and recent (20Mar)1dd9308e2f784aa07bdc3cc00387c0a0c8b58dbe - Board: NUCLEO-WB09KE
About this issue
- Original URL
- State: open
- Created 2 years ago
- Comments: 15 (5 by maintainers)
Hello, approaching this again I couldn’t not replicate this on Pixel8a.
After some thinking, I think what was originally happening is that I had iOS or MacOS somehow trying to connect in the background which was causing my Pixel problems, I just didn’t notice it. I’m attaching a snif from Pixel 8a (which looks like correct behaviour to me).
Summing up, the issue is only about iOS/MacOS. Sorry for the confusion.
WB09-Pixel.zip