STM32 MCUs

I have been trying for hours to upload code to the STM32-N6 and I am simply out of ideas. I only managed to upload debug code to RAM once, then I tried erasing the flash on the PCB using STM32CubeProgrammer (which worked, the standard code is not on there anymore) but now I cannot even use the debug option. Every time I try to upload code (I tried all BOOT pin combinations) it simply doesn't work. sometimes it has a timeout while trying to connect and really often I get the following output:  Starting server with the following options:Persistent Mode : DisabledLogging Level : 1Listen Port Number : 7184Status Refresh Delay : 15sVerbose Mode : DisabledSWD Debug : EnabledInitWhile : EnabledInfo : default port : 7184Info : Remote address: 127.0.0.1Info : stlinkserver already running, exitTarget unknown error 32Error in initializing ST-LINK device.Reason: Unknown. Please check power and cabling to target. I am using the 5V_STLK header connection for power. Right now, I cannot

I am using software Independent watchdog at STM32H735IGK and i want to freeze it when entering standby mode.I set option byte FW_IWDG_SDBY unchecked but unfortunately it is not working and my program keeps getting out from standby mode.My code:At init:MX_IWDG1_Init(); While the program is running:__HAL_IWDG_RELOAD_COUNTER(hiwdg); When entering standby: HAL_RTCEx_DeactivateWakeUpTimer(&hrtc); HAL_PWREx_ClearWakeupFlag (PWR_WAKEUP_FLAG_ALL); __HAL_PWR_CLEAR_FLAG(PWR_FLAG_WU); __HAL_PWR_CLEAR_WAKEUPFLAG(PWR_FLAG_WKUP1); // E1 __HAL_PWR_CLEAR_WAKEUPFLAG(PWR_FLAG_WKUP4); // INT //Configuring wakeup pins PWREx_WakeupPinTypeDef sWakeupPin1; sWakeupPin1.WakeUpPin = PWR_WAKEUP_PIN1; sWakeupPin1.PinPolarity = PWR_PIN_POLARITY_LOW; // Flanco de bajada sWakeupPin1.PinPull = PWR_PIN_PULL_UP; HAL_PWREx_EnableWakeUpPin(&sWakeupPin1); PWREx_WakeupPinTypeDef sWakeupPin4; sWakeupPin4.WakeUpPin = PWR_WAKEUP_PIN4; sWakeupPin4.PinPolarity = PWR_PIN_POLARITY_LOW; // Flanco de bajada

I'm referring to RM0481 Rev 4 and I'm currently working on my SDMMC driver. For one reason and another, I need to start a data transfer for multiple read/write commands, but without sending the command again (because it has already been done so).The RM states this about the DTEN (Data Transfer Enable) bit: Ok. Maybe I'm missing something, but isn't the whole point of SDMMC is to communicate with SD, SDIO, and eMMC cards? The marketing people said so: What gives? Can I use or not use the DTEN bit? Or is it just leftover legacy from older versions of the SDMMC IP?

The UCPD / CC circuit is one of the few that connect an MCU pin to the PCB connector. There does not appear to be any specific information on how to protect this pin. Thus, I assume the same rules as other pins apply. That means 5V  or even 3V being applied to this pin when the MCU is unpowered would be bad. Is there any recommended protection scheme against this? Is an inline resistor sufficient?

HI, I have a strange issue with our STM32H747 board using the IS42S16400J SDRAM chip.We have been reading the "How to set up the FMC peripheral to interface with... - STMicroelectronics Community" page and this all seems OK.The differences between the system described and our board is that we have 8 MB RAM instead of 32 MB and we do not use the byte lane select signals (LDQM and UDQM from the SDRAM chip are routed to ground). When writing to SDRAM, we see (random) writes to the other 32 bits word within the same 64 bits. This is true for both 16 and 32 bits write from the CM7 core. So writing 0x12345678 to address 0 in the SDRAM results in a random value being written to address 4. Same applies when writing to address 4 - there I see a random value appearing at address 0. If I first write 0x12345678 to address 0 and then 0xaa55aa55 to address 0x14, I see the value 0x12345678 being writting to address 0x10.This is almost as if the processor performs a 64 bits write with the lower o

I am having to program a unit via UART, and every time I open the STM32CubeProgrmmer GUI the interface selector shows J-Link/Flasher.It remembers if I choose ST-Link.If I manually edit the "interface=" entry in config.properties to 2, STM32CubeProgrmmer opens with UART selected.On exit, the "interface=" entry is rewritten to 1.If I select USB as the interface, the "interface=" entry is rewritten to 2, which opens as UART the next time, and then the "interface=" entry is rewritten to 1 on the next exit.

Hello, I created a complex project for a STM32H573 based custom board. That project is ThreadX based and it shall use the USPBD package. I generated to project with STM32CubeMX version 6.16.1 using STM32Cube MCU Package for STM32H5 Series 1.5.1 (see attached IOC file for reference) I create the code for the latest STM32CubeIDE 2.0.0. The project is imported successfully, but does not compile and the following errors are logged: Description Resource Path Location Type 'USBPD_CORE_PDO_TYPE_APDO' undeclared (first use in this function); did you mean 'USBPD_CORE_PDO_TYPE_FIXED'? usbpd_dpm_user.c /test03/USBPD/Target line 1100 C/C++ Problem 'USBPD_CORE_PDO_TYPE_APDO' undeclared (first use in this function); did you mean 'USBPD_CORE_PDO_TYPE_FIXED'? usbpd_dpm_user.c /test03/USBPD/Target line 1577 C/C++ Problem 'USBPD_ParamsTypeDef' has no member named 'PE_UnchunkSupport' usbpd_dpm_user.c /test03/USBPD/Target line 1507 C/C++ Problem 'USBPD_ParamsTypeDef' has no member named 'PE_UnchunkSupport

Hi everyone,I'm relatively new to STM32 and I'm running into a confusing issue with the debugger in STM32CubeIDE.I have a simple while loop where I read an ADC value (potentiometer) and use that value as the delay time for a blinking LED.The code is definitely working physically. When I turn the potentiometer, the LED blinks faster or slower accordingly. This confirms `HAL_ADC_GetValue` is returning a changing value.When I run the code in Debug mode and look at my variable (adcDeger) in the live expressions tab, it is stuck at 0. It never updates, even though the LED behavior proves the value is changing.My variable is global and volatile (dont mind the printf i was trying to write the value to console):#include "main.h" #include "stdio.h" #include "string.h" ADC_HandleTypeDef hadc1; volatile uint32_t adcDeger = 0; void SystemClock_Config(void); static void MX_GPIO_Init(void); static void MX_ADC1_Init(void); int _write(int file, char *ptr, int len) { int DataIdx; for (DataIdx = 0

Hello ST/TouchGFX team,Our team have been using scroller widgets to display data that is lazily loaded from a persistent database. It works well, but since these widgets use 16-bit indexes, it limits the amount of rows that can be displayed to 32k. Given the way these widgets work, it's only necessary to keep the visible items in memory and the index is kept only as the first visible item's offset, increasing the index size would have minimal if not negligible memory impact, and since TouchGFX only runs on 32-bit ST MCUs, any arithmetic operations are done in 32-bit anyway so there should be no performance impact.In fact, we've been able to hack a solution to this by modifying the provided framework headers and source files to these widgets. The only issue is that the TouchGFX generator is hardcoded to create the updateitem callbacks with int16 signature and there is no way to change this except for modifying the base classes -- which are overwritten every time the project is rege

Hey there at @Pavel A. I've implemented USBCDC as a device In stand alone mode successfully I intend on implementing CDC host stand alone that is to say without X-thread RTOS.The generated files from cube MX don't have Read_run and Write_run functions for stand-alone when implementing the host side which makes me wonder if it is achievable you to have USBx as a host in stand alone.

Hi everyone,I am working on a custom board based on the STM32F429I MCU (RMII mode) and I am trying to integrate LwIP with a DP83848 PHY.At the moment, I am unable to get Ethernet working. The issue appears during PHY initialization — the code blocks while trying to communicate with the PHY over MDIO.Project ContextMCU: STM32F429IPHY: DP83848 (RMII mode)Middleware: LwIPDevelopment tool: STM32CubeIDE (project originally generated with CubeMX, but I cannot re-generate it now due to version mismatch)ETH driver: HALI have tried:Using the LwIP stack with the HAL ETH driverAttempting raw Ethernet (without LwIP)In both cases, the system gets stuck during PHY initialization.Observed BehaviorThe code freezes when accessing PHY registers (MDIO communication).When debugging, execution appears to stop when checking or configuring the ETH clock.The PHY does not respond to register reads.Suspected CauseI suspect either:The RMII clock (50 MHz reference clock) is not correctly generated or routed.The P

 # External Loader Issue: STM32U5G9ZJT6Q + MX25L12833FZNI-10G (Quad-SPI)## 1. Problem SummaryHello, I'm a novice developer who recently started working with embedded systems. I've been struggling significantly with implementing an external loader for several weeks now...I'm developing an external loader for **MX25L12833F** (16MB Quad-SPI NOR Flash) connected to **STM32U5G9ZJT6Q** via OCTOSPI1, but it continuously fails in STM32CubeProgrammer. The loader compiles successfully and generates a `.stldr` file, but programming operations fail.---## 2. Hardware Configuration### 2.1 MCU: STM32U5G9ZJT6Q (LQFP144)- Cortex-M33, up to 160 MHz- 2.5MB SRAM- OCTOSPI peripheral### 2.2 External Flash: MX25L12833FZNI-10G (Macronix)| Parameter | Value ||-----------|-------|| Capacity | 16MB (128Mbit) || Max Clock | 133 MHz || Page Size | 256 bytes || Sector Size | 4KB || Block Size | 64KB || Operating Voltage | 2.7V - 3.6V |### 2.3 Pin Mapping (OCTOSPI1 Port 1)| Function | STM32 Pin | Flash Pin ||--

I've reported a STM32CubeMX bug, but I am afraid that there is no one to look at it. Is there any better place to report bugs/issues? Things I've reported are quite a blocker for me and I really need to know if there is anyone working on it, or I'll have to find a workaround.Thanks.

Hi All,   I have been using SPI1 over DMA2 on Zephyr RTOS recently to read my external flash. I had done similar thing on Bare metal / FreeRTOS based program. Both of them work fine. However, there is a problem in Zephyr based implementation of its driver compared with what i developed on Bare Metal. I configure the SPI1 to use its full possible clock 42MHz on both platforms. On my bare metal platform it runs at full 42Mbps but on Zephyr it starts giving read errors. However, if i reduce the clock to < 42MHz (to which zephyr driver forcelly rounds it down to 21MHz) it works fine.Here is my dts node of spi1 for my development board: &spi1 { pinctrl-0 = <&spi1_sck_pb3 &spi1_miso_pb4 &spi1_mosi_pb5>; pinctrl-names = "default"; clock-frequency = <42000000>; // 42MHz dmas = <&dma2 2 3 (STM32_DMA_PERIPH_TO_MEMORY | STM32_DMA_MEM_INC | STM32_DMA_PRIORITY_HIGH) STM32_DMA_FIFO_1_4>, <&dma2 3 3 (STM32_DMA_MEMORY_TO_PERIPH | STM32_DMA_M

The main website states:"STM32CubeIDE integrates STM32 configuration and project creation functionalities from STM32CubeMX to offer all-in-one tool experience and save installation and development time. "https://www.st.com/en/development-tools/stm32cubeide.html However, @Aimen1 writes here:"STM32CubeIDE is now independent from STM32CubeMX."https://community.st.com/t5/stm32cubeide-mcus/stm32cubeide-2-0-0-released/td-p/857110 This caused us some useless troubleshooting trying to see why the installation didn't contain everything that was expected.Perhaps the main website can be updated, and/or a notice can be added in the CubeIDE that it will no longer generate the .ioc files for projects.

Hey, I am running into issues with a custom PCB based on STM32H743IIT6.Using IS42S32400J-6TLI as SDRAM,  with an LCD screen. Using TouchGFX and DMA2D deactivated.A hard fault is encountered after entering Model:Tick()Hard Fault Error Detected at: Debug stack view: LTDC:SDRAM - only 16 data bits used:TouchGFX: MCU:  Any suggestions what could be causing this Hard Fault error? 

I am using below component toolsMCU: STM32H750IBT6IDE: STM32CubeIDE Version: 1.20.0GUI: TouchGFX Version: 4.26.0SDRAM: IS42S32400J-6TLIFLASH: MT25QL512ABB8ESF-0SIT (QUADSPI) I have made my own external loader that proves works for the QUADSPI IC using this video: https://www.st.com/content/st_com/en/support/learning/stm32-education/stm32-moocs/external_QSPI_loader.html Thank you in advance!

Hey,I am using STM32H750IBT6 with MT25QL512ABB8ESF-0SIT QSPI flash IC for external memory and IS42S32400J-6TLI as SDRAM, on a custom PCB with an LCD screen. Using TouchGFX.QSPI pinout is as follows:I've edited the FLASH_Id script - added as a .c file as an attachment.I would prefer to not use a bootloader, but if that is the only way or quickest way to get this working then please let me know. I have looked at using external loaders but as the pin out of my QSPI is slight different, external loaders will not be compatible. My code compiles but it does not flash: Under 'ASSETS_FLASH', ExtFlashSection does appear as expected after loading images onto TouchGFX. If you have any suggestions why I can not flash the external QSPI flash IC, please let me know. Additionally, within STM32CubeProgrammer I can connect to the MCU. I can successfully mass erase the flash too. Thank you for any assistance in advance!  

I am running into issues with a custom PCB based on STM32H743IIT6.Using MT25QL512ABB8ESF-0SIT QSPI flash IC for external memory and IS42S32400J-6TLI as SDRAM,  with an LCD screen. Using TouchGFX. I am getting this error. Any ideas what could be causing it? Thank you in advance!

I'm trying to establish communication with FDCAN and view the signal via PCan View, but nothing appears on the screen. There are no errors in the connections. These are the codes: /* USER CODE BEGIN Header */ /** ****************************************************************************** * @file : main.c * @brief : Main program body ****************************************************************************** * @attention * * Copyright (c) 2026 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 ------------------------------------------------------------------*/ #include "main.h" /* Private includes ---------------------------------------------------------

CubeMX does not generate sourcecode completely for the chosen STM32H723.Even for a minimum System, several CMSIS includes are not present.Please see my IOC file.CubeMX Version 6.16.1CubeIDE Version 2.0Firmware STM32Cube_FW_H7_V1.12.0 gepatched to 1.12.1A similar file which includes LwIP also has many LwIP files not included.Please help ....

Hi all,I am currently trying to merge the STM32N6 VENC_SDCARD Project with my Codebase that is based on the STM32 Modelzoo Object Detection (https://github.com/AlexGraefe/STM32N6CameraEvaluation). However, naively copy-pasting the code does not work. For most resolutions, the generated h264 streams are wrong and for the others, the code crashes at weird places e.g., when leaving a function. As the only difference between my code and the VENC_SDCARD example is the linker script, I was wondering if wrong memory allocations might be the reason for this. The heap in the object detection example is placed on AXISRAM1, which might too small. However, I am unable to place the heap onto other parts of the RAM (internal or external), without the program crashing directly upon startup.Copying the linker script provided by VENC_SDCARD also does not work as then, I run into compilation errors stating the code uses too much RAM (as buffers for images are placed in different regions).Moreover,

I use STM32F407 with internal PHY What external elements need I for connecting USB flash to MCU? 

I am experiencing a segmentation fault when clicking a toggle button inside a ScrollList container.I have a ScrollList (alarmsSelector) populated with a custom container type called alarmsItem. Each alarmsItem contains a toggle button. When clicked, the button should invoke a callback defined in the parent view (alarmSettingsView).The callback is initialized in the view constructor as a member variable:alarmSettingsView::alarmSettingsView(): settingsChanged(false), saveAlarmsChangesOption(SAVE_ALARMS_CHANGES), alarmsItemAlarmSelectedCallback(this, &alarmSettingsView::alarmsItemAlarmSelectedCallbackHandler) { }In the view// alarmSettingsView.hpp protected: touchgfx::Callback<alarmSettingsView, const int8_t> alarmsItemAlarmSelectedCallback; void alarmsItemAlarmSelectedCallbackHandler(const int8_t itemIndex);The callback is assigned to each visible item inside ScrollUpdateItem:void alarmSettingsView::alarmsSelectorScrollUpdateItem(alarmsItem& item, int16_t itemIndex) {

HiCan anyone please show me an example of a working USB CDC Host sending the SetControlLineState command? This hasn't been implemented in the STM32 HAL drivers/middleware but it should be a simple thing to add.SetControlLineState is used to signal the Host is ready to receive data from the CDC device. I tried adding and calling my own routine after the USB enumeration completes:USBH_StatusTypeDef USBH_CDC_SetControlLineState(USBH_HandleTypeDef *phost) {   phost->Control.setup.b.bmRequestType = USB_H2D | USB_REQ_TYPE_CLASS | USB_REQ_RECIPIENT_INTERFACE; phost->Control.setup.b.bRequest = CDC_SET_CONTROL_LINE_STATE; phost->Control.setup.b.wValue.w = 3U; phost->Control.setup.b.wIndex.w = 2; phost->Control.setup.b.wLength.w = 0;   return USBH_CtlReq(phost, 0, 0); }The transmitted data appears to be correctly formed but the phost->RequestState appears to get stuck on CMD_WAIT expecting a reply from the device which I understand is not part of the CDC proto