arno/trezor-firmware
1
0
Fork 0
mirror of https://github.com/trezor/trezor-firmware.git synced 2024-11-23 07:58:09 +00:00
Code Issues Releases Wiki Activity
251 Commits 353 Branches 205 Tags 210 MiB
Python 34.6%
C 33.7%
Rust 29.4%
Nix 0.6%
C++ 0.4%
Other 1.1%
73e7d82e3f
Go to file
Jochen Hoenicke 73e7d82e3f Allow initialize() to abort PIN wait
2016-05-28 16:24:14 +02:00
bootloader Faster flashing, smoother animation. 2016-05-25 00:41:13 +02:00
demo
firmware Allow initialize() to abort PIN wait 2016-05-28 16:24:14 +02:00
gen fix python shebangs 2016-05-24 20:31:01 +02:00
gitian
vendor
.gitignore
.gitmodules
.travis.yml
bootloader-docker-build.sh
buttons.c
buttons.h
COPYING
Dockerfile
firmware-docker-build.sh
firmware-fingerprint.sh
layout.c
layout.h
Makefile fix ar usage 2016-05-24 20:27:45 +02:00
Makefile.include fix ar usage 2016-05-24 20:27:45 +02:00
memory_app_0.0.0.ld
memory_app_1.0.0.ld
memory.c
memory.h
memory.ld
oled.c
oled.h
README.md
rng.c
rng.h
serialno.c
serialno.h
setup.c
setup.h
util.c
util.h

README.md

TREZOR Firmware

Build Status gitter

http://bitcointrezor.com/

How to build TREZOR firmware?

  1. Install Docker
  2. git clone https://github.com/trezor/trezor-mcu.git
  3. cd trezor-mcu
  4. ./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?

  1. Install Docker
  2. git clone https://github.com/trezor/trezor-mcu.git
  3. cd trezor-mcu
  4. ./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?

  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 (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.