You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mynewt.apache.org by ad...@apache.org on 2016/02/08 20:38:22 UTC

incubator-mynewt-site git commit: update issue tracking info in community.html and add newtmgr doc including project slinky

Repository: incubator-mynewt-site
Updated Branches:
  refs/heads/master 307c1fb34 -> c0e21b896


update issue tracking info in community.html and add newtmgr doc including project slinky


Project: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/commit/c0e21b89
Tree: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/tree/c0e21b89
Diff: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/diff/c0e21b89

Branch: refs/heads/master
Commit: c0e21b8965257d7ea249364952e1ab7afee0c65f
Parents: 307c1fb
Author: aditihilbert <ad...@runtime.io>
Authored: Mon Feb 8 11:38:07 2016 -0800
Committer: aditihilbert <ad...@runtime.io>
Committed: Mon Feb 8 11:38:07 2016 -0800

----------------------------------------------------------------------
 custom-theme/community.html       |  49 +++---
 docs/community.md                 |   2 +-
 docs/modules/shell.md             |   2 -
 docs/newtmgr/overview.md          | 221 ++++++++++++++++++++++++++-
 docs/newtmgr/pics/serial_conn.png | Bin 0 -> 1064089 bytes
 docs/newtmgr/project-slinky.md    | 265 ++++++++++++++++++++++++++++++++-
 6 files changed, 513 insertions(+), 26 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/c0e21b89/custom-theme/community.html
----------------------------------------------------------------------
diff --git a/custom-theme/community.html b/custom-theme/community.html
index c060f54..61328d9 100644
--- a/custom-theme/community.html
+++ b/custom-theme/community.html
@@ -71,29 +71,44 @@
                 <p><a href="mailto:notifications-unsubscribe@mynewt.incubator.apache.org">notifications-unsubscribe@mynewt.incubator.apache.org</a></p>
             </div>
         </div>
-        <div class="col-md-6 mailing-list">
-            <div class="bg-purple mailing-list-title">
-                Issue Tracking Mailing List
-            </div>
-            <div class="list-info">
-                <p><a class="bold-link" href="mailto:issues@mynewt.incubator.apache.org">issues@mynewt.incubator.apache.org</a></p>
-                <p>For all known issues.</p>
             </div>
-            <div class="bg-grey subscribe">
-                Subscribe
-            </div>
-            <div class="list-info">
-                <p><a href="mailto:issues-subscribe@mynewt.incubator.apache.org">issues-subscribe@mynewt.incubator.apache.org</a></p>
-            </div>
-            <div class="bg-grey subscribe">
-                Unsubscribe
+</div>
+
+<div class="content">
+    <div class="container">
+        <div class="row">
+            <div class="col-md-12">
+                <h2>Mail Archives</h2>
+                <p>The archives of the emails exchanged on the mailing lists can be found here: 
+                <li>
+                <a href="http://mail-archives.apache.org/mod_mbox/incubator-mynewt-dev/">For dev@mynewt.incubator.apache.org</a> </p>
+                </li>
+                <li>
+                <a href="http://mail-archives.apache.org/mod_mbox/incubator-mynewt-commits/">For commits@mynewt.incubator.apache.org</a> </p>
+                </li>
             </div>
-            <div class="list-info">
-                <p><a href="mailto:issues-unsubscribe@mynewt.incubator.apache.org">issues-unsubscribe@mynewt.incubator.apache.org</a></p>
+        </div>
+    </div>
+</div>
+
+
+<div class="content">
+    <div class="container">
+        <div class="row">
+            <div class="col-md-12">
+                <h2>Issue Tracking</h2>
+                <p>Issues, features, improvements, and wish-lists are tracked using the Atlassian JIRA software on Apache Software Foundation: 
+               
+                <li>
+                <a href="https://issues.apache.org/jira/browse/Mynewt/">ASF JIRA</a> </p>
+                </li>
             </div>
         </div>
     </div>
 </div>
+
+
+
 <div class="bg-orange padded">
     <div class="container">
         <div class="row">

http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/c0e21b89/docs/community.md
----------------------------------------------------------------------
diff --git a/docs/community.md b/docs/community.md
index b505f86..4ceee3d 100644
--- a/docs/community.md
+++ b/docs/community.md
@@ -2,6 +2,6 @@
 
 ##Mailing Lists
 
-To subscribe to a mailing list, you simply send an email to a special subscription address. To subscribe to the dev list, send an email to [dev-subscribe@mynewt.incubator.apache.org](mailto:dev-subscribe@mynewt.incubator.apache.org).
+To subscribe to a mailing list, you simply send an email to a special subscription address. For example, to subscribe to the dev list, send an email to [dev-subscribe@mynewt.incubator.apache.org](mailto:dev-subscribe@mynewt.incubator.apache.org).
 
 The following mailing lists can be used to get help with MyNewt.

http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/c0e21b89/docs/modules/shell.md
----------------------------------------------------------------------
diff --git a/docs/modules/shell.md b/docs/modules/shell.md
index a01a1b7..0febb4f 100644
--- a/docs/modules/shell.md
+++ b/docs/modules/shell.md
@@ -23,8 +23,6 @@ user@~/dev/larva$ newt target set blinky_sim project=blinky
 Target blinky_sim successfully set project to blinky
 user@~/dev/larva$ newt target set blinky_sim bsp=hw/bsp/native
 Target blinky_sim successfully set bsp to hw/bsp/native
-user@~/dev/larva$ newt target set blinky_sim compiler_def=sim
-Target blinky_sim successfully set compiler_def to sim
 user@~/dev/larva$ newt target set blinky_sim compiler_def=debug
 Target blinky_sim successfully set compiler_def to debug
 user@~/dev/larva$ newt target set blinky_sim compiler=sim

http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/c0e21b89/docs/newtmgr/overview.md
----------------------------------------------------------------------
diff --git a/docs/newtmgr/overview.md b/docs/newtmgr/overview.md
index d7bf273..0b17e65 100644
--- a/docs/newtmgr/overview.md
+++ b/docs/newtmgr/overview.md
@@ -1,9 +1,226 @@
 ## Newt Manager
 
-<synopsis> 
+Newt Manager (newtmgr) is the application tool that enables a user to communicate with and manage remote instances of Mynewt OS. 
 
 
 ## Description
 
 
-## Command List
\ No newline at end of file
+
+## Command List
+
+### Available high-level commands
+
+```no-highlight
+    help        Lists commands and flags available 
+    conn        Manage newtmgr connection profiles
+    echo        Send data to remote endpoint using newtmgr, and receive data back
+    image       Manage images on remote instance
+    stat        Read statistics from a remote endpoint
+    taskstats   Read statistics from a remote endpoint
+    mpstats     Read statistics from a remote endpoint
+    config      Read or write config value on target
+```
+
+### Available Flags
+
+```no-highlight
+  -c, --connection string       connection profile to use.
+  -l, --loglevel string   log level to use (default WARN.)
+```
+
+Examples
+
+Sub-command  | Usage                  | Explanation
+-------------| -----------------------|-----------------
+newtmgr -caditi03 taskstats
+
+### *help*
+
+#### Usage:
+```no-highlight
+    newtmgr help [input1]
+```    
+You can also use "newtmgr [command] --help" to display the help text for a newtmgr command.
+
+Flags:
+
+```no-highlight
+  -c, --connection string      connection profile to use.
+  -l, --loglevel string   log level to use (default WARN.)
+```
+    
+Examples
+
+Sub-command | Available Flags | Explanation
+------------| ----------------|-----------------
+taskstats  | newtmgr -cprofile1 taskstats | Run the taskstats subcommand on the device connected via the 'profile1' connection
+   
+### *conn*
+
+#### Usage:
+```no-highlight
+    newtmgr conn [flags]
+    newtmgr conn [command]
+```    
+
+Available commands: 
+
+```no-highlight
+    add         Add a newtmgr connection profile
+    delete      Delete a newtmgr connection profile
+    show        Show newtmgr connection profiles
+```
+
+Flags:
+
+```no-highlight
+  -c, --conn string       connection profile to use.
+  -l, --loglevel string   log level to use (default WARN.)
+```
+
+Description
+
+Sub-command  | Explanation
+-------------| ------------------------
+add       | Adds a connection profile. A properly defined profile needs a name, a connection type, and the physical or virtual port to be used for communication.
+delete    | Deletes a connection profile associated with the given name
+show      | List the specified or all the connection profiles with the name, connection type, and the controlling terminal or port.
+    
+
+Examples
+
+Sub-command  | Usage                  | Explanation
+-------------| -----------------------|-----------------
+add       | newtmgr conn add myserial02 type=serial connstring=/dev/ttys002 | Adds a newtmgr connection profile for the serial port /dev/ttys002 and names it 'myserial02'
+delete    | newtmgr conn delete myserial02  | Deletes the connection profile named 'myserial02'
+show      | newtmgr conn show myserial01 | Shows the details of the profile named 'myserial01'
+show      | newtmgr conn show  | Shows all the current profiles defined
+    
+### *echo*
+
+#### Usage:
+```no-highlight
+    newtmgr echo [flags] [text]
+```    
+This command sends the text to the remote device at the other end of the connection specified with the -c flag and outputs the text when it gets a response from the device. If the device is not responding or if the connection profile is invalid it displays errors. 
+
+Flags:
+
+```no-highlight
+  -c, --conn string       connection profile to use.
+  -l, --loglevel string   log level to use (default WARN.)
+```
+
+Examples
+
+Sub-command  | Usage                  | Explanation
+-------------| -----------------------|-----------------
+echo       | newtmgr echo -c profile01 hello | Sends the string 'hello' to the remote device over the connection profile 'profile01' and receives the string back and displays it.
+
+
+   
+### *image*
+
+#### Usage:
+```no-highlight
+  newtmgr image [flags]
+  newtmgr image [command]
+```    
+
+Available commands: 
+
+```no-highlight
+    list         Show target images
+    upload       Upload image to target
+    boot         Which image to boot
+    fileupload   Upload file to target
+    filedownload Download file from target
+```
+
+Flags:
+
+```no-highlight
+  -c, --conn string       connection profile to use.
+  -l, --loglevel string   log level to use (default WARN.)
+```
+
+Description
+
+Sub-command  | Explanation
+-------------| ------------------------
+list      | Adds a connection profile. A properly defined profile needs a name, a connection type, and the physical or virtual port to be used for communication.
+upload    | Deletes a connection profile associated with the given name
+boot      | Specify the image to boot 
+fileupload | upload file to the remote target
+filedownload | download/retrieve file from remote target
+    
+
+Examples
+
+Sub-command  | Usage                  | Explanation
+-------------| -----------------------|-----------------
+list       | newtmgr list | 
+upload     | newtmgr upload  | 
+boot       | newtmgr boot | 
+fileupload | newtmgr fileupload  | 
+filedownload | newtmgr filedownload | 
+
+
+### *stat*
+
+#### Usage:
+```no-highlight
+  newtmgr stat [flags]
+  newtmgr stat [command]
+```    
+Flags:
+
+```no-highlight
+  -c, --conn string       connection profile to use.
+  -l, --loglevel string   log level to use (default WARN.)
+```
+
+Examples
+
+Sub-command  | Usage                  | Explanation
+-------------| -----------------------|-----------------
+stat       | newtmgr stat | 
+
+
+### *taskstats*
+
+#### Usage:
+```no-highlight
+  newtmgr taskstats [flags]
+  newtmgr taskstats [command]
+```    
+
+Lists all the tasks running on the remote endpoint at the end of the specified connection and for each task lists statistics such as priority, task id, runtime (how long the task has been running in ms), context switch count, stack size allocated, actual stack usage, last sanity checkin, next sanity check-in. 
+
+Flags:
+
+```no-highlight
+  -c, --conn string       connection profile to use.
+  -l, --loglevel string   log level to use (default WARN.)
+```
+
+Examples
+
+Sub-command  | Usage                  | Explanation
+-------------| -----------------------|-----------------
+stat       | newtmgr taskstats -c profile01 | Lists all the tasks running on the remote device at the end of connection named 'profile01' 
+
+Example output
+
+```no-highlight
+$ newtmgr  -c profile01 taskstats
+Return Code = 0
+  idle (prio=255 tid=0 runtime=3299340 cswcnt=280342 stksize=1024 stkusage=1000 last_checkin=0 next_checkin=0)
+  os_sanity (prio=254 tid=1 runtime=0 cswcnt=3287 stksize=1024 stkusage=1000 last_checkin=0 next_checkin=0)
+  shell (prio=3 tid=2 runtime=0 cswcnt=165 stksize=1024 stkusage=1000 last_checkin=0 next_checkin=0)
+  uart_poller (prio=0 tid=3 runtime=0 cswcnt=279368 stksize=1024 stkusage=1000 last_checkin=0 next_checkin=0)
+  newtmgr (prio=4 tid=4 runtime=0 cswcnt=14 stksize=1024 stkusage=1000 last_checkin=0 next_checkin=0)
+  task1 (prio=1 tid=5 runtime=0 cswcnt=3287 stksize=1024 stkusage=1000 last_checkin=0 next_checkin=0)
+  task2 (prio=2 tid=6 runtime=0 cswcnt=3287 stksize=1024 stkusage=1000 last_checkin=0 next_checkin=0)
+```
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/c0e21b89/docs/newtmgr/pics/serial_conn.png
----------------------------------------------------------------------
diff --git a/docs/newtmgr/pics/serial_conn.png b/docs/newtmgr/pics/serial_conn.png
new file mode 100644
index 0000000..32f27c7
Binary files /dev/null and b/docs/newtmgr/pics/serial_conn.png differ

http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/c0e21b89/docs/newtmgr/project-slinky.md
----------------------------------------------------------------------
diff --git a/docs/newtmgr/project-slinky.md b/docs/newtmgr/project-slinky.md
index 9f74d0a..7aa1996 100644
--- a/docs/newtmgr/project-slinky.md
+++ b/docs/newtmgr/project-slinky.md
@@ -1,9 +1,266 @@
-## Project Slinky
+## Project Slinky 
+
+
+### Objective
+
+The goal of the project is to enable and demonstate remote communications with a device or target via newt manager (newtmgr). We will first build the project image for a simulated device and then build an image for a hardware target. Next, the tool newtmgr has to be installed and a connection established with the target. Finally, various available commands in newtmgr will be used to query the target, upgrade image, and collect data from the endpoint.
+
+
+### What you need
+
+1. STM32-E407 development board from Olimex. You can order it from [http://www.mouser.com](http://www.mouser.com/ProductDetail/Olimex-Ltd/STM32-E407/?qs=UN6GZl1KCcit6Ye0xmPO4A%3D%3D), [http://www.digikey.com](http://www.digikey.com/product-detail/en/STM32-E407/1188-1093-ND/3726951), and other places.
+2. ARM-USB-TINY-H connector with JTAG interface for debugging ARM microcontrollers (comes with the ribbon cable to hook up to the board)
+3. USB A-B type cable to connect the debugger to your personal computer
+4. A USB to TTL Serial Cable with female wiring harness. An example is [http://www.amazon.com/JBtek®-WINDOWS-Supported-Raspberry-Programming/dp/B00QT7LQ88/ref=lp_464404_1_9?s=pc&ie=UTF8&qid=1454631303&sr=1-9](http://www.amazon.com/JBtek®-WINDOWS-Supported-Raspberry-Programming/dp/B00QT7LQ88/ref=lp_464404_1_9?s=pc&ie=UTF8&qid=1454631303&sr=1-9)
+5. Personal Computer
+
+The instructions assume the user is using a Bourne-compatible shell (e.g. bash or zsh) on your computer. The given instructions have been tested with the following releases of operating systems:
+
+* Mac: OS X Yosemite Version 10.10.5
+
+### Overview of steps
+
+* Define targets using the newt tool
+* Build executables for the targets using the newt tool
+* Set up serial connection with the targets - both the physical connection with a hardware target and the connection profile using the newtmgr tool
+* Use the newtmgr tool to communicate with the targets
+
+The following instructions will walk you through the update of the larva nest and the installation of newtmgr as well.
+
+### Creating local repository
+
+Make sure Mynewt's default nest `larva` is up to date by downloading the latest from the Apache mynewt repository ([https://git-wip-us.apache.org/repos/asf/incubator-mynewt-larva](https://git-wip-us.apache.org/repos/asf/incubator-mynewt-larva)).
+
+```no-highlight
+        $ pwd
+        /Users/<user>/dev/larva
+        $ ls -al
+        total 72
+        drwxr-xr-x  18 <user>  staff    612 Feb  3 15:47 .
+        drwxr-xr-x   5 <user>  staff    170 Feb  3 13:32 ..
+        drwxr-xr-x  13 <user>  staff    442 Feb  3 13:32 .git
+        -rw-r--r--   1 <user>  staff     66 Feb  3 13:32 .gitignore
+        -rw-r--r--   1 <user>  staff      0 Feb  3 13:32 .gitmodules
+        drwxr-xr-x   4 <user>  staff    136 Feb  3 16:13 .nest
+        -rw-r--r--   1 <user>  staff  11358 Feb  3 13:32 LICENSE
+        ...
+        ...
+        drwxr-xr-x   5 <user>  staff    170 Feb  3 13:32 sys
+        $ git pull origin master
+```
+
+### Installing Newtmgr
+
+You will first download the source code for newt. Currently, you need to create a symbolic link for all the directory references in the go scripts to work correctly.
+
+```no-highlight
+        $ cd ~/dev
+        $ go get git-wip-us.apache.org/repos/asf/incubator-mynewt-newt.git/newt
+        $ ln -s ~/dev/go/src/git-wip-us.apache.org/repos/asf/incubator-mynewt-newt.git ~/dev/go/src/git-wip-us.apache.org/repos/asf/incubator-mynewt-newt
+
+        $ pwd
+       /Users/<user>/dev/go
+        $ ls
+         bin	pkg	   src
+        $ cd src/git-wip-us.apache.org/repos/asf/incubator-mynewt-newt/newt
+        $ ls
+        newt	newtmgr	   newtvm	util
+        $ cd newtmgr
+        $ go build
+        $ 
+```
+
+Note: If the `go build` command results in errors indicating some package cannot be found, do a `go get` to download all the third-party files needed from github.com and then run `go build` again. 
+
+### Building Targets
+
+You will create a total of 4 targets. The first one is a simulation target and the second a hardware target (for STM32-E407 Olimex development board). In order to run an image from the flash on the Olimex board, a bootloader is required. You will build two additional targets (bootloader and bin2img) as explained in Project Blinky under [Using flash to make LED blink](../get_started/project1/#using-flash-to-make-led-blink) and as shown below.
+
+Here;'s how to create the target for simulation.
+
+```no-highlight
+        $ newt target create slinky_sim
+        Creating target slinky_sim
+        Target slinky_sim sucessfully created!
+        $ newt target set slinky_sim arch=sim
+        Target slinky_sim successfully set arch to sim
+        $ newt target set slinky_sim compiler=sim
+        Target slinky_sim successfully set compiler to sim
+        $ newt target set slinky_sim project=slinky
+        Target slinky_sim successfully set project to slinky
+        $ newt target set slinky_sim compiler_def=debug
+        Target slinky_sim successfully set compiler_def to debug
+        $ newt target set slinky_sim bsp=hw/bsp/native
+        Target slinky_sim successfully set bsp to hw/bsp/native
+        $ newt target show slinky_sim
+        slinky_sim
+        	arch: sim
+        	bsp: hw/bsp/native
+        	compiler: sim
+        	compiler_def: debug
+        	name: slinky_sim
+        	project: slinky     
+```
+Repeat the above steps using the attribute information for each target from the target output shown below to create the remaining three targets. The four target definitions are:
+
+```no-highlight
+        $ newt target show
+        bin2img
+        	arch: sim
+        	bsp: hw/bsp/native
+        	compiler: sim
+        	compiler_def: debug
+        	name: bin2img
+        	project: bin2img
+        boot_olimex
+        	arch: cortex_m4
+	        bsp: hw/bsp/olimex_stm32-e407_devboard
+	        compiler: arm-none-eabi-m4
+	        compiler_def: optimized
+	        name: boot_olimex
+	        project: boot
+        slinky1
+        	arch: cortex_m4
+	        bsp: hw/bsp/olimex_stm32-e407_devboard
+	        compiler: arm-none-eabi-m4
+	        compiler_def: debug
+	        name: slinky1
+	        project: slinky
+        slinky_sim
+	        arch: sim
+	        bsp: hw/bsp/native
+	        compiler: sim
+	        compiler_def: debug
+	        name: slinky_sim
+	        project: slinky
+```
+Go ahead and build all the targets. The build command for slinky_sim is shown below.
+```no-highlight
+        $ newt target build slinky_sim
+        Building target slinky_sim (project = slinky)
+        Compiling base64.c
+        Compiling cbmem.c
+        ...
+        Archiving libnative.a
+        Compiling main.c
+        Building project slinky
+        Linking slinky.elf
+        Successfully run!
+```
+Now run the `newt target build` command for the remaining three targets.
+     
+
+### Using newtmgr with a sim target 
+
+* Run the executable you have build for the simulated environment. The serial port name on which the simulated target is connected is shown in the output.
+
+```no-highlight
+        $ pwd
+        /Users/<user>/dev/larva/project/slinky
+        $ ./bin/slinky_sim/slinky.elf
+        uart0 at /dev/ttys007
+```
+* You will now set up a connection profile using `newtmgr` for the serial port connection and start communicating with the simulated remote device.
+
+```no-highlight
+        $ newtmgr conn add sim1 type=serial connstring=/dev/ttys007
+        Connection profile sim1 successfully added
+        $ newtmgr conn show
+        Connection profiles: 
+          sim1: type=serial, connstring='/dev/ttys007'
+        $ newtmgr -c sim1 taskstats
+        Return Code = 0
+          uart_poller (prio=0 tid=3 runtime=0 cswcnt=43810 stksize=1024 stkusage=325 last_checkin=0 next_checkin=0)
+          newtmgr (prio=4 tid=4 runtime=0 cswcnt=6 stksize=1024 stkusage=585 last_checkin=0 next_checkin=0)
+          task1 (prio=1 tid=5 runtime=0 cswcnt=551 stksize=1024 stkusage=83 last_checkin=0 next_checkin=0)
+          task2 (prio=2 tid=6 runtime=0 cswcnt=551 stksize=1024 stkusage=85 last_checkin=0 next_checkin=0)
+          idle (prio=255 tid=0 runtime=552525 cswcnt=44005 stksize=1024 stkusage=529 last_checkin=0 next_checkin=0)
+          os_sanity (prio=254 tid=1 runtime=0 cswcnt=551 stksize=1024 stkusage=82 last_checkin=0 next_checkin=0)
+          shell (prio=3 tid=2 runtime=0 cswcnt=20 stksize=1024 stkusage=142 last_checkin=0 next_checkin=0)
+        $ newtmgr -c sim1 stat stat
+        Return Code = 0
+        Stats Name: stat
+          s0: 1
+```
+
+
+
+### Using newtmgr with a remote target 
+
+* First make sure the USB A-B type cable is connected to the ARM-USB-TINY-H debugger connector on the Olimex board. 
+
+     Next go the to project directory and download the slinky project image to the flash of the Olimex board. You will see the executables in the `slinky1` directory created for the Olimex target to run the slinky project.
+
+```no-highlight
+        $ pwd
+        /Users/<user>/dev/larva/project/slinky
+        $ ls
+        bin		egg.yml		slinky.yml	src
+        $ ls bin
+        slinky1		slinky_sim
+        $ ls bin/slinky1
+        slinky.elf	slinky.elf.bin	slinky.elf.cmd    slinky.elf.img    slinky.elf.lst    slinky.elf.map
+        $ newt target download boot_olimex
+        Downloading with /Users/<user>/dev/larva/hw/bsp/olimex_stm32-e407_devboard/olimex_stm32-e407_devboard_download.sh
+        $ newt target download slinky1
+        Downloading with /Users/<user>/dev/larva/hw/bsp/olimex_stm32-e407_devboard/olimex_stm32-e407_devboard_download.sh
+```
+
+   You can now disconnect the debugging cable from the board. You should see the green LED blinking. If not, try powercycling the board.
+   
+* Now you have to set up the serial connection from your computer to the Olimex board. Locate the PC6/USART6_TX (pin#3), PC7/USART6_RX (pin#4), and GND (pin#2) of the UEXT connector on the Olimex board. More information on the UEXT connector can be found at [https://www.olimex.com/Products/Modules/UEXT/](https://www.olimex.com/Products/Modules/UEXT/). The schematic of the board can be found at [https://www.olimex.com/Products/ARM/ST/STM32-E407/resources/STM32-E407_sch.pdf](https://www.olimex.com/Products/ARM/ST/STM32-E407/resources/STM32-E407_sch.pdf) for reference.
+
+     ![Alt Layout - Serial Connection](pics/serial_conn.png)
+
+
+	* Connect the female RX pin of the USB-TTL serial cable to the TX of the UEXT connector on the board. 
+	* Connect the female TX pin of the USB-TTL serial cable to the RX of the UEXT connector on the board. 
+	* Connect the GND pin of the USB-TTL serial cable to the GND of the UEXT connector on the board.
+
+
+* Locate the serial connection established in the /dev directory of your computer. It should be of the type `tty.usbserial-<some identifier>`.
+
+```no-highlight
+        $ ls /dev/tty.usbserial-AJ03HAQQ 
+        /dev/tty.usbserial-AJ03HAQQ
+```
+
+* You now have to define a connection profile using newtmgr. You can give it any name you want. The example below shows the connection profile being named as the very imaginative `olimex01`.
+
+```no-highlight
+        $ pwd
+        /Users/<user>/dev/larva/project/slinky
+        $ newtmgr conn add olimex01 type=serial connstring=/dev/tty.usbserial-AJ03HAQQ 
+        Connection profile olimex01 successfully added
+        $ newtmgr conn show
+        Connection profiles: 
+          sim1: type=serial, connstring='/dev/ttys007'
+          olimex01: type=serial, connstring='/dev/tty.usbserial-AJ03HAQQ'
+```
+
+* Now go ahead and query the Olimex board to get responses back. The simplest command is the `echo` command to ask it to respond with the text you send it. 
+
+```no-highlight
+        $ newtmgr echo -c olimex01 hello
+        {"r": "hello"}
+        $ newtmgr image -c olimex01 list
+        Images:
+            0 : 11.22.33.44
+        $ newtmgr -c olimex01 taskstats
+        Return Code = 0
+          shell (prio=3 tid=1 runtime=0 cswcnt=5 stksize=1024 stkusage=60 last_checkin=0 next_checkin=0)
+          newtmgr (prio=4 tid=2 runtime=0 cswcnt=4 stksize=1024 stkusage=256 last_checkin=0 next_checkin=0)
+          task1 (prio=1 tid=3 runtime=0 cswcnt=23 stksize=1024 stkusage=32 last_checkin=0 next_checkin=0)
+          task2 (prio=2 tid=4 runtime=0 cswcnt=24 stksize=1024 stkusage=33 last_checkin=0 next_checkin=0)
+          idle (prio=255 tid=0 runtime=23121 cswcnt=26 stksize=32 stkusage=16 last_checkin=0 next_checkin=0)
+```
+
+
+
+
+
 
-<synopsis> 
 
 
-## Objective
 
 
-## What you need
\ No newline at end of file