feat(firmware): validate configuration and migrate sensor-driven flight APIs
Validate configuration through its owning schemas and keep board declarations separate from shared F722 resource ownership. Bound USB transitions, isolate transport failures and retain restart-only activation. Migrate navigation and flight consumers with the sensor and schema contracts. Require explicit installation data and synchronous output authority; board motor outputs remain inhibited. Validation: assembled-prefix host tests, strict Clippy, platform/USB tests and both ARM release builds. Final-source coverage and scoped Miri/Kani evidence are retained separately from hardware qualification.
This commit is contained in:
1 parent
fb1b8af2d1
commit
f9a61a086f
211 files changed
+45657
-12740
No files matched your search
@@ -18,4 +18,16 @@ pub enum Error<BusError> {
|
||||
/// The selected SPI route reported a terminal transfer fault.
|
||||
#[kaptan_error(id = 5104)]
|
||||
TransferFault,
|
||||
/// The bus could not safely accept and copy out the completed transfer.
|
||||
#[kaptan_error(id = 5105)]
|
||||
Completion(kaptan_spi::CompletionError),
|
||||
/// An accepted SPI transfer exceeded the 10 ms service deadline.
|
||||
#[kaptan_error(id = 5106)]
|
||||
TransferTimeout,
|
||||
/// The bus stayed busy for the pending operation's 20 ms admission budget.
|
||||
#[kaptan_error(id = 5107)]
|
||||
AdmissionTimeout,
|
||||
/// No acquisition was requested within two output periods plus 10 ms.
|
||||
#[kaptan_error(id = 5108)]
|
||||
DataReadyTimeout,
|
||||
}
|
||||
Reference in new issue
Block a user