STM32 MCUs

I have a NUCLEO-F103RB (MB1136 rev C05). My goal is to remove the ST-LINK and power via a hat supplying 3.3v. For the 3.3v I have: Moved JP5 to pins 2-3. Checked JP1 is removed. Removed SB2 zero ohm resistor. Removed SB12 zero ohm resistor. Verified my shield is putting out a good 3.3v which is attached to connector CN7 pin 16. For the HSE I have: Removed SB54 and SB55. Soldered zero ohm resistors to R35 and R37. Soldered 20pf capacitors to C33 and C34. Removed SB16. Removed SB50. Added 8Mhz 16pf crystal X3. The ST-LINK is still physically attached at the moment, but I do plan to cut it off once things are working. The board comes up and accepts programming and works in the debugger. Stepping through the initialization it gets to where the HSE is set up and then sits in an infinite loop waiting for the HSE to come ready. I tried replacing the crystal X3 just in case I got a bad one but there was no change in behavior. The clock config is unchanged, other than setting HSE to "crysta

HI,     I'm capturing image as RGB565 using camera over DCMI on DMA. Capturing is complete and data is available. Now I need it to convert into JPEG format.      But, the JPEG in/out DMA is not working. Any help will be appreciated.   snippet:  MX_DCMIQueue_Config(); HAL_DMAEx_List_LinkQ(&handle_GPDMA1_Channel12, &DCMIQueue); __HAL_LINKDMA(&hdcmi, DMA_Handle, handle_GPDMA1_Channel12); MX_JPEGInQueue_Config(); HAL_DMAEx_List_LinkQ(&handle_GPDMA1_Channel13, &JPEGInQueue); __HAL_LINKDMA(&hjpeg, hdmain, handle_GPDMA1_Channel13); MX_JPEGOutQueue_Config(); HAL_DMAEx_List_LinkQ(&handle_GPDMA1_Channel14, &JPEGOutQueue); __HAL_LINKDMA(&hjpeg, hdmaout, handle_GPDMA1_Channel14);   Thatnks-Shubhendu Using following:1. STM32CubeIDE, Version: 1.16.12. MCU: STM32U5G9BJYXQ3. Camera: OV7725 @devjeet-adben 

Please use English on this forum.Translated: The development board is STM32H723, using stm32cubemx for development, debug is disabled, using stlink to burn found that it can be burned, and it can also be debugged, which is very strange! (The development board is STM32H723.) It was developed using STM32CUBEMX. The debugging option is set to "Disabled". Programming with stlink, discovering that it can be programmed and debugged. It's weird! ）Original:开发板为STM32H723，使用stm32cubemx进行开发，debug勾选禁用，使用stlink烧录发现可以烧录，并且还可以调试，非常奇怪！（开发板是STM32H723。它是使用stm32cubemx开发的。调试选项设置为“禁用”。使用stlink进行编程，发现可以编程，也可以调试。这很奇怪！） 

Hi,I am currently developing a small application with a STM32U5 where I write a few bytes into flash using HAL_FLASH_Program(). All seems to work fine. Except I can only read the data back after I do a reset. I suspect that DCACHE is playing a trick on me? But I am not sure how to invalidate the DCache (preferably only for a small section)SCB_InvalidateDCache();Seems to have some problems on the STM32U5? At least, I was unable to include the prober h-file w/o getting tons of errors. What is the new strategy for cache invalidation? Thanks,Juergen 

I am facing an issue in STM32CubeIDE on Windows where the I/O Configuration / Pinout & Configuration window is not appearing after creating or opening a project.Normally, when opening the .ioc file, the Device Configuration Tool (CubeMX interface) should open showing the MCU pin diagram and peripheral configuration options. However, in my case, this interface is not appearing.Issue Details:Operating System: WindowsSoftware: STM32CubeIDEWhen I create or open an STM32 project, the Pinout & Configuration view does not open.The .ioc file either does not open correctly or the graphical configuration window is missing.Because of this, I cannot configure GPIO, ADC, UART, or other peripherals.Expected Behavior:Opening the .ioc file should display:Pinout & ConfigurationClock ConfigurationProject Managerwith the MCU pin diagram and peripheral configuration options.What I Have Tried:Opening the .ioc file manually from Project Explorer.Restarting STM32CubeIDE.Resetting the perspective.

Hi,I am using the STMH745 MCU and trying to synchronize the ADC trigger to HRTIM. For HRTIM I set the "ADC Trigger Configuration" as given in figure HRTIM.jpg - it defines only a SINGLE trigger. However, in ADC configuration (figure ADC.jpg), TWO HRTIM trigger outs are visible.Can anyone explain the relation between these two option sets? How to correctly synchronize the ADC trigger to the given value value of a HRTIM timer?Thanks!

Hello, I’m having a problem with a board I’m developing based on the STM32H747BIT6. The issue is related to SPI communication. When I connect any device to the SPI bus, the signal level drops from 3.3 V to around 1.5 V. I have tested different SPI peripherals, but they all show the same behavior. Could this be related to the drive strength or power capability of a specific pin?

Hi,When I worked on the Discovery kit with STM32F769NI MCU it supported in the STM32CubeIDE/MX the  LWIP package (from 2025) with FreeRTOS/V1. Now when I pass my project to NUCLEO-H563ZI I see in the TM32CubeIDE/MX that ST will not support the LWIP with FreeRTOS anymore. FreeRTOS is only v2 in this board.Is someone integrete the LWIP package on NUCLEO-H563ZI with FreeRTOS/v2? The code main files that should be changed from STM32F769NI to NUCLEO-H563ZI  are LWIP/App/lwip.c, LWIP/Target/ethernetif.c/h, LWIP/Target/lwipopts.h, main.c.Is there any project in git that have done this miggration for LWIP package (code from 2025) and using FreeRTOS/v2 in it's LWIP package? Or share with me those 4 LWIP files for NUCLEO-H563ZI board. Thanks.

Hi everyone,I just started developing software for a new project containing on of the STM32L4P5 series microcontrollers. Therefore I bought the NUCELO-L4P5ZG starter-kit to get used to the IDE, HAL and so on. I use the STM32CubeMX IDE (Version 6.16.1) to configure the board and generate the basic initialization sources. Further code writing is done in STM32CubeIDE (Version: 2.1.1).For the beginning I configured three GPIO pins for the LEDs on the board and the LPUART for simple data transfer to terminal on host computer. For the transmission I want to use DMA . After generating the code with CubeMX and implementing some simple blink logic for the LEDs, I added the line HAL_UART_Transmit_DMA(&hlpuart1, buffer, 14); to the main loop. I debugged the code and saw that the code ran into the infinite loop in the DefaultHandler in the startup file startup_stm32l4p5zgtx.s: After searching for two and a half hour I finally found the problem: the generated names for the interrupt h

See Inconsistent pin naming for CubeMX - does the same apply to CubeMX2 ?   (Cross-posting at the request of @Ghofrane GSOURI; again, no label available for "Suggestions")

Hi all, I have a small issue with the STM32N6570-DK board and the VENC_SDCard example code. The PN12 pin has a voltage of 0V (card inserted) or 1.80V (no card inserted); on the MCU side, the GPION data register (IDR) always shows a logic 0 in both situations. The VENC_SDCard / VENC_SDCard_ThreadX example code basically jumps over SD Card detection as it assumes a logic level of 0 == card present. If there is no card, mounting fails and aborts further processing. I have the requirement to react to card inserts / removals, so I'd like to trigger an interrupt or at least be able to read a logic high once in a while but could not find out what exactly is missing in the code. * I tested with an empty CubeMX project and set this PN12 to input; here I do see logic level changes.   * I susptected the VDDIO voltage domains to be at 3V3 for that block and manually switched VDDIO_SD to be at 1V8, but that did not show a change as well * I did not fiddle with security bit settings... may

Hi. I want to use the A HRTIM timer to independently control two MOSFETs. Namely, I have a transformer with the midpoint connected to the positive pole of the power supply, and these two transistors switch the 2 halves of the winding as lower switches to generate 2 half-waves of a sine wave.But I can't configure it in STN32CubeMX for the second output the condition for set. STN32CubeMX "Set Sources: nothing to set as Dead Time is enabled, Output2 signal is defined based on Output1 Configuration Set Sources must be 0." although the channels are configured as independent. Moreover, before the update there was no such problem. Now STM32CubeF3 Firmware Package V1.11.5Why the problem? 

Good day folks,I have the DCMI camera interface on a STM32N6 streaming to the SDCard, and I am noticing that there are cases that the DCMI reports an Overrun when a SD access occurs at the same time that the Hsync interrupt was meant to occur.Digging into it I believe its due to congestion on the underlying AXI bus, and the IDMA of the SDMMC taking priority over the DCMI DMA. I have set the DCMI and its DMA to the highest possible priority as below. HAL_NVIC_SetPriority(GPDMA1_Channel12_IRQn, 0, 0); HAL_NVIC_EnableIRQ(GPDMA1_Channel12_IRQn); HAL_NVIC_SetPriority(DCMI_PSSI_IRQn, 0, 0); HAL_NVIC_EnableIRQ(DCMI_PSSI_IRQn); HAL_NVIC_SetPriority(SDMMC1_IRQn, 5, 5); HAL_NVIC_EnableIRQ(SDMMC1_IRQn); gpdma_dcmi.Instance = GPDMA1_Channel12; gpdma_dcmi.Init.Request = GPDMA1_REQUEST_DCMI_PSSI; gpdma_dcmi.Init.BlkHWRequest = DMA_BREQ_SINGLE_BURST; gpdma_dcmi.Init.Direction = DMA_PERIPH_TO_MEMORY; gpdma_dcmi.Init.SrcInc = DMA_SINC_FIXED; gpdma_dcmi.Init.DestInc = DMA_DINC_INCREMENTED;

Hello,In my project, I want to hold boot params in BKPSRAM so "Application project" can also write and read this section easily. If boot is needed, "Application project" will set boot params as required and after that it will use "NVIC_System_Reset".Therefore, I tried to write and read some parameters in this area. I can see the datas is written successfully in "BKPSRAM_BASE_S" section while debugging but when I restart the debug session, BKPSRAM section is all fill with zeros. I know that I am missing something but did not find it. - STM32N655 custom board. #define BKP_SRAM_START_ADDRESS ((uint32_t)BKPSRAM_BASE_S) #define BOOT_PARAMS_PTR ((BootParameters_t*)BKP_SRAM_START_ADDRESS) /* USER CODE BEGIN Init */ __HAL_RCC_PWR_CLK_ENABLE(); __HAL_RCC_RAMCFG_CLK_ENABLE(); __HAL_RCC_BKPSRAM_MEM_CLK_ENABLE(); HAL_PWR_EnableBkUpAccess(); HAL_PWREx_EnableBkupRAMRetention(); /* USER CODE END Init */ /* Configure the system clock */ SystemClock_Config(); /* Configure the per

Hello ST Community,My name is Gorakhnath. I am currently pursuing M.Tech (Power Electronics and Drives) at NIT Kurukshetra. I am using the STM32F4DISCOVERY (STM32F407VGT) board and I need stable DAC outputs for my hardware application.What I need (requirement)When the DAC command is 0 V, I need the output to be as close as possible to true 0.0000 V, because my external circuit maps:0 V → 0 A3 V → 50 AEven a small voltage like 0.045–0.05 V produces unwanted current (~0.5 A) in my system.Issue / ObservationOn both DAC pins:PA4 (DAC_OUT1)PA5 (DAC_OUT2)I measure about:~0.05 V (sometimes ~0.045 V) when the command is 0 VThis happens even when I am not sending any command from LabVIEW, or when I send 0,0.What I tried (software checks)Set DAC values to 0 using HAL on both channels:HAL_DAC_SetValue(..., 0) for DAC channel 1 and channel 2Forced PA4/PA5 to GPIO output LOW when command is 0 V:Configured PA4/PA5 as GPIO_MODE_OUTPUT_PP and wrote&nbs

Hello,I got a radio MCU which connects to cloud and can receive binaries from database. And I got a STM32 that controls some stuff, including other MCUs. In production this means a lot of headers and programming time for all of them, no way to update remotely, and even if the code is thoroughly tested - glitches are still possible.So I want to connect things in a chain, so that if something apart from the radio crashes - radio MCU could re-flash the whole system. This of course could be done with UART when using bootloaders, but this again means you have to pre-program bootloaders on MCUs, and there's still a very slim chance it might fail.So I need an example of how one MCU can flash another via JTAG or SWD (preferably), and then verify the result. From there I could get it to work on Arduino / STM / AVR / radio ARM. What I really want is a proof of concept simple test example to show it works with the peripheral (bit banging is always possible, but surely there is a smarter way to do

I am trying to develop a GUI application with the STM32H7S78-DK.  I want to send uart data from the board over wires to a raspberry pi.  To simplify the process without graphics I'm just trying to send a simple "Hello" string over UART7.  From what I can see from the data sheet, UART7 is connected to pins PE7 and PE8, which correspond to D0 and D1 on CN14 on the arduino headers by default.  Please correct me if I am wrong.  So I first am just initializing those pins with uart on STM32CubeMX then I was just sending a simple HAL_UART_Transmit() with a 2 second HAL_Delay().  However, I see no data coming through when putting a logic analyzer on those pins. What am I doing wrong?  Here is the very simple basic uart code in main.  /* USER CODE BEGIN Header */ /** ****************************************************************************** * @file : main.c * @brief : Main program body ****************************************************

HI,I am working on a board using STM32H573V and have a working solution with UCPD detecting an inserted memory stick and running the MSC class. In an other part of the software I am using PC9 as an GPIO push-pull, low speed output and as soon as I set it to high, the voltage at PB14 (UCPD CC2) drops from 3.3V to 1.5V and my UCPD handler signals a device attached and turns VBUS on even though nothing is attached. There is no other electrical connection between PC9 and PB14 on the board. I am using a TCPP03-M20 for VBUS switching. The board is acting as VBUS source.

About EVSTSPIN32G4, I started the code generated by MotorControl Workbench 5. Y.3 normally.If you transplant the IIC configuration of the pre drive and enable PWM output, the VDS will report an error.After carefully reading the generated code, it is found that before PWM complementary output, the lower tube is opened for charging, and the output PWM pre drive or VDS protection is written. Is there a routine for STSPIN32G4 IIC to configure PWM output?

Hello all,I've designed a board around a STM32H743 (LQFP-100) and am running into the following issue.On 2 boards out of 10, the HSE seems not to start properly. The HSE_RDY flag is never set after enabling HSE. I have checked it's not in bypass mode. On the other boards, it works perfectly.The crystal is a ABM3B-8.000MHZ-10-1-U-T and the load caps are 10 pF. We checked possible soldering issues, tested different load cap values just to see, and even replaced the crystal on the failing boards - to no avail.Looking at the OSC_IN/OSC_OUT signals (PH0/PH1) on a scope does not show a significant difference between the working and non-working boards. Maybe just a very slight difference in p-p amplitude.I have looked at the AN2867 app note, and the gain margin seems sufficient according to the formulas given there. I have heard that this crystal may have a bit too high ESR (200 ohm) for the STM32H7 HSE, but again, the gain margin seems alright.Any idea? I have tested with a minimal

I've always found it a little irritating:#define CLK_A_Pin GPIO_PIN_0 #define CLK_A_GPIO_Port GPIOFWhy is it deemed necessary to have "GPIO" in one, but not the other? Surely, that should be either:#define CLK_A_GPIO_Pin GPIO_PIN_0 #define CLK_A_GPIO_Port GPIOF("GPIO" in both), Or:#define CLK_A_Pin GPIO_PIN_0 #define CLK_A_Port GPIOF ("GPIO" in neither) (There isn't a label for "suggestion" - so "bug report" is the nearest option)

Hi, I am not sure how to categorize this problem. I have a custom board that I had done an initial software development cycle on STM32CubeIDE. I am working a newer version in VSCode with the STM32 Extension. Everything is working with the exception of one problem. I am using a watchdog on my MCU (STM32L4R9ZGJ6), which triggers while I have the processor halted. I know how to fix this in CubeIDE (Debugger tab, Enable Suspend Watchdogs) but cannot figure it out on the VSCode/GDB side. Below is the launch.json I have so far:{ "version": "0.2.0", "configurations": [ { "cwd": "${workspaceFolder}", "executable": "./build/debug/build/test.elf", "name": "Debug with ST-Link", "request": "launch", "type": "cortex-debug", "runToEntryPoint": "main", "showDevDebugOutput": "none", "servertype": "stlink" }, { "name": "Launch", "type": "cppdbg", "request": "launch", "cwd": "${workspaceFolder}", "program": "${command:cmake.launchTargetPath}", "MIMode": "gdb", "miDebuggerPa

[PN]: custom Board based on evspin32g4-dual[VERSION]: 6.4.0[Motor]: Xing2207 1800Kv[CubeMx]:6.14.1Hello,I have a problem with getting my FOC BLDC motor to start, the specs of the motor are: 0,08Ohm 50uH 0,32Vrms/kRPM. My project is for two sensorless motors with one shunt each, but I am trying to get started with the one connected directly to the stspin32G4.When using 10kHz Pwm the motor first vibrates but does not spin, then it starts accelerating, then I get the startup failure. The failure always occurs when it reaches the start-up speed threshold. When I try 40kHz PWM it wont start at all. I noticed that in cubeMX there are some errors.The schematic for the mosfet drivers is identical to the evspin32g4-dual:33Ohm gate resistors and 1uF Boot CapI set the Boot charge time to 50ms and the Charging Duty cycle to 15% Below is a screenshot of the startup phase once the motor is running, orange: one phase, blue: voltage over shunt, the digital signals are the gates of all t

Hi I have created a project using STM32Cube.AI Studio. I am able to successfully run and generate the project from the tool. After that, I can open the project in STM32CubeIDE and build it without any issues.However, while debugging, I encounter the error shown in the image below.I am able to debug the image classification and face detection sample projects provided by ST without any issues. Therefore, I suspect that there may be a problem with the project configuration generated by STM32Cube.AI Studio.The evaluation board I am currently using is the STM32N6570-DK.Please help me to resolve this issue?

I am running the  FLASH_EraseProgram example code provided by STM32CubeU3.  the code fails in erasing the flash and enters ErrorHandler. I have verified the FLASH_USER_START_ADDR & FLASH_USER_END_ADDR.  it is set as follows. #define FLASH_USER_START_ADDR ADDR_FLASH_PAGE_128 /* Start @ of user Flash area */#define FLASH_USER_END_ADDR (ADDR_FLASH_PAGE_255 + FLASH_PAGE_SIZE - 1) /* End @ of user Flash area */I have tested in both debug and run mode, it is not working as expected. Is anything to be modified to run the code. regards,Rajath