Trezor firmware

This commit fixes a small but real bug in the Trezor emulator (the desktop/Unix version used for testing, not the real hardware wallet). When the emulator tries to shut down a MicroPython task, it previously ignored whether the internal 'push call' operation succeeded. If that operation failed, the code would still try to switch to the task, potentially leaving the emulator in an inconsistent or hung state. The fix adds an explicit error shutdown if the push fails. It is a hardening fix rather than a clear exploitable vulnerability, and it only affects the Unix emulator build.

This is a code cleanup change in Trezor's embedded firmware. It moves display de-initialization logic into a new compatibility helper file and renames a clock-setting function to make the code clearer. There is no direct evidence in the commit that this fixes an active security vulnerability; it appears to be a refactoring to remove a circular dependency between system startup code and the display driver.

This commit fixes a build or runtime problem in the Trezor hardware wallet's production-test firmware when it is compiled for the software emulator. It wraps real hardware calls (deinitializing the Bluetooth module and UART, resetting the NRF chip, and entering direct test mode) inside a check that skips them on the emulator. There is no direct user security impact; it is a build/test-harness fix.

This commit only adds Rust compiler directives to silence warnings about unused macros and imports. It does not change any program behavior, fix a bug, or address a security issue.

This commit simply adds a new build output folder named 'build-xtask' to the .gitignore file in the Trezor firmware repository. A .gitignore file tells Git which files and folders to ignore and not track in version control. This change has no effect on the actual firmware code, device behavior, or security of the product. It is a routine housekeeping change for developers.

This commit fixes a type mismatch in the Trezor firmware emulator's bootloader code. The FIRMWARE_START symbol was declared as a pointer to bytes (uint8_t*) but was being assigned a raw memory address value. On 64-bit emulator builds this could lead to incorrect memory handling or crashes because the sizes and interpretations of the two types differ. The fix changes the symbol to a plain integer address type (uintptr_t), which is the correct way to store raw memory addresses in portable C code. This change only affects the emulator (software simulation), not real Trezor hardware.

This commit is a code cleanup that moves a panic-screen function declaration from one header file to another and updates which files include it. It also fixes a minor stub function in the Unix emulator so it now returns the expected value. There is no indication this fixes a security vulnerability or changes device behavior in a way attackers could exploit.

This commit is a code cleanup that changes how a special testing-only feature is enabled in Trezor firmware. Previously, the feature was enabled whenever Python optimization was disabled (PYOPT == 0). Now it is enabled through a dedicated flag called USE_OPTIGA_TESTING. The feature itself—raising the Optiga security event counter to maximum—remains a debug/testing capability and is not intended for production. The change does not remove the feature; it only changes the build condition that turns it on. There is no direct evidence in the commit that this fixes an active security vulnerability.

This commit simply moves a source file from one directory to another within the Trezor firmware build system. The actual code content is unchanged. There is no security-relevant change visible in the diff.

This commit is a straightforward code cleanup: it changes the way source files locate shared header files from absolute-style paths to relative paths. There is no change to program logic, no bug fix, and no security-relevant behavior.

This commit is a code reorganization: it moves the code that initializes the hardware security boundary (TrustZone) from one internal system module into a dedicated security module, and makes sure every startup program calls it at the very beginning. The actual security settings look unchanged from the diff. It is not a fix for a known bug or vulnerability, but it changes where and when sensitive hardware is configured, which could matter for security if the move accidentally changes behavior or ordering.

This commit adds small adapter functions (called trampolines) so that two existing functions are called with the correct number and type of arguments when passed to a task scheduler. It is a code-correctness improvement for the Unix emulator build of the Trezor firmware and does not introduce obvious security flaws.

This commit moves a security setting for the screen framebuffer from a per-app switching routine to a one-time enable during system startup. It makes the framebuffer permanently accessible to less-privileged code, rather than toggling access on and off as apps start and stop. The change is described by the developer as a refactor and has no changelog entry. On its own it looks like a deliberate design relaxation, not an accidental bug, but it removes a layer of isolation that previously restricted unprivileged tasks from touching display memory.

This is a code cleanup and build-fix change for the Trezor firmware bootloader. It moves the bootloader's binary header definition from a shared security file into a bootloader-specific file, and fixes the build configuration for a special continuous-integration (CI) bootloader variant. There is no direct evidence in the commit that this fixes an exploitable security vulnerability; it appears to be a refactoring and build repair.

This commit changes one line in the Trezor firmware emulator's bootloader simulation. It replaces a function that writes a single 32-bit word to flash storage with a more general 'write data' function. The change appears to be a code cleanup or portability fix for emulator behavior, not a security patch for a real device vulnerability. There is no indication in the commit that this fixes a security issue.

This commit is a code cleanup that moves a small data table (the 'coreapp header') out of the processor's interrupt vector table file and into its own dedicated file. It does not change what the firmware does, only where the table is defined in the source code. There is no indication this fixes or introduces a security problem.

This commit adds software 'stubs' that let the Trezor firmware emulator (a simulated version used for development/testing) compile and run on a regular computer. These stubs replace real hardware security features—such as tamper detection, secure memory, hardware encryption, and the secure chip (Optiga)—with no-op or always-success placeholders. There is no indication this code is meant for real Trezor devices, and the commit message explicitly frames it as emulator-only driver implementation. It does not appear to be a security fix or vulnerability patch.

This commit updates the hardware wallet's build configuration files (linker scripts) so they work with a newer linker tool called LLD. The changes replace a non-standard memory permission flag 'wal' with the standard 'rw' flag, and change how empty placeholder sections reserve stack/heap/header space. There is no direct evidence this fixes an exploitable security bug; it appears to be a build-tool compatibility cleanup. However, because linker scripts control where code and data live in memory, any mistake could theoretically affect memory protections, so the change warrants careful review.

This commit removes an unused internal field called transition_out from the user-interface event-handling code in the Trezor firmware. It also deletes the helper functions that set and read that field, and updates the two places that used to call those helpers. There is no change to how the device behaves; it is purely a cleanup of dead code.

This commit only changes the capitalization and punctuation of on-screen text labels for the Cardano cryptocurrency feature in Trezor firmware. For example, 'Key hash' becomes 'key hash' and a credential description template gains a colon on some device layouts. It also updates the corresponding automated UI test snapshots. There is no security-relevant code change.

This is a routine automated update by Dependabot that raises the minimum allowed version of a Python template library called Mako from 1.0.7 to 1.3.11. The change only affects build/development dependency files and does not alter Trezor firmware source code. There is no direct evidence in the commit that this fixes a security problem, but keeping dependencies current is generally good maintenance practice.

This commit adds a new mechanism for passing small data structures (called 'startup arguments') from one boot stage to the next inside Trezor hardware wallets. It changes how the device hands control from the boardloader/bootloader to the next firmware stage. The change is a feature addition, not a fix for a known bug or vulnerability. There is no evidence in the commit message or diff that this is a security patch or that it addresses a disclosed issue.

This commit adds a Python 'with' statement feature to Trezor's Rust-based UI layout objects. It lets code explicitly clean up a UI layout when leaving a block, and raises an error if someone tries to use an already-destroyed layout. There is no direct security bug visible in the change; it is a feature addition for explicit resource management.

This commit only adds a longer test case for an existing Ethereum transaction-signing test. It does not change any firmware, application, or library code that users run. It only changes test files and their expected output fingerprints, so it has no direct security impact on the product.

This commit is a routine code cleanup in the Rust portions of the Trezor firmware. It fixes compiler lint warnings by modernizing syntax (for example replacing manual remainder checks with built-in methods, adding explicit lifetime markers, and simplifying match statements). There is no indication it fixes a security bug or changes product behavior.