Trezor firmware

This commit simply removes an unused Python import (`shlex`) from five build scripts. It does not change any program logic, behavior, or security boundary. It is a routine code cleanup with no security relevance.

This commit changes the text shown on the bottom home bar of a Trezor hardware wallet screen. The boot screen now says 'Unlock' instead of 'Tap to start', matching the lock screen wording. It is a cosmetic/user-interface consistency fix with no security relevance.

This commit simply deletes an unused on-screen text label ('Tap to start') and its associated translation key from the Trezor firmware source code. No security issue is present; it is a routine cleanup change.

This commit changes build scripts so that a file providing printf-style debugging output is only included in non-production builds. It is a build-system cleanup to fix a nightly CI failure, not a security fix. There is no indication it addresses a vulnerability or changes runtime behavior of shipped devices.

This commit simply adds a missing firmware version number (1.7.0) to a list of released versions in a JSON file. It does not change any code, fix any bug, or introduce any security issue. It is a routine bookkeeping change.

This commit simply updates a timestamp and a matching version number used to track the latest released Ethereum token/chain definitions. There is no code logic change, no bug fix, and no security-related content.

This commit only updates documentation: it moves changelog entries for firmware version 2.9.6 into the published changelog files and deletes the temporary source files. No program code is changed, so this commit by itself cannot introduce or fix a security vulnerability.

This commit simply adds a new digital signature entry to a JSON file that records approved language translation packages for Trezor devices. There is no code change, no bug fix, and no apparent security issue. It appears to be routine release housekeeping.

This commit simply adds a new firmware version number (2.9.6) and the device model it supports (T3W1) to a release metadata file. There are no code changes, no bug fixes, and no security-related content in the diff.

This commit replaces two binary firmware files for the Trezor T3W1 hardware wallet's security monitor (secmon) with newer versions built from secmon v1.0.5. The actual code changes are not visible because the files are binary blobs. There is no claim in the commit message that this fixes a security vulnerability, and no independent references were provided. On its own, this looks like a routine component update.

This commit fixes how the Trezor hardware wallet resets its Tropic secure chip during startup. The change makes sure the chip-select line is pulled low before power is toggled and released afterward, which is needed for a clean reset. There is no direct evidence this is a security vulnerability rather than a reliability bug, but improper reset handling of a security chip could in theory lead to an unstable or unpredictable secure state.

This commit changes the order of two cleanup steps when a Tropic secure chip hits an alarm mode during a retry. Previously the code de-initialized the driver before resetting the chip; now it resets the chip first, then de-initializes, then re-initializes. The change is defensive and likely fixes a bug where the retry/reset sequence could leave the chip or driver in an inconsistent state. There is no claim in the commit that this is a security vulnerability, and no external references are provided.

This commit is a routine internal refactoring of how the Trezor firmware represents success/error status codes. It introduces a new typed status code (ts_t), helper macros to check it, and a function to convert HAL driver errors into these new codes. There is no change to user-facing behavior, no bug fix, and no security patch.

This commit adds a new set of helper macros for handling error codes inside the Trezor firmware's core runtime library. It is purely a code-structure addition: it defines patterns like 'if something failed, jump to cleanup code and return the error.' There is no bug fix, no behavior change to existing code, and no security vulnerability present in the diff itself.

This commit is a code cleanup in the Trezor firmware. It moves special error-screen functions (for wipe code, too many PIN attempts, install restricted, and device wiped) out of the runtime library (RTL) error-handling module and into a new dedicated 'rsod_special' module. It also removes the 'ensure' macro from a public header. The change is architectural refactoring; it does not appear to fix a security bug or introduce a new vulnerability. The commit message and diff give no indication this is a security patch.

This commit is a routine translation update. It changes translated text strings in Czech, German, Spanish, French, and Portuguese, updates the cryptographic signature that verifies those translations, and refreshes the expected screen hashes used by automated UI tests. There is no code behavior change and no security issue visible in the diff.

This commit adds a new centralized logging system to the Trezor firmware. It is a feature/refactoring change: debug output is routed through a new 'syslog' layer with log levels and filters, and the debug console is now gated behind a compile-time flag. There is no direct evidence in the commit that this fixes a security vulnerability; it appears to be a developer-facing infrastructure improvement.

This commit adds a new developer-only command, `trezorctl set-log-filter`, that lets someone with physical debug access to a Trezor device change which internal log messages are printed. It only works when the device was built with a special debug-console feature enabled, and it does not change how ordinary user operations work. There is no direct evidence in the commit that this creates a security vulnerability, but any new debug command slightly increases the attack surface available to someone who already has debug access.

This commit changes two bootloader linker scripts for Trezor hardware wallets, reducing the alignment padding between code/data sections from 512 bytes down to 4 bytes. The stated purpose is to remove unnecessary padding and save flash space. There is no indication in the commit or supplied references that this fixes a security vulnerability.

This commit replaces Trezor's small, home-grown printf-style string formatter with a more capable third-party library (eyalroz/printf). The change is described as adding 'extended formatting capabilities' and is marked with '[no changelog]'. The new library supports more format specifiers, including the %n specifier, which can write back into caller-provided memory. Trezor's configuration enables %n support. Because this is a low-level runtime component used across bootloader, firmware, kernel, secure monitor, and production-test builds, any bug in the new formatter could have broad consequences. However, the commit itself does not fix a known vulnerability, and there is no vendor statement that this change is security-relevant.

This commit is a straightforward code cleanup: it replaces old-style printf debug messages with a new centralized logging system (LOG_ macros). It also removes some unused non-production debug hooks and switches header include guards to '#pragma once'. There is no change to security logic, cryptography, user-facing behavior, or access controls.

This commit is a code cleanup that replaces the use of a small printf-style formatter (mini_snprintf) with simpler, purpose-built string helpers in the Trezor bootloader and low-level system code. It does not add or remove security features, and there is no direct evidence it fixes a specific vulnerability. The change may reduce the attack surface by removing format-string parsing from some paths, but it also introduces new helper functions whose correctness now matters for safety.

This commit is a small internal cleanup of the Trezor firmware's debug console. It changes the debug-console write function so it returns the number of bytes written (or an error code) instead of returning nothing. It also makes the USB virtual-com-port backend avoid blocking when called from interrupt context. The changes are confined to debug-only code and do not appear to fix a known security vulnerability.

This is a one-line build configuration change in low-level firmware code. It swaps the condition used to decide whether to compile a special secure-mode memory check. The change appears aimed at reducing flash memory usage in board/bootloader builds, not at fixing a security vulnerability. There is no direct evidence in the commit of a security issue.

This commit is a maintenance change to the Trezor firmware's embedded printf library. It adds source attribution comments, unconditionally includes a configuration header, and adds a compile-time guard that blocks printf from being used in production firmware builds. There is no direct evidence in the commit of a security vulnerability being fixed.