STM32CubeMX (MCUs)

When I used the MMT tool in STM32CubeMX to configure a 256MB NAND FLASH based on FMC, an error appeared. I am using the STM32H743IIT6 chip and have configured NAND FLASH in the FMC. I want to know how to solve this problem. 

Yes I should have taken a backup - but modern software must always have build-in backup solution so you do not corrupt your own files. Ask chatgpt if you need the code. I used 2 days to make this project, luckily I have the main.c so I can copy names from this.  I am on Linux Mint version 22.2 with STM32CubeMX version 6.16.1 and Visual Studio Code Version: 1.107.1.The fault was in STM32CubeMX, that did not save correctly. During my work I experienced the software closing without saying a word on the error, especially in the ADC1 setup. But every time I could just start it again, but not this time:-(Attached you find the surviving part of the IOC file.Thank you for listening to my disaster. Best regards   

 We are using the STM32N657Z0H3Q (142-pin TFBGA package).CSI behavior in STM32CubeMX is inconsistent across versions:In older CubeMX versions(1.64), CSI lanes (CSI_D0P/N, CSI_D1P/N, CSI_CKP/CKN, CSI_REXT, etc.) are displayed in the Pinout view, but these signals are not actually assignable to physical pins. They appear as virtual pins only.In newer CubeMX versions(1.65), CSI is still listed in the peripheral view, but no CSI lane pins are shown at all. In case, the generated .ioc file contains only virtual signals:VP_CSI_VS_CSI.Mode=CSI VP_CSI_VS_CSI.Signal=CSI_VS_CSI VP_DCMIPP_CSI.Mode=SerialInterface VP_DCMIPP_CSI.Signal=DCMIPP_CSIOn hardware, when connecting a CSI-2 camera, the following is observed:DCMIPP and CSI registers initialize correctly,no LP-to-HS transition on the supposed CSI pins,ClkAct remains at 0,CSI interrupts never trigger.This behavior strongly suggests that the CSI-2 D-PHY pins are not bonded out on the STM32N657Z0H3Q package, even though CubeMX and the

Hello ST Community,I am writing to report a serious regression in STM32CubeMX 6.16.0 running on Arch Linux (KDE Plasma) with a 1920x1080 resolution.Environment:OS: Arch Linux (Rolling)Java: OpenJDK 25Desktop: KDE Plasma (Wayland/X11)Screen Resolution: 1920x1080The Regression (Comparison):1. STM32CubeMX 6.15.0 (Previous Version):Status: Works perfectly out-of-the-box.Details: I did not need to modify any configuration files or set any environment variables. The application launched correctly, the UI was usable, and the window could be resized and maximized without issues.2. STM32CubeMX 6.16.0 (Current Version):Status: Unusable / Broken.Details:The default UI rendering has issues (fonts are tiny or behavior is inconsistent).When trying to fix it using standard scaling methods (e.g., _JAVA_OPTIONS="-Dsun.java2d.uiScale=2" or GDK_SCALE=2), the window management breaks.The window refuses to maximize, enter full screen, or resize properly. It seems internal window constraints have been chang

The STM32H7RS series includes a USB HS PHY with a special PLL that generates the 480MHz clock required as well as a 60MHz clock for the OTG HS peripheral and optionally a 48MHz clock for the separate OTG FS peripheral. The PLL for the USB PHY has several configuration bitfields in the RCC->CCIPR1 register that are used to set the source of the PLL reference clock, as well as its frequency: Bits 13:12 USBPHYCSEL[1:0]: USBPHYC kernel clock source selection. Set and reset by software.00: hse_ker_ck (default after reset)01: hse_ker_ck / 210: pll3_q_ck11: reserved, the kernel clock is disabledBits 11:8 USBREFCKSEL[3:0]: USBPHYC kernel clock frequency selection .Set and reset by software.This field is used to indicate to the USBPHYC, the frequency of the reference kernel clock providedto the USBPHYC.0011: The kernel clock frequency provided to the USBPHYC is 16 MHz1000: The kernel clock frequency provided to the USBPHYC is 19.2 MHz1001: The kernel clock frequency provided to the USBP

Greetings everyone,Using the C programming language, I'm creating the encryption algorithm AES-256 code for a trusted execution environment and checking to see if the hardware supports it.AES/CRYP enabling is giving me trouble. I can't find it under Connectivity or Security, and I can't enable it with STM32CubeMX.I'm getting this error, so please assist. 

We are using STM MCU MPN : STM32U375VGT6Q for one of our new projects, we are currently using HSE External 16 MHz crystal for system clock.We are trying to configure the STM32U375 MCU to run at 96 MHz using an HSE external 16 MHz crystal. In STM32CubeMX, we are unable to find the PLL option sourced from HSE in the clock tree on the Clock Configuration page.Could you please advise us on below points:Use HSE (16 MHz) as the PLL sourceSet the PLL multipliers/dividers to achieve SYSCLK = 96 MHz

It seems like CubeMX sets this default value hspi1.Init.MasterKeepIOState = SPI_MASTER_KEEP_IO_STATE_DISABLE; when doing software NSS and SPI Mode 3 like: hspi1.Init.CLKPolarity = SPI_POLARITY_HIGH; hspi1.Init.CLKPhase = SPI_PHASE_2EDGE; hspi1.Init.NSS = SPI_NSS_SOFT; This results in a non working SPI at least on STM32H652 (did not check the signals with Oscilloscope, but I assume the CLK and/or MOSI float back to an undefined value after the first transaction, breaking the next one). This can be fixed by doing:hspi1.Init.MasterKeepIOState = SPI_MASTER_KEEP_IO_STATE_ENABLE; Wouldn't it be recommended CubeMX defaults the IO_STATE_ENABLE in this case? This one Bit just cost me 5 Hours of headache :\

Why can’t my cubemx configure L1 cache? How to enable it?Also, the MPU cannot be configured. You can only use the default configuration and modify it in the generate code.I also configured Memory management, but did not see the enable Cache and MPU synchronization settingsCubeMx 6.16.1 on macos MAC 26.1MCU:STM32H743IIT6  

I need to learn more (detail) about STMCubeMX  "extended mode" and small-pincount multi-bonded MCUs (this posting label specifies STM32C0 series which is what I'm currently working with.)STM32CubeMX UM1718 section 4.5.8 describes extended mode (I encountered when exploring this option while using STM32CubeMX with a new project), but other than cautions (that an option byte is required and that improper use can affect power consumption etc) I could find no further ("how it works") detail there.HAL_SYSCONFIG_SetBinBinding doesn't provide a suitable solution (concurrent access to a single physical pin by more than one possible peripheral.)Any recommendations on where (=application note?) I can proceed to learn about multi-bonding implementation and limitations for these small-packaged MCU products?Thanks! 

Hello Community,I'm working on a storage module using SDcard for my project. In my application I would like to read and write to the SDcard using the MDMA as indicated in the reference manual of my micro-controller. For now I have the SDcard working in 4-bit mode but using the CPU.I use the STM32H757II on a PCB connected to a SDcard reader on the same PCB.With CubeMX I generated the code that allow me to mount a FATFS on my microcontroller and I can create/open/write/read on file with no problem.But my application needs to log a lot of data to the sdcard periodically, to free-up the CPU I would like to do the transfer using a DMA.In the reference manual 58.5.7 MDMA request generation it is explained that the MDMA can control the SDMMC peripheral to start new transfer"The internal trigger lines from the SDMMC allow passing direct request to MDMA controllerto enable successive transfers from/to different internal RAM addresses without CPU use. [...]The event can trigger the clearance of

Hello allI am trying to integrate CMSIS-DSP in my CMake project. From CubeMX, I have the following options:and I see the following folder struct:and to include DSP folder in my project, I have done the following changes in my top level CMakeLists.txt.... some code # Enable CMake support for ASM and C languages enable_language(C ASM) # Create an executable object type add_executable(${CMAKE_PROJECT_NAME}) # Add STM32CubeMX generated sources add_subdirectory(cmake/stm32cubemx) add_subdirectory(Drivers/CMSIS/DSP/Source) # Link directories setup target_link_directories(${CMAKE_PROJECT_NAME} PRIVATE # Add user defined library search paths ) # Add sources to executable target_sources(${CMAKE_PROJECT_NAME} PRIVATE # Add user sources here ${CMAKE_SOURCE_DIR}/Core/Src/tm1638.c ) # Add include paths target_include_directories(${CMAKE_PROJECT_NAME} PRIVATE # Add user defined include paths # Include CMSIS core headers ${CMAKE_SOURCE_DIR}/Drivers/CMSIS/Include ${CMAKE_SOURCE_DIR}/Driv

My projects are all in C++ and were building completely fine. After I generated the code from CubeMX, the language switched back to C. I had to go and manually switch to C++, then it gave me build errors with linker script... Please fix!

Created a new project with v6.8 and reproduced the issueSteps: 1.cubeMX create new STM32F334 project and generate code.(Project-application structure-advancedProject-IDE-MDK-v5.32Code Generator- copy only the necessary library filesCode Generator- Delete previously gernerated files) 2.Create a Middlewares folder (/project folder/Middlewares), copy some folders in this folder (/project folder/Middlewares/mymiddleware).3.Generate code again, Middlewares folder is deleted.os:Win10jre:IBM Semeru jre 11.0.18.10​

The STM32N6 supports YCbCr as an input format (see reference manual RM0486 section 21.3.5). As of version 6.16.1, this option is still not available in STM32CubeMX. The generated code can be manually modified to make it work by settinghdma2d.LayerCfg[x].InputColorMode = DMA2D_INPUT_YCBCR;   

I am starting use of UM3029 Rev 3 (STM32C0 HAL drivers) and trying ensure I use HAL_SYSCONFIG_SetPinBinding properly (important because the 6 usable IO pins are multiply bonded to device peripheral pads.)I am working with STM32C011J6 (SO8 package) and am using STM32CubeMX and HAL to create example device support code (i.e., drivers.)UM3029 Rev 3 section 6 (HAL System Driver) takes me to section 6.2.1 (HAL Bind Pin Config) which has a listing for some device package/pin assignments for GPIO (my current task is to get a pin working as GPIO input), however, the list does not include any defines for SO8 package. The instruction I'm currently trying to verify (generated by STM32CubeMX for my project) is HAL_SYSCFG_SetPinBinding(HAL_BIND_SO8_PIN5_PA8), but there are others and I'd like to fully understand the utility of this function and it's arguments.I looked in UM3029 Rev 3 for a listing of allowed arguments to SetPinBinding for C0 series SO8 package in UM3029 and came up empty hande

I'm working on a project with the STM32H503CBU7 which requires USB. I have a 32MHz external crystal on my board that appears to be stable. The chip works and can be programmed and such. I also troubleshot out other physical issues like cold joints and shorts because that has burned me before when the USB device fails to enumerate.My intent was to use the PLL2Q source with the USB peripheral so I could also specify a 200MHz sys clock for everything else via PLL1. When I use the PLL2Q source however,  I get no interrupts from the `USB_DRD_FS_IRQHandler` handler and so my USB stack does not operate.To make things more confusing, it also does not work even when both PLL's have the same values set for all parameters, as shown in the image below.It is important to note that this works with the PLL1Q source, as it is shown in the image, and I'm currently compromising a little on the sys clock speed. It will work for my purposes, but I'm more interested to know whether there's some "magic

Hello.It's not possible to find a controller with a specific number of CAN buses using MCUFinder. MCUFinder counts each CAN bus twice: If it physically has 3 CAN buses, MCUFinder adds:    3 CAN buses + the same 3 CAN2.0 buses = 6 CAN buses.  This is great if it allows the controller's peripherals to be doubled so easily. Excellent. But it is very misleading because it raises false hope and displays completely unsuitable controllers.However, the program is useless when I'm searching for controllers with 4 or more CAN buses and I get a huge list of 70 possible controllers, all of which have at least 6 CAN buses, but none of them possess these qualities.  Can this bug be fixed?  

Hi there! Thank you for reading this.Where has the support for exporting footprints/symbols to Altium Designer from STM32CubeMX gone?In the promotional video from https://www.st.com/en/development-tools/stm32cubemx.html it appears there is an option for doing this, but when I try it on a recent version of STM32CubeMX no option is available.What am I missing here? Check following screenshot of promotional video vs. STM32CubeMX side by side.STM32CubeMX version: 6.16.0

After upgrade from 6.15 to 6.16 on linux ubuntu 24.04 I got this blocking error if I load project file (created with cubemx 6.15):cannot invoke com.st.microxploer.mcu.IP.getInstanceName() because mpu is nullI tried both "migrate" and "continue" options but I got the same error. Attached the project file

MCU: STM32H563VITx Stm32CubeMX version: 6.14.0 HAL Driver version: 1.5.0 When I enable EDATA option bytes in CubeMX, it generates the following code: void MX_FLASH_Init(void) { /* USER CODE BEGIN FLASH_Init 0 */ /* USER CODE END FLASH_Init 0 */ FLASH_OBProgramInitTypeDef pOBInit = {0}; /* USER CODE BEGIN FLASH_Init 1 */ /* USER CODE END FLASH_Init 1 */ if (HAL_FLASH_Unlock() != HAL_OK) { Error_Handler(); } /* Option Bytes settings */ if (HAL_FLASH_OB_Unlock() != HAL_OK) { Error_Handler(); } pOBInit.OptionType = OPTIONBYTE_EDATA; pOBInit.Banks = FLASH_BANK_2; pOBInit.EDATASize = 2; if (HAL_FLASHEx_OBProgram(&pOBInit) != HAL_OK) { Error_Handler(); } if (HAL_FLASH_OB_Lock() != HAL_OK) { Error_Handler(); } if (HAL_FLASH_Lock() != HAL_OK) { Error_Handler(); } /* Launch Option Bytes Loading */ /*HAL_FLASH_OB_Launch(); */ /* USER CODE BEGIN FLASH_Init 2 */ /* USER CODE END FLASH_Init 2 */ }​ The function does not launch

The CubeMX 6.16.0 is able to generate a CMake-project for an STM32H7 - great. A small conflict currently exists in the following two generated files [for a "basic" STM32H7 project]:- CM7/CMakeLists.txt:69# Add linked libraries target_link_libraries(${CMAKE_PROJECT_NAME} PRIVATE # Add user defined libraries )- CM7/mx-generated.cmake:81# Add libraries to the project target_link_libraries(${CMAKE_PROJECT_NAME} ${MX_LINK_LIBS}) The first specifies PRIVATEwhile the second does not - which is incompatible as per CMake. Can someone confirm this observation? Can this be made consistent in the future? If so, I would prefer the one with the scope keyword - but could also live without it here.

When enabling 2 ADCs ,  ADC1 and ADC2 of  STM32U5A5 ,both in Independent mode . The RCC enabling in MspInit called only for ADC1 and not for ADC2. What causes , that If one decide disable generataion of call to MX_ADC1_Init() in CubeMx , in order to call it somwhere else , but still enable generation to call to MX_ADC2_Init() in CubeMx , ADC2 won't work untill MX_ADC1_Init() is called.

Hi,I'm searching for a MCU with one or two advanced motor control timers to control 1 or 2 bldc motors.For this purpose I use the MCU selection tool from here: STM32 family of 32-bit microcontrollers (MCUs) - STMicroelectronicsWhen I use the filter for one or two advanced motor control timers the MCUs from the STM32G series are never displayed and I don't understand why? How should I search for all MCUs with motor control functionalities?Thanks for every hint!Best regards,Roger

Hi,I have three small suggestions to improve the CMake build system generated by STM32CubeMX to be used by VS Code to fix some annoyances. 1.In cmake/stm32cubemx/CMakeLists.txt, useset(TOOLCHAIN_LINK_LIBRARIES "-lm")instead ofset(TOOLCHAIN_LINK_LIBRARIES "m")This way CMake knows that the "m" library is an external one. When the user setsset(CMAKE_LINK_LIBRARIES_ONLY_TARGETS ON)in the "CMakeLists.txt" in order to help finding issues in complex project setups, the old behaviour causes a CMake error as there is no explicit "m" target, but with "-lm" CMake is happy. Being able to use "CMAKE_LINK_LIBRARIES_ONLY_TARGETS" is desirable as it helps finding typos easily when many targets/components are defined across many individual CMake files.2.In cmake/stm32cubemx/CMakeLists.txt, usetarget_link_libraries(${CMAKE_PROJECT_NAME} PRIVATE ${MX_LINK_LIBS})instead oftarget_link_libraries(${CMAKE_PROJECT_NAME} ${MX_LINK_LIBS})i.e. use the explicit syntax. When the user wants to refer to addition