From 92a5a007277005744740dabd36182410b87b6441 Mon Sep 17 00:00:00 2001 From: Rob Austein Date: Sun, 14 Feb 2021 17:47:46 +0000 Subject: Add image links Clean up whacky invisible unicode characters in links on a couple of source packages --- pelican/content/AlphaBoardPictures.md | 4 ++-- pelican/content/AlphaSealedBags.md | 2 +- pelican/content/CoretestHashesC5G.md | 2 +- pelican/content/DevBridgeBoard.md | 6 +++--- pelican/content/GettingStartedNovena.md | 2 +- pelican/content/Hardware.md | 2 +- pelican/content/NoisyDiode.md | 8 ++++---- pelican/content/OpenCryptoChip.md | 4 ++-- pelican/content/RoughV1.md | 4 ++-- pelican/content/StateOfPlay.md | 8 ++++---- pelican/content/UsingSTLink.md | 2 +- 11 files changed, 22 insertions(+), 22 deletions(-) (limited to 'pelican') diff --git a/pelican/content/AlphaBoardPictures.md b/pelican/content/AlphaBoardPictures.md index 27caebe..9e006f0 100644 --- a/pelican/content/AlphaBoardPictures.md +++ b/pelican/content/AlphaBoardPictures.md @@ -8,5 +8,5 @@ The current revision of the Alpha board is rev03. rev01 was the board known as the 'dev-bridge'. rev02 was functionally the same as the rev03, but in another form factor. - - +![Alpha_rev03_top_med.jpg]({attach}AlphaBoardPictures/Alpha_rev03_top_med.jpg) +![Alpha_rev03_bottom_med.jpg]({attach}AlphaBoardPictures/Alpha_rev03_bottom_med.jpg) diff --git a/pelican/content/AlphaSealedBags.md b/pelican/content/AlphaSealedBags.md index 0f4d720..a69a66c 100644 --- a/pelican/content/AlphaSealedBags.md +++ b/pelican/content/AlphaSealedBags.md @@ -15,7 +15,7 @@ At this time, we do not keep records of which exact unit was sent to whom. This is a picture of the currently used bags: - +![Alpha_tamper_bag_2016-12-16.png]({attach}AlphaSealedBags/Alpha_tamper_bag_2016-12-16.png) diff --git a/pelican/content/CoretestHashesC5G.md b/pelican/content/CoretestHashesC5G.md index 6d98aea..20a3faa 100644 --- a/pelican/content/CoretestHashesC5G.md +++ b/pelican/content/CoretestHashesC5G.md @@ -57,7 +57,7 @@ interface connected to a FPGA device. The subsystem consists of: well as connecting the rxd and txd ports on the uart to external pins as well as clk and reset. This core repo also contains the Python command line program hash_tester we will be using to talk to coretester and perform tests of the sha1 and sha256 cores. - +![coretest_hashes.png]({attach}CoretestHashesC5G/coretest_hashes.png) *The coretest_hashes subsystem with sha1 and sha256 cores. The system is connected to a host computer via a serial interface.* diff --git a/pelican/content/DevBridgeBoard.md b/pelican/content/DevBridgeBoard.md index 41a12c4..2df3ac4 100644 --- a/pelican/content/DevBridgeBoard.md +++ b/pelican/content/DevBridgeBoard.md @@ -11,13 +11,13 @@ Schematics and layouts are at [user/ft/stm32-dev-bridge/hardware/rev01](https:// High resolution pictures of rev01 of the dev-bridge board are attached at the bottom of this page, but the following should be more than sufficient to read the silkscreens. - +![dev-bridge_rev01_front_medium.jpg]({attach}DevBridgeBoard/dev-bridge_rev01_front_medium.jpg) - +![dev-bridge_rev01_back_medium.jpg]({attach}DevBridgeBoard/dev-bridge_rev01_back_medium.jpg) Here is the board mounted on the Novena, attached to the programmer: - +![IMG_9983s.jpg]({attach}DevBridgeBoard/IMG_9983s.jpg) Note that it's rather bigger than the Netgear enclosure I use to transport the Novena. (Not only does it protect the board, but I have this superstition that TSA is more comfortable with a home gateway than a bare motherboard.) diff --git a/pelican/content/GettingStartedNovena.md b/pelican/content/GettingStartedNovena.md index 97668a1..8c58aed 100644 --- a/pelican/content/GettingStartedNovena.md +++ b/pelican/content/GettingStartedNovena.md @@ -26,7 +26,7 @@ $ sudo apt-get upgrade ## The Avalanche Noise Board - +![rev03-on-novena.jpg]({attach}GettingStartedNovena/rev03-on-novena.jpg) The avalanche noise board is a Novena daughter board that contains a zener-diode noise circuit that can be read directly by the FPGA. diff --git a/pelican/content/Hardware.md b/pelican/content/Hardware.md index eaba3fa..fbdac48 100644 --- a/pelican/content/Hardware.md +++ b/pelican/content/Hardware.md @@ -12,7 +12,7 @@ Various generic FPGA development boards. An Alpha version of a CrypTech HSM, currently in early design - +![cryptech-g3.png]({attach}Hardware/cryptech-g3.png) There is no real tamper wrapping and no tamper sensors. The tamper switch is used to simulate tamper detection to test the system's tamper reaction(s). diff --git a/pelican/content/NoisyDiode.md b/pelican/content/NoisyDiode.md index b4afe5a..46e5ec2 100644 --- a/pelican/content/NoisyDiode.md +++ b/pelican/content/NoisyDiode.md @@ -7,21 +7,21 @@ Avalanche breakdown is a physical process that occurs when current is forced bac The unamplified noise looks like this: - +![noise1.jpg]({attach}NoisyDiode/noise1.jpg) After amplification, details are lost but the signal is now 3.3V (blue is noise before amplification, yellow is amplified) - +![noise2.jpg]({attach}NoisyDiode/noise2.jpg) Many implementations on the Internet feed a similar signal into an ADC (Analog Digital converter) and use the resulting data value at the time of the sampling as entropy. The Cryptech project believes a more robust way of extracting entropy is to instead feed the noise to a Schmitt trigger and then measure the time between rising edges. This would be more robust since any analog reading of the noise (such as with an ADC) will be sensitive to changes in temperature, supplied voltage and component aging. After beeing fed through a Schmitt trigger, the noise looks like this (yellow signal, blue is just a 4 MHz clock): - +![noise-schmitt.jpg]({attach}NoisyDiode/noise-schmitt.jpg) The Cryptech project has to date made a couple of different hardware entropy source boards, but they all share the same design for the avalanche noise source. The core parts of the circuit are shown below. Git repository with full schematics and source code is linked at the bottom of this page. - +![noise-schematics.png]({attach}NoisyDiode/noise-schematics.png) Links: diff --git a/pelican/content/OpenCryptoChip.md b/pelican/content/OpenCryptoChip.md index ab250a3..c8163f8 100644 --- a/pelican/content/OpenCryptoChip.md +++ b/pelican/content/OpenCryptoChip.md @@ -5,7 +5,7 @@ ## The Layer Cake Architecture Picture - +![layer-cake.jpg]({attach}OpenCryptoChip/layer-cake.jpg) @@ -26,7 +26,7 @@ * Password management - +![cryptech venn.png]({attach}OpenCryptoChip/cryptech%20venn.png) ## Basic Functions of Crypto Chip diff --git a/pelican/content/RoughV1.md b/pelican/content/RoughV1.md index 1c0ec56..ada39d9 100644 --- a/pelican/content/RoughV1.md +++ b/pelican/content/RoughV1.md @@ -19,13 +19,13 @@ source out of the can. for v.2 (or whatever) we would move it down to the FPGA Verilog. ## FPGA Overview - +![HW_sketch_v0001.png]({attach}RoughV1/HW_sketch_v0001.png) ## Sketch of TRNG Chain - +![HW_RNG.png]({attach}RoughV1/HW_RNG.png) diff --git a/pelican/content/StateOfPlay.md b/pelican/content/StateOfPlay.md index 06ad190..524971b 100644 --- a/pelican/content/StateOfPlay.md +++ b/pelican/content/StateOfPlay.md @@ -80,22 +80,22 @@ See [Libraries Guide for HDL Designs]]([http://www.xilinx.com/support/documentat ### Module relationships in core/novena build - +![novena__linkcells.svg]({attach}StateOfPlay/novena__linkcells.svg) ### Module relationships in core/novena_i2c_simple build - +![novena_i2c_simple__linkcells.svg]({attach}StateOfPlay/novena_i2c_simple__linkcells.svg) ### Module relationships in core/novena_eim build - +![novena_eim__linkcells.svg]({attach}StateOfPlay/novena_eim__linkcells.svg) ### Module relationships in cores/trng build By special request, here's a graph for the TRNG too, even though we don't yet have a way to speak to it from the Novena: - +![trng__linkcells.svg]({attach}StateOfPlay/trng__linkcells.svg) ## C Code diff --git a/pelican/content/UsingSTLink.md b/pelican/content/UsingSTLink.md index 18c0807..1c6f7da 100644 --- a/pelican/content/UsingSTLink.md +++ b/pelican/content/UsingSTLink.md @@ -23,7 +23,7 @@ on the Alpha board (top, just left of center). This photo shows the correct orientation of the cables (both boards oriented so that the logo is right-side up): - +![IMG_20170512_205557_s.jpg]({attach}UsingSTLink/IMG_20170512_205557_s.jpg) NOTE: The STM boards have an unfortunate tendency to short unexpectedly, so I recommend putting them in an enclosure. In this case, I've cut holes in -- cgit v1.2.3