AnsweredAssumed Answered

STM32CubeMX V4.13.0 problems

Question asked by Aussie Susan on Feb 7, 2016
Latest reply on Mar 22, 2016 by STM32Cube-T
Yesterday I upgraded to V4.13.0 which required that I also upgrade to STM32CubeL4 V1.3.0.
Since then, every project that I generate exhibits a couple of problems:
1) every reference to RCC_xxx #defines shows up in the IDE as "Type RCC_xxx could not be resolved". Same with anything that looks like it could be a system defined preprocessor symbol. The programs compile OK so I think this is an issue with the generated code for the project
2) every program starts in debug and, before it gets to the 'main' function, ends up in the "startup_stm32L476xx.s" file at some labels called "Default_Hander:" and "Infinite_Loop:" where the executable code is exactly that - a branch back to the label. I have single stepped through the code form the "Reset_Handler:" label and the last statement seems to cause the problem is "bi __libc_init_array" in that I cannot step into that function and when I pause the processor I'm at the infinite loop.

The console shows:

Breakpoint 1, LoopFillZerobss () at C:/Users/Administrator/workspace/Blinky/Drivers/CMSIS/Device/ST/STM32L4xx/Source/Templates/gcc\startup_stm32l476xx.s:114

114         bl __libc_init_array

Program received signal SIGINT, Interrupt.

WWDG_IRQHandler () at C:/Users/Administrator/workspace/Blinky/Drivers/CMSIS/Device/ST/STM32L4xx/Source/Templates/gcc\startup_stm32l476xx.s:134

134          b     Infinite_Loop

Have I done something or not done something that has caused this?