Trezor firmware

This commit adds support for a new Trezor development board called D003 (based on an STM32U5 Nucleo evaluation kit). It is purely an enablement change for internal hardware bring-up: new configuration files, memory layout, bootloader hash, vendor headers, and build-system entries. There is no indication it fixes a security bug or introduces a vulnerability in shipping products.

This commit adds support for a new microcontroller chip (the STM32U5A5) to the Trezor firmware build system. It is a hardware-enablement change: it wires up the right compiler flags, linker scripts, memory layouts, and trustzone settings so the existing code can compile and run on the new chip. There is no user-facing behavior change, no bug fix, and no security patch in this diff.

This commit hardens how Trezor compares secret values (passwords, PINs, cryptographic tags, and checksums) so that an attacker cannot learn information by measuring how long the comparison takes. It also adds a fault-injection check: if a glitch skips the comparison loop, the device is supposed to detect that and halt. The change is defensive and reduces the risk of side-channel and fault attacks, but it does not by itself fix a known, directly exploitable bug.

This is a small test-infrastructure change for the Trezor hardware wallet. It makes the test harness more tolerant of unexpected protocol responses and logs the full error trace instead of immediately stopping the entire pytest session. It does not change the device firmware or how real user transactions are validated; it only affects automated testing of the older protocol-v1 communication code.

This is a minor user-interface polish change for the Trezor hardware wallet's Caesar layout. It removes an unnecessary blank line from transaction summary screens when either the amount label or the amount value is empty. There is no security relevance: it does not change what the device signs, how it signs, or any cryptographic behavior. The large diff is mostly updated test screenshot hashes reflecting the slightly different screen layout.

This commit is a small test-only UI adjustment for the Trezor hardware wallet's Caesar layout. It changes when a menu icon is reported as visible in automated UI snapshots, limiting it to the last page of a multi-page flow. The code change only affects test fixtures and snapshot hashes, not user-facing security behavior. There is no indication this fixes a security vulnerability.

This commit changes how Trezor's Ethereum 'clear signing' helper data is loaded in memory. Previously, all definitions were stored in a permanent module-level list that MicroPython's garbage collector could not reclaim. The patch wraps them in a generator function so they are created on demand and can be freed afterward. The stated goal is to avoid memory pressure, not to fix a security bug. There is no direct evidence of an exploitable vulnerability in the diff itself.

This commit is a minor code cleanup: it replaces a named constant with the literal number 0 in one place and removes the constant definition. There is no functional change, no bug fix, and no security relevance visible in the diff.

This commit adds a new Rust implementation of the Trezor Host Protocol (THP), which is the secure communication layer between a Trezor hardware wallet and a host computer/phone. It introduces encryption, channel management, pairing, and credential verification. Because this is a large new cryptographic and network-facing subsystem, any bugs here could affect device security, but the commit itself is a feature addition rather than a documented fix for a known vulnerability.

This commit fixes a bug in how the Trezor hardware wallet calculates the width of on-screen text. Previously, very long text could cause an internal counter to overflow from a large positive number to a negative number, which might make text appear incorrectly sized or positioned. The fix uses saturating arithmetic so the counter stops at the maximum safe value instead of wrapping around.