mirror of
https://github.com/trezor/trezor-firmware.git
synced 2025-03-26 04:55:43 +00:00
![]() This patch adds calls to usbPoll in the progress callback. This should address #98. We call usbDelay instead of Poll, to call usbd_poll several times. Otherwise it would only handle one event instead of handling all events that were pending so far. The ugly magic number 5 is a guess. Note that we also need to set usbTiny, so that we don't recursively process messages. Since we don't know whether usbTiny is set, we need to store the old value (especially true for u2f). This fix also relies on another fix in libopencm3. |
||
---|---|---|
bootloader | ||
demo | ||
firmware | ||
gen | ||
gitian | ||
vendor | ||
.gitignore | ||
.gitmodules | ||
.travis.yml | ||
bootloader-docker-build.sh | ||
buttons.c | ||
buttons.h | ||
ChangeLog | ||
COPYING | ||
Dockerfile | ||
firmware-docker-build.sh | ||
firmware-fingerprint.sh | ||
layout.c | ||
layout.h | ||
Makefile | ||
Makefile.include | ||
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 |
TREZOR Firmware
How to build TREZOR firmware?
- Install Docker
git clone https://github.com/trezor/trezor-mcu.git
cd trezor-mcu
./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?
- Install Docker
git clone https://github.com/trezor/trezor-mcu.git
cd trezor-mcu
./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?
- Pick version of firmware binary listed on https://wallet.mytrezor.com/data/firmware/releases.json
- Download it:
wget -O trezor.signed.bin https://wallet.mytrezor.com/data/firmware/trezor-1.3.6.bin
./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.