STM32 MCUs Wireless

Hi everyone,I am encountering an issue while trying to run the Zephyr Bluetooth peripheral sample on a Nucleo-WB55RG board.I am currently working with the Zephyr main branch (specifically commit v4.3.0-2267-g3be4c4c5a819).Hardware & Firmware Setup:Board: Nucleo-WB55RGFUS Version: V2.2.0.0Wireless Stack: V1.20.0.2 (stm32wb5x_BLE_HCILayer_fw)Zephyr Version: v4.3.0-2267-g3be4c4c5a819I have explicitly started the Wireless Stack on the M0+ core (using STM32CubeProgrammer), but upon booting the Zephyr application on the M4 core, I get a kernel oops regarding an HCI command timeout after like 10 seconds.Error Log:*** Booting Zephyr OS build v4.3.0-2267-g3be4c4c5a819 *** [00:00:00.017,000] <inf> fs_nvs: 2 Sectors of 4096 bytes [00:00:00.017,000] <inf> fs_nvs: alloc wra: 0, fe8 [00:00:00.017,000] <inf> fs_nvs: data wra: 0, 0 ASSERTION FAIL [err == 0] @ WEST_TOPDIR/zephyr/subsys/bluetooth/host/hci_core.c:506 Controller unresponsive, command opcode 0xfc0c timeout with

Dear colleagues, Thanks to the recommendations of STTwo-32 , we have managed to establish communication between the BLE_CableReplacement on the b_wb1m_wpan1 module and our modified version of the ST BLE Sensor application on an Android smartphone. Since STM does not plan to open the source code of the ST BLE Toolbox, we used ST BLE Sensor as a base and modified the code as we understood it. However, during development, some issues have arisen: 1. We can only transmit data from the smartphone in response to receiving data from the WB module — meaning we have achieved half-duplex communication, not full-duplex as intended. 2. Main problem: We experience packet loss when attempting to send data to the smartphone at intervals below 100 ms. The issue becomes noticeable well before reaching 10 ms, making it impossible to achieve the 10 ms interval required by our application (which is within the BLE standard). We cannot determine whether the packet loss occurs on the WB side or the smartphon

Dear ST members,My application is using the EEPROM emulated library (X-CUBE-EEPROM) with an STM32WB microcontroller. I noticed that, when I update a variable, the page can be padded with random zeros. Attached are screenshots of the page before and after two variables were updated.I initially thought this could be unused variables, since we need to define the NB_OF_VARIABLES. Even reducing its value to match the number of variables I am using, the random zeros are still added to the page. The AN4894 says there is a wear levelling algorithm but this is the worst I have ever seen on an emulated EEPROM implementation. This makes it difficult to calculate the erase cycles I will need for my application. Can you clarify where these random zeros are coming from and if I can get rid of them? Regards

According to BLE spec, whitelisting is not related to paired or bonded devices. Our application uses the advertisement and scanning for sensor beaconing application. STM32WB55 is not able to scan the interested sensors by whitelisting. STM32WB is not supporting whitelisting in advertisement scanning.Now with scanning I am getting too many advertisement reports in the bluetooth dense environment. 

I just flashed the end node of the P nucleo LRWAN 3 with the AT master firmware, but I am still unable to send AT commands via my terminal to reconfigure some parameters of the end node. I also made sure I set up all the necessary parameters in the terraterm software correctly and I am still not able to communicate with the end node via terminal using AT commands.

Hello, Board: NUCLEO-WL55JC2 (2 boards)MCU: STM32WL55JCIDE: STM32CubeIDEProgramming: Bare-metal C or Cube IDE(C/C++) Goal:I want a minimal RF example using two NUCLEO-WL55JC2 boards where one board transmits a simple message and the other receives it and for example toggles an LED . I searched on ST website and GitHub, but most available examples are full LoRaWAN stacks. I could not find a simple RF Tx/Rx reference similar to an LED blink example. I have not written RF code yet and am looking for an official ST reference to start from.Suggest any website reference or youtube videos where i can understand it clearly. Questions:1. Is there an official ST RF Tx/Rx example for NUCLEO-WL55JC2?2. Any recommended CubeWL example or GitHub repository?3. Which example is best for learning basic RF communication? 4. Should i need to use the RF like NRF24L01 Transcever or does it supports? Thanks in advance.

Hi,  I'm using a STM32WL5MOC. I see that in the LoRaWAN_Init the LmHandlerJoin is not in a USER CODE section, meaning that it can't be disabled. In my application I would like to do the join upon my request and not in the init. How I can prevent from join? /* USER CODE END LoRaWAN_Init_2 */ LmHandlerJoin(ActivationType, ForceRejoin); if (EventType == TX_ON_TIMER) Thanks.  

Hello There i am using https://github.com/STMicroelectronics/STM32CubeWL/tree/main/Projects/NUCLEO-WL55JC/Applications/LoRaWAN/LoRaWAN_End_Node_FreeRTOS this example ,in that there is timer used for sent the data , i want RTC for send data for particular time and all how can i do ???

I am using STM32WBA5MMGH6TR in my project for sending data received from a sensor. BT is used for transmission.The data will be transmitted to a central node.This is a battery operated device. The signal chain is given below.Sensor--> ADC-->STM32WBA5MMGH6TR.Could you please review the attached schematic.

Hi,   I'm working with LoRa on STM32WL5MOC for a custom board and comparing performance with the dev board. I've measured RSSI and SNR at different distances. - Custom board vs Dev board RSSI, SNR values are noted for reference. How do I improve the custom board's RSSI? Are there specific design or config tweaks (like antenna matching, RF switch, etc.) to boost it? Using STM32WL5MOC reference for the custom board.   Any insights would help! Thanks

Split from STM32WBA5MMGH6TR Debug interface PCB layout - which is a separate question.Hi , thank you very much.In my module (STM32WBA5MMGH6TRTR), there is only one pin for boot selection BOOT0. I believe when it is pulled low booting happens from main flash memory. But when it is high , from where the module is booting.

I am using STM32WBA5MMG in my design. This the development board schematic. Below image is from development board schematic.As per the constrains , SWDIO and SWCLK must be length matched. Also need to provide a shield.My questions are given below.SWDIO and SWCLK are not differential lines, why length matching is required for them.By shield did they mean routing SWDIO and SWCLK on top of a solid GND plane

I'm using Seeed Studio's Wio E5 board, LoRaWAN 1.0.3 and the repository Seeed Studio Wio E5 LoRa  as the base of my source code. I want my device to force a rejoin only when NVM context is not restored (e.g., after a reset or memory clear), and to resume using the previous session if the NVM context is successfully restored. I have already set LORAWAN_FORCE_REJOIN_AT_BOOT to false and CONTEXT_MANAGEMENT_ENABLED to true, and I noticed that even if NVM data is restored successfuly the device rejoins (which is wrong).

I have tested the LoRaWAN_End_Node example on a B-WL5M-SUBG1 board and I measure power consumption of 1.7uA when the processor is in STOP mode between transmissions.  This is exactly what I expected to see.I designed a very simple custom board based on the B-WL5M-SUBG1 design, downloaded the same .elf file to it, and it communicates with my LoRaWAN gateway as I expect.  However I measure ~300uA current draw while it is in STOP mode.  I have compared my custom board schematic to that of the B-WL5M-SUBG1 several times looking for a difference that would account for that much extra power consumption and I just have not found it.I am using STM32CubeMX v6.16.0, STM32Cube FW_WL V1.4.0, and the part is STM32WL5MOCH6TR.  I have attached the schematic of my custom board.I am hopeful that someone can see what I have missed.

Dear Team,How to configure the BOOT0 pin of this module.In the reference design it is let floating with an option to pull up.In the application note (How to develop RF hardware using STM32WBA MCUs - Application note) it is pulled down.May I know in all these three configurations(Pull up, Pull down, floating) what will be happening. From where it is booting.You have any document which describes how to configure this BOOT0 pin.RegardsHariom 

The Application circuits in the Datasheet under section 5 do not list any values for the components, are they available somewhere? All of the reference designs linked in the wiki and on the website are for the STM32WL33C. Do the values directly transfer over? We are also explicitly interested in the configuration without the SMPS as there are no application examples for the STM32WL33C without the SMPS and it is not clear which components can be removed when not using it.

Hello ST Community and ST Engineers, I am currently working with a NUCLEO-WL55JC1 (STM32WL55 dual-core: Cortex-M4 + Cortex-M0+) and I am facing an issue when using dual-core projects generated with STM32CubeMX. I would really appreciate any guidance or confirmation from ST engineers or experienced users.   Hardware / Software: Board: NUCLEO-WL55JC1 (STM32WL55 CM4 + CM0+) Tools: STM32CubeIDE, STM32CubeMX, STM32CubeProgrammer Also tested using VSCode with STM32 extensions Firmware packages tested: STM32Cube_FW_WL_V1.3.0 STM32Cube_FW_WL_V1.4.0 Examples tested: LoRaWAN_End_Node LoRaWAN_End_Node_FreeRTOS LoRaWAN_End_Node_DualCore LoRaWAN_End_Node_DualCoreFreeRTOS References followed: YouTube (LoRaWAN workflow overview): https://www.youtube.com/watch?v=8KNfrWoa1fw Dual-core from scratch and CM4/CM0+ LED blink walkthroughs: Playlist: https://www.youtube.com/playlist?list=PLnMKNibPkDnFPqEmJAwEjsSS8MOQZHRNF Specific video: https://www.youtube.com/watch?v

Hello all, I have been running into a lot of issues trying to get the firmware for the BLE onto my board using the STM32WB55RG. Now I did follow this video and originally got it working, but then I accidently hit delete firmware and was unable to get it on again. Right now any time I try to upgrade my firmware I always get the WARNING: FUS_STATE_IMG_NOT_FOUND.I have tried doing a mass erase and then re-upgrading as I saw in another post but that also will not work.Here is the list of steps I take right now:1. Plug in board2. Connect via STM32CubeProgrammer3. Start FUS4. Read FUS Info5. Attempt to upgrade stm32wb5x_BLE_Stack_full_fw.bin at 0x080C70006. Receive error messageThis is a custom board, but I did at one point have the BLE working on it. Here is my option bytes configuration:  

Dear Team, I am using STM32WBA5MMG in my project. The datasheet does not contain pin description and their alternate functions. I also checked STM32WBA5xxx datasheet (DS14127). It does not contain any pin description and alternate functions of STM32WBA5MMG. For finding the pin details of , may I know where I need to check in the datasheet. Regards HARIOM

I have an X-Nucleo-67W61M1 with a Nucleo-WB55RG host board. I was following this link for how to do the set up How to use X-CUBE-ST67W61 STM32CubeMX pack. One of the prerequisites says that I need to ensure that I flash the updated code before using.In this link there is steps to flash the board with an STM32 host ST67W611M1 Hardware setup. It says that what I need to do is migrate the NCP_Loader to generate the binaries, but I am unsure how to do this.Is there anyone that has some suggestions? I am new to working with STM boards and I would appreciate any help.

HERE WE R USING STM32WB55 MCU FOR BLE PURPOS AND FACING ISSUE IN FLASHING BLE STACK .HERE IT SHOWS 0.0 STACK VERSION AND FUS VERSION 2.1 IN IMAGE AFTER READING.  WE ARE USING ADDRESS FOR FUS 0X80EC00 AND FOR BLE STACK WE ARE USING 0X80C7000 OR 0X80C000,AND AFTER FIRMWARE UPGRADE WE R GETTING ISSUE OF FUS STATE IMAGE NOT FOUND .HOW CAN WE SOLVE THIS ISSUE PLEASE PROVIDE A SUPPORT FOR THAT.FOR YOUR REFERENCE WE ATTCHED SOME IMAGES .

I am using the Stm32wb09kev6tr ic for the ble.I am not able to update the fus or wireless stack from the st link? is there anything i am doing wrong? is there any documents regarding this which will helpfull?

When I Debug cmwx1zzabz_0xx, I get a hard fault somewhere near a call to HAL_PWR_EnterSLEEPMode(). It happens just after all the init code, somewhere in the first call to MX_LoRaWAN_Process(). If I step into MX_LoRaWAN_Process() and continue stepping, there is no fault.Note that I commented out the calls to DBG_Disable() and DBG_ProbesInit() in SystemApp_Init() since they drop the ST-Link connection over USB. 

I enabled the bonding feature in STM32WB5MMGH6TR.Bonding is working correctly. But when the device(STM32WB) is bonded to phone(Android 15), calling disconnect from the phone does not disconnect the device.This problem does not occur when:-1. Phone Android version is less than 15(even after bonding it can disconnect).2. Device is not bonded to the phone(Android 15).

Hello ST Community,I am working with NUCLEO-WBA55CG and encountering a startup issue when using the BLE_p2pServerThreadX example from STM32CubeWBA v1.8.0.EnvironmentBoard: NUCLEO-WBA55CGMCU: STM32WBA55 (single-core Cortex-M33)SDK: STM32CubeWBA v1.8.0RTOS: Azure RTOS ThreadXExample: BLE_p2pServerThreadXIDE / Toolchain: IAR Embedded Workbench 9.60Debugger: ST-LINK (on-board)Problem DescriptionAfter programming the firmware to the board::cross_mark: On cold power-on (Power-On Reset), the application does not start:white_heavy_check_mark: After pressing the RESET button, the application runs normallyThe issue is 100% reproducibleBLE advertising starts correctly only after a manual reset, not after initial power-up. Additional Tests PerformedThe issue occurs even when Timebase Source is set to SysTickThe MCU is confirmed to be STM32WBA55 (single-core)(not STM32WB, no wireless coprocessor)No user code is executed after early initialization during the failing POR caseAfter RESET, behavio