<p>The stdio uart pins usually default to device 0.  According to <a href="https://github.com/RIOT-OS/RIOT/blob/master/boards/common/stm32f103c8/include/periph_conf.h">the periph configuration</a> device 0 is actually a10 and a9.</p>
<pre><code>        .rx_pin     = GPIO_PIN(PORT_A, 10),
        .tx_pin     = GPIO_PIN(PORT_A, 9),
</code></pre>
<p>So you could try to get terminal output by connecting to those pins.</p>
<p><em>(A2 and A3 are for the rom uart bootloader I think)</em></p>
<p>As for the LED it should be C13 and you should see it flashing (if something else isn't already enabled).  A few things to note about the LED is that it is sinking, so a 0 turns it on and a 1 turns it off.  Also the QA for the bluepills are not the best (that is one thing that keeps the cost so low) some have the LED connected to different pins.  This is the reason why there are so many different binaries for the <a href="https://github.com/rogerclarkmelbourne/STM32duino-bootloader/tree/master/bootloader_only_binaries">dfu_util bootloader</a>.  Now if you already tested the hardware it is probably not that.  You could also try to flash the RIOT/tests/led/ application.</p>
<p>Your almost there!</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/RIOT-OS/RIOT/issues/11030#issuecomment-466760819">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AEn7YM5XGrRixcsGP3ycHkhvt8pffNHXks5vQmlZgaJpZM4bAdoU">mute the thread</a>.<img src="https://github.com/notifications/beacon/AEn7YHFx3xkLURghVumB-rns35c5waSLks5vQmlZgaJpZM4bAdoU.gif" height="1" width="1" alt="" /></p>
<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/RIOT-OS/RIOT","title":"RIOT-OS/RIOT","subtitle":"GitHub repository","main_image_url":"https://github.githubassets.com/images/email/message_cards/header.png","avatar_image_url":"https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/RIOT-OS/RIOT"}},"updates":{"snippets":[{"icon":"PERSON","message":"@MrKevinWeiss in #11030: The stdio uart pins usually default to device 0.  According to [the periph configuration](https://github.com/RIOT-OS/RIOT/blob/master/boards/common/stm32f103c8/include/periph_conf.h) device 0 is actually a10 and a9.\r\n```\r\n        .rx_pin     = GPIO_PIN(PORT_A, 10),\r\n        .tx_pin     = GPIO_PIN(PORT_A, 9),\r\n```\r\n\r\nSo you could try to get terminal output by connecting to those pins.\r\n\r\n_(A2 and A3 are for the rom uart bootloader I think)_\r\n\r\nAs for the LED it should be C13 and you should see it flashing (if something else isn't already enabled).  A few things to note about the LED is that it is sinking, so a 0 turns it on and a 1 turns it off.  Also the QA for the bluepills are not the best (that is one thing that keeps the cost so low) some have the LED connected to different pins.  This is the reason why there are so many different binaries for the [dfu_util bootloader](https://github.com/rogerclarkmelbourne/STM32duino-bootloader/tree/master/bootloader_only_binaries).  Now if you already tested the hardware it is probably not that.  You could also try to flash the RIOT/tests/led/ application.\r\n\r\nYour almost there!"}],"action":{"name":"View Issue","url":"https://github.com/RIOT-OS/RIOT/issues/11030#issuecomment-466760819"}}}</script>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/RIOT-OS/RIOT/issues/11030#issuecomment-466760819",
"url": "https://github.com/RIOT-OS/RIOT/issues/11030#issuecomment-466760819",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>