Trezor firmware

This is a small internal cleanup in the Python helper library that handles Trezor One firmware files. It removes two exposed fields ('magic' and 'code_length') from a Python class and renames them to private internal names ('_magic' and '_code_length'). The actual binary parsing behavior is unchanged: the 'TRZR' magic bytes are still required, and the code length is still computed and embedded exactly as before. There is no security fix or vulnerability here.

This is a small code cleanup in Trezor's Python firmware-handling library. It removes an unused firmware header type for Nordic (NRF) chips and renames an internal 'magic' field so it is no longer treated as a user-facing header type. It also fixes two default boolean values from the integers 1 to the Python booleans True. There is no security-relevant change here.

This commit fixes a small bug in the Python Trezor library that identifies which Trezor hardware model is being used. Previously, the code would crash when it saw a valid but unrecognized model identifier. The fix makes the parser accept any valid model identifier instead of rejecting unknown ones. This is a routine robustness improvement, not a clear security vulnerability, but it could affect how firmware updates or device interactions behave if a new model is introduced.

This commit adds new Python code to the Trezor firmware tools for parsing and building Nordic Semiconductor (nRF) style firmware images. It is a feature addition, not a fix. The code handles firmware headers, TLV metadata blocks, SHA-256 digests, Ed25519 signatures, and device model identifiers. There is no indication in the commit that this resolves a security bug or is being released as a security patch.

This commit updates a bootloader linker script for a new STM32U58-based Trezor variant to support an alternative 'PQ' (post-quantum) bootloader header format. It adds a code-size symbol, a small padding section, and changes how the bootloader image is padded to its maximum size. There is no direct evidence in the commit that this fixes a security vulnerability; it reads as a build/enablement change for a new hardware configuration.

This commit changes how a build reporting tool calculates memory usage for the Trezor bootloader. Previously, the tool counted the zero padding that fills the bootloader image up to its maximum size as 'used' memory, making the bootloader always appear 100% full. The patch lets the linker export the padding size and subtracts it from the reported usage so developers see real content size versus padding. It is a build tooling and reporting improvement, not a fix for a runtime security bug.

This is a small internal code cleanup in the Trezor firmware's Ethereum transaction confirmation flow. It changes several function parameters from 'Iterable' (a general 'can be looped over' type) to 'Sequence' (a type that supports indexing and has a known length). The commit title says the goal is to 'avoid allocation' because the code no longer needs to convert the items into a list before passing them to the UI. There is no direct evidence in the commit of a security vulnerability being fixed; it reads as a performance or memory-efficiency refactor.

This commit turns off several unused features in the MicroPython interpreter that runs on Trezor hardware wallets. It is a hardening change that reduces the amount of code available to an attacker, but it does not by itself fix a known, exploitable bug. The commit message explicitly calls it a routine cleanup ('chore') and says it needs no changelog entry.

This commit only updates automated test scripts and recorded test snapshots (fixtures) for the Trezor firmware. It adds support for testing a new backup method called N4W1 alongside the existing on-screen display backup method. There are no changes to the actual device firmware, wallet logic, or security-critical code, so this commit does not introduce or fix a security vulnerability.