STM32CubeMX (MCUs)

I made a support pack for better support of CAN connections.But there is no possibility to create a "Platform Setting" for CAN connections I tried to edit the "Modes.xml" manually. Than the PackCreator shows the correct IP, but STM32CubeMX doesn't accept it.  Additional: if I create a not usable platform setting there will be "unsovlable" warning.

I select a new project and select the STM32L100C6U6A. STM32CubeMX says it has 4 kBytes of RAM.I generate the project for EWARM.But when I generate the project for EWARM it puts stm32l100xba_flash.icf file in the project and that files says RAM is 16384 bytes.And the datasheet for STM32L100C6U6A says 4 kByte.Is this a bug in STM32CubeMX?My application still seems to run without errors. IAR reports 9511 bytes of readwrite data memory used.Why does it still work? Is the datasheet wrong and this device is actually delivered with 16 kBytes RAM?    

The STM32N6 reference manual shows that IC18 drives the CSI2Host and CSIPHY IP blocks at a maximum frequency of 200 MHz. CubeMX generates this clock configuration code but does not show the clock path in the clock configuration window. Additionally, it does not provide any error checking and will allow IC18 to be configured above 200 MHz.Clock tree diagram:Maximum clock rate spec:CubeMX generated code in HAL_DCMIPP_MspInit:PeriphClkInitStruct.PeriphClockSelection = RCC_PERIPHCLK_DCMIPP|RCC_PERIPHCLK_CSI; PeriphClkInitStruct.DcmippClockSelection = RCC_DCMIPPCLKSOURCE_IC17; PeriphClkInitStruct.ICSelection[RCC_IC17].ClockSelection = RCC_ICCLKSOURCE_PLL4; PeriphClkInitStruct.ICSelection[RCC_IC17].ClockDivider = 1; PeriphClkInitStruct.ICSelection[RCC_IC18].ClockSelection = RCC_ICCLKSOURCE_PLL4; PeriphClkInitStruct.ICSelection[RCC_IC18].ClockDivider = 2; 

Reporting two issues when using STM32CubeMX v6.16.1 to generate STM32N6 code. I created new secure only template project for STM32N6570-DK to demonstrate the issue (it's attached).Only changes to the new project are these:In MMT defined RAM2 area over AXI SRAM3-6. Also check the "Apply Application Regions Settings to Peripherals".Then activated RIF for FSBL:Now generate code.It generates FSBL\Core\Src\main.c function SystemIsolation_Config(void).There are two function calls that cause assert failure because they violate the HW capability: /* set up base region configuration for CPUAXI_RAM0*/ /* region2 is secure */ risaf_base_config.EndAddress = 0x1003ff; risaf_base_config.StartAddress = 0x00000400; HAL_RIF_RISAF_ConfigBaseRegion(RISAF2, RISAF_REGION_2, &risaf_base_config); /* set up Sub region configuration for CPUAXI_RAM0*/ risaf_sub_config.EndAddress = 0xfffff; risaf_sub_config.StartAddress = 0x00000400; HAL_RIF_RISAF_ConfigSubRegion(RISAF2, RISAF_REGION_2, RISAF_S

I'm considering migrating from STM32F469NIH6 to STM32F769NIH6. From data sheets it is apparant that these two MCU's have compatible pinout, however the pinout compatibility tool of STM32CUBEMX V6.15.0 doesn't show these MCU's as compatible, why is this?

When using the memory management tool (MMT) on the STM32H573 to set the backup RAM as secure it generates an invalid secure attribution unit (SAU) config:#define SAU_INIT_REGION5 1 #define SAU_INIT_START5 0x40000000 /* start address of SAU region 5 */ #define SAU_INIT_END5 0x400373FF /* end address of SAU region 5 */ #define SAU_INIT_NSC5 0The above code is the last region the MMT defines for the SAU.Typically the tool would define the region 0x40000000 to 0x4fffffff (the non-secure peripheral address space) as non-secure. However 0x40036400 is the start of the backup RAM address space which shouldn't be made non-secure.Since this is the last SAU region, there is nothing configuring the region 0x40037400 to 0x4fffffff as non-secure, and so hard faults occur when e.g. trying to access the non-secure RCC address space.I believe correctly generated code should look like the below:#define SAU_INIT_REGION5 1 #define SAU_INIT_START5 0x40000000 /* start address of SAU region 5 */ #d

CubeMX version 6.16.1 I found STM32WBA55CG project with ThreadX,  the  parameter of "TX_LOW_POWER_USER_ENTER" and "TX_LOW_POWER_USER_EXIT" will be reset to default after the ioc re-open.This bug can be 100% reproduce. 

I created a new project using CubeMX, and after that I plan to implement a framework for my firmware. I would like to better understand the best way to organize a clean and maintainable folder structure.A colleague told me that all folders should be created inside the Core directory. I would like to understand whether using Core to contain my framework is the best approach, or if it is acceptable to create additional source folders outside of it.Additionally, where can I find examples of STM32 firmware projects generated using CubeMX?

Ports definition in main.h forced to include too mutch in dependend source files when one needs ports definition only.More convenient dedicated header file with ports definition only. Something like ports.h.It would be nice to have more layered structure.

Hello ST Community,I would like to report a potential discrepancy I have discovered between the pin definitions in STM32CubeMX and the official datasheet for the STM32N6 series, specifically concerning the Serial Wire Output (SWO) signal used for debugging (SWV/ITM). This issue led to a hardware design error on my part, and I believe it warrants clarification to prevent others from encountering the same problem.According to the STM32N647xx datasheet (and related family documents), the SWO function is assigned to Pin PB5, The TRACECLK function is assigned to Pin PB3However, within STM32CubeMX (I am using version 6.16.1)(N6 MCU package version 1.3.0), the graphical pinout view shows that Pin PB3 is also listed with the "DEBUG-JTDO-SWO" functionality. More importantly, when configuring the debug port in the "SYS" settings (e.g., selecting "Trace Asynchronous Sw"), the software automatically assigns the SWO signal to PB3.Trusting the configuration tool, I proceeded to design my PCB wi

do the example of LPGPIO,why show this error.Getting started with LPBAM - stm32mcu 

I have just spoken with an ST sidekick, and I was informed that STM32CubeMX is currently not supported on Windows ARM64.Thank you for the clarification.  

Question moved from this post. Hi @mƎALLEm ,I am using STMCubeIDE with cubeMX, in that there is no such configuration for VREFBUF. is there any alternative way for that?

On a Nucleo-H563ZI with CubeIDE 1.14.0 and firmware package for H5 1.1.1.I managed to get SPI transmit and receive using DMA, triggered by a timer, going not using linked lists. I get my requested number of transmissions and results into my buffers as witnessed on an oscilloscope and a live watchpoint.But when I enable circular mode, no other modifications, in MX_SPI1_Init - HAL_SPI_Init - HAL_SPI_MspInit it sets up NodeConfig.Init.SrcDataWidth = DMA_SRC_DATAWIDTH_WORD; NodeConfig.Init.DestDataWidth = DMA_DEST_DATAWIDTH_HALFWORD;builds the node (whatever that is), inserts it into the correct DMA channel, sets circular mode, basically looks like magic but I can imagine what it is doing. But then the stuff in the NodeConfig doesn't get applied to handle_GPDMA1_Channel1, so later when I finally call HAL_SPI_TransmitReceive_DMA, it gets grumpy around line 2230 because hspi->hdmarx->Init is all zeros still. It never got updated maybe?I think there is a problem with HAL_SPI_M

CubeMX 6.16.1 MacOS 15.7.3 IntelSTM32H563ZITxI have a project using FreeRTOS with 5 tasks.If you go into <Categories><X-CUBE_FREERTOS>Choose <Tasks and Queues> click on one of the tasks. An Edit panel comes up to help you set all sorts of stuff.Click on "Task name" column header to re-sort the list according to task name and click on one of the tasks. The Edit panel comes up for the wrong task.The changes you make get applied to the task shown, but the wrong task gets shown.That is all

I'm attempting to follow https://community.st.com/t5/stm32-mcus/using-the-itm-console-for-printf-redirects-and-lwip-debug/tac-p/850072/highlight/true#M1661 but this always fails. This is on an STM32F303K8T. My reference manual saysand offers an example:    "To output a simple value to the TPIU:• Configure the TPIU and assign TRACE I/Os by configuring the DBGMCU_CR (refer toSection 33.17.2: TRACE pin assignment and Section 33.16.3: Debug MCUconfiguration register)• Write 0xC5ACCE55 to the ITM Lock Access Register to unlock the write access to theITM registers• Write 0x00010005 to the ITM Trace Control Register to enable the ITM with Syncenabled and an ATB ID different from 0x00• Write 0x1 to the ITM Trace Enable Register to enable the Stimulus Port 0• Write 0x1 to the ITM Trace Privilege Register to unmask stimulus ports 7:0• Write the value to output in the Stimulus Port Register 0: this can be done by software(using a printf function)"Based on this, and based

Pull field is not set on UART8 GPIO when configured as single-wire.STM32H743 / STM32H753. 

I'm using STM32CubeMX for STM32N657x0HxQ controller. I would like to use ST ISP Library to handle MB1854 camera module. But I could not find the X-CUBE-ISP in STM32CubeMX Pinout & Configuration page, which is as follows. So I tried to import x-cube-isp.zip file downloaded from GitHub. But I came across the following error message. My STM32CubeMX version is Version 6.16.1 for Windows 11. 

I'm using STM32N6570-DK board and developing an image processing application.When I tried to use STM32CubeMX to generate the project, I was able to set DCMIPP Pipe1 just like the attached screen capture.I would like to downsize the source image data to 800x480, but I could not find the option field in the DCMIPP Configuration view in STM32CubeMX.Is there something that I missed?My STM32CubeMX is Version 6.16.1 for Windows 11.  

Hello, I'm working with the STM32H7S7L8-DK and i want to use both USB HS and FS in device mode  but it seems in cube mx that i'm unable to enable both IRQ If i enable the HS one the FS one isn't generated and same fort the other way Is it a bug  and how manage this to get it work?Thanks 

Hi,after updating STM32CubeMX, I was no longer able to start the program without admin rights.In the past, I always used STM32CubeMX integrated with STM32CubeIDE and was able to update everything without any admin rights. Starting with version 2.0.0 of STM32CubeIDE, STM32CubeMX was removed, so I installed it separately (STM32CubeMX 6.16.0). For the installation, my company's IT department selected the installation for all users, and until now I have been able to use the program without any problems.I needed to update STM32CubeMX to the new version 6.16.1, and that's where I ran into my first problem: I couldn't update to the new version without admin rights, so I had to contact the IT department to do the update. The big problem is that after the update, I was no longer able to start the program without admin rights, and the quickest solution was to uninstall STM32CubeMX and then install version 6.16.1 directly. Now I can use the application again without any problems, but I would like

Hello!I have encountered a problem - I am unable to create a project for STM32F769I-DISCO board with both FreeRTOS using CMSIS_V2 interface and LwIP with NO_SYS parameter set to "OS Used".In old project that was setup with STM32CubeMX V6.14.0 using STM32Cube FW-F7 V1.17.2 I had no problem with setting both CMSIS_V2 and "OS Used" value.In new project that uses STM32CubeMX V6.16.1 and STM32Cube FW_F7 V1.14.4 I have to use CMSIS_V1 interface for FreeRTOS if I want to change LwIP's NO_SYS parameter to "OS Used".Did something change in recent updates, is it a bug or am I doing something wrong? Thank You for help in advance. Using FreeRTOS with CMSIS_V2Can't change NO_OS parameterCubeMX 6.16.1, Firmware F7_V1.17.4

Hi @TDK ,I have just downloaded and installed the new version 2.0.0 of the IDE and the MX software (since it is no longer integrated). I was working on a project based on the STM32WB5MMG, and everything was working correctly with IDE version 1.19.0 and STM32Cube FW_WB V1.23.0.After opening the project and regenerating the code with the new IDE version and STM32Cube FW_WB V1.24.0, I noticed some issues: in custom_stm.c it generates two times this variables:/* USER CODE BEGIN PM */ /* USER CODE END PM */ /* Private variables ---------------------------------------------------------*/ uint16_t SizeFw_Ver = 1; uint16_t SizeDatetime = 7; uint16_t SizeStatus = 6; uint16_t SizeMonitor = 15; uint16_t SizeEnv_Data = 90; uint16_t SizeFw_Ver = 1; uint16_t SizeDatetime = 7; uint16_t SizeStatus = 6; uint16_t SizeMonitor = 15; uint16_t SizeEnv_Data = 90;​2. it doesn't generate any local functions in custom_app.c:/* USER CODE END FD */ /***************************************************

When choosing SmartCard mode for USART, parameter Parity is automatically set to Even. However generated code in usart.c, does not has:hsmartcard1.Init.Parity = SMARTCARD_PARITY_EVEN;Only when I manually reselect that in GUI, the parity will be set in the generated code.I am using Nucleo-G0B1RE.

I need to use STM32CubeMX to generate initialization routine for two pins (7,8) on SO8 package of STM32CubeC011 MCU that switches the pin's roles BACK to STLINK mode. I created a new project on STM32CubeMX whose only task is to initialize pins 7 and 8 to PA13/PA14 SWCLK/SWDIO. I wanted to copy the GPIO initialization function MX generated into an existing application which had previously (that is, after start-up) changed the two pins to another mode; after that work is done, the two pins no longer need to be in GPIO mode and can be switched back to STLINK mode to facilitate firmware upgrade/debug/etc.Two screen captures from STLINK32MX are below (pin assignments and project specifications.)The resulting (very short) C language program generates the following code for initialization of the two pins: static void MX_GPIO_Init(void) { /* USER CODE BEGIN MX_GPIO_Init_1 */ /* USER CODE END MX_GPIO_Init_1 */ /* GPIO Ports Clock Enable */ __HAL_RCC_GPIOA_CLK_ENABLE(); /* USER CODE BEGIN M