STM32 MCUs Wireless

I have a requirement to implement the BLE SPP protocol that will eventually be ported to the STM32WB1MCC module. Since I am totally new to BLE, I'd like a recommendation for a place to start. Specifically which demo or eval board and associated software. For example, is the NUCLEO-WB51CC the best (most supported and easily ported)?Thanks, Dave

This is coming from someone with very limited experience with BLE, so be patient in your response.I have a requirement for a device that will operate as a GATT Server emulating a UART to an external device (IOS or Android). On input from the user, this should be terminated and the device go into a BLE Advertising mode sending out data packets periodically. Similarly, the device must be able to revert back to the UART emulation mode.My search so far keeps leading me to the STM32WB1MMC as the production volume is low and this module provides the required certifications.First question: Can the STM32WB1MMC operate in these modes and switch between them?Second question: With the volumes of information I've read on ST's web site, can you point me to a evaluation platform and corresponding documentation to get started? (I am easily confused by all the reading!)Final question: Other than "RUN!" what advice would be of help for a starter?Thanks, Dave

Hi,I need to implement the following behavior on a STM32WB55.Upon a command, device must advertise in 2 different modes:Just works. No bonding, connection is accepted without any authentication requirements. All characteristics can be read and written.Legacy pincode. No bonding, a fixed pincode shall be required by the host at every connection.To acheive that, I followed scrupulously the ST wiki & configured the following:aci_gap_set_io_capabilityaci_gap_set_authentication_requirementcharacteristic security permissionsI am able to have either one of the 2 scenarii, but I cannot switch dynamically from one another.The key difference resides in the security permission of each characteristic.

Hi,I'm having an issue with the WBA6_LinkLayer_BLE_Basic_lib.a library on zephyr.The library is found in zephyrproject/modules/hal/stm32/zephyr/blobs/stm32wba/lib directory in zephyr 4.2 (tag v4.2.0 in https://github.com/zephyrproject-rtos/zephyr/tags).The issue is with function llhwc_conn_evnt_done in object llhwc.o inside the library:On occasions, this function generates a Usage Fault (unaligned memory access) when run on nucleo_wba65ri board.The offending instruction is 'ldrh r3, [r2, #0]' at address 0x0000359c (function assembly code below).The registers at the time of the fault are:R0: 0x00008F10R1: 0x00008208R2: 0x4802FFFFR3: 0x0000FFFFR4: 0x2000CBB0R5: 0x4802000CR6: 0x0000FFFFR7: 0x48020000R8: 0x2000DD34R9: 0x0000923C

Hi,I got a NUCLEO-WB55RG board and was trying to program it as a HID device. I have configured the STM32CubeIDE and have uploaded the code to the board. Yet, when I tried connecting the User USB, it unfortunately didn't work. My computer did not recognize it as an HID device. I have switched to USB MCU on JP1.

Hello,I have created two BIS channels eng and esp, under BIG main group by assigning bis[0] and bis[1] and given left and right channel as the input. At the receiver side, the first channel [0] will perfectly get connect and displays "synced with some freq as assigned" but for the second one it doesnt like that and no data is streaming. How to correct the issue. Kindly do the needful.Thank you

The parameters  for the AT+TCONF are shown differently in your example to where you show the breakdown of the individual paramters.In your example you show the <cr. parameter on the command line as 4/5  868000000:14:125:12:4/5:0:0:1:255:0:0:0where in the description of the parameters on page 28 you show that 1:  represents 4/5, so shouldn't command line look like this instead   868000000:14:125:12:1:0:0:1:255:0:0:0   

背景描述：1.我现在使用的是：STM32Cube_FW_WB0_V1.4.0\STM32Cube_FW_WB0_V1.4.0\Projects\NUCLEO-WB09KE\Applications\BLE\BLE_DataThroughput_Server中BLE_DataThroughput_Server例程2现在使用的是STM32CUBE6.16进行配置需要帮助：1BLE_DataThroughput_Server例程中用到了UART1RX和UART1TX,我的项目中这两个引脚另有他用，但是我在这个例程的基础上去除这两个引脚后，例程不能进行蓝牙通信了，我不知道那个参数影响到蓝牙通信？这两个引脚与蓝牙通信的关系？2能否提供本身并不使用这两个引脚的，蓝牙通信的例程（只实现蓝牙通信）？

Dear all,with the latest update of STM32Cube_FW_WBA_V1.8.0, the BLE_p2pServer_TZ example no longer works. The following error occurs during compilation:make: *** No rule to make target 'C:/0_ST_abc/Example/Projects/Common/WPAN/Interfaces/app_bsp.c', needed by 'Application/User/Common/WPAN/Interface/app_bsp.o'. Stop. If I copy the missing file from another location in the folder structure, it is deleted every time STM32CubeMX is used to regenerate the project.Even when using a copied of this file from a previous firmware version, the button is not recognized by the ST BLE Toolbox.Is there a simple workaround to get this project running?Thanks in advance.

Hello Community,I have been working on a BLE project in which the server needs to send notification of a characteristics that is up to 512 bytes long. As in previous CubeMX versions (6.12 and before), I was expecting CubeMX to generate the function Custom_<CHAR_NAME>_Send_Notification() within custom_app.c  to properly call aci_gatt_update_char_value_ext(), which indeed supports chars up to 512 (see code below).However, this is no longer the case from Ver. 6.13 onwards. Instead, CubeMX now generates only functions based on aci_gatt_update_char_value(), which handles lengths lesser than the limit (BLE_CMD_MAX_PARAM_LEN - 6), which is 243 maximum. Needless to say, my project no longer works without the proper notification function.ST Support said that the latest CubeMX behavior is "normal", but it did not explain why

I'm having trouble changing the linker files to take 20 kB of flash from CM0+ for CM4's use on a STM32WL5.  Is this possible? 

Hello Forum,I upgraded my (alredy working) project, based on AT-Slave to the latestSTMCubeIDE: V2.0.0STMCubeMX: V6.16.0and STM32Cube_FW_WL_V1.4.0My problem: suddenly I get Flash Error -6 "FLASH_IF_PARAM_ERROR" after "AT+CS".Is this a know issue? Before, all worked and "AT+CS" stored well.My Stack, derived from AT-Slave:AT+VER=? APPLICATION_VERSION: V1.4.0 MW_LORAWAN_VERSION: V2.6.2 MW_RADIO_VERSION: V1.3.1 L2_SPEC_VERSION: V1.0.4 RP_SPEC_VERSION: V2-1.0.3I think there might be some issue with the FLASH-IF-Driver? I also reconised in "lora_at.c" a missleading comment:(it should be 256kBytes, not 128), whereas ADDRESS is right. /** * @brief LoRaWAN NVM Flash address * @note last 2 sector of a 128kBytes device */ #define LORAWAN_NVM_BASE_ADDRESS ((void *)0x0803F000UL)

There is an error in table 17 on page 33 in regards to two of the pin positions for the MB1880A adapter.  Table 17 states that pin 2 is SPI1_MOSIP (PA7) / UART1_TX (PC1) and pin 3 is SPI1_MISOP (PA6) / UART1_RX (PC0).  These two pins are reversed in both the CN2 and CN3 columns. In actuality, pin 2 is SPI1_MOSIP (PA7) / UART1_RX (PC0) and pin 3 is SPI1_MISOP (PA6) / UART1_TX (PC1).  This is confirmed by table 13 (page 28), the MB1779 schematic (MB1779-HIGH-BAND-B02 Board schematic under the B-WL5M-SUBG1 CAD Resources tab), and wasting an hour trying to determine why the I2C3 port was not talking to a device.

Hello, ST CommunityI’m currently working with the NUCLEO-WB55RG board to enable BLE communication.Initially, BLE advertising worked perfectly when the board was powered via USB (connected to a PC or 5V Adaptor). However, now BLE advertising do not start, when I power it via USB - 5V adapter. The 5V adapter is not the issue — it’s a stable power source rated at 5V / 3A.I powered using CN15(ST-Link 5V-usb) in both cases before and now. System setupBoard: NUCLEO-WB55RGExpansion board: X-NUCLEO-NFC08A1Initialization sequence in main.c:int main(void) { HAL_Init(); MX_APPE_Config(); SystemClock_Config(); P

Hey guys. I recently got a nucleo wba55cg board into my hands and tried to finish the ble app youtube tutorial, but it didnt work. A led was supposed to be blinking to indicate that the device advertices for a bl connection, but that didn't happen. I also couldn't find the board on the available bl devices. What i did step by step1) Downloaded cubeIDE 1.19 (mx 1.15) and wba_fw1.8 since 1.8 requires MX version 1.162) Downlaoded the ble p2p server example from here 3) Chose to open a Cube MX/IDE .ioc file 4) Changed device and advertising name to WPAN_MOOC5) Built the project6) Flashed the project to my deviceAgain, no result whatso ever. I tried to open a serial terminal and reset the nucleo board, to check the logger. It seems that everything initializes fine, but no actual output abo

Is it possible to add MotionFx to an STM32WB09TEF7TR MCU?According to the table on page 6 of this document:https://www.st.com/resource/en/brochure/sensor_libraries_software_pack_for_stm32cube.pdfMotionFx is available on Cortex M0+However when trying to add this in CubeMx I get the warning "This component cannot be used as it has device or context compatibility issues. 

I updated The FUS of my STM32WB55 Nucleo Board to FUS v2.2.0.0 and the BLE Stack to v1.24.0.3After this change Flash erase operations fail at the call of `SHCI_C2_FLASH_EraseActivity` with the error code `SHCI_FUS_CMD_NOT_SUPPORTED`Additionally BLE does not advertise anymore.The log from the `Read FUS infos` returns some warnings:notably:10:35:12 : Warning: Option Byte: nSWboot0, value: 0x0, was not modified. 10:35:12 : Warning: Option Byte: nboot0, value: 0x1, was not modified. 10:35:12 : Warning: Option Byte: nboot1, value: 0x1, was not modified. 10:35:12 : Warning: Option Bytes are unchanged, Data won't be downloadedThe entire log:10:35:12 : Warning: Option Byte: nSWboot0, value: 0x0, was not modified. 10:35:12 : Warning: Option Byte: nboot0, value: 0x1, was not modified. 10:35:12 : Warning: Option Byte: nboot1, value: 0x1, w

Actually i tried to upload a custom frimware as per tutorial given in the Lora e5 mini documentation everything is going fine but when it came to changing the RDP level from BB to AA in the post i just changed the level fro BB to AA and clicked apply after changes the module got disconnected and that is the first and last time my board connected to my cube programmer after that i can't connect my lora e5 mini to my cube i tried every method by under reset option and one thing i cannot access the boot0 pin in this board so i cant try this method if any one faced this problem and solved it can you give me solution for this problem 

Hello there,We are working on a project that includes a STM32WB5MMG in a custom board and we would like to update via OTA our firmware application, as well as the BLE stack and FUS. Our project is based on the P-NUCLEO-WB55.Nucleo 2 Images. This project defines two regions (slots) in the flash, one used to store the firmware to run and the other as a storage area for the new firmware image sent via OTA. The question here would be if we update either the BLE stack or FUS if they also have a separate storage area beyond the SFSA address (the start address where the current stack and FUS are stored) or if a flash region between the end of slot 2 and the SFSA address must be reserved as temporary storage for the new stack/FUS image.Thanks in advance

I am working on custom evk of STM32WB05KZ sdk(stm32cubewb0-v1-3-0) on STM32CubeIDE_v_1.19.0 and STM32CubeProgrammer and trying to redirect logs on UART1 through __io_putchar/_write. It is working with Examples(GPIO_EXT, I2C, ADC, etc) but while running BLE(Any of it) section from Applications it is not giving any log through UART/Virtual COM Port. Below is the refrenced code of my main.c:   /* USER CODE BEGIN Header */ /** ****************************************************************************** * @file : main.c * @brief : Main program body ****************************************************************************** * @attention * * Copyright (c) 2024 STMicroelectronics. * All rights reserved. * * This software is licensed under terms that can be found in the LICENSE file * in the root directory of this software component. * If no LICENSE file comes with this software, it is

Hello community,I recently tried to flash the BLE_SerialCom_Central example code onto the STM32WBA55 board. During the debug session, when I clicked the 'Suspend' button, a number of messages appeared in the debug window. I took a screenshot and attached it. I'm still struggling to find a solution to flashing the example code.It would be great if someone who has encountered this issue before could give me some advice.Best regards.

I have NUCLEO-WB05K/NUCLEO-WB07CC/NUCLEO-WB09KE only the NUCLEO-WB09KE can be connected to with Software Reset mode. The NUCLEO-WB05K/NUCLEO-WB07CC boards have the above error on connect. The Hardware Reset mode doesn't work with the NUCLEO-WB09KE (or the other boards). All STLink firmware up to date - not many jumper options to get wrong on these boards.  Windows 11.

Hello,I am working on a Zigbee project for my school and i have never worked with any form of wireless communication. I managed to flash the Zigbee_OnOff_Server_Coord application on my nucleo board and the Zigbee_OnOff_Client_Router on my USB dongle. And when i click on the dongle button the led on the nucleo toggles, that alone works just fine.  But for my project i need to connect an Aqara Door and Window Sensor to my P-NUCLEO-WB55. When i click on the "pairing" button on my sensor even tho i am able to connect it with the nucleo i have no idea on what to do after that, because when i toggle the door sensor state (manually open/close the sensor) nothing appears on the terminal.

Split from STM32WB55 - Achieve lowest possible power mode.I am also not able to achieve Shutdown mode in Nucleo-WL55JC1.Instead, I tried with STOP2 mode https://github.com/STMicroelectronics/STM32CubeWL/tree/main/Projects/NUCLEO-WL55JC/Examples/PWR/PWR_STOP2_RTC , but it also gives 2mA. Kindly let me know, How can achieve STOP2/Shutdown mode ?. Thanks in advance!

Hello ST Community,I'm encountering a persistent issue with the Secure Boot and Secure Firmware Update (SBSFU) implementation on the STM32WB55VGQ6. I am using a setup largely based on the official SBSFU examples, but modified for my specific application.The core problem is that the first successful firmware update via YModem works perfectly (signature verification and decryption pass), but all subsequent updates fail authentication, even with the same, correctly signed and encrypted .sfb file.Target and Configuration DetailsTarget MCU: STM32WB55VGQ6Bootloader: SBSFU (Close to standard example, running on Cortex-M4 only).Update Method: YModem over UART @ 115200 baud.Firmware Image: Custom .sfb file, encrypted and signed using the standard provided tools (prepareimage, etc.) with self-generated keys.Initial Programming:UserKey (for