CPS-IoT Tutorial todos Tentative Outline

3/25 - 3/29

• RSSI (@tyler-potyondy)
• Channel Switching (@tyler-potyondy)
• EUI64 Getter (@tyler-potyondy)
• 6LoWPAN Capsule Panic Bug (@tyler-potyondy)
• Testing openthread-tock build system (Alex Vochescu, Gabriel Pavaloiu, @lschuermann)
  • Confirm current openthread_hello example app is able to build on your system
• Decide on application for tutorial

4/1 - 4/5

• Border router setup
• Tutorial outline complete (@tyler-potyondy)
• Testing: (Alex Vochescu, Gabriel Pavaloiu, @lschuermann)
  • connect to network (and remain attached for up to 7 minutes) -- test this with checking child table on router cli (cmd child table)
  • receive UDP packets
• alarm wrapping at 7 minutes bug (@atar13 @Samir-Rashid)
• Write screen app (@bradjc?)
• brainstorm visualization?

4/8 - 4/12

• Complete docker setup work (@bradjc)
• Write openthread app and setup interprocess communication (@tyler)
• Test openthread (Alex Vochescu, Gabriel Pavaloiu @lschuermann)
  • perform test with multiple routers and ~30 child nodes to test for any bugs that may arise from higher traffic etc (@tyler-potyondy)
• Write tutorial openthread section

4/15 - 4/19

• Write tutorial robustness section
• Setup border router scripting / additional
• Tutorial completed
• Pilot tutorial with Anthony and Samir

4/22 - 4/26

• Pilot / test tutorial with some group of undergrads unexposed to tock
  open for last minute or lingering issues

4/29 - 5/3

open for last minute or lingering issues

5/6 - 5/10

• Send Setup Instructions to Participants

5/13 - Tutorial

Looking at diffs is murderous because most is built output. We should have netlify run the build step as part of the deploy operation (like we do in tock proper) and remove all of the built artifacts from this repo

Hello 😸 ,
In this part of the Tock OS book, I'm not sure how I should open the process console.

In which step should I input help to open the process console ??
Typing help during the tockloader listen session doesn't seem to do anything..

Thank you!