STM32 MCUs Wireless

I have the nucleo board connected to the STLINK-V3PWR via JP2 and ground connections. Flashed onto the device I have a mioty evaluation stack from LZE. I am taking readings of the current drawn and getting a consistent value of 3mA. I was trying to evaluate the deepstop current so wanted to know if the fact is that I have got my measurements/ connections wrong or that the firmware is preventing me from entering the mode. 

I have designed a custom board. I have connected SWCLK to PA3 and SWDIO to PA12. I found I can not connect. So I made a patch and connected SWDIO to PA2 which seems to be default after boot. Now I can connect to the board. However after downloading my software the board becomes unaccessible. The code is running fine on a NUCLEO-WL33CC1 board.I can not access the board with CubeProgrammer either. It is like bricked.I found one issue with LSE which I have connected to PB14 and PB15 instead of PB12 and PB13. So I changed my code disabled LSE and enabled LSI and tested this on a new board. Initially I can connect but as soon as I try to singlestep through the code contact is lost and after that the board is no longer accesable in CubeProgrammer either.I am running out of boards if I can not find a way to unbrick them. ​@STTwo-32 

Hi!i made a custom PCB with the STM32WB1MMC. But Ii’m getting hardly 2 or 3 meters range.Seems to be the same issue as  but my device is right on the edge of the PCB.My antenna keep put zone is a bit narrower than the reference board. Apart from this I not able to see what else could be wrong. Any pointers would be much appreciated. Thanks!

Are there any single MCU + LoRa 2.4 GHz ICs in the world?

HI，   I am using stm32wba65i_dk1 board to develop my ble audio application.  I choose zephyr as my software platform and tmap as ble audio profile. However, when the TMAP application initiates advertising, the Pixel 9 cannot detect the device name broadcast by the TMAP peripheral. I also captured over-the-air packets using the professional BLE sniffer X240, which confirmed that no BLE advertising packets were transmitted from the STM32WBA65I_DK1 board.I enabled logging for all HCI commands sent by the HCI Core and all received HCI events, yet no obvious anomalies were observed in the HCI logs. I am unable to identify the root cause of this issue. # 1. LE Set Extended Advertising Parameters [v1]Send Command:[00:00:03.106,000] <dbg> bt_hci_core: bt_hci_cmd_send_sync: buf 0x20010c18 opcode 0x2036 len 25[00:00:03.110,000] <dbg> bt_hci_core: bt_hci_cmd_send_sync: cmd params 00 01 00 20 00 00 30 00 00 07 01 00 00 00 00 00

Hi, I’m looking into the WL55JC1 for a project which would require the system to remain dormant (ideally standby) for weeks, maybe months and then resume operation on a set date at a set time. I would like to use LSI as power and space will be very limited.So far I’ve discovered, that of course there is an RTC and it has alarms that can be used to wake from standby mode. However all examples and documentation I can find only ever use times or maybe day-of-week or day-of-month as the set wake up time. Never a full date and time. Looking at the code, stm32wlxx_hal_rtc.h defines a struct RTC_AlarmTypeDef with fields for seconds, minutes, hours and either a day-of-month, or day-of-week.Is it really not possible to give the system a full a date and time yyyy-mm-dd and hh-mm to wake up at? Will I need to build workaround waking up at least once a month to recalculate the next wake-up until the actual target time is within the same calendar month?Or am I overlooking something?I’d appreciate a

Hi ST Team,I am trying to enable Bluetooth LE Privacy (Resolvable Private Address) on an STM32WB55CG.EnvironmentMCU: STM32WB55CG STM32CubeWB Package: v1.23.0 BLE Stack: v1.23.0.3 FUS: v1.2.0.0What I changedI changed the address type from: #define CFG_BLE_ADDRESS_TYPE PUBLIC_ADDRto #define CFG_BLE_ADDRESS_TYPE RESOLVABLE_PRIVATE_ADDRThe generated code calls: aci_gap_init( role, 2, ...);and aci_gap_set_discoverable( ... RESOLVABLE_PRIVATE_ADDR, ...);Initially, aci_gap_set_authentication_requirement() was also using CFG_BLE_ADDRESS_TYPE as the Identity Address Type. I found an ST forum discussion mentioning this is incorrect, so I changed it to: aci_gap_set_authentication_requirement( ... PUBLIC_ADDR);However, the behavior did not change.Observed behaviorWith CFG_BLE_ADDRESS_TYPE = PUBLIC_ADDRPairing succeeds. Device works normally.With CFG_BLE_ADDRESS_TYPE = RESOLVABLE_PRIVATE_ADDRConnection is established. Pairing fails. ACI_GAP_PAIRING_COMPLETE_VSEVT_CODE

NUCLEOWB55RG I set I2C3 in MX. I have 2 x temp sensors & 2 x accelerometers in the bus./* Snippets of code to show how I2C3 is set up & used */#include "main.h"#include "adt7410.h"#include "adxl345.h"I2C_HandleTypeDef hi2c3;ADT7410 temp_0;ADT7410 temp_1;ADXL345 acc_0;ADXL345 acc_1;static void MX_GPIO_Init(void);static void MX_I2C3_Init(void);int main(void){ HAL_Init(); MX_GPIO_Init(); MX_I2C3_Init(); /* ADT7410 set up */ /* temp_0 at 0x48 * temp_1 at 0x49 */ temp_0.adti2c = &hi2c3; // I2C Handler ADT7410_Init(&temp_0, 0x48); // I2C address depends of A0 and A1 pins ADT7410_Reset(&temp_0); // Optional ADT7410_SetResolution(&temp_0, ADT7410_16BITS); // Put the device in 16 bits resolution temp_1.adti2c = &hi2c3; // I2C Handler ADT7410_Init(&temp_1, 0x49); // I2C address depends of A0 and A1 pins ADT7410_Reset(&temp_1); // Optional ADT7410_SetResolution(&temp_1, ADT7410_16BITS); // Put the

Have any User Guide to setup matter in STM32WBA65RI? Matter 1.5.0 is supported in STM32WBA65RI?

Are there any Dual Core LoRaWAN Application examples for the STM32WL55CC that use the STM32Cube FW WL V1.5.0 (LBM) libraries?  If  there aren’t, will this be supported in the future? Thanks,Nick

Hello STM Community,We are developing a battery-powered iot product using the STM32WLE5 (single-core variant) with LoRaWAN communication. Problem DescriptionAfter an under-voltage event, the SUBGHZSPI bit gets permanently stuck at 0. The radio becomes completely unresponsive. Key observations:The issue **persists across full power cycles** (battery removed for minutes, capacitors fully discharged) A **software system reset** (`NVIC_SystemReset()`) does NOT fix it  **Re-flashing the firmware** does NOT fix it The only known fix is using STM32CubeProgrammer To Reset the bit ( Done in the picture below ). The error is SUBGHSPISD stuck to 0. Once we set the bit to 1 we can resume normal operation.    What we have tried (without success):1.RF subsystem reset via RCC_CSR_RFRST LL_RCC_RF_EnableReset(); // delay LL_RCC_RF_DisableReset(); // wait for RFRSTF to clear 2. SUBGHZSPI peripheral reset (APB3 bus): __HAL_RCC_SUBGHZSPI_FORCE_RESET(); // delay __HAL_RCC_SUBGHZSPI_RELEA

I set PA6 and PA7 to ADC4_INx in CubeMX and ran CODE GENERATE.The generated main.c file implements MX_ADC4_Init(), but it doesn't seem to be called from anywhere.Should I call this somewhere in the main statement?Also, I tried implementing ADC reading within the main loop, but the return value of HAL_ADC_GetValue() is always 0 (even though it's actually around VDD/2).I've attached main.c. Could you please tell me the correct implementation method?

I am trying to adapt the QSPI Flash (QSPI_MemoryMapped) example found in the STM32WB5MM-DK to run with FreeRTOS. My hardware uses different ports for the QSPI connection but all has been set up through the ST32CubeMX program.What I did then was to copy the code from the example into my project as a FreeRTOS task. However, the code pulls in some header files that don’t make sense to me. For example: stm32wbxx_hal_tim_ex.h results in the error “unknown type name 'HAL_StatusTypeDef”I’m not sure why this is happening, or even why this header file is being pulled int, I so would appreciate any pointers. My guess is that is has to do the the HAL timer versus the FreeRTOS timer, but even then don’t know were to look!Since I am using the flash without a fie system, maybe the QSPI_ReadWrite_DMA or QSPI_ReadWrite_IT would be better. If so, please suggest...Thanks

Hello, I hope all is well. I’m also looking for the FCC test report for the STM32WLE5CCU6. I noticed someone else had requested it previously, but the inquiry seemed to be redirected and may not have been followed through. In short, I will need someone from your compliance or technical team to contact me directly via email. We are currently working on the FCC frequency‑hopping requirements, and I’d like to understand how this was handled on your side and hopefully obtain some manufacturer guidance. Thank you in advance.  

Pins 43 (PB1) and 44 (PB0) on the STM32WB5MMG Datasheet are listed at NC (no connection). In CubeMx these pins are available to use. I would like to confirm which is correct for the Bluetooth module LGA86 STM32WB5MMG. 

I have written a small code which inits a GPIO in push pull config and a UART using cubemx then goes into stop mode. I have implemented same example in STM32L073 nucleo and STM32WL55 nucelo. In L073 I am able to see the current goes to 2-3uA. But in WL55 it is consuming 300uA or so. As per datasheet both will disable clocks to peripherals while going into stop mode. But in case of WL55 I am able to 1.5uA only when I denit all the gpios and disable clocks. Is it expected behavior or am I missing something.  I have added my code below for reference, thanks in advance. int main(void){/* USER CODE BEGIN 1 *//* USER CODE END 1 *//* MCU Configuration--------------------------------------------------------*//* Reset of all peripherals, Initializes the Flash interface and the Systick. */HAL_Init();/* USER CODE BEGIN Init *//* USER CODE END Init *//* Configure the system clock */SystemClock_Config();/* USER CODE BEGIN SysInit *//* USER CODE END SysInit *//* Initialize all configured peripherals

Hey,I want to enable a fast connection with the STM32WB09KE. How do i avoid that the services and characteristics are discoverd every connection? i toughts there was a option for that when using the full ble stack. But whit this firmware and mcu i don’t see it in the STM32CubeMX. So before is start is this possible with this MCU and ble firmware options? Thx in advance! Best regardsMathias 

Hi, Is there a way to disable Boot0 on PA11 on STM32WL33 ? I can’t find any Bytes Option. The only thing I can find, is we can re map PA11 to another pin.Thanks

Hello, We’re trying to program a STM32WBA23KE controller using SPI. We use the same function for STM32WB10 over SPI and it works.We’ve connected the SPI bootloader pins PA0/PA5/PB8/PB9 according to AN2606, where it mentions these are the pins used for QFN32 packages.We’ve also replaced an older part with an old date code to date code 620 because of the bootloader issue mentioned in the errata (should have been fixed since date code 614).We also have the PH3-BOOT0 pin connected and the NRESET. Still, we can’t get the bootloader to respond to the SPI sync command. What are we missing?

Hello,I designed a custom 4-layer PCB using STM32WB55CGU6. After assembly, ST-LINK cannot detect the MCU.ST-LINK connection:- SWDIO connected to MCU SWDIO pin- SWCLK connected to MCU SWCLK pin- GND connected- Target VCC connected- ST-LINK reports target voltage around 3.25 V- Error message:  "Unable to get core ID"  "No STM32 target found"Main symptoms:1. The board has 3.25 V on the 3V3 rail.2. ST-LINK cannot connect to the MCU.3. PA10 is configured as GPIO output high to drive LED1, but PA10 voltage is only about 2.18 V.   - R8 MCU side: 2.18 V   - R8 LED side: 2.15 V4. The same firmware works on another known-good board.5. I replaced the STM32WB55CGU6 with a known-good chip, but the issue remains.   The removed chip still works on another board, so the MCU itself does not seem damaged.6. Current consumption comparison:   - Known-good board: about 23 mA   - Problem board: about 9.2 mA   - Known-good board while holding RESET: about 12 mA   - Problem board while holding RESET: about 3

Hi, If you were to remove the antenna from circuit and transmit on the STM32WL5MOC, would you damage the internal rf power amplifier that transmits the signal due to the signal being fully reflected back to the output of the rf amplifer? Best Regards,Dave

I designed a custom PCB referencing the NUCLEO board, yet the board cannot be detected by any means. When flashing via STM32CubeIDE, the error pops up: Target no device found. Error in initializing ST-LINK device. Reason: No device found on target.I also tried detection with STM32CubeProgrammer, but neither SWD nor USART interfaces can identify the chip. I have verified that the ST-LINK probe works properly. I measured power supplies with a multimeter: the main supply is a stable 3.3 V, and VDDSMPS reads 0.98 V.The five PCBs I received after SMT assembly all exhibit the same connection failure, which rules out soldering defects as the root cause.Attached is my schematic. I would appreciate any troubleshooting suggestions. Thanks to all ST engineers and fellow developers. 

Hello everyone!I am trying to get all services and characteristics from steval-stwinbx1 board running FP-SNS-Datalog2 function pack. Here's simple program I wrote:import asyncio from bleak import BleakClient MAC_ADDRESS = "DA:3E:83:DD:30:F8" async def discover_services(mac_addr): async with BleakClient(mac_addr) as client: for service in client.services: print(f"\n[Service] {service.uuid}") print(f"Description: {service.description}") for char in service.characteristics: print(f" |") print(f" +-- [Characteristic] {char.uuid}") print(f" Properties: {', '.join(char.properties)}") if __name__ == "__main__": asyncio.run(discover_services(MAC_ADDRESS)) I expected to get services listed by nRF Connect app.But the program output is empty. Why? PS: I have done some research and experiments. I have tried running same script on linux and it ran perfectly (I used 2 machines: same machine (dual boot) and raspberry pi). I have noticed that board crashes if you are trying to

We are using the STM32WBA5MMG in our design but because of space and the shape of the board we need to be very precise with our components. The issue i'm having is with the documentation of the clearance required for the STM32WBA5MMG.In document “DS14801 @6.4 schematics and layout for pcb” the clearance on the left side of the package is 1.93mm from the side of the packageBut in “AN6305 @figure 35 to 39” the clearance on the side of the package is 1.93mm from the left side of pin 72.We are going to use the STM32 with the +10dB for Bluetooth and need the best option but also need to fit a lot of components on the PCB. Q.What clearance do i need to follow for the best Bluetooth signal, clearance in AN6305 or DS14801?

After generating the BLE_Sensor project files for the B-WBA5M-WPAN board with STM32CubeMX Version 6.17.0, the STM32CubeIDE shown this error. I looked for the file in STM32Cube_FW_WBA_V1.9.0 and it is not there. Please advise.10:56:39 **** Incremental Build of configuration Debug for project BLE_Sensor ****make -j9 allmake: *** No rule to make target '/Users/user/STM32Cube/Example/BLE_Sensor/Drivers/STM32WBAxx_HAL_Driver/Src/stm32wbaxx_hal_pka.c', needed by 'Drivers/STM32WBAxx_HAL_Driver/stm32wbaxx_hal_pka.o'. Stop."make -j9 all" terminated with exit code 2. Build might be incomplete.