trezor-mcu

Go to file

Pavol Rusnak 03a053c944 implement change logic for multisig		2014-12-21 02:15:56 +01:00
bootloader	…
demo	…
firmware	…
gen	…
trezor-common@94d17ef8bc	…
trezor-crypto@c6ca89a850	…
trezor-qrenc@f12996741c	…
.gitignore	…
.gitmodules	…
COPYING	…
Dockerfile	…
Makefile	…
Makefile.include	…
README.rst	…
buttons.c	…
buttons.h	…
firmware-docker-build.sh	…
firmware-fingerprint.sh	…
layout.c	…
layout.h	…
memory.c	…
memory.h	…
memory.ld	…
memory_app_0.0.0.ld	…
memory_app_1.0.0.ld	…
oled.c	…
oled.h	…
rng.c	…
rng.h	…
serialno.c	…
serialno.h	…
setup.c	…
setup.h	…
util.c	…
util.h	…

README.rst

TREZOR Firmware
===============

http://bitcointrezor.com/

How to build Trezor firmware?
-----------------------------

1. Install Docker (from docker.com or from your distribution repositories)
2. ``git clone https://github.com/trezor/trezor-mcu.git``
3. ``cd trezor-mcu``
4. ``./firmware-docker-build.sh``

This creates trezor.bin in current directory and prints its fingerprint at the last line of the build log.

How to get fingerprint of firmware signed and distributed by SatoshiLabs?
-------------------------------------------------------------------------

1. Pick version of firmware binary listed on https://mytrezor.com/data/firmware/releases.json
2. Download it: ``wget -O trezor.signed.bin.hex https://mytrezor.com/data/firmware/trezor-1.1.0.bin.hex``
3. ``xxd -r -p trezor.signed.bin.hex trezor.signed.bin``
4. ``./firmware-fingerprint.sh trezor.signed.bin``

Step 4 should produce the same sha256 fingerprint like your local build.

The reasoning for ``firmware-fingerprint.sh`` script is that signed firmware has special header holding signatures themselves, which must be avoided while calculating the fingerprint.