STM32CubeMX (MCUs)

Hi,Id need to measure the frequency of an input signal using TIM4. My device is a STM32L475RCT and to do this I've used the TIM_InputCapture example from CubeIDE. In my application TIM1 is not available.The problem is for the TIM4 I'm not able to set the Input Capture Interrupt from NVIC Interrupt table. How can I do this? I've also observed the TIM17 is available and I think this timer can be linked to TIM1 somehow. The Input Capture Interrupt for TIM1 is feasible.Any idea?regards,gaston

My board has ethernet PHY Micrel KSZ8721.I use STM32F407, RMII, LWIP, noRTOS.CubeMX 6.7, STM32Lib 1.27.1Although this is no exotic PHY, it is not listed in the supported BSP PHY as LAN8742 and DP83848.How can I write a mock driver so that custom calls to support the PHY are integrated into the auto-generated LWIP.c functions.I see some potential problems in the current CubeMX setup:1) PHY must be setup in Ethernet AND LwIP tab. As the single responsibility theory says: one should setup only in 1(one) place.2) If USER_PHY is selected , then USER_PHX calls should be generated, and not omitted as now.3) USER_PHY creates warning, but it should be an accepted solution ...Thanks, Adib.

Hi,after upgrading the whole suite to last release (as 09-jul-2024), code generation breaks code in function MX_FLASH_Init (main.c file).If without condition is generated at line 19, no indentation on following block (which closes at line 53)./** * @brief FLASH Initialization Function * @PAram None * @retval None */ static void MX_FLASH_Init(void) { /* USER CODE BEGIN FLASH_Init 0 */ /* USER CODE END FLASH_Init 0 */ FLASH_OBProgramInitTypeDef pOBInit = {0}; /* USER CODE BEGIN FLASH_Init 1 */ /* USER CODE END FLASH_Init 1 */ HAL_FLASHEx_OBGetConfig(&pOBInit); if () { if (HAL_FLASH_Unlock() != HAL_OK) { Error_Handler(); } /* Option Bytes settings */ if (HAL_FLASH_OB_Unlock() != HAL_OK) { Error_Handler(); } pOBInit.OptionType = OPTIONBYTE_USER|OPTIONBYTE_BOOTADDR; pOBInit.USERType = OB_USER_BOR_LEV; pOBInit.USERConfig = OB_BOR_LEVEL_4; pOBInit.BootAddrConfig = OB_BOOTADDR_NS0; pOBInit.BootAddr = 0x08000000; if (HAL_FLASHEx_OBProgram(&pOBInit) != H

I've been using the recently added CMake generation feature of cubemx, as of now it creates an INTERFACE library for both project related and drivers related sources, the problem is that those sources get propagated for every external library that needs stm32cube drivers.One workaround is creating a STATIC wrapper library like this:# Retrieve properties from the INTERFACE library generated by STM32CubeMXget_target_property(STM32_SOURCES stm32cubemx INTERFACE_SOURCES)get_target_property(STM32_INCLUDE_DIRS stm32cubemx INTERFACE_INCLUDE_DIRECTORIES)get_target_property(STM32_COMPILE_DEFINITIONS stm32cubemx INTERFACE_COMPILE_DEFINITIONS)get_target_property(STM32_LINK_DIRECTORIES stm32cubemx INTERFACE_LINK_DIRECTORIES)get_target_property(STM32_LINK_LIBRARIES stm32cubemx INTERFACE_LINK_LIBRARIES)# Log the propertiesmessage(STATUS "STM32_SOURCES: ${STM32_SOURCES}")message(STATUS "STM32_INCLUDE_DIRS: ${STM32_INCLUDE_DIRS}")message(STATUS "STM32_COMPILE_DEFINITIONS: ${STM32_COMPILE_DEFINITIONS}"

Hi there;I'm extremely new to the world of ST, and trying to get my feet under me with it, coming from a few years' experience developing for esp32 microcontrollers using the esp-idf framework. I have an Adafruit stm32f405 feather; I understand this isn't the same as a proper ST development board, but I am trying to learn with it nevertheless. The board has an onboard neopixel - out of the box, the board can be plugged into USB and the neopixel begins cycling through colors. I *think* it comes configured with circuitPython, but I am interested in getting it working using ST's tools and workflows, and so I'm trying to figure out how to get that neopixel working in cubeIDE. Studying the schematic, I can see the neopixel is connected via pin PC0. This is where I'm getting a bit lost - I *think* what I need to do is configure PWM using some timer settings somewhere (?), then connect this pin PC0 to that timer/pwm generator. But it's not clear to me how to do this in the cube

Hi there!Opening an H7.ioc file FW_H7 V1.11.1 in CubeMX 6.11.1 containing a LWIP secition and upgrade to FW_H7 V1.11.2 removes LWIP section.Cheers!open the attached .ioc file in CubeMX 6.11.1migrate to FW version FW_H7 V1.11.2do not change anything and save the .ioc fileobserve missing LWIP secition in .ioc fileobserve the missing / not found LWIP files in CubeIDEpre uppgrade FW_H7 V1.11.1post upgrade FW_H7 V1.11.2LWIP is not availabe for single core (M7 / M4)delta of .ioc 

For my project I'm using an STM32L476 MCU with CubeIDE 1.15.1 and CubeMX 6.11.1In this project I'm using ThreadX / Azure RTOS.For a new feature I doubled the speed of the MSI, which doubles the system clock, but the HCLK stays the same (by changing the prescaler).Now when I click regenerate code in CubeMX, the values for the systick are doubled in the tx_initialize_low_level.sSo as an overview Old valueNew valueMSI1 MHz2 MHzSysClk1 MHz2 MHzHClk1 MHz1 MHzSYSTEM_CLOCK var in tx_initialize_low_level.s1 MHz2 MHzThe SYSTEM_CLOCK var in tx_initialize_low_level.s is used to configure the SysTick.To me this looks like a bug in the generator as the System clock does not affect the SysTick (the HClk does)?

Hello,For some reason, I'm not able to enable LWIP on CubeMX 6.11.1, it looks grayed out. I have enabled ETH in RMII mode and CPU DCache.However, if I enable both Cortex M7 and M4, then I'm able to enable LWIP. Is this the expected behavior?

im using stm32h743zi2 nucleo board . im triyng to do programming in ethernet with udp without freeRTOS . using firmware version of 1.10.0 but it is not pinging .  anybody  did programming with this FW  . please let me know the reasons for not ping.or send me the working code for ping. thanks

..

Hi, is any possibility to protect editing code generated with in STM32Cube. I sometimes made some mistake and change the generated code. It would by good, if it is in STMCube some toggle button, that I can enable disable editing the the code generated with STMCube. The user code would be editable every time. The best solution would be if the not editable text code will be sad or grey.

Hello,in CubeIDE (MX) RS485-direction switching is only selectable for UART4 and UART5 (by hardware, not by SW-GPIO). According to user manual, it should be possible for all UARTs/USARTs (Pin DE/RTS). Is this feature missing in CubeIDE or is this hardware-feature only available for UART4/5 (manual is incorrect)? RegardsSteffen

Hi all,I recently updated to the latest STM32CubeMX version 6.12 in order to take advantage of the ability for CubeMX to generate a CMake project for a dual-core MCU (specifically for the STM32H7 family). However, I'm a little confused on the implementation of this feature, specifically with how it compares to the CMake projects generated for single-core MCUs.Could anyone help me understand why the CMake project is now generate as PRIVATE, in a separate mx-generated.cmake file, rather than as an INTERFACE library as it was with single-core projects? Having the code generated in this way allowed me to use the generated CMakeLists file (the one with all of the HAL driver source files and include paths, I think it's typically located at [cubeMX project location]/cmake/stm32cubemx) as a way to easily add the HAL driver for a given micro to my app, and I was able to build the same app targeting multiple different micros thanks to this.Ultimately, my issue is with how the CMake project gener

HI Forum,I am configuring my USART as a synchronous slave receive only, the cube software configures clock, receive and transmit GPIO and I cannot remove the transmit GPIO configuration in the GUI without it removing the entire peripheral.  Is their a way to configure this properly.  I can configure the USART with clock and receive manually and the and use the TX pin for some other GPIO in code without a problem. When receive or transmit only is selected from the data direction option the corresponding unused pin should become free.

We are using MIPI-DSI on a STM32U5G9NJ.First bug: There are 2 pins missing in the Pinout View: D4 and J9. Both are VDD11 pins. Second bug:After Enabling LTDC and DSI in STM32CubeMX I can't select "Active High" for "Data Enable Polarity" in LTDC -> Parameter settings. To reproduce:* Create project with STM32U5G9NJ (or a different STM32U5G9 package)* Enable HSE (System Core -> RCC -> HSE)* Enable LTDC (with a DSI setting; which one doesn't matter)* Now I'm able to choose "Active High" for "Data Enable Polarity"* Enable DSI (mode doesn't matter)* Now I can only select "Active Low" for "Data Enable Polarity" (if "Active High" was selected previously, LTDC displays an error telling me to select something different)We use a display where we need DE polarity "Active high". So we can see that this setting is applied and making a huge difference when changing it manually in the source code.

 The documentation from Eclipse ThreadX states you must call context save/restore assembly routines for ISRs when using ThreadX calls (e.g. tx_thread_resume) in the ISR.    https://github.com/eclipse-threadx/rtos-docs/blob/71a7c00f369b9cd648f73dfddb0d5ca6d5a1b855/rtos-docs/threadx/chapter3.md#isr-template In our MX generated code, the EXTI9_5_IRQHandler is a C function, its doesn't have the ThreadX calls to save/restore.  _tx_thread_context_save_tx_thread_context_restore 

I just configured an MCU using the latest configurator, in STM32CubeIDE V1.16.0. Set up a bunch of GPIOs no problem, gave them useful names.One pin though wouldn't let me: each time I entered the desired nae ("5V_ENA") I'd get "The label '*' on pin '*' should start with a character or an underscore"If I started it with an underscore, it was ok, but 5V_ENA was rejected. What did I miss? [UPDATE] A number ('5') is not considered a character apparently. "ENA_5V" was ok. Solved, leaving here for reference.

I am trying to generate code using CubeMX (version 6.11.1), using the NUCLEO-H563ZI board to start the project. But, I am getting the following pop-up when trying to use the USART3 peripheral which seems to be unavailable:Because of this, I had to downgrade the version of CubeMX to 6.10.0 to use USART3. However, I observed that even after saving the ioc file, later when we opened the file again CubeMX had overwritten the pins to the default state.Why is this happening and is there any workaround for it?

I'm using cubemx for stm32f401.I have to address several SPI devices using a sing spi bus, and different chip selects.Each SPI device requires a different configuration of CPOL/CPHA.So when the bus is idle (when all the chip selects are high) I use HAL_SPI_Init () to change the settings SPI settings accordingly. This works fine with the exception of the initial idle clock level.Apparantly the SPI controller does not set SCK to the correct idle value until after the first message is sent.The reference manual (RM0368 Rev 5) states on page 564 that:The idle state of SCK must correspond to the polarity selected in the SPI_CR1 register (by pulling up SCK if CPOL=1 or pulling down SCK if CPOL=0) It seems that this isn't implemented in the HAL SPI driver?

 "I am using your program and made some changes, but when I use it in the function  HAL_DAC_Start_DMA(&hdac, DAC_CHANNEL_1, (uint32_t*)value, 89, DAC_ALIGN_12B_R); HAL_TIM_Base_Start(&htim4); the signal result on the oscilloscope is not continuous. What I mean is, when I use a very long array, the result does not match what I expected. To help you understand, I am attaching two photos comparing the result I want and the result from the program. I have a signal result like the one on the left, but I want it to be like the one on the right. After investigating, it turns out that the length value in HAL_DAC_Start_DMA was manually changed. If it can be done automatically, please give suggestions so I don't have to set it manually.program to check uint16_t hold_samples = 50; uint16_t firstHalf[64] = { 2100, 2149, 2250, 2350, 2450, 2549, 2646, 2742, 2837, 2929, 3020, 3108, 3193, 3275, 3355, 3431, 3504, 3574, 3639, 3701, 3759, 3812, 3861, 3906, 3946, 398

My platform is Windows 11. I had to run STM32CubeMX in a command-line mode. According to the video tutorial and UM1718:jre\bin\java -jar STM32CubeMX.exe -iruns STM32CubeMX in interactive command-line mode.It took me a long time to find out that it works only if I append a Project.ioc. Otherwise, the cursor is not in the desired MX> position. My apologies if this happens only in my case. If it is common, I expect ST to exhibit more maturity in providing documentation.

FreeRtos V2 generates errors in compiler version 6. May I ask when this problem can be solved? Currently, this problem can be solved by porting the portmacro.h and port.c files, but you need to report each time you update the package version. Very troublesome

I am trying to use stm32f407 and w25q128 to get a usb drive, for this I wrote a driver to control the flash drive and initialized the USB MSC using CubeMX. When I connect the stm32 to the PC (Ubuntu) I see the new storage device in the Disks app but it doesn't mount, I tried to erase it but the process freezes until I reboot the boardw251128 has:PageSize = 256SectorSize = 4096SectorCount = 4096PageCount = 65536BlockSize = 65536CapacityInKiloByte = 16MbBased on this information, I set the defines in `usbd_storage_if.c`:```#define STORAGE_LUN_NBR 1#define STORAGE_BLK_NBR 0x1000#define STORAGE_BLK_SIZ 0x1000int8_t STORAGE_Read_FS(uint8_t lun, uint8_t *buf, uint32_t blk_addr, uint16_t blk_len){w25q_readSector(buf, blk_addr, 0, blk_len * 4096); // 0 is offsetreturn USBD_OK;}int8_t STORAGE_Write_FS(uint8_t lun, uint8_t *buf, uint32_t blk_addr, uint16_t blk_len){w25q_eraseBlock(blk_addr);w25q_writeBlock(buf, blk_addr, 0, blk_len * 4096);return USBD_OK;}```I added some printfs inside these met

Hi guysI want to generate a time base by a general purpose timer interrupt (TIM6) on a F334 with low level library. I do not know why, I get init functions fine but no interrupt request handler is generated, nowhere.It should be very simple, I thought, but I did nothing with STM32 for a longer time. I remember to did this (and more...) with old HAL library years ago, but even though if I select HAL in advanced settigs, I get nothing better. I use the last firmware package version (CubeMX says its version 1.11.5) and tried many things before, including that here:https://community.st.com/t5/stm32cubemx-mcus/how-to-generate-callback-functions-in-stm32cubemx/td-p/130320So I come up here, maybe someone else know what is going wrong here? I attach the cubemx file, maybe somebody can ivestigate what I've forgotten?