mirrors/embedded-trainings-2020
1
0
Fork 0
mirror of https://github.com/ferrous-systems/embedded-trainings-2020.git synced 2025-01-02 12:28:48 +00:00
Code Issues Projects Releases Wiki Activity

rm links to oxidize

Browse source
This commit is contained in:
Lotte Steenbrink 2021-01-19 16:29:44 +01:00
parent 7e7901b1e7
commit d87272cb76
3 changed files with 24 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
README.md
View file

@ -1,10 +1,17 @@
# `embedded-trainings-2020`
Material for the beginner and advanced workshops of Oxidize Global (15.07.2020).
This repository contains the material for the beginner and advanced Embedded Rust workshops held by [Ferrous Systems].
Website for this workshop: [https://embedded-trainings.ferrous-systems.com][book]
You can find the rendered book containing all instructions at [embedded-trainings.ferrous-systems.com][book]
If you'd like to attend one of our open classes or book a custom training, please visit our [trainings website].
*This workshop was initially held at [Oxidize Global 2020]*
[book]: https://embedded-trainings.ferrous-systems.com
[Ferrous Systems]: https://ferrous-systems.com
[trainings website]: https://ferrous-systems.com/training/
[Oxidize Global 2020]: https://oxidizeconf.com
## Required hardware
@ -13,7 +20,6 @@ Website for this workshop: [https://embedded-trainings.ferrous-systems.com][book
- 2 micro-USB cables
- 2 available USB-A ports on your laptop / PC (you can use a USB hub if you don't have enough ports)
## License
The Ferrous Systems Embedded Training Courses (this project) are distributed under the following licenses:

13
embedded-workshop-book/src/troubleshoot-cargo-flash.md
View file

@ -18,7 +18,10 @@ $ cargo flash --chip nRF52840_xxAA --bin hello
Error failed to flash app: The execution of 'erase_sector' failed with code 1
```
flash write protection is enabled in the device. To disable it use the `nrf-recover` tool. Instructions can be found in the [setup page](https://oxidizeconf.com/oxidize-global-setup/) and in the top-level README of this repository.
flash write protection is enabled in the device. To disable it use the `nrf-recover` tool. Instructions can be found in the [`nrf-recover` section of the Installation Instructions].
[`nrf-recover` section of the Installation Instructions]: ./installation.md#nrf-recover
## Linux permissions
@ -30,7 +33,9 @@ Caused by:
USB error while opening USB device: Access denied (insufficient permissions)
```
udev rules need to be changed to allow non-root access. Instructions can be found in the [setup page](https://oxidizeconf.com/oxidize-global-setup/) and in the top-level README of this repository.
udev rules need to be changed to allow non-root access. Instructions can be found in the [`Linux only: USB` section of the Installation Instructions].
[`Linux only: USB` section of the Installation Instructions]: ./installation.md#linux-only-usb
## Wrong Windows Driver
@ -42,4 +47,6 @@ Caused by:
USB error while opening USB device: Entity not found
```
You need to bind the BULK interface of the J-Link USB device to the WinUSB driver using the Zadig tool. Instructions can be found in the [setup page](https://oxidizeconf.com/oxidize-global-setup/) and in the top-level README of this repository.
You need to bind the BULK interface of the J-Link USB device to the WinUSB driver using the Zadig tool. Instructions can be found in the [`Windows only: Zadig JLink driver` section of the Installation Instructions].
[`Windows only: Zadig JLink driver` section of the Installation Instructions]: ./installation.md#windows-only-zadig-jlink-driver

6
embedded-workshop-book/src/troubleshoot-dongle-flash.md
View file

@ -6,4 +6,8 @@ packaging iHex using nrfutil ...
Error: No such file or directory (os error 2)
```
this indicates that `nrfutil`, the Python tool, is not installed or not available in your PATH. Instructions on how to install `nrfutil` can be found in the [setup page](https://oxidizeconf.com/oxidize-global-setup/) and in the top-level README of this repository. If you install `nrfutil` in a virtual environment you'll need to activate the environment; the `nrfutil` binary must be available in your PATH.
this indicates that `nrfutil`, the Python tool, is not installed or not available in your PATH. Instructions on how to install `nrfutil` can be found in the [`nrfutil` section of the Installation Instructions].
❗️ If you install `nrfutil` in a virtual environment you'll need to activate the environment; the `nrfutil` binary must be available in your PATH.
[`nrfutil` section of the Installation Instructions]: ./installation.md#nrfutil