AnsweredAssumed Answered

STM32CubeMX 4.2.0 Known Issues

Question asked by denehan.joe on Jun 11, 2014
Latest reply on Jun 17, 2014 by greiman.william
I'm just wondering if there could be a single thread where all the known bugs with the latest version of CubeMX can be listed. Maybe a sticky? (admins).

Hopefully then they would be fixed in next release so we don't have to wait for another update cycle to get fixes that have already been reported.

I know the delay bug linked below wasn't fixed in the last release even though it had been reported.

Delay
=====
[DEAD LINK /public/STe2ecommunities/mcu/Lists/cortex_mx_stm32/Flat.aspx?RootFolder=/public/STe2ecommunities/mcu/Lists/cortex_mx_stm32/%5bbug%20report%5d%20Bug%20in%20HAL%20%28SPL%29%20delay%20function&FolderCTID=0x01200200770978C69A1141439FE559EB459D7580009C4E14902C3CDE46A77F0FFD06506F5B&currentviews=180]https://my.st.com/public/STe2ecommunities/mcu/Lists/cortex_mx_stm32/Flat.aspx?RootFolder=/public/STe2ecommunities/mcu/Lists/cortex_mx_stm32/%5bbug%20report%5d%20Bug%20in%20HAL%20%28SPL%29%20delay%20function&FolderCTID=0x01200200770978C69A1141439FE559EB459D7580009C4E14902C3CDE46A77F0FFD06506F5B¤tviews=180

FIXED IN MX_V4.3.0_FW_V1.2.0

SDIO
====
[DEAD LINK /public/STe2ecommunities/mcu/Lists/cortex_mx_stm32/Flat.aspx?RootFolder=/public/STe2ecommunities/mcu/Lists/cortex_mx_stm32/STM32Cube%20%2B%20F4-Discovery%20%2B%20FatFS&FolderCTID=0x01200200770978C69A1141439FE559EB459D7580009C4E14902C3CDE46A77F0FFD06506F5B&currentviews=153]https://my.st.com/public/STe2ecommunities/mcu/Lists/cortex_mx_stm32/Flat.aspx?RootFolder=%2Fpublic%2FSTe2ecommunities%2Fmcu%2FLists%2Fcortex_mx_stm32%2FSTM32Cube%20%2B%20F4-Discovery%20%2B%20FatFS&FolderCTID=0x01200200770978C69A1141439FE559EB459D7580009C4E14902C3CDE46A77F0FFD06506F5B¤tviews=153

Fixed in MX4.3 FW1.2.0 ( Note: DMA not tested, only non-DMA )

ADC1
====
[DEAD LINK /public/STe2ecommunities/mcu/Lists/STM32Java/Flat.aspx?RootFolder=/public/STe2ecommunities/mcu/Lists/STM32Java/STM32CubeMX%20-%20BUG%20report%20%20bug%20in%20ADC%20injected%20channels%20and%20bad%20code%20generation&FolderCTID=0x01200200770978C69A1141439FE559EB459D758000F9A0E3A95BA69146A17C2E80209ADC21&TopicsView=https%3a//my.st.com/public/STe2ecommunities/mcu/Lists/STM32Java/AllItems.aspx&currentviews=22]https://my.st.com/public/STe2ecommunities/mcu/Lists/STM32Java/Flat.aspx?RootFolder=%2fpublic%2fSTe2ecommunities%2fmcu%2fLists%2fSTM32Java%2fSTM32CubeMX%20-%20BUG%20report%20%20bug%20in%20ADC%20injected%20channels%20and%20bad%20code%20generation&FolderCTID=0x01200200770978C69A1141439FE559EB459D758000F9A0E3A95BA69146A17C2E80209ADC21&TopicsView=https%3A%2F%2Fmy%2Est%2Ecom%2Fpublic%2FSTe2ecommunities%2Fmcu%2FLists%2FSTM32Java%2FAllItems%2Easpx¤tviews=22

Reported as fixed by STM32Cube-T in MX4.3
       
Reported by Stivy as only partially fixed. ( see thread )

ADC1 ( greiman.william )
==============
                                   
           
Initialization of ADC1 for STM32F401RE fails because multimode.DMAAccessMode is not set in in main.c function MX_ADC1_Init().

            This causes assert_param() to fail in HAL_ADCEx_MultiModeConfigChannel().
           

GPIO.C
====
[DEAD LINK /public/STe2ecommunities/mcu/Lists/STM32Java/Flat.aspx?RootFolder=/public/STe2ecommunities/mcu/Lists/STM32Java/STM32Cube%20file%20generation%20problem&FolderCTID=0x01200200770978C69A1141439FE559EB459D758000F9A0E3A95BA69146A17C2E80209ADC21&TopicsView=https%3a//my.st.com/public/STe2ecommunities/mcu/Lists/STM32Java/AllItems.aspx&currentviews=257]https://my.st.com/public/STe2ecommunities/mcu/Lists/STM32Java/Flat.aspx?RootFolder=%2fpublic%2fSTe2ecommunities%2fmcu%2fLists%2fSTM32Java%2fSTM32Cube%20file%20generation%20problem&FolderCTID=0x01200200770978C69A1141439FE559EB459D758000F9A0E3A95BA69146A17C2E80209ADC21&TopicsView=https%3A%2F%2Fmy%2Est%2Ecom%2Fpublic%2FSTe2ecommunities%2Fmcu%2FLists%2FSTM32Java%2FAllItems%2Easpx¤tviews=257

STM32Cube SDHC capacity bug
====================
[DEAD LINK /public/STe2ecommunities/mcu/Lists/STM32Java/Flat.aspx?RootFolder=/public/STe2ecommunities/mcu/Lists/STM32Java/STM32Cube%20SDHC%20capacity%20bug%20%28solved%29&FolderCTID=0x01200200770978C69A1141439FE559EB459D758000F9A0E3A95BA69146A17C2E80209ADC21&TopicsView=https%3a//my.st.com/public/STe2ecommunities/mcu/Lists/STM32Java/AllItems.aspx&currentviews=102]https://my.st.com/public/STe2ecommunities/mcu/Lists/STM32Java/Flat.aspx?RootFolder=%2fpublic%2fSTe2ecommunities%2fmcu%2fLists%2fSTM32Java%2fSTM32Cube%20SDHC%20capacity%20bug%20%28solved%29&FolderCTID=0x01200200770978C69A1141439FE559EB459D758000F9A0E3A95BA69146A17C2E80209ADC21&TopicsView=https%3A%2F%2Fmy%2Est%2Ecom%2Fpublic%2FSTe2ecommunities%2Fmcu%2FLists%2FSTM32Java%2FAllItems%2Easpx¤tviews=102

*NOT* FIXED IN MX_V4.3.0_FW_V1.2.0

USB CDC Bug in CubeMX firmware
========================
[DEAD LINK /public/STe2ecommunities/mcu/Lists/STM32Java/Flat.aspx?RootFolder=/public/STe2ecommunities/mcu/Lists/STM32Java/USB%20CDC%20Bug%20in%20CubeMX%20firmware&FolderCTID=0x01200200770978C69A1141439FE559EB459D758000F9A0E3A95BA69146A17C2E80209ADC21&TopicsView=https%3a//my.st.com/public/STe2ecommunities/mcu/Lists/STM32Java/AllItems.aspx?SortField%3DItemChildCount%26SortDir%3DDesc%26View%3D%257bA243F4C3%252dE27B%252d4AFC%252d9B75%252d9DE978C721FA%257d&currentviews=584]https://my.st.com/public/STe2ecommunities/mcu/Lists/STM32Java/Flat.aspx?RootFolder=%2fpublic%2fSTe2ecommunities%2fmcu%2fLists%2fSTM32Java%2fUSB%20CDC%20Bug%20in%20CubeMX%20firmware&FolderCTID=0x01200200770978C69A1141439FE559EB459D758000F9A0E3A95BA69146A17C2E80209ADC21&TopicsView=https%3A%2F%2Fmy%2Est%2Ecom%2Fpublic%2FSTe2ecommunities%2Fmcu%2FLists%2FSTM32Java%2FAllItems%2Easpx%3FSortField%3DItemChildCount%26SortDir%3DDesc%26View%3D%257bA243F4C3%252dE27B%252d4AFC%252d9B75%252d9DE978C721FA%257d¤tviews=584

STM32Cube_FW_F4 HAL_RCC_OscConfig does not change HSI calibration
=============================================
[DEAD LINK /public/STe2ecommunities/mcu/Lists/STM32Java/Flat.aspx?RootFolder=/public/STe2ecommunities/mcu/Lists/STM32Java/STM32Cube_FW_F4%20HAL_RCC_OscConfig%20does%20not%20change%20HSI%20calibration&FolderCTID=0x01200200770978C69A1141439FE559EB459D758000F9A0E3A95BA69146A17C2E80209ADC21&TopicsView=https%3a//my.st.com/public/STe2ecommunities/mcu/Lists/STM32Java/AllItems.aspx?Paged%3DTRUE%26p_StickyPost%3D%26p_DiscussionLastUpdated%3D20140604%252014%253a52%253a42%26p_ID%3D766%26View%3D%257bA243F4C3%252dE27B%252d4AFC%252d9B75%252d9DE978C721FA%257d%26FolderCTID%3D0x012001%26PageFirstRow%3D41&currentviews=47]https://my.st.com/public/STe2ecommunities/mcu/Lists/STM32Java/Flat.aspx?RootFolder=%2fpublic%2fSTe2ecommunities%2fmcu%2fLists%2fSTM32Java%2fSTM32Cube_FW_F4%20HAL_RCC_OscConfig%20does%20not%20change%20HSI%20calibration&FolderCTID=0x01200200770978C69A1141439FE559EB459D758000F9A0E3A95BA69146A17C2E80209ADC21&TopicsView=https%3A%2F%2Fmy%2Est%2Ecom%2Fpublic%2FSTe2ecommunities%2Fmcu%2FLists%2FSTM32Java%2FAllItems%2Easpx%3FPaged%3DTRUE%26p_StickyPost%3D%26p_DiscussionLastUpdated%3D20140604%252014%253a52%253a42%26p_ID%3D766%26View%3D%257bA243F4C3%252dE27B%252d4AFC%252d9B75%252d9DE978C721FA%257d%26FolderCTID%3D0x012001%26PageFirstRow%3D41¤tviews=47

New RCC file in MX_V4.3.0_FW_V1.2.0 contains "__HAL_RCC_HSI_CALIBRATIONVALUE_ADJUST(RCC_OscInitStruct->HSICalibrationValue);" so assume fixed. ( needs confirmation )

Added (ocuej):
HAL_xxx_CLEAR_IT 
============
[DEAD LINK /public/STe2ecommunities/mcu/Lists/STM32Java/Flat.aspx?RootFolder=/public/STe2ecommunities/mcu/Lists/STM32Java/STM32F4xx%20HAL_TIM_IRQHandler%20misses%20interrupts%20on%20nearly%20overlapping%20TIM%20interrupts&FolderCTID=0x01200200770978C69A1141439FE559EB459D758000F9A0E3A95BA69146A17C2E80209ADC21&currentviews=90]https://my.st.com/public/STe2ecommunities/mcu/Lists/STM32Java/Flat.aspx?RootFolder=%2fpublic%2fSTe2ecommunities%2fmcu%2fLists%2fSTM32Java%2fSTM32F4xx%20HAL_TIM_IRQHandler%20misses%20interrupts%20on%20nearly%20overlapping%20TIM%20interrupts&FolderCTID=0x01200200770978C69A1141439FE559EB459D758000F9A0E3A95BA69146A17C2E80209ADC21¤tviews=90

FIXED IN MX_V4.3.0_FW_V1.2.0

Added (feichtinger.peter):
SPI3
===
When configuring SPI (at least SPI3, I didn't test the others) the generated code fails because hspi3.Init.CRCPolynomial is not set, which leads to a failed assertion in HAL_SPI_Init

*NOT* FIXED IN MX_V4.3.0_FW_V1.2.0 ( checked for SPI1 & SPI3  )

Added (feichtinger.peter):
MCO2
====
When MCO2 is configured with PLLI2SCLK as source, no code for the PLLI2S configuration is created, if no I2S instance is configured.

HAL_RCC_MCOConfig(RCC_MCO2, RCC_MCO2SOURCE_PLLI2SCLK, RCC_MCODIV_1); is generated in  MX_V4.3.0_FW_V1.2.0 so presume  fixed???

GUI ISSUES
==========

STM32CubeMX Changes my Debug Port to JTAG
=======================================
[DEAD LINK /public/STe2ecommunities/mcu/Lists/STM32Java/Flat.aspx?RootFolder=/public/STe2ecommunities/mcu/Lists/STM32Java/STM32CubeMX%20Changes%20my%20Debug%20Port%20to%20JTAG&FolderCTID=0x01200200770978C69A1141439FE559EB459D758000F9A0E3A95BA69146A17C2E80209ADC21&TopicsView=https%3a//my.st.com/public/STe2ecommunities/mcu/Lists/STM32Java/AllItems.aspx&currentviews=51]https://my.st.com/public/STe2ecommunities/mcu/Lists/STM32Java/Flat.aspx?RootFolder=%2fpublic%2fSTe2ecommunities%2fmcu%2fLists%2fSTM32Java%2fSTM32CubeMX%20Changes%20my%20Debug%20Port%20to%20JTAG&FolderCTID=0x01200200770978C69A1141439FE559EB459D758000F9A0E3A95BA69146A17C2E80209ADC21&TopicsView=https%3A%2F%2Fmy%2Est%2Ecom%2Fpublic%2FSTe2ecommunities%2Fmcu%2FLists%2FSTM32Java%2FAllItems%2Easpx¤tviews=51

( I would add complier optimization to this fault, it's always reset to -O3 )

Outcomes