Compare commits
14 Commits
053eea8b11
...
main
Author | SHA1 | Date | |
---|---|---|---|
593b44d260 | |||
6961bd948b | |||
1ff545434f | |||
d0df3ab7ae | |||
145a871d1d | |||
b018456d64 | |||
6a8712dc7c | |||
892f40f37e | |||
83ceb7a5d0 | |||
3395a32204 | |||
4f1ea82d06 | |||
2857e5ea84 | |||
142ab93d04 | |||
90c9111a08 |
2
.obsidian/app.json
vendored
2
.obsidian/app.json
vendored
@ -2,7 +2,7 @@
|
|||||||
"vimMode": true,
|
"vimMode": true,
|
||||||
"promptDelete": false,
|
"promptDelete": false,
|
||||||
"pdfExportSettings": {
|
"pdfExportSettings": {
|
||||||
"includeName": true,
|
"includeName": false,
|
||||||
"pageSize": "Letter",
|
"pageSize": "Letter",
|
||||||
"landscape": false,
|
"landscape": false,
|
||||||
"margin": "0",
|
"margin": "0",
|
||||||
|
@ -14,7 +14,7 @@
|
|||||||
"prevConfig": {
|
"prevConfig": {
|
||||||
"pageSize": "A4",
|
"pageSize": "A4",
|
||||||
"marginType": "1",
|
"marginType": "1",
|
||||||
"showTitle": true,
|
"showTitle": false,
|
||||||
"open": true,
|
"open": true,
|
||||||
"scale": 100,
|
"scale": 100,
|
||||||
"landscape": false,
|
"landscape": false,
|
||||||
|
29
notes/USB.md
Normal file
29
notes/USB.md
Normal file
@ -0,0 +1,29 @@
|
|||||||
|
A USB system is composed of three areas:
|
||||||
|
- USB interconnect (cables, ports)
|
||||||
|
- USB devices (keyboard, storage, controller)
|
||||||
|
- USB host (Laptop, computer)
|
||||||
|
|
||||||
|
# Hosts
|
||||||
|
There is only one host in any USB system. The USB interface to the host computer is referred to as the Host Controller. The Host Controller may be implemented in a combination of hardware, firmware, or software. A root hub is integrated within the host system to provide one or more attachment points.
|
||||||
|
# Devices
|
||||||
|
USB devices are one of the following:
|
||||||
|
- A hub, providing additional attachment points to the bus
|
||||||
|
- Functions that provide capabilities to the system (speakers, keyboard)
|
||||||
|
# Interconnects
|
||||||
|
|
||||||
|
# Protocol
|
||||||
|
A Universal Serial bus is strictly a *polled* bus, meaning the host controller initiates every data transfer.
|
||||||
|
|
||||||
|
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 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 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 when a USB device is configured in order to provide access to the device's configuration, status, and control info.
|
||||||
|
|
||||||
|
For more, see the USB 2.0 specification section 4.4.
|
Reference in New Issue
Block a user