It is, I've put up various bits of code on Github (mostly targeting
the 32F4 vs the F2 but it might give you some ideas. And there is a
Google+ group "Cortex M Developers" which has both a rep from ARM in
it and a rep from ST Micro so you can get some official answers there
reasonably quickly.
--C
On Sun, 12 Jan 2014, Chuck McManis wrote:
# > I will revisit after coffee :)
#
# Heh, always a good idea :-). HSE is high speed external, HSI is high
# speed Internal.
Discovered the CMSIS Periph pdf on the ST site, which clued me in
on this point ;)
I had (for fun) pop
> I will revisit after coffee :)
Heh, always a good idea :-). HSE is high speed external, HSI is high
speed Internal.
On Sun, Jan 12, 2014 at 9:20 PM, skeezix wrote:
> On Sun, 12 Jan 2014, skeezix wrote:
>
> # rcc_clock_setup_hse_3v3 ( &hse_8mhz_3v3[CLOCK_3V3_120MHZ]);
> #
> #
On Sun, 12 Jan 2014, skeezix wrote:
# rcc_clock_setup_hse_3v3 ( &hse_8mhz_3v3[CLOCK_3V3_120MHZ]);
#
# Question: are there any pre-req's for this function to work? I
# know the lib works at least at some level, since blinking the LED via GPIO
# function call is happy.
Ah, as
Complete STM32 noobie here, I'm afraid.
I noticed in the rcc.[hc] code theres a handy dandy function that
looks ready to go to set 120MHz (which is the chip max - STM32F205RE if
memory serves, just slapped onto a breadboard; its working, I can blink
LEDs.)
rcc_clock_se
