New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add bsc exercise text #196
Add bsc exercise text #196
Conversation
6591dae
to
bf87279
Compare
@@ -26,6 +26,8 @@ | |||
- [Starting a Project from Scratch](./from-scratch.md) | |||
- [Down the Stack Workbook](./down-the-stack.md) | |||
- [BSC Exercise](./bsc-exercise.md) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This particular file ./bsc-exercise.md
shows up as empty on my version of the mdbook
when rendering. Slight papercut, but a small blurb or image about the exercise (or an off-beat motivational sentence to encourage the participants) could occupy some space there.
## Knowledge | ||
|
||
### Comments | ||
The `lib.rs` has an attribute #![deny(missing_docs)]. This means, that missing doc comments for structs are returned as compiler errors, to remind you to document your work properly. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit:
Backticks on #![deny(missing_docs)]
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left some comments. Most of it is re-ordering "Exercise Button" to "Button Exercise", but there are also some notes which I hope clarify the Uarte example a little bit.
Looks like a fun exercise!
ls /dev/tty.usbmodem* | ||
``` | ||
|
||
✅ Run the following command to run `screen` with the nRF52840-DK with 115200 baud. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
screen
is a bit of a pain to exit and doesn't have a great UI. I have had a lot of success with python3 -m serial.tools.miniterm
(or the alias pyserial-miniterm
), but that requires you have Python and pyserial installed. PuTTY and TeraTerm are other popular options (especially on Windows).
|
||
On your terminal window where `screen` runs, "Hello, World" should appear. | ||
|
||
You need to terminate `screen` manually. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ha! Good luck with that. It's very easy to 'disconnect' the instance but leave it running in the background, hogging the COM port device.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How is that done properly?
Co-authored-by: Jonathan Pallant <jonathan.pallant@ferrous-systems.com>
Co-authored-by: Jonathan Pallant <jonathan.pallant@ferrous-systems.com>
Co-authored-by: Jonathan Pallant <jonathan.pallant@ferrous-systems.com>
Co-authored-by: Jonathan Pallant <jonathan.pallant@ferrous-systems.com>
Co-authored-by: Jonathan Pallant <jonathan.pallant@ferrous-systems.com>
Co-authored-by: Jonathan Pallant <jonathan.pallant@ferrous-systems.com>
Co-authored-by: Jonathan Pallant <jonathan.pallant@ferrous-systems.com>
Co-authored-by: Jonathan Pallant <jonathan.pallant@ferrous-systems.com>
Co-authored-by: Jonathan Pallant <jonathan.pallant@ferrous-systems.com>
Co-authored-by: Jonathan Pallant <jonathan.pallant@ferrous-systems.com>
Co-authored-by: Jonathan Pallant <jonathan.pallant@ferrous-systems.com>
Co-authored-by: Jonathan Pallant <jonathan.pallant@ferrous-systems.com>
Co-authored-by: Jonathan Pallant <jonathan.pallant@ferrous-systems.com>
Co-authored-by: Jonathan Pallant <jonathan.pallant@ferrous-systems.com>
Co-authored-by: Jonathan Pallant <jonathan.pallant@ferrous-systems.com>
Co-authored-by: Jonathan Pallant <jonathan.pallant@ferrous-systems.com>
Co-authored-by: Jonathan Pallant <jonathan.pallant@ferrous-systems.com>
Co-authored-by: Jonathan Pallant <jonathan.pallant@ferrous-systems.com>
Co-authored-by: Jonathan Pallant <jonathan.pallant@ferrous-systems.com>
Co-authored-by: Jonathan Pallant <jonathan.pallant@ferrous-systems.com>
Co-authored-by: Jonathan Pallant <jonathan.pallant@ferrous-systems.com>
Co-authored-by: Jonathan Pallant <jonathan.pallant@ferrous-systems.com>
Co-authored-by: Jonathan Pallant <jonathan.pallant@ferrous-systems.com>
No description provided.