Had a serious issue installing V0313 OSX64 using:
% ./trezorctl update trezor.bin.
The message generated by a Trezor device with prior production Trezor firmware v.1.4.0 installed was: Firmware installation aborted. You need to repeat the procedure with the correct firmware.
Effectively, the V0313 supplied "notes.txt" file really needs a step 0 for those not installing the Monero firmware on Trezor device "straight out of its tamper proof box".
The solution was to wipe the Trezor device before the loading Monero firmware. Ended up using the https://github.com/trezor/python-trezor package that has a Python implementation of trezorctl that can be easily inspected for how to apply, e.g. "python-trezor/trezorctl -h".
% python-trezor/trezorctl wipe_device <- Wiped the Trezor device to put it into a ground state prior to a 3-finger "bootloader" mode
% python-trezor/trezorctl firmware_update -f trezor.bin <- Is executed around 5 seconds after a Trezor device is connected into a USB port (to ensure a Trezor has hit steady state) with a Trezor 3-finger "bootloader" death grip prior to releasing the death grip.
From experimentation, I noticed uploading production Trezor firmware had no sensitivity to being previously wiped, for example following worked flawlessly:
% python-trezor/trezorctl firmware_update -u https://wallet.mytrezor.com/data/firmware/trezor-1.3.5.bin
If Trezor firmware files were downloaded locally using a command such as:
% curl -vL https://wallet.mytrezor.com/data/firmware/trezor-X.Y.Z.bin -o trezor-X.Y.Z.bin
It was a requirement to first wipe a functional Trezor device prior to uploading a local firmware file with a command of this form:
% python-trezor/trezorctl firmware_update -f trezor-X.Y.Z.bin
Fingerprints can be verified using piped commands to bitcoin-explorer (bx) *.bin Trezor firmware files, for example:
% tail -c +257 trezor.bin | bx base16-encode | bx sha256
Production Trezor firmware fingerprints are located here for those desiring rollback to production firmware.
Most everything else proceeded as expected. The number of wallet files decreased, no *.keys exist when an external HD device is used. The infamous "refresh" takes around 20 minutes.
However, I have an issue spending funds managed by a Trezor when I have a "password" in addition to my PIN. The wallet seems to think I have no funds to transfer when the balance shows otherwise.
If one is to compile Monero, what passed "make" arguments will cause the resulting "./build/release/bin/monero-wallet-cli" to support the "--hardware-wallet" input option? Not sure if my assumption that the "master" branch is currently the official fork prior to a Trezor merge into monero-project/monero?
Also, are there any details as to were the source to compile the Monero V0313 ./trezor.bin that is a fork of https://github.com/trezor/trezor-mcu?