Go to file

Pavol Rusnak 1e297c68fa cosmetic changes to matrix recovery		8 years ago
bootloader	fix bug when long press of buttons breaks usb communication in bootloader, bump bl version to 1.3.1	8 years ago
demo	…
firmware	cosmetic changes to matrix recovery	8 years ago
gen	New Matrix-based recovery	8 years ago
gitian	…
vendor	use new hdnode_private_ckd_cached API	8 years ago
.gitignore	…
.gitmodules	…
.travis.yml	add webhooks to travis	8 years ago
COPYING	…
ChangeLog	bump version, add changelog	8 years ago
Dockerfile	…
Makefile	timer: Use Cortex-M3 SysTick timers	8 years ago
Makefile.include	cosmetic changes to matrix recovery	8 years ago
README.md	…
bootloader-docker-build.sh	…
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	…
timer.c	timer: Fix non-critical integer overflow (#129 )	8 years ago
timer.h	timer: Fix non-critical integer overflow (#129 )	8 years ago
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://wallet.mytrezor.com/data/firmware/releases.json
Download it: wget -O trezor.signed.bin https://wallet.mytrezor.com/data/firmware/trezor-1.3.6.bin
./firmware-fingerprint.sh trezor.signed.bin

Step 3 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.