Ask questions and discuss STM32 wireless solutions and their implementation for running Bluetooth LE, Zigbee, LoRaWAN applications.
Most recent activity
Unluckily, I haven't found indications as to which of this functions to use for a basic transmit/receive application. In the HAL documentation and inside the stm32wlxx_hal_subghz.c file the functions are described independently but there is no context for their use. For example, in the case of the function HAL_SUBGHZ_ExecSetCmd it says that it's used to send a command to the radio and although the commands are listed in the stm32wlxx_hal_subghz.h file, I couldn't find what each of them do. In my application I don't need to use RTC and DMA but the code that CubeMX generates doesn't compile if I don't use them because they are required by the timer_if.c and usart_if.c files.On the other hand, I have also tried to modify the code of the SubGHz_Phy_PingPong_DualCore project which is my second opinion because I want to use hal functions. I don't completely understand the code, for example, why are there subghz functions in both core's main.c files if according to CubeMX the subghz periphera
Hello all,I am running a custom BLE application on STM32WB55 and I want to implement low power STOP2 mode because it's the deepest while RF is still alive. The idea is to periodically wakeup, procced some data and go back to STOP2. I may also need to wakeup on a BLE connection request.From my research and what I understund (please do not hesitate to correct me in anyway) : I don't need to care about CPU2 (Cortex-M0+) low power because it will achieve this best availableI need to take care of semaphores when going into STOP2 to synchronize between the 2 cores I've look carefully about the hearth rate project and try to use it as a template. What I've done: I am running on HSE_Sys@32MHz, to be able to use function provide in stm32_lpm_if.c whitout modification.On app_entry.c into MX_APPE_Init():/** * The Standby mode should not be entered before the initialization is over * The default state of the Low Power Manager is to allow the Standby Mode so an request is needed here */ UTIL_LP
Hi, I'm trying to start the zigbee on Nucleo-WB55.After upgrading the FUS to 1.2.0.0 and Stack to 1.16.0.0 without any problem, I get an issue in the running code when it checks the "StackType",it should be 48 or 49 but it returns 0:Tested with two different examples on two boards... What can I check?Thank you, Pierre
Hi All,I have implemented a code using Arduno IDE. In that we are transmitting data at every 5 minutes. For that I am getting sleep current around 6uA. But When I am using STM32cubeIDE to generate same type of code I am getting sleep current around 5mA. How can I reduce this Sleep current. It is very much crucial for my project.Please give your ideas.
..
HelloI have a P-NUCLEO-LRWAN3 kit. I would like to apply some peripheral at Gateway but I didn't find the source code.If I can't get the gateway source code. I would like to get the binary pre-installed on the NUCLEO-WRWAN3 gateway.Thank you.
Hi, I want to choose a ST MCU/MPU and I would like the CPU to have BLE, to be able to run a low power mode (STANDBY), use < 5µA in STANDBY and be able to listen on BLE during STANDBY mode Best is that BLE chip would be in STANDBY as well but listening So MCU/MPU + BLE in STANDBY would use less than 50µA Is there a ST MCU/MPU solution? Thanks,
How to write our own STM32WB BD Address when production? Is there any tool or APIs of Windows to control STM32WB for testing frequency offset/ TX power/ RX sensitivity with 8852.
I'm using a NUCLEO-WB55RG board and if I create a new project in STM32CubeIDE 1.12.0 and enable the STM32_WPAN and HeartRate example it doesn't work because the different buffers that need to be in SRAM2 is not placed there.The app_entry.c defines these buffers like this:PLACE_IN_SECTION("MB_MEM2") ALIGN(4) static uint8_t EvtPool[POOL_SIZE]; PLACE_IN_SECTION("MB_MEM2") ALIGN(4) static TL_CmdPacket_t SystemCmdBuffer; PLACE_IN_SECTION("MB_MEM2") ALIGN(4) static uint8_t SystemSpareEvtBuffer[sizeof(TL_PacketHeader_t) + TL_EVT_HDR_SIZE + 255U]; PLACE_IN_SECTION("MB_MEM2") ALIGN(4) static uint8_t BleSpareEvtBuffer[sizeof(TL_PacketHeader_t) + TL_EVT_HDR_SIZE + 255];The automatically generated linker script contains the following, which ends up placing the buffers in RAM1 if I look at the address at runtime using the debugger./* Specify the memory areas */ MEMORY { FLASH (rx) : ORIGIN = 0x08000000, LENGTH = 512K RAM1 (xrw) : ORIGIN = 0x20000008, LENGTH = 0x2FFF8 RAM_SHARED (xrw) : ORIGIN = 0x2
Hi All,I have implemented EEPROM Emul Middleware in STM32WL project (https://www.st.com/resource/en/application_note/an4894-eeprom-emulation-techniques-and-software-for-stm32-microcontrollers-stmicroelectronics.pdf) in lieu of writing directly in FLASH the NVM Lorawan Context Structure.LorawanEndNode example store the NVM Lorawan Context Structure in FLASH, directly as follow( function OnStoreContextRequest in lora_app.c):if (FLASH_IF_Erase(LORAWAN_NVM_BASE_ADDRESS, FLASH_PAGE_SIZE) == FLASH_IF_OK) { FLASH_IF_Write(LORAWAN_NVM_BASE_ADDRESS, (const void *)nvm, nvm_size); }I changed this function to my own function using EEPROM Emul //store nvm in eeprom writeNVMContext_EEPROMemul ((const void *)nvm, nvm_size);And something similar to restore the context.It is working properly as desired: I store the NVM lorawan context every Uplink/Downlink message. This works for my OTAA session is always ok after poweron/off or hard resets.Save lifetime of FLASH in this case of use:EEPROM Emul: E
I am following this video link showing step by step to create OTA app.https://www.youtube.com/watch?v=mRzZOa3jmuM.I am successfully to create the custom application, download the OTA loader app at 0x08000000, and the custom's app at 0x08007000. The problem I am facing is whenever I sent some data to OTA Reboot characteristic, the custom app is just reset, then go back to the custom app. It didn't enter the OTA loader app. Am I missing something like the erase current app function? I also notice in my custom app, once the ST BLE tool box or ST BLE Sensor app connects to my device, it didn't show the OTA reboot option like when I tried the BLE_p2pServer_ota.
Hello Geeks...Hope all are doing wellRecently, I'm working on STM32WB FUOTAI know the FUOTA terminology of the STM32WB through the application document AN5247Moreover, I have gone through the YouTube Tutorial series of the FUOTA for WB seriesI'm trying to update my application over FUOTA but, some how it's verification always fails and it's rollover to BLE OTA loader app!here are the steps which I'm followingUpdated the linker script as per the "BLE_HeartRate_ota" example commented SCB->VTOR from system_stm32wbxx.c file BLE_CFG_OTA_REBOOT_CHAR set to 1 in ble_conf.hAdded the OTA reboot characteristic (which is working well, and MCU able to reboot during the OTA request) Flashed "BLE_Ota" Firmware starting from 0x08000000 flash memory location Flashed the main application Firmware with OTA enable char. starting from 0x08007000 flash memory location Verified the MagicKeywordAddress address 0x08007140Problem statements & Test procedure 1. Application firmware seems work
Edit: It's always embarrassing when you ask a question and immediately afterwards you find what you where looking for...Please ignore this question.---Original question: I'm starting to work with the STM32WB5MM-DK, but I can't find the schematics. Are they not available yet?For some first visual feedback I wanted to use the RGB LED, but the user manual of the DK says: "In this configuration, GPIO_SELECT2 (PH1) is the chip select for this RGB device on SPI1.The RGB LED is driven by the TLC59731 PWM LED driver from Texas Instruments."Unfortunately theTLC59731 doesn't have a chip select. And the data protocol is not SPI, but some weird "EasySet" single wire interface.So I would like to check the board schematics, to understand how the TLC chip is wired to the STM.
Hi all !Does anyone know if it's possible to port SPI Emulator to the STM32WB5MMG family ? (or have an example of a possible implementation from scratch ?)I would like to implement a simple slow half-duplex master SPI protocol using custom ports.Did give a quick try to adapt the existing library for STM32F but for the moment the compilator mainly complains about this portion of the code (tried to create stm32wbxx_hal_def similarly to what's existing for STM32F series because it doesn't exist in hal library but spi emul needs it)#define __HAL_LINKDMA(__HANDLE__, __PPP_DMA_FIELD__, __DMA_HANDLE__) \ do{ \ (__HANDLE__)->__PPP_DMA_FIELD__ = &(__DMA_HANDLE__); \ (__DMA_HANDLE__).Parent = (__HANDLE__); \ } wh
I have a question about STM32WB55RGV6. I will list my current progress below.- First of all, I will be using the NUCLEO-WB55RG board to use the IEEE 802.15.4 MAC Stack. - I want to communicate with the Xbee S2C (XB24CZ7WIT-004) from Digi to send and receive data via USB UART.- The configuration of Xbee S2C is as shown in the picture below. (PanID : 0x3332, Channel : 0x0C ...)- The link below is the information of Digi Xbee S2C.https://www.digi.com/resources/library/data-sheets/ds_xbee_zigbee?view=fullscreen- The connection configuration is as shown in the "Block Diagram" photo below.- I used the example in the link https://github.com/STMicroelectronics/STM32CubeWB- The current version of STM32WB Copro Wireless Binaries is 1.16.0.- The current FUS version is V1.2.0.0.- "...\STM32CubeWB-master_Origin\STM32CubeWB-master\Projects\P-NUCLEO-WB55.Nucleo\Applications\Mac_802_15_4\Mac_802_15_4_FFD\STM32_WPAN\App:" I modified the "app_ffd_mac_802_15_4.c" file in this path to fix the Channel a
I am getting the following errors when debuging the project from the package. I have the standard package downloaded directly from the official website, I've also done a full chip erease and after this, load the firmware again, and the error persists. I am using the version 2.1.0 of the package.On the following I am putting the error prints.set *(int *)0xE000EDFC=*(int *)0xE000EDFC|0x400set *(unsigned int *)0x40015804&=~0x6Temporary breakpoint 1, main () at C:/Users/eduar/OneDrive/Escriptori/STM32CubeExpansion_LRWAN_V2.1.0/Projects/NUCLEO-L073RZ/Applications/LoRaWAN/LoRaWAN_End_Node/Core/Src/main.c:7373 HAL_Init();
Hey everyone, I am trying to send out two different characteristic notifications, one after the other and I am getting error 0x93 (BLE_STATUS_BUSY) in return for the second characteristic update, It then takes at least 100mS (often a lot more than this) before I am able to update the second notification. I am assuming that this is a limitation of the underlying BLE stack but can't find any information of what causes a busy status.When just updating a single characteristic, I get often get an 0x64 which I can easily recover from by listening for the gatt tx pool available event, however I can't find a way of knowing when the second CPU is no longer busy.Any other tips on optimising throughput when updating multiple characteristics would be greatly appreciated.
I want to use MAC 802_15_4 with other peripherals like SPI2, I2C1 and USB as a CDC device but there is no option in cubemx to generate code for MAC 802_15_4 and i didn't find any application notes to write program for MAC 802_15_4 only i found 2 sample code in Application folder of STM32CubeWb and when i am trying to relocate that sample code to another folder compiler throwing error even i have changed include path and added necessary files and folder in local path.Thanks in advance.
Hi,I am working with a STM32WB55 MCU connected using a STLINK probe (SWD).In the flashing flow, I use STM32_Programmer_CLI to erase the device, put it in FUS mode, update the FUS, update the BLE stack image, and then flash the app image.One thing I realized was that after those steps, I couldn't start the app image without powering off and on the device. No reset, hardrst, core_rst nor anything I could find in the STM32_Programmer_CLI --helpcommand allowed me to launch my app.Is there any way to launch the app without having to manually power-off and on the board?Is it quite annoying to have this extra step in the flow!Kind regards,A.P.
Hi,I am evaluating 2 MCUs (STM32WL54CCU6 and STM32WLE5CBU6) for our new design. I would like to get the receiver sensitivity at the following condition: 2-(G)FSK, BER <1%, 200kbps, 50kHz FDA at 915 MHz, which datasheet don't have. When you have a chance, could you please provide the data at that test condition? Many thanks.
HiWe develop a project on the STM32WB5MMG MCU. We have 2 issues:1. How can we get the actual MTU after the negotiation with the remote client (probably a smartphone) ? We want to support all kind of smartphones including those with small MTU. Do we have to be worried about this issue in case of transmitting too large packets to the client or would the packet be divided into sub-packets automatically ?2. When working with the debugger on both EVB (STM32WB5MMG-DK) and our board is ok, both after disconnecting power and connecting it again, we don't get advertise again. Have someone now what cause this ?Thanks
During testing to see what happens if power is interrupted during various parts of firmware update, I removed power from my test board while updating FUS. Now, when I connect via SWD using STM32CubeProgrammer, it shows the following: When I try to update FUS in this state (writing FUS v1.2.0 to 0x080EC000), I get an error, "FUS_STATE_ERR_UNKNOWN".Is it possible to recover from this state?
I have a burst sampling MCU application that wakes up via interrupt, samples, and should now signal a backend through LoRaWANThe CubeMX skeleton spins up a whole system with sequencer, power mode management etc, which is - did I get this right? - built to wake up periodically on a duty cycle interval.I assume this is probably giving you the best efficiency you can have, but is a bit overwhelming for me in comparison to Arduino-like LoRaWAN stacks which expose simple interfaces like Join, Send and a callback for Rx.I am wondering what would be the most pragmatic way to get my application going without digging too deep in the middleware internals?These are the options I was thinking of:Switch to FreeRTOS, where examples suggest easier task combination. Unsure if Low Power Mode management will interfereUse dual-core STM32WL55x, running AT slave skeleton on the second core for a simple interface. Downside: I planned to target a Seeed E5-mini, which has a STM32WLE5x.Find a simple option f
I am confused because I thought I have read somewhere that on the STM32WL55JC, only the M0+ Core is connected to the RF part and therefore M4 core normally hosts app code, M0+ core the RF part.In the examples I have seen for the Nucleo WL55JC there are mono-core are well as dual-core implementations.So, is the SUBGHZ just a peripherial just any other and its up to me on which core I use it and furthermore, single-core code written for a STM32WL55 would also work and behave similar on a single-core STM32WLE5?
On a custom board, the RED_LED is connected to PA15, which is pulled-up by default (JTDI).The pin has been set to Push-Pull Output GPIO in CubeMX and is initialized to 0.The STM32WB55CGUx was experiencing random resets, until this particular IO was set to 1, line 34 in the code below.Now the code runs fine and is stable.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 */ //SysTick_Config(32000/0); /* USER CODE END SysInit */ /* Initialize all configured peripherals */ MX_GPIO_Init(); MX_ADC1_Init(); MX_SPI1_Init(); MX_TIM1_Init(); MX_TIM2_Init(); MX_USART1_UART_Init(); MX_RF_Init(); MX_RTC
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.