You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mynewt.apache.org by ad...@apache.org on 2017/04/26 00:31:34 UTC
[1/7] incubator-mynewt-site git commit: Updates to installation on
Linux and Mac, removal of references to develop branch on website
Repository: incubator-mynewt-site
Updated Branches:
refs/heads/asf-site e7404297d -> 45c390ea1
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/latest/os/tutorials/pin-wheel-mods/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/pin-wheel-mods/index.html b/latest/os/tutorials/pin-wheel-mods/index.html
deleted file mode 100644
index 8b5a431..0000000
--- a/latest/os/tutorials/pin-wheel-mods/index.html
+++ /dev/null
@@ -1,681 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
- <head>
- <meta charset="utf-8">
- <meta http-equiv="X-UA-Compatible" content="IE=edge">
- <meta name="viewport" content="width=device-width, initial-scale=1.0">
-
-
- <!-- This is broken by doc revisioning.
- <link rel="canonical" href="http://mynewt.apache.org/os/tutorials/pin-wheel-mods/"> -->
- <link rel="shortcut icon" href="../../../img/favicon.ico">
-
- <title>Pinwheel Blinky - Apache Mynewt</title>
-
- <link href="../../../css/bootstrap-3.0.3.min.css" rel="stylesheet">
- <link rel="stylesheet" href="../../../css/highlight.css">
- <link href="../../../css/base.css" rel="stylesheet">
- <link href="../../../css/custom.css" rel="stylesheet">
- <link href="../../../css/v2.css" rel="stylesheet">
- <link href="https://fonts.googleapis.com/css?family=Lato" rel="stylesheet">
- <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/font-awesome/4.5.0/css/font-awesome.min.css">
- <link href="../../../extra.css" rel="stylesheet">
-
- <!-- HTML5 shim and Respond.js IE8 support of HTML5 elements and media queries -->
- <!--[if lt IE 9]>
- <script src="https://oss.maxcdn.com/libs/html5shiv/3.7.0/html5shiv.js"></script>
- <script src="https://oss.maxcdn.com/libs/respond.js/1.3.0/respond.min.js"></script>
- <![endif]-->
-
-
- <script>
- (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
- (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
- m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
- })(window,document,'script','//www.google-analytics.com/analytics.js','ga');
-
- ga('create', 'UA-72162311-1', 'auto');
- ga('send', 'pageview');
- </script>
-
- </head>
-
-
- <body class="Pinwheel Blinky">
-
-
- <div class="container">
- <div class="row v2-main-banner">
- <a class="logo-cell" href="/">
- <img class="logo" src="/img/logo.png">
- </a>
- <div class="tagline-cell">
- <h4 class="tagline">An OS to build, deploy and securely manage billions of devices</h4>
- </div>
- <div class="news-cell">
- <div class="well">
- <h4>Latest News:</h4> <a href="/download">Apache Mynewt 1.0.0</a> released (March 22, 2017)
- </div>
- </div>
- </div>
-</div>
-
-
-
-
-
-
-
-
-<nav id="navbar" class="navbar navbar-inverse affix-top" data-spy="affix" data-offset-top="150" role="navigation">
- <div class="container">
- <!-- Collapsed navigation -->
- <div class="navbar-header">
- <!-- Expander button -->
- <button type="button" class="navbar-toggle" data-toggle="collapse" data-target=".navbar-collapse">
- <span class="sr-only">Toggle navigation</span>
- <span class="icon-bar"></span>
- <span class="icon-bar"></span>
- <span class="icon-bar"></span>
- </button>
-
- </div>
-
- <!-- Expanded navigation -->
- <div class="navbar-collapse collapse">
- <!-- Main navigation -->
- <ul class="nav navbar-nav navbar-right">
- <li
- class=""
->
- <a href="/"><i class="fa fa-home" style="font-size: larger;"></i></a>
- </li>
- <li
- class="important"
->
- <a href="/quick-start/">Quick Start</a>
- </li>
- <li
- class=""
->
- <a href="/about/">About</a>
- </li>
- <li
- class=""
->
- <a href="/talks/">Talks</a>
- </li>
- <li
- class="active"
->
- <a href="/latest/os/introduction">Documentation</a>
- </li>
- <li
- class=""
->
- <a href="/download/">Download</a>
- </li>
- <li
- class=""
->
- <a href="/community/">Community</a>
- </li>
- <li
- class=""
->
- <a href="/events/">Events</a>
- </li>
- </ul>
-
- <!-- Search, Navigation and Repo links -->
- <ul class="nav navbar-nav navbar-right">
-
- </ul>
- </div>
- </div>
-</nav>
-
-
-
- <div class="container">
-
- <div class="row">
- <div class="col-md-3 v2-sidebar sidebar-container"><div id="docSidebar" class="hidden-print" role="complementary">
- <div class="top">
- <div role="search">
- <form id="rtd-search-form" class="wy-form" action="../../../search.html" method="get">
- <div class="form-group">
- <input type="text" name="q" class="form-control" placeholder="Search documentation" />
- </div>
- </form>
- </div>
- </div>
- <ul class="toc-nav">
- <li class="doc-version">
-<select class="form-control" onchange="if (this.value) window.location.href=this.value">
-
- <option
- value="/develop/os/introduction"
- selected="selected"
- >
- Version: develop (latest)
- </option>
-
- <option
- value="/v0_9_0/os/introduction"
-
- >
- Version: 0.9.0
- </option>
-
-</select>
-</li>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- <li ><a href="../../introduction/">Mynewt Documentation</a>
-
-
- <ul>
-
-
-
-
-
-
-
- <li ><a href="../../get_started/get_started/">Basic Setup</a>
-
-
- </li>
-
-
-
-
-
- <li >
- <a href="../../get_started/vocabulary/">Concepts</a>
- </li>
-
-
-
-
-
-
-
- <li ><a href="../tutorials/">Tutorials</a>
-
-
- <ul>
-
-
-
-
-
-
-
- <li ><a href="../blinky/">Project Blinky</a>
-
-
- <ul>
-
-
-
-
-
- <li >
- <a href="../arduino_zero/">Blinky on Arduino Zero</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../blinky_primo/">Blinky on Arduino Primo</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../olimex/">Blinky on Olimex</a>
- </li>
-
-
-
-
-
-
-
- <li ><a href="../STM32F303/">Blinky on STM32F303</a>
-
-
- <ul>
-
-
-
-
-
- <li class="active">
- <a href="./">Pinwheel Blinky</a>
- </li>
-
-
-
- </ul>
-
- </li>
-
-
-
-
-
- <li >
- <a href="../nRF52/">Blinky on nRF52</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../rbnano2/">Blinky on RedBear Nano 2</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../blinky_console/">Add Console and Shell to Blinky</a>
- </li>
-
-
-
- </ul>
-
- </li>
-
-
-
-
-
-
-
- <li ><a href="../repo/add_repos/">Work with repositories</a>
-
-
- </li>
-
-
-
-
-
-
-
- <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
-
-
- </li>
-
-
-
-
-
- <li >
- <a href="../ibeacon/">BLE iBeacon</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../eddystone/">BLE Eddystone</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../add_shell/">Enable the OS Shell and Console</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../tasks_lesson/">Tasks and Priority Management</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../unit_test/">Write a Test Suite for a Package</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../event_queue/">Events and Event Queues</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../bletiny_project/">BLE app to check stats via console</a>
- </li>
-
-
-
-
-
-
-
- <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
- </li>
-
-
-
-
-
- <li >
- <a href="../blehci_project/">BLE HCI interface</a>
- </li>
-
-
-
-
-
-
-
- <li><a href="
- ../air_quality_sensor/
-">Air-quality Sensor project</a>
-
-
- </li>
-
-
-
-
-
- <li >
- <a href="../nrf52_adc/">Add an Analog Sensor</a>
- </li>
-
-
-
- </ul>
-
- </li>
-
-
-
-
-
-
-
- <li ><a href="../../os_user_guide/">OS User Guide</a>
-
-
- </li>
-
-
-
-
-
-
-
- <li><a href="
- ../../../network/ble/ble_intro/
-">BLE User Guide</a>
-
-
- </li>
-
-
-
-
-
-
-
- <li ><a href="../../../newt/newt_intro/">Newt Tool Guide</a>
-
-
- </li>
-
-
-
-
-
-
-
- <li ><a href="../../../newtmgr/overview/">Newt Manager Guide</a>
-
-
- </li>
-
-
-
- </ul>
-
- </li>
-
-
-
-
-
-
-
- <li><a href="
- ../../../faq/go_env/
-">Appendix</a>
-
-
- </li>
-
-
-
- </ul>
-</div></div>
-
- <div class="col-md-9" role="main">
- <div class="doc-header">
- <div role="navigation" aria-label="breadcrumbs navigation">
- <ul class="wy-breadcrumbs pull-right">
- <li><a href="/latest/os/introduction">Docs</a></li>
-
-
-
- <li>» <a href="../blinky/">Project Blinky</a></li>
-
-
-
- <li>» <a href="../STM32F303/">Blinky on STM32F303</a></li>
-
-
-
- <li>» Pinwheel Blinky</li>
-
-
-
- </ul>
-</div>
- </div>
-
- <h2 id="pin-wheel-modifications-to-blinky-on-stm32f3-discovery">Pin Wheel Modifications to "Blinky" on STM32F3 Discovery</h2>
-<p><br></p>
-<h3 id="objective">Objective</h3>
-<p>Learn how to modify an existing app -- the <a href="../STM32F303/">blinky</a> app -- to light all the LEDs on the STM32F3 Discovery board. </p>
-<p><br></p>
-<h3 id="what-you-need">What you need</h3>
-<ul>
-<li>Discovery kit with STM32F303VC MCU</li>
-<li>Laptop running Mac OSX. </li>
-<li>It is assumed you have already installed and run the <a href="../STM32F303/">blinky</a> app succesfully.</li>
-</ul>
-<p><br></p>
-<p>Since you've already successfully created your blinky app project, you'll need to modify only one file, main.c, in order to get this app working.</p>
-<p><br></p>
-<p>The main.c file resides in the apps/blinky/src directory in your project folder so you can edit it with your favorite editor. You'll make the following changes:</p>
-<p><br></p>
-<p>Replace the line:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span style="color: #A90D91">int</span> <span style="color: #000000">g_led_pin</span>;
-</pre></div>
-
-
-<p>With the line:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span style="color: #A90D91">int</span> <span style="color: #000000">g_led_pins</span>[<span style="color: #1C01CE">8</span>] <span style="color: #000000">=</span> {<span style="color: #000000">LED_BLINK_PIN_1</span>, <span style="color: #000000">LED_BLINK_PIN_2</span>, <span style="color: #000000">LED_BLINK_PIN_3</span>, <span style="color: #000000">LED_BLINK_PIN_4</span>, <span style="color: #000000">LED_BLINK_PIN_5</span>, <span style="color: #000000">LED_BLINK_PIN_6</span>, <span style="color: #000000">LED_BLINK_PIN_7</span>, <span style="color: #000000">LED_BLINK_PIN_8</span>};
-</pre></div>
-
-
-<p>So that you now have an array of all 8 LED Pins on the board.</p>
-<p>Delete the line:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span style="color: #000000">g_led_pin</span> <span style="color: #000000">=</span> <span style="color: #000000">LED_BLINK_PIN</span>;
-</pre></div>
-
-
-<p>And in its place, add the following lines to initialize all the LED_PINS correctly:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span style="color: #A90D91">int</span> <span style="color: #000000">x</span>;
-<span style="color: #A90D91">for</span>(<span style="color: #000000">x</span> <span style="color: #000000">=</span> <span style="color: #1C01CE">0</span>; <span style="color: #000000">x</span> <span style="color: #000000"><</span> <span style="color: #1C01CE">8</span>; <span style="color: #000000">x++</span>){
- <span style="color: #000000">hal_gpio_init_out</span>(<span style="color: #000000">g_led_pins</span>[<span style="color: #000000">x</span>], <span style="color: #1C01CE">1</span>);
-}
-<span style="color: #A90D91">int</span> <span style="color: #000000">p</span> <span style="color: #000000">=</span> <span style="color: #1C01CE">0</span>;
-</pre></div>
-
-
-<p>We'll use that 'p' later. Next you'll want to change the line:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span style="color: #000000">os_time_delay</span>(<span style="color: #1C01CE">1000</span>);
-</pre></div>
-
-
-<p>to a shorter time in order to make it a little more interesting. A full 1 second delay doesn't look great, so try 100 for starters and then you can adjust it to your liking.</p>
-<p>Finally, change the line:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span style="color: #000000">hal_gpio_toggle</span>(<span style="color: #000000">g_led_pin</span>);
-</pre></div>
-
-
-<p>to look like this:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span style="color: #000000">hal_gpio_toggle</span>(<span style="color: #000000">g_led_pins</span>[<span style="color: #000000">p++</span>]);
-<span style="color: #000000">p</span> <span style="color: #000000">=</span> (<span style="color: #000000">p</span> <span style="color: #000000">></span> <span style="color: #1C01CE">7</span>) <span style="color: #000000">?</span> <span style="color: #1C01CE">0</span> <span style="color: #000000">:</span> <span style="color: #000000">p</span>;
-</pre></div>
-
-
-<p><br></p>
-<h3 id="build-the-target-and-executables-and-download-the-images">Build the target and executables and download the images</h3>
-<p>Run the same commands you used on the blinky app to build and load this one:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt create-image stmf3_blinky 1.2.3
-App image successfully generated: ~/dev/myproj/bin/stmf3_blinky/apps/blinky/blinky.img
-Build manifest:~/dev/myproj/bin/stmf3_blinky/apps/blinky/manifest.json
-$ newt -v load stmf3_boot
-$ newt -v load stmf3_blinky
-</pre></div>
-
-
-<p><br></p>
-<h3 id="watch-the-leds-go-round-and-round">Watch the LEDs go round and round</h3>
-<p>The colored LEDs should now all light up in succession, and once they're all lit, they should then go off in the same order. This should repeat continuously.</p>
-<p>If you see anything missing or want to send us feedback, please do so by signing up for appropriate mailing lists on our <a href="../../../community/">Community Page</a>.</p>
-<p>Keep on hacking and blinking!</p>
-
- <div class="row">
-
-
-
-
-<ul class="nav nav-pills" style="margin-bottom: 10px">
- <li>
-
- <a href=../STM32F303/>
- <span class="fa fa-arrow-left"></span>
- Previous: Blinky on STM32F303
- </a>
-
- </li>
- <li class="pull-right">
-
- <a href=../nRF52/>
- Next: Blinky on nRF52
- <span class="fa fa-arrow-right"></span>
- </a>
-
- </li>
-</ul>
- </div>
- <footer class="row">
- <div class="col-xs-12">
-
- <p class="copyright">Apache Mynewt (incubating) is available under Apache License, version 2.0.</p>
-
- </div>
- <div class="col-xs-12">
- <div class="logos">
- <img src="/img/asf_logo_wide_small.png" alt="Apache" title="Apache">
- <small class="footnote">
- MyNewt is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.
- </small>
- <img src="/img/egg-logo2.png" alt="Apache Incubator" title="Apache Incubator">
- </div>
- </div>
-</footer>
- </div>
- </div>
-
-
- </div>
-
- <script src="../../../js/jquery-1.10.2.min.js"></script>
- <script src="../../../js/bootstrap-3.0.3.min.js"></script>
- <script src="../../../js/highlight.pack.js"></script>
- <script src="../../../js/base.js"></script>
- <script src="../../../js/custom.js"></script>
-
- </body>
-</html>
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/latest/os/tutorials/project-nrf52-slinky/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/project-nrf52-slinky/index.html b/latest/os/tutorials/project-nrf52-slinky/index.html
index c59af5f..a98e685 100644
--- a/latest/os/tutorials/project-nrf52-slinky/index.html
+++ b/latest/os/tutorials/project-nrf52-slinky/index.html
@@ -507,6 +507,7 @@
<ul>
<li>Meet the prerequisites listed in <a href="../project-slinky/">Project Slinky</a>. </li>
<li>Have a Nordic nRF52-DK board. </li>
+<li>Install the <a href="https://www.segger.com/jlink-software.html">Segger JLINK Software and documentation pack</a>.</li>
</ul>
<h3 id="create-a-new-project">Create a New Project</h3>
<p>Create a new project if you do not have an existing one. You can skip this step and proceed to <a href="#create_targets">create the targets</a> if you already have a project created or completed the <a href="../project-slinky/">Sim Slinky</a> tutorial. </p>
@@ -652,7 +653,7 @@ $
<p><br></p>
<h3 id="use-newtmgr-to-query-the-board">Use Newtmgr to Query the Board</h3>
-<p>Run some newtmgr commands to query and receive responses back from the board (See the <a href="../newtmgr/overview">Newt Manager Guide</a> for more information on the newtmgr commands). </p>
+<p>Run some newtmgr commands to query and receive responses back from the board (See the <a href="../../../newtmgr/overview">Newt Manager Guide</a> for more information on the newtmgr commands). </p>
<p>Run the <code>newtmgr echo hello -c nrf52serial</code> command. This is the simplest command that requests the board to echo back the text. </p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newtmgr echo hello -c nrf52serial
hello
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/latest/os/tutorials/project-stm32-slinky/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/project-stm32-slinky/index.html b/latest/os/tutorials/project-stm32-slinky/index.html
index be5ce2f..05ebabc 100644
--- a/latest/os/tutorials/project-stm32-slinky/index.html
+++ b/latest/os/tutorials/project-stm32-slinky/index.html
@@ -511,6 +511,7 @@
<li>Have a ARM-USB-TINY-H connector with JTAG interface for debugging ARM microcontrollers (comes with the ribbon cable to hook up to the board)</li>
<li>Have a USB A-B type cable to connect the debugger to your computer. </li>
<li>Have a USB to TTL Serial Cable with female wiring harness.</li>
+<li>Install the <a href="../../../os/get_started/cross_tools/">OpenOCD debugger</a>.</li>
</ul>
<h3 id="create-a-new-project">Create a New Project</h3>
<p>Create a new project if you do not have an existing one. You can skip this step and proceed to <a href="#create_targets">create the targets</a> if you already have a project created or completed the <a href="../project-slinky/">Sim Slinky</a> tutorial.</p>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/latest/os/tutorials/rbnano2/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/rbnano2/index.html b/latest/os/tutorials/rbnano2/index.html
index a4ae875..e6e0fa9 100644
--- a/latest/os/tutorials/rbnano2/index.html
+++ b/latest/os/tutorials/rbnano2/index.html
@@ -265,17 +265,6 @@
-
-
- <li ><a href="../STM32F303/">Blinky on STM32F303</a>
-
-
- </li>
-
-
-
-
-
<li >
<a href="../nRF52/">Blinky on nRF52</a>
</li>
@@ -543,8 +532,8 @@
<ul>
<li>Meet the prerequisites listed in <a href="../blinky/">Project Blinky</a>.</li>
<li>Have a RedBear Nano 2 board. </li>
+<li>Install a patched version of OpenOCD 0.10.0 described in <a href="../os/get_started/cross_tools/">Install OpenOCD</a>.</li>
</ul>
-<p><strong>Note:</strong> You must install a patched version of OpenOCD .10.0 (See <a href="../../../os/tutorials/blinky_primo">Debugger Option 2 in the Arduino Primo Blinky Tutorial</a>).</p>
<h3 id="create-a-project">Create a Project</h3>
<p>Create a new project if you do not have an existing one. You can skip this step and proceed to <a href="#create_targets">create the targets</a> if you already have a project created. </p>
<p>Run the following commands to create a new project:</p>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/latest/os/tutorials/tutorials/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/tutorials/index.html b/latest/os/tutorials/tutorials/index.html
index 76fbd1e..861a603 100644
--- a/latest/os/tutorials/tutorials/index.html
+++ b/latest/os/tutorials/tutorials/index.html
@@ -478,7 +478,6 @@
<li>You have installed Docker container of Newt tool and toolchains or you have installed them natively on your machine</li>
<li>You have created a new project space (directory structure) and populated it with the core code repository (apache-mynewt-core) or know how to as explained in <a href="../../get_started/project_create">Creating Your First Project</a>.</li>
<li>You have at least one of the supported development boards:<ul>
-<li><a href="../STM32F303/">STM32F3 discovery kit from ST Micro</a></li>
<li><a href="../arduino_zero/">Arduino Zero hardware</a></li>
<li><a href="../olimex/">Olimex/STM32F407ZGT6 Cortex-M4 hardware</a></li>
<li><a href="../nRF52/">nRF52 Development Kit from Nordic Semiconductor</a></li>
@@ -495,15 +494,8 @@
<ul>
<li><a href="../arduino_zero/">Blinky on Arduino Zero hardware</a></li>
<li><a href="../olimex/">Blinky on Olimex/STM32F407ZGT6 Cortex-M4 hardware</a></li>
-<li><a href="../STM32F303/">Blinky on STM32F3 discovery kit from ST Micro</a></li>
<li><a href="../nRF52/">Blinky on nRF52 Development Kit from Nordic Semiconductor</a> <strong>Note:</strong> This supports BLE.</li>
-</ul>
-<p><br></p>
-</li>
-<li>
-<p>Tweaking available apps to customize behavior e.g. making a more exciting LED blink pattern</p>
-<ul>
-<li><a href="../pin-wheel-mods/">Pinwheel Blinky on STM32F3 discovery board</a></li>
+<li><a href="../rbnano2/">Blinky on Redbear Nano2</a></li>
</ul>
<p><br></p>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/latest/sitemap.xml
----------------------------------------------------------------------
diff --git a/latest/sitemap.xml b/latest/sitemap.xml
index c476bb9..b635405 100644
--- a/latest/sitemap.xml
+++ b/latest/sitemap.xml
@@ -4,7 +4,7 @@
<url>
<loc>http://mynewt.apache.org/</loc>
- <lastmod>2017-04-24</lastmod>
+ <lastmod>2017-04-25</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -13,7 +13,7 @@
<url>
<loc>http://mynewt.apache.org/pages/ble/</loc>
- <lastmod>2017-04-24</lastmod>
+ <lastmod>2017-04-25</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -22,7 +22,7 @@
<url>
<loc>http://mynewt.apache.org/quick-start/</loc>
- <lastmod>2017-04-24</lastmod>
+ <lastmod>2017-04-25</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -30,7 +30,7 @@
<url>
<loc>http://mynewt.apache.org/about/</loc>
- <lastmod>2017-04-24</lastmod>
+ <lastmod>2017-04-25</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -38,7 +38,7 @@
<url>
<loc>http://mynewt.apache.org/talks/</loc>
- <lastmod>2017-04-24</lastmod>
+ <lastmod>2017-04-25</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -46,7 +46,7 @@
<url>
<loc>http://mynewt.apache.org/download/</loc>
- <lastmod>2017-04-24</lastmod>
+ <lastmod>2017-04-25</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -54,7 +54,7 @@
<url>
<loc>http://mynewt.apache.org/community/</loc>
- <lastmod>2017-04-24</lastmod>
+ <lastmod>2017-04-25</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -62,7 +62,7 @@
<url>
<loc>http://mynewt.apache.org/events/</loc>
- <lastmod>2017-04-24</lastmod>
+ <lastmod>2017-04-25</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -71,7 +71,7 @@
<url>
<loc>http://mynewt.apache.org/os/introduction/</loc>
- <lastmod>2017-04-24</lastmod>
+ <lastmod>2017-04-25</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -83,7 +83,7 @@
<url>
<loc>http://mynewt.apache.org/os/get_started/vocabulary/</loc>
- <lastmod>2017-04-24</lastmod>
+ <lastmod>2017-04-25</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -123,19 +123,19 @@
<url>
<loc>http://mynewt.apache.org/faq/go_env/</loc>
- <lastmod>2017-04-24</lastmod>
+ <lastmod>2017-04-25</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/how_to_edit_docs/</loc>
- <lastmod>2017-04-24</lastmod>
+ <lastmod>2017-04-25</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/answers/</loc>
- <lastmod>2017-04-24</lastmod>
+ <lastmod>2017-04-25</lastmod>
<changefreq>daily</changefreq>
</url>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/mkdocs/search_index.json
----------------------------------------------------------------------
diff --git a/mkdocs/search_index.json b/mkdocs/search_index.json
index ad542cc..db528e4 100644
--- a/mkdocs/search_index.json
+++ b/mkdocs/search_index.json
@@ -62,7 +62,7 @@
},
{
"location": "/download/",
- "text": "Latest Apache Mynewt OS Release\n\n\n\n\nRelease Version: Apache Mynewt 1.0.0-incubating\n\n\nRelease Date: March 22, 2017\n\n\nRelease Notes\n\n\n\n\nFresh install\n\n\nIf you are brand new to Mynewt, go to \nQuick Start\n. The Newt tool will automatically download the latest release.\n\n\nIf you have already installed the Newt tool but not started any project yet, go to \nCreate Your First Project\n. The Newt tool will automatically download the latest release.\n\n\nUpgrade\n\n\nIf you have already installed the Newt tool and started a project that installed a previous version of Apache Mynewt, upgrade using Newt tool:\n\n\n$ newt upgrade\n\n\n\n\n\nCode in development\n\n\nWhile the use of one of the official releases listed above is generally recommended, you may be interested in seeing work in progress.\n\n\nThe most recent code resides in the \ndevelop\n branch of the Mynewt git repository. You may view or fork the repositories for Mynewt OS and Newt Tool
from the Apache mirror on github.com.\n\n\n\n\nApache Mynewt OS mirror on github.com\n\n\nApache Newt Tool mirror on github.com\n\n\n\n\nAlternatively, you can clone the desired branch using git:\n\n\n$ git clone git://github.com/apache/incubator-mynewt-core.git -b develop\n$ git clone git://github.com/apache/incubator-mynewt-newt.git -b develop\n\n\n\n\n\n\n\nA relatively stable version of code in progress can be found in the \nmaster\n branch of the Mynewt git repository.\nYou may access the code for Mynewt OS and Newt Tool from the 'master` branch of the Apache mirror on github.com or clone it using git:\n\n\n$ git clone git://github.com/apache/incubator-mynewt-core.git\n$ git clone git://github.com/apache/incubator-mynewt-newt.git\n\n\n\n\n\n\n\nFor general information on using Git at Apache, go to https://git-wip-us.apache.org.\n\n\n\n\nRelease Archives\n\n\n\n\nApache Mynewt 0.8.0-incubating, \nRelease Notes\n\n\nApache Mynewt 0.8.0-b2-incubating, \nRelease Notes\n\n\nApache
Mynewt 0.9.0-incubating, \nRelease Notes\n\n\nApache Mynewt 1.0.0-b1-incubating, \nRelease Notes\n\n\nApache Mynewt 1.0.0-b2-incubating, \nRelease Notes",
+ "text": "Latest Apache Mynewt OS Release\n\n\n\n\nRelease Version: Apache Mynewt 1.0.0-incubating\n\n\nRelease Date: March 22, 2017\n\n\nRelease Notes\n\n\n\n\nFresh install\n\n\nIf you are brand new to Mynewt, go to \nQuick Start\n. The Newt tool will automatically download the latest release.\n\n\nIf you have already installed the Newt tool but not started any project yet, go to \nCreate Your First Project\n. The Newt tool will automatically download the latest release.\n\n\nUpgrade\n\n\nIf you have already installed the Newt tool and started a project that installed a previous version of Apache Mynewt, upgrade using Newt tool:\n\n\n$ newt upgrade\n\n\n\n\n\nCode in development\n\n\nWhile the use of one of the official releases listed above is generally recommended, you may be interested in seeing work in progress.\n\n\nThe most recent code that is fairly stable over the full OS resides in the \nmaster\n branch of the Mynewt git repository. You may view or fork the re
positories for Mynewt OS and Newt Tool from the Apache mirror on github.com.\n\n\n\n\nApache Mynewt OS mirror on github.com\n\n\nApache Newt Tool mirror on github.com\n\n\n\n\nThe most recent code to support a major feature (e.g. Bluetooth 5) can be found in a long-lived feature branch dedicated to that feature (bluetooth5, in the example for Bluetooth 5) and not the master. If you are interested in seeing the latest code for that feature, you can clone the desired branch using git:\n\n\n$ git clone git://github.com/apache/incubator-mynewt-core.git -b \nfeature-branch-name\n\n$ git clone git://github.com/apache/incubator-mynewt-newt.git -b \nfeature-branch-name\n\n\n\n\n\n\n\n\nFor general information on using Git at Apache, go to https://git-wip-us.apache.org.\n\n\n\n\nRelease Archives\n\n\n\n\nApache Mynewt 0.8.0-incubating, \nRelease Notes\n\n\nApache Mynewt 0.8.0-b2-incubating, \nRelease Notes\n\n\nApache Mynewt 0.9.0-incubating, \nRelease Notes\n\n\nApache Mynewt 1.0.0-b1-incu
bating, \nRelease Notes\n\n\nApache Mynewt 1.0.0-b2-incubating, \nRelease Notes",
"title": "Download"
},
{
@@ -82,7 +82,7 @@
},
{
"location": "/download/#code-in-development",
- "text": "While the use of one of the official releases listed above is generally recommended, you may be interested in seeing work in progress. The most recent code resides in the develop branch of the Mynewt git repository. You may view or fork the repositories for Mynewt OS and Newt Tool from the Apache mirror on github.com. Apache Mynewt OS mirror on github.com Apache Newt Tool mirror on github.com Alternatively, you can clone the desired branch using git: $ git clone git://github.com/apache/incubator-mynewt-core.git -b develop\n$ git clone git://github.com/apache/incubator-mynewt-newt.git -b develop A relatively stable version of code in progress can be found in the master branch of the Mynewt git repository.\nYou may access the code for Mynewt OS and Newt Tool from the 'master` branch of the Apache mirror on github.com or clone it using git: $ git clone git://github.com/apache/incubator-mynewt-core.git\n$ git clone git://github.com/apache/incubator-myn
ewt-newt.git For general information on using Git at Apache, go to https://git-wip-us.apache.org.",
+ "text": "While the use of one of the official releases listed above is generally recommended, you may be interested in seeing work in progress. The most recent code that is fairly stable over the full OS resides in the master branch of the Mynewt git repository. You may view or fork the repositories for Mynewt OS and Newt Tool from the Apache mirror on github.com. Apache Mynewt OS mirror on github.com Apache Newt Tool mirror on github.com The most recent code to support a major feature (e.g. Bluetooth 5) can be found in a long-lived feature branch dedicated to that feature (bluetooth5, in the example for Bluetooth 5) and not the master. If you are interested in seeing the latest code for that feature, you can clone the desired branch using git: $ git clone git://github.com/apache/incubator-mynewt-core.git -b feature-branch-name \n$ git clone git://github.com/apache/incubator-mynewt-newt.git -b feature-branch-name For general information on using Git at Apa
che, go to https://git-wip-us.apache.org.",
"title": "Code in development"
},
{
@@ -142,12 +142,12 @@
},
{
"location": "/os/get_started/get_started/",
- "text": "Quick Start\n\n\nIf you are curious about Mynewt and want to get a quick feel for the project, you've come to the right place. We have two options for you:\n\n\n\n\nOption 1\n is the quick and easy way to get up and running with Mynewt. The Newt tool and build toolchains are all available in a single \nAll-in-one Docker Container\n that you can install on your laptop or computer.\n\n\n\n\nOption 2\n allows you to install the Newt tool, instances of the Mynewt OS (for simulated targets), and toolchains for developing embedded software (e.g. GNU toolchain) natively on your laptop or computer. You may want this if you are already familiar with such environments or are concerned about performance on your machine. Follow the instructions to \ninstall native tools\n and \ninstall cross tools for ARM\n if you prefer this option.\n\n\n\n\nYou can then proceed with the instructions on how to \n* \nCreate Your First Project\n - on simulated hardware.\n\n\nUpon successful
start, several tutorials await your eager attention!\n\n\n\n\nSend us an email on the dev@ mailing list if you have comments or suggestions!\n If you haven't joined the mailing list, you will find the links \nhere\n.",
+ "text": "Quick Start\n\n\nIf you are curious about Mynewt and want to get a quick feel for the project, you've come to the right place. We have two options for you:\n\n\n\n\nOption 1\n allows you to install the Newt tool, instances of the Mynewt OS (for simulated targets), and toolchains for developing embedded software (e.g. GNU toolchain) natively on your laptop or computer. You may want this if you are already familiar with such environments or are concerned about performance on your machine. Follow the instructions to \ninstall native tools\n and \ninstall cross tools for ARM\n if you prefer this option.\n\n\nOption 2\n is a bundled option to get up and running with Mynewt for a quick look at the OS. The Newt tool and build toolchains are all available in a single \nAll-in-one Docker Container\n that you can install on your laptop or computer.\n\n\n\n\nYou can then proceed with the instructions on how to \n* \nCreate Your First Project\n - on simulated hardware.\n\n\
nUpon successful start, several tutorials await your eager attention!\n\n\n\n\nSend us an email on the dev@ mailing list if you have comments or suggestions!\n If you haven't joined the mailing list, you will find the links \nhere\n.",
"title": "toc"
},
{
"location": "/os/get_started/get_started/#quick-start",
- "text": "If you are curious about Mynewt and want to get a quick feel for the project, you've come to the right place. We have two options for you: Option 1 is the quick and easy way to get up and running with Mynewt. The Newt tool and build toolchains are all available in a single All-in-one Docker Container that you can install on your laptop or computer. Option 2 allows you to install the Newt tool, instances of the Mynewt OS (for simulated targets), and toolchains for developing embedded software (e.g. GNU toolchain) natively on your laptop or computer. You may want this if you are already familiar with such environments or are concerned about performance on your machine. Follow the instructions to install native tools and install cross tools for ARM if you prefer this option. You can then proceed with the instructions on how to \n* Create Your First Project - on simulated hardware. Upon successful start, several tutorials await your eager attention!
Send us an email on the dev@ mailing list if you have comments or suggestions! If you haven't joined the mailing list, you will find the links here .",
+ "text": "If you are curious about Mynewt and want to get a quick feel for the project, you've come to the right place. We have two options for you: Option 1 allows you to install the Newt tool, instances of the Mynewt OS (for simulated targets), and toolchains for developing embedded software (e.g. GNU toolchain) natively on your laptop or computer. You may want this if you are already familiar with such environments or are concerned about performance on your machine. Follow the instructions to install native tools and install cross tools for ARM if you prefer this option. Option 2 is a bundled option to get up and running with Mynewt for a quick look at the OS. The Newt tool and build toolchains are all available in a single All-in-one Docker Container that you can install on your laptop or computer. You can then proceed with the instructions on how to \n* Create Your First Project - on simulated hardware. Upon successful start, several tutorials await y
our eager attention! Send us an email on the dev@ mailing list if you have comments or suggestions! If you haven't joined the mailing list, you will find the links here .",
"title": "Quick Start"
},
{
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/os/get_started/get_started/index.html
----------------------------------------------------------------------
diff --git a/os/get_started/get_started/index.html b/os/get_started/get_started/index.html
index b3027ef..f6a47f4 100644
--- a/os/get_started/get_started/index.html
+++ b/os/get_started/get_started/index.html
@@ -354,9 +354,8 @@
<h2 id="quick-start">Quick Start</h2>
<p>If you are curious about Mynewt and want to get a quick feel for the project, you've come to the right place. We have two options for you:</p>
<p><br></p>
-<p><strong>Option 1</strong> is the quick and easy way to get up and running with Mynewt. The Newt tool and build toolchains are all available in a single <a href="../docker/">All-in-one Docker Container</a> that you can install on your laptop or computer.</p>
-<p><br></p>
-<p><strong>Option 2</strong> allows you to install the Newt tool, instances of the Mynewt OS (for simulated targets), and toolchains for developing embedded software (e.g. GNU toolchain) natively on your laptop or computer. You may want this if you are already familiar with such environments or are concerned about performance on your machine. Follow the instructions to <a href="../native_tools/">install native tools</a> and <a href="../cross_tools/">install cross tools for ARM</a> if you prefer this option.</p>
+<p><strong>Option 1</strong> allows you to install the Newt tool, instances of the Mynewt OS (for simulated targets), and toolchains for developing embedded software (e.g. GNU toolchain) natively on your laptop or computer. You may want this if you are already familiar with such environments or are concerned about performance on your machine. Follow the instructions to <a href="../native_tools/">install native tools</a> and <a href="../cross_tools/">install cross tools for ARM</a> if you prefer this option.</p>
+<p><strong>Option 2</strong> is a bundled option to get up and running with Mynewt for a quick look at the OS. The Newt tool and build toolchains are all available in a single <a href="../docker/">All-in-one Docker Container</a> that you can install on your laptop or computer.</p>
<p><br></p>
<p>You can then proceed with the instructions on how to
* <a href="../project_create/">Create Your First Project</a> - on simulated hardware.</p>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/sitemap.xml
----------------------------------------------------------------------
diff --git a/sitemap.xml b/sitemap.xml
index 9157a60..650f503 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -4,7 +4,7 @@
<url>
<loc>http://mynewt.apache.org/</loc>
- <lastmod>2017-04-24</lastmod>
+ <lastmod>2017-04-25</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -13,13 +13,13 @@
<url>
<loc>http://mynewt.apache.org/pages/ble/</loc>
- <lastmod>2017-04-24</lastmod>
+ <lastmod>2017-04-25</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/pages/securitybullets/</loc>
- <lastmod>2017-04-24</lastmod>
+ <lastmod>2017-04-25</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -28,7 +28,7 @@
<url>
<loc>http://mynewt.apache.org/quick-start/</loc>
- <lastmod>2017-04-24</lastmod>
+ <lastmod>2017-04-25</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -36,7 +36,7 @@
<url>
<loc>http://mynewt.apache.org/about/</loc>
- <lastmod>2017-04-24</lastmod>
+ <lastmod>2017-04-25</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -44,7 +44,7 @@
<url>
<loc>http://mynewt.apache.org/talks/</loc>
- <lastmod>2017-04-24</lastmod>
+ <lastmod>2017-04-25</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -52,7 +52,7 @@
<url>
<loc>http://mynewt.apache.org/download/</loc>
- <lastmod>2017-04-24</lastmod>
+ <lastmod>2017-04-25</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -60,7 +60,7 @@
<url>
<loc>http://mynewt.apache.org/community/</loc>
- <lastmod>2017-04-24</lastmod>
+ <lastmod>2017-04-25</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -68,7 +68,7 @@
<url>
<loc>http://mynewt.apache.org/events/</loc>
- <lastmod>2017-04-24</lastmod>
+ <lastmod>2017-04-25</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -77,7 +77,7 @@
<url>
<loc>http://mynewt.apache.org/os/introduction/</loc>
- <lastmod>2017-04-24</lastmod>
+ <lastmod>2017-04-25</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -89,7 +89,7 @@
<url>
<loc>http://mynewt.apache.org/os/get_started/vocabulary/</loc>
- <lastmod>2017-04-24</lastmod>
+ <lastmod>2017-04-25</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -129,13 +129,13 @@
<url>
<loc>http://mynewt.apache.org/faq/how_to_edit_docs/</loc>
- <lastmod>2017-04-24</lastmod>
+ <lastmod>2017-04-25</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/answers/</loc>
- <lastmod>2017-04-24</lastmod>
+ <lastmod>2017-04-25</lastmod>
<changefreq>daily</changefreq>
</url>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/v0_9_0/sitemap.xml
----------------------------------------------------------------------
diff --git a/v0_9_0/sitemap.xml b/v0_9_0/sitemap.xml
index 9157a60..650f503 100644
--- a/v0_9_0/sitemap.xml
+++ b/v0_9_0/sitemap.xml
@@ -4,7 +4,7 @@
<url>
<loc>http://mynewt.apache.org/</loc>
- <lastmod>2017-04-24</lastmod>
+ <lastmod>2017-04-25</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -13,13 +13,13 @@
<url>
<loc>http://mynewt.apache.org/pages/ble/</loc>
- <lastmod>2017-04-24</lastmod>
+ <lastmod>2017-04-25</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/pages/securitybullets/</loc>
- <lastmod>2017-04-24</lastmod>
+ <lastmod>2017-04-25</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -28,7 +28,7 @@
<url>
<loc>http://mynewt.apache.org/quick-start/</loc>
- <lastmod>2017-04-24</lastmod>
+ <lastmod>2017-04-25</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -36,7 +36,7 @@
<url>
<loc>http://mynewt.apache.org/about/</loc>
- <lastmod>2017-04-24</lastmod>
+ <lastmod>2017-04-25</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -44,7 +44,7 @@
<url>
<loc>http://mynewt.apache.org/talks/</loc>
- <lastmod>2017-04-24</lastmod>
+ <lastmod>2017-04-25</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -52,7 +52,7 @@
<url>
<loc>http://mynewt.apache.org/download/</loc>
- <lastmod>2017-04-24</lastmod>
+ <lastmod>2017-04-25</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -60,7 +60,7 @@
<url>
<loc>http://mynewt.apache.org/community/</loc>
- <lastmod>2017-04-24</lastmod>
+ <lastmod>2017-04-25</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -68,7 +68,7 @@
<url>
<loc>http://mynewt.apache.org/events/</loc>
- <lastmod>2017-04-24</lastmod>
+ <lastmod>2017-04-25</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -77,7 +77,7 @@
<url>
<loc>http://mynewt.apache.org/os/introduction/</loc>
- <lastmod>2017-04-24</lastmod>
+ <lastmod>2017-04-25</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -89,7 +89,7 @@
<url>
<loc>http://mynewt.apache.org/os/get_started/vocabulary/</loc>
- <lastmod>2017-04-24</lastmod>
+ <lastmod>2017-04-25</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -129,13 +129,13 @@
<url>
<loc>http://mynewt.apache.org/faq/how_to_edit_docs/</loc>
- <lastmod>2017-04-24</lastmod>
+ <lastmod>2017-04-25</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/answers/</loc>
- <lastmod>2017-04-24</lastmod>
+ <lastmod>2017-04-25</lastmod>
<changefreq>daily</changefreq>
</url>
[2/7] incubator-mynewt-site git commit: Updates to installation on
Linux and Mac, removal of references to develop branch on website
Posted by ad...@apache.org.
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/latest/newt/install/newt_linux/index.html
----------------------------------------------------------------------
diff --git a/latest/newt/install/newt_linux/index.html b/latest/newt/install/newt_linux/index.html
index d44c0c5..ed4c63e 100644
--- a/latest/newt/install/newt_linux/index.html
+++ b/latest/newt/install/newt_linux/index.html
@@ -391,181 +391,218 @@
</div>
</div>
- <h2 id="install-newt-tool-on-linux">Install newt tool on Linux</h2>
+ <h2 id="installing-newt-on-linux">Installing Newt on Linux</h2>
+<p>You can install the latest stable release (1.0.0) of newt from a Debian binary package (amd64) or from a Debian source package. This page shows you how to:</p>
+<ol>
+<li>Set up your computer to retrieve Debian packages from the runtimeco debian package repository.</li>
+<li>Install the latest stable release version of newt from a Debian binary package. </li>
+<li>Install the latest stable release version of newt from a Debian source package.</li>
+</ol>
+<p>If you are running on an amd64 platform, we recommend that you install from the binary package.</p>
+<p><strong>Note:</strong> See <a href="../../../faq/go_env">Setting Up an Go Environment to Contribute to Newt and Newtmgr Tools</a> if you want to: </p>
+<ul>
+<li>Use the newt tool with the latest updates from the master branch. The master branch may be unstable and we recommend that you use the latest stable release version.</li>
+<li>Contribute to the newt tool. </li>
+</ul>
<p><br></p>
-<h3 id="getting-your-linux-box-ready">Getting your Linux box Ready</h3>
-<p>If you want to build the <em>newt</em> tool from its source code, follow the following steps:</p>
-<h4 id="1-install-git-libcurl">1. Install git, libcurl</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ sudo apt-get install git
- $ sudo apt-get install libcurl4-gnutls-dev
+<h3 id="setting-up-your-computer-to-get-packages-from-runtimeco">Setting Up Your Computer to Get Packages from runtimeco</h3>
+<p>The newt Debian packages are stored in a private repository on <strong>https://github/runtimeco/debian-mynewt</strong>. </p>
+<p><strong>Note:</strong> You will only need to perform these steps only once on your computer.
+The following steps must be performed on your computer:</p>
+<ol>
+<li>Add the <code>apt-transport-https</code> package to use HTTPS to retrieve packages. </li>
+<li>Download the public key for the runtimeco debian repository and import the key into the apt keychain.</li>
+<li>Add the repository for the binary and source packages to the apt source list.</li>
+</ol>
+<p><br>
+Add the apt-transport-https package:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$sudo apt-get update
+$sudo apt-get install apt-transport-https
</pre></div>
-<p><strong>NOTE:</strong> On 64-bit host, you may also need to install gcc-multilib, if you encounter compilation errors related to 'sys/cdefs.h'</p>
<p><br></p>
-<h4 id="2-install-go-the-programming-language">2. Install Go, the programming language</h4>
-<ul>
-<li>
-<p>Go language environment dictates a directory structure. Known in Go parlance as a workspace, it must contain three sibling directories with the directory names src, pkg and bin, as explained below. </p>
-<ul>
-<li>
-<p>src contains Go source files organized into packages (one package per directory),</p>
-</li>
-<li>
-<p>pkg contains package objects, and</p>
-</li>
-<li>
-<p>bin contains executable commands.</p>
-</li>
-</ul>
-<p>The GOPATH environment variable specifies the location of your workspace. To setup this workspace environment, create a 'dev' directory and then a 'go' directory under it. Set the GOPATH environment variable to this directory where you will soon clone the <em>newt</em> tool repository.</p>
-</li>
-</ul>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ cd $HOME
- $ mkdir -p dev/go
- $ cd dev/go
- $ export GOPATH=`pwd`
+<p>Download the public key for the runtimeco apt repo (<strong>Note:</strong> There is <code>-</code> after the add):</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">wget -qO - https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/mynewt.gpg.key | sudo apt-key add -
</pre></div>
-<p>(Note that you need to add export statements to ~/.bash_profile to export variables permanently. Don't forget to source the file for the change to go into effect.)</p>
<p><br></p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ vi ~/.bash_profile
- $ source ~/.bash_profile
+<p>Add the repository for the binary and source packages to the apt source list:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$sudo -s
+[sudo] password for <user>:
+root$ cat > /etc/apt/sources.list.d/mynewt.list <<EOF
+deb https://raw.githubusercontent.com/runtimeco/debian-package/master latest main
+deb-src https://raw.githubusercontent.com/runtimeco/debian-package/master latest main
+EOF
+</pre></div>
+
+
+<p><br>
+Check the content of the file:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">root$more /etc/apt/sources.list.d//mynewt.list
+deb https://raw.githubusercontent.com/runtimeco/debian-package/master latest main
+deb-src https://raw.githubusercontent.com/runtimeco/debian-package/master latest main
+</pre></div>
+
+
+<p><br> </p>
+<p>Exit the root shell:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">root$exit
</pre></div>
<p><br></p>
-<ul>
-<li>
-<p>Next, install Go. When installed, Go offers you as a developer a language environment (to compile Go code), construct Go packages (to assemble Go packages) and import Go code (from github). In the next step, you will use the Go commands to import <em>newt</em> repo into your local Go environment.</p>
-<p><strong>Note</strong>: The Newt tool requires Go version 1.7 or later. Currently, the latest Go version that Ubuntu installs is 1.6. You can run <code>apt-get install golang-1.7-go</code> to install version 1.7. You can also download version 1.7 from <a href="https://golang.org/dl/">https://golang.org/dl/</a>. </p>
-</li>
-</ul>
+<h3 id="installing-the-latest-release-of-newt-from-a-binary-package">Installing the Latest Release of Newt from a Binary Package</h3>
+<p>For Linux amd64 platform, you can install the latest stable version (1.0.0) of newt from the newt Debian binary package:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$sudo apt-get update
+$sudo apt-get install newt
+Reading package lists... Done
+Building dependency tree
+Reading state information... Done
+
+ ...
+
+Preparing to unpack .../newt_1.0.0-1_amd64.deb ...
+Unpacking newt (1.0.0-1) ...
+Setting up newt (1.0.0-1) ...
+</pre></div>
+
+
+<p><br>
+See <a href="#check">Checking the Installed Version of Newt</a> to verify that you are using the installed version of newt.</p>
+<p><br></p>
+<h3 id="installing-the-latest-stable-release-of-newt-from-a-source-package">Installing the Latest Stable Release of Newt from a Source Package</h3>
+<p>If you are running Linux on a different architecture, you can install the Debian source package for the latest stable release (1.0.0) of newt. The installation of the source package builds the newt binary and creates a Debian binary package that you then install.</p>
+<p><strong>Note</strong>: Newt version 1.0.0 has been tested on Linux amd64 platform. Version 1.0.0 does not build on the 32 bit platform but have been fixed for the next release.</p>
+<p><br></p>
+<h4 id="installing-go-17">Installing Go 1.7</h4>
+<p>You need Go version 1.7 or higher to build Newt version 1.0.0. Currently, the latest Go version that Ubuntu installs is 1.6. Run <code>go version</code> to check if you have Go 1.7 installed. </p>
+<p><br></p>
+<p>Install Go version 1.7:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$sudo apt-get install golang-1.7-go
Reading package lists... Done
...
Unpacking golang-1.7-go (1.7.1-2ubuntu1) ...
Setting up golang-1.7-go (1.7.1-2ubuntu1) ...
$
-$sudo ln -s /usr/lib/go-1.7/bin/go /usr/bin/go
+$sudo ln -sf ../lib/go-1.7/bin/go /usr/bin/go
$go version
go version go1.7.1 linux/amd64
</pre></div>
-<p><br> </p>
-<h4 id="3-create-local-repository">3. Create local repository</h4>
-<ul>
-<li>Use Go commands to copy the directory (currently the ASF incubator directory). Be patient as it may take a minute or two. Check the directories installed.</li>
-</ul>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ go get mynewt.apache.org/newt/...
-</pre></div>
-
-
+<p>You can also download version 1.7 from <a href="https://golang.org/dl/">https://golang.org/dl/</a>. </p>
<p><br></p>
-<ul>
-<li>Check that newt.go is in place.</li>
-</ul>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ ls $GOPATH/src/mynewt.apache.org/newt
- DISCLAIMER NOTICE newt newtvm viper
- LICENSE README.md newtmgr util yaml
+<h4 id="installing-from-the-source-package">Installing from the Source Package</h4>
+<p>Create a directory and change into the directory, download the source package, and build a binary package from the source package:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">mkdir newt_source
+$cd newt_source
+$sudo apt-get --build source newt
+[sudo] password for <user>:
+Reading package lists... Done
+Need to get 1,866 kB of source archives.
+Get:1 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newt 1.0.0-1 (dsc) [795 B]
+Get:2 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newt 1.0.0-1 (tar) [1,864 kB]
+Get:3 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newt 1.0.0-1 (diff) [2,000 B]
+Fetched 1,866 kB in 1s (1,222 kB/s)
+dpkg-source: warning: extracting unsigned source package (newt_1.0.0-1.dsc)
+dpkg-source: info: extracting newt in newt-1.0.0
+dpkg-source: info: unpacking newt_1.0.0.orig.tar.gz
+dpkg-source: info: unpacking newt_1.0.0-1.debian.tar.xz
+
+ ...
+
+dpkg-deb: building package 'newt' in '../newt_1.0.0-1_amd64.deb'.
+ dpkg-genchanges --build=any,all >../newt_1.0.0-1_amd64.changes
+dpkg-genchanges: info: binary-only upload (no source code included)
+ dpkg-source --after-build newt-1.0.0
+dpkg-buildpackage: info: binary-only upload (no source included)
+W: Can't drop privileges for downloading as file 'newt_1.0.0-1.dsc' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)
</pre></div>
-<p><br></p>
-<h4 id="4-build-the-newt-tool">4. Build the Newt tool</h4>
-<ul>
-<li>Use Go to run the newt.go program to build the <em>newt</em> tool. The command <code>go install</code> compiles and writes the resulting executable to an output file named <code>newt</code>, which is then installed, along with its dependencies, in $GOPATH/bin. If you get errors it is likely because of path resolution issues. Try <code>go build</code> followed by <code>go install</code> in that case.</li>
-</ul>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ cd $GOPATH/src/mynewt.apache.org/newt/newt
- $ go install
- $ ls "$GOPATH"/bin/
- newt newtmgr newtvm
+<p><strong>Note:</strong> You can ignore the "Permission denied: warning message at the end of the command.</p>
+<p><br>
+Install the newt binary package that is created from the source package:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$sudo dpkg -i newt_1.0.0-1_amd64.deb
+Selecting previously unselected package newt.
+(Reading database ... 252969 files and directories currently installed.)
+Preparing to unpack newt_1.0.0-1_amd64.deb ...
+Unpacking newt (1.0.0-1) ...
+Setting up newt (1.0.0-1) ...
</pre></div>
<p><br></p>
-<ul>
-<li>At this point, you can try using <em>newt</em>. For example, check for the version number by typing 'newt version'. See all the possible commands available to a user of newt by typing 'newt -h'.</li>
-</ul>
-<p>(Note: If you are going to be modifying the <em>newt</em> often and going to be compile the program every time you call it, you will want to store the command in a variable in your .bash_profile. So type in <code>export newt="go run $GOPATH/mynewt.apache.org/newt/newt/newt.go"</code> in your .bash_profile and execute it by calling <code>$newt</code> at the prompt instead of <code>newt</code>. Essentially, <code>$newt</code> calls <code>go run</code> which runs the compiled binary directly without producing an executable. Don't forget to reload the updated bash profile by typing <code>source ~/.bash_profile</code> at the prompt! )</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ newt version
- Newt version: 1.0
- $ newt -h
- Newt allows you to create your own embedded application based on the Mynewt
- operating system. Newt provides both build and package management in a single
- tool, which allows you to compose an embedded application, and set of
- projects, and then build the necessary artifacts from those projects. For more
- information on the Mynewt operating system, please visit
- https://mynewt.apache.org/.
-
- Please use the newt help command, and specify the name of the command you want
- help for, for help on how to use a specific command
-
- Usage:
- newt [flags]
- newt [command]
-
- Examples:
- newt
- newt help [<command-name>]
- For help on <command-name>. If not specified, print this message.
-
- Available Commands:
- build Build one or more targets
- clean Delete build artifacts for one or more targets
- create-image Add image header to target binary
- debug Open debugger session to target
- info Show project info
- install Install project dependencies
- load Load built target to board
- mfg Manufacturing flash image commands
- new Create a new project
- pkg Create and manage packages in the current workspace
- run build/create-image/download/debug <target>
- size Size of target components
- sync Synchronize project dependencies
- target Commands to create, delete, configure, and query targets
- test Executes unit tests for one or more packages
- upgrade Upgrade project dependencies
- vals Display valid values for the specified element type(s)
- version Display the Newt version number
-
- Flags:
- -h, --help Help for newt commands
- -j, --jobs int Number of concurrent build jobs (default 8)
- -l, --loglevel string Log level (default "WARN")
- -o, --outfile string Filename to tee output to
- -q, --quiet Be quiet; only display error output
- -s, --silent Be silent; don't output anything
- -v, --verbose Enable verbose output when executing commands
-
- Use "newt [command] --help" for more information about a comma
+<h3 id="checking-the-installed-version-of-newt"><a name="check"></a> Checking the Installed Version of Newt</h3>
+<p>After you have installed newt from either a Debian binary or source package, check that you are using the installed version of newt from <strong>/usr/bin</strong>. </p>
+<p>Check the modification time of the binary and the newt tool that you are using:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ls -l /usr/bin/newt
+-rwxr-xr-x 1 root root 6919280 Apr 22 10:09 /usr/bin/newt
+$which newt
+/usr/bin/newt
+$newt version
+Apache Newt (incubating) version: 1.0.0
</pre></div>
-<p><br></p>
-<h4 id="5-updating-the-newt-tool">5. Updating the Newt tool</h4>
-<ul>
-<li>You will update the newt tool in the same place as you initially installed the newt tool.</li>
-<li>Start by updating the git repository of the newt tool (you can change to a different branch using git checkout [branch] if you need to)</li>
-<li>Then update each of the tools newt, newtmgr and newtvm as needed</li>
-</ul>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ cd $GOPATH/src/mynewt.apache.org/newt
- $ git pull
- $ cd newt
- $ go install
- $ cd ../newtmgr
- $ go install
- $ cd ../newtvm
- $ go install
- $ ls "$GOPATH"/bin/
- newt newtmgr newtvm
+<p><strong>Note:</strong> If you previously built newt from source and the output of <code>which newt</code> shows "$GOPATH/bin/newt", you will need to move "$GOPATH/bin" after "/usr/bin" in your $PATH and export your $PATH.</p>
+<p><br>
+Get information about newt:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$newt
+Newt allows you to create your own embedded application based on the Mynewt
+operating system. Newt provides both build and package management in a single
+tool, which allows you to compose an embedded application, and set of
+projects, and then build the necessary artifacts from those projects. For more
+information on the Mynewt operating system, please visit
+https://mynewt.apache.org/.
+
+Please use the newt help command, and specify the name of the command you want
+help for, for help on how to use a specific command
+
+Usage:
+ newt [flags]
+ newt [command]
+
+Examples:
+ newt
+ newt help [<command-name>]
+ For help on <command-name>. If not specified, print this message.
+
+Available Commands:
+ build Build one or more targets
+ clean Delete build artifacts for one or more targets
+ create-image Add image header to target binary
+ debug Open debugger session to target
+ info Show project info
+ install Install project dependencies
+ load Load built target to board
+ mfg Manufacturing flash image commands
+ new Create a new project
+ pkg Create and manage packages in the current workspace
+ run build/create-image/download/debug <target>
+ size Size of target components
+ sync Synchronize project dependencies
+ target Commands to create, delete, configure, and query targets
+ test Executes unit tests for one or more packages
+ upgrade Upgrade project dependencies
+ vals Display valid values for the specified element type(s)
+ version Display the Newt version number
+
+Flags:
+ -h, --help Help for newt commands
+ -j, --jobs int Number of concurrent build jobs (default 8)
+ -l, --loglevel string Log level (default "WARN")
+ -o, --outfile string Filename to tee output to
+ -q, --quiet Be quiet; only display error output
+ -s, --silent Be silent; don't output anything
+ -v, --verbose Enable verbose output when executing commands
+
+Use "newt [command] --help" for more information about a command.
</pre></div>
-<p>That should have updated your newt, newtmgr and newtvm to the latest versions based on the git repository you used.</p>
<p><br></p>
<div class="row">
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/latest/newtmgr/install_linux/index.html
----------------------------------------------------------------------
diff --git a/latest/newtmgr/install_linux/index.html b/latest/newtmgr/install_linux/index.html
index 716fdd1..a06f3fe 100644
--- a/latest/newtmgr/install_linux/index.html
+++ b/latest/newtmgr/install_linux/index.html
@@ -372,59 +372,197 @@
</div>
</div>
- <h1 id="installing-newtmgr-on-linux">Installing Newtmgr on Linux</h1>
-<p>This page shows you how to install newtmgr from source code on Linux.</p>
-<h3 id="install-go-golang">Install Go (golang)</h3>
-<p>Install Go if it is not installed. The Newtmgr tool version 1.0.0 requires Go version 1.7 or later. Currently, the latest Go version that Ubuntu installs is
-1.6. You can run <code>apt-get install golang-1.7-go</code> to install version 1.7. You can also download version 1.7 from <a href="https://golang.org/dl/">https:/
-/golang.org/dl/</a>.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span style="background-color: #ffffcc">$sudo apt-get install golang-1.7-go
-</span>Reading package lists... Done
+ <h2 id="installing-newtmgr-on-linux">Installing Newtmgr on Linux</h2>
+<p>You can install the latest stable release (1.0.0) of newtmgr from a Debian binary package (amd64) or from a Debian source package. This page shows you how to:</p>
+<ol>
+<li>
+<p>Set up your computer to retrieve Debian packages from the runtimeco debian package repository. </p>
+<p><strong>Note:</strong> You can skip this step if you already set up your computer to access the runtimeco debian repository when you installed the newt tool. </p>
+</li>
+<li>
+<p>Install the latest stable release version of newtmgr from a Debian binary package. </p>
+</li>
+<li>Install the latest stable release version of newtmgr from a Debian source package.</li>
+</ol>
+<p>If you are running on an amd64 platform, we recommend that you install from the binary package.</p>
+<p><strong>Note:</strong> See <a href="../../faq/go_env">Setting Up an Go Environment to Contribute to Newt and Newtmgr Tools</a> if you want to: </p>
+<ul>
+<li>Use the newtmgr tool with the latest updates from the master branch. The master branch may be unstable and we recommend that you use the latest stable release version.</li>
+<li>Contribute to the newtmgr tool. </li>
+</ul>
+<p><br></p>
+<h3 id="setting-up-your-computer-to-get-packages-from-runtimeco">Setting Up Your Computer to Get Packages from runtimeco</h3>
+<p>The newtmgr Debian packages are stored in a private repository on <strong>https://github/runtimeco/debian-mynewt</strong>. </p>
+<p><strong>Note</strong>: You will only need to perform these steps once on your computer. You can skip this step if you already set up your computer to access the runtimeco debian repository when you installed the newt tool. </p>
+<p>The following steps must be performed on your computer:</p>
+<ol>
+<li>Add the <code>apt-transport-https</code> package to use HTTPS to retrieve packages. </li>
+<li>Download the public key for the runtimeco debian repository and import the key into the apt keychain.</li>
+<li>Add the repository for the binary and source packages to the apt source list.</li>
+</ol>
+<p><br>
+Add the apt-transport-https package:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$sudo apt-get update
+$sudo apt-get install apt-transport-https
+</pre></div>
+
+
+<p><br></p>
+<p>Download the public key for the runtimeco apt repo (<strong>Note:</strong> There is <code>-</code> after the add):</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">wget -qO - https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/mynewt.gpg.key | sudo apt-key add -
+</pre></div>
+
+
+<p><br></p>
+<p>Add the repository for the binary and source packages to the apt source list:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$sudo -s
+[sudo] password for <user>:
+root$ cat > /etc/apt/sources.list.d/mynewt.list <<EOF
+deb https://raw.githubusercontent.com/runtimeco/debian-package/master latest main
+deb-src https://raw.githubusercontent.com/runtimeco/debian-package/master latest main
+EOF
+</pre></div>
+
+
+<p><br>
+Check the content of the file:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">root$more /etc/apt/sources.list.d//mynewt.list
+deb https://raw.githubusercontent.com/runtimeco/debian-package/master latest main
+deb-src https://raw.githubusercontent.com/runtimeco/debian-package/master latest main
+</pre></div>
+
+
+<p><br> </p>
+<p>Exit the root shell:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">root$exit
+</pre></div>
+
+
+<p><br></p>
+<h3 id="installing-the-latest-release-of-newtmgr-from-a-binary-package">Installing the Latest Release of Newtmgr from a Binary Package</h3>
+<p>For Linux amd64 platform, you can install the latest stable version (1.0.0) of newtmgr from the newtmgr Debian binary package:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$sudo apt-get update
+$sudo apt-get install newtmgr
+Reading package lists... Done
+Building dependency tree
+Reading state information... Done
+The following NEW packages will be installed:
+ newtmgr
+0 upgraded, 1 newly installed, 0 to remove and 204 not upgraded.
+Need to get 0 B/2,312 kB of archives.
+After this operation, 11.5 MB of additional disk space will be used.
+Selecting previously unselected package newtmgr.
+(Reading database ... 211647 files and directories currently installed.)
+Preparing to unpack .../newtmgr_1.0.0-1_amd64.deb ...
+Unpacking newtmgr (1.0.0-1) ...
+Setting up newtmgr (1.0.0-1)
+</pre></div>
+
+
+<p><br>
+See <a href="#check">Checking the Installed Version of Newtmgr</a> to verify that you are using the installed version of newtmgr.</p>
+<p><br></p>
+<h3 id="installing-the-latest-stable-release-of-newtmgr-from-a-source-package">Installing the Latest Stable Release of Newtmgr from a Source Package</h3>
+<p>If you are running Linux on a different architecture, you can install the Debian source package for the latest stable release (1.0.0) of newtmgr. The installation of the source package builds the newtmgr binary and creates a Debian binary package that you then install.</p>
+<p><strong>Note</strong>: Newtmgr version 1.0.0 has been tested on Linux amd64 platform. </p>
+<p><br></p>
+<h4 id="installing-go-17">Installing Go 1.7</h4>
+<p>You need Go version 1.7 or higher to build Newtmgr version 1.0.0. Currently, the latest Go version that Ubuntu installs is 1.6. Run <code>go version</code> to check if you have Go 1.7 installed. </p>
+<p><br></p>
+<p>Install Go version 1.7:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$sudo apt-get install golang-1.7-go
+Reading package lists... Done
...
Unpacking golang-1.7-go (1.7.1-2ubuntu1) ...
Setting up golang-1.7-go (1.7.1-2ubuntu1) ...
$
-<span style="background-color: #ffffcc">$sudo ln -sf ../lib/go-1.7/bin/go /usr/bin/go
-</span>$go version
+$sudo ln -sf ../lib/go-1.7/bin/go /usr/bin/go
+$go version
go version go1.7.1 linux/amd64
</pre></div>
+<p>You can also download version 1.7 from <a href="https://golang.org/dl/">https://golang.org/dl/</a>. </p>
<p><br></p>
-<p>To use go, you must set a <code>$GOPATH</code> variable in your environment. This tells
-go where to put all the packages it downloads, builds and runs.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ mkdir $HOME/dev
-$ export GOPATH=$HOME/dev/Go
+<h4 id="installing-from-the-source-package">Installing from the Source Package</h4>
+<p>Create a directory and change into the directory, download the source package, and build a binary package from the source package:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">mkdir newtmgr_source
+$cd newtmgr_source
+$sudo apt-get --build source newtmgr
+[sudo] password for <user>:
+
+sudo apt-get --build source newtmgr
+Reading package lists... Done
+Need to get 1,867 kB of source archives.
+Get:1 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newtmgr 1.0.0-1 (dsc) [822 B]
+Get:2 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newtmgr 1.0.0-1 (tar) [1,864 kB]
+Get:3 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newtmgr 1.0.0-1 (diff) [2,372 B]
+Fetched 1,867 kB in 1s (1,767 kB/s)
+
+ ...
+
+dpkg-deb: building package 'newtmgr' in '../newtmgr_1.0.0-1_amd64.deb'.
+ dpkg-genchanges --build=any,all >../newtmgr_1.0.0-1_amd64.changes
+dpkg-genchanges: info: binary-only upload (no source code included)
+ dpkg-source --after-build newtmgr-1.0.0
+dpkg-buildpackage: info: binary-only upload (no source included)
</pre></div>
-<p><br></p>
-<p>Its best to add this to your <code>.profile</code> so its set automatically for your
-environment. </p>
-<p><br></p>
-<h3 id="download-the-newtmgr-source">Download the newtmgr source</h3>
-<p>You will first download the source code for newt.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">go get mynewt.apache.org/newt/...
+<p><br>
+Install the newtmgr binary package that is created from the source package:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$sudo dpkg -i newtmgr_1.0.0-1_amd64.deb
</pre></div>
<p><br></p>
-<h3 id="building-newtmgr">Building newtmgr</h3>
-<p>Change into the directory where the newmgr tool was downloaded and
-install the newtmgr tool</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$cd $GOPATH/src/mynewt.apache.org/newt/newtmgr
-$go install
-$ls $GOPATH/bin
-... newtmgr ...
+<h3 id="checking-the-installed-version-of-newtmgr"><a name="check"></a> Checking the Installed Version of Newtmgr</h3>
+<p>After you have installed newtmgr from either a Debian binary or source package, check that you are using the installed version of newtmgr from <strong>/usr/bin</strong>. </p>
+<p>Check the modification time of the binary and the newtmgr tool that you are using:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ls -l /usr/bin/newtmgr
+-rwxr-xr-x 1 root root 11473328 Apr 25 10:10 /usr/bin/newtmgr
+$which newtmgr
+/usr/bin/newtmgr
</pre></div>
-<p><br></p>
-<p><strong>Note:</strong> If the <code>go install</code> command results in errors indicating some package
-cannot be found, do a <code>go get</code> to download all the third-party files needed
-from github.com and then run <code>go install</code> again. </p>
-<h3 id="add-to-your-path">Add to your Path</h3>
-<p>Add your <code>$GOPATH/bin</code> directory to your path.</p>
+<p><strong>Note:</strong> If you previously built newtmgr from source and the output of <code>which newtmgr</code> shows "$GOPATH/bin/newtmgr", you will need to move "$GOPATH/bin" after "/usr/bin" in your $PATH and export your $PATH.</p>
+<p><br>
+Get information about newtmgr:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$newtmgr
+Newtmgr helps you manage remote devices running the Mynewt OS
+
+Usage:
+ newtmgr [flags]
+ newtmgr [command]
+
+Available Commands:
+ config Read or write a config value on a device
+ conn Manage newtmgr connection profiles
+ crash Send a crash command to a device
+ datetime Manage datetime on a device
+ echo Send data to a device and display the echoed back data
+ fs Access files on a device
+ image Manage images on a device
+ log Manage logs on a device
+ mpstats Read memory pool statistics from a device
+ reset Send reset request to a device
+ run Run test procedures on a device
+ stat Read statistics from a device
+ taskstats Read task statistics from a device
+
+Flags:
+ -c, --conn string connection profile to use
+ -h, --help Help for newtmgr commands
+ -l, --loglevel string log level to use (default "info")
+ -t, --trace print all bytes transmitted and received
+
+Use "newtmgr [command] --help" for more information about a command.
+</pre></div>
+
+
+<p>```
+<br></p>
<div class="row">
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/latest/os/get_started/cross_tools/index.html
----------------------------------------------------------------------
diff --git a/latest/os/get_started/cross_tools/index.html b/latest/os/get_started/cross_tools/index.html
index 9dcfe2b..85ec703 100644
--- a/latest/os/get_started/cross_tools/index.html
+++ b/latest/os/get_started/cross_tools/index.html
@@ -392,11 +392,14 @@
</div>
<h1 id="installing-cross-tools-for-arm">Installing Cross Tools for ARM</h1>
-<p>This page shows how to install tools on your laptop/computer to use for direct communication (e.g. for debugging) with some ARM based HW platforms running Apache Mynewt. You will also have to use the Newt tool installed to run natively on your machine. You may choose to do this instead of using the build toolchain and Newt tool available in a Docker container.</p>
-<p>This page provides guidance for installing the tools directly on your MAC and Linux machine. See the relevant sections below.</p>
+<p>This page shows how to install tools on your laptop/computer to use for direct communication (e.g. for debugging) with some ARM based HW platforms running Apache Mynewt. It shows you how to install the following tools for Mac OS X and Linux:</p>
+<ul>
+<li>ARM Cross toolchain</li>
+<li>Debugger to load and debug your device</li>
+</ul>
<p><br></p>
-<h2 id="install-arm-cross-tools-in-mac-os-x">Install ARM Cross tools in Mac OS X</h2>
-<h3 id="install-tool-chain">Install Tool Chain</h3>
+<h2 id="install-arm-cross-toolchain">Install ARM Cross Toolchain</h2>
+<h3 id="install-arm-toolchain-for-mac-os-x">Install ARM Toolchain For Mac OS X</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,
@@ -420,22 +423,7 @@ 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</h3>
-<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>
-<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 <user> admin 36 Sep 17 16:22 /usr/local/bin/openocd -> ../Cellar/open-ocd/0.9.0/bin/openocd
-</pre></div>
-
-
-<p><br></p>
-<h2 id="install-arm-cross-arm-tools-for-linux">Install ARM cross arm tools for Linux</h2>
-<h3 id="install-tool-chain_1">Install Tool Chain</h3>
+<h3 id="install-arm-toolchain-for-linux">Install ARM Toolchain For Linux</h3>
<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/~team-gcc-arm-embedded/+archive/ubuntu/ppa">https://launchpad.net/~team-gcc-arm-embedded/+archive/ubuntu/ppa</a>.</p>
@@ -448,20 +436,86 @@ $ sudo apt-get install gdb-arm-none-eabi
<p><br></p>
-<h3 id="install-openocd_1">Install OpenOCD</h3>
+<h2 id="install-debugger">Install Debugger</h2>
+<p>Mynewt uses, depending on the board, either the OpenOCD or SEGGER J-Link debugger. </p>
+<h3 id="install-openocd">Install OpenOCD</h3>
<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
+<p>OpenOCD version 0.10.0 with nrf52 support is required. A binary for this version is available to download for Mac OS and Linux.</p>
+<p><br></p>
+<h4 id="install-openocd-on-mac-os">Install OpenOCD on Mac OS</h4>
+<p>Step 1: Download the <a href="https://github.com/runtimeco/openocd-binaries/raw/master/openocd-bin-0.10.0-MacOS.tgz">binary tarball for Mac OS</a>.</p>
+<p>Step 2: Change to the root directory: </p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$cd /
+</pre></div>
+
+
+<p><br>
+Step 3: Untar the tarball and install into <strong> /usr/local/bin</strong>. You will need to replace <strong> ~/Downloads </strong> with the directory that the tarball is downloaded to. </p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">sudo tar -xf ~/Downloads/openocd-bin-0.10.0-MacOS.tgz `
+</pre></div>
+
+
+<p><br>
+Step 4: Check the OpenOCD version you are using: </p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$which openocd
+/usr/local/bin/openocd
+$openocd -v
+Open On-Chip Debugger 0.10.0
+Licensed under GNU GPL v2
+For bug reports, read
+http://openocd.org/doc/doxygen/bugs.html
+</pre></div>
+
+
+<p>You should see version: <strong>0.10.0</strong>. </p>
+<p><br></p>
+<h4 id="install-openocd-on-linux">Install OpenOCD on Linux</h4>
+<p>Step 1: Download the <a href="https://github.com/runtimeco/openocd-binaries/raw/master/openocd-bin-0.10.0-Linux.tgz">binary tarball for Linux</a></p>
+<p>Step 2: Change to the root directory: </p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$cd /
</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><br>
+Step 3: Untar the tarball and install into <strong> /usr/local/bin</strong>. You will need to replace <strong> ~/Downloads </strong> with the directory that the tarball is downloaded to. </p>
+<p><strong> Note:</strong> You must specify the -p option for the tar command.</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$sudo tar -xpf ~/Downloads/openocd-bin-0.10.0-Linux.tgz
+</pre></div>
+
+
+<p><br>
+Step 4: Check the OpenOCD version you are using: </p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$which openocd
+/usr/local/bin/openocd
+$openocd -v
+Open On-Chip Debugger 0.10.0
+Licensed under GNU GPL v2
+For bug reports, read
+http://openocd.org/doc/doxygen/bugs.html
+</pre></div>
+
+
+<p>You should see version: <strong>0.10.0</strong>. </p>
+<p>If you see any of these error messages:</p>
+<ul>
+<li>
+<p>openocd: error while loading shared libraries: libhidapi-hidraw.so.0: cannot open shared object file: No such file or directory</p>
+</li>
+<li>
+<p>openocd: error while loading shared libraries: libusb-1.0.so.0: cannot open shared object file: No such file or directory </p>
+</li>
+</ul>
+<p>run the following command to install the libraries: </p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$sudo apt-get install libhidapi-dev:i386
+</pre></div>
+
+
+<p><br></p>
+<h3 id="install-seggar-j-link">Install SEGGAR J-Link</h3>
+<p>You can download and install Segger J-LINK Software and documentation pack from <a href="https://www.segger.com/jlink-software.html">SEGGER</a>. </p>
<div class="row">
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/latest/os/get_started/get_started/index.html
----------------------------------------------------------------------
diff --git a/latest/os/get_started/get_started/index.html b/latest/os/get_started/get_started/index.html
index 8e648ae..96eca2f 100644
--- a/latest/os/get_started/get_started/index.html
+++ b/latest/os/get_started/get_started/index.html
@@ -361,13 +361,12 @@
<h2 id="quick-start">Quick Start</h2>
<p>If you are curious about Mynewt and want to get a quick feel for the project, you've come to the right place. We have two options for you:</p>
+<p><br>
+<strong>Option 1 (Recommended)</strong> allows you to install the Newt tool, instances of the Mynewt OS (for simulated targets), and toolchains for developing embedded software (e.g. GNU toolchain) natively on your laptop or computer. We have tried to make the process easy. For example, for the Mac OS we created brew formulas. </p>
+<p>We recommend this option if you are familiar with such environments or are concerned about performance on your machine. Follow the instructions to <a href="../native_tools/">install native tools</a> and <a href="../cross_tools/">install cross tools for ARM</a> if you prefer this option.</p>
<p><br></p>
-<p><strong>Option 1</strong> is an easy, self-contained way to get up and running with Mynewt - but has limitations! The Newt tool and build toolchains are all available in a single <a href="../docker/">All-in-one Docker Container</a> that you can install on your laptop or computer.</p>
-<p>However, this is not a long-term option since support is not likely for all features useful or critical to embedded systems development. For example, USB device mapping available in the Docker toolkit (used in this Option 1) is no longer available in the new Docker releases. The Docker option is also typically slower than the native install option. </p>
-<p><span style="color:red"> Therefore, the recommended option is Option 2 below. </span></p>
-<p><br></p>
-<p><strong>Option 2 (Recommended)</strong> allows you to install the Newt tool, instances of the Mynewt OS (for simulated targets), and toolchains for developing embedded software (e.g. GNU toolchain) natively on your laptop or computer. We have tried to make the process easy. For example, for the Mac OS we created brew formulas. </p>
-<p>You want this option if you are familiar with such environments or are concerned about performance on your machine. Follow the instructions to <a href="../native_tools/">install native tools</a> and <a href="../cross_tools/">install cross tools for ARM</a> if you prefer this option.</p>
+<p><strong>Option 2</strong> is an easy, self-contained way to get up and running with Mynewt - but has limitations! The Newt tool and build toolchains are all available in a single <a href="../docker/">All-in-one Docker Container</a> that you can install on your laptop or computer.</p>
+<p>However, this is not a long-term option since support is not likely for all features useful or critical to embedded systems development. For example, USB device mapping available in the Docker toolkit is no longer available in the new Docker releases. The Docker option is also typically slower than the native install option. </p>
<p><br></p>
<p>You can then proceed with the instructions on how to
* <a href="../project_create/">Create Your First Project</a> - on simulated hardware.</p>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/latest/os/get_started/native_tools/index.html
----------------------------------------------------------------------
diff --git a/latest/os/get_started/native_tools/index.html b/latest/os/get_started/native_tools/index.html
index 38c0f4d..8c957f0 100644
--- a/latest/os/get_started/native_tools/index.html
+++ b/latest/os/get_started/native_tools/index.html
@@ -411,8 +411,8 @@
<p><br></p>
<p>Check the gcc version you have installed (either using brew or previously installed). The brew-installed version can be checked using <code>brew list gcc</code>. The default compiler.yml configuration file in Mynewt expects version 5.x for Mac users, so if the installed version is 6.x and you wish to continue with this newer version, modify the <code><mynewt-src-directory>/repos/apache-mynewt-core/compiler/sim/compiler.yml</code> file to change the default <code>gcc-5</code> defined there to <code>gcc-6</code>. In other words, replace the lines shown highlighted below:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"># OS X.
-<span style="background-color: #ffffcc">compiler.path.cc.DARWIN.OVERWRITE: "/usr/local/bin/gcc-5"
-</span><span style="background-color: #ffffcc">compiler.path.as.DARWIN.OVERWRITE: "/usr/local/bin/gcc-5 -x assembler-with-cpp"
+<span style="background-color: #ffffcc">compiler.path.cc.DARWIN.OVERWRITE: "gcc-5"
+</span><span style="background-color: #ffffcc">compiler.path.as.DARWIN.OVERWRITE: "gcc-5"
</span>compiler.path.objdump.DARWIN.OVERWRITE: "gobjdump"
compiler.path.objsize.DARWIN.OVERWRITE: "objsize"
compiler.path.objcopy.DARWIN.OVERWRITE: "gobjcopy"
@@ -420,16 +420,16 @@ compiler.path.objcopy.DARWIN.OVERWRITE: "gobjcopy"
<p>with the following:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">compiler.path.cc.DARWIN.OVERWRITE: "/usr/local/bin/gcc-6"
-compiler.path.as.DARWIN.OVERWRITE: "/usr/local/bin/gcc-6 -x assembler-with-cpp\u201d
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">compiler.path.cc.DARWIN.OVERWRITE: "gcc-6"
+compiler.path.as.DARWIN.OVERWRITE: "gcc-6\u201d
</pre></div>
<p><br></p>
<p>In case you wish to use Clang, you can change your <code><mynewt-src-directory>/repos/apache-mynewt-core/compiler/sim/compiler.yml</code> to use Clang. Delete the gcc-5 DARWIN.OVERWRITE lines highlighted below.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"># OS X.
-<span style="background-color: #ffffcc">compiler.path.cc.DARWIN.OVERWRITE: "/usr/local/bin/gcc-5"
-</span><span style="background-color: #ffffcc">compiler.path.as.DARWIN.OVERWRITE: "/usr/local/bin/gcc-5 -x assembler-with-cpp"
+<span style="background-color: #ffffcc">compiler.path.cc.DARWIN.OVERWRITE: "gcc-5"
+</span><span style="background-color: #ffffcc">compiler.path.as.DARWIN.OVERWRITE: "gcc-5"
</span>compiler.path.objdump.DARWIN.OVERWRITE: "gobjdump"
compiler.path.objsize.DARWIN.OVERWRITE: "objsize"
compiler.path.objcopy.DARWIN.OVERWRITE: "gobjcopy"
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/latest/os/get_started/project_create/index.html
----------------------------------------------------------------------
diff --git a/latest/os/get_started/project_create/index.html b/latest/os/get_started/project_create/index.html
index 249a2e5..4098295 100644
--- a/latest/os/get_started/project_create/index.html
+++ b/latest/os/get_started/project_create/index.html
@@ -442,7 +442,7 @@ file. </p>
</pre></div>
-<p>Changing to 1-dev will put you on the develop branch. <strong>The Develop Branch may not be stable and you may encounter bugs or other problems.</strong></p>
+<p>Changing to 0-dev will put you on the latest master branch. <strong>This branch may not be stable and you may encounter bugs or other problems.</strong></p>
<p><br></p>
<h3 id="newt-install">Newt Install</h3>
<p>Once you've switched into your new project's directory, the next step is to fetch
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/latest/os/get_started/vocabulary/index.html
----------------------------------------------------------------------
diff --git a/latest/os/get_started/vocabulary/index.html b/latest/os/get_started/vocabulary/index.html
index 3afe373..10353ff 100644
--- a/latest/os/get_started/vocabulary/index.html
+++ b/latest/os/get_started/vocabulary/index.html
@@ -363,8 +363,8 @@ the <code>apache-mynewt-core</code> repository.</p>
</li>
<li>
<p><code>vers=1-latest</code>: Defines the repository version. This string will use the
-latest code in the 'Master' github branch. To use the latest version in the
-develop branch, just change it to <code>vers=1-dev</code></p>
+latest stable version in the 'Master' github branch. To use the latest version in the
+master branch, just change it to <code>vers=0-dev</code>. Note that this branch might not be stable. </p>
</li>
</ul>
<p>Repositories are versioned collections of packages. </p>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/latest/os/tutorials/STM32F303/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/STM32F303/index.html b/latest/os/tutorials/STM32F303/index.html
deleted file mode 100644
index c256e9b..0000000
--- a/latest/os/tutorials/STM32F303/index.html
+++ /dev/null
@@ -1,774 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
- <head>
- <meta charset="utf-8">
- <meta http-equiv="X-UA-Compatible" content="IE=edge">
- <meta name="viewport" content="width=device-width, initial-scale=1.0">
-
-
- <!-- This is broken by doc revisioning.
- <link rel="canonical" href="http://mynewt.apache.org/os/tutorials/STM32F303/"> -->
- <link rel="shortcut icon" href="../../../img/favicon.ico">
-
- <title>toc - Apache Mynewt</title>
-
- <link href="../../../css/bootstrap-3.0.3.min.css" rel="stylesheet">
- <link rel="stylesheet" href="../../../css/highlight.css">
- <link href="../../../css/base.css" rel="stylesheet">
- <link href="../../../css/custom.css" rel="stylesheet">
- <link href="../../../css/v2.css" rel="stylesheet">
- <link href="https://fonts.googleapis.com/css?family=Lato" rel="stylesheet">
- <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/font-awesome/4.5.0/css/font-awesome.min.css">
- <link href="../../../extra.css" rel="stylesheet">
-
- <!-- HTML5 shim and Respond.js IE8 support of HTML5 elements and media queries -->
- <!--[if lt IE 9]>
- <script src="https://oss.maxcdn.com/libs/html5shiv/3.7.0/html5shiv.js"></script>
- <script src="https://oss.maxcdn.com/libs/respond.js/1.3.0/respond.min.js"></script>
- <![endif]-->
-
-
- <script>
- (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
- (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
- m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
- })(window,document,'script','//www.google-analytics.com/analytics.js','ga');
-
- ga('create', 'UA-72162311-1', 'auto');
- ga('send', 'pageview');
- </script>
-
- </head>
-
-
- <body class="toc">
-
-
- <div class="container">
- <div class="row v2-main-banner">
- <a class="logo-cell" href="/">
- <img class="logo" src="/img/logo.png">
- </a>
- <div class="tagline-cell">
- <h4 class="tagline">An OS to build, deploy and securely manage billions of devices</h4>
- </div>
- <div class="news-cell">
- <div class="well">
- <h4>Latest News:</h4> <a href="/download">Apache Mynewt 1.0.0</a> released (March 22, 2017)
- </div>
- </div>
- </div>
-</div>
-
-
-
-
-
-
-
-
-<nav id="navbar" class="navbar navbar-inverse affix-top" data-spy="affix" data-offset-top="150" role="navigation">
- <div class="container">
- <!-- Collapsed navigation -->
- <div class="navbar-header">
- <!-- Expander button -->
- <button type="button" class="navbar-toggle" data-toggle="collapse" data-target=".navbar-collapse">
- <span class="sr-only">Toggle navigation</span>
- <span class="icon-bar"></span>
- <span class="icon-bar"></span>
- <span class="icon-bar"></span>
- </button>
-
- </div>
-
- <!-- Expanded navigation -->
- <div class="navbar-collapse collapse">
- <!-- Main navigation -->
- <ul class="nav navbar-nav navbar-right">
- <li
- class=""
->
- <a href="/"><i class="fa fa-home" style="font-size: larger;"></i></a>
- </li>
- <li
- class="important"
->
- <a href="/quick-start/">Quick Start</a>
- </li>
- <li
- class=""
->
- <a href="/about/">About</a>
- </li>
- <li
- class=""
->
- <a href="/talks/">Talks</a>
- </li>
- <li
- class="active"
->
- <a href="/latest/os/introduction">Documentation</a>
- </li>
- <li
- class=""
->
- <a href="/download/">Download</a>
- </li>
- <li
- class=""
->
- <a href="/community/">Community</a>
- </li>
- <li
- class=""
->
- <a href="/events/">Events</a>
- </li>
- </ul>
-
- <!-- Search, Navigation and Repo links -->
- <ul class="nav navbar-nav navbar-right">
-
- </ul>
- </div>
- </div>
-</nav>
-
-
-
- <div class="container">
-
- <div class="row">
- <div class="col-md-3 v2-sidebar sidebar-container"><div id="docSidebar" class="hidden-print" role="complementary">
- <div class="top">
- <div role="search">
- <form id="rtd-search-form" class="wy-form" action="../../../search.html" method="get">
- <div class="form-group">
- <input type="text" name="q" class="form-control" placeholder="Search documentation" />
- </div>
- </form>
- </div>
- </div>
- <ul class="toc-nav">
- <li class="doc-version">
-<select class="form-control" onchange="if (this.value) window.location.href=this.value">
-
- <option
- value="/develop/os/introduction"
- selected="selected"
- >
- Version: develop (latest)
- </option>
-
- <option
- value="/v0_9_0/os/introduction"
-
- >
- Version: 0.9.0
- </option>
-
-</select>
-</li>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- <li ><a href="../../introduction/">Mynewt Documentation</a>
-
-
- <ul>
-
-
-
-
-
-
-
- <li ><a href="../../get_started/get_started/">Basic Setup</a>
-
-
- </li>
-
-
-
-
-
- <li >
- <a href="../../get_started/vocabulary/">Concepts</a>
- </li>
-
-
-
-
-
-
-
- <li ><a href="../tutorials/">Tutorials</a>
-
-
- <ul>
-
-
-
-
-
-
-
- <li ><a href="../blinky/">Project Blinky</a>
-
-
- <ul>
-
-
-
-
-
- <li >
- <a href="../arduino_zero/">Blinky on Arduino Zero</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../blinky_primo/">Blinky on Arduino Primo</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../olimex/">Blinky on Olimex</a>
- </li>
-
-
-
-
-
-
-
- <li class="active"><a href="./">Blinky on STM32F303</a>
-
-
- <ul>
-
-
-
-
-
- <li >
- <a href="../pin-wheel-mods/">Pinwheel Blinky</a>
- </li>
-
-
-
- </ul>
-
- </li>
-
-
-
-
-
- <li >
- <a href="../nRF52/">Blinky on nRF52</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../rbnano2/">Blinky on RedBear Nano 2</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../blinky_console/">Add Console and Shell to Blinky</a>
- </li>
-
-
-
- </ul>
-
- </li>
-
-
-
-
-
-
-
- <li ><a href="../repo/add_repos/">Work with repositories</a>
-
-
- </li>
-
-
-
-
-
-
-
- <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
-
-
- </li>
-
-
-
-
-
- <li >
- <a href="../ibeacon/">BLE iBeacon</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../eddystone/">BLE Eddystone</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../add_shell/">Enable the OS Shell and Console</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../tasks_lesson/">Tasks and Priority Management</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../unit_test/">Write a Test Suite for a Package</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../event_queue/">Events and Event Queues</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../bletiny_project/">BLE app to check stats via console</a>
- </li>
-
-
-
-
-
-
-
- <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
- </li>
-
-
-
-
-
- <li >
- <a href="../blehci_project/">BLE HCI interface</a>
- </li>
-
-
-
-
-
-
-
- <li><a href="
- ../air_quality_sensor/
-">Air-quality Sensor project</a>
-
-
- </li>
-
-
-
-
-
- <li >
- <a href="../nrf52_adc/">Add an Analog Sensor</a>
- </li>
-
-
-
- </ul>
-
- </li>
-
-
-
-
-
-
-
- <li ><a href="../../os_user_guide/">OS User Guide</a>
-
-
- </li>
-
-
-
-
-
-
-
- <li><a href="
- ../../../network/ble/ble_intro/
-">BLE User Guide</a>
-
-
- </li>
-
-
-
-
-
-
-
- <li ><a href="../../../newt/newt_intro/">Newt Tool Guide</a>
-
-
- </li>
-
-
-
-
-
-
-
- <li ><a href="../../../newtmgr/overview/">Newt Manager Guide</a>
-
-
- </li>
-
-
-
- </ul>
-
- </li>
-
-
-
-
-
-
-
- <li><a href="
- ../../../faq/go_env/
-">Appendix</a>
-
-
- </li>
-
-
-
- </ul>
-</div></div>
-
- <div class="col-md-9" role="main">
- <div class="doc-header">
- <div role="navigation" aria-label="breadcrumbs navigation">
- <ul class="wy-breadcrumbs pull-right">
- <li><a href="/latest/os/introduction">Docs</a></li>
-
-
-
- <li>» <a href="../blinky/">Project Blinky</a></li>
-
-
-
- <li>» Blinky on STM32F303</li>
-
-
-
-
-
- </ul>
-</div>
- </div>
-
- <h2 id="blinky-your-hello-world-on-stm32f303-discovery">Blinky, your "Hello World!", on STM32F303 Discovery</h2>
-<p><br></p>
-<h3 id="objective">Objective</h3>
-<p>Learn how to use packages from a default application repository of Mynewt to build your first <em>Hello World</em> application (Blinky) on a target board. Once built using the <em>newt</em> tool, this application will blink the LED lights on the target board.</p>
-<p>Create a project with a simple app that blinks an LED on the stmf303
-discovery board. In the process import some external libraries into your project. Download the application to the target and watch it blink!</p>
-<p><br></p>
-<h3 id="what-you-need">What you need</h3>
-<ul>
-<li>Discovery kit with STM32F303VC MCU</li>
-<li>Laptop running Mac OSX. </li>
-<li>It is assumed you have already installed newt tool. </li>
-<li>It is assumed you already installed native tools as described <a href="../../get_started/native_tools/">here</a></li>
-</ul>
-<p>Also, we assume that you're familiar with UNIX shells. Let's gets started!</p>
-<p><br></p>
-<h3 id="create-a-project">Create a project</h3>
-<p>Create a new project to hold your work. For a deeper understanding, you can read about project creation in
-<a href="../../get_started/project_create/">Get Started -- Creating Your First Project</a>
-or just follow the commands below.</p>
-<p>If you've already created a project from another tutorial, you can re-use
-that project.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ mkdir ~/dev
-$ cd ~/dev
-$ newt new myproj
-Downloading project skeleton from apache/incubator-mynewt-blinky...
-Installing skeleton in myproj...
-Project myproj successfully created.
-
-$ cd myproj
-</pre></div>
-
-
-<p><strong>Note:</strong> Don't forget to change into the <code>myproj</code> directory.</p>
-<p><br></p>
-<h3 id="import-external-stm32f3-library-support">Import External STM32F3 Library support</h3>
-<p>The STM32F303 support for Mynewt lives in an external repository. It's
-necessary to add another repository to the project. To do this,
-edit the file <code>project.yml</code> in the root directory of your project <code>myproj</code></p>
-<p>This requires two changes to this file.</p>
-<ol>
-<li>You must define the properties of the external repository that you want
-to add</li>
-<li>You must include the repository in your project.</li>
-</ol>
-<p>Edit the file <code>project.yml</code> with your favorite editor and add the
-following repository details in the file (after the core
-repository). This gives newt the information to contact the repository
-and extract its contents. In this case, the repository is on github in
-the <code>runtimeinc</code> collection. Its name is <code>mynewt-stm32f3</code> and we will accept
-any version up to the latest. You can look at the contents <a href="https://github.com/runtimeinc/mynewt_stm32f3">here</a>.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">repository.mynewt_stm32f3:
- type: github
- vers: 0-latest
- user: runtimeinc
- repo: mynewt_stm32f3
-</pre></div>
-
-
-<p><br></p>
-<p>In the same file, add the following highlighted line to the
-<code>project.repositories</code> variable. This tells newt to download the
- repository contents into your project. </p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">project.repositories:
- - apache-mynewt-core
-<span style="background-color: #ffffcc"> - mynewt_stm32f3
-</span></pre></div>
-
-
-<p><br></p>
-<h3 id="install-dependencies">Install dependencies</h3>
-<p>Now you can install this into the project using:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt install -v
-Downloading repository description for apache-mynewt-core... success!
-...
-apache-mynewt-core successfully installed version 0.9.1-none
-...
-Downloading repository description for mynewt_stm32f3... success!
-Downloading repository mynewt_stm32f3
-...
-Resolving deltas: 100% (65/65), done.
-Checking connectivity... done.
-mynewt_stm32f3 successfully installed version 0.9.0-none
-</pre></div>
-
-
-<p><br></p>
-<h3 id="create-targets">Create targets</h3>
-<p>Create two targets to build using the stmf3 board support package and the
-app blinky example from mynewt. The output of these commands are not
-shown here for brevity. </p>
-<p>The first target is the application image itself. The second
-target is the bootloader which allows you to upgrade your mynewt
-applications. </p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt target create stmf3_blinky
-$ newt target set stmf3_blinky build_profile=optimized
-$ newt target set stmf3_blinky bsp=@mynewt_stm32f3/hw/bsp/stm32f3discovery
-$ newt target set stmf3_blinky app=apps/blinky
-
-$ newt target create stmf3_boot
-$ newt target set stmf3_boot app=@apache-mynewt-core/apps/boot
-$ newt target set stmf3_boot bsp=@mynewt_stm32f3/hw/bsp/stm32f3discovery
-$ newt target set stmf3_boot build_profile=optimized
-
-$ newt target show
-
-targets/stmf3_blinky
- app=apps/blinky
- bsp=@mynewt_stm32f3/hw/bsp/stm32f3discovery
- build_profile=optimized
-targets/stmf3_boot
- app=apps/boot
- bsp=@mynewt_stm32f3/hw/bsp/stm32f3discovery
- build_profile=optimized
-</pre></div>
-
-
-<p><br></p>
-<h3 id="build-the-target-executables">Build the target executables</h3>
-<p>To build the images, use the <code>newt build</code> command below.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt build stmf3_blinky
- ...
-Archiving stm32f3discovery.a
-Linking blinky.elf
-App successfully built: ~/dev/myproj/bin/stmf3_blinky/apps/blinky/blinky.elf
-
-$ newt build stmf3_boot
-Compiling log_shell.c
-Archiving log.a
-Linking boot.elf
-App successfully built: ~/dev/myproj/bin/stmf3_boot/apps/boot/boot.elf
-</pre></div>
-
-
-<p><br></p>
-<h3 id="sign-and-create-the-blinky-application-image">Sign and create the blinky application image</h3>
-<p>You must sign and version your application image to download it using newt. Use
-the <code>newt create-image</code> command to perform this action. Here we assign this
-image an arbitrary version <code>1.2.3</code>.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt create-image stmf3_blinky 1.2.3
-App image successfully generated: ~/dev/myproj/bin/stmf3_blinky/apps/blinky/blinky.img
-Build manifest:~/dev/myproj/bin/stmf3_blinky/apps/blinky/manifest.json
-</pre></div>
-
-
-<p><br></p>
-<h3 id="configure-the-hardware">Configure the hardware</h3>
-<p>The STM32F3DISCOVERY board includes an ST-LINK/V2 embedded debug tool interface that will be used to program/debug the board. To program the MCU on the board, simply plug in the two jumpers on CN4, as shown in the picture in red. If you want to learn more about the board you will find the User Manual at <a href="http://www.st.com/st-web-ui/static/active/jp/resource/technical/document/user_manual/DM00063382.pdf">http://www.st.com/st-web-ui/static/active/jp/resource/technical/document/user_manual/DM00063382.pdf</a></p>
-<p>Just plug the USB cable into the <code>USB ST-LINK</code> port and it should power on and be ready to dowload to.</p>
-<ul>
-<li><img alt="STMdiscovery" src="../pics/STM32f3discovery_connector.png" /></li>
-</ul>
-<p><br></p>
-<h3 id="download-the-images">Download the Images</h3>
-<p>Use the <code>newt load</code> command to download the images to the target board.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt -v load stmf3_boot
-$ newt -v load stmf3_blinky
-</pre></div>
-
-
-<p><br></p>
-<h3 id="watch-the-led-blink">Watch the LED blink</h3>
-<p>Congratulations! You have built, downloaded, and run your first application using mynewt for the stm32f3 discovery board. One of the LEDs on the LED wheel should be blinking at 1 Hz.</p>
-<p><br></p>
-<h3 id="want-more">Want more?</h3>
-<p>Want to make your board do something a little more exciting with the LEDs? Then try making the modifications to the Blinky app to make it a <a href="../pin-wheel-mods/">pin-wheel app</a> and you can light all the LEDs in a pin-wheel fashion.</p>
-<p>We have more fun tutorials for you to get your hands dirty. Be bold and try other Blinky-like <a href="../nRF52/">tutorials</a> or try enabling additional functionality such as <a href="../project-slinky/">remote comms</a> on the current board.</p>
-<p>If you see anything missing or want to send us feedback, please do so by signing up for appropriate mailing lists on our <a href="../../../community/">Community Page</a>.</p>
-<p>Keep on hacking and blinking!</p>
-
- <div class="row">
-
-
-
-
-<ul class="nav nav-pills" style="margin-bottom: 10px">
- <li>
-
- <a href=../olimex/>
- <span class="fa fa-arrow-left"></span>
- Previous: Blinky on Olimex
- </a>
-
- </li>
- <li class="pull-right">
-
- <a href=../pin-wheel-mods/>
- Next: Pinwheel Blinky
- <span class="fa fa-arrow-right"></span>
- </a>
-
- </li>
-</ul>
- </div>
- <footer class="row">
- <div class="col-xs-12">
-
- <p class="copyright">Apache Mynewt (incubating) is available under Apache License, version 2.0.</p>
-
- </div>
- <div class="col-xs-12">
- <div class="logos">
- <img src="/img/asf_logo_wide_small.png" alt="Apache" title="Apache">
- <small class="footnote">
- MyNewt is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.
- </small>
- <img src="/img/egg-logo2.png" alt="Apache Incubator" title="Apache Incubator">
- </div>
- </div>
-</footer>
- </div>
- </div>
-
-
- </div>
-
- <script src="../../../js/jquery-1.10.2.min.js"></script>
- <script src="../../../js/bootstrap-3.0.3.min.js"></script>
- <script src="../../../js/highlight.pack.js"></script>
- <script src="../../../js/base.js"></script>
- <script src="../../../js/custom.js"></script>
-
- </body>
-</html>
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/latest/os/tutorials/arduino_zero/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/arduino_zero/index.html b/latest/os/tutorials/arduino_zero/index.html
index 3360523..ca09ea1 100644
--- a/latest/os/tutorials/arduino_zero/index.html
+++ b/latest/os/tutorials/arduino_zero/index.html
@@ -265,17 +265,6 @@
-
-
- <li ><a href="../STM32F303/">Blinky on STM32F303</a>
-
-
- </li>
-
-
-
-
-
<li >
<a href="../nRF52/">Blinky on nRF52</a>
</li>
@@ -543,6 +532,7 @@
<li>Meet the prerequisites listed in <a href="../blinky/">Project Blinky</a>.</li>
<li>Have an Arduino Zero board.<br />
Note: There are many flavors of Arduino. Make sure you are using an Arduino Zero. See below for the versions of Arduino Zero that are compatible with this tutorial.</li>
+<li>Install the <a href="../../../os/get_started/cross_tools/">OpenOCD debugger</a>.</li>
</ul>
<p>This tutorial uses the Arduino Zero Pro board. The tutorial has been tested on the following three Arduino Zero boards - Zero, M0 Pro, and Zero-Pro.</p>
<p><img src="https://www.arduino.cc/en/uploads/Main/Zero_Usb_Ports.jpg" alt="Drawing" style="width: 390px;"/>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/latest/os/tutorials/blehci_project/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/blehci_project/index.html b/latest/os/tutorials/blehci_project/index.html
index 7f898ab..179dbff 100644
--- a/latest/os/tutorials/blehci_project/index.html
+++ b/latest/os/tutorials/blehci_project/index.html
@@ -594,13 +594,16 @@ Bluetooth monitor ver 5.37
<p><br></p>
<h3 id="attach-the-blehci-device-to-bluez">Attach the blehci device to BlueZ</h3>
<p>In a different terminal, attach the blehci device to the BlueZ daemon (substitute the correct /dev filename for ttyUSB0).</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ sudo btattach -B /dev/ttyUSB0 -S 115200
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ sudo btattach -B /dev/ttyUSB0 -S 1000000
Attaching BR/EDR controller to /dev/ttyUSB0
Switched line discipline from 0 to 15
Device index 1 attached
</pre></div>
+<p>The baud rate used to connect to the controller may be changed by overriding the default value of 1000000 in the <code>net/nimble/transport/uart/syscfg.yml</code>. Settings in the serial transport <code>syscfg.yml</code> file can be overridden by a higher priority package such as the application. So, for example, you may set the <code>BLE_HCI_UART_BAUD</code> to a different value in <code>apps/blehci/syscfg.yml</code>.</p>
+<p>If there is no CTS/RTS lines present in the test environment, flow control should be turned off. This can be done with
+-N option for btattach. <strong>Note:</strong> -N option came with BlueZ ver 5.44.</p>
<p><br></p>
<h3 id="start-btmgmt-to-send-commands">Start btmgmt to send commands</h3>
<p>In a third terminal, start btmgmt. This tool allows you to send commands to the blehci controller. Use the index number that shows up when you <code>btattach</code> in the previous step.</p>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/latest/os/tutorials/blinky/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/blinky/index.html b/latest/os/tutorials/blinky/index.html
index 72c0ba6..9f77141 100644
--- a/latest/os/tutorials/blinky/index.html
+++ b/latest/os/tutorials/blinky/index.html
@@ -265,17 +265,6 @@
-
-
- <li ><a href="../STM32F303/">Blinky on STM32F303</a>
-
-
- </li>
-
-
-
-
-
<li >
<a href="../nRF52/">Blinky on nRF52</a>
</li>
@@ -556,9 +545,8 @@
<li>Have a computer to build a Mynewt application and connect to the board over USB.</li>
<li>Have a Micro-USB cable to connect the board and the computer.</li>
<li>Install the Newt tool and toolchains (See <a href="../../get_started/get_started/">Basic Setup</a>).</li>
-<li>Install either the Jlink or OpenOCD debugger.</li>
-<li>Create a project space (directory structure) and populate it with the core code repository (apache-mynewt-core) or know how to as explained in <a href="../../../os/get_started/project_create">Creating Your First Project</a>.</li>
-<li>Read the Mynewt OS <a href="../../get_started/vocabulary/">Concepts</a> section.
+<li>Read the Mynewt OS <a href="../../get_started/vocabulary/">Concepts</a> section. </li>
+<li>Create a project space (directory structure) and populate it with the core code repository (apache-mynewt-core) or know how to as explained in <a href="../../../os/get_started/project_create">Creating Your First Project</a>.
<br></li>
</ul>
<h3 id="overview-of-steps">Overview of Steps</h3>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/latest/os/tutorials/blinky_console/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/blinky_console/index.html b/latest/os/tutorials/blinky_console/index.html
index 0c1e4ed..f8067ad 100644
--- a/latest/os/tutorials/blinky_console/index.html
+++ b/latest/os/tutorials/blinky_console/index.html
@@ -265,17 +265,6 @@
-
-
- <li ><a href="../STM32F303/">Blinky on STM32F303</a>
-
-
- </li>
-
-
-
-
-
<li >
<a href="../nRF52/">Blinky on nRF52</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/latest/os/tutorials/blinky_primo/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/blinky_primo/index.html b/latest/os/tutorials/blinky_primo/index.html
index 39bfa5d..bd384e6 100644
--- a/latest/os/tutorials/blinky_primo/index.html
+++ b/latest/os/tutorials/blinky_primo/index.html
@@ -265,17 +265,6 @@
-
-
- <li ><a href="../STM32F303/">Blinky on STM32F303</a>
-
-
- </li>
-
-
-
-
-
<li >
<a href="../nRF52/">Blinky on nRF52</a>
</li>
@@ -544,7 +533,7 @@
<ul>
<li>Meet the the prerequisites listed in <a href="../blinky/">Project Blinky</a>.</li>
<li>Have an Arduino Primo board.</li>
-<li>Install a debugger choose one of the two options below: Option 1 requires additional hardware but very easy to set up. </li>
+<li>Install a debugger. Choose one of the two options below: Option 1 requires additional hardware but very easy to set up. </li>
</ul>
<p><br></p>
<h5 id="option-1">Option 1</h5>
@@ -554,20 +543,7 @@
<li>Install the <a href="https://www.segger.com/jlink-software.html">Segger JLINK Software and documentation pack</a>. </li>
</ul>
<h5 id="option-2">Option 2</h5>
-<p>No additional hardware is required but a version of OpenOCD 0.10.0 that is currently in development needs to be installed. A patch for the nRF52 has been applied to the OpenOCD code in development and a tarball has been made available for download <a href="../downloads/openocd-wnrf52.tgz">here</a>. Untar it. From the top of the directory tree ("openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4"), build it using the following configuration:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$./configure --enable-cmsis-dap --enable-openjtag_ftdi --enable-jlink --enable-stlink
-</pre></div>
-
-
-<p>Then run <code>make</code> and <code>sudo make install</code>. This step takes minutes, so be patient.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ openocd -v
-Open On-Chip Debugger 0.10.0-dev-snapshot (2016-05-20-10:43)
-Licensed under GNU GPL v2
-For bug reports, read
- http://openocd.org/doc/doxygen/bugs.html
-</pre></div>
-
-
+<p>This board requires a patch version of OpenOCD 0.10.0 that is in development. See <a href="../../get_started/cross_tools/">Install OpenOCD</a> instructions to install it if you do not have this version installed.</p>
<p>You can now use openocd to upload to Arduino Primo board via the USB port itself.</p>
<h3 id="create-a-project">Create a Project</h3>
<p>Create a new project if you do not have an existing one. You can skip this step and proceed to <a href="#create_targets">create the targets</a> if you already created a project.</p>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/latest/os/tutorials/nRF52/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/nRF52/index.html b/latest/os/tutorials/nRF52/index.html
index 723cfb1..43b4566 100644
--- a/latest/os/tutorials/nRF52/index.html
+++ b/latest/os/tutorials/nRF52/index.html
@@ -265,17 +265,6 @@
-
-
- <li ><a href="../STM32F303/">Blinky on STM32F303</a>
-
-
- </li>
-
-
-
-
-
<li class="active">
<a href="./">Blinky on nRF52</a>
</li>
@@ -549,6 +538,7 @@
<li>Eval Kit from Rigado - BMD-300-EVAL-ES</li>
</ul>
</li>
+<li>Install the <a href="https://www.segger.com/jlink-software.html">Segger JLINK Software and documentation pack</a>.</li>
</ul>
<p>This tutorial uses the Nordic nRF52-DK board.</p>
<h3 id="create-a-project">Create a Project</h3>
@@ -716,9 +706,9 @@ $
<ul class="nav nav-pills" style="margin-bottom: 10px">
<li>
- <a href=../pin-wheel-mods/>
+ <a href=../olimex/>
<span class="fa fa-arrow-left"></span>
- Previous: Pinwheel Blinky
+ Previous: Blinky on Olimex
</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/latest/os/tutorials/nrf52_adc/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/nrf52_adc/index.html b/latest/os/tutorials/nrf52_adc/index.html
index 74c90c3..b2c8ef1 100644
--- a/latest/os/tutorials/nrf52_adc/index.html
+++ b/latest/os/tutorials/nrf52_adc/index.html
@@ -526,7 +526,7 @@ project.repositories:
#
repository.apache-mynewt-core:
type: github
- vers: 1-dev
+ vers: 1-latest
user: apache
repo: incubator-mynewt-core
<span style="background-color: #ffffcc">repository.mynewt_nordic:
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/latest/os/tutorials/olimex/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/olimex/index.html b/latest/os/tutorials/olimex/index.html
index 19f17c7..e769619 100644
--- a/latest/os/tutorials/olimex/index.html
+++ b/latest/os/tutorials/olimex/index.html
@@ -265,17 +265,6 @@
-
-
- <li ><a href="../STM32F303/">Blinky on STM32F303</a>
-
-
- </li>
-
-
-
-
-
<li >
<a href="../nRF52/">Blinky on nRF52</a>
</li>
@@ -544,9 +533,10 @@
<li>Meet the prerequisites listed in <a href="../blinky/">Project Blinky</a>.</li>
<li>Have a STM32-E407 development board from Olimex. </li>
<li>Have a ARM-USB-TINY-H connector with JTAG interface for debugging ARM microcontrollers (comes with the ribbon cable to hook up to the board)</li>
-<li>Have a USB A-B type cable to connect the debugger to your computer.
-<br></li>
+<li>Have a USB A-B type cable to connect the debugger to your computer.</li>
+<li>Install the <a href="../../../os/get_started/cross_tools/">OpenOCD debugger</a>.</li>
</ul>
+<p><br></p>
<h3 id="create-a-project">Create a Project</h3>
<p>Create a new project if you do not have an existing one. You can skip this step and proceed to <a href="#create_targets">create the targets</a> if you already created a project.</p>
<p>Run the following commands to create a new project:</p>
@@ -747,8 +737,8 @@ Let's double check that it is indeed booting from flash and making the LED blink
</li>
<li class="pull-right">
- <a href=../STM32F303/>
- Next: Blinky on STM32F303
+ <a href=../nRF52/>
+ Next: Blinky on nRF52
<span class="fa fa-arrow-right"></span>
</a>
[4/7] incubator-mynewt-site git commit: Updates to installation on
Linux and Mac, removal of references to develop branch on website
Posted by ad...@apache.org.
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/develop/os/tutorials/pin-wheel-mods/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/pin-wheel-mods/index.html b/develop/os/tutorials/pin-wheel-mods/index.html
deleted file mode 100644
index 27a3ac2..0000000
--- a/develop/os/tutorials/pin-wheel-mods/index.html
+++ /dev/null
@@ -1,681 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
- <head>
- <meta charset="utf-8">
- <meta http-equiv="X-UA-Compatible" content="IE=edge">
- <meta name="viewport" content="width=device-width, initial-scale=1.0">
-
-
- <!-- This is broken by doc revisioning.
- <link rel="canonical" href="http://mynewt.apache.org/os/tutorials/pin-wheel-mods/"> -->
- <link rel="shortcut icon" href="../../../img/favicon.ico">
-
- <title>Pinwheel Blinky - Apache Mynewt</title>
-
- <link href="../../../css/bootstrap-3.0.3.min.css" rel="stylesheet">
- <link rel="stylesheet" href="../../../css/highlight.css">
- <link href="../../../css/base.css" rel="stylesheet">
- <link href="../../../css/custom.css" rel="stylesheet">
- <link href="../../../css/v2.css" rel="stylesheet">
- <link href="https://fonts.googleapis.com/css?family=Lato" rel="stylesheet">
- <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/font-awesome/4.5.0/css/font-awesome.min.css">
- <link href="../../../extra.css" rel="stylesheet">
-
- <!-- HTML5 shim and Respond.js IE8 support of HTML5 elements and media queries -->
- <!--[if lt IE 9]>
- <script src="https://oss.maxcdn.com/libs/html5shiv/3.7.0/html5shiv.js"></script>
- <script src="https://oss.maxcdn.com/libs/respond.js/1.3.0/respond.min.js"></script>
- <![endif]-->
-
-
- <script>
- (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
- (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
- m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
- })(window,document,'script','//www.google-analytics.com/analytics.js','ga');
-
- ga('create', 'UA-72162311-1', 'auto');
- ga('send', 'pageview');
- </script>
-
- </head>
-
-
- <body class="Pinwheel Blinky">
-
-
- <div class="container">
- <div class="row v2-main-banner">
- <a class="logo-cell" href="/">
- <img class="logo" src="/img/logo.png">
- </a>
- <div class="tagline-cell">
- <h4 class="tagline">An OS to build, deploy and securely manage billions of devices</h4>
- </div>
- <div class="news-cell">
- <div class="well">
- <h4>Latest News:</h4> <a href="/download">Apache Mynewt 1.0.0</a> released (March 22, 2017)
- </div>
- </div>
- </div>
-</div>
-
-
-
-
-
-
-
-
-<nav id="navbar" class="navbar navbar-inverse affix-top" data-spy="affix" data-offset-top="150" role="navigation">
- <div class="container">
- <!-- Collapsed navigation -->
- <div class="navbar-header">
- <!-- Expander button -->
- <button type="button" class="navbar-toggle" data-toggle="collapse" data-target=".navbar-collapse">
- <span class="sr-only">Toggle navigation</span>
- <span class="icon-bar"></span>
- <span class="icon-bar"></span>
- <span class="icon-bar"></span>
- </button>
-
- </div>
-
- <!-- Expanded navigation -->
- <div class="navbar-collapse collapse">
- <!-- Main navigation -->
- <ul class="nav navbar-nav navbar-right">
- <li
- class=""
->
- <a href="/"><i class="fa fa-home" style="font-size: larger;"></i></a>
- </li>
- <li
- class="important"
->
- <a href="/quick-start/">Quick Start</a>
- </li>
- <li
- class=""
->
- <a href="/about/">About</a>
- </li>
- <li
- class=""
->
- <a href="/talks/">Talks</a>
- </li>
- <li
- class="active"
->
- <a href="/latest/os/introduction">Documentation</a>
- </li>
- <li
- class=""
->
- <a href="/download/">Download</a>
- </li>
- <li
- class=""
->
- <a href="/community/">Community</a>
- </li>
- <li
- class=""
->
- <a href="/events/">Events</a>
- </li>
- </ul>
-
- <!-- Search, Navigation and Repo links -->
- <ul class="nav navbar-nav navbar-right">
-
- </ul>
- </div>
- </div>
-</nav>
-
-
-
- <div class="container">
-
- <div class="row">
- <div class="col-md-3 v2-sidebar sidebar-container"><div id="docSidebar" class="hidden-print" role="complementary">
- <div class="top">
- <div role="search">
- <form id="rtd-search-form" class="wy-form" action="../../../search.html" method="get">
- <div class="form-group">
- <input type="text" name="q" class="form-control" placeholder="Search documentation" />
- </div>
- </form>
- </div>
- </div>
- <ul class="toc-nav">
- <li class="doc-version">
-<select class="form-control" onchange="if (this.value) window.location.href=this.value">
-
- <option
- value="/develop/os/introduction"
- selected="selected"
- >
- Version: develop (latest)
- </option>
-
- <option
- value="/v0_9_0/os/introduction"
-
- >
- Version: 0.9.0
- </option>
-
-</select>
-</li>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- <li ><a href="../../introduction/">Mynewt Documentation</a>
-
-
- <ul>
-
-
-
-
-
-
-
- <li ><a href="../../get_started/get_started/">Basic Setup</a>
-
-
- </li>
-
-
-
-
-
- <li >
- <a href="../../get_started/vocabulary/">Concepts</a>
- </li>
-
-
-
-
-
-
-
- <li ><a href="../tutorials/">Tutorials</a>
-
-
- <ul>
-
-
-
-
-
-
-
- <li ><a href="../blinky/">Project Blinky</a>
-
-
- <ul>
-
-
-
-
-
- <li >
- <a href="../arduino_zero/">Blinky on Arduino Zero</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../blinky_primo/">Blinky on Arduino Primo</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../olimex/">Blinky on Olimex</a>
- </li>
-
-
-
-
-
-
-
- <li ><a href="../STM32F303/">Blinky on STM32F303</a>
-
-
- <ul>
-
-
-
-
-
- <li class="active">
- <a href="./">Pinwheel Blinky</a>
- </li>
-
-
-
- </ul>
-
- </li>
-
-
-
-
-
- <li >
- <a href="../nRF52/">Blinky on nRF52</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../rbnano2/">Blinky on RedBear Nano 2</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../blinky_console/">Add Console and Shell to Blinky</a>
- </li>
-
-
-
- </ul>
-
- </li>
-
-
-
-
-
-
-
- <li ><a href="../repo/add_repos/">Work with repositories</a>
-
-
- </li>
-
-
-
-
-
-
-
- <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
-
-
- </li>
-
-
-
-
-
- <li >
- <a href="../ibeacon/">BLE iBeacon</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../eddystone/">BLE Eddystone</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../add_shell/">Enable the OS Shell and Console</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../tasks_lesson/">Tasks and Priority Management</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../unit_test/">Write a Test Suite for a Package</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../event_queue/">Events and Event Queues</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../bletiny_project/">BLE app to check stats via console</a>
- </li>
-
-
-
-
-
-
-
- <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
- </li>
-
-
-
-
-
- <li >
- <a href="../blehci_project/">BLE HCI interface</a>
- </li>
-
-
-
-
-
-
-
- <li><a href="
- ../air_quality_sensor/
-">Air-quality Sensor project</a>
-
-
- </li>
-
-
-
-
-
- <li >
- <a href="../nrf52_adc/">Add an Analog Sensor</a>
- </li>
-
-
-
- </ul>
-
- </li>
-
-
-
-
-
-
-
- <li ><a href="../../os_user_guide/">OS User Guide</a>
-
-
- </li>
-
-
-
-
-
-
-
- <li><a href="
- ../../../network/ble/ble_intro/
-">BLE User Guide</a>
-
-
- </li>
-
-
-
-
-
-
-
- <li ><a href="../../../newt/newt_intro/">Newt Tool Guide</a>
-
-
- </li>
-
-
-
-
-
-
-
- <li ><a href="../../../newtmgr/overview/">Newt Manager Guide</a>
-
-
- </li>
-
-
-
- </ul>
-
- </li>
-
-
-
-
-
-
-
- <li><a href="
- ../../../faq/go_env/
-">Appendix</a>
-
-
- </li>
-
-
-
- </ul>
-</div></div>
-
- <div class="col-md-9" role="main">
- <div class="doc-header">
- <div role="navigation" aria-label="breadcrumbs navigation">
- <ul class="wy-breadcrumbs pull-right">
- <li><a href="/develop/os/introduction">Docs</a></li>
-
-
-
- <li>» <a href="../blinky/">Project Blinky</a></li>
-
-
-
- <li>» <a href="../STM32F303/">Blinky on STM32F303</a></li>
-
-
-
- <li>» Pinwheel Blinky</li>
-
-
-
- </ul>
-</div>
- </div>
-
- <h2 id="pin-wheel-modifications-to-blinky-on-stm32f3-discovery">Pin Wheel Modifications to "Blinky" on STM32F3 Discovery</h2>
-<p><br></p>
-<h3 id="objective">Objective</h3>
-<p>Learn how to modify an existing app -- the <a href="../STM32F303/">blinky</a> app -- to light all the LEDs on the STM32F3 Discovery board. </p>
-<p><br></p>
-<h3 id="what-you-need">What you need</h3>
-<ul>
-<li>Discovery kit with STM32F303VC MCU</li>
-<li>Laptop running Mac OSX. </li>
-<li>It is assumed you have already installed and run the <a href="../STM32F303/">blinky</a> app succesfully.</li>
-</ul>
-<p><br></p>
-<p>Since you've already successfully created your blinky app project, you'll need to modify only one file, main.c, in order to get this app working.</p>
-<p><br></p>
-<p>The main.c file resides in the apps/blinky/src directory in your project folder so you can edit it with your favorite editor. You'll make the following changes:</p>
-<p><br></p>
-<p>Replace the line:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span style="color: #A90D91">int</span> <span style="color: #000000">g_led_pin</span>;
-</pre></div>
-
-
-<p>With the line:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span style="color: #A90D91">int</span> <span style="color: #000000">g_led_pins</span>[<span style="color: #1C01CE">8</span>] <span style="color: #000000">=</span> {<span style="color: #000000">LED_BLINK_PIN_1</span>, <span style="color: #000000">LED_BLINK_PIN_2</span>, <span style="color: #000000">LED_BLINK_PIN_3</span>, <span style="color: #000000">LED_BLINK_PIN_4</span>, <span style="color: #000000">LED_BLINK_PIN_5</span>, <span style="color: #000000">LED_BLINK_PIN_6</span>, <span style="color: #000000">LED_BLINK_PIN_7</span>, <span style="color: #000000">LED_BLINK_PIN_8</span>};
-</pre></div>
-
-
-<p>So that you now have an array of all 8 LED Pins on the board.</p>
-<p>Delete the line:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span style="color: #000000">g_led_pin</span> <span style="color: #000000">=</span> <span style="color: #000000">LED_BLINK_PIN</span>;
-</pre></div>
-
-
-<p>And in its place, add the following lines to initialize all the LED_PINS correctly:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span style="color: #A90D91">int</span> <span style="color: #000000">x</span>;
-<span style="color: #A90D91">for</span>(<span style="color: #000000">x</span> <span style="color: #000000">=</span> <span style="color: #1C01CE">0</span>; <span style="color: #000000">x</span> <span style="color: #000000"><</span> <span style="color: #1C01CE">8</span>; <span style="color: #000000">x++</span>){
- <span style="color: #000000">hal_gpio_init_out</span>(<span style="color: #000000">g_led_pins</span>[<span style="color: #000000">x</span>], <span style="color: #1C01CE">1</span>);
-}
-<span style="color: #A90D91">int</span> <span style="color: #000000">p</span> <span style="color: #000000">=</span> <span style="color: #1C01CE">0</span>;
-</pre></div>
-
-
-<p>We'll use that 'p' later. Next you'll want to change the line:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span style="color: #000000">os_time_delay</span>(<span style="color: #1C01CE">1000</span>);
-</pre></div>
-
-
-<p>to a shorter time in order to make it a little more interesting. A full 1 second delay doesn't look great, so try 100 for starters and then you can adjust it to your liking.</p>
-<p>Finally, change the line:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span style="color: #000000">hal_gpio_toggle</span>(<span style="color: #000000">g_led_pin</span>);
-</pre></div>
-
-
-<p>to look like this:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span style="color: #000000">hal_gpio_toggle</span>(<span style="color: #000000">g_led_pins</span>[<span style="color: #000000">p++</span>]);
-<span style="color: #000000">p</span> <span style="color: #000000">=</span> (<span style="color: #000000">p</span> <span style="color: #000000">></span> <span style="color: #1C01CE">7</span>) <span style="color: #000000">?</span> <span style="color: #1C01CE">0</span> <span style="color: #000000">:</span> <span style="color: #000000">p</span>;
-</pre></div>
-
-
-<p><br></p>
-<h3 id="build-the-target-and-executables-and-download-the-images">Build the target and executables and download the images</h3>
-<p>Run the same commands you used on the blinky app to build and load this one:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt create-image stmf3_blinky 1.2.3
-App image successfully generated: ~/dev/myproj/bin/stmf3_blinky/apps/blinky/blinky.img
-Build manifest:~/dev/myproj/bin/stmf3_blinky/apps/blinky/manifest.json
-$ newt -v load stmf3_boot
-$ newt -v load stmf3_blinky
-</pre></div>
-
-
-<p><br></p>
-<h3 id="watch-the-leds-go-round-and-round">Watch the LEDs go round and round</h3>
-<p>The colored LEDs should now all light up in succession, and once they're all lit, they should then go off in the same order. This should repeat continuously.</p>
-<p>If you see anything missing or want to send us feedback, please do so by signing up for appropriate mailing lists on our <a href="../../../community/">Community Page</a>.</p>
-<p>Keep on hacking and blinking!</p>
-
- <div class="row">
-
-
-
-
-<ul class="nav nav-pills" style="margin-bottom: 10px">
- <li>
-
- <a href=../STM32F303/>
- <span class="fa fa-arrow-left"></span>
- Previous: Blinky on STM32F303
- </a>
-
- </li>
- <li class="pull-right">
-
- <a href=../nRF52/>
- Next: Blinky on nRF52
- <span class="fa fa-arrow-right"></span>
- </a>
-
- </li>
-</ul>
- </div>
- <footer class="row">
- <div class="col-xs-12">
-
- <p class="copyright">Apache Mynewt (incubating) is available under Apache License, version 2.0.</p>
-
- </div>
- <div class="col-xs-12">
- <div class="logos">
- <img src="/img/asf_logo_wide_small.png" alt="Apache" title="Apache">
- <small class="footnote">
- MyNewt is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.
- </small>
- <img src="/img/egg-logo2.png" alt="Apache Incubator" title="Apache Incubator">
- </div>
- </div>
-</footer>
- </div>
- </div>
-
-
- </div>
-
- <script src="../../../js/jquery-1.10.2.min.js"></script>
- <script src="../../../js/bootstrap-3.0.3.min.js"></script>
- <script src="../../../js/highlight.pack.js"></script>
- <script src="../../../js/base.js"></script>
- <script src="../../../js/custom.js"></script>
-
- </body>
-</html>
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/develop/os/tutorials/project-nrf52-slinky/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/project-nrf52-slinky/index.html b/develop/os/tutorials/project-nrf52-slinky/index.html
index 27c9665..45e39f2 100644
--- a/develop/os/tutorials/project-nrf52-slinky/index.html
+++ b/develop/os/tutorials/project-nrf52-slinky/index.html
@@ -507,6 +507,7 @@
<ul>
<li>Meet the prerequisites listed in <a href="../project-slinky/">Project Slinky</a>. </li>
<li>Have a Nordic nRF52-DK board. </li>
+<li>Install the <a href="https://www.segger.com/jlink-software.html">Segger JLINK Software and documentation pack</a>.</li>
</ul>
<h3 id="create-a-new-project">Create a New Project</h3>
<p>Create a new project if you do not have an existing one. You can skip this step and proceed to <a href="#create_targets">create the targets</a> if you already have a project created or completed the <a href="../project-slinky/">Sim Slinky</a> tutorial. </p>
@@ -652,7 +653,7 @@ $
<p><br></p>
<h3 id="use-newtmgr-to-query-the-board">Use Newtmgr to Query the Board</h3>
-<p>Run some newtmgr commands to query and receive responses back from the board (See the <a href="../newtmgr/overview">Newt Manager Guide</a> for more information on the newtmgr commands). </p>
+<p>Run some newtmgr commands to query and receive responses back from the board (See the <a href="../../../newtmgr/overview">Newt Manager Guide</a> for more information on the newtmgr commands). </p>
<p>Run the <code>newtmgr echo hello -c nrf52serial</code> command. This is the simplest command that requests the board to echo back the text. </p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newtmgr echo hello -c nrf52serial
hello
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/develop/os/tutorials/project-stm32-slinky/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/project-stm32-slinky/index.html b/develop/os/tutorials/project-stm32-slinky/index.html
index d2fb5be..08d5e4d 100644
--- a/develop/os/tutorials/project-stm32-slinky/index.html
+++ b/develop/os/tutorials/project-stm32-slinky/index.html
@@ -511,6 +511,7 @@
<li>Have a ARM-USB-TINY-H connector with JTAG interface for debugging ARM microcontrollers (comes with the ribbon cable to hook up to the board)</li>
<li>Have a USB A-B type cable to connect the debugger to your computer. </li>
<li>Have a USB to TTL Serial Cable with female wiring harness.</li>
+<li>Install the <a href="../../../os/get_started/cross_tools/">OpenOCD debugger</a>.</li>
</ul>
<h3 id="create-a-new-project">Create a New Project</h3>
<p>Create a new project if you do not have an existing one. You can skip this step and proceed to <a href="#create_targets">create the targets</a> if you already have a project created or completed the <a href="../project-slinky/">Sim Slinky</a> tutorial.</p>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/develop/os/tutorials/rbnano2/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/rbnano2/index.html b/develop/os/tutorials/rbnano2/index.html
index b6298bd..af1959e 100644
--- a/develop/os/tutorials/rbnano2/index.html
+++ b/develop/os/tutorials/rbnano2/index.html
@@ -265,17 +265,6 @@
-
-
- <li ><a href="../STM32F303/">Blinky on STM32F303</a>
-
-
- </li>
-
-
-
-
-
<li >
<a href="../nRF52/">Blinky on nRF52</a>
</li>
@@ -543,8 +532,8 @@
<ul>
<li>Meet the prerequisites listed in <a href="../blinky/">Project Blinky</a>.</li>
<li>Have a RedBear Nano 2 board. </li>
+<li>Install a patched version of OpenOCD 0.10.0 described in <a href="../os/get_started/cross_tools/">Install OpenOCD</a>.</li>
</ul>
-<p><strong>Note:</strong> You must install a patched version of OpenOCD .10.0 (See <a href="../../../os/tutorials/blinky_primo">Debugger Option 2 in the Arduino Primo Blinky Tutorial</a>).</p>
<h3 id="create-a-project">Create a Project</h3>
<p>Create a new project if you do not have an existing one. You can skip this step and proceed to <a href="#create_targets">create the targets</a> if you already have a project created. </p>
<p>Run the following commands to create a new project:</p>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/develop/os/tutorials/tutorials/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/tutorials/index.html b/develop/os/tutorials/tutorials/index.html
index cf90b0b..8db3d34 100644
--- a/develop/os/tutorials/tutorials/index.html
+++ b/develop/os/tutorials/tutorials/index.html
@@ -478,7 +478,6 @@
<li>You have installed Docker container of Newt tool and toolchains or you have installed them natively on your machine</li>
<li>You have created a new project space (directory structure) and populated it with the core code repository (apache-mynewt-core) or know how to as explained in <a href="../../get_started/project_create">Creating Your First Project</a>.</li>
<li>You have at least one of the supported development boards:<ul>
-<li><a href="../STM32F303/">STM32F3 discovery kit from ST Micro</a></li>
<li><a href="../arduino_zero/">Arduino Zero hardware</a></li>
<li><a href="../olimex/">Olimex/STM32F407ZGT6 Cortex-M4 hardware</a></li>
<li><a href="../nRF52/">nRF52 Development Kit from Nordic Semiconductor</a></li>
@@ -495,15 +494,8 @@
<ul>
<li><a href="../arduino_zero/">Blinky on Arduino Zero hardware</a></li>
<li><a href="../olimex/">Blinky on Olimex/STM32F407ZGT6 Cortex-M4 hardware</a></li>
-<li><a href="../STM32F303/">Blinky on STM32F3 discovery kit from ST Micro</a></li>
<li><a href="../nRF52/">Blinky on nRF52 Development Kit from Nordic Semiconductor</a> <strong>Note:</strong> This supports BLE.</li>
-</ul>
-<p><br></p>
-</li>
-<li>
-<p>Tweaking available apps to customize behavior e.g. making a more exciting LED blink pattern</p>
-<ul>
-<li><a href="../pin-wheel-mods/">Pinwheel Blinky on STM32F3 discovery board</a></li>
+<li><a href="../rbnano2/">Blinky on Redbear Nano2</a></li>
</ul>
<p><br></p>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/develop/sitemap.xml
----------------------------------------------------------------------
diff --git a/develop/sitemap.xml b/develop/sitemap.xml
index c476bb9..b635405 100644
--- a/develop/sitemap.xml
+++ b/develop/sitemap.xml
@@ -4,7 +4,7 @@
<url>
<loc>http://mynewt.apache.org/</loc>
- <lastmod>2017-04-24</lastmod>
+ <lastmod>2017-04-25</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -13,7 +13,7 @@
<url>
<loc>http://mynewt.apache.org/pages/ble/</loc>
- <lastmod>2017-04-24</lastmod>
+ <lastmod>2017-04-25</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -22,7 +22,7 @@
<url>
<loc>http://mynewt.apache.org/quick-start/</loc>
- <lastmod>2017-04-24</lastmod>
+ <lastmod>2017-04-25</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -30,7 +30,7 @@
<url>
<loc>http://mynewt.apache.org/about/</loc>
- <lastmod>2017-04-24</lastmod>
+ <lastmod>2017-04-25</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -38,7 +38,7 @@
<url>
<loc>http://mynewt.apache.org/talks/</loc>
- <lastmod>2017-04-24</lastmod>
+ <lastmod>2017-04-25</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -46,7 +46,7 @@
<url>
<loc>http://mynewt.apache.org/download/</loc>
- <lastmod>2017-04-24</lastmod>
+ <lastmod>2017-04-25</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -54,7 +54,7 @@
<url>
<loc>http://mynewt.apache.org/community/</loc>
- <lastmod>2017-04-24</lastmod>
+ <lastmod>2017-04-25</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -62,7 +62,7 @@
<url>
<loc>http://mynewt.apache.org/events/</loc>
- <lastmod>2017-04-24</lastmod>
+ <lastmod>2017-04-25</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -71,7 +71,7 @@
<url>
<loc>http://mynewt.apache.org/os/introduction/</loc>
- <lastmod>2017-04-24</lastmod>
+ <lastmod>2017-04-25</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -83,7 +83,7 @@
<url>
<loc>http://mynewt.apache.org/os/get_started/vocabulary/</loc>
- <lastmod>2017-04-24</lastmod>
+ <lastmod>2017-04-25</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -123,19 +123,19 @@
<url>
<loc>http://mynewt.apache.org/faq/go_env/</loc>
- <lastmod>2017-04-24</lastmod>
+ <lastmod>2017-04-25</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/how_to_edit_docs/</loc>
- <lastmod>2017-04-24</lastmod>
+ <lastmod>2017-04-25</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/answers/</loc>
- <lastmod>2017-04-24</lastmod>
+ <lastmod>2017-04-25</lastmod>
<changefreq>daily</changefreq>
</url>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/download/index.html
----------------------------------------------------------------------
diff --git a/download/index.html b/download/index.html
index 2a69e28..4f3e0a4 100644
--- a/download/index.html
+++ b/download/index.html
@@ -160,22 +160,14 @@
<h3 id="code-in-development">Code in development</h3>
<p>While the use of one of the official releases listed above is generally recommended, you may be interested in seeing work in progress.</p>
-<p>The most recent code resides in the <code>develop</code> branch of the Mynewt git repository. You may view or fork the repositories for Mynewt OS and Newt Tool from the Apache mirror on github.com.</p>
+<p>The most recent code that is fairly stable over the full OS resides in the <code>master</code> branch of the Mynewt git repository. You may view or fork the repositories for Mynewt OS and Newt Tool from the Apache mirror on github.com.</p>
<ul>
-<li><a href="https://github.com/apache/incubator-mynewt-core/tree/develop">Apache Mynewt OS mirror on github.com</a></li>
-<li><a href="https://github.com/apache/incubator-mynewt-newt/tree/develop">Apache Newt Tool mirror on github.com</a></li>
+<li><a href="https://github.com/apache/incubator-mynewt-core/tree/master">Apache Mynewt OS mirror on github.com</a></li>
+<li><a href="https://github.com/apache/incubator-mynewt-newt/tree/master">Apache Newt Tool mirror on github.com</a></li>
</ul>
-<p>Alternatively, you can clone the desired branch using git:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ git clone git://github.com/apache/incubator-mynewt-core.git -b develop
-$ git clone git://github.com/apache/incubator-mynewt-newt.git -b develop
-</pre></div>
-
-
-<p><br></p>
-<p>A relatively stable version of code in progress can be found in the <code>master</code> branch of the Mynewt git repository.
-You may access the code for Mynewt OS and Newt Tool from the 'master` branch of the Apache mirror on github.com or clone it using git:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ git clone git://github.com/apache/incubator-mynewt-core.git
-$ git clone git://github.com/apache/incubator-mynewt-newt.git
+<p>The most recent code to support a major feature (e.g. Bluetooth 5) can be found in a long-lived feature branch dedicated to that feature (bluetooth5, in the example for Bluetooth 5) and not the master. If you are interested in seeing the latest code for that feature, you can clone the desired branch using git:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ git clone git://github.com/apache/incubator-mynewt-core.git -b <feature-branch-name>
+$ git clone git://github.com/apache/incubator-mynewt-newt.git -b <feature-branch-name>
</pre></div>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/latest/faq/go_env/index.html
----------------------------------------------------------------------
diff --git a/latest/faq/go_env/index.html b/latest/faq/go_env/index.html
index 17b0d97..36d3bd2 100644
--- a/latest/faq/go_env/index.html
+++ b/latest/faq/go_env/index.html
@@ -262,22 +262,23 @@
</div>
</div>
- <h2 id="contributing-to-newt-and-newtmgr-tools">Contributing to Newt and Newtmgr Tools</h2>
-<p>Newt and Newtmgr are written in Go (golang). This guide shows you how to install Go and setup your environment if
-you would like to contribute to the newt or newtmgr tools.</p>
+ <h2 id="contributing-to-newt-or-newtmgr-tools">Contributing to Newt or Newtmgr Tools</h2>
+<p>Newt and Newtmgr are written in Go (golang). This guide shows you how to install Go and setup your environment to update and build the tools if you want to: </p>
+<ul>
+<li>Contribute to newt or newtmgr features or fix bugs.</li>
+<li>Build the tools with latest updates from the master branch on a Linux platform.</li>
+</ul>
<p>This guide shows you how to perform the following:</p>
<ol>
-<li>Install Go on either Mac OS or Linux.</li>
+<li>Install Go on either Mac OS X or Linux. (Tasks that are specific to each platform are called out.)</li>
<li>Setup the Go environment.</li>
-<li>Download the newt and newtmgr source code.</li>
-<li>Build the newt and newtmgr tools.</li>
+<li>Download the source, build, and install the newt or newtmgr tools.</li>
<li>Update and rebuild the tools. </li>
</ol>
-<p>Steps 2-5 apply to both Mac OS and Linux platforms.</p>
-<p><strong>Note:</strong> You will also need to read and follow the instructions from <a href="../../faq/answers/">FAQ</a> to set up your git repos to submit changes.</p>
+<p><strong>Note:</strong> You will also need to read and follow the instructions from the <a href="../../faq/answers/">FAQ</a> to set up your git repos to submit changes.</p>
<h3 id="step-1-installing-go">Step 1: Installing Go</h3>
-<p>The latest master branch of newt and newtmgr requires GO version 1.6 or higher.
-<br></p>
+<p>The latest master branch of newt and newtmgr requires GO version 1.6 or higher. You can skip this step and proceed to Step 2 if you already have Go version 1.6 or higher installed.</p>
+<p><br></p>
<h4 id="installing-go-on-mac-os-x">Installing Go on Mac OS X</h4>
<p>If you do not have Homebrew installed, run the following command. You will be prompted for your sudo password.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
@@ -325,13 +326,14 @@ go version go1.6.3 linux/amd64
<p><br></p>
<h3 id="step-2-setting-up-your-go-environment">Step 2: Setting Up Your Go Environment</h3>
-<p>Go provides an environment to compile Go code, construct Go packages, and import Go code. You will use Go commands to import the <strong>newt</strong> repository into your local Go environment. The Go language environment dictates a specific directory structure, or workspace in Go parlance. It must contain three sibling directories with the names <strong>src</strong>, <strong>pkg</strong> and <strong>bin</strong>: </p>
+<p>This section describes the Go environment and how to setup a Go workspace. If you already have a Go workspace for your other Go projects, you can skip this step and proceed to Step 3.</p>
+<p>Go provides an environment to compile Go code, construct Go packages, and import Go code. You will use Go commands to import the newt or newtmgr package repository into your local Go environment. The Go language environment dictates a specific directory structure, or workspace in Go parlance. It must contain three sibling directories with the names <strong>src</strong>, <strong>pkg</strong> and <strong>bin</strong>: </p>
<ul>
<li>src contains Go source files organized into packages (one package per directory)</li>
<li>pkg contains package objects</li>
-<li>bin contains executable commands.</li>
+<li>bin contains the Go application executables that Go builds and installs.</li>
</ul>
-<p>The <strong>GOPATH</strong> environment variable specifies the location of your workspace. To setup this workspace environment, create a <strong>dev</strong> directory and then a <strong>go</strong> directory under it. Set the GOPATH environment variable to this directory where you will clone the newt repository.</p>
+<p>The <strong>GOPATH</strong> environment variable specifies the location of your workspace. To setup this workspace environment, create a <strong>dev</strong> directory and then a <strong>go</strong> directory under it. Set the GOPATH environment variable to this directory where you will clone the newt and newtmgr repositories.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ cd $HOME
$ mkdir -p dev/go
$ cd dev/go
@@ -340,57 +342,113 @@ $ export GOPATH=`pwd`
<p><br>
-Add the export GOPATH statement to the ~/.bash_profile file and source the file:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ vi ~/.bash_profile
-$ source ~/.bash_profile
+Add the following export statements to your ~/.bash_profile file and source the file:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">export GOPATH=$HOME/dev/go
+export PATH=$GOPATH/bin:$PATH
</pre></div>
<p><br></p>
-<h3 id="step-3-downloading-the-source">Step 3: Downloading the Source</h3>
-<p>Use Go commands to retrieve the latest source from the newt repository (currently the ASF incubator directory). Check that the directories are installed.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ go get mynewt.apache.org/newt/...
-$ ls $GOPATH/src/mynewt.apache.org/newt
-DISCLAIMER NOTICE newt newtvm viper
-LICENSE README.md newtmgr util yaml
+<h3 id="step-3-downloading-the-source-and-installing-the-tools">Step 3: Downloading the Source and Installing the Tools</h3>
+<p>Newt and newtmgr are individual Go packages and have their own git repositories. You can download the source and install one or both tools.</p>
+<p>We use the <code>go get</code> command to download the source, build, and install the binary in the <strong>$GOPATH/bin</strong> directory. </p>
+<p><br></p>
+<h4 id="downloading-and-installing-the-newt-tool">Downloading and Installing the Newt Tool</h4>
+<p>The newt Go package is <strong>mynewt.apache.org/newt/newt</strong> and is stored in the <a href="https://github.com/apache/incubator-mynewt-newt">Apache Mynewt newt tool repository mirrored on github</a>. </p>
+<p>Download the newt package source and install the tool:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$cd $GOPATH
+$go get mynewt.apache.org/newt/newt
+$cd $GOPATH/src/mynewt.apache.org/newt
+$ls
+DISCLAIMER RELEASE_NOTES.md util
+INSTALLING.md build.sh viper
+LICENSE newt yaml
+NOTICE newtmgr
+README.md newtvm
+$git status
+On branch master
+Your branch is up-to-date with 'origin/master'.
+
+nothing to commit, working directory clean
+</pre></div>
+
+
+<p><br>
+<strong>Note:</strong> The source code under the <strong>newtmgr</strong> directory is no longer used or updated. The current <strong>newtmgr</strong> source has its own Git repository.</p>
+<p><br>
+Check that the newt binary is installed and you are using the one from <strong> $GOPATH/bin</strong>:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ls $GOPATH/bin/newt
+~/dev/go/bin/newt
+$which newt
+~/dev/go/bin/newt
+$newt version
+Apache Newt (incubating) version: 1.0.0-dev
</pre></div>
<p><br></p>
-<h3 id="step-4-building-the-newt-and-newtmgr-tools">Step 4: Building the Newt and Newtmgr Tools</h3>
-<p>Perform the following commands to build the tools:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ cd $GOPATH/src/mynewt.apache.org/newt/newt
-$ go install
-$ ls $GOPATH/bin/
-newt newtmgr newtvm
+<h4 id="downloading-and-installing-the-newtmgr-tool">Downloading and Installing the Newtmgr Tool</h4>
+<p>The newtmgr Go package is <strong>mynewt.apache.org/newtmgr/newtmgr</strong>. It is stored in the <a href="https://github.com/apache/incubator-mynewt-newtmgr">Apache Mynewt newtmgr tool repository mirrored on github</a>.</p>
+<p>Download the newtmgr package and install the tool:</p>
+<p><strong>Note:</strong> <code>-ldflags -s</code> must be passed to the <code>go get</code> command.</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$cd $GOPATH
+$go get -ldflags -s mynewt.apache.org/newtmgr/newtmgr
+$cd $GOPATH/src/mynewt.apache.org/newtmgr
+$ls
+DISCLAIMER NOTICE newtmgr
+LICENSE README.md nmxact
+$git status
+On branch master
+Your branch is up-to-date with 'origin/master'.
+
+nothing to commit, working directory clean
+</pre></div>
+
+
+<p><br>
+Check that the newtmgr binary is installed and you are using the one from <strong>$GOPATH/bin</strong>:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ls $GOPATH/bin/newtmgr
+~/dev/go/bin/newtmgr
+$which newt
+~/dev/go/bin/newtmgr
</pre></div>
<p><br></p>
-<h3 id="step-5-updating-and-rebuilding-the-tools">Step 5: Updating and Rebuilding the Tools</h3>
-<p>Change to the directory where you initially installed the source: </p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ cd $GOPATH/src/mynewt.apache.org/newt
+<h3 id="step-4-updating-and-rebuilding-the-tools">Step 4: Updating and Rebuilding the Tools:</h3>
+<p>This section shows you how to rebuild the newt and newtmgr tools with the latest updates from the master branch or after you have made changes in your branch. </p>
+<p>Here is the general procedure to rebuild either the newt or newtmgr tool. The only difference is the directory where you will be executing the commands from. You will need to repeat the procedure to rebuild both tools.</p>
+<ol>
+<li>Change to the directory where the local Git repository for the tool is installed.</li>
+<li>Pull the latest changes from the master branch. If you made changes you will need to rebase with <strong>origin master</strong> (See <a href="../../faq/answers/">FAQ</a>).</li>
+<li>Build and install the tool.</li>
+</ol>
+<p><br>
+Change to the directory where the source for the tool is installed.</p>
+<p>For the <strong>newt</strong> tool:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$cd $GOPATH/src/mynewt.apache.org/newt/newt
+</pre></div>
+
+
+<p>For the <strong>newtmgr</strong> tool:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$cd $GOPATH/src/mynewt.apache.org/newtmgr/newtmgr
</pre></div>
<p><br>
-Pull the latest source from the repository (you can change to a different branch using git checkout [branch] if you need to)</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ git pull
+After you change to the specific tool directory, get the latest updates from the master branch. If you made changes and need to rebase with the origin, add the <code>--rebase origin master</code> arguments to the <code>git pull</code> command:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$git pull
</pre></div>
<p><br>
-Install the tools from the latest source:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ cd newt
-$ go install
-$ cd ../newtmgr
-$ go install
-$ ls $GOPATH /bin/
-newt newtmgr newtvm
+Build and install the tool. The updated binary will be installed in the <strong>$GOPATH/bin</strong> directory: </p>
+<p>(<strong>Note:</strong> <code>-ldflags -s</code> must be passed to the <code>go install</code> command if you are rebuilding newtmgr)</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$go install
</pre></div>
-<p>This should have updated your newt and newtmgr to the latest version based on the git repository you used.</p>
+<p>You can run the <code>ls -l</code> command to check the modification time for the binary to ensure the new version is installed. </p>
<div class="row">
[5/7] incubator-mynewt-site git commit: Updates to installation on
Linux and Mac, removal of references to develop branch on website
Posted by ad...@apache.org.
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/develop/newt/install/newt_linux/index.html
----------------------------------------------------------------------
diff --git a/develop/newt/install/newt_linux/index.html b/develop/newt/install/newt_linux/index.html
index df1b621..cbdbbd4 100644
--- a/develop/newt/install/newt_linux/index.html
+++ b/develop/newt/install/newt_linux/index.html
@@ -391,181 +391,218 @@
</div>
</div>
- <h2 id="install-newt-tool-on-linux">Install newt tool on Linux</h2>
+ <h2 id="installing-newt-on-linux">Installing Newt on Linux</h2>
+<p>You can install the latest stable release (1.0.0) of newt from a Debian binary package (amd64) or from a Debian source package. This page shows you how to:</p>
+<ol>
+<li>Set up your computer to retrieve Debian packages from the runtimeco debian package repository.</li>
+<li>Install the latest stable release version of newt from a Debian binary package. </li>
+<li>Install the latest stable release version of newt from a Debian source package.</li>
+</ol>
+<p>If you are running on an amd64 platform, we recommend that you install from the binary package.</p>
+<p><strong>Note:</strong> See <a href="../../../faq/go_env">Setting Up an Go Environment to Contribute to Newt and Newtmgr Tools</a> if you want to: </p>
+<ul>
+<li>Use the newt tool with the latest updates from the master branch. The master branch may be unstable and we recommend that you use the latest stable release version.</li>
+<li>Contribute to the newt tool. </li>
+</ul>
<p><br></p>
-<h3 id="getting-your-linux-box-ready">Getting your Linux box Ready</h3>
-<p>If you want to build the <em>newt</em> tool from its source code, follow the following steps:</p>
-<h4 id="1-install-git-libcurl">1. Install git, libcurl</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ sudo apt-get install git
- $ sudo apt-get install libcurl4-gnutls-dev
+<h3 id="setting-up-your-computer-to-get-packages-from-runtimeco">Setting Up Your Computer to Get Packages from runtimeco</h3>
+<p>The newt Debian packages are stored in a private repository on <strong>https://github/runtimeco/debian-mynewt</strong>. </p>
+<p><strong>Note:</strong> You will only need to perform these steps only once on your computer.
+The following steps must be performed on your computer:</p>
+<ol>
+<li>Add the <code>apt-transport-https</code> package to use HTTPS to retrieve packages. </li>
+<li>Download the public key for the runtimeco debian repository and import the key into the apt keychain.</li>
+<li>Add the repository for the binary and source packages to the apt source list.</li>
+</ol>
+<p><br>
+Add the apt-transport-https package:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$sudo apt-get update
+$sudo apt-get install apt-transport-https
</pre></div>
-<p><strong>NOTE:</strong> On 64-bit host, you may also need to install gcc-multilib, if you encounter compilation errors related to 'sys/cdefs.h'</p>
<p><br></p>
-<h4 id="2-install-go-the-programming-language">2. Install Go, the programming language</h4>
-<ul>
-<li>
-<p>Go language environment dictates a directory structure. Known in Go parlance as a workspace, it must contain three sibling directories with the directory names src, pkg and bin, as explained below. </p>
-<ul>
-<li>
-<p>src contains Go source files organized into packages (one package per directory),</p>
-</li>
-<li>
-<p>pkg contains package objects, and</p>
-</li>
-<li>
-<p>bin contains executable commands.</p>
-</li>
-</ul>
-<p>The GOPATH environment variable specifies the location of your workspace. To setup this workspace environment, create a 'dev' directory and then a 'go' directory under it. Set the GOPATH environment variable to this directory where you will soon clone the <em>newt</em> tool repository.</p>
-</li>
-</ul>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ cd $HOME
- $ mkdir -p dev/go
- $ cd dev/go
- $ export GOPATH=`pwd`
+<p>Download the public key for the runtimeco apt repo (<strong>Note:</strong> There is <code>-</code> after the add):</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">wget -qO - https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/mynewt.gpg.key | sudo apt-key add -
</pre></div>
-<p>(Note that you need to add export statements to ~/.bash_profile to export variables permanently. Don't forget to source the file for the change to go into effect.)</p>
<p><br></p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ vi ~/.bash_profile
- $ source ~/.bash_profile
+<p>Add the repository for the binary and source packages to the apt source list:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$sudo -s
+[sudo] password for <user>:
+root$ cat > /etc/apt/sources.list.d/mynewt.list <<EOF
+deb https://raw.githubusercontent.com/runtimeco/debian-package/master latest main
+deb-src https://raw.githubusercontent.com/runtimeco/debian-package/master latest main
+EOF
+</pre></div>
+
+
+<p><br>
+Check the content of the file:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">root$more /etc/apt/sources.list.d//mynewt.list
+deb https://raw.githubusercontent.com/runtimeco/debian-package/master latest main
+deb-src https://raw.githubusercontent.com/runtimeco/debian-package/master latest main
+</pre></div>
+
+
+<p><br> </p>
+<p>Exit the root shell:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">root$exit
</pre></div>
<p><br></p>
-<ul>
-<li>
-<p>Next, install Go. When installed, Go offers you as a developer a language environment (to compile Go code), construct Go packages (to assemble Go packages) and import Go code (from github). In the next step, you will use the Go commands to import <em>newt</em> repo into your local Go environment.</p>
-<p><strong>Note</strong>: The Newt tool requires Go version 1.7 or later. Currently, the latest Go version that Ubuntu installs is 1.6. You can run <code>apt-get install golang-1.7-go</code> to install version 1.7. You can also download version 1.7 from <a href="https://golang.org/dl/">https://golang.org/dl/</a>. </p>
-</li>
-</ul>
+<h3 id="installing-the-latest-release-of-newt-from-a-binary-package">Installing the Latest Release of Newt from a Binary Package</h3>
+<p>For Linux amd64 platform, you can install the latest stable version (1.0.0) of newt from the newt Debian binary package:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$sudo apt-get update
+$sudo apt-get install newt
+Reading package lists... Done
+Building dependency tree
+Reading state information... Done
+
+ ...
+
+Preparing to unpack .../newt_1.0.0-1_amd64.deb ...
+Unpacking newt (1.0.0-1) ...
+Setting up newt (1.0.0-1) ...
+</pre></div>
+
+
+<p><br>
+See <a href="#check">Checking the Installed Version of Newt</a> to verify that you are using the installed version of newt.</p>
+<p><br></p>
+<h3 id="installing-the-latest-stable-release-of-newt-from-a-source-package">Installing the Latest Stable Release of Newt from a Source Package</h3>
+<p>If you are running Linux on a different architecture, you can install the Debian source package for the latest stable release (1.0.0) of newt. The installation of the source package builds the newt binary and creates a Debian binary package that you then install.</p>
+<p><strong>Note</strong>: Newt version 1.0.0 has been tested on Linux amd64 platform. Version 1.0.0 does not build on the 32 bit platform but have been fixed for the next release.</p>
+<p><br></p>
+<h4 id="installing-go-17">Installing Go 1.7</h4>
+<p>You need Go version 1.7 or higher to build Newt version 1.0.0. Currently, the latest Go version that Ubuntu installs is 1.6. Run <code>go version</code> to check if you have Go 1.7 installed. </p>
+<p><br></p>
+<p>Install Go version 1.7:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$sudo apt-get install golang-1.7-go
Reading package lists... Done
...
Unpacking golang-1.7-go (1.7.1-2ubuntu1) ...
Setting up golang-1.7-go (1.7.1-2ubuntu1) ...
$
-$sudo ln -s /usr/lib/go-1.7/bin/go /usr/bin/go
+$sudo ln -sf ../lib/go-1.7/bin/go /usr/bin/go
$go version
go version go1.7.1 linux/amd64
</pre></div>
-<p><br> </p>
-<h4 id="3-create-local-repository">3. Create local repository</h4>
-<ul>
-<li>Use Go commands to copy the directory (currently the ASF incubator directory). Be patient as it may take a minute or two. Check the directories installed.</li>
-</ul>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ go get mynewt.apache.org/newt/...
-</pre></div>
-
-
+<p>You can also download version 1.7 from <a href="https://golang.org/dl/">https://golang.org/dl/</a>. </p>
<p><br></p>
-<ul>
-<li>Check that newt.go is in place.</li>
-</ul>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ ls $GOPATH/src/mynewt.apache.org/newt
- DISCLAIMER NOTICE newt newtvm viper
- LICENSE README.md newtmgr util yaml
+<h4 id="installing-from-the-source-package">Installing from the Source Package</h4>
+<p>Create a directory and change into the directory, download the source package, and build a binary package from the source package:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">mkdir newt_source
+$cd newt_source
+$sudo apt-get --build source newt
+[sudo] password for <user>:
+Reading package lists... Done
+Need to get 1,866 kB of source archives.
+Get:1 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newt 1.0.0-1 (dsc) [795 B]
+Get:2 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newt 1.0.0-1 (tar) [1,864 kB]
+Get:3 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newt 1.0.0-1 (diff) [2,000 B]
+Fetched 1,866 kB in 1s (1,222 kB/s)
+dpkg-source: warning: extracting unsigned source package (newt_1.0.0-1.dsc)
+dpkg-source: info: extracting newt in newt-1.0.0
+dpkg-source: info: unpacking newt_1.0.0.orig.tar.gz
+dpkg-source: info: unpacking newt_1.0.0-1.debian.tar.xz
+
+ ...
+
+dpkg-deb: building package 'newt' in '../newt_1.0.0-1_amd64.deb'.
+ dpkg-genchanges --build=any,all >../newt_1.0.0-1_amd64.changes
+dpkg-genchanges: info: binary-only upload (no source code included)
+ dpkg-source --after-build newt-1.0.0
+dpkg-buildpackage: info: binary-only upload (no source included)
+W: Can't drop privileges for downloading as file 'newt_1.0.0-1.dsc' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)
</pre></div>
-<p><br></p>
-<h4 id="4-build-the-newt-tool">4. Build the Newt tool</h4>
-<ul>
-<li>Use Go to run the newt.go program to build the <em>newt</em> tool. The command <code>go install</code> compiles and writes the resulting executable to an output file named <code>newt</code>, which is then installed, along with its dependencies, in $GOPATH/bin. If you get errors it is likely because of path resolution issues. Try <code>go build</code> followed by <code>go install</code> in that case.</li>
-</ul>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ cd $GOPATH/src/mynewt.apache.org/newt/newt
- $ go install
- $ ls "$GOPATH"/bin/
- newt newtmgr newtvm
+<p><strong>Note:</strong> You can ignore the "Permission denied: warning message at the end of the command.</p>
+<p><br>
+Install the newt binary package that is created from the source package:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$sudo dpkg -i newt_1.0.0-1_amd64.deb
+Selecting previously unselected package newt.
+(Reading database ... 252969 files and directories currently installed.)
+Preparing to unpack newt_1.0.0-1_amd64.deb ...
+Unpacking newt (1.0.0-1) ...
+Setting up newt (1.0.0-1) ...
</pre></div>
<p><br></p>
-<ul>
-<li>At this point, you can try using <em>newt</em>. For example, check for the version number by typing 'newt version'. See all the possible commands available to a user of newt by typing 'newt -h'.</li>
-</ul>
-<p>(Note: If you are going to be modifying the <em>newt</em> often and going to be compile the program every time you call it, you will want to store the command in a variable in your .bash_profile. So type in <code>export newt="go run $GOPATH/mynewt.apache.org/newt/newt/newt.go"</code> in your .bash_profile and execute it by calling <code>$newt</code> at the prompt instead of <code>newt</code>. Essentially, <code>$newt</code> calls <code>go run</code> which runs the compiled binary directly without producing an executable. Don't forget to reload the updated bash profile by typing <code>source ~/.bash_profile</code> at the prompt! )</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ newt version
- Newt version: 1.0
- $ newt -h
- Newt allows you to create your own embedded application based on the Mynewt
- operating system. Newt provides both build and package management in a single
- tool, which allows you to compose an embedded application, and set of
- projects, and then build the necessary artifacts from those projects. For more
- information on the Mynewt operating system, please visit
- https://mynewt.apache.org/.
-
- Please use the newt help command, and specify the name of the command you want
- help for, for help on how to use a specific command
-
- Usage:
- newt [flags]
- newt [command]
-
- Examples:
- newt
- newt help [<command-name>]
- For help on <command-name>. If not specified, print this message.
-
- Available Commands:
- build Build one or more targets
- clean Delete build artifacts for one or more targets
- create-image Add image header to target binary
- debug Open debugger session to target
- info Show project info
- install Install project dependencies
- load Load built target to board
- mfg Manufacturing flash image commands
- new Create a new project
- pkg Create and manage packages in the current workspace
- run build/create-image/download/debug <target>
- size Size of target components
- sync Synchronize project dependencies
- target Commands to create, delete, configure, and query targets
- test Executes unit tests for one or more packages
- upgrade Upgrade project dependencies
- vals Display valid values for the specified element type(s)
- version Display the Newt version number
-
- Flags:
- -h, --help Help for newt commands
- -j, --jobs int Number of concurrent build jobs (default 8)
- -l, --loglevel string Log level (default "WARN")
- -o, --outfile string Filename to tee output to
- -q, --quiet Be quiet; only display error output
- -s, --silent Be silent; don't output anything
- -v, --verbose Enable verbose output when executing commands
-
- Use "newt [command] --help" for more information about a comma
+<h3 id="checking-the-installed-version-of-newt"><a name="check"></a> Checking the Installed Version of Newt</h3>
+<p>After you have installed newt from either a Debian binary or source package, check that you are using the installed version of newt from <strong>/usr/bin</strong>. </p>
+<p>Check the modification time of the binary and the newt tool that you are using:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ls -l /usr/bin/newt
+-rwxr-xr-x 1 root root 6919280 Apr 22 10:09 /usr/bin/newt
+$which newt
+/usr/bin/newt
+$newt version
+Apache Newt (incubating) version: 1.0.0
</pre></div>
-<p><br></p>
-<h4 id="5-updating-the-newt-tool">5. Updating the Newt tool</h4>
-<ul>
-<li>You will update the newt tool in the same place as you initially installed the newt tool.</li>
-<li>Start by updating the git repository of the newt tool (you can change to a different branch using git checkout [branch] if you need to)</li>
-<li>Then update each of the tools newt, newtmgr and newtvm as needed</li>
-</ul>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ cd $GOPATH/src/mynewt.apache.org/newt
- $ git pull
- $ cd newt
- $ go install
- $ cd ../newtmgr
- $ go install
- $ cd ../newtvm
- $ go install
- $ ls "$GOPATH"/bin/
- newt newtmgr newtvm
+<p><strong>Note:</strong> If you previously built newt from source and the output of <code>which newt</code> shows "$GOPATH/bin/newt", you will need to move "$GOPATH/bin" after "/usr/bin" in your $PATH and export your $PATH.</p>
+<p><br>
+Get information about newt:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$newt
+Newt allows you to create your own embedded application based on the Mynewt
+operating system. Newt provides both build and package management in a single
+tool, which allows you to compose an embedded application, and set of
+projects, and then build the necessary artifacts from those projects. For more
+information on the Mynewt operating system, please visit
+https://mynewt.apache.org/.
+
+Please use the newt help command, and specify the name of the command you want
+help for, for help on how to use a specific command
+
+Usage:
+ newt [flags]
+ newt [command]
+
+Examples:
+ newt
+ newt help [<command-name>]
+ For help on <command-name>. If not specified, print this message.
+
+Available Commands:
+ build Build one or more targets
+ clean Delete build artifacts for one or more targets
+ create-image Add image header to target binary
+ debug Open debugger session to target
+ info Show project info
+ install Install project dependencies
+ load Load built target to board
+ mfg Manufacturing flash image commands
+ new Create a new project
+ pkg Create and manage packages in the current workspace
+ run build/create-image/download/debug <target>
+ size Size of target components
+ sync Synchronize project dependencies
+ target Commands to create, delete, configure, and query targets
+ test Executes unit tests for one or more packages
+ upgrade Upgrade project dependencies
+ vals Display valid values for the specified element type(s)
+ version Display the Newt version number
+
+Flags:
+ -h, --help Help for newt commands
+ -j, --jobs int Number of concurrent build jobs (default 8)
+ -l, --loglevel string Log level (default "WARN")
+ -o, --outfile string Filename to tee output to
+ -q, --quiet Be quiet; only display error output
+ -s, --silent Be silent; don't output anything
+ -v, --verbose Enable verbose output when executing commands
+
+Use "newt [command] --help" for more information about a command.
</pre></div>
-<p>That should have updated your newt, newtmgr and newtvm to the latest versions based on the git repository you used.</p>
<p><br></p>
<div class="row">
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/develop/newtmgr/install_linux/index.html
----------------------------------------------------------------------
diff --git a/develop/newtmgr/install_linux/index.html b/develop/newtmgr/install_linux/index.html
index c5bb466..c191e51 100644
--- a/develop/newtmgr/install_linux/index.html
+++ b/develop/newtmgr/install_linux/index.html
@@ -372,59 +372,197 @@
</div>
</div>
- <h1 id="installing-newtmgr-on-linux">Installing Newtmgr on Linux</h1>
-<p>This page shows you how to install newtmgr from source code on Linux.</p>
-<h3 id="install-go-golang">Install Go (golang)</h3>
-<p>Install Go if it is not installed. The Newtmgr tool version 1.0.0 requires Go version 1.7 or later. Currently, the latest Go version that Ubuntu installs is
-1.6. You can run <code>apt-get install golang-1.7-go</code> to install version 1.7. You can also download version 1.7 from <a href="https://golang.org/dl/">https:/
-/golang.org/dl/</a>.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span style="background-color: #ffffcc">$sudo apt-get install golang-1.7-go
-</span>Reading package lists... Done
+ <h2 id="installing-newtmgr-on-linux">Installing Newtmgr on Linux</h2>
+<p>You can install the latest stable release (1.0.0) of newtmgr from a Debian binary package (amd64) or from a Debian source package. This page shows you how to:</p>
+<ol>
+<li>
+<p>Set up your computer to retrieve Debian packages from the runtimeco debian package repository. </p>
+<p><strong>Note:</strong> You can skip this step if you already set up your computer to access the runtimeco debian repository when you installed the newt tool. </p>
+</li>
+<li>
+<p>Install the latest stable release version of newtmgr from a Debian binary package. </p>
+</li>
+<li>Install the latest stable release version of newtmgr from a Debian source package.</li>
+</ol>
+<p>If you are running on an amd64 platform, we recommend that you install from the binary package.</p>
+<p><strong>Note:</strong> See <a href="../../faq/go_env">Setting Up an Go Environment to Contribute to Newt and Newtmgr Tools</a> if you want to: </p>
+<ul>
+<li>Use the newtmgr tool with the latest updates from the master branch. The master branch may be unstable and we recommend that you use the latest stable release version.</li>
+<li>Contribute to the newtmgr tool. </li>
+</ul>
+<p><br></p>
+<h3 id="setting-up-your-computer-to-get-packages-from-runtimeco">Setting Up Your Computer to Get Packages from runtimeco</h3>
+<p>The newtmgr Debian packages are stored in a private repository on <strong>https://github/runtimeco/debian-mynewt</strong>. </p>
+<p><strong>Note</strong>: You will only need to perform these steps once on your computer. You can skip this step if you already set up your computer to access the runtimeco debian repository when you installed the newt tool. </p>
+<p>The following steps must be performed on your computer:</p>
+<ol>
+<li>Add the <code>apt-transport-https</code> package to use HTTPS to retrieve packages. </li>
+<li>Download the public key for the runtimeco debian repository and import the key into the apt keychain.</li>
+<li>Add the repository for the binary and source packages to the apt source list.</li>
+</ol>
+<p><br>
+Add the apt-transport-https package:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$sudo apt-get update
+$sudo apt-get install apt-transport-https
+</pre></div>
+
+
+<p><br></p>
+<p>Download the public key for the runtimeco apt repo (<strong>Note:</strong> There is <code>-</code> after the add):</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">wget -qO - https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/mynewt.gpg.key | sudo apt-key add -
+</pre></div>
+
+
+<p><br></p>
+<p>Add the repository for the binary and source packages to the apt source list:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$sudo -s
+[sudo] password for <user>:
+root$ cat > /etc/apt/sources.list.d/mynewt.list <<EOF
+deb https://raw.githubusercontent.com/runtimeco/debian-package/master latest main
+deb-src https://raw.githubusercontent.com/runtimeco/debian-package/master latest main
+EOF
+</pre></div>
+
+
+<p><br>
+Check the content of the file:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">root$more /etc/apt/sources.list.d//mynewt.list
+deb https://raw.githubusercontent.com/runtimeco/debian-package/master latest main
+deb-src https://raw.githubusercontent.com/runtimeco/debian-package/master latest main
+</pre></div>
+
+
+<p><br> </p>
+<p>Exit the root shell:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">root$exit
+</pre></div>
+
+
+<p><br></p>
+<h3 id="installing-the-latest-release-of-newtmgr-from-a-binary-package">Installing the Latest Release of Newtmgr from a Binary Package</h3>
+<p>For Linux amd64 platform, you can install the latest stable version (1.0.0) of newtmgr from the newtmgr Debian binary package:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$sudo apt-get update
+$sudo apt-get install newtmgr
+Reading package lists... Done
+Building dependency tree
+Reading state information... Done
+The following NEW packages will be installed:
+ newtmgr
+0 upgraded, 1 newly installed, 0 to remove and 204 not upgraded.
+Need to get 0 B/2,312 kB of archives.
+After this operation, 11.5 MB of additional disk space will be used.
+Selecting previously unselected package newtmgr.
+(Reading database ... 211647 files and directories currently installed.)
+Preparing to unpack .../newtmgr_1.0.0-1_amd64.deb ...
+Unpacking newtmgr (1.0.0-1) ...
+Setting up newtmgr (1.0.0-1)
+</pre></div>
+
+
+<p><br>
+See <a href="#check">Checking the Installed Version of Newtmgr</a> to verify that you are using the installed version of newtmgr.</p>
+<p><br></p>
+<h3 id="installing-the-latest-stable-release-of-newtmgr-from-a-source-package">Installing the Latest Stable Release of Newtmgr from a Source Package</h3>
+<p>If you are running Linux on a different architecture, you can install the Debian source package for the latest stable release (1.0.0) of newtmgr. The installation of the source package builds the newtmgr binary and creates a Debian binary package that you then install.</p>
+<p><strong>Note</strong>: Newtmgr version 1.0.0 has been tested on Linux amd64 platform. </p>
+<p><br></p>
+<h4 id="installing-go-17">Installing Go 1.7</h4>
+<p>You need Go version 1.7 or higher to build Newtmgr version 1.0.0. Currently, the latest Go version that Ubuntu installs is 1.6. Run <code>go version</code> to check if you have Go 1.7 installed. </p>
+<p><br></p>
+<p>Install Go version 1.7:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$sudo apt-get install golang-1.7-go
+Reading package lists... Done
...
Unpacking golang-1.7-go (1.7.1-2ubuntu1) ...
Setting up golang-1.7-go (1.7.1-2ubuntu1) ...
$
-<span style="background-color: #ffffcc">$sudo ln -sf ../lib/go-1.7/bin/go /usr/bin/go
-</span>$go version
+$sudo ln -sf ../lib/go-1.7/bin/go /usr/bin/go
+$go version
go version go1.7.1 linux/amd64
</pre></div>
+<p>You can also download version 1.7 from <a href="https://golang.org/dl/">https://golang.org/dl/</a>. </p>
<p><br></p>
-<p>To use go, you must set a <code>$GOPATH</code> variable in your environment. This tells
-go where to put all the packages it downloads, builds and runs.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ mkdir $HOME/dev
-$ export GOPATH=$HOME/dev/Go
+<h4 id="installing-from-the-source-package">Installing from the Source Package</h4>
+<p>Create a directory and change into the directory, download the source package, and build a binary package from the source package:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">mkdir newtmgr_source
+$cd newtmgr_source
+$sudo apt-get --build source newtmgr
+[sudo] password for <user>:
+
+sudo apt-get --build source newtmgr
+Reading package lists... Done
+Need to get 1,867 kB of source archives.
+Get:1 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newtmgr 1.0.0-1 (dsc) [822 B]
+Get:2 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newtmgr 1.0.0-1 (tar) [1,864 kB]
+Get:3 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newtmgr 1.0.0-1 (diff) [2,372 B]
+Fetched 1,867 kB in 1s (1,767 kB/s)
+
+ ...
+
+dpkg-deb: building package 'newtmgr' in '../newtmgr_1.0.0-1_amd64.deb'.
+ dpkg-genchanges --build=any,all >../newtmgr_1.0.0-1_amd64.changes
+dpkg-genchanges: info: binary-only upload (no source code included)
+ dpkg-source --after-build newtmgr-1.0.0
+dpkg-buildpackage: info: binary-only upload (no source included)
</pre></div>
-<p><br></p>
-<p>Its best to add this to your <code>.profile</code> so its set automatically for your
-environment. </p>
-<p><br></p>
-<h3 id="download-the-newtmgr-source">Download the newtmgr source</h3>
-<p>You will first download the source code for newt.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">go get mynewt.apache.org/newt/...
+<p><br>
+Install the newtmgr binary package that is created from the source package:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$sudo dpkg -i newtmgr_1.0.0-1_amd64.deb
</pre></div>
<p><br></p>
-<h3 id="building-newtmgr">Building newtmgr</h3>
-<p>Change into the directory where the newmgr tool was downloaded and
-install the newtmgr tool</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$cd $GOPATH/src/mynewt.apache.org/newt/newtmgr
-$go install
-$ls $GOPATH/bin
-... newtmgr ...
+<h3 id="checking-the-installed-version-of-newtmgr"><a name="check"></a> Checking the Installed Version of Newtmgr</h3>
+<p>After you have installed newtmgr from either a Debian binary or source package, check that you are using the installed version of newtmgr from <strong>/usr/bin</strong>. </p>
+<p>Check the modification time of the binary and the newtmgr tool that you are using:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ls -l /usr/bin/newtmgr
+-rwxr-xr-x 1 root root 11473328 Apr 25 10:10 /usr/bin/newtmgr
+$which newtmgr
+/usr/bin/newtmgr
</pre></div>
-<p><br></p>
-<p><strong>Note:</strong> If the <code>go install</code> command results in errors indicating some package
-cannot be found, do a <code>go get</code> to download all the third-party files needed
-from github.com and then run <code>go install</code> again. </p>
-<h3 id="add-to-your-path">Add to your Path</h3>
-<p>Add your <code>$GOPATH/bin</code> directory to your path.</p>
+<p><strong>Note:</strong> If you previously built newtmgr from source and the output of <code>which newtmgr</code> shows "$GOPATH/bin/newtmgr", you will need to move "$GOPATH/bin" after "/usr/bin" in your $PATH and export your $PATH.</p>
+<p><br>
+Get information about newtmgr:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$newtmgr
+Newtmgr helps you manage remote devices running the Mynewt OS
+
+Usage:
+ newtmgr [flags]
+ newtmgr [command]
+
+Available Commands:
+ config Read or write a config value on a device
+ conn Manage newtmgr connection profiles
+ crash Send a crash command to a device
+ datetime Manage datetime on a device
+ echo Send data to a device and display the echoed back data
+ fs Access files on a device
+ image Manage images on a device
+ log Manage logs on a device
+ mpstats Read memory pool statistics from a device
+ reset Send reset request to a device
+ run Run test procedures on a device
+ stat Read statistics from a device
+ taskstats Read task statistics from a device
+
+Flags:
+ -c, --conn string connection profile to use
+ -h, --help Help for newtmgr commands
+ -l, --loglevel string log level to use (default "info")
+ -t, --trace print all bytes transmitted and received
+
+Use "newtmgr [command] --help" for more information about a command.
+</pre></div>
+
+
+<p>```
+<br></p>
<div class="row">
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/develop/os/get_started/cross_tools/index.html
----------------------------------------------------------------------
diff --git a/develop/os/get_started/cross_tools/index.html b/develop/os/get_started/cross_tools/index.html
index d4adb46..6398a54 100644
--- a/develop/os/get_started/cross_tools/index.html
+++ b/develop/os/get_started/cross_tools/index.html
@@ -392,11 +392,14 @@
</div>
<h1 id="installing-cross-tools-for-arm">Installing Cross Tools for ARM</h1>
-<p>This page shows how to install tools on your laptop/computer to use for direct communication (e.g. for debugging) with some ARM based HW platforms running Apache Mynewt. You will also have to use the Newt tool installed to run natively on your machine. You may choose to do this instead of using the build toolchain and Newt tool available in a Docker container.</p>
-<p>This page provides guidance for installing the tools directly on your MAC and Linux machine. See the relevant sections below.</p>
+<p>This page shows how to install tools on your laptop/computer to use for direct communication (e.g. for debugging) with some ARM based HW platforms running Apache Mynewt. It shows you how to install the following tools for Mac OS X and Linux:</p>
+<ul>
+<li>ARM Cross toolchain</li>
+<li>Debugger to load and debug your device</li>
+</ul>
<p><br></p>
-<h2 id="install-arm-cross-tools-in-mac-os-x">Install ARM Cross tools in Mac OS X</h2>
-<h3 id="install-tool-chain">Install Tool Chain</h3>
+<h2 id="install-arm-cross-toolchain">Install ARM Cross Toolchain</h2>
+<h3 id="install-arm-toolchain-for-mac-os-x">Install ARM Toolchain For Mac OS X</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,
@@ -420,22 +423,7 @@ 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</h3>
-<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>
-<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 <user> admin 36 Sep 17 16:22 /usr/local/bin/openocd -> ../Cellar/open-ocd/0.9.0/bin/openocd
-</pre></div>
-
-
-<p><br></p>
-<h2 id="install-arm-cross-arm-tools-for-linux">Install ARM cross arm tools for Linux</h2>
-<h3 id="install-tool-chain_1">Install Tool Chain</h3>
+<h3 id="install-arm-toolchain-for-linux">Install ARM Toolchain For Linux</h3>
<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/~team-gcc-arm-embedded/+archive/ubuntu/ppa">https://launchpad.net/~team-gcc-arm-embedded/+archive/ubuntu/ppa</a>.</p>
@@ -448,20 +436,86 @@ $ sudo apt-get install gdb-arm-none-eabi
<p><br></p>
-<h3 id="install-openocd_1">Install OpenOCD</h3>
+<h2 id="install-debugger">Install Debugger</h2>
+<p>Mynewt uses, depending on the board, either the OpenOCD or SEGGER J-Link debugger. </p>
+<h3 id="install-openocd">Install OpenOCD</h3>
<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
+<p>OpenOCD version 0.10.0 with nrf52 support is required. A binary for this version is available to download for Mac OS and Linux.</p>
+<p><br></p>
+<h4 id="install-openocd-on-mac-os">Install OpenOCD on Mac OS</h4>
+<p>Step 1: Download the <a href="https://github.com/runtimeco/openocd-binaries/raw/master/openocd-bin-0.10.0-MacOS.tgz">binary tarball for Mac OS</a>.</p>
+<p>Step 2: Change to the root directory: </p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$cd /
+</pre></div>
+
+
+<p><br>
+Step 3: Untar the tarball and install into <strong> /usr/local/bin</strong>. You will need to replace <strong> ~/Downloads </strong> with the directory that the tarball is downloaded to. </p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">sudo tar -xf ~/Downloads/openocd-bin-0.10.0-MacOS.tgz `
+</pre></div>
+
+
+<p><br>
+Step 4: Check the OpenOCD version you are using: </p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$which openocd
+/usr/local/bin/openocd
+$openocd -v
+Open On-Chip Debugger 0.10.0
+Licensed under GNU GPL v2
+For bug reports, read
+http://openocd.org/doc/doxygen/bugs.html
+</pre></div>
+
+
+<p>You should see version: <strong>0.10.0</strong>. </p>
+<p><br></p>
+<h4 id="install-openocd-on-linux">Install OpenOCD on Linux</h4>
+<p>Step 1: Download the <a href="https://github.com/runtimeco/openocd-binaries/raw/master/openocd-bin-0.10.0-Linux.tgz">binary tarball for Linux</a></p>
+<p>Step 2: Change to the root directory: </p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$cd /
</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><br>
+Step 3: Untar the tarball and install into <strong> /usr/local/bin</strong>. You will need to replace <strong> ~/Downloads </strong> with the directory that the tarball is downloaded to. </p>
+<p><strong> Note:</strong> You must specify the -p option for the tar command.</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$sudo tar -xpf ~/Downloads/openocd-bin-0.10.0-Linux.tgz
+</pre></div>
+
+
+<p><br>
+Step 4: Check the OpenOCD version you are using: </p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$which openocd
+/usr/local/bin/openocd
+$openocd -v
+Open On-Chip Debugger 0.10.0
+Licensed under GNU GPL v2
+For bug reports, read
+http://openocd.org/doc/doxygen/bugs.html
+</pre></div>
+
+
+<p>You should see version: <strong>0.10.0</strong>. </p>
+<p>If you see any of these error messages:</p>
+<ul>
+<li>
+<p>openocd: error while loading shared libraries: libhidapi-hidraw.so.0: cannot open shared object file: No such file or directory</p>
+</li>
+<li>
+<p>openocd: error while loading shared libraries: libusb-1.0.so.0: cannot open shared object file: No such file or directory </p>
+</li>
+</ul>
+<p>run the following command to install the libraries: </p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$sudo apt-get install libhidapi-dev:i386
+</pre></div>
+
+
+<p><br></p>
+<h3 id="install-seggar-j-link">Install SEGGAR J-Link</h3>
+<p>You can download and install Segger J-LINK Software and documentation pack from <a href="https://www.segger.com/jlink-software.html">SEGGER</a>. </p>
<div class="row">
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/develop/os/get_started/get_started/index.html
----------------------------------------------------------------------
diff --git a/develop/os/get_started/get_started/index.html b/develop/os/get_started/get_started/index.html
index 596404f..9b8332e 100644
--- a/develop/os/get_started/get_started/index.html
+++ b/develop/os/get_started/get_started/index.html
@@ -361,13 +361,12 @@
<h2 id="quick-start">Quick Start</h2>
<p>If you are curious about Mynewt and want to get a quick feel for the project, you've come to the right place. We have two options for you:</p>
+<p><br>
+<strong>Option 1 (Recommended)</strong> allows you to install the Newt tool, instances of the Mynewt OS (for simulated targets), and toolchains for developing embedded software (e.g. GNU toolchain) natively on your laptop or computer. We have tried to make the process easy. For example, for the Mac OS we created brew formulas. </p>
+<p>We recommend this option if you are familiar with such environments or are concerned about performance on your machine. Follow the instructions to <a href="../native_tools/">install native tools</a> and <a href="../cross_tools/">install cross tools for ARM</a> if you prefer this option.</p>
<p><br></p>
-<p><strong>Option 1</strong> is an easy, self-contained way to get up and running with Mynewt - but has limitations! The Newt tool and build toolchains are all available in a single <a href="../docker/">All-in-one Docker Container</a> that you can install on your laptop or computer.</p>
-<p>However, this is not a long-term option since support is not likely for all features useful or critical to embedded systems development. For example, USB device mapping available in the Docker toolkit (used in this Option 1) is no longer available in the new Docker releases. The Docker option is also typically slower than the native install option. </p>
-<p><span style="color:red"> Therefore, the recommended option is Option 2 below. </span></p>
-<p><br></p>
-<p><strong>Option 2 (Recommended)</strong> allows you to install the Newt tool, instances of the Mynewt OS (for simulated targets), and toolchains for developing embedded software (e.g. GNU toolchain) natively on your laptop or computer. We have tried to make the process easy. For example, for the Mac OS we created brew formulas. </p>
-<p>You want this option if you are familiar with such environments or are concerned about performance on your machine. Follow the instructions to <a href="../native_tools/">install native tools</a> and <a href="../cross_tools/">install cross tools for ARM</a> if you prefer this option.</p>
+<p><strong>Option 2</strong> is an easy, self-contained way to get up and running with Mynewt - but has limitations! The Newt tool and build toolchains are all available in a single <a href="../docker/">All-in-one Docker Container</a> that you can install on your laptop or computer.</p>
+<p>However, this is not a long-term option since support is not likely for all features useful or critical to embedded systems development. For example, USB device mapping available in the Docker toolkit is no longer available in the new Docker releases. The Docker option is also typically slower than the native install option. </p>
<p><br></p>
<p>You can then proceed with the instructions on how to
* <a href="../project_create/">Create Your First Project</a> - on simulated hardware.</p>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/develop/os/get_started/native_tools/index.html
----------------------------------------------------------------------
diff --git a/develop/os/get_started/native_tools/index.html b/develop/os/get_started/native_tools/index.html
index 0a6e774..2e4082a 100644
--- a/develop/os/get_started/native_tools/index.html
+++ b/develop/os/get_started/native_tools/index.html
@@ -411,8 +411,8 @@
<p><br></p>
<p>Check the gcc version you have installed (either using brew or previously installed). The brew-installed version can be checked using <code>brew list gcc</code>. The default compiler.yml configuration file in Mynewt expects version 5.x for Mac users, so if the installed version is 6.x and you wish to continue with this newer version, modify the <code><mynewt-src-directory>/repos/apache-mynewt-core/compiler/sim/compiler.yml</code> file to change the default <code>gcc-5</code> defined there to <code>gcc-6</code>. In other words, replace the lines shown highlighted below:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"># OS X.
-<span style="background-color: #ffffcc">compiler.path.cc.DARWIN.OVERWRITE: "/usr/local/bin/gcc-5"
-</span><span style="background-color: #ffffcc">compiler.path.as.DARWIN.OVERWRITE: "/usr/local/bin/gcc-5 -x assembler-with-cpp"
+<span style="background-color: #ffffcc">compiler.path.cc.DARWIN.OVERWRITE: "gcc-5"
+</span><span style="background-color: #ffffcc">compiler.path.as.DARWIN.OVERWRITE: "gcc-5"
</span>compiler.path.objdump.DARWIN.OVERWRITE: "gobjdump"
compiler.path.objsize.DARWIN.OVERWRITE: "objsize"
compiler.path.objcopy.DARWIN.OVERWRITE: "gobjcopy"
@@ -420,16 +420,16 @@ compiler.path.objcopy.DARWIN.OVERWRITE: "gobjcopy"
<p>with the following:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">compiler.path.cc.DARWIN.OVERWRITE: "/usr/local/bin/gcc-6"
-compiler.path.as.DARWIN.OVERWRITE: "/usr/local/bin/gcc-6 -x assembler-with-cpp\u201d
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">compiler.path.cc.DARWIN.OVERWRITE: "gcc-6"
+compiler.path.as.DARWIN.OVERWRITE: "gcc-6\u201d
</pre></div>
<p><br></p>
<p>In case you wish to use Clang, you can change your <code><mynewt-src-directory>/repos/apache-mynewt-core/compiler/sim/compiler.yml</code> to use Clang. Delete the gcc-5 DARWIN.OVERWRITE lines highlighted below.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"># OS X.
-<span style="background-color: #ffffcc">compiler.path.cc.DARWIN.OVERWRITE: "/usr/local/bin/gcc-5"
-</span><span style="background-color: #ffffcc">compiler.path.as.DARWIN.OVERWRITE: "/usr/local/bin/gcc-5 -x assembler-with-cpp"
+<span style="background-color: #ffffcc">compiler.path.cc.DARWIN.OVERWRITE: "gcc-5"
+</span><span style="background-color: #ffffcc">compiler.path.as.DARWIN.OVERWRITE: "gcc-5"
</span>compiler.path.objdump.DARWIN.OVERWRITE: "gobjdump"
compiler.path.objsize.DARWIN.OVERWRITE: "objsize"
compiler.path.objcopy.DARWIN.OVERWRITE: "gobjcopy"
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/develop/os/get_started/project_create/index.html
----------------------------------------------------------------------
diff --git a/develop/os/get_started/project_create/index.html b/develop/os/get_started/project_create/index.html
index 3c72674..c932da5 100644
--- a/develop/os/get_started/project_create/index.html
+++ b/develop/os/get_started/project_create/index.html
@@ -442,7 +442,7 @@ file. </p>
</pre></div>
-<p>Changing to 1-dev will put you on the develop branch. <strong>The Develop Branch may not be stable and you may encounter bugs or other problems.</strong></p>
+<p>Changing to 0-dev will put you on the latest master branch. <strong>This branch may not be stable and you may encounter bugs or other problems.</strong></p>
<p><br></p>
<h3 id="newt-install">Newt Install</h3>
<p>Once you've switched into your new project's directory, the next step is to fetch
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/develop/os/get_started/vocabulary/index.html
----------------------------------------------------------------------
diff --git a/develop/os/get_started/vocabulary/index.html b/develop/os/get_started/vocabulary/index.html
index 7dee262..18e7b19 100644
--- a/develop/os/get_started/vocabulary/index.html
+++ b/develop/os/get_started/vocabulary/index.html
@@ -363,8 +363,8 @@ the <code>apache-mynewt-core</code> repository.</p>
</li>
<li>
<p><code>vers=1-latest</code>: Defines the repository version. This string will use the
-latest code in the 'Master' github branch. To use the latest version in the
-develop branch, just change it to <code>vers=1-dev</code></p>
+latest stable version in the 'Master' github branch. To use the latest version in the
+master branch, just change it to <code>vers=0-dev</code>. Note that this branch might not be stable. </p>
</li>
</ul>
<p>Repositories are versioned collections of packages. </p>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/develop/os/tutorials/STM32F303/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/STM32F303/index.html b/develop/os/tutorials/STM32F303/index.html
deleted file mode 100644
index 00802d0..0000000
--- a/develop/os/tutorials/STM32F303/index.html
+++ /dev/null
@@ -1,774 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
- <head>
- <meta charset="utf-8">
- <meta http-equiv="X-UA-Compatible" content="IE=edge">
- <meta name="viewport" content="width=device-width, initial-scale=1.0">
-
-
- <!-- This is broken by doc revisioning.
- <link rel="canonical" href="http://mynewt.apache.org/os/tutorials/STM32F303/"> -->
- <link rel="shortcut icon" href="../../../img/favicon.ico">
-
- <title>toc - Apache Mynewt</title>
-
- <link href="../../../css/bootstrap-3.0.3.min.css" rel="stylesheet">
- <link rel="stylesheet" href="../../../css/highlight.css">
- <link href="../../../css/base.css" rel="stylesheet">
- <link href="../../../css/custom.css" rel="stylesheet">
- <link href="../../../css/v2.css" rel="stylesheet">
- <link href="https://fonts.googleapis.com/css?family=Lato" rel="stylesheet">
- <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/font-awesome/4.5.0/css/font-awesome.min.css">
- <link href="../../../extra.css" rel="stylesheet">
-
- <!-- HTML5 shim and Respond.js IE8 support of HTML5 elements and media queries -->
- <!--[if lt IE 9]>
- <script src="https://oss.maxcdn.com/libs/html5shiv/3.7.0/html5shiv.js"></script>
- <script src="https://oss.maxcdn.com/libs/respond.js/1.3.0/respond.min.js"></script>
- <![endif]-->
-
-
- <script>
- (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
- (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
- m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
- })(window,document,'script','//www.google-analytics.com/analytics.js','ga');
-
- ga('create', 'UA-72162311-1', 'auto');
- ga('send', 'pageview');
- </script>
-
- </head>
-
-
- <body class="toc">
-
-
- <div class="container">
- <div class="row v2-main-banner">
- <a class="logo-cell" href="/">
- <img class="logo" src="/img/logo.png">
- </a>
- <div class="tagline-cell">
- <h4 class="tagline">An OS to build, deploy and securely manage billions of devices</h4>
- </div>
- <div class="news-cell">
- <div class="well">
- <h4>Latest News:</h4> <a href="/download">Apache Mynewt 1.0.0</a> released (March 22, 2017)
- </div>
- </div>
- </div>
-</div>
-
-
-
-
-
-
-
-
-<nav id="navbar" class="navbar navbar-inverse affix-top" data-spy="affix" data-offset-top="150" role="navigation">
- <div class="container">
- <!-- Collapsed navigation -->
- <div class="navbar-header">
- <!-- Expander button -->
- <button type="button" class="navbar-toggle" data-toggle="collapse" data-target=".navbar-collapse">
- <span class="sr-only">Toggle navigation</span>
- <span class="icon-bar"></span>
- <span class="icon-bar"></span>
- <span class="icon-bar"></span>
- </button>
-
- </div>
-
- <!-- Expanded navigation -->
- <div class="navbar-collapse collapse">
- <!-- Main navigation -->
- <ul class="nav navbar-nav navbar-right">
- <li
- class=""
->
- <a href="/"><i class="fa fa-home" style="font-size: larger;"></i></a>
- </li>
- <li
- class="important"
->
- <a href="/quick-start/">Quick Start</a>
- </li>
- <li
- class=""
->
- <a href="/about/">About</a>
- </li>
- <li
- class=""
->
- <a href="/talks/">Talks</a>
- </li>
- <li
- class="active"
->
- <a href="/latest/os/introduction">Documentation</a>
- </li>
- <li
- class=""
->
- <a href="/download/">Download</a>
- </li>
- <li
- class=""
->
- <a href="/community/">Community</a>
- </li>
- <li
- class=""
->
- <a href="/events/">Events</a>
- </li>
- </ul>
-
- <!-- Search, Navigation and Repo links -->
- <ul class="nav navbar-nav navbar-right">
-
- </ul>
- </div>
- </div>
-</nav>
-
-
-
- <div class="container">
-
- <div class="row">
- <div class="col-md-3 v2-sidebar sidebar-container"><div id="docSidebar" class="hidden-print" role="complementary">
- <div class="top">
- <div role="search">
- <form id="rtd-search-form" class="wy-form" action="../../../search.html" method="get">
- <div class="form-group">
- <input type="text" name="q" class="form-control" placeholder="Search documentation" />
- </div>
- </form>
- </div>
- </div>
- <ul class="toc-nav">
- <li class="doc-version">
-<select class="form-control" onchange="if (this.value) window.location.href=this.value">
-
- <option
- value="/develop/os/introduction"
- selected="selected"
- >
- Version: develop (latest)
- </option>
-
- <option
- value="/v0_9_0/os/introduction"
-
- >
- Version: 0.9.0
- </option>
-
-</select>
-</li>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- <li ><a href="../../introduction/">Mynewt Documentation</a>
-
-
- <ul>
-
-
-
-
-
-
-
- <li ><a href="../../get_started/get_started/">Basic Setup</a>
-
-
- </li>
-
-
-
-
-
- <li >
- <a href="../../get_started/vocabulary/">Concepts</a>
- </li>
-
-
-
-
-
-
-
- <li ><a href="../tutorials/">Tutorials</a>
-
-
- <ul>
-
-
-
-
-
-
-
- <li ><a href="../blinky/">Project Blinky</a>
-
-
- <ul>
-
-
-
-
-
- <li >
- <a href="../arduino_zero/">Blinky on Arduino Zero</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../blinky_primo/">Blinky on Arduino Primo</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../olimex/">Blinky on Olimex</a>
- </li>
-
-
-
-
-
-
-
- <li class="active"><a href="./">Blinky on STM32F303</a>
-
-
- <ul>
-
-
-
-
-
- <li >
- <a href="../pin-wheel-mods/">Pinwheel Blinky</a>
- </li>
-
-
-
- </ul>
-
- </li>
-
-
-
-
-
- <li >
- <a href="../nRF52/">Blinky on nRF52</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../rbnano2/">Blinky on RedBear Nano 2</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../blinky_console/">Add Console and Shell to Blinky</a>
- </li>
-
-
-
- </ul>
-
- </li>
-
-
-
-
-
-
-
- <li ><a href="../repo/add_repos/">Work with repositories</a>
-
-
- </li>
-
-
-
-
-
-
-
- <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
-
-
- </li>
-
-
-
-
-
- <li >
- <a href="../ibeacon/">BLE iBeacon</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../eddystone/">BLE Eddystone</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../add_shell/">Enable the OS Shell and Console</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../tasks_lesson/">Tasks and Priority Management</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../unit_test/">Write a Test Suite for a Package</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../event_queue/">Events and Event Queues</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../bletiny_project/">BLE app to check stats via console</a>
- </li>
-
-
-
-
-
-
-
- <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
- </li>
-
-
-
-
-
- <li >
- <a href="../blehci_project/">BLE HCI interface</a>
- </li>
-
-
-
-
-
-
-
- <li><a href="
- ../air_quality_sensor/
-">Air-quality Sensor project</a>
-
-
- </li>
-
-
-
-
-
- <li >
- <a href="../nrf52_adc/">Add an Analog Sensor</a>
- </li>
-
-
-
- </ul>
-
- </li>
-
-
-
-
-
-
-
- <li ><a href="../../os_user_guide/">OS User Guide</a>
-
-
- </li>
-
-
-
-
-
-
-
- <li><a href="
- ../../../network/ble/ble_intro/
-">BLE User Guide</a>
-
-
- </li>
-
-
-
-
-
-
-
- <li ><a href="../../../newt/newt_intro/">Newt Tool Guide</a>
-
-
- </li>
-
-
-
-
-
-
-
- <li ><a href="../../../newtmgr/overview/">Newt Manager Guide</a>
-
-
- </li>
-
-
-
- </ul>
-
- </li>
-
-
-
-
-
-
-
- <li><a href="
- ../../../faq/go_env/
-">Appendix</a>
-
-
- </li>
-
-
-
- </ul>
-</div></div>
-
- <div class="col-md-9" role="main">
- <div class="doc-header">
- <div role="navigation" aria-label="breadcrumbs navigation">
- <ul class="wy-breadcrumbs pull-right">
- <li><a href="/develop/os/introduction">Docs</a></li>
-
-
-
- <li>» <a href="../blinky/">Project Blinky</a></li>
-
-
-
- <li>» Blinky on STM32F303</li>
-
-
-
-
-
- </ul>
-</div>
- </div>
-
- <h2 id="blinky-your-hello-world-on-stm32f303-discovery">Blinky, your "Hello World!", on STM32F303 Discovery</h2>
-<p><br></p>
-<h3 id="objective">Objective</h3>
-<p>Learn how to use packages from a default application repository of Mynewt to build your first <em>Hello World</em> application (Blinky) on a target board. Once built using the <em>newt</em> tool, this application will blink the LED lights on the target board.</p>
-<p>Create a project with a simple app that blinks an LED on the stmf303
-discovery board. In the process import some external libraries into your project. Download the application to the target and watch it blink!</p>
-<p><br></p>
-<h3 id="what-you-need">What you need</h3>
-<ul>
-<li>Discovery kit with STM32F303VC MCU</li>
-<li>Laptop running Mac OSX. </li>
-<li>It is assumed you have already installed newt tool. </li>
-<li>It is assumed you already installed native tools as described <a href="../../get_started/native_tools/">here</a></li>
-</ul>
-<p>Also, we assume that you're familiar with UNIX shells. Let's gets started!</p>
-<p><br></p>
-<h3 id="create-a-project">Create a project</h3>
-<p>Create a new project to hold your work. For a deeper understanding, you can read about project creation in
-<a href="../../get_started/project_create/">Get Started -- Creating Your First Project</a>
-or just follow the commands below.</p>
-<p>If you've already created a project from another tutorial, you can re-use
-that project.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ mkdir ~/dev
-$ cd ~/dev
-$ newt new myproj
-Downloading project skeleton from apache/incubator-mynewt-blinky...
-Installing skeleton in myproj...
-Project myproj successfully created.
-
-$ cd myproj
-</pre></div>
-
-
-<p><strong>Note:</strong> Don't forget to change into the <code>myproj</code> directory.</p>
-<p><br></p>
-<h3 id="import-external-stm32f3-library-support">Import External STM32F3 Library support</h3>
-<p>The STM32F303 support for Mynewt lives in an external repository. It's
-necessary to add another repository to the project. To do this,
-edit the file <code>project.yml</code> in the root directory of your project <code>myproj</code></p>
-<p>This requires two changes to this file.</p>
-<ol>
-<li>You must define the properties of the external repository that you want
-to add</li>
-<li>You must include the repository in your project.</li>
-</ol>
-<p>Edit the file <code>project.yml</code> with your favorite editor and add the
-following repository details in the file (after the core
-repository). This gives newt the information to contact the repository
-and extract its contents. In this case, the repository is on github in
-the <code>runtimeinc</code> collection. Its name is <code>mynewt-stm32f3</code> and we will accept
-any version up to the latest. You can look at the contents <a href="https://github.com/runtimeinc/mynewt_stm32f3">here</a>.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">repository.mynewt_stm32f3:
- type: github
- vers: 0-latest
- user: runtimeinc
- repo: mynewt_stm32f3
-</pre></div>
-
-
-<p><br></p>
-<p>In the same file, add the following highlighted line to the
-<code>project.repositories</code> variable. This tells newt to download the
- repository contents into your project. </p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">project.repositories:
- - apache-mynewt-core
-<span style="background-color: #ffffcc"> - mynewt_stm32f3
-</span></pre></div>
-
-
-<p><br></p>
-<h3 id="install-dependencies">Install dependencies</h3>
-<p>Now you can install this into the project using:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt install -v
-Downloading repository description for apache-mynewt-core... success!
-...
-apache-mynewt-core successfully installed version 0.9.1-none
-...
-Downloading repository description for mynewt_stm32f3... success!
-Downloading repository mynewt_stm32f3
-...
-Resolving deltas: 100% (65/65), done.
-Checking connectivity... done.
-mynewt_stm32f3 successfully installed version 0.9.0-none
-</pre></div>
-
-
-<p><br></p>
-<h3 id="create-targets">Create targets</h3>
-<p>Create two targets to build using the stmf3 board support package and the
-app blinky example from mynewt. The output of these commands are not
-shown here for brevity. </p>
-<p>The first target is the application image itself. The second
-target is the bootloader which allows you to upgrade your mynewt
-applications. </p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt target create stmf3_blinky
-$ newt target set stmf3_blinky build_profile=optimized
-$ newt target set stmf3_blinky bsp=@mynewt_stm32f3/hw/bsp/stm32f3discovery
-$ newt target set stmf3_blinky app=apps/blinky
-
-$ newt target create stmf3_boot
-$ newt target set stmf3_boot app=@apache-mynewt-core/apps/boot
-$ newt target set stmf3_boot bsp=@mynewt_stm32f3/hw/bsp/stm32f3discovery
-$ newt target set stmf3_boot build_profile=optimized
-
-$ newt target show
-
-targets/stmf3_blinky
- app=apps/blinky
- bsp=@mynewt_stm32f3/hw/bsp/stm32f3discovery
- build_profile=optimized
-targets/stmf3_boot
- app=apps/boot
- bsp=@mynewt_stm32f3/hw/bsp/stm32f3discovery
- build_profile=optimized
-</pre></div>
-
-
-<p><br></p>
-<h3 id="build-the-target-executables">Build the target executables</h3>
-<p>To build the images, use the <code>newt build</code> command below.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt build stmf3_blinky
- ...
-Archiving stm32f3discovery.a
-Linking blinky.elf
-App successfully built: ~/dev/myproj/bin/stmf3_blinky/apps/blinky/blinky.elf
-
-$ newt build stmf3_boot
-Compiling log_shell.c
-Archiving log.a
-Linking boot.elf
-App successfully built: ~/dev/myproj/bin/stmf3_boot/apps/boot/boot.elf
-</pre></div>
-
-
-<p><br></p>
-<h3 id="sign-and-create-the-blinky-application-image">Sign and create the blinky application image</h3>
-<p>You must sign and version your application image to download it using newt. Use
-the <code>newt create-image</code> command to perform this action. Here we assign this
-image an arbitrary version <code>1.2.3</code>.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt create-image stmf3_blinky 1.2.3
-App image successfully generated: ~/dev/myproj/bin/stmf3_blinky/apps/blinky/blinky.img
-Build manifest:~/dev/myproj/bin/stmf3_blinky/apps/blinky/manifest.json
-</pre></div>
-
-
-<p><br></p>
-<h3 id="configure-the-hardware">Configure the hardware</h3>
-<p>The STM32F3DISCOVERY board includes an ST-LINK/V2 embedded debug tool interface that will be used to program/debug the board. To program the MCU on the board, simply plug in the two jumpers on CN4, as shown in the picture in red. If you want to learn more about the board you will find the User Manual at <a href="http://www.st.com/st-web-ui/static/active/jp/resource/technical/document/user_manual/DM00063382.pdf">http://www.st.com/st-web-ui/static/active/jp/resource/technical/document/user_manual/DM00063382.pdf</a></p>
-<p>Just plug the USB cable into the <code>USB ST-LINK</code> port and it should power on and be ready to dowload to.</p>
-<ul>
-<li><img alt="STMdiscovery" src="../pics/STM32f3discovery_connector.png" /></li>
-</ul>
-<p><br></p>
-<h3 id="download-the-images">Download the Images</h3>
-<p>Use the <code>newt load</code> command to download the images to the target board.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt -v load stmf3_boot
-$ newt -v load stmf3_blinky
-</pre></div>
-
-
-<p><br></p>
-<h3 id="watch-the-led-blink">Watch the LED blink</h3>
-<p>Congratulations! You have built, downloaded, and run your first application using mynewt for the stm32f3 discovery board. One of the LEDs on the LED wheel should be blinking at 1 Hz.</p>
-<p><br></p>
-<h3 id="want-more">Want more?</h3>
-<p>Want to make your board do something a little more exciting with the LEDs? Then try making the modifications to the Blinky app to make it a <a href="../pin-wheel-mods/">pin-wheel app</a> and you can light all the LEDs in a pin-wheel fashion.</p>
-<p>We have more fun tutorials for you to get your hands dirty. Be bold and try other Blinky-like <a href="../nRF52/">tutorials</a> or try enabling additional functionality such as <a href="../project-slinky/">remote comms</a> on the current board.</p>
-<p>If you see anything missing or want to send us feedback, please do so by signing up for appropriate mailing lists on our <a href="../../../community/">Community Page</a>.</p>
-<p>Keep on hacking and blinking!</p>
-
- <div class="row">
-
-
-
-
-<ul class="nav nav-pills" style="margin-bottom: 10px">
- <li>
-
- <a href=../olimex/>
- <span class="fa fa-arrow-left"></span>
- Previous: Blinky on Olimex
- </a>
-
- </li>
- <li class="pull-right">
-
- <a href=../pin-wheel-mods/>
- Next: Pinwheel Blinky
- <span class="fa fa-arrow-right"></span>
- </a>
-
- </li>
-</ul>
- </div>
- <footer class="row">
- <div class="col-xs-12">
-
- <p class="copyright">Apache Mynewt (incubating) is available under Apache License, version 2.0.</p>
-
- </div>
- <div class="col-xs-12">
- <div class="logos">
- <img src="/img/asf_logo_wide_small.png" alt="Apache" title="Apache">
- <small class="footnote">
- MyNewt is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.
- </small>
- <img src="/img/egg-logo2.png" alt="Apache Incubator" title="Apache Incubator">
- </div>
- </div>
-</footer>
- </div>
- </div>
-
-
- </div>
-
- <script src="../../../js/jquery-1.10.2.min.js"></script>
- <script src="../../../js/bootstrap-3.0.3.min.js"></script>
- <script src="../../../js/highlight.pack.js"></script>
- <script src="../../../js/base.js"></script>
- <script src="../../../js/custom.js"></script>
-
- </body>
-</html>
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/develop/os/tutorials/arduino_zero/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/arduino_zero/index.html b/develop/os/tutorials/arduino_zero/index.html
index 9620a75..41b0eb3 100644
--- a/develop/os/tutorials/arduino_zero/index.html
+++ b/develop/os/tutorials/arduino_zero/index.html
@@ -265,17 +265,6 @@
-
-
- <li ><a href="../STM32F303/">Blinky on STM32F303</a>
-
-
- </li>
-
-
-
-
-
<li >
<a href="../nRF52/">Blinky on nRF52</a>
</li>
@@ -543,6 +532,7 @@
<li>Meet the prerequisites listed in <a href="../blinky/">Project Blinky</a>.</li>
<li>Have an Arduino Zero board.<br />
Note: There are many flavors of Arduino. Make sure you are using an Arduino Zero. See below for the versions of Arduino Zero that are compatible with this tutorial.</li>
+<li>Install the <a href="../../../os/get_started/cross_tools/">OpenOCD debugger</a>.</li>
</ul>
<p>This tutorial uses the Arduino Zero Pro board. The tutorial has been tested on the following three Arduino Zero boards - Zero, M0 Pro, and Zero-Pro.</p>
<p><img src="https://www.arduino.cc/en/uploads/Main/Zero_Usb_Ports.jpg" alt="Drawing" style="width: 390px;"/>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/develop/os/tutorials/blehci_project/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/blehci_project/index.html b/develop/os/tutorials/blehci_project/index.html
index de2973b..06932ac 100644
--- a/develop/os/tutorials/blehci_project/index.html
+++ b/develop/os/tutorials/blehci_project/index.html
@@ -594,13 +594,16 @@ Bluetooth monitor ver 5.37
<p><br></p>
<h3 id="attach-the-blehci-device-to-bluez">Attach the blehci device to BlueZ</h3>
<p>In a different terminal, attach the blehci device to the BlueZ daemon (substitute the correct /dev filename for ttyUSB0).</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ sudo btattach -B /dev/ttyUSB0 -S 115200
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ sudo btattach -B /dev/ttyUSB0 -S 1000000
Attaching BR/EDR controller to /dev/ttyUSB0
Switched line discipline from 0 to 15
Device index 1 attached
</pre></div>
+<p>The baud rate used to connect to the controller may be changed by overriding the default value of 1000000 in the <code>net/nimble/transport/uart/syscfg.yml</code>. Settings in the serial transport <code>syscfg.yml</code> file can be overridden by a higher priority package such as the application. So, for example, you may set the <code>BLE_HCI_UART_BAUD</code> to a different value in <code>apps/blehci/syscfg.yml</code>.</p>
+<p>If there is no CTS/RTS lines present in the test environment, flow control should be turned off. This can be done with
+-N option for btattach. <strong>Note:</strong> -N option came with BlueZ ver 5.44.</p>
<p><br></p>
<h3 id="start-btmgmt-to-send-commands">Start btmgmt to send commands</h3>
<p>In a third terminal, start btmgmt. This tool allows you to send commands to the blehci controller. Use the index number that shows up when you <code>btattach</code> in the previous step.</p>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/develop/os/tutorials/blinky/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/blinky/index.html b/develop/os/tutorials/blinky/index.html
index 0493a2a..bfc9c0e 100644
--- a/develop/os/tutorials/blinky/index.html
+++ b/develop/os/tutorials/blinky/index.html
@@ -265,17 +265,6 @@
-
-
- <li ><a href="../STM32F303/">Blinky on STM32F303</a>
-
-
- </li>
-
-
-
-
-
<li >
<a href="../nRF52/">Blinky on nRF52</a>
</li>
@@ -556,9 +545,8 @@
<li>Have a computer to build a Mynewt application and connect to the board over USB.</li>
<li>Have a Micro-USB cable to connect the board and the computer.</li>
<li>Install the Newt tool and toolchains (See <a href="../../get_started/get_started/">Basic Setup</a>).</li>
-<li>Install either the Jlink or OpenOCD debugger.</li>
-<li>Create a project space (directory structure) and populate it with the core code repository (apache-mynewt-core) or know how to as explained in <a href="../../../os/get_started/project_create">Creating Your First Project</a>.</li>
-<li>Read the Mynewt OS <a href="../../get_started/vocabulary/">Concepts</a> section.
+<li>Read the Mynewt OS <a href="../../get_started/vocabulary/">Concepts</a> section. </li>
+<li>Create a project space (directory structure) and populate it with the core code repository (apache-mynewt-core) or know how to as explained in <a href="../../../os/get_started/project_create">Creating Your First Project</a>.
<br></li>
</ul>
<h3 id="overview-of-steps">Overview of Steps</h3>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/develop/os/tutorials/blinky_console/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/blinky_console/index.html b/develop/os/tutorials/blinky_console/index.html
index 2e8f957..4761d6b 100644
--- a/develop/os/tutorials/blinky_console/index.html
+++ b/develop/os/tutorials/blinky_console/index.html
@@ -265,17 +265,6 @@
-
-
- <li ><a href="../STM32F303/">Blinky on STM32F303</a>
-
-
- </li>
-
-
-
-
-
<li >
<a href="../nRF52/">Blinky on nRF52</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/develop/os/tutorials/blinky_primo/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/blinky_primo/index.html b/develop/os/tutorials/blinky_primo/index.html
index d37552f..6e9b84a 100644
--- a/develop/os/tutorials/blinky_primo/index.html
+++ b/develop/os/tutorials/blinky_primo/index.html
@@ -265,17 +265,6 @@
-
-
- <li ><a href="../STM32F303/">Blinky on STM32F303</a>
-
-
- </li>
-
-
-
-
-
<li >
<a href="../nRF52/">Blinky on nRF52</a>
</li>
@@ -544,7 +533,7 @@
<ul>
<li>Meet the the prerequisites listed in <a href="../blinky/">Project Blinky</a>.</li>
<li>Have an Arduino Primo board.</li>
-<li>Install a debugger choose one of the two options below: Option 1 requires additional hardware but very easy to set up. </li>
+<li>Install a debugger. Choose one of the two options below: Option 1 requires additional hardware but very easy to set up. </li>
</ul>
<p><br></p>
<h5 id="option-1">Option 1</h5>
@@ -554,20 +543,7 @@
<li>Install the <a href="https://www.segger.com/jlink-software.html">Segger JLINK Software and documentation pack</a>. </li>
</ul>
<h5 id="option-2">Option 2</h5>
-<p>No additional hardware is required but a version of OpenOCD 0.10.0 that is currently in development needs to be installed. A patch for the nRF52 has been applied to the OpenOCD code in development and a tarball has been made available for download <a href="../downloads/openocd-wnrf52.tgz">here</a>. Untar it. From the top of the directory tree ("openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4"), build it using the following configuration:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$./configure --enable-cmsis-dap --enable-openjtag_ftdi --enable-jlink --enable-stlink
-</pre></div>
-
-
-<p>Then run <code>make</code> and <code>sudo make install</code>. This step takes minutes, so be patient.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ openocd -v
-Open On-Chip Debugger 0.10.0-dev-snapshot (2016-05-20-10:43)
-Licensed under GNU GPL v2
-For bug reports, read
- http://openocd.org/doc/doxygen/bugs.html
-</pre></div>
-
-
+<p>This board requires a patch version of OpenOCD 0.10.0 that is in development. See <a href="../../get_started/cross_tools/">Install OpenOCD</a> instructions to install it if you do not have this version installed.</p>
<p>You can now use openocd to upload to Arduino Primo board via the USB port itself.</p>
<h3 id="create-a-project">Create a Project</h3>
<p>Create a new project if you do not have an existing one. You can skip this step and proceed to <a href="#create_targets">create the targets</a> if you already created a project.</p>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/develop/os/tutorials/nRF52/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/nRF52/index.html b/develop/os/tutorials/nRF52/index.html
index b4d86ea..36fbb3c 100644
--- a/develop/os/tutorials/nRF52/index.html
+++ b/develop/os/tutorials/nRF52/index.html
@@ -265,17 +265,6 @@
-
-
- <li ><a href="../STM32F303/">Blinky on STM32F303</a>
-
-
- </li>
-
-
-
-
-
<li class="active">
<a href="./">Blinky on nRF52</a>
</li>
@@ -549,6 +538,7 @@
<li>Eval Kit from Rigado - BMD-300-EVAL-ES</li>
</ul>
</li>
+<li>Install the <a href="https://www.segger.com/jlink-software.html">Segger JLINK Software and documentation pack</a>.</li>
</ul>
<p>This tutorial uses the Nordic nRF52-DK board.</p>
<h3 id="create-a-project">Create a Project</h3>
@@ -716,9 +706,9 @@ $
<ul class="nav nav-pills" style="margin-bottom: 10px">
<li>
- <a href=../pin-wheel-mods/>
+ <a href=../olimex/>
<span class="fa fa-arrow-left"></span>
- Previous: Pinwheel Blinky
+ Previous: Blinky on Olimex
</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/develop/os/tutorials/nrf52_adc/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/nrf52_adc/index.html b/develop/os/tutorials/nrf52_adc/index.html
index 9e88c62..933f8f4 100644
--- a/develop/os/tutorials/nrf52_adc/index.html
+++ b/develop/os/tutorials/nrf52_adc/index.html
@@ -526,7 +526,7 @@ project.repositories:
#
repository.apache-mynewt-core:
type: github
- vers: 1-dev
+ vers: 1-latest
user: apache
repo: incubator-mynewt-core
<span style="background-color: #ffffcc">repository.mynewt_nordic:
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/develop/os/tutorials/olimex/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/olimex/index.html b/develop/os/tutorials/olimex/index.html
index 9e1e071..0780b13 100644
--- a/develop/os/tutorials/olimex/index.html
+++ b/develop/os/tutorials/olimex/index.html
@@ -265,17 +265,6 @@
-
-
- <li ><a href="../STM32F303/">Blinky on STM32F303</a>
-
-
- </li>
-
-
-
-
-
<li >
<a href="../nRF52/">Blinky on nRF52</a>
</li>
@@ -544,9 +533,10 @@
<li>Meet the prerequisites listed in <a href="../blinky/">Project Blinky</a>.</li>
<li>Have a STM32-E407 development board from Olimex. </li>
<li>Have a ARM-USB-TINY-H connector with JTAG interface for debugging ARM microcontrollers (comes with the ribbon cable to hook up to the board)</li>
-<li>Have a USB A-B type cable to connect the debugger to your computer.
-<br></li>
+<li>Have a USB A-B type cable to connect the debugger to your computer.</li>
+<li>Install the <a href="../../../os/get_started/cross_tools/">OpenOCD debugger</a>.</li>
</ul>
+<p><br></p>
<h3 id="create-a-project">Create a Project</h3>
<p>Create a new project if you do not have an existing one. You can skip this step and proceed to <a href="#create_targets">create the targets</a> if you already created a project.</p>
<p>Run the following commands to create a new project:</p>
@@ -747,8 +737,8 @@ Let's double check that it is indeed booting from flash and making the LED blink
</li>
<li class="pull-right">
- <a href=../STM32F303/>
- Next: Blinky on STM32F303
+ <a href=../nRF52/>
+ Next: Blinky on nRF52
<span class="fa fa-arrow-right"></span>
</a>
[3/7] incubator-mynewt-site git commit: Updates to installation on
Linux and Mac, removal of references to develop branch on website
Posted by ad...@apache.org.
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/latest/mkdocs/search_index.json
----------------------------------------------------------------------
diff --git a/latest/mkdocs/search_index.json b/latest/mkdocs/search_index.json
index 0af8892..4de7a25 100644
--- a/latest/mkdocs/search_index.json
+++ b/latest/mkdocs/search_index.json
@@ -137,17 +137,17 @@
},
{
"location": "/os/get_started/get_started/",
- "text": "Quick Start\n\n\nIf you are curious about Mynewt and want to get a quick feel for the project, you've come to the right place. We have two options for you:\n\n\n\n\nOption 1\n is an easy, self-contained way to get up and running with Mynewt - but has limitations! The Newt tool and build toolchains are all available in a single \nAll-in-one Docker Container\n that you can install on your laptop or computer.\n\n\nHowever, this is not a long-term option since support is not likely for all features useful or critical to embedded systems development. For example, USB device mapping available in the Docker toolkit (used in this Option 1) is no longer available in the new Docker releases. The Docker option is also typically slower than the native install option. \n\n\n Therefore, the recommended option is Option 2 below. \n\n\n\n\nOption 2 (Recommended)\n allows you to install the Newt tool, instances of the Mynewt OS (for simulated targets), and toolchains for develop
ing embedded software (e.g. GNU toolchain) natively on your laptop or computer. We have tried to make the process easy. For example, for the Mac OS we created brew formulas. \n\n\nYou want this option if you are familiar with such environments or are concerned about performance on your machine. Follow the instructions to \ninstall native tools\n and \ninstall cross tools for ARM\n if you prefer this option.\n\n\n\n\nYou can then proceed with the instructions on how to \n* \nCreate Your First Project\n - on simulated hardware.\n\n\nUpon successful start, several tutorials await your eager attention!\n\n\n\n\nSend us an email on the dev@ mailing list if you have comments or suggestions!\n If you haven't joined the mailing list, you will find the links \nhere\n.",
+ "text": "Quick Start\n\n\nIf you are curious about Mynewt and want to get a quick feel for the project, you've come to the right place. We have two options for you:\n\n\n\n\nOption 1 (Recommended)\n allows you to install the Newt tool, instances of the Mynewt OS (for simulated targets), and toolchains for developing embedded software (e.g. GNU toolchain) natively on your laptop or computer. We have tried to make the process easy. For example, for the Mac OS we created brew formulas. \n\n\nWe recommend this option if you are familiar with such environments or are concerned about performance on your machine. Follow the instructions to \ninstall native tools\n and \ninstall cross tools for ARM\n if you prefer this option.\n\n\n\n\nOption 2\n is an easy, self-contained way to get up and running with Mynewt - but has limitations! The Newt tool and build toolchains are all available in a single \nAll-in-one Docker Container\n that you can install on your laptop or computer.\n\
n\nHowever, this is not a long-term option since support is not likely for all features useful or critical to embedded systems development. For example, USB device mapping available in the Docker toolkit is no longer available in the new Docker releases. The Docker option is also typically slower than the native install option. \n\n\n\n\nYou can then proceed with the instructions on how to \n* \nCreate Your First Project\n - on simulated hardware.\n\n\nUpon successful start, several tutorials await your eager attention!\n\n\n\n\nSend us an email on the dev@ mailing list if you have comments or suggestions!\n If you haven't joined the mailing list, you will find the links \nhere\n.",
"title": "toc"
},
{
"location": "/os/get_started/get_started/#quick-start",
- "text": "If you are curious about Mynewt and want to get a quick feel for the project, you've come to the right place. We have two options for you: Option 1 is an easy, self-contained way to get up and running with Mynewt - but has limitations! The Newt tool and build toolchains are all available in a single All-in-one Docker Container that you can install on your laptop or computer. However, this is not a long-term option since support is not likely for all features useful or critical to embedded systems development. For example, USB device mapping available in the Docker toolkit (used in this Option 1) is no longer available in the new Docker releases. The Docker option is also typically slower than the native install option. Therefore, the recommended option is Option 2 below. Option 2 (Recommended) allows you to install the Newt tool, instances of the Mynewt OS (for simulated targets), and toolchains for developing embedded software (e.g. GNU toolchain)
natively on your laptop or computer. We have tried to make the process easy. For example, for the Mac OS we created brew formulas. You want this option if you are familiar with such environments or are concerned about performance on your machine. Follow the instructions to install native tools and install cross tools for ARM if you prefer this option. You can then proceed with the instructions on how to \n* Create Your First Project - on simulated hardware. Upon successful start, several tutorials await your eager attention! Send us an email on the dev@ mailing list if you have comments or suggestions! If you haven't joined the mailing list, you will find the links here .",
+ "text": "If you are curious about Mynewt and want to get a quick feel for the project, you've come to the right place. We have two options for you: Option 1 (Recommended) allows you to install the Newt tool, instances of the Mynewt OS (for simulated targets), and toolchains for developing embedded software (e.g. GNU toolchain) natively on your laptop or computer. We have tried to make the process easy. For example, for the Mac OS we created brew formulas. We recommend this option if you are familiar with such environments or are concerned about performance on your machine. Follow the instructions to install native tools and install cross tools for ARM if you prefer this option. Option 2 is an easy, self-contained way to get up and running with Mynewt - but has limitations! The Newt tool and build toolchains are all available in a single All-in-one Docker Container that you can install on your laptop or computer. However, this is not a long-term option sinc
e support is not likely for all features useful or critical to embedded systems development. For example, USB device mapping available in the Docker toolkit is no longer available in the new Docker releases. The Docker option is also typically slower than the native install option. You can then proceed with the instructions on how to \n* Create Your First Project - on simulated hardware. Upon successful start, several tutorials await your eager attention! Send us an email on the dev@ mailing list if you have comments or suggestions! If you haven't joined the mailing list, you will find the links here .",
"title": "Quick Start"
},
{
"location": "/os/get_started/native_tools/",
- "text": "Installing Native Mynewt Tools\n\n\nThis page shows how to install tools for native Mynewt targets (simulated targets on your laptop/computer) without using a Docker container. In other words, it allows you to run Mynewt OS as a native application on your Mac or Linux machine to simulate a target and use the Newt tool running natively on your machine to manage the simulated target. It also allows you to run the test suites for all packages not requiring HW support. You may choose to do this instead of using the build toolchain and Newt tool available in a Docker container.\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 with, a different compiler is used as
default: 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\nCheck the gcc version you have installed (either using brew or previously installed). The brew-installed version can be checked using \nbrew list gcc\n. The default compiler.yml configuration file in Mynewt expects version 5.x for Mac users, so if the installed version is 6.x and you wish to continue with this newer version, modify the \nmynewt-src-directory\n/repos/apache-mynewt-core/compiler/sim/compiler.yml\n file to change the default \ngcc-5\n defined there to \ngcc-6\n. In other words, replace the lines shown highlighted below:\n\n\n# OS X.\n\ncompiler.path.cc.DARWIN.OVERWRITE: \n/usr/local/bin/gcc-5\n\n\ncompiler.path.as.DARWIN.OVERWRITE: \n/usr/local/bin/gcc-5 -x assembler-with-cpp\n\n\ncompiler.path.objdump.DARWIN.OVERWRITE: \ngobjdump\n\ncompiler.path.objsize.DARWIN.OVERWRITE: \nobjsize\n\ncompiler.path.objcopy.DARWIN.OVERWRITE: \ngobjc
opy\n\n\n\n\n\n\nwith the following:\n\n\ncompiler.path.cc.DARWIN.OVERWRITE: \n/usr/local/bin/gcc-6\n\ncompiler.path.as.DARWIN.OVERWRITE: \n/usr/local/bin/gcc-6 -x assembler-with-cpp\u201d\n\n\n\n\n\n\n\nIn case you wish to use Clang, you can change your \nmynewt-src-directory\n/repos/apache-mynewt-core/compiler/sim/compiler.yml\n to use Clang. Delete the gcc-5 DARWIN.OVERWRITE lines highlighted below.\n\n\n# OS X.\n\ncompiler.path.cc.DARWIN.OVERWRITE: \n/usr/local/bin/gcc-5\n\n\ncompiler.path.as.DARWIN.OVERWRITE: \n/usr/local/bin/gcc-5 -x assembler-with-cpp\n\n\ncompiler.path.objdump.DARWIN.OVERWRITE: \ngobjdump\n\ncompiler.path.objsize.DARWIN.OVERWRITE: \nobjsize\n\ncompiler.path.objcopy.DARWIN.OVERWRITE: \ngobjcopy\n\n\n\n\n\n\n\n\nNOTE:\n Both the newer gcc 6.x and Clang report a few warnings but they can be ignored.\n\n\n\n\nFURTHER NOTE:\n Mynewt developers mostly use gcc 5.x for sim builds; so it may take a little while to fix issues reported by the newer compiler. One option
is to \ndisable warnings\n. To do that, remove the \n-Werror\n flag as an option for the compiler in the \nmynewt-src-directory\n/repos/apache-mynewt-core/compiler/sim/compiler.yml\n file as shown below. \n\n\ncompiler.flags.base: \n\n\n -m32 -Wall -ggdb\n\n\n\n\n\nYou may alternatively choose to \nspecify the precise warnings to ignore\n depending on the error thrown by the compiler. For example, if you see a \n[-Werror=misleading-indentation]\n error while building the sim image, add \n-Wno-misleading-indentation]\n as a compiler flag in the same line from the \nmynewt-src-directory\n/repos/apache-mynewt-core/compiler/sim/compiler.yml\n file.\n\n\ncompiler.flags.base: \n\n\n -m32 -Wall -Werror -ggdb -Wno-misleading-indentation\n\n\n\n\n\nA third option is to simply \ndowngrade to gcc 5.x\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, y
ou 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 installed all the necessary software to build and test code on a simluator running on your Mac or Linux. Proceed to the \nCreate Your First Project\n section.",
+ "text": "Installing Native Mynewt Tools\n\n\nThis page shows how to install tools for native Mynewt targets (simulated targets on your laptop/computer) without using a Docker container. In other words, it allows you to run Mynewt OS as a native application on your Mac or Linux machine to simulate a target and use the Newt tool running natively on your machine to manage the simulated target. It also allows you to run the test suites for all packages not requiring HW support. You may choose to do this instead of using the build toolchain and Newt tool available in a Docker container.\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 with, a different compiler is used as
default: 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\nCheck the gcc version you have installed (either using brew or previously installed). The brew-installed version can be checked using \nbrew list gcc\n. The default compiler.yml configuration file in Mynewt expects version 5.x for Mac users, so if the installed version is 6.x and you wish to continue with this newer version, modify the \nmynewt-src-directory\n/repos/apache-mynewt-core/compiler/sim/compiler.yml\n file to change the default \ngcc-5\n defined there to \ngcc-6\n. In other words, replace the lines shown highlighted below:\n\n\n# OS X.\n\ncompiler.path.cc.DARWIN.OVERWRITE: \ngcc-5\n\n\ncompiler.path.as.DARWIN.OVERWRITE: \ngcc-5\n\n\ncompiler.path.objdump.DARWIN.OVERWRITE: \ngobjdump\n\ncompiler.path.objsize.DARWIN.OVERWRITE: \nobjsize\n\ncompiler.path.objcopy.DARWIN.OVERWRITE: \ngobjcopy\n\n\n\n\n\n\nwith the following:\n\n\ncompiler.p
ath.cc.DARWIN.OVERWRITE: \ngcc-6\n\ncompiler.path.as.DARWIN.OVERWRITE: \ngcc-6\u201d\n\n\n\n\n\n\n\nIn case you wish to use Clang, you can change your \nmynewt-src-directory\n/repos/apache-mynewt-core/compiler/sim/compiler.yml\n to use Clang. Delete the gcc-5 DARWIN.OVERWRITE lines highlighted below.\n\n\n# OS X.\n\ncompiler.path.cc.DARWIN.OVERWRITE: \ngcc-5\n\n\ncompiler.path.as.DARWIN.OVERWRITE: \ngcc-5\n\n\ncompiler.path.objdump.DARWIN.OVERWRITE: \ngobjdump\n\ncompiler.path.objsize.DARWIN.OVERWRITE: \nobjsize\n\ncompiler.path.objcopy.DARWIN.OVERWRITE: \ngobjcopy\n\n\n\n\n\n\n\n\nNOTE:\n Both the newer gcc 6.x and Clang report a few warnings but they can be ignored.\n\n\n\n\nFURTHER NOTE:\n Mynewt developers mostly use gcc 5.x for sim builds; so it may take a little while to fix issues reported by the newer compiler. One option is to \ndisable warnings\n. To do that, remove the \n-Werror\n flag as an option for the compiler in the \nmynewt-src-directory\n/repos/apache-mynewt-core
/compiler/sim/compiler.yml\n file as shown below. \n\n\ncompiler.flags.base: \n\n\n -m32 -Wall -ggdb\n\n\n\n\n\nYou may alternatively choose to \nspecify the precise warnings to ignore\n depending on the error thrown by the compiler. For example, if you see a \n[-Werror=misleading-indentation]\n error while building the sim image, add \n-Wno-misleading-indentation]\n as a compiler flag in the same line from the \nmynewt-src-directory\n/repos/apache-mynewt-core/compiler/sim/compiler.yml\n file.\n\n\ncompiler.flags.base: \n\n\n -m32 -Wall -Werror -ggdb -Wno-misleading-indentation\n\n\n\n\n\nA third option is to simply \ndowngrade to gcc 5.x\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 abili
ty 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 installed all the necessary software to build and test code on a simluator running on your Mac or Linux. Proceed to the \nCreate
Your First Project\n section.",
"title": "toc"
},
{
@@ -167,7 +167,7 @@
},
{
"location": "/os/get_started/native_tools/#install-gcclibc",
- "text": "OS X ships with a C compiler called Clang. To build applications for the Mynewt simulator with, a different compiler is used as default: gcc. $ brew install gcc\n...\n...\n== Summary\n\ud83c\udf7a /usr/local/Cellar/gcc/5.2.0: 1353 files, 248M Check the gcc version you have installed (either using brew or previously installed). The brew-installed version can be checked using brew list gcc . The default compiler.yml configuration file in Mynewt expects version 5.x for Mac users, so if the installed version is 6.x and you wish to continue with this newer version, modify the mynewt-src-directory /repos/apache-mynewt-core/compiler/sim/compiler.yml file to change the default gcc-5 defined there to gcc-6 . In other words, replace the lines shown highlighted below: # OS X. compiler.path.cc.DARWIN.OVERWRITE: /usr/local/bin/gcc-5 compiler.path.as.DARWIN.OVERWRITE: /usr/local/bin/gcc-5 -x assembler-with-cpp compiler.path.objdump.DARWIN.OVERWRITE: gobjdump
\ncompiler.path.objsize.DARWIN.OVERWRITE: objsize \ncompiler.path.objcopy.DARWIN.OVERWRITE: gobjcopy with the following: compiler.path.cc.DARWIN.OVERWRITE: /usr/local/bin/gcc-6 \ncompiler.path.as.DARWIN.OVERWRITE: /usr/local/bin/gcc-6 -x assembler-with-cpp\u201d In case you wish to use Clang, you can change your mynewt-src-directory /repos/apache-mynewt-core/compiler/sim/compiler.yml to use Clang. Delete the gcc-5 DARWIN.OVERWRITE lines highlighted below. # OS X. compiler.path.cc.DARWIN.OVERWRITE: /usr/local/bin/gcc-5 compiler.path.as.DARWIN.OVERWRITE: /usr/local/bin/gcc-5 -x assembler-with-cpp compiler.path.objdump.DARWIN.OVERWRITE: gobjdump \ncompiler.path.objsize.DARWIN.OVERWRITE: objsize \ncompiler.path.objcopy.DARWIN.OVERWRITE: gobjcopy NOTE: Both the newer gcc 6.x and Clang report a few warnings but they can be ignored. FURTHER NOTE: Mynewt developers mostly use gcc 5.x for sim builds; so it may take a little while to fix issues reported by the newer
compiler. One option is to disable warnings . To do that, remove the -Werror flag as an option for the compiler in the mynewt-src-directory /repos/apache-mynewt-core/compiler/sim/compiler.yml file as shown below. compiler.flags.base: -m32 -Wall -ggdb You may alternatively choose to specify the precise warnings to ignore depending on the error thrown by the compiler. For example, if you see a [-Werror=misleading-indentation] error while building the sim image, add -Wno-misleading-indentation] as a compiler flag in the same line from the mynewt-src-directory /repos/apache-mynewt-core/compiler/sim/compiler.yml file. compiler.flags.base: -m32 -Wall -Werror -ggdb -Wno-misleading-indentation A third option is to simply downgrade to gcc 5.x .",
+ "text": "OS X ships with a C compiler called Clang. To build applications for the Mynewt simulator with, a different compiler is used as default: gcc. $ brew install gcc\n...\n...\n== Summary\n\ud83c\udf7a /usr/local/Cellar/gcc/5.2.0: 1353 files, 248M Check the gcc version you have installed (either using brew or previously installed). The brew-installed version can be checked using brew list gcc . The default compiler.yml configuration file in Mynewt expects version 5.x for Mac users, so if the installed version is 6.x and you wish to continue with this newer version, modify the mynewt-src-directory /repos/apache-mynewt-core/compiler/sim/compiler.yml file to change the default gcc-5 defined there to gcc-6 . In other words, replace the lines shown highlighted below: # OS X. compiler.path.cc.DARWIN.OVERWRITE: gcc-5 compiler.path.as.DARWIN.OVERWRITE: gcc-5 compiler.path.objdump.DARWIN.OVERWRITE: gobjdump \ncompiler.path.objsize.DARWIN.OVERWRITE: objsize
\ncompiler.path.objcopy.DARWIN.OVERWRITE: gobjcopy with the following: compiler.path.cc.DARWIN.OVERWRITE: gcc-6 \ncompiler.path.as.DARWIN.OVERWRITE: gcc-6\u201d In case you wish to use Clang, you can change your mynewt-src-directory /repos/apache-mynewt-core/compiler/sim/compiler.yml to use Clang. Delete the gcc-5 DARWIN.OVERWRITE lines highlighted below. # OS X. compiler.path.cc.DARWIN.OVERWRITE: gcc-5 compiler.path.as.DARWIN.OVERWRITE: gcc-5 compiler.path.objdump.DARWIN.OVERWRITE: gobjdump \ncompiler.path.objsize.DARWIN.OVERWRITE: objsize \ncompiler.path.objcopy.DARWIN.OVERWRITE: gobjcopy NOTE: Both the newer gcc 6.x and Clang report a few warnings but they can be ignored. FURTHER NOTE: Mynewt developers mostly use gcc 5.x for sim builds; so it may take a little while to fix issues reported by the newer compiler. One option is to disable warnings . To do that, remove the -Werror flag as an option for the compiler in the mynewt-src-directory /repos/apa
che-mynewt-core/compiler/sim/compiler.yml file as shown below. compiler.flags.base: -m32 -Wall -ggdb You may alternatively choose to specify the precise warnings to ignore depending on the error thrown by the compiler. For example, if you see a [-Werror=misleading-indentation] error while building the sim image, add -Wno-misleading-indentation] as a compiler flag in the same line from the mynewt-src-directory /repos/apache-mynewt-core/compiler/sim/compiler.yml file. compiler.flags.base: -m32 -Wall -Werror -ggdb -Wno-misleading-indentation A third option is to simply downgrade to gcc 5.x .",
"title": "Install gcc/libc"
},
{
@@ -222,83 +222,88 @@
},
{
"location": "/newt/install/newt_linux/",
- "text": "Install newt tool on Linux\n\n\n\n\nGetting your Linux box Ready\n\n\nIf you want to build the \nnewt\n tool from its source code, follow the following steps:\n\n\n1. Install git, libcurl\n\n\n $ sudo apt-get install git \n $ sudo apt-get install libcurl4-gnutls-dev \n\n\n\n\n\nNOTE:\n On 64-bit host, you may also need to install gcc-multilib, if you encounter compilation errors related to 'sys/cdefs.h'\n\n\n\n\n2. Install Go, the programming language\n\n\n\n\n\n\nGo language environment dictates a directory structure. Known in Go parlance as a workspace, it must contain three sibling directories with the directory names src, pkg and bin, as explained below. \n\n\n\n\n\n\nsrc contains Go source files organized into packages (one package per directory),\n\n\n\n\n\n\npkg contains package objects, and\n\n\n\n\n\n\nbin contains executable commands.\n\n\n\n\n\n\nThe GOPATH environment variable specifies the location of your workspace. To setup this work
space environment, create a 'dev' directory and then a 'go' directory under it. Set the GOPATH environment variable to this directory where you will soon clone the \nnewt\n tool repository.\n\n\n\n\n\n\n $ cd $HOME\n $ mkdir -p dev/go \n $ cd dev/go\n $ export GOPATH=`pwd`\n\n\n\n\n\n(Note that you need to add export statements to ~/.bash_profile to export variables permanently. Don't forget to source the file for the change to go into effect.)\n\n\n\n\n $ vi ~/.bash_profile\n $ source ~/.bash_profile\n\n\n\n\n\n\n\n\n\n\n\nNext, install Go. When installed, Go offers you as a developer a language environment (to compile Go code), construct Go packages (to assemble Go packages) and import Go code (from github). In the next step, you will use the Go commands to import \nnewt\n repo into your local Go environment.\n\n\nNote\n: The Newt tool requires Go version 1.7 or later. Currently, the latest Go version that Ubuntu installs is 1.6. You can
run \napt-get install golang-1.7-go\n to install version 1.7. You can also download version 1.7 from \nhttps://golang.org/dl/\n. \n\n\n\n\n\n\n$sudo apt-get install golang-1.7-go\nReading package lists... Done\n ...\nUnpacking golang-1.7-go (1.7.1-2ubuntu1) ...\nSetting up golang-1.7-go (1.7.1-2ubuntu1) ...\n$\n$sudo ln -s /usr/lib/go-1.7/bin/go /usr/bin/go\n$go version\ngo version go1.7.1 linux/amd64\n\n\n\n\n\n \n\n\n3. Create local repository\n\n\n\n\nUse Go commands to copy the directory (currently the ASF incubator directory). Be patient as it may take a minute or two. Check the directories installed.\n\n\n\n\n $ go get mynewt.apache.org/newt/...\n\n\n\n\n\n\n\n\n\nCheck that newt.go is in place.\n\n\n\n\n $ ls $GOPATH/src/mynewt.apache.org/newt\n DISCLAIMER NOTICE newt newtvm viper\n LICENSE README.md newtmgr util yaml\n\n\n\n\n\n\n\n4. Build the Newt tool\n\n\n\n\nUse Go to run the newt.go program to build
the \nnewt\n tool. The command \ngo install\n compiles and writes the resulting executable to an output file named \nnewt\n, which is then installed, along with its dependencies, in $GOPATH/bin. If you get errors it is likely because of path resolution issues. Try \ngo build\n followed by \ngo install\n in that case.\n\n\n\n\n $ cd $GOPATH/src/mynewt.apache.org/newt/newt\n $ go install\n $ ls \n$GOPATH\n/bin/\n newt newtmgr newtvm\n\n\n\n\n\n\n\n\n\nAt this point, you can try using \nnewt\n. For example, check for the version number by typing 'newt version'. See all the possible commands available to a user of newt by typing 'newt -h'.\n\n\n\n\n(Note: If you are going to be modifying the \nnewt\n often and going to be compile the program every time you call it, you will want to store the command in a variable in your .bash_profile. So type in \nexport newt=\"go run $GOPATH/mynewt.apache.org/newt/newt/newt.go\"\n in your .bash_profile and execute it by c
alling \n$newt\n at the prompt instead of \nnewt\n. Essentially, \n$newt\n calls \ngo run\n which runs the compiled binary directly without producing an executable. Don't forget to reload the updated bash profile by typing \nsource ~/.bash_profile\n at the prompt! )\n\n\n $ newt version\n Newt version: 1.0\n $ newt -h\n Newt allows you to create your own embedded application based on the Mynewt \n operating system. Newt provides both build and package management in a single \n tool, which allows you to compose an embedded application, and set of \n projects, and then build the necessary artifacts from those projects. For more \n information on the Mynewt operating system, please visit \n https://mynewt.apache.org/. \n\n Please use the newt help command, and specify the name of the command you want \n help for, for help on how to use a specific command\n\n Usage:\n newt [flags]\n ne
wt [command]\n\n Examples:\n newt\n newt help [\ncommand-name\n]\n For help on \ncommand-name\n. If not specified, print this message.\n\n Available Commands:\n build Build one or more targets\n clean Delete build artifacts for one or more targets\n create-image Add image header to target binary\n debug Open debugger session to target\n info Show project info\n install Install project dependencies\n load Load built target to board\n mfg Manufacturing flash image commands\n new Create a new project\n pkg Create and manage packages in the current workspace\n run build/create-image/download/debug \ntarget\n\n size Size of target components\n sync Synchronize project dependencies\n target Commands to create, delete, confi
gure, and query targets\n test Executes unit tests for one or more packages\n upgrade Upgrade project dependencies\n vals Display valid values for the specified element type(s)\n version Display the Newt version number\n\n Flags:\n -h, --help Help for newt commands\n -j, --jobs int Number of concurrent build jobs (default 8)\n -l, --loglevel string Log level (default \nWARN\n)\n -o, --outfile string Filename to tee output to\n -q, --quiet Be quiet; only display error output\n -s, --silent Be silent; don\nt output anything\n -v, --verbose Enable verbose output when executing commands\n\n Use \nnewt [command] --help\n for more information about a comma\n\n\n\n\n\n\n\n5. Updating the Newt tool\n\n\n\n\nYou will update the newt tool in the same place as you initially installed the newt tool.
\n\n\nStart by updating the git repository of the newt tool (you can change to a different branch using git checkout [branch] if you need to)\n\n\nThen update each of the tools newt, newtmgr and newtvm as needed\n\n\n\n\n $ cd $GOPATH/src/mynewt.apache.org/newt\n $ git pull\n $ cd newt\n $ go install\n $ cd ../newtmgr\n $ go install\n $ cd ../newtvm\n $ go install\n $ ls \n$GOPATH\n/bin/\n newt newtmgr newtvm\n\n\n\n\n\nThat should have updated your newt, newtmgr and newtvm to the latest versions based on the git repository you used.",
+ "text": "Installing Newt on Linux\n\n\nYou can install the latest stable release (1.0.0) of newt from a Debian binary package (amd64) or from a Debian source package. This page shows you how to:\n\n\n\n\nSet up your computer to retrieve Debian packages from the runtimeco debian package repository.\n\n\nInstall the latest stable release version of newt from a Debian binary package. \n\n\nInstall the latest stable release version of newt from a Debian source package.\n\n\n\n\nIf you are running on an amd64 platform, we recommend that you install from the binary package.\n\n\nNote:\n See \nSetting Up an Go Environment to Contribute to Newt and Newtmgr Tools\n if you want to: \n\n\n\n\nUse the newt tool with the latest updates from the master branch. The master branch may be unstable and we recommend that you use the latest stable release version.\n\n\nContribute to the newt tool. \n\n\n\n\n\n\nSetting Up Your Computer to Get Packages from runtimeco\n\n\nThe newt Debian pac
kages are stored in a private repository on \nhttps://github/runtimeco/debian-mynewt\n. \n\n\nNote:\n You will only need to perform these steps only once on your computer.\nThe following steps must be performed on your computer:\n\n\n\n\nAdd the \napt-transport-https\n package to use HTTPS to retrieve packages. \n\n\nDownload the public key for the runtimeco debian repository and import the key into the apt keychain.\n\n\nAdd the repository for the binary and source packages to the apt source list.\n\n\n\n\n\nAdd the apt-transport-https package:\n\n\n$sudo apt-get update\n$sudo apt-get install apt-transport-https\n\n\n\n\n\n\n\nDownload the public key for the runtimeco apt repo (\nNote:\n There is \n-\n after the add):\n\n\nwget -qO - https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/mynewt.gpg.key | sudo apt-key add -\n\n\n\n\n\n\n\nAdd the repository for the binary and source packages to the apt source list:\n\n\n$sudo -s\n[sudo] password for \nuser\n:\nroot$ cat \
n /etc/apt/sources.list.d/mynewt.list \nEOF\ndeb https://raw.githubusercontent.com/runtimeco/debian-package/master latest main\ndeb-src https://raw.githubusercontent.com/runtimeco/debian-package/master latest main\nEOF\n\n\n\n\n\n\nCheck the content of the file:\n\n\nroot$more /etc/apt/sources.list.d//mynewt.list\ndeb https://raw.githubusercontent.com/runtimeco/debian-package/master latest main\ndeb-src https://raw.githubusercontent.com/runtimeco/debian-package/master latest main\n\n\n\n\n\n \n\n\nExit the root shell:\n\n\nroot$exit\n\n\n\n\n\n\n\nInstalling the Latest Release of Newt from a Binary Package\n\n\nFor Linux amd64 platform, you can install the latest stable version (1.0.0) of newt from the newt Debian binary package:\n\n\n$sudo apt-get update\n$sudo apt-get install newt\nReading package lists... Done\nBuilding dependency tree \nReading state information... Done\n\n ...\n\nPreparing to unpack .../newt_1.0.0-1_amd64.deb ...\nUnpacking newt (1.0.0-1) ...\nSettin
g up newt (1.0.0-1) ...\n\n\n\n\n\n\nSee \nChecking the Installed Version of Newt\n to verify that you are using the installed version of newt.\n\n\n\n\nInstalling the Latest Stable Release of Newt from a Source Package\n\n\nIf you are running Linux on a different architecture, you can install the Debian source package for the latest stable release (1.0.0) of newt. The installation of the source package builds the newt binary and creates a Debian binary package that you then install.\n\n\nNote\n: Newt version 1.0.0 has been tested on Linux amd64 platform. Version 1.0.0 does not build on the 32 bit platform but have been fixed for the next release.\n\n\n\n\nInstalling Go 1.7\n\n\nYou need Go version 1.7 or higher to build Newt version 1.0.0. Currently, the latest Go version that Ubuntu installs is 1.6. Run \ngo version\n to check if you have Go 1.7 installed. \n\n\n\n\nInstall Go version 1.7:\n\n\n$sudo apt-get install golang-1.7-go\nReading package lists... Done\n ...\nUnpacki
ng golang-1.7-go (1.7.1-2ubuntu1) ...\nSetting up golang-1.7-go (1.7.1-2ubuntu1) ...\n$\n$sudo ln -sf ../lib/go-1.7/bin/go /usr/bin/go\n$go version\ngo version go1.7.1 linux/amd64\n\n\n\n\n\nYou can also download version 1.7 from \nhttps://golang.org/dl/\n. \n\n\n\n\nInstalling from the Source Package\n\n\nCreate a directory and change into the directory, download the source package, and build a binary package from the source package:\n\n\nmkdir newt_source\n$cd newt_source\n$sudo apt-get --build source newt\n[sudo] password for \nuser\n: \nReading package lists... Done\nNeed to get 1,866 kB of source archives.\nGet:1 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newt 1.0.0-1 (dsc) [795 B]\nGet:2 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newt 1.0.0-1 (tar) [1,864 kB]\nGet:3 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newt 1.0.0-1 (diff) [2,000 B]\nFetched 1,866 kB in 1s (1,222 kB/s)\nd
pkg-source: warning: extracting unsigned source package (newt_1.0.0-1.dsc)\ndpkg-source: info: extracting newt in newt-1.0.0\ndpkg-source: info: unpacking newt_1.0.0.orig.tar.gz\ndpkg-source: info: unpacking newt_1.0.0-1.debian.tar.xz\n\n ...\n\ndpkg-deb: building package \nnewt\n in \n../newt_1.0.0-1_amd64.deb\n.\n dpkg-genchanges --build=any,all \n../newt_1.0.0-1_amd64.changes\ndpkg-genchanges: info: binary-only upload (no source code included)\n dpkg-source --after-build newt-1.0.0\ndpkg-buildpackage: info: binary-only upload (no source included)\nW: Can\nt drop privileges for downloading as file \nnewt_1.0.0-1.dsc\n couldn\nt be accessed by user \n_apt\n. - pkgAcquire::Run (13: Permission denied)\n\n\n\n\n\nNote:\n You can ignore the \"Permission denied: warning message at the end of the command.\n\n\n\nInstall the newt binary package that is created from the source package:\n\n\n$sudo dpkg -i newt_1.0.0-1_amd64.deb \nSelecting previously unselected package newt.\n(Rea
ding database ... 252969 files and directories currently installed.)\nPreparing to unpack newt_1.0.0-1_amd64.deb ...\nUnpacking newt (1.0.0-1) ...\nSetting up newt (1.0.0-1) ...\n\n\n\n\n\n\n\n Checking the Installed Version of Newt\n\n\nAfter you have installed newt from either a Debian binary or source package, check that you are using the installed version of newt from \n/usr/bin\n. \n\n\nCheck the modification time of the binary and the newt tool that you are using:\n\n\n$ls -l /usr/bin/newt\n-rwxr-xr-x 1 root root 6919280 Apr 22 10:09 /usr/bin/newt\n$which newt\n/usr/bin/newt\n$newt version\nApache Newt (incubating) version: 1.0.0\n\n\n\n\n\nNote:\n If you previously built newt from source and the output of \nwhich newt\n shows \"$GOPATH/bin/newt\", you will need to move \"$GOPATH/bin\" after \"/usr/bin\" in your $PATH and export your $PATH.\n\n\n\nGet information about newt:\n\n\n$newt\nNewt allows you to create your own embedded application based on the Mynewt\noperating syst
em. Newt provides both build and package management in a single\ntool, which allows you to compose an embedded application, and set of\nprojects, and then build the necessary artifacts from those projects. For more\ninformation on the Mynewt operating system, please visit\nhttps://mynewt.apache.org/.\n\nPlease use the newt help command, and specify the name of the command you want\nhelp for, for help on how to use a specific command\n\nUsage:\n newt [flags]\n newt [command]\n\nExamples:\n newt\n newt help [\ncommand-name\n]\n For help on \ncommand-name\n. If not specified, print this message.\n\nAvailable Commands:\n build Build one or more targets\n clean Delete build artifacts for one or more targets\n create-image Add image header to target binary\n debug Open debugger session to target\n info Show project info\n install Install project dependencies\n load Load built target to board\n mfg Manufacturing flash image
commands\n new Create a new project\n pkg Create and manage packages in the current workspace\n run build/create-image/download/debug \ntarget\n\n size Size of target components\n sync Synchronize project dependencies\n target Commands to create, delete, configure, and query targets\n test Executes unit tests for one or more packages\n upgrade Upgrade project dependencies\n vals Display valid values for the specified element type(s)\n version Display the Newt version number\n\nFlags:\n -h, --help Help for newt commands\n -j, --jobs int Number of concurrent build jobs (default 8)\n -l, --loglevel string Log level (default \nWARN\n)\n -o, --outfile string Filename to tee output to\n -q, --quiet Be quiet; only display error output\n -s, --silent Be silent; don\nt output anything\n -v, --verbose Enable verbose output when executing comm
ands\n\nUse \nnewt [command] --help\n for more information about a command.",
"title": "Install Newt on Linux"
},
{
- "location": "/newt/install/newt_linux/#install-newt-tool-on-linux",
- "text": "",
- "title": "Install newt tool on Linux"
- },
- {
- "location": "/newt/install/newt_linux/#getting-your-linux-box-ready",
- "text": "If you want to build the newt tool from its source code, follow the following steps:",
- "title": "Getting your Linux box Ready"
+ "location": "/newt/install/newt_linux/#installing-newt-on-linux",
+ "text": "You can install the latest stable release (1.0.0) of newt from a Debian binary package (amd64) or from a Debian source package. This page shows you how to: Set up your computer to retrieve Debian packages from the runtimeco debian package repository. Install the latest stable release version of newt from a Debian binary package. Install the latest stable release version of newt from a Debian source package. If you are running on an amd64 platform, we recommend that you install from the binary package. Note: See Setting Up an Go Environment to Contribute to Newt and Newtmgr Tools if you want to: Use the newt tool with the latest updates from the master branch. The master branch may be unstable and we recommend that you use the latest stable release version. Contribute to the newt tool.",
+ "title": "Installing Newt on Linux"
},
{
- "location": "/newt/install/newt_linux/#1-install-git-libcurl",
- "text": "$ sudo apt-get install git \n $ sudo apt-get install libcurl4-gnutls-dev NOTE: On 64-bit host, you may also need to install gcc-multilib, if you encounter compilation errors related to 'sys/cdefs.h'",
- "title": "1. Install git, libcurl"
+ "location": "/newt/install/newt_linux/#setting-up-your-computer-to-get-packages-from-runtimeco",
+ "text": "The newt Debian packages are stored in a private repository on https://github/runtimeco/debian-mynewt . Note: You will only need to perform these steps only once on your computer.\nThe following steps must be performed on your computer: Add the apt-transport-https package to use HTTPS to retrieve packages. Download the public key for the runtimeco debian repository and import the key into the apt keychain. Add the repository for the binary and source packages to the apt source list. \nAdd the apt-transport-https package: $sudo apt-get update\n$sudo apt-get install apt-transport-https Download the public key for the runtimeco apt repo ( Note: There is - after the add): wget -qO - https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/mynewt.gpg.key | sudo apt-key add - Add the repository for the binary and source packages to the apt source list: $sudo -s\n[sudo] password for user :\nroot$ cat /etc/apt/sources.list.d/mynewt.lis
t EOF\ndeb https://raw.githubusercontent.com/runtimeco/debian-package/master latest main\ndeb-src https://raw.githubusercontent.com/runtimeco/debian-package/master latest main\nEOF \nCheck the content of the file: root$more /etc/apt/sources.list.d//mynewt.list\ndeb https://raw.githubusercontent.com/runtimeco/debian-package/master latest main\ndeb-src https://raw.githubusercontent.com/runtimeco/debian-package/master latest main Exit the root shell: root$exit",
+ "title": "Setting Up Your Computer to Get Packages from runtimeco"
},
{
- "location": "/newt/install/newt_linux/#2-install-go-the-programming-language",
- "text": "Go language environment dictates a directory structure. Known in Go parlance as a workspace, it must contain three sibling directories with the directory names src, pkg and bin, as explained below. src contains Go source files organized into packages (one package per directory), pkg contains package objects, and bin contains executable commands. The GOPATH environment variable specifies the location of your workspace. To setup this workspace environment, create a 'dev' directory and then a 'go' directory under it. Set the GOPATH environment variable to this directory where you will soon clone the newt tool repository. $ cd $HOME\n $ mkdir -p dev/go \n $ cd dev/go\n $ export GOPATH=`pwd` (Note that you need to add export statements to ~/.bash_profile to export variables permanently. Don't forget to source the file for the change to go into effect.) $ vi ~/.bash_profile\n $ source ~/.bash_profile
Next, install Go. When installed, Go offers you as a developer a language environment (to compile Go code), construct Go packages (to assemble Go packages) and import Go code (from github). In the next step, you will use the Go commands to import newt repo into your local Go environment. Note : The Newt tool requires Go version 1.7 or later. Currently, the latest Go version that Ubuntu installs is 1.6. You can run apt-get install golang-1.7-go to install version 1.7. You can also download version 1.7 from https://golang.org/dl/ . $sudo apt-get install golang-1.7-go\nReading package lists... Done\n ...\nUnpacking golang-1.7-go (1.7.1-2ubuntu1) ...\nSetting up golang-1.7-go (1.7.1-2ubuntu1) ...\n$\n$sudo ln -s /usr/lib/go-1.7/bin/go /usr/bin/go\n$go version\ngo version go1.7.1 linux/amd64",
- "title": "2. Install Go, the programming language"
+ "location": "/newt/install/newt_linux/#installing-the-latest-release-of-newt-from-a-binary-package",
+ "text": "For Linux amd64 platform, you can install the latest stable version (1.0.0) of newt from the newt Debian binary package: $sudo apt-get update\n$sudo apt-get install newt\nReading package lists... Done\nBuilding dependency tree \nReading state information... Done\n\n ...\n\nPreparing to unpack .../newt_1.0.0-1_amd64.deb ...\nUnpacking newt (1.0.0-1) ...\nSetting up newt (1.0.0-1) ... \nSee Checking the Installed Version of Newt to verify that you are using the installed version of newt.",
+ "title": "Installing the Latest Release of Newt from a Binary Package"
},
{
- "location": "/newt/install/newt_linux/#3-create-local-repository",
- "text": "Use Go commands to copy the directory (currently the ASF incubator directory). Be patient as it may take a minute or two. Check the directories installed. $ go get mynewt.apache.org/newt/... Check that newt.go is in place. $ ls $GOPATH/src/mynewt.apache.org/newt\n DISCLAIMER NOTICE newt newtvm viper\n LICENSE README.md newtmgr util yaml",
- "title": "3. Create local repository"
+ "location": "/newt/install/newt_linux/#installing-the-latest-stable-release-of-newt-from-a-source-package",
+ "text": "If you are running Linux on a different architecture, you can install the Debian source package for the latest stable release (1.0.0) of newt. The installation of the source package builds the newt binary and creates a Debian binary package that you then install. Note : Newt version 1.0.0 has been tested on Linux amd64 platform. Version 1.0.0 does not build on the 32 bit platform but have been fixed for the next release.",
+ "title": "Installing the Latest Stable Release of Newt from a Source Package"
},
{
- "location": "/newt/install/newt_linux/#4-build-the-newt-tool",
- "text": "Use Go to run the newt.go program to build the newt tool. The command go install compiles and writes the resulting executable to an output file named newt , which is then installed, along with its dependencies, in $GOPATH/bin. If you get errors it is likely because of path resolution issues. Try go build followed by go install in that case. $ cd $GOPATH/src/mynewt.apache.org/newt/newt\n $ go install\n $ ls $GOPATH /bin/\n newt newtmgr newtvm At this point, you can try using newt . For example, check for the version number by typing 'newt version'. See all the possible commands available to a user of newt by typing 'newt -h'. (Note: If you are going to be modifying the newt often and going to be compile the program every time you call it, you will want to store the command in a variable in your .bash_profile. So type in export newt=\"go run $GOPATH/mynewt.apache.org/newt/newt/newt.go\" in your .bash_profile and
execute it by calling $newt at the prompt instead of newt . Essentially, $newt calls go run which runs the compiled binary directly without producing an executable. Don't forget to reload the updated bash profile by typing source ~/.bash_profile at the prompt! ) $ newt version\n Newt version: 1.0\n $ newt -h\n Newt allows you to create your own embedded application based on the Mynewt \n operating system. Newt provides both build and package management in a single \n tool, which allows you to compose an embedded application, and set of \n projects, and then build the necessary artifacts from those projects. For more \n information on the Mynewt operating system, please visit \n https://mynewt.apache.org/. \n\n Please use the newt help command, and specify the name of the command you want \n help for, for help on how to use a specific command\n\n Usage:\n newt [flags]\n n
ewt [command]\n\n Examples:\n newt\n newt help [ command-name ]\n For help on command-name . If not specified, print this message.\n\n Available Commands:\n build Build one or more targets\n clean Delete build artifacts for one or more targets\n create-image Add image header to target binary\n debug Open debugger session to target\n info Show project info\n install Install project dependencies\n load Load built target to board\n mfg Manufacturing flash image commands\n new Create a new project\n pkg Create and manage packages in the current workspace\n run build/create-image/download/debug target \n size Size of target components\n sync Synchronize project dependencies\n target Commands to create, delete, configure,
and query targets\n test Executes unit tests for one or more packages\n upgrade Upgrade project dependencies\n vals Display valid values for the specified element type(s)\n version Display the Newt version number\n\n Flags:\n -h, --help Help for newt commands\n -j, --jobs int Number of concurrent build jobs (default 8)\n -l, --loglevel string Log level (default WARN )\n -o, --outfile string Filename to tee output to\n -q, --quiet Be quiet; only display error output\n -s, --silent Be silent; don t output anything\n -v, --verbose Enable verbose output when executing commands\n\n Use newt [command] --help for more information about a comma",
- "title": "4. Build the Newt tool"
+ "location": "/newt/install/newt_linux/#installing-go-17",
+ "text": "You need Go version 1.7 or higher to build Newt version 1.0.0. Currently, the latest Go version that Ubuntu installs is 1.6. Run go version to check if you have Go 1.7 installed. Install Go version 1.7: $sudo apt-get install golang-1.7-go\nReading package lists... Done\n ...\nUnpacking golang-1.7-go (1.7.1-2ubuntu1) ...\nSetting up golang-1.7-go (1.7.1-2ubuntu1) ...\n$\n$sudo ln -sf ../lib/go-1.7/bin/go /usr/bin/go\n$go version\ngo version go1.7.1 linux/amd64 You can also download version 1.7 from https://golang.org/dl/ .",
+ "title": "Installing Go 1.7"
},
{
- "location": "/newt/install/newt_linux/#5-updating-the-newt-tool",
- "text": "You will update the newt tool in the same place as you initially installed the newt tool. Start by updating the git repository of the newt tool (you can change to a different branch using git checkout [branch] if you need to) Then update each of the tools newt, newtmgr and newtvm as needed $ cd $GOPATH/src/mynewt.apache.org/newt\n $ git pull\n $ cd newt\n $ go install\n $ cd ../newtmgr\n $ go install\n $ cd ../newtvm\n $ go install\n $ ls $GOPATH /bin/\n newt newtmgr newtvm That should have updated your newt, newtmgr and newtvm to the latest versions based on the git repository you used.",
- "title": "5. Updating the Newt tool"
+ "location": "/newt/install/newt_linux/#installing-from-the-source-package",
+ "text": "Create a directory and change into the directory, download the source package, and build a binary package from the source package: mkdir newt_source\n$cd newt_source\n$sudo apt-get --build source newt\n[sudo] password for user : \nReading package lists... Done\nNeed to get 1,866 kB of source archives.\nGet:1 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newt 1.0.0-1 (dsc) [795 B]\nGet:2 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newt 1.0.0-1 (tar) [1,864 kB]\nGet:3 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newt 1.0.0-1 (diff) [2,000 B]\nFetched 1,866 kB in 1s (1,222 kB/s)\ndpkg-source: warning: extracting unsigned source package (newt_1.0.0-1.dsc)\ndpkg-source: info: extracting newt in newt-1.0.0\ndpkg-source: info: unpacking newt_1.0.0.orig.tar.gz\ndpkg-source: info: unpacking newt_1.0.0-1.debian.tar.xz\n\n ...\n\ndpkg-deb: building package newt in
../newt_1.0.0-1_amd64.deb .\n dpkg-genchanges --build=any,all ../newt_1.0.0-1_amd64.changes\ndpkg-genchanges: info: binary-only upload (no source code included)\n dpkg-source --after-build newt-1.0.0\ndpkg-buildpackage: info: binary-only upload (no source included)\nW: Can t drop privileges for downloading as file newt_1.0.0-1.dsc couldn t be accessed by user _apt . - pkgAcquire::Run (13: Permission denied) Note: You can ignore the \"Permission denied: warning message at the end of the command. \nInstall the newt binary package that is created from the source package: $sudo dpkg -i newt_1.0.0-1_amd64.deb \nSelecting previously unselected package newt.\n(Reading database ... 252969 files and directories currently installed.)\nPreparing to unpack newt_1.0.0-1_amd64.deb ...\nUnpacking newt (1.0.0-1) ...\nSetting up newt (1.0.0-1) ...",
+ "title": "Installing from the Source Package"
},
{
"location": "/os/get_started/cross_tools/",
- "text": "Installing Cross Tools for ARM\n\n\nThis page shows how to install tools on your laptop/computer to use for direct communication (e.g. for debugging) with some ARM based HW platforms running Apache Mynewt. You will also have to use the Newt tool installed to run natively on your machine. You may choose to do this instead of using the build toolchain and Newt tool available in a Docker container.\n\n\nThis page provides guidance for installing the tools directly on your MAC and Linux machine. See the relevant sections below.\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 upda
te\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 you
r\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\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/bin/openocd -\n ../Cellar/open-ocd/0.9.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/~team-gcc-arm-embedded/+archive/ubuntu/ppa\n.\n\n\n$ sudo apt-get remove binutils-arm-none-eabi gcc-arm-none-eabi \n$ sudo add-apt-repository ppa:team-gcc-arm-embedded/ppa\n$ sudo apt-get update \n$ sudo apt-get install gcc-arm-none-eabi\n$ sudo apt-get install gdb-arm-none-eabi\n\n\n\n\n\n\n\nInstall OpenOCD\n\n\nOpenOCD (Open On-Chip D
ebugger) 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.",
+ "text": "Installing Cross Tools for ARM\n\n\nThis page shows how to install tools on your laptop/computer to use for direct communication (e.g. for debugging) with some ARM based HW platforms running Apache Mynewt. It shows you how to install the following tools for Mac OS X and Linux:\n\n\n\n\nARM Cross toolchain\n\n\nDebugger to load and debug your device\n\n\n\n\n\n\nInstall ARM Cross Toolchain\n\n\nInstall ARM Toolchain For Mac OS X\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/embe
dded-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 ARM Toolchain For Linux\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/~team-gcc-arm-embedded/+archive/ubuntu/ppa\n.\n\n\n$
sudo apt-get remove binutils-arm-none-eabi gcc-arm-none-eabi \n$ sudo add-apt-repository ppa:team-gcc-arm-embedded/ppa\n$ sudo apt-get update \n$ sudo apt-get install gcc-arm-none-eabi\n$ sudo apt-get install gdb-arm-none-eabi\n\n\n\n\n\n\n\nInstall Debugger\n\n\nMynewt uses, depending on the board, either the OpenOCD or SEGGER J-Link debugger. \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\nOpenOCD version 0.10.0 with nrf52 support is required. A binary for this version is available to download for Mac OS and Linux.\n\n\n\n\nInstall OpenOCD on Mac OS\n\n\nStep 1: Download the \nbinary tarball for Mac OS\n.\n\n\nStep 2: Change to the root directory: \n\n\n$cd / \n\n\n\n\n\n\nStep 3: Untar the tarball and install into \n /usr/local/
bin\n. You will need to replace \n ~/Downloads \n with the directory that the tarball is downloaded to. \n\n\nsudo tar -xf ~/Downloads/openocd-bin-0.10.0-MacOS.tgz ` \n\n\n\n\n\n\nStep 4: Check the OpenOCD version you are using: \n\n\n$which openocd\n/usr/local/bin/openocd\n$openocd -v\nOpen On-Chip Debugger 0.10.0\nLicensed under GNU GPL v2\nFor bug reports, read\nhttp://openocd.org/doc/doxygen/bugs.html\n\n\n\n\n\nYou should see version: \n0.10.0\n. \n\n\n\n\nInstall OpenOCD on Linux\n\n\nStep 1: Download the \nbinary tarball for Linux\n\n\nStep 2: Change to the root directory: \n\n\n$cd / \n\n\n\n\n\n\nStep 3: Untar the tarball and install into \n /usr/local/bin\n. You will need to replace \n ~/Downloads \n with the directory that the tarball is downloaded to. \n\n\n Note:\n You must specify the -p option for the tar command.\n\n\n$sudo tar -xpf ~/Downloads/openocd-bin-0.10.0-Linux.tgz\n\n\n\n\n\n\nStep 4: Check the OpenOCD version you are using: \n\n\n$which openocd\n/usr/lo
cal/bin/openocd\n$openocd -v\nOpen On-Chip Debugger 0.10.0\nLicensed under GNU GPL v2\nFor bug reports, read\nhttp://openocd.org/doc/doxygen/bugs.html\n\n\n\n\n\nYou should see version: \n0.10.0\n. \n\n\nIf you see any of these error messages:\n\n\n\n\n\n\nopenocd: error while loading shared libraries: libhidapi-hidraw.so.0: cannot open shared object file: No such file or directory\n\n\n\n\n\n\nopenocd: error while loading shared libraries: libusb-1.0.so.0: cannot open shared object file: No such file or directory \n\n\n\n\n\n\nrun the following command to install the libraries: \n\n\n$sudo apt-get install libhidapi-dev:i386\n\n\n\n\n\n\n\nInstall SEGGAR J-Link\n\n\nYou can download and install Segger J-LINK Software and documentation pack from \nSEGGER\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 on your laptop/computer to use for direct communication (e.g. for debugging) with some ARM based HW platforms running Apache Mynewt. You will also have to use the Newt tool installed to run natively on your machine. You may choose to do this instead of using the build toolchain and Newt tool available in a Docker container. This page provides guidance for installing the tools directly on your MAC and Linux machine. See the relevant sections below.",
+ "text": "This page shows how to install tools on your laptop/computer to use for direct communication (e.g. for debugging) with some ARM based HW platforms running Apache Mynewt. It shows you how to install the following tools for Mac OS X and Linux: ARM Cross toolchain Debugger to load and debug your device",
"title": "Installing Cross Tools for ARM"
},
{
- "location": "/os/get_started/cross_tools/#install-arm-cross-tools-in-mac-os-x",
+ "location": "/os/get_started/cross_tools/#install-arm-cross-toolchain",
"text": "",
- "title": "Install ARM Cross tools in Mac OS X"
+ "title": "Install ARM Cross Toolchain"
},
{
- "location": "/os/get_started/cross_tools/#install-tool-chain",
+ "location": "/os/get_started/cross_tools/#install-arm-toolchain-for-mac-os-x",
"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"
+ "title": "Install ARM Toolchain For Mac OS X"
+ },
+ {
+ "location": "/os/get_started/cross_tools/#install-arm-toolchain-for-linux",
+ "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/~team-gcc-arm-embedded/+archive/ubuntu/ppa . $ sudo apt-get remove binutils-arm-none-eabi gcc-arm-none-eabi \n$ sudo add-apt-repository ppa:team-gcc-arm-embedded/ppa\n$ sudo apt-get update \n$ sudo apt-get install gcc-arm-none-eabi\n$ sudo apt-get install gdb-arm-none-eabi",
+ "title": "Install ARM Toolchain For Linux"
+ },
+ {
+ "location": "/os/get_started/cross_tools/#install-debugger",
+ "text": "Mynewt uses, depending on the board, either the OpenOCD or SEGGER J-Link debugger.",
+ "title": "Install Debugger"
},
{
"location": "/os/get_started/cross_tools/#install-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 . $ 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.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 . OpenOCD version 0.10.0 with nrf52 support is required. A binary for this version is available to download for Mac OS and Linux.",
"title": "Install OpenOCD"
},
{
- "location": "/os/get_started/cross_tools/#install-arm-cross-arm-tools-for-linux",
- "text": "",
- "title": "Install ARM cross arm tools for Linux"
+ "location": "/os/get_started/cross_tools/#install-openocd-on-mac-os",
+ "text": "Step 1: Download the binary tarball for Mac OS . Step 2: Change to the root directory: $cd / \nStep 3: Untar the tarball and install into /usr/local/bin . You will need to replace ~/Downloads with the directory that the tarball is downloaded to. sudo tar -xf ~/Downloads/openocd-bin-0.10.0-MacOS.tgz ` \nStep 4: Check the OpenOCD version you are using: $which openocd\n/usr/local/bin/openocd\n$openocd -v\nOpen On-Chip Debugger 0.10.0\nLicensed under GNU GPL v2\nFor bug reports, read\nhttp://openocd.org/doc/doxygen/bugs.html You should see version: 0.10.0 .",
+ "title": "Install OpenOCD on Mac OS"
},
{
- "location": "/os/get_started/cross_tools/#install-tool-chain_1",
- "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/~team-gcc-arm-embedded/+archive/ubuntu/ppa . $ sudo apt-get remove binutils-arm-none-eabi gcc-arm-none-eabi \n$ sudo add-apt-repository ppa:team-gcc-arm-embedded/ppa\n$ sudo apt-get update \n$ sudo apt-get install gcc-arm-none-eabi\n$ sudo apt-get install gdb-arm-none-eabi",
- "title": "Install Tool Chain"
+ "location": "/os/get_started/cross_tools/#install-openocd-on-linux",
+ "text": "Step 1: Download the binary tarball for Linux Step 2: Change to the root directory: $cd / \nStep 3: Untar the tarball and install into /usr/local/bin . You will need to replace ~/Downloads with the directory that the tarball is downloaded to. Note: You must specify the -p option for the tar command. $sudo tar -xpf ~/Downloads/openocd-bin-0.10.0-Linux.tgz \nStep 4: Check the OpenOCD version you are using: $which openocd\n/usr/local/bin/openocd\n$openocd -v\nOpen On-Chip Debugger 0.10.0\nLicensed under GNU GPL v2\nFor bug reports, read\nhttp://openocd.org/doc/doxygen/bugs.html You should see version: 0.10.0 . If you see any of these error messages: openocd: error while loading shared libraries: libhidapi-hidraw.so.0: cannot open shared object file: No such file or directory openocd: error while loading shared libraries: libusb-1.0.so.0: cannot open shared object file: No such file or directory run the following command to instal
l the libraries: $sudo apt-get install libhidapi-dev:i386",
+ "title": "Install OpenOCD on Linux"
},
{
- "location": "/os/get_started/cross_tools/#install-openocd_1",
- "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"
+ "location": "/os/get_started/cross_tools/#install-seggar-j-link",
+ "text": "You can download and install Segger J-LINK Software and documentation pack from SEGGER .",
+ "title": "Install SEGGAR J-Link"
},
{
"location": "/os/get_started/docker/",
@@ -347,7 +352,7 @@
},
{
"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\n\n\nPre-Requisites\n\n\n\n\nNewt:\n\n\nIf you have taken the Docker route, you have already installed Newt.\n\n\nIf you have taken the native install route, you have to ensure that you have installed the Newt tool following the instructions for \nMac\n or \nLinux\n as appropriate, and that the \nnewt\n command is in your system path. \n\n\n\n\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 crea
ted.\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\nNote\n: If you do not have \ntree\n, install it by running \nbrew install tree\n.\n\n\n$ cd myproj\n$ tree \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\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\n6 directories, 11 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 \ntarget\n 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 internally 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\nNOTE:\n By default newt uses the code in the master branch. This is the latest stable\ncode
for newt. If you need to use a different branch, you can set this in the project.yml\nfile. \n\n\nrepository.apache-mynewt-core:\n type: github\n vers: 1-latest\n user: apache\n repo: incubator-mynewt-core\n\n\n\n\n\nChanging to 1-dev will put you on the develop branch. \nThe Develop Branch may not be stable and you may encounter bugs or other problems.\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\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 v
iew them by issuing the following commands in the base directory of the new project. The actual output will depend on what is in the latest 'master' branch you have pulled from.\n\n\n$ tree -L 2 repos/apache-mynewt-core/\n\nrepos/apache-mynewt-core/\n\u251c\u2500\u2500 CODING_STANDARDS.md\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 RELEASE_NOTES.md\n\u251c\u2500\u2500 apps\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 blecent\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 blehci\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 bleprph\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 bleprph_oic\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 blesplit\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 bletest\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 bletiny\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 bleuart\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 boot\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 fat2native\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 ffs2native\n\u25
02\u00a0\u00a0 \u251c\u2500\u2500 ocf_sample\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 slinky\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 slinky_oic\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 spitest\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 splitty\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 test\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 testbench\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 timtest\n\u251c\u2500\u2500 boot\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 boot_serial\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 bootutil\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 split\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 split_app\n\u251c\u2500\u2500 compiler\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 arm-none-eabi-m0\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 arm-none-eabi-m4\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 gdbmacros\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 mips\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 sim\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 sim-mips\n\u251c\u2500\u2500 crypto\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 mbedtls\n\u25
02\u00a0\u00a0 \u2514\u2500\u2500 tinycrypt\n\u251c\u2500\u2500 docs\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 doxygen.xml\n\u251c\u2500\u2500 encoding\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 base64\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 cborattr\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 json\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 tinycbor\n\u251c\u2500\u2500 fs\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 disk\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 fatfs\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 fcb\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 cmsis-core\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 drivers\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 hal\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 mcu\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 scripts\n\u251c\u2500\u2500 kernel\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 os\n\u251c\u2500\u2500 libc\n\u2502\u00a0\u00a0 \u2514\u250
0\u2500 baselibc\n\u251c\u2500\u2500 mgmt\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 imgmgr\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 mgmt\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 newtmgr\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 oicmgr\n\u251c\u2500\u2500 net\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 ip\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 nimble\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 oic\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 wifi\n\u251c\u2500\u2500 project.yml\n\u251c\u2500\u2500 repository.yml\n\u251c\u2500\u2500 sys\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 config\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 console\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 coredump\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 defs\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 flash_map\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 id\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 log\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 mfg\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 reboot\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 shell\n\u2502\u00a0\u00a0 \u251c\u2
500\u2500 stats\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 sysinit\n\u251c\u2500\u2500 targets\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 unittest\n\u251c\u2500\u2500 test\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 crash_test\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 flash_test\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 runtest\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 testutil\n\u251c\u2500\u2500 time\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 datetime\n\u2514\u2500\u2500 util\n \u251c\u2500\u2500 cbmem\n \u251c\u2500\u2500 crc\n \u2514\u2500\u2500 mem\n\n94 directories, 9 files\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\nYou have already built your first basic project. You can ask Newt to execute the unit tests in a package. For example, to test the \nsys/config\n package in the \napache-mynewt-core\n repo, call newt as shown below.\n\n\n$ newt test @apache-mynewt-core/sys/config\
nTesting package @apache-mynewt-core/sys/config/test-fcb\nCompiling bootutil_misc.c\nCompiling image_ec.c\nCompiling image_rsa.c\nCompiling image_validate.c\n\n ...\n\nLinking ~/dev/myproj/bin/targets/unittest/sys_config_test-fcb/app/sys/config/test-fcb/sys_config_test-fcb.elf\nExecuting test: ~/dev/myproj/bin/targets/unittest/sys_config_test-fcb/app/sys/config/test-fcb/sys_config_test-fcb.elf\nTesting package @apache-mynewt-core/sys/config/test-nffs\nCompiling repos/apache-mynewt-core/encoding/base64/src/hex.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_cli.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_dirent.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_mkdir.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_mount.c\nCompiling repos/apache-mynewt-core/encoding/base64/src/base64.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_file.c\nCompiling repos/apache-mynewt-core/fs/disk/src/disk.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_nmgr.c\nCompiling repos/a
pache-mynewt-core/fs/fs/src/fsutil.c\nCompiling repos/apache-mynewt-core/fs/nffs/src/nffs.c\n\n ...\n\nLinking ~/dev/myproj/bin/targets/unittest/sys_config_test-nffs/app/sys/config/test-nffs/sys_config_test-nffs.elf\nExecuting test: ~/dev/myproj/bin/targets/unittest/sys_config_test-nffs/app/sys/config/test-nffs/sys_config_test-nffs.elf\nPassed tests: [sys/config/test-fcb sys/config/test-nffs]\nAll tests passed\n\n\n\n\n\nNOTE:\n If you've installed the latest gcc using homebrew on your Mac, you will likely be running gcc-6. Make sure you have adjusted the compiler.yml configuration to reflect that as noted in \nNative Install Option\n. You can choose to downgrade to gcc-5 in order to use the default gcc compiler configuration for MyNewt.\n\n\nNOTE:\n If you are running the standard gcc for 64-bit machines, it does not support 32-bit. In that case you will see compilation errors. You need to install multiboot gcc (e.g. gcc-multilib if you running on a 64-bit Ubuntu).\n\n\n$ brew
uninstall gcc-6\n$ brew link gcc-5\n\n\n\n\n\n\n\nTo test all the packages in a project, specify \nall\n instead of the package name.\n\n\n$ newt test all\nTesting package @apache-mynewt-core/boot/boot_serial/test\nCompiling repos/apache-mynewt-core/boot/boot_serial/test/src/boot_test.c\nCompiling repos/apache-mynewt-core/boot/boot_serial/test/src/testcases/boot_serial_setup.c\n\n ...\n\nLinking ~/dev/myproj/bin/targets/unittest/boot_boot_serial_test/app/boot/boot_serial/test/boot_boot_serial_test.elf\n\n...lots of compiling and testing...\n\nLinking ~/dev/myproj/bin/targets/unittest/util_cbmem_test/app/util/cbmem/test/util_cbmem_test.elf\nExecuting test: ~/dev/myproj/bin/targets/unittest/util_cbmem_test/app/util/cbmem/test/util_cbmem_test.elf\nPassed tests: [boot/boot_serial/test boot/bootutil/test crypto/mbedtls/test encoding/base64/test encoding/cborattr/test encoding/json/test fs/fcb/test fs/nffs/test kernel/os/test net/ip/mn_socket/test net/nimble/host/test net/oic/test sys
/config/test-fcb sys/config/test-nffs sys/flash_map/test sys/log/full/test util/cbmem/test]\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 \nBuilding target targets/my_blinky_sim\nCompiling repos/apache-mynewt-core/hw/hal/src/hal_common.c\nCompiling repos/apache-mynewt-core/hw/drivers/uart/src/uart.c\nCompiling repos/apache-mynewt-core/hw/hal/src/hal_flash.c\nCompiling repos/apache-mynewt-core/hw/bsp/native/src/hal_bsp.c\nCompiling repos/apache-mynewt-core/hw/drivers/uart/uart_hal/src/uart_hal.c\nCompiling apps/blinky/src/main.c\n\n ...\n\n\nArchiving sys_mfg.a\nArchiving sys_sysinit.a\nArchiving util_mem.a\nLinking ~/dev/myproj/bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf\nTarget successfully built: targets/my_blinky_sim\n\n\n\n\n\n\n\nRun the Project\n\n\nYou can run the simulated version of your project and see the simulated LED\nblink. If you are using n
ewt docker, use \nnewt run\n to run the simulated binary.\n\n\n$ newt run my_blinky_sim\nLoading app image into slot 1\n ...\nDebugging ~/dev/myproj/bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf\n ...\nReading symbols from /bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf...done.\n(gdb)\n\n\n\n\n\nType \nr\n at the \n(gdb)\n prompt to run the project. You will see an output indicating that the hal_gpio pin is toggling between 1 and 0 in a simulated blink.\n\n\nIf you natively install the toolchain, you can either use \nnewt run\n or call the binary directly. Generally, \nnewt run\n is the expected way to call things.\n\n\n$ ./bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf\nhal_gpio set pin 1 to 0\n\n\n\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 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.\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!",
+ "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\nNewt:\n\n\nIf you have taken the Docker route, you have already installed Newt.\n\n\nIf you have taken the native install route, you have to ensure that you have installed the Newt tool following the instructions for \nMac\n or \nLinux\n as appropriate, and that the \nnewt\n command is in your system path. \n\n\n\n\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 crea
ted.\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\nNote\n: If you do not have \ntree\n, install it by running \nbrew install tree\n.\n\n\n$ cd myproj\n$ tree \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\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\n6 directories, 11 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 \ntarget\n 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 internally by \nnewt\n and is not a formal build target.\n\n\n\n\nNOTE:\n The actual code and package file
<TRUNCATED>
[7/7] incubator-mynewt-site git commit: Updates to installation on
Linux and Mac, removal of references to develop branch on website
Posted by ad...@apache.org.
Updates to installation on Linux and Mac, removal of references to develop branch on website
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/45c390ea
Tree: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/tree/45c390ea
Diff: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/diff/45c390ea
Branch: refs/heads/asf-site
Commit: 45c390ea1c6a086245f0a883d02a6daec1606d73
Parents: e740429
Author: aditihilbert <ad...@runtime.io>
Authored: Tue Apr 25 17:31:25 2017 -0700
Committer: aditihilbert <ad...@runtime.io>
Committed: Tue Apr 25 17:31:25 2017 -0700
----------------------------------------------------------------------
develop/faq/go_env/index.html | 140 +++-
develop/mkdocs/search_index.json | 317 +++-----
develop/newt/install/newt_linux/index.html | 311 ++++----
develop/newtmgr/install_linux/index.html | 206 ++++-
develop/os/get_started/cross_tools/index.html | 108 ++-
develop/os/get_started/get_started/index.html | 11 +-
develop/os/get_started/native_tools/index.html | 12 +-
.../os/get_started/project_create/index.html | 2 +-
develop/os/get_started/vocabulary/index.html | 4 +-
develop/os/tutorials/STM32F303/index.html | 774 -------------------
develop/os/tutorials/arduino_zero/index.html | 12 +-
develop/os/tutorials/blehci_project/index.html | 5 +-
develop/os/tutorials/blinky/index.html | 16 +-
develop/os/tutorials/blinky_console/index.html | 11 -
develop/os/tutorials/blinky_primo/index.html | 28 +-
develop/os/tutorials/nRF52/index.html | 16 +-
develop/os/tutorials/nrf52_adc/index.html | 2 +-
develop/os/tutorials/olimex/index.html | 20 +-
develop/os/tutorials/pin-wheel-mods/index.html | 681 ----------------
.../tutorials/project-nrf52-slinky/index.html | 3 +-
.../tutorials/project-stm32-slinky/index.html | 1 +
develop/os/tutorials/rbnano2/index.html | 13 +-
develop/os/tutorials/tutorials/index.html | 10 +-
develop/sitemap.xml | 26 +-
download/index.html | 20 +-
latest/faq/go_env/index.html | 140 +++-
latest/mkdocs/search_index.json | 317 +++-----
latest/newt/install/newt_linux/index.html | 311 ++++----
latest/newtmgr/install_linux/index.html | 206 ++++-
latest/os/get_started/cross_tools/index.html | 108 ++-
latest/os/get_started/get_started/index.html | 11 +-
latest/os/get_started/native_tools/index.html | 12 +-
latest/os/get_started/project_create/index.html | 2 +-
latest/os/get_started/vocabulary/index.html | 4 +-
latest/os/tutorials/STM32F303/index.html | 774 -------------------
latest/os/tutorials/arduino_zero/index.html | 12 +-
latest/os/tutorials/blehci_project/index.html | 5 +-
latest/os/tutorials/blinky/index.html | 16 +-
latest/os/tutorials/blinky_console/index.html | 11 -
latest/os/tutorials/blinky_primo/index.html | 28 +-
latest/os/tutorials/nRF52/index.html | 16 +-
latest/os/tutorials/nrf52_adc/index.html | 2 +-
latest/os/tutorials/olimex/index.html | 20 +-
latest/os/tutorials/pin-wheel-mods/index.html | 681 ----------------
.../tutorials/project-nrf52-slinky/index.html | 3 +-
.../tutorials/project-stm32-slinky/index.html | 1 +
latest/os/tutorials/rbnano2/index.html | 13 +-
latest/os/tutorials/tutorials/index.html | 10 +-
latest/sitemap.xml | 26 +-
mkdocs/search_index.json | 8 +-
os/get_started/get_started/index.html | 5 +-
sitemap.xml | 26 +-
v0_9_0/sitemap.xml | 26 +-
53 files changed, 1422 insertions(+), 4121 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/develop/faq/go_env/index.html
----------------------------------------------------------------------
diff --git a/develop/faq/go_env/index.html b/develop/faq/go_env/index.html
index 551e115..f897a6f 100644
--- a/develop/faq/go_env/index.html
+++ b/develop/faq/go_env/index.html
@@ -262,22 +262,23 @@
</div>
</div>
- <h2 id="contributing-to-newt-and-newtmgr-tools">Contributing to Newt and Newtmgr Tools</h2>
-<p>Newt and Newtmgr are written in Go (golang). This guide shows you how to install Go and setup your environment if
-you would like to contribute to the newt or newtmgr tools.</p>
+ <h2 id="contributing-to-newt-or-newtmgr-tools">Contributing to Newt or Newtmgr Tools</h2>
+<p>Newt and Newtmgr are written in Go (golang). This guide shows you how to install Go and setup your environment to update and build the tools if you want to: </p>
+<ul>
+<li>Contribute to newt or newtmgr features or fix bugs.</li>
+<li>Build the tools with latest updates from the master branch on a Linux platform.</li>
+</ul>
<p>This guide shows you how to perform the following:</p>
<ol>
-<li>Install Go on either Mac OS or Linux.</li>
+<li>Install Go on either Mac OS X or Linux. (Tasks that are specific to each platform are called out.)</li>
<li>Setup the Go environment.</li>
-<li>Download the newt and newtmgr source code.</li>
-<li>Build the newt and newtmgr tools.</li>
+<li>Download the source, build, and install the newt or newtmgr tools.</li>
<li>Update and rebuild the tools. </li>
</ol>
-<p>Steps 2-5 apply to both Mac OS and Linux platforms.</p>
-<p><strong>Note:</strong> You will also need to read and follow the instructions from <a href="../../faq/answers/">FAQ</a> to set up your git repos to submit changes.</p>
+<p><strong>Note:</strong> You will also need to read and follow the instructions from the <a href="../../faq/answers/">FAQ</a> to set up your git repos to submit changes.</p>
<h3 id="step-1-installing-go">Step 1: Installing Go</h3>
-<p>The latest master branch of newt and newtmgr requires GO version 1.6 or higher.
-<br></p>
+<p>The latest master branch of newt and newtmgr requires GO version 1.6 or higher. You can skip this step and proceed to Step 2 if you already have Go version 1.6 or higher installed.</p>
+<p><br></p>
<h4 id="installing-go-on-mac-os-x">Installing Go on Mac OS X</h4>
<p>If you do not have Homebrew installed, run the following command. You will be prompted for your sudo password.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
@@ -325,13 +326,14 @@ go version go1.6.3 linux/amd64
<p><br></p>
<h3 id="step-2-setting-up-your-go-environment">Step 2: Setting Up Your Go Environment</h3>
-<p>Go provides an environment to compile Go code, construct Go packages, and import Go code. You will use Go commands to import the <strong>newt</strong> repository into your local Go environment. The Go language environment dictates a specific directory structure, or workspace in Go parlance. It must contain three sibling directories with the names <strong>src</strong>, <strong>pkg</strong> and <strong>bin</strong>: </p>
+<p>This section describes the Go environment and how to setup a Go workspace. If you already have a Go workspace for your other Go projects, you can skip this step and proceed to Step 3.</p>
+<p>Go provides an environment to compile Go code, construct Go packages, and import Go code. You will use Go commands to import the newt or newtmgr package repository into your local Go environment. The Go language environment dictates a specific directory structure, or workspace in Go parlance. It must contain three sibling directories with the names <strong>src</strong>, <strong>pkg</strong> and <strong>bin</strong>: </p>
<ul>
<li>src contains Go source files organized into packages (one package per directory)</li>
<li>pkg contains package objects</li>
-<li>bin contains executable commands.</li>
+<li>bin contains the Go application executables that Go builds and installs.</li>
</ul>
-<p>The <strong>GOPATH</strong> environment variable specifies the location of your workspace. To setup this workspace environment, create a <strong>dev</strong> directory and then a <strong>go</strong> directory under it. Set the GOPATH environment variable to this directory where you will clone the newt repository.</p>
+<p>The <strong>GOPATH</strong> environment variable specifies the location of your workspace. To setup this workspace environment, create a <strong>dev</strong> directory and then a <strong>go</strong> directory under it. Set the GOPATH environment variable to this directory where you will clone the newt and newtmgr repositories.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ cd $HOME
$ mkdir -p dev/go
$ cd dev/go
@@ -340,57 +342,113 @@ $ export GOPATH=`pwd`
<p><br>
-Add the export GOPATH statement to the ~/.bash_profile file and source the file:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ vi ~/.bash_profile
-$ source ~/.bash_profile
+Add the following export statements to your ~/.bash_profile file and source the file:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">export GOPATH=$HOME/dev/go
+export PATH=$GOPATH/bin:$PATH
</pre></div>
<p><br></p>
-<h3 id="step-3-downloading-the-source">Step 3: Downloading the Source</h3>
-<p>Use Go commands to retrieve the latest source from the newt repository (currently the ASF incubator directory). Check that the directories are installed.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ go get mynewt.apache.org/newt/...
-$ ls $GOPATH/src/mynewt.apache.org/newt
-DISCLAIMER NOTICE newt newtvm viper
-LICENSE README.md newtmgr util yaml
+<h3 id="step-3-downloading-the-source-and-installing-the-tools">Step 3: Downloading the Source and Installing the Tools</h3>
+<p>Newt and newtmgr are individual Go packages and have their own git repositories. You can download the source and install one or both tools.</p>
+<p>We use the <code>go get</code> command to download the source, build, and install the binary in the <strong>$GOPATH/bin</strong> directory. </p>
+<p><br></p>
+<h4 id="downloading-and-installing-the-newt-tool">Downloading and Installing the Newt Tool</h4>
+<p>The newt Go package is <strong>mynewt.apache.org/newt/newt</strong> and is stored in the <a href="https://github.com/apache/incubator-mynewt-newt">Apache Mynewt newt tool repository mirrored on github</a>. </p>
+<p>Download the newt package source and install the tool:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$cd $GOPATH
+$go get mynewt.apache.org/newt/newt
+$cd $GOPATH/src/mynewt.apache.org/newt
+$ls
+DISCLAIMER RELEASE_NOTES.md util
+INSTALLING.md build.sh viper
+LICENSE newt yaml
+NOTICE newtmgr
+README.md newtvm
+$git status
+On branch master
+Your branch is up-to-date with 'origin/master'.
+
+nothing to commit, working directory clean
+</pre></div>
+
+
+<p><br>
+<strong>Note:</strong> The source code under the <strong>newtmgr</strong> directory is no longer used or updated. The current <strong>newtmgr</strong> source has its own Git repository.</p>
+<p><br>
+Check that the newt binary is installed and you are using the one from <strong> $GOPATH/bin</strong>:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ls $GOPATH/bin/newt
+~/dev/go/bin/newt
+$which newt
+~/dev/go/bin/newt
+$newt version
+Apache Newt (incubating) version: 1.0.0-dev
</pre></div>
<p><br></p>
-<h3 id="step-4-building-the-newt-and-newtmgr-tools">Step 4: Building the Newt and Newtmgr Tools</h3>
-<p>Perform the following commands to build the tools:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ cd $GOPATH/src/mynewt.apache.org/newt/newt
-$ go install
-$ ls $GOPATH/bin/
-newt newtmgr newtvm
+<h4 id="downloading-and-installing-the-newtmgr-tool">Downloading and Installing the Newtmgr Tool</h4>
+<p>The newtmgr Go package is <strong>mynewt.apache.org/newtmgr/newtmgr</strong>. It is stored in the <a href="https://github.com/apache/incubator-mynewt-newtmgr">Apache Mynewt newtmgr tool repository mirrored on github</a>.</p>
+<p>Download the newtmgr package and install the tool:</p>
+<p><strong>Note:</strong> <code>-ldflags -s</code> must be passed to the <code>go get</code> command.</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$cd $GOPATH
+$go get -ldflags -s mynewt.apache.org/newtmgr/newtmgr
+$cd $GOPATH/src/mynewt.apache.org/newtmgr
+$ls
+DISCLAIMER NOTICE newtmgr
+LICENSE README.md nmxact
+$git status
+On branch master
+Your branch is up-to-date with 'origin/master'.
+
+nothing to commit, working directory clean
+</pre></div>
+
+
+<p><br>
+Check that the newtmgr binary is installed and you are using the one from <strong>$GOPATH/bin</strong>:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ls $GOPATH/bin/newtmgr
+~/dev/go/bin/newtmgr
+$which newt
+~/dev/go/bin/newtmgr
</pre></div>
<p><br></p>
-<h3 id="step-5-updating-and-rebuilding-the-tools">Step 5: Updating and Rebuilding the Tools</h3>
-<p>Change to the directory where you initially installed the source: </p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ cd $GOPATH/src/mynewt.apache.org/newt
+<h3 id="step-4-updating-and-rebuilding-the-tools">Step 4: Updating and Rebuilding the Tools:</h3>
+<p>This section shows you how to rebuild the newt and newtmgr tools with the latest updates from the master branch or after you have made changes in your branch. </p>
+<p>Here is the general procedure to rebuild either the newt or newtmgr tool. The only difference is the directory where you will be executing the commands from. You will need to repeat the procedure to rebuild both tools.</p>
+<ol>
+<li>Change to the directory where the local Git repository for the tool is installed.</li>
+<li>Pull the latest changes from the master branch. If you made changes you will need to rebase with <strong>origin master</strong> (See <a href="../../faq/answers/">FAQ</a>).</li>
+<li>Build and install the tool.</li>
+</ol>
+<p><br>
+Change to the directory where the source for the tool is installed.</p>
+<p>For the <strong>newt</strong> tool:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$cd $GOPATH/src/mynewt.apache.org/newt/newt
+</pre></div>
+
+
+<p>For the <strong>newtmgr</strong> tool:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$cd $GOPATH/src/mynewt.apache.org/newtmgr/newtmgr
</pre></div>
<p><br>
-Pull the latest source from the repository (you can change to a different branch using git checkout [branch] if you need to)</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ git pull
+After you change to the specific tool directory, get the latest updates from the master branch. If you made changes and need to rebase with the origin, add the <code>--rebase origin master</code> arguments to the <code>git pull</code> command:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$git pull
</pre></div>
<p><br>
-Install the tools from the latest source:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ cd newt
-$ go install
-$ cd ../newtmgr
-$ go install
-$ ls $GOPATH /bin/
-newt newtmgr newtvm
+Build and install the tool. The updated binary will be installed in the <strong>$GOPATH/bin</strong> directory: </p>
+<p>(<strong>Note:</strong> <code>-ldflags -s</code> must be passed to the <code>go install</code> command if you are rebuilding newtmgr)</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$go install
</pre></div>
-<p>This should have updated your newt and newtmgr to the latest version based on the git repository you used.</p>
+<p>You can run the <code>ls -l</code> command to check the modification time for the binary to ensure the new version is installed. </p>
<div class="row">
[6/7] incubator-mynewt-site git commit: Updates to installation on
Linux and Mac, removal of references to develop branch on website
Posted by ad...@apache.org.
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/develop/mkdocs/search_index.json
----------------------------------------------------------------------
diff --git a/develop/mkdocs/search_index.json b/develop/mkdocs/search_index.json
index 0af8892..4de7a25 100644
--- a/develop/mkdocs/search_index.json
+++ b/develop/mkdocs/search_index.json
@@ -137,17 +137,17 @@
},
{
"location": "/os/get_started/get_started/",
- "text": "Quick Start\n\n\nIf you are curious about Mynewt and want to get a quick feel for the project, you've come to the right place. We have two options for you:\n\n\n\n\nOption 1\n is an easy, self-contained way to get up and running with Mynewt - but has limitations! The Newt tool and build toolchains are all available in a single \nAll-in-one Docker Container\n that you can install on your laptop or computer.\n\n\nHowever, this is not a long-term option since support is not likely for all features useful or critical to embedded systems development. For example, USB device mapping available in the Docker toolkit (used in this Option 1) is no longer available in the new Docker releases. The Docker option is also typically slower than the native install option. \n\n\n Therefore, the recommended option is Option 2 below. \n\n\n\n\nOption 2 (Recommended)\n allows you to install the Newt tool, instances of the Mynewt OS (for simulated targets), and toolchains for develop
ing embedded software (e.g. GNU toolchain) natively on your laptop or computer. We have tried to make the process easy. For example, for the Mac OS we created brew formulas. \n\n\nYou want this option if you are familiar with such environments or are concerned about performance on your machine. Follow the instructions to \ninstall native tools\n and \ninstall cross tools for ARM\n if you prefer this option.\n\n\n\n\nYou can then proceed with the instructions on how to \n* \nCreate Your First Project\n - on simulated hardware.\n\n\nUpon successful start, several tutorials await your eager attention!\n\n\n\n\nSend us an email on the dev@ mailing list if you have comments or suggestions!\n If you haven't joined the mailing list, you will find the links \nhere\n.",
+ "text": "Quick Start\n\n\nIf you are curious about Mynewt and want to get a quick feel for the project, you've come to the right place. We have two options for you:\n\n\n\n\nOption 1 (Recommended)\n allows you to install the Newt tool, instances of the Mynewt OS (for simulated targets), and toolchains for developing embedded software (e.g. GNU toolchain) natively on your laptop or computer. We have tried to make the process easy. For example, for the Mac OS we created brew formulas. \n\n\nWe recommend this option if you are familiar with such environments or are concerned about performance on your machine. Follow the instructions to \ninstall native tools\n and \ninstall cross tools for ARM\n if you prefer this option.\n\n\n\n\nOption 2\n is an easy, self-contained way to get up and running with Mynewt - but has limitations! The Newt tool and build toolchains are all available in a single \nAll-in-one Docker Container\n that you can install on your laptop or computer.\n\
n\nHowever, this is not a long-term option since support is not likely for all features useful or critical to embedded systems development. For example, USB device mapping available in the Docker toolkit is no longer available in the new Docker releases. The Docker option is also typically slower than the native install option. \n\n\n\n\nYou can then proceed with the instructions on how to \n* \nCreate Your First Project\n - on simulated hardware.\n\n\nUpon successful start, several tutorials await your eager attention!\n\n\n\n\nSend us an email on the dev@ mailing list if you have comments or suggestions!\n If you haven't joined the mailing list, you will find the links \nhere\n.",
"title": "toc"
},
{
"location": "/os/get_started/get_started/#quick-start",
- "text": "If you are curious about Mynewt and want to get a quick feel for the project, you've come to the right place. We have two options for you: Option 1 is an easy, self-contained way to get up and running with Mynewt - but has limitations! The Newt tool and build toolchains are all available in a single All-in-one Docker Container that you can install on your laptop or computer. However, this is not a long-term option since support is not likely for all features useful or critical to embedded systems development. For example, USB device mapping available in the Docker toolkit (used in this Option 1) is no longer available in the new Docker releases. The Docker option is also typically slower than the native install option. Therefore, the recommended option is Option 2 below. Option 2 (Recommended) allows you to install the Newt tool, instances of the Mynewt OS (for simulated targets), and toolchains for developing embedded software (e.g. GNU toolchain)
natively on your laptop or computer. We have tried to make the process easy. For example, for the Mac OS we created brew formulas. You want this option if you are familiar with such environments or are concerned about performance on your machine. Follow the instructions to install native tools and install cross tools for ARM if you prefer this option. You can then proceed with the instructions on how to \n* Create Your First Project - on simulated hardware. Upon successful start, several tutorials await your eager attention! Send us an email on the dev@ mailing list if you have comments or suggestions! If you haven't joined the mailing list, you will find the links here .",
+ "text": "If you are curious about Mynewt and want to get a quick feel for the project, you've come to the right place. We have two options for you: Option 1 (Recommended) allows you to install the Newt tool, instances of the Mynewt OS (for simulated targets), and toolchains for developing embedded software (e.g. GNU toolchain) natively on your laptop or computer. We have tried to make the process easy. For example, for the Mac OS we created brew formulas. We recommend this option if you are familiar with such environments or are concerned about performance on your machine. Follow the instructions to install native tools and install cross tools for ARM if you prefer this option. Option 2 is an easy, self-contained way to get up and running with Mynewt - but has limitations! The Newt tool and build toolchains are all available in a single All-in-one Docker Container that you can install on your laptop or computer. However, this is not a long-term option sinc
e support is not likely for all features useful or critical to embedded systems development. For example, USB device mapping available in the Docker toolkit is no longer available in the new Docker releases. The Docker option is also typically slower than the native install option. You can then proceed with the instructions on how to \n* Create Your First Project - on simulated hardware. Upon successful start, several tutorials await your eager attention! Send us an email on the dev@ mailing list if you have comments or suggestions! If you haven't joined the mailing list, you will find the links here .",
"title": "Quick Start"
},
{
"location": "/os/get_started/native_tools/",
- "text": "Installing Native Mynewt Tools\n\n\nThis page shows how to install tools for native Mynewt targets (simulated targets on your laptop/computer) without using a Docker container. In other words, it allows you to run Mynewt OS as a native application on your Mac or Linux machine to simulate a target and use the Newt tool running natively on your machine to manage the simulated target. It also allows you to run the test suites for all packages not requiring HW support. You may choose to do this instead of using the build toolchain and Newt tool available in a Docker container.\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 with, a different compiler is used as
default: 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\nCheck the gcc version you have installed (either using brew or previously installed). The brew-installed version can be checked using \nbrew list gcc\n. The default compiler.yml configuration file in Mynewt expects version 5.x for Mac users, so if the installed version is 6.x and you wish to continue with this newer version, modify the \nmynewt-src-directory\n/repos/apache-mynewt-core/compiler/sim/compiler.yml\n file to change the default \ngcc-5\n defined there to \ngcc-6\n. In other words, replace the lines shown highlighted below:\n\n\n# OS X.\n\ncompiler.path.cc.DARWIN.OVERWRITE: \n/usr/local/bin/gcc-5\n\n\ncompiler.path.as.DARWIN.OVERWRITE: \n/usr/local/bin/gcc-5 -x assembler-with-cpp\n\n\ncompiler.path.objdump.DARWIN.OVERWRITE: \ngobjdump\n\ncompiler.path.objsize.DARWIN.OVERWRITE: \nobjsize\n\ncompiler.path.objcopy.DARWIN.OVERWRITE: \ngobjc
opy\n\n\n\n\n\n\nwith the following:\n\n\ncompiler.path.cc.DARWIN.OVERWRITE: \n/usr/local/bin/gcc-6\n\ncompiler.path.as.DARWIN.OVERWRITE: \n/usr/local/bin/gcc-6 -x assembler-with-cpp\u201d\n\n\n\n\n\n\n\nIn case you wish to use Clang, you can change your \nmynewt-src-directory\n/repos/apache-mynewt-core/compiler/sim/compiler.yml\n to use Clang. Delete the gcc-5 DARWIN.OVERWRITE lines highlighted below.\n\n\n# OS X.\n\ncompiler.path.cc.DARWIN.OVERWRITE: \n/usr/local/bin/gcc-5\n\n\ncompiler.path.as.DARWIN.OVERWRITE: \n/usr/local/bin/gcc-5 -x assembler-with-cpp\n\n\ncompiler.path.objdump.DARWIN.OVERWRITE: \ngobjdump\n\ncompiler.path.objsize.DARWIN.OVERWRITE: \nobjsize\n\ncompiler.path.objcopy.DARWIN.OVERWRITE: \ngobjcopy\n\n\n\n\n\n\n\n\nNOTE:\n Both the newer gcc 6.x and Clang report a few warnings but they can be ignored.\n\n\n\n\nFURTHER NOTE:\n Mynewt developers mostly use gcc 5.x for sim builds; so it may take a little while to fix issues reported by the newer compiler. One option
is to \ndisable warnings\n. To do that, remove the \n-Werror\n flag as an option for the compiler in the \nmynewt-src-directory\n/repos/apache-mynewt-core/compiler/sim/compiler.yml\n file as shown below. \n\n\ncompiler.flags.base: \n\n\n -m32 -Wall -ggdb\n\n\n\n\n\nYou may alternatively choose to \nspecify the precise warnings to ignore\n depending on the error thrown by the compiler. For example, if you see a \n[-Werror=misleading-indentation]\n error while building the sim image, add \n-Wno-misleading-indentation]\n as a compiler flag in the same line from the \nmynewt-src-directory\n/repos/apache-mynewt-core/compiler/sim/compiler.yml\n file.\n\n\ncompiler.flags.base: \n\n\n -m32 -Wall -Werror -ggdb -Wno-misleading-indentation\n\n\n\n\n\nA third option is to simply \ndowngrade to gcc 5.x\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, y
ou 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 installed all the necessary software to build and test code on a simluator running on your Mac or Linux. Proceed to the \nCreate Your First Project\n section.",
+ "text": "Installing Native Mynewt Tools\n\n\nThis page shows how to install tools for native Mynewt targets (simulated targets on your laptop/computer) without using a Docker container. In other words, it allows you to run Mynewt OS as a native application on your Mac or Linux machine to simulate a target and use the Newt tool running natively on your machine to manage the simulated target. It also allows you to run the test suites for all packages not requiring HW support. You may choose to do this instead of using the build toolchain and Newt tool available in a Docker container.\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 with, a different compiler is used as
default: 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\nCheck the gcc version you have installed (either using brew or previously installed). The brew-installed version can be checked using \nbrew list gcc\n. The default compiler.yml configuration file in Mynewt expects version 5.x for Mac users, so if the installed version is 6.x and you wish to continue with this newer version, modify the \nmynewt-src-directory\n/repos/apache-mynewt-core/compiler/sim/compiler.yml\n file to change the default \ngcc-5\n defined there to \ngcc-6\n. In other words, replace the lines shown highlighted below:\n\n\n# OS X.\n\ncompiler.path.cc.DARWIN.OVERWRITE: \ngcc-5\n\n\ncompiler.path.as.DARWIN.OVERWRITE: \ngcc-5\n\n\ncompiler.path.objdump.DARWIN.OVERWRITE: \ngobjdump\n\ncompiler.path.objsize.DARWIN.OVERWRITE: \nobjsize\n\ncompiler.path.objcopy.DARWIN.OVERWRITE: \ngobjcopy\n\n\n\n\n\n\nwith the following:\n\n\ncompiler.p
ath.cc.DARWIN.OVERWRITE: \ngcc-6\n\ncompiler.path.as.DARWIN.OVERWRITE: \ngcc-6\u201d\n\n\n\n\n\n\n\nIn case you wish to use Clang, you can change your \nmynewt-src-directory\n/repos/apache-mynewt-core/compiler/sim/compiler.yml\n to use Clang. Delete the gcc-5 DARWIN.OVERWRITE lines highlighted below.\n\n\n# OS X.\n\ncompiler.path.cc.DARWIN.OVERWRITE: \ngcc-5\n\n\ncompiler.path.as.DARWIN.OVERWRITE: \ngcc-5\n\n\ncompiler.path.objdump.DARWIN.OVERWRITE: \ngobjdump\n\ncompiler.path.objsize.DARWIN.OVERWRITE: \nobjsize\n\ncompiler.path.objcopy.DARWIN.OVERWRITE: \ngobjcopy\n\n\n\n\n\n\n\n\nNOTE:\n Both the newer gcc 6.x and Clang report a few warnings but they can be ignored.\n\n\n\n\nFURTHER NOTE:\n Mynewt developers mostly use gcc 5.x for sim builds; so it may take a little while to fix issues reported by the newer compiler. One option is to \ndisable warnings\n. To do that, remove the \n-Werror\n flag as an option for the compiler in the \nmynewt-src-directory\n/repos/apache-mynewt-core
/compiler/sim/compiler.yml\n file as shown below. \n\n\ncompiler.flags.base: \n\n\n -m32 -Wall -ggdb\n\n\n\n\n\nYou may alternatively choose to \nspecify the precise warnings to ignore\n depending on the error thrown by the compiler. For example, if you see a \n[-Werror=misleading-indentation]\n error while building the sim image, add \n-Wno-misleading-indentation]\n as a compiler flag in the same line from the \nmynewt-src-directory\n/repos/apache-mynewt-core/compiler/sim/compiler.yml\n file.\n\n\ncompiler.flags.base: \n\n\n -m32 -Wall -Werror -ggdb -Wno-misleading-indentation\n\n\n\n\n\nA third option is to simply \ndowngrade to gcc 5.x\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 abili
ty 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 installed all the necessary software to build and test code on a simluator running on your Mac or Linux. Proceed to the \nCreate
Your First Project\n section.",
"title": "toc"
},
{
@@ -167,7 +167,7 @@
},
{
"location": "/os/get_started/native_tools/#install-gcclibc",
- "text": "OS X ships with a C compiler called Clang. To build applications for the Mynewt simulator with, a different compiler is used as default: gcc. $ brew install gcc\n...\n...\n== Summary\n\ud83c\udf7a /usr/local/Cellar/gcc/5.2.0: 1353 files, 248M Check the gcc version you have installed (either using brew or previously installed). The brew-installed version can be checked using brew list gcc . The default compiler.yml configuration file in Mynewt expects version 5.x for Mac users, so if the installed version is 6.x and you wish to continue with this newer version, modify the mynewt-src-directory /repos/apache-mynewt-core/compiler/sim/compiler.yml file to change the default gcc-5 defined there to gcc-6 . In other words, replace the lines shown highlighted below: # OS X. compiler.path.cc.DARWIN.OVERWRITE: /usr/local/bin/gcc-5 compiler.path.as.DARWIN.OVERWRITE: /usr/local/bin/gcc-5 -x assembler-with-cpp compiler.path.objdump.DARWIN.OVERWRITE: gobjdump
\ncompiler.path.objsize.DARWIN.OVERWRITE: objsize \ncompiler.path.objcopy.DARWIN.OVERWRITE: gobjcopy with the following: compiler.path.cc.DARWIN.OVERWRITE: /usr/local/bin/gcc-6 \ncompiler.path.as.DARWIN.OVERWRITE: /usr/local/bin/gcc-6 -x assembler-with-cpp\u201d In case you wish to use Clang, you can change your mynewt-src-directory /repos/apache-mynewt-core/compiler/sim/compiler.yml to use Clang. Delete the gcc-5 DARWIN.OVERWRITE lines highlighted below. # OS X. compiler.path.cc.DARWIN.OVERWRITE: /usr/local/bin/gcc-5 compiler.path.as.DARWIN.OVERWRITE: /usr/local/bin/gcc-5 -x assembler-with-cpp compiler.path.objdump.DARWIN.OVERWRITE: gobjdump \ncompiler.path.objsize.DARWIN.OVERWRITE: objsize \ncompiler.path.objcopy.DARWIN.OVERWRITE: gobjcopy NOTE: Both the newer gcc 6.x and Clang report a few warnings but they can be ignored. FURTHER NOTE: Mynewt developers mostly use gcc 5.x for sim builds; so it may take a little while to fix issues reported by the newer
compiler. One option is to disable warnings . To do that, remove the -Werror flag as an option for the compiler in the mynewt-src-directory /repos/apache-mynewt-core/compiler/sim/compiler.yml file as shown below. compiler.flags.base: -m32 -Wall -ggdb You may alternatively choose to specify the precise warnings to ignore depending on the error thrown by the compiler. For example, if you see a [-Werror=misleading-indentation] error while building the sim image, add -Wno-misleading-indentation] as a compiler flag in the same line from the mynewt-src-directory /repos/apache-mynewt-core/compiler/sim/compiler.yml file. compiler.flags.base: -m32 -Wall -Werror -ggdb -Wno-misleading-indentation A third option is to simply downgrade to gcc 5.x .",
+ "text": "OS X ships with a C compiler called Clang. To build applications for the Mynewt simulator with, a different compiler is used as default: gcc. $ brew install gcc\n...\n...\n== Summary\n\ud83c\udf7a /usr/local/Cellar/gcc/5.2.0: 1353 files, 248M Check the gcc version you have installed (either using brew or previously installed). The brew-installed version can be checked using brew list gcc . The default compiler.yml configuration file in Mynewt expects version 5.x for Mac users, so if the installed version is 6.x and you wish to continue with this newer version, modify the mynewt-src-directory /repos/apache-mynewt-core/compiler/sim/compiler.yml file to change the default gcc-5 defined there to gcc-6 . In other words, replace the lines shown highlighted below: # OS X. compiler.path.cc.DARWIN.OVERWRITE: gcc-5 compiler.path.as.DARWIN.OVERWRITE: gcc-5 compiler.path.objdump.DARWIN.OVERWRITE: gobjdump \ncompiler.path.objsize.DARWIN.OVERWRITE: objsize
\ncompiler.path.objcopy.DARWIN.OVERWRITE: gobjcopy with the following: compiler.path.cc.DARWIN.OVERWRITE: gcc-6 \ncompiler.path.as.DARWIN.OVERWRITE: gcc-6\u201d In case you wish to use Clang, you can change your mynewt-src-directory /repos/apache-mynewt-core/compiler/sim/compiler.yml to use Clang. Delete the gcc-5 DARWIN.OVERWRITE lines highlighted below. # OS X. compiler.path.cc.DARWIN.OVERWRITE: gcc-5 compiler.path.as.DARWIN.OVERWRITE: gcc-5 compiler.path.objdump.DARWIN.OVERWRITE: gobjdump \ncompiler.path.objsize.DARWIN.OVERWRITE: objsize \ncompiler.path.objcopy.DARWIN.OVERWRITE: gobjcopy NOTE: Both the newer gcc 6.x and Clang report a few warnings but they can be ignored. FURTHER NOTE: Mynewt developers mostly use gcc 5.x for sim builds; so it may take a little while to fix issues reported by the newer compiler. One option is to disable warnings . To do that, remove the -Werror flag as an option for the compiler in the mynewt-src-directory /repos/apa
che-mynewt-core/compiler/sim/compiler.yml file as shown below. compiler.flags.base: -m32 -Wall -ggdb You may alternatively choose to specify the precise warnings to ignore depending on the error thrown by the compiler. For example, if you see a [-Werror=misleading-indentation] error while building the sim image, add -Wno-misleading-indentation] as a compiler flag in the same line from the mynewt-src-directory /repos/apache-mynewt-core/compiler/sim/compiler.yml file. compiler.flags.base: -m32 -Wall -Werror -ggdb -Wno-misleading-indentation A third option is to simply downgrade to gcc 5.x .",
"title": "Install gcc/libc"
},
{
@@ -222,83 +222,88 @@
},
{
"location": "/newt/install/newt_linux/",
- "text": "Install newt tool on Linux\n\n\n\n\nGetting your Linux box Ready\n\n\nIf you want to build the \nnewt\n tool from its source code, follow the following steps:\n\n\n1. Install git, libcurl\n\n\n $ sudo apt-get install git \n $ sudo apt-get install libcurl4-gnutls-dev \n\n\n\n\n\nNOTE:\n On 64-bit host, you may also need to install gcc-multilib, if you encounter compilation errors related to 'sys/cdefs.h'\n\n\n\n\n2. Install Go, the programming language\n\n\n\n\n\n\nGo language environment dictates a directory structure. Known in Go parlance as a workspace, it must contain three sibling directories with the directory names src, pkg and bin, as explained below. \n\n\n\n\n\n\nsrc contains Go source files organized into packages (one package per directory),\n\n\n\n\n\n\npkg contains package objects, and\n\n\n\n\n\n\nbin contains executable commands.\n\n\n\n\n\n\nThe GOPATH environment variable specifies the location of your workspace. To setup this work
space environment, create a 'dev' directory and then a 'go' directory under it. Set the GOPATH environment variable to this directory where you will soon clone the \nnewt\n tool repository.\n\n\n\n\n\n\n $ cd $HOME\n $ mkdir -p dev/go \n $ cd dev/go\n $ export GOPATH=`pwd`\n\n\n\n\n\n(Note that you need to add export statements to ~/.bash_profile to export variables permanently. Don't forget to source the file for the change to go into effect.)\n\n\n\n\n $ vi ~/.bash_profile\n $ source ~/.bash_profile\n\n\n\n\n\n\n\n\n\n\n\nNext, install Go. When installed, Go offers you as a developer a language environment (to compile Go code), construct Go packages (to assemble Go packages) and import Go code (from github). In the next step, you will use the Go commands to import \nnewt\n repo into your local Go environment.\n\n\nNote\n: The Newt tool requires Go version 1.7 or later. Currently, the latest Go version that Ubuntu installs is 1.6. You can
run \napt-get install golang-1.7-go\n to install version 1.7. You can also download version 1.7 from \nhttps://golang.org/dl/\n. \n\n\n\n\n\n\n$sudo apt-get install golang-1.7-go\nReading package lists... Done\n ...\nUnpacking golang-1.7-go (1.7.1-2ubuntu1) ...\nSetting up golang-1.7-go (1.7.1-2ubuntu1) ...\n$\n$sudo ln -s /usr/lib/go-1.7/bin/go /usr/bin/go\n$go version\ngo version go1.7.1 linux/amd64\n\n\n\n\n\n \n\n\n3. Create local repository\n\n\n\n\nUse Go commands to copy the directory (currently the ASF incubator directory). Be patient as it may take a minute or two. Check the directories installed.\n\n\n\n\n $ go get mynewt.apache.org/newt/...\n\n\n\n\n\n\n\n\n\nCheck that newt.go is in place.\n\n\n\n\n $ ls $GOPATH/src/mynewt.apache.org/newt\n DISCLAIMER NOTICE newt newtvm viper\n LICENSE README.md newtmgr util yaml\n\n\n\n\n\n\n\n4. Build the Newt tool\n\n\n\n\nUse Go to run the newt.go program to build
the \nnewt\n tool. The command \ngo install\n compiles and writes the resulting executable to an output file named \nnewt\n, which is then installed, along with its dependencies, in $GOPATH/bin. If you get errors it is likely because of path resolution issues. Try \ngo build\n followed by \ngo install\n in that case.\n\n\n\n\n $ cd $GOPATH/src/mynewt.apache.org/newt/newt\n $ go install\n $ ls \n$GOPATH\n/bin/\n newt newtmgr newtvm\n\n\n\n\n\n\n\n\n\nAt this point, you can try using \nnewt\n. For example, check for the version number by typing 'newt version'. See all the possible commands available to a user of newt by typing 'newt -h'.\n\n\n\n\n(Note: If you are going to be modifying the \nnewt\n often and going to be compile the program every time you call it, you will want to store the command in a variable in your .bash_profile. So type in \nexport newt=\"go run $GOPATH/mynewt.apache.org/newt/newt/newt.go\"\n in your .bash_profile and execute it by c
alling \n$newt\n at the prompt instead of \nnewt\n. Essentially, \n$newt\n calls \ngo run\n which runs the compiled binary directly without producing an executable. Don't forget to reload the updated bash profile by typing \nsource ~/.bash_profile\n at the prompt! )\n\n\n $ newt version\n Newt version: 1.0\n $ newt -h\n Newt allows you to create your own embedded application based on the Mynewt \n operating system. Newt provides both build and package management in a single \n tool, which allows you to compose an embedded application, and set of \n projects, and then build the necessary artifacts from those projects. For more \n information on the Mynewt operating system, please visit \n https://mynewt.apache.org/. \n\n Please use the newt help command, and specify the name of the command you want \n help for, for help on how to use a specific command\n\n Usage:\n newt [flags]\n ne
wt [command]\n\n Examples:\n newt\n newt help [\ncommand-name\n]\n For help on \ncommand-name\n. If not specified, print this message.\n\n Available Commands:\n build Build one or more targets\n clean Delete build artifacts for one or more targets\n create-image Add image header to target binary\n debug Open debugger session to target\n info Show project info\n install Install project dependencies\n load Load built target to board\n mfg Manufacturing flash image commands\n new Create a new project\n pkg Create and manage packages in the current workspace\n run build/create-image/download/debug \ntarget\n\n size Size of target components\n sync Synchronize project dependencies\n target Commands to create, delete, confi
gure, and query targets\n test Executes unit tests for one or more packages\n upgrade Upgrade project dependencies\n vals Display valid values for the specified element type(s)\n version Display the Newt version number\n\n Flags:\n -h, --help Help for newt commands\n -j, --jobs int Number of concurrent build jobs (default 8)\n -l, --loglevel string Log level (default \nWARN\n)\n -o, --outfile string Filename to tee output to\n -q, --quiet Be quiet; only display error output\n -s, --silent Be silent; don\nt output anything\n -v, --verbose Enable verbose output when executing commands\n\n Use \nnewt [command] --help\n for more information about a comma\n\n\n\n\n\n\n\n5. Updating the Newt tool\n\n\n\n\nYou will update the newt tool in the same place as you initially installed the newt tool.
\n\n\nStart by updating the git repository of the newt tool (you can change to a different branch using git checkout [branch] if you need to)\n\n\nThen update each of the tools newt, newtmgr and newtvm as needed\n\n\n\n\n $ cd $GOPATH/src/mynewt.apache.org/newt\n $ git pull\n $ cd newt\n $ go install\n $ cd ../newtmgr\n $ go install\n $ cd ../newtvm\n $ go install\n $ ls \n$GOPATH\n/bin/\n newt newtmgr newtvm\n\n\n\n\n\nThat should have updated your newt, newtmgr and newtvm to the latest versions based on the git repository you used.",
+ "text": "Installing Newt on Linux\n\n\nYou can install the latest stable release (1.0.0) of newt from a Debian binary package (amd64) or from a Debian source package. This page shows you how to:\n\n\n\n\nSet up your computer to retrieve Debian packages from the runtimeco debian package repository.\n\n\nInstall the latest stable release version of newt from a Debian binary package. \n\n\nInstall the latest stable release version of newt from a Debian source package.\n\n\n\n\nIf you are running on an amd64 platform, we recommend that you install from the binary package.\n\n\nNote:\n See \nSetting Up an Go Environment to Contribute to Newt and Newtmgr Tools\n if you want to: \n\n\n\n\nUse the newt tool with the latest updates from the master branch. The master branch may be unstable and we recommend that you use the latest stable release version.\n\n\nContribute to the newt tool. \n\n\n\n\n\n\nSetting Up Your Computer to Get Packages from runtimeco\n\n\nThe newt Debian pac
kages are stored in a private repository on \nhttps://github/runtimeco/debian-mynewt\n. \n\n\nNote:\n You will only need to perform these steps only once on your computer.\nThe following steps must be performed on your computer:\n\n\n\n\nAdd the \napt-transport-https\n package to use HTTPS to retrieve packages. \n\n\nDownload the public key for the runtimeco debian repository and import the key into the apt keychain.\n\n\nAdd the repository for the binary and source packages to the apt source list.\n\n\n\n\n\nAdd the apt-transport-https package:\n\n\n$sudo apt-get update\n$sudo apt-get install apt-transport-https\n\n\n\n\n\n\n\nDownload the public key for the runtimeco apt repo (\nNote:\n There is \n-\n after the add):\n\n\nwget -qO - https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/mynewt.gpg.key | sudo apt-key add -\n\n\n\n\n\n\n\nAdd the repository for the binary and source packages to the apt source list:\n\n\n$sudo -s\n[sudo] password for \nuser\n:\nroot$ cat \
n /etc/apt/sources.list.d/mynewt.list \nEOF\ndeb https://raw.githubusercontent.com/runtimeco/debian-package/master latest main\ndeb-src https://raw.githubusercontent.com/runtimeco/debian-package/master latest main\nEOF\n\n\n\n\n\n\nCheck the content of the file:\n\n\nroot$more /etc/apt/sources.list.d//mynewt.list\ndeb https://raw.githubusercontent.com/runtimeco/debian-package/master latest main\ndeb-src https://raw.githubusercontent.com/runtimeco/debian-package/master latest main\n\n\n\n\n\n \n\n\nExit the root shell:\n\n\nroot$exit\n\n\n\n\n\n\n\nInstalling the Latest Release of Newt from a Binary Package\n\n\nFor Linux amd64 platform, you can install the latest stable version (1.0.0) of newt from the newt Debian binary package:\n\n\n$sudo apt-get update\n$sudo apt-get install newt\nReading package lists... Done\nBuilding dependency tree \nReading state information... Done\n\n ...\n\nPreparing to unpack .../newt_1.0.0-1_amd64.deb ...\nUnpacking newt (1.0.0-1) ...\nSettin
g up newt (1.0.0-1) ...\n\n\n\n\n\n\nSee \nChecking the Installed Version of Newt\n to verify that you are using the installed version of newt.\n\n\n\n\nInstalling the Latest Stable Release of Newt from a Source Package\n\n\nIf you are running Linux on a different architecture, you can install the Debian source package for the latest stable release (1.0.0) of newt. The installation of the source package builds the newt binary and creates a Debian binary package that you then install.\n\n\nNote\n: Newt version 1.0.0 has been tested on Linux amd64 platform. Version 1.0.0 does not build on the 32 bit platform but have been fixed for the next release.\n\n\n\n\nInstalling Go 1.7\n\n\nYou need Go version 1.7 or higher to build Newt version 1.0.0. Currently, the latest Go version that Ubuntu installs is 1.6. Run \ngo version\n to check if you have Go 1.7 installed. \n\n\n\n\nInstall Go version 1.7:\n\n\n$sudo apt-get install golang-1.7-go\nReading package lists... Done\n ...\nUnpacki
ng golang-1.7-go (1.7.1-2ubuntu1) ...\nSetting up golang-1.7-go (1.7.1-2ubuntu1) ...\n$\n$sudo ln -sf ../lib/go-1.7/bin/go /usr/bin/go\n$go version\ngo version go1.7.1 linux/amd64\n\n\n\n\n\nYou can also download version 1.7 from \nhttps://golang.org/dl/\n. \n\n\n\n\nInstalling from the Source Package\n\n\nCreate a directory and change into the directory, download the source package, and build a binary package from the source package:\n\n\nmkdir newt_source\n$cd newt_source\n$sudo apt-get --build source newt\n[sudo] password for \nuser\n: \nReading package lists... Done\nNeed to get 1,866 kB of source archives.\nGet:1 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newt 1.0.0-1 (dsc) [795 B]\nGet:2 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newt 1.0.0-1 (tar) [1,864 kB]\nGet:3 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newt 1.0.0-1 (diff) [2,000 B]\nFetched 1,866 kB in 1s (1,222 kB/s)\nd
pkg-source: warning: extracting unsigned source package (newt_1.0.0-1.dsc)\ndpkg-source: info: extracting newt in newt-1.0.0\ndpkg-source: info: unpacking newt_1.0.0.orig.tar.gz\ndpkg-source: info: unpacking newt_1.0.0-1.debian.tar.xz\n\n ...\n\ndpkg-deb: building package \nnewt\n in \n../newt_1.0.0-1_amd64.deb\n.\n dpkg-genchanges --build=any,all \n../newt_1.0.0-1_amd64.changes\ndpkg-genchanges: info: binary-only upload (no source code included)\n dpkg-source --after-build newt-1.0.0\ndpkg-buildpackage: info: binary-only upload (no source included)\nW: Can\nt drop privileges for downloading as file \nnewt_1.0.0-1.dsc\n couldn\nt be accessed by user \n_apt\n. - pkgAcquire::Run (13: Permission denied)\n\n\n\n\n\nNote:\n You can ignore the \"Permission denied: warning message at the end of the command.\n\n\n\nInstall the newt binary package that is created from the source package:\n\n\n$sudo dpkg -i newt_1.0.0-1_amd64.deb \nSelecting previously unselected package newt.\n(Rea
ding database ... 252969 files and directories currently installed.)\nPreparing to unpack newt_1.0.0-1_amd64.deb ...\nUnpacking newt (1.0.0-1) ...\nSetting up newt (1.0.0-1) ...\n\n\n\n\n\n\n\n Checking the Installed Version of Newt\n\n\nAfter you have installed newt from either a Debian binary or source package, check that you are using the installed version of newt from \n/usr/bin\n. \n\n\nCheck the modification time of the binary and the newt tool that you are using:\n\n\n$ls -l /usr/bin/newt\n-rwxr-xr-x 1 root root 6919280 Apr 22 10:09 /usr/bin/newt\n$which newt\n/usr/bin/newt\n$newt version\nApache Newt (incubating) version: 1.0.0\n\n\n\n\n\nNote:\n If you previously built newt from source and the output of \nwhich newt\n shows \"$GOPATH/bin/newt\", you will need to move \"$GOPATH/bin\" after \"/usr/bin\" in your $PATH and export your $PATH.\n\n\n\nGet information about newt:\n\n\n$newt\nNewt allows you to create your own embedded application based on the Mynewt\noperating syst
em. Newt provides both build and package management in a single\ntool, which allows you to compose an embedded application, and set of\nprojects, and then build the necessary artifacts from those projects. For more\ninformation on the Mynewt operating system, please visit\nhttps://mynewt.apache.org/.\n\nPlease use the newt help command, and specify the name of the command you want\nhelp for, for help on how to use a specific command\n\nUsage:\n newt [flags]\n newt [command]\n\nExamples:\n newt\n newt help [\ncommand-name\n]\n For help on \ncommand-name\n. If not specified, print this message.\n\nAvailable Commands:\n build Build one or more targets\n clean Delete build artifacts for one or more targets\n create-image Add image header to target binary\n debug Open debugger session to target\n info Show project info\n install Install project dependencies\n load Load built target to board\n mfg Manufacturing flash image
commands\n new Create a new project\n pkg Create and manage packages in the current workspace\n run build/create-image/download/debug \ntarget\n\n size Size of target components\n sync Synchronize project dependencies\n target Commands to create, delete, configure, and query targets\n test Executes unit tests for one or more packages\n upgrade Upgrade project dependencies\n vals Display valid values for the specified element type(s)\n version Display the Newt version number\n\nFlags:\n -h, --help Help for newt commands\n -j, --jobs int Number of concurrent build jobs (default 8)\n -l, --loglevel string Log level (default \nWARN\n)\n -o, --outfile string Filename to tee output to\n -q, --quiet Be quiet; only display error output\n -s, --silent Be silent; don\nt output anything\n -v, --verbose Enable verbose output when executing comm
ands\n\nUse \nnewt [command] --help\n for more information about a command.",
"title": "Install Newt on Linux"
},
{
- "location": "/newt/install/newt_linux/#install-newt-tool-on-linux",
- "text": "",
- "title": "Install newt tool on Linux"
- },
- {
- "location": "/newt/install/newt_linux/#getting-your-linux-box-ready",
- "text": "If you want to build the newt tool from its source code, follow the following steps:",
- "title": "Getting your Linux box Ready"
+ "location": "/newt/install/newt_linux/#installing-newt-on-linux",
+ "text": "You can install the latest stable release (1.0.0) of newt from a Debian binary package (amd64) or from a Debian source package. This page shows you how to: Set up your computer to retrieve Debian packages from the runtimeco debian package repository. Install the latest stable release version of newt from a Debian binary package. Install the latest stable release version of newt from a Debian source package. If you are running on an amd64 platform, we recommend that you install from the binary package. Note: See Setting Up an Go Environment to Contribute to Newt and Newtmgr Tools if you want to: Use the newt tool with the latest updates from the master branch. The master branch may be unstable and we recommend that you use the latest stable release version. Contribute to the newt tool.",
+ "title": "Installing Newt on Linux"
},
{
- "location": "/newt/install/newt_linux/#1-install-git-libcurl",
- "text": "$ sudo apt-get install git \n $ sudo apt-get install libcurl4-gnutls-dev NOTE: On 64-bit host, you may also need to install gcc-multilib, if you encounter compilation errors related to 'sys/cdefs.h'",
- "title": "1. Install git, libcurl"
+ "location": "/newt/install/newt_linux/#setting-up-your-computer-to-get-packages-from-runtimeco",
+ "text": "The newt Debian packages are stored in a private repository on https://github/runtimeco/debian-mynewt . Note: You will only need to perform these steps only once on your computer.\nThe following steps must be performed on your computer: Add the apt-transport-https package to use HTTPS to retrieve packages. Download the public key for the runtimeco debian repository and import the key into the apt keychain. Add the repository for the binary and source packages to the apt source list. \nAdd the apt-transport-https package: $sudo apt-get update\n$sudo apt-get install apt-transport-https Download the public key for the runtimeco apt repo ( Note: There is - after the add): wget -qO - https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/mynewt.gpg.key | sudo apt-key add - Add the repository for the binary and source packages to the apt source list: $sudo -s\n[sudo] password for user :\nroot$ cat /etc/apt/sources.list.d/mynewt.lis
t EOF\ndeb https://raw.githubusercontent.com/runtimeco/debian-package/master latest main\ndeb-src https://raw.githubusercontent.com/runtimeco/debian-package/master latest main\nEOF \nCheck the content of the file: root$more /etc/apt/sources.list.d//mynewt.list\ndeb https://raw.githubusercontent.com/runtimeco/debian-package/master latest main\ndeb-src https://raw.githubusercontent.com/runtimeco/debian-package/master latest main Exit the root shell: root$exit",
+ "title": "Setting Up Your Computer to Get Packages from runtimeco"
},
{
- "location": "/newt/install/newt_linux/#2-install-go-the-programming-language",
- "text": "Go language environment dictates a directory structure. Known in Go parlance as a workspace, it must contain three sibling directories with the directory names src, pkg and bin, as explained below. src contains Go source files organized into packages (one package per directory), pkg contains package objects, and bin contains executable commands. The GOPATH environment variable specifies the location of your workspace. To setup this workspace environment, create a 'dev' directory and then a 'go' directory under it. Set the GOPATH environment variable to this directory where you will soon clone the newt tool repository. $ cd $HOME\n $ mkdir -p dev/go \n $ cd dev/go\n $ export GOPATH=`pwd` (Note that you need to add export statements to ~/.bash_profile to export variables permanently. Don't forget to source the file for the change to go into effect.) $ vi ~/.bash_profile\n $ source ~/.bash_profile
Next, install Go. When installed, Go offers you as a developer a language environment (to compile Go code), construct Go packages (to assemble Go packages) and import Go code (from github). In the next step, you will use the Go commands to import newt repo into your local Go environment. Note : The Newt tool requires Go version 1.7 or later. Currently, the latest Go version that Ubuntu installs is 1.6. You can run apt-get install golang-1.7-go to install version 1.7. You can also download version 1.7 from https://golang.org/dl/ . $sudo apt-get install golang-1.7-go\nReading package lists... Done\n ...\nUnpacking golang-1.7-go (1.7.1-2ubuntu1) ...\nSetting up golang-1.7-go (1.7.1-2ubuntu1) ...\n$\n$sudo ln -s /usr/lib/go-1.7/bin/go /usr/bin/go\n$go version\ngo version go1.7.1 linux/amd64",
- "title": "2. Install Go, the programming language"
+ "location": "/newt/install/newt_linux/#installing-the-latest-release-of-newt-from-a-binary-package",
+ "text": "For Linux amd64 platform, you can install the latest stable version (1.0.0) of newt from the newt Debian binary package: $sudo apt-get update\n$sudo apt-get install newt\nReading package lists... Done\nBuilding dependency tree \nReading state information... Done\n\n ...\n\nPreparing to unpack .../newt_1.0.0-1_amd64.deb ...\nUnpacking newt (1.0.0-1) ...\nSetting up newt (1.0.0-1) ... \nSee Checking the Installed Version of Newt to verify that you are using the installed version of newt.",
+ "title": "Installing the Latest Release of Newt from a Binary Package"
},
{
- "location": "/newt/install/newt_linux/#3-create-local-repository",
- "text": "Use Go commands to copy the directory (currently the ASF incubator directory). Be patient as it may take a minute or two. Check the directories installed. $ go get mynewt.apache.org/newt/... Check that newt.go is in place. $ ls $GOPATH/src/mynewt.apache.org/newt\n DISCLAIMER NOTICE newt newtvm viper\n LICENSE README.md newtmgr util yaml",
- "title": "3. Create local repository"
+ "location": "/newt/install/newt_linux/#installing-the-latest-stable-release-of-newt-from-a-source-package",
+ "text": "If you are running Linux on a different architecture, you can install the Debian source package for the latest stable release (1.0.0) of newt. The installation of the source package builds the newt binary and creates a Debian binary package that you then install. Note : Newt version 1.0.0 has been tested on Linux amd64 platform. Version 1.0.0 does not build on the 32 bit platform but have been fixed for the next release.",
+ "title": "Installing the Latest Stable Release of Newt from a Source Package"
},
{
- "location": "/newt/install/newt_linux/#4-build-the-newt-tool",
- "text": "Use Go to run the newt.go program to build the newt tool. The command go install compiles and writes the resulting executable to an output file named newt , which is then installed, along with its dependencies, in $GOPATH/bin. If you get errors it is likely because of path resolution issues. Try go build followed by go install in that case. $ cd $GOPATH/src/mynewt.apache.org/newt/newt\n $ go install\n $ ls $GOPATH /bin/\n newt newtmgr newtvm At this point, you can try using newt . For example, check for the version number by typing 'newt version'. See all the possible commands available to a user of newt by typing 'newt -h'. (Note: If you are going to be modifying the newt often and going to be compile the program every time you call it, you will want to store the command in a variable in your .bash_profile. So type in export newt=\"go run $GOPATH/mynewt.apache.org/newt/newt/newt.go\" in your .bash_profile and
execute it by calling $newt at the prompt instead of newt . Essentially, $newt calls go run which runs the compiled binary directly without producing an executable. Don't forget to reload the updated bash profile by typing source ~/.bash_profile at the prompt! ) $ newt version\n Newt version: 1.0\n $ newt -h\n Newt allows you to create your own embedded application based on the Mynewt \n operating system. Newt provides both build and package management in a single \n tool, which allows you to compose an embedded application, and set of \n projects, and then build the necessary artifacts from those projects. For more \n information on the Mynewt operating system, please visit \n https://mynewt.apache.org/. \n\n Please use the newt help command, and specify the name of the command you want \n help for, for help on how to use a specific command\n\n Usage:\n newt [flags]\n n
ewt [command]\n\n Examples:\n newt\n newt help [ command-name ]\n For help on command-name . If not specified, print this message.\n\n Available Commands:\n build Build one or more targets\n clean Delete build artifacts for one or more targets\n create-image Add image header to target binary\n debug Open debugger session to target\n info Show project info\n install Install project dependencies\n load Load built target to board\n mfg Manufacturing flash image commands\n new Create a new project\n pkg Create and manage packages in the current workspace\n run build/create-image/download/debug target \n size Size of target components\n sync Synchronize project dependencies\n target Commands to create, delete, configure,
and query targets\n test Executes unit tests for one or more packages\n upgrade Upgrade project dependencies\n vals Display valid values for the specified element type(s)\n version Display the Newt version number\n\n Flags:\n -h, --help Help for newt commands\n -j, --jobs int Number of concurrent build jobs (default 8)\n -l, --loglevel string Log level (default WARN )\n -o, --outfile string Filename to tee output to\n -q, --quiet Be quiet; only display error output\n -s, --silent Be silent; don t output anything\n -v, --verbose Enable verbose output when executing commands\n\n Use newt [command] --help for more information about a comma",
- "title": "4. Build the Newt tool"
+ "location": "/newt/install/newt_linux/#installing-go-17",
+ "text": "You need Go version 1.7 or higher to build Newt version 1.0.0. Currently, the latest Go version that Ubuntu installs is 1.6. Run go version to check if you have Go 1.7 installed. Install Go version 1.7: $sudo apt-get install golang-1.7-go\nReading package lists... Done\n ...\nUnpacking golang-1.7-go (1.7.1-2ubuntu1) ...\nSetting up golang-1.7-go (1.7.1-2ubuntu1) ...\n$\n$sudo ln -sf ../lib/go-1.7/bin/go /usr/bin/go\n$go version\ngo version go1.7.1 linux/amd64 You can also download version 1.7 from https://golang.org/dl/ .",
+ "title": "Installing Go 1.7"
},
{
- "location": "/newt/install/newt_linux/#5-updating-the-newt-tool",
- "text": "You will update the newt tool in the same place as you initially installed the newt tool. Start by updating the git repository of the newt tool (you can change to a different branch using git checkout [branch] if you need to) Then update each of the tools newt, newtmgr and newtvm as needed $ cd $GOPATH/src/mynewt.apache.org/newt\n $ git pull\n $ cd newt\n $ go install\n $ cd ../newtmgr\n $ go install\n $ cd ../newtvm\n $ go install\n $ ls $GOPATH /bin/\n newt newtmgr newtvm That should have updated your newt, newtmgr and newtvm to the latest versions based on the git repository you used.",
- "title": "5. Updating the Newt tool"
+ "location": "/newt/install/newt_linux/#installing-from-the-source-package",
+ "text": "Create a directory and change into the directory, download the source package, and build a binary package from the source package: mkdir newt_source\n$cd newt_source\n$sudo apt-get --build source newt\n[sudo] password for user : \nReading package lists... Done\nNeed to get 1,866 kB of source archives.\nGet:1 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newt 1.0.0-1 (dsc) [795 B]\nGet:2 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newt 1.0.0-1 (tar) [1,864 kB]\nGet:3 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newt 1.0.0-1 (diff) [2,000 B]\nFetched 1,866 kB in 1s (1,222 kB/s)\ndpkg-source: warning: extracting unsigned source package (newt_1.0.0-1.dsc)\ndpkg-source: info: extracting newt in newt-1.0.0\ndpkg-source: info: unpacking newt_1.0.0.orig.tar.gz\ndpkg-source: info: unpacking newt_1.0.0-1.debian.tar.xz\n\n ...\n\ndpkg-deb: building package newt in
../newt_1.0.0-1_amd64.deb .\n dpkg-genchanges --build=any,all ../newt_1.0.0-1_amd64.changes\ndpkg-genchanges: info: binary-only upload (no source code included)\n dpkg-source --after-build newt-1.0.0\ndpkg-buildpackage: info: binary-only upload (no source included)\nW: Can t drop privileges for downloading as file newt_1.0.0-1.dsc couldn t be accessed by user _apt . - pkgAcquire::Run (13: Permission denied) Note: You can ignore the \"Permission denied: warning message at the end of the command. \nInstall the newt binary package that is created from the source package: $sudo dpkg -i newt_1.0.0-1_amd64.deb \nSelecting previously unselected package newt.\n(Reading database ... 252969 files and directories currently installed.)\nPreparing to unpack newt_1.0.0-1_amd64.deb ...\nUnpacking newt (1.0.0-1) ...\nSetting up newt (1.0.0-1) ...",
+ "title": "Installing from the Source Package"
},
{
"location": "/os/get_started/cross_tools/",
- "text": "Installing Cross Tools for ARM\n\n\nThis page shows how to install tools on your laptop/computer to use for direct communication (e.g. for debugging) with some ARM based HW platforms running Apache Mynewt. You will also have to use the Newt tool installed to run natively on your machine. You may choose to do this instead of using the build toolchain and Newt tool available in a Docker container.\n\n\nThis page provides guidance for installing the tools directly on your MAC and Linux machine. See the relevant sections below.\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 upda
te\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 you
r\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\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/bin/openocd -\n ../Cellar/open-ocd/0.9.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/~team-gcc-arm-embedded/+archive/ubuntu/ppa\n.\n\n\n$ sudo apt-get remove binutils-arm-none-eabi gcc-arm-none-eabi \n$ sudo add-apt-repository ppa:team-gcc-arm-embedded/ppa\n$ sudo apt-get update \n$ sudo apt-get install gcc-arm-none-eabi\n$ sudo apt-get install gdb-arm-none-eabi\n\n\n\n\n\n\n\nInstall OpenOCD\n\n\nOpenOCD (Open On-Chip D
ebugger) 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.",
+ "text": "Installing Cross Tools for ARM\n\n\nThis page shows how to install tools on your laptop/computer to use for direct communication (e.g. for debugging) with some ARM based HW platforms running Apache Mynewt. It shows you how to install the following tools for Mac OS X and Linux:\n\n\n\n\nARM Cross toolchain\n\n\nDebugger to load and debug your device\n\n\n\n\n\n\nInstall ARM Cross Toolchain\n\n\nInstall ARM Toolchain For Mac OS X\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/embe
dded-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 ARM Toolchain For Linux\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/~team-gcc-arm-embedded/+archive/ubuntu/ppa\n.\n\n\n$
sudo apt-get remove binutils-arm-none-eabi gcc-arm-none-eabi \n$ sudo add-apt-repository ppa:team-gcc-arm-embedded/ppa\n$ sudo apt-get update \n$ sudo apt-get install gcc-arm-none-eabi\n$ sudo apt-get install gdb-arm-none-eabi\n\n\n\n\n\n\n\nInstall Debugger\n\n\nMynewt uses, depending on the board, either the OpenOCD or SEGGER J-Link debugger. \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\nOpenOCD version 0.10.0 with nrf52 support is required. A binary for this version is available to download for Mac OS and Linux.\n\n\n\n\nInstall OpenOCD on Mac OS\n\n\nStep 1: Download the \nbinary tarball for Mac OS\n.\n\n\nStep 2: Change to the root directory: \n\n\n$cd / \n\n\n\n\n\n\nStep 3: Untar the tarball and install into \n /usr/local/
bin\n. You will need to replace \n ~/Downloads \n with the directory that the tarball is downloaded to. \n\n\nsudo tar -xf ~/Downloads/openocd-bin-0.10.0-MacOS.tgz ` \n\n\n\n\n\n\nStep 4: Check the OpenOCD version you are using: \n\n\n$which openocd\n/usr/local/bin/openocd\n$openocd -v\nOpen On-Chip Debugger 0.10.0\nLicensed under GNU GPL v2\nFor bug reports, read\nhttp://openocd.org/doc/doxygen/bugs.html\n\n\n\n\n\nYou should see version: \n0.10.0\n. \n\n\n\n\nInstall OpenOCD on Linux\n\n\nStep 1: Download the \nbinary tarball for Linux\n\n\nStep 2: Change to the root directory: \n\n\n$cd / \n\n\n\n\n\n\nStep 3: Untar the tarball and install into \n /usr/local/bin\n. You will need to replace \n ~/Downloads \n with the directory that the tarball is downloaded to. \n\n\n Note:\n You must specify the -p option for the tar command.\n\n\n$sudo tar -xpf ~/Downloads/openocd-bin-0.10.0-Linux.tgz\n\n\n\n\n\n\nStep 4: Check the OpenOCD version you are using: \n\n\n$which openocd\n/usr/lo
cal/bin/openocd\n$openocd -v\nOpen On-Chip Debugger 0.10.0\nLicensed under GNU GPL v2\nFor bug reports, read\nhttp://openocd.org/doc/doxygen/bugs.html\n\n\n\n\n\nYou should see version: \n0.10.0\n. \n\n\nIf you see any of these error messages:\n\n\n\n\n\n\nopenocd: error while loading shared libraries: libhidapi-hidraw.so.0: cannot open shared object file: No such file or directory\n\n\n\n\n\n\nopenocd: error while loading shared libraries: libusb-1.0.so.0: cannot open shared object file: No such file or directory \n\n\n\n\n\n\nrun the following command to install the libraries: \n\n\n$sudo apt-get install libhidapi-dev:i386\n\n\n\n\n\n\n\nInstall SEGGAR J-Link\n\n\nYou can download and install Segger J-LINK Software and documentation pack from \nSEGGER\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 on your laptop/computer to use for direct communication (e.g. for debugging) with some ARM based HW platforms running Apache Mynewt. You will also have to use the Newt tool installed to run natively on your machine. You may choose to do this instead of using the build toolchain and Newt tool available in a Docker container. This page provides guidance for installing the tools directly on your MAC and Linux machine. See the relevant sections below.",
+ "text": "This page shows how to install tools on your laptop/computer to use for direct communication (e.g. for debugging) with some ARM based HW platforms running Apache Mynewt. It shows you how to install the following tools for Mac OS X and Linux: ARM Cross toolchain Debugger to load and debug your device",
"title": "Installing Cross Tools for ARM"
},
{
- "location": "/os/get_started/cross_tools/#install-arm-cross-tools-in-mac-os-x",
+ "location": "/os/get_started/cross_tools/#install-arm-cross-toolchain",
"text": "",
- "title": "Install ARM Cross tools in Mac OS X"
+ "title": "Install ARM Cross Toolchain"
},
{
- "location": "/os/get_started/cross_tools/#install-tool-chain",
+ "location": "/os/get_started/cross_tools/#install-arm-toolchain-for-mac-os-x",
"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"
+ "title": "Install ARM Toolchain For Mac OS X"
+ },
+ {
+ "location": "/os/get_started/cross_tools/#install-arm-toolchain-for-linux",
+ "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/~team-gcc-arm-embedded/+archive/ubuntu/ppa . $ sudo apt-get remove binutils-arm-none-eabi gcc-arm-none-eabi \n$ sudo add-apt-repository ppa:team-gcc-arm-embedded/ppa\n$ sudo apt-get update \n$ sudo apt-get install gcc-arm-none-eabi\n$ sudo apt-get install gdb-arm-none-eabi",
+ "title": "Install ARM Toolchain For Linux"
+ },
+ {
+ "location": "/os/get_started/cross_tools/#install-debugger",
+ "text": "Mynewt uses, depending on the board, either the OpenOCD or SEGGER J-Link debugger.",
+ "title": "Install Debugger"
},
{
"location": "/os/get_started/cross_tools/#install-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 . $ 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.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 . OpenOCD version 0.10.0 with nrf52 support is required. A binary for this version is available to download for Mac OS and Linux.",
"title": "Install OpenOCD"
},
{
- "location": "/os/get_started/cross_tools/#install-arm-cross-arm-tools-for-linux",
- "text": "",
- "title": "Install ARM cross arm tools for Linux"
+ "location": "/os/get_started/cross_tools/#install-openocd-on-mac-os",
+ "text": "Step 1: Download the binary tarball for Mac OS . Step 2: Change to the root directory: $cd / \nStep 3: Untar the tarball and install into /usr/local/bin . You will need to replace ~/Downloads with the directory that the tarball is downloaded to. sudo tar -xf ~/Downloads/openocd-bin-0.10.0-MacOS.tgz ` \nStep 4: Check the OpenOCD version you are using: $which openocd\n/usr/local/bin/openocd\n$openocd -v\nOpen On-Chip Debugger 0.10.0\nLicensed under GNU GPL v2\nFor bug reports, read\nhttp://openocd.org/doc/doxygen/bugs.html You should see version: 0.10.0 .",
+ "title": "Install OpenOCD on Mac OS"
},
{
- "location": "/os/get_started/cross_tools/#install-tool-chain_1",
- "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/~team-gcc-arm-embedded/+archive/ubuntu/ppa . $ sudo apt-get remove binutils-arm-none-eabi gcc-arm-none-eabi \n$ sudo add-apt-repository ppa:team-gcc-arm-embedded/ppa\n$ sudo apt-get update \n$ sudo apt-get install gcc-arm-none-eabi\n$ sudo apt-get install gdb-arm-none-eabi",
- "title": "Install Tool Chain"
+ "location": "/os/get_started/cross_tools/#install-openocd-on-linux",
+ "text": "Step 1: Download the binary tarball for Linux Step 2: Change to the root directory: $cd / \nStep 3: Untar the tarball and install into /usr/local/bin . You will need to replace ~/Downloads with the directory that the tarball is downloaded to. Note: You must specify the -p option for the tar command. $sudo tar -xpf ~/Downloads/openocd-bin-0.10.0-Linux.tgz \nStep 4: Check the OpenOCD version you are using: $which openocd\n/usr/local/bin/openocd\n$openocd -v\nOpen On-Chip Debugger 0.10.0\nLicensed under GNU GPL v2\nFor bug reports, read\nhttp://openocd.org/doc/doxygen/bugs.html You should see version: 0.10.0 . If you see any of these error messages: openocd: error while loading shared libraries: libhidapi-hidraw.so.0: cannot open shared object file: No such file or directory openocd: error while loading shared libraries: libusb-1.0.so.0: cannot open shared object file: No such file or directory run the following command to instal
l the libraries: $sudo apt-get install libhidapi-dev:i386",
+ "title": "Install OpenOCD on Linux"
},
{
- "location": "/os/get_started/cross_tools/#install-openocd_1",
- "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"
+ "location": "/os/get_started/cross_tools/#install-seggar-j-link",
+ "text": "You can download and install Segger J-LINK Software and documentation pack from SEGGER .",
+ "title": "Install SEGGAR J-Link"
},
{
"location": "/os/get_started/docker/",
@@ -347,7 +352,7 @@
},
{
"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\n\n\nPre-Requisites\n\n\n\n\nNewt:\n\n\nIf you have taken the Docker route, you have already installed Newt.\n\n\nIf you have taken the native install route, you have to ensure that you have installed the Newt tool following the instructions for \nMac\n or \nLinux\n as appropriate, and that the \nnewt\n command is in your system path. \n\n\n\n\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 crea
ted.\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\nNote\n: If you do not have \ntree\n, install it by running \nbrew install tree\n.\n\n\n$ cd myproj\n$ tree \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\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\n6 directories, 11 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 \ntarget\n 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 internally 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\nNOTE:\n By default newt uses the code in the master branch. This is the latest stable\ncode
for newt. If you need to use a different branch, you can set this in the project.yml\nfile. \n\n\nrepository.apache-mynewt-core:\n type: github\n vers: 1-latest\n user: apache\n repo: incubator-mynewt-core\n\n\n\n\n\nChanging to 1-dev will put you on the develop branch. \nThe Develop Branch may not be stable and you may encounter bugs or other problems.\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\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 v
iew them by issuing the following commands in the base directory of the new project. The actual output will depend on what is in the latest 'master' branch you have pulled from.\n\n\n$ tree -L 2 repos/apache-mynewt-core/\n\nrepos/apache-mynewt-core/\n\u251c\u2500\u2500 CODING_STANDARDS.md\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 RELEASE_NOTES.md\n\u251c\u2500\u2500 apps\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 blecent\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 blehci\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 bleprph\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 bleprph_oic\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 blesplit\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 bletest\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 bletiny\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 bleuart\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 boot\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 fat2native\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 ffs2native\n\u25
02\u00a0\u00a0 \u251c\u2500\u2500 ocf_sample\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 slinky\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 slinky_oic\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 spitest\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 splitty\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 test\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 testbench\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 timtest\n\u251c\u2500\u2500 boot\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 boot_serial\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 bootutil\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 split\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 split_app\n\u251c\u2500\u2500 compiler\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 arm-none-eabi-m0\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 arm-none-eabi-m4\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 gdbmacros\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 mips\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 sim\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 sim-mips\n\u251c\u2500\u2500 crypto\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 mbedtls\n\u25
02\u00a0\u00a0 \u2514\u2500\u2500 tinycrypt\n\u251c\u2500\u2500 docs\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 doxygen.xml\n\u251c\u2500\u2500 encoding\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 base64\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 cborattr\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 json\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 tinycbor\n\u251c\u2500\u2500 fs\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 disk\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 fatfs\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 fcb\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 cmsis-core\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 drivers\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 hal\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 mcu\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 scripts\n\u251c\u2500\u2500 kernel\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 os\n\u251c\u2500\u2500 libc\n\u2502\u00a0\u00a0 \u2514\u250
0\u2500 baselibc\n\u251c\u2500\u2500 mgmt\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 imgmgr\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 mgmt\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 newtmgr\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 oicmgr\n\u251c\u2500\u2500 net\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 ip\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 nimble\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 oic\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 wifi\n\u251c\u2500\u2500 project.yml\n\u251c\u2500\u2500 repository.yml\n\u251c\u2500\u2500 sys\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 config\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 console\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 coredump\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 defs\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 flash_map\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 id\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 log\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 mfg\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 reboot\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 shell\n\u2502\u00a0\u00a0 \u251c\u2
500\u2500 stats\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 sysinit\n\u251c\u2500\u2500 targets\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 unittest\n\u251c\u2500\u2500 test\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 crash_test\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 flash_test\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 runtest\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 testutil\n\u251c\u2500\u2500 time\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 datetime\n\u2514\u2500\u2500 util\n \u251c\u2500\u2500 cbmem\n \u251c\u2500\u2500 crc\n \u2514\u2500\u2500 mem\n\n94 directories, 9 files\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\nYou have already built your first basic project. You can ask Newt to execute the unit tests in a package. For example, to test the \nsys/config\n package in the \napache-mynewt-core\n repo, call newt as shown below.\n\n\n$ newt test @apache-mynewt-core/sys/config\
nTesting package @apache-mynewt-core/sys/config/test-fcb\nCompiling bootutil_misc.c\nCompiling image_ec.c\nCompiling image_rsa.c\nCompiling image_validate.c\n\n ...\n\nLinking ~/dev/myproj/bin/targets/unittest/sys_config_test-fcb/app/sys/config/test-fcb/sys_config_test-fcb.elf\nExecuting test: ~/dev/myproj/bin/targets/unittest/sys_config_test-fcb/app/sys/config/test-fcb/sys_config_test-fcb.elf\nTesting package @apache-mynewt-core/sys/config/test-nffs\nCompiling repos/apache-mynewt-core/encoding/base64/src/hex.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_cli.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_dirent.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_mkdir.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_mount.c\nCompiling repos/apache-mynewt-core/encoding/base64/src/base64.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_file.c\nCompiling repos/apache-mynewt-core/fs/disk/src/disk.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_nmgr.c\nCompiling repos/a
pache-mynewt-core/fs/fs/src/fsutil.c\nCompiling repos/apache-mynewt-core/fs/nffs/src/nffs.c\n\n ...\n\nLinking ~/dev/myproj/bin/targets/unittest/sys_config_test-nffs/app/sys/config/test-nffs/sys_config_test-nffs.elf\nExecuting test: ~/dev/myproj/bin/targets/unittest/sys_config_test-nffs/app/sys/config/test-nffs/sys_config_test-nffs.elf\nPassed tests: [sys/config/test-fcb sys/config/test-nffs]\nAll tests passed\n\n\n\n\n\nNOTE:\n If you've installed the latest gcc using homebrew on your Mac, you will likely be running gcc-6. Make sure you have adjusted the compiler.yml configuration to reflect that as noted in \nNative Install Option\n. You can choose to downgrade to gcc-5 in order to use the default gcc compiler configuration for MyNewt.\n\n\nNOTE:\n If you are running the standard gcc for 64-bit machines, it does not support 32-bit. In that case you will see compilation errors. You need to install multiboot gcc (e.g. gcc-multilib if you running on a 64-bit Ubuntu).\n\n\n$ brew
uninstall gcc-6\n$ brew link gcc-5\n\n\n\n\n\n\n\nTo test all the packages in a project, specify \nall\n instead of the package name.\n\n\n$ newt test all\nTesting package @apache-mynewt-core/boot/boot_serial/test\nCompiling repos/apache-mynewt-core/boot/boot_serial/test/src/boot_test.c\nCompiling repos/apache-mynewt-core/boot/boot_serial/test/src/testcases/boot_serial_setup.c\n\n ...\n\nLinking ~/dev/myproj/bin/targets/unittest/boot_boot_serial_test/app/boot/boot_serial/test/boot_boot_serial_test.elf\n\n...lots of compiling and testing...\n\nLinking ~/dev/myproj/bin/targets/unittest/util_cbmem_test/app/util/cbmem/test/util_cbmem_test.elf\nExecuting test: ~/dev/myproj/bin/targets/unittest/util_cbmem_test/app/util/cbmem/test/util_cbmem_test.elf\nPassed tests: [boot/boot_serial/test boot/bootutil/test crypto/mbedtls/test encoding/base64/test encoding/cborattr/test encoding/json/test fs/fcb/test fs/nffs/test kernel/os/test net/ip/mn_socket/test net/nimble/host/test net/oic/test sys
/config/test-fcb sys/config/test-nffs sys/flash_map/test sys/log/full/test util/cbmem/test]\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 \nBuilding target targets/my_blinky_sim\nCompiling repos/apache-mynewt-core/hw/hal/src/hal_common.c\nCompiling repos/apache-mynewt-core/hw/drivers/uart/src/uart.c\nCompiling repos/apache-mynewt-core/hw/hal/src/hal_flash.c\nCompiling repos/apache-mynewt-core/hw/bsp/native/src/hal_bsp.c\nCompiling repos/apache-mynewt-core/hw/drivers/uart/uart_hal/src/uart_hal.c\nCompiling apps/blinky/src/main.c\n\n ...\n\n\nArchiving sys_mfg.a\nArchiving sys_sysinit.a\nArchiving util_mem.a\nLinking ~/dev/myproj/bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf\nTarget successfully built: targets/my_blinky_sim\n\n\n\n\n\n\n\nRun the Project\n\n\nYou can run the simulated version of your project and see the simulated LED\nblink. If you are using n
ewt docker, use \nnewt run\n to run the simulated binary.\n\n\n$ newt run my_blinky_sim\nLoading app image into slot 1\n ...\nDebugging ~/dev/myproj/bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf\n ...\nReading symbols from /bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf...done.\n(gdb)\n\n\n\n\n\nType \nr\n at the \n(gdb)\n prompt to run the project. You will see an output indicating that the hal_gpio pin is toggling between 1 and 0 in a simulated blink.\n\n\nIf you natively install the toolchain, you can either use \nnewt run\n or call the binary directly. Generally, \nnewt run\n is the expected way to call things.\n\n\n$ ./bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf\nhal_gpio set pin 1 to 0\n\n\n\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 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.\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!",
+ "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\nNewt:\n\n\nIf you have taken the Docker route, you have already installed Newt.\n\n\nIf you have taken the native install route, you have to ensure that you have installed the Newt tool following the instructions for \nMac\n or \nLinux\n as appropriate, and that the \nnewt\n command is in your system path. \n\n\n\n\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 crea
ted.\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\nNote\n: If you do not have \ntree\n, install it by running \nbrew install tree\n.\n\n\n$ cd myproj\n$ tree \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\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\n6 directories, 11 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 \ntarget\n 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 internally by \nnewt\n and is not a formal build target.\n\n\n\n\nNOTE:\n The actual code and package
<TRUNCATED>