STM32 MCUs

We have an issue with a scroll list widget, on the hardware when you touch and scroll to a point, stop then lift your finger of the display the list accelerates  in the direction it was dragged in initially. This behaviour is not seen the simulator. In the designer, we have scrollable container with a scroll list inside it. Setting animation has no effect, easing option = In, Swipe Acc = 0, Drag Acc = 0, Overshoot % = 0. we have tried adjusting the both Acc without any effect.The list has up to 50 entries.scroll list void listMenuView::setupScreen() { menuItems = presenter->getListItermParams(); scrollList1.setItemSelectedCallback(scrollListItemSelectedCallback); params = static_cast<CONTROL_VERTICAL_MENU_T *>(presenter->getWidgetParams()); menuHeader1.params = &params->menuHeader; menuHeader1.updateConfigs(); menuHeader1.setEventListener(this); messageBox1.setEventListener(this); // set the size of the scroll list based on the number of items

I am working on a custom board with STM32F103CBT6TR. Initially, flashing the code resulted in a Hard Fault error, but now it consistently enters a SIGTRAP even after removing all breakpoints. Additionally, the GPIO pins are not toggling as expected. The code is attached as notepad file for reference. Can someone give a solution to this, thank you. 

Title edited to indicate that this is specific to J-Link.Hi,After updating to STM32CubeIDE 2.1.0 I get the following message after starting a debug session. Live expressions do not work.From the console:SEGGER J-Link GDB Server V9.14a Command Line Version JLinkARM.dll V9.14a (DLL compiled Jan 28 2026 17:11:52) Command line: -port 2331 -s -device STM32F769NI -endian little -speed 4000 -if swd -swoport 2332 -vd -rtos C:\ST\STM32CubeIDE_1.11.2\STM32CubeIDE\plugins\com.st.stm32cube.ide.mcu.externaltools.jlink.win32_2.5.200.202601091506\tools\bin\GDBServer\RTOSPlugin_FreeRTOS.dll -----GDB Server start settings----- GDBInit file: none GDB Server Listening port: 2331 SWO raw output listening port: 2332 Terminal I/O port: 2333 Accept remote connection: localhost only Generate logfile: off Verify download: on Init regs on start: off Silent mode: off Single run mode: on Target connection timeout: 0 ms ------J-Link related settings------ J-Link Host interface: USB J-Link script: none J-Lin

I've got some trouble with the CRC unit in an STM32L475.At first, I got wrong CRC results, but then it dawned on me that the compiled code didn't force only 8 bits at a time into CRC->DR. So I added what I've used elsewhere, to force the compiler to store only 8 bits in a 32-bit register.*(__IO uint8_t *)(CRC->DR) = Temp;Temp is a uint8_t variable. Below, it certainly looks like a single byte is transferred to CRC-DR (strb instruction). *(__IO uint8_t *)(CRC->DR) = Temp; 80013ea: 683b ldr r3, [r7, #0] 80013ec: 7018 strb r0, [r3, #0]However, after I modified my code that way, it would seem that nothing is calculated at all. No matter how many (non-zero) bytes I throw into CRC->DR, the output just stays at 0.If I revert back toCRC->DR = Temp;at least I get something, albeit an incorrect value as soon as I enter more than one byte.I initialise the CRC unit like this: CRC->POL = 0x04C11DB7; CRC->INIT = 0; CRC->CR = CRC_CR_RESET;Is there something blatantly obv

I’m choosing a microcontroller for a new STM32 design and I’d appreciate some recommendations.I don’t have particular requirements for compute performance, memory size, or ultra‑low power — just solid peripheral support and a Nucleo board available for development. Required peripherals: 1 × FDCAN (CAN FD) 3 × SPI (in practice only 1 SPI with multiple CS likely) 3 × I2C  Constraints: Prefer MCU in LQFP / QFN (no BGA) Compact (48 pins)  Development on a Nucleo board  I’ve looked at parts like STM32C552VET6 and STM32L552CCT6 as potential targets, but I can’t find a dedicated Nucleo board for them.   Any suggestion? thank you,   best regards,   Gianluca

Hi,I am using a STM32WB5MMGH6 BLE module and for some reason HAL_IncTick() is not being called. It is baffling because it was working perfectly well when I was recently working on it before switching to another project for a week.I stripped the project down to almost nothing and placed a HAL_Delay() right after the CubeMX-generated initialization code in main(). So no custom code could do anything to affect that behavior (like turning off interrupts etc). However, the delay never completes.The code is stuck inside the while loop in HAL_Delay() because HAL_IncTick() is never being called (i.e. the system tick is not incrementing) so the HAL_GetTick() always returns 0. __weak void HAL_Delay(uint32_t Delay) { uint32_t tickstart = HAL_GetTick(); uint32_t wait = Delay; /* Add a freq to guarantee minimum wait */ if (wait < HAL_MAX_DELAY) { wait += (uint32_t)(uwTickFreq); } while ((HAL_GetTick() - tickstart) < wait) { } } The Timebase Source is set to SysTick

Hi,Observed ProblemHAL_ADC_Start_DMA() returns HAL_OK, TIM2 starts, ADC begins converting (confirmed via ADC_ISR in debugger), but HPDMA1 Channel 0 immediately raises a DTE (Data Transfer Error), triggering the error callback. EnvironmentMCU: STM32N657X0HXQBoot mode: Two-stage boot — FSBL + XIP Application (external flash via XSPI2, mapped at 0x70100400)Toolchain: STM32CubeIDE / GCCHAL: STM32CubeN6 (latest)Security mode: Full Secure — all code runs in Secure Privileged mode, no NonSecure worldProject DescriptionThis is a minimal reproduction project containing only:ADC1 — single channel (PA8 / INP5), triggered by TIM2 TRGO, DMA circular modeHPDMA1 Channel 0 — linked-list circular mode, PERIPH_TO_MEMORY, ADC1 → AXISRAM2TIM2 — provides ADC trigger at fixed rate (Period=799, no prescaler)No ETH, no LwIP, no NPU — deliberately stripped down to isolate the DMA issue.Memory Layout (Linker Script)  ROM (XIP) : 0x70100400, 511K — code in external flashRAM (FLEXRAM) : 0x34000000,

I am using an STM32H7 MCU and configuring the system clock to 400 MHz using CubeMX. The clock tree shows SYSCLK = 400 MHz, and MCO2 is configured to output SYSCLK.However, when I debug:HAL_RCC_GetSysClockFreq() returns 64 MHzRCC->CFGR shows SWS = 0 (HSI is used)SW = 0, meaning the system is not switching to PLL It seems that the PLL is not being selected or is failing to lock, and the system remains on HSI. I have configured PLL and SYSCLK source in CubeMX, but the change is not reflected at runtime.HAL_RCC_GetSysClockFreq() RETURNS 64MHZ  

Hi Support,I am unfamiliar with this project structure where the generated project contains separate boot/ and appli/ directories. I created the project using STM32CubeMX with the CMake toolchain selected, and noticed that two separate .elf files are produced after building.I am unsure which of these should be used when flashing the board using STM32CubeProgrammer. Currently, I am able to successfully flash the device using the .elf located in the /boot/ build directory, but I cannot flash the .elf located in /appli/.Could you clarify the purpose of the boot/ and appli/ directories and which firmware image is intended to be flashed? Additionally, is there a way to generate a more traditional single-application project structure (i.e., without separate boot and application directories) when targeting the STM32H7S3L8?Any guidance or suggestions would be greatly appreciated.

Post updated by a ST moderator: 1- Title translated from Chinese to English. 2- Used </> button for the code. I am attempting to transplant the latest FreeRTOS kernel program on the basis of the project generated by CubeMX. When FreeRTOS uses HSI, there is no problem and it runs normally. However, when using HSE, an initialization timeout occurs. Without transplanting FreeRTOS, HSE can pass the initialization normally.My approach was to incorporate the xPortSysTickHandler, xPortPendSVHandler, and vPortSVCHandler required by FreeRTOS into the three functions in the it file. Then, I found that it was the xPortSysTickHandler() within the systick_handler() that was causing the issue. After commenting it out, the HSE could be initialized normally. So, I'm asking on the forum what the reason is and if there's a way to solve it. AI is not reliable. void SysTick_Handler(void) { /* USER CODE BEGIN SysTick_IRQn 0 */ /* USER CODE END SysTick_IRQn 0 */ HAL_IncTick(); /* USER CODE BEGIN

HiAs I experienced some problems with 2.1.0, I reverted to 2.0.0 and in that process I seem to have gotten the error:Program "gcc" not found in PATH - "[Discovery options] page in project properties"I followed the instructions found in the stm32CubeIDE user guide https://www.st.com/resource/en/user_manual/um2609-stm32cubeide-user-guide-stmicroelectronics.pdf, but the problem persists.Is there a way to manually clear this from any of the configuration XMLs perhaps?The code does still compile and creates binaries, so the error is just a nuisance.[Edit] spellingBest regardsMartin 

在官网下载的CLT工具链安装包，管理员运行后显示如图报错该怎么办？

So, when I was actually trying to work on the STM32F103CBT6TR MCU which is placed onto the custom board while I tried to toggle PA1 in it which only gave floating values then in debug, I found out it is going into Hard Fault Handler so then again I replaced them with new IC but again it is coming as same Hard Fault Handler. I also tried for pin 0 too. What can we do to solve this?

Split from How to make the FDCAN with DMA - which is solved.TL;DR: STM32s don't support DMA for CAN or FDCAN.Hi, thanks for the clarity.But, the doubt I'm having was, then how to handle that much data rate like eg.5mbps in FDCAN without any help of DMA?In my case, the CPU will be busy with doing other high priority works, so how can I handle the CAN data without the intervention of CPU.Kindly, suggest a way to resolve this. Thanks

I updated the STM3CubeProgrammer to version v2.22.0, and after restarting the app, it started showing a blank page. I was also not able to close the application directly. I had to end the task from the task manager. I uninstalled the latest version and installed v2.20.0, but it is also showing a blank page. Also, in STM32CubeIDE, I am not able to run and debug code. It gets stuck at  "Download in progress". Are both problems related?

Hello, I'm using the STM32N6570-DK board.I completed the TOUCHGFX project through this URL, and there was a DEBUG problem while I was making CUBEMX and CUBEIDE operating it.(https://community.st.com/t5/stm32-mcus/how-to-debug-stm32n6-touchgfx-applications-using-stm32cubeide/ta-p/845901)I'm not moving from FSBL to APPLI. I'm asking for your help on this part.Please check.

Hi, I tried to configure the USB Host for a project, but it’s difficult to configure, and I am not finding any online support available for the STM32H5 series controller. My requirement: I configured PB4 as an output, which is connected to a green LED. Whenever I plug the USB into my controller, the green light turns on, and whenever I remove the USB from the controller, the green light turns off. I’ve tried some methods, but they are not working. Can anyone please help me?      

I have been using a STM32F469i Disco board to interface with a 800x800 LCD in MIPI DSI video burst mode. In order for this to work from the DISCO board, I have an adapter PCB to connect from the DISCO board to the LCD.It took a while to get going, but the setup with the custom LCD and DISCO board is working fine.I have recently moved to a custom board; I have intentionally made the video dependent aspects of this board the same as the disco board so that I can run my software on either the disco or the custom board without making any changes.The custom board sometimes exhibits odd behaviour when rendering from the SDRAM via the LTDC.Enabling the test colour bars from the DSI always display ok without any problem.From SDRAM/LTDC, the horizontal start point shifts from the left side of the display to some arbitrary location across the width of the display. This occurs randomly, it can be running for hours and remain stable, other times it may shift once, then be stable for a time and may

What is recommended way to change or override the 'SYSTEM_CLOCK' symbol defined in 'tx_initialize_low_level.S' , that feeds into the threadX systick period calculation?  I could change the SysTick after threadX is started -- that is probably the easist fix. I dont want to modify the threadX submodule in my project, as its pulled from the internet at some pinned version. I've currently made a local copy of 'tx_initialize_low_level.S', and then I use CMake to select that particular S file - so that solves the problem, but I dont like having a personal copy of a file from the submodule. After experimenting for some time, and then scouring the web, I cant find any suggestions on this issue, there are some changes that can be imported via having your own 'tx_user.h' -- but I cant see anything that can override the SYSTEM_CLOCK.   Cheers, Nick

Code generation of the attached .ioc file (copy of ST example file of similar name) does not generate clock init for UART4.  This means the example application hard faults.  I see no reason why the UART clock should not be initialised here and would save someone time debugging in the future!In stm32mp2xx_hal.c:void HAL_UART_MspInit(UART_HandleTypeDef* huart) { GPIO_InitTypeDef GPIO_InitStruct = {0}; if(huart->Instance==UART4) { /* USER CODE BEGIN UART4_MspInit 0 */ // TODO: Need this here! __HAL_RCC_UART4_CLK_ENABLE(); /* USER CODE END UART4_MspInit 0 */ /**UART4 GPIO Configuration PH8 ------> UART4_RX PH7 ------> UART4_TX */ GPIO_InitStruct.Pin = GPIO_PIN_8; GPIO_InitStruct.Mode = GPIO_MODE_AF_PP; GPIO_InitStruct.Pull = GPIO_NOPULL; GPIO_InitStruct.Alternate = GPIO_AF4_UART4; HAL_GPIO_Init(GPIOH, &GPIO_InitStruct); GPIO_InitStruct.Pin = GPIO_PIN_7; GPIO_InitStruct.Mode = GPIO_MODE_AF_PP; GPIO_InitStruct.Pull = GPIO_NOPULL; GPIO_InitStruct.Sp

Hello,I found a bug in STM32CubeMX code generation for STM32H7S3.When configuring Ethernet with external clock input (ETH_CLK pin,PD6 with AF4_ETH) as PHY clock source, CubeMX does not generateGPIO initialization for this pin in HAL_ETH_MspInit().Workaround - must add manually:__HAL_RCC_GPIOD_CLK_ENABLE();GPIO_InitStruct.Pin = GPIO_PIN_6;GPIO_InitStruct.Mode = GPIO_MODE_AF_PP;GPIO_InitStruct.Pull = GPIO_NOPULL;GPIO_InitStruct.Speed = GPIO_SPEED_FREQ_HIGH;GPIO_InitStruct.Alternate = GPIO_AF4_ETH;HAL_GPIO_Init(GPIOD, &GPIO_InitStruct);Without this, Ethernet does not work even though all otherETH pins are correctly initialized by CubeMX.Steps to reproduce:1. Select STM32H7S32. Enable Ethernet (ETH)3. Set clock source to external clock via ETH_CLK pin (PD6)4. Generate code5. ETH_CLK pin GPIO init is missing in generated codeCubeMX version: 6.17.0MCU: STM32H7S3Thank you

Hello. Have some issues with MCU ADC configuration and data.Hardware:                                                                                                                                                                                                                                           - MCU: STM32G473MET3                         &

Hello :My project use physical buttons and no touch screen.Can I bind physical buttons to repeat buttons? So I don't have to realise it myself.

Hello, I have come across an issue with the RTC in my project. In my project I am using the following:- MCU:- STM32H743IIT6 IDE version:- 1.19.0 SDK version:- 1.12.1 I will discuss the issue here, I wrote a program that uses the RTC and print the current time and I tested it straight for 72 hours, what I noticed since the second day that there was a constant drift in time, which kept on changing, and on the last day I observed that there was a total drift of 13 seconds since I started the test. This drift is really concerning for the product that we have made, and that product is already out for field operations. This issue was earlier reported and a ticket was created on ST's online support forum the ticket id is 00255958. They replied to the issue that was reported and asked us to perform the test that I described above, and report this issue over here at ST Community. Please do reply to this message if anyone has any solution for this issue. It is a matter of urgency I a

I created a GUI with TouchGFX, enabled UART and created a custom task in freeRTOS in STMCubeMX.  When running the code the display is just blank when I add this code inside of my custom taskif(xQueueReceive(queueHandle, &message, 0) == pdPASS) { printf("Message received"); }If I comment this code out the gui displays.  However, I found something interesting that if I debug and set a breakpoint at the for(;;) loop statement on line 729 in main in the UART_Task and another breakpoint on the print message and then press play to continue, the GUI displays and when I tap a button on my GUI I get to the breakpoint on the printf message which is exactly what I'm trying to do and it works perfectly.  I'm not sure why it works when I first breakpoint there, but won't work just loading the program onto the board.  Here is the main code/* USER CODE BEGIN Header */ /** ****************************************************************************** * @file : main.c * @bri