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
matejcik b0e879b30e
docker: update build scripts and instructions to fix Docker emulator (#419)
6 years ago
bootloader use env where possible 6 years ago
demo demo: fix crypto call 6 years ago
emulator
firmware reset: don't show internal entropy when no_backup is set 6 years ago
gen
gitian
script docker: update build scripts and instructions to fix Docker emulator (#419) 6 years ago
vendor firmware: introduce seedless setup (aka no_backup) 6 years ago
.gitignore
.gitmodules
.travis.yml travis: trying anoter trick 6 years ago
COPYING
Dockerfile docker: update build scripts and instructions to fix Docker emulator (#419) 6 years ago
Dockerfile.emulator docker: quick fix of Dockerfiles 6 years ago
Makefile re-enable WebUSB 6 years ago
Makefile.include fix Clang compile issue with unicode literals 6 years ago
Pipfile travis: move everything into pipenv, update to python 3.6 6 years ago
Pipfile.lock travis: move everything into pipenv, update to python 3.6 6 years ago
README.md docker: update build scripts and instructions to fix Docker emulator (#419) 6 years ago
build.sh docker: update build scripts and instructions to fix Docker emulator (#419) 6 years ago
buttons.c
buttons.h
layout.c
layout.h
memory.c
memory.h
memory.ld
memory_app_0.0.0.ld
memory_app_1.0.0.ld
memory_app_fastflash.ld
oled.c
oled.h
rng.c
rng.h
serialno.c
serialno.h
setup.c
setup.h
shell.nix nix: use gcc-arm-embedded-7 package in shell.nix 6 years ago
startup.s
supervise.c
supervise.h
timer.c
timer.h
usb21_standard.c
usb21_standard.h re-enable WebUSB 6 years ago
util.c
util.h
webusb.c firmware: don't use WebUSB landing page for firmware, it's annoying 6 years ago
webusb.h firmware: don't use WebUSB landing page for firmware, it's annoying 6 years ago
webusb_defs.h re-enable WebUSB 6 years ago
winusb.c re-enable WebUSB 6 years ago
winusb.h re-enable WebUSB 6 years ago
winusb_defs.h re-enable WebUSB 6 years ago

README.md

TREZOR One Bootloader and Firmware

Build Status gitter

https://trezor.io/

How to build the TREZOR bootloader, firmware and emulator

Ensure that you have Docker installed. You can follow Docker's installation instructions.

Clone this repository:

git clone https://github.com/trezor/trezor-mcu.git`
cd trezor-mcu

Use the build.sh command to build the images.

  • to build bootloader 1.6.0 and firmware 1.7.0:
    ./build.sh bl1.6.0 v1.7.0
    
  • to build latest firmware from master:
    ./build.sh
    
  • to build the emulator from master:
    ./build.sh EMU
    
  • to build the emulator for version 1.7.0:
    ./build.sh EMU v1.7.0
    

Build results are stored in the build/ directory. File bootloader-<tag>.bin represents the bootloader, trezor-<tag>.bin is the firmware image, and trezor-emulator-<tag>.elf is the emulator executable.

You can use TREZOR_OLED_SCALE environment variable to make emulator screen bigger.

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

How to install custom built firmware?

WARNING: This will erase the recovery seed stored on the device! You should never do this on TREZOR that contains coins!

  1. Install python-trezor: pip install trezor (more info)
  2. trezorctl firmware_update -f build/trezor-TAG.bin

Building for development

If you want to build device firmware, make sure you have the GNU ARM Embedded toolchain installed.

  • If you want to build the emulator instead of the firmware, run export EMULATOR=1 TREZOR_TRANSPORT_V1=1
  • If you want to build with the debug link, run export DEBUG_LINK=1. Use this if you want to run the device tests.
  • When you change these variables, use script/setup to clean the repository
  1. To initialize the repository, run script/setup
  2. To build the firmware or emulator, run script/cibuild

If you are building device firmware, the firmware will be in firmware/trezor.bin.

You can launch the emulator using firmware/trezor.elf. To use trezorctl with the emulator, use trezorctl -t udp (for example, trezorctl -t udp get_features).

If trezorctl -t udp appears to hang, make sure you have run export TREZOR_TRANSPORT_V1=1.