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 1d3c7ee3f2
cleanup Waking up screen usage
9 years ago
bootloader move submodules to vendor subdirectory 9 years ago
demo move submodules to vendor subdirectory 9 years ago
firmware cleanup Waking up screen usage 9 years ago
gen move submodules to vendor subdirectory 9 years ago
vendor cleanup Waking up screen usage 9 years ago
.gitignore
.gitmodules move submodules to vendor subdirectory 9 years ago
.travis.yml fix travis build 9 years ago
COPYING
Dockerfile include libopencm3 as submodule 9 years ago
Makefile
Makefile.include move submodules to vendor subdirectory 9 years ago
README.md
buttons.c
buttons.h
firmware-docker-build.sh move submodules to vendor subdirectory 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 move submodules to vendor subdirectory 9 years ago
setup.h
util.c
util.h

README.md

TREZOR Firmware

Build Status

http://bitcointrezor.com/

How to build TREZOR firmware?

  1. Install Docker (from docker.com or from your distribution repositories)
  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 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.