STM32F030C8T6 Clock Issue

[Tabulous]

I have a STM32F041 Nucleo32 board, I could test on that but I am having problems flashing it using OpenOCD, have to understand why.

Giovanni

F041 ???

thats not even listed on ST website

[Giovanni]

My fault, it is F042K6.

Giovanni

[Tabulous]

F042K6 this is a more normal clock tree, so i believe it will work outta the box.

Its the parts that have hardware div2 and no PREDIV that dont work

[Tabulous]

F042K6 this is a more normal clock tree, so i believe it will work outta the box.

Its the parts that have hardware div2 and no PREDIV that dont work

if you also get a F031K6 this has the other clock tree, so if your get it it working with both these all should be good

[Giovanni]

Hi,

I made both of them (F031K6 and F042K6) work, there was an error in makefiles but not both demos are OK.

Giovanni

[Tabulous]

Hi,

I made both of them (F031K6 and F042K6) work, there was an error in makefiles but not both demos are OK.

Giovanni

is this updated on the repo ?

[Giovanni]

Of course.

Giovanni

[Tabulous]

STill cant get the STM32F030CC working, still bombs the debug when enabling the PLL in the clock setup.........

one thing i have found weird is using ST-Link flasher it detects the part as Device family :STM32F091xB-xC/F098xC which is weird......ST must be doing something like using 91/98 silicon for other devices.

[Giovanni]

Is cortex-m0 specified in the Makefile as target?

Giovanni

[Tabulous]

yep

even just tried the the Nucleo F091RC demo on my target hardware and this does the same as soon as you single step through PLL enable

Code: Select all

  /* PLL activation.*/
  RCC->CR   |= RCC_CR_PLLON;

debugger is dropped....