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.
trezor-firmware/core/embed/bootloader_ci
Pavol Rusnak b0e0280465
chore: drop obsolete fw_vendor_keys field from Features
3 years ago
..
.changelog.d fix(core): change logic of vendor header comparison 3 years ago
.towncrier.template.md docs(core+legacy): use towncrier for generating CHANGELOG.md 3 years ago
CHANGELOG.md docs(core+legacy): use towncrier for generating CHANGELOG.md 3 years ago
CHANGELOG.unreleased docs(core+legacy): use towncrier for generating CHANGELOG.md 3 years ago
README.md
bootloader_flash.jlink
bootui.c
bootui.h
header.S
icon_done.h
icon_fail.h
icon_install.h
icon_welcome.h
icon_wipe.h
main.c fix(core): change logic of vendor header comparison 3 years ago
memory.ld
messages.c chore: drop obsolete fw_vendor_keys field from Features 3 years ago
messages.h
protob
startup.s
towncrier.toml docs(core+legacy): use towncrier for generating CHANGELOG.md 3 years ago
version.h

README.md

Bootloader for CI device tests

This bootloader always runs into bootloader mode, waits for firmware to be uploaded, then runs the firmware.

Storage is not erased. If you wish to erase storage you can send WipeDevice message to the bootloader.

All user interaction is removed (no clicking or confirmations required) so that it can be used in an automated way for tests.

The bootloader will run any firmware that looks "sane" (good header, hashes), but does not check any trust flags.

Firmware must be compiled with PRODUCTION=0 because otherwise it would replace the bootloader and lock device.