arno/trezor-firmware
1
0
Fork 0
mirror of https://github.com/trezor/trezor-firmware.git synced 2024-11-23 16:08:17 +00:00
Code Issues Releases Wiki Activity
220 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%
d41e46f842
Go to file
Pavol Rusnak d41e46f842 Merge pull request #81 from jhoenicke/master 
Move public key recovery (verify) to trezor-crypto
2016-04-27 18:22:11 +02:00
bootloader adapt the reorder of hash_final functions 2016-04-26 11:53:58 +02:00
demo
firmware Move public key recovery (verify) to trezor-crypto 2016-04-27 18:10:21 +02:00
gen
gitian
vendor adapt the reorder of hash_final functions 2016-04-26 11:53:58 +02:00
.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
Makefile.include ed25519 support 2016-04-22 18:22: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

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.