Git-Mirrors/tillitis-key
1
0
Fork 0
mirror of https://github.com/tillitis/tillitis-key1.git synced 2024-12-19 04:44:24 -05:00
Code Issues Packages Projects Releases Wiki Activity

Make synth.json depend on data/{uds,udi}.hex; revise docs

Browse Source
This commit is contained in:
Daniel Lublin 2022-09-20 16:34:58 +02:00
parent 6ff117cb5d
commit 40803993e1
No known key found for this signature in database
GPG Key ID: 75BD0FEB8D3E7830
3 changed files with 22 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
doc/quickstart.md
View File

@ -13,6 +13,8 @@ The Tillitis Key1 kit includes:
- USB-C cable - USB-C cable
- USB-C to USB-A adapter - USB-C to USB-A adapter
# Programming FPGA bitstream and firmware onto Tillitis Key 1
Connect the programmer to the computer using the mentioned cable. It Connect the programmer to the computer using the mentioned cable. It
is convenient to connect the USB device to the USB-C cable, and then is convenient to connect the USB device to the USB-C cable, and then
connect the cable to the computer. The latter using the USB-C-to-A, if connect the cable to the computer. The latter using the USB-C-to-A, if
@ -40,15 +42,22 @@ $ cd tillitis-key1/hw/application_fpga
$ make prog_flash $ make prog_flash
``` ```
After programming, when your Key1 device is connected to the host, it would boot the firmware. After programming, when your device is connected to the host, it would boot the
When boot has completed, the device will start flashing the LED white. This indicates that the device firmware. When boot has completed, the device will start flashing the LED
is ready to receive and measure an app. white. This indicates that the device is ready to receive and measure an app.
To personalize the device, you need to modify the hex file that contain the Unique Device Secret (UDS). # Device personalization
You should also update the Unique Device Identity (UDI). These hex files are located in hw/application_fpga/data.
To make this easier there is a tool, tpt that can generate these files. The tool can be found in hw/application_fpga/tools/tpt. To personalize the device, you need to modify the hex file that contains the
The tool allow you to supply a secret used as part of the UDS generation. The tool can be run interactively, or by suppling Unique Device Secret (UDS). You should also update the Unique Device Identity
inputs on the command line: (UDI). These hex files are located in `hw/application_fpga/data/`. Note that
after modify the files in this directory, you need to rebuild and program the
device again (as above).
To make this easier there is a tool that can generate these files. The tool can
be found in `hw/application_fpga/tools/tpt`. The tool allow you to supply a
secret used as part of the UDS generation. The tool can be run interactively,
or by suppling inputs on the command line:
``` ```
usage: tpt.py [-h] [-v] [--uss USS] [--vid VID] [--pid PID] [--rev REV] [--serial SERIAL] usage: tpt.py [-h] [-v] [--uss USS] [--vid VID] [--pid PID] [--rev REV] [--serial SERIAL]

2
hw/application_fpga/Makefile
View File

@ -168,7 +168,7 @@ verilator: $(VERILATOR_TOP_SRC) $(VERILOG_SRCS) firmware.hex $(ICE40_SIM_CELLS)
# Main FPGA build flow. # Main FPGA build flow.
# Synthesis. Place & Route. Bitstream generation. # Synthesis. Place & Route. Bitstream generation.
#------------------------------------------------------------------- #-------------------------------------------------------------------
synth.json: $(TOP_SRC) $(VERILOG_SRCS) bram_fw.hex synth.json: $(TOP_SRC) $(VERILOG_SRCS) bram_fw.hex $(P)/data/uds.hex $(P)/data/udi.hex
$(YOSYS_PATH)yosys -v3 -l synth.log -DBRAM_FW_SIZE=$(BRAM_FW_SIZE) \ $(YOSYS_PATH)yosys -v3 -l synth.log -DBRAM_FW_SIZE=$(BRAM_FW_SIZE) \
-DFIRMWARE_HEX=\"$(P)/bram_fw.hex\" \ -DFIRMWARE_HEX=\"$(P)/bram_fw.hex\" \
-DUDS_HEX=\"$(P)/data/uds.hex\" \ -DUDS_HEX=\"$(P)/data/uds.hex\" \