STM32CubeMX (MCUs)

Hello,I'm pretty new to this, but bear with me... Generating configuration code for NUCLEO-H732FX which includes MEMS.  In app_mems.c the generated code appears to attempt initializing the virtual COM out with an incorrectly formed call: /* Initialize Virtual COM Port */ BSP_COM_Init(COM1);returning:Description Resource Path Location Typetoo few arguments to function 'BSP_COM_Init' app_mems.c /first_test/MEMS/App line 168 C/C++ Problemthe declaration in stm32h7xx_nucleo.c seems to confirm the incorrect call:#if (USE_BSP_COM_FEATURE > 0) /** * @brief Configures COM port. * @PAram COM COM port to be configured. * This parameter can be COM1 * @PAram COM_Init Pointer to a UART_HandleTypeDef structure that contains the * configuration information for the specified USART peripheral. * @retval BSP error code */ int32_t BSP_COM_Init(COM_TypeDef COM, COM_InitTypeDef *COM_Init) I suppose I could try editing the generated code, but any other workarounds that don't requir

Scenario: I am using STM32CubeMX (v6.13.0) to generate the necessary project files for a default STM32U5A9J-DK project with ThreadX enabled.  The project files are copied into a docker container and built with cmake.  Building and debugging in the container works until I attempt to add the ThreadX middleware.  Outside of the container building and debugging with STM32CubeIde is not an issue.Problem: The STM32CubeMX generated project files are not sufficient to compile a ThreadX program.  Undefined reference problems flood the output.Debug:1) I have tried combinations of the settings in STM32CubeMX including: "Generate Under Root," "Enable multi-threaded support," and "copy all used libraries into the project folder" to no avail.  My cmake program recursively adds all .h, .c, and .s/.S files as sources or include paths as appropriate in the project folder, so all generated files are always used.2) I attempted to resolve the undefined issues by manually adding th

I can't measure tempsensor with vbat and vref because cubemx generates low layer code in the following order:LL_ADC_REG_SetSequencerRanks(ADC1, LL_ADC_REG_RANK_6, LL_ADC_CHANNEL_TEMPSENSOR); LL_ADC_SetChannelSamplingTime(ADC1, LL_ADC_CHANNEL_TEMPSENSOR, LL_ADC_SAMPLINGTIME_640CYCLES_5); LL_ADC_SetChannelSingleDiff(ADC1, LL_ADC_CHANNEL_TEMPSENSOR, LL_ADC_SINGLE_ENDED); LL_ADC_SetCommonPathInternalCh(__LL_ADC_COMMON_INSTANCE(ADC1), LL_ADC_PATH_INTERNAL_TEMPSENSOR); /** Configure Regular Channel */ LL_ADC_REG_SetSequencerRanks(ADC1, LL_ADC_REG_RANK_7, LL_ADC_CHANNEL_VREFINT); LL_ADC_SetChannelSamplingTime(ADC1, LL_ADC_CHANNEL_VREFINT, LL_ADC_SAMPLINGTIME_640CYCLES_5); LL_ADC_SetChannelSingleDiff(ADC1, LL_ADC_CHANNEL_VREFINT, LL_ADC_SINGLE_ENDED); LL_ADC_SetCommonPathInternalCh(__LL_ADC_COMMON_INSTANCE(ADC1), LL_ADC_PATH_INTERNAL_VREFINT); // Previously enabled tempsensor bit get overwritten here and only internal vrefint channel is enabled.. I took a few hours until I figured ou

Hello, I'm using STM32H503RBT and trying to configure a DMA transfer from memory to the HASH engine, but even though I have that peripheral configured as show on the picture below, I can't assign it as the request source for the DMA is grayed out and when I hover my mouse over it a pop-up appear's saying "IP has to be configured". I tried creating a second project with the same MCU and had the same problem, although interestingly that's not a problem on the CBT variant (48 instead of 64 pin package). Is this a bug or am I doing something wrong? I'm using version 1.17.0 on Windows. 

Hi everyone,I was just wondering how to configure two PWM Channels of TIM1 to generate two phase shifted PWM signals in asymmetric PWM mode as shown in the attachment. I'm using a STM32F303 on a custom board with CubeMX and SW4STM32. According to Reference Manual RM0316 OC1REF1 is triggered by CCR1 and CCR2 as compare values during up- and down-counting and respectively OC1REF2 by CCR3 and CCR4. Theory all good but how on earth do I configure that in CubeMX? When configuring a TIM channel to asymmetric mode I can only set one CCR value. Do channels 2 and 4 have to be set to 'PWM Generation No Output' and Mode:'Asymmetric PWM' to set CCR3 and CCR4 in the CCR register or how does the timer know all the CCR values to work in asymmetric mode? (See attachment).Has anyone succeeded to configure with this nice feature on STM32MCUs so far?cheers

When using Clock Configuration (clock tree) feature it would be niceProposal 1: When selecting dividers or input clock frequency or clicking endpoint of clock output, tool would higlight (e.g. in RED) the whole path (LINES) which the change will affect. Sometimes it is hard to see the path of some change.Proposal 2: In Clock Configuration (clock tree) it would be nice to have search functionality (CRTL + F). It is sometime hard to find some text in clock tree.

Dear ST support team,In STM32CubeMX under the "Project Manager - Advanced Settings" path in the "Generated Function Calls" window user can select to make the generated functions' scope static or external. However, the SystemClock_Config() is always static within the main.c where this function is also generated. This is a bit annoying for all of us who do not use the main() function in the main.c and want to call all the required HAL initializations externally. This issue seems MCU family independent.Another one is the fact that for some MCUs there are issues with linker file generation. The CubeMX-generated linker file is leaving out some linker code. While I'm not seeing this issue on the STM32U535, this remains an issue for the STM32F756. The explanation of the problem and the solution is shown below (answer provided by @grzegorz in the thread https://community.st.com/t5/stm32cubemx-mcus/flash-ld-syntax-error-when-upgrading-to-cubemx-v6-12-1/td-p/722343/page/2) Cu

We are pleased to announce to you that the release 6.13.0 of STM32CubeMX is available. What is new in 6.13.0: Added support for the following series, microcontrollers and microprocessors: STM32N6, STM32U3, STM32WL3x, STM32G411xx and STM32C0 Added the support for the following Nucleo boards: NUCLEO-N657X0-Q, NUCLEO-C051C8, NUCLEO-C092RC, NUCLEO-U385RG-Q, NUCLEO-WL33CC1 and NUCLEO-WL33CC2 Added the support for a new Discovery kits and a new expansion boards: STM32N6570-DK and B-WBA5M-WPAN Extended the implementation of the CMake and Makefile build generators taking into account the memory management tool (MMT) features: Single-core microcontrollers without Arm® TrustZone®(a), excluding STM32H7Rx/7Sx, or with disabled TrustZone® Dual-core microcontrollers without TrustZone® (such as in the STM32H7 series) Add the support of the memory management tool on STM32H7 dual-core and STM32WBA5Mxx microcontrollers Added the compare projects feature to make user able to differentiate b

I have the following big problem:I had installed previously release 6.2.0 of STM32CubeMX and everything works fine. Then i uninstall this release and update to the new one 6.3.0.Now the programm craches after start. An backgroundprocess at windows for java (OpenJDK Platform binary) appears, but that's all. The program/app window doesn't appear anymore. A reinstallation of the older release 6.2.0 doesn't help.The OpenJDK Platform binary process remains as backgroundprocess "forever".I have also tried out what happen when i start STM32CubeProgrammer: backgroundprocess at windows for java (OpenJDK Platform binary) appears also, but after a short while the process becomes an app. The backgroundprocess disappear.I not really know what i should do now...

CubeMx version v6.9.0 deleting my folder structure/ Middleware. I tried to generate code via v6.9.0 and it just deletes my entire middleware files. My all commits are gone.       

I'm using the NUCLEO-H7S3L8 and the max CPU frequency is 600MHz. By default, CubeMX sets VOS is set to 0 (low).But if this were the case, wouldn't it be violating the datasheet where it states 400MHz is the max CPU clock? I've been using 600MHz clock without ever setting VOS high and I haven't gotten any issues, so I'm not sure whether or not it's fine to leave VOS alone.

Why can't I change the Firmware Relative Path when I have unchecked the "Use Default Firmware Location"?I clicked the "Browse" button and there was no response.

Excuse me, what is the reason why I didn't respond when I clicked browse. 

Hi,I am using STM32CubeMX version 6.13.0.I have created my own folders inside Middlewares folder. After each code regeneration, my own folders are deleted automatically. This issue is linked to the previous thread https://community.st.com/t5/stm32cubemx-mcus/cubemx-version-v6-9-0-deleting-my-folder-structure-middleware/td-p/577299 Regards,Hani  

Hi, I have tried to configure the STM32H523RET6 for using USART1 with multiprocessor communication mode and enabled the auto baudrate detection. However, according to the application Note AN4908, the MCU stm32h523 doesn't support auto-baudrate. I don't know why STM32CubeMX has allowed me to enable/disable the auto-baudrate. Either the CubeMX has an error or the application note I am using CubeMX version 6.13.0 Regards,Hani

Hello!I would like to report a bug. Using STM32CubeIDE 1.16.0 and the integrated STM32CubeMX 6.12.0 i encountered a bug regarding OCTOSPI and MDMA on STM32H723ZGT6 MCU. Inside HAL_SPI_Receive_DMA(handle, pdata); where the HAL_MDMA_Start_IT is called the destination and source pointers are/were swapped resulting so the DMA was writing 64 bytes into the DR register which was crashing my application. Swapping these 2 attributes fixed the issue and is now working as intended, below im adding the swapped code where the commented out line is the false one (incorrect one).Thanks for your time. I hpe some ST employee sees this and fixes it but if not at least someone will be aware of the issue when he finds it on google

CubeMX shows the light blue start screen, and stops without any message!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

We are happy to announce that the issue preventing macOS users from generating STM32CubeIDE projects from STM32CubeMX has now been resolved. How to Fix the Issue: Please download the latest STM32CubeMX from st.com Background: A couple of weeks ago, we identified an issue that was affecting macOS users, preventing them from generating code for the STM32CubeIDE toolchain using STM32CubeMX. We appreciate your patience as we worked diligently to resolve this matter. For more details, please refer to our detailed post.

What does a red highlight mean? I am able to select the pin for the function I want but I'm seeing at least two pins with of these red highlights. One is an GPIO output which toggles fine. The other is for an EXTI which no longer generates an interrupt when the signal transitions.   

Hello everyone,I'm sitting over here working on one of my projects and found that STM32CubeMX generated code with an error. My project uses the STM32H7R3L8H6H MCU with Ethernet activated in the connectivity. I have my project set to "generate individual files" because I like it more that way. However, the file "eth.c" contains an error at the beginning of the file: #if defined ( __ICCARM__ ) /*!< IAR Compiler */ #pragma location=0x24020000 ETH_DMADescTypeDef DMARxDscrTab[ETH_RX_DESC_CNT]; /* Ethernet Rx DMA Descriptors */ #pragma location=0x24020080 ETH_DMADescTypeDef DMATxDscrTab[ETH_TX_DESC_CNT]; /* Ethernet Tx DMA Descriptors */ #elif defined ( __CC_ARM ) /* MDK ARM Compiler */ __attribute__((at(0x24020000))) ETH_DMADescTypeDef DMARxDscrTab[ETH_RX_DESC_CNT]; /* Ethernet Rx DMA Descriptors */ __attribute__((at(0x24020080))) ETH_DMADescTypeDef DMATxDscrTab[ETH_TX_DESC_CNT]; /* Ethernet Tx DMA Descriptors */ #elif defined ( __GNUC__ ) || defined ( __ARMCC_VERSION )) /* GNU

I'm setting up Dual Regular Simultaneous mode on my STM32H533RE and I cane across a problem. When the code is gerated, both MX_ADC1_Init() and MX_ADC2_Init() end up with this: /** Configure the ADC multi-mode*/// multimode.Mode = ADC_DUALMODE_REGSIMULT;// multimode.DMAAccessMode = ADC_DMAACCESSMODE_12_10_BITS;// multimode.TwoSamplingDelay = ADC_TWOSAMPLINGDELAY_1CYCLE;// if (HAL_ADCEx_MultiModeConfigChannel(&hadc2, &multimode) != HAL_OK)// {// Error_Handler();// } WhereHAL_ADCEx_MultiModeConfiChannel expects MASTER as the first argument. So when I start up, ADC1 inits fine, but ADC2 fails because it tries to run that above functionwith hadc2 as the master, even though it is a slave, and has a HAL config error. If I comment out the above block on MX_ADC2_Init, all seems to work well.  Is this a bug? Or can I do something different in CubeMX to make this not happen?

I want to manage a uart in reception with a DMA in circular mode using "low level" functions on a STM32U575ZITxQ processor. The initialization of my code is done with STM32CubeMx 6.13.0.In the "Project Manager->Advanced Settings", I chose "LL" for "GPIO", "GPDMA", "TIM" and "USART".In "Sytem Core->GPDMA1" channel1 is configured in circular mode with a "request" = USART1_RX.When I generate the code, the following code is generated for the uart initialization function:Unfortunately, as we can see, the node "Node_GPDMA1_Channel1" is declared local to the function, which makes its effective use impossible (unlike the "HAL" functions which make the node global).For my code to work (and it does), it is necessary that I take the node declaration out of the function and make it global.Of course, I have to repeat this change every time I regenerate the code with STM32CubeMx...Is there something I didn't do correctly, or is this an STM32CubeMx issue? 

I am in the process of transferring from Mbed to VSCode with the STM332 extension. I have set up a project using CubeMX set to the default settings for a NUCLEO-L073 and have no issues. I believe this setup uses the MSI clock. I am trying to implement the HSE with an external 8MHz crystal but cannot get it to work. The program does not run (basic LED blinky) and there is no clock signal on the crystal when monitored with an oscilloscope.The changes I have made from the default NUCLEO-L073 CubeMX settings are:Pinout & Configuration tab: RCC High Speed Clock (HSE) set to Crystal/Ceramic ResonatorClock Configuration tab: System Clock Mux set to HSEI have verified that there is no issue with the hardware - when running from mbed the crystal has a good 8Mhz signal. Are there any other settings I am missing?Is there any other code i need to add on top of the CubeMX generated output?Thanks  

Hello ST Community,    I have a project using the H563. I recently upgraded STM32CubeMX from 6.12.0 to 6.13.0.  After upgrading, and attempting to open the .ioc file, the following message is displayed: Regardless if I choose Continue or Migrate, I get the following error message in STM32CubeMX: If I downgrade STM32CubeMX to 6.12.0, I do not get the migration notification pop-up, and the .ioc file opens as expected.   I was hoping to find out why this is occuring and a resolution to it.  I have attached the STM32CubeMX log (which contains both the attempt at Continue and attempt at Migrate, both of which returns the 'not valid ioc file' error), and the .ioc file used.   Please let me know if additional details or documents are needed. Best regards,-Aaron Wheeler

Hi everyone,I'm new to STM32CubeIDE and working on integrating an ONNX model. I have generated the C code for the model using STM32CUBEMX on the STM32F746NGHx and noticed that the main function includes functions like: MX_X_CUBE_AI_Init(); MX_X_CUBE_AI_Process();However, this differs from the default main function mentioned in the document.   void main_loop() { aiInit(); while (1) { /* 1 - Acquire, pre-process and fill the input buffers */ acquire_and_process_data(in_data); /* 2 - Call inference engine */ aiRun(in_data, out_data); /* 3 - Post-process the predictions */ post_process(out_data); } aiDeinit(); }   I'm unable to find these functions in the generated code. (using the latest versions)I want to:Understand the flow of the generated code, especially how the inputs are processed.Test the model with different inputs.Measure the number of cycles taken for execution with varying inputs.When I build the code, I get an output. STMi