mynewt-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ad...@apache.org
Subject incubator-mynewt-site git commit: removed banner from Mynewt home page, removed links to empty tutorials, moved slinky and target-slinky under tutorials.
Date Wed, 23 Mar 2016 21:30:15 GMT
Repository: incubator-mynewt-site
Updated Branches:
  refs/heads/master 39bcbce3f -> 421743966


removed banner from Mynewt home page, removed links to empty tutorials, moved slinky and target-slinky
under tutorials.


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/42174396
Tree: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/tree/42174396
Diff: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/diff/42174396

Branch: refs/heads/master
Commit: 4217439664dd899985928aba4e31f3c82a0fd6d7
Parents: 39bcbce
Author: aditihilbert <aditi@runtime.io>
Authored: Wed Mar 23 14:30:04 2016 -0700
Committer: aditihilbert <aditi@runtime.io>
Committed: Wed Mar 23 14:30:04 2016 -0700

----------------------------------------------------------------------
 custom-theme/landing.html                  |  18 +--
 docs/newtmgr/project-slinky.md             | 142 ------------------
 docs/newtmgr/project-target-slinky.md      | 192 ------------------------
 docs/os/tutorials/add_repos.md             |   4 +-
 docs/os/tutorials/project-slinky.md        | 139 +++++++++++++++++
 docs/os/tutorials/project-target-slinky.md | 190 +++++++++++++++++++++++
 mkdocs.yml                                 |   7 +-
 7 files changed, 335 insertions(+), 357 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/42174396/custom-theme/landing.html
----------------------------------------------------------------------
diff --git a/custom-theme/landing.html b/custom-theme/landing.html
index a774b73..4d6414b 100644
--- a/custom-theme/landing.html
+++ b/custom-theme/landing.html
@@ -1,20 +1,6 @@
 {% include 'main-banner.html' %}
-<div class="bg-orange padded event-callout content">
-    <div class="row">
-        <div class="col-md-12">
-            <div class="container">
-                <div class="row">
-                    <div class="col-md-12 text-center">
-                        <h3>{{ config.extra.events['event 1'].title }}</h3>
-                        <p>{{ config.extra.events['event 1'].location }}</p>
-                        <p>{{ config.extra.events['event 1'].date }}</p>
-                        <a href="/events/">Click here for more details</a>
-                    </div>
-                </div>
-            </div>
-        </div>
-    </div>
-</div>
+<br>
+<br>
 <div class="row">
     <div class="column col-md-12">
         <div class="container">

http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/42174396/docs/newtmgr/project-slinky.md
----------------------------------------------------------------------
diff --git a/docs/newtmgr/project-slinky.md b/docs/newtmgr/project-slinky.md
deleted file mode 100644
index c00e1f8..0000000
--- a/docs/newtmgr/project-slinky.md
+++ /dev/null
@@ -1,142 +0,0 @@
-## Project Sim Slinky  
-
-
-### Objective
-
-The goal of the project is to enable and demonstrate remote communications with the Mynewt
OS via newt manager (newtmgr). We will do this through building a project with Mynewt called
Slinky that runs via the native platform. 
-
-### What you need
-
-1.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
-
-* Install dependencies
-* Define a target using the newt tool
-* Build executables for the targets using the newt tool
-* Set up serial connection with the targets 
-* Create a connection profile using the newtmgr tool
-* Use the newtmgr tool to communicate with the targets
-
-### Installing newt
-
-If you have not already installed `newt` see the 
-[newt installation instructions](../newt/install/newt_mac.md) and ensure newt is installed
an in your path.
-
-### Installing newtmgr
-
-If you have not already installed `newtmgr` see the 
-[newtmgr installation instructions](installing.md) and ensure newtmgr is installed an in
your path.
-
-### Creating a new project
-
-Instructions for creating a project are located in the [Getting Started](../os/get_started/project_create.md)
section of the [Mynewt OS Manual](../os/get_started/introduction.md)
-
-We will list only the steps here for brevity.  We will name the project
-`slinky`.
-
-```no-highlight
-    $ newt new slinky
-    Downloading project skeleton from apache/incubator-mynewt-blinky...
-    ...
-    Installing skeleton in slink...
-    Project slink successfully created
-    $ cd slinky
-    $ newt install -v
-    Downloading repository description for apache-mynewt-core... success!
-    ...
-    Repos successfully installed
-```
-
-### Setting up your target build
-
-Create a target for `slinky` using the native bsp.  See 
-[How to Define a Target](../newt/tutorials/define_target.md) for a detailed
-description.  We will list only the steps and suppress the tool output 
-here for brevity.
-
-```no-highlight
-    $ newt target create sim_slinky
-    $ newt target set sim_slinky bsp=@apache-mynewt-core/hw/bsp/native
-    $ newt target set sim_slinky build_profile=debug
-    $ newt target set sim_slinky app=@apache-mynewt-core/apps/slinky
-```
-
-### Building Your target
-
-To build your target, use `newt build`.  When complete, an executable file
-is created.
-
-```no-highlight
-    $ newt build sim_slinky 
-    Compiling main.c
-    ...
-    Linking slinky.elf
-    App successfully built: ~/dev/slinky/bin/sim_slinky/apps/slinky/slinky.elf
-```
-
-### Run the 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
-when mynewt slinky starts.
-
-```no-highlight
-    $ ~/dev/slinky/bin/sim_slinky/apps/slinky/slinky.elf
-    uart0 at /dev/ttys005
-```
-
-<br>
-
-In this example, the slinky app opened up a com port `/dev/ttys005`
-for communications with newtmgr. 
-
-**NOTE:** This application will block. You will need to open a new console (or execute this
in another console) to continue the tutorial.*
-
-<br>
-
-### Setting up a connection profile
-
-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/ttys005
-    Connection profile sim1 successfully added
-    $ newtmgr conn show
-    Connection profiles: 
-      sim1: type=serial, connstring='/dev/ttys007'
-```
-
-### Executing newtmgr commands with the target
-
-You can now use connection profile `sim1` to talk to the running sim_blinky.
-As an example, we will query the running mynewt OS for the usage of its 
-memory pools.  
-
-```no-highlight
-    $ newtmgr -c sim1 mpstats
-    Return Code = 0
-      nffs_cache_inode_pool (blksize=36 nblocks=4 nfree=4)
-      nffs_cache_block_pool (blksize=32 nblocks=64 nfree=64)
-      nffs_dir_pool (blksize=8 nblocks=4 nfree=4)
-      default_mbuf_data (blksize=256 nblocks=10 nfree=8)
-      nffs_file_pool (blksize=12 nblocks=4 nfree=4)
-      nffs_inode_entry_pool (blksize=24 nblocks=100 nfree=98)
-      nffs_block_entry_pool (blksize=12 nblocks=100 nfree=100)
-```
-
-As a test command, you can send an arbitrary string to the target and it
-will echo that string back in a response to newtmgr.
-
-```no-highlight
-    $ newtmgr -c sim1 echo "Hello Mynewt"
-    {"r": "Hello Mynewt"}
-```
-
-The response comes back as a json string.
-
-In addition to these, you can also examine running tasks, statistics, 
-logs, image status (not on sim), and configuration.

http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/42174396/docs/newtmgr/project-target-slinky.md
----------------------------------------------------------------------
diff --git a/docs/newtmgr/project-target-slinky.md b/docs/newtmgr/project-target-slinky.md
deleted file mode 100644
index ed93ec0..0000000
--- a/docs/newtmgr/project-target-slinky.md
+++ /dev/null
@@ -1,192 +0,0 @@
-## Project Slinky 
-
-
-### Objective
-
-The goal of the project is to enable and demonstrate remote communications with the Mynewt
OS via newt manager (newtmgr). We will do this through a project with Mynewt called Slinky
that runs on the STM32-E407 board.
-
-### 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
-
-* Install dependencies
-* Define a target using the newt tool
-* Build executables for the targets using the newt tool
-* Set up serial connection with the targets 
-* Create a connection profile using the newtmgr tool
-* Use the newtmgr tool to communicate with the targets
-
-### Install newt
-
-If you have not already installed `newt`, see the 
-[newt installation instructions](../newt/install/newt_mac.md) and ensure newt is installed
an in your path.
-
-### Install newtmgr
-
-If you have not already installed `newtmgr`, see the 
-[newtmgr installation instructions](installing.md) and ensure newtmgr is installed an in
your path.
-
-### Create a new project
-
-Instructions for creating a project are located in the [Getting Started](../os/get_started/project_create.md)
section of the [Mynewt OS Manual](../os/get_started/introduction.md).
-
-If you already completed [sim slinky](project-slinky.md) you can skip this step.
-
-We will list only the steps here for brevity.  We will name the project
-`slinky`.
-
-```no-highlight
-$ newt new slinky
-Downloading project skeleton from apache/incubator-mynewt-blinky...
-...
-Installing skeleton in slink...
-Project slink successfully created
-$ cd slinky
-$newt install -v
-Downloading repository description for apache-mynewt-core... success!
-...
-Repos successfully installed
-```
-
-<br>
-
-### Set up your target builds
-
-Create a target for `stm32_slinky` using the native bsp.  See 
-[How to Define a Target](../newt/tutorials/define_target.md) for a detailed
-description.  The tool output is suppressed below for brevity.
-
-```no-highlight
-$ newt target create stm32_slinky
-$ newt target set stm32_slinky bsp=@apache-mynewt-core/hw/bsp/olimex_stm32-e407_devboard
-$ newt target set stm32_slinky build_profile=debug
-$ newt target set stm32_slinky app=@apache-mynewt-core/apps/slinky
-```
-
-Create a second target for `stm32_bootloader` to build a bootloader to boot
-the `stm32_slinky` image.  The tool output is suppressed below for brevity.
-
-```no-highlight
-$ newt target create stm32_bootloader
-$ newt target set stm32_bootloader bsp=@apache-mynewt-core/hw/bsp/olimex_stm32-e407_devboard
-$ newt target set stm32_bootloader build_profile=optimized
-$ newt target set stm32_bootloader target.app=@apache-mynewt-core/apps/boot
-```
-
-<br>
-
-### Build Targets
-
-```no-highlight
-$ newt build stm32_slinky
-Compiling main.c
-...
-Linking slinky.elf
-App successfully built: ~/dev/slinky/bin/stm32_slinky/apps/slinky/slinky.elf
-```
-
-```no-highlight
-newt build stm32_bootloader
-Compiling crc16.c
-...
-Linking boot.elf
-App successfully built: ~/slinky/bin/stm32_bootloader/apps/boot/boot.elf
-```
-
-For the main image, you need to create an image using newt create-image.
-Give this image some arbitrary version number "1.2.3".
-
-```no-highlight
-$ newt create-image stm32_slinky 1.2.3
-App image succesfully generated: /Users/paulfdietrich/dev/slinky/bin/stm32_slinky/apps/slinky/slinky.img
-Build manifest: /Users/paulfdietrich/dev/slinky/bin/stm32_slinky/apps/slinky/manifest.json
-```
-
-<br>
-
-### 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. 
-
-```no-highlight
-$ newt load stm32_bootloader
-$ newt load stm32_slinky
-```
-
-You can now disconnect the debugging cable from the board. You should see the green LED blinking.
If not, try powercycling the board.
-
-<br>
-
-* 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.
-
-<br>
-
-* 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
-```
-
-<br>
-
-* 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'
-```
-
-<br>
-
-* 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 : 1.2.3
-    $ newtmgr -c olimex01 taskstats
-    Return Code = 0
-      newtmgr (prio=4 tid=2 runtime=0 cswcnt=12 stksize=512 stkusage=255 last_checkin=0 next_checkin=0)
-      task1 (prio=1 tid=3 runtime=0 cswcnt=299 stksize=128 stkusage=33 last_checkin=0 next_checkin=0)
-      task2 (prio=2 tid=4 runtime=0 cswcnt=300 stksize=128 stkusage=31 last_checkin=0 next_checkin=0)
-      idle (prio=255 tid=0 runtime=299916 cswcnt=313 stksize=32 stkusage=18 last_checkin=0
next_checkin=0)
-      shell (prio=3 tid=1 runtime=1 cswcnt=20 stksize=384 stkusage=60 last_checkin=0 next_checkin=0)
-```
-
-
-
-
-
-
-
-
-
-

http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/42174396/docs/os/tutorials/add_repos.md
----------------------------------------------------------------------
diff --git a/docs/os/tutorials/add_repos.md b/docs/os/tutorials/add_repos.md
index 43d1873..6c2137b 100644
--- a/docs/os/tutorials/add_repos.md
+++ b/docs/os/tutorials/add_repos.md
@@ -6,7 +6,7 @@ A repository is a version-ed Mynewt project, which is a collection of Mynewt
pac
 
 What differentiates a repository from a Mynewt project is the presence of a
 `repository.yml` file describing the repository. This will be described 
-below. For a basic understanding of repositories you may read the [Newt Tool Manual](../../newt/newt_intro.md)
and [How to create repos](../../newt/create_repo.md).
+below. For a basic understanding of repositories you may read the [Newt Tool Manual](../../newt/newt_intro.md)
and [How to create repos](create_repo.md).
 
 **Note:** For the remainder of this document we'll use the term repo as shorthand for a Mynewt
repository.
 
@@ -164,7 +164,7 @@ please use `0-latest` in the `vers` field in your repo descriptor.
     vers:0-latest
 ```
 
-See [Create a Repo](../../newt/create_repo) for a description of the versioning system and
all the possible ways to specify a version to use.
+See [Create a Repo](create_repo) for a description of the versioning system and all the possible
ways to specify a version to use.
 
 <br>
 

http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/42174396/docs/os/tutorials/project-slinky.md
----------------------------------------------------------------------
diff --git a/docs/os/tutorials/project-slinky.md b/docs/os/tutorials/project-slinky.md
new file mode 100644
index 0000000..f084939
--- /dev/null
+++ b/docs/os/tutorials/project-slinky.md
@@ -0,0 +1,139 @@
+## Project Sim Slinky  
+
+
+### Objective
+
+The goal of the project is to enable and demonstrate remote communications with the Mynewt
OS via newt manager (newtmgr). We will do this through building a project with Mynewt called
Slinky that runs via the native platform. 
+
+### What you need
+
+1.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
+
+* Install dependencies
+* Define a target using the newt tool
+* Build executables for the targets using the newt tool
+* Set up serial connection with the targets 
+* Create a connection profile using the newtmgr tool
+* Use the newtmgr tool to communicate with the targets
+
+### Installing newt
+
+If you have not already installed `newt` see the 
+[newt installation instructions](../../newt/install/newt_mac.md) and ensure newt is installed
an in your path.
+
+### Installing newtmgr
+
+If you have not already installed `newtmgr` see the 
+[newtmgr installation instructions](../../newtmgr/installing.md) and ensure newtmgr is installed
an in your path.
+
+### Creating a new project
+
+Instructions for creating a project are located in the [Getting Started](../get_started/project_create.md)
section of the [Mynewt OS Manual](../get_started/introduction.md)
+
+We will list only the steps here for brevity.  We will name the project
+`slinky`.
+
+```no-highlight
+    $ newt new slinky
+    Downloading project skeleton from apache/incubator-mynewt-blinky...
+    ...
+    Installing skeleton in slink...
+    Project slink successfully created
+    $ cd slinky
+    $ newt install -v
+    Downloading repository description for apache-mynewt-core... success!
+    ...
+    Repos successfully installed
+```
+
+### Setting up your target build
+
+Create a target for `slinky` using the native bsp. We will list only the steps and suppress
the tool output here for brevity.
+
+```no-highlight
+    $ newt target create sim_slinky
+    $ newt target set sim_slinky bsp=@apache-mynewt-core/hw/bsp/native
+    $ newt target set sim_slinky build_profile=debug
+    $ newt target set sim_slinky app=@apache-mynewt-core/apps/slinky
+```
+
+### Building Your target
+
+To build your target, use `newt build`.  When complete, an executable file
+is created.
+
+```no-highlight
+    $ newt build sim_slinky 
+    Compiling main.c
+    ...
+    Linking slinky.elf
+    App successfully built: ~/dev/slinky/bin/sim_slinky/apps/slinky/slinky.elf
+```
+
+### Run the 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
+when mynewt slinky starts.
+
+```no-highlight
+    $ ~/dev/slinky/bin/sim_slinky/apps/slinky/slinky.elf
+    uart0 at /dev/ttys005
+```
+
+<br>
+
+In this example, the slinky app opened up a com port `/dev/ttys005`
+for communications with newtmgr. 
+
+**NOTE:** This application will block. You will need to open a new console (or execute this
in another console) to continue the tutorial.*
+
+<br>
+
+### Setting up a connection profile
+
+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/ttys005
+    Connection profile sim1 successfully added
+    $ newtmgr conn show
+    Connection profiles: 
+      sim1: type=serial, connstring='/dev/ttys007'
+```
+
+### Executing newtmgr commands with the target
+
+You can now use connection profile `sim1` to talk to the running sim_blinky.
+As an example, we will query the running mynewt OS for the usage of its 
+memory pools.  
+
+```no-highlight
+    $ newtmgr -c sim1 mpstats
+    Return Code = 0
+      nffs_cache_inode_pool (blksize=36 nblocks=4 nfree=4)
+      nffs_cache_block_pool (blksize=32 nblocks=64 nfree=64)
+      nffs_dir_pool (blksize=8 nblocks=4 nfree=4)
+      default_mbuf_data (blksize=256 nblocks=10 nfree=8)
+      nffs_file_pool (blksize=12 nblocks=4 nfree=4)
+      nffs_inode_entry_pool (blksize=24 nblocks=100 nfree=98)
+      nffs_block_entry_pool (blksize=12 nblocks=100 nfree=100)
+```
+
+As a test command, you can send an arbitrary string to the target and it
+will echo that string back in a response to newtmgr.
+
+```no-highlight
+    $ newtmgr -c sim1 echo "Hello Mynewt"
+    {"r": "Hello Mynewt"}
+```
+
+The response comes back as a json string.
+
+In addition to these, you can also examine running tasks, statistics, 
+logs, image status (not on sim), and configuration.

http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/42174396/docs/os/tutorials/project-target-slinky.md
----------------------------------------------------------------------
diff --git a/docs/os/tutorials/project-target-slinky.md b/docs/os/tutorials/project-target-slinky.md
new file mode 100644
index 0000000..fd5ff31
--- /dev/null
+++ b/docs/os/tutorials/project-target-slinky.md
@@ -0,0 +1,190 @@
+## Project Slinky 
+
+
+### Objective
+
+The goal of the project is to enable and demonstrate remote communications with the Mynewt
OS via newt manager (newtmgr). We will do this through a project with Mynewt called Slinky
that runs on the STM32-E407 board.
+
+### 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
+
+* Install dependencies
+* Define a target using the newt tool
+* Build executables for the targets using the newt tool
+* Set up serial connection with the targets 
+* Create a connection profile using the newtmgr tool
+* Use the newtmgr tool to communicate with the targets
+
+### Install newt
+
+If you have not already installed `newt`, see the 
+[newt installation instructions](../../newt/install/newt_mac.md) and ensure newt is installed
an in your path.
+
+### Install newtmgr
+
+If you have not already installed `newtmgr`, see the 
+[newtmgr installation instructions](../../newtmgr/installing.md) and ensure newtmgr is installed
an in your path.
+
+### Create a new project
+
+Instructions for creating a project are located in the [Getting Started](../get_started/project_create.md)
section of the [Mynewt OS Manual](../get_started/introduction.md).
+
+If you already completed [sim slinky](project-slinky.md) you can skip this step.
+
+We will list only the steps here for brevity.  We will name the project
+`slinky`.
+
+```no-highlight
+$ newt new slinky
+Downloading project skeleton from apache/incubator-mynewt-blinky...
+...
+Installing skeleton in slink...
+Project slink successfully created
+$ cd slinky
+$newt install -v
+Downloading repository description for apache-mynewt-core... success!
+...
+Repos successfully installed
+```
+
+<br>
+
+### Set up your target builds
+
+Create a target for `stm32_slinky` using the native BSP. The Newt tool output is suppressed
below for brevity.
+
+```no-highlight
+$ newt target create stm32_slinky
+$ newt target set stm32_slinky bsp=@apache-mynewt-core/hw/bsp/olimex_stm32-e407_devboard
+$ newt target set stm32_slinky build_profile=debug
+$ newt target set stm32_slinky app=@apache-mynewt-core/apps/slinky
+```
+
+Create a second target for `stm32_bootloader` to build a bootloader to boot
+the `stm32_slinky` image.  The tool output is suppressed below for brevity.
+
+```no-highlight
+$ newt target create stm32_bootloader
+$ newt target set stm32_bootloader bsp=@apache-mynewt-core/hw/bsp/olimex_stm32-e407_devboard
+$ newt target set stm32_bootloader build_profile=optimized
+$ newt target set stm32_bootloader target.app=@apache-mynewt-core/apps/boot
+```
+
+<br>
+
+### Build Targets
+
+```no-highlight
+$ newt build stm32_slinky
+Compiling main.c
+...
+Linking slinky.elf
+App successfully built: ~/dev/slinky/bin/stm32_slinky/apps/slinky/slinky.elf
+```
+
+```no-highlight
+newt build stm32_bootloader
+Compiling crc16.c
+...
+Linking boot.elf
+App successfully built: ~/slinky/bin/stm32_bootloader/apps/boot/boot.elf
+```
+
+For the main image, you need to create an image using newt create-image.
+Give this image some arbitrary version number "1.2.3".
+
+```no-highlight
+$ newt create-image stm32_slinky 1.2.3
+App image succesfully generated: /Users/paulfdietrich/dev/slinky/bin/stm32_slinky/apps/slinky/slinky.img
+Build manifest: /Users/paulfdietrich/dev/slinky/bin/stm32_slinky/apps/slinky/manifest.json
+```
+
+<br>
+
+### 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. 
+
+```no-highlight
+$ newt load stm32_bootloader
+$ newt load stm32_slinky
+```
+
+You can now disconnect the debugging cable from the board. You should see the green LED blinking.
If not, try powercycling the board.
+
+<br>
+
+* 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.
+
+<br>
+
+* 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
+```
+
+<br>
+
+* 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'
+```
+
+<br>
+
+* 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 : 1.2.3
+    $ newtmgr -c olimex01 taskstats
+    Return Code = 0
+      newtmgr (prio=4 tid=2 runtime=0 cswcnt=12 stksize=512 stkusage=255 last_checkin=0 next_checkin=0)
+      task1 (prio=1 tid=3 runtime=0 cswcnt=299 stksize=128 stkusage=33 last_checkin=0 next_checkin=0)
+      task2 (prio=2 tid=4 runtime=0 cswcnt=300 stksize=128 stkusage=31 last_checkin=0 next_checkin=0)
+      idle (prio=255 tid=0 runtime=299916 cswcnt=313 stksize=32 stkusage=18 last_checkin=0
next_checkin=0)
+      shell (prio=3 tid=1 runtime=1 cswcnt=20 stksize=384 stkusage=60 last_checkin=0 next_checkin=0)
+```
+
+
+
+
+
+
+
+
+
+

http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/42174396/mkdocs.yml
----------------------------------------------------------------------
diff --git a/mkdocs.yml b/mkdocs.yml
index 64b74c4..f023150 100644
--- a/mkdocs.yml
+++ b/mkdocs.yml
@@ -25,13 +25,13 @@ pages:
         - 'Blinky on Olimex': 'os/tutorials/olimex.md'
         - 'Blinky on STM32F303': 'os/tutorials/STM32F303.md'
         - 'Blinky on nRF52': 'os/tutorials/nRF52.md'
-        - 'Define a target': 'os/tutorials/define_target.md'
         - 'Add repo to project': 'os/tutorials/add_repos.md'
         - 'Create a repo': 'os/tutorials/create_repo.md'
         - 'Upgrade a repo': 'os/tutorials/upgrade_repo.md'
+        - 'Enable remote comms on sim device': 'os/tutorials/project-slinky.md'
+        - 'Enable Remote comms on STM32 board': 'os/tutorials/project-target-slinky.md'
         - 'Write a Test Suite for a Package': 'os/tutorials/unit_test.md'
         - 'Air-quality Sensor project': 'os/tutorials/air_quality_sensor.md'
-        - 'Enable BLE using nimBLE': 'os/tutorials/bletiny_project.md'
         - 'Add task to manage multiple events': 'os/tutorials/event_queue.md'
     - OS User Guide:
         - toc: 'os/os_user_guide.md'
@@ -328,9 +328,6 @@ pages:
 - Newt Manager Manual:
     - 'Introduction': 'newtmgr/overview.md'
     - 'Install': 'newtmgr/installing.md'
-    - Tutorials:
-        - 'Sim Slinky': 'newtmgr/project-slinky.md'
-        - 'Target Slinky': 'newtmgr/project-target-slinky.md'
     - Manual:
         - 'Protocol': 'newtmgr/protocol.md'
 - Appendix:


Mime
View raw message