You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Go to file
Pavol Rusnak cda9ae4b29
change version description in bootloader
8 years ago
bootloader change version description in bootloader 8 years ago
demo
firmware Update coins.c for Zcash mainnet (#111) 8 years ago
gen add gitlab to u2f_knownapps 8 years ago
gitian
vendor fix unaligned access in serialno; update trezor-crypto 8 years ago
.gitignore
.gitmodules
.travis.yml
COPYING
Dockerfile add python-ecdsa dependency 8 years ago
Makefile
Makefile.include
README.md update readme to reflect new mytrezor location 8 years ago
bootloader-docker-build.sh
buttons.c
buttons.h
firmware-docker-build.sh sign firmware inside docker container 8 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 Faster SPI communication 8 years ago
oled.h
rng.c
rng.h
serialno.c fix unaligned access in serialno; update trezor-crypto 8 years ago
serialno.h
setup.c Faster SPI communication 8 years ago
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://wallet.mytrezor.com/data/firmware/releases.json
  2. Download it: wget -O trezor.signed.bin https://wallet.mytrezor.com/data/firmware/trezor-1.3.6.bin
  3. ./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.