Ask questions and discuss STM32 wireless solutions and their implementation for running Bluetooth LE, Zigbee, LoRaWAN applications.
Most recent activity
Hello, I've tried running and debugging the example project for lorawan end node and it gets stuck at waiting for LSE ready when I debug it using JLink. I also have a custom L072 board with sx1276 and the same thing occurs. The devkit is in working order, there is no hardware issues because it works in arduino lorawan example. (https://github.com/GrumpyOldPizza/ArduinoCore-stm32l0/tree/master/libraries/LoRaWAN/examples/LoRaWAN_Join_OTAA)I also have a WL55JC lorawan devkit and it works fine with the official CubeWLAny idea why the official I-CUBE-LRWAN does not run or any suggestions how to get it up and running?
..
I see 2 types of drivers. one are under ll , e.g., "stm32wbxx_hal_exti"and one under hal e.g., "stm32wbxx_ll_exti"Why are there two types for each?Can EXTI C2EMR2 be configured via the hal drivers and not the ll drivers?
The UM2587 User manual, "Getting started with the P-NUCLEO-LRWAN2 and P-NUCLEO-LRWAN3" covers only TTN V2.TTN V2 WILL BE SHUT DOWN NEXT WEEK!Also, it says "By default, the gateway is configured to forward packets to Loriot network server" - I don't think this is true?I think the default is TTN (V2) EU?This video covers re-configuring for The Things Stack (TTN V3) - but only in the US:https://www.youtube.com/watch?v=uJU3YM1MWN4For the EU, I believe the 'LORAWAN SERVER' should be set to eu1.cloud.thethings.networkAlso missing from UM2587 is the importance of checking that the MAC Address is correctly set (this is covered in the video).LRWAN_GS_HF1
hi I was looking for protocol documentation for provided firmware for these devices,the thing is, i cant set up the gateway properly to connect to the Chirpstask server.there is some ACK requested by the server and not provided by these devices, but actually, i am not sure, since it says support Semtech packet forwarder, is there any specific documentation for the provided firmwarethank you in advance
Hi I'm mattehw.When I Tested advertise setting using P-Nucleo-WB55 board, error occurred about advertise max length.so I have question about STM32WB55 BLE advertise setting.I want to use Local Name(10bytes) + 128bit UUID(18bytes) in advertising data(max 31bytes) without scan response.but cant use that because STM32WB55RG basically include Ad flag(3bytes) + Tx power(3bytes) 6bytes in Advertising data packets.*Local Name(10bytes) + 128bit UUID(18bytes) + Ad flag(3bytes) + Tx power(3bytes) = 34bytes.so i want to make to disable Tx_power option as below .*Ad flag(3bytes) + Local Name(10bytes) + 128bit UUID(18bytes) = 31bytes.As the title says, How to disable Tx_power(3bytes) in Advertising data packets?Is that a possible?
I have a custom board running the BLE (full) stack. The application code is written using the Zephyr RTOS. The power source is a CR2032 coin cell battery. After operating for a while (the actual times vary), some units (not all as far as I know) get into a state where I cannot get the device back by asserting the reset signal on the processor. Only a POR will recover the device. Some notes:I've measured the current consumption in this state and it is a consistent 400-500uA. The current consumption increases when I assert reset so I know the reset signal is getting assertedIt does not seem to be going into the bootloader as it doesn't come up as a DFU device over USB.The ST-LINK debugger cannot connect to the target using any mode (Hot-plug, normal, or under reset).How can the chip get into such a state where power cycling is necessary to effectively restart it? Has anyone seen something like this before?
I started my project from scratch in CubeIde. So just select stm32wl55ccu6, choose all necessary peripherals and lorawan. Unfortunately, from scratch, this MCU can't choose only one core option(M4). To be able to use the Lorawan option, I need to IPCC turn it on. I created the project successfully.I stuck hereI found a similar problem on this forum.https://community.st.com/s/question/0D53W00000VgqmvSAB/trouble-with-the-stm32cubewl-dual-core-example-projectsOf course, I can't debug Cortex M0. But it doesn't work in my project. I replaced ***.ld and ***.s files for M0. Would you please reproduce it and give me some hints on how to start Cortex M0 core?My project is available on githttps://github.com/voloviq/stm32wl55ccu6-end-node.git
My company is working on a product based on the STM32WB55, using the full BLE stack, currently v1.11.0. The error described below was also occurring on v1.10.1 previously.As far as the host application on CPU1 knows, the device is advertising successfully. See logs such as:[app_ble.c][Adv_Request][718] Successfully Start Fast AdvHowever, I am never able to actually observe advertisements from a BLE scanning mobile phone app.In BLE debug trace logs, I am receiving the following:[tl_mbox.c][OutputDbgTrace][759] ble evt: 0x10 [tl_mbox.c][OutputDbgTrace][762] payload: 02 [tl_mbox.c][OutputDbgTrace][777] According to AN5270, Table 311 in section 3.1 and Table 315 in section 3.1.4, this signifies HCI_HARDWARE_ERROR_EVENT with error code event_time_overrun, described as "bluecore time overrun error detected". I haven't found any more documentation anywhere about this.Full log posted here: https://gist.github.com/towynlin/2744c2101c4175ab77154ddf1eca6312User @MLancaster posted about the
Hello,We are trying to write(erase) the flash during BLE connection.If we follow the STM32Cube_FW_WB_V1.4.0/Projects/P-NUCLEO-WB55.Nucleo/Examples/FLASH/FLASH_EraseProgramExample the BLE connection terminates immediately (timeout error code).Apparently you have to let the CPU2 know that you are about to access the flash. The only example I found for this is:STM32Cube_FW_WB_V1.4.0/Middlewares/ST/STM32_WPAN/ble/mesh/PAL/STM32WB/pal_nvm.cIt works when BLE is not connected.When there is an active connection the code is stuck in dead-loop on first:while(LL_FLASH_IsActiveFlag_OperationSuspended());(pal_nvm.c line 226).Once BLE device is disconnected, it passes this while.Now... I am trying to erase a single sector, and this happens even before address is given or anything; no prior errors.The Erase is called from main loop handler.CPU2 firmware used is 1.4.0 (latest).Any ideas?Thanks in advance.
I am using hw_timerserver and sequencer for BLE. I added additional tasks to the sequencer for my application. It appeared that my tasks are running much too frequently, so I looked into the clock configuration of the RTC and found that WUCLK was driven by HSE and did not have the WU Clock and WU Counters configured properly. I switched the clock source to LSE, with WU clock & counters set to RTCCLK/16 & 2, for proper operation in Low-power modes. I then found that Systick was slowed down considerably. Any ideas?
I really need to use the SRAM2A that can hold data while in standby mode.But I have a hard time finding how much of the SRAM2A that I can use without meddling with BLE ? I found (STM32WB software architecture AN5289) and the mention about SBRSA But nothing more about the SBRSA address .Any one knows ?And also the correct way to modify the linker script to expand on the SRAM2 ?
Hi everyoneI have ported p2pClient project to a custom board and kept it running for hew hours.I`m using the STM32Cube_FW_WB_V1.7.0 ilbraries and and imported system workbench project.Eveyrthing seems to be working but after 4 hours board was not responsive.There was no BLE server present during my test and below is the call stack where I got into this loop. It`s interesting that normally there is a timeout associated with the call hci_cmd_resp_wait(HCI_TL_DEFAULT_TIMEOUT); //33seconds but I don`t see this being used anywhere. Some backround on the applicationI`m running a bacnet task in the main loop which collects sensor data from LPUART (buffered in thread context) and another sensor data received from p2pServer project but during the test p2pServer wasn`t present as I mentioned above.Does this look familiar , has anyone experienced this before ?Thanks
In the function Ble_Hci_Gap_Gatt_Init(), it stopped at hci_cmd_resp_wait(HCI_TL_DEFAULT_TIMEOUT);And does not advertising any signal.what the problem may be with my board.Thanks.
Hello,I am developing a system using an STM32WB55 Nucleo, such that the STM32 receives data from a Windows application via BLE changing of characteristic value, the STM32 then sends this over uart to an external device which returns an acknowledgement via uart.In receiving the acknowledgement on the STM32 via HW_UART_Receive_IT() and Custom_UART_RxCpltCallback(), I then look to return the data via BLE to the Windows app using Custom_Update_Char() or Custom_STM_App_Update_Char() etc. During this process, the application receives the data via the ValueChanged event, but following this the STM32 locks up. I have narrowed the locking up to be occurring within the hci_send_req function, I believe the hci_cmd_resp_wait(HCI_TL_DEFAULT_TIMEOUT) function is never being released, causing the function to lock.edit : Above function never gets released due to no events being raised, however the outer while loop (while(local_cmd_status == HCI_TL_CmdBusy)) within the hci_send_req function is also nev
Hello,I build my own end node based on STM32WL55CCU6 in the QFN package.During bring up I noticed missing VR_PAVDDPA is available on pin 25.Can someone help me to understand why is missing? I check also on the oscilloscope and is missing too. Nothing happens on this 24 pin (VR_PA). I check soldering and everything looks perfectly not shortcuts or miss connections.Thanks for any help to resolve this problem.BRMichal
I am implementing a bootloader that will support OTA installation of a new BLE stack if needed. I want to be able to command the FUS to install a new stack and I am utilizing the delete WS and FW upgrade SHCI commands to do this. I am always deleting the stack and programming a new stack from scratch (along with erasing the flash). Currently I am programming in the stack .bin file using JLINK or STM32 programming tools and when tell my bootloader (via UART) to do the FW upgrade, a few resets happen and then the status command that comes back is FUS_STATE_ERROR_IMG_CORRUPT. Every time, regardless of how I program the stack or where I program the stack in flash. Ive even tried new, never used boards to ensure that its not something with keys. Is there something that needs to happen to the stack image before it gets programmed into flash? Ive read through AN5185 several times and I am following the instructions.FUS version is 1.2.0
I have created a project in CubeMX with CubeWB. Set the device to beacon mode (UID). On initialization, I can set the NamespaceID and BeaconID. But I do not understand how I can change this data during the operation of the beacon. Please tell me the sequence of actions. Perhaps there is a visual solution?
Hello. When I send data from my phone (ST BLE Toolbox App) to my stm32wb55rg nucleo board the code enter in Custom_STM_Event_Handler(void *Event) function in custom.stm. The description of this function sais that the parameter *Event is the location of the buffer of the event. Im sending 0x1111, but when I display the variable event_pkt im not able to see the value i have set or the direction of the memory of the value. Do you know what could happend?Thank you.
I am using BLE peripheral on STM32WB5MMG module. For some reason the BLE gets disconnects on its own and not able to connect it again when it disconnects on its own. So I want to understand on what event BLE gets disconnects. Is it anyway possible to get events due to which disconnection happens from the firmware itself, since I am not getting disconnection event on the firmware. For now I am using NRF app to connect to BLE and I have enclosed the image on what I have observed on the app. Just wanted to know how can I find reason for disconnection happening through function available in STM32CubeIde.
Hi I am testing STM32WL55.I am testing UART1 of STM32WL55 by referring to SubGHz_Phy_PingPongI can transmit data using UTIL_ADV_TRACE_Send.I tried to receive data from terminal using UART1.But it didnot work.I inserted UTIL_ADV_TRACE_StartRxProcess(TRACE_RxCpltCallback); in SystemApp_Init();TRACE_RxCpltCallback is as belows void TRACE_RxCpltCallback(uint8_t *PData, uint16_t Size, uint8_t Error) { UTIL_ADV_TRACE_Send(PData, Size); }When data is input from the terminal, no data is returned.When a break point is set in the TRACE_RxCpltCallback function, a break is not caught when inputting data.When I set HAL_UART_RxCpltCallback function, a break is caught in HAL_UART_RxCpltCallback function when inputting dataWhen inputting data, Should TRACE_RxCpltCallback run when data is entered? Or should HAL_UART_RxCpltCallback work?Let me know that.Please Let me eplain how to resolve the problem if there are other problems or not1. SystemApp_Init() function void SystemApp_Init(void) {&n
Hello ST - would you please clarify these two errata and share the missing formula from PM0271:Slot guard time (1.25 ms or 1.5 ms?The last sentence of 5.2 specifies a 1.25 ms guard time.5.2.2 specifies a 1.5 ms guard time and Figure 22 shows 1.5 ms guard times.Advertising interval minimum?5.1.1 specifies a random offset of 0..10 ms.5.2.3 specifies a length of 14.6 ms which "cannot be reduced" but only references min/max interval plus 5 ms (i.e. not min/max plus 10 ms).So is the realizable minimum advertising interval 14.6 + 10 --> 24.6 (plus I presume a 1.5 ms guard time, so 26.1 rounded to 1.25 ms multiple, so 26.25).Or is the random delay specified at 10 ms but ST SW truncates to 5 ms, so min adv int that can be realized is actually 14.6 + 5 --> 19.6? If so, would a mandatory 1.5 ms guard time be added to that?Finally, where can we find the formula referred to in 5.4:The following formula is defined:• GET_Master_Slave_device_connection_parameters(Num_Masters, Num_Slaves, Scan_W
Hi, I use an Nucleo-32WL55JC1 with one MS5637 (pressure sensor). (The point is not the precise sensor but the I2C communication. )In CubeMX, I designed the pins : In main.c, I added : I2C_HandleTypeDef hi2c1;And in the main function : BSP_LED_Init(LED3);And in the error handler : In order to see errors without the debeugger.Then, in lora_app.c, #include "i2c.h"at the begging of the SendTxData(): The results : Then, 5 seconds after, the RED LED blinks -> Thus, It's in Error_HandlerBUTif I comment this line : my_ret=HAL_I2C_Master_Transmit(&hi2c1, MS5637_ADDRESS_W, pMS5637_RESET, sizeof(pMS5637_RESET), 50); -> It's work well, I receive messagesInstead of the action 1, if in sys_conf.h I put 1 to LOW_POWER_DISABLE and 1 also to DEBUGGER_ENABLED -> It's work well, I receive messagesThus, I cannot see clearly the problem because each time with the debeugger it is ok but without it it's not ! Thank you for your help
Was anybody able to implement a custom BLE profile for the STM32WB55 using STM32CubeIDE v1.7 (or around) and the firmware package 1.11.1 (or around)? I would like to recreate and make publicly available this workshop. It is out-of-date.
I want to use an STM32WB module as a ble beacon receiver/detector so I can monitor beacons on my PC using a uart or USB vcom? Are there any examples that can help me and if "Yes" where can I find them?
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.