harden USB telemetry transport
This commit is contained in:
@@ -39,11 +39,11 @@ bytes even though stdio reports a successful write. Firmware therefore cannot
|
||||
retain that particular frame or increment its drop counter. The receiver still
|
||||
detects the loss through CRC resynchronization and packet/sample sequence gaps.
|
||||
|
||||
ESP-IDF's direct USB Serial/JTAG driver provides bounded writes and an explicit
|
||||
transmit-drain wait, allowing a connected stall to become observable to the
|
||||
transport policy. That is a useful improvement for the common transport layer.
|
||||
It is not proof of receiver delivery; application acknowledgements and replay
|
||||
are needed for that stronger guarantee and are planned with BLE integration.
|
||||
This limitation was subsequently closed at the device/endpoint boundary by the
|
||||
shared transport state machine and direct USB Serial/JTAG driver described in
|
||||
`transport-layer-validation-2026-08-17.md`. It is not proof of receiver delivery;
|
||||
application acknowledgements and replay are still needed for that stronger
|
||||
guarantee and are planned with BLE integration.
|
||||
|
||||
## Final hardware capture
|
||||
|
||||
|
||||
Reference in New Issue
Block a user