mirror of https://github.com/trezor/trezor-firmware.git synced 2024-11-10 09:39:00 +00:00

History

cepetr 3336e3902f feat(core): introduce new display drivers [no changelog]		2024-05-17 09:17:37 +02:00
..
.changelog.d	feat(core): add basic support for STM32U5	2024-02-29 23:05:56 +01:00
.towncrier.template.md
bootloader_flash.jlink	core/bootloader_ic: introduce CI bootloader for TT device tests (#1182 )	2020-08-21 14:39:56 +02:00
bootui.c	feat(core): introduce new display drivers	2024-05-17 09:17:37 +02:00
bootui.h	fix(core): remove unused stuff from bootloader_ci	2021-03-04 17:01:01 +01:00
CHANGELOG.md
CHANGELOG.unreleased	docs(core+legacy): use towncrier for generating CHANGELOG.md	2021-07-21 14:27:20 +02:00
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
icon_fail.h
icon_install.h
icon_welcome.h
icon_wipe.h
main.c	feat(core): introduce new display drivers	2024-05-17 09:17:37 +02:00
memory_stm32f4.ld	feat(core): introduce new display drivers	2024-05-17 09:17:37 +02:00
memory_stm32u5a.ld	feat(core): use confidential section for confidential and sensitive data	2024-04-05 18:54:30 +02:00
memory_stm32u58.ld	feat(core): use confidential section for confidential and sensitive data	2024-04-05 18:54:30 +02:00
messages.c	fix(core): fix quadword-only storage	2024-02-20 09:37:28 +01: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_stm32f4.s	feat(core): add basic support for STM32U5	2024-02-29 23:05:56 +01:00
startup_stm32u5.s	feat(core): use confidential section for confidential and sensitive data	2024-04-05 18:54:30 +02:00
towncrier.toml
version.h	chore(core): bootloader_ci - decouple file links from original bootloader	2021-01-27 23:43:38 +01:00

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.