STM32 MCUs Wireless

We have a custom `STM32WL33CCV6` (`VFQFPN32`) board that should reach about `4 µA` in Deepstop, similar to the NUCLEO-WL33, but instead it drops only to roughly `450–500 µA` and appears to restart on Deepstop entry. `NRST` does not glitch low, and the behavior is unchanged with only `3.3V` and `GND` connected. We also tested direct `HAL_PWR_EnterDEEPSTOPMode()` with wake sources disabled, and it still appears to reboot rather than stay in Deepstop. We reviewed ST errata `ES0612` and applied the documented `VFQFPN32` workaround from section `2.2.9` for nonbonded GPIOs causing increased Run-mode current by forcing the listed nonbonded pins to pulldown at startup. That workaround had no effect on the Deepstop issue. The custom board’s `VFBSD / VLXSD / VDDSD / VDDRF` schematic and BOM appear close to the ST reference, so we are asking whether there are known WL33 low-power / SMPS / Deepstop pitfalls beyond errata `2.2.9` that could explain a persistent `~500 µA` floor or an appar

I am currently working with the LoRa-E5 Mini module based on the STM32WLE5JC microcontroller, and I am using STM32CubeIDE version 2.1.0 for development. I have successfully tested basic GPIO functionality (LED blinking), and I am now trying to implement LoRa-based communication (transmission and reception) using the integrated SubGHz radio. However, I am facing challenges in properly configuring and utilizing the SubGHz_Phy middleware and radio drivers within STM32CubeIDE. Specifically, I need guidance on the following: The correct procedure to enable and configure the SubGHz radio peripheral in STM32CubeIDE for STM32WLE5JC. How to properly include and use the SubGHz_Phy middleware for basic LoRa communication. Availability of any official example projects (such as Ping-Pong or Tx/Rx) compatible with STM32CubeIDE 2.1.0 for the LoRa-E5 Mini module. Proper conf

Board / SoCBoard: NUCLEO-WB09KESoC: STM32WB09SoftwareZephyr version: v4.4.0-rc2-41-g149c8b1758a8Toolchain / build system: West + Zephyr standard build flowIssue summaryWhen building a very small Zephyr application for NUCLEO-WB09KE, simply enabling:CONFIG_BT=ycan cause intermittent boot failure.The failure happens very early in boot:no UART outputno boot bannerno application printk()main() appears to never run in failed bootsThis happens even when the application does not call any Bluetooth API.

Ok, a tricky one.  So for services and attributes it's documented that there is 10752 bytes, each service takes up 48 bytes, each attribute 40 bytes, and if you got th number of services and attributes you can compute backwards  BLE_ATT_VALUE_ARRAY_SIZE (after you mapped all characteristics to actual attributes), given the upper limit. Easy enough. (GATT_DB_Size_SRAM_NVM.xlsx) My problem is now BLE_MBLOCK_COUNT. There is this macro:#define BLE_TOTAL_BUFFER_SIZE(n_link, mblocks_count) \ (16 + BLE_FIXED_BUFFER_SIZE_BYTES + \ (BLE_PER_LINK_SIZE_BYTES * (n_link)) + \ ((BLE_MEM_BLOCK_SIZE + 8) * (mblocks_count)))What is the limit for BLE_TOTAL_BUFFER_SIZE ? If that

Hi everyone,I am experiencing a very specific initialization issue with a custom board based on the STM32WB55RGV6.We recently manufactured a batch of 30 boards. 22 of them are working flawlessly, but 8 boards fail to start the BLE radio on a cold boot (Power-On Reset). They all run the exact same firmware and have the exact same layout.Hardware details:MCU: STM32WB55RGV6HSE: 32 MHz crystal (CS06410-32M)LSE: 32.768 kHz crystalRF: MLPF-WB55-01E3 filter + Ceramic AntennaSymptoms & Debugging Steps Taken:No RF Output: Using an SDR and Near Field Probes, I confirmed there is zero RF energy being transmitted on the 2.4 GHz band during a cold boot on the faulty boards.HSE is Alive:

Hello,I have designed a custom board with stm32wb55. I used the reference schematic and checked everything but I cannot program the board from my cubeide. I have tried different configuration settings in Cube IDE but always got "No device on target" error. I connecte SWDIO, SWCLK, GND and NRST pin to my stlink. These did not work so I tried different configurations with OpenOCD too but they also failed with these symptomsSymptoms (Multiple attempts with OpenOCD at 100 kHz):SWD-DP responds reliably: chip identified as Cortex-M4 r0p1Examination usually succeeds: shows correct breakpoint and watchpoint countsHalt always fails with "Fail reading CTRL/STAT register" → "Not halted"Roughly 1 in 4 attempts fail to even initialize, but when init succeeds, halt always failsManual NRST-to-GND-then-release tried, same resultAlready reflowed the WB55 once with gel flux, no c

Dear ST team.   I am testing UART of NUCLEO-WB09KE with the board [STM32WB09 Nucleo-64 board (MB1801 and MB2032)] I Set UART1 PIN PB4, PB4 with the source attached[100ms period tx send ]. I am checking CN3(23), CN4(35) but no signal shown. Is there anythn

Hello,I am currently working with the STM32WBA65RI for BLE Direction Finding using connectionless mode. I would like to know if it is possible to use a low-power mode such as Standby with RTC, allowing the board to consume only a few nanoamps, then wake up periodically via the RTC, perform advertising for a defined period, and return to Standby mode.Could anyone provide guidance or share experience with this approach?Best regards.

I am struggling with the keys in the new V1.5.0 LBM stack. Keys are read from NFC EEPROM and device is joining. After joining, I expect the stack to save the join and session keys in secure memory so the keys are deleted in EEPROM for security. After reset, the device does not join. How must this be handled.

Hello. I'm working on a BLE  application that uses an STM WBA55 board and ThreadX. It was based on the St Threadx p2pServer example, The Sequencer is disabled. I'm using stmCubeIDE 1.19 and st_fw1.7 and i cannot migrate to new versions due to compatibility reasons.The main idea for the application is that the board initializes, advertizes 10-20 seconds for a connection, connects to a device like a phone pc, gets data from a sensor and transfers the data to the connected device. If no connection occurs or if the device is disconnected it should go into sleep/stop/standby mode until an EXTI interrupt from the user button is triggered. As of now the application is structured as follows:-- A main thread is in charge of initializing the rest of the threads (one thread for each type of sensor eg temp adc etc) and handle events like ble connection/disconnection and sleep/wake up requests.--Upon a sleep request a flag is set into an

Dear Sir or Madam,  We would like to use NUCLEO-WL33CC2 to verify DMR RSSI reliable detection(compulsory requirement) and demodulation(optional requirement).  We only need rx chain for scanning purpose.  As per ETSI TS 102 361-1, DMR TDMA frame has sync word in the middle of 30ms frame and does not have preamble. And in Chapter 10.2.2.2 (Physical layer), an RRC filter is designed for 4FSK.  It seems these settings may not have corresponding option in STMWiseCube, so that we would like double check with you if there is any better setting for detect 30ms packet RSSI at least.  We do know the sync word content for DMR, which is 48 bit long. The modulation is 4FSK, nomial channel width is 12.5kHz, and data rate is 9.6kbps. And deviation is +/-0.648kHz and +/- 1.944kHz for 4FSK, shall we use 1.944kHz in the setting of deviation in STMWiseCube?   Our requirement is RSSI at room temperature for this TDMA fra

When using a Zephyr RTOS host with PAwR synchronization response enabled, the STM32WB09 controller (observer role) reports a legacy LE Periodic Advertising Report (subevent 0x0F) while syncing to a PAwR broadcaster.The broadcaster is implemented on EFR32BG42 (SiLabs). Zephyr host reports:[00:00:02.987,453] <dbg> bt_hci_core: hci_event: event 0x3e[00:00:02.987,480] <dbg> bt_hci_core: hci_le_meta_event: subevent 0x0f[00:00:02.987,497] <err> bt_scan: The controller shall raise the latest unmasked version of the eventWhich corresponds to:LE Meta EventLE Periodic Advertising Report (legacy) The Zephyr BLE controller layer is based on stm32wb0x_ble_stack_controller_only.aDoes stm32wb0x_ble_stack_controller_only.a support:BLE 5.4 PAwR (Period

Hello, I’m working on a low-power BLE peripheral design on an STM32WBA63 and I’ve hit a timing issue that I’m hoping someone can help me with.Hardware / softwareMCU: STM32WBA63CIUxSTM32CubeMX: 6.15.0Firmware package: STM32Cube FW_WBA V1.7.0Wireless stack: STM32_WPAN (BLE)RTOS: FreeRTOS 1.3.1 with tickless idle enabledLow power mode: STOP1 (not standby/off)BLE role: peripheral advertisingAdvertising interval: ADV_INTERVAL_MIN = 0x0640 (

Split from STM32WB05KNV6TR missing in STM32CubeIDE 2.0.0 Target Selector - this is a new questionHi Ghofrane,Thank you for the explanation. Since the WB05xN acts as a network coprocessor, it doesn't fit my current design goals as I want to avoid using an external Host MCU to keep the BOM cost and PCB footprint at a minimum.I am looking for a standalone (single-chip) STM32 wireless solution. My requirements are:Standalone Operation: The application and BLE stack must run on the same chip.Eddystone Support: It must be capable of broadcasting in Eddystone format.FOTA (Firmware Over-the-Air): The chip must support wireless firmware updates.

I have a STM32WB05TZF6TR. All VCCs are running off 1.8V. I'm trying to use PA8 and PB5 with 3.3V 10k pullups. But the signals are being clamped at 2.5V. I had expected this not to happen, as they are supposed to be 5V tolerant. Does anyone know what's happening here? There's nothing connected to the pins besides the pullups. I have a bare STM32CubeMX project, with just this GPIO init:void MX_GPIO_Init(void){ GPIO_InitTypeDef GPIO_InitStruct = {0}; /* GPIO Ports Clock Enable */ __HAL_RCC_GPIOB_CLK_ENABLE(); __HAL_RCC_GPIOA_CLK_ENABLE(); /*Configure GPIO pin : PB5 */ GPIO_InitStruct.Pin = GPIO_PIN_5; GPIO_InitStruct.Mode = GPIO_MODE_INPUT; GPIO_InitStruct.Pull = GPIO_NOPULL; HAL_GPIO_Init(GPIOB, &GPIO_InitStruct); /*Configure GPIO pin : PA8 */ GPIO_InitStruct.Pin = GPIO_PIN_8; GPIO_InitStruct.Mode = GPIO_MODE_INPUT; GPIO_InitStruct.Pull = GPIO_NOPULL; HAL_GPIO_Init(GPIOA, &amp

I am using the NUCLEO-WL33CC1 (for 868 MHz freq) and I tried the LPAWUR feature based on the Github examples that you provided:https://github.com/STMicroelectronics/STM32CubeWL3/tree/main/Projects/NUCLEO-WL33CC/Demonstrations/LPAWUR/LPAWUR_WakeupRadio_Rxhttps://github.com/STMicroelectronics/STM32CubeWL3/tree/main/Projects/NUCLEO-WL33CC/Demonstrations/MRSUBG/MRSUBG_WakeupRadio_Tx The issue is that the range that I get is a max of 3 meters, no more that this. I already soldered the C3 capacitor, that is by default missing, with a valu

Hi,We are currently developing a solution based on the STM32WBA65RIV6 MCU, and we would like the internal RTC to remain active while the MCU is powered down.We assume that this is possible, and we would like to clarify the following points:For how long does the RTC retain its values after the MCU is powered down (by default)?Is it possible to connect a backup capacitor or battery to supply only the RTC or part of the MCU in order to extend the retention time?We also want to know if there is any documentation available on this topic. We have not been able to find detailed information.Thank you in advance.Best regards,Luis

Hi,I am working with the STM32WB5MMGH6TR and would like to achieve the following:Stream GATT data to a mobile phoneSimultaneously play simple audio to BLE earbudsThe audio requirement is modest: a tone that rises and falls in a sine-wave pattern (no music, no complex audio, no high-quality audio). The frequency should sweep between 500 Hz and 2 kHz, with a modulation rate of up to 60 Hz.Is this feasible using the standard ST BLE stack for the STM32WB5MMGH6TR? The key requirement is that both operations run concurrently.If it is possible, could you please outline the recommended approach?Thank you as always.

Hello,My end node activation mode is OTAA, and is supposed to enter shutdown mode and wake up after a specified period of time period, in order to save power, the end node should skip joining the network at every wake up. I was able to skip the joining process by switching the activation mode from OTAA to ABP after the first join process, but after that, the server did not receive every packet sent from the end node like it used to when i was working with OTAA I doubt this is a good solution since a lot of packets are lostMy questions are:1) What do you think of my solution? is it missing something?2) What are my options if I want to stick to OTAA while skipping the joining process?3) Should I just go with ABP?

Can force a specific DR for LoRaWAN?I tried using: uint8_t custom_dr[7] = {0};custom_dr[3] = 1;lorawan_api_dr_strategy_set(USER_DR_DISTRIBUTION, STACK_ID);lorawan_api_dr_custom_set(custom_dr, STACK_ID);   but did not work.

Hello,I am trying to port the official BLE_Ota example from STM32CubeWB (WB55 project) to an STM32WB30 device, but I am facing multiple compilation issues after importing the project into STM32CubeIDE.After configuring STM32_WPAN and generating the project for STM32WB30, I get many errors such as:RTC_HandleTypeDef unknown typeIPCC undeclaredFLASH_ECCR_* undeclaredSCB_* undeclaredLL_* functions not declaredHAL and LL drivers missing or inconsistentIt seems like the project is not correctly recognizing the STM32WB30 device definition, and many peripherals (RTC, IPCC, FLASH, RCC) are not properly included or enabled.I already tried:Adding STM32WB30xx define in the compiler preprocessorEnabling STM32_WPAN middleware (BLE stack full mode)Checking stm32wbxx_hal_conf.hHowever, the issues persist and the project still behaves as if it is partially configured for STM32WB55.My questions are:

Hi, I'm working on a ESL project using STM32WB09. In order to reach greater distances, is it possible to use the CODED PHY ? Thank you

Hello,I'm designing a 2 layer PCB using STM32WL for LoRa operations at 433MHz and need a review of my RF layout. The board is JLCPCB 2 layer standard FR4, 1.6mm thick 1.46mm core, 1oz copper, 50Ω microstrip at ~2.8mm width, about 38mm long. I have placeholder caps/inductor to be populated after board fabrication. I am seeking expert opinion for:Trace width & impedance - does 2.8mm yield 50ohm given FR4, 1oz copper, and 1.46mm dielectric height?Critical length - Are there implications for 38mm length on transmission-line behavior?Taper - Taper starts 5mm in. Are there optimal lengths for tapers? Should I taper for shunt pads?Stitching vias - Recommendations for via spacing for this trace width? Every 5-8mm?Test points - Recommendations for RF test points without effecting impedance?Any other best practices or tips would be helpful. I thank you for any guidance.Best, John

Hi everyone,I’m working on a 4-layer PCB design using the STM32WL (based on the Nucleo WL55JC reference design).For the RF section, I followed the same layout approach as the Nucleo board, including the layer stack-up and RF trace widths.The only difference in my design is that I have some GPIO signals routed close to the RF section. These signals are routed on the 3rd layer, while I am still maintaining solid ground planes on the 2nd and 3rd layers underneath the RF section.I would like to clarify:Is it acceptable to route non-RF signals on the 3rd layer near the RF section if solid ground planes are maintained?Are there any risks (e.g., noise coupling or RF performance degradation) with this approach?Additionally, if I modify the layer stack-up:What parameters need to be adjusted (e.g., RF trace width, impedance matching, ground reference)?Are there any recommended guidelines for maintaining RF perf

The product page and datasheet only mention BLE Core 6.0 but don't call out channel sounding support explicitly like other BLE features. Is it actually supported?