STM32 MCUs

Hello all,Anyone successfully implemented the Standby Mode for STM32WBA52/55?  I am struggling going thru the examples and I wouldn't be able to enter the standby mode level.  My board still consume about 70mA when I enter the standby mode.  From the datasheet, it should be under 1uA with SRAM.Thank you.

I have just received 2 NUCLEO-WL55JC1. Upon connecting either one of them via I see The Red (main power) and green LEDs on. The other thre are flashing alternatively (red, orange, blue). I haven't changed the default jumper settings.The following debug probes were found:[0]: STLink V3 -- 0483:3754:0026003A3234510A33353533 (ST-LINK)12:21:32 : STM32CubeProgrammer API v2.21.0 | Linux-64Bits12:21:46 : UR connection mode is defined with the SWrst reset mode12:21:46 : ST-LINK SN : 0026003A3234510A3335353312:21:46 : ST-LINK FW : V3J16M812:21:46 : Board : NUCLEO-WL55JC12:21:46 : Voltage : 3.24V12:21:46 : Unable to get core ID12:21:46 : No STM32 target found! If your product embeds Debug Authentication, please perform a discovery using Debug Authentication12:21:46 : ST-LINK SN : 0026003A3234510A3335353312:21:46 : ST-LINK FW : V3J16M812:21:46 : Board : NUCLEO-WL55JC12:21:46 : Voltage : 3.23V12:21:46 : Error: Unable to get core ID12:21:46 : Error: No STM32 target found! If your product embed

Hi everyoneI am looking for a tutorial on: how to integrate your code in TouchGFX with some used case examples such as ON/OFF control of an LED or sending data over serial port to Putty terminal on PCI am using the following Board:STM32F469I-DISCO

Split from old thread Nucleo-H755ZI-Q How can I resolve ST-Link "No device found on target" error? - which is solved.i am using same mcu i have this error in the begining like target dectection now that target is dectecing problem is resolved but  now getting this issue  STMicroelectronics ST-LINK GDB server. Version 7.11.0Copyright (c) 2025, STMicroelectronics. All rights reserved.Starting server with the following options:Persistent Mode : DisabledLogging Level : 1Listen Port Number : 61234Status Refresh Delay : 15sVerbose Mode : DisabledSWD Debug : EnabledInitWhile : EnabledWaiting for debugger connection...Debugger connectedWaiting for debugger connection...Debugger connectedWaiting for debugger connection...-------------------------------------------------------------------STM32CubeProgrammer v2.20.0 ------------------------------------------------------------------- Log output file: C:\Users\kavya\AppData\Local\Temp\STM32CubeProgrammer_a01920.logST-Link S

Hi, team I previously worked with a SWB (dual core) microcontroller, and I was able to obtain the stack version using the SHCI_GetWirelessFwInfo function. Now, I am working with a SWBA (single core) but I was unable to find an equivalent function to do it. Do you know if there is an equivalent?, I want to know the stack version on compilation time or runtime, it does not matter. Thanks in advance.

Requesting ST to kindly provide a working example for STM32U545 using stand-alone USB HOST MSC to interface with a USB Pen drive. A Tech-Note explaining the code to be added to the various CUBEMX generated files would help.I have been logging to the USB Pen Drive for years using the F105 and F405 series.For battery operated devices I planned to move to U545 expecting a simple code migration but the USB interface has changed from the familiar and simple FATFS.I tried to refer to the available USBX/FILEX samples of various other devices but could not get them to work as many refer OTG types while U545 has DRD types.I referred to various threads on the community.st.com but they trail off without answers.Thanks.

This article documents step by step the changes to be done in a CUBEMX generated U545 project to access a USB Pen Drive using ST Usb_Host MSC and FatFs Working Code for the NUCLEO-U545RE-Q board is available at  https://github.com/NereusF1/stm32u545-classic-coremw-usb-host-fatfsBuilt using embedded software package STM32U5 v1.8 and STM32CUDEIDE v1.19.0This project is tested on the NUCLEO-U545RE-Q board.USB Pen drive must be formatted to FAT32.The classic Middleware versions are ST USB Host Lib V3.5.1. and FatFs VR0.12c (ST modified 2023-08-18). The classic Middleware are copied over from an F439 project built using embedded software package STM32F4 v1.28.31. Create a projectStart a new project in STM32CubeIDE by selecting File → New → STM32 Project. Navigate to the [Board Selector] tab and choose [NUCLEO-U545RE-Q].2. Keep the default board options3. After creating the project, navigate to the [Con

Hi there and happy new year! I am currently trying to develop a dimmable color light with an stm32wb55 (Nucleo Board). Everything seems to work when connecting the device to a zigbee2mqtt server over zigbee. But actually all color server related callbacks are never invoked and i have no clue why. The other clusters are working just fine and the callbacks are called (on/off, brightness). My endpoint setup code: /** * @brief Configure Zigbee application endpoints * None * @retval None */ static void APP_ZIGBEE_ConfigEndpoints(void) { struct ZbApsmeAddEndpointReqT req; struct ZbApsmeAddEndpointConfT conf; memset(&req, 0, sizeof(req)); /* Endpoint: SW1_ENDPOINT */ req.profileId = ZCL_PROFILE_HOME_AUTOMATION; req.deviceId = ZCL_DEVICE_COLOR_DIMMABLE_LIGHT; req.endpoint = SW1_ENDPOINT; ZbZclAddEndpoint(zigbee_app_info.zb, &req, &conf); assert(conf.status == ZB_STATUS_SUCCESS); /* Basic client/server */ zigbee_app_info.basic_client_1 = ZbZclBasicClientAlloc(zigbe

Heyho,not really a bug, but the register ETH_MACCSRSWCRis missing in the struct ETH_TypeDef, in the CMSIS / STM32H7 header files, at least for H723 .. H735.Also checked the github repos.Any specific reason for that?

I'm working on a project based on the STM32WB5MMG module that must support the following three building blocks:ZigBee APS Coordinator - Only APS Layer packets, I dont need nor want the ZCL or any compatibility.USBFreeRTOSThe examples for the STM32WB5MM-DK are non-existent and the only useful examples I could find in the STM32Cube_FW_WB_V1.24.0 repository were for the P-NUCLEO-WB55.Nucleo.After weeks of tweaking and much struggle I was able to create a project with USB, FreeRTOS, and ZigBee APS Coordinator that compiles and kinda works. This is how I did it.First, I created a project for the STM32WB5MMG using STM32CubeMX where I added and configured the USB and FreeRTOS. I Also added "RF" since that is the only thing related to ZigBee you can do there. This project which only has USB runs fine and works well.Then, I took the two P-NUCLEO-WB55.Nucleo projects; Zigbee_APS_Coord and Zigbee_OnOff_Server_Coord_FreeRTOS, and I was able to merge them together

I am working with the STM32U585RIT6 and need to implement a secure firmware update. In my application code, I don’t want to handle flash management or low-level update logic. I only want to generate a secure binary file and perform the update.I reviewed the SBSFU and X-CUBE-SFI examples. The X-CUBE-SFI solution requires a license and an HSM card, which I do not want to use. The SBSFU example available under B-U585I-IOT02A/Projects/Application/SBSFU involves multiple procedures and is somewhat difficult to understand.Given these constraints, how should I approach implementing a secure firmware update?

Hello, Can you please share an example code where active tampering is enabled in Standby mode and tamper event (disconnect loop) is used to wake up the MCU.I would like to know how we can configure the TAMP as a wakeup source during Standby. If you can show configuration in terms of STM HAL driver that would be great. Let me know if you need more context. Kind Regards,

Hi, I’m working with an STM32H7S78-DK board and I want to replace the current display with a new one that has a resolution of 480x272. I’d like to know if this is possible, and if so, what steps or considerations I need to follow to make it work properly. Any guidance on configuring the MCU, adjusting the display driver, or handling any hardware/software changes would be really helpful. Thanks!

Hello,I modified the BLE Beacon example to send 5 beacon packets and then enter into the STOP2 mode. It is possible to wake-up and resend 5 packets when a button is activated. However, when the time is set, the MCU wakes-up, and freeze.The function UTIL_LPM_EnterLowPower() is used for entering low-power, and HAL_RTCEx_SetWakeUpTimer_IT() is used for setting the wake-up time. a few seconds are used as wake-up time. The wake-up is only verified by monitoring the current consumption increased from few µA to approx. 2.5mA after the time is elapsed. Beside that turning on one of the LEDs has been implemented in the RTC wake-up interrupt routine, and one just after the __WFI without it's being triggered.It has not been possible to debug, as the debug does not return until the execution is paused, and when it's paused the PC points on the next line of the __WFI instruction.Do you have any ideas of what the reason can be, or any suggestion on debugging?Best regards,Fatih 

New question = New thread. Split from this post. Hi mƎALLEm, Thanks for the support, I was able to successfully perform UART-based flashing. For the actual use case, I need to flash the STM32F767ZI Nucleo using the CAN interface. I have a PEAK USB-to-CAN converter and an external CAN transceiver and ST-Link V2. According to AN2606 (Table 94), the STM32F767 series supports booting via the CAN2 interface when the appropriate boot pins are configured. The STM32CubeProgrammer User Manual also mentions CAN as a supported bootloader interface. However, in STM32CubeProgrammer, there is no option to select a CAN interface. Does the STM32F767ZI Nucleo actually include a CAN bootloader? Can a PEAK USB-to-CAN adapter be used for CAN flashing, or is an ST-Link V3 required since it provides a CAN bridge? Could you please suggest the correct method or recommended setup for implementing CAN-based flashing on the STM32F767ZI Nucleo? Thank you, Arun_Badiger.  

Hi all,I was doing a firmware update from my raspberrypi to my MCU through I2C, and I facing this write protection issue.On initial flash with swd, I was flashing bootloader + main app to their required locations with their meta data like CRC program length into flash locations 0x08012810, 0x08012820 respectively. I am facing this issue while I try to erase and program new value "Write protection error at 0x08012800 - check flash protection settings".Mcu used : STM32G070CBT6 (F: 128 Kb, R: 36kb), , Page size 2KBOption bytes used : WRP1A_STRT = 0x3f WRP1A_END = 0x00, WRP1B_STRT = 0x3f WRP1B_END = 0x00 

hii am using stm32u585 controller for my project . here i enabled the internal tamper detection using the below code  /* USER CODE BEGIN TAMP_Init 2 */ sAllTamper_inter.IntTamper = RTC_INT_TAMPER_1|RTC_INT_TAMPER_2|RTC_INT_TAMPER_3|RTC_INT_TAMPER_9; sAllTamper_inter.NoErase = RTC_TAMPER_ERASE_BACKUP_ENABLE; sAllTamper_inter.TimeStampOnTamperDetection = RTC_TIMESTAMPONTAMPERDETECTION_ENABLE; if (HAL_RTCEx_SetInternalTamper_IT(&hrtc, &sAllTamper_inter) != HAL_OK) { Error_Handler(); }from the reference manual its mentioned that internal temperature tamper can detect when the temperature range is out of operational temperature and there is no specific data about the tamper triggering temperature range.based on the operation condition as mentioned in the datasheet i varied the ambient temperature  but in both below and above functional range also i cant able to detect the tamper in my device .expecting a answer ASAP since i need to release the product for testing

Board: B-G431B-ESC1OS: Windows 11Attempting to use the Motor Pilot or Profiler but unable to connect. I know I am connected because ST-Link can read the MCU and I am able to program it. From previous posts it seems to be related to the version of MCSDK so I attempted to use 5.4.8, 6.2.1, 6.2.0, 6.1.0, and 6.3.1. Done the obvious restart computer, board, run as admin.Generated Firmware using the MC workbench, ensured Motor Profiler was checked in Application Configuration and uploaded to boardDouble checked to make sure UART was initializedAnother post said to set build configuration to release, didnt work Not sure how to diagnose from here  From the Motor Profiler (Any of them)[INFO] - UART worker: Successfully open port COM6 @ 115200[INFO] - : try to configure the board'From the Motor Profiler (Any of them)[ERROR] - : Failed to discover Board at 1843200 Bauds and 115200 Bauds[INFO] - : disconnect UART START[INFO] - : Disconnected from board[INFO] - : disconnect UAR

I want to measure current draw on a Nucleo-WBA65RI board using a Nordic PPK2 power profiler. I put the PPK2 in ammeter mode across JP2 of the Nucleo board, and loaded the BLE_Power_Central example in IDE. The Nucleo board is being powered by the USB connection st-link. This is following STM32WBA Bluetooth® Low Energy – Power consumption applications - stm32mcu When the firmware runs, I see around 4mA drawn for the first 10s setup time. The the red led goes out, as it enters the measurement time, and yet I still see a current draw of 4mA.What do I need to do to truly measure the current draw of the stm32wba65? 

Hi all,I'm currently designing a board that requires using an stm32h723 with USB HS (I need more bandwidth than FS allows). The stm32h723 I'm using doesn't expose pc2 or pc3, which are needed for ULPI DIR and NXT respectively. Instead, pc2_c and pc3_c are exposed as pins on the chip. These are internally connected to pc2/pc3 internally with an analog switch, but is this really sufficient for ULPI? The datasheet doesn't seem to be clear.The stm32h747 datasheet does specify using ULPI over pc2_c/pc3_c, which makes me think it's at least been considered. I'm curious why it doesn't seem to be specified in the stm32h723 datasheet (either specifying whether it will or won't work)I did find a few forum posts of people using pc2_c/pc3_c with USB, although it seemed like this had issues (including hardware damage, possibly of the analog switch itself).Thanks!

Hello,   I am very heravily struggling setting up my ADC in continmous conversion mode with HPDMA with multipkle channels.   The DMA seems to stay idle, while the SFRs are saying the ADC is running.   Is there a issue in the config of the ADCs?   /* USER CODE BEGIN Header */ /** ****************************************************************************** * @file adc.c * @brief This file provides code for the configuration * of the ADC instances. ****************************************************************************** * @attention * * Copyright (c) 2025 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 Header */ /* Includes ------------------------------

When I use an STM32WB55 as a Central to connect to another STM32WB55 acting as a Peripheral, I find via a sniffer that the Window Size in the connection parameters is 3 (3.75 ms). However, when I connect the same Peripheral with a mobile phone, the sniffer shows the Window Size is 1 (1.25 ms). How can I modify this parameter in the STM32WB55?

I am designing a compact, low power device using the STM32L433.The device is powered by a 1S battery and I use a buck-boost converter (TPS63070) to generate the 3.3V supply.However, at the moment the buck-boost converter is permantely powered (enable pin permentatly pulled high).I use both shutdown and standby power modes, which use WKUP2 (pin PC13) and RTC to wake the STM32.  But I have just noticed the VBAT pin which could potentially reduce power consumption drastically.  In both shutdown and standby power modes, I use RTC and LSE.However, there are two issues I am not sure how to resolve.1. The WKUP2 pin currently uses the 3.3V from the buck-boost converter (I copied the same circuit used on the Nucleo develpment board).  But if I disable the buck-boost converter then there will be no 3.3V supply to the switch for the WKUP pin, so the STM32 would never wake.  The circuit is shown below.. 2. The battery is 1S so could be up to 4.2V, but t

I have a project in which I try to sync my assembly code on a signal on a GPIO, using WFE for minimum latency and jitter.I use a Rust HAL ony for initialisation of the clock and to put some GPIOs into input mode, and one in output mode that I use to check the timings of my assembly code with an oscilloscope.The synchronization works (PA15 in input mode, using EXTI line 15 to send the wake-up event), but the WFE also wakes up at regular interval. Apparently every second when no debuger is connected, and maybe a bit slower when openocd / gdb is connected.I try to understand why it does wake-up, but really can't find anything. Here are the sources of wake-up I checked:- Interruptions:SEVONPEND is zero (gdb) x/t 0xE000ED10 0xe000ed10: 00000000000000000000000000000000 and if I replace the stack with $AAAAAAAAs, I see no trace of an interruption being called when the core wakes up.- Event on EXTI lines:EXTI_EMR1 and EXTI_EMR2 only activate Px15 (gdb) x/t 0x40010404 0x40010404: 00000000000000

 Hi, The STM32G474CEU6 LQFPN48 was previously used in our projects with a 3.3 V supply, where we successfully operated a 25 MHz FL2500326 crystal using 6.8 pF load capacitors, and the crystal oscillation was stable.In the current design, the same controller is powered at 1.8 V for all VDD, VDDA, and VREF+ pins, while using the same crystal and the same load capacitors. However, under this configuration, the crystal oscillator does not start, and no crystal output is observed.As an alternative, we are currently using HSI clock (16 MHz) as system clock in our application. It is observed in other posts that HSI cannot be used for high speed peripherals like USB and Ethernet due to it's low accuracy, and also it varies with temperature. In our application, we are using 2 - UARTs, 2 - I2Cs and one SPI along with few GPIOs. Is it recommendable to run the STM32g474 with 1.8V VDD? Also can someone give advice on the HSI system clock mode?  Please let us know how to sol