We are happy to announce that the issue preventing macOS users from generating STM32CubeIDE projects from STM32CubeMX has now been resolved. How to Fix the Issue: Please download the latest STM32CubeMX from st.com Background: A couple of weeks ago, w...
We are pleased to announce to you that the release 6.13.0 of STM32CubeMX is available. What is new in 6.13.0: Added support for the following series, microcontrollers and microprocessors: STM32N6, STM32U3, STM32WL3x, STM32G411xx and STM32C0Added the ...
Are there example MX projects? The IDE has xcellent example projects?
I am using the interfaces octospi1 and octospi2 to interface two qspi-nor flashes.The interfaces are configured the following way:Quad spi (octospi 1 uses low port 1 and octospi 2 uses low port 2)CLK (octospi 1 uses port 1 and octospi 2 uses port 2)N...
version: 1.5.1MCU: STM32F446RETx
Previously I posted that I need MASTER Timer enabled so that the HRTIM1E interrupt would occur in H747.https://community.st.com/s/question/0D53W00000UfL6uSAF/hrtime1-interrupt-not-firingIt turns out that it is similar to G474.The code generated by Cu...
point 1) "DAC_InitStruct.WaveAutoGenerationConfig = __LL_DAC_FORMAT_SAWTOOTHWAVECONFIGPOLARITYRESET_DATASTEP_DATA;" should be " DAC_InitStruct.WaveAutoGenerationConfig = __LL_DAC_FORMAT_SAWTOOTHWAVECONFIG(LL_DAC_SAWTOOTH_POLARITY_DECREMENT, 2000, 10...
This is an everlasting bug of STM32CubeMX since v6.x release. After installing the latest v6.2.1 and trying to open IOC file (STM32H745BI MCU) creaded with previous version v5.x of CubeMX one gets unknown error window shown in the attachment.It does ...
@STM32 MCUs In our project we use USB_CDC. We don't use VBUS, disabled at all places in CubeMX, as far as I can see.Now we want to add an external interrupt on PC0. I have done this.CubeMX generates the following code, already before I added externa...
Edit: I managed to narrow this down and create a reproducible, minimal example.Posted as bug-report here: https://community.st.com/s/question/0D53W000011uLtPSAU/stm32h7-cubemx-critical-codegeneration-bug-rccllIn my opinion the CubeMX generated clock ...
When I enable a peripheral like LTDC - the pins automatically get assigned. I would prefer to assign them manually so that I can have all related signals come out from a single side of the LQFP. How can I do this? Or is this not advised?
there is some code left out of the Cube initialisation that causes this issueplease put this back in...using L432 today, but this issue is a HAL problem.This corrected function fixes this issue. ( thanks to stack overflow)https://stackoverflow.com/qu...
