arno/trezor-firmware
1
0
Fork 0
mirror of https://github.com/trezor/trezor-firmware.git synced 2024-11-18 05:28:40 +00:00
Code Issues Releases Wiki Activity
da71f7c45d
trezor-firmware/README.md
Pavol Rusnak cc01b86ab7
update readme
2017-01-10 15:14:29 +01:00

1.6 KiB
Raw Blame History

TREZOR Firmware

Build Status gitter

https://trezor.io/

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.trezor.io/data/firmware/releases.json
  2. Download it: wget -O trezor.signed.bin https://wallet.trezor.io/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.