Ask questions and discuss STM32 wireless solutions and their implementation for running Bluetooth LE, Zigbee, LoRaWAN applications.
Most recent activity
We're using the STM32WB55CE across a range of products, using a mostly shared codebase. Thousands of devices deployed and mostly very stable, but one particular device (the one with the largest code base) is causing a lot of grief..After a few weeks of "life", the device will not turn on. Power cycle does nothing. We read protect all the devices so can't attach a debugger (ofc, can't reproduce the issue when not protected, that would be too easy). But we can still read the option bytes and some of the registers. Reprogramming the device ALWAYS fixes the issue: RDP to 0xAA (erase), reprog, all works straight away. But we have no confidence that it will stay fixed.What I can see is the devices are going into LOCKUP with PC 0xfffffffe. I've got a range of theories regarding how this can happen, but not sure if any are correct, these are currently my main two:- a bug in this version of code is causing the flash at 0x8000000 to be erased (we use eeprom flash emulation and have boo
Hi, I'm trying to run BLE_TransparentMode on my STM32WB55VG for DTM purposes. I'm using FUS 1.2.0, Wireless Stack 1.13.2 (stm32wb5x_BLE_HCILayer_extended_fw), BLE_TransparentMode app 1.13.2.I'm building it in STM32CubeIde 1.8.0 with CubeMX 6.4.0, only thing I'm changing comparing to default config is USART-TX pin from PB7 to PA9 (in .ioc file).App works almost fine. It responds for most of the commands with Command Complete but there is a problem while ending TX test.HCI_LE_TRANSMITTER_TEST is sent and I got Command Complete as a result, then I'm trying to send HCI_LE_TEST_END and here is the problem. Response goes back after ~30sec, with Command Complete as result. The same app works fine for my Nucleo Board with STM32WB55 (with the same stack and FUS).Can you help me figure it out what I could do wrong or where to debug?BR,Sebastian
Hello.I have an STM32WB55 pcb that I developed. I have been working with it for over a month now and all was working fine. Today the CubeIDE decided to generate an error (see below):Download verified successfullyFailed to assign value 80037b1, to register 0Failed to assign value 2002fff8, to register 0Failed to assign value 8001390, to register 0Shutting down...Exit.I have an STLINK-V3SET plugged directly into a Windows 11 machine (no hub). I have tried a second board which also worked fine and it too is generating the message. I have closed the IDE, unplugged power from the board and powered down the debugger THEN repowered all, cleaned the project and rebuilt and SOMETIMES it works and SOMETIMES it doesn't. I have been working with this debugger and STM32 products for a while and have not seen this before. Can someone please tell me what to do as we are under urgent development at this end!The application used to go to main() but now when it breaks
Hi,I am using STM32L072 LoRa discovery kit and enabled UART with DMA. Some times my code gets stuck in HAL_UART_Receive_DMA( ....) function at the line SET_BIT(huart->Instance->CR3, USART_CR3_EIE);This is called at the begining of the code. It wont recover at all until i reset the MCU for some number of times.Kindly let me know how shall I resolve this issue.
Hello,I measured the performance of uSD card connected through the SPI on Read/Write operation.The weird thing is that the Block read speed is 3x to 4x slower than the write speed. I'm writing/read 4kB of data and the SD card is formatted with 4kB allocation unit.The SPI transaction of the 4k write is about 5-7ms, when considering the SPI transaction of the block read it takes about 20ms.Does someone have an idea of what the issues can be?
Hi, I am using the NUCLEO-WL55JC1 to send/recv the data via LoRaWAN.The sample code AT_Slave in SDK 1.3.0 worked well when I tested at region AS923. However, I started to test at the region EU868, the device worked until I reset the device.The device restore lora parameters from NVM but it return error when I send data.My flow is:Factory reset to clear data in NVM (AT+RFS)Set region EU868 (AT+BAND=5)Join with OTAA (AT+JOIN=1), I can get the join request on the TTI backendSend data (AT+SEND=5:0:11223344) , I can see the data on TTI backend.Store context data to NVM (AT+CS)System reset or reboot (ATZ), the device shows NVM DATA RESTORED.Join fail (it blocks without any notification like TX on freq 868100000 Hz at DR 0)I tried to disable the force_join, the join returned OK but the AT+SEND return ERROR immediately.Then I changed to the region AS923, my flow worked weill.I traced into the driver LmHandler/LoRaMAC layer, the LoRaMacMcpsRequest returned error status LORAM
I am using STM32WB5MMGH6 as slave and communicating with host using BLE. I would like to ask a question here: He has read AN5270 and is considering a method for the user to detect when data transmission fails due to BLE disconnection etc. during data transmission. However, this is my first time using BLE and STM32, so I can't decide which is better or how to use them. If anyone knows, please let me know.what i want to know is・Notification of completion of data packet transmission from slaveor・Get the status of the buffer sending data from the slave The tool used is STM32CubeIDE, which uses MX to automatically generate the FW. thank you.
Throughout the codebase the PLACE_IN_SECTION macro is used to place bluetooth related static variables into their own sections. I guess this is done increase the isolation from possible errors in other parts of the code.The sections (for example "BLE_DRIVER_CONTEXT", "BLE_APP_CONTEXT") are not mentioned in the linker script, so the linker places them on it's own.Because of this the sections created are not assigned to the .data or .bss segments. This has two implications:Zero initialized static/global variables (that normally reside in .bss) take up equal amounts of ram and flash. (In .bss they actually only take up ram, since it's not neccessary to store explicit 0 initializer values)static/global variables are not initialized at all. Since the sections are neither in .bss or .data, neither zero initialized nor explicitly initialized data sections are copied from flash to ram by the startup code.Especially point 2 is a subtile source of bugs, because initialized global/static variable
Hi,I plan to design and build a soil moisture sensor for our plants at home, based on the STM32WB55 (I need ZigBee / Thread). But I want to build up a prototype by using my STM32WB15 nucleo board and some of these cheap Arduino Soul Moisture PCBs without components to get a sensor field.I saw that STM is providing a touch middleware for buttons and I guess that this middleware can not be used for my purpose. Instead, I want to use the touch peripheral on the MCU and connect it to my STM32WB55 in the following way (the values are from an Application Note and TP1 is my sensor field):Does the touch driver support this scenario and which example can I use for testing?
I'm looking to create a test case to verify that the handling of the interrupt generated by RTC SSRU is working correctly.In the LoRaWAN code base, the SSR time is set up such that the underflow will happen after about 48.5 days.There doesn't seem to be any way to directly manipulate the sub second register, so apart from leaving a device running for 7 weeks, is there any other way to verify that the code is working as intended?Ideally, I'd like to set the SSR to something like 10-seconds to go (1024*10) and then watch it do its thing.Any hacks to do this? Can the SSR be set externally via the debugger?
So I just don't get something in BLE,My service discovery says it is from 0x000C up to 0x0011. my service has 2 characteristics.but then I scan the characteristics in that range (from 000C to 0011 ) and get them but also get an gatt error on attribute 0x0010.
Hello Dear,Was debugging this command today, and unfortunately found it to be working only partly.From what I see, is that the command aci_gatt_disc_char_by_uuid_cp0 occasionally works and occasionally doesn't.Currently developing on the stm32wb55, both for client and server.On my peripheral, I have created 2 services: ( in this order )Service1: Has 2 characteristics: First is secured read + notify+indicate, and Second is secured write.Service2: This is a duplicate of Service1. After Connection: the command works and finds all attributes by their UUID.Next, after MTU exchange, it no longer finds the attributes of the second service UUIDs. Surprisingly, it does still finds the first service IUUIDs.Note: Discover primary services and other discovery command work. Seems like your MTU exchange breaks something. Thank you, and hope to hear from you soon.
Hi there! We are developing a new STM32WL based product that must be compatible with the existing STM32L0 + S2-LP products. It appears that the GFSK data whitening algorithm is different(?). I used an SDR dongle to sniff the raw bytes transmitted over the air. A 4 byte packet is transmitted with the following content (in HEX; before data whitening): PREAMBLE: 55 55 55 55 SYNC: 93 0B 51 DE LEN: 04 DATA: AA BB CC DD The packet transmitted over the air by the S2-LP is (after data whitening): PREAMBLE: 55 55 55 55 SYNC: 93 0B 51 DE LEN: FB DATA: 4B A6 56 30 The packet transmitted over the air by the STM32WL is (after data whitening): PREAMBLE: 55 55 55 55 SYNC: 93 0B 51 DE LEN: FB DATA: 2D 03 95 6A So the LEN field is correct but the DATA is different. I have looked at section 7.10 of the S2-LP datasheet and section 6.2.3.4 of the SX1261/2 datasheet but can't figure out the difference. The STM32WL whitening seed is set to 0x1FF (alll ones) w
..
Hello, I'm looking for the declaration of conformity document for the P-NUCLEO-WB55 pack [MCU STM32WB55RG (Nucleo68) and MCU STM32WB55CG (USB Dongle)]The document I need should reference the RF standards that the product is in compliance with.I checked the documents on the product page, but I couldn't find any useful documents.
Hello!I need your help in finding a way to know if BLE advertising is active.Thank you
hey!someone can help me to understand and make changes on the server dongle and client dongle on stm32wb55 ? thankyou
I am using STM32WB5MMGH6 as a slave and communicating with the host using BLE.The question I would like to ask here is is there a way for the user to detect when data transmission fails due to BLE disconnection, etc. during data transmission?The tool I use is STM32CubeIDE, which automatically generates the FW using MX.Thank you.
Following section 4 in UM2587, I've connected an FTDI UART-RS232 adapter to the I-NUCLEO-LRWAN1 sensor board to read the APPEUI but I don't get any response. I've also tried reading from memory 0x08080000 of the NUCLEO-L073RZ board, but I only get zeros. I've tried flashing the L073RZ with the AT_Master demo project from the STM32CubeExpansion_LRWAN_V2.1.0 firmware, following UM2073, but It's still not working. Should I be able to use AT commands via UART on LPUART1_Rx/Tx independent of the firmware on the NUCLEO-L073RZ ? What changes do I need to make to the AT_Master project to make it work ? I think the AppEUI for example, should be populated automatically into memory based on internal memory of the I-NUCLEO-LRWAN1 ? Or do I need to call the functions LoRa_SetDeviceID() and LoRa_SetAppID() to populate memory 0x08080000 on the L073 ? I think the documentation could be more "beginner friendly" as most people buy demo-kits to get a minimum working example that you can m
I understand that C2 manages the power state automatically. I have confirmed this using the Cube power monitor utility, seeing that when there's no RF activity power draw on an the st32wb55 nucleo eval kit falls below 3uA. This was done with a simple Cube generated application in peripheral mode with library v1.17 - had to disable all debugging and debugger support in app_conf.h - as well as correcting the "bug" in line 178 of the linker script -> "*(MB_MEM2) ;"My problem is that after integrating the stack into my proprietary application - not using the library schedular, I cant get CPU2 to enter STOP mode: EXTSCR->C2STOPF = 0x1My application completes stack initialization and start advertising. My schedular enters wait state so C1 enters stop mode but not C2. Even if I initialize the stack without advertising start or call aci_gap_set_non_discoverable(); C2 never enters stop mode.What are the pre-requisites for C2 to enter stop mode ? How can I "force" RF activity halt on C2 ?
Board: STM32WB55Software: RTC and BLEHello,I am trying to get a project set up on the above board. It needs BLE, USB and RTC seperately. I have the USB running with Bluetooth now thanks to a relatively recent post offering a means to fix the incompatability. Now, I need to get a date running on my RTC but as the init code of bluetooth uses the RTC timing, this does not seem possible (without of course adding a seperate clock chip into the project). So, is there a way to init BLE from another internal timing source?Thanks
Hello,I've got an issue with STM32WB55(ZigBee) reporting routines. I've successfully registered 3 servers(temp_meas_server_1, temp_meas_server_2, water_content_server_1). I can easilyread the temperatures and the humidity from my ED using another ED (address0x0000). The attributes data is refreshed every 1 second.Unfortunately, there is no way to enable the BDB Reporting. The attribute list is as follows:static const struct ZbZclAttrT ZclTemp_AttrList[] = { { ZCL_TEMP_MEAS_ATTR_MEAS_VAL, ZCL_DATATYPE_SIGNED_16BIT, ZCL_ATTR_FLAG_REPORTABLE, 0, // custom size NULL, &nbs
I have a problem with STM32WB55 USB dongle Nucleo. After adding some code (according to: AN5289 Building wireless applications with STM32WB series MCUs, , https://wiki.st.com/stm32mcu/wiki/Category:Bluetooth_Low_Energy, https://www.youtube.com/watch?v=7_wBH7mTQ2g&list=PLnMKNibPkDnG9JRe2fbOOpVpWY7E4WbJ-) Nucleo board randomly stops appearing in available Bluetooth device list after reattach to PC USB port. I have to then plug/unplug this device as many times as I will see device on Bluetooth device list. I enabled log tracing BT Application stack and the logs are the same with discoverable BT device on available BT device list and when the device is not discoverable (even if the App stack log says otherwise). Log below. [app_entry.c][APPE_SysUserEvtRx][360] Wireless Firmware version 1.16.0 [app_entry.c][APPE_SysUserEvtRx][361] Wireless Firmware build 4 [app_entry.c][APPE_SysUserEvtRx][362] FUS version 1.2.0 [app_entry.c][APPE_SysUserEvtRx][364] >>== SHCI_SUB_EVT_CODE_RE
Hello! Is it possible to connect stm32wb55 dongle to multiple servers without using a smartphone app???so i can get data from servers and see it on terminal over usb , like Realterm???
WATCH ON-DEMAND | STM32 Summit 2026
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.