<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tillitis TKey Developer Handbook on TKey Developer Handbook</title><link>https://dev.tillitis.se/</link><description>Recent content in Tillitis TKey Developer Handbook on TKey Developer Handbook</description><generator>Hugo</generator><language>en</language><atom:link href="https://dev.tillitis.se/index.xml" rel="self" type="application/rss+xml"/><item><title>Build bitstream</title><link>https://dev.tillitis.se/unlocked/build/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dev.tillitis.se/unlocked/build/</guid><description>&lt;h1 id="build-bitstream">
 Build bitstream
 &lt;a class="anchor" href="#build-bitstream">#&lt;/a>
&lt;/h1>
&lt;p>Building the bitstream consists of these steps:&lt;/p>
&lt;ol>
&lt;li>Install the toolchain&lt;/li>
&lt;li>Download the repository&lt;/li>
&lt;li>Start the container, if using &lt;code>tkey-builder&lt;/code>&lt;/li>
&lt;li>Generate a unique UDS and UDI&lt;/li>
&lt;li>Build the bitstream&lt;/li>
&lt;/ol>
&lt;h2 id="1-install-the-toolchain">
 1. Install the toolchain
 &lt;a class="anchor" href="#1-install-the-toolchain">#&lt;/a>
&lt;/h2>
&lt;p>Our recommendation is to build using our OCI image,

 &lt;a href="https://ghcr.io/tillitis/tkey-builder">tkey-builder&lt;/a>, in combination
with Podman, which is supported on Linux, macOS, and Windows.&lt;/p>
&lt;p>If Podman is not a valid choice for you, it is also possible to either
use Docker or build the tools natively by compiling from source:

 &lt;a href="https://github.com/tillitis/tillitis-key1/blob/main/doc/toolchain_setup.md">native toolchain setup
instructions&lt;/a>.&lt;/p></description></item><item><title>Program NVCM</title><link>https://dev.tillitis.se/unlocked/nvcm/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dev.tillitis.se/unlocked/nvcm/</guid><description>&lt;h1 id="program-the-nvcm">
 Program the NVCM
 &lt;a class="anchor" href="#program-the-nvcm">#&lt;/a>
&lt;/h1>
&lt;p>Programming the NVCM (Non-Volatile Configuration Memory) makes it
possible to securely write the bitstream with its secrets and make it
non-readable.&lt;/p>
&lt;p>Programming the NVCM consists of these steps:&lt;/p>
&lt;ol>
&lt;li>Download tool.&lt;/li>
&lt;li>Program the NVCM.&lt;/li>
&lt;li>Remove traces of build.&lt;/li>
&lt;/ol>
&lt;blockquote class="book-hint warning">
&lt;p>&lt;strong>NOTE:&lt;/strong>
The NVCM of the FPGA is a one-time-write only! There is no way of
restoring or reprogramming the FPGA. If you want the possbility to
reprogram the TKey multiple times, consider 
 &lt;a href="https://dev.tillitis.se/unlocked/spiflash/">programming the SPI
flash&lt;/a> instead.&lt;/p></description></item><item><title>Program SPI flash</title><link>https://dev.tillitis.se/unlocked/spiflash/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dev.tillitis.se/unlocked/spiflash/</guid><description>&lt;h1 id="program-the-spi-flash-of-the-tkey">
 Program the SPI flash of the TKey
 &lt;a class="anchor" href="#program-the-spi-flash-of-the-tkey">#&lt;/a>
&lt;/h1>
&lt;p>Programming the SPI flash of the TKey makes it possible to develop and
test different FPGA configurations and firmwares while
reprogramming multiple times.&lt;/p>
&lt;blockquote class="book-hint warning">
&lt;p>The entire content of the SPI flash can be read by anyone who has
access to the TKey. If you want a secure, locked-down version of TKey,
you should instead program the 
 &lt;a href="https://dev.tillitis.se/unlocked/nvcm/">NVCM&lt;/a>.&lt;/p>
&lt;/blockquote>
&lt;p>Programming the SPI flash is done in two steps:&lt;/p></description></item><item><title>Casing</title><link>https://dev.tillitis.se/unlocked/casing/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dev.tillitis.se/unlocked/casing/</guid><description>&lt;h1 id="casing">
 Casing
 &lt;a class="anchor" href="#casing">#&lt;/a>
&lt;/h1>
&lt;p>Once you have completed the provisioning of your TKey Unlocked, it is
time to glue the case around it. There has been two cases in
production and depending on which one you have, the glue needed are
slighly different.&lt;/p>
&lt;p>The reason the glue has to be different is due to factors such as
adhesiveness and blooming. This depends on the plastic used and you
can get two completly different results depending on the glue chosen,
both astetic and the fact how well the parts stick together.&lt;/p></description></item></channel></rss>