aboutsummaryrefslogtreecommitdiff
path: root/pelican/content/AlphaBoardStrategy.md
diff options
context:
space:
mode:
Diffstat (limited to 'pelican/content/AlphaBoardStrategy.md')
-rw-r--r--pelican/content/AlphaBoardStrategy.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/pelican/content/AlphaBoardStrategy.md b/pelican/content/AlphaBoardStrategy.md
index bfe04bf..fc20bd8 100644
--- a/pelican/content/AlphaBoardStrategy.md
+++ b/pelican/content/AlphaBoardStrategy.md
@@ -9,8 +9,8 @@ Develop a first, custom HSM board that can be used to support a first set of app
* The use cases and requirements for the alpha board are specified on the [Dashboard](http://trac.cryptech.is/wiki/Dashboard).
-* The basic blocks of the Alpha board is [shown here](Hardware).
-* The [BOM and component requirements](AlphaBoardComponents).
+* The basic blocks of the Alpha board is [shown here](Hardware.md).
+* The [BOM and component requirements](AlphaBoardComponents.md).
* The detailed [Alpha board functional drawing](http://trac.cryptech.is/browser/doc/design/Alpha_board_drawing.pdf).
@@ -18,7 +18,7 @@ Develop a first, custom HSM board that can be used to support a first set of app
## Plan
1. Choose FPGA and ARM (done)
2. Develop BOM, requirements and functional diagram (done-ish).
-3. Develop complete [schematics](AlphaSchematics) (almost done).
+3. Develop complete [schematics](AlphaSchematics.md) (almost done).
4. Develop dev-board ouorselves to connect chosen ARM to FPGA on Novena, to do some early development and testing in parallell with step 5.
5. Get professional designer to do many-layer PCB from schematics.
6. Manufacture a couple of boards (~10).