Ask questions and discuss STM32 wireless solutions and their implementation for running Bluetooth LE, Zigbee, LoRaWAN applications.
Most recent activity
Please go and visit our wiki pages where you can find a lot of information on our wireless product families (WB, WBA, WL) and the supported protocols: BLE, Zigbee, Thread, Matter, Lora, ... To begin your technical journey, please start from this top page: https://wiki.st.com/stm32mcu/wiki/Category:Connectivity This top page will guide you to the first steps to develop a wireless application using connectivity protocols on ST wireless microcontrollers. For BLE protocol, please visit: https://wiki.st.com/stm32mcu/wiki/Connectivity:Introduction_to_BLE_with_STM32https://wiki.st.com/stm32mcu/wiki/Connectivity:Introduction_to_Bluetooth_LE_Audio You can find information on BLE Certification, BLE Features, BLE Mesh, BLE Audio, … For Zigbee protocol, please visit: https://wiki.st.com/stm32mcu/wiki/Connectivity:Introduction_to_Zigbee You can find information on Zigbee certification, Zigbee Features, BLE-Zigbee concurrent mode, … For Tread protocol, please visit: https://wiki
Dear all, The X-CUBE-MATTER Expansion Package is now available on our official website following this link MATTER - Matter software expansion for STM32Cube - STMicroelectronics It is a reference implementation for the demonstration of Matter on STM32. It is ready for prototyping a Matter end-device on a reference development platform. Refer to STMicroelectronics Matter wiki articles at https://wiki.st.com/stm32mcu/wiki/Connectivity:Introduction_to_Matter to get started with matter for the supported STM32 platforms. Kind regards, Ouadi
Dear ST Support Team,I am developing an audio application for STM32WBA (Cortex-M33) using Keil MDK with Arm Compiler 6 (ArmClang).I currently have the following library:libPDMFilter_CM33_Keil_wc16.libHowever, my project requires the default 32-bit wchar_t configuration and cannot use the -fshort-wchar compiler option.Could you please provide the corresponding library:libPDMFilter_CM33_Keil_wc32.libAlternatively, is there an official source-code version of the PDMFilter library that can be compiled with ArmClang using the default 32-bit wchar_t configuration?Thank you for your assistance.Best regards
Hi,I have just noticed that the comments and documentation surrounding the `ViterbiEnable` value in `SHCI_C2_Ble_Init_Cmd_Packet_t` are not consistent.Both the comment in `SHCI_C2_Ble_Init_Cmd_Packet_t`’s declaration in `shci.h` and AN5289 indicate that 0 is enabled and 1 is disabled.However the comment in `app_conf.h` states the opposite 1 is enabled and 0 is disabled.Could this be clarified please? Best Regards,Graham
I’m using an STM32WB6MM-DK as a BLE sniffer and all works well until I try to “follow” a connection as described in https://wiki.st.com/stm32mcu/wiki/Connectivity:STM32_Sniffer_for_BLE_User_guide#Following_a_connectionAfter carefully following the instructions, I get nothing. When I try to paste the original 00:00:00:00:00:00 back into the target window and starting a capture, the window or save or not pops up and when I select discard, it seems to start, but no data is captured. On hitting stop, an error window pops up to the extent of “attempting to use a port that is not open.”Am I doing something wrong or have the Wireshark plugin scripts changed recently?
Hi, I am having some issues with concurrent peripheral connections when using the stm32wb5x_BLE_Stack_full_fw version 1.21.0.I created a minimal project using CubeMX according to STM32WB Bluetooth® LE - STM32CubeMX Application Conception, targeting an STM32WB5MM-DK board with the following modifications:Targeted to v1.20.0 repository. RFWKP clock set to HSE/1024. Added restarting advertising until 2 connections are established. Added advertising at the shortest connection interval of any existing connection (or default if there are no existing connections)The firmware for this is attached to this post.When running this on the STM32WB5MM-DK with stm32wb5x_BLE_Stack_full_fw version 1.20.0 I can successfully connect 2 central devices to it, however if I change the stack version to 1.21.0 the second central device connects and immediately disconnects.In both scenarios it is the same to central devices connecting.iOS device using BLEHero App (Connection interval 30mS, timeout 720mS) nRF Co
I want to upgrade the FUS (at the moment it is FUS version 1.2.0) to upload next version 2.2.0, the FTD thread stack. But when I upload the stm32wb5x_FUS_fw.bin with SMT32CubeProgrammer, I got the following eror: "Error: FUS_AUTH_TAG_CUST_NOTFOUND".
Hello,We use an STM32WB55VGY with STM32CubeWB v1.17.2 middleware and are investigating blocking in the command-response path.In hci_send_req(), each call to hci_cmd_resp_wait() is followed by draining HciCmdEventQueue. The function remains busy until a Command Status or Command Complete event reports Num_HCI_Command_Packets > 0.Could you clarify:Can CPU2 generate multiple Command Status/Command Complete events during one hci_send_req() call—for example, a response with zero command credits followed by an opcode-zero credit update? Can an opcode-zero credit notification arrive before the matching command response? If so, what prevents hci_send_req() from returning before receiving that response? Are there known issues or recommended updates concerning blocked HCI/SHCI response waits in this middleware version?Thank you.
Hello,I am working on a Zigbee application using an STM32WBA65.I am trying to make the attribute reporting configuration persistent.Persistence works correctly: when the device reconnects to the network, the values of attributes marked as persistent are successfully restored; however, this is not the case for the reporting configuration, which reverts to default values.I have not found an API that allows for the detection of changes to the reporting configuration.BRAnthony S.
PA level 28 is max.Hi!I’m using a custom made board for STM32WBA54 and the Direct test mode from CubeMX and CubeIDE (STM32Cube FW_WBA V1.10.0). We have tried to set the board in high power mode in CubeMx and in CubeRF change PA level but it does not work. Not sure what I’m doing wrong here?BRjohannes
Hello,I'm trying to test a Nucleo-WBA25CE1 by flashing BLE_HeartRate_ota onto it. I added code to turn on an LED in main.c and built the project. /* Infinite loop */ /* USER CODE BEGIN WHILE */ HAL_GPIO_WritePin(LD1_B_GPIO_Port, LD1_B_Pin, GPIO_PIN_RESET); HAL_GPIO_WritePin(LD2_G_GPIO_Port, LD2_G_Pin, GPIO_PIN_SET); HAL_GPIO_WritePin(LD3_R_GPIO_Port, LD3_R_Pin, GPIO_PIN_RESET); while (1) { /* USER CODE END WHILE */ MX_APPE_Process(); /* USER CODE BEGIN 3 */ }After performing a full chip erase, the LED lights up correctly when flashed via CubeIDE. However, when flashed via CubeProgrammer after a full chip erase, the LED doesn't light up at all. What causes this difference?Console message when flashing from IDE:STMicroelectronics ST-LINK GDB server. Version 7.14.0Copyright (c) 2026, STMicroelectronics. All rights reserved.Starting server with the following options: Persistent Mode : Disabled Logging Level : 1 Listen Port Numbe
Dear ST Engineers,In our previous project, we used the STM32WBA55CEU and currently have remaining stock of 2.2 µH and 10 nH inductors from that SMPS circuit.For our new product, we are using the STM32WB09KE. Looking at the EVK schematic, the design specifies a 10 µH main SMPS inductor and a 22 nH RF filter inductor. Since we still have stock of the older inductors, we would like to reuse them if possible.Could the team please advise if using the 2.2 µH and 10 nH inductors on the STM32WB09KE is acceptable, or if we must stick to the schematic's recommended values?Thank you very much!
I have the B-U585I-IOT02A board, i was able to successfully upgrade the FUS and stack software in the BLE controller, Serial Port Data The module shows the above information on the serial port. But i cannot see the module on the ST BLE Sensor application. How do i solve the issue?
Dear Team,I hope you are doing well.I am currently working with a Nucleo-WL55JC1 board running the LoRaWAN_AT_Slave application from the STM32WL v1.4.0 SDK.I have enabled both Context Management and Class B support in the lorawan_conf.h configuration file and successfully completed the following steps: Joined the LoRaWAN network. Configured the ping slot periodicity. Switched the device to Class B. Sent several uplink messages to the ChirpStack Network Server to notify it that the device had switched to Class B. After enabling the debug logs, I confirmed that: Beacon reception was working correctly. Ping slots were being opened as expected. Queued downlink messages were successfully received during the ping slots. However, I noticed an unexpected behavior after executing the AT+CS command, which returns NVM_CONTEXT_STORED.Following this command, beacon reception and ping slot activity stop appearing in the logs. They only resume after I send another uplink message.I have obse
Board: WeAct STM32WB55 Core Board (STM32WB55CGU6, 1MB flash)STM32CubeProgrammer: v2.23.0Connections tested: ST-LINK/V2 clone (SWD, mode=HOTPLUG) and native USB DFU bootloader (port=usb1, H3/BOOT0 held high to 3.3V)SUMMARYA wireless-stack upgrade (v1.20.0.2 -> v1.24.0 stack, which alsorequired a FUS upgrade from v1.1.1 to a newer FUS) was interruptedpartway through due to the target losing USB connection during thereconnect phase. Since then, the FUS no longer completes any realoperation (fwdelete, fwupgrade all fail with FUS_STATE_ERR_UNKNOWN)on either interface. FUS_GET_STATE itself gives a confirmed,repeatable, interface-dependent result -- see point 10 -- whichdoesn't correspond to operations actually working on either side.STARTING STATE (before anything went wrong)Read via USB bootloader, Read FUS infos: FUS State : FUS_IDLE FUS Status : FUS_NO_ERROR FUS Version : v1.1.1.0 STACK Version: v1.20.0.2 STACK Address: 0x80CE000WHAT WAS
Hello ST Community,I am designing an RF matching network for the STM32WLE5CCU6 (UFQFPN48) at 923 MHz, +22 dBm.In AN5457, I found PA output impedance data for 915 MHz (+22 dBm, UFQFPN48), but not for 923 MHz.I would like to ask: What is the recommended optimal PA load impedance at 923 MHz, +22 dBm for UFQFPN48? Can I use the 915 MHz impedance values for designing the 923 MHz matching network? Does ST provide reference matching component values for this configuration? Thank you for your support!
Hello, I am designing a circuit using the STM32WL3R with a single shared antenna for two transmit frequencies. My requirements are:- 315 MHz: TX output, low RF power (approximately -40 dBm)- 433 MHz: TX_HP output, high RF power (approximately +12 dBm)- One shared antenna- Separate matching networks for 315 MHz and 430 MHz I would like to avoid an external RF switch if possible. 1. Can both matching networks be permanently connected to the shared antenna feed point, while enabling only one PA path at a time?2. When TX is transmitting at 315 MHz, what is the RF impedance of the disabled TX_HP output? Can the TX_HP output and its matching network affect the 315 MHz matching? I would appreciate any recommendations regarding the RF topology and matching network design. Thanks.
When using deep stop mode on the stm32wb09ke, setting the wakeup source to PWR_WAKEUP_BLEHOST or PWR_WAKEUP_BLE causes a reset and reboot.
Hello Team, Please confirm are part numbers ST67W611M1A6BTR and STM32WBA5MMGH6TR compliance with standard EN 301 489 / EN 300 328 / EN 62311 or not? Please provide certification.
In AN2606 Rev 69, the STM32WBA6x system bootloader section describes the UART interface as USART3, but there appear to be errors:1. Inconsistency within the same entry:The TX pin description mixes USART2 and USART3 in the same sentence:USART3_TX pin Output PA12 pin: USART2 in transmission mode. Kept in reset configuration until 0x7F detected on USART_RX.While the RX pin description correctly uses USART3:USART3_RX pin Input PA11 pin: USART3 in reception mode. Used in alternate push-pull, pull-up mode.2. PA11/PA12 are assigned to USART2, not USART3:According to the STM32WBA62 datasheet, PA11 and PA12 are mapped to USART2 (USART2_RX / USART2_TX), not USART3.Question:Does the STM32WBA6x system bootloader actually use USART2 on PA11/PA12? It seems the document should read USART2 throughout, and the current "USART3" label is an error.Could ST please clarify and correct this in the next revision of AN2606?Environment:- Document: AN2606 Rev 69- MCU: STM32WBA62CGU6- Section: STM32WBA6x boo
I am trying to configure IEEE 802.15.4 packet sniffing on a NUCLEO-WB55 using STM32CubeMonitor-RF and Wireshark.I flashed the following firmware: Wireless coprocessor (M0+): stm32wb5x_Mac_802_15_4_fw.bin from STM32Cube_FW_WB_V1.24.0 Application (M4): Mac_802_15_4_Sniffer_Nucleo.bin from STM32CubeMonitor-RF IssueThe sniffer is detected successfully as a USB Virtual COM Port, and Wireshark recognizes it as an STM32CubeMonitor-RF 802.15.4 sniffer.However, no packets are captured, even when transmitting IEEE 802.15.4 frames from another STM32WB board.Troubleshooting Performed Tested both USB and ST-LINK/SWD connections. Verified USB device and serial port detection. Verified Python, PySerial, and Wireshark compatibility. Confirmed Wireshark recognizes the sniffer interface through extcap. Tested direct capture using stm32cubeMonRf_sniffer.py. Tested capturing through Wireshark and STM32CubeMonitor-RF. Configured matching IEEE 802.15.4 channels. Verified that the transmitter
I am using custom board that only has STM32WBA65CIU6 and IIS3DWB. I am using STM32CubeIDE v2.2.0, STM32CubeMX v6.18.1, and STM32Cube FW_WBA V1.10.0.I generated a project from CubeMX with the default configurations without changing or enabling anything except1) Enable ICACHE 2-way2) Enable HSE and LSE, use SMPS and turn off prefetch3) Enable SRAM1 and SRAM2to match the conditions mentioned in the datasheet for the current charactersticsI tried in an empty code, just the generated initialization from CubeMx and empty while(1)1) Using HSE + PLL to have 100MHz HCLK and read 3.39 mA which is fine2) Using HSE only to have 32MHz HCLK and read 2.27 mA which is above the 1.7 mA3) Using HSI only to have 16MHz HCLK and read 1.53 mA which is above the 0.46 mAWhen I try entering any low power mode, I read 0.87 mA which is much higher than expected.I tried disabling the RAMs and the ICACHE, disabling the HSE and the LSE, set ULPMEN to 1 and leave it, and other many cases and still get the same 0.87
Here’s the situation. The system is built on the STM32WB5MM with basic code written using FreeRTOS. All works well, so now I add the BLE HeartRate application. If I prevent my code from running using a while (1) [ osDelay(10); } loop, the STM BLE Toolbox on my Android phone works fine displaying data. However, if I allow my code to run, the Toolbox connects, but no data is displayed. Pursuing this in my code, I determined that the wake-up interrupts were not occurring as they should.By moving where I stop my code, I have narrowed it down to the following sequence:HAL_PWR_EnableBkUpAccess();HAL_RTCEx_BKUPWrite(&hrtc, RTC_BKP_DR19, Value);HAL_PWR_DisableBkUpAccess();If I simply comment out the last line allowing backup access to remain on. It also works. However, that leaves the backup registers vulnerable. (Note: I use this sequence frequently to protect data that must be retained through a power cycle. VBAT is provided by a coin cell. So, a general solution is preferable.)This is t
Hi,I’m running a LoRaWAN end node on the B-WL5M-SUBG1 (MB1779B), based on the LoRaWAN_End_Node_LBM example from CubeWL 1.6.0. The board is powered from a 3.6 V battery on CN5 (E3V3). SB14 is removed and the STMod+ adapter and debugger are disconnected.In Stop2 I measure about 2 µA on JP2, so the module itself is fine. But on CN5 the whole board still draws around 80 µA.What I’ve done so far: PA3 pull-up and PA15 pull-down (from this thread), all unused pins incl. SWD/UART set to analog, RF switch pins PC3–5 low during sleep, SPI flash in deep power-down, and all four sensors put into power-down over I2C at boot. Opening SB15 made it worse (~600 µA), I guess because the sensors get back-powered through the I2C pull-ups.Is ~80 µA expected for this board on E3V3? Which parts are still powered from 3V3?Thanks!
I built up an application using STM32CubeMX and FreeRTOS but left BLE disabled. Now, I want to add that connectivity.I went back into CubeMX and turned on BLE with the HeartRate application. The only thing I changed were ASYNC_PRESALER and SYNC_PRESCALER so that the RTC time keeping would be correct.Now, whenever I allow appe_TI_Init() to execute, I get an IPCC_C1_RX_IT interrupt (VECTACTIVE = 0x3C) as soon as osKernelStart() is called. If I comment out the call to appe_TI_Init(), the rest of the code operates as before. Yes, I know that BLE is not running.What have I missed that causes the interrupt when it is not handled?Thanks
WATCH ON-DEMAND | STM32 Summit 2026
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.