AnsweredAssumed Answered

FW.F1.1.6.0 Debug in OpenSTM32

Question asked by David Cox on Jul 19, 2017
Latest reply on Jul 30, 2017 by David Cox



I was running CubeMx4.21.0 and upgrade for 4.22.0

This meant an upgrade on the F1 family from 1.4.0 to 1.6.0 (may 2017)


have a bootloader configured, so debug should align to 0x8004000 

On the new version everything builds just fine it seems like the its ok,



In STM32SystemWorkbench debug mode, the debugger is now starting at 0x8000000. 

If I use git to specifically roll back the ONLY STM32F1xx_HAL_Driver  folder, then debug works just fine. 


Im guessing there is a define somewhere that causes eclipse to debug from the default location and it is looking for a parameter that is now new-or-missing on the new driver. 

Any ideas why it works on 1.4 and not 1.6?