Solved

I was trying to get the most out of my H563 set up and run as fast as possible. I am using the Nucleo-H563 board. I reconfigured in CubeMX to use System clock mux to use HSE source mux, multipliers and dividers set correctly for 250MHZ operation. There are no errors shown in the setup and I am showing 250 Mhz as the SYSCLK. My AHB is /1, HCLK shows 250MHZ which is feeding the peripheral busses. While the clock configuration APB1 shows 250Mhz it does not seem to be correct as when I set the timers and prescalers for such the timing is not correct... the bus seems to be running at 125mhz. For my TMR1 to get 1us clock I have to set the divider to 124 which implies the internal clock is running at 125Mhz not 250 like the clock diagram shows.    I have attached the Clock Configuration from CubeMX that shows no clock issues.

Hello ST Support Team, I’m currently designing a custom board using STM32H750XBH6.In this design, I would like to interface a 32-bit SDRAM for improved memory bandwidth and performance. However, I noticed that in the official STM32H750 development board (Nucleo/Discovery), the same MCU (STM32H750XBH6) is connected to a 16-bit SDRAM interface only. I would like to confirm the following points: Is it possible to interface a 32-bit wide SDRAM with the STM32H750XBH6? If yes, are there any pin multiplexing conflicts or hardware limitations on the FMC (Flexible Memory Controller) that I should be aware of? Any reference schematics, Cube MX configuration tips, or verified examples for 32-bit SDRAM with STM32H7 would be very helpful. Your technical guidance will be very valuable to me in finalizing this design. Thank you.

I am having some issues with getting UART uploading working. I can read the chip and get it's ID, but it keeps saying it cannot get acknowledgments.  Everything is directly connected. Serial TX/RX to their corresponding pins and RTS to Boot and DTR to Reset.At first, I thought it was because the FT232RNL chip has flipped polarity, but we can change this through the FTDI programmer. After changing it, I am still having the issue above. Looking online, I see some people put a cap in between the DTR and Reset. Is this actually required? I know they did not on Arduino's. but I always though it was because their bootloader required it since there was no boot pin like on the ST's.I cycled through all the possibilities for the DTR and RTS configuration in the ST Programmer software, but none of them seem to fix the issue.  Any guidance on this? 

Hello!I am using a custom board with STM32H563VIT6. I want to create an MQTT project which will send data to a local laptop via an Ethernet cable. I am using STM32H573I-DK\Applications\NetXDuo\Nx_MQTT_Client as the example project to do so, but I am facing a problem.The problem is that when the nx_app_thread_entry function is called it will get stuck when this line is calledif(tx_semaphore_get(&DHCPSemaphore, TX_WAIT_FOREVER) != TX_SUCCESS)Then this leads to "__tx_ts_wait" in the nx_thread_schedule.S forever.This is my call stack up to __tx_ts_wait:__tx_ts_wait@0x08000336 (...\STM32H563VIT6_Ethernet\Middlewares\ST\threadx\ports\cortex_m33\gnu\src\tx_thread_schedule.S:279) <signal handler called>@0xffffffbc (Unknown Source:0) _tx_ipsr_get@0x08009bdc (...\STM32H563VIT6_Ethernet\Middlewares\ST\threadx\ports\cortex_m33\gnu\inc\tx_port.h:511) _tx_thread_system_return_inline@0x08009bdc (...\STM32H563VIT6_Ethernet\Middlewares\ST\threadx\ports\cortex_m33\gnu\inc\tx_port.h:615) _

I created a simple project back in May (simple - some buttons, temperature display) and mounted in a box (landscape/0 rotation).I went to reuse the display with a new TouchGFX project (same box) and it is flipped 180! When I load the old code, correct side up, new project in TouchGFX and it is upside down.  I checked the forum and this isn't easy to do and requires extra code - how is this even possible?  For reference, it is a fairly new STM32F469I-DISCO (blue) purchased in May of 2025.  Old project - SDCARD/Headphone jack faces down.

Hello Everybody,Here are the software and boards in this case:1. MC workbench 6.4.12. STM32 FW V1.28.2I designed a project for my board, but the generated code has an error as illustrated in the picture, I didn't make any modification on the code and complie it directly after the generateion,How can I fix the problem??Thank you! 

Hello, I am working on a home made board featuring an STM32G474QE in 128 pins and multiple relay drivers (MAX4896 : MAX4896 - Space-Saving, 8-Channel Relay/Load Driver)If I understand it well, the principle is fairly easy, sending a flow of data consisting of 8 times the number of MAX. Once that is done, driving the Chip Select to LOW will drive the outputs of the relay drivers depending on what the value of each bit is.In my case, I have 9 relay driver daisy-chained so that would be 72 bits to send in one data flow. I have two questions regarding this. First off all, what mode should I put the SPI in, I coulnd't find this information in the MAX datasheet.My second question is more of a code issue, would anyone have any example of how to code something of this sort.Thank you very much for any help

I am referring to the note AN5373 and MB1550/1549 schematics to design a STM32U575xx based board. The note AN5373 shows no connection for the VLXSMPS and VDDSMPS  pins when SMPS is not used. Do i just leave them floating? How should I connect them if I do not want to use the SMPS? Also there is no 'VCAP' pin on my symbol.Please Assist.

Hello everyone,I’m trying to locate the DSMPS 3kW – LLC STM32F334x firmware package, which is described as containing the following folders:Documentation – includes compressed HTML and LaTeX help files generated by DoxygenDrivers – includes HAL, LL, CMSIS, and BSP driversFullBridge_LLC_Project – includes a README file, source files, linker configuration file (.icf), microcontroller startup file (.s), and IAR Embedded Workbench project files (.eww, .ewp, .ewd)Could anyone please let me know where I can download or access this full firmware package?A link to the official STMicroelectronics source, GitHub repository, or firmware library reference would be greatly appreciated.Thank you for your support! 

I have a NUCLEO-C071RB with an STM32C071RB.  In section 31.1 of RM0490 Rev 5, it describes the first 32 bits of the unique ID like this:Bits 31:0 UID[31:0]: X and Y coordinates on the wafer expressed in BCD formatBCD should mean binary-coded decimal, which means each 4-bit nibble is between 0 and 9, but if I run "STM32_Programmer_CLI --connect port=swd -r8 0x1FFF7550 12", I get:0x1FFF7550 : AF 00 40 00 14 50 36 42 48 37 30 20The first byte, 0xAF, is not BCD.In my experience working with these chips, it looks like bytes 0 and 2 are just arbitrary binary bytes which tend to be less than 0x80 but not always.  And bytes 1 and 3 are always 0.So what do those first four bytes really represent?  And is the documentation for the other 8 bytes in RM0490 accurate? It says there is a 1-byte wafer number, followed by 7 bytes of ASCII for the lot number.(Part of the reason I'd like to know this is so I can make a good scheme for converting the unique ID to an ASCII  string

Hello,I have been using the this ToF sensor along an ESP32-WROOM MCU for a while without major issues. My impementation of the i2c interface seems to be working well since in most simple ranging cases everything works well.However, recently, i have been playing around with detection thresholds. I discovered that when I enable detection thresholds while in autonomous mode, I am unable to start ranging. In fact, the sensor gets properly configured (resolution, ranging mode, integration time, frequency and detection thresholds) but when it starts ranging (function vl53l8_start_ranging), error VL53L8_STATUS_ERROR occurs. The error gets raised in this part of the function  /* Read ui range data content and compare if data size is the correct one */ status |= l8_dci_read_data(p_dev, (uint8_t*)p_dev->temp_buffer, 0x5440, 12); (void)memcpy(&tmp, &(p_dev->temp_buffer[0x8]), sizeof(tmp)); if(tmp != p_dev->data_read_size) { status |= L8_STATUS_ERROR; }&nb

Could you provide me a repo link to the SDIO driver so that I can read through it and implement my custom code. I need something generic to FreeRTOS SDK.

Dear SupportI am using STM32H563, try to get internal Vref, and temperature working, and ADC conversion is OK, but when using macro  __HAL_ADC_CALC_VREFANALOG_VOLTAGE, and __HAL_ADC_CALC_TEMPERATURE to convert to Vref and temperature, it ends up a in HardFault_Handler(), I tried to read the address directly for the value like below:Cal2 = (float)((int32_t)*TEMPSENSOR_CAL2_ADDR);Cal1 = (float)((int32_t)*TEMPSENSOR_CAL1_ADDR); And ends up same, no matter in Nucleo-H563 or my target board, please help!Regards!Ping

Dear STMicroelectronics Support Team, We have observed a discrepancy between two STUSB documents regarding the default configuration of the VBUS discharge feature:STUSB Datasheet / Online Document (Section 3.4.2 and 5.2) [Link: @STUSB4500.html]It states that the VBUS discharge feature is enabled by default in the NVM and can be disabled through NVM programming.Parameter: VBUS_DISCH_DISABLEDefault Value: 0b (VBUS discharge enabled)Description: Setting to 1b disables the discharge function.Programming Guide (Section 3.23) [Link: @STUSB_programming_guide.pdf]It specifies that the VBUS_DISCHARGE_EN bit is disabled by default:Address: STUSB_BLOCKBaseAddress + 0x26Type: R/WReset: 0x00 (initialized by NVM)Bit [7]: VBUS_DISCHARGE_EN0: Disable the forced assertion of VBUS discharge path1: Enable the forced assertion of VBUS discharge pathDue to this apparent contradiction - one document indicating that the VBUS discharge feature is enabled by default

Good Evening Sir/Mam, Sir/Mam, I have a query about the DCMI of STM32U595RJT6Q. I have read the Datasheet of STM32U595xxx and it was written in it that- DCMI of this MCU is for use with Black & White Camera Modules and it is assumed that all preprocessing is pre- performed in the Camera Module. Sir/Mam, it would be very helpful if you could please confirm and verify these both things (Interface with Black & White Camera Module and Preprocessing is needed to be pre-  performed in the Camera Module), and if you could please provide any-  websites at which- X24 & X5 Camera Modules would be available at cheapest rates (if any).  Thanking You, ANKUR. 

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

Hello!I've been uploading code to my STM32 Bluepill using my computer but it died recently and I had to use a different computer. After adding the library for the STM32F1, i tried to compile and upload again but i received these errors. Im a bit lost on where to start and would appreciate if anyone could help point me in the right direction for a fix!! The error code from the arduino terminal is as belowexec: "C:\\Users\\hisha\\AppData\\Local\\Arduino15\\packages\\STMicroelectronics\\tools\\xpack-arm-none-eabi-gcc\\14.2.1-1.1/bin/arm-none-eabi-gcc": file does not existCompilation error: exec: "C:\\Users\\hisha\\AppData\\Local\\Arduino15\\packages\\STMicroelectronics\\tools\\xpack-arm-none-eabi-gcc\\14.2.1-1.1/bin/arm-none-eabi-gcc": file does not exist

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 ?

can some one please tell me why is the schematics the pd8 is connected to gnd?here is a picture of the schematics 

Table 20, "CN9 ZIO Connector pinout" on page 40 of "UM2407 User manual Rev 2 - STM32H Nucleo-144 boards (MB1364)" lists the wrong pin name for pin CN9-15. It is listing PE0 while it should be listing PE9.

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)

Hi, Why is DAC_OVP_Threshold = 23830 ?  @GMA  Thx :) 

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.

Hi,  I am trying to flash our software to our STM32MP13xx MPU. I am able to connect to the device using the STM32 Programmer CLI. The first file in the .tsv file list is downloaded succesfully to the device, but then I run into the following errors: "-------------------------------------------------------------------STM32CubeProgrammer v2.19.0------------------------------------------------------------------- USB speed : Full Speed (12MBit/s)Manuf. ID : STMicroelectronicsProduct ID : DFU in FS Mode @Device ID /0x501, @Revision ID /0x1003SN : 0015001E3033510430393732DFU protocol: 1.1Board : --Device ID : 0x0501Device name : STM32MP13xxDevice type : MPURevision ID : --Device CPU : Cortex-A7Start Embedded Flashing serviceOpening and parsing file: tf-a-intuedrive-stm32mp135x-512m-usb.stm32Memory Programming ...File : tf-a-intuedrive-stm32mp135x-512m-usb.stm32Size : 74.74 KBPartition ID : 0x01Download in Progress:██████████████████████████████████████████████████ 100%Fil