2016-10-07 09:54 AM
The code generated by CubeMX (V. 4.16.1 and FW L4 1.5.1) does not work. The ErrorHandler() function is called by MX_USART2_UART_Init(). If I comment out this function and have an simple
HAL_GPIO_TogglePin(LD2_GPIO_Port, LD2_Pin);
HAL_Delay(1000);
in the main loop, the MCU gets stuck in HAL_Delay(). So this seams to be an issue with the SysTick System!
System used:
SystemWorkbench 1.10.... under Linux (Kubuntu 15.10). Does this work under Windows? Anyone? #stm32l476 #!stm32-!cubemx-!bug
2016-10-11 01:01 AM
Hi wwmv,
Is it possible to check the error flags when debugging?I am not sure that the ErrorHandler() code is generated by CubeMX. It seems to be added by your self.-Mayla-To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
2016-10-11 07:58 AM
Hello,
the ErrorHandler is generated by CubeMX. Anyway, version 4.17 of CubeMX with the firmware update STM32L4 1.5.2 fixes the problem. (same setup/config, just migrated + code regeneration)