STM32 MCUs Products

Hello, we intend to implement a time-dependent channel change via the operational amplifier in voltage follower mode, as described in AN5306 - Rev 1 Page 31, 5.1. However, when checking the output, there is an unwanted gain (x2) on channel 2. Any idea where it comes from or what could be set incorrectly? Switching between channels using a timer and MUX works as expected, but the second channel has a gain of 2, although in voltage follower mode this should not be the case.For testing, 1 volt was connected to both channels and it was expected that 1 volt would come out at the output, despite the change via the MUX, but it changes between 1 volt and 2 volts because the second channel has this unwanted gain. CubeMX Configuration: OPATimer:Pins: code settings: /** * @brief System Clock Configuration * @retval None */ void SystemClock_Config(void) { RCC_OscInitTypeDef RCC_OscInitStruct = {0}; RCC_ClkInitTypeDef RCC_ClkInitStruct = {0}; /** Configure the main int

Tried running DMA with ADC simultaneously by configuring both in CubeMX, but I am not getting correct ADC values in the buffer. The sin wave from the signal generator is completely distorted. The ADC works individually without the DMA by filling the buffer through interrupts. The DMA is configured in circular mode. I even tried running the sample code of ADCgainCompensation from ST(modified a little to get values in a buffer), but had no success. 

Hello everyone,I’m currently working on a small STM32-based project where I’m designing a touchscreen menu display for a food & beverage ordering concept. The idea is similar to a coffee shop menu (for example a Dunkin’ Donuts style menu with categories, prices, and images) mainly to test UI responsiveness, memory usage, and image rendering on a constrained MCU.Project details:MCU: STM32F4 seriesDisplay: 3.5" TFT (RGB interface)Graphics: Simple icons, menu lists, and price labelsToolchain: STM32CubeIDE + HALUI framework: Lightweight custom graphics (not LVGL yet)I’m facing a few challenges:Optimizing Flash and RAM usage when loading multiple menu imagesBest practices for font rendering and scaling without excessive memory overheadWhether switching to external QSPI Flash is recommended for menu-style UI projectsAny suggestions for structuring menu data (categories, items, prices) efficientlyFor reference, I’ve mocked up a sample menu layout similar to a café menu here.This

Hello,i have a STM32F114 (Black Pill V3.0) and a strange timer problem. We all know that when setting the APB1 clock divisior is > 1, the APB1 timers gets twice as fast (2x, TIMPRE bit is not set). However, my timers are 4x when the divisor is > 2 (RCC_CFGR_PPRE1_DIV4, RCC_CFGR_PPRE1_DIV8, ...). It doesn't matter if i use HSI, HSE or PLL as sys clock source. My timer interrupt is twice as fast compared to a APB1 divisor of 1 or 2:APB1 divisor = 1: timer interrupt each 0.1 ms (10 KHz)APB1 divisor = 2: timer interrupt each 0.1 msAPB1 divisor = 4: timer interrupt each 0.05 ms (20 KHz)...I checked different frequencies (16 MHz, 48 MHz and 100 MHz sysclock). AHB and APB2 divisors are 1. I used two STM32F114 devices for testing. I double checked everything.  Code:// reset state assumed, HSI is 16 MHz unsigned long cfgr = RCC->CFGR; cfgr = (cfgr & ~RCC_CFGR_HPRE) | RCC_CFGR_HPRE_DIV1; // AHB clock = 16 MHz cfgr = (cfgr & ~RCC_CFGR_PPRE1) | RCC_CFGR_PPRE1_DIV8; // AP

We are using STM32U5G9's I2C with a diff-I2C to single ended I2C converter IC PCA9616. PCA9616 is used to program the STM32 MCU over I2C1 by converting diff-I2C to single ended I2C.However, while probing the I2C1 of the STM32U5G9, we are seeing negative overshoot and level shifting on it. It seems like MCU is taking control of the I2C while in the slave mode. See I2C_SCL_waveform1.pngAlso, we have tried disabling I2C1 of the MCU (by configuring it as a GPIO input only), by doing this we are able to mitigate the negative overshoot problem. I think the problem is with MCU, looks like it is taking control even if it is a SLAVE. See I2C_SCL_waveform2.jpgKindly let us know the exact reason and how to mitigate this issue.

Hello,We are currently using the STM32G070CBT6 microcontroller in one of our data logger devices, which operates on a three-phase power supply and is used in a transformer application. In our design, the microcontroller triggers a relay, and the relay controls a contactor. We are facing an issue where the STM32G070CBT6 is continuously rebooting during normal operation, which is affecting the overall functionality and reliability of the product. For your reference, we have attached the reset circuit schematic used in our design. We kindly request you to review the schematic and help us identify the possible causes of the continuous reboot behavior. Please let us know if any additional information, measurements, or test data are required from our side to assist in the analysis. Thank you for your support.

After a recent firmware update, I’m noticing some unexpected behavior during runtime on an STM32-based project. Has anyone experienced Mytime kroger portal similar issues or identified specific settings or configurations that commonly cause this? Any guidance or best practices would be appreciated.

Hello everyone,I am working with an STM32H7 device using the DSI host interface and would like some clarification regarding supported display resolutions.As per the STM32H7 datasheet, it is mentioned that:“Extended resolutions beyond the DPI standard maximum resolution of 800×480 pixels; the maximum resolution is limited by the available DSI physical link bandwidth.”Based on this statement, I would like to confirm the following:Can a 640×480 display be reliably connected to the STM32H7 using the DSI interface?Are there any practical limitations related to DSI lane count, lane speed, or refresh rate that would prevent using 640×480, even though it is below 800×480?Has anyone successfully driven a 640×480 display (at 60 Hz or other refresh rates) on STM32H7 using DSI + LTDC?Is the limitation purely bandwidth-based, or are there additional constraints in the STM32 DSI/LTDC implementation?Attaching the clock configuration of STM32CubeMX of DSI.Any insights, calculations, or real-world expe

 I am trying to source a 12.288MHz clock for an STM32L433 but having difficulties finding something.The clock is required for I2S playback with a bluetooth receiver (BT401).I have tried using the internal MSI RC to generate the 12.288MHz clock for SAI,  but the BT401 is misbehaving so it might be because the MSI RC clock has too much jitter.I was wondering if a ASFL1-12.288MHZ-EC-T would be suitable for the clock source for the SAI external clock input....https://uk.rs-online.com/web/p/crystal-oscillators/2403583Below is the setup...   The I2S amplifier (MAX98357A) seems to work fine with the 12.288MHz clock generated by the internal MSI RC and PLL. But the BT401 either requires multiple attempts to start playing and sometimes plays just a screeching sound for a few seconds then stops.  So I need to rule out whether the issue is caused by clock jitter by trying a more accurate clock source. I am currently using the STM32L433 Nucleo board whi

Hi Sir,Does any STM32 MCU support two independent USB 2.0 High-Speed (480 Mbps) interfaces simultaneously? I have observed that current H7 parts limit the second core to Full-Speed only. Do any newer series support true dual-HS operation?Thank you.

Hello everyone,I am migrating a design from STM32F446 (UFBGA-144) to STM32H533 (UFBGA-144) and noticed that FMC-SDRAM is no longer supported on the STM32H533.On the STM32F446, the FMC supports SDRAM and provides signals such as SDCLK, SDCKE, and SDNE, allowing the use of external SDRAM devices. On the STM32H533, these SDRAM-related signals and the FMC SDRAM mode are completely absent, and only SRAM/PSRAM/NOR/NAND memories are supported. From the reference manual and datasheet, this appears to be a hardware design choice.Could someone clarify the main reason for this architectural change between STM32F446 and STM32H533, and also for applications that previously relied on SDRAM performance, is OctoSPI PSRAM/HyperRAM considered the recommended alternative on STM32H5? Thank you in advance for your clarification,Best regards,Aymen

I was doing reset through SPI command and expected results are not happening. this is the line i was expecting to reset the MCUSCB->AIRCR = (NVIC_AIRCR_VECTKEY | (SCB->AIRCR & (0x700)) | (1 << NVIC_SYSRESETREQ));where#define NVIC_AIRCR_VECTKEY (0x05FA << 16) #define NVIC_SYSRESETREQ 2also my watchdog is running and expected to reset the system.code snippet FLASH_Unlock(); FLASH_ErasePage(0x08013000); FLASH_ProgramWord(0x08013000, (uint64_t)0x0000000000000000ULL); FLASH_Lock(); FLASH_Unlock(); FLASH_ErasePage(0x08013008); FLASH_Lock(); SCB->AIRCR = (NVIC_AIRCR_VECTKEY | (SCB->AIRCR & (0x700)) | (1 << NVIC_SYSRESETREQ)); __DSB(); while (1); Edited to apply proper source code formatting - please see How to insert source code for future reference.

Since the description of the FDCAN controller in the reference manual ofthe STM32G474 was not detailed enough, I looked around for more Informationand found the Application Note AN5348 ("FDCAN peripheral on STM32 devices ").But that didn't make me feel more confused.- but that didn't answer myquestions, I'm even more confused nowAt the moment I am busy sending CAN messages.According to AN5348, the FDCAN has dedicated Tx buffers and optionallya Tx FIFO or a Tx queue (Figure 4. CAN message RAM mapping.)The FDCAN controller on the STM32G474 seems to be like aminimal implementation of the controller described in the AN5348 -obviously 32 Tx buffers are possible, but the STM32G474 has according to.Reference Manuel only 3 of them. And as I understand I understand, they areused as a TxFIFO or a TX queue - therefore there are no "dedicated" Tx buffer !?Or can I simply use the 3 buffers in a detected manner by ignoringthe TXFQS registers and working only with registers TXBRP, TXBAR and TXBTO?I a

Hi all,I've been working through this tutorial: How-To-Create  to bring up LWIP + FreeRTOS on the STM32H735IGK development kit. I'm using STM32CubeIDE 1.18.0, FreeRTOS with CMSIS-v1, and STM32Cube FW_H7 version 1.12.1I noticed that pinging is very sporadic, and the STM32 eventually stops replying to ARP requests. I've attached a couple of pictures(wireshark captures) that describe the problem.For reference, here are relevant screenshots my MPU settings, linker script, ethernetif.c, and lwiopts.h files. However, if I disable D-Cache, then pinging becomes stable (I'm able to ping for > 30 minutes continuously). I don't want to disable D-Cache, as my MPU should be disabling caching for the relevant memory regions.I understand that MPU regions have priority, and I'm overlaying region 2 onto region 1, but both regions disable caching. What's going on here?Please let me know if there additional information that you may need.Thank you!@Piranha, @STea, @Pavel A. 

I am running the ADC using a timer trigger and DMA to sample a sinusoidal signal.The captured samples are transmitted to a PC via UART.However, as shown in the attached image, the ADC output appears to be step-like and does not capture smoothly changing values, even though the input signal is a clean sine wave.I have checked the external reference voltage, interrupts, and the microcontroller power supply, but the issue still persist

Hi,We are facing the same issue like the below community post. https://community.st.com/t5/stm32-mcus-products/flash-via-i2c-bootloader-problem-for-stm32g0b1kbu6/m-p/636467#M234685 But we are using  'STM32G431RBT6' in our project, kindly let us know if any specific pins need to be handled in this MCU for proper operation.Kindly reply on this as early as possible. Thanks,Ananthu

I created a custom STM32F411 PCB. I can program it and blink a LED for example just fine. I also have a STM32 blackpill board which uses the same MCU. When I run some USB HID code it works fine on the blackpill but once uploaded to my custom PCB and I plug it into my windows PC, it says the usb device malfunctioned and is not working. I followed all the guidelines from the datasheet for the USB design. (I dont need external pull-ups for D+, no need for VBUS sensing). Also I have a 25Mhz HSE clock that is properly configured for the precise 48Mhz USB clock even though its only running at FS. Any ideas to why this might be happening?  

I am using the STM32H725RE (68-pin package).My goal is to have full duplex SPI communication with a 16 bit shift register using the stm32h7 as the SPI master (with no dma controller).I am using the SPI3 with the following pin (12MHz)PA15 (SPI3_nCS), PC10 (SPI3_SCK), PC11 (SPI3_MISO) and PC12 (SPI3_MOSI).With the following code it is already possible to write the data successfully and the shift register also sends the data correctly to the MISO wire. (as you can see in the logic analyser screenshot)But I have problems reading the receive buffer, the flags are set correctly (RXP is set correctly), but when I read the RXDR I only read the data 0xFFFF, although other data should be read as shown in the logic analyser screenshot?#include <stm32h7xx.h>#include "stm32h725xx.h"  #define pSpiSR SPI3 static void initSPI3() { RCC->APB2ENR |= RCC_APB2ENR_SPI1EN; // SPI1 Peripherie Enable (FLASH)// PA15 (SPI3_nCS)GPIOA->MODER &= ~(GPIO_MODER_MODE15);GPIOA->MOD

I am trying to flash a .bin file to an STM32F767ZI Nucleo board using UART via STM32CubeProgrammer. While I can successfully connect to the board using ST-LINK, I am unable to establish a connection over UART and encounter the following error:  I have tested USART1, USART2, and USART3 with various baud rates, and configured the BOOT0 pin to logic high followed by pressing the reset button, as described in the reference manual. However, the issue persists. Please suggest possible causes/solutions for this problem.  Thank you. Arun Badiger,

helloDescription:I'm currently working with the STM32U585 and encountered an issue related to GPIO behavior after waking up from standby mode.Before entering standby, I configure certain GPIO pull-up:(No external pull-down resistors on the affected pins)HAL_PWREx_EnableGPIOPullUp(PWR_GPIO_D, PWR_GPIO_BIT_14); HAL_PWREx_EnablePullUpPullDownConfig();However, after the MCU wakes up from standby (via wakeup pin), I observe a brief voltage drop on those previously GPIOs, about 300ms. This drop occurs before the firmware reinitializes the GPIO configuration:i added a delay(implemented with i--)before calling the HAL_Init() function, and the voltage drop became less pronounced:Questions:Is this behavior expected due to the standby mode reset mechanism?Is there a recommended way to retain GPIO output levels across standby wakeup?Could this be related to the IO pull settings or the boot configuration?Are there any hardware-level workarounds to avoid this voltage dip?Why does delay have such an

I have seen the question asked many times, references made but the question never gets answered with precision.  So, once again...I want to use HAL_I2C_Master_Seq_Transmit_IT along with receive to read an I2C device register.1. START SLAVEADDRESSWR (N-Byte RegAddress)2. REPEATEDSART SLAVEADDRESSRD (N-Byte returned data) STOPStep 1 would us HAL_I2C_Master_Seq_Transmit_IT Step 2 would use HAL_I2C_Master_Seq_Receive_ITWhat are the "Option" parameters such as I2C_FIRST_FRAME, etc. for each of these calls to avoid a STOP between the sequences and make the REPEATEDSTART occur, and of course finish up with a STOP?And using the memory read/write calls does not work because the register memory address cannot be of arbitrary length.  Don't have a scope handy to see the protocol generated, so I won't know things are working until my device actually returns correct default register values.   

Using the information from the chip's datasheet and reference manual:I have the following routine (using the HAL routines).  My issue is that I have verified code execution and setting of the two OB values via JTAG, but when the system reset is issued I go right back into user code at 0x0800 0000 and not the DFU loader as expected (0x0BF9 0000).This seems like it should be simple... what am I missing or doing wrong?   void EnterFirmwareUpdateMode(void){HAL_StatusTypeDef status; // See RM0438 STM32L562 Ref Manual - pg 193 sect 6.4.2 option bytes programming// See boot configuration pg 98 table 6, line 4 - Set Flash OPTR nBoot0 to 0 and nSWBOOT0 to 0status = HAL_FLASH_Unlock();status = HAL_FLASH_OB_Unlock(); CLEAR_BIT(FLASH->OPTR, FLASH_OPTR_nSWBOOT0_Msk);CLEAR_BIT(FLASH->OPTR, FLASH_OPTR_nBOOT0_Msk);SET_BIT(FLASH->NSCR, FLASH_NSCR_OPTSTRT_Msk); // Seems un-needed since Launch supposedly reboots processorstatus = HAL_FLASH_OB_Lock();status = HA

Hello, In the MCU datasheet, there is a table on page 200: Table 72. Typical dynamic current consumption of peripherals.What is the meaning of the current writing in the peripherals on stop modes, since in this mode, all clocks in the core domain are stopped? I saw that there is an option to enable MSIS/HSI16 in stop mode if a peripheral requests it, but according to what frequency?  The frequency of the processor or the frequency that entered the clock tree for the peripheral that required it?moreover, I tried to simulate it on STMCube and saw that adding peripherals does not increase current consumption in stop mode, while on datasheet writes that they consume current in units of uA/MHz. thank you amit

Hi, I am configuring the ADC in single-channel continuous conversion mode using DMA. However, once I call HAL_ADC_Start_DMA(&hadc, &AD_RES, 1), the main loop stops executing, and the HAL_ADC_ConvCpltCallback() function is not triggered.I noticed that setting hadc.Init.DMAContinuousRequests = ENABLE causes the main loop to become blocked.How can I configure DMA to continuously retrieve ADC values without blocking the main loop and the HAL_ADC_ConvCpltCallback() will be called continuously? I'm following this ADC tutorial: https://deepbluembedded.com/stm32-adc-continuous-conversion-mode-dma-poll-interrupt-single-channel/   /* USER CODE BEGIN Header */ /** ****************************************************************************** * @file : main.c * @brief : Main program body ****************************************************************************** * @attention * * Copyright (c) 2024 STMicroelectronics. * All rights reserved. *

Hello everyone,This is my first post on the ST Community forum.I recently moved from a custom 6-layer board using STM32H725IGKB to a simpler 4-layer board using STM32H723ZGT6. Both designs use an external OCTOSPI memory, with 50 ohm controlled-impedance routing and 33 ohm series resistors on the signals.On the new 4-layer board, I am seeing read/write errors on the OCTOSPI interface, while the original 6-layer board works reliably with similar routing and firmware.I would like to ask whether the OCTOSPI output driver characteristics or output impedance differ between STM32H725 and STM32H723, or if these issues are more likely related to signal integrity, stack-up, or return-path differences on a 4-layer PCB.Any guidance or experience would be appreciated.Thank you in advance.