Go to file

Pavol Rusnak d77152b5a5 use OPTFLAGS=-Os for bootloader docker build		9 years ago
bootloader	show firmware hash screen after unofficial firmware dialog	9 years ago
demo	…
firmware	fix usage of inline/static	9 years ago
gen	…
gitian	add gitian build (work in progress)	9 years ago
vendor	update submodules	9 years ago
.gitignore	…
.gitmodules	…
.travis.yml	fix travis build	9 years ago
COPYING	…
Dockerfile	…
Makefile	…
Makefile.include	rework OPTFLAGS, add DBGFLAGS (so it's easier to just replace -O3 to -Os for building bootloader)	9 years ago
README.md	bootloader autobuild in docker	9 years ago
bootloader-docker-build.sh	use OPTFLAGS=-Os for bootloader docker build	9 years ago
buttons.c	…
buttons.h	…
firmware-docker-build.sh	bootloader autobuild in docker	9 years ago
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	fix usage of inline/static	9 years ago

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.