Trezor firmware

This commit is a routine internal cleanup that switches how Trezor's firmware defines built-in MicroPython object types. It replaces older, manually-written type structures with a newer macro provided by the upstream MicroPython project. There is no user-visible change, no bug fix, and no security patch in the diff.

This commit is a straightforward internal code refactor. It adds a small C wrapper file so that Rust code can call two specific internal MicroPython functions that are declared as static/inline in headers. There is no user-facing change, no bug fix, and no security-relevant behavior change visible in the diff.

This commit updates Trezor firmware code to match a renamed and slightly changed version of the micropython uzlib decompression library. It renames types (e.g., `uzlib_uncomp` to `uzlib_uncomp_t`), replaces old return-code constants (`TINF_OK` with `UZLIB_OK`), and adds a new `source_read_data` field used by the library's callback mechanism. The changes are a routine refactor to stay compatible with an upstream micropython update. There is no direct evidence in the commit that this fixes a security vulnerability, but any mismatch between firmware and its decompression library could in principle cause crashes or incorrect behavior during firmware updates.

This commit is a routine build-system update for the Trezor firmware. It changes where the build process looks for the MicroPython cross-compiler binary (mpy-cross) and synchronizes a configuration header with newer MicroPython code. There is no indication this fixes or introduces a security vulnerability.

This commit updates the Trezor firmware build system to use a newer MicroPython mechanism for tracking special memory pointers called 'root pointers.' It removes hard-coded lists of these pointers from configuration files and instead collects them automatically from source files during the build. The change itself is a build-system modernization and does not appear to fix an active security bug, but it helps prevent a class of future memory-management mistakes that could, in theory, lead to device instability or security issues.

This commit updates the Trezor firmware's embedded MicroPython runtime to version 1.28.0. It swaps in newer ARM assembly helpers for garbage collection, removes some old event-polling macros, and adds support for a new exception-handling callback mechanism. There is no direct evidence in the commit or supplied references that this fixes a security vulnerability; it reads as a routine upstream synchronization/refactoring.

This commit updates an internal debugging tool (meminfo) to work with a newer version of MicroPython. It only changes how memory statistics are printed and how internal MicroPython structures are accessed. There is no indication this affects user funds, wallet security, or introduces an exploitable vulnerability.

This commit removes support for sys.argv (command-line argument lists) from the Trezor firmware's embedded MicroPython interpreter. In a hardware wallet, there is no legitimate command line, so keeping sys.argv enabled only added unused code and a small potential attack surface. The change is a hardening/refactoring step rather than a fix for a known exploit.

This commit only updates expected test result hashes (called 'fixtures') in a single test data file. It does not change any firmware, application, or cryptographic code. There is no direct evidence of a security vulnerability being fixed or introduced here.

This is a routine internal refactoring in the Trezor firmware's Rust code. It updates how Rust code builds MicroPython object type definitions to match a newer version of MicroPython that stores type information in a 'slots' array rather than a flat structure. There is no user-facing feature change and no indication of a security fix.

This commit is a large but purely mechanical code cleanup: it replaces the custom STATIC macro with the standard C keyword static across many MicroPython module files. There is no change to program logic, security boundaries, or behavior. It also removes build-system workarounds that were only needed because the old macro was being abused to expose internal functions.

This is a routine code cleanup that swaps one internal MicroPython time module for another. It does not fix or introduce any security issue visible in the commit.

This commit is a routine code cleanup that updates Trezor firmware to match a newer MicroPython version where built-in module names dropped the 'u' prefix (for example, 'uos' became 'os' and 'ustruct' became 'struct'). It renames imports, configuration flags, and source file references, and removes old mock files. There is no security fix or vulnerability here.

This is a tiny code cleanup that changes how a list of backup words is prepared before being shown to the user. It adds sorting so automated UI tests produce the same screen order regardless of internal hash randomness. The actual list is still shuffled with a secure random function afterward, so user-facing behavior is unchanged. There is no security issue here.

This commit refactors the Trezor firmware's Unix emulator main file to more closely match the upstream MicroPython project. It enables a virtual file system (VFS) for the emulator, but explicitly blocks live filesystem access when running the frozen (production-like) emulator build. The changes are described as maintenance-only and carry a '[no changelog]' tag, meaning the vendor does not treat them as a security fix.

This is a tiny code cleanup in the Ethereum transaction signing code. It moves where a variable is defined without changing what the code actually does. There is no security issue visible in the change.

This commit only updates the changelog text in core/CHANGELOG.md. It adds a one-line note describing a security fix ('Discard low-order keys in THP Code Entry pairing') that was already merged in a previous pull request. There are no code changes, no new functionality, and no direct security fix in this commit itself.

This commit is a small internal cleanup of how Ethereum transaction 'access lists' are formatted for RLP encoding in the Trezor firmware. It replaces a hand-rolled length calculation and manual header writing with higher-level helper functions that do the same job. There is no user-visible behavior change and no indication of a security fix.

This commit only adds a missing line to a changelog file describing a security fix that was already implemented in earlier code. It does not change any source code, firmware behavior, or cryptographic logic. There is nothing here that could directly affect device security.

This commit fixes a deadlock bug in the Trezor firmware's task-killing code. Previously, the code that terminates a background task was marked as a function that never returns, but under some conditions it could actually return and then spin forever doing nothing. That could freeze the device. The fix moves the 'never return' guarantee to the outer system-exit functions and lets the internal task-killer return normally after handing control back to the kernel task.

This commit only updates the firmware version number from 2.12.4 to 2.12.5 in the source code and translation files. It does not change any security-related logic, fix any bug, or alter any cryptographic behavior. It is a routine release bookkeeping change with no security relevance.

This commit only increases a version number from 1.0.13 to 1.0.14 in a header file for the secure monitor component. There are no code changes, no bug fixes, and no security-related content in the diff.

This is a routine build-system cleanup for the Trezor firmware. It switches the internal 'trezor_lib' Rust crate to be built with the project's own 'xbuild' tool, removes transitional feature flags, and reorganizes Cargo.toml files. There is no indication this change fixes or introduces a security vulnerability.

This commit adds a new cryptographic signature entry to a JSON file that records approved translation bundles for the Trezor hardware wallet. It does not change any executable code, fix a bug, or alter security logic. The signature appears to be a routine administrative update authorizing a new set of translated strings for firmware version 2.12.4.0.

This commit is a small internal cleanup in the Rust code that handles device logging. It replaces manual pointer-and-length handling with a helper called FatPtr, which is designed to safely represent string slices. There is no indication this change fixes a security bug or introduces a new vulnerability; it appears to be a routine refactoring that relies on a newly available language feature.