STM32 MCUs Wireless

Hello folks, I've seen a similar topic(link) on this forum, but it had no solution, I'll take my chance and see if you could offer me some tips on how to debug this. I've designed a custom "break-out" board for STM32WB5MMG and I'm trying to communicate with the MCU via SWD using a STLINK-V3 MINIE but unfortunately, it's not able to detect the target MCU even though I have connected the MCUs PA13/SWDIO & PA14/SWCLK directly to STLINKV3. I've referred to the data sheet on page 16 to the best of my ability on how to design the breakout board but still I am not able to communicate with the MCU. (see schematic below)Am I missing something here? Any tips would be greatly appreciated thanks!

Hi, I'm facing an issue with waking the STM32WL55JC1 from Standby mode using RTC Alarm A. Setup: Using LSE as RTC clock source RTC and Alarm A are initialized correctly Alarm A interrupt works when not entering standby Wake-up via RTC Wakeup Timer works fine (standby + timer = success) Issue: When I: Clear RTC time and date Set Alarm A to trigger a few seconds ahead Enter Standby mode Wait for wake-up → The system does not wake up from Alarm A. However, if I skip Standby mode, Alarm A fires the interrupt as expected. Observation: RTC Alarm A interrupt is configured and enabled. EXTI and NVIC settings are correct. I suspect the Alarm A wakeup source isn’t properly enabled or EXTI line isn’t configured before entering standby. Request: Could you confirm the correct sequence or any missing configuration required for: Enabling Alarm A as a wakeup source from standby Ensuring EXTI line 17 is correctly set before standby Let me know if additional register dump

 I followed the tutorial from this video: https://www.youtube.com/watch?v=6JPys9B497c to practice setting up BLE.However, after building the project I encountered the following error:  crtn.o: missing C:/ST/STM32CubeIDE_1.19.0/STM32CubeIDE/plugins/com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.13.3.rel1.win32_1.0.0.202411081344/tools/bin/../lib/gcc/arm-none-eabi/13.3.1/../../../../arm-none-eabi/bin/ld.exe: warning: C:/ST/STM32CubeIDE_1.19.0/STM32CubeIDE/plugins/com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.13.3.rel1.win32_1.0.0.202411081344/tools/bin/../lib/gcc/arm-none-eabi/13.3.1/thumb/v8-m.main+fp/hard/crtn.o: missing .note.GNU-stack section implies executable stackC:/ST/STM32CubeIDE_1.19.0/STM32CubeIDE/plugins/com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.13.3.rel1.win32_1.0.0.202411081344/tools/bin/../lib/gcc/arm-none-eabi/13.3.1/../../../../arm-none-eabi/bin/ld.exe: NOTE: This behaviour is deprecated and will be removed in a fu

Dear ST Support Team and Community Experts,I'm developing a BLE application using the STM32WB55 Nucleo board (P-NUCLEO-WB55) and observed unexpectedly low data throughput, requesting guidance on optimization.1. Issue DescriptionCurrent Rate:Modified BLE_p2pServer example to send sensor data via P2PS_Send_notification() in a loop.Measured: ~4.5KB/s (7.5ms connection interval).Comparative Tests:Enabled L2CAP CoC in Data Throughput example (SW2 press): ~40KB/s (still below expectations).Competing device (nRF52840) achieves >100KB/s under identical conditions (2M PHY + DLE).Anomaly:No throughput improvement after forcing 2M PHY via aci_hal_set_phy_parameters().2. Test EnvironmentHardware: STM32WB55CGU6 (Nucleo-68 module).Software:Wireless Stack: v1.18.03 (FUS not upgraded).IDE: STM32CubeIDE v1.15.0.Configurations applied per AN5289 Rev 8 (Sections 7.8 & 8.6.9 for DLE/MTU/CoC).Connection Pa

I have recently taken delviery of a custom board carring the SMT32WB5MMG SiP. This is the first time I have used this specific part in a custom design, but previously have been working with a SMT32WB55 development kit without any issues.In my design I have followed the guidelines in the datasheet to the best of my ability, supplying power to the SiP as shown in the reference schematics provided on page 14.I am trying to program the board via a SWD header (supplying 3V3 power to this header only), but have had difficulty connecting to the board with any combinaton of settings in STM32CubeProgrammer;The reference doesn't explicitly show how the SWD pins should be connected, but I assume a direct connection to the SWDIO and SWCLK pins would be sufficient. Please see my schematic for the controller below;Can someone please review my schematic and provide some advice on what might be going wrong here?Many thanks,Craig 

Hi everyone,   I couldn't find the application note on STM32WB0 MCU hardware development. Can I refer to AN5290 which is for STM32WB instead of the STM32WB0. If so, is there anything I would need to pay attention to for the STM32WB0 series? Or should I reference from the NUCLEO-WB07CC's schematics instead?    Thank you for your time and help!

Given that STM32WL product line seems to support Wi-Fi 802.11ah (HaLow) bandwidth and modulations. Would one be able to configure the radio to connect to such network?

Hi all, I'm setting up a custom board using the STM32WL33 device. I'm using four single-ended ADC inputs: ADC_VINM0, ADC_VINP0, ADC_VINM3, ADC_VINP3.I would like to use DMA and sequencer, adding TEMP and VDD as 5th and 6th conversions. I managed to got the above up and running, but: a) appears that ALL conversion is done on 3.6V conversion range, regardless of software setup and subsequent SWITCH register settings (which appears correctly set: 0x8282); using the below macro gives correct ADC_value => mV conversion: __HAL_ADC_CALC_DATA_TO_VOLTAGE(ADC_VIN_RANGE_3V6, adc[2], ADC_DS_DATA_WIDTH_12_BIT);b) TEMP reading appears totally wrong. At ambient temp (30°C), ADC readings is around 726 (over 12 bits). If I readback calibration registers: uint32_t Calib_c30 = (int32_t)*TEMPSENSOR_C30_ADDR; // =2556uint32_t TCK_c30 = (int32_t)*TEMPSENSOR_TCK_ADDR; // =300and use RM0511 - chpt 12.2.1 formula, I get T[°C] = -153°C (!!!) ADC register settings:Finally, n

Hi,Totally newb. I have a custom board with a STM32WB55CEU6. Connected over ST-LINK.I'm trying to upgrade FUS. Using stm32wb5x_FUS_fw.bin at 0x0807A000Everything seems to work fine until the very last step, where I get an error: FUS_STATE_IMG_NOT_FOUND: Firmware/FUS upgrade requested but no image found. (such as image header corrupted or flash memory corrupted)Any ideas?Here's my log:16:59:29 : Old Firmware delete ...16:59:29 : Warning: Option Byte: nSWboot0, value: 0x0, was not modified.16:59:29 : Warning: Option Byte: nboot0, value: 0x1, was not modified.16:59:29 : Warning: Option Byte: nboot1, value: 0x1, was not modified.16:59:29 : Warning: Option Bytes are unchanged, Data won't be downloaded16:59:29 : Time elapsed during option Bytes configuration: 00:00:00.00016:59:29 : Succeeded to set nSWboot0=0 nboot1=1 nboot0=116:59:29 : Memory Programming ...16:59:29 : Opening and parsing file: 0x495_FUS_Operator.bin16:59:29 : File : 0x495_FUS_Operator.bin16:59:29 : Size : 8.00 KB16:59:29 :

Hi community,I'm very new to STM32 wireless. I need some support.I followed the MOOC "STM32WB Getting Started Series: Part 12b, Lab. Receiving data from the phone " using Nucleo WBA55CG board. When I build the code, there were 0 error and 0 warning. Problem started with flashing. I couldn't find the STM board on ST BLE Toolbox on my phone. However, when I followed MOOC "STM32WBA5x workshop - 5- Add a BLE profile (P2PServer) to your peripheral" usng same HW, it worked perfectly. I could find STM board on the phone, receive noti when button is clicked und toggle the LEDs from phone. How can I solve this issue? I'm using Windows 11 Enterprise 23H2, STM32CubeMX v6.15.0, STM32Cube IDE 1.18.0 with STM32Cube_FW_WB_V1.7.0.

Hello STM32 Community,I accidentally erased the full firmware on my STEVAL-PROTEUS1 board (STM32WB5MMG). After that, I followed this process to recover:FUS firmware: Updated using stm32wb5x_FUS_fw.bin from STSW-PROTEUS (since FUS was missing in the other package).BLE Stack: Flashed stm32wb5x_BLE_Stack_full_fw.bin from FP-AI-PDMWBSOC.OTA Reference App: Flashed Proteus_BLE_FUOTA_reference.bin from FP-AI-PDMWBSOC.After these steps, Bluetooth worked fine — I could connect to the board via my phone.However, when I upload the user application PDMWBSOC.bin (from FP-AI-PDMWBSOC), Bluetooth stops working — it gets disconnected and doesn’t advertise anymore.I tried uploading the application using:STM32CubeProgrammerOTA method via the mobile appIn both cases, the same issue occurs.My Goal: I want to use the FP-AI-PDMWBSOC software pack to run the predictive maintenance application via BLE.Can someone please guide me on what might be going wrong or if any additional steps are needed after uploadin

Hi,I'm having strange situation with mine BLE application on STM32WB5M module, i.e. Peripheral mode, which has implemented configuration characteristic (write with confirm) according by BLUEST protocol 00000000-000F-11e1-9ab4-0002a5d5c51b. Client reported, that during write operation to one of config characteristic (activate beep & 30s LCD), STM32 breaks connection, but it happens only on low battery!I started investigation with debug console, as main objective was to replicate situation, using HopeRF and AT commands as Central (tested before all worked smoothly). Currently I can connect, but I can't proceed the write operation, as STM32 breaks BLE connection with very little feedback (picture), i.e. Reason 0x8. When I used the ST BLE Toolkit, it does work fine though. What I tried and failed:- set the same interval, latency and timeout for Phone and HopeRF- changing the ST BLE stack from 1.18 to 1.21Thanks for any help. Marcin  

Hi everyone,I'm working on a LoRa project using the STM32WL55JC1 microcontroller, and I'm looking to implement a self-healing mesh network with multiple repeaters.Could anyone suggest existing libraries, detailed tutorials (step-by-step preferred), or GitHub repositories that would be helpful for this specific implementation? Any information or guidance on achieving a self-healing mesh with the STM32WL55JC1 would be greatly appreciated.Thank you in advance for your time and assistance!

Ever since being forced to update STM32CubeIde, every time a change is made to the .ioc file and the code is regenerated the following errors show up.app_ble.c /** * Write the BD Address */ p_bd_addr = BleGetBdAddress(); ret = aci_hal_write_config_data(CONFIG_DATA_PUBLIC_ADDRESS_OFFSET, CONFIG_DATA_PUBLIC_ADDRESS_LEN, (uint8_t*) p_bd_addr); if (ret != BLE_STATUS_SUCCESS) { APP_DBG_MSG(" Fail : aci_hal_write_config_data command - CONFIG_DATA_PUBLIC_ADDRESS_OFFSET, result: 0x%x \n", ret); } else { APP_DBG_MSG(" Success: aci_hal_write_config_data command - CONFIG_DATA_PUBLIC_ADDRESS_OFFSET\n"); APP_DBG_MSG(" Public Bluetooth Address: %02x:%02x:%02x:%02x:%02x:%02x\n",p_bd_addr[5],p_bd_addr[4],p_bd_addr[3],p_bd_addr[2],p_bd_addr[1],p_bd_addr[0]); } CONFIG_DATA_PUBLIC_* needs to be changed to CONFIG_DATA_RANDOM_* case ACI_HAL_WARNING_VSEVT_CODE: { aci_hal_warning_event_rp0 *p_warning_event; p_warning_event = (aci_hal_warning_event_rp0 *)p_blecore_evt->data; U

I've added the X-CUBE_AZRTOS-WB software pack and checked all the boxes for ThreadX but the RTOS ThreadX checkbox in STM32CubeIDE is disabled.  Is something else required to use ThreadX on an STM32WB? Kindes regards

Hello.I'm trying to launch a minimal LoRaWAN project. CubeMX version 6.15.0. When using MSI RC clocking, the module works without issues. When attempting to use the TCXO, the module starts, packets are successfully transmitted to the server, but are not received (IRQ_RX_TX_TIMEOUT error). In the "LoRaWAN Middleware / TCXO Support" settings, it displays "TCXO not available," and no other options are present.Part of the code from the SystemClock_Config initialization function:RCC_OscInitStruct.OscillatorType = RCC_OSCILLATORTYPE_HSE|RCC_OSCILLATORTYPE_LSE; RCC_OscInitStruct.HSEState = RCC_HSE_BYPASS_PWR;Attaching screenshots of the settings.

I want to use a USB connection on a STM32WBA65 processor, purely for debug purposes to get some info back to a PC on a virtual com port. The device will not be powered by USB.I don't want the processor to act as a host.Questions:Can the STM32WBA65 provide this implementation of a virtual com port? How is this set up in the HAL?If I use a USB micro connector, which pins should be connected to where? In the past, on simpler STM32 devices, I have just connected ground, DP & DM from the cable directly into the micro.If I use a USB-C connector, because they are generally more sturdy, which pins need connecting? Do I need to connect CC pins? Can I just pull them up (or down) with simple resistors? 

I would like to use STM32WB (NUCLEO-WB55) with eddystone and sleep periodically.I find examples about beacon and about power low mode but it's not easy merge them.I'm looking for an example.Thank youPaolo Preioni

Hello everyone,I'm using STM32WLE5 (LoRa E5) module for sending the data from one module to the other. The Lora transmitter will be receiving the data from the UART1 which is then transmitted over the radio.I have used baudrate 115200 and tested, everything works fine. But when I change the baudrate from 115200 to the higher baudrate(921600), No data is being received by the STM32WLE5 module. Clock of the peripheral is running with 48MHz. Is there any configuration of UART that need to be changed for the uart baudrate to work properly?

Hi there,for a project at university we need to estimate the power consumption of stm32wl33c8 mcu. One open question is the power needed for transition from deepsleep to waking state as we need to wake the cpu very often over a long time to read out an i2c sensor, read out an analog value with adc and put back to sleep.So first guess is that most time is needed to stabilize HSI actually, but actually can't find values for it on datasheet. The sensor becomes ready within 5ms.Hope we'll get good suggestions here.Best regards

Hi,I am trying to set up a SPI communication to the STM32WL's integrated LoRa transceiver. So, I was able get NSS, MOSI and SCK to work, however I won't receive any data on the MISO line.My code is following:void SUBGHZSPI_DebugEnable(void) { RCC->AHB2ENR |= (1U << 0); //enable GPIO-A GPIOA->MODER &= ~(3U << 8); //reset PA4 GPIOA->MODER |= (2U << 8); //set PA4 GPIOA->MODER &= ~(3U << 10); //reset PA5 GPIOA->MODER |= (2U << 10); //set PA5 GPIOA->MODER &= ~(3U << 12); //reset PA6 GPIOA->MODER |= (2U << 12); //set PA6 GPIOA->MODER &= ~(3U << 14); //reset PA7 GPIOA->MODER |= (2U << 14); //set PA7 GPIOA->AFR[0] &= ~(15U<<16); //reset AF of PA4 GPIOA->AFR[0] |= (13U<<16); //set AF13 of PA4 GPIOA->AFR[0] &= ~(15U<<20); //reset AF of PA5 GPIOA->AFR[0] |= (13U<<20); //set AF13 of PA5 GPIOA->AFR[0] &= ~(15U<<24); /

Issue Description:I’m trying to upgrade the FUS firmware on an STM32WB55 (specifically STM32WB55CGU6) using STM32CubeProgrammer (v2.20.0). However, when selecting the file stm32wb5x_FUS_fw.bin and starting the upgrade, I get the following error:Error: FUS_STATE_ERR_UNKNOWN: Unknown errorSystem Details:MCU: STM32WB55CGU6Connection Mode: ST-LINK (SWD, Hot plug, Hardware reset)Target Voltage: 3.23VCurrent FUS Version: v0.0.0.0 (target file is FUS V2.1.0.0)STACK Version: v0.0.0.0ST-LINK Firmware Version: V2J37S7Operating System: Windows 11STM32CubeProgrammer version: v2.20.0Log Output:Download Stack/FUS image at address 0x08C00000Opening and parsing file: stm32wb5x_FUS_fw.binMemory Programming...File: stm32wb5x_FUS_fw.binSize: 23889 KBAddress: 0x08C00000Erasing memory corresponding to segment 0:Erasing internal memory sectors [203 208]Download in Progress:File download completeTime elapsed during download operation: 00:00:00.648Firmware Upgrade process begins...Application is running, Plea

Hello,I am trying to get I2S and DMA working on my stm32wb55 microcontroller. I want to read data from an INMP441 (or similar). I did try to use the STCube IDE (or MX) to configure I2S and DMA using tutorials from the internet but this also did not work. The tutorials are all made for other ST-microcontrollers though.I either have a problem setting up the DMA, SAI (for I2S) or the DMA interrupt. I do not really have any idea where my problem lies. Just using the standard configurations from STCube do not seem to work.Does anyone here have any experience with the STM32WB55 and the SAI of this Microcontroller in particular? I am using the WeAct STM32WB55CGU6 for testing.Thanks a lot for helping me out here.

I have 3 Nucleo-WL55JC and 2 B-WL5M-SUBG1 systems all running same code and located within a 1 foot of each other.  Additionally I have custom sensors based on the STM32WL5MOC located 4 to 8 feet away.  The Nucleo-WL55JC modules report rssi values between -50 and -60 dBm.  The B-WL5M-SUBG1 modules report rssi values between -100 and -110 dBm.Physical range test suggest these reads are real.  As I move the sensors away the B-WL5M-SUBG1 lose the ability to receive the packets much sooner than the Nucleo-WL55JC.  Note the reads above are based on unmodified modules. There is a footprint on the B-WL5M-SUBG1 modules for a pi filter in the antenna line.  The factory configuration is a single serial 0 ohm resistors which is not performing very well.The datasheet for the for the STM32WL5MOC states that for 915MHz operation:"Max output power 21 dBm is obtained for Z load = 63 + j×22".I have tried adjusting the impedance

Hello there, I ran into an issue with my STM32WBA55CGU6 chip. I designed my board with schmematics from Mouser: 511-STM32WBA55CGU6 with the UFQFPN48 pinout. When setting up my chip in CubeIDE I also chose the STM32WBA55CGU6 version. But when comparing the pinout of the chip the SMPS version of the UFQFPN48 footprint is displayed.Is this an issue I can solve by selecting the correct footprint in CubeIDE or is it, that CubeIDE is wrong at that point? The UFQFPN48 version should have PB12 on Pin1 and not VSSSMPS as shown in the image. Thanks in advance,Tim