STM32 MCUs Products

Hello STM32 Community,I'm having trouble getting UART communication working on my NUCLEO-L4R5ZI-P board and would appreciate any guidance.Board Details:NUCLEO-L4R5ZI-P with STM32L4R5ZIT6PUST-Link firmware updated to the latest versionProgramming/debugging works fineLED control works perfectlyProblem: No UART output appears in any terminal program, despite testing multiple configurations. The virtual COM port is detected by both macOS and Windows, but no TX activity occurs (TX indicator never lights up in terminal programs).What I've Tested:USART2 on PD5/PD6 (as shown in STM32CubeIDE pin configuration)USART3 on PD8/PD9 (based on datasheet D0/D1 assignments)LPUART1 on PG7/PG8 (documented as virtual COM port option)USART2 on PA2/PA3 (standard NUCLEO configuration)Multiple alternate function mappings (AF7, AF8)Different baud rates (9600, 38400, 115200)Tested on both Mac (CoolTerm) and Windows (PuTTY)Hardware Verification:Solder bridges SB130 and SB131 have resistors (closed)GPIO test on PD

I think from what I've read this should be possible, but before diving into the details and trying to make it work I'm hoping someone can just give me a yes/no answer for this question. Basically, what I'm trying to do is use DMA to send a block of SPI data and when that block is done start another DMA transfer on another channel sending a very short block of data to a GPIO port BSRR register to toggle some I/O pins and when that block is done restart the first DMA transfer of SPI data. The idea is that the SPI data followed by the toggling of a few I/O pins (all on the same GPIO port, through a sequence) in an infinite high speed loop. Can MDMA be used to make this happen on an STM32 micro?Thanks.

Hello,We are working with an STM32F03 and an ECS-320-8-37B-CKY-TR 32 MHz crystal (CL = 8 pF).Our earlier design used an 8 MHz crystal (CL = 8 pF) with 4 pF load capacitors and a 5.1 kΩ series resistor. After switching to the 32 MHz crystal, the HSE no longer starts. This sparked criticism about the correct component values depending on the crystal used.Here are some results from my testing with 32 MHz + 5.1 kΩ:Startup works reliably at ~0 Ω and ~1 kΩMarginal at ~1.5 kΩFails at ≥2 kΩBased on the ECS-320 datasheet (CL = 8 pF, and estimated ~3 pF stray), the correct load capacitors should be ~10 pF each, not 4 pF.Where we are unsure is the interpretation of AN2867:Harmonic suppression (§3.5.3): Formula Rext = 1/(2πfCL²) → ~1.2 kΩ at 32 MHz with 4 pF loads, which matches our *failing* results.Drive level trimming (§3.3): Says to use Rext = 0 Ω unless the drive exceeds the crystal spec. We don’t have low-C probes to measure the drive directly.Empirical: Anything in the hundre

 Hello Community, I am using 2 function calls __LL_ADC_CALC_VREFANALOG_VOLTAGE();__LL_ADC_CALC_TEMPERATURE_FLOAT();My implementation:uhADCxConvertedData_VrefAnalog_mVolt = __LL_ADC_CALC_VREFANALOG_VOLTAGE(aADCxConvertedData[1], LL_ADC_RESOLUTION_12B);temperature = __LL_ADC_CALC_TEMPERATURE_FLOAT(uhADCxConvertedData_VrefAnalog_mVolt, aADCxConvertedData[2], LL_ADC_RESOLUTION_12B); I am seeing the above macros not respond and there is a hard-fault whenever I call the above functions. Any help would be appreciated.  Thank you

Hello,I am trying to use the GPDMA linked list on an STM32U5 to toggle seven chip-select GPIOs before and after SPI transfers.Setup:MCU: STM32U575ZITXI build a linked list of nodes:Write CSx_Pin to GPIOx->BRR (drive CS low)Dummy delay node (memory→memory)Write CSx_Pin to GPIOx->BSRR (drive CS high)word width, DataSize = 4, SrcInc = FIXED, DstInc = FIXED.Destination addresses are the GPIO BSRR/BRR registers.Problem:Only 3 out of 7 chip-select pins actually toggle when the DMA queue runs. The working pins are:PE3PE1PB6The non-working ones are on GPIOG (PG9, PG11, PG13) and PB8.If I write to these pins directly from the CPU with HAL_GPIO_WritePin, they work correctly. Only DMA writes fail.Questions:Are all GPIO ports on STM32U5 supposed to be reachable by the GPDMA?Is there a known limitation where certain GPIO ports (e.g. GPIOG) cannot be written by DMA?Any clarification on which GPIO ports are DMA-accessible would be appreciated.Thank you.Linked List Setup Code :#define ADC_COUNT

STM32G473 via SPI I have most of the other commands working, but the Get Checksum command (0xA1) fails to return an ACK when I send the CRC init value. I am using the default CRC configuration:#define DEFAULT_CRC32_POLY 0x04C11DB7U#define DEFAULT_CRC_INITVALUE 0xFFFFFFFFU It accepts the command, start address, memory size, and polynomial, then fails on the init value.I haven't found any documentation that indicates what init value is accepted on this MCU, but I do find it hard to believe it does not accept the default init value from the HAL itself.

Hello everybody,in our application, we want to avoid using the ADC software calibration procedure (not even once).We hence think about writing a fixed value to the Calibration register CALFACT as we saw that most of the times the calib value is very close to 64 (half of the 7-bit range).We can accept a comparably high offset error of the ADC (+-12LSB at 12 bit) and from our measurements so far we think we can work without calibration, however we cannot find any worst-case offset values for the uncalibrated ADC anywhere. So our questions are:Can you confirm that 64 is the somewhat "neutral" value for CALFACT?Where can I find the worst case offset error of the ADC without calibration? Best regards and thank you very much in advanceSamuel

In the RM for the H743 there is little information about using IO cell compensation aimed at reducing noise on VDD and EMI radiated.Posts show the following calls to active:-__HAL_RCC_CSI_ENABLE();__HAL_RCC_SYSCFG_CLK_ENABLE();HAL_EnableCompensationCell();The RM briefly mentions values for PMOS and NMOS transistors to presumably control slew rates, but I cannot find any data on how to determine the bit values.There is a function, HAL_SYSCFG_CompensationCodeSelect(), but again there are no examples of its use.  Google also shows no example code!I have tested the sample code posted on this forum but it does nothing noticeable to reduce noise on the VDD line.Is more information available about how to reduce noise via slew rate adjustment?Hello STM staff, is there anybody out there? 

Hi, I am evaluating the STM32H7R7Z8J6, intended to working with a TFT-LCD which is working in parallel RGB interface with DE mode only. The HSYNC and VSYNC signals are not connected. Both AN4861 (Introduction to LCD-TFT display controller (LTDC) on STM32 MCUs) and RM0477 (STM32H7Rx/7Sx Arm®-based 32-bit MCUs) documents only SYNC+DE mode, but the does not mention if the DE-mode-only is supported or not? Could you help to point out the documentation where explains how the LTDC working for DE mode in detail?  Thanks! Leo    

Hi everyone,I am working on an STM32H7A3ZI and I'm trying to to exchange audio data with an SGTL5000 audio codec. Because i want to both send and receive data from the codec i configured the I2S peripheral on the STM32 to Full-Duplex Master mode in Cube MX.My problem:Transmitting data using the HAL I2S functions (HAL_I2S_Transmit, or HAL_I2S_Transmit_DMA) works fine, but when i try to receive data (also using the HAL functions) the bit- and word-select-clock won't start. If i first transmit data and then try to receive everything works fine, because the clocks stay on. If i change the I2S config to Half-Duplex Master Receive mode, just receiving also starts the clocks.So in Full-Duplex Master mode i have to transmit data first (or at least write some data into the transmit data register, which starts the clocks), before i can receive data.My question:This seems to be intended behavior, but i couldn't find any documentation on it. Why is this implemented like that?

Hi all! AGENDA: Need to verify the external QSPI flash (AT25Q128A) all sectors Write, Read and Comparing with STM32L496ZG-P using driver code. APPROACH: For write, I am have created a buffer which comprises of page size of 256, and I am using two "for" loops one outer "for" loop for incrementing total sectors i.e. 4096 times and inner "for' loop as there are 16 pages for a single sector I am incrementing it to 16 times.  In below case I am trying to write letter O to all sectors and read and compare,  // Fill buffer with character 'O' for (int i = 0; i < PAGE_SIZE; i++) { page_buffer[i] = 'O'; } for (uint32_t sector = 0; sector < TOTAL_SECTORS; sector++) { uint32_t base_address = sector * SECTOR_SIZE; for (uint32_t page = 0; page < PAGES_PER_SECTOR; page++) { uint32_t page_address = base_address + (page * PAGE_SIZE); //// Write to flash if (CSP_QSPI_WriteMemory((uint8_t*)page_buffer, page_address, PAGE_SIZE) != HAL_OK) { // flash_write_success = false; //

I have a problem I can't solve.In a previous project, I used an STM32L4A6 and set the PC8 and PC9 lines high before entering the system bootloader. After starting the system bootloader, these lines remained high. They were used to maintain power to the device.In the new project, the MCU was changed to an STM32F446. I used the PD10 and PD12 lines to maintain power after confirming with the AN2606 that they were not being used by the system bootloader. Unfortunately, after starting the bootloader, both lines are reset.Why does this happen?

Apologies if this is the wrong group for this query. I have implemented a library from scratch which performs the host side of a DFU upgrade (avoids the dependencies in CubeProgrammer_API.dll, for which I could not find source). The code works just fine but I have a question about the expected values of bAlternateSetting across the whole range of STM32 devices.For the STM32U575, there are three DFU Interface Descriptors with bAlternateSetting values of 0, 1 and 2. These correspond to 0=Internal Flash, 1=Option Bytes, 2=OTP Memory. [This is very clear from the memory descriptor string corresponding to the iInterface value of each interface.]My question is: are these values consistent across the range of STM32s, or might some devices have (say) 1=Internal Flash or whatever?Is there any available documentation for this? I've spent quite a bit of time trawling various UMxxxx and ANxxxx as part of creating this library, but have not found much about bAlternateSetting.The behaviour of D

Hello everyone,I’m facing an issue with an STM32L4-based design where the USB FS Device stack (CDC) sporadically fails to start correctly. Maybe someone has seen similar behavior or can point me to potential root causes. System overview / setupMCU: STM32L4 (CubeMX / HAL / FreeRTOS)Clocking:MSI as system clock (16 MHz)USB via PLLSAI1 (48 MHz)USB: FS Device Stack (CDC), initialized after HAL_Init() / SystemClock_Config() in the first TaskESD protection: USBLC6-2SC6Lines: no series resistors on D+ / D-Firmware Package Name and Version: STM32Cube FW_L4 V1.15.0Hardware layout: Clock configuration: USB Stack configuration:  Observed behaviorOn several boards, the USB stack does not reliably start after power-up.In that case, the firmware blocks → Watchdog reset after ~8 s → endless reset loop.Disconnecting/reconnecting the supply sometimes fixes the issue, and the USB connection to the PC works normally.Interesting: When probing D+ or D- with an oscilloscope, th

I am having trouble connecting to the STM32N6 with SWD.I have implemented a design using the STM32N645X0H3Q (though I have placed the STM32N647X0H3Q) using external VDDCORE. R110 is not mounted (to set VLXSMPS to NC).On startup I have VDDIO (3.3V) and VDDA1V8ON (1.8V) to the MCU, and the MCU activated PWR_ON (I have VDDA1V8ON to the PDR_ON pin, A1 on another page). This activates the reset of the power, including VDDCORE. All voltage measurements are as expected on the board.When I try to connect to the board using SWD in STMProgrammer (v2.20.0), I see the 3.3V, but the STMProgrammer does not connect. I am using a Minnie V3 (v V3J16M8) on Windows. I have tried lower frequencies and all modes and reset modes without success. I should mention that on my prototype board, I have not mounted external crystals, flash or ram. Though I believe that is not necessary for STMProgrammer to see the MCU. Any help is greatly appreciated!

OS: `Linux Mint 22`Kernel Version: `6.8.0-48-generic`STM32CubeMX version: `6.14.1`STM32 Chip: `STM32F401RET6`I'm trying to just run a simple light blink script for testing. I'm using a Segger J-Link EDU Mini and programming over SWD using a 10-Pin connection. I'm using a CMake project generated by STM32CubeMX and I am debugging from VSCode (which is launching `JLinkGDBServerCLExe`).If I run `Start debugging` I get this output (and it just stops there indefinitely):```/opt/SEGGER/JLink/JLinkGDBServerCLExe -singlerun -nogui -if swd -port 50000 -swoport 50001 -telnetport 50002 -device STM32F401RESEGGER J-Link GDB Server V8.38 Command Line VersionJLinkARM.dll V8.38 (DLL compiled May 28 2025 12:45:51)Command line: -singlerun -nogui -if swd -port 50000 -swoport 50001 -telnetport 50002 -device STM32F401RE-----GDB Server start settings-----GDBInit file: noneGDB Server Listening port: 50000SWO raw output listening port: 50001Terminal I/O port: 50002Accept remote connection: yesGenerate logfile:

Hello ST Community,I'm facing a MIPI DSI configuration issue with my STM32U5A9 and TFT LCD. When using PHY DSI as the DSI lane byte clock source, my code fails with a timeout on HAL_DSI_ShortWrite. When I switch to PLL3P, the initialization proceeds, but the LCD displays distorted images.Request for Assistance: I'm new to MIPI and suspect a misconfiguration in clock settings. Any insights on proper configurations or similar experiences with STM32U5A9 MIPI DSI would be greatly appreciated.Details:MCU: STM32U5A9LCD: TFT LCD with st7796SClock Source: PHY DSI (fails) / PLL3P (distorted images)  Your help in resolving this challenge is appreciated. Share your insights or suggestions if you've encountered a similar problem.Thank you,

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 read the jedec id from the  MT25TL512HBA8E12-0AAT TR using stm32h750xbh6 with qspii configured qspi using mx like follows:hqspi.Instance = QUADSPI; hqspi.Init.ClockPrescaler = 1; hqspi.Init.FifoThreshold = 4; hqspi.Init.SampleShifting = QSPI_SAMPLE_SHIFTING_NONE; hqspi.Init.FlashSize = 25; hqspi.Init.ChipSelectHighTime = QSPI_CS_HIGH_TIME_6_CYCLE; hqspi.Init.ClockMode = QSPI_CLOCK_MODE_0; hqspi.Init.DualFlash = QSPI_DUALFLASH_ENABLE; i configured the clock using rcc enabled hse and lse and finally giving the clock for qspi around 50mhz the function im using to read is the below one static HAL_StatusTypeDef QSPI_ReadID_3B(QSPI_HandleTypeDef *hq, uint8_t id[3]) { QSPI_CommandTypeDef c = {0}; c.InstructionMode = QSPI_INSTRUCTION_1_LINE; c.Instruction = 0x9F; /

Hello Community,I’m facing an issue with Pin PC15 on my board. I am unable to configure or use it as a GPIO, either as input or output. I’ve tried basic initialization, but it doesn’t seem to respond as expected.Has anyone experienced a similar issue with PC15, or is there a special configuration/limitation I should be aware of? Any guidance or suggestions would be greatly appreciated.Thank you in advance!Clock Configuration:LSI at 32 KHzHCLK at 86 MHz

Hi all,I am experimenting with H7 ADC (after having tried the G4 ADC).I see in the HAL that the calibration, HAL_ADCEx_Calibration_Start(), for H7 MCU wants a parameter more than G4. One should specify ADC_CALIB_OFFSET or ADC_CALIB_OFFSET_LINEARITY.I am confused, and reading the datasheet does not help me. Can't understand the difference between the two methods.Should I use ADC_CALIB_OFFSET  or  ADC_CALIB_OFFSET_LINEARITY, when calling the calibration_start()?Or should I call the calibration *twice*, one for each option?TY,linuxfan

I saw a strange behavior when using STM32F401RBTx, to show you I added only 1 output as LED and  toggled it.  I have just that much code. I tried with 16 MHz, 48 MHz, 64 MHz, 84 MHz. It went hard fault when speed is 64 MHz or 84 MHz.    This is the clock setting which calculated by STM32CubeIDE.   It goes inside of HAL_RCC_ClockConfig function and can't go beyond HAL_InitTick function. When I put breakpoint inside HAL_InitTick I could delay hard fault little bit and saw below callstack. I tried this with 2 microcontrollers and same thing was happening. How can I solve this? Thank you.  

Hi ST expertI'm ready to use STM32G473CBUx now. According to the datasheet, the STM32G473CBUx does not have an analog ground VSSA, only a ground VSS. I have questions:1. The analog input of the internal ADC/DAC is referenced to the chip's VSS, or has STM32G473CBUx internally partitioned an analog ground? 2. When I design the schematic, is the analog power VDDA referenced to VSS? 

Hello everyone!  Recently, I have been developing a firmware product based on STM32H750, using FreeRTOS and LwIP. Because the application scenarios for this product frequently involve large volumes of broadcase messages, while the product's own communication does not use broadcast at all. So I enable the ETH MAC filter to detect and drop the broadcast frame by hardware itself, which means reducing the processing load on LwIP.   However, after that I discovery a problem, which is that the hardware also drop ARP broadcast request too! Just because the destination mac address filed in ARP broadcast request is FF:FF:FF:FF:FF:FF. The result is that many functions relying ARP have been affected, such as ICMP, UDP unicast, TCP client etc. In these functions, if the remote host's ARP cache does not contain the hardware's IP and MAC addresses, ARP broadcast requests and responses must be used.   In the datasheet RM0433, I found a bit called ARPEN(bit 31) in the ETH_MACC

I am implementing a system with two STM32H753 microcontrollers. MCU1 reads ADC data and sends it over UART to MCU2 using UART DMA on ADC conversion. MCU2 reads data from UART via DMA and is supposed to do some filtering (among other things) to the received data. Earlier, all of the tasks were done by a single MCU (hence it was simpler, as we had access to the ADC data buffer already). The issue I am facing is that the UART Receive DMA is never triggering the HAL_UART_RxCpltCallback() callback no matter what I do. I have tried the same with UART_Receive_IT() with no results either. To help me ensure that it is not a configuration issue, I configured the same UART in a separate project (which is more of a simpler example of what I am trying to do) and verified my configuration to be working (posted about it earlier). 

Hello, We're working on a custom board for the STM32H750IBX. Our boards arrived. The first time, the chip was installed poorly and shorted out. We assembled a new board at the SMT factory with the new chip, but we still can't connect to the chip to program it.We checked the voltage and the connection as best we could. We couldn't check the chip itself because it's a BGA package. However, we did an X-ray, and everything looks fine.We tried connecting with STMCUBE IDE and ST_LINK Utility, but they still can't recognize the target.We've exhausted all possible solutions and are asking the community for help. Schematics:STM32H750IB SCHEMATICS Layout:RED ARE SWD LINES