STM32 MCUs Products

Hi,The SDADC has three possible input modes,• Differential mode• Single-ended offset mode• Single-ended zero-reference modeTotal 9 pair SDADC channels are available in controller(ex. SDADC_AINP and SDADC_AINM)in our product we have utilized 8 pair SDADC channels using Single-ended offset mode or Single-ended zero-reference mode for metering application and positive input is connected to SDADC_AINP and external GND is connected to SDADC_AINM also attached reference schematic. kindly review the schematic and suggest

Hello,I have an issue with the CAN bus on STM32F042G6 µC. For the moment I just want to receive Frames from an other controller (STM32G0B1) and it doesn't work at all.I am using PA11 as Rx Pin and PA12 as Tx Pin Pins.Here is the configuration part with a 12MHz external clock :static void MX_CAN_Init(void) { /* USER CODE BEGIN CAN_Init 0 */ /* USER CODE END CAN_Init 0 */ /* USER CODE BEGIN CAN_Init 1 */ /* USER CODE END CAN_Init 1 */ hcan.Instance = CAN; hcan.Init.Prescaler = 16; hcan.Init.Mode = CAN_MODE_NORMAL; hcan.Init.SyncJumpWidth = CAN_SJW_1TQ; hcan.Init.TimeSeg1 = CAN_BS1_1TQ; hcan.Init.TimeSeg2 = CAN_BS2_1TQ; hcan.Init.TimeTriggeredMode = DISABLE; hcan.Init.AutoBusOff = DISABLE; hcan.Init.AutoWakeUp = DISABLE; hcan.Init.AutoRetransmission = DISABLE; hcan.Init.ReceiveFifoLocked = DISABLE; hcan.Init.TransmitFifoPriority = DISABLE; if (HAL_CAN_Init(&hcan) != HAL_OK) { Error_Handler(); } /* USER CODE BEGIN CAN_Init 2 */ /* USER CODE END CAN_Init 2

Environment:- STM32Cube VSCode Extension (with Build Analyzer)- CMake-based project generated by STM32CubeMX- Windows 11 / GCC toolchainIssue:- The Build Analyzer fails to detect the .map file and reports "NO_MAP_FILE".- Investigation shows that the analyzer seems to only look for a .map file named after the *project folder*(e.g. build/Debug/<project_folder>.map).- However, in CMake projects the actual build target name is derived from ${CMAKE_PROJECT_NAME}, which can differfrom the folder name.(In my case: project name = VaporChamberController_V2, folder name = VaporChamberController_V2_vscode).Steps to reproduce:1. Create a project where the folder name and project name are different.2. Build the project with CMake.3. A .map file is generated (using the target name), but the Build Analyzer shows "NO_MAP_FILE".Workaround:- Manually force the linker to generate a .map file with the folder name using `target_link_options()`.Suggestion:- Modify the Build Analyzer to also check for

Hi!My STM32F207 behave funny when i "blx r3" from 0x800'0344 (FLASH) to 0x870 (lower 112KiB SRAM mapped to 0x0):It seems to ignore the first 4 bytes of instructions... When i insert 4 nops at 0x870 (or "DSB();ISB();"), then everything works as expected:int main() { { dbgb[0]=0xAFFE0000; asm("nop\n nop\n nop\n nop"); } { dbgb[19]=__SP(); for (u32 i=0; i<16; i++) dbgb[i]=0xABBA0000|i; } { dbgb[8]=__get_MSP(); dbgb[10]=__get_PSP(); dbgb[12]=__SP(); } { dbgb[0]=0xAFFEABBA; bla(); dbgb[1]=0xAFFEBEEB; } { dbgb[9]=__get_MSP(); dbgb[11]=__get_PSP(); dbgb[13]=__SP(); reset(); return 0; } init(); if (!mainrptver(0)) reset(); SET_BIT(SCB->SCR,SCB_SCR_SLEEPONEXIT_Msk); __WFI(); } void Reset_Handler() { dbgb[16]=__get_MSP(); main(); }the code in the flash is this (P is a u32* to 0x2000'0000):SYSCFG->MEMRMP = (0b11 << SYSCFG_MEMRMP_MEM_MODE_Pos); __DSB(); __ISB(); // map first 112KiB of SRAM to 0x0 __set_MSP(P[0]); __DSB(); __ISB(); // set stack pointer from app's ((u32*

I guess I have found a Bug in the G473RC debug launch script:I have a STM32G473RC MCU with 128k RAM and 256k Flash.As long as the Flash File stays below the size of 128k all works fine. I can develop, test and debug with CubeIDE. As soon as the flash file becomes larger than 128k, I can no longer debug the Software, because the Launch of the debugger exits with an error message:error dialogThe complete output in the console is:STMicroelectronics ST-LINK GDB server. Version 7.4.0Copyright (c) 2023, STMicroelectronics. All rights reserved.Starting server with the following options: Persistent Mode : Disabled Logging Level : 1 Listen Port Number : 61234 Status Refresh Delay : 15s Verbose Mode : Disabled SWD Debug : Enabled InitWhile : EnabledWaiting for debugger connection...Debugger connectedWaiting for debugger connection...Debugger connectedWaiting for debugger connection... ------------------------------------------------------------------- STM32CubeProgrammer v2.14.0 ---------------

Hello, I have the same problem but with the new version STM32CubeIDE_1.19.0. All the symptoms are the same as in this post but in the STM32G473RB processor and when the firmware becomes more than 64KB.    Cube programmer normally writes the .elf taken from the project10:46:40 : Data read successfully10:46:40 : Time elapsed during the read operation is: 00:00:00.00710:46:44 : External loader sector number is too big, displaying only the first 4000 sectors10:47:12 : Memory Programming ...10:47:12 : Opening and parsing file: bms_g474.elf10:47:12 : File : bms_g474.elf10:47:12 : Size : 64.05 KB10:47:12 : Address : 0x0800000010:47:12 : Erasing memory corresponding to segment 0:10:47:12 : Erasing internal memory sectors [0 65280]10:47:13 : Download in Progress:10:47:14 : File download complete10:47:14 : Time elapsed during download operation: 00:00:01.89110:47:14 : Verifying ...10:47:14 : Read progress:10:47:14 : Download verified successfully10:47:14 : RUNNING Program ...

We are creating a driver for a W25Q128JV Winbond Nor Flash chip. We are working with a STM32 H743ZI2 board and communicating on the QSPI peripheral with the help of the HAL libraries. Currently the driver can successfully Write to the chip using standard Page Program (0x02h) and the Quad Page Program (0x32h). We are also successfully doing a Fast Read (0x0Bh) up to speeds of 72MHz and a Fast Read Dual Output (0x3Bh) up to speeds of 36MHz before they start to fail. Currently we are using a 3.3V power bus, so based on the AC Electrical Characteristics seen in the datasheet we expect these commands to work up to speeds of 133MHz.Below is the CubeMX setup we are using for the QSPI peripheral:*Scaled clock down to 12MHz for logic analyzer testingIf you prefer the generated code that is also provided below.QSPI_HandleTypeDef hqspi;   /* QUADSPI init function */ void MX_QUADSPI_Init(void) {   /* USER CODE BEGIN QUADSPI_Init 0 */   /* USER CODE END QUADSPI_Init 0 */   /*

I am officially confused.I'm trying to use an ADC without the HAL layer, and for some reason I just don't get it to work. With HAL, it works fine.I have tried comparing register contents, and I've now run into a wall. There must be something the HAL function is doing that I am missing or misunderstanding.In this test, I am trying to sample ADC2, channel 16, just once, without DMA or anything. With my own code, ADCSTART never goes low after I've started the ADC.When I check what the HAL code does differently, I simply don't get it.The HAL setup code (which works): ADC2Handle->Init.ClockPrescaler = ADC_CLOCK_ASYNC_DIV1; ADC2Handle->Init.ContinuousConvMode = DISABLE; ADC2Handle->Init.DMAContinuousRequests = DISABLE; ADC2Handle->Init.DataAlign = ADC_DATAALIGN_RIGHT; ADC2Handle->Init.DiscontinuousConvMode = DISABLE; ADC2Handle->Init.EOCSelection = ADC_EOC_SINGLE_CONV; ADC2Handle->Init.ExternalTrigConv = ADC_SOFTWARE_START; ADC2Handle->Init.ExternalTrigConvEdge

I am connecting NUCLEO-H743ZI2 to PC via USB, it gives the following error:The interface firmware FAILED to reset/halt the target MCU STM-32List possible solutions to the above error.

Hello,I am using on my board STM32H755XIH6 CPU and I connected the SMPS feature.The board voltage is 3.3V, the SMPS regulate the voltage to 1.8V and supplies the LDO.I am using VOS1 and right now it's working WELL at room temperature.I measured the VLXSMPS and I want to be sure if the overshoot and undershoot is ok?can the component be damaged from this overshoot and undershoot?can you explain to me why I see this? 

Hi all,I’m working on a project using an STM32F407 and running into issues with low-power modes. I can put the MCU into STOP mode successfully, but when I try to wake it up with an external interrupt (EXTI line on a GPIO pin), nothing happens. The device just stays stuck until I reset it manually.Here’s what I’ve tried so far:Configured the EXTI line with rising-edge trigger.Verified the interrupt works fine when the MCU is running normally.Enabled the corresponding NVIC interrupt before entering STOP mode.Added __WFI() after setting STOP mode in the power control register.Despite this, the MCU never wakes up when the pin is toggled. I must be missing something in the clock or power configuration, but I can’t figure it out.Has anyone dealt with this before on STM32F4 (or similar STM32 family)? Any pointers on debugging wake-up sources in STOP mode would be a huge help.Thanks!

It seems like the program is getting stuck in the Error_Handler loop and not coming out. Could there be a problem with my code? /* USER CODE BEGIN Header */ /** ****************************************************************************** * @file : main.c * @brief : Main program body ****************************************************************************** * @attention * * Copyright (c) 2025 STMicroelectronics. * All rights reserved. * * This software is licensed under terms that can be found in the LICENSE file * in the root directory of this software component. * If no LICENSE file comes with this software, it is provided AS-IS. * ****************************************************************************** */ /* USER CODE END Header */ /* Includes ------------------------------------------------------------------*/ #include "main.h" #include "can.h" #include "usart.h" #include "gpio.h" /* Private includes -------------------------------------------------------

I have a question, when I jump from the bootloader to application code from internal flash, I didn't have to disable the interrupt and re-enable them in application, however when I do using the external flash I have first disable then re-enable the interrupt in the application code, otherwise the code just get stuck inside the HAL_InitTick() if i do not disable interrupt in bootloader. It is only that I re-enable the interrupt after SystemClock_Config() function in the application code that my code start working properly as I disable the interrupt from bootloader.  I'm a bit confused why is this the behaviour even though the jumping function is same with the only reason of disabling interrupt in the case of external flash with the reason mentioned above ?

Hello, I found in the documentation search for STM32U5G9 that some interfaces available for high-speed communication, such as OctoSPI and HexaSPI, do not seem to support slave mode. The device we are making requires two STM32U5G9 chips, each connected to a display, and these displays need to show synchronized content. Additionally, one of the U5G9s will connect to a CYW55513IUBGT for network/Bluetooth communication, while the other needs to acquire data through high-speed communication between chips, so UART may not meet the requirements. Therefore, I would like to understand how I can enable high-speed communication between the two STM32U5G9 chips. ...

Hello, I am working with the STM32H747I microcontroller and using the SPI6 peripheral to interface with an external ADC (MCP3462RT). I have observed that when the system clock (SYSCLK) is set to 120 MHz, SPI6 communication works correctly and the ADC provides valid data. However, when SYSCLK is configured to 480 MHz, the ADC starts giving wrong readings even though SPI6 does not hang. To debug this further, I need clarification: On the STM32H747BIT6, is SPI6 clocked from APB4 (via RCC_APB4ENR) or from another APB domain? If SPI6 is indeed on APB4, does its effective clock depend on D2PCLK1/D2PCLK2 or directly on D3PCLK4? Are there any known limitations when running SPI6 at high system clock frequencies (SYSCLK = 480 MHz)? Understanding the exact clock domain of SPI6 will help me tune the prescaler and ensure reliable ADC communication. Thanks in advance for your support. Best regards,Sai Ganesh CS

Hi,  When I clear the EXTSEL bits in the ADC1 CFGR1 register, my resolution bits also get cleared ?. My ADC randomly changes resolution. Below is screenshots of the code.  Why does this happen ?, I can disable the ADC to write the RES bits to what they were. Don't really want to do that unless I have to. 

Hi,We've successfully implemented the use of external RAM connected via the OCTOSPI1 interface on the B-U585I-IOT02A board, using the example code provided in the CubeMX packages for read/write operations. Everything works as expected under normal conditions.However, things get complicated when we introduce Stop2 mode. Upon exiting Stop2, the system enters the HardFault handler, suggesting a fault likely triggered during or immediately after wake-up.According to the datasheet, the OCTOSPI interface is frozen during low-power modes, and its register values are preserved. Based on this, I assumed that reconfiguring the clocks after exiting Stop2 would be sufficient—but apparently, it's not.Has anyone successfully implemented external RAM access with Stop2 mode? Are there additional steps or configurations required before entering or after exiting Stop2 ?Note : the issue happens only out of the debug mode (when the debug probe is not used) !Thanks in advance for any insights! 

hi:I have two NUCLEO-H563ZI EVB boards  and tried to implement I3C controller and target feature.When ENTDAA was issued, I obtained the target 48-bit provisioned ID "0x020813810100" from waveform, I saw the description from I3C register  I3C_EPIDR ,it said" Bits[31:16] of the provisioned ID can be 0" but I got the actual value is "0x1381",so where is this value stored?In addition, it seems that the target can issue a 48 bit provided ID without software operation , is this sending process entirely completed by MCU hardware？

Hi, @FBL  I am also using this board and STM32Cube_FW_U5_V1.8.0 to create a USBX stand-alone (without THREADX) MSC device,but struggling to get the board to enumerate with the PC.I'm not sure if it's a configuration issue or a code modification problem. Below are my configurations and code modification points.Could you please help analyze them? Thank you very much! configurations: USB_OGT_HS: NVIC: RCC： SYS： USBX: clock tree： code: UINT MX_USBX_Device_Init(VOID){//default code...... /* USER CODE BEGIN MX_USBX_Device_Init1 */ USBX_APP_Device_Init(); /* USER CODE END MX_USBX_Device_Init1 */ return ret;} USBX_APP_Device_Init: MX_USB_OTG_HS_PCD_Init： HAL_PCD_MspInit:   edit related thread: Solved: STM32U5A9J-DK1 USB Device question - STMicroelectronics Community

Hi all, i am going through deeper configuration of GPDMA on STM32U5 and there are some things i do not understand.S/DBL_1 in TR1 register is able to vrite destination/source burst length in range 0-63 but FIFO size is 8 bytes for channels 0-11 and 32bytes for channels 12-15. Why is burst length possible to set up up to 64? How is GPDMA able to buffer that into FIFO? Isnt it a mistake in RM0456? 

Is there a way to set the FDCAN TX and RX FIFO sizes for STM32H7R7 in CubeIDE?I snooped around and found a list of macros that are responsible for determining the FDCAN RAM size in the stm32h7rsxx_hal_fdcan.c. Do I just modify these values to set the FIFO sizes? Here is my configuration parameters. 

I am using the Advanced and General purpose timers on the STM32G474VE for PWM generation and Input capture.Is it possible, for example, to use TIM4 Ch1 to generate PWM output and TIM4 Ch2 to be used as Input Capture simultaneously?If these 2 features are used on different channels of the same timer are there any timing issues that could prevent me from using them simultaneously to drive, for example, a PWM controlled fan with a Tachometer that generates signals for the MCU?

I found https://community.st.com/t5/stm32-mcus-products/stm32g491kxu6-don-t-have-exposed-die-pad/m-p/625099#M231656 on differences between STM32G491KCU3 and KCU6. Is junction temperature range the only difference between these parts?

Greetings, I'm making a project, using a B-U585I-IOT02A board in which I made a Java program that can flash a firmware (using the USB DFU protocol) and also set Readout Protection to Level 1 through the Option Bytes. The program can flash the firmware and set RDP level 1 successfully, but I wanted to be able to flash a firmware, using the USB DFU while having the RDP set to level 1 and I can't. Every time I set the RDP level 1, I can't upgrade using USB DFU, I need to use the STLINK, go to the STM32CubeProgrammer and set the Option Bytes back to level 0, which will mass erase the flash. I know I can't do all this with the STM32CubeProgrammer, but I want to be able to do it with my program (for personal reasons).So the question is, how can I upgrade the firmware using USB DFU, with RDP set to level 1? Thank you! 

I would need to know how much power does an STM32G0 consume when kept in reset by pulling down the RST pin.Is it specified somewhere?I'm afraid it might be more than what the part uses running a well power optimized software, right?