AnsweredAssumed Answered

Bugreport STM32CubeMX 4.20

Question asked by zwarteveld.johan on Mar 13, 2017
Latest reply on Apr 28, 2017 by Jeanne Joly

1. Faulty code generation

STMCube Generates to following code in the function: void SystemClock_Config(void)

RCC_OscInitStruct.OscillatorType = RCC_OSCILLATORTYPE_HSI|RCC_OSCILLATORTYPE_HSE;

this results that the SystemClock_Config function always enters the Error_Handler

HSE Clock is used as main clock.
By removing the RCC_OSCILATORTYPE_HSI define code functions normally

 

2. Non working code USB MSC

Code generated for USB MSC stops working after the usb command USB Set Configuration Request

Device Manager reports Error Code 10 (can't start device)

The usb analyzer tool of wireshark shows no communication after host sends Set Configuration Request.

Problem observed from at least STM32CubeMX V4.18+

 

Changing driver versions does not solve the isuue

 

Tested on STM32446e-Eval and STM23F446ZC
PC: Windows 10
Toolchain: KEIL µVsion V5

Outcomes