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 49691c2436
fix demo
8 years ago
bootloader use __asm__ instead of asm 8 years ago
demo fix demo 8 years ago
firmware disable ECIES 8 years ago
gen
gitian
vendor update submodule 8 years ago
.gitignore
.gitmodules
.travis.yml
COPYING
Dockerfile use the latest ubuntu lts in docker build 8 years ago
Makefile add make vendor 8 years ago
Makefile.include fix bugs in debug 8 years ago
README.md update readme 8 years ago
bootloader-docker-build.sh use OPTFLAGS=-Os for bootloader docker build 8 years ago
buttons.c
buttons.h
firmware-docker-build.sh bootloader autobuild in docker 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
oled.h
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.