Commit a3ff5ca3 authored by schneider's avatar schneider
Browse files


parent 1db8a71c
Pipeline #1263 passed with stages
in 52 seconds
......@@ -2,13 +2,6 @@
title: Firmware
## Overview
card10 will have had a dual-core processor. To make maximum use of this, its
firmware will have been split into two parts, one for each core. The main
"OS", running on core 0 which will have been called "Epicardium" and the
MicroPython running on core 1 which will have been called "Pycardium":
<img class="center" alt="firmware overview" src="/media/firmware/overview.svg" width="600" height="auto" align="center">
## How to help
Dear card10logists and fellow researchers!
......@@ -19,6 +12,8 @@ are still lots of things that need to have been done. We keep track in the
[issue tracker](
of the [firmware]( repo.
We are documenting our firmware in our [firmware documentation](
If there is an issue you would like to help with, please leave a comment so we
can assign it to you. Issues tagged as **Easy** should be doable without much
previous knowledge of embedded development/the card10 firmware. The 3 labels
......@@ -31,3 +26,17 @@ Matrix-bridge.
card10 prototypes have been distributed to the hackerspaces listed here:
[Distribution of prototypes](../prototype_distribution).
## Overview
To make the most of card10’s dual-core processor, its firmware will have been divided
into two parts: The “main” firmware running on core 0 which will have been called
Epicardium and the “user-code” running on core 1. In most cases this will have
been Pycardium, our MicroPython port.
<img class="center" alt="firmware overview" src="" width="600" height="auto" align="center">
## Details
Please tend to where we
have extensive documentation about the firmware itself but also about how
to implement new modules an features.
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment