STM32CubeMX (MCUs)

I used CubeMX (v5.0.0, H7 pack v1.3.0) to generate some initialization code for the STM32H750, with the CPU core at 200 MHz and the various peripheral clocks at 100MHz.Cube then set the core voltage to PWR_REGULATOR_VOLTAGE_SCALE3 and the flash latency to FLASH_LATENCY_1 in the generated clock initialization function.But looking at Table 12 in the ref manual RM0433 rev 5, it sounds like I need to be set to FLASH_LATENCY_2 for 100 MHz AXI periph clock @ VOS3, or be set to VOS2 or VOS1 for FLASH_LATENCY_1. Is the generated code incorrect?

I can update and install the firmware packages ok and my Windows and AV firewalls list STM32CubeMX as allowed to access the internet. In the updater Settings I get the green tick in the Check Connection button.I've uninstalled the program and re-installed !I've included a few screen shots of my settings.Any Idea's where to go from here ?Regards John

Steps to reproduce:Open STM32CubeMXOpen the MCU Selector to create a new ProjectEnter "STM32L151C8" in the part number searchYou should have something like in the screenshotSee that STM32L151C8Tx has 10 KB of RAMSee that STM32L151C8TxA has 32 KB of RAMCreate project using STM32L151C8TxGo to Help -> Docs and Resources -> DatasheetThe datasheet (DS6876) shows 16 KB of RAM (not 10 KB, not 32 KB, but 16 KB!) Go back, create a project using STM32L151C8TxA Go to Help -> Docs and Resources -> Datasheet That will open the same datasheet (DS6876) which shows 16 KB of RAM (we were expecting 32 KB here)So confusing.I think there are two bugs here.MCU selector should show 16 KB of SRAM for STM32L151C8Tx (instead of 10 KB)STM32L151C8TxA -based project should open the DS9515 datasheet instead of DS6876 from the "Docs and Resources" windowThank you.

This code is Successfully generated under C:/...... but MDK ARM v5.29 project generation have a problem.I have give the right version of Keil also

Hi,The latest version of CubeMX (5.4) fails to create a project with MDK 5.29.I'm using the latest version of Java x64 1_8_0_231I've attached the cube log file, which shows an exception in ToolChainGenerator.Any help most appreciated.Glen.

Code generation is failing when using STM32CubeMX 6.1.0 with a Keil uVision project.  Code generation for a uVision project is working for STM32CubeMX Version 5.3.0, with any uVision version. After STM32CubeMX Version 5.3.0 code generation fails. The log file looks like it can't find the generator: My sytem:Windows 10 Pro (Ver. 20H2, Build 19042.572)Keil uVision V5.29.0.0STM32CubeMX Version 6.1.0I have tried reinstalling different versions of uVision and STM32CubeMX. I have tried changing Java versions.Any ideas? I would really like to use some of the features in the newer version.

I can not use QubeMX to set in the MX_ADC1_Init(void){} function call the following:hadc1.Init.DMAContinuousRequests = is always set to DISABLE,I want this:hadc1.Init.DMAContinuousRequests = ENABLE;but I get this from QubeMX:hadc1.Init.DMAContinuousRequests = DISABLE;

Hello,Has anyone tested the cubemx project generation for STM32H753 eval kit.IDE: AtollicMCU- STM32H753I am trying to generate Ethernet related project with cubemx (Application Structure = Advanced)After hitting the generate code button I have two issue1) In the LWIP folder there are two ethernetif.c files. One is corrupted and other is good. I can exclude the corrupted ethernetif.c files but after generating code two or three times the cubemx application is frozen. I have to kill the application. After restarting the cubemx I again hit the generate code button to find out it is frozen again.2) The ethernet descriptors are not defined in the linker file. This bug has been there for a long time and it is not yet fixed. I have to manually add the sections in linker file every time I generate the code.

I want this:hadc1.Init.ContinuousConvMode = ENABLE;but I get this from QubeMX:hadc1.Init.ContinuousConvMode = DISABLE;

CubeMx complains that a 64 bit Java is needed with it. I have 32bit Windows 7 here, so 64 bit Java doesn't run in it. What kind of problems should I expect? I have problems with HW SPI.Upgrading 32 bit Windows gives 32 bit Win 10 and installing 64 bit Win 10 requires quite a lot of work, because I want to keep this W7 system also.

It seems that windows 10 version 2004 (build 19041.388) affects somehow the keil project file generation. It fails with the error: "The code is succesfully generated but MDK-ARM v5 project generation have a problem".Question is: Where is the problem ?I tried to generate in different locations e.g. C:\ , C:\Users\myuser\ but it did not worked for meLast try was on Windows version 1809 (build 17763.1294) and it worked perfecly Java version (non working)C:\Users\psany>java -versionjava version "1.8.0_261"Java(TM) SE Runtime Environment (build 1.8.0_261-b12)Java HotSpot(TM) Client VM (build 25.261-b12, mixed mode)Java version (working)openjdk version "1.8.0_252"OpenJDK Runtime Environment (Zulu 8.46.0.20-SA-win64) (build 1.8.0_252-b14)OpenJDK 64-Bit Server VM (Zulu 8.46.0.20-SA-win64) (build 25.252-b14, mixed mode)RegardsSandor

I've used earlier versions of CubeMX without this kind of problem. I've generated a project for STM32H745 which delivers a project package (makefile project) without error messages. When I try to compile the project (with no source modification other than the problem in Makefile which I describe below), many device symbols can't be found. An example would be the SPI device handle, yet stm32h7xx_hal_conf has the correct header files uncommented.One thing I noticed right away is that the Makefile has 2 copies of the source code list which causes an early failure. When the extra copy is removed, the process goes farther, but dies with undefined symbols that ought to be defined by the header files.EDIT ADD: I should have said that this is a dual core device and the project is also supposed to support both cores - I see subdirectories for CM4 and CM7 which makes sense. I've looked at the error messages and (naively) added #include statements to the files mentioned in the error messages. Thi

Hi, I'm seo. when i use STM32CubeMX(5.3.0) USART2 doesn't work.I attached ioc file. other uarts works well.I debugged MX_USART2_UART_Init(), but the source code looks like well.Could you give a sample ioc file for nucleo-l476rg which working USART2?Thank you.

Hi,ALLI have generated project with CubeMX 6.0.1. It contains FreeRTOS.The chip is STM32L4S7ZITWhen breakpoint is hit i see that after 10 seconds (approximately) the program is executed further. Although breakpoint is still active. It is placed in one task.Is it possible to fix this problem?After i step further i step into interrupt from timer17 (it is a clock base). It is normal.But why the whole system is executed?Thanks

Install stm32cubemx and display the message "STM32CubeMX Installer"This application requires a Java Runtime Environment 1.8.0_45 (64-bit)' "Why did the installation fail?

Hi!I have to report a bug. I cannot analyze the neural network in STM32CubeMX 1.3.0. I don't use 1.4.0 because they won't work with FreeRTOS.How to repeat this issue:Start a new Project.Select STM32 F446RE Nucleo boardUse CubeMX AI 5.1.0Download Mobilenet_V1_0.25_128_quant from https://www.tensorflow.org/lite/guide/hosted_models Download keras_cifar10_trained_model_100_epochs.h5 from https://github.com/ABurrello/CubeMX-AI-demo/tree/master/saved_modelsDownload mobilenetv2-7.onnx from https://github.com/onnx/models/tree/master/vision/classification/mobilenet/modelAs you can see, the mobilenetv2-7.onnx is the only file that can be analyzed with.Thank you.Operative system: Lubuntu Linux 20.04Installation file: Generic LinuxIDE: STM32 CubeMX IDE 1.3.0AI: CubeMX AI 5.1.0

Hello,I have previously complained about the issues in the latest version of STM32Cube firmware for F7 microprocessors:https://community.st.com/s/question/0D53W000007YhLNSA0/a-bug-in-the-latest-version-of-stmcubemx-561I am not sure whether these observations were taken into consideration by the STM32 staff. I want to show a MWE to illustrate the current issues, that I believe originate form the changes in SystemInit() (as I've mentioned in my previous thread).This MWE runs on the STM32F769I-EVAL board. In general it is applicable to any F7 with the latest STM32Cube firmware. What I essentially want to do is to setup the system clock to 100 MHz (using the HSI as the source for simplicity's sake) and to display the PLL output on PA8. To do so, the following steps need to be undertaken in STMCubeMX:Setup the system clock:Enable the MCO1 output:Set PA8 to PPLLCLK:Set PA8 GPIO speed to very high:This bare-bones project works just fine for STM32Cube_FW_F7_V1.15.0 (or older). An expected 100

Hello @Khouloud ZEMMELI​ ,I install STM32CubeMX to folder C:\STM32CubeMX and then set REPOSITORY FOLDER TO C:\STM32CubeMX\Repository as I want to keep the STM32CubeMX and its dependencies at one place.I have reported earlier this issue either on the STM32CubeH7 (GitHub page) or maybe on ST forums, but never got to know of a fix for the issue:STM32CubeMX installation resulting in deleting all sub folders including Repository when it starts the uninstallation process for old version.Steps for reproducing this issue:STM32CubeMX version 6.0.1 installed at location C:\STM32CubeMXOpen the STM32CubeMX. Press ALT+S and change Repository Folder to C:\STM32CubeMX\Repository and click OKPress ALT+U and under description STM32H7 select checkbox for STM32Cube MCU Package for STM32H7 Series (Size: 1079 MB) (with available version 1.8.0) and click on Install Now button. Once the installation is complete follow next steps.Press ALT+C. Press Refresh button on the popped up Check update Manager Pop

Hello everyone. I'm trying to setup ADC in my STM32F107, configuring it with CubeMX (ver. 5.4.0, MCU package 1.8.0), but, I fell into issue. Multiple issues, actually, but I should start with just one now, I guess.I notice odd behaviour, while I'm trying to configure my ADC to work with DMA:At one time after the start, first byte of destination buffer gets filled with a value. This byte (lets consider it's address 0x20000100) never gets overwriten, and no nearby (e.g. 0x200000FF or 0x20000101 and so on).Sometime after this byte set, program goes to DMA1_Channel1_IRQHandler. The call for this function heppend two times only, during whole program run (Half and Full Buffer interrupts, I guess).I've suggested, that that's might be because ADC has stopped, but ADC1->DR keeps changing.There's no more changes in the CubeMX generated code, than HAL_ADC_Start_DMA(&hadc1, (uint32_t*)adc_buf, ADC_BUF_LEN) added in to USER CODE 2 brackets.Any advice, what could it be, and what should I

Hello @ASELSTM , @Khouloud ZEMMELI​  ,To observe the below reported issue it is mandatory that macro configASSERT_DEFINED == 1The issue is observed inside the function void vPortValidateInterruptPriority( void )which is available with FreeRTOS file GCC\ARM_CM4\port.cI am observing two ASSERTS / concerns in the file (triggered as a result of Reading from or Writing to a Queue from ISR):First Issue:Is observed for configASSERT( ucCurrentPriority >= ucMaxSysCallPriority );when variable uwTickPrio = TICK_INT_PRIORITY (either assigned directly or with help of variable TickPriority), where macro TICK_INT_PRIORITY is assigned a value of 0.If I do not use a software interrupt to process the Queue, then because of uwTickPrio value (i.e. 0) being used as priority for FreeRTOS Timer (i.e. Timer 2), the ASSERT gets raised.If I use the software interrupt, then I observe the second issue stated belowSecond issue:Is observed for configASS

Dear experts,I am using STM32H750 vbt6 in my project .Recently I decided to use MCO1 to produce clocks for other devices attached to this chip .Also, I am using STM32cube IDE for working .It seems that setting the right parameters for MCO1 to work properly, is an easy task (by using CubeMX).(The input of source multiplexer of MCO1 is: HSE or PLL1Q and the output frequency of this MCO1 pin will be between 28MHz to 35 MHz.)Here are my questions:1-Are there any HW or SW recommendations for me to make this MCO pin work properly? 2-Does this pin produce "square wave form clock pulses"?Your consideration is highly appreciated.Regards,HT.

I've tried multiple versions and searched the form. After generating a .IOC i cannot generate code because cubeIDE cannot handle downloading and installing new firmware on its own. Why has this issue been known about for over a year and from what i see on the forum nothing has been done to correct it. I had this working previously with version 1.8.0 for STM32F10X. Because of the new update to 1.8.3 i cannot do anything! this is beyond frustrating since i migrated to the STM32 platform specifically for the improved toolchain. I am seriously considering switching to ARM and being done with this. I have manually tried to install the 1.8.0 and 1.8.3 packages, by downloading them from the web and point cubeIDE to the zip and that fails too. I even uninstalled cubeIDE because i was at version 1.3.0 and reinstalled to 1.4 and still nothing. really considering dropping STM32 from current and future developments.

I am using STM32F412CGU6 MCU.I want to configure USART1 as Half Duplex mode (Single wire mode) with TX only and below configurations:Baud-rate = 115200Start bits = 1Parity = evenData bits = 7Flow control = offStop bits = 1But in STM CUBEMX , "Start bits" can not be set/configured. Check attached snapshot for reference.Can you please suggest the way/ code changes for configuring the USART1 with above settings? 

I am on a project that I generated with CubeMX 4.25.0.RC2 for STM32F303VCT6 and it worked perfectley until I regenerated the code with CubeMX 5.6.1-RC1.First found that USART DMA doesn't work. I found some differences in generated stm32f3xx_hal_uart and stm32f3xx_hal_uart_ex files.I used the same code for the old and then new version expecting it would work as it did before. MX_USART1_UART_Init();   ...   HAL_DMA_Start(&hdma_usart1_rx, (uint32_t)&huart1.Instance->RDR, (uint32_t)USART_PCReceiveBuffer, sizeof(USART_PCReceiveBuffer)); HAL_UART_Receive_DMA(&huart1, USART_PCReceiveBuffer, sizeof(USART_PCReceiveBuffer));You can see the different results right after this code in huart1 in the attached images. Is there anything I should change to use UART DMA and CubeMX5 ?B.R. Peter