STM32 MCUs Products

I am trying to wire a graphics application on an STM32H745i-DISCO board, and place the framebuffer in external SDRAM.So I configured the FMC as follows:

Hi ST,Using the STM32L476 for a custom battery-operated application, on trying to implement the USB 2.0 through a type C receptable, I need clarity on the connections of the USB.AFAIK the VBUS sensing on PA9 should be connected through a resistor divider to reduce the voltage to a safe level when the MCU is not powered. My doubts are1. Can I power the MCU from the VBUS using the VDDUSB (only USB peripheral working is needed) or should I connect both the VDD and VDDUSB so that the MCU should be powered ON and the USB peripheral won't work with only the VDDUSB connected to the VBUS.2. How much does the USB peripheral and the MCU both consume during startup considering VBUS can only supply 500mA.3. Can VBUS be 3.3V or will it be only 5V4. Recommended Specs for voltage regulator if VBUS is 5V

I’m working on a project using the STM32F446RE microcontroller and I’m trying to set up the debugger's printf viewer in Keil MDK. I would like to use the printf function to output debug information to the debugger’s terminal.I’m having trouble seeing the printf output in the debug view. I suspect that I might be missing some configuration steps or might not be using the correct setup.Could someone provide a step-by-step guide on how to properly configure the debugger in Keil MDK to view printf outputs for the STM32F446RE? Any help or tips on the necessary configurations would be greatly appreciated.Thanks in advance!

Are there any guides or tips on making an STM32 MCU last in a high temperature (~150°C) environment? Specific voltage or clock speed tweaks?The MCU would sleep most of the time, but now and then take and store some measurements.Would certain families be better (for example because of different semiconductor nodes)? We're looking at the G4 and L4 MCUs (G4 for the embedded OPAMPs) but the application would work with pretty much any part number.Similarly, would certain package types be more temperature resilient?

Hello,I'm trying to record the execution trace of my firmware running on a STM32H753. For this I'm using the ETM functionality of Cortex M7. I don't want to use external tools but rather to use the ETF (Embedded Trace FIFO) that can be accessed directly from the processor.I have been struggling to understand how the different debug components (ETM, ETF, DWT, etc...) are working together. i've read STM32H7 reference manual, ARM ETM technical ref manual and architecture spec but all these debug components are particularly confusing and unclear.My understanding is that the DWT peripheral compares the execution address and triggers the ETM if it matches. Then the ETM feeds the ETF (?).Here is the code:// enable DWT in Debug Exception and Monitor Control Register   *DEMCR |= 1 "the CMPMATCH[N] signals   // from the DWT unit are available as control inputs to the ETM unit"   *DWT_COMP0 = 0x00000000;

I am in the early stages of writing an application that writes audio data to an SD card and, on request from the RPi, writes the same data from the SD card to the Pi. The project requires that it's done this way, as I would like a copy of the data on the RPi and a 'hard copy' on the SD card without having to manually remove the SD card and copy over files via a card reader. I am working with an STM32F446RE and the SD card I'm using is 64 GB formatted as exFAT. I have code that properly creates a file and writes the data to it on the SD card. Now I just need to transmit this file over USB to the Pi. Where I'm a bit lost is that I don't fully understand exactly how I will allow the Pi to read files off of the SD card while the STM32 is writing with FATFS. Other posts I have read from this forum suggest that it's not possible without incurring file overwrites or corruption on the card. Will I have to unmount the SD card from FATFS each time the PC tries to read the FAT on t

Hello,I'm following this example: How to use the STM32 ADC's internal reference volt... - STMicroelectronics Community I'm using ADC4 rather than ADC1. I checked off Vrefint Channel and Vbat/4 Channel, and I let the IOC take care of the sequencing (it happens to convert Vrefint first). The device is powered by battery only. Hardware-wise, the VBAT pin is connected to Vdd and Vdda. For testing this I'm substituting a power supply to control the input voltage. Just focusing on the raw values obtained with HAL_ADC_PollForConversion() / HAL_ADC_GetValue() (like the example uses), when the supply voltage goes up the Vbat raw value goes down (and vice versa), while Vrefint stays roughly constant (as it should).The converted voltage measurement is not important, but knowing when the voltage is low is. Is there some software

Greetings,I tried to setup a L0 using SPI to connect with LSM6DSR, all codes are generated using CubeMX (also the driver code for LSM6DSR with X-CUBE-MEMS1)The weird thing is, when ever it tries to utilize SPI functions (Transmit, Receive, and Transmit/Receive), it will always return HAL_SPI_ERROR_MODF.  The SPI1 only have LSM6DSR connected, no other slaves, the only master is the L0.The SPI is setup as below, generated by CubeMX but I think there shouldn't be a problem: __weak HAL_StatusTypeDef MX_SPI1_Init(SPI_HandleTypeDef* hspi) { HAL_StatusTypeDef ret = HAL_OK; hspi->Instance = SPI1; hspi->Init.Mode = SPI_MODE_MASTER; hspi->Init.Direction = SPI_DIRECTION_2LINES; hspi->Init.DataSize = SPI_DATASIZE_8BIT; hspi->Init.CLKPolarity = SPI_POLARITY_HIGH; hspi->Init.CLKPhase = SPI_PHASE_1EDGE; hspi->Init.NSS = SPI_NSS_SOFT; hspi->Init.BaudRatePrescaler = SPI_BAUD

Hi,I'm getting this below compile time errors...  undefined reference to `MX_RTC_Init'  However, I have included the rtc.h header file, which contains the declaration of the MX_RTC_Init(void) function.  #include "main.h" #include "cmsis_os.h" #include "fdcan.h" #include "i2c.h" #include "lwip.h" #include "rtc.h" #include "spi.h" #include "usart.h" #include "usb_device.h" #include "app_touchgfx.h"  Why does CubeIDE still giving me this error?Thanks 

Hi All,I am implementing a custom bootloader on a STM32U575QII6, but it is not jumping to my program.I have my bootloader in bank 1, and I have written my program to Flash at address 0x08014000 - within the same bank.I have tried multiple things and followed different posts etc but nothing is working for me. There is nothing specific around the U5 series. #define APPLICATION_ADDRESS 0x08014000void (*pFunction)(void) = (void(*)(void)) APPLICATION_ADDRESS + 4; HAL_RCC_DeInit(); HAL_DeInit(); __disable_irq(); SysTick->CTRL = 0; SysTick->LOAD = 0; SysTick->VAL = 0;

I sample a 1000Hz periodic signal twice  each period. At 50us after the start of the period for samples A and after 850us for samples B with a single ADC and a single channel. I trigger the ADC with a delayed PWM (Combined PWM1 on a G431) and the results go in a circular 32 values long DMA buffer and I get 16 A and 16 B samples alternated in it. Circular since I do not process the values constantly. But the fact that A and B samples are alternating in one buffer doesn’t please me. Is there a way to get two DMA buffers out with A samples triggered by the rising edge of the timer and B on the falling edge (10us conversion times)? I have explored DMAMUX a bit. Was new to me. But that seems to only have one input from the ADC that cannot be multiplexed further based on ADC conversion complete combined with the value of the PWM trigger signal. Is there a logical way to do this? 

I ordered few free samples on 1st August. But still my order is showing processing I have no idea is that cancelled or how long it will take to ship. can anyone from st help me? It will be a great help 

Hi everyone,I'm encountering a problem with my STM32 project where I need to use both LTDC for display and audio playback (via FATFS). The issue seems to stem from a conflict in clock configurations.My setup:     MCU = STM32F469i-DiscoThe problemWhen I configure the clock for LTDC like this:LTDC clock configuration (stm32469i_discovery_lcd.c line 342):   PeriphClkInitStruct.PeriphClockSelection = RCC_PERIPHCLK_LTDC; PeriphClkInitStruct.PLLSAI.PLLSAIN = 384; PeriphClkInitStruct.PLLSAI.PLLSAIR = 7; PeriphClkInitStruct.PLLSAIDivR = RCC_PLLSAIDIVR_2; HAL_RCCEx_PeriphCLKConfig(&PeriphClkInitStruct);   The display works perfectly, but the audio playback through FATFS fails (specifically in Audioplayer.c at line 42).However, when I comment out the LTDC c

hi I'm going to store JPEG data in an array and then decode itI'm using H7A3ZI-Q for the board uint16_t outdatabuffer [65535] ={0};JPEG_Decode_DMA(&JPEG_Handle,(uint32_t)frameBuffer,bufferPointer , outdatabuffer);I used this code, but only 0 was saved in outdatabuffer Please let me know if there is any additional part or example code that needs to be set to decode the JPEG image data.Thank you.

Greetings,We are currently using NUCLEO64 MB1814(STM32H503RB) in our application in which when configuring GPIOs in PORT A and integrating it with data pulses, the following error occurs stating the target device not responding. The data pulses are of 5V and the GPIO PORT A pins we have selected are 5V tolerant, but the EVM MCU operates in 3.3V. We have tried the same operation in PORT C, and it worked. Can you explain what the difference between PORT A and PORT B regarding this regard is.  We are using STM32 Cube IDE STMicroelectronics ST-LINK GDB server. Version 7.8.0Copyright (c) 2024, STMicroelectronics. All rights reserved. Starting server with the following options:Persistent Mode : DisabledLogging Level : 1Listen Port Number : 61234Status Refresh Delay : 15sVerbose Mode : DisabledSWD Debug : EnabledInitWhile : Enabled Waiting for debugger connection...

Dear all, in my application I want to send constantly data to an external I2C device in DMA mode. For this I use the function HAL_I2C_Mem_Write_DMA. I have my ADCs and SPI correctly working with DMA but with the I2C I get the error I2C_DMAError  in the XferErrorCallback. I have set up the DMA in Circular mode and run the function before the While(1) loop. I can see the I2C clock being sent. I use the function as follows:  HAL_I2C_Mem_Write_DMA(&hi2c1, I2C_DEVICE_ADD, DEST_ADDRESS,I2C_MEMADD_SIZE_8BIT,(uint8_t*)i2c_data,10); where uint16_t i2c_data[5] = {0x0044,0xF021,0x0082,0x0100,0x0000}; I2C Init: static void MX_I2C1_Init(void) { /* USER CODE BEGIN I2C1_Init 0 */ /* USER CODE END I2C1_I

Hi I want to improve the FPS of TFT when using SPI interface.I use SPI+DMA+QuadSPI PSRAM+QuadSPI Flash for now.I notice STM32L4P5RG has DMA2D.So can it use for SPI interface?Will it have any improvement when I refresh TFT?If it has, how to use it?

Hello. I've a problem regarding LSE On stm32l562xx mcu. Sometimes it boots, sometimes it doesn't "90 % of time it generates timeout Error" . and it takes too much time to boot up to 4 seconds. I've tried all your sdk initializations, also tried setting lse drive to all 4 modes but nothing changes. Same behaviour and same time. Below is my initialization code and attached how we connect LSE on our board. Regards   RCC_OscInitTypeDef RCC_OscInitStruct = {0};  RCC_ClkInitTypeDef RCC_ClkInitStruct = {0};  /** Configure the main internal regulator output voltage  */  if (HAL_PWREx_ControlVoltageScaling(PWR_REGULATO

I find that flashing a program using openocd, STLink (using a Nucleo F446, or L474), to our custom board frequently fails when there is CAN bus activity. What is causing this?Our board has BOOT0 tied to ground. The SWD is gnd, data, clock, and connects to pins STLlink on the Nucleo board. For a while the flashing would "usually" work, occasionally there would be a failure to erase a blocks, or range of blocks, or a failure to write. With more units on the CAN bus, it always fails. For a while I thought the processor flash had gone bad until I stumbled on it working "better" when some of the other units were taken off the bus. That led to determining that flashing works 100% if the unit being flashed is the only unit on the bus (i.e. it is powered from the CAN cable as that carries power as well as the CAN signals). The docs talk about the built-in routine for flashing where the standard peripheral pins are checked for data, etc. That suggests that somehow t

Hello, everyone this is my first post here.I'm starting to learn Embedded Programming and I choose STM32F103C8T6 using Blue Pill development board. I'm trying to understand SPI communication, my goal is to read multiple input using 74HC165 IC. I'm able to read that successfully when I set SPI1 to use Full-Duplex Master. But since I just want to receive, I thought why not use the Receive Only Master to save 1 pin(SPI_MOSI) since it won't be used anyway, [but the problem is somehow when I use Receive Only Master the clock pulse is not generated for SPI_SCK pin] The clock turns out to be generated but it stuck on this line HAL_SPI_TransmitReceive when I debug it and I can't get over it . Can anyone help me understand what is going on and what I miss? I also attached the spi and main file.Please let me know in case I need to provide more information and thank you in

I'm using the STM32G030C8 for one of my projects and i realize that in some cases the RTC stops when the power supply is up. While in VBAT supply the resonator works well and provide the correct date and time, but when i use the power supply the resonator immediately stops to work. The oscilation signal disappears in osciloscope. It looks like the microcontroller does not switch the power for LSE properly. The crystal i'm using is the ECS 32.768 KHz 6 pF +/-10 ppm (https://br.mouser.com/ProductDetail/ECS/ECS-.327-6-34B-C-TR?qs=eP2BKZSCXI77Gsmdv1lxlw%3D%3D) with 10pF for load capacitors. The LSE Drive Level Capability is set to high. I even tested it with medium low and medium high and it doesn't make difference. In 8 boards assembled, the proble

Per the presentation linked below, the independent watchdog timeout range for the SMT32H7 is from 125 microseconds to 32 seconds. Is 32 seconds a hard limit? We would like to increase this value.STM32H7-WDG_TIMERS-Independent Watchdog (IWDG)Thanks in advance for your help.Regards, Mark

Hi,We are facing some challenge with external watchdog timer and STM32H7855xi. when there is no program in flash input to external watch dog timer (WDI) is output and no pulse . during this time external watch dog timer continuously generate reset pulse to microprocessor pin (nRST which is default of pull up) .when we trying to program through JLINK pro external watch dog timer not allowing to program , it continuously resetting the processor , we need to manually separate external watch dog timer reset pin from nRST pin by removing R69 as per given schematic.Do you have any suggestion to avoid manual intervention  

Hi,I am trying to make a program in which in the micro stm32u5 is stored in ram memory some data after activating the Sleep Mode. For this I have defined in the flash file the SRAM2 memory which is the one that is supposed to be in charge of this:   MEMORY { RAM (xrw) : ORIGIN = 0x20000000, LENGTH = 768K SRAM4 (xrw) : ORIGIN = 0x28000000, LENGTH = 16K SRAM2 (xrw) : ORIGIN = 0x20030000, LENGTH = 64K FLASH (rx) : ORIGIN = 0x08000000, LENGTH = 2048K } .ram2 (NOLOAD): { _sram2 = .; *(.ram2*) . = ALIGN(4); _eram2 = .; } >SRAM2 Once SRAM2 is defined, what I want to do is to save a structure that I have defined as follows: NODEconf_TypeDef NODE_conf __attribute__((section(".ram2"))); When I run the code I can see in Memory that this st

Currently I'm able to run ADC1 and ADC2 in interleaved mode using seperate (on purpose) DMA channels for ADC1 and ADC2. To start I'm using:  SET_BIT(hadc2.Instance->CFGR, ADC_CFGR_DMAEN); //Enable DMA transfer for ADC slave (ADC12_CCR.MDMA = 0b00 -> MDMA mode disabled) HAL_DMA_Start(hadc2.DMA_Handle,(uint32_t)&hadc2.Instance->DR, (uint32_t)adc_dma_voltage_buffer,NUMBER_OF_ADC_SAMPLES); //Start ADC slave DMA SET_BIT(hadc1.Instance->CFGR, ADC_CFGR_DMAEN); //Enable DMA transfer for ADC master (ADC12_CCR.MDMA = 0b00 -> MDMA mode disabled) HAL_ADCEx_MultiModeStart_DMA(&hadc1,(uint32_t *)adc_dma_current_buffer,NUMBER_OF_ADC_SAMPLES); //Start ADC interleaved mode My handler looks like this: void HAL_ADC_ConvCpltCallback(ADC_HandleTypeDef *hadc) { if (hadc->Instance == ADC1) { // Process the data in adc_buffer