mirror of
https://github.com/trezor/trezor-firmware.git
synced 2024-12-31 18:40:56 +00:00
b5fa8a266a
Having CoinType using the protobuf structures has several disadvantages. - We always need to change trezor-common if we need a new field (like bech32 prefix) - Every time Trezor initializes it sends all this information out and nobody cares. - The protobuf structures add storage overhead due to their fixed size. I also removed most of the `has_` fields except for forkid: - `has_segwit` was merged with segwit - `has_coin_shortcut` can be replaced by test for NULL if necessary. The fields were reordered for better padding. |
||
|---|---|---|
| bootloader | ||
| demo | ||
| fastflash | ||
| firmware | ||
| gen | ||
| gitian | ||
| vendor | ||
| .gitignore | ||
| .gitmodules | ||
| .travis.yml | ||
| build-bootloader.sh | ||
| build-firmware.sh | ||
| buttons.c | ||
| buttons.h | ||
| COPYING | ||
| Dockerfile | ||
| layout.c | ||
| layout.h | ||
| Makefile | ||
| Makefile.include | ||
| memory_app_0.0.0.ld | ||
| memory_app_1.0.0.ld | ||
| memory_app_fastflash.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 | ||
| startup.s | ||
| timer.c | ||
| timer.h | ||
| util.c | ||
| util.h | ||
TREZOR Firmware
How to build TREZOR firmware?
- Install Docker
git clone https://github.com/trezor/trezor-mcu.gitcd trezor-mcu./build-firmware.sh TAG(where TAG is v1.5.0 for example, if left blank the script builds latest commit in master branch)
This creates file build/trezor-TAG.bin and prints its fingerprint and size at the end of the build log.
How to build TREZOR bootloader?
- Install Docker
git clone https://github.com/trezor/trezor-mcu.gitcd trezor-mcu./build-bootloader.sh TAG(where TAG is bl1.3.2 for example, if left blank the script builds latest commit in master branch)
This creates file build/bootloader-TAG.bin and prints its fingerprint and size at the end of the build log.
How to get fingerprint of firmware signed and distributed by SatoshiLabs?
- Pick version of firmware binary listed on https://wallet.trezor.io/data/firmware/releases.json
- Download it:
wget -O trezor.signed.bin https://wallet.trezor.io/data/firmware/trezor-1.3.6.bin - Compute fingerprint:
tail -c +257 trezor.signed.bin | sha256sum
Step 3 should produce the same sha256 fingerprint like your local build (for the same version tag). Firmware has a special header (of length 256 bytes) holding signatures themselves, which must be avoided while calculating the fingerprint, that's why tail command has to be used.