arno
/
trezor-firmware
mirror of https://github.com/trezor/trezor-firmware.git
1
0
Fork 0
Code Issues Releases Wiki Activity
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.
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '72dc8f57e8'
${ noResults }
trezor-firmware/core/embed/bootloader_ci
History
tychovrahe 8815e764d2
feat(core): add support for STM32U585 		4 months ago
..
.changelog.d feat(core): add basic support for STM32U5 4 months ago
.towncrier.template.md
…
CHANGELOG.md
…
CHANGELOG.unreleased
…
README.md
…
bootloader_flash.jlink
…
bootui.c refactor(core/embed): introduce display_utils.c 5 months ago
bootui.h
…
header.S feat(core): prevent installing and running of incompatible firmware, prevent bootloader downgrade 1 year ago
icon_done.h feat(core): icon and images using new format 2 years ago
icon_fail.h feat(core): icon and images using new format 2 years ago
icon_install.h feat(core): icon and images using new format 2 years ago
icon_welcome.h feat(core): icon and images using new format 2 years ago
icon_wipe.h feat(core): icon and images using new format 2 years ago
main.c chore(core, legacy, storage): refactor flash drivers 4 months ago
memory_stm32f4.ld chore(core): refactor boot_args 4 months ago
memory_stm32u5a.ld chore(core): use cortex-m33 stack protection 4 months ago
memory_stm32u58.ld feat(core): add support for STM32U585 4 months ago
messages.c fix(core): fix quadword-only storage 5 months ago
messages.h feat(core): prevent installing and running of incompatible firmware, prevent bootloader downgrade 1 year ago
protob
…
startup_stm32f4.s feat(core): add basic support for STM32U5 4 months ago
startup_stm32u5.s chore(core): use cortex-m33 stack protection 4 months ago
towncrier.toml
…
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.