embedded-trainings-2020/embedded-workshop-book/src/supporting-standard-requests.md

# USB-4: Supporting more Standard Requests

After responding to the `GET_DESCRIPTOR Device` request the host will start sending different requests.

✅ Update the parser in `common/usb` so that it can handle the following requests:

1. `GET_DESCRIPTOR Configuration`, see the section on [Handling GET_DESCRIPTOR Configuration Requests](./get-descriptor-config.md#handling-get_descriptor-configuration-requests)
2. `SET_CONFIGURATION`, see the section on [SET_CONFIGURATION](./getting-device-configured.md#set_configuration) of this course material

The starter `common/usb` code contains unit tests for these other requests as well as extra `Request` variants for these requests. All of them have been commented out using a `#[cfg(TODO)]` attribute which you can remove once you need any new variant or new unit test.

✅ For each green test, extend `usb-4.rs` to handle the new requests your parser is now able to recognize. **Make sure to read the next sections as you're working**, since they contain explanations about the concepts used and needed to complete this task.

❗️ Keep the cable connected to the J3 port for the rest of the workshop

If you need a reference, you can find solutions to parsing `GET_DESCRIPTOR Configuration` and `SET_CONFIGURATION` requests in the following files:

- `advanced/common/usb/solution-get-descriptor-configuration.rs`
- `advanced/common/usb/solution-set-configuration.rs`

Each file contains just enough code to parse the request in its name and the `GET_DESCRIPTOR Device` and `SET_ADDRESS` requests. So you can refer to `solution-get-descriptor-configuration.rs` without getting "spoiled" about how to parse the `SET_CONFIGURATION` request.
add advanced material 2020-07-13 11:48:24 +00:00			`# USB-4: Supporting more Standard Requests`

tell folks to keep the USB cable connected 2020-07-16 12:07:17 +00:00			After responding to the `GET_DESCRIPTOR Device` request the host will start sending different requests.
more didactic changes 2020-07-15 16:53:31 +00:00
			✅ Update the parser in `common/usb` so that it can handle the following requests:
add advanced material 2020-07-13 11:48:24 +00:00
embedded-workshop-book: fix links to book sections/chapters 2020-07-15 12:14:18 +00:00			1. `GET_DESCRIPTOR Configuration`, see the section on [Handling GET_DESCRIPTOR Configuration Requests](./get-descriptor-config.md#handling-get_descriptor-configuration-requests)
			2. `SET_CONFIGURATION`, see the section on [SET_CONFIGURATION](./getting-device-configured.md#set_configuration) of this course material
add advanced material 2020-07-13 11:48:24 +00:00
			The starter `common/usb` code contains unit tests for these other requests as well as extra `Request` variants for these requests. All of them have been commented out using a `#[cfg(TODO)]` attribute which you can remove once you need any new variant or new unit test.

more didactic changes 2020-07-15 16:53:31 +00:00			✅ For each green test, extend `usb-4.rs` to handle the new requests your parser is now able to recognize. Make sure to read the next sections as you're working, since they contain explanations about the concepts used and needed to complete this task.
add advanced material 2020-07-13 11:48:24 +00:00
tell folks to keep the USB cable connected 2020-07-16 12:07:17 +00:00			`❗️ Keep the cable connected to the J3 port for the rest of the workshop`

add advanced material 2020-07-13 11:48:24 +00:00			If you need a reference, you can find solutions to parsing `GET_DESCRIPTOR Configuration` and `SET_CONFIGURATION` requests in the following files:

rename USB parser solutions also put them outside the `src` directory so people don't think they are modules 2020-07-14 11:28:23 +00:00			- `advanced/common/usb/solution-get-descriptor-configuration.rs`
			- `advanced/common/usb/solution-set-configuration.rs`
add advanced material 2020-07-13 11:48:24 +00:00
rename USB parser solutions also put them outside the `src` directory so people don't think they are modules 2020-07-14 11:28:23 +00:00			Each file contains just enough code to parse the request in its name and the `GET_DESCRIPTOR Device` and `SET_ADDRESS` requests. So you can refer to `solution-get-descriptor-configuration.rs` without getting "spoiled" about how to parse the `SET_CONFIGURATION` request.