Trezor firmware

This commit changes how a production-test tool reports problems when checking whether a Tropic secure chip is paired. Previously, the check function itself printed error messages; now it only records diagnostic traces, and the calling commands decide whether to report an error. It also fixes two callers that were passing a dummy/NULL context so they now pass the real command-line interface, meaning their 'pairing required' error messages will actually be shown. This is a code-quality and diagnostics change in a factory/testing tool, not a fix for an exploitable security flaw in end-user firmware.

This is a tiny build-tool fix in a code-generation template. It swaps single quotes for double quotes inside a Python f-string so the template works with older Python versions that don't allow single quotes inside f-string braces. There is no runtime security effect on the Trezor firmware itself.

This commit simply renames a constant from TROPIC_MAC_AND_DESTROY_SLOTS_COUNT to TROPIC_MAC_AND_DESTROY_SLOT_COUNT (singular) across three files. The numeric value stays the same (64), and no program behavior changes. It is a typo-fixing refactor with no security relevance.

This commit is a simple code cleanup: it renames a few internal variables in a production-test file by adding a 'g_' prefix to indicate they are global variables. No behavior of the code changes, and there is no security fix or vulnerability introduced.

This commit adds a new factory/production-test command called tropic-stress-test. It is meant for manufacturing diagnostics and repeatedly exercises the Tropic secure chip's session, MAC-and-destroy, and signing functions to make sure the chip does not enter an alarm state. There is no indication this change fixes a security bug or introduces a vulnerability; it is a testing feature.

This commit is a minor code cleanup in Trezor's production-test tool. It adds the 'const' keyword to two large configuration tables so the compiler knows they should not be modified at runtime. There is no functional change, no bug fix, and no security vulnerability indicated in the diff or commit message.

This commit is a routine code cleanup. It introduces a small helper file that provides a standard, safe way to convert between float numbers and their raw 32-bit representations. It then replaces a few existing hand-written conversions in the battery telemetry code with these helpers. There is no functional change and no security issue.

This commit reorganizes where the device's internal battery/telemetry tracking code lives and adds a fake fixed-response version for the desktop emulator. It does not fix any security bug, introduce a new attack path, or change how real hardware protects data. It is a build/structure-only change.

This commit adds a new data field called battery_cycles to the device's telemetry report. It simply reads an existing stored battery-cycle counter and includes it in the telemetry message sent to connected software. There is no indication this change fixes a bug, changes access controls, or introduces a security vulnerability.

This commit changes how a hardware wallet tracks battery wear. It removes a cast that was truncating a fractional cycle counter to a whole number, and adds interrupt locks around several battery-related operations. The practical effect is that small battery-cycle increments are no longer silently discarded, and concurrent access to shared battery data is better protected. There is no direct evidence in the commit that this fixes an exploitable security vulnerability; it appears to be a correctness and robustness fix.

This commit is a routine feature update to the trezorctl command-line tool and related firmware code. It adds display of a 'battery cycle count' field in telemetry data and changes the internal data type from signed to unsigned integer. There is no indication this change fixes or introduces a security vulnerability.

This commit adds a new battery-cycle counter to the device's internal telemetry system. It lets the firmware record how much the battery has been used, similar to an odometer on a car. There is no direct evidence in the commit that this fixes a security bug; it appears to be a routine feature addition for device-health monitoring.

This is a small bugfix in Trezor's Python developer tools. A command that resets an internal hardware counter (Optiga security event counter) was accidentally being sent over the normal device connection instead of the special debug-only connection. The patch corrects it to use the debug connection. It does not appear to introduce a security vulnerability; rather it fixes a tooling mistake so the debug command works as intended.

This commit adds support for showing clear, human-readable details when signing a Shasta testnet USDT token transfer on the Tron blockchain. Previously, such transactions were displayed as opaque smart-contract data. The change borrows parsing logic from the Ethereum app and hardcodes one testnet token address. It is a feature addition, not a fix for an active vulnerability, though it reduces the chance a user accidentally approves a misleading token transaction.

This is a tiny emulator-only fix that fills in two missing status fields (battery and temperature sensor connected) in a fake power-management report used only on the Unix emulator build. It has no security relevance for real Trezor hardware or user funds.

This commit only updates documentation. It renames a link, adds a note about Python style checkers, updates a tutorial's example code to include a standard Python import, and changes two example commit links. There is no change to the actual Trezor firmware, software, or build process.

This is a documentation-only edit. It fixes two typos ('dtto' to 'ditto', 'For some Python code' to 'For existing Python code') and updates the developer 'Hello World' guide to describe a newer workflow for updating UI test fixtures. No source code, build scripts, or device firmware were changed.

This change fixes a deadlock in Trezor's production-test firmware. The pairing process for a Tropic security chip now retrieves internal secrets before writing anything to flash memory. Previously, it could write the chip's public key to flash first, then call a routine that waits for another initialization step (secrets-init), causing both operations to get stuck waiting for each other. The fix simply reorders the steps so secrets are loaded first. This is a reliability bug in a factory tool, not a user-exploitable security vulnerability in the consumer wallet firmware.

This commit adds a new command-line tool feature that lets users read non-sensitive telemetry data (like device temperature and battery status) from a Trezor hardware wallet. It is a straightforward read-only feature addition with no apparent security implications.

This is a small firmware fix for the Trezor hardware wallet's battery monitoring. It stops the device from reporting a battery temperature to internal telemetry when the temperature sensor (NTC) is physically disconnected. Without the fix, telemetry could record an invalid or misleading temperature value. There is no direct security exploit here; it is a data-quality and robustness improvement.

This commit adds a new kernel syscall (a secure gateway) that lets applications read a telemetry data structure from the kernel. The syscall is guarded by a compile-time flag (USE_TELEMETRY) and uses the existing verifier pattern to check that the app has write access to the destination buffer before copying data. There is no direct evidence in the commit of a security vulnerability; it appears to be a routine addition of a read-only information channel.

This commit adds a new telemetry feature that records when the hardware wallet's battery subsystem reports problems, such as the battery being disconnected, temperature jumps, or charging being limited. It also exposes a new secure-monitor call so other parts of the firmware can report these errors. The change is a feature addition, not a fix for a known vulnerability, and the commit message does not claim any security relevance.

This commit adds a new read-only feature that lets the host computer ask a Trezor device for internal telemetry records: minimum/maximum temperature and battery error counts. It is a feature addition, not a fix. There is no direct evidence in the commit that this introduces a security vulnerability, but it does expose previously internal device data over the USB/Protobuf interface. The security relevance depends on whether the new TelemetryGet message is protected by an existing session/access policy or can be requested by any connected host.

This commit only adds new message definitions for reading out device telemetry (battery temperature extremes and battery error flags). It does not include any firmware logic that actually collects or responds to these messages, so it cannot by itself be used to attack a device. It is essentially plumbing for a future feature.

This is a small developer-only change that adds a 2-second wait when starting a Tropic emulator used in Trezor's Python test tooling. It fixes a timing/race condition where the emulator appears ready to accept connections but still needs a moment before it can actually handle requests. There is no security issue here.