Go to file

Pavol Rusnak 437c5739f1 Merge branch 'jhoenicke-master'		8 years ago
bootloader	remove DialogIcon enum, use bitmap structure directly	8 years ago
demo	remove DialogIcon enum, use bitmap structure directly	8 years ago
firmware	Merge branch 'jhoenicke-master'	8 years ago
gen	add gitlab to u2f_knownapps	8 years ago
gitian	…
vendor	Merge branch 'master' of https://github.com/jhoenicke/trezor-mcu into jhoenicke-master	8 years ago
.gitignore	…
.gitmodules	…
.travis.yml	fix travis build failure	8 years ago
COPYING	…
Dockerfile	…
Makefile	fix ar usage	8 years ago
Makefile.include	fix ar usage	8 years ago
README.md	…
bootloader-docker-build.sh	add set -e to shell scripts	8 years ago
buttons.c	…
buttons.h	…
firmware-docker-build.sh	add set -e to shell scripts	8 years ago
firmware-fingerprint.sh	add set -e to shell scripts	8 years ago
layout.c	remove DialogIcon enum, use bitmap structure directly	8 years ago
layout.h	remove DialogIcon enum, use bitmap structure directly	8 years ago
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.md

TREZOR Firmware

http://bitcointrezor.com/

How to build TREZOR firmware?

Install Docker
git clone https://github.com/trezor/trezor-mcu.git
cd trezor-mcu
./firmware-docker-build.sh TAG (where TAG is v1.3.2 for example, if left blank the script builds latest commit)

This creates file output/trezor-TAG.bin and prints its fingerprint at the last line of the build log.

How to build TREZOR bootloader?

Install Docker
git clone https://github.com/trezor/trezor-mcu.git
cd trezor-mcu
./bootloader-docker-build.sh

This creates file output/bootloader.bin and prints its fingerprint and size at the last line of the build log.

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

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

Step 4 should produce the same sha256 fingerprint like your local build (for the same version tag).

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.