mynewt-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ad...@apache.org
Subject [2/2] incubator-mynewt-site git commit: Cleaned up links and instructions in Quick Start or getting started lessons. This closes pull request #61
Date Sat, 19 Mar 2016 07:01:45 GMT
Cleaned up links and instructions in Quick Start or getting started lessons. This closes pull request #61


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

Branch: refs/heads/asf-site
Commit: 00265afef38437c6f75e4c17db29e61e65b48f1c
Parents: 5a1122a
Author: aditihilbert <aditi@runtime.io>
Authored: Sat Mar 19 00:01:34 2016 -0700
Committer: aditihilbert <aditi@runtime.io>
Committed: Sat Mar 19 00:01:34 2016 -0700

----------------------------------------------------------------------
 mkdocs/search_index.json                 |  54 +++----
 os/get_started/cross_tools/index.html    |  83 +++++++----
 os/get_started/introduction/index.html   | 126 +---------------
 os/get_started/native_tools/index.html   |  43 ++++--
 os/get_started/project_create/index.html | 203 +++++++++++++++-----------
 sitemap.xml                              |  22 +--
 6 files changed, 237 insertions(+), 294 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/00265afe/mkdocs/search_index.json
----------------------------------------------------------------------
diff --git a/mkdocs/search_index.json b/mkdocs/search_index.json
index 1baa47f..6fa4e5c 100644
--- a/mkdocs/search_index.json
+++ b/mkdocs/search_index.json
@@ -72,7 +72,7 @@
         }, 
         {
             "location": "/os/get_started/introduction/", 
-            "text": "Introduction\n\n\nWelcome to Apache Mynewt\n\n\nApache Mynewt is an operating system that makes it easy to develop\napplications for microcontroller environments where power and cost \nare driving factors. Examples of these devices are connected locks, \nlights, and wearables.\n\n\nMicrocontroller environments have a number of characteristics that \nmakes the operating system requirements for them unique: \n\n\n\n\n\n\nLow memory footprint: memory on these systems range from \n8-16KB (on the low end) to 16MB (on the high end).\n\n\n\n\n\n\nReduced code size: code often runs out of flash, and total available code size ranges from 64-128KB to 16-32MB.\n\n\n\n\n\n\nLow processing speed: processor speeds vary from 10-12MHz to 160-200MHz.  \n\n\n\n\n\n\nLow power operation: devices operate in mostly sleeping mode, in order to conserve\nbattery power and maximize power usage.\n\n\n\n\n\n\nAs more and more devices get connected, these interconnected devices perform com
 plex tasks. To\nperform these tasks, you need low-level operational functionality built into the operating system.\nTypically, connected devices built with these microcontrollers perform a myriad of functions: \n\n\n\n\n\n\nNetworking Stacks: Bluetooth Low Energy and Thread\n\n\n\n\n\n\nPeripherals: PWM to drive motors, ADCs to measure sensor data, and RTCs\nto keep time.\n\n\n\n\n\n\nScheduled Processing: actions must happen on a calendared or periodic basis.\n\n\n\n\n\n\nApache Mynewt accomplishes all the above easily, by providing a complete\noperating system for constrained devices, including:\n\n\n\n\n\n\nA fully open-source Bluetooth Low Energy stack with both Host and \nController implementations. \n\n\n\n\n\n\nA pre-emptive, multi-tasking Real Time operating system kernel\n\n\n\n\n\n\nA Hardware Abstraction Layer (HAL) that abstracts the MCU's \nperipheral functions, allowing developers to easily write cross-platform\ncode.\n\n\n\n\n\n\n\n\nNewt\n\n\nIn order to provide all 
 this functionality, and operate in an \nextremely low resource environment, Mynewt provides a very fine-grained source \npackage management and build system tool, called \nnewt\n. \n\n\nYou can install and build \nnewt\n for \nLinux\n or \nMac\n. \n\n\n\n\nBuild your first Mynewt App with Newt\n\n\nBefore you start your first Mynewt application, you must first create a new Mynewt\nproject with the \nnewt\n tool: \n\n\n$ newt new my_project\nDownloading project skeleton from apache/incubator-mynewt-blinky...\nInstalling skeleton in my_app...\nProject my_app successfully created.\n\n\n\n\n\n\n\nNewt populates this new project with a base skeleton of a new Apache Mynewt \nproject.  It has the following structure:\n\n\n$ cd my_project\n$ tree -L 3\n.\n\u251c\u2500\u2500 DISCLAIMER\n\u251c\u2500\u2500 LICENSE\n\u251c\u2500\u2500 NOTICE\n\u251c\u2500\u2500 README.md\n\u251c\u2500\u2500 apps\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 blinky\n\u2502\u00a0\u00a0     \u251c\u2500\u2500 pkg.yml\n\
 u2502\u00a0\u00a0     \u2514\u2500\u2500 src\n\u251c\u2500\u2500 project.yml\n\u2514\u2500\u2500 targets\n    \u251c\u2500\u2500 my_blinky_sim\n    \u2502\u00a0\u00a0 \u251c\u2500\u2500 pkg.yml\n    \u2502\u00a0\u00a0 \u2514\u2500\u2500 target.yml\n    \u2514\u2500\u2500 unittest\n        \u251c\u2500\u2500 pkg.yml\n        \u2514\u2500\u2500 target.yml\n\n6 directories, 10 files\n$ \n\n\n\n\n\nOnce you've switched into your new project's directory, the next step is to fetch\nany dependencies this project has.  By default, all Newt projects rely on a single\nremote repository, apache-mynewt-core.  Newt install will fetch this locally:\n\n\n$ newt install\napache-mynewt-core\n$\n\n\n\n\n\nNOTE:\n \napache-mynewt-core\n may take a while to download, to see progress, use the \n-v\n (verbose) option to install. \n\n\nOnce \nnewt install\n has successfully finished, the contents of \napache-mynewt-core\n\nwill have been downloaded into your local directory.  You can view them by issuing 
 the \nfollowing commands in the base directory of the new project:\n\n\n$ cd repos/apache-mynewt-core\n$ tree -L2\n.\n\nsnip\n\n\u251c\u2500\u2500 fs\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 fs\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 nffs\n\u251c\u2500\u2500 hw\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 bsp\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 hal\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 mcu\n\u251c\u2500\u2500 libs\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 baselibc\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 bootutil\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 cmsis-core\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 console\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 elua\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 flash_test\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 imgmgr\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 json\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 mbedtls\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 newtmgr\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 os\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 shell\n\u2502\u00a0\u00a0 \u251c
 \u2500\u2500 testreport\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 testutil\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 util\n\u251c\u2500\u2500 net\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 nimble\n\nsnip\n\n\n\n\n\n\n\n\nAs you can see, the core of the Apache Mynewt operating system has been brought \ninto your local directory!  \n\n\nNew projects created with Newt, come with by default an example application \n(\napps/blinky\n) and an example target (\nmy_blinky_sim\n) which allows you to \nbuild that application for the simulated platform.  \n\n\nWith your new project, all you need to build and run your new application is to \nissue the following commands: \n\n\n$ newt build my_blinky_sim \nCompiling base64.c\nCompiling cbmem.c\nCompiling datetime.c\nCompiling tpq.c\nArchiving util.a\nCompiling main.c\nArchiving blinky.a\nCompiling flash_map.c\nCompiling hal_flash.c\nArchiving hal.a\nCompiling cons_fmt.c\nCompiling cons_tty.c\n\nsnip\n\nLinking blinky.elf\nApp successfully built: /Users/ste
 rling/dev/tmp/my_app/bin/my_blinky_sim/apps/blinky/blinky.elf\n$ newt run my_blinky_sim\n(runs target my_blinky_sim on the simulator)\n\n\n\n\n\n\n\nAt this point you have your first Mynewt application!\n\n\nApache Mynewt has a lot more functionality than just running simulated applications.  It provides all \nthe features you'll need to cross-compile your application, run it on real hardware and develop a \nfull featured application.\n\n\nIf you're interested in learning more, a good next step is to choose a project to \n\nget started\n with, and begin to familiarize \nyourself with operating within the newt environment.  These projects will get your toolchain installed, \nand get you blinking an LED with the Apache Mynewt OS.\n\n\nAfter you've tried a few getting started projects, there are plenty of tutorials that will help \nexpose you to much of the functionality provided by the Apache Mynewt Core Operating System.   There is \nalso full reference documentation for all of the C
 ore Apache Mynewt APIs.\n\n\nHappy Hacking!", 
+            "text": "Introduction\n\n\nWelcome to Apache Mynewt\n\n\nApache Mynewt is an operating system that makes it easy to develop\napplications for microcontroller environments where power and cost \nare driving factors. Examples of these devices are connected locks, \nlights, and wearables.\n\n\nMicrocontroller environments have a number of characteristics that \nmakes the operating system requirements for them unique: \n\n\n\n\n\n\nLow memory footprint: memory on these systems range from \n8-16KB (on the low end) to 16MB (on the high end).\n\n\n\n\n\n\nReduced code size: code often runs out of flash, and total available code size ranges from 64-128KB to 16-32MB.\n\n\n\n\n\n\nLow processing speed: processor speeds vary from 10-12MHz to 160-200MHz.  \n\n\n\n\n\n\nLow power operation: devices operate in mostly sleeping mode, in order to conserve\nbattery power and maximize power usage.\n\n\n\n\n\n\nAs more and more devices get connected, these interconnected devices perform com
 plex tasks. To\nperform these tasks, you need low-level operational functionality built into the operating system.\nTypically, connected devices built with these microcontrollers perform a myriad of functions: \n\n\n\n\n\n\nNetworking Stacks: Bluetooth Low Energy and Thread\n\n\n\n\n\n\nPeripherals: PWM to drive motors, ADCs to measure sensor data, and RTCs\nto keep time.\n\n\n\n\n\n\nScheduled Processing: actions must happen on a calendared or periodic basis.\n\n\n\n\n\n\nApache Mynewt accomplishes all the above easily, by providing a complete\noperating system for constrained devices, including:\n\n\n\n\n\n\nA fully open-source Bluetooth Low Energy stack with both Host and \nController implementations. \n\n\n\n\n\n\nA pre-emptive, multi-tasking Real Time operating system kernel\n\n\n\n\n\n\nA Hardware Abstraction Layer (HAL) that abstracts the MCU's \nperipheral functions, allowing developers to easily write cross-platform\ncode.\n\n\n\n\n\n\n\n\nNewt\n\n\nIn order to provide all 
 this functionality, and operate in an \nextremely low resource environment, Mynewt provides a very fine-grained source \npackage management and build system tool, called \nnewt\n. \n\n\nYou can install and build \nnewt\n for \nLinux\n or \nMac\n. \n\n\n\n\nBuild your first Mynewt App with Newt\n\n\nWith the introductions out of the way, now is a good time to \nget\nstarted\n with your first Mynewt application.\n\n\nHappy Hacking!", 
             "title": "Introduction"
         }, 
         {
@@ -92,7 +92,7 @@
         }, 
         {
             "location": "/os/get_started/introduction/#build-your-first-mynewt-app-with-newt", 
-            "text": "Before you start your first Mynewt application, you must first create a new Mynewt\nproject with the  newt  tool:   $ newt new my_project\nDownloading project skeleton from apache/incubator-mynewt-blinky...\nInstalling skeleton in my_app...\nProject my_app successfully created.   Newt populates this new project with a base skeleton of a new Apache Mynewt \nproject.  It has the following structure:  $ cd my_project\n$ tree -L 3\n.\n\u251c\u2500\u2500 DISCLAIMER\n\u251c\u2500\u2500 LICENSE\n\u251c\u2500\u2500 NOTICE\n\u251c\u2500\u2500 README.md\n\u251c\u2500\u2500 apps\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 blinky\n\u2502\u00a0\u00a0     \u251c\u2500\u2500 pkg.yml\n\u2502\u00a0\u00a0     \u2514\u2500\u2500 src\n\u251c\u2500\u2500 project.yml\n\u2514\u2500\u2500 targets\n    \u251c\u2500\u2500 my_blinky_sim\n    \u2502\u00a0\u00a0 \u251c\u2500\u2500 pkg.yml\n    \u2502\u00a0\u00a0 \u2514\u2500\u2500 target.yml\n    \u2514\u2500\u2500 unittest\n        \u251c\u2500
 \u2500 pkg.yml\n        \u2514\u2500\u2500 target.yml\n\n6 directories, 10 files\n$   Once you've switched into your new project's directory, the next step is to fetch\nany dependencies this project has.  By default, all Newt projects rely on a single\nremote repository, apache-mynewt-core.  Newt install will fetch this locally:  $ newt install\napache-mynewt-core\n$  NOTE:   apache-mynewt-core  may take a while to download, to see progress, use the  -v  (verbose) option to install.   Once  newt install  has successfully finished, the contents of  apache-mynewt-core \nwill have been downloaded into your local directory.  You can view them by issuing the \nfollowing commands in the base directory of the new project:  $ cd repos/apache-mynewt-core\n$ tree -L2\n. snip \n\u251c\u2500\u2500 fs\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 fs\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 nffs\n\u251c\u2500\u2500 hw\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 bsp\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 hal\n\
 u2502\u00a0\u00a0 \u2514\u2500\u2500 mcu\n\u251c\u2500\u2500 libs\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 baselibc\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 bootutil\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 cmsis-core\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 console\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 elua\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 flash_test\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 imgmgr\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 json\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 mbedtls\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 newtmgr\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 os\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 shell\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 testreport\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 testutil\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 util\n\u251c\u2500\u2500 net\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 nimble snip    As you can see, the core of the Apache Mynewt operating system has been brought \ninto your local directory!    New projects created with Newt, come with
  by default an example application \n( apps/blinky ) and an example target ( my_blinky_sim ) which allows you to \nbuild that application for the simulated platform.    With your new project, all you need to build and run your new application is to \nissue the following commands:   $ newt build my_blinky_sim \nCompiling base64.c\nCompiling cbmem.c\nCompiling datetime.c\nCompiling tpq.c\nArchiving util.a\nCompiling main.c\nArchiving blinky.a\nCompiling flash_map.c\nCompiling hal_flash.c\nArchiving hal.a\nCompiling cons_fmt.c\nCompiling cons_tty.c snip \nLinking blinky.elf\nApp successfully built: /Users/sterling/dev/tmp/my_app/bin/my_blinky_sim/apps/blinky/blinky.elf\n$ newt run my_blinky_sim\n(runs target my_blinky_sim on the simulator)   At this point you have your first Mynewt application!  Apache Mynewt has a lot more functionality than just running simulated applications.  It provides all \nthe features you'll need to cross-compile your application, run it on real hardware and d
 evelop a \nfull featured application.  If you're interested in learning more, a good next step is to choose a project to  get started  with, and begin to familiarize \nyourself with operating within the newt environment.  These projects will get your toolchain installed, \nand get you blinking an LED with the Apache Mynewt OS.  After you've tried a few getting started projects, there are plenty of tutorials that will help \nexpose you to much of the functionality provided by the Apache Mynewt Core Operating System.   There is \nalso full reference documentation for all of the Core Apache Mynewt APIs.  Happy Hacking!", 
+            "text": "With the introductions out of the way, now is a good time to  get\nstarted  with your first Mynewt application.  Happy Hacking!", 
             "title": "Build your first Mynewt App with Newt"
         }, 
         {
@@ -107,7 +107,7 @@
         }, 
         {
             "location": "/os/get_started/native_tools/", 
-            "text": "Installing Native Mynewt Tools\n\n\nThis page shows how to install tools for native Mynewt targets. This\nallows you to run Mynewt OS as a native application.  It also allows\nyou to run the test suites for all packages not requiring HW support. \n\n\nThis page provides guidance for MAC and Linux. See the relevant sections below.\n\n\nSet up toolchain for Mac\n\n\nInstall Brew\n\n\nIf you have not already installed Homebrew from the \n\nnewt\n tutorials pages\n, install it. \n\n\nInstall gcc/libc\n\n\nUse brew to install gcc.\n\n\n        $ brew install gcc\n        ...\n        ...\n        ==\n Summary\n        \ud83c\udf7a  /usr/local/Cellar/gcc/5.2.0: 1353 files, 248M\n\n\n\n\n\nInstall gdb\n\n\n        $ brew install gdb\n        ...\n        ...\n        ==\n Summary\n        \ud83c\udf7a  /usr/local/Cellar/gdb/7.10.1: XXX files,YYM\n\n\n\n\n\nNOTE: When running a program with gdb, you may need to sign your gdb\nexecutable.  \nThis page\n\nshows a recipe f
 or gdb signing. Alternately you can skip this step and\ncontinue without the ability to debug your mynewt application on your PC.\n\n\nSet up toolchain for Linux\n\n\nInstall gcc/libc that will produce 32-bit executables:\n\n\n        $ sudo apt-get install gcc-multilib libc6-i386\n\n\n\n\n\nInstall gdb\n\n\n$sudo apt-get install gdb\n\nReading package lists... Done\nBuilding dependency tree       \nReading state information... Done\nSuggested packages:\n  gdb-doc gdbserver\nThe following NEW packages will be installed:\n  gdb\n...\nProcessing triggers for man-db (2.6.7.1-1ubuntu1) ...\nSetting up gdb (7.7.1-0ubuntu5~14.04.2) ...\n$ \n\n\n\n\n\nAt this point you have installed all the necessary software to build and test code on a simluator for Linux. Proceed to the \nBuild test code on simulator\n section.", 
+            "text": "Installing Native Mynewt Tools\n\n\nThis page shows how to install tools for native Mynewt targets. This\nallows you to run Mynewt OS as a native application.  It also allows\nyou to run the test suites for all packages not requiring HW support. \n\n\nThis page provides guidance for MAC and Linux. See the relevant sections below.\n\n\n\n\nSet up toolchain for Mac\n\n\nInstall Brew\n\n\nIf you have not already installed Homebrew from the \n\nnewt\n tutorials pages\n, install it. \n\n\n\n\nInstall gcc/libc\n\n\nOS X ships with a C compiler called Clang.  To build applications for the Mynewt simulator, you will need a different compiler: gcc.\n\n\n$ brew install gcc\n...\n...\n==\n Summary\n\ud83c\udf7a  /usr/local/Cellar/gcc/5.2.0: 1353 files, 248M\n\n\n\n\n\n\n\nInstall gdb\n\n\n$ brew install gdb\n...\n...\n==\n Summary\n\ud83c\udf7a  /usr/local/Cellar/gdb/7.10.1: XXX files,YYM\n\n\n\n\n\n\n\nNOTE:\n When running a program with gdb, you may need to sign your gdb
 \nexecutable.  \nThis page\n\nshows a recipe for gdb signing. Alternately you can skip this step and\ncontinue without the ability to debug your mynewt application on your PC.*\n\n\n\n\nSet up toolchain for Linux\n\n\nThe below procedure can be used to set up a Debian-based Linux system (e.g.,\nUbuntu).  If you are running a different Linux distribution, you will need to\nsubstitute invocations of \napt-get\n in the below steps with the package manager\nthat your distro uses.\n\n\n\n\nInstall gcc/libc that will produce 32-bit executables:\n\n\n$ sudo apt-get install gcc-multilib libc6-i386\n\n\n\n\n\n\n\nInstall gdb\n\n\n$ sudo apt-get install gdb\n\nReading package lists... Done\nBuilding dependency tree       \nReading state information... Done\nSuggested packages:\n  gdb-doc gdbserver\nThe following NEW packages will be installed:\n  gdb\n...\nProcessing triggers for man-db (2.6.7.1-1ubuntu1) ...\nSetting up gdb (7.7.1-0ubuntu5~14.04.2) ...\n\n\n\n\n\n\n\nAt this point you have i
 nstalled all the necessary software to build and test code on a simluator for Linux. Proceed to the \nBuild test code on simulator\n section.", 
             "title": "Install Native Tools"
         }, 
         {
@@ -127,17 +127,17 @@
         }, 
         {
             "location": "/os/get_started/native_tools/#install-gcclibc", 
-            "text": "Use brew to install gcc.          $ brew install gcc\n        ...\n        ...\n        ==  Summary\n        \ud83c\udf7a  /usr/local/Cellar/gcc/5.2.0: 1353 files, 248M", 
+            "text": "OS X ships with a C compiler called Clang.  To build applications for the Mynewt simulator, you will need a different compiler: gcc.  $ brew install gcc\n...\n...\n==  Summary\n\ud83c\udf7a  /usr/local/Cellar/gcc/5.2.0: 1353 files, 248M", 
             "title": "Install gcc/libc"
         }, 
         {
             "location": "/os/get_started/native_tools/#install-gdb", 
-            "text": "$ brew install gdb\n        ...\n        ...\n        ==  Summary\n        \ud83c\udf7a  /usr/local/Cellar/gdb/7.10.1: XXX files,YYM  NOTE: When running a program with gdb, you may need to sign your gdb\nexecutable.   This page \nshows a recipe for gdb signing. Alternately you can skip this step and\ncontinue without the ability to debug your mynewt application on your PC.", 
+            "text": "$ brew install gdb\n...\n...\n==  Summary\n\ud83c\udf7a  /usr/local/Cellar/gdb/7.10.1: XXX files,YYM   NOTE:  When running a program with gdb, you may need to sign your gdb\nexecutable.   This page \nshows a recipe for gdb signing. Alternately you can skip this step and\ncontinue without the ability to debug your mynewt application on your PC.*", 
             "title": "Install gdb"
         }, 
         {
             "location": "/os/get_started/native_tools/#set-up-toolchain-for-linux", 
-            "text": "", 
+            "text": "The below procedure can be used to set up a Debian-based Linux system (e.g.,\nUbuntu).  If you are running a different Linux distribution, you will need to\nsubstitute invocations of  apt-get  in the below steps with the package manager\nthat your distro uses.", 
             "title": "Set up toolchain for Linux"
         }, 
         {
@@ -147,12 +147,12 @@
         }, 
         {
             "location": "/os/get_started/native_tools/#install-gdb_1", 
-            "text": "$sudo apt-get install gdb\n\nReading package lists... Done\nBuilding dependency tree       \nReading state information... Done\nSuggested packages:\n  gdb-doc gdbserver\nThe following NEW packages will be installed:\n  gdb\n...\nProcessing triggers for man-db (2.6.7.1-1ubuntu1) ...\nSetting up gdb (7.7.1-0ubuntu5~14.04.2) ...\n$   At this point you have installed all the necessary software to build and test code on a simluator for Linux. Proceed to the  Build test code on simulator  section.", 
+            "text": "$ sudo apt-get install gdb\n\nReading package lists... Done\nBuilding dependency tree       \nReading state information... Done\nSuggested packages:\n  gdb-doc gdbserver\nThe following NEW packages will be installed:\n  gdb\n...\nProcessing triggers for man-db (2.6.7.1-1ubuntu1) ...\nSetting up gdb (7.7.1-0ubuntu5~14.04.2) ...   At this point you have installed all the necessary software to build and test code on a simluator for Linux. Proceed to the  Build test code on simulator  section.", 
             "title": "Install gdb"
         }, 
         {
             "location": "/os/get_started/project_create/", 
-            "text": "Create Your First Mynewt Project\n\n\nThis page shows how to create a Mynewt Project using the \nnewt\n command-line tool.\n\n\nPre-Requisites\n\n\n\n\nEnsure you have installed \nnewt\n and that the \nnewt command is in your system path. \n\n\nYou must have Internet connectivity to fetch remote Mynewt components.\n\n\nYou must \ninstall the compiler tools\n to \nsupport native compiling to build the project this tutorial creates.  \n\n\n\n\n\n\nNewt New\n\n\nChoose a project name. For this tutorial we will call this project \nmyproj\n.\nEnter the \nnewt new myproj\n command. \n\n\n    $ newt new myproj\n    Downloading project skeleton from apache/incubator-mynewt-blinky...\n    Installing skeleton in myproj...\n    Project myproj successfully created.\n\n\n\n\n\n\n\nThe \nnewt\n tool has created a project directory structure like the one below:\n\n\n    \u2500\u2500\u2500 myproj\n        \u251c\u2500\u2500 DISCLAIMER\n        \u251c\u2500\u2500 LICENSE\n      
   \u251c\u2500\u2500 NOTICE\n        \u251c\u2500\u2500 README.md\n        \u251c\u2500\u2500 apps\n        \u2502\u00a0\u00a0 \u2514\u2500\u2500 blinky\n        \u2502\u00a0\u00a0     \u251c\u2500\u2500 pkg.yml\n        \u2502\u00a0\u00a0     \u2514\u2500\u2500 src\n        \u2502\u00a0\u00a0         \u2514\u2500\u2500 main.c\n        \u251c\u2500\u2500 project.yml\n        \u2514\u2500\u2500 targets\n            \u251c\u2500\u2500 my_blinky_sim\n            \u2502\u00a0\u00a0 \u251c\u2500\u2500 pkg.yml\n            \u2502\u00a0\u00a0 \u2514\u2500\u2500 target.yml\n            \u2514\u2500\u2500 unittest\n                \u251c\u2500\u2500 pkg.yml\n                \u2514\u2500\u2500 target.yml\n\n\n\n\n\n\n\nnewt\n has installed the base files for a project comprising the following.\n\n\n\n\nfile \nproject.yml\n contains the repository list that the project uses to fetch\nits packages. Your project is a collection of repositories.  In this case, the project just\ncomprises the core
  mynewt repository.  Later you will add more repositories\nto include other mynewt components.\n\n\nthe file \napps/blinky/pkg.yml\n contains the description of your application\nand its package dependencies.\n\n\nA target directory containing \nmy_blinky_sim\n, a target descriptor used to\nbuild a version of myproj.  Use \nnewt target show\n to see available build \ntargets.\n\n\nA non-build-able target called \nunittest\n.  This is used\ninternally by \nnewt\n and is not a formal build target.\n\n\n\n\nNOTE:\n the actual code and package files are not installed \n(except the template for \nmain.c\n).  See the next step for installing the packages.\n\n\n\n\nNewt Install\n\n\nChange into the \nmyproj\n directory.  Then ask newt to install all the \nproject package dependencies using \nnewt install\n.\n\n\n    $ newt install -v \n    apache-mynewt-core\n    Downloading repository description for apache-mynewt-core... success!\n    Downloading repository incubator-mynewt-core (branch:
  master; commit: mynewt_0_8_0_b2_tag) at https://github.com/apache/incubator-mynewt-core.git\n    Cloning into \n/var/folders/7l/7b3w9m4n2mg3sqmgw2q1b9p80000gn/T/newt-repo969988348\n...\n    remote: Counting objects: 17935, done.\n    remote: Compressing objects: 100% (234/234), done.\n    remote: Total 17935 (delta 101), reused 0 (delta 0), pack-reused 17686\n    Receiving objects: 100% (17935/17935), 6.18 MiB | 315.00 KiB/s, done.\n    Resolving deltas: 100% (10541/10541), done.\n    Checking connectivity... done.\n    apache-mynewt-core successfully installed version 0.7.9-none\n    $ \n\n\n\n\n\nNow you will have installed packages required to build your project. Note in \nthe package you now have dependent packages stored in the \nrepos\n directory\nunder the specific repository you have included in the base project.  \n\n\n    .\n    \u251c\u2500\u2500 apps\n    \u2502\u00a0\u00a0 \u2514\u2500\u2500 blinky\n    \u2502\u00a0\u00a0     \u2514\u2500\u2500 src\n    \u251c\u2500\u2
 500 repos\n    \u2502\u00a0\u00a0 \u2514\u2500\u2500 apache-mynewt-core\n    \u2502\u00a0\u00a0     \u251c\u2500\u2500 apps\n    \u2502\u00a0\u00a0     \u251c\u2500\u2500 compiler\n    \u2502\u00a0\u00a0     \u251c\u2500\u2500 fs\n    \u2502\u00a0\u00a0     \u251c\u2500\u2500 hw\n    \u2502\u00a0\u00a0     \u251c\u2500\u2500 libs\n    \u2502\u00a0\u00a0     \u251c\u2500\u2500 net\n    \u2502\u00a0\u00a0     \u251c\u2500\u2500 scripts\n    \u2502\u00a0\u00a0     \u251c\u2500\u2500 sys\n    \u2502\u00a0\u00a0     \u2514\u2500\u2500 targets\n    \u2514\u2500\u2500 targets\n        \u251c\u2500\u2500 my_blinky_sim\n        \u2514\u2500\u2500 unittest\n\n\n\n\n\nWithin each of these directories are the packages required to build your\nproject for the various targets.\n\n\n\n\nTesting the Project\n\n\nTo validate, you can also run all the units test through simulation.\n\n\n    $ newt test all\n    ...lots of compiling and testing...\n    ...about 2 minutes later ...\n    Archiving bootut
 il.a\n    Linking test_bootutil\n    Executing test: /myproj/bin/unittest/libs/bootutil/test_bootutil\n    Passed tests: [net/nimble/host fs/nffs libs/os hw/hal libs/mbedtls libs/util sys/config libs/bootutil]\n    All tests passed\n\n\n\n\n\n\n\nBuilding the Project\n\n\nTo build the project you can use \nnewt build\n using the target \n\n\n    $ newt build my_blinky_sim\n    App successfully built: /bin/my_blinky_sim/apps/blinky/blinky.elf\n\n\n\n\n\n\n\nYou can run the simulated version of your project and see the simulated LED\nblink\n\n\n    ./bin/my_blinky_sim/apps/blinky/blinky.elf\n    hal_gpio set pin  1 to 0\n\n\n\n\n\nJust do \nctrl-c\n to exit.\n\n\n\n\nComplete\n\n\nCongratulations, you have created your first project!  This project contains \nthe core OS, a simple application to blink an LED and all of the dependencies\nrequired.", 
+            "text": "Create Your First Mynewt Project\n\n\nThis page shows how to create a Mynewt Project using the \nnewt\n command-line tool.\n\n\n\n\nPre-Requisites\n\n\n\n\nEnsure you have installed \nnewt\n and that the \nnewt command is in your system path. \n\n\nYou must have Internet connectivity to fetch remote Mynewt components.\n\n\nYou must \ninstall the compiler tools\n to \nsupport native compiling to build the project this tutorial creates.  \n\n\n\n\n\n\nNewt New\n\n\nChoose a project name. For this tutorial we will call this project \nmyproj\n.\nEnter the \nnewt new myproj\n command. \n\n\n$ newt new myproj\nDownloading project skeleton from apache/incubator-mynewt-blinky...\nInstalling skeleton in myproj...\nProject myproj successfully created.\n\n\n\n\n\n\n\nNewt populates this new project with a base skeleton of a new Apache Mynewt \nproject.  It has the following structure:\n\n\n$ cd myproj\n$ tree -L 3\n.\n\u251c\u2500\u2500 DISCLAIMER\n\u251c\u2500\u2500 LICEN
 SE\n\u251c\u2500\u2500 NOTICE\n\u251c\u2500\u2500 README.md\n\u251c\u2500\u2500 apps\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 blinky\n\u2502\u00a0\u00a0     \u251c\u2500\u2500 pkg.yml\n\u2502\u00a0\u00a0     \u2514\u2500\u2500 src\n\u251c\u2500\u2500 project.yml\n\u2514\u2500\u2500 targets\n    \u251c\u2500\u2500 my_blinky_sim\n    \u2502\u00a0\u00a0 \u251c\u2500\u2500 pkg.yml\n    \u2502\u00a0\u00a0 \u2514\u2500\u2500 target.yml\n    \u2514\u2500\u2500 unittest\n        \u251c\u2500\u2500 pkg.yml\n        \u2514\u2500\u2500 target.yml\n\n6 directories, 10 files\n\n\n\n\n\n\n\nThe Newt tool has installed the base files for a project comprising the following:\n\n\n\n\nthe file \nproject.yml\n contains the repository list that the project uses to fetch\nits packages. Your project is a collection of repositories.  In this case, the project just\ncomprises the core mynewt repository.  Later you will add more repositories\nto include other mynewt components.\n\n\nthe file \napps/blinky/pkg
 .yml\n contains the description of your application\nand its package dependencies.\n\n\nA target directory containing \nmy_blinky_sim\n, a target descriptor used to\nbuild a version of myproj.  Use \nnewt target show\n to see available build \ntargets.\n\n\nA non-buildable target called \nunittest\n.  This is used\ninternally by \nnewt\n and is not a formal build target.\n\n\n\n\nNOTE:\n the actual code and package files are not installed \n(except the template for \nmain.c\n).  See the next step for installing the packages.\n\n\n\n\nNewt Install\n\n\nOnce you've switched into your new project's directory, the next step is to fetch\nany dependencies this project has.  By default, all Newt projects rely on a\nsingle remote repository, apache-mynewt-core.  The \nnewt install\n command will\nfetch this repository.\n\n\n$ newt install\napache-mynewt-core\n\n\n\n\n\nNOTE:\n \napache-mynewt-core\n may take a while to download.  To see progress,\nuse the \n-v\n (verbose) option to install.
  \n\n\nOnce \nnewt install\n has successfully finished, the contents of \napache-mynewt-core\n will have been downloaded into your local directory.  You can view them by issuing the following commands in the base directory of the new project:\n\n\n$ tree -L 2 repos/apache-mynewt-core/\n.\n\nsnip\n\n\u251c\u2500\u2500 fs\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 fs\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 nffs\n\u251c\u2500\u2500 hw\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 bsp\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 hal\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 mcu\n\u251c\u2500\u2500 libs\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 baselibc\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 bootutil\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 cmsis-core\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 console\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 elua\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 flash_test\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 imgmgr\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 json\n\u2502\u00a0\u00a0 \u251c\u2500\u2
 500 mbedtls\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 newtmgr\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 os\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 shell\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 testreport\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 testutil\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 util\n\u251c\u2500\u2500 net\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 nimble\n\nsnip\n\n\n\n\n\n\nAs you can see, the core of the Apache Mynewt operating system has been brought \ninto your local directory!  \n\n\n\n\nTest the project's packages\n\n\nUse the following command to execute a package's unit tests:\n\n\n$ newt test \npackage-name\n\n\n\n\n\n\nTo test all the packages in a project, specify \nall\n as the \npackage-name>\n.\n\n\n$ newt test all\n...lots of compiling and testing...\n...about 2 minutes later ...\nArchiving bootutil.a\nLinking test_bootutil\nExecuting test: /myproj/bin/unittest/libs/bootutil/test_bootutil\nPassed tests: [net/nimble/host fs/nffs libs/os hw/hal libs/mbedtls libs/util s
 ys/config libs/bootutil]\nAll tests passed\n\n\n\n\n\n\n\nBuild the Project\n\n\nTo build and run your new application, simply issue the following command:\n\n\n$ newt build my_blinky_sim \nCompiling base64.c\nCompiling cbmem.c\nCompiling datetime.c\nCompiling tpq.c\nArchiving util.a\nCompiling main.c\nArchiving blinky.a\nCompiling flash_map.c\nCompiling hal_flash.c\nArchiving hal.a\nCompiling cons_fmt.c\nCompiling cons_tty.c\n\nsnip\n\nLinking blinky.elf\nApp successfully built: /Users/sterling/dev/tmp/my_app/bin/my_blinky_sim/apps/blinky/blinky.elf\n\n\n\n\n\n\n\nYou can run the simulated version of your project and see the simulated LED\nblink.\n\n\n./bin/my_blinky_sim/apps/blinky/blinky.elf\nhal_gpio set pin  1 to 0\n\n\n\n\n\nJust press \nctrl-c\n to exit.\n\n\n\n\nComplete\n\n\nCongratulations, you have created your first project!  The blinky application\nis not terribly exciting when it is run in the simulator, as there is no LED to\nblink.  Apache Mynewt has a lot more funct
 ionality than just running simulated\napplications.  It provides all the features you'll need to cross-compile your\napplication, run it on real hardware and develop a full featured application.\n\n\nIf you're interested in learning more, a good next step is to dig in to one of\nthe \ntutorials\n and get a Mynewt project running on real hardware.\n\n\nHappy Hacking!", 
             "title": "Create Your First Project"
         }, 
         {
@@ -167,67 +167,67 @@
         }, 
         {
             "location": "/os/get_started/project_create/#newt-new", 
-            "text": "Choose a project name. For this tutorial we will call this project  myproj .\nEnter the  newt new myproj  command.       $ newt new myproj\n    Downloading project skeleton from apache/incubator-mynewt-blinky...\n    Installing skeleton in myproj...\n    Project myproj successfully created.   The  newt  tool has created a project directory structure like the one below:      \u2500\u2500\u2500 myproj\n        \u251c\u2500\u2500 DISCLAIMER\n        \u251c\u2500\u2500 LICENSE\n        \u251c\u2500\u2500 NOTICE\n        \u251c\u2500\u2500 README.md\n        \u251c\u2500\u2500 apps\n        \u2502\u00a0\u00a0 \u2514\u2500\u2500 blinky\n        \u2502\u00a0\u00a0     \u251c\u2500\u2500 pkg.yml\n        \u2502\u00a0\u00a0     \u2514\u2500\u2500 src\n        \u2502\u00a0\u00a0         \u2514\u2500\u2500 main.c\n        \u251c\u2500\u2500 project.yml\n        \u2514\u2500\u2500 targets\n            \u251c\u2500\u2500 my_blinky_sim\n            \u2502\u00a0\u00a0 \u251c\u
 2500\u2500 pkg.yml\n            \u2502\u00a0\u00a0 \u2514\u2500\u2500 target.yml\n            \u2514\u2500\u2500 unittest\n                \u251c\u2500\u2500 pkg.yml\n                \u2514\u2500\u2500 target.yml   newt  has installed the base files for a project comprising the following.   file  project.yml  contains the repository list that the project uses to fetch\nits packages. Your project is a collection of repositories.  In this case, the project just\ncomprises the core mynewt repository.  Later you will add more repositories\nto include other mynewt components.  the file  apps/blinky/pkg.yml  contains the description of your application\nand its package dependencies.  A target directory containing  my_blinky_sim , a target descriptor used to\nbuild a version of myproj.  Use  newt target show  to see available build \ntargets.  A non-build-able target called  unittest .  This is used\ninternally by  newt  and is not a formal build target.   NOTE:  the actual code and packag
 e files are not installed \n(except the template for  main.c ).  See the next step for installing the packages.", 
+            "text": "Choose a project name. For this tutorial we will call this project  myproj .\nEnter the  newt new myproj  command.   $ newt new myproj\nDownloading project skeleton from apache/incubator-mynewt-blinky...\nInstalling skeleton in myproj...\nProject myproj successfully created.   Newt populates this new project with a base skeleton of a new Apache Mynewt \nproject.  It has the following structure:  $ cd myproj\n$ tree -L 3\n.\n\u251c\u2500\u2500 DISCLAIMER\n\u251c\u2500\u2500 LICENSE\n\u251c\u2500\u2500 NOTICE\n\u251c\u2500\u2500 README.md\n\u251c\u2500\u2500 apps\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 blinky\n\u2502\u00a0\u00a0     \u251c\u2500\u2500 pkg.yml\n\u2502\u00a0\u00a0     \u2514\u2500\u2500 src\n\u251c\u2500\u2500 project.yml\n\u2514\u2500\u2500 targets\n    \u251c\u2500\u2500 my_blinky_sim\n    \u2502\u00a0\u00a0 \u251c\u2500\u2500 pkg.yml\n    \u2502\u00a0\u00a0 \u2514\u2500\u2500 target.yml\n    \u2514\u2500\u2500 unittest\n        \u251c\u2500\u2500 
 pkg.yml\n        \u2514\u2500\u2500 target.yml\n\n6 directories, 10 files   The Newt tool has installed the base files for a project comprising the following:   the file  project.yml  contains the repository list that the project uses to fetch\nits packages. Your project is a collection of repositories.  In this case, the project just\ncomprises the core mynewt repository.  Later you will add more repositories\nto include other mynewt components.  the file  apps/blinky/pkg.yml  contains the description of your application\nand its package dependencies.  A target directory containing  my_blinky_sim , a target descriptor used to\nbuild a version of myproj.  Use  newt target show  to see available build \ntargets.  A non-buildable target called  unittest .  This is used\ninternally by  newt  and is not a formal build target.   NOTE:  the actual code and package files are not installed \n(except the template for  main.c ).  See the next step for installing the packages.", 
             "title": "Newt New"
         }, 
         {
             "location": "/os/get_started/project_create/#newt-install", 
-            "text": "Change into the  myproj  directory.  Then ask newt to install all the \nproject package dependencies using  newt install .      $ newt install -v \n    apache-mynewt-core\n    Downloading repository description for apache-mynewt-core... success!\n    Downloading repository incubator-mynewt-core (branch: master; commit: mynewt_0_8_0_b2_tag) at https://github.com/apache/incubator-mynewt-core.git\n    Cloning into  /var/folders/7l/7b3w9m4n2mg3sqmgw2q1b9p80000gn/T/newt-repo969988348 ...\n    remote: Counting objects: 17935, done.\n    remote: Compressing objects: 100% (234/234), done.\n    remote: Total 17935 (delta 101), reused 0 (delta 0), pack-reused 17686\n    Receiving objects: 100% (17935/17935), 6.18 MiB | 315.00 KiB/s, done.\n    Resolving deltas: 100% (10541/10541), done.\n    Checking connectivity... done.\n    apache-mynewt-core successfully installed version 0.7.9-none\n    $   Now you will have installed packages required to build your project. Note in 
 \nthe package you now have dependent packages stored in the  repos  directory\nunder the specific repository you have included in the base project.        .\n    \u251c\u2500\u2500 apps\n    \u2502\u00a0\u00a0 \u2514\u2500\u2500 blinky\n    \u2502\u00a0\u00a0     \u2514\u2500\u2500 src\n    \u251c\u2500\u2500 repos\n    \u2502\u00a0\u00a0 \u2514\u2500\u2500 apache-mynewt-core\n    \u2502\u00a0\u00a0     \u251c\u2500\u2500 apps\n    \u2502\u00a0\u00a0     \u251c\u2500\u2500 compiler\n    \u2502\u00a0\u00a0     \u251c\u2500\u2500 fs\n    \u2502\u00a0\u00a0     \u251c\u2500\u2500 hw\n    \u2502\u00a0\u00a0     \u251c\u2500\u2500 libs\n    \u2502\u00a0\u00a0     \u251c\u2500\u2500 net\n    \u2502\u00a0\u00a0     \u251c\u2500\u2500 scripts\n    \u2502\u00a0\u00a0     \u251c\u2500\u2500 sys\n    \u2502\u00a0\u00a0     \u2514\u2500\u2500 targets\n    \u2514\u2500\u2500 targets\n        \u251c\u2500\u2500 my_blinky_sim\n        \u2514\u2500\u2500 unittest  Within each of these directories a
 re the packages required to build your\nproject for the various targets.", 
+            "text": "Once you've switched into your new project's directory, the next step is to fetch\nany dependencies this project has.  By default, all Newt projects rely on a\nsingle remote repository, apache-mynewt-core.  The  newt install  command will\nfetch this repository.  $ newt install\napache-mynewt-core  NOTE:   apache-mynewt-core  may take a while to download.  To see progress,\nuse the  -v  (verbose) option to install.   Once  newt install  has successfully finished, the contents of  apache-mynewt-core  will have been downloaded into your local directory.  You can view them by issuing the following commands in the base directory of the new project:  $ tree -L 2 repos/apache-mynewt-core/\n. snip \n\u251c\u2500\u2500 fs\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 fs\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 nffs\n\u251c\u2500\u2500 hw\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 bsp\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 hal\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 mcu\n\u251c\u2500\
 u2500 libs\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 baselibc\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 bootutil\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 cmsis-core\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 console\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 elua\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 flash_test\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 imgmgr\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 json\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 mbedtls\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 newtmgr\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 os\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 shell\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 testreport\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 testutil\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 util\n\u251c\u2500\u2500 net\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 nimble snip   As you can see, the core of the Apache Mynewt operating system has been brought \ninto your local directory!", 
             "title": "Newt Install"
         }, 
         {
-            "location": "/os/get_started/project_create/#testing-the-project", 
-            "text": "To validate, you can also run all the units test through simulation.      $ newt test all\n    ...lots of compiling and testing...\n    ...about 2 minutes later ...\n    Archiving bootutil.a\n    Linking test_bootutil\n    Executing test: /myproj/bin/unittest/libs/bootutil/test_bootutil\n    Passed tests: [net/nimble/host fs/nffs libs/os hw/hal libs/mbedtls libs/util sys/config libs/bootutil]\n    All tests passed", 
-            "title": "Testing the Project"
+            "location": "/os/get_started/project_create/#test-the-projects-packages", 
+            "text": "Use the following command to execute a package's unit tests:  $ newt test  package-name   To test all the packages in a project, specify  all  as the  package-name> .  $ newt test all\n...lots of compiling and testing...\n...about 2 minutes later ...\nArchiving bootutil.a\nLinking test_bootutil\nExecuting test: /myproj/bin/unittest/libs/bootutil/test_bootutil\nPassed tests: [net/nimble/host fs/nffs libs/os hw/hal libs/mbedtls libs/util sys/config libs/bootutil]\nAll tests passed", 
+            "title": "Test the project's packages"
         }, 
         {
-            "location": "/os/get_started/project_create/#building-the-project", 
-            "text": "To build the project you can use  newt build  using the target       $ newt build my_blinky_sim\n    App successfully built: /bin/my_blinky_sim/apps/blinky/blinky.elf   You can run the simulated version of your project and see the simulated LED\nblink      ./bin/my_blinky_sim/apps/blinky/blinky.elf\n    hal_gpio set pin  1 to 0  Just do  ctrl-c  to exit.", 
-            "title": "Building the Project"
+            "location": "/os/get_started/project_create/#build-the-project", 
+            "text": "To build and run your new application, simply issue the following command:  $ newt build my_blinky_sim \nCompiling base64.c\nCompiling cbmem.c\nCompiling datetime.c\nCompiling tpq.c\nArchiving util.a\nCompiling main.c\nArchiving blinky.a\nCompiling flash_map.c\nCompiling hal_flash.c\nArchiving hal.a\nCompiling cons_fmt.c\nCompiling cons_tty.c snip \nLinking blinky.elf\nApp successfully built: /Users/sterling/dev/tmp/my_app/bin/my_blinky_sim/apps/blinky/blinky.elf   You can run the simulated version of your project and see the simulated LED\nblink.  ./bin/my_blinky_sim/apps/blinky/blinky.elf\nhal_gpio set pin  1 to 0  Just press  ctrl-c  to exit.", 
+            "title": "Build the Project"
         }, 
         {
             "location": "/os/get_started/project_create/#complete", 
-            "text": "Congratulations, you have created your first project!  This project contains \nthe core OS, a simple application to blink an LED and all of the dependencies\nrequired.", 
+            "text": "Congratulations, you have created your first project!  The blinky application\nis not terribly exciting when it is run in the simulator, as there is no LED to\nblink.  Apache Mynewt has a lot more functionality than just running simulated\napplications.  It provides all the features you'll need to cross-compile your\napplication, run it on real hardware and develop a full featured application.  If you're interested in learning more, a good next step is to dig in to one of\nthe  tutorials  and get a Mynewt project running on real hardware.  Happy Hacking!", 
             "title": "Complete"
         }, 
         {
             "location": "/os/get_started/cross_tools/", 
-            "text": "Installing Cross Tools for ARM\n\n\nThis page shows how to install tools to use some ARM based platforms \nwith mynewt.\n\n\nInstall Cross tools for ARM MAC\n\n\nInstall Tool Chain\n\n\nInstall the PX4 Toolchain and check the version installed. ARM maintains a pre-built GNU toolchain with a GCC source branch targeted at Embedded ARM Processors, namely Cortex-R/Cortex-M processor families. After installing, ensure that the symbolic link installed by Homebrew points to the correct version of the debugger. If not, you can either change the symbolic link using the \"ln -f -s\" command or just go ahead and try with the version it points to!\n\n\n        $ brew tap PX4/homebrew-px4\n        $ brew update\n        $ brew install gcc-arm-none-eabi-49\n        $ arm-none-eabi-gcc --version  \n        arm-none-eabi-gcc (GNU Tools for ARM Embedded Processors) 4.9.3 20150529 (release) [ARM/embedded-4_9-branch revision 224288]\n        Copyright (C) 2014 Free Software Founda
 tion, Inc.\n        This is free software; see the source for copying conditions.  There is NO\n        warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.\n        $ ls -al /usr/local/bin/arm-none-eabi-gdb\n        lrwxr-xr-x  1 aditihilbert  admin  69 Sep 22 17:16 /usr/local/bin/arm-none-eabi-gdb -\n /usr/local/Cellar/gcc-arm-none-eabi-49/20150609/bin/arm-none-eabi-gdb\n\n\n\n\n\nNote: If no version is specified, brew will install the latest version available. Mynewt OS will eventually work with multiple versions available, including the latest releases. However, at present we have tested only with this version and recommend it for getting started. \n\n\nInstall OpenOCD\n\n\nInstall OpenOCD (Open On-Chip Debugger), which is an open-source software that will allow you to interface with the JTAG debug connector/adaptor for the Olimex board, debug, and test embedded target devices, including the Olimex board. For more on OpenOCD go to \nhttp://openocd.org\n.\n
 \n\n        $ brew install open-ocd\n        $ which openocd\n        /usr/local/bin/openocd\n        $ ls -l $(which openocd)\n        lrwxr-xr-x  1 \nuser\n  admin  36 Sep 17 16:22 /usr/local/bin/openocd -\n ../Cellar/open-ocd/0.9.0/bin/openocd\n\n\n\n\n\nInstall cross arm tools for Linux\n\n\nInstall Tool Chain\n\n\nFor the LED project on the Olimex hardware, you should install gcc for AM 4.9.3.  This package can be installed with apt-get as documented below. The steps are explained in depth at \nhttps://launchpad.net/~terry.guo/+archive/ubuntu/gcc-arm-embedded\n.\n\n\n        $ sudo apt-get remove binutils-arm-none-eabi gcc-arm-none-eabi \n        $ sudo add-apt-repository ppa:terry.guo/gcc-arm-embedded \n        $ sudo apt-get update \n        $ sudo apt-get install gcc-arm-none-eabi\n\n\n\n\n\nInstall OpenOCD\n\n\nAnd finally, install OpenOCD (Open On-Chip Debugger), which is an open-source software that will allow you to interface with the JTAG debug connector/adaptor for the
  Olimex board, debug your program and test embedded target devices which, including the Olimex board.\n\n\nIf you are running Ubuntu 15.x, then you are in luck and you can simply run: \n\n\n        $ sudo apt-get install openocd \n\n\n\n\n\nFor this project, you should download the openocd 0.8.0 package from \nhttps://launchpad.net/ubuntu/vivid/+source/openocd\n. The direct link to the amd64 build is \nhttp://launchpadlibrarian.net/188260097/openocd_0.8.0-4_amd64.deb\n.", 
+            "text": "Installing Cross Tools for ARM\n\n\nThis page shows how to install tools to use some ARM based platforms with\nApache Mynewt.\n\n\n\n\nInstall ARM Cross tools in Mac OS X\n\n\nInstall Tool Chain\n\n\nInstall the PX4 Toolchain and check the version installed. ARM maintains a\npre-built GNU toolchain with a GCC source branch targeted at Embedded ARM\nProcessors, namely Cortex-R/Cortex-M processor families. After installing,\nensure that the symbolic link installed by Homebrew points to the correct\nversion of the debugger.\n\n\n$ brew tap PX4/homebrew-px4\n$ brew update\n$ brew install gcc-arm-none-eabi-49\n$ arm-none-eabi-gcc --version  \narm-none-eabi-gcc (GNU Tools for ARM Embedded Processors) 4.9.3 20150529 (release) [ARM/embedded-4_9-branch revision 224288]\nCopyright (C) 2014 Free Software Foundation, Inc.\nThis is free software; see the source for copying conditions.  There is NO\nwarranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.\n
 $ ls -al /usr/local/bin/arm-none-eabi-gdb\nlrwxr-xr-x  1 aditihilbert  admin  69 Sep 22 17:16 /usr/local/bin/arm-none-eabi-gdb -\n /usr/local/Cellar/gcc-arm-none-eabi-49/20150609/bin/arm-none-eabi-gdb\n\n\n\n\n\nNote:\n If no version is specified, brew will install the latest version\navailable. Mynewt OS will eventually work with multiple versions available,\nincluding the latest releases. However, at present we have tested only with\nthis version and recommend it for getting started. \n\n\n\n\nInstall OpenOCD\n\n\nOpenOCD (Open On-Chip Debugger) is open-source software that allows your\ncomputer to interface with the JTAG debug connector on a variety of boards.  A\nJTAG connection lets you debug and test embedded target devices. For more on\nOpenOCD go to \nhttp://openocd.org\n.\n\n\nCurrently, only OpenOCD 0.8.0 is supported.\n\n\n$ brew install open-ocd\n$ which openocd\n/usr/local/bin/openocd\n$ ls -l $(which openocd)\nlrwxr-xr-x  1 \nuser\n  admin  36 Sep 17 16:22 /usr/local/b
 in/openocd -\n ../Cellar/open-ocd/0.8.0/bin/openocd\n\n\n\n\n\n\n\nInstall ARM cross arm tools for Linux\n\n\nInstall Tool Chain\n\n\nOn a Debian-based Linux distribution, gcc 4.9.3 for ARM can be installed with\napt-get as documented below. The steps are explained in depth at\n\nhttps://launchpad.net/~terry.guo/+archive/ubuntu/gcc-arm-embedded\n.\n\n\n$ sudo apt-get remove binutils-arm-none-eabi gcc-arm-none-eabi \n$ sudo add-apt-repository ppa:terry.guo/gcc-arm-embedded \n$ sudo apt-get update \n$ sudo apt-get install gcc-arm-none-eabi\n\n\n\n\n\n\n\nInstall OpenOCD\n\n\nOpenOCD (Open On-Chip Debugger) is open-source software that allows your\ncomputer to interface with the JTAG debug connector on a variety of boards.  A\nJTAG connection lets you debug and test embedded target devices. For more on\nOpenOCD go to \nhttp://openocd.org\n.\n\n\nIf you are running Ubuntu 15.x, then you are in luck and you can simply run: \n\n\n$ sudo apt-get install openocd \n\n\n\n\n\nFor this project
 , you should download the openocd 0.8.0 package from\n\nhttps://launchpad.net/ubuntu/vivid/+source/openocd\n.\nThe direct link to the amd64 build is\n\nhttp://launchpadlibrarian.net/188260097/openocd_0.8.0-4_amd64.deb\n.", 
             "title": "Install Cross Tools for ARM"
         }, 
         {
             "location": "/os/get_started/cross_tools/#installing-cross-tools-for-arm", 
-            "text": "This page shows how to install tools to use some ARM based platforms \nwith mynewt.", 
+            "text": "This page shows how to install tools to use some ARM based platforms with\nApache Mynewt.", 
             "title": "Installing Cross Tools for ARM"
         }, 
         {
-            "location": "/os/get_started/cross_tools/#install-cross-tools-for-arm-mac", 
+            "location": "/os/get_started/cross_tools/#install-arm-cross-tools-in-mac-os-x", 
             "text": "", 
-            "title": "Install Cross tools for ARM MAC"
+            "title": "Install ARM Cross tools in Mac OS X"
         }, 
         {
             "location": "/os/get_started/cross_tools/#install-tool-chain", 
-            "text": "Install the PX4 Toolchain and check the version installed. ARM maintains a pre-built GNU toolchain with a GCC source branch targeted at Embedded ARM Processors, namely Cortex-R/Cortex-M processor families. After installing, ensure that the symbolic link installed by Homebrew points to the correct version of the debugger. If not, you can either change the symbolic link using the \"ln -f -s\" command or just go ahead and try with the version it points to!          $ brew tap PX4/homebrew-px4\n        $ brew update\n        $ brew install gcc-arm-none-eabi-49\n        $ arm-none-eabi-gcc --version  \n        arm-none-eabi-gcc (GNU Tools for ARM Embedded Processors) 4.9.3 20150529 (release) [ARM/embedded-4_9-branch revision 224288]\n        Copyright (C) 2014 Free Software Foundation, Inc.\n        This is free software; see the source for copying conditions.  There is NO\n        warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.\n        $
  ls -al /usr/local/bin/arm-none-eabi-gdb\n        lrwxr-xr-x  1 aditihilbert  admin  69 Sep 22 17:16 /usr/local/bin/arm-none-eabi-gdb -  /usr/local/Cellar/gcc-arm-none-eabi-49/20150609/bin/arm-none-eabi-gdb  Note: If no version is specified, brew will install the latest version available. Mynewt OS will eventually work with multiple versions available, including the latest releases. However, at present we have tested only with this version and recommend it for getting started.", 
+            "text": "Install the PX4 Toolchain and check the version installed. ARM maintains a\npre-built GNU toolchain with a GCC source branch targeted at Embedded ARM\nProcessors, namely Cortex-R/Cortex-M processor families. After installing,\nensure that the symbolic link installed by Homebrew points to the correct\nversion of the debugger.  $ brew tap PX4/homebrew-px4\n$ brew update\n$ brew install gcc-arm-none-eabi-49\n$ arm-none-eabi-gcc --version  \narm-none-eabi-gcc (GNU Tools for ARM Embedded Processors) 4.9.3 20150529 (release) [ARM/embedded-4_9-branch revision 224288]\nCopyright (C) 2014 Free Software Foundation, Inc.\nThis is free software; see the source for copying conditions.  There is NO\nwarranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.\n$ ls -al /usr/local/bin/arm-none-eabi-gdb\nlrwxr-xr-x  1 aditihilbert  admin  69 Sep 22 17:16 /usr/local/bin/arm-none-eabi-gdb -  /usr/local/Cellar/gcc-arm-none-eabi-49/20150609/bin/arm-none-eabi-gdb  Not
 e:  If no version is specified, brew will install the latest version\navailable. Mynewt OS will eventually work with multiple versions available,\nincluding the latest releases. However, at present we have tested only with\nthis version and recommend it for getting started.", 
             "title": "Install Tool Chain"
         }, 
         {
             "location": "/os/get_started/cross_tools/#install-openocd", 
-            "text": "Install OpenOCD (Open On-Chip Debugger), which is an open-source software that will allow you to interface with the JTAG debug connector/adaptor for the Olimex board, debug, and test embedded target devices, including the Olimex board. For more on OpenOCD go to  http://openocd.org .          $ brew install open-ocd\n        $ which openocd\n        /usr/local/bin/openocd\n        $ ls -l $(which openocd)\n        lrwxr-xr-x  1  user   admin  36 Sep 17 16:22 /usr/local/bin/openocd -  ../Cellar/open-ocd/0.9.0/bin/openocd", 
+            "text": "OpenOCD (Open On-Chip Debugger) is open-source software that allows your\ncomputer to interface with the JTAG debug connector on a variety of boards.  A\nJTAG connection lets you debug and test embedded target devices. For more on\nOpenOCD go to  http://openocd.org .  Currently, only OpenOCD 0.8.0 is supported.  $ brew install open-ocd\n$ which openocd\n/usr/local/bin/openocd\n$ ls -l $(which openocd)\nlrwxr-xr-x  1  user   admin  36 Sep 17 16:22 /usr/local/bin/openocd -  ../Cellar/open-ocd/0.8.0/bin/openocd", 
             "title": "Install OpenOCD"
         }, 
         {
-            "location": "/os/get_started/cross_tools/#install-cross-arm-tools-for-linux", 
+            "location": "/os/get_started/cross_tools/#install-arm-cross-arm-tools-for-linux", 
             "text": "", 
-            "title": "Install cross arm tools for Linux"
+            "title": "Install ARM cross arm tools for Linux"
         }, 
         {
             "location": "/os/get_started/cross_tools/#install-tool-chain_1", 
-            "text": "For the LED project on the Olimex hardware, you should install gcc for AM 4.9.3.  This package can be installed with apt-get as documented below. The steps are explained in depth at  https://launchpad.net/~terry.guo/+archive/ubuntu/gcc-arm-embedded .          $ sudo apt-get remove binutils-arm-none-eabi gcc-arm-none-eabi \n        $ sudo add-apt-repository ppa:terry.guo/gcc-arm-embedded \n        $ sudo apt-get update \n        $ sudo apt-get install gcc-arm-none-eabi", 
+            "text": "On a Debian-based Linux distribution, gcc 4.9.3 for ARM can be installed with\napt-get as documented below. The steps are explained in depth at https://launchpad.net/~terry.guo/+archive/ubuntu/gcc-arm-embedded .  $ sudo apt-get remove binutils-arm-none-eabi gcc-arm-none-eabi \n$ sudo add-apt-repository ppa:terry.guo/gcc-arm-embedded \n$ sudo apt-get update \n$ sudo apt-get install gcc-arm-none-eabi", 
             "title": "Install Tool Chain"
         }, 
         {
             "location": "/os/get_started/cross_tools/#install-openocd_1", 
-            "text": "And finally, install OpenOCD (Open On-Chip Debugger), which is an open-source software that will allow you to interface with the JTAG debug connector/adaptor for the Olimex board, debug your program and test embedded target devices which, including the Olimex board.  If you are running Ubuntu 15.x, then you are in luck and you can simply run:           $ sudo apt-get install openocd   For this project, you should download the openocd 0.8.0 package from  https://launchpad.net/ubuntu/vivid/+source/openocd . The direct link to the amd64 build is  http://launchpadlibrarian.net/188260097/openocd_0.8.0-4_amd64.deb .", 
+            "text": "OpenOCD (Open On-Chip Debugger) is open-source software that allows your\ncomputer to interface with the JTAG debug connector on a variety of boards.  A\nJTAG connection lets you debug and test embedded target devices. For more on\nOpenOCD go to  http://openocd.org .  If you are running Ubuntu 15.x, then you are in luck and you can simply run:   $ sudo apt-get install openocd   For this project, you should download the openocd 0.8.0 package from https://launchpad.net/ubuntu/vivid/+source/openocd .\nThe direct link to the amd64 build is http://launchpadlibrarian.net/188260097/openocd_0.8.0-4_amd64.deb .", 
             "title": "Install OpenOCD"
         }, 
         {

http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/00265afe/os/get_started/cross_tools/index.html
----------------------------------------------------------------------
diff --git a/os/get_started/cross_tools/index.html b/os/get_started/cross_tools/index.html
index 8d4fac8..c737a27 100644
--- a/os/get_started/cross_tools/index.html
+++ b/os/get_started/cross_tools/index.html
@@ -406,53 +406,76 @@
                         </div>
                         
                             <h1 id="installing-cross-tools-for-arm">Installing Cross Tools for ARM<a class="headerlink" href="#installing-cross-tools-for-arm" title="Permanent link">&para;</a></h1>
-<p>This page shows how to install tools to use some ARM based platforms 
-with mynewt.</p>
-<h2 id="install-cross-tools-for-arm-mac">Install Cross tools for ARM MAC<a class="headerlink" href="#install-cross-tools-for-arm-mac" title="Permanent link">&para;</a></h2>
+<p>This page shows how to install tools to use some ARM based platforms with
+Apache Mynewt.</p>
+<p><br></p>
+<h2 id="install-arm-cross-tools-in-mac-os-x">Install ARM Cross tools in Mac OS X<a class="headerlink" href="#install-arm-cross-tools-in-mac-os-x" title="Permanent link">&para;</a></h2>
 <h3 id="install-tool-chain">Install Tool Chain<a class="headerlink" href="#install-tool-chain" title="Permanent link">&para;</a></h3>
-<p>Install the PX4 Toolchain and check the version installed. ARM maintains a pre-built GNU toolchain with a GCC source branch targeted at Embedded ARM Processors, namely Cortex-R/Cortex-M processor families. After installing, ensure that the symbolic link installed by Homebrew points to the correct version of the debugger. If not, you can either change the symbolic link using the "ln -f -s" command or just go ahead and try with the version it points to!</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">        $ brew tap PX4/homebrew-px4
-        $ brew update
-        $ brew install gcc-arm-none-eabi-49
-        $ arm-none-eabi-gcc --version  
-        arm-none-eabi-gcc (GNU Tools for ARM Embedded Processors) 4.9.3 20150529 (release) [ARM/embedded-4_9-branch revision 224288]
-        Copyright (C) 2014 Free Software Foundation, Inc.
-        This is free software; see the source for copying conditions.  There is NO
-        warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
-        $ ls -al /usr/local/bin/arm-none-eabi-gdb
-        lrwxr-xr-x  1 aditihilbert  admin  69 Sep 22 17:16 /usr/local/bin/arm-none-eabi-gdb -&gt; /usr/local/Cellar/gcc-arm-none-eabi-49/20150609/bin/arm-none-eabi-gdb
+<p>Install the PX4 Toolchain and check the version installed. ARM maintains a
+pre-built GNU toolchain with a GCC source branch targeted at Embedded ARM
+Processors, namely Cortex-R/Cortex-M processor families. After installing,
+ensure that the symbolic link installed by Homebrew points to the correct
+version of the debugger.</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ brew tap PX4/homebrew-px4
+$ brew update
+$ brew install gcc-arm-none-eabi-49
+$ arm-none-eabi-gcc --version  
+arm-none-eabi-gcc (GNU Tools for ARM Embedded Processors) 4.9.3 20150529 (release) [ARM/embedded-4_9-branch revision 224288]
+Copyright (C) 2014 Free Software Foundation, Inc.
+This is free software; see the source for copying conditions.  There is NO
+warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
+$ ls -al /usr/local/bin/arm-none-eabi-gdb
+lrwxr-xr-x  1 aditihilbert  admin  69 Sep 22 17:16 /usr/local/bin/arm-none-eabi-gdb -&gt; /usr/local/Cellar/gcc-arm-none-eabi-49/20150609/bin/arm-none-eabi-gdb
 </pre></div>
 
 
-<p>Note: If no version is specified, brew will install the latest version available. Mynewt OS will eventually work with multiple versions available, including the latest releases. However, at present we have tested only with this version and recommend it for getting started. </p>
+<p><strong>Note:</strong> If no version is specified, brew will install the latest version
+available. Mynewt OS will eventually work with multiple versions available,
+including the latest releases. However, at present we have tested only with
+this version and recommend it for getting started. </p>
+<p><br></p>
 <h3 id="install-openocd">Install OpenOCD<a class="headerlink" href="#install-openocd" title="Permanent link">&para;</a></h3>
-<p>Install OpenOCD (Open On-Chip Debugger), which is an open-source software that will allow you to interface with the JTAG debug connector/adaptor for the Olimex board, debug, and test embedded target devices, including the Olimex board. For more on OpenOCD go to <a href="http://openocd.org">http://openocd.org</a>.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">        $ brew install open-ocd
-        $ which openocd
-        /usr/local/bin/openocd
-        $ ls -l $(which openocd)
-        lrwxr-xr-x  1 &lt;user&gt;  admin  36 Sep 17 16:22 /usr/local/bin/openocd -&gt; ../Cellar/open-ocd/0.9.0/bin/openocd
+<p>OpenOCD (Open On-Chip Debugger) is open-source software that allows your
+computer to interface with the JTAG debug connector on a variety of boards.  A
+JTAG connection lets you debug and test embedded target devices. For more on
+OpenOCD go to <a href="http://openocd.org">http://openocd.org</a>.</p>
+<p>Currently, only OpenOCD 0.8.0 is supported.</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ brew install open-ocd
+$ which openocd
+/usr/local/bin/openocd
+$ ls -l $(which openocd)
+lrwxr-xr-x  1 &lt;user&gt;  admin  36 Sep 17 16:22 /usr/local/bin/openocd -&gt; ../Cellar/open-ocd/0.8.0/bin/openocd
 </pre></div>
 
 
-<h2 id="install-cross-arm-tools-for-linux">Install cross arm tools for Linux<a class="headerlink" href="#install-cross-arm-tools-for-linux" title="Permanent link">&para;</a></h2>
+<p><br></p>
+<h2 id="install-arm-cross-arm-tools-for-linux">Install ARM cross arm tools for Linux<a class="headerlink" href="#install-arm-cross-arm-tools-for-linux" title="Permanent link">&para;</a></h2>
 <h3 id="install-tool-chain_1">Install Tool Chain<a class="headerlink" href="#install-tool-chain_1" title="Permanent link">&para;</a></h3>
-<p>For the LED project on the Olimex hardware, you should install gcc for AM 4.9.3.  This package can be installed with apt-get as documented below. The steps are explained in depth at <a href="https://launchpad.net/~terry.guo/+archive/ubuntu/gcc-arm-embedded">https://launchpad.net/~terry.guo/+archive/ubuntu/gcc-arm-embedded</a>.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">        $ sudo apt-get remove binutils-arm-none-eabi gcc-arm-none-eabi 
-        $ sudo add-apt-repository ppa:terry.guo/gcc-arm-embedded 
-        $ sudo apt-get update 
-        $ sudo apt-get install gcc-arm-none-eabi
+<p>On a Debian-based Linux distribution, gcc 4.9.3 for ARM can be installed with
+apt-get as documented below. The steps are explained in depth at
+<a href="https://launchpad.net/~terry.guo/+archive/ubuntu/gcc-arm-embedded">https://launchpad.net/~terry.guo/+archive/ubuntu/gcc-arm-embedded</a>.</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ sudo apt-get remove binutils-arm-none-eabi gcc-arm-none-eabi 
+$ sudo add-apt-repository ppa:terry.guo/gcc-arm-embedded 
+$ sudo apt-get update 
+$ sudo apt-get install gcc-arm-none-eabi
 </pre></div>
 
 
+<p><br></p>
 <h3 id="install-openocd_1">Install OpenOCD<a class="headerlink" href="#install-openocd_1" title="Permanent link">&para;</a></h3>
-<p>And finally, install OpenOCD (Open On-Chip Debugger), which is an open-source software that will allow you to interface with the JTAG debug connector/adaptor for the Olimex board, debug your program and test embedded target devices which, including the Olimex board.</p>
+<p>OpenOCD (Open On-Chip Debugger) is open-source software that allows your
+computer to interface with the JTAG debug connector on a variety of boards.  A
+JTAG connection lets you debug and test embedded target devices. For more on
+OpenOCD go to <a href="http://openocd.org">http://openocd.org</a>.</p>
 <p>If you are running Ubuntu 15.x, then you are in luck and you can simply run: </p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">        $ sudo apt-get install openocd 
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ sudo apt-get install openocd 
 </pre></div>
 
 
-<p>For this project, you should download the openocd 0.8.0 package from <a href="https://launchpad.net/ubuntu/vivid/+source/openocd">https://launchpad.net/ubuntu/vivid/+source/openocd</a>. The direct link to the amd64 build is <a href="http://launchpadlibrarian.net/188260097/openocd_0.8.0-4_amd64.deb">http://launchpadlibrarian.net/188260097/openocd_0.8.0-4_amd64.deb</a>. </p>
+<p>For this project, you should download the openocd 0.8.0 package from
+<a href="https://launchpad.net/ubuntu/vivid/+source/openocd">https://launchpad.net/ubuntu/vivid/+source/openocd</a>.
+The direct link to the amd64 build is
+<a href="http://launchpadlibrarian.net/188260097/openocd_0.8.0-4_amd64.deb">http://launchpadlibrarian.net/188260097/openocd_0.8.0-4_amd64.deb</a>. </p>
                         
                         <div class="row">
                             

http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/00265afe/os/get_started/introduction/index.html
----------------------------------------------------------------------
diff --git a/os/get_started/introduction/index.html b/os/get_started/introduction/index.html
index 49e9521..c27bf81 100644
--- a/os/get_started/introduction/index.html
+++ b/os/get_started/introduction/index.html
@@ -428,130 +428,8 @@ package management and build system tool, called <em>newt</em>. </p>
 <p>You can install and build <em>newt</em> for <a href="../../../newt/install/newt_linux/">Linux</a> or <a href="../../../newt/install/newt_mac/">Mac</a>. </p>
 <p><br></p>
 <h3 id="build-your-first-mynewt-app-with-newt">Build your first Mynewt App with Newt<a class="headerlink" href="#build-your-first-mynewt-app-with-newt" title="Permanent link">&para;</a></h3>
-<p>Before you start your first Mynewt application, you must first create a new Mynewt
-project with the <em>newt</em> tool: </p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt new my_project
-Downloading project skeleton from apache/incubator-mynewt-blinky...
-Installing skeleton in my_app...
-Project my_app successfully created.
-</pre></div>
-
-
-<p><br></p>
-<p>Newt populates this new project with a base skeleton of a new Apache Mynewt 
-project.  It has the following structure:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ cd my_project
-$ tree -L 3
-.
-├── DISCLAIMER
-├── LICENSE
-├── NOTICE
-├── README.md
-├── apps
-│   └── blinky
-│       ├── pkg.yml
-│       └── src
-├── project.yml
-└── targets
-    ├── my_blinky_sim
-    │   ├── pkg.yml
-    │   └── target.yml
-    └── unittest
-        ├── pkg.yml
-        └── target.yml
-
-6 directories, 10 files
-$ 
-</pre></div>
-
-
-<p>Once you've switched into your new project's directory, the next step is to fetch
-any dependencies this project has.  By default, all Newt projects rely on a single
-remote repository, apache-mynewt-core.  Newt install will fetch this locally:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt install
-apache-mynewt-core
-$
-</pre></div>
-
-
-<p><strong>NOTE:</strong> <code>apache-mynewt-core</code> may take a while to download, to see progress, use the <code>-v</code> (verbose) option to install. </p>
-<p>Once <code>newt install</code> has successfully finished, the contents of <code>apache-mynewt-core</code>
-will have been downloaded into your local directory.  You can view them by issuing the 
-following commands in the base directory of the new project:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ cd repos/apache-mynewt-core
-$ tree -L2
-.
-&lt;snip&gt;
-├── fs
-│   ├── fs
-│   └── nffs
-├── hw
-│   ├── bsp
-│   ├── hal
-│   └── mcu
-├── libs
-│   ├── baselibc
-│   ├── bootutil
-│   ├── cmsis-core
-│   ├── console
-│   ├── elua
-│   ├── flash_test
-│   ├── imgmgr
-│   ├── json
-│   ├── mbedtls
-│   ├── newtmgr
-│   ├── os
-│   ├── shell
-│   ├── testreport
-│   ├── testutil
-│   └── util
-├── net
-│   └── nimble
-&lt;snip&gt;
-</pre></div>
-
-
-<p><br></p>
-<p>As you can see, the core of the Apache Mynewt operating system has been brought 
-into your local directory!  </p>
-<p>New projects created with Newt, come with by default an example application 
-(<code>apps/blinky</code>) and an example target (<code>my_blinky_sim</code>) which allows you to 
-build that application for the simulated platform.  </p>
-<p>With your new project, all you need to build and run your new application is to 
-issue the following commands: </p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt build my_blinky_sim 
-Compiling base64.c
-Compiling cbmem.c
-Compiling datetime.c
-Compiling tpq.c
-Archiving util.a
-Compiling main.c
-Archiving blinky.a
-Compiling flash_map.c
-Compiling hal_flash.c
-Archiving hal.a
-Compiling cons_fmt.c
-Compiling cons_tty.c
-&lt;snip&gt;
-Linking blinky.elf
-App successfully built: /Users/sterling/dev/tmp/my_app/bin/my_blinky_sim/apps/blinky/blinky.elf
-$ newt run my_blinky_sim
-(runs target my_blinky_sim on the simulator)
-</pre></div>
-
-
-<p><br></p>
-<p>At this point you have your first Mynewt application!</p>
-<p>Apache Mynewt has a lot more functionality than just running simulated applications.  It provides all 
-the features you'll need to cross-compile your application, run it on real hardware and develop a 
-full featured application.</p>
-<p>If you're interested in learning more, a good next step is to choose a project to 
-<a href="../get_started/">get started</a> with, and begin to familiarize 
-yourself with operating within the newt environment.  These projects will get your toolchain installed, 
-and get you blinking an LED with the Apache Mynewt OS.</p>
-<p>After you've tried a few getting started projects, there are plenty of tutorials that will help 
-expose you to much of the functionality provided by the Apache Mynewt Core Operating System.   There is 
-also full reference documentation for all of the Core Apache Mynewt APIs.</p>
+<p>With the introductions out of the way, now is a good time to <a href="../project_create/">get
+started</a> with your first Mynewt application.</p>
 <p>Happy Hacking!</p>
                         
                         <div class="row">

http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/00265afe/os/get_started/native_tools/index.html
----------------------------------------------------------------------
diff --git a/os/get_started/native_tools/index.html b/os/get_started/native_tools/index.html
index 99b0876..02b3673 100644
--- a/os/get_started/native_tools/index.html
+++ b/os/get_started/native_tools/index.html
@@ -410,41 +410,52 @@
 allows you to run Mynewt OS as a native application.  It also allows
 you to run the test suites for all packages not requiring HW support. </p>
 <p>This page provides guidance for MAC and Linux. See the relevant sections below.</p>
+<p><br></p>
 <h2 id="set-up-toolchain-for-mac">Set up toolchain for Mac<a class="headerlink" href="#set-up-toolchain-for-mac" title="Permanent link">&para;</a></h2>
 <h3 id="install-brew">Install Brew<a class="headerlink" href="#install-brew" title="Permanent link">&para;</a></h3>
 <p>If you have not already installed Homebrew from the 
 <a href="../../../newt/install/newt_mac/"><code>newt</code> tutorials pages</a>, install it. </p>
+<p><br></p>
 <h3 id="install-gcclibc">Install gcc/libc<a class="headerlink" href="#install-gcclibc" title="Permanent link">&para;</a></h3>
-<p>Use brew to install gcc.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">        $ brew install gcc
-        ...
-        ...
-        ==&gt; Summary
-        🍺  /usr/local/Cellar/gcc/5.2.0: 1353 files, 248M
+<p>OS X ships with a C compiler called Clang.  To build applications for the Mynewt simulator, you will need a different compiler: gcc.</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ brew install gcc
+...
+...
+==&gt; Summary
+🍺  /usr/local/Cellar/gcc/5.2.0: 1353 files, 248M
 </pre></div>
 
 
+<p><br></p>
 <h3 id="install-gdb">Install gdb<a class="headerlink" href="#install-gdb" title="Permanent link">&para;</a></h3>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">        $ brew install gdb
-        ...
-        ...
-        ==&gt; Summary
-        🍺  /usr/local/Cellar/gdb/7.10.1: XXX files,YYM
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ brew install gdb
+...
+...
+==&gt; Summary
+🍺  /usr/local/Cellar/gdb/7.10.1: XXX files,YYM
 </pre></div>
 
 
-<p><em>NOTE: When running a program with gdb, you may need to sign your gdb
+<p><br></p>
+<p><strong>NOTE:</strong> When running a program with gdb, you may need to sign your gdb
 executable.  <a href="https://gcc.gnu.org/onlinedocs/gnat_ugn/Codesigning-the-Debugger.html">This page</a>
 shows a recipe for gdb signing. Alternately you can skip this step and
-continue without the ability to debug your mynewt application on your PC.</em></p>
+continue without the ability to debug your mynewt application on your PC.*</p>
+<p><br></p>
 <h2 id="set-up-toolchain-for-linux">Set up toolchain for Linux<a class="headerlink" href="#set-up-toolchain-for-linux" title="Permanent link">&para;</a></h2>
+<p>The below procedure can be used to set up a Debian-based Linux system (e.g.,
+Ubuntu).  If you are running a different Linux distribution, you will need to
+substitute invocations of <em>apt-get</em> in the below steps with the package manager
+that your distro uses.</p>
+<p><br></p>
 <h3 id="install-gcclibc-that-will-produce-32-bit-executables">Install gcc/libc that will produce 32-bit executables:<a class="headerlink" href="#install-gcclibc-that-will-produce-32-bit-executables" title="Permanent link">&para;</a></h3>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">        $ sudo apt-get install gcc-multilib libc6-i386
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ sudo apt-get install gcc-multilib libc6-i386
 </pre></div>
 
 
+<p><br></p>
 <h3 id="install-gdb_1">Install gdb<a class="headerlink" href="#install-gdb_1" title="Permanent link">&para;</a></h3>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$sudo apt-get install gdb
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ sudo apt-get install gdb
 
 Reading package lists... Done
 Building dependency tree       
@@ -456,10 +467,10 @@ The following NEW packages will be installed:
 ...
 Processing triggers for man-db (2.6.7.1-1ubuntu1) ...
 Setting up gdb (7.7.1-0ubuntu5~14.04.2) ...
-$ 
 </pre></div>
 
 
+<p><br></p>
 <p>At this point you have installed all the necessary software to build and test code on a simluator for Linux. Proceed to the <a href="#build-test-code-on-simulator">Build test code on simulator</a> section.</p>
                         
                         <div class="row">


Mime
View raw message