Product forums

Hi everyone,I'm working on a project using NASA's Core Flight System (cFS) running over RTEMS RTOS, and I need approximately 8MB or more of external RAM for the workspace/heap.Currently, I'm using a NUCLEO-H753ZI board (STM32H753ZI), which only has 1MB of internal SRAM. I've been looking for an easy way to add external RAM, but I'm running into some challenges.My questions: Is there an easy way to add 8MB+ of external RAM to the NUCLEO-H753ZI? I've looked into FMC-based SDRAM shields/expansion boards, but I haven't found any off-the-shelf solutions that work well with this board. Is there a shield, module, or expansion board I should know about? If adding RAM to this board is not practical, which STM32 board would you recommend instead? I need: 8MB+ RAM, Cortex-M7 (or similar performance), and preferably existing RTEMS/cFS support. I've seen mentions of STM32H745I-DISCO or STM32H747I-DISCO having onboard SDRAM, but I'd like community input on the best choice. My sta

Hi,I'm working on a battery-powered sensor with STM32L071CBTx (LQFP48).The device cycles between Standby mode (~12 µA) and short Run mode (~250 ms).Reading RM0377 Section 20 (IWDG), I understand that:1. IWDG cannot be stopped once started (only reset can stop it).2. IWDG clock (LSI) runs in Standby mode.I have two specific questions:Q1: Does STM32L071CB support an IWDG_STDBY option byte bit that freezes    the IWDG counter in Standby mode (similar to STM32G0/WB/U5 series)?    If yes, what is the bit name and how to configure it via HAL?Q2: If Q1 answer is "no", what is the recommended approach to combine    IWDG-based hang protection with Standby-based ultra-low-power    operation? Two options I'm considering:        (a) Use LSI manual stop via RCC_CSR.LSION = 0 before entering        Standby (does IWDG still run if LSI is stopped?)        (b) Software watchdog using a basic timer (TIM6/TIM7) refreshed        in run mode, NVIC_SystemReset() on timeout.Best regards, 

I was trying to use the xcube_TOF application inside the st32cubemx for the stm32h7 nucleo board. However, the tof initialisation is keep getting failed. Is it really possible to implement a i2c connection between x_nucleo_53l8a1 and the stm32H7 nucleo board? I tried to implement the hardware connections just like in the stm32nucleof401re.Could anyone please help me with this?

Hi ST team, I am using STM32L4Q5VGT6 I need to use 2xQuad SPI memory. I need a confirmation whether we can use OCTOSPIM_P1_NCS pin from PE11 & PA2 CS-pin as individual cs pin for both Quad memory chip.  Thanks, 

Environment & hardware:STM32F722RET6:LQFP64USB3300EZKSTM32CubeIDE v2.1.1STM32CubeMX v6.17.0Windows 11 OS Description of problem:I am trying to use ULPI with external HS USB phy with the follwing schematic:when calling MX_USB_DEVICE_Init(), it will be stuck at  /* Required few clock cycles before accessing USB PHY Controller Registers */for (volatile uint32_t i = 0; i < 10; i++) { __NOP(); // No Operation instruction to create a delay} /* Core Soft Reset */ USBx->GRSTCTL |= USB_OTG_GRSTCTL_CSRST; do { count++; if (count > HAL_USB_TIMEOUT) { return HAL_TIMEOUT; } } while ((USBx->GRSTCTL & USB_OTG_GRSTCTL_CSRST) == USB_OTG_GRSTCTL_CSRST); return HAL_OK;}in USB_CoreReset(), eventually returning HAL_TIMEOUT. Images of USBx and RCC:USBx before core soft resetUSBx after soft core resetRCC before & after soft core resetMy clock configuration, everything not included in this image is greyed outULPI pins: /**USB_OTG_HS GPIO Configuration PC0

My design uses a STM32H750VBT6 MCU with the USB3300-EZK PHY for high-speed USB. The hardware and software implementations are complete and in general everything works extremely will. The only issue I am seeing is that there are occasional startup problems with the host computer (both Mac and Linux) reading the device descriptor. This occurs about 10% of the time. The Linux error log is: <6>[19177.992026] usb 1-1.1.4: new full-speed USB device number 75 using xhci-hcd<3>[19178.072046] usb 1-1.1.4: device descriptor read/64, error -32<3>[19178.260043] usb 1-1.1.4: device descriptor read/64, error -32<6>[19178.448021] usb 1-1.1.4: new full-speed USB device number 76 using xhci-hcd<3>[19178.528074] usb 1-1.1.4: device descriptor read/64, error -32<3>[19178.716051] usb 1-1.1.4: device descriptor read/64, error -32 A normal connection log as follows: <6>[19166.984026] usb 1-1.1.4: new high-speed USB device number 74 using xhci-hcd<6>[

Hello,I am currently trying to leverage STM32H753 FMC feature to interface with legacy Motorola flexbus style peripheral.I suspect the answer to my question is no but I could not find an explicit statement within documentation saying it is precluded hardware wise :Is there a mode / configuration (down to the registers level) that could allow the write enable signal (WE) to be asserted before the chip select signal (NE) ?Thanks

Hi, If you were to remove the antenna from circuit and transmit on the STM32WL5MOC, would you damage the internal rf power amplifier that transmits the signal due to the signal being fully reflected back to the output of the rf amplifer? Best Regards,Dave

Hello everyone,We’ve been dealing with a puzzling power management issue on our board (battery-powered design). The PMIC (STPMIC1) intermittently enters an unresponsive state that we believe matches the state described in AN5861. We’ve already implemented the supervisory circuit, but in this case it doesn’t have the desired effect. We're about to enter production, and this issue is our final blocker. We’d appreciate any pointers on how to resolve it. Part number STPMIC1BPQR with the AN5861 supervisory circuit fitted EnvironmentSTM32MP151AAB3 The device is battery-powered; the battery is non-removable. The product is charged via a wireless charger (STWBC86). Schematics Please see parts of our schematics attached. DetailsThe unit appears to experience a brown-out/battery protection event. It seems to happen at very low battery levels. The unit sometimes does not respond to the power button afterwards, which essentially means the device is bricked. Putting the device on the charger does n

I’m using SPC58EC80E5 and i wanted to load the files into unit without using JTAG, so that i wanted a Bootloader, How to work on that and if any sample projects are there for reference ? I already searched for this project “SPC582Bxx_RLA Bootloader Test Application for Discovery” it was no there.In fields i should load the project without using JTAG , i have only connection with CAN.

Could you please let me know when STM32 CubeMX 2 is expected to support USB device and host middleware?Also, will STM32H, STM32F, and other STM32 series continue to be supported in CubeMX 2?

Hello, few days ago ST MCU FINDER PC v 6.1.0 stop downloading updates with error message:It's only me, or server problem? Thank you. Regards,Slavomir Tomascik

STM32CubeMX generates incorrect linker script for BKPRAM (Backup RAM) via Memory Management ToolEnvironmentSTM32CubeMX: v6.17.0, see "Memory Management" (Tools > Memory Management) MCU: STM32H523RETx Toolchain: STM32CubeIDE - GNU Tools for STM32 (14.3.rel1)Applied Memory Setup (screenshot):STM32CubeMX generates 3 linker scripts (STM32H523RETX_FLASH.ld, STM32H523RETX_FLASH_MMT_TEMPLATE.ld, STM32H523RETX_RAM.ld). The STM32H523RETX_FLASH_MMT_TEMPLATE.ld is used in the generated STM32CubeIDE project output. Issue 1: BKPRAM memory region has incorrect x (execute) permissionGenerated linker script contains:BKPRAM (xrw) : ORIGIN = 0x40036400, LENGTH = 2KThe x (executable) flag is incorrect. BKPSRAM is a data-only backup memory — it is not executable. According to RM0481 sec. 2.3, BKPSRAM is accessible only via the system bus (S-AHB), not the code bus (C-AHB). Marking it executable is misleading and may cause incorrect MPU configuration.Expected:BKPRAM (rw) : ORIGIN = 0x40036400, LENGTH = 2

The STUSB4500 cannot communicate with my I2C bus. The voltages measured on the chip's 1V2 and 2V7 capacitor pins are 3V and 5V, respectively, and VBUS is also 5V. I tried to read the chip ID, but the result was 0, which is obviously incorrect.The following schematic showswiring diagram.

Hello STM Community,I am facing an XCP protocol timeout when trying to use Simulink Monitor & Tune (External Mode) with a custom STM32H750VBTx board and an ST-LINK-V3 (COM10, 115200 baud).The Setup & Symptoms: What works: Code generation and flashing complete successfully. "Build, Deploy and Start" works perfectly (e.g., standard LED blink routines run fine). What fails: Clicking "Connect" for External Mode immediately times out with: XCP internal error: timeout expired, in response to XCP CONNECT command. Hardware verified: Standard UART communication has been tested separately on this custom board and works flawlessly at 115200 baud. No other software is locking the COM port. Questions: Cache/MPU: Since this is an STM32H7, do the buffers used by the Simulink XCP serial stack require specific MPU or D-Cache configurations to prevent data coherency issues? Interrupt Conflict: Is there a known issue where the XCP background task gets starved by higher priority model execut

Implementation: STM32F405, using Timer 2 to synchronously trigger ADC1 and ADC2 acquisition with DMA.Problem: The sampling frequencies of ADC1 and ADC2 are correct, but the phase difference keeps changing for each acquisition – they are not sampling synchronously, and the captured waveform does not match what is observed on the oscilloscope.Question: 1，How can I debug and resolve this issue?2， I found that I must call HAL_ADC_Start(&hadc2) before HAL_ADCEx_MultiModeStart_DMA(&hadc1, ...);  Is this correct？     HAL_ADC_Start(&hadc2);     HAL_ADCEx_MultiModeStart_DMA(&hadc1,(uint32_t*)adc_dma_buf,POINTS_PER_CH);Specific code: /* USER CODE BEGIN Header *//**  ******************************************************************************  * @file           : main.c  * @brief          : Main program body  ******************************************************************************  * @attention  *  * Copyright (c) 2026 STMicroelectronics.  * All rights reserved.  *  * This

I’m seeing that the X-CUBE-FREERTOS packege is being updated to 1.6.0 to support FreeRTOS 11.2From the changelog it says that it’s restricted to    - Restricted to processor vendor: STMicroelectronics:13    - Restricted to processor name matching: STM32H5*|STM32U5*|STM32C0*|STM32WBA*|STM32U0*|STM32N6*|STM32U3*Are there any plans to bring to STM32H7* as well?

I have the latest version of STM32CubeIDE for Mac with an Apple Silicon (2.1.1).From time to time, I get the messageWhen I check the program informations, it confirms that I have the correct version (Apple Silicon).I think the problem is caused by Eclipse (version 4.33), which is out of date.Is there an upcoming update for STM32CubeIDE with the ARM version of Eclipse? 

Hi,I am using an STM32U585 MCU in a Iot Application . I am facing an issue during power-up.Problem description: When the main supply is turned ON, the MCU appears to hang or gets stuck somewhere during startup. If I press the reset pushbutton connected to NRST, the MCU starts working normally. After that, the system runs without any issues. Every time I turn the main supply OFF and ON again, the same problem occurs. A manual reset is required for proper operation. This behavior is observed with different power supplies as well. Hardware details: MCU: STM32U585 NRST pin: 10k  pull-up or 100nf capacitor connected Pushbutton reset available on NRST   Any suggestions or recommended checks would be greatly appreciated.Thank you.

I use one Nucleo-F401RE create one project for TIM1-CH1-DMA, check RM0368 (rm0368-stm32f401xbc-and-stm32f401xde-advanced-armbased-32bit-mcus-stmicroelectronics.pdf) table 29, I can use DMA2_stream 6.(support ch1,ch2,ch3)When I open CUBEMX, there doesn’t support ch1, only support ch3, which one is correct CUBEMX or RM0368?

Hi everyone,I am encountering an issue where my MCU freezes during continuous data transmission, and I am looking for some advice or debugging directions.Hardware & Setup: MCU: STM32U575 Network Module: ST67W611M1 Protocol: TCP Driver/Firmware Version: V1.3.0 Issue Description: My application is designed to send a 1KB data packet to a remote server every 3 seconds. The transmission works perfectly fine at the beginning. However, after successfully transmitting several hundred KBs in total, the MCU gets stuck.Through debugging, I found that the firmware completely hangs inside the W61_Net_SendData() API.Observations: The remote server is confirmed to be alive and functioning normally when the hang occurs. The MCU does not hard fault; it simply blocks indefinitely inside W61_Net_SendData(). My Questions: Are there any known issues regarding buffer overflows or memory leaks in this specific API when sending large amounts of data over time? Is there a way to configure a non-b

Hello,I realized, that there are different informations about the features of LPUART1 in the datasheet and refmanual.The datasheets (at least DS15125 and DS15136) probably falsely specify in Table 8, that the LPUART1 features receiver timeout interrupt, modbus com and auto baudrate detection.In the refmanual (RM0522, Table 439) these features are specified as not supported. This seams to be the right information, when looking into CubeMX2, where the RTO for LPUART1 can not be activated.  

We are trying to get raw Ethernet (LAN) running on our SPC572 without using FreeRTOSIs there any code samples that we can use / low level drivers? All help is very much apreciated.Best Regards,  Lars

Hi.I’m working with a Nucleo H7A3ZI-Q. It used to work fine, but one day after we did some measurements it suddenly stopped refused to download code. I’m now trying to troubleshoot it. When connected to STM32cubeprogrammer, the board is detected well, but it does not connect, and gives me this error: and this error in the fail.txt: The interface firmware FAILED to reset/halt the target MCU I am also able to update the card with STLink Updater through STLink-V3, which I have done succesfully, but the result remains the same. I have tried on a mac and a windows.

I try to use my own model which build form python and keras, however when I import the model to the tool it have error as follow:>>> C:\ST\STEdgeAI\4.0\Utilities\windows\stedgeai.exe validate --model C:\Users\user\Documents\battery_model_MLP.keras --batch-size 10 --mode host --name network --verbosity 1 --c-api st-ai --optimization balanced --target stm32g4 --memory-pool C:\Users\user\.stm32cubeaistudio\workspace\EISv3_SOCSOHpredictor\.ai\run\run-3\.ai\mempools.json --save-csv --workspace C:\Users\user\.stm32cubeaistudio\workspace\EISv3_SOCSOHpredictor\.ai\run\run-3\.ai\st_ai_ws --output C:\Users\user\.stm32cubeaistudio\workspace\EISv3_SOCSOHpredictor\.ai\run\run-3\.ai\st_ai_outputST Edge AI Core v4.0.1-20581 7ed50de05INTERNAL ERROR: File is not a zip fileRun failed: Error: validate error: INTERNAL ERROR: File is not a zip file. Please check the report for more details. Output: ST Edge AI Core v4.0.1-20581 7ed50de05PASS:   0%|          | 0/187 [00:00<?, ?it/s]