Merge pull request #21 from PeterKietzmann/lastmin_fixes

Several minor lastminute fixes

Author: cgundogan

README.md

@@ -4,7 +4,7 @@
 
 For links go to [https://github.com/RIOT-OS/Tutorials](https://github.com/RIOT-OS/Tutorials)
 
-**Quick Setup** (Using a Virtual Machine)
+**Quick Setup using a Virtual Machine (recommended for this Tutorial)**
 
 * Install and set up [git](https://help.github.com/articles/set-up-git/)
 * Install latest [VirtualBox](https://www.virtualbox.org/wiki/Downloads) & [VirtualBox Extension Pack](https://www.virtualbox.org/wiki/Downloads) for **your system**
@@ -19,11 +19,10 @@ For links go to [https://github.com/RIOT-OS/Tutorials](https://github.com/RIOT-O
     cd Tutorials
     git submodule update --init --recursive
     ```
-* Change to the `RIOT` directory: `cd Tutorials/RIOT/`
 * In case a virtual machine is disseminated locally, adapt the path for the vagrant box `vagrant box add RIOT/ubuntu1604 <path to box>`
 * Run `vagrant up` and `vagrant ssh` afterwards. See the [Vagrant RIOT Setup](https://github.com/RIOT-OS/RIOT/blob/master/dist/tools/vagrant/README.md) for a more general explanation.
 
-**Recommended Setup** (Without Using a VM)
+**Regular Setup without using a VM (recommended for RIOT developement)**
 
 * Install and set up [git](https://help.github.com/articles/set-up-git/)
 * Install the build-essential packet (make, gcc etc.). This varies based on the operating system in use.

phytec.png

@@ -41,27 +41,54 @@
 ## Task 1.2: Run your first application on real hardware
 1.  Get to know your hardware
 
+    *Atmel SAM R21 Xplained Pro*
+
     ![SAMR21-XPRO](../SAM-R21.jpg)
 
     MCU                    | ATSAMR21G18A
     -----------------------|------------------------------------
     Family                 | ARM Cortex-M0+
     Vendor                 | Atmel
-    RAM                    | 32Kb
-    Flash                  | 256Kb
+    RAM/ROM                | 32Kb / 256Kb
     Frequency              | up to 48MHz
-    FPU                    | no
     Timers                 | 6 (1x 16-bit, 2x 24-bit, 3x 32-bit)
     ADCs                   | 1x 12-bit (8 channels)
     UARTs / SPIs / I2Cs    | max 5 (shared)
     Vcc                    | 1.8V - 3.6V
+    Radio                  | IEEE802.15.4 @ 2,4GHz
+    Sensors                | none
+
+    *Phytec phyNODE KW22*
+
+    ![phyNODE](../phytec.png)
+
+    MCU                    | MKW22D512
+    -----------------------|------------------------------------
+    Family                 | ARM Cortex-M4
+    Vendor                 | Kinetis
+    RAM/ROM                | 65Kb / 512Kb
+    Frequency              | up to 50MHz
+    Timers                 | up to 12 (16-bit, 24-bit, 32-bit)
+    ADCs                   | 1x 16-bit (8 channels)
+    UARTs / SPIs / I2Cs    | 3 / 1 / 2
+    Vcc                    | 1.8V - 3.6V
+    Radio                  | IEEE802.15.4 @ 2,4GHZ
+    Sensors                | diverse
 
 2.  To compile an application for a specific board, we can make use of the `BOARD` environment
     variable.
+
+    In case you are running on an Atmel board, type:
     ```sh
     BOARD=samr21-xpro make all flash term
     ```
-    This command will compile the application, burn the image onto the `samr21-xpro` and open a
+
+    For the (yellow) phyNODE use;
+    ```sh
+    BOARD=pba-d-01-kw2x make all flash term
+    ```
+
+    This command will compile the application, burn the image onto the board and open a
     connection to the RIOT shell.
 
 3.  Verify the output of `RIOT_BOARD` matches your hardware.

task-01/README.md

@@ -30,9 +30,9 @@ USEMODULE += auto_init_gnrc_netif
 * Check with `ifconfig` or `ip link`!
 
 ## Task 5.1 -- Your first networking application
-* Run the application on `native`: `PORT=tap0 make all term`
+* Run the application on `native`: `make all term PORT=tap0`
 * Type `help`
-* Run a second instance with `PORT=tap1 make all term`
+* Run a second instance with `make all term PORT=tap1`
 * Type `ifconfig` on both to get hardware address and interface number
 * Use `txtsnd` command to exchange messages between the two instances
 

task-05/README.md

@@ -1,5 +1,5 @@
 # name of your application
-APPLICATION = Task04
+APPLICATION = Task06
 
 # If no BOARD is found in the environment, use this default:
 BOARD ?= native

task-06/Makefile

@@ -1,8 +1,11 @@
-APPLICATION = ccn-lite-relay
+APPLICATION = Task08
 
 # If no BOARD is found in the environment, use this default:
 BOARD ?= native
 
+# This has to be the absolute path to the RIOT base directory:
+RIOTBASE ?= $(CURDIR)/../RIOT
+
 BOARD_WHITELIST := fox iotlab-m3 msba2 mulle native pba-d-01-kw2x samr21-xpro
 
 

task-08/Makefile

@@ -6,6 +6,8 @@ from [CCN-Lite](http://www.ccn-lite.net/) on RIOT. In the current state you can
 use only one packet format, `ndn2013`, and only relay over the link-layer
 (Ethernet, IEEE~802.15.4 or what else is supported by your network device).
 
+*Please note that compiling this application will clone the CCN-Lite remote repository.*
+
 ## The shell commands
 
 RIOT provides three shell to interact with the CCN-Lite stack:
@@ -42,7 +44,7 @@ RIOT provides three shell to interact with the CCN-Lite stack:
 * Create some content for /dagstuhl/m2m/<youraccountname>
 * Send an interest for /dagstuhl/m2m/<otheraccountname>
 
-## Task 8.2: Modify the default shell commands
+## Task 8.2: Modify the default shell commands (advanced task)
 
 * Take a look at the default shell commands in `sys/shell/commands/sc_ccnl.c`
 * Create a new command to send an interest with a shorter timeout