trezor-firmware

Go to file

Pavol Rusnak f2f50aa188 bump version to 1.3.1		10 years ago
bootloader	rework layoutProgress functions	10 years ago
demo	update trezor-crypto	10 years ago
firmware	bump version to 1.3.1	10 years ago
gen	speed up public ckd (used in multisig)	10 years ago
trezor-common@201b66a559	introduce homescreen	10 years ago
trezor-crypto@d814f58a3b	use const char * const * for wordlist	10 years ago
trezor-qrenc@1da1cedfd6	enable OP_RETURN	10 years ago
.gitignore	bootloader source code	10 years ago
.gitmodules	…
COPYING	…
Dockerfile	check gpg key in Dockerfile	10 years ago
Makefile	…
Makefile.include	Disable assertion checking	10 years ago
README.rst	update README	10 years ago
buttons.c	…
buttons.h	…
firmware-docker-build.sh	bump version to 1.3.1	10 years ago
firmware-fingerprint.sh	…
layout.c	speed up public ckd (used in multisig)	10 years ago
layout.h	rework layoutProgress functions	10 years ago
memory.c	use hdnode_private_ckd_cached where appropriate	10 years ago
memory.h	…
memory.ld	…
memory_app_0.0.0.ld	…
memory_app_1.0.0.ld	…
oled.c	correctly skip utf-8 characters	10 years ago
oled.h	refactor font handling	10 years ago
rng.c	use Knuth shuffles	10 years ago
rng.h	use Knuth shuffles	10 years ago
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.