STM32CubeMX (MCUs)

I am configuring to support Stop mode 2 in the stm32_wpan configuration section in the STM32CubeMX.The following lines are generated in stm32_lpm_if.cSYSTEM_DEBUG_SIGNAL_SET(LOW_POWER_STOP2_MODE_ENTER); SYSTEM_DEBUG_SIGNAL_SET(LOW_POWER_STOP2_MODE_ACTIVE); SYSTEM_DEBUG_SIGNAL_SET(LOW_POWER_STOP2_MODE_EXIT);However, the definitions of LOW_POWER_STOP2_MODE_ENTER, LOW_POWER_STOP2_MODE_ACTIVE and LOW_POWER_STOP2_MODE_EXIT don't get generated, which are causing undefined compilation errors.I checked the expected types for these definitions, and see that these should be defined as part of the system_debug_signal_t enum inside debug_signals.h. I have tried looking for additional configurations that might generate the missing definitions but I haven't had any success so far.What should I look into or how can I generate these missing definitions? I could try to manually add these definitions to system_debug_signal_t. but then any time I re-generate with new configurations it

Hi,I am trying to minimise the error between the I2S sampling rate.You can do this pretty well in the STM32F4 because it has an independent I2SPLL (0.02% error between target sampling rate and actual rate is excellent), this is done by changing the PLLI2S N and R values. However, I do not understand why the 48kHz sample rate needs "I2S clocks (MHz)" to be around 49 MHz. Can someone explain that?

Hello!I'm using an STM32u5a9 with a user interface and SMBus enabled battery and charger board.CubeMX does not allow me to include both the X-CUBE-TOUCHGFX and X-CUBE-SMBUS libraries. I'm guessing there is some conflict with the I2C or how the HAL handles it?  if I choose X-CUBE-TOUCHGFX first then try to choose X-CUBE-SMBus, CubeMX reports "This component cannot be selected: this application cannot be selected while the application from pack STMicrolectronics.X-CUBE-Touchgfx is selected": I'm wondering is there a way to get around this and use both libraries? It's my first time working with SMBus but I should also be able to configure an i2c bus separate from the one used for touchgfx to handle the smbus communication just without the HAL. Appreciate anyone's input! Thank you!  

Hello, I would like to know how to install CubeMX and in which directory should I install it so that STM32CubeIDE can recognize it ? Thank you

Hi,I looked everywhere including the MCU Finder App and there does not seem to be any dev kit with DSI display that has a DSI example project that uses CubeMX .IOC configuration.Surely there must be at least one...?Could someone please point me in the right direction. :folded_hands:Thank you :)

Hi all,I encountered a build error while developing a TouchGFX project for the STM32H747-DISCO board. I followed these steps:Steps to Reproduce:Create a TouchGFX Project:Used TouchGFX Environment on Windows to generate an empty STM32H747-DISCO project.Added a background image and an Analog Clock.Set the initial time of the clock to 00:00:00.Clicked "Generate Code".Modify the Project in STM32CubeMX:Opened the project directory.Used STM32CubeMX v6.14.0 to open the CubeMX project file.Added the following peripherals:CM4: RTC, OpenAMP, FreeRTOSCM7: OpenAMPClicked "Generate Code" again.Build in STM32CubeIDE:Opened the project in STM32CubeIDE v1.18.0.Attempted to build the CM7 project.Encountered the following build error:Build Error Output:15:24:38 **** Incremental Build of configuration Debug for project STM32H747I-DISCO_CM7 **** make all arm-none-eabi-g++ -o "STM32H747I-DISCO_CM7.elf" @"objects.list" -l:libtouchgfx-float-abi-hard.a -mcpu=cortex-m7 -T"D:\TouchGFX_Project\STM32H7_RTC_Clock\

Hi,in CubeMX clock configuration, after inputting a desired value into one of the PLL outputs (like in the LTDC Clock box) you can lock it and it turns gray (see screenshot), you can then set another related PLL output (like the DSI) and it should reconfigure the PLL parameters so both outputs are as desired (or at least the second one - the DSI in this example - is as close as possible to the set value).But it does not seem to work like that at all...Once I lock the LTDC, and then change the DSI clock, it does change the locked LTDC clock and by a lot. I can find closer matching values manually by trying a few combinations.Is it a bug in CubeMX?How can I get it to work correctly (fix one value and get CubeMX to calculate the PLL settings of the second when I input it)?Thank you  

Hi AllI have installed STM32 CubeMX on a Mac and I get the following error when trying to generate code:The Eclipse executable launcher was unable to locate its companion shared library.

I just wanted a basic driver with a few API calls to run the VL53L4CX proximity sensor, but I think I got enough code to land a Falcon 9. Attempting to add the X-CUBE-TOF1 middleware with the VL53L4CX sensor to our projects in CubeMX v6.14.0 currently fails.  STM32CubeMX either permanently freezes or generates invalid code and references, even when inserted into a fresh project.  We had to reinstall CubeMX and revert all changes to a prior state to get it unstuck. The base driver files require something like 9 header files just to define the sensor in the user application.  The VL53L4CX driver is too complicated. Are there any simplified documentation resources with stepwise register read and writes?Where is the actual I2C register datasheet to use this sensor? 

I am using hrtim to trigger the adc, but if the regular channel is not triggered with hrtim, it doesn't go into the interrupt of the ADC properly, I checked a lot of information and didn't find a solution, here is my code and cubemx configuration:   NVIC_SetPriority(HRTIM1_TIMC_IRQn, NVIC_EncodePriority(NVIC_GetPriorityGrouping(),0, 0)); NVIC_EnableIRQ(HRTIM1_TIMC_IRQn); NVIC_SetPriority(HRTIM1_FLT_IRQn, NVIC_EncodePriority(NVIC_GetPriorityGrouping(),4, 0)); NVIC_EnableIRQ(HRTIM1_FLT_IRQn); LL_HRTIM_SetSyncInSrc(HRTIM1, LL_HRTIM_SYNCIN_SRC_TIM_EVENT); LL_HRTIM_ConfigDLLCalibration(HRTIM1, LL_HRTIM_DLLCALIBRATION_MODE_CONTINUOUS, LL_HRTIM_DLLCALIBRATION_RATE_3); LL_HRTIM_ConfigADCTrig(HRTIM1, LL_HRTIM_ADCTRIG_2, LL_HRTIM_ADCTRIG_UPDATE_TIMER_D, LL_HRTIM_ADCTRIG_SRC24_TIMDCMP2|LL_HRTIM_ADCTRIG_SRC24_TIMDRST); LL_HRTIM_SetADCPostScaler(HRTIM1, LL_HRTIM_ADCTRIG_2, 0x0); LL_HRTIM_ConfigADCTrig(HRTIM1, LL_HRTIM_ADCTRIG_3, LL_HRTIM_ADCTRIG_UPDATE_TIMER_D, LL_HRTIM_ADCTRIG_SR

I am using the STM32CubeMX to edit pinout configurations for the STM32U595ZJYxQ. Process worked well for the past few days however on Friday the tool appeared to hang after saving the config. The first time this happened the tool closed on its own after several minutes. The next time this happened today, I restarted the laptop. Once the reboot completed, I tried opening the file again but the contents of the file appeared to have changed. The LTIM core assignments were gone as was a SPI chip select GPIO config.  The IOC was backed up by versions so I picked last friday's version and it opened without those issues. Comparing file versions between working and corrupted, I see a 3kbyte size difference (14K corrupted vs 17K working). My experience was on a file that was saved on a corporate NAS behind a VPN. I have since copied that file locally and started only making local updates.  Has anyone else experienced thest types of issues? I am running STM32CubeMX v6.14

Hi, I’m new to STM32. I wanted to set SPI_TX in DMA settings, but I think it has to be configured before using it, as you can see in the picture. I want to give an output for display... can anyone help to solve the problem?  

STM32G030K6T6 - can not configure ADC1_IN16 @ PA12The STM32CubeIDE does not allowed me to enable the ADC1_IN16.The message is "IN16 Disable...Available if sequencer is set to not fully configurable in parameter settings tab"How can I enable it?

It is same error for me with stm32g071cbt6 I just made a new project. And tried to use ADC1_IN16 pin for analog conversion. Still I can not use ADC1_IN16 Do you have a solution?

Hi,When the STM32CubeMX or STM32MCUFinder try to update the database, I receive this error at the final step. I tried many things but all failed. It happens recently. I had not such a problem before.

Does the STM32G491KC have Quad SPI capability? The documentation and product selector tools (on website and within Cube IDE) say that it does have QSPI, but when I try to configure it within the Cube IDE the options is grayed out with the message "Dual Bank mode must be enabled"  

In a project I made with the stm32f072 processor, I am using version 1.16.1 for stm32 CUBE IDE and version 6.12 for Stm32CUBEMX.In this project, I want to define the 2 pins that I defined as interrupt as input. However, after making changes, my code does not work. When I define input and then define the pins as interrupt again without making any code changes, my working code does not work. Is there a problem when updating ioc files?

I'm working on a STM32H755ZIQ.  I am setting up a SPI master, with CPol= 0, CPha = 1, accordingly I need the clock to be low when inactive.  Additionally I want the clock to be low when idling, even when the SPI is not active. To achieve this, I have modified the GPIO settings to use a pulldown resistor on the clock pin.I set this up using the CubeMX utility, but I don't necessarily trust it, so I have checked the generated code, and I find, in main.c, within the function MX_SPI1_Init(void), the polarity is set low:and also, in stm32h7xx_hal_msp.c, within the function HAL_SPI_MspInit(SPI_HandleTypeDef* hspi), the GPIO is set to use the pulldown resistor:And yet, the clock is idling high. You can see in the logic trace below, that the clock is NOT normally pulled down, but only goes low when the SPI is activated.  I assert the CS pin before carrying out an SPI write operation. The clock is still high when the slave detects the CS change, and the slave fails

CubeMX upgrade 6.13 -> 6.14left in linker script following configuration:_estack = ORIGIN(RAM_D1) + LENGTH(RAM_D1); /* end of RAM */MEMORY{/* Start MX regions */DTCMRAM (xrw) : ORIGIN = 0x20000000, LENGTH = 128KFLASH (rx) : ORIGIN = 0x08000000, LENGTH = 2048KRAM_D3 (xrw) : ORIGIN = 0x38000000, LENGTH = 64KITCMRAM (xrw) : ORIGIN = 0x00000000, LENGTH = 64KRAM_D2 (xrw) : ORIGIN = 0x30000000, LENGTH = 288KRAM (xrw) : ORIGIN = 0x24000000, LENGTH = 512K/* End MX regions */RAM_D1 (xrw) : ORIGIN = 0x24000000, LENGTH = 512K}.data :{} >RAM_D1 AT> FLASH.bss :{} >RAM_D1 ._user_heap_stack : {} >RAMduplicated area of RAM and overlapping heap with data

Hello Guys,I am trying to read data via I2C bus using HAL_I2C_Master_Receive_DMA and HAL_I2C_Mem_Read_DMA, but both are not workingIf I use HAL_I2C_Master_Receive it is workingI tried to manually disable and then re-enable DMA channel used by setting enable bit but this doesn't helpIf I add DMA function in addition to HAL_I2C_Master_Receive iw also stoped working except on first use.Also in debugger instruction marker is skipping DMA functionsI tried to add volatile to array definition and to set compilator optimization level to 0, but nothing helpedI tried my simple code in uVision5 and True Studio debuggers and result is the same, DMA functions are not workingCould you help me with this issue and give me some examples of using above functions?

Hi,I am designing a custom board with a STM32F405RGTv being flashed by a FT2232 over the 4-wire JTAG protocol, where the FT2232 chip triggers the STM RESET line as needed.  This circuit has been verified in my previous designs.  However this new board contains a EXTI configuration for pin PA4.  In creating the CubeMX configuration for the board, I added this EXTI configuration and that disabled my 4-wire JTAG configuration.  I attempted to add it back and found it greyed out.  Is there a conflict between running JTAG without the nJRST line and the EXTI4 interupt controller?  Is this related to errata 2.2.7, which although different mentions how one cannot use PB4 as a GPIO when the other 4 wires of JTAG are active?  I want to ensure I can move foward with this EXTI channel before I finalize board design, any help would be much appreciated. TLDR: Do 4-wire JTAG and EXTI4 channel conflict on the STM32F405RG?  If so, can I be pointed to a resou

I tried to validate on desktop... an ai model but ended with this error...please help me with this error

Hi! I'm using an STM32F401RET6 and was planning on using both USART1 in Asynchronous mode and USB_OTG_FS peripherals.In STM32CubeIDE when they are configured at the same time there is an error. I've tried PA9/10 and PB6/7 for TX/RX for USART1 but the same warning/error shows. I wonder if there is some pin configuration interference that it isn't showing or if maybe some interference with the boot modes (Section 3.12 of DS9716).Can I use USART1 and and USB_OTG_FS at the same time? 

Hi, Not sure if this is an issue or if I'm missing something.Shouldn't the processors reset-pin be pinned by default even though it allows for alternative functions?Maybe this is a non issue, but I feel like the reset pin is somewhat critical. 

I just started working with the STM32N6570-DK and tried a simple blink the LED example based on the "How to create an STM32N6 FSBL load and run" article.  I selected the Initialize with default parameters option and without touching any configuration options, I received this warning on Code Generation.  "Main Config: These peripherals still have some not configured or wrong parameter values: [Clock]."  If I cancel the build, I can go back and get the option to run automatic clock issue solver.  The Clock Configuration screen has a complete section in yellow related to PLLs and frequencies to IC1 to IC20 listed individually (partial screenshot attached).  Is this yellow indicating the configuration error or just highlighting something that CubeMX wants to emphasize?  What are these IC1 to IC20 designations represent?  Without doing anything I can exit, and code will be generated without another error.  Trying to run that code results in the Error