mirror of
https://github.com/ferrous-systems/embedded-trainings-2020.git
synced 2024-11-13 04:01:46 +00:00
Merge pull request #73 from ferrous-systems/fix-links-advanced
fix broken links
This commit is contained in:
commit
7ab4fb0863
2 changed files with 4 additions and 0 deletions
|
@ -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
|
||||
|
|
|
@ -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.
|
||||
|
|
Loading…
Reference in a new issue