STM32CubeMX (MCUs)

Hello,I am now using STM32CubeMX to config STM32G030F6P6, I want to use TIM14 to capture pulse, so I configged to Input Capture direct mode, which is obviously input port, but GPIO setting becomes GPIO output Low. is this a stm32cubeMX bug?please confirm.Thanks@GMA  

I have a project on a H563ZI Nucleo board, and noticed an issue when I enable both the Board Support Package (BSP) options and ThreadX.The MX-generated code in main.c places the BSP initialisation after the call to MX_ThreadX_Init()  - see snippet below.  This means the BSP code is unreachable and the components are not initialised.The workaround is simple (copy the BSP code into the USER CODE 2 section), but it should probably be looked at. Snippet of automatically MX-generated code from main.c: /* USER CODE END 2 */ MX_ThreadX_Init(); /* Initialize leds */BSP_LED_Init(LED_GREEN);BSP_LED_Init(LED_YELLOW);BSP_LED_Init(LED_RED); /* Initialize USER push-button, will be used to trigger an interrupt each time it's pressed.*/BSP_PB_Init(BUTTON_USER, BUTTON_MODE_EXTI); /* Initialize COM1 port (115200, 8 bits (7-bit data + 1 stop bit), no parity */BspCOMInit.BaudRate = 115200;BspCOMInit.WordLength = COM_WORDLENGTH_8B;BspCOMInit.StopBits = COM_STOPBITS_1

Hi,I am using the STM32U5G9VJT6Q and in CubeMX I configured the clock to the full 160MHz for all busses including the core (first screenshot). According to the documentation for 160MHz I need to set 4 Wait States for those speeds and VCORE voltage needs to be in Range 1 (second screenshot).Two questions if someone could please help:1. after setting the clock in MX, where can I check that the wait states have been set correctly (in MX - not programmatically, debug or other ways) ?2. in MX, where do I set the VCORE? If it is set automatically, where can I check that it is set correctly (in MX - not programmatically, debug or other ways)?Thank you :)Ricko   

I am using STM32F7 or STM32H7 to test SDRAM using FMC controller. Initially I could ot se a clock output. Seaching here has got that going. I have tried theSTM32CubeIDE and even set SDRAM bank 2 the same as Bank1 after reading there may be an issue.So far nothing. I stepped through and see a clock being anabled. It is mapped to PG8 on both H7 and F7 but I see not output there. I have tried various HCLK speeds with no joy.I saw a message about needing static void BSP_SDRAM_Initialization_Sequence(SDRAM_HandleTypeDef *hsdram, FMC_SDRAM_CommandTypeDef *Command)but I cannot find a reference to original documentaton so am using it from the github repository.Also what is the 16-bit byte enable, I already have 16bit wide bus enabled. Thanks for help with this... I see it enles extra lines for how it writes but agin I cannot fd documentation about it. just a presentaion saying everything it can do, but not how to do it!What simple thing am I missing? Most other things work through STM32CubeIDE

I'm migrating a project from STM32G431KB to STM32G431CBT6. Both projects were generated using STM32CubeMX and are developed in Keil (MDK ARM), so I only transferred the user code. However when debugging code on the new chip, random breakpoint commands in the disassembly window appear (not the user-defined red dots, but the BKPT mnemonic specifically).It's always first 3 times between _sys_open and _sys_close, then one time between _sys_istty and_sys_seek and another one between _sys_write, _sys_read, then my program runs normally. I tried a full chip wipe, code regeneration, code rebuilds all without any luck. I'm guessing there might be a setting I forgot somewhere that could cause this or a library from CubeMX, but so far I haven't been able to figure out what it could be.The CubeMX software packs I use:Selected features:

Good day all, USBX crashes at line 171 of the file ux_dcd_stm32_initialize_complete.c, as the dcd structure is not initialized at this point. I have tried this on two different MCUs, U575 and H753. In concert, on the H753 the code generator does not generate the call to MX_USBX_Device_Init() and in both cases the call to HAL_PCD_Start() is not generated as well, so this functionality will not work out of the box either. I suppose that I should insert some more calls for initialization, does anyone have idea? Regards,Dmitry

This appears to be loosely related tohttps://community.st.com/t5/stm32cubemx-mcus/warning-during-stm3cubemx-setting-in-usb-host-on-platform/m-p/194919#M8793If I start with Cube IDE:File -> New -> STM32 Project then select NUCLEO-C071RB and then Ux_Host_HID_Standaloneall goes swimmingly well.  However, if I start with CubeMX, then choose the same example I get errors:I can make the Platform Settings error go away by assigning a GPIO to who knows what, per the related post, but I don't want to waste a GPIO and furthermore, I want to make changes to the project that I cannot do using the IDE-only method. Is there some other setting I'm missing in the CubeMX example creation?

I'm using ADC regular and injected channels in STM32G4. I need different oversampling ratio for regular and injected channels, in STM32CubeMX it's possible to configure the oversampling ratio independently for regular and injection channels, but when I took a look at the generated code I saw that the same function has been called for oversampling configuration. It seems like the second function call is overriding the first configuration.Also I've checked on oscilloscope to measure both channels acquisition times. When I'm modifying the parameters of the first function call (which is the oversampling ratio of the regular channels), I see no changes in acquisition time of the regular channels, it's just following the parameters of the second call (injected channels oversampling ratio).I have 2 questions:Why we have configurations for oversampling ratio of both channels in STM32CubeMX, when it's not possible to control them independently?Is there a way to have different ratios other than

Is there a way to prevent CubeMX from constantly messing up the source code formatting?  I spent time setting up the preferences in the CubeIDE tool, but every time CubeMx touches the files, it resets the code formatting.  After the CubeMX returns to the IDE, is there a way to run the IDE source->reformat command?if not possible today, can this be added to the development wish list?thanksMatthew

I would like to use the CAN interface with a CANOPEN library on my STM32F723.As I have found there is a Library for STM chips provided by emotas: https://www.st.com/en/partner-products-and-services/canopen.htmlI have downloaded the Lib on my STM32CubeIDE an now are trying to add it in my CubeMX to the Project: The problem is, it says, its not supporting my MCU. But in the description of the Library it says it should support the F7 chips.Is the library not "free" and I have first to contact emotas or did I forget to install something? Best regards,CO

Hi,I have problem with LTC7106 and STM32G431CBT6.LTC7106 use PMBUS. I never used SMBUS or PMBUS before.I tried to use normal SMBUS implementation and:I can find device (it find 0xC, 0x2A, 0x5A, 0x5B devices. First one is strange but maybe I don’t know something) - the device should have 0x2A address - so I assume that it work properly.I can’t force it to send or receive any data from the device.I tried to do everything as described in: SMBUS/SMBUS_TSENSOR/readme.txt in terms of configuration – but I have no idea what cause the problem.So I have a question – does PMBUS device should be accessible via standard implementation od SMBUS in STM32? I mean should it read and write registers without any problems?To solve the problem I tried to use X-CUBE-SMBUS – I tried to do everything like in: https://community.st.com/t5/stm32-mcus-products/this-is-an-issue-related-to-the-initialization-of-the-x-cube/m-p/751304 and in AN4502But it hang in STACK_SMBUS_Init -> SMBUS_Enable_IRQ -&gt

Hi,I'm trying to configure LevelX using CubeMX.  Does any one know how to link the component driver to LevelX? under file system interfaces, under bsp,The QuadSPI is different from the one listed under bsp, but I included in the project so I can figure out how to write my version.  But I can't seem to figure out how I can define a new driver.  Under LevelX configuration:It says the QSPI component name is MT25TL01G.  How do I change this so I can provide my own driver? 

Dear All,I have created a project where I have placed the APS6408L memory on the HSPI1 peripheral of the STM32U5G9NJH6Q.On CubeMX, I am setting this in the peripheral configuration:And in the memory management tab I see this:I was expecting to see 16MB there.Using this setup my project does not work as the device hard faults when I try to access the second half of the external RAM.Doing this in the configuration:leads to this:And I have tested the code allocating a buffer at the end of the external RAM, playing with it and it works, but I believe that the configuration should be the that of the first image and the result should be that of the second image.Is this an issue of CubeMX?Thanks in advance

Hi,i am using CubeIDE 1.16.1 and if i import the BLE_p2pServer example for NUCLEO-WBA55CG, a few pins (GPIOs for LEDs and buttons) are marked in reset state.Can somebodey explain why they are in reset state and not in GPIO_Input or GPIO_Output?

Hi everyone,I used STM32CubeMX (version 6.11.1) to generate the initialization code for an STM32G491RCT.The toolchain is configured as a Makefile project.At the end of the C_SOURCES definition, it specifies sysmem.c and syscalls.c.# C sources C_SOURCES = \ Core/Src/main.c \ ... Core/Src/sysmem.c \ Core/Src/syscalls.cHowever, those two files were not generated, resulting in the following error:make: *** No rule to make target 'build/sysmem.o', needed by 'build/firmware.elf'. Stop.Is this a bug in STM32CubeMX or am I supposed to implement the functions myself?

I have enable IN1, IN2 and IN5 as ADC inputs. IN1 is called TEMPERATURE. IN2 is called CURRENT and IN5 is called POTENTIOMETER. The DMA is enabled with normal mode and it's called by the Complete Conversion Callback function every time the TIM1 is updated. So, there are also 3 elements in my DMA array. The first element in the DMA array is IN1 and the middle is IN2 and the last one is IN5. In my current situation, IN2 is always zero because there is no voltage at CURRENT (PA1). But sometimes IN1 and IN2 switch position when ADC is sampling data....or DMA switch their place. I don't know. I can see that this occurs sometimes and IN1 gets a zero and IN2 get the same value as IN1 had just before. Thi will occurs once every 15 seconds.Data:Processor: STM32F051R8T6STM32CubeIDE: 1.16.1Firmware: STM32_Cube_FW_F0 V1.11.5Question:How can I take control over the ADC sampling for each element for the DMA? I want to make sure that the ADC scanning the inputs in the correct order and not

Hello,Configuring the I2S on CubeMX on STM32G431, for which I've connected a microphone in PDM, I want a sampling frequency of 48KHz@16bit.Typically, this requires a PDM frequency of 3.072MHz and a decimation of 64.I wonder why I need to tell CubeMX the sampling frequency, since the decimation factor is configured externally to CubeMX (in PDMTOPCM lib).To have a PDM clock  of 3.072MHz, I actually have to select a value of 192KHz for "selected audio frequency" in CubeMX, and not 48KHz.I'm a bit confused... 

hello,I am working on a design using MB1684 with STM32C011 as target. I configured UART2 as half duplex, TX only, so that I could use it for debugging, and I discovered that CubMX generates code which causes the board to hang, because it waits for both TX and RX sides to be ready. It is necessary to manually correct the generated code to have a working board.Below is the generated code and the correction:  static void MX_USART2_UART_Init(void) { /* USER CODE BEGIN USART2_Init 0 */ /* USER CODE END USART2_Init 0 */ LL_USART_InitTypeDef USART_InitStruct = {0}; LL_GPIO_InitTypeDef GPIO_InitStruct = {0}; /* Peripheral clock enable */ LL_APB1_GRP1_EnableClock(LL_APB1_GRP1_PERIPH_USART2); LL_IOP_GRP1_EnableClock(LL_IOP_GRP1_PERIPH_GPIOA); /**USART2 GPIO Configuration PA2 ------> USART2_TX */ GPIO_InitStruct.Pin = DBG_UART_Pin; GPIO_InitStruct.Mode = LL_GPIO_MODE_ALTERNATE; GPIO_InitStruct.Speed = LL_GPIO_SPEED_FREQ_LOW; GPIO_InitStruct.OutputType = LL_GPIO_OU

I used CubeMX 6.12 to generate code and DAC output works as intended.I cloned that project, migrated to CubeMX 6.13 and generated code. DAC output doesn't work. Migration to 6.13 also used FW H5 1.4 instead of 1.3.Comparing stm32h5xx_hal_msp.c I see the 6.13 generated code lacksRCC_PeriphCLKInitTypeDef PeriphClkInitStruct = {0}; if(hdac->Instance==DAC1) { /* USER CODE BEGIN DAC1_MspInit 0 */ /* USER CODE END DAC1_MspInit 0 */ /** Initializes the peripherals clock */ PeriphClkInitStruct.PeriphClockSelection = RCC_PERIPHCLK_DAC; if (HAL_RCCEx_PeriphCLKConfig(&PeriphClkInitStruct) != HAL_OK) { Error_Handler(); } }in HAL_DAC_MspInit(). When I add the above code to stm32h5xx_hal_msp.c in the migrated project, DAC output works as expected.No significant differences between the IOC files.Is there a problem with CubeMX 6.13?Attaching STM32H563VIT6_2.ioc (original, CubeMX 6.12, DAC works) and NGC_HW_Verification_Clone.ioc (cloned, CubeMX 6.13, DAC does

Hi,I am trying to "generate code" using an existing .ioc file. When I click on "generate code" , it is stuck. I am not able to close the window. I had to restart my laptop. I uninstalled and installed again. Tried the same process. But it didn't work. Need help. 

Hi, I'm using the last version of STM32cubeMX. When trying to generate a makefile project for the STM32L073RZ microcontroller. The resulting makefile is wrong. Build target are nonsense: ########################################################################################################################## # File automatically-generated by tool: [projectgenerator] version: [4.5.0-RC5] date: [Mon Feb 24 12:20:46 CET 2025] ########################################################################################################################## # ------------------------------------------------ # Generic Makefile (based on gcc) # # ChangeLog : # 2017-02-10 - Several enhancements + project update mode # 2015-07-22 - first version # ------------------------------------------------ ###################################### # target ###################################### ###################################### # building variables ###################################### # debug bu

If I activate the calibration output 1 of the RTC, CubeMx lags and afterwards marks the options red with "unkown conflict". GPIO does not get assigned or gets cleared if done manually before. Same behavior for 1Hz and 512Hz output. OUT2 works. restarted application and PC, still the sameuC: STM32H7R7L8H6HCubeMX V6.13.0FW versions see below Thanks and regards 

I'm experiencing complete failure in generation of new projects.  Using either CubeMX or CubeIDE it is the same behavior.Generate a new project like I've done for 10+ years, only to find the folder structure missing almost everything required to build a project.Standard structure:This is selecting STM32CubeIDE as the Toolchain / IDE 2025-02-16 22:15:09,802 [INFO] ProjectBuilder:3289 - Time for Copy HAL[1] : 24mS. 2025-02-16 22:15:09,807 [INFO] ProjectBuilder:4876 - Project Generator version: 4.5.0-RC5 [Fatal Error] :-1:-1: Premature end of file. 2025-02-16 22:15:09,868 [ERROR] AbstractXmlFileManage:141 - Premature end of file. 2025-02-16 22:15:09,900 [INFO] ConfigFileManager:1579 - The Die is : DIE482 2025-02-16 22:15:09,905 [INFO] ApiDbMcu:508 - Load IP Config File for FILEX 2025-02-16 22:15:09,909 [INFO] ApiDbMcu:508 - Load IP Config File for LEVELX 2025-02-16 22:15:09,916 [INFO] ApiDbMcu:508 - Load IP Config File for NETXDUO 2025-02-16 22:15:09,919 [INFO] ApiDbMcu:508 - Lo

I am using an stm32F103 and have configured PB4 as a output pin and this works correctly. However when the chip is reset, this pin is automatically pulled high. It appears that this behavior exists because of the pin's dual use as NJTRST. Is there a way I can reconfigure the chip so that this pin will no longer be pulled high when the NRST pin is pulled low?Thanks.

As far as I can tell from the datasheet for the STM32H753VIH, as well as the part selector in CubeMX, the device should have an OctoSPI peripheral.However, when I create a project with the device and go to the connectivity tab, I don't see the OctoSPI peripheral listed like I do in other parts.Is this an issue with CubeMX or does this part not actually have an OctoSPI peripheral in this package?The package is the 100 pin TFBGA with 0.8 mm pitch.Thanks