Skip to main content
DJC
DJC
Senior
July 19, 2017
Solved

FW.F1.1.6.0 Debug in OpenSTM32

  • July 19, 2017
  • 1 reply
  • 649 views
Posted on July 19, 2017 at 16:49

Hi. 

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,

however

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? 

/David

#stm32f1 #cubemx-4.22 #system-workbench
This topic has been closed for replies.
Best answer by DJC
Posted on July 30, 2017 at 16:49

I fixed this myself.

I created a whole new project and made sure some basic LED flashing worked on my board. Then I used meld diff-tool to compare the two directories and copied my code into the new project (including the entire .git folder allowing me to keep my project history as if only the new STMF1 and the project settings were updated. 

1 reply

DJC
DJCAuthorAnswer
Senior
July 30, 2017
Posted on July 30, 2017 at 16:49

I fixed this myself.

I created a whole new project and made sure some basic LED flashing worked on my board. Then I used meld diff-tool to compare the two directories and copied my code into the new project (including the entire .git folder allowing me to keep my project history as if only the new STMF1 and the project settings were updated. 

Terms & ConditionsAccessibility statement