STM32F103C8T6 - Arm Cortex-M3 MCU (Blue Pill)

<!doctype html><html lang=en><head><meta charset=utf-8>
<meta name=viewport content="width=device-width,initial-scale=1"><title>STM32F103C8T6 pinout</title>
<style>
:root{color-scheme:dark}
body{margin:0;padding:4px 0 10px;background:transparent;
  font-family:'Satoshi',system-ui,-apple-system,'Segoe UI',sans-serif;color:#e6edf3}
</style>
<!-- The REGISTERED widget, not a copy of it.

     This file used to inline ~20KB of pinout-widget.js. That meant fixes shipped
     in adom-widget never arrived here: the corner-overhang fix (28e23c3,
     2026-08-24) sat unapplied on this page for a week while the registry served
     the corrected script the whole time. Loading /widget-script/adom-pinout.js
     means the next fix lands without anyone editing this page.

     The frame's CSP is `script-src 'unsafe-inline' https:` and `connect-src
     'self'`, so both the script and the same-origin data fetch resolve.

     The data src uses the /api/pages/.../files/ path. An earlier version of this
     comment said the /render/ shortcut is broken on component pages. That is wrong,
     and worth correcting because it reads as guidance: /render/ works here fine.
     The confusion is that this file's REPO PATH is render/pinout.json, so the
     shortcut carries the segment twice and looks malformed:

       /adom/stm32f103c8t6/render/pinout.json          404   (no such repo path)
       /adom/stm32f103c8t6/render/render/pinout.json   200   (repo path is render/)
       /adom/stm32f103c8t6/render/README.md            200
       /adom/stm32f103c8t6/render/sections/pinout.html 200

     Both forms serve the same bytes. The /api/pages/ path is kept only because it
     reads unambiguously, not because the shortcut fails. -->
<script src="https://wiki.adom.inc/widget-script/adom-pinout.js"></script>
</head><body>
<adom-pinout src="/api/pages/adom/stm32f103c8t6/files/render/pinout.json"></adom-pinout>
<script>
function fit(){parent.postMessage({type:'readme-height',height:document.documentElement.scrollHeight},'*')}
addEventListener('load',fit);new ResizeObserver(fit).observe(document.documentElement);
</script>
</body></html>