From b56cf9246bac921c93ea7307eea2d8fc511f6a2a Mon Sep 17 00:00:00 2001 From: Pavol Rusnak Date: Tue, 28 Apr 2015 21:20:51 +0200 Subject: [PATCH] fix last commit --- README.rst | 2 +- firmware-docker-build.sh | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/README.rst b/README.rst index 5b0929d..9ba8eba 100644 --- a/README.rst +++ b/README.rst @@ -11,7 +11,7 @@ How to build Trezor firmware? 3. ``cd trezor-mcu`` 4. ``./firmware-docker-build.sh TAG`` (where TAG is v1.3.2 for example, if left blank the script builds latest commit) -This creates trezor.bin in current directory and prints its fingerprint at the last line of the build log. +This creates file ``output/trezor-TAG.bin`` and prints its fingerprint at the last line of the build log. How to get fingerprint of firmware signed and distributed by SatoshiLabs? ------------------------------------------------------------------------- diff --git a/firmware-docker-build.sh b/firmware-docker-build.sh index d734404..f705c8f 100755 --- a/firmware-docker-build.sh +++ b/firmware-docker-build.sh @@ -11,7 +11,7 @@ docker run -t -v $(pwd)/output:/output $IMAGETAG /bin/sh -c "\ make && \ cd firmware && \ make && \ - cp trezor.bin /output/trezor-$FIRMWARETAG.bin" + cp trezor.bin /output/trezor-$FIRMWARETAG.bin" echo "---------------------" echo "Firmware fingerprint:"