1
0
mirror of https://github.com/trezor/trezor-firmware.git synced 2024-11-16 04:29:08 +00:00
trezor-firmware/core/embed/bootloader_ci
2024-10-07 11:39:09 +02:00
..
.changelog.d feat(core): add basic support for STM32U5 2024-02-29 23:05:56 +01:00
.towncrier.template.md docs(core+legacy): use towncrier for generating CHANGELOG.md 2021-07-21 14:27:20 +02:00
bootloader_flash.jlink
bootui.c feat(core): introduce new display drivers 2024-05-17 09:17:37 +02:00
bootui.h
CHANGELOG.md docs(core+legacy): use towncrier for generating CHANGELOG.md 2021-07-21 14:27:20 +02:00
CHANGELOG.unreleased docs(core+legacy): use towncrier for generating CHANGELOG.md 2021-07-21 14:27:20 +02:00
header.S refactor(core): extract monotonic version to model specific headers 2024-09-03 13:07:34 +02:00
icon_done.h feat(core): icon and images using new format 2022-09-29 21:50:10 +02:00
icon_fail.h feat(core): icon and images using new format 2022-09-29 21:50:10 +02:00
icon_install.h feat(core): icon and images using new format 2022-09-29 21:50:10 +02:00
icon_welcome.h feat(core): icon and images using new format 2022-09-29 21:50:10 +02:00
icon_wipe.h feat(core): icon and images using new format 2022-09-29 21:50:10 +02:00
main.c refactor(core): improve random_delays api 2024-10-07 11:39:09 +02:00
messages.c refactor(core): streamline layout definitions 2024-09-27 09:49:20 +02:00
messages.h feat(core): prevent installing and running of incompatible firmware, prevent bootloader downgrade 2023-01-12 15:38:36 +01:00
protob
README.md
towncrier.toml docs(core+legacy): use towncrier for generating CHANGELOG.md 2021-07-21 14:27:20 +02:00
version_check.c fix(core): fix bootloader_ci production build 2024-09-18 08:27:32 +02:00
version_check.h fix(core): fix bootloader_ci production build 2024-09-18 08:27:32 +02:00
version.h refactor(core): extract monotonic version to model specific headers 2024-09-03 13:07:34 +02:00

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.