LegacyDfuException
Errors specific to the Nordic Legacy DFU protocol. These are a subtype of DfuException so the existing handler error-path code (which catches DfuException) covers both protocols.
Inheritors
Types
Init packet (dat) appears to be Secure-DFU shaped (signed/CBOR), not the small legacy 14-32 B form.
The BLE link dropped while firmware bytes were in flight. Carries the host in-flight offset (the end of the write the host had dispatched or was in flight at the moment of the drop) so the retry coordinator can distinguish a mid-stream failure (which switches subsequent Legacy uploads to LegacyDfuStreamProfile.RECOVERY) from a handshake/connect failure (which does not).
Bytes received reported by device differs from bytes sent past last PRN window.
Device returned a non-success status for a given opcode.
START_DFU was rejected with INVALID_STATE because the bootloader still holds state from an interrupted session. The current connection is closed without attempting RESET; SecureDfuHandler performs a bounded reset-prime over a fresh connection before retrying.
Bootloader exposes DFU Version characteristic with a value below 5 (Nordic SDK ≤ 6). Unsupported.