Skip to content

Board: initial support for the STM32F103C8T6#7735

Closed
smlng wants to merge 3 commits intoRIOT-OS:masterfrom
smlng:board/stm32f103c8t6
Closed

Board: initial support for the STM32F103C8T6#7735
smlng wants to merge 3 commits intoRIOT-OS:masterfrom
smlng:board/stm32f103c8t6

Conversation

@smlng
Copy link
Copy Markdown
Member

@smlng smlng commented Oct 13, 2017

This adds support for the STM32F103C8T6 demo board. Its a rather cheap board (i.e., approx. 2 EUR on ebay), and because of that kind of popular with lots of resources on-line - now users can switch and use RIOT 🎉

@smlng smlng added Area: boards Area: Board ports Type: new feature The issue requests / The PR implemements a new feature for RIOT labels Oct 13, 2017
@smlng smlng self-assigned this Oct 13, 2017
@smlng smlng added the CI: ready for build If set, CI server will compile all applications for all available boards for the labeled PR label Oct 13, 2017
@pyropeter
Copy link
Copy Markdown
Contributor

pyropeter commented Oct 14, 2017

This board is commonly known as "Blue Pill" and there is a second PR adding support for it here: #7727

@bergzand
Copy link
Copy Markdown
Member

This board is commonly known as "Blue Pill" and there is a second PR adding support for it here: #7727

The "blue pill" uses the stm32f103cb, this one is known as the "black pill" I think.

@smlng
Copy link
Copy Markdown
Member Author

smlng commented Oct 14, 2017

sorry wasn't aware of these alternative names, though I saw the other PR I (hence) didn't made the connection. I'll check if and how they are related, as @bergzand pointed out there might be differing MCUs here?

@smlng
Copy link
Copy Markdown
Member Author

smlng commented Oct 14, 2017

mhm, seems like mine is actually the bluepill, too. And as far as my quick look up resolved, the stm32f103cb and stm32f103c8t6 have only minor diffs, so it should be possible to integrate both into one or use the greatest common denominator (regarding periphs).

I'll try #7727 with my board and report back if it is working, and will close my PR then - no need to duplicate a board under different names 😉

@smlng smlng added the State: duplicate State: The issue/PR is a duplicate of another issue/PR label Oct 14, 2017
@nmeum
Copy link
Copy Markdown
Member

nmeum commented Oct 14, 2017

The board added with #7727 theoretically also has an stm32f103c8, however, we discovered that it has 128 KiB flash even though it claims to have only 64 KiB flash therefore we decided to use stm32f103cb as the CPU_MODEL. We are currently investigating this further, would be nice to know if that's also the case on your board.

Nonetheless your PR seems to add some things we didn't take care of for instance the gpio_params.h saul configuration, if you decide to close this one in favor of #7727 I would copy this file to our PR.

@smlng
Copy link
Copy Markdown
Member Author

smlng commented Oct 17, 2017

@gebart wasn't aware of that, thanks for the pointer. And obviously a good idea, I totally agree to better keep order of periphs according to board and select RIOTs usage separately.

@smlng
Copy link
Copy Markdown
Member Author

smlng commented Oct 19, 2017

closing in favour #7727

@smlng smlng closed this Oct 19, 2017
@smlng smlng deleted the board/stm32f103c8t6 branch June 29, 2018 18:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Area: boards Area: Board ports CI: ready for build If set, CI server will compile all applications for all available boards for the labeled PR State: duplicate State: The issue/PR is a duplicate of another issue/PR Type: new feature The issue requests / The PR implemements a new feature for RIOT

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants