summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGuido Günther <agx@sigxcpu.org>2015-06-29 11:17:02 +0200
committerGuido Günther <agx@sigxcpu.org>2015-06-29 11:20:35 +0200
commitd8e23a8bd66e237fd62deee6bc356ffb53a0d205 (patch)
tree1c1ca8c967b471238d3cdce991a4f76ed1bef5ce
parent86a342f84ba4d63d08bc15c7ce5d6740b66cb60c (diff)
Some progress on the merkur-board
-rw-r--r--hw/merkur-board.mdwn23
1 files changed, 19 insertions, 4 deletions
diff --git a/hw/merkur-board.mdwn b/hw/merkur-board.mdwn
index 93bb27d..d10b6d4 100644
--- a/hw/merkur-board.mdwn
+++ b/hw/merkur-board.mdwn
@@ -27,9 +27,9 @@ Compiling works like
cd ./osd-contiki/examples/osd/arduino-plantobserving
./run.sh
-The build software can then be flushed to the device. Note that it used
-/dev/ttyUSB0 by default. This needs to be adjusted. But currently when trying
-the flash the merkur-board I'm only seeing
+The build software can then be flushed to the device. Note that it uses
+/dev/ttyUSB0 by default. This needs to be adjusted. When trying the flash the
+merkur-board with the usual USB-serial converter I see:
$ sudo apt-get install avrdude
$ cd osd-contiki/examples/osd/arduino-plantobserving
@@ -54,8 +54,21 @@ the flash the merkur-board I'm only seeing
Makefile:88: recipe for target 'flash' failed
make: *** [flash] Error 1
-even if I [ground the reset pin][7] (Pin 3).
+even if I [ground the reset pin][7] (Pin 3). However if I use a [*FTDI basic
+breakout*][8] flashing works as expected:
+ ....
+
+The flashed firmware uses *channel 26* and *pan_id 0xabcd* by default. This can
+be seen on the serial output (you can use the same serial converter as for
+flashing). To read the serial console I've so far used the serial console
+window from the arduino ide since *screen* doesn't support the 14400 baud used
+by the merkur-board.
+
+While I'm seeing packages looking for a RIPL router send by the merkur-board
+when using a Raspberry Pi as described in [[here|rpi6lowpan]], I can't ping the
+board on it's link local address yet. I can also verify that it detects the
+RIPL router but the device is still not reachable.
[0]: http://osdwiki.open-entry.com/doku.php/de:projekte:merkur
[1]: http://osdwiki.open-entry.com/doku.php/de:projekte:plant_observation_kit
@@ -66,3 +79,5 @@ even if I [ground the reset pin][7] (Pin 3).
[6]: http://osdwiki.open-entry.com/doku.php/de:products:merkur_grove_board_4#steckerbelegung
[7]: http://www.meetup.com/IoT-Vienna/events/181968432/
[Prolific Pinout]: https://jethomson.files.wordpress.com/2010/02/ca-42_dku-5_pinout.jpg
+[8]: http://www.open-entry.com/coxcoon/de/Zubehoer/FTDI-Basic-Breakout-3-3V.html
+