STM32 MCUs Products

Hi everyone,I’m currently designing a board using an STM32H533RET6 and I have a question regarding the VSSA pin connection.Should VSSA be tied directly to GND (VSS) like the other ground pins, or should there be an inductor (L) placed between VSSA and VSS, as shown in the schematic below [see image]?I couldn’t find any explicit recommendation about this in the datasheet or reference manual. However, I’ve noticed that some older designs used an inductor between VSSA and VSS.Personally, I would tend to connect VSSA directly to GND (= other VSS Pins) and leave out the inductor, unless there’s a clear benefit to including it.Has anyone here implemented the STM32H5 series and can confirm the recommended approach?Thanks in advance for your insights!  

DS13565 Rev 2 says under 3.20: "The embedded USB controller cannot be used on STM32G0B0KE as this device does not provide an HSE oscillator input.". Well, sounds reasonable. But same DS says in Table 11 for Pin 2 (LQFP32) PC14: "OSC32_IN, OSC_IN" whereas for the higher pin count packages PC14 has only "OSC32_IN".So, HSE bypass is available on LQFP32?!Now CubeMX 6.10.0 with G0 1.6.1, gives after selection of "G0 series" and "USB FS" a list *INCLUDING* STM32G0B0KET6, and even the "Features" tab of the very same device shows  "USB 2.0 FS device and host controller". After selecting STM32G0B0KET6, one can definitely check "BYPASS Clock Source" under "RCC", and Pinout view shows this is located on PC14, as expected. Clock config tab now allows HSE -> PLL -> PLLR -> SYSCLOCK, and even shows "PLLQ" and "USB Clock Mux", but both not configurable. But neither RM nor DS restricts use of PLLQ divider for LQFP32. Pretty inconsistent.So, after all, what's the intention regarding

Hi everyone, I'm using an STM32H755 microcontroller to read 20 temperature sensors (NTC thermistors) via 20 ADC channels for a testing setup. Each thermistor is wired in a simple voltage divider circuit like this: [VCC] -- [NTC] --+-- [Fixed Resistor] -- [GND] | [ADCx] All 20 ADC inputs are configured identically (same sampling time, resolution, continuous mode disabled, calibration enabled). However, I've noticed that ADC1_IN9 (PB0) consistently reports a temperature value that is ~3°C lower than the others. The remaining 19 channels produce nearly identical readings under the same conditions. Same NTC , same RES. Here’s what I’ve already checked: - ADC sampling time is long enough (e.g. 64,5+ cycles).- GPIO analog mode is properly set.- No visible layout issues or external interference.- Measurements are stable and repeatable — the deviation is not noise.- Swapped NTCs between channels — issue remains on PB0. This is quite puzzling. - PB0 has an internal analog path that's affect

The ref manual (RM0481 page 2585) says: "This circuit has a defined startup time (tSTARTUP specified in the datasheet) during which the behavior of the USB transceiver is not defined.". I searched for USB and tSTARTUP but could not find anything in the datasheet (DS14258 Rev 1). Is it missing or mentioned differently ?

Referring to RM0444 and DS12232 (referring to STM32G0x1 programming manual and data sheet).In the Low Power section, the RM states that there are five wakeup pins:But in the register section, there is clear mention of WKUP3 (EWUP3 bit in PWR->CR3, WP3 bit in PWR->CR4, WUF3 bit in PWR->SR1, and CWUF3 bit in PWR->SCR).However, when I look at the CMSIS files (stm32g081xx.h), I see:#define PWR_SCR_CWUF_Msk (0x3BUL << PWR_SCR_CWUF_Pos)0x3B = 00111011 --> note, the third bit (CWUF3) is not included in the mask.Are the register maps in RM0444 wrong for including bits for WKUP3, or is there some hidden use for WKUP3 I haven't found yet?Edit: also, WKUP3 does not appear anywhere in DS12232 (Data Sheet for the STM32G071)

In RM0440, it states that "Generation of a single interrupt request for the DMA1 controller," however looking at the exception vectors indicates that there is a separate interrupt vector for each channel for both DMA 1 and 2. Also the stm32cube library header files reflect this.

I am currently working on integrating the AFBR-S50 Time-of-Flight sensor with STM32F030CCT6 microcontroller.I have seen that there's an official document and example for AFBR-S50 and STM32F401RE, which includes the whole setup and integration. But I haven't come across anything similar for F0 series(especially STM32F030CCT6).I have the reference manual and datasheet for the MCU but I'd like to know if anybody is working with same setup and if they can help.If someone can provide any tips or guidance on integration and timing configurations. Any insights, experiences, or example references would be really appreciated. I am attaching a project that I have created using the porting guide available for STM32F401RE. I am having problem in the Periodic interrupt test and finally I am not getting the MeasurementCallback which will result in increment of mydatareadyevent variable. If there's any other problem in the code, please mention that as well. Thanks i

Hello folks,I've been having a weird issue and haven't found anyone else with the same problem, so I figured I'd post here.I have a project for the STM32H735 BLANK. The PCB has an 25 MHz external oscillator (ABM8W-25.0000MHZ-8-D1X-T3) used as the HSE.When I use the 64 MHz HSI or the 25 MHz HSE without the PLL to generate the sysclock, SWV printing works great. When I run them through the PLL (I'd like to run this with a sysclk at at around 450 MHz), even if I set up the PLL to output the same clock it is given, SWV printing fails. I do not change any other aspects of the code. aside from the sysclock source. I am not forgetting to swap the sysclock on the IDE debug settings side when changing clock settings, and I know I've correctly set up ITM otherwise because I can see it when not using the PLL. Using the debugger and breakpoints, I've verified the code runs correctly for all test cases below (or at least does to the best my knowledge).Clearly, I'm missing something.My four test cas

I’m using an analog camera with a CVBS output connected to an ADV7280/TVP5150, which interfaces with the DCMI on the STM32H747. However, the LCD display is not showing any image. Previously, I used the OV5640 camera, and it worked fine. void CAM_DMA2D_Config(uint16_t xsize, uint32_t ysize) { /* output,Configure the DMA2D Mode, Color Mode and output offset */ hlcd_dma2d.Instance = DMA2D; hlcd_dma2d.Init.Mode = DMA2D_M2M_PFC; // no pixformat convert hlcd_dma2d.Init.ColorMode = DMA2D_OUTPUT_RGB565; hlcd_dma2d.Init.OutputOffset = 0; /* DMA2D Callbacks Configuration */ hlcd_dma2d.XferCpltCallback = CAM_DMA2D_TransferCompleteCallback; /* Input,Foreground Configuration */ hlcd_dma2d.LayerCfg[1].AlphaMode = DMA2D_REPLACE_ALPHA; hlcd_dma2d.LayerCfg[1].InputAlpha = 0xFF; //hlcd_dma2d.LayerCfg[1].InputColorMode = DMA2D_INPUT_RGB565; hlcd_dma2d.LayerCfg[1].InputColorMode = DMA2D_INPUT_YCBCR; hlcd_dma2d.LayerCfg[1].InputOffset = 0; hlcd_dma2d.Instance = DMA2D; HAL_DMA2D_DeInit(&hlcd_dma2d);

I get the following error when trying to debug an STM32H757 with SWO enabled. Failed to enable SWV configuration.Failed to execute MI command:-data-write-memory 0x5c003010 x 4 0x77etc...It would seem the debugger (ST-link v2) is not able to read the SWO and DBGMCU registers.With the same debug configuration and code, SWO works on H747 hardware, so I'm wondering if there is an SWO difference between these two micros that is not obvious or documented.Has anyone come across this issue before and has an idea of how to fix it?Thanks

We want to use the SDADC to measure the temperature of a PT100 sensor. The measurement should have a very high accuracy of +-0.5Kelvin. Therefore, it is important to have a low offset error. The datasheet lists very large values ​​for single-ended mode, e.g., 2000uV for VREFSD+=3.3. Differential mode cannot be used because the number of channels would then be insufficient (We need 18 channels, and the STM32F3 has only 11 differential Channels). There is a product lineup where the offset error is specified as < 1 LSB. Why is the offset error specified in the datasheet so high in single-ended mode ?Can it be reduced by using a buffer op-amp at the input ( The buffer op-amp would mean a very low source impedance and would reduce e.g. bias errors ) ? I have also read the AN4207 section offset calibration, but there are no details about single ended or differential ended offset errors after calibration

Hi,What I want to implement is to receive the Input Trigger (called Ch1) signal on the rising edge in One Pulse Mode and output a PWM signal through Ch2. At the same time, I want to capture an ICP interrupt on both the rising and falling edges of Ch1 to determine whether a signal is currently being received or not on Ch1.Previously, the STM32F103 couldn't handle the One Pulse Mode Input and ICP as a single pin, so I had to split the signal between two pins in hardware.However, the MCUs I'm currently using are the STM32H723 and STM32G071.I found out that they can internally route channels, so I don't need to receive signals on two pins, but can receive them with a single pin. Is this actually possible on these two MCUs?thanks in advance.

Hi, I am using STM32L4R9ZIJ6 with power pin connections as following image.On the same design where VREF+ pin is connected to P3V3, if I configure Vrefbuffer for ADC measurements & use Vrefbuf as 2.5V, I observe that current draw from P3V3 goes from 10mA to 20mA.I understand that it is not correct to apply external voltage at Vref+ pin when it is configured as Vrefbuffer = 2.5V. I will avoid it on final production boards. Please can you explain why this increased current draw is observed.

Spent two days of trying to see printf via USART1 from U585 and U575 boards. Was trying to load  BLE via DFU on B-U585 and get it work but USART1 became silent. (Wrote separate post on B-U585I-IOT2A as documentation nightmare). Problem: USB-C + STLINK-V3 USB mini enumeration Conflict. Need confirmation from support and opened ticket. On Windows to revive USART1 needed to go to regedit and clean all enumerations of old USB from all previous controllers but the combination of USB-C and ST-LINK mini connected to same Windows or Linux host IMHO looks dangerous  Setup: STM32U575ZI-Q or B-U585I-IOT2A board with: USB-C connected to native USB peripheral (for DFU) STLINK-V3 connected via USB (for debug + Virtual COM Port) Issue: When both interfaces are connected to Windows 10 or Ubuntu — either in sequence or simultaneously: DFU mode consistently enumerates and stays visible Virtual COM Port (VCP) fails to transmit data, even though it appears in the device list No output from&nbsp

Hello, I'm working on finding the smallest possible power solution for the STM32N6. The reference boards(STM32N6570-DK and STM32N6 Nucleo-144) uses multiple discrete buck converters and LDO to power the N6. It must be possible to do it smaller. From I understand from the datasheet, the sequence of power-up goes like the following: 1. VDD and VDD18AON is applied 2. N6 outputs PWR_ON signal that must enable VDDcore/ internal SMPS3. VDDcore/internal SMPS( 1.8V) powers up and the N6 is alive. From the AN6000 and  AN5967 is believe I understand that you have two chooses:  1. Use an external SMPS for the VDDcore that can support dynamic voltage(as the TPS62088YFP with a transistor on the ref. boards) or 2. Use another external SMPS or LDO (1.8V) to feed the internal SMPS. With a small filter, it should be possible to use the same supply for VDD18Aon and the internal SMPS. Was anyone experience with using the internal SMPS with minimal externa

I’m performing low-power consumption tests using the NUCLEO-U545RE-Q development board. However, after entering STOP2 mode, I observed that the current consumption remains around 23 µA, which is significantly higher than the typical values stated in the datasheet (DS14216 Rev. 4, Table 59, page 162), where STOP2 mode is expected to consume only a few microamps. I’d like to understand what might be causing this discrepancy.Test Configuration:Hardware Platform:ST official development board NUCLEO-U545RE-Q.Clock and Peripheral Settings (STM32CubeMX .ioc):All peripherals are disabled, including the RTC.The system clock source is MSIS at 16 MHz.Both HSE and LSE oscillators are disabled.SRAM Configuration:Only SRAM2 (64KB) is enabled.SRAM1 and SRAM4 are disabled.Power Supply Configuration:The MCU is configured to use SMPS instead of LDO.Test Environment:Room temperature conditions (approximately 25 °C).Given the above setup, what might be the reason for the higher-than-expected power consump

In the Datasheet, Table 16 specifies TJMAX as 150 °C, but Table 17 indicates the TJ range as -40~130 °C, which one should I refer to?Table 16. Thermal characteristicsSymbol Ratings Value UnitTSTG Storage temperature range –65 to +150 °CTJ  Maximum junction temperature 150 °CTable 17. General operating conditionsTJ Junction temperature range    Suffix 6 version -40 105  °C    Suffix 3 version -40 130 

 I'm attempting to use a stm32g030 as an I2C slave device however the mcu fails to accept connections with the master device.  I have run this code on several different board including several using a stm32g031 but experience the same issue so I am tentatively ruling out a hardware error.  I use physical pull-up registers on SDA and SCL.I have printed out several important registers after calling 'i2c_slave_init'.GPI0A->AFR[1]: 0x00066000I2C2->OAR1: 0x00008010I2C2->CR1: 0x000000bdI2C2->IIMINGR: 0x10b17db5PCLK1 = 64000000 HzThere must be something I'm failing to do in my code but I've been staring at code for so long I simply don't see it.  Any suggestions would be greatly appreciated.-A// Rrequired Header Files //----------------------------------------------------------------------------- #include "stm32g030xx.h" #include "gpio.hh" #define slave_address 0x08 /** * @brief Initialize I2C2 as a 7-bit slave on PA11=SCL and PA12=SDA. * @PAram slave_addr

Which pin is the VSSA of STM32L051K8U6?

As title really. Keyboard project i'm working on in QMK required a bit more RAM so upgraded from the STMf401 to an STM32F412xE. Flashed firmware onto it RGB animations and OLED work correctly but USB device not recognised by computer. STM32cubeprogrammer shows 1mb of flash memory so concerned if JLCPCB have swapped it out for another model which would potentially be incompatible or just striahgt upgraded to the xG wtihout mentioning anything? Anybody experienced anything similar?

Post edited by ST moderator to be inline with the community rules especially with the code sharing. In next time please use </> button to paste your code. Please read this post: How to insert source code I am trying to use USB(CDC) without  the VBus connection on the STM32H755(Nuclueo-H755ZI-Q). But I can't. Please tell me the correct confinglation and procedure   I use ST USB middleware with CDC class. There is no sample project for STM32H755. So I ported myself. It worked.(with VBus)   I changed following points for using without VBus.   comment out following.(main() "main.c") HAL_PWREx_EnableUSBVoltageDetector();   comment out followings.(void HAL_PCD_MspInit(PCD_HandleTypeDef * hpcd) "usbd_conf.c") /* Configure VBUS Pin */ GPIO_InitStruct.Pin = GPIO_PIN_9; GPIO_InitStruct.Mode = GPIO_MODE_INPUT; GPIO_InitStruct.Pull = GPIO_NOPULL; HAL_GPIO_Init(GPIOA, &GPIO_InitStruct);   And I checked this. USBD_StatusTypeDef USBD_LL_Init(USBD_HandleTypeDef

Hi everyone,Has anyone interfaced the Micron MT35XU02GCBA2G12-0AUT (2 Gbit xccela Flash) with the STM32N6 XSPI controller? I  would like to know if it works with the existing Macronix presets or needs custom XSPI settings.Any working example or experience would help. Thanks!

Hi everyone,Has anyone interfaced the MX66UW1G45GXDI00 (1Gbit octal SPI Flash) with the STM32N6 XSPI controller?Any working example or experience would help.Thanks!

I am working on a project to connect QSPI flash memory to a PC as a USB mass storage device (MSC) using USBX, FILEX, LVLX, and THREADX on an STM32. This setup should allow the QSPI flash to appear as a drive in Windows.Previously, I successfully implemented a similar project using the MCU's internal RAM as the storage medium. However, after switching to QSPI flash, I encounter the error message: 'Please insert a disk into USB Drive' when connecting the device to a PC.To debug this issue, I tested the QSPI flash read/write functionality using FILEX + LVLX + THREADX without USBX, and it worked perfectly. This suggests the problem lies in the integration with USB MSC.I am including my code for review. Could anyone help identify any potential errors or missing steps in my implementation? Additionally, are there specific areas I should focus on to resolve this issue? Thank you.EDIT :lastlba ux_device_msc.c

Hi,I would greatly appreciate it if someone could share their thoughts here and let me know if my understanding is correct.Question 1. The STM32H573 supports both USB Host and Device, but why are “USB_OTG_FS” or “USB_DRD_FS” not visible in CubeMX?It appears to be due to the USB IP architecture. The STM32H573 integrates a dedicated USB 2.0 Full-Speed Host & Device block, but unlike some other STM32 series, it does not provide an OTG/DRD block with ID-pin based automatic role switching.As a result, CubeMX only exposes it as “USB (FS)”, and the user has to manually select either Host or Device mode.Question 2. Is the current CubeMX GUI template for the STM32H5 series limited to Device-only USB configuration?Both Host and Device functionality are supported by the hardware, but in CubeMX the GUI is still modeled primarily for Device-only use.This means that CubeMX does not automatically generate the corresponding code for Host operation, and the developer must manually initialize the HA