mirrors/embedded-trainings-2020
1
0
Fork 0
mirror of https://github.com/ferrous-systems/embedded-trainings-2020.git synced 2024-04-28 22:59:00 +00:00
Code Issues Projects Releases Wiki Activity

fix broken links

Browse source
This commit is contained in:
Mirabellensaft 2020-07-16 17:50:38 +02:00
parent 2a12128732
commit 4a9159e800
2 changed files with 4 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
embedded-workshop-book/src/control-transfers.md
View file

@ -15,3 +15,6 @@ The control pipe handles *control transfers*, a special kind of data transfer us
During the SETUP stage the host sends 8 bytes of data that identify the control request. Depending on the issued request there may be a DATA stage or not; during the DATA stage data is transferred either from the device to the host or the other way around. During the STATUS stage the device acknowledges, or not, the whole control request.
For detailed information about control transfers check section 5.5, Control Transfers, of the [USB 2.0 specification][usb20].
[usb20]: https://www.usb.org/document-library/usb-20-specification

1
embedded-workshop-book/src/setup-stage.md
View file

@ -4,6 +4,7 @@ At the end of program `usb-1` we received a EP0SETUP event. This event signals t
In `usb-2.rs`, you will find a short description of each register above the variable into which it should be read.
> For in-depth register documentation, refer to sections 6.35.13.31 to 6.35.13.38 of the [nRF52840 Product Specification][nrf product spec].
[nrf product spec]: https://infocenter.nordicsemi.com/pdf/nRF52840_PS_v1.1.pdf
When you need to write some `no_std` code that does not involve device-specific I/O you should consider writing it as a separate crate. This way, you can test it on your development machine (e.g. `x86_64`) using the standard `cargo test` functionality.