History

cepetr c4c571d837 chore(core): refactor boot_args [no changelog]		4 months ago
..
.changelog.d	…
.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	…
README.md	…
bootloader_flash.jlink	core/bootloader_ic: introduce CI bootloader for TT device tests (#1182 )	4 years ago
bootui.c	…
bootui.h	…
header.S	…
icon_done.h	feat(core): icon and images using new format	2 years ago
icon_fail.h	…
icon_install.h	…
icon_welcome.h	…
icon_wipe.h	feat(core): icon and images using new format	2 years ago
main.c	…
memory_stm32f4.ld	…
memory_stm32u5a.ld	chore(core): refactor boot_args	4 months ago
messages.c	…
messages.h	…
protob	core/bootloader_ic: introduce CI bootloader for TT device tests (#1182 )	4 years ago
startup_stm32f4.s	…
startup_stm32u5.s	…
towncrier.toml	…
version.h	chore(core): bootloader_ci - decouple file links from original bootloader	3 years ago

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.