Skip to content

boards/stm32f030f4-demo: deprecate board#22264

Open
crasbe wants to merge 1 commit into
RIOT-OS:masterfrom
crasbe:pr/deprecate_stm32f030f4-demo
Open

boards/stm32f030f4-demo: deprecate board#22264
crasbe wants to merge 1 commit into
RIOT-OS:masterfrom
crasbe:pr/deprecate_stm32f030f4-demo

Conversation

@crasbe
Copy link
Copy Markdown
Contributor

@crasbe crasbe commented May 9, 2026

Contribution description

The STM32F030F4 Demo board was added in 2019 by @benpicco as a cheap board to run RIOT.
It can indeed be bought reasonably cheap for <2€, but it's also kind of obscure and the RIOT documentation is among the first results for it, which is not necessarily a sign that the board is widely used 😅

Also the board has so little RAM, that it is excluded from many tests and examples anyways:

cbuec@W11nMate:~/RIOTstuff/riot-vanillaice/RIOT$ grep -RnwI -i stm32f030f4-demo . | grep Makefile.ci | wc -l
293

These days it's not worth hassling with the Chinese STM32 boards which more often than not have fake STM32 chips on them, since the Nucleo boards have become so widely available and cheap and don't have fake chips, weird bootloaders and other stuff that makes the development experience annoying.

Testing procedure

Execute BOARD=stm32f030f4-demo make -C tests/sys/shell and observe the wonderful yellow deprecation warning.

Issues/PRs references

Support was added in #12433
Noticed in #22257

Declaration of AI-Tools / LLMs usage:

AI-Tools / LLMs that were used are:

  • none

@crasbe crasbe requested a review from benpicco May 9, 2026 11:51
@crasbe crasbe requested a review from jia200x as a code owner May 9, 2026 11:51
@crasbe crasbe added Discussion: RFC The issue/PR is used as a discussion starting point about the item of the issue/PR Type: cleanup The issue proposes a clean-up / The PR cleans-up parts of the codebase / documentation CI: ready for build If set, CI server will compile all applications for all available boards for the labeled PR Process: deprecation Integration Process: The PR is deprecating a feature or API labels May 9, 2026
@github-actions github-actions Bot added Area: doc Area: Documentation Area: boards Area: Board ports labels May 9, 2026
@riot-ci
Copy link
Copy Markdown

riot-ci commented May 9, 2026

Murdock results

✔️ PASSED

393d188 boards/stm32f030f4-demo: deprecate board

Success Failures Total Runtime
470 0 470 05m:05s

Artifacts

@benpicco
Copy link
Copy Markdown
Contributor

I mean you can still buy it ¯\(ツ)

But yea it was mostly a curiosity to support such a cheap board.

@crasbe
Copy link
Copy Markdown
Contributor Author

crasbe commented May 11, 2026

I mean you can still buy it ¯_(ツ)_/¯

Some might say I have a personal vendetta after having spent hours trying to get a fake STM32 working in like 2018.
I built a small PCB with a display and stuff on it to play with on the Chaos Communication Congress with some friends, but after not getting it to work because of the fake chip I was so demotivated that I didn't go to the Congress the next day even though I had a ticket :(

@AnnsAnns
Copy link
Copy Markdown
Member

The Pico 2 spoiled me holy heck those specs are wild. Generally I'd advocate for a warning like "Hey, like, maybe use a board that has more than 16KiB of flash" and then maybe deprecate it in a year? I feel like generally there is not too much harm to having that board in RIOT since afaik we don't have to have special handling for that board (other than disabling it for every test imaginable because tf are you supposed to do with a board that small)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Area: boards Area: Board ports Area: doc Area: Documentation CI: ready for build If set, CI server will compile all applications for all available boards for the labeled PR Discussion: RFC The issue/PR is used as a discussion starting point about the item of the issue/PR Process: deprecation Integration Process: The PR is deprecating a feature or API Type: cleanup The issue proposes a clean-up / The PR cleans-up parts of the codebase / documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants