Get ready for the STM32 Summit 2026 | Online, November 3
Ask questions and discuss STM32 wireless solutions and their implementation for running Bluetooth LE, Zigbee, LoRaWAN applications.
Most recent activity
Hi,I just updated the CubeMonitor/CubeIDE/CubeProgrammer to the latest versions.After doing this my old version of Transparrent Mode (for STM32WB10) does not compile anymore.After creating a new project, and getting it to compile and run. I can now connect to my device through CubeMonitor-RF... sort of.It reads the version information and reports "Command Complet" but it says Unknown device CM4 version: No information CM0 version: No informationand when I try to read the HCI_READ_RSSI, the program freezes completely.The following screenshot is just after connecting.I can debug the code and pause the execution, but it is not in any fault handler.What can be wrong??? It was working under the last version CubeMonitor-RF V2.8.1last version of CubeIDE (before 1.9.0)
Hello,Setup:STM32WB,Wireless Firmware version 1.14.1Wireless Firmware build 1FUS version 1.1.0Working on a custom boardPhone Xiaomi MI A2 Android 10My issue is that my custom device (server) don't accept connection with a phone (client) that is already saved in the whitelist.I followed the tutorial below to configure my device: https://community.st.com/s/article/how-to-configure-the-stm32wb-le-central-client-or-peripheral-server-for-whitelist-operation-part-1?t=1663338701632Steps:1- On my device I start by initializing the BLE, then I clear the whitelist2- On the phone I clear the bond of my device.3- Device: start advertising (aci_gap_set_discoverable(ADV_IND, Min_Inter, Max_Inter, PUBLIC_ADDR, WHITE_LIST_FOR_ONLY_CONN, sizeof(local_name), (uint8_t*) &local_name, BleApplicationContext.BleApplicationContext_legacy.advtServUUIDlen, BleApplicationContext.BleApplicationContext_legacy.advtServUUID, 0, 0);4- With my phone I connect then bond to the device (using ST toolbox last version)
I have a program that builds upon the p2p example.The scanner starts when I press a button withaci_gap_start_general_connection_establish_proc(HCI_SCAN_TYPE_ACTIVE, LE_Scan_Interval, LE_Scan_Window, PUBLIC_ADDR,0x00, 0);If the button is held for 5 seconds after that I want to stop scanningaci_gap_terminate_gap_proc(GAP_GENERAL_CONNECTION_ESTABLISHMENT_PROC)But I will never get out of this function. It stops in hci_cmd_resp_wait(HCI_TL_DEFAULT_TIMEOUT);the termination will work when it is called from a HCI_LE_ADVERTISING_REPORT_SUBEVT_CODE callback.Anyone has any clue of why this is?
Has anyone got a simple example of the steps needed to get THREAD working? I have followed the application notes and cant get things working :( I have got the STM32WB55 nucleo board running with OpenThread FTD CLI example code nicely, but would like to make the same functionality without the examples. From Stm32CubeIDE, I select New Project -> select the same chip that is on the nucleo board. I set SEM/IPCC/Clocks/OpenThread.The first issue is errno is not defined and adding in the C files allows it to compile. extern int errnoThe code just hangs in the main loop. One observation on the UARTS for OpenThread, even when you pick that you dont want a CLI, it still wants a UART to be set in the GUI. Any help would be greatly appreciatedRichard
..
STM32Cube_FW_WL_V1.2.0, lorawan_end_node project:file: lora_app.h has the following line:#define APP_TX_DUTYCYCLE 10000 << meaning 10 secIncreasing the 10000 (=10 sec) does not work; the stm32wl55jc board will not join any longer.What variable can be changed to increase it from 10 sec to a larger interval?Everything I read indicates that the most frequent upload to TTN should be an interval of hours.10 sec is good for testing, but now I am deploying.
Dear all,I develop a LoRa device that is built around STM32WLE5CCU6. In order to certify the product with CE marking from a notified body, I need to have the test reports and the declaration of conformity for STM32WLE5CCU6.Does anyone know where I can find these documents?Thanks in advance.
Hi, im currently working on a project (STM32WL55) where i need to send data via LoRa. I plan to use the SubGHz HAL driver as it seems pretty low level and provides easy usage of the internal subghz spi.While researching, i found AN5406 where it says in page 6 that i need to implement the HAL_SUBGHZ_MspInit function, but not how. In stmwlxx_hal_subghz.c there is a weak function that doesn't do anything, and is meant to be overwritten:/** * @brief Initialize the SUBGHZ MSP. * @param hsubghz pointer to a SUBGHZ_HandleTypeDef structure that contains * the handle information for SUBGHZ module. * @retval None */ __weak void HAL_SUBGHZ_MspInit(SUBGHZ_HandleTypeDef *hsubghz) { /* NOTE : This function should not be modified, when the callback is needed, the HAL_SUBGHZ_MspInit should be implemented in the user file */ /* Prevent unused argument(s) compilation warning */ UNUSED(hsubghz); }In HAL_SUBGHZ_Init it says that the function is meant to Init the low level hardware : GPIO,
Hi,I am using a STM32WB55RG MCU and I flashed a custom BLE_Ota application on it that uses the HSE clock instead of the default LSE and where the user app starts at 0x10000 instead of the default 0x7000.I am using FUS v1.2.0 and BLE Stack 1.13.0.Using the ST BLE Sensor Android application, I can find the board and for most of the images I try, the OTA succeeds completely.But for random other ones (no big obvious differences in the application), the transfer just stalls forever always at the same point, after sending the first 52824 bytes (regardless of the size of the application to be sent). I joined here a screenshot of this screen.It looks like there might be a flash writing issue at this specific flash address (0x10000 + 52824 = 0x1CE58) but for other apps of the same size/logic, it works fine. This is consistent as non-working apps will always fail at this exact point during the OTA transfer and working ones always work nicely until the end of the transfer.Is this a known issue?Be
i'm using stm32wb30, and when i try to debug a empty program with ST-LINK/V2 and i get the following message:
HiI am using STM32WL55I want to download firmware to MCU using system bootloader.I set pin4(PB6) to usart1_tx, and pin5(PB7) to usart1_rx.I installed Flash Loader Demonstrator Ver 2.8.0I set BOOT0 pin(PH13, pin19) to hight and then power up.(of course serial cable is connected with pc )I pressed Next button on Flash Loader Demonstratorbut The following message appears and nothing works.How can I use system bootloader?Please Help me.thank you.
Hello,Our Devices(50 devices) uses STM32WLE5CC and STM32WL V1.0.1 SDK. I have generated code with Lorawan. All system works perfectly for around 49 days, after that all devices get reboots.We found that it happens when HAL_Gettick() overflows(we send HAL_Gettick() value to our server on each uplink).I didn't use HAL_Gettick() function in any other function expect dding this value in lorawan frame , but uses Timer API to create timer and wake device on time.Please guide us how can I solve this issue?Currently can't generate issue again as it needs 49 days to overflow HAL_Gettick(). Is there any method I can set HAL_Gettick() time manually so I can be sure about that.Thank You
The hardware is B-L072Z-LRWAN1 kit.In STM32CubeExpansion_LRWAN_V1.3.1 I can change the Data rate and Tx power.But after update to STM32CubeExpansion_LRWAN_V2.1.0 I can't change data rate and tx power as I want.The data rate I change by edit LORAWAN_DEFAULT_DATA_RATE, LORAWAN_ADR_STATE is LORAMAC_HANDLER_ADR_OFF.static LmHandlerParams_t LmHandlerParams ={ .ActiveRegion = ACTIVE_REGION, .DefaultClass = LORAWAN_DEFAULT_CLASS, .AdrEnable = LORAWAN_ADR_STATE, .TxDatarate = LORAWAN_DEFAULT_DATA_RATE, .PingPeriodicity = LORAWAN_DEFAULT_PING_SLOT_PERIODICITY};#define LORAWAN_DEFAULT_DATA_RATE DR_5#define LORAWAN_ADR_STATE LORAMA
Hello,As underflow of sub-second register RTC_SSR of STM32WLE5CC will takes 48 days.So, please guide us any method, can be used faster overflow of RTC_SSR, in least possible time.Thank You
We have two "P-NUCLEO-LRWAN1" bought several years ago, it is obsolete from ST,I try to play with LoRa, is "I-CUBE-LRWAN" still can work with those kit?
Hi, im currently working on a project for universtiy and im quite new to stm32. I hava a sensor on my board that coummuicates via UART, were it dumps its data once per second. My problem is that the first HAL_UART_RECEIVE works as intended, but afterwards it always instantly times out, seemingly even before the set timout is over. My MCU is a STM32WL55My code is: /* USER CODE BEGIN Header */ /** ****************************************************************************** * @file : main.c * @brief : Main program body ****************************************************************************** * @attention * * Copyright (c) 2022 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 provided AS-IS. * ****************************************************************************** */ /* USER CODE END H
Hi,My custom device with custom firmware don't respond to LL_FEATURE_REQ so the device disconnect.The connectivity part of my project is very similar to the example BLE_p2p_server, the device start advertising and when I connect to it with the mobile app ST BLE TOOLBOX the connection fail, in wireshark I see the master device is sending LL_FEATURE_REQ but the device doesn't respond.Can you please help me as I'm stuck for a week now?I share with you the wireshark logs (remove the .csv extension)MCU : STM32WB55Stack: stm32wb5x_BLE_Stack_full_fw.bin v 1.13.1Thanks by advance for the help.
Hi all, I am new to Lora technology and need some guidance from experts here.I am working on B-L072z LRWAN1 module that allows to transmits messages using Lora. I was able to download and flash the example code available in LRWAN library provided by ST. I can see the messages going out using LED indicator on device as i still don't have my gateway working.I had couple of questions here.1)can i use two B-L072z LRWAN1 devices to achieve point to point communication using Lora?2)if yes,how can i achieve that?Is there any example code for that or i need to change the current example i am using to achieve what i want ?3)My assumption is that if i transmit the message from one device,it should be received by second device.Is my assumption correct?any help will be appreciated.Thanks
Hello,When I try to start a new project with stm32wl MCU, I see that LoRaWAN is locked in cubeMX. When I import one pre-configured project, I see that it is enabled, but I don't know if I have to enable some other peripherals first to enable LoRaWAN and configure it. Can someone help me understand this problem here?Bests,Isaac
Hi there,I am using the STM32WLE4C8 and I am trying to write a safe handler for the NMI interrupt. From what I can tell, the NMI interrupt is triggered by a flash double ECC error, an HSE failure, or an SRAM parity error. All of these are fairly serious and I am not sure of the best way to handle them safely. Ideally, I would like to be able to send an RF message describing the error, but this seems unlikely as it is a complex process and the flash may be corrupt, or the TCXO dead. At a minimum, I would like to write a small log entry to flash. Is this possible? Are there other actions I should be taking alongside this?Thanks,Rebecca
We are starting a project using STM32WB MCU. We would like to minimize the power consumption while in sleep, but able to wake it up via BLE command. From the document AN5071(STM32WB ultra-low-power features overview) it says "Wakeup from this mode can also be performed by the Radio sub-system." But I didn't found any further description or example about the 'Radio sub-system'. Does the 'Radio sub-system' is same as BLE?Is there any document or example we can study?
Hello, I need to broadcast data between multiple STM32WB55 boards in a mesh using Zigbee. So I figured trying to make the APS Message example bi-directional (so both sides can send a request) would be a good starting point. So basicly I copied every function and initialization that was missing on the Coord side from the Router and the other way around, so that both sites should be able to send a request and reply to a request.But every time I try to send a request I get the trace Message:[app_zigbee.c][APP_ZIGBEE_APS_Conf_cb][847] [M4 APPLICATION] APP_ZIGBEE_APS_Conf_cb : Error, APS confirm status = 0xa60xa6 is ZB_APS_STATUS_INVALID_PARAMETER which, in my understanding, could be anything, so this was not really helpfull to me.I tried following the steps but I can't figure out why it comes up. I compared the input data from the example Router side to my copied one on the coordinator and everything seems similiar. I also set the highest debug level and enabled Full_Trace but still n
Hi Sir:I try to builld a project with unicast/broadcast function with custom message payload on NVM example. But, I found that ZbZclMsgClient/ZbZclMsgSever can't use the following code to broadcast message.Is there any issue to broadcast by ZbZclMsgClient/ZbZclMsgSever?Best Regards,Jack Lai dst.mode = ZB_APSDE_ADDRMODE_GROUP; dst.endpoint = SW1_ENDPOINT; dst.nwkAddr = SW1_GROUP_ADDR; /* Coordinator */ APP_DBG("SW2 PUSHED (SENDING GOOD BYE TO CLIENT)"); if (ZbZclMsgServerDisplayMessageReq(zigbee_app_info.messaging_server_1, &dst, &my_second_message, NULL, NULL) != ZCL_STATUS_SUCCESS) { APP_DBG("Error, ZbZclMsgServerDisplayMessageReq failed (SW1_ENDPOINT)"); }
Hi I'm right now using the Nucleo-WB55RG as a Peripheral device to which the central (tablet) connects. I built most of my codebase with the CubeMX Code Generator – that means I defined all of my services and characteristics in the GUI choosing the BLE Server profile.Now as requirements change I need to add the capability of acting as a central device simultaneously.I know there is the option to choose "Router profile" as BLE Application type in CubeMX but that deletes all my settings for the server role and there is no option to define them again for the new dual topology.So my question is: How can I extend the existing codebase by the new central device functionality but keep the possibility to regenerate code with cubeMX. What is the best approach?I already tried to look into the P2P_Routeur example but it helped just a little.Thanks for any help :folded_hands:GreetingBenjamin
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.