arc/notes
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

vault backup: 2025-08-03 13:46:47

Browse Source
This commit is contained in:
arc
2025-08-03 13:46:47 -06:00
parent 1ff545434f
commit 6961bd948b
1 changed files with 7 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
notes/USB.md
View File

@ -18,6 +18,11 @@ Most bus transactions involve the transmission of up to three packets.
1. The token packet
> Each transaction begins when the host, on a scheduled basis, sends a USB packet describing the type and direction of a transaction, the USB device address, and endpoint number.
2. The data packet
> Depending on the di
> Depending on the direction of data transfer (specified in the token packet), this packet will move from the host to the device, or vice versa. If the source of the transaction has no data to send, it will send that instead.
3. The handshake packet
> The destination, in general, responds to a handshake packet indicating whether the transfer was successful.
> The destination, in general, responds to a handshake packet indicating whether the transfer was successful.
The USB data transfer model between a source or destination on the host and an endpoint on a device is referred to as a *pipe*. There are two types of pipes: stream, and message. Stream data has no USB defined structure, while message data is structured. Each pipe is associated with a bandwidth, transfer service, and endpoint characteristics like directionality and buffer size.
One message pipe, the Default Control Pipe, always exists