trezor-mcu

Go to file

Pavol Rusnak 960c665aac update protobuf, require address for verifymsg		2014-11-15 02:00:07 +01:00
bootloader	use stack protector in bootloader	2014-10-30 17:57:33 +01:00
demo	update trezor-crypto	2014-10-30 01:38:40 +01:00
firmware	update protobuf, require address for verifymsg	2014-11-15 02:00:07 +01:00
gen	…
trezor-common@e675d5fd76	update protobuf, require address for verifymsg	2014-11-15 02:00:07 +01:00
trezor-crypto@f6560c7d13	update trezor-crypto	2014-10-30 01:38:40 +01:00
trezor-qrenc@f12996741c	start implementing EncryptMessage/DecryptMessage	2014-10-22 19:53:25 +02:00
.gitignore	bootloader source code	2014-10-23 18:09:41 +02:00
.gitmodules	implement GetAddress.show_display	2014-08-13 11:08:15 +02:00
COPYING	…
Dockerfile	enable stack protector	2014-07-31 19:44:03 +02:00
Makefile	…
Makefile.include	implement GetAddress.show_display	2014-08-13 11:08:15 +02:00
README.rst	update README	2014-08-20 10:46:48 +02:00
buttons.c	…
buttons.h	…
firmware-docker-build.sh	simplify firmware-docker-build.sh	2014-07-07 16:59:37 +02:00
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	new trezor-crypto, uint32_t -> size_t	2014-07-17 19:58:19 +02:00
rng.h	new trezor-crypto, uint32_t -> size_t	2014-07-17 19:58:19 +02:00
serialno.c	enable stack protector	2014-07-31 19:44:03 +02:00
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.