[examples] Add examples for STM32F103C8T6 Minimum System Development … #154
Conversation
|
Is this the "blue pill" board from eBay? |
|
Please fix the commit message length ;-P |
| { | ||
|
|
||
| /// STM32F103 running at 72MHz generated from the external 8MHz crystal | ||
| using systemClock = SystemClock<Pll<ExternalCrystal<MHz8>, MHz72> >; |
There was a problem hiding this comment.
This works only by accident! SystemClock is only configured for the F100 chip.
There was a problem hiding this comment.
You may be able to use the F103RB clock tree from the Nucleo board and modify it to the C8 clock tree.
|
I think "blue_pill" is a better name for it. |
|
Can you split this commit into two? One for adding the board and one for adding the example. This will make it easier to cherry pick the boards in future. Please update the ReadMe with a link of the blue pill and the number of stars (4 stars) in the first commit. |
|
Yes, it's the "Blue Pill". |
strongly-typed
force-pushed
the
feature/stm32f103msdb
branch
from
dbf9640
to
0d4cf41
Compare
|
@salkinium Are you fine with all these commits or did I miss something? |
|
The system clock should be implemented manually. Reasoning. I know it's ugly, but this way it's a lot less magic for devs who want to port to another board. The way I figure out the peripherals is to look at the reference manual section 3.3 (memory map), which gives you the peripheral and the attached bus. You can use the F103RB board target as a starting point and modify it. |
|
Oh, you implicitly and politely asked me to do that? |
I think the UK is getting to me… |
strongly-typed
force-pushed
the
feature/stm32f103msdb
branch
from
4d6ac61
to
97f7ccc
Compare
|
Awesome, will merge manually. |
…Board.