1
0
mirror of https://github.com/trezor/trezor-firmware.git synced 2024-10-19 14:30:31 +00:00
trezor-firmware/core/embed/bootloader_ci
2023-09-11 14:36:11 +02:00
..
.changelog.d fix(core): fix bootloader_ci startup, remove unused function from limited_util.s 2023-09-11 14:36:11 +02:00
.towncrier.template.md
bootloader_flash.jlink
bootui.c refactor(core): remove unused C display_icon and display_loader functions 2023-04-25 10:28:33 +02:00
bootui.h
CHANGELOG.md
CHANGELOG.unreleased
header.S feat(core): prevent installing and running of incompatible firmware, prevent bootloader downgrade 2023-01-12 15:38:36 +01: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): add abstraction over flash memory layout 2023-07-25 10:25:20 +02:00
memory.ld feat(core): Copy firmware image header to bootloader RAM to be able to skip directly to firmware install, jumping from firmware to bootloader 2023-09-11 14:36:11 +02:00
messages.c refactor(core): add abstraction over flash memory layout 2023-07-25 10:25: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
startup.s fix(core): fix bootloader_ci startup, remove unused function from limited_util.s 2023-09-11 14:36:11 +02:00
towncrier.toml
version.h

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.