HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
stlink-org
stlink
C2012–2019
stlink-org / stlink

stlink

Open source STM32 MCU programming toolset

3Distinct people
3Mentions
0Explicit recommenders
5.2KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Open source STM32 MCU programming toolset

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:03:16 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year3 dated mentions

Observed mentions: 2012-10-22 18:08:32 UTC to 2019-05-12 04:33:49 UTC.

012012-01-01 00:00:00 UTC to 2013-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20122013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20152016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2019

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20122012-01-01 00:00:00 UTC2013-01-01 00:00:00 UTC101
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC000
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC000
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC000
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC000
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC000
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC101
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC101

What Hacker News says

3 sources
It's not about the best way to behave differently at runtime and sometimes call exit depending on how the script was invoked, it's about the idea that a scripting language would SUPPORT and ENCOURAGE writing that kind of script, with a special magic built-in variable and a section in the already-complex documentation encouraging its use. Scripts should not behave differently depending on if they were invoked from other scripts, and modular reusable libraries should never take it upon themselves to call "exit" when there's an error. The way to control the flow of recursive functions is by passing explicit parameters (like the recursion depth, or a data structure to walk, or an error callback), not reflecting on the depth of the runtime stack or looking at how the function was called. If bash is too weak to handle errors, or exceptions, or
Read the rest
recursion, or passing functional callback parameters properly, or even file names with spaces in them, then use a better scripting language, don't just throw up your hands and exit. https://stackoverflow.com/questions/14199689/how-can-i-handl... https://github.com/texane/stlink/issues/634
In Surprising Bash Variables
If your goal was a small hardware RNG and you don't mind spending some time hacking, then I can save you some money. Buy an ST103F development board ($1.72 shipped to US from China): https://www.aliexpress.com/item/1pcs-STM32F103C8T6-ARM-STM32... Also buy an STLink programmer for it ($1.98 shipped): https://www.aliexpress.com/item/ST-Link-V2-Programming-Unit-... Build https://github.com/texane/stlink/ or install OpenOCD. Clone the NeuG repo and build for the Maple Mini target: https://anonscm.debian.org/cgit/gnuk/gnuk/neug.git/ Now flash neug.bin to the development board via the STLink, then unplug it and plug the board into your nearest micro-USB cable. You now have a hardware RNG running the same NeuG software on the same processor family as the FST-01. This board doesn't have enough program space to run GnuK, I think. Nor is it in the
Read the rest
tiny form factor of the FST-01 that makes it more suitable as a hardware token.
In NeuG USB True Random Number Generator
I'll second this recommandation. This kit became is my go-to choice for prototyping more complex microcontroller projects. Plenty of peripherals, flexible pin muxing, good documentation and the ARM core is quite fast. Finally, I almost forgot about the open source HW debugger to GDB bridge[0]. I actually wrote a set of drivers, libraries and a build system to allow easy prototyping (like Arduino) but also enable access to the more complex features of the SoC. [0] https://github.com/texane/stlink
In Arduino DUE (32 bit) Now Available

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.