BitBox02 firmware

This commit is a routine internal refactoring: it moves three existing device-control functions (reboot, reset Bluetooth chip, and disable SmartEEPROM) behind a common Rust 'system' interface so different parts of the firmware call them through a hardware-abstraction layer instead of directly. The actual device behavior does not change; it is not a security fix and does not introduce a known vulnerability.

This commit is a routine internal code reorganization. It moves the device's startup orientation screen logic from a general workflow module into a hardware-abstraction trait so different device variants can define their own startup behavior. There is no user-facing security change, no bug fix, and no indication this addresses a vulnerability.

This commit is a routine code cleanup: it moves the progress-bar UI code behind a Rust trait (interface) so different parts of the firmware can use it through a common abstraction. It does not change security behavior, fix a bug, or add a new user-facing feature beyond the existing progress bars.

This commit is a routine code reorganization. It moves two constant definitions—how long device names and multisig account names can be—from the C code into Rust, so both the BitBox02 and future BitBox03 products can share the same values. The actual length limits (63 characters plus a null terminator for device names, 30 plus null for multisig names) are unchanged, and the commit adds compile-time checks to prove they stay the same. There is no security bug being fixed here.

This commit only cleans up test code by removing unnecessary calls to a mock memory setup function. It does not change the actual firmware that runs on the BitBox02 device, so it has no security impact on users.

This commit is a simple rename of a Rust function from `subsystems()` to `as_mut()` across several files. It does not change what the code does, only makes the name clearer to programmers. There is no security issue here.

This commit is a small internal code cleanup. It moves the unlock animation from a separate workflow module into the general user-interface (UI) trait, and updates the unlock process to use the new location. There is no change to security behavior or user-visible functionality.

This commit is a straightforward internal code refactor. It introduces a new 'KeystoreHal' adapter so that the keystore code can borrow only the hardware subsystems it needs (memory, random number generator, secure chip) instead of borrowing the entire HAL, which also contains the user interface. The stated reason is to allow a UI animation to run in parallel while the device unlocks. There is no change to security logic, cryptography, or user-facing behavior.

This is a small internal code cleanup in the BitBox02 firmware's Rust code. It changes a helper function so it borrows only the memory/storage part of the hardware abstraction layer, rather than the whole hardware abstraction layer. The commit message says this is preparation for a future change where the user interface part of the hardware layer will be used at the same time during wallet unlocking. There is no direct security fix here and no vulnerability is described.

This commit simply moves a function from one Rust source file to another. The code itself is unchanged; only its location in the project changed. There is no indication of a security fix or vulnerability.

This commit is a straightforward internal code cleanup: it moves where a hardware-abstraction object is created so that a Rust library no longer directly depends on a specific device implementation. There is no user-facing change, no bug fix, and no security vulnerability visible in the diff.

This commit simply moves a function called rust_salt_hash_data from one Rust source file to another. The function itself is unchanged; only its location and the associated test code are reorganized. There is no indication this fixes or introduces a security problem.

This commit is a routine code reorganization. It moves two C-callable Rust functions related to Bluetooth Low Energy (BLE) communication mode from one Rust source file to another, and adjusts which Rust crate features enable the relevant code. There is no visible change to what the code does, only where it lives in the project. No security issue is evident from the diff.

This commit is a straightforward code reorganization: it moves the U2F C API module from one Rust crate (bitbox02-rust) to another (bitbox02-rust-c). The actual logic of the U2F workflow functions is copied almost unchanged, with only import paths adjusted. There is no indication in the commit message or diff that this fixes a security bug, changes behavior, or addresses a reported vulnerability. It appears to be a routine refactoring to improve code structure.

This commit is a straightforward internal code reorganization. It moves the C-compatible entry point for the device's main loop from one Rust module to another, so that the core Rust logic no longer directly depends on the hardware abstraction layer. There is no change to user-facing behavior, no bug fix, and no security-related content.

This commit is a pure internal code reorganization: it moves the BitBox02 hardware-abstraction-layer implementation from one Rust crate (bitbox02-rust) into another (bitbox02). The actual logic, behavior, and security-sensitive operations such as memory access, random number generation, secure-chip handling, SD card access, and user-interface prompts remain identical; only the file paths and import paths change. There is no indication of a security fix or vulnerability being addressed.

This commit is a routine code reorganization: it moves hardware-abstraction trait definitions (interfaces describing how the firmware talks to the screen, secure chip, memory, SD card, random number generator and system reboot) from one internal Rust crate to a newly created crate called bitbox-hal. No behavior of the actual device code is changed; it is purely a dependency and file move to avoid circular imports in the future.

This commit is a routine code cleanup in the BitBox02 firmware's user-interface layer. It removes a convenience method called get_mnemonic from the UI hardware-abstraction trait and makes callers use the underlying workflow function directly. The change also expands unit-test helpers so the existing restore-from-mnemonic test can simulate a 24-word recovery phrase. There is no indication this fixes a security bug or changes user-visible behavior.

This commit is a code cleanup and test improvement. It removes a redundant user-interface method called show_and_confirm_mnemonic from the hardware abstraction layer and makes callers use the underlying workflow directly. It also adds more detailed test helpers so the device screens shown during backup verification can be checked more precisely. There is no indication this fixes a security bug or changes real device behavior in a risky way.

This commit is a straightforward internal code reorganization. It moves a small setting called CanCancel (which controls whether a user can cancel a text-entry screen) from one Rust module to another so the hardware abstraction layer can stand on its own. No behavior changes, no security fixes, and no bug fixes are visible in the diff.

This commit is a routine internal code cleanup. It introduces a new Rust enum called TrinaryChoice inside a hardware abstraction layer (HAL) so that higher-level code no longer directly depends on a lower-level bitbox02 UI type. The actual on-device behavior is unchanged; only the names used in the source code are different. There is no security bug being fixed here.

This commit is a routine internal code cleanup in the BitBox02 firmware's Rust code. It introduces a new hardware-abstraction-layer (HAL) structure for string-entry screens and updates existing code to use it. There is no indication of a security bug, vulnerability fix, or behavior change affecting users.

This commit is a routine internal code cleanup. It moves the definitions of confirmation-screen parameters and fonts out of the workflow layer and into the hardware-abstraction (HAL) layer, then updates all call sites to use the new names. There is no change to user-facing behavior, no bug fix, and no security vulnerability being addressed.

This commit is a small internal cleanup in the BitBox02 firmware's Rust code. It removes a duplicate definition of a 'user cancelled' error type used when the user aborts an SD card insertion prompt, and makes all code use a single shared 'UserAbort' type instead. There is no change to user-facing behavior or security.

This commit is a routine internal code cleanup. It removes a small, dedicated 'cancel' error type and replaces it with an existing, equivalent 'UserAbort' type in the hardware abstraction layer (HAL). The goal stated by the developer is to make the HAL self-contained so it can later be moved to its own crate. There is no change to user-visible behavior, no bug fix, and no security-related change.