STM32 MCUs Wireless

Hello,I am having some hard time to connect my nucleo-wl55jc1 to any LNS, even though i checked that Device, Join, and App EUIs are all correct and there is no mismatch, but whichever LNS I try, I always get the same result First, I tried with an indoor RAK gateway, these gateways use MAC version 1.0.3, and the nucleo example uses version 1.0.4 Then I tried using MeteoScientific LNS and Helium network, could not join as well. Finally I tried to connect LORIOT to my RAK gateway, and they successfully connected, but still the nucleo could not join the server, and the gateway did not transfer any packets. Even though the steps are fairly simple, I don't know what is the problem here     what is the meaning of "Event received: RESET" in the nucleo serial logs?

I have been working with the single core LoRaWAN_End_Node example application on a B-WL5M-SUBG1 board with good success.  With STM32CubeMx v6.16.0, WL Firmware 1.4.0, I see a current draw of under 2uA between transmissions.Last week I upgraded STM32CubeMx to v6.17.0 which in turn upgraded the WL Firmware to 1.5.0, changed the end node example to use the LBM library rather than the LmHandler for managing the radio, and changed the example application name to LoRaWAN_End_Node_LBM.  The application functionality is good but the power consumption jumped to around 80uA between transmissions.In both cases I configured pullups in the USART2 pins (PA2, PA3).I can alternate between these two versions of the application on the same board and the results are very consistent.Has anyone else seen this and does anyone have any suggestions?

 Hello,I am currently developing a project that requires an ultra-low-power BLE-based indoor localization tag. The device should periodically wake up and advertise, remaining in standby mode (targeting approximately 500 nA to 1 µA) for about 90% of the time. I am using NUCLEO-STM32WBA65RI.For an initial test, I plan to configure the system to stay in standby for around 5 minutes, then wake up and advertise for 30 seconds.I have already studied the documentation regarding STM32 low-power modes and reviewed examples such as the Heart Rate application, where BLE is used together with low-power modes. However, I still have some doubts.From my understanding, these examples are designed for continuous radio operation and rely on SRAM1/SRAM2/RADIO retention, which increases power consumption. It also appears that some internal mechanism - possibly the UTIL_TIMER based on RTC or the 2.4 GHz radio timer - is responsible for periodically waking the system to handle BLE activity. Could you c

 Hello,I am currently working with the NUCLEO-STM32WBA65RI. My main goal is to place the board in Standby mode and periodically wake it up to perform BLE advertising (as a Peripheral), while still allowing it to handle a possible connection request from another device.So far, I have followed the "Standby with RTC" example to implement low-power operation. I would now like to integrate the BLE stack to enable advertising during the wake-up periods. The intended behavior is for the device to sleep for 1 minute, wake up via the RTC, perform advertising for a short duration, and then return to Standby mode.From the documentation, I understand that the radio and Link Layer must be in deep sleep for Standby mode to be properly achieved. Could you provide some guidance on the correct way to ensure this state? Additionally, what happens if the radio is not in deep sleep when attempting to enter Standby mode?Best regards,

Hello, I am currently working with the NUCLEO-WB05KN1 development board (STM32WB05KN MCU) and I would like to implement FOTA (Firmware Over-The-Air) / OTA update over Bluetooth. However, I could not find any clear reference documentation, application note, or example project related to: Bootloader implementation for OTA Memory partitioning (dual bank / slot usage) BLE-based firmware update flow Any official FOTA example for STM32WB05 series I checked the datasheet and reference manual, but there is no clear explanation of: Whether a built-in/system bootloader supports OTA via BLE How to structure the flash (bootloader + application separation) Any middleware/library support for firmware update Currently, my memory usage is: FLASH: ~34% RAM: ~49% So I still have space to implement a custom bootloader if needed. My questions: Is there any official ST example or application note for OTA/FOTA on STM32WB05KN? Does STM32WB05 series support BLE OTA natively (like STM32WB55)? If not, wh

Title edited to clarify that this refers to a NUCLEO-WBA65RI board.Hello, I am currently using STM32WBA65RI with Standby mode. According to datasheet, this mode should be able to reach 120nA current consumption with the 16 GPIO wake-up pins (RTC disabled). However running the Standby example and shutting down the RTC I am still getting 3uA of current consumption. What can I do to decrease the current consumption up to the nanoA?Best regards.

Hi,  I am using STM32WBA55G-DK1 as a BLE TMAP Peripheral, I have a transmitter, which is transmitting 4 channels/subgroups of data. But the device is stucking at Syncing PA, but when the same is given with 2 channels(BIS), I am able to to connect and listen the music. What are the changes to be made to avoid this issue.   Thank you

I am working with the STM32WB5MMG and implementing firmware updates using OTA. For testing, I am using the ST BLE Sensor Android application. What I Tested I first tested OTA using the example projects available in the STM32CubeWB firmware package: Heartrate_ota P2PServer_ota Both examples work correctly. I can: Flash the example firmware Connect using the ST BLE Sensor app Upload another firmware via OTA successfully My Custom Firmware After verifying OTA with the examples, I created my own firmware that includes: Custom BLE service Custom characteristics Custom UUIDs and device name When I upload this custom firmware via OTA from the example firmware, the update completes successfully and the device runs my application correctly. Problem After my custom firmware starts running: The device no longer appears in the ST BLE Sensor app as OTA-capable. I cannot upload another firmware via OTA. The device does not advertise as an OTA device like the Heartrate_ota

Hello. We are developing a p2p application using two Wio-E5 mini modules based on stm32 WLE5JC.The problem I'm facing is HAL_DELAY not working. I created the project, chose HSE, LSE, then SysTick, and then after I selected SysTick, HAL_IncTick() was well declared in SysTick_Handler, and I also checked NVIC. But when I do HAL_GetTick() at any moment, I get zero. Isn't there a problem with this??The Ping Pong example also uses HAL_Delay, but I cannot understand why this happened.  This is very critical for my project becaude when i set modem state in RX, it call timeout in next loop. please help me

I want to disable the AGC and use supply manual attenuation values.Disabling the AGC is pretty straight forward, I just set the AGC_EN bit in AGC0CTRL to zero.This works fine, but the gain/attenuation is fixed at the reset value and I'd like to use a custom value.To set manual attenuation values, I suppose I need to write them to the AGC_ANA_ENG register.However, i noticed something weird: This AGC_ANA_ENG register is not present in the driver files. Its not mentioned anywhere and in the MRSUBG register definitions it is listed as "Reserved". The "Description of STM32WL3 HAL and LL drivers" pdf (UM3438) even lists a couple of LL-functions to modify it, such as LL_MRSubG_SetAgcForceGains, but they exist nowhere in the driver files.Why is this register not mentioned in the official driver files and why dont the LL-methods exist?

Hi together, I have been developping a simple BLE application (that I can attach eventually) on the STM32WB55RG P-Nucleo This application combines BLE + USB Device (FS) But after I upgraded the BLE stack firmware from: FUSVER:1.2.0.0STKVER:1.13.2.2STK@:80CF000FUSOP:3.1.0 To: FUSVER:2.2.0.0STKVER:1.24.0.2STK@:80D0000FUSOP:3.1.0 Then I can no longer get any BLE connection nor bonding to my board, using a smartphone.  I'm very suprised of that.

The STM32WB55 it will jump to the SysTick_Handler interrupt handler routine after we have configured the clocks and the RTC and then enable the interrupts. I don't understand why this is happening. I have checked the following registers:SysTick->CTRL->CLKSOURCE is set to processor clockSysTick->CTRL->TICKINT is disabledSysTick->CTRL->ENABLE is activeShouldn't the interrupt have been disabled by setting SysTick->CTRL->TICKINT to '0'?

Hello, I am using different ST MCUs from few years and already have a wide set of development boards, tools and JTAG emulators and so far did not experienced any troubles to attach new board (even custom made) to CuveIDE and to flash and debug my solutions... until this week.I've deceded to get some more experience in low power SubGHz solutions from ST and ordered two NUCLEO-WL33CC1 development boards (Mouser store) and also some Chinese modules based on STM32WL33 (AliExpress).Now I have few different STM32WL33 based boards and 3 different available debug interfaces - J-LINK (stand-alone), ST_LINK V2 (stand-alone) and ST_LINK V3 (embedded in NUCLEO-WL33CC1).The problem is that there is no any combination of boards and JTAGs that can connect to STM32CubeIDE.So far there is only one partial success - Using STM32CubeProgrammer + ST_LINK V2 and Chinese modile - I can connect, flash and verify some ELF file: 08:47:13 : UR connection mode is defined with the HWrst reset mode08:47:1

hello everyone, i am a beginner in STM32cube. i was working on board Nucleo wb55rg. and following this tutorial STM32WB Getting Started Series: Part 12a, STM32CubeMX & STM32CubeIDE lab. Introduction, and it said on 2:33 that i need to activate "system core>IPCC and enable both interrupt". i am using STM32CubeIDE 1.5.0 and it does not show IPCC option on it .   any help and guidance is appreciated, thank you

HiIf I develop an application using the STM32WBA25 MCU with BLE, ThreadX, and USBX, is the RAM size sufficient?

Hello everyone!I am trying to get all services and characteristics from steval-stwinbx1 board running FP-SNS-Datalog2 function pack. Here's simple program I wrote:import asyncio from bleak import BleakClient MAC_ADDRESS = "DA:3E:83:DD:30:F8" async def discover_services(mac_addr): async with BleakClient(mac_addr) as client: for service in client.services: print(f"\n[Service] {service.uuid}") print(f"Description: {service.description}") for char in service.characteristics: print(f" |") print(f" +-- [Characteristic] {char.uuid}") print(f" Properties: {', '.join(char.properties)}") if __name__ == "__main__": asyncio.run(discover_services(MAC_ADDRESS)) I expected to get services listed by nRF Connect app.But the program output is empty. Why? PS: I have done some research and experiments. I have tried running same script on linux and it ran perfectly (I used 2 machines: same machine (dual boot) and raspberry pi). I have noticed that board crashes if you are trying to

Hi everyone, I am working on a Beacon project using NUCLEO-WB05KN. My goal is to broadcast Eddystone-UID and allow a connected phone to update the Namespace ID and Instance ID via GATT characteristics. The Setup: I have a Custom Service with two characteristics: Namespace (10 bytes) and Instance (6 bytes). The device broadcasts Eddystone-UID correctly in connectable mode. I’ve added the GATT_NOTIFY_ATTRIBUTE_WRITE (0x01) mask to both characteristics. I’m using hci_init(hci_user_evt_proc, NULL); for event handling. The Problem: When I write a value from the nRF Connect app, the write is successful on the phone side, but the aci_gatt_srv_attribute_modified_event callback is never triggered on the MCU side. I have disabled EnterStopMode() to ensure the MCU stays awake. I have tried implementing the callback in both app_stm32wb05n.c and stm32wb05n_events_cb.c (overriding the WEAK function), but still no luck. My Device_Init Code: C   /* Namespace Characteristic *

Hello, I'm using 2x NUCLEO-WB55RG boards with the unmodified BLE_MeshLightingPRFNode example from STM32CubeWB V1.24.0. Setup:- BLE Stack full v1.13.2.2 (stm32wb5x_BLE_Stack_full_fw.bin)- FUS v1.2.0- Provisioned with ST BLE Mesh app (tested on both iOS and Android)- Both nodes subscribed and published to Default group (0xC000)- Both nodes have AppKey 00 bound to all models Firmware boot logs confirm:- Relay = Enabled- Proxy = Enabled- Friend = Enabled- PB-ADV = Enabled- PB-GATT = Enabled- Default TTL = 8- Different MAC addresses on each board Problem:1. Sending a Generic OnOff command to the Default group (0xC000) from the app only turns on the LED of the node connected via GATT proxy. The other node never receives the message. 2. SW1 button press toggles only the local LED, never the remote node's LED. 3. It is ALWAYS the last provisioned node that responds. If I reverse the provisioning order, it is still the last one that works. The first provisioned nod

Hello,I am working with STM32WB05KN in beacon mode (non-connectable advertising, legacy advertising).I am configuring advertising manually using:aci_gap_set_advertising_configuration()aci_gap_set_advertising_data_nwk()aci_gap_set_advertising_enable()My advertising data contains only:Flags (0x01)Manufacturer specific data (iBeacon format)  aci_gap_init(PRIVACY_DISABLED, HCI_ADDR_PUBLIC); : : uint8_t adv_data[] = { /* Advertising data: Flags AD Type */ 0x02, 0x01, 0x06, /* Advertising data: manufacturer specific data */ 26, /* len */ AD_TYPE_MANUFACTURER_SPECIFIC_DATA, /* manufacturer type */ 0x30, 0x00, /* Company identifier code (Default is 0x0030 - STMicroelectronics: To be customized for specific identifier) */ 0x02, /* ID */ 0x15, /* Length of the remaining payload */ 0xE2, 0x0A, 0x39, 0xF4, 0x73, 0xF5, 0x4B, 0xC4, /* Location UUID */ 0xA1, 0x2F, 0x17, 0xD1, 0xAD, 0x07, 0xA9, 0x61, 0x00, 0x00, /* Major number */ 0x00, 0x00, /* Minor number */ 0xC8 /* 2's compleme

Good day. I am using STM32WL31 on a custom board.DeepStop mode entry works correctly, but wakeup from PA0 (WakeUp pin) is not reliable or does not work. I used the example code in project:STM32Cube_FW_WL3_V1.3.1\Projects\NUCLEO-WL33CC\Examples\PWR\PWR_DEEPSTOPThe same code I use in my custom board works correctly on NUCLEO-WL33CC2 board (I have tested succefull the code on the NUCLEO-WL33CC2). In my opinion the difference from my custom bord + my code and the NUCLEO-WL33CC2 is the microcontroller; the NUCLEO-WL33CC2 mount the STM32WL33, my board mount the STM32WL31. Code sequence foe enter in deep stop:1. Enable wakeup pin (PA0, PA11 used as wakeup pins are connected by a button to GND). Internal pull-up enabled using LL_PWR_EnableGPIOPullUp on PA0 e PA112. Clear WUF flags3. Enter DeepStop When I press PA0 or PA11 buttons the MCU does not resume execution OR behaves inconsistently, it look like as the micro is in an undefined state.After programmed the micro it seam

I am using a STM32WB05KZ of a custom PDB, and I can not read a correct value of Vbattery.I have programed the ACD (+DMA) usgin CubeMX.  I use DMA to read the analog inputs:ADC_Conv_Cplt = 0; HAL_ADC_Start_DMA(&hadc1, value, 3); uint32_t start = HAL_GetTick(); while(ADC_Conv_Cplt==0){ //timeout if ((HAL_GetTick() - start) > 3000){//wait 3 seconds break; } }; HAL_ADC_Stop_DMA(&hadc1);According de manual, the formula for ADC converted data after calibration is the following: Code = Integer(4096/3.6 * VIN) [clamped at 4095]. The result of conversion from Vbat is 0x271, applying the formula I get 0,549V when the Vbat is 3V.I also use 2 analog inputs in PB2 and PB5 and nome of them read correctly. In other proyects with stm32l105 and stm32wl55 the DMA works. I sure I am doing something wrong...Can anybody help me?Edited to apply proper source code formatting - please see How to insert source code for future reference.

Hi, will ST extend I-CUBE-LRWAN support to include the new MuRata LBAA0QB1SJ-TEMP-EVK? Or offer a ST board based on LBAA0QB1SJ-295? Any suggestion on how to reconfigure the current I-CUBE-LRWAN version to work on the new EVK? We were previously using B-L072Z-LRWAN1. 

Hello, I've been trying to setup bi-directional communication with USB-HID on a custom board with STM32WB55CEU. I can send data to the PC from the STM just fine. My usb stack runs, enumerates and reports correctly. However, when trying to send Data from the PC back to the STM, I always receive garbage packages. Here's my device descriptor for the Outreport: 0x09, 0x03, // USAGE (Vendor Usage 3) 0x75, 0x08, // REPORT_SIZE (8) 0x95, 0x04, // REPORT_COUNT (4) 0x91, 0x02, // OUTPUT (Data,Var,Abs)So 4 Bytes. I also tried this with and without adding a Report ID, which did not change the results whatsoever.I have also tried running the code with defining USB_CUSTOMHID_REPORT_BUFFER_EVENT_ENABLED; both in main.h and in usbd_customhid.c and usbd_customhid.h to no changes.I also tried changing CUSTOM_HID_EPOUT_SIZE to 0x04 and 0x05, same with USBD_CUSTOMHID_OUTREPORT_BUF_SIZE. Including all of the combinations with and without report ID and with and without enabling the buffer define.

I am trying to develop a small scale lorawan app on a nucleo-wl55jc using the application example in stm32cube_fw_wl_v1.5.0 and have spent several hours trying to trace my error/bug in the software. All join attempts fail because the deveui as it appears in the se-identity.h file is ignored and the mcu derived value applied. Tracing this value to the lora_app.c file shows the se-identity.h file is correctly read and the macro expansion appears to give the correct value in the set user credentials section (lines 617-620) but the join is attempted using what I believe to be the mcu derived value. The same credentials work as expected when used under stm32cude_fw_wl_1.4.0 At the outset, I must confess it's 25 years since I did any serious programming so I may of missed something obvious but I would be grateful for any pointers as to why it's failing!  

Hi all, I am currently working with the STM32WLE5JC for a LoRa/LoRaWAN-based IoT node and would like to clarify some points regarding LoRa FHSS and LR-FHSS support. From several discussions in the STMicroelectronics Community, I noted the following statements from ST employees and contributors: “There is no way to activate the frequency hopping as the LoRa stack does not offer this feature on the STM32WL.” “After further investigation, it appears that the Semtech SX1262 does not support LoRa FHSS, (but supports for LR FHSS). This is a hardware limitation rather than a driver limitation.” “There is no reference to LoRa FHSS in the driver code or documentation.” It is also understood that: Semtech SX1262 RF IP (which the STM32WLE5 is based on) does not support LoRa FHSS from a hardware perspective Based on this, my understanding is that: :backhand_index_pointing_right: STM32WLE5JC does not support LoRa FHSS However, I would like clarification on the following: 1. LoRa FHSS Support C