Ask questions and discuss STM32 wireless solutions and their implementation for running Bluetooth LE, Zigbee, LoRaWAN applications.
Most recent activity
STM32WB5MMG�?�STMicro�?�ら�??供�?�れるLibrary,Driver,FUS_fw,BLE_Stack_full_fw,BLE_Otaを利用�?��?��?カスタムプロファイル�?�BLEを�?�載�?��?�製�?を開発�?��?��?��?��?�。�?�れを販売�?�る�?��?�?Bluetooth SIG�?証を�?��?��?��?��?�考�?��?��?��?��?�。QDID170767,160724�?�該当�?�る�?��?�?れ�?��?��?��?プロファイル サブシステム QDID 122688�?�カスタムプロファイル�?��?��?��?�も該当�?�る�?��?��?��?�分�?�り�?��?�ん。教�?��?��??�?��?��?�。
Hi everyone,I use the STM32CubeIDE 1.6.0 and the STM32WL package 1.0.0I am trying to implement the clock synchronization feature but I cannot get the application to be built.I enabled the with the following definition#define LORAWAN_DATA_DISTRIB_MGT 1 in lorawan_conf.hBut while building the project it returns undefined reference of two functions defined in LmhpDataDistribution.hI tried to clean and build again but it doesn't workBoth files (LmhpDataDistribution.h and LmhpDataDistribution.c) are included in the project. Do I miss something?
But we need to increase the memory for CM4, so we modified the files STM32WL55CCUX_FLASH.ld:CM0PLUSFLASH (rx) : ORIGIN = 0x08030000, LENGTH = 64KCM4FLASH (rx) : ORIGIN = 0x08000000, LENGTH = 192KUnfortunately, it stopped working with this definition. Apparently something else needs to be adjusted or what are we doing wrong?
How can I wake up the B-L072Z-LRWAN1 STM32L072CZ PA0 pin when I want to measure the begin and end of a movement plus gathering measurements from the FIFO after one or several FIFO watermark interrupts?Ideally I want to let the STM32 go back into low power mode and let the begin/end of movement and any FIFO watermark interrupt wake up the STM32. There is no reason to not go back to lop power mode when the accelerometer gathers data for several seconds.The problem is that there is only one external wakeup pin on the STM32L072CZ which is PA0 while I want to wake up the STM32 for two different interrupts.I am sure that this is not the first time that something like this is required. There might be a solution already documented or answered before but for now I can't find them.Thanks in advance
Hi, I just found this in the guide (image)
..
I have interesting problem.Custom PCB as master role using SDK 1.15.0.Trying bonding procedure, I find an situatiotion where after ACI_GAP_PAIRING_COMPLETE_VSEVT_CODE event, waiting 100ms (as in "BLE_HeartRateFreeRTOS_ANCS" example) (Ithink it is a mistake or error using that algorithm) and starting disconnect operation calling "aci_gap_terminate()" - the FW freeze and I newer receive an "HCI_DISCONNECTION_COMPLETE_EVT_CODE" event.This log of bonding proc with trying disconnect after ACI_GAP_PAIRING_COMPLETE_VSEVT_CODE like in "BLE_HeartRateFreeRTOS_ANCS" example :-------------------------------------------------------------------------------SCAN START: 1 use white_list: 0 result: 0CONNECT BEGIN: 0 HCI_VENDOR: 0407HCI_LE_META: 0001CONNECTION_COMPLETE wit peer: 0000Bonded=0 SMode=1 SLevel 1HCI_VENDOR: 0C03HCI_LE_META: 0007HCI_VENDOR: 0C03HCI_VENDOR: 0C10HCI_ENCRYPTION_CHANGE: enabled: 0001 status: 0000HCI_VENDOR: 0802HCI_LE_META: 0003HCI_VENDOR: 0401ACI_GAP_PAIRING_COMPLETE: 0000 0
I'm trying to check the dependence of BLE data rate with respect to distance from the board. I runned the BLE_DataThroughput example but I'm having a hard time to interpret the info on the gatt_server terminal (I'm using a nucleo board with a smartphone).1) here I sent the word hello** data error ** N= 4 DataThroughput = 5 bytes/s lost = 116762973 what does lost = 116762973 mean?2) I expected to see a roughly constant value of bytes/s (and higher of course) but it seems that the software just counts out the amount of characters that I send from the smartphone. DataThroughput = 22 bytes/s lost = 0 DataThroughput = 70 bytes/s lost = 0 in this case https://community.st.com/s/question/0D53W00000ElwrQSAR/stm32wb-data-throughput-issues someone got higher throughputs.How to understand this behavior? Thanks in advance.
Beside the MB1791 BOM doubt, there is PCB Layer Stack doubt too.About MB1791 PCB & Gerber Files, there is no Signal copper layout in the Middle Layer-1 (G1 Layer) & Middle Layer-2 (G2 Layer). Why the setting applied 4-layers PCB instead of 2-layers PCB ? Info referring --> STM32WL55CC - Sub-GHz Wireless Microcontrollers. Dual-core Arm Cortex-M4/M0+ @48 MHz with 256 Kbytes of Flash memory, 64 Kbytes of SRAM. LoRa, (G)FSK, (G)MSK, BPSK modulations. AES 256-bit. Multiprotocol System-on-Chip. - STMicroelectronicsPls advise.
Hello all....New to the STM32WL world and trying to understand some things:Could someone point me to the appropriate applications, within the STM32WL Library package framework, for creating a remote control hub that could send a user defined packet structure to various nodes (network would be either simplex or half duplex (call / response)? (I want to use the LoRa phy but not have the restrictions of the LoRaWan protocol as this is a self contained intranet ---- no internet required)Thank you
Hello I bought the P-NUCLEO-LRWAN3 developer board to use as a gateway for lorawan.Only to realise that its meant for 433MHz, and I need 868MHz.As far as can see there is little difference between the 2 versions.Its the same PCB, so I was wondering if I could modify the LRWAN_GS_LF1 to become a LRWAN_GS_HF1.I would just buy the P-NUCLEO-LRWAN2 but its sold out everywhere.Morten, Denmark
The WL product has been around for a while now and I still only see one FCC approved RF module (Seeed )......I had heard that ST was going to produce an FCC module with the WL55 product. Can anyone from ST validate any truth to this and comment on the time frame that we can expect a SoM? I am surprised, that only Seeed has produced modules for sale at this point. Thank you
Hi,Now I am working on I2C sensor (BH1750 sensor) integration with LoRaWAN base firmware(STM32cube_FW_WL_V1.0.0) in RAK module. The controller specification is STM32WLE5JCI had configured the I2C peripheral initialization as mentioned below document.I had configured the I2C sensor data reading function(I2C transmit & receive) as mentioned below document.While I am integrating, I am getting my I2C sensor's data(BH1750's LUX value) by calling the I2C data reading function after the immediate initialization of I2C peripheral.That means, it needs I2C peripheral initialization for every I2C data reading function while integrating I2C with LoRaWAN Stack.But in Embedded program, without LoRaWAN stack, I2C peripheral integration with the RAK module is working fine with the same I2C configuration.I have attached the I2C configuration details & What are all the changes I did for this I2C integration in the below mentioned document.Kindly, Do find the attachment and go-through it once.Kin
Hi All, I am evaluating the usage of the WL55 on a legacy system. Our legacy system is a 2-gfsk with whitening; it relies on 0xAAAAAA preamble frame, but it is detected as 0x555555 by the semtech submodule. This leads to a shift in the sync word and the following payload. Is there a way to change the preamble frame word? K.R.Luca.
Hi Team,I'm facing some trap in the STM32WLE5 device during RTC init, some time RTC initialization works, some time it hangs in generated function "HAL_RTC_MspInit()" during HAL_NVIC_EnableIRQ(RTC_Alarm_IRQn). if any one faced this issue kindly let me know tow it was resolved.Thanks in Advance.
Hi everyone,EDIT: This is on the NUCLEO-WB55RG development boardWas using the board last week without any problems. Started using it this morning and the board boots up, but it cannot connect to the computer to dump code. The chip under the removable shield (I'm not sure whether its the M0 or the M4 chip, I think its the M4) is getting very hot.All the components/soldering/traces look fine so I'm leaning towards internal failure of the chip under the shield. Is there any way I can verify whether this board is broken for good?The LED boot sequence is different (I have two boards), the working board boots as follows:Plug USB in via computer - board powers onLED 6 turns red ONLED 5 turns ONProgram starts and all is fineHowever, the suspicious board boots like so:Plug USB in via computer - board powers onLED 6 turns red ONLEDs 4 & 5 flash on then off x2LED 6 turns red OFF and green ONLED 6 turns green OFF and red ONLEDs 4 & 5 turns ONMCU under shield becomes very hot and cannot
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.
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.