STM32 MCUs Products

Hello,Trying to implement SPI bus (Master only) to transmit 16 bit to LCD, utilize linked list GPDMA ch 6, I looked at the UART linked list example and tried to modify it to work with SPI with no success, only the first half word is sent and then it stops without any interrupts...I'm using the "HAL_SPI_Transmit_DMA" after initiate all linked list array by CubeMx.Does any one has any SPI linked list example?     

Reading through the docs for the STM32 G474 FDCAN TX sections, it seems like if FDCAN is in FIFO mode, there is no way to cancel a pending message. The message can only be dequeued from being sent. If this is the case, how should one handle the case of the currently TX'ing message not ever being acked? In this case, if the message is never acked, it cannot ever be dequeued and the FDCAN TX will essentially be stalled for any other messages. I do see the cancellation functionality, but it seems as though none of it applies to FDCAN in FIFO mode?

Hi,   I want to start using the STM32U073KCU6 MCU in an upcoming product but don't have a ton of familiarity with STM MCUs. My attraction to the device is based around the integrated USB functionality and I am trying to figure out if it can be field programed using the USB lines only (and of course being powered on).   What do I need to do in my pcb to make sure this is possible? what software tools (command line scripts or otherwise) do you recommend for this programming step?   Best,   Teva  

Hi,I have a situation where the configured watchdog on my STM32L031 does not trigger even though the MCU gets stuck in an I2C function. In my program flow, I first run through some initializations (as well as I2C_Init()) and then start the IWDG (Start_WDG()). I then try to establish an I2C connection to another device. In some cases this fails and I get stuck on line "while(!(I2C1->ISR & I2C_ISR_TXIS));". Surprisingly, in this situation the watchdog does not trigger as expected. I am of course aware that the code in this form is not properly programmed and error handling in this situation solves the problem (implemented a timeout which itself does a system reset). Nevertheless, it would be interesting to know why the IWDG in this version does not trigger.Thanks in regard.Greetings from Salzburg

I am configuring wakeup pin PA0 to WAKEUP1 by wirting 01 (pull-up) at WKUPPUPD (PWR_KUPEPR) as said at RefManual by using "HAL_PWREx_EnableWakeUpPin ".   PWREx_WakeupPinTypeDef sPinParams; sPinParams.PinPolarity = PWR_PIN_POLARITY_LOW; sPinParams.PinPull = PWR_PIN_PULL_UP; sPinParams.WakeUpPin = PWR_WAKEUP_FLAG1; HAL_PWREx_EnableWakeUpPin (&sPinParams);   After that i go to standby mode by using: HAL_PWR_EnterSTANDBYMode();   Then at standby mode, there is no pull up at PA0. At the manual it is said that the pull up config is kept at standby mode. Do i have to do something else?   Thanks!!    

An application created directly for the configurator where TIM3_CH! is set to PB4 where the internal clock is either ticked or not ticked it crashes at if (HAL_TIM_PWM_Init(&htim3) != HAL_OK) with No source available for "uwTickPrio() at 0x20000004"  STM32CubeIDE Version: 1.18.1Build: 24813_20250409_2138 (UTC) static void MX_TIM3_Init(void) { /* USER CODE BEGIN TIM3_Init 0 */ /* USER CODE END TIM3_Init 0 */ TIM_MasterConfigTypeDef sMasterConfig = {0}; TIM_OC_InitTypeDef sConfigOC = {0}; /* USER CODE BEGIN TIM3_Init 1 */ /* USER CODE END TIM3_Init 1 */ htim3.Instance = TIM3; htim3.Init.Prescaler = 0; htim3.Init.CounterMode = TIM_COUNTERMODE_UP; htim3.Init.Period = 65535; htim3.Init.ClockDivision = TIM_CLOCKDIVISION_DIV1; htim3.Init.AutoReloadPreload = TIM_AUTORELOAD_PRELOAD_DISABLE; if (HAL_TIM_PWM_Init(&htim3) != HAL_OK) { Error_Handler(); } sMasterConfig.MasterOutputTrigger = TIM_TRGO_RESET; sMasterConfig.MasterSlaveMode = TIM_MASTERSLAVEMODE_DISABLE; if (H

The 32-pin package doesn't seem to have any kind of external clock input at all, and the device does not feature "crystal-less USB". How do we provide a stable clock for USB then?

Greetings,I have acquired Nucleo-U031R8 as I was searching for ULP controllers and specification of this one was good. I am currently trying to lower current consumption as low as possible. Previously, I have used Nucleo-L073RZ where I was able to achieve approx. 300uA in low power run mode and 150uA in sleep mode. I was hoping to get much lower current consumption using U0 series processor but it seems like it is consuming more power then L0 series. Note that in both controller program and other peripheral configurations are same. Can someone please suggest why it is happing and what can I do about it? Thank you so much for the help. @KDJEM.1 @LPetr.1 @TDK /* USER CODE BEGIN Header */ /** ****************************************************************************** * @file : main.c * @brief : Main program body ****************************************************************************** * @attention * * Copyright (c) 2025 STMicroelectronics.

Can the STM32F469I-DISCO support reading/writing a FLASH Drive on its UTB-OTG interface ?What software does it need for this ? (Pardon my ignorance - I'm a Hardware guy!).     

I'm using STM32 with HAL and LL drivers (H7 and G4 families, in particular, but I think this can be a general question) and I trying to avoid being forced in recursive faults when reading a flash location with broken ECC. In my application it may happen to try to read a broken flash location.In TrapHandler I'm able to intercept the error, report it to flash driver, clear error flags, and avoid any reset.However, when returning from TrapHandler, I'll fall back on the same flash instruction which generated the fault, which will try to read the same location again, and so another fault will be generated in loop.Is there a way to continue with the execution in a portable way after encountering this fault? For a deeper understanding, this is one of the specific use case in which I would need the above behavior:When in bootloader, before jumping to application, I calculate the CRC of application flash, compare it with the one stored to another flash location, and jump to applicatio

Hello at allTo do this, I use STM32CubeIDE and STMCubeMX to configure my I/O interfaces and serial buses, including two SPI buses to control my converters.Only the hardware configuration of an SPI bus is limited to between 8 and 16 data buses, whereas my converters operate with between 24 and 32 bits of data...However, in hardware SPI, my sync (CS) goes back after an 8- to 16-bit frame, whereas I need it to remain at 0 to meet the TI requirement.So I tried to manage the sync pin in IO mode, but it still goes back...I tried using DMA, but the CS signal delay I'm managing is too long before the start of my frame and ends long after it; I must be at about sixty microseconds, too long.Note that I'm running my MCU at 24 MHz and I want to be able to retrieve my converted data in about 10 µS.Currently, I'm using SPI bit bang, or I've configured my SPI port as IO, and I'm retrieving my values ​​in 212 µS, which is too long...So, should I try assembler?...Do you have any advice on this? A recom

I am dealing with an I2C lockup issue where the I2C bus is locked up periodically and I need to toggle the SCL pin to free up the bus.  To test my theory and make sure that the fix works I just used an osDelay(1) call.  I know this is a 1ms delay but it was enough to prove that if I do that it fixes my problem.  However, there is no reason to take up an entire 20 ms to complete this operation (from what I've read it's recommended to toggle 10 times to reliably unlock the bus) when 20us is enough.  How would I implement a 1us delay function or is there one already available to use?

Good day,I have stumbled upon an issue with my device's bootloader that seems to be inconsistent with the ST documentation. I have an STM32G031K8T6. USART1 RX and TX are connected to an RS-232 transceiver, which is then connected to my host PC using a USB-to-RS232 cable:[STM32G03x USART1] <----> [RS232 tranceiver (MAX3232 equivalent)] <---> [FTDI RS-232 USB cable] <---> [Host PC]I would like to use the bootloader to upload firmware to the device, over this UART link. Normally, this works just fine. However, I have observed that the bootloader will not respond if it receives invalid data before receiving the valid 0xF7. To reproduce "good" behavior:Create an empty boardApply BOOT0, and power on (bootloader mode).Connect to the COM port using TeraTerm, or some other serial terminal (57600, 8 bit, even parity, 1 stop bit)Don't send any dataDisconnect from TeraTermAttempt to connect to board using Stm32CubeProgrammer (UART, 57600, 8 bit, even parity, 1 stop bit)Conne

Hi team,I am using example code GPIO_IOToggle. which is working fine.1. Tried to use below changes in .ld file as below and that also works fine when we dump code form STMCubeIDE.MEMORY { RAM (xrw) : ORIGIN = 0x20000000, LENGTH = 32K FLASH (rx) : ORIGIN = 0x8000000, LENGTH = 114K }2. Then tried same with STMCubeProgrammer tool by dumping this binary at 0x8005000 address and run. Here it just keep the LED ON continuously. No toggle done.MEMORY { RAM (xrw) : ORIGIN = 0x20000000, LENGTH = 32K FLASH (rx) : ORIGIN = 0x8005000, LENGTH = 114K } Here is the full .ld file for more reference/* ****************************************************************************** ** ** @file : LinkerScript.ld ** ** @author : Auto-generated by STM32CubeIDE ** ** @brief : Linker script for STM32U083RCTx Device from STM32U0 series ** 256KBytes FLASH ** 32KBytes RAM ** ** Set heap size, stack size and stack location according ** to application requirements. ** ** Set memory bank area and size i

Hello,For some reason I'm unable to get valid readout of internal MCU temperature. Maybe someone have an ide why this might be happening? System is running on STM32G0B0 MCU. I init ADC over HAL generated code and enable only internal inputs (`ADC_CHANNEL_TEMPSENSOR`, `ADC_CHANNEL_VREFINT` and `ADC_CHANNEL_VBAT`), after init I run ADC calibration which reports that it did it's job. but when I start to read temperature periodically - every minute, I see following results (these are raw values domming from DMA so I assume it is `temp`, `Vref` and `Vbat`):temp Vref Vbat 03B7 07E3 045B 050F 07E4 045D 0513 07E4 0460 0511 07E5 045B 0512 07E5 045B 0512 07E5 045A 0513 07E3 0457 0504 07E9 0481 0509 07E9 0488 0526 07EB 0497 0532 07ED 049C 051F 07EB 0499 0502 07E7 0482 0508 07E8 047B 050A 07E5 0475 0509 07E5 0470 050B 07E5 046F 050F 07E5 0470 050E 07E5 046D 050B 07E3 0467 0510 07E5 0466 0513 07E5 0465 0513 07E5 0466 050F 07E4 0467 0512 07E5 0464 050F 07E5 0463 0511 07E5 0464If I plot these values

Dear Team,I am completely new to Embedded systems.I am an analog design engineer.Decided to start my embedded learning with STM32.I bought  a nucleo-64 board.If you don't mind could you please guide me how do I start. I saw many training materials in ST website itself.Don't know which one will be best for a complete beginner.Can you please suggest the learning path and materials for each of these learning path.My final goal is to learn edge AI.RegardsHari

Hello Team,We are facing an issue with the STM32F407ZGT6 microcontroller, specifically with the PC10 pin.Our primary objective is to use PC10 as a clock output pin for SPI communication. However, we observed that the expected clock pulses are not being generated on this pin. To further debug the issue, we wrote a simple test code to toggle PC10 as a GPIO output. Unfortunately, even this basic GPIO operation did not function as expected—there was no voltage change observed on the pin, verified using a multimeter.This unexpected behavior appears to be isolated to the PC10 pin, as the same code works correctly when tested on other GPIOs.We would appreciate it if you could provide your insights on this issue. Please let us know if there are any known errata related to this behavior or any specific considerations for using PC10 for SPI or general GPIO use.Feel free to reach out if you require any additional information, such as schematics, test code, or setup details.Looking forward to your

Hi,Can short circuit between near pins (not GND and VCCO) cause damage to STM32F103RET7 ?Thank you. 

I am evaluating using SPI and ST's internal System Bootloader for a 2 processor application.To that end, I am attempting to attempt to read in the bootloader via SPI on an STLink V3.I am successfully able to do so for a NUCLEO-L496ZG, but fails for a NUCLEO-U575ZI-Q. This is what the traces look like on the Oscilloscope. Yellow is the MISO line.What it isn't:It is not an issue with going into boot mode. I pull Boot0 pin via jumper and press the reset button to put it in boot mode. I am able to verify that it is in boot mode, as I check whether STLink V3 can connect via I2C. It can. I also reset in between connection attempts, as I am aware the bootloader turns off other peripherals when a connection is established.It is not an issue with the hardware/pins. I used the same Nucleoboard with the same pins in the U575 SPI Slave example. I configured another U575 to be the master. I even modified the Slave example to configure those pins (PA5, PA6, PA7) to be in pulldown mode, like AN2

I am trying to get my STM32F446RE (using STM32CubeIde) into USB DFU mode via firmware rather than using the RST and BOOT0 inputs which are going to switches on the board. I know this is doable but for some reason it is not working for mewhenever I go into JumpToDFUBootloader(void); the windows host computer does nothing looking at windows device manager I should see "STM32 BOOTLOADER" under USB Devices but I do not see this which means the correct processto go into DFU mode is not happening, I notice that if I jump the BOOT0 pin high and execute JumpToDFUBootloader() it does go into USB DFU mode and I can see the "STM32 BOOTLOADER" but unfortunately I DO NOT want to relyon my BOOT0 or RST input pins I just want to go into DFU mode upload new firmware and repower the system to re-initialize into normal operating mode afte a firmware update.Any suggestions or help with this would be greatly apprciatedMy code is below:  /*///////These below are before and when entering my main()

Hi,I'm using an STM32C051K6T6 to read an audio file from FLASH (a book on tape, basically) and output the data over I2S to a codec/amplifier. I would like to understand the drawbacks, if any, of using the internally generated PLLI2SCLK instead of an external clock source (through the I2C_CKIN input) for the I2S clocks. I would prefer to use the PLLI2SCLK so that the pin for I2C_CKIN can be used as a GPIO instead, but I'm uncertain of the impact of doing so. For example, will the audio quality be significantly compromised by using PLLI2CLK instead of an external clock?Thanks,James 

Hi ST-Members,I need to interface a 10.3-inch LVDS display with a resolution of 1920x720 to an STM32F769-disc0. I also have an H743 Nucleo board. Could you please advise on the method I should use to make the display work? Additionally, I plan to initiate TouchGFX for an ECG application.I came across a schematic for an interface board(attached below) from STM32F769-EVL to LVDS in the community. How can I follow this schematic to make it compatible with the F7-DISC0 or H7 Nucleo boards? Alternatively, is there an interface converter board available in the market that converts onboard MIPI DSI to LVDS? If not, please guide me on the proper steps to modify the PCB schematic for the STM32F7-DISC0 or H7.Solved: LTDC (RGB) to LVDS interface - STMicroelectronics Communityregards,embed_engr

I am trying to drive a lc resonator from a h bridge. Frequency of the resonator changes when inductor is loaded. TIM15 creates the complimentary PWM for the H bridge. I need TIM2 to read the new frequency of the resonator so i can adjust the PWM frequency of TIM15. TIM2 will be reading a square wave.I tried this guide(and every other one I could find). I tried DMA. I tried interrupts. I even put a breakpoint inside the HAL_TIM_IC_CaptureCallback. It didn't even get triggered.https://community.st.com/t5/stm32-mcus/how-to-use-the-input-capture-feature/ta-p/704161At this point i am not sure if my code is wrong or if there is an actual problem with the board. Would it be possible for someone to send me a code for TIM2 interrupt that is confirmed working or test my code on a stm32 that is confirmed good?I am questioning my sanity. The board programs and debugs just fine. cubeide or cubeprogrammer gives no error codes.here is all the edits I have done to my main.c file/* USER

SPI communication using DMA on the STM32H743.We have created a program for SPI communication using DMA, The first send/receive with HAL_SPI_TransmitReceive_DMA is successful.However, when the exact same process is executed afterwards, all received values are 0.The second send/receive with HAL_SPI_TransmitReceive_DMA is not successful.Does anyone know why this is happening?