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 ed3fbf901c
passphrase protection -> encryption (in dialog)
10 years ago
bootloader rework layoutProgress functions 10 years ago
demo
firmware passphrase protection -> encryption (in dialog) 10 years ago
gen
trezor-common@201b66a559 introduce homescreen 10 years ago
trezor-crypto@54aa5a4482 enable OP_RETURN 10 years ago
trezor-qrenc@1da1cedfd6 enable OP_RETURN 10 years ago
.gitignore
.gitmodules
COPYING
Dockerfile rework docker build script 10 years ago
Makefile
Makefile.include
README.rst
buttons.c
buttons.h
firmware-docker-build.sh rework docker build script 10 years ago
firmware-fingerprint.sh
layout.c rework layoutProgress functions 10 years ago
layout.h rework layoutProgress functions 10 years ago
memory.c use hdnode_private_ckd_cached where appropriate 10 years ago
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.rst

TREZOR Firmware
===============

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``

This creates trezor.bin in current directory 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.

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.