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
..
Hello everyone.I have a question about the STM32WB BLE. I set one device as a server and the other device as a client. In order for the devices to communicate in ST's own software, the client device needs to know the service and characteristic features of the server device. I have run instances of ST but the connection time is too long. Therefore, I made a connection on the address without scanning directly. The connection was made quickly, but it took a long time to receive the service and characteristics. Is there a way to get service and characteristics faster? I am using the following functionaci_gatt_disc_all_primary_services();
Currently I am using BlueNRG M2 which acts as a network co processor which I communicate with my main controller. I have some data processing application for which I have to use other main controller and cannot use the processor of BlueNRG M2 Now, I have to use several features of BLE which are present in STM32WB5MMG module and not in BlueNRG M2 like LE 2M PHY for which I am forced to use STM32WB5MMG.I searched but couldn't find any resource on how to use STM32WB5MMG module as a network co processor only so that my other main controller can work on DSP part while I use STM32WB5MMG only for BLE related application? Is there a way I can use it as a network co processor only?
Hello, we are working on new release of STM32WL "STM32Cube_FW_WL_V1.3.0". release which has introduced changes in RTC driver which we believe is fixed for the issue (RTC loosing time issue STMicroelectronics/STM32CubeH7#24 )But, after running RTC overnight we have seen RTC issue is still persist in different manner this time RTC is increasing timeTest Start time : 17:55:56, UTC time 1670415956Test End Time: 9:48:00, UTC time 1670473080, (57124 Seconds)Difference of UTC time should be : 57124 (1670473080 - 1670415956)But, From attached logs we can see Test End time is 9:48:00 and total seconds are 57135s837 (check last line in logs).RTC had generated 57135s837 seconds instead of 57124 Seconds.So, 57135 - 57124 = 11 Seconds are increased in actual timeRTCTestLogs.txtRTC Driver.zipDriver files are also attached for more details.Can someone please explain how to fix this?
hey there! in a recent video posted to the ST youtube channel about STM32WL rf layout, there's a reference to the existence and availability of four separate reference designs - MB1720, MB1842, MB1791, and MB1792 using STM32WL parts, but it seems none of these are available for access on the ST website yet. I'm interested to see them, because they seem much closer to the cut down approach to the design I'd like to do, as compared to the nucleo reference design which is available.Normally I'd just be doing my own cut down design/layout based on the nucleo design I have been evaluating right now, but if more work is already done on ST's side, it would be really nice if I could get the files to look at and start from there. Also the existence but unavailability of those designs is a little worrying.. are they unavailable because of a problem with the basic approach they follow? if so I'd love to know before I waste a bunch of time prototyping my own similar approach.
Hello,I am playing with NUCLEO-WB15CC board + zephyr + BLE beacon example. After compiling and flashing the example to the board I got "Precise data bus error" during Bluetooth initialization.Because zephyr does not support stm32wb15 out of the box, I added board and dts definitions.Zephyr version: zephyr-v3.3.0-877-g7deecb4e4e1dCopro Wireless Binaries: stm32wb1x_BLE_HCILayer_fw.bin, v1.16.00x08009416 - points to file zephyr/include/zephyr/sys/dlist.h:499, function sys_dlist_removeI tried to playing around with thread stack size but without any success.I was able to compile and run basic examples (LED, Button).
BLE-HID demo of STM32Cube_FW_WB_V1.14.1 not working with Android 13 ?Hello,The BLE_Hid of demo STM32Cube_FW_WB_V1.14.1 does not work with my Android 13 phone at all (services cannot be listed at all in nRFconnect)while it only kind of works with my Android 12 one (I can list the services with nRFconnect but cannot access them with an error BLUETOOTH_PRIVILEDGED required).- STM32CubeIDE Version: 1.12.0 Build: 14980_20230301_1550 (UTC)- STM32Cube_FW_WB_V1.14.1- BLE stack used is stm32wb5x_BLE_Stack_light_fw.bin from the same firmware package, and I have confirmed that it works using other example projects (BLE_Beacon for example)- code is STM32Cube_FW_WB_V1.14.1\Projects\P-NUCLEO-WB55.Nucleo\Applications\BLE\BLE_Hid without any modification- Nucleo board has no modification, and has the appropriate jumpers (tested using other BLE demos)The serial interface of the HID demo (the menu allowing to select mouse x,y,wheel and buttons) works as expected when clicking SW1, and I can change the v
We have 2 devices on one I2C port. We require fast DMA RX for high data throughput. We use circular buffers to shadow the FIFO on each device. We do this all the time with one I2C device. Two devices on the same I2C line seems impossible using the STM32WB5MMMGHx MCU. There is really no way to determine when the first DMA RX is complete. With a circular buffer CNDTR is not usable as an interrupt. If you have done this before and have a solution we would appreciate a comment.
Hi allI am trying to test and implement a multicast LoRa network using the STM32WL.I have been going through the thread: https://community.st.com/s/question/0D53W00001JCdeESAT/has-anyone-managed-to-make-a-working-lorawan-multicast-with-stm32wl-if-so-howHowever I am still lost as to the setup of multicast. Our application does not require FOTA, it only requires to decode a broadcast message. In this scenario whether I still need include and define (LmhpRemoteMcastSetup.c). LmHandlerPackageRegister (PACKAGE_ID_REMOTE_MCAST_SETUP, NULL), if so, where in the init of the project should it be called?can the multicast key be be setup directly through the end node API as opposed to MAC command? (it would be fixed/hardcoded in this case)if the MC keys can be set through the API, would it mean that the MC group setup could be done manually, as opposed to MAC commands? is it possible to be part of more than one MC group ?Kind regards Xarion
I am trying to use as little power as possible, I want my board to wake up every 30 seconds or so, check if battery has been sufficiently charged, if not, go back to sleep, if it has then turn off rtc and do a function. Is it possible to disable rtc whilst running?
Hi Team,I'm using STM32WLE5 MUC for Lora communication (SubGHz_Phy), I want to know is there a way to use Systick instead of timer ?This is because I used RTC to some other use case. kindly share me the way for the same.Thanks,
In STM32WB55 the LSF must be 32KHz or it can be others like 42KHz etc. as well? Thanks.
I want to know maximun number of pairing device information can the STM32WB save.Is regard to device's flash capacity?
Kind folks,STM32Cube IDE newbie here, so please forgive the simple questions.Context:I'm trying to create a multi-vendor testbed and diagnostic environment for Matter networks. In the case of ST Micro products, the thought occurs that the two Thread-capable boards in the P-NUCLEO-WB55 pack could form a minimal Thread network, just chatting back and forth between themselves to provide some RF traffic. Idea is to use the demo Thread_FTD_Coap_Multicast application from the STM32CubeWB firmware (v 1.5.0) sample projects, modified to send a packet to its twin based on a timer (instead of user button input).Questions:Is this a good approach? Can you suggest a better one?The firmware library provides STMCube IDE projects for both boards, under folders labeled P-NUCLEO-WB55.Nucleo and P-NUCLEO-WB55.USBDongle.The former contains an .ioc configuration project, loads and builds easily in the IDE. Can be written to the board's flash from the IDE or the STM32CubeProgrammer. So far so good.But the f
Is it possible to create a project in CubeMX for a concurrent BLE & Thread application for the STM32WB55?My attempts so far only allow for either a BLE or a Thread project (not both together).Thanks
When I create a new project using STM32CubeMX with my board (NUCLEO-WL55JC1), neither defines for PIN labels will be generated in main.h nor is there a BSP folder in the Drivers folder with a xxxnucleo.h containing definitions as I have seen in the examples. I have tried with another board configuration (NUCLEO-C031C6) where label defines were populated in main.h as expected....
Hello,I am trying NUCLEO-WB55RG Matter device over thread example with apple home pod mini (support thread border router and matter) but it fails to commission and connect.I have already flashed "STM32WB_Copro_Wireless_Binaries/STM32WB5x/stm32wb5x_BLE_Thread_ForMatter_fw.bin" on board from repository.Below are versions and git repo I am using.IOS 16.3.1 , iPhone XSGitHub - GitHub - stm32-hotspot/stm32wb-matter-device-over-thread: Matter device over thread for STM32WBI am able to scan QR code and finish all process but at last iPhone shows "Unable to add accessory."I am attaching logs from Nucelo board here. Please letme know if you need anything to help on this.Thank you
While reverse engineering a demo application from ST / Seeed ( Seeed-Studio/LoRaWan-E5-Node at qian (github.com)), I started monitoring all commands and register access from the MCU to the embedded SX126.I see there are writes to register:WR [08E2]:0CWR [08E5]:20Those registers are not mentioned in the datasheet from Semtech, nor the STM32WLE5 datasheet from ST…What is the purpose of those registers ?Why is the SW writing those values ?Why is this not in the datasheet ???
Ive seen this issue in various different forms over the last 2 years and it seems like CPU2 is corrupting the TL_RefTable structure while configuring advertising. We are using v1.15.0 of the stack on a STM32WB55. This happens every few hours in the following sequence.aci_gap_set_non_discoverable(); // Wait 40 seconds aci_hal_set_tx_power_level(1, powLevel); aci_gap_set_discoverable(ADV_IND, RateMin, RateMax, addrType, NO_WHITE_LIST_USE, 0, NULL, 0, NULL, 0, 0); aci_gap_update_adv_data(Manufacturing specific type) aci_gap_update_adv_data(Name) aci_gap_delete_ad_type(AD_TYPE_TX_POWER_LEVEL) // Wait 20 secondsThen the sequence repeats over and over until we get a connection. If I just let it run (over night for example) TL_RefTable gets corrupted and triggers an MPU fault on the next advertising sequence. Why is this happening? What can I do to stop it?
Hi! I have a peripheral that callsaci_gap_terminate(BleApplicationContext.BleApplicationContext_legacy.connectionHandle, HCI_AUTHENTICATION_FAILURE_ERR_CODE)aci_gap_terminate(BleApplicationContext.BleApplicationContext_legacy.connectionHandle, HCI_AUTHENTICATION_FAILURE_ERR_CODE)itself it receives the HCI_CONNECTION_TERMINATED_BY_LOCAL_HOST_ERR_CODE reason in disconnect which I guess makes sense.But the central that it disconnects from will always receive the HCI_REMOTE_USER_TERMINATED_CONNECTION_ERR_CODE 0x13 case HCI_DISCONNECTION_COMPLETE_EVT_CODE: { /* USER CODE BEGIN EVT_DISCONN_COMPLETE */ cc = (hci_disconnection_complete_event_rp0 *) event_pckt->data; /* USER CODE END EVT_DISCONN_COMPLETE */ handleNotification.Reason = cc->Reason; APP_DBG_MSG("\r\n\r** DISCONNECTION EVENT WITH SERVER reason: %x status: %x \n\r", cc->Reason, cc->Status); }Reason will always be 0x13 and status 0x00The devices are flashed with the latest ble binariesstm32wb1x_BLE_Stack_full
The new STM32WBA series comes to complete the STM32 Wireless MCUs portfolio. The STM32WBA series is brings designers the performance, efficiency, and security required for Bluetooth® Low Energy 5.3-enabled applications. Certified for Bluetooth® Low Energy 5.3 protocol, this product series allows non-expert developers to easily add wireless communication to their device, at an affordable cost. Based on the Arm® Cortex®-M33 core featuring TrustZone® technology, the STM32WBA series provides a high level of security, protecting data, customer IP, keys and preventing hacks or device cloning. The STM32WBA wireless MCU embeds 1 Mbyte of Flash memory and 128 Kbytes of RAM. Leveraging the STM32U5 architecture, the STM32WBA series offers the same digital and analog peripherals, suitable for many applications, from industrial, to smart home and consumer markets. STM32WBA enabling features · Support for latest protocol · En
Can you point me to any wireless module out there (WiFi, Bluetooth, Zigbee, whatever).Requirements:Has easy integration with any stm32 MCU with examples in STM32CubeIDE and preferably some community support. I need the chosen protocol to offer certificated industrial gateways with the capability to communicate to an MQTT Broker.I would love the protocol to be WiFi but since ST doesn't support it officially, this way is pretty much burned.Looking forward to your replyGeorge
I have NUCLEO-WB%55RG the VREF+ and VDDA are connected together. Can I use the 2.5V internal VREF for the ADC please?
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.