STM32CubeMX (MCUs)

The motor control workbench seems to only want to use the standalone STM32CUBEMX tool and not the integrated version included with the STM32CUBEIDE.Bottom line, how do I get a motor control workbench out into the new STM32CUBEIDE as a project.I have tried my local official support ST team but they have no idea on motor control development. Dissapointing.

Hi all,I'm using STM32CubeMX 5.3.0 (integrated into STM32CubeIDE):When I save the .ioc and Re-generate code, all the info for Paths and Libraries gets deleted.I must to add again include dirs and external source files each time I change the configuration.This is similar to what is stated here (v 4.26): https://community.st.com/s/question/0D50X00009XkWD5SAN/cubemx-deleted-all-my-custom-includes-and-libraries-but I don't get the code between /* USER CODE */ tags deleted.Thanks.

My home path includes non-english characters. Problem has raised long time ago, when MX updater was creating abracadabra folders in my C:\Users directory with .stm32cubemx  subfolders in it. So I changed repo path in settings to C:\Repo. It worked for some time. But from version 5.0 or 5.1 it also started to show error messages on manual update. MX 5.4 just doesn't want to start after update. Updater log states it cant' find database or something. Clean deinstall/install helped, But updater.ini still contains abracadabra in UpdaterPath=. I think next time I'll get same problems. Could someone from ST make a ticket for MX developers to fix that ugly path-names support? It's 2019 out there and unicode is not a problem in Java.

The first issue is, CubeMX does not generates User labels for Pepipherals for example GPIOs assigned to Cortex-M4 similar to User labels assigned to Cortex-M7. Used IAR toolchain.The second issue is IAR project generated by CubeMX for Cortex-M4, throws The stack pointer for stack 'CSTACK' is outside the stack range. This is broken project generation.

On the first power on, Graphical demo ran. After running GPIO example program provided in the STM32H7 FW package, IAR complains that No STM32 MCU detected. Same issue with the STM32CubeProgrammer tool. Why is this board is difficult to work compare to other ST boards?

I'm trying to get 96kHz/24-bit I2S to work in full-duplex master mode. I select SAI 3A to be master, but "synchronous slave" is grayed out on SAI 3B. Is there something I'm missing in the settings to get it synchronize with sub-block A? I'm using a STM32H745ZI. The changelog says this problem was supposedly fixed in v5.2.0, so I'm not sure why I'm having this problem.

Dear communityWe are pleased to announce the release of STM32CubeMX v5.2.0What is new in STM32CubeMX V5.2.0? • Added the support of new dual-core part numbers in the STM32H7 Series: – Added the support of dual-core configuration, code, and project generation: context assignment (CM4, CM7, both CM4 and CM7 with initializer), Boot0 mode support (both CPUs booting at once), resource manager, and power domains (D1, D2 and D3). – Added the support of new part numbers: STM32H74x and STM32H75x. – Added the support of the PCC feature, examples, and Tj versus Ta calculation for the dual-core devices in the STM32H7 Series. – Added the support of new boards: STM32H747I-DISCO, STM32H747I-DISC1, STM32H745I-DISCO, NUCLEO-H745ZI-Q, NUCLEO-H755ZI-Q, NUCLEOH743ZI2, NUCLEO-H753ZI, STM32H743I-EVAL2, STM32H753I-EVAL2, STM32H747I-EVAL, and STM32H757I-EVAL.• Added the support of new single-core part numbers in the STM32H7 Series: STM32H742x. • Added the support of a new board for the STM32H7 Value Line: STM

To assign pull mode of output pin the function LL_GPIO_SetPinPull writes 0 or 1 to the output buffer (inside the body of LL_GPIO_Init ). Hence if pull-up or pull-down is not necessary (pull parameter equals zero) the output of the pin changes to 0.So the routine should be corrected so that if the pull parameter is not assigned nothing is written to the output buffer. Generally, the pull parameter for output pin type is excess. It should be hiden in CubeMx.

..

The C standard says in 7.1.3 Reserved identifiers:"All identifiers that begin with an underscore and either an uppercase letter or another underscore are always reserved for any use."Yet the code CubeMX generates is full of __HAL... identifiers. Is there a reason for that?Also, the code does not include needed headers. E.g. stm32f4xx_hal.h uses uint32_t without including stdint.h.Are there efforts to improve on this kind of issues?

Dear ST,I had an old project from 2017 with Cube and Keil V5 (its not old for Embedded projects). I wanted to change some things but the result was ****. I had freeRTOS configured but this was disabled,.... big troubles. I had already another thread about this bug. Then I decide to retype both projects with STM32F407VGT6 (STM32F407-Discovery) again and spend more than 8 hours to get both project in the same config as 2 years ago. The result was another lot of bugs (too much for so short time between last changes and now) which I explain:1.) I used Keil V5 and generate the project. Then I click on open project, Keil starts, Then the pack manager opens and asked for update the packs. I dont need the new packs but I update them anyhow. Keil ask for update pack (which was updated through pack manager). I click to reload the pack then I got message that the device is not existent. The Message was "Error: Device not found, Device: ??Device??, Vendor: STMicroelectronis. Please update your dei

Hello,Newbie here, I was trying to import HRTIM_Buck_Sync_Rect found in STM32Cube_FW_G4_V1.1.0\Projects\B-G474E-DPOW1\Examples_MIX\HRTIM\When I import the folder, I would need to generate code first, but will not be able to build.So I go Project Manager >> Code Generator >> Copy only the necessary files (changed from "Add necessary library....").Then generate code and I will be able to build but with errors on using LL functions and insert library and BSP codesI can see that in the HRTIM, the init was done using HAL but inside the HRTIM interrupt and Main funtions, LL was used.Can HAL and LL of the same peripherals use both HAL and LL?How to link the LL library in the project?How to add link to BSP api and codes?I am using STMCudeIDE 1.0.2 on windows 7. I tried on Linux, almost same errors can be seen.

Hi, I just tried to update the firmware of my STM32CubeMX-generated project and regenerated the code. Afterwards my user code in "stm32l4xx_it.c" within "/* USER CODE BEGIN 1 */" and "/* USER CODE END 1 */" was deleted. This is obviously a bug. Is there a fix for it without having to manually insert all the code sections again? Best regardsdcob

..

Posted on June 26, 2018 at 20:50Hello,I am using the STM32CubeMX application version 4.26.0 (see the attached files)There is no option for me to choose 'Copy all used libraries into the project folder'. The radio button was there but it grey out (disable).  Does anyone know how to re-enable the radio button?  Thank you#stm32cubemx.

I have a NUCLEO_F429ZI board, I try to use the MCO2 output 50Mhz clock, but this function doesn't work.Please refer to the attached project, the IDE is TrueStudio and code generator tool is STM32Cube 5.0.0.I'm not sure this is my boards fault or F429ZI doesn't support MCO2 clock output.RegardsSamuel

I have generated code using STM32Cubemx v.5.1 i have selected SDIO and FATFS and i want to use freeRTOS . so as soon as i enable freeRTOS my FATFS stops mounting performing operations. how to get working with both ?? any suggestion ??

Hello ,The Micro Controller Iam Using is STM32h743ZI. an iam using ST link V2 programmer.I have Configured My GPIO pins ,Clock and i have generated the code the code got generated without any errors once the code gets generated i have added the following code for LED Blink.HAL_GPIO_TogglePin(GPIOG, GPIO_PIN_2);  HAL_Delay(500);and i have debugged it iam not getting any errors it is getting debugged perfectly and it shows download and Verified Successfully but My LED is not blinking it is not getting Toggled.i have Attached the code , pin Configuration , Clock Configuration , Setting .kindly Give me a Solution so that it will be very helpfull.Thank you,Muthukumar Ganesan

Hello,somewhere along the work. CubeMX offered me to upgrade to 5.2.1. Then I wanted to continue working with projects, but continue led only to CubeMX doing nothing (just spins the whell with no result).Then I selected to migrate project and then the problems started. I still cannot compile the project, that compiled ok before migration. But that's another story.What is really obvious is that generated project has option MBEDTLS_CONFIG_FILE added twice. Since I'm on embedded system this causes a lot of errors. If I remove those two options manualy, it works, but I have to do this on each generation of the code...Why is CubeMX adding this option by itself? I haven't found any reference to this option in CubeMX project settings (particularly in MBEDTLS part). Thanks in advance,regards,Bulek.

As per the section 5.2.3 of the STM32H747I-DISCO board user manual, the default configuration of the hardware is to use SMPS mode but the default mode generated by STM32CubeMX when you select STM32H747I-DISCO board is LDO. Because of this mismatch, the board is bricked.ST should have used the same power supply configuration in both the hardware board and default CubeMX configuration.

I am using MDK5 (5.22) with STM32CubeMX (4.26.1). I generate blank project within CubeMX for STM32L471ZGTx (144pin MCU). Clock configuration uses internal HSI and LSI and it's set to 16MHz. For testing purposes I configured clocks so all other clocks are 16MHz (SYSCLK, APB1, Timers, Cortex etc...)Under SYS menu I enable TRACE asynchronous SW to use SW for programming and SWO for retargeting printf. I generate project and open it in MDK5 then under RTE editor I set up Compiler->I/O and select all options to ITM. So retargeting of printf goes to ITM. Under options for target I enable TRACE - ITM channel 0. Then I try to use printf in my main function int main(void) { /* Reset of all peripherals, Initializes the Flash interface and the Systick. */ HAL_Init();   /* Configure the system clock */ SystemClock_Config();   /* Initialize all configured peripherals */ MX_GPIO_Init(); printf("Hello world\n");   ...But I get stuck on that command. If I press Stop code execu

Hi,I'm working with the STM32H750VBTx and I switched to the latest FW version package, STM32Cube FW_H7 V1.3.2.CubeMX generated the stm32f7xx_hal_conf.h file and a line was added to this file:#ifdef HAL_EXTI_MODULE_ENABLED #include "stm32f7xx_hal_exti.h" #endif /* HAL_EXTI_MODULE_ENABLED */The EXTI flags are all enabled in the CubeMX.The stm32f7xx_hal_exti.h file does not exist and so a fatal error is generated: stm32h7xx_hal_exti.h: No such file or directoryIs there a new version of FW H7-package?Do you know this problem?

Hi,I bought a STM32H745I-DISCO dev board because STM32CubeMX support was mentioned. However I find that if I choose that board within Board Selector, then later look at Toolchain/IDE options, TrueSTUDIO is greyed out for some reason. Is this a known issue? Is it likely to be fixed soon?In the case of what would be very disappointing news that such support was not likely to arrive soon, would it be feasible for me to manually construct such a project in TrueStudio myself, perhaps reusing files generated for other toolchains? Any guidance of how to set up a dual-core project like this would be most appreciated; I was hoping that STM32CubeMX could take the edge off the learning curve but I've got very little to work with at the moment unfortunately.Thanks in advance,Robert

While I am installing stm32cubemx v5.3 in my PC, and changing the installation path to somewhere in disk D. It is posted that: Invalid directory path. Please enter a directory path that meets the operation system's requirements.Only default intallation path under disk c is OK for installation.However, I do not have enough space in C. I wanna install it in disk D.How can I solve it?BTW, the OS is win10 v1903. I am running the exe file as administrator.

I am trying to use an external 8MHz clock with the STM32L011. I generate the clock using the MCO output on a STM32Nucleo-L476 board, and connect it to a STM32Nucleo-L011 board on its PA0 pi (A0 on the Nucleo's CN4 connector). I used STM32CubeMX to generate the code for the L476 to generate the clock. The clock works fine, providing a very good 3.3 volt, 8 MHz square wave as seen on my 200 MHz oscilloscope. The code for the Nucleo L011 was generated by STM32CubeMX as well. The clock configuration has the HSE clock selected to provide SYSCLK, and the MCO output has SYSCLK selected for output with a divider of 1.The inner "while(1)" loop contains a simple bit toggle with a 1-second period. That works fine as long as the external clock is not connected or the L476 board is in RESET so that its MCO output is disabled. The output frequency on the L011 MCO pin is 2.102 MHz; presumably this is the LSI oscillator providing the clock.However, when the external clock is present on the Nucleo L011