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 8372504238
show home screen on Initialize
9 years ago
bootloader update bootloader and demo to new usb api 9 years ago
demo update bootloader and demo to new usb api 9 years ago
firmware show home screen on Initialize 9 years ago
gen
trezor-common@3fc31bfe9c update trezor-common 9 years ago
trezor-crypto@cbbc0bdc71 update trezor-crypto 9 years ago
trezor-qrenc@1183aa7146 use -O3 instead of -Os 9 years ago
.gitignore
.gitmodules
.travis.yml gcc-arm-none-eabi is not available in travis yet, install manually 9 years ago
COPYING
Dockerfile simplify Dockerfile, add travis CI 9 years ago
Makefile
Makefile.include gcc-arm-none-eabi is not available in travis yet, install manually 9 years ago
README.md simplify Dockerfile, add travis CI 9 years ago
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
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.