STM32 MCUs Products

Hello,I’m working on a telephone‑line–powered device based on the STM32L072VBT6 and I need to push the MCU’s Run‑mode current down to ≤ 1.2 mA (ideally lower) while on‑hook. So far I’ve managed to get down to 1.6–1.7 mA by applying the following:CPU clock reduced from 16 MHz → 4 MHz (MSI). Any lower crashes my SPI2 link to the AS2522 line driver.GPIO: all unused pins set to Analog / No Pull.Regulator: switched to Voltage Scale 3.RCC gating: disabled clocks for every unused peripheral.Delay/tick: moved from SysTick → LPTIM1 (LSO domain), and completely turned off SysTick.External gating: used an EXTI line to physically power‑gate off‑board modules when not needed.Has anyone tried any of the above on an L0-series? Or do you have other exotic low‑power knobs I’m missing? Any concrete code/config snippets or CubeMX settings would be hugely appreciated.Thanks for your help!

Hi,I am using the STM32F407VET6 chip to simulate the SENT protocol. I have encountered some issues and would appreciate it if professionals in the forum could provide some answers.1.Since the SENT protocol signal needs to change the output waveform based on the transmitted data, I attempted to use the TIM BURST feature of the chip to simulate the SENT signal. I am configuring it using STM32CubeMX software. Below are the relevant configurations:   2.The SENT protocol specifies that one tick is 3μs to 10μs. I initially set the PWM to a period of 3μs with a 50% duty cycle square wave and output it. Since I am not very familiar with the TIM BURST feature, I first used the HAL_TIM_DMABurst_WriteStart() function to attempt to modify the waveform originally output by the chip. I plan to change the waveform to the synchronization signal in the SENT protocol, which involves outputting 5 ticks of low-level signal and 51 ticks of high-level signal.Initial PWM output waveform:The de

Heyho,a few questions to those who already used the PTP offload function (not via IP / UDP, but PTP directly over ethernet, MAC packet type 0x88F7), which can auto-generate SYNC and DelayRequest messages:1) As this feature does not auto-generate FollowUp messages (so no "two-step" timestamp), I assume that the timestamp sent with the auto-generated SYNC message is the "exact timestamp" when the packet leaves the STM32's MAC, so that 2-step is absolutely not required ?2) And was this ever tested at STM? -->> examples...3) Why was no automatism created for Announce messages? (Okay, these are timing-wise not important)Using the HW would greatly reduce speed and code size, because LWIP would be completely unused for PTP, and my modified PTPd could be reduced greatly (much less "manual" packet processing)Anyway, one more request for example source code!@STea please, or whoever ...

 Hello,I'm working with the STM32H723 and need to interface with an external ADC that provides a DRDY (PG2 pin) signal. I'd like to initiate an SPI transfer via DMA whenever the DRDY pin goes low. The ADC is connected to SPI6, and I understand that only BDMA can be used with this peripheral.My main question is:How can I configure DMAMUX to trigger a BDMA transfer for SPI6 when the DRDY pin goes low?I'm using STM32CubeMX for configuration. I’ve looked through existing forum posts and the STM documentation, but haven’t found a clear example or explanation for this setup. Any guidance, examples, or tips to get started would be greatly appreciated.Thanks in advance!

I have the following clock tree for STM32L471I am using TIM2 as trigger for DAC, ADC1, and ADC2 at 2.4MHz. Clock frequency of TIM2 is 48MHz with a counter value of 19 and prescaler = 0.With oscilloscope, I confirmed that the DAC is generating the signal at 2.4MHz sampling frequency.The ADC1 and ADC2 are running in dual mode with single DMA channel. The following is the ADC configuration/* 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. * ******************************

I am designing a system with an STM32 and an FPGA(Xilinx 7 series).STM32 is in charge of the user interface and the FPGA is in charge of driving the LCD to show images.Information needs to be exchanged between the STM32 and the FPGA. (STM32 send a command to the FPGA to choose which image to display or to stop displaying. STM32 also need to write all logs to the SD card through the FPGA. FPGA needs to report to the STM32 how many images are displayed and how many remain.)After some research, I found SPI seems to be fast and easy to implement.(I am not sure which interface is commonly used for communication between STM32 and FPGA?). I wonder if there is another interface that is faster or easier to implement?

Hi STM Team,  We are planning to use STM32G491 MCU in our application. As per datasheet, it is mentioned that STM32G491 MCU will support USB PD 3.0. We have come across the below STM document where it is mentioned that "STM32 UCPD MCUs are compliant with the latest USB PD r3.1 specifications" and EPR support is there. Could you please confirm, whether STM32G491 MCU supports USB PD 3.1 and Extended Power Range Support(upto 240W). Warm Regards,Mythili B 

 Tests Performed and Results:1.A DC regulated power supply was used to provide 14V to the board directly. At room temperature, the CPU's TIM pin output is normal. However, at high temperatures, the output waveform becomes intermittent.2.The on-board 3.3V and 5V power supplies remain stable and within specification at all times.3.The external crystal oscillator connected to the microcontroller maintains a stable waveform under all temperature conditions.4.The same issue occurs even after replacing the CPU with one from a previous production batch: the TIM pin output is normal at room temperature but becomes intermittent at high temperatures.5.This TIM pin is used to simulate a frequency signal. When the output becomes intermittent, the total output duration becomes longer. The firmware uses a pulse count to determine when to stop the output, so it appears the missing pulses (due to missed interrupts) cause the output to last longer than expected.Questions:Given the above results, w

Hello,I'm using a specific board where the STM32 cohabit with another "master" device on the parralel bus.One time the STM32 is the master and "drive" the external RAM and one time the other device "drive" this RAM.My first thought was to disable the FMC and put all pins in disable (input ?) mode when the STM32 is not the master.And when the STM32 become the master again, put th GPIO back in alternate mode and re enable the FMC.Something like this to disable the FMC:__FMC_DISABLE(); LL_GPIO_SetPinMode(GPIO_FMC_A0_Port,GPIO_FMC_A0_Pin,LL_GPIO_MODE_INPUT); LL_GPIO_SetPinMode(GPIO_FMC_A1_Port,GPIO_FMC_A1_Pin,LL_GPIO_MODE_INPUT); ..... And to reenable it, something like :LL_GPIO_SetPinMode(GPIO_FMC_A0_Port,GPIO_FMC_A0_Pin,LL_GPIO_MODE_ALTERNATE); LL_GPIO_SetPinMode(GPIO_FMC_A1_Port,GPIO_FMC_A1_Pin,LL_GPIO_MODE_ALTERNATE); ..... __FMC_ENABLE(); Obviously, if I'm here this is because it's not working as expected...When the FMC is disabled, the other device canno't access the RAM. L

Hi allI am working with SPI1 on stm32f407vgtx and issue what I am, facing my NSS which internally controlled by SPI is taking more time for goes high even CLOCk has been stopped . my configuration are SPI full duplex 16 bit data clock is 2.6MHZ after prescaled I am transmitting on spi every 10ms task. Please check the screenshot of logic analyzer for further understanding .Note: in the end I have disabled SPE bit  before checking TXE and busy flags.  

 I’m using the STM32L443 in one of my products, and currently, there are around 2,500 units deployed in the field. I’ve been experiencing issues that I believe are related to the firmware programming process during production. The product includes a seven-segment LCD. After programming the firmware and running tests, I noticed that some characters do not display correctly in certain menu screens. I’m confident this is not a hardware issue. Interestingly, when I reflash the firmware on the same board, everything starts working properly — the display shows the correct characters. These are just the visible symptoms. I’ve also observed cases where the firmware seems to get stuck in a specific scenario. For example, there’s a routine that runs every 5 minutes. On the third iteration, the system hangs. Even after a power cycle, it always gets stuck at the same point. However, if I reflash the firmware, the issue disappears. This makes me suspect that the firmware might n

I'm trying to understand the operation of the STM32F446xx family of microcontrollers. I'm reading the reference manual that's available here: https://www.st.com/resource/en/reference_manual/rm0390-stm32f446xx-advanced-armbased-32bit-mcus-stmicroelectronics.pdf. I'm struggling to understand the timing of how the FMC SDRAM controller reads the data it anticipates and stores them in the FIFO. I have the following questions: 1. On page 313, in the description of the RPIPE bits, it is stated, "These bits define the delay, in KCK_FMC clock cycles, for reading data after CAS latency." Which clock does KCK_FMC refer to? And how are KCK_FMC and SDCLK related? I couldn't find KCK_FMC mentioned anywhere else in the manual. 2. On page 306, it is stated, "The FMC SDRAM controller features a Cacheable read FIFO (6 lines x 32 bits). It is used to store data read in advance DURING the CAS latency period and the RPIPE delay ..." I'm confused as to how data is read DURING the CAS latency

Hi everyone,I'm working with an STM32U5 and using USBX with the CDC-ACM class.My setup is as follows:I have a USBX CDC ACM receive thread that calls usbx_cdc_acm_read_thread_entry() in ux_device_cdc_acm.c file.Alongside, I have a state machine running in another context (main loop).If the device stays idle (no USB activity) for a certain timeout, the state machine puts the MCU into Sleep Mode using:HAL_SuspendTick();HAL_PWR_EnterSLEEPMode(PWR_LOWPOWERREGULATOR_ON, PWR_SLEEPENTRY_WFI);HAL_ResumeTick();The goal is to wake up the MCU only when data is received on the USB.To achieve this, I tried relying on USB interrupts:OTG_FS_IRQn is enabled in NVIC.The USB OTG FS peripheral is initialized properly via HAL_PCD_Init().OTG_FS_IRQHandler() is defined and calls HAL_PCD_IRQHandler()But I'm not getting out from the Sleep mode, I'm completely stuck and running out of ideas. Any assistance would be greatly appreciated. Thank you! 

Hi, I'm searching for more details on  STM32F303 ADC Voltage Regulator Function ADVREG. According AN4195 it needs to be enabled before ADC calibration. ADC Regulator is by default disabled. But i cannot see any big difference on ADC conversion results bettween enabled and default (disabled) state of the regulator. I'm using recommended ADVREG enable sequence 10 -> 00 > 01. Thanks!

... leads to "funny" results:STM32L011 with 16 kB of flash, HAL inits and LED toggle in main, DEBUG, no optimization:93% of flash usedI had not expected it to be that bad! :grinning_face_with_sweat:Okay, I will probably not use too much HAL, will use Release version with optimization,but I better select an L01 in the next bigger QFN package (4x4) to get 32 kB of flash.

Hello.First of all, thank you for your help.I have a question about UART & debug.When I stop transmitting from the PC while communicating with the PC and then debug, there is no problem.When I stop debugging and resume while transmitting from the PC, the communication fails. When I check the UART related register, it remains in busy state.This problem was previously fixed using stm32cubeide 1.9.0 or 1.17.0, but it has been fixed after changing to 1.19.0. Is there a problem with the installation? Where should I set to solve this problem?Additionally, I opened and checked the old project, and there is no problem with the old project. The IC used to be mainly stm32f103, and this is the first time I am using stm32h743. Is there a problem with the chip parameter settings?        

I'm using UART7 on a STM32H743 to drive a RS-485 transceiver. I've set it up to use the hardware DE pin to switch the transceiver between TX and RX modes. I transmit 14byte messages to devices on the bus, and they send back ~14byte messages. My code does this TX/RX16 times a second in bursts of 8 transfers. All works well 99.999% of the time. However, at a random interval from hours down to every consecutive data transfer, I receive back junk data. It averages around 5 minutes between errors.I put a scope on the transceiver and found that the errors are caused by the DE pin staying asserted too long after the last stop bit of a transmission ends; the transceiver stays in TX mode and blocks the incoming reception. This happens very rarely, but remains to be a headache for my system. The length of the deassertion time seems deterministic and very fast normally, but during these glitches it can be between 50 and 200us (50us is about how long it takes for the RS-485 device to respond

I am trying to implement an application with USB CDC-ECM host capabilities. As a bring up setup, I configured two STM32 boards:1) STM32U5G9J-DK2 board, configured as a CDC-ECM device, using USBX.2) STM32U575I-EV, configured as a CDC-ECM host, using USBX. I am able to connect both boards, and get some basic networking functionality, including ping and  UDP traffic. Now I am trying to implement host suspend/resume and remote wakeup by device.When performing suspend and resume by host only (without remote wakeup), everything works fine, andI can see both suspend and resume signaling on device. However, when using remote wakeup by device, I see the following flow of events:1) Host sending suspend to device.2) Device is getting the suspend signaling and enters suspend mode.3) Device is activating remote wakeup signaling4) Remote wake signal is detected on host (OTG_GINTSTS_WKUPINT is fired).5) Host waits ~10 msec and desserts the resume signal (OTG_HPRT_PRES)6)

I am using one of the 32 bit timers to measure intervals for fault protection on a HV pulse modulator.  I have an interrupt on EXTI that captures both leading and trailing edges of the command pulse.   In the service routine, I simply store the latest uptime and downtime to calc the pulsewidth and period....pretty simple.    The pulsewidth is pretty small, so I use the free-running SYSTICK (400 MHz) for pulsewidth, but it is only 24 bits, so I need to use a 32 bit timer for the pulse period, and do so at 50 MHz.I initially coded this with TIM2, and it worked perfectly.  Then I realized that I needed to use TIM2 elsewhere because I already wired a different time-critical signal to the TIM2.ETR pin (the ETR interrupt latency is far less than the EXTI latency).  So I switched my code to use TIM5 for the period.   This did not work.   It bounces around semi-randomly, and by appearances is acting like a 16 bit timer.I switched to T

My simple program to test wake from standby with PC13/Wakeup_pin4 is working.  I use the pushbutton on this pin as an EXTI and had to add the GPIO_DeInit before setting the pin as an input without EXTI.The same code does not work in my larger program and I can't work out why?? printf("0 - sleep until button pressed\r\n"); HAL_GPIO_DeInit(GPIOC, GPIO_PIN_13); GPIO_InitTypeDef GPIO_InitStruct = {0}; GPIO_InitStruct.Pin = GPIO_PIN_13; GPIO_InitStruct.Mode = GPIO_MODE_INPUT; GPIO_InitStruct.Pull = GPIO_NOPULL; HAL_GPIO_Init(GPIOC, &GPIO_InitStruct); HAL_PWR_DisableWakeUpPin(PWR_WAKEUP_PIN4); PWR->WKUPCR = 0x3F; // Clear all wakeup flags (write 1 to clear) PWREx_WakeupPinTypeDef sPinParams = { .WakeUpPin = PWR_WAKEUP_PIN4, .PinPolarity = PWR_PIN_POLARITY_HIGH, .PinPull = PWR_PIN_NO_PULL }; HAL_PWREx_EnableWakeUpPin(&sPinParams); HAL_Delay(10); HAL_TIM_Base_Stop_IT(&htim6); HAL_SuspendTick(); BlinkOff(); HAL_PWR_EnterSTANDBYMode(); 

I’m working on a design where I need to communicate with two SPI devices that operate at different logic levels:1) A sensor running at 1.8v logic (need SPI + 2 other lines, all at 1.8v) 2) Everything else on my board, preferably running at 3.3v, I will need CAN, UART, and another SPI. I’m trying to avoid level shifters if possible (and avoid sourcing 1.8 V CAN/UART transceivers). Ideally, I’d like to use an STM32 that has split power domains, both with SPI peripherals. So far, I’ve found that the STM32L496QI supports SPI on both the main VDD rail and the VDDIO2 rail (which can be independently run at 1.8 V), which fits the bill. The only issue is that it’s a 100-pin part, which is way more than I need for this design.What I’m looking for:STM32 with VDDIO2 or similarSPI on both 1.8V and 3.3V-capable banksPreferably 64 pins or lessThanks, Sameer 

I have measured the MCU current on the NUCLEO-L433RC-P dev board by removing JP6 and connecting a multimeter. The current in shutdown is ~1mA, why is this so high ?   The shutdown current should be nA or uA at most...  To shutdown I call "HAL_PWREx_EnterSHUTDOWNMode();" and have PC13 (the blue top button) set to SYS_WKUP2 to wake up. Looking at the dev board schematic, it appears that the only other load on the 3.3V supply are two level shifters (SN74LVC2T45DCUT) but the datasheet says that these have a low power consumption, 4-μA maximum ICC. 

Hello,   I am using this example: https://github.com/STMicroelectronics/x-cube-n6-ai-h264-usb-uvc HW: STM32N6570-DK + STEVAL-66GYMAI  I have this strange behavior only when using the VD66GY. If no motion on the video, i barely see the flickering. However, when i do a little motion in front of the camera, I begin to see white horizontal lines on the  of the video stream, this flickering happens only at around 30fps. Only when I reduce to 15fps it disappears...   Also lowering the VENC resolution did not fix it.  #define VENC_VD66GY_WIDTH #define VENC_VD66GY_HEIGHT BTW, The IMX335 works fine at 30fps. Can someone help me ?   Thank you.

Hello again, The DMA now works in standard request mode with circular mode disabled, but it doesn't when I am trying to use circular buffering mode (my destination buffer only contains 0s). I defined manually the data size, the source and destination addresses in my code once my memory buffers are defined. Once these parameters defined I enable the GPDMA. Here are the lines I add in the main() : LL_DMA_ConfigAddresses(GPDMA1, LL_DMA_CHANNEL_0, p_dma_buffer, m_dma_buffer); LL_DMA_SetBlkDataLength(GPDMA1, LL_DMA_CHANNEL_0, 8); LL_DMA_EnableChannel(GPDMA1, LL_DMA_CHANNEL_0);     But when I launch the debug only the parameters I set manually were taken into account. All the CubeMX Configuration doesn't appear here (for example DINC and SINC should be at 1 in GPDMA_C0TR1 in the image below) ... Do you have any idea of what I should do to use circular buffering in standard request mode? I saw in the user manual an example of application for circular buffering using link

Hello All, I am using STM32L011G4U6TR for one of my application development. I have written a code where I am using,11 GPIO, 1 UART and Internat EEProm.When I am building the code in I am getting below Error and not able to load the Application on STM32L011G4U6TR board.If someone could guide how to resolve it, would be helpful. (Have removed the unnecessary arrays variables and using minimum variables to optimized ). Description Resource Path Location TypeIPL_Handpiece_Control_Board_Firmware.elf section `.text' will not fit in region `FLASH' IPL_Handpiece_Control_Board_Firmware C/C++ Problemmake: *** [makefile:64: IPL_Handpiece_Control_Board_Firmware.elf] Error 1 IPL_Handpiece_Control_Board_Firmware C/C++ Problemregion `FLASH' overflowed by 568 bytes IPL_Handpiece_Control_Board_Firmware C/C++ Problem Note when I am commenting some part of needed code then, I am able to load it and debug, but I need all the GPIO, UART, EEprom working together. Will do as pe