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/05/22 16:41:04 UTC
[1/5] incubator-mynewt-site git commit: This closes #183. This closes
#184. Adding instructions to use Visual Studio for Mynewt developers
Repository: incubator-mynewt-site
Updated Branches:
refs/heads/asf-site 72f0a4461 -> 65dc6d41a
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/latest/newt/install/newt_windows/index.html
----------------------------------------------------------------------
diff --git a/latest/newt/install/newt_windows/index.html b/latest/newt/install/newt_windows/index.html
index aa11a7e..84b7359 100644
--- a/latest/newt/install/newt_windows/index.html
+++ b/latest/newt/install/newt_windows/index.html
@@ -491,11 +491,10 @@ README.md newtvm
<p><br>
Check that the newt tool is installed and it is in your path:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ls go/bin
-$ ls bin/newt
-bin/newt
-$which go
-/home/<user>/dev/go/bin/newt
+<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>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/latest/newtmgr/install_windows/index.html
----------------------------------------------------------------------
diff --git a/latest/newtmgr/install_windows/index.html b/latest/newtmgr/install_windows/index.html
index b87d79e..49d1ce2 100644
--- a/latest/newtmgr/install_windows/index.html
+++ b/latest/newtmgr/install_windows/index.html
@@ -403,7 +403,7 @@ nothing to commit, working directory clean
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
+$which newtmgr
~/dev/go/bin/newtmgr
</pre></div>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/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 e2e7925..65bff72 100644
--- a/latest/os/get_started/project_create/index.html
+++ b/latest/os/get_started/project_create/index.html
@@ -641,7 +641,7 @@ All tests passed
<p><br></p>
<h3 id="building-and-running-the-simulated-blinky-application">Building and Running the Simulated Blinky Application</h3>
<p>The section shows you how to build and run the blinky application to run on Mynewt's simulated hardware.</p>
-<p><strong>Note</strong>: This is not yet supported on Windows. Refer to the <a href="../../tutorials/blinky/">Blinky Tutorials</a> to create a blinky application on a target boards.</p>
+<p><strong>Note</strong>: This is not yet supported on Windows. Refer to the <a href="../../tutorials/blinky/">Blinky Tutorials</a> to create a blinky application for a target board.</p>
<p><br></p>
<h4 id="building-the-application">Building the Application</h4>
<p>To build the simulated blinky application, run <code>newt build my_blinky_sim</code>:</p>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/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 639341e..1fe8b67 100644
--- a/latest/os/tutorials/arduino_zero/index.html
+++ b/latest/os/tutorials/arduino_zero/index.html
@@ -573,6 +573,7 @@ the repository to the <code>project.yml</code> file in your base project directo
<p>Here is an example <code>project.yml</code> file with the Arduino Zero repository
added. The sections with <code>mynewt_arduino_zero</code> that need to be added to
your project file are highlighted.</p>
+<p><strong>Note:</strong> On Windows platforms: You need to set <code>vers</code> to <code>0-dev</code> and use the latest master branch for both repositories.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ more project.yml
project.name: "my_project"
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/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 37c222f..920c63b 100644
--- a/latest/os/tutorials/blinky_primo/index.html
+++ b/latest/os/tutorials/blinky_primo/index.html
@@ -671,7 +671,7 @@ App image succesfully generated: ~/dev/myproj/bin/targets/primoblinky/app/apps/b
</ul>
<p><img alt="J-Link debug probe to Arduino" src="../pics/primo-jlink.jpg" title="Connecting J-Link debug probe to Arduino Primo" /></p>
<p><strong>Note:</strong> If you are using the OpenOCD debugger, you do not need to attach this connector. </p>
-<h3 id="load-the-bootloader-and-the-blinky-application-image">Load the Bootloader and the Blinky Application Image</h3>
+<h3 id="load-the-bootloader">Load the Bootloader</h3>
<p>Run the <code>newt load primo_boot</code> command to load the bootloader onto the board:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt load primo_boot
Loading bootloader
@@ -679,8 +679,15 @@ $
</pre></div>
-<p><br>
-Run the <code>newt load primoblinky</code> command to load the Blinky application image onto the board.</p>
+<p><strong>Note:</strong> If you are using OpenOCD on a Windows platform and you get an <code>unable to find CMSIS-DAP device</code> error, you will need to download and install the mbed Windows serial port driver from <a href="https://developer.mbed.org/handbook/Windows-serial-configuration">https://developer.mbed.org/handbook/Windows-serial-configuration</a>. Follow the instructions from the site to install the driver. Here are some additional notes about the installation:</p>
+<ol>
+<li>The instructions indicate that the mbed Windows serial port driver is not required for Windows 10. If you are using Windows 10 and get the <code>unable to find CMSIS-DAP device</code> error, we recommend that you install the driver.</li>
+<li>If the driver installation fails, we recommend that you unplug the board, plug it back in, and retry the installation.</li>
+</ol>
+<p>Run the <code>newt load primo_boot</code> command again.</p>
+<p><br></p>
+<h3 id="load-the-blinky-application-image">Load the Blinky Application Image</h3>
+<p>Run the <code>newt load primoblinky</code> command to load the Blinky application image onto the board.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt load primoblinky
Loading app image into slot 1
$
@@ -690,6 +697,7 @@ $
<p>You should see the orange LED (L13), below the ON LED, on the board blink!</p>
<p>Note: If the LED does not blink, try resetting the board.</p>
<p><br></p>
+<h3 id="erase-flash">Erase Flash</h3>
<p>If you want to erase the flash and load the image again, use JLinkExe and issue the <code>erase</code> command when you are using the Jlink debug probe: </p>
<p><strong>Note:</strong> On Windows: Run the <code>jlink</code> command with the same arguments from a Windows Command Prompt terminal.
<br></p>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/latest/os/tutorials/blinky_stm32f4disc/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/blinky_stm32f4disc/index.html b/latest/os/tutorials/blinky_stm32f4disc/index.html
index facab1f..e1f188f 100644
--- a/latest/os/tutorials/blinky_stm32f4disc/index.html
+++ b/latest/os/tutorials/blinky_stm32f4disc/index.html
@@ -668,6 +668,14 @@ Loading bootloader
</pre></div>
+<p>Note: If you are using Windows and get an <code>open failed</code> or <code>no device found</code> error, you will need to install the usb driver. Download <a href="http://zadig.akeo.ie">Zadig</a> and run it:</p>
+<ul>
+<li>Select Options > List All Devices.</li>
+<li>Select <code>STM32 STLink</code> from the drop down menu.</li>
+<li>Select the <code>WinUSB</code> driver.</li>
+<li>Click Install Driver.</li>
+<li>Run the <code>newt load stm32f4disc_boot</code> command again.</li>
+</ul>
<p><br>
Run the <code>newt load stm32f4disc_blinky</code> command to load the Blinky application image onto the board.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$newt load stm32f4disc_blinky
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/latest/os/tutorials/olimex/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/olimex/index.html b/latest/os/tutorials/olimex/index.html
index 618a14f..1ad77dd 100644
--- a/latest/os/tutorials/olimex/index.html
+++ b/latest/os/tutorials/olimex/index.html
@@ -682,11 +682,11 @@ Successfully loaded image.
</pre></div>
-<p>Note: If you are using Windows and get the <code>no device found</code> error, you will need to install the usb drivers for your Olimex debugger. Download <a href="http://zadig.akeo.ie">Zadig</a> and run it:</p>
+<p>Note: If you are using Windows and get a <code>no device found</code> error, you will need to install the usb driver. Download <a href="http://zadig.akeo.ie">Zadig</a> and run it:</p>
<ul>
<li>Select Options > List All Devices.</li>
-<li>Select Olimex OpenOCD JTAG ARM-USB-TINY-H from the drop down menu.</li>
-<li>Select the WinUSB drivers.</li>
+<li>Select <code>Olimex OpenOCD JTAG ARM-USB-TINY-H</code> from the drop down menu.</li>
+<li>Select the <code>WinUSB</code> driver.</li>
<li>Click Install Driver.</li>
<li>Run the <code>newt load boot_olimex</code> command again. </li>
</ul>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/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 06af2fc..8a17f4f 100644
--- a/latest/os/tutorials/project-stm32-slinky/index.html
+++ b/latest/os/tutorials/project-stm32-slinky/index.html
@@ -622,6 +622,15 @@ $
<p><br>
+Note: If you are using Windows and get a <code>no device found</code> error, you will need to install the usb driver. Download <a href="http://zadig.akeo.ie">Zadig</a> and run it:</p>
+<ul>
+<li>Select Options > List All Devices.</li>
+<li>Select <code>Olimex OpenOCD JTAG ARM-USB-TINY-H</code> from the drop down menu.</li>
+<li>Select the <code>WinUSB</code> driver.</li>
+<li>Click Install Driver.</li>
+<li>Run the <code>newt load stm32_boot</code> command again.</li>
+</ul>
+<p><br>
Run the <code>newt load stm32_slinky</code> command to load the Slinky application image onto the board:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt load stm32_slinky
Loading app image into slot 1
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/latest/os/tutorials/rbnano2/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/rbnano2/index.html b/latest/os/tutorials/rbnano2/index.html
index 24d6ed1..56d44aa 100644
--- a/latest/os/tutorials/rbnano2/index.html
+++ b/latest/os/tutorials/rbnano2/index.html
@@ -645,7 +645,7 @@ App image succesfully generated: ~/dev/myproj/bin/targets/rbnano2_blinky/app/app
<p><br></p>
<h3 id="connect-to-the-board">Connect to the Board</h3>
<p>Connect the RedBear Nano 2 USB to a USB port on your computer. You should see an orange LED light up on the board.</p>
-<h3 id="load-the-bootloader-and-the-blinky-application-image">Load the Bootloader and the Blinky Application Image</h3>
+<h3 id="load-the-bootloader">Load the Bootloader</h3>
<p>Run the <code>newt load rbnano2_boot</code> command to load the bootloader onto the board: </p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt load rbnano2_boot
Loading bootloader
@@ -653,8 +653,16 @@ $
</pre></div>
-<p><br>
-Note: The flash memory on the RedBear Nano 2 comes write protected from the factory. If you get an error loading the bootloader and you are using a brand new chip, you need to clear the write protection from the debugger and then load the bootloader again. Run the <code>newt debug rbnano2_blinky</code> command and issue the following commands at the highlighted (gdb) prompts. </p>
+<p><br></p>
+<p><strong>Note:</strong> On Windows platforms, if you get an <code>unable to find CMSIS-DAP device</code> error, you will need to download and install the mbed Windows serial port driver from <a href="https://developer.mbed.org/handbook/Windows-serial-configuration">https://developer.mbed.org/handbook/Windows-serial-configuration</a>. Follow the instructions from the site to install the driver. Here are some additional notes about the installation:</p>
+<ol>
+<li>The instructions indicate that the mbed Windows serial port driver is not required for Windows 10. If you are using Windows 10 and get the <code>unable to find CMSIS-DAP device</code> error, we recommend that you install the driver.</li>
+<li>If the driver installation fails, we recommend that you unplug the board, plug it back in, and retry the installation.</li>
+</ol>
+<p>Run the <code>newt load rbnano2_boot</code> command again.</p>
+<p><br></p>
+<h4 id="clear-the-write-protection-on-the-flash-memory">Clear the Write Protection on the Flash Memory</h4>
+<p>The flash memory on the RedBear Nano 2 comes write protected from the factory. If you get an error loading the bootloader and you are using a brand new chip, you need to clear the write protection from the debugger and then load the bootloader again. Run the <code>newt debug rbnano2_blinky</code> command and issue the following commands at the highlighted (gdb) prompts. </p>
<p><strong>Note:</strong> The output of the debug session below is for Mac OS and Linux platforms. On Windows, openocd and gdb are started in separate Windows Command Prompt terminals, and the terminals are automatically closed when you quit gdb. In addition, the output of openocd is logged to the openocd.log file in your project's base directory instead of the terminal.</p>
<p><br></p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$newt debug rbnano2_blinky
@@ -683,8 +691,10 @@ Error: Failed to read memory at 0x00009ef4
</pre></div>
+<p><br></p>
+<h3 id="load-the-blinky-application-image">Load the Blinky Application Image</h3>
<p><br>
-Run the <code>newt load rbnano2_blinky</code> command to load the Blinky application image onto the board.</p>
+Run the <code>newt load rbnano2_blinky</code> command to load the Blinky application image onto the board:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt load rbnano2_blinky
Loading app image into slot 1
</pre></div>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/latest/os/tutorials/wi-fi_on_arduino/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/wi-fi_on_arduino/index.html b/latest/os/tutorials/wi-fi_on_arduino/index.html
index c820b0a..78100a0 100644
--- a/latest/os/tutorials/wi-fi_on_arduino/index.html
+++ b/latest/os/tutorials/wi-fi_on_arduino/index.html
@@ -518,13 +518,10 @@ the repository to the <code>project.yml</code> file in your base project directo
low level operations. Sometimes this code is licensed only for the specific manufacturer of the chipset and cannot live in the Apache Mynewt repository. That happens to be the case for the Arduino Zero board which uses Atmel SAMD21. Runtime's github repository hosts such external third-party packages and the Newt tool can fetch them.</p>
<p>To fetch the package with MCU support for Atmel SAMD21 for Arduino Zero from the Runtime git repository, you need to add
the repository to the <code>project.yml</code> file in your base project directory (<code>arduinowifi</code>).</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">user@~/dev/arduinowifi$ vi project.yml
-</pre></div>
-
-
<p>Here is an example <code>project.yml</code> file with the Arduino Zero repository
added. The sections with <code>mynewt_arduino_zero</code> that need to be added to
your project file are highlighted.</p>
+<p><strong>Note:</strong> On Windows platforms: You need to set <code>vers</code> to <code>0-dev</code> and use the latest master branch for both repositories.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ more project.yml
project.name: "my_project"
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/latest/sitemap.xml
----------------------------------------------------------------------
diff --git a/latest/sitemap.xml b/latest/sitemap.xml
index edefac3..b535b74 100644
--- a/latest/sitemap.xml
+++ b/latest/sitemap.xml
@@ -4,7 +4,7 @@
<url>
<loc>http://mynewt.apache.org/</loc>
- <lastmod>2017-05-14</lastmod>
+ <lastmod>2017-05-22</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -13,7 +13,7 @@
<url>
<loc>http://mynewt.apache.org/pages/ble/</loc>
- <lastmod>2017-05-14</lastmod>
+ <lastmod>2017-05-22</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -22,7 +22,7 @@
<url>
<loc>http://mynewt.apache.org/quick-start/</loc>
- <lastmod>2017-05-14</lastmod>
+ <lastmod>2017-05-22</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -30,7 +30,7 @@
<url>
<loc>http://mynewt.apache.org/about/</loc>
- <lastmod>2017-05-14</lastmod>
+ <lastmod>2017-05-22</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -38,7 +38,7 @@
<url>
<loc>http://mynewt.apache.org/talks/</loc>
- <lastmod>2017-05-14</lastmod>
+ <lastmod>2017-05-22</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -46,7 +46,7 @@
<url>
<loc>http://mynewt.apache.org/download/</loc>
- <lastmod>2017-05-14</lastmod>
+ <lastmod>2017-05-22</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -54,7 +54,7 @@
<url>
<loc>http://mynewt.apache.org/community/</loc>
- <lastmod>2017-05-14</lastmod>
+ <lastmod>2017-05-22</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -62,7 +62,7 @@
<url>
<loc>http://mynewt.apache.org/events/</loc>
- <lastmod>2017-05-14</lastmod>
+ <lastmod>2017-05-22</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -71,7 +71,7 @@
<url>
<loc>http://mynewt.apache.org/os/introduction/</loc>
- <lastmod>2017-05-14</lastmod>
+ <lastmod>2017-05-22</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -83,7 +83,7 @@
<url>
<loc>http://mynewt.apache.org/os/get_started/vocabulary/</loc>
- <lastmod>2017-05-14</lastmod>
+ <lastmod>2017-05-22</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -123,19 +123,25 @@
<url>
<loc>http://mynewt.apache.org/faq/go_env/</loc>
- <lastmod>2017-05-14</lastmod>
+ <lastmod>2017-05-22</lastmod>
+ <changefreq>daily</changefreq>
+ </url>
+
+ <url>
+ <loc>http://mynewt.apache.org/faq/ide/</loc>
+ <lastmod>2017-05-22</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/how_to_edit_docs/</loc>
- <lastmod>2017-05-14</lastmod>
+ <lastmod>2017-05-22</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/answers/</loc>
- <lastmod>2017-05-14</lastmod>
+ <lastmod>2017-05-22</lastmod>
<changefreq>daily</changefreq>
</url>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/sitemap.xml
----------------------------------------------------------------------
diff --git a/sitemap.xml b/sitemap.xml
index 53793e0..8b4d2ba 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -4,7 +4,7 @@
<url>
<loc>http://mynewt.apache.org/</loc>
- <lastmod>2017-05-14</lastmod>
+ <lastmod>2017-05-22</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -13,13 +13,13 @@
<url>
<loc>http://mynewt.apache.org/pages/ble/</loc>
- <lastmod>2017-05-14</lastmod>
+ <lastmod>2017-05-22</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/pages/securitybullets/</loc>
- <lastmod>2017-05-14</lastmod>
+ <lastmod>2017-05-22</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -28,7 +28,7 @@
<url>
<loc>http://mynewt.apache.org/quick-start/</loc>
- <lastmod>2017-05-14</lastmod>
+ <lastmod>2017-05-22</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -36,7 +36,7 @@
<url>
<loc>http://mynewt.apache.org/about/</loc>
- <lastmod>2017-05-14</lastmod>
+ <lastmod>2017-05-22</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -44,7 +44,7 @@
<url>
<loc>http://mynewt.apache.org/talks/</loc>
- <lastmod>2017-05-14</lastmod>
+ <lastmod>2017-05-22</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -52,7 +52,7 @@
<url>
<loc>http://mynewt.apache.org/download/</loc>
- <lastmod>2017-05-14</lastmod>
+ <lastmod>2017-05-22</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -60,7 +60,7 @@
<url>
<loc>http://mynewt.apache.org/community/</loc>
- <lastmod>2017-05-14</lastmod>
+ <lastmod>2017-05-22</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -68,7 +68,7 @@
<url>
<loc>http://mynewt.apache.org/events/</loc>
- <lastmod>2017-05-14</lastmod>
+ <lastmod>2017-05-22</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -77,7 +77,7 @@
<url>
<loc>http://mynewt.apache.org/os/introduction/</loc>
- <lastmod>2017-05-14</lastmod>
+ <lastmod>2017-05-22</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -89,7 +89,7 @@
<url>
<loc>http://mynewt.apache.org/os/get_started/vocabulary/</loc>
- <lastmod>2017-05-14</lastmod>
+ <lastmod>2017-05-22</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -129,13 +129,13 @@
<url>
<loc>http://mynewt.apache.org/faq/how_to_edit_docs/</loc>
- <lastmod>2017-05-14</lastmod>
+ <lastmod>2017-05-22</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/answers/</loc>
- <lastmod>2017-05-14</lastmod>
+ <lastmod>2017-05-22</lastmod>
<changefreq>daily</changefreq>
</url>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/v0_9_0/faq/pics/debug_new_config_small.png
----------------------------------------------------------------------
diff --git a/v0_9_0/faq/pics/debug_new_config_small.png b/v0_9_0/faq/pics/debug_new_config_small.png
new file mode 100755
index 0000000..5d2e287
Binary files /dev/null and b/v0_9_0/faq/pics/debug_new_config_small.png differ
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/v0_9_0/faq/pics/gdb_debug_small.png
----------------------------------------------------------------------
diff --git a/v0_9_0/faq/pics/gdb_debug_small.png b/v0_9_0/faq/pics/gdb_debug_small.png
new file mode 100755
index 0000000..5ebfb11
Binary files /dev/null and b/v0_9_0/faq/pics/gdb_debug_small.png differ
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/v0_9_0/faq/pics/gdb_server_small.png
----------------------------------------------------------------------
diff --git a/v0_9_0/faq/pics/gdb_server_small.png b/v0_9_0/faq/pics/gdb_server_small.png
new file mode 100755
index 0000000..e6a42d7
Binary files /dev/null and b/v0_9_0/faq/pics/gdb_server_small.png differ
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/v0_9_0/faq/pics/gdb_small.png
----------------------------------------------------------------------
diff --git a/v0_9_0/faq/pics/gdb_small.png b/v0_9_0/faq/pics/gdb_small.png
new file mode 100755
index 0000000..f6c35d2
Binary files /dev/null and b/v0_9_0/faq/pics/gdb_small.png differ
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/v0_9_0/faq/pics/integrated_terminal_small.png
----------------------------------------------------------------------
diff --git a/v0_9_0/faq/pics/integrated_terminal_small.png b/v0_9_0/faq/pics/integrated_terminal_small.png
new file mode 100755
index 0000000..11414c8
Binary files /dev/null and b/v0_9_0/faq/pics/integrated_terminal_small.png differ
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/v0_9_0/faq/pics/launch_small.png
----------------------------------------------------------------------
diff --git a/v0_9_0/faq/pics/launch_small.png b/v0_9_0/faq/pics/launch_small.png
new file mode 100755
index 0000000..5c13dcf
Binary files /dev/null and b/v0_9_0/faq/pics/launch_small.png differ
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/v0_9_0/faq/pics/task_json_small.png
----------------------------------------------------------------------
diff --git a/v0_9_0/faq/pics/task_json_small.png b/v0_9_0/faq/pics/task_json_small.png
new file mode 100755
index 0000000..5047f61
Binary files /dev/null and b/v0_9_0/faq/pics/task_json_small.png differ
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/v0_9_0/faq/pics/task_runner_small.png
----------------------------------------------------------------------
diff --git a/v0_9_0/faq/pics/task_runner_small.png b/v0_9_0/faq/pics/task_runner_small.png
new file mode 100755
index 0000000..25a70fa
Binary files /dev/null and b/v0_9_0/faq/pics/task_runner_small.png differ
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/v0_9_0/faq/pics/task_select_small.png
----------------------------------------------------------------------
diff --git a/v0_9_0/faq/pics/task_select_small.png b/v0_9_0/faq/pics/task_select_small.png
new file mode 100755
index 0000000..35bc304
Binary files /dev/null and b/v0_9_0/faq/pics/task_select_small.png differ
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/v0_9_0/faq/pics/task_start_small.png
----------------------------------------------------------------------
diff --git a/v0_9_0/faq/pics/task_start_small.png b/v0_9_0/faq/pics/task_start_small.png
new file mode 100755
index 0000000..f84cd26
Binary files /dev/null and b/v0_9_0/faq/pics/task_start_small.png differ
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/v0_9_0/sitemap.xml
----------------------------------------------------------------------
diff --git a/v0_9_0/sitemap.xml b/v0_9_0/sitemap.xml
index 53793e0..8b4d2ba 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-05-14</lastmod>
+ <lastmod>2017-05-22</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -13,13 +13,13 @@
<url>
<loc>http://mynewt.apache.org/pages/ble/</loc>
- <lastmod>2017-05-14</lastmod>
+ <lastmod>2017-05-22</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/pages/securitybullets/</loc>
- <lastmod>2017-05-14</lastmod>
+ <lastmod>2017-05-22</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -28,7 +28,7 @@
<url>
<loc>http://mynewt.apache.org/quick-start/</loc>
- <lastmod>2017-05-14</lastmod>
+ <lastmod>2017-05-22</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -36,7 +36,7 @@
<url>
<loc>http://mynewt.apache.org/about/</loc>
- <lastmod>2017-05-14</lastmod>
+ <lastmod>2017-05-22</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -44,7 +44,7 @@
<url>
<loc>http://mynewt.apache.org/talks/</loc>
- <lastmod>2017-05-14</lastmod>
+ <lastmod>2017-05-22</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -52,7 +52,7 @@
<url>
<loc>http://mynewt.apache.org/download/</loc>
- <lastmod>2017-05-14</lastmod>
+ <lastmod>2017-05-22</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -60,7 +60,7 @@
<url>
<loc>http://mynewt.apache.org/community/</loc>
- <lastmod>2017-05-14</lastmod>
+ <lastmod>2017-05-22</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -68,7 +68,7 @@
<url>
<loc>http://mynewt.apache.org/events/</loc>
- <lastmod>2017-05-14</lastmod>
+ <lastmod>2017-05-22</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -77,7 +77,7 @@
<url>
<loc>http://mynewt.apache.org/os/introduction/</loc>
- <lastmod>2017-05-14</lastmod>
+ <lastmod>2017-05-22</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -89,7 +89,7 @@
<url>
<loc>http://mynewt.apache.org/os/get_started/vocabulary/</loc>
- <lastmod>2017-05-14</lastmod>
+ <lastmod>2017-05-22</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -129,13 +129,13 @@
<url>
<loc>http://mynewt.apache.org/faq/how_to_edit_docs/</loc>
- <lastmod>2017-05-14</lastmod>
+ <lastmod>2017-05-22</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/answers/</loc>
- <lastmod>2017-05-14</lastmod>
+ <lastmod>2017-05-22</lastmod>
<changefreq>daily</changefreq>
</url>
[4/5] incubator-mynewt-site git commit: This closes #183. This closes
#184. Adding instructions to use Visual Studio for Mynewt developers
Posted by ad...@apache.org.
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/develop/mkdocs/search_index.json
----------------------------------------------------------------------
diff --git a/develop/mkdocs/search_index.json b/develop/mkdocs/search_index.json
index 32cc45b..1282385 100644
--- a/develop/mkdocs/search_index.json
+++ b/develop/mkdocs/search_index.json
@@ -222,7 +222,7 @@
},
{
"location": "/newt/install/newt_windows/",
- "text": "Installing Newt on Windows\n\n\nYou can develop and build Mynewt OS applications for your target boards on the Windows platform. This page shows you how to build the newt tool from the lastest source on the master branch of the \nMynewt newt git repository\n. The tool is written in Go (golang).\n\n\nIn Windows, we use MinGW as the development environment to build and run Mynewt OS applications for target boards. MinGW runs the bash shell and provides a Unix-like environment. This provides a uniform way to build Mynewt OS applications. The Mynewt documentation and tutorials use Unix commands and you can use the same Unix commands on MinGW to follow the tutorials. The documentation will note any commands or behaviors that are specific to Windows.\n\n\nThis guide shows you how to perform the following:\n\n\n\n\nInstall MSYS2/MinGW. \n\n\nInstall Git.\n\n\nInstall Go. \n\n\nSetup the Go environment.\n\n\nDownload the source, build, and install the newt tool.\n\n\n
\n\n\n\nStep 1: Installing MSYS2/MinGW\n\n\nMSYS2/MinGW provides a bash shell and tools to build applications that run on Windows. It includes three subsystems:\n\n\n\n\nMSYS2 toolchain to build POSIX applications that run on Windows. \n\n\nMinGW32 toolchains to build 32 bit native Windows applications. \n\n\nMinGW64 toolchains to build 64 bit native Windows applications. \n\n\n\n\nThe subsystems run the bash shell and provide a Unix-like environment. You can also run Windows applications from the shell. We will use the MinGW subsystem.\n\n\nTo install and setup MSYS2 and MinGW:\n\n\n\n\nDownload and run the \nMSYS2 installer\n. Select the 64 bit version if you are running on a 64 bit platform. Follow the prompts and check the \nRun MSYS2 now\n checkbox on the \nInstallation Complete\n dialog. \n\n\n\n\nIn the MSYS2 terminal, run the \npacman -Syuu\n command. If you get a message to run the update again, close the terminal and run the \npacman -Syuu\n command in a new terminal. \
n\n\nTo start a new MSYS2 terminal, select the \"MSYS2 MSYS\" application from the Windows start menu.\n\n\n\n\n\n\nAdd a new user variable named \nMSYS2_PATH_TYPE\n and set the value to \ninherit\n in your Windows environment. This enables the MSYS2 and MinGW bash to inherit your Windows user \nPath\n values. \n\n\nTo add the variable, select properties for your computer \n Advanced system settings \n Environment Variables \n New\n\n\n\n\n\n\nRun the \npacman -Su vim\n command to install the vim editor. \n\n\nNote:\nYou can also use a Windows editor. You can access your files from the \nC:\\\nmsys-install-folder\n\\home\\\nusername\n folder, where \nmsys-install-folder\n is the folder you installed MSYS2 in. For example, if you installed MSYS2 in the \nmsys64\n folder, your files are stored in \nC:\\msys64\\home\\\nusername\n\n\n\n\n\n\nYou will need to start a MinGW terminal to run the commands specified in the Mynewt documentation and tutorials. To start a MinGW terminal, sele
ct the \"MSYS2 Mingw\" application from the start Menu (you can use either MinGW32 or MinGW64). \nIn Windows, we use the MingGW subsystem to build Mynewt tools and applications. \n\n\nStep 2: Installing Git for Windows\n\n\nDownload and install \nGit for Windows\n if it is not already installed.\n\n\nStep 3: Installing Go\n\n\nDownload and install the latest version of \nGo\n. Newt requires Go version 1.7 or higher.\n\n\nStep 4: Setting Up Your Go Environment\n\n\nThis section describes the Go environment and how to setup a Go workspace. Go provides an environment to compile Go code, construct Go packages, and import Go code. You will use Go commands to import the newt 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 \nsrc\n, \npkg\n and \nbin\n: \n\n\n\n\nsrc contains Go source files organized into packages (one package
per directory)\n\n\npkg contains package objects\n\n\nbin contains the Go application executables that Go builds and installs.\n\n\n\n\nThe \nGOPATH\n environment variable specifies the location of your workspace. To setup this workspace environment, create a \ndev\n directory and then a \ngo\n directory under it. Set the GOPATH environment variable to this directory where you will clone the newt repository.\n\n\nStart up a MinGW terminal and run the following commands to set up your Go workspace:\n\n\n$ cd $HOME\n$ mkdir -p dev/go \n$ cd dev/go\n$ export GOPATH=`pwd`\n\n\n\n\n\n\nAdd the following export statements to your ~/.bash_profile file and source the file:\n\n\nexport GOPATH=$HOME/dev/go\nexport PATH=$GOPATH/bin:$PATH\n\n\n\n\n\n\n\nStep 5: Downloading the Source and Installing the Newt Tool\n\n\nThe newt Go package is \nmynewt.apache.org/newt/newt\n and is stored in the \nApache Mynewt newt tool repository mirrored on github\n. We use the \ngo get\n command to download
the source, build, and install the newt tool binary in the \n$GOPATH/bin\n directory. \n\n\n\nDownload the newt package source and install the tool:\n\n\n$cd $GOPATH\n$go get mynewt.apache.org/newt/newt\n$cd $GOPATH/src/mynewt.apache.org/newt\n$ls \nDISCLAIMER RELEASE_NOTES.md util\nINSTALLING.md build.sh viper\nLICENSE newt yaml\nNOTICE newtmgr\nREADME.md newtvm\n\n\n\n\n\n\nCheck that the newt tool is installed and it is in your path:\n\n\n$ls go/bin\n$ ls bin/newt\nbin/newt\n$which go\n/home/\nuser\n/dev/go/bin/newt\n$ newt version\nApache Newt (incubating) version: 1.0.0-dev\n\n\n\n\n\n\nGet information about the newt tool:\n\n\n$newt\nNewt allows you to create your own embedded application based on the Mynewt\noperating system. 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 project
s. 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 tar
get 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 4)\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\nUse \nnewt [command] --help\n for more information about a command.",
+ "text": "Installing Newt on Windows\n\n\nYou can develop and build Mynewt OS applications for your target boards on the Windows platform. This page shows you how to build the newt tool from the lastest source on the master branch of the \nMynewt newt git repository\n. The tool is written in Go (golang).\n\n\nIn Windows, we use MinGW as the development environment to build and run Mynewt OS applications for target boards. MinGW runs the bash shell and provides a Unix-like environment. This provides a uniform way to build Mynewt OS applications. The Mynewt documentation and tutorials use Unix commands and you can use the same Unix commands on MinGW to follow the tutorials. The documentation will note any commands or behaviors that are specific to Windows.\n\n\nThis guide shows you how to perform the following:\n\n\n\n\nInstall MSYS2/MinGW. \n\n\nInstall Git.\n\n\nInstall Go. \n\n\nSetup the Go environment.\n\n\nDownload the source, build, and install the newt tool.\n\n\n
\n\n\n\nStep 1: Installing MSYS2/MinGW\n\n\nMSYS2/MinGW provides a bash shell and tools to build applications that run on Windows. It includes three subsystems:\n\n\n\n\nMSYS2 toolchain to build POSIX applications that run on Windows. \n\n\nMinGW32 toolchains to build 32 bit native Windows applications. \n\n\nMinGW64 toolchains to build 64 bit native Windows applications. \n\n\n\n\nThe subsystems run the bash shell and provide a Unix-like environment. You can also run Windows applications from the shell. We will use the MinGW subsystem.\n\n\nTo install and setup MSYS2 and MinGW:\n\n\n\n\nDownload and run the \nMSYS2 installer\n. Select the 64 bit version if you are running on a 64 bit platform. Follow the prompts and check the \nRun MSYS2 now\n checkbox on the \nInstallation Complete\n dialog. \n\n\n\n\nIn the MSYS2 terminal, run the \npacman -Syuu\n command. If you get a message to run the update again, close the terminal and run the \npacman -Syuu\n command in a new terminal. \
n\n\nTo start a new MSYS2 terminal, select the \"MSYS2 MSYS\" application from the Windows start menu.\n\n\n\n\n\n\nAdd a new user variable named \nMSYS2_PATH_TYPE\n and set the value to \ninherit\n in your Windows environment. This enables the MSYS2 and MinGW bash to inherit your Windows user \nPath\n values. \n\n\nTo add the variable, select properties for your computer \n Advanced system settings \n Environment Variables \n New\n\n\n\n\n\n\nRun the \npacman -Su vim\n command to install the vim editor. \n\n\nNote:\nYou can also use a Windows editor. You can access your files from the \nC:\\\nmsys-install-folder\n\\home\\\nusername\n folder, where \nmsys-install-folder\n is the folder you installed MSYS2 in. For example, if you installed MSYS2 in the \nmsys64\n folder, your files are stored in \nC:\\msys64\\home\\\nusername\n\n\n\n\n\n\nYou will need to start a MinGW terminal to run the commands specified in the Mynewt documentation and tutorials. To start a MinGW terminal, sele
ct the \"MSYS2 Mingw\" application from the start Menu (you can use either MinGW32 or MinGW64). \nIn Windows, we use the MingGW subsystem to build Mynewt tools and applications. \n\n\nStep 2: Installing Git for Windows\n\n\nDownload and install \nGit for Windows\n if it is not already installed.\n\n\nStep 3: Installing Go\n\n\nDownload and install the latest version of \nGo\n. Newt requires Go version 1.7 or higher.\n\n\nStep 4: Setting Up Your Go Environment\n\n\nThis section describes the Go environment and how to setup a Go workspace. Go provides an environment to compile Go code, construct Go packages, and import Go code. You will use Go commands to import the newt 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 \nsrc\n, \npkg\n and \nbin\n: \n\n\n\n\nsrc contains Go source files organized into packages (one package
per directory)\n\n\npkg contains package objects\n\n\nbin contains the Go application executables that Go builds and installs.\n\n\n\n\nThe \nGOPATH\n environment variable specifies the location of your workspace. To setup this workspace environment, create a \ndev\n directory and then a \ngo\n directory under it. Set the GOPATH environment variable to this directory where you will clone the newt repository.\n\n\nStart up a MinGW terminal and run the following commands to set up your Go workspace:\n\n\n$ cd $HOME\n$ mkdir -p dev/go \n$ cd dev/go\n$ export GOPATH=`pwd`\n\n\n\n\n\n\nAdd the following export statements to your ~/.bash_profile file and source the file:\n\n\nexport GOPATH=$HOME/dev/go\nexport PATH=$GOPATH/bin:$PATH\n\n\n\n\n\n\n\nStep 5: Downloading the Source and Installing the Newt Tool\n\n\nThe newt Go package is \nmynewt.apache.org/newt/newt\n and is stored in the \nApache Mynewt newt tool repository mirrored on github\n. We use the \ngo get\n command to download
the source, build, and install the newt tool binary in the \n$GOPATH/bin\n directory. \n\n\n\nDownload the newt package source and install the tool:\n\n\n$cd $GOPATH\n$go get mynewt.apache.org/newt/newt\n$cd $GOPATH/src/mynewt.apache.org/newt\n$ls \nDISCLAIMER RELEASE_NOTES.md util\nINSTALLING.md build.sh viper\nLICENSE newt yaml\nNOTICE newtmgr\nREADME.md newtvm\n\n\n\n\n\n\nCheck that the newt tool is installed and it is in your path:\n\n\n$ls $GOPATH/bin/newt\n~/dev/go/bin/newt\n$which newt\n~/dev/go/bin/newt\n$ newt version\nApache Newt (incubating) version: 1.0.0-dev\n\n\n\n\n\n\nGet information about the newt tool:\n\n\n$newt\nNewt allows you to create your own embedded application based on the Mynewt\noperating system. 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 com
ponents\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 4)\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\nUse \nnewt [command] --help\n for more information about a command.",
"title": "Install Newt on Windows"
},
{
@@ -252,7 +252,7 @@
},
{
"location": "/newt/install/newt_windows/#step-5-downloading-the-source-and-installing-the-newt-tool",
- "text": "The newt Go package is mynewt.apache.org/newt/newt and is stored in the Apache Mynewt newt tool repository mirrored on github . We use the go get command to download the source, build, and install the newt tool binary in the $GOPATH/bin directory. \nDownload the newt package source and install the tool: $cd $GOPATH\n$go get mynewt.apache.org/newt/newt\n$cd $GOPATH/src/mynewt.apache.org/newt\n$ls \nDISCLAIMER RELEASE_NOTES.md util\nINSTALLING.md build.sh viper\nLICENSE newt yaml\nNOTICE newtmgr\nREADME.md newtvm \nCheck that the newt tool is installed and it is in your path: $ls go/bin\n$ ls bin/newt\nbin/newt\n$which go\n/home/ user /dev/go/bin/newt\n$ newt version\nApache Newt (incubating) version: 1.0.0-dev \nGet information about the newt tool: $newt\nNewt allows you to create your own embedded application based on the Mynewt\noperating system. Newt provides both build and package managemen
t 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 [ command-name ]\n For help on command-name . 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 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\nFlags:\n -h, --help Help for newt commands\n -j, --jobs int Number of concurrent build jobs (default 4)\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\nUse newt [command] --help for more information ab
out a command.",
+ "text": "The newt Go package is mynewt.apache.org/newt/newt and is stored in the Apache Mynewt newt tool repository mirrored on github . We use the go get command to download the source, build, and install the newt tool binary in the $GOPATH/bin directory. \nDownload the newt package source and install the tool: $cd $GOPATH\n$go get mynewt.apache.org/newt/newt\n$cd $GOPATH/src/mynewt.apache.org/newt\n$ls \nDISCLAIMER RELEASE_NOTES.md util\nINSTALLING.md build.sh viper\nLICENSE newt yaml\nNOTICE newtmgr\nREADME.md newtvm \nCheck that the newt tool is installed and it is in your path: $ls $GOPATH/bin/newt\n~/dev/go/bin/newt\n$which newt\n~/dev/go/bin/newt\n$ newt version\nApache Newt (incubating) version: 1.0.0-dev \nGet information about the newt tool: $newt\nNewt allows you to create your own embedded application based on the Mynewt\noperating system. 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 [ command-name ]\n For help on command-name . 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 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\nFlags:\n -h, --help Help for newt commands\n -j, --jobs int Number of concurrent build jobs (default 4)\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\nUse newt [command] --help for more information about a
command.",
"title": "Step 5: Downloading the Source and Installing the Newt Tool"
},
{
@@ -407,7 +407,7 @@
},
{
"location": "/os/get_started/project_create/",
- "text": "Creating Your First Mynewt Project\n\n\nThis page shows you how to create a Mynewt project using the \nnewt\n command-line tool. The project is a blinky application that toggles a pin. The application uses the Mynewt's simulated hardware and runs as a native application on Mac OS and Linux. \n\n\nNote:\n The Mynewt simulator is not yet supported on Windows. If you are using the native install option (not the Docker option), you will need to create the blinky application for a target board. We recommend that you read the section on creating a new project and fetching the source repository to understand the Mynewt repository structure, create a new project, and fetch the source dependencies before proceeding to one of the \nBlinky Tutorials\n. \n\n\nThis guide shows you how to:\n\n\n\n\nCreate a new project and fetch the source repository and dependecies.\n\n\nTest the project packages (Not supported on Windows).\n\n\nBuild and run the simulated blinky applicatio
n (Not supported on Windows). \n\n\n\n\n\n\nPrerequisites\n\n\n\n\nHave Internet connectivity to fetch remote Mynewt components.\n\n\nInstall the newt tool: \n\n\nIf you have taken the native install option, see the installation instructions for \nMac OS\n, \nLinux\n, or \nWindows\n. \n\n\nIf you have taken the Docker option, you have already installed Newt.\n\n\n\n\n\n\nInstall the \nnative toolchain\n to compile and build a Mynewt native application. \n\n\n\n\n\n\nCreating a New Project and Fetching the Source Repository\n\n\nThis section describes how to use the newt tool to create a new project and fetch the core mynewt source repository.\n\n\n\n\nCreating a New Project\n\n\nChoose a name for your project. We name the project \nmyproj\n. \n\n\n\nRun the \nnewt new myproj\n command, from your \ndev\n directory, to create a new project:\n\n\nNote:\n This tutorial assumes you created a \ndev\n directory under your home directory. \n\n\n$cd ~/dev\n$ newt new myproj\nDownloading pr
oject skeleton from apache/incubator-mynewt-blinky...\nInstalling skeleton in myproj...\nProject myproj successfully created.\n\n\n\n\n\n\n\nThe newt tool creates a project base directory name \nmyproj\n. All newt tool commands are run from the project base directory. The newt tool populates this new project with a base skeleton of a new Apache Mynewt project in the project base directory. It has the following structure: \n\n\nNote\n: If you do not have \ntree\n, run \nbrew install tree\n to install on Mac OS, \nsudo apt-get install tree\n to install on Linux, and \npacman -Su tree\n from a MinGW terminal to install on Windows.\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\u
2500 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 installs the following files for a project in the project base directory:\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 only \ncomprises the core mynewt repository. Later, you will add more repositories to include other mynewt components.\n\n\nThe file \napps/blinky/pkg.yml\n contains the description of your application and its package dependencies.\n\n\nA \ntarget\n directory that contains the \nmy_blinky_sim\n directory. The \nmy_blinky_sim\n directory \na target information
to build 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 (except the template for \nmain.c\n). See the next step to install the packages.\n\n\n\n\nFetching the Mynewt Source Repository and Dependencies\n\n\nBy default, Mynewt projects rely on a single repository: \napache-mynewt-core\n and uses the source in the master branch. If you need to use a different branch, you need to change the \nvers\n value in the project.yml file: \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 vers to 0-dev will put you on the latest master branch. \nThis branch may not be stable and you may encounter bugs or other problems.\n\n\nNote:\n On Windows platforms, you will need to change
vers to 0-dev and use the latest master branch. Release 1.0.0 is not supported on Windows.\n\n\n\nRun the \nnewt install\n command, from your project base directory (myproj), to fetch the source repository and dependencies: \n\n\n$ newt install\napache-mynewt-core\n\n\n\n\n\nNote:\n It may take a while to download the apache-mynewt-core reposistory. Use the \n-v\n (verbose) option to see the installation progress.\n\n\n\n\nView the core of the Apache Mynewt OS that is downloaded into your local directory. \n\n\n(The actual output will depend on what is in the latest 'master' branch)\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 \u
251c\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\u2502\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\u2502\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\u2500\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 \u
251c\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\u2500\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\n\n
\nTesting the Project Packages\n\n\nNote\n: This is not yet supported on Windows.\n\n\nYou can use the newt tool to execute the unit tests in a package. For example, run the following command to test the \nsys/config\n package in the \napache-mynewt-core\n repo: \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_mk
dir.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/apache-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 installed the latest gcc using homebrew on your Mac, you are probably running gcc-6. Make sure you change the compiler.yml configuration to specify that you are using gcc-6 (See \nNative Install Option\n). You can also downgrade your inst
allation to gcc-5 and use the default gcc compiler configuration for MyNewt:\n\n\n$ brew uninstall gcc-6\n$ brew link gcc-5\n\n\n\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 multilib gcc (e.g. gcc-multilib if you running on a 64-bit Ubuntu).\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/my
proj/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\nBuilding and Running the Simulated Blinky Application\n\n\nThe section shows you how to build and run the blinky application to run on Mynewt's simulated hardware.\n\n\nNote\n: This is not yet supported on Windows. Refer to the \nBlinky Tutorials\n to create a blinky application on a target boards.\n\n\n\n\nBuilding the Application\n\n\nTo build the simulated blinky application, run \nnewt build my_blinky_sim\n:\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\nCo
mpiling 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\nRunning the Blinky Application\n\n\nYou can run the simulated version of your project and see the simulated LED blink. \n\n\nIf you natively install the toolchain execute the binary directly:\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\nIf you are using newt 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_bli
nky_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\n\n\nExploring other Mynewt OS Features\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": "Creating Your First Mynewt Project\n\n\nThis page shows you how to create a Mynewt project using the \nnewt\n command-line tool. The project is a blinky application that toggles a pin. The application uses the Mynewt's simulated hardware and runs as a native application on Mac OS and Linux. \n\n\nNote:\n The Mynewt simulator is not yet supported on Windows. If you are using the native install option (not the Docker option), you will need to create the blinky application for a target board. We recommend that you read the section on creating a new project and fetching the source repository to understand the Mynewt repository structure, create a new project, and fetch the source dependencies before proceeding to one of the \nBlinky Tutorials\n. \n\n\nThis guide shows you how to:\n\n\n\n\nCreate a new project and fetch the source repository and dependecies.\n\n\nTest the project packages (Not supported on Windows).\n\n\nBuild and run the simulated blinky applicatio
n (Not supported on Windows). \n\n\n\n\n\n\nPrerequisites\n\n\n\n\nHave Internet connectivity to fetch remote Mynewt components.\n\n\nInstall the newt tool: \n\n\nIf you have taken the native install option, see the installation instructions for \nMac OS\n, \nLinux\n, or \nWindows\n. \n\n\nIf you have taken the Docker option, you have already installed Newt.\n\n\n\n\n\n\nInstall the \nnative toolchain\n to compile and build a Mynewt native application. \n\n\n\n\n\n\nCreating a New Project and Fetching the Source Repository\n\n\nThis section describes how to use the newt tool to create a new project and fetch the core mynewt source repository.\n\n\n\n\nCreating a New Project\n\n\nChoose a name for your project. We name the project \nmyproj\n. \n\n\n\nRun the \nnewt new myproj\n command, from your \ndev\n directory, to create a new project:\n\n\nNote:\n This tutorial assumes you created a \ndev\n directory under your home directory. \n\n\n$cd ~/dev\n$ newt new myproj\nDownloading pr
oject skeleton from apache/incubator-mynewt-blinky...\nInstalling skeleton in myproj...\nProject myproj successfully created.\n\n\n\n\n\n\n\nThe newt tool creates a project base directory name \nmyproj\n. All newt tool commands are run from the project base directory. The newt tool populates this new project with a base skeleton of a new Apache Mynewt project in the project base directory. It has the following structure: \n\n\nNote\n: If you do not have \ntree\n, run \nbrew install tree\n to install on Mac OS, \nsudo apt-get install tree\n to install on Linux, and \npacman -Su tree\n from a MinGW terminal to install on Windows.\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\u
2500 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 installs the following files for a project in the project base directory:\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 only \ncomprises the core mynewt repository. Later, you will add more repositories to include other mynewt components.\n\n\nThe file \napps/blinky/pkg.yml\n contains the description of your application and its package dependencies.\n\n\nA \ntarget\n directory that contains the \nmy_blinky_sim\n directory. The \nmy_blinky_sim\n directory \na target information
to build 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 (except the template for \nmain.c\n). See the next step to install the packages.\n\n\n\n\nFetching the Mynewt Source Repository and Dependencies\n\n\nBy default, Mynewt projects rely on a single repository: \napache-mynewt-core\n and uses the source in the master branch. If you need to use a different branch, you need to change the \nvers\n value in the project.yml file: \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 vers to 0-dev will put you on the latest master branch. \nThis branch may not be stable and you may encounter bugs or other problems.\n\n\nNote:\n On Windows platforms, you will need to change
vers to 0-dev and use the latest master branch. Release 1.0.0 is not supported on Windows.\n\n\n\nRun the \nnewt install\n command, from your project base directory (myproj), to fetch the source repository and dependencies: \n\n\n$ newt install\napache-mynewt-core\n\n\n\n\n\nNote:\n It may take a while to download the apache-mynewt-core reposistory. Use the \n-v\n (verbose) option to see the installation progress.\n\n\n\n\nView the core of the Apache Mynewt OS that is downloaded into your local directory. \n\n\n(The actual output will depend on what is in the latest 'master' branch)\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 \u
251c\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\u2502\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\u2502\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\u2500\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 \u
251c\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\u2500\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\n\n
\nTesting the Project Packages\n\n\nNote\n: This is not yet supported on Windows.\n\n\nYou can use the newt tool to execute the unit tests in a package. For example, run the following command to test the \nsys/config\n package in the \napache-mynewt-core\n repo: \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_mk
dir.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/apache-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 installed the latest gcc using homebrew on your Mac, you are probably running gcc-6. Make sure you change the compiler.yml configuration to specify that you are using gcc-6 (See \nNative Install Option\n). You can also downgrade your inst
allation to gcc-5 and use the default gcc compiler configuration for MyNewt:\n\n\n$ brew uninstall gcc-6\n$ brew link gcc-5\n\n\n\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 multilib gcc (e.g. gcc-multilib if you running on a 64-bit Ubuntu).\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/my
proj/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\nBuilding and Running the Simulated Blinky Application\n\n\nThe section shows you how to build and run the blinky application to run on Mynewt's simulated hardware.\n\n\nNote\n: This is not yet supported on Windows. Refer to the \nBlinky Tutorials\n to create a blinky application for a target board.\n\n\n\n\nBuilding the Application\n\n\nTo build the simulated blinky application, run \nnewt build my_blinky_sim\n:\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\nCo
mpiling 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\nRunning the Blinky Application\n\n\nYou can run the simulated version of your project and see the simulated LED blink. \n\n\nIf you natively install the toolchain execute the binary directly:\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\nIf you are using newt 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_bli
nky_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\n\n\nExploring other Mynewt OS Features\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!",
"title": "Create Your First Project"
},
{
@@ -442,7 +442,7 @@
},
{
"location": "/os/get_started/project_create/#building-and-running-the-simulated-blinky-application",
- "text": "The section shows you how to build and run the blinky application to run on Mynewt's simulated hardware. Note : This is not yet supported on Windows. Refer to the Blinky Tutorials to create a blinky application on a target boards.",
+ "text": "The section shows you how to build and run the blinky application to run on Mynewt's simulated hardware. Note : This is not yet supported on Windows. Refer to the Blinky Tutorials to create a blinky application for a target board.",
"title": "Building and Running the Simulated Blinky Application"
},
{
@@ -582,7 +582,7 @@
},
{
"location": "/os/tutorials/arduino_zero/",
- "text": "Blinky, your \"Hello World!\", on Arduino Zero\n\n\nThis tutorial shows you how to create, build and run the Blinky application on an Arduino Zero board.\n\n\nPrerequisites\n\n\n\n\nMeet the prerequisites listed in \nProject Blinky\n.\n\n\nHave an Arduino Zero board.\n\nNote: 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.\n\n\nInstall the \nOpenOCD debugger\n.\n\n\n\n\nThis 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.\n\n\n\n\n\n\n\n\nMynewt has not been tested on Arduino M0 which has no internal debugger support.\n\n\n\n\nCreate a Project\n\n\nCreate a new project if you do not have an existing one. You can skip this step and proceed to \nfetch external packages\n if you already created a project. \n\n\nRun the following commands to create a new projec
t: \n\n\n $ mkdir ~/dev\n $ cd ~/dev\n $ newt new myproj\n Downloading project skeleton from apache/incubator-mynewt-blinky...\n Installing skeleton in myproj...\n Project myproj successfully created.\n $ cd myproj\n $ newt install\n apache-mynewt-core\n $\n\n\n\n\n\n\n\n Fetch External Packages\n\n\nMynewt uses source code provided directly from the chip manufacturer for\nlow level operations. Sometimes this code is licensed only for the specific manufacturer of the chipset and cannot live in the Apache Mynewt repository. That happens to be the case for the Arduino Zero board which uses Atmel SAMD21. Runtime's github repository hosts such external third-party packages and the newt tool can fetch them.\n\n\nTo fetch the package with MCU support for Atmel SAMD21 for Arduino Zero from the Runtime git repository, you need to add\nthe repository to the \nproject.yml\n file in your base project directory.\n\n\nHere is an example \nproject.yml\n file with the
Arduino Zero repository\nadded. The sections with \nmynewt_arduino_zero\n that need to be added to\nyour project file are highlighted.\n\n\n$ more project.yml\nproject.name: \nmy_project\n\n\nproject.repositories:\n - apache-mynewt-core\n\n - mynewt_arduino_zero\n\n\nrepository.apache-mynewt-core:\n type: github\n vers: 1-latest\n user: apache\n repo: incubator-mynewt-core\n\n\nrepository.mynewt_arduino_zero:\n\n type: github\n\n vers: 1-latest\n\n user: runtimeco\n\n repo: mynewt_arduino_zero\n\n$\n\n\n\n\n\n\nInstall the project dependencies using the \nnewt install\n command (you can specify \n-v\n for verbose output):\n\n\n$ newt install\napache-mynewt-core\nmynewt_arduino_zero\n$\n\n\n\n\n\n\n\nNOTE:\n If there has been a new release of a repo used in your project since you last installed it, the \n1-latest\n version for the repo in the \nproject.yml\n file will refer to the new release and will not match the installed files. In that case you will
get an error message saying so and you will need to run \nnewt upgrade\n to overwrite the existing files with the latest codebase.\n\n\n\nYou need to create two targets for the Arduino Zero Pro board, one for the bootloader and one for the Blinky application.\n\n\n\nRun the following \nnewt target\n commands, from your project directory, to create a bootloader target. We name the target \narduino_boot\n.\n\n\n$ newt target create arduino_boot\n$ newt target set arduino_boot bsp=@mynewt_arduino_zero/hw/bsp/arduino_zero\nTarget targets/arduino_boot successfully created\n$ newt target set arduino_boot app=@apache-mynewt-core/apps/boot\nTarget targets/arduino_boot successfully set target.app to @apache-mynewt-core/apps/boot\n$ newt target set arduino_boot build_profile=optimized\nTarget targets/arduino_boot successfully set target.build_profile to optimized\n$ newt target set arduino_boot syscfg=BSP_ARDUINO_ZERO_PRO=1\nTarget targets/arduino_boot successfully set target.syscfg to BSP_
ARDUINO_ZERO_PRO=1\n$\n\n\n\n\n\nNote:\n If you have an Arduino Zero instead of an Arduino Zero Pro or Arduino M0 Pro board, replace \nBSP_ARDUINO_ZERO_PRO\n with \nBSP_ARDUINO_ZERO\n in the last \nnewt target set\n command.\n\n\nThese commands perform the following:\n\n\n\n\nCreate a target named \narduino_boot\n for the Arduino Zero Bootloader. \n\n\nSet the application for the \narduino_boot\n target to the default Apache Mynewt\n bootloader (\n@apache-mynewt-core/apps/boot\n)\n\n\nSet the board support package for the target to\n \n@mynewt_arduino_zero/hw/bsp/arduino_zero\n. This is a reference to the downloaded\n Arduino Zero support from Github.\n\n\nUse the \"optimized\" build profile for the \narduino_boot\n target. This\n instructs Newt to generate smaller and more efficient code for this target.\n This setting is necessary due to the bootloader's strict size constraints.\n\n\nSets the system configuration setting for Board Support Package to support the
Arduino Zero Pro. \n\n\n\n\nSee the \nConcepts\n section for more information on setting options.\n\n\n\nCreate a Target for the Blinky Application\n\n\nRun the following \nnewt target\n commands to create the Blinky application target. We name the application target \narduino_blinky\n.\n\n\n$ newt target create arduino_blinky\nTarget targets/arduino_blinky successfully created\n$ newt target set arduino_blinky app=apps/blinky\nTarget targets/arduino_blinky successfully set target.app to apps/blinky\n$ newt target set arduino_blinky bsp=@mynewt_arduino_zero/hw/bsp/arduino_zero\nTarget targets/arduino_blinky successfully set target.bsp to @mynewt_arduino_zero/hw/bsp/arduino_zero\n$ newt target set arduino_blinky build_profile=debug\nTarget targets/arduino_blinky successfully set target.build_profile to debug\n$ newt target set arduino_blinky syscfg=BSP_ARDUINO_ZERO_PRO=1\nTarget targets/arduino_boot successfully set target.syscfg to BSP_ARDUINO_ZERO_PRO=1\n$\n\n\n\n\n\nNote:\n If yo
u have an Arduino Zero instead of a Arduino Zero Pro board, replace \nBSP_ARDUINO_ZERO_PRO\n with \nBSP_ARDUINO_ZERO\n in the last \nnewt target set\n command.\n\n\n\n\nBuild the Bootloader\n\n\nRun the \nnewt build arduino_boot\n command to build the bootloader:\n\n\n$ newt build arduino_boot\nBuilding target targets/arduino_boot\nCompiling bin/targets/arduino_boot/generated/src/arduino_boot-sysinit-app.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/image_rsa.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/image_ec.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/image_ec256.c\nCompiling bin/targets/arduino_boot/generated/src/arduino_boot-sysflash.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/image_validate.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/bootutil_misc.c\nCompiling repos/apache-mynewt-core/apps/boot/src/boot.c\nCompiling repos/apache-mynewt-core/crypto/mbedtls/src/arc4.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src
/loader.c\nCompiling repos/apache-mynewt-core/crypto/mbedtls/src/aes.c\n\n ....\n\nArchiving sys_mfg.a\nArchiving sys_sysinit.a\nArchiving util_mem.a\nLinking ~/dev/myproj/bin/targets/arduino_boot/app/apps/boot/boot.elf\nTarget successfully built: targets/arduino_boot\n\n\n\n\n\n\n\nBuild the Blinky Application\n\n\nRun the \nnewt build arduino_blinky\n command to build the Blinky application image:\n\n\n$ newt build arduino_blinky\nBuilding target targets/arduino_blinky\nCompiling repos/apache-mynewt-core/hw/hal/src/hal_flash.c\nCompiling apps/blinky/src/main.c\nCompiling repos/mynewt_arduino_zero/hw/mcu/atmel/samd21xx/src/sam0/drivers/i2s/i2s.c\nCompiling repos/mynewt_arduino_zero/hw/bsp/arduino_zero/src/hal_bsp.c\nCompiling repos/mynewt_arduino_zero/hw/mcu/atmel/samd21xx/src/sam0/drivers/i2s/i2s_callback.c\nCompiling repos/mynewt_arduino_zero/hw/mcu/atmel/samd21xx/src/sam0/drivers/nvm/nvm.c\n\n ...\n\nArchiving sys_mfg.a\nArchiving sys_sysinit.a\nArchiving util_mem.a\nLi
nking ~/dev/myproj/bin/targets/arduino_blinky/app/apps/blinky/blinky.elf\nTarget successfully built: targets/arduino_blinky\n\n\n\n\n\n\n\nConnect to the Board\n\n\nConnect your computer to the Arduino Zero (from now on we'll call this the\ntarget) with a Micro-USB cable through the Programming Port as shown below.\nMynewt will load the image onto the board and debug the target through this port. You should see a\ngreen LED come on that indicates the board has power.\n\n\nNo external debugger is required. The Arduino Zero comes with an internal\ndebugger that can be accessed by Mynewt.\n\n\nThe images below show the Arduino Zero Programming Port.\n\n\n\n\n\n\n\n\nLoad the Bootloader onto the Board\n\n\nRun the \nnewt load arduino_boot\n command to load the bootloader onto the board:\n\n\n$ newt load arduino_boot\nLoading bootloader\n$\n\n\n\n\n\nThe bootloader is loaded onto your board succesfully when the \nnewt load\n command returns to the command prompt after the \nLoading boo
tloader\n status message. You can proceed to load and run your Blinky application image (See \nRun the Blinky Application\n).\n\n\nIf the \nnewt load\n command outputs the following error messages, you will need to erase the board.\n\n\n$ newt load arduino_boot -v\nLoading bootloader\nError: Downloading ~/dev/myproj/bin/targets/arduino_boot/app/apps/boot/boot.elf.bin to 0x0\nOpen On-Chip Debugger 0.9.0 (2015-11-15-05:39)\nLicensed under GNU GPL v2\nFor bug reports, read\n http://openocd.org/doc/doxygen/bugs.html\nInfo : only one transport option; autoselect \nswd\n\nadapter speed: 500 kHz\nadapter_nsrst_delay: 100\ncortex_m reset_config sysresetreq\nInfo : CMSIS-DAP: SWD Supported\nInfo : CMSIS-DAP: JTAG Supported\nInfo : CMSIS-DAP: Interface Initialised (SWD)\nInfo : CMSIS-DAP: FW Version = 01.1F.0118\nInfo : SWCLK/TCK = 1 SWDIO/TMS = 1 TDI = 1 TDO = 1 nTRST = 0 nRESET = 1\nInfo : CMSIS-DAP: Interface ready\nInfo : clock speed 500 kHz\nInfo : SWD IDCODE 0x0bc11477\nInfo : at91
samd21g18.cpu: hardware has 4 breakpoints, 2 watchpoints\nError: Target not halted\n\n\n\n\n\n\nTo erase your board, start a debug session and enter the highlighted commands at the \n(gdb)\n prompts:\n\n\nNote:\n On Windows, openocd and gdb are started in separate Windows Command Prompt terminals, and the terminals are automatically closed when you quit gdb. In addition, the output of openocd is logged to the openocd.log file in your project's base directory instead of the terminal.\n\n\n$ newt debug arduino_blinky\n(gdb) mon at91samd chip-erase\nchip erased\nchip erased\n(gdb) x/32wx 0\n0x0: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n0x10: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n0x20: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n0x30: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n0x40: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n0x50: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n0x60: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n0x70: 0
xffffffff 0xffffffff 0xffffffff 0xffffffff\n(gdb) q\n\n\n\n\n\n\nRun the \nnewt load arduino_boot\n command again after erasing the board. \n\n\n Reminder if you are using Docker: \n When working with actual hardware, remember that each board has an ID. If you swap boards and do not refresh the USB Device Filter on the VirtualBox UI, the ID might be stale and the Docker instance may not be able to see the board correctly. For example, you may see an error message like \nError: unable to find CMSIS-DAP device\n when you try to load or run an image on the board. In that case, you need to click on the USB link in VirtualBox UI, remove the existing USB Device Filter (e.g. \"Atmel Corp. EDBG CMSIS-DAP[0101]\") by clicking on the \"Removes selected USB filter\" button, and add a new filter by clicking on the \"Adds new USB filter\" button.\n\n\n\n\nRun the Blinky Application\n\n\nAfter you load the bootloader successfully onto your board, you can load and run the Blinky application. \n
\n\nRun the \nnewt run arduino_blinky 1.0.0\n command to build the arduino_blinky target (if necessary), create an image with version 1.0.0, load the image onto the board, and start a debugger session. \n\n\nNote\n The output of the debug session below is for Mac OS and Linux platforms. On Windows, openocd and gdb are started in separate Windows Command Prompt terminals. The output of openocd is logged to the openocd.log file in your project's base directory and not to the terminal. The openocd and gdb terminals will close automatically when you quit gdb. \n\n\n\n$ newt run arduino_blinky 1.0.0\nApp image succesfully generated: ~/dev/myproj/bin/targets/arduino_blinky/app/apps/blinky/blinky.img\nLoading app image into slot 1\n[~/dev/myproj/repos/mynewt_arduino_zero/hw/bsp/arduino_zero/arduino_zero_debug.sh ~/dev/myproj/repos/mynewt_arduino_zero/hw/bsp/arduino_zero ~/dev/myproj/bin/targets/arduino_blinky/app/apps/blinky/blinky]\nOpen On-Chip Debugger 0.9.0 (2015-11-15-13:10)\nLicense
d under GNU GPL v2\nFor bug reports, read\nhttp://openocd.org/doc/doxygen/bugs.html\nInfo : only one transport option; autoselect \nswd\n\nadapter speed: 500 kHz\nadapter_nsrst_delay: 100\ncortex_m reset_config sysresetreq\nInfo : CMSIS-DAP: SWD Supported\nInfo : CMSIS-DAP: JTAG Supported\nInfo : CMSIS-DAP: Interface Initialised (SWD)\nInfo : CMSIS-DAP: FW Version = 01.1F.0118\nInfo : SWCLK/TCK = 1 SWDIO/TMS = 1 TDI = 1 TDO = 1 nTRST = 0 nRESET = 1\nInfo : CMSIS-DAP: Interface ready\nInfo : clock speed 500 kHz\nInfo : SWD IDCODE 0x0bc11477\nInfo : at91samd21g18.cpu: hardware has 4 breakpoints, 2 watchpoints\ntarget state: halted\ntarget halted due to debug-request, current mode: Thread \nxPSR: 0x21000000 pc: 0x0000fca6 psp: 0x20002408\nGNU gdb (GNU Tools for ARM Embedded Processors) 7.8.0.20150604-cvs\nCopyright (C) 2014 Free Software Foundation, Inc.\nLicense GPLv3+: GNU GPL version 3 or later \nhttp://gnu.org/licenses/gpl.html\n\nThis is free software: you are free to change and
redistribute it.\nThere is NO WARRANTY, to the extent permitted by law. Type \nshow copying\n\nand \nshow warranty\n for details.\nThis GDB was configured as \n--host=x86_64-apple-darwin10 --target=arm-none-eabi\n.\nType \nshow configuration\n for configuration details.\nFor bug reporting instructions, please see:\n\nhttp://www.gnu.org/software/gdb/bugs/\n.\nFind the GDB manual and other documentation resources online at:\n\nhttp://www.gnu.org/software/gdb/documentation/\n.\nFor help, type \nhelp\n.\nType \napropos word\n to search for commands related to \nword\n...\nReading symbols from ~/dev/myproj/bin/targets/arduino_blinky/app/apps/blinky/blinky.elf...(no debugging symbols found)...done.\nInfo : accepting \ngdb\n connection on tcp/3333\nInfo : SAMD MCU: SAMD21G18A (256KB Flash, 32KB RAM)\n0x0000fca6 in os_tick_idle ()\ntarget state: halted\ntarget halted due to debug-request, current mode: Thread \nxPSR: 0x21000000 pc: 0x000000b8 msp: 0x20008000\ntarget state: halted\ntarget h
alted due to debug-request, current mode: Thread \nxPSR: 0x21000000 pc: 0x000000b8 msp: 0x20008000\n(gdb) r\nThe \nremote\n target does not support \nrun\n. Try \nhelp target\n or \ncontinue\n.\n(gdb) c\nContinuing.\n\n\n\n\n\n\n\nNOTE:\n The 1.0.0 is the version number to assign to the image. You may assign an arbitrary version number. If you are not providing remote upgrade, and are just developing locally, you can provide 1.0.0 for every image version.\n\n\nIf you want the image to run without the debugger connected, simply quit the\ndebugger and restart the board. The image you programmed will come up and run on \nthe Arduino on the next boot! \n\n\n\nYou should see the LED blink!",
+ "text": "Blinky, your \"Hello World!\", on Arduino Zero\n\n\nThis tutorial shows you how to create, build and run the Blinky application on an Arduino Zero board.\n\n\nPrerequisites\n\n\n\n\nMeet the prerequisites listed in \nProject Blinky\n.\n\n\nHave an Arduino Zero board.\n\nNote: 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.\n\n\nInstall the \nOpenOCD debugger\n.\n\n\n\n\nThis 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.\n\n\n\n\n\n\n\n\nMynewt has not been tested on Arduino M0 which has no internal debugger support.\n\n\n\n\nCreate a Project\n\n\nCreate a new project if you do not have an existing one. You can skip this step and proceed to \nfetch external packages\n if you already created a project. \n\n\nRun the following commands to create a new projec
t: \n\n\n $ mkdir ~/dev\n $ cd ~/dev\n $ newt new myproj\n Downloading project skeleton from apache/incubator-mynewt-blinky...\n Installing skeleton in myproj...\n Project myproj successfully created.\n $ cd myproj\n $ newt install\n apache-mynewt-core\n $\n\n\n\n\n\n\n\n Fetch External Packages\n\n\nMynewt uses source code provided directly from the chip manufacturer for\nlow level operations. Sometimes this code is licensed only for the specific manufacturer of the chipset and cannot live in the Apache Mynewt repository. That happens to be the case for the Arduino Zero board which uses Atmel SAMD21. Runtime's github repository hosts such external third-party packages and the newt tool can fetch them.\n\n\nTo fetch the package with MCU support for Atmel SAMD21 for Arduino Zero from the Runtime git repository, you need to add\nthe repository to the \nproject.yml\n file in your base project directory.\n\n\nHere is an example \nproject.yml\n file with the
Arduino Zero repository\nadded. The sections with \nmynewt_arduino_zero\n that need to be added to\nyour project file are highlighted.\n\n\nNote:\n On Windows platforms: You need to set \nvers\n to \n0-dev\n and use the latest master branch for both repositories.\n\n\n$ more project.yml\nproject.name: \nmy_project\n\n\nproject.repositories:\n - apache-mynewt-core\n\n - mynewt_arduino_zero\n\n\nrepository.apache-mynewt-core:\n type: github\n vers: 1-latest\n user: apache\n repo: incubator-mynewt-core\n\n\nrepository.mynewt_arduino_zero:\n\n type: github\n\n vers: 1-latest\n\n user: runtimeco\n\n repo: mynewt_arduino_zero\n\n$\n\n\n\n\n\n\nInstall the project dependencies using the \nnewt install\n command (you can specify \n-v\n for verbose output):\n\n\n$ newt install\napache-mynewt-core\nmynewt_arduino_zero\n$\n\n\n\n\n\n\n\nNOTE:\n If there has been a new release of a repo used in your project since you last installed it, the \n1-latest\n version for
the repo in the \nproject.yml\n file will refer to the new release and will not match the installed files. In that case you will get an error message saying so and you will need to run \nnewt upgrade\n to overwrite the existing files with the latest codebase.\n\n\n\nYou need to create two targets for the Arduino Zero Pro board, one for the bootloader and one for the Blinky application.\n\n\n\nRun the following \nnewt target\n commands, from your project directory, to create a bootloader target. We name the target \narduino_boot\n.\n\n\n$ newt target create arduino_boot\n$ newt target set arduino_boot bsp=@mynewt_arduino_zero/hw/bsp/arduino_zero\nTarget targets/arduino_boot successfully created\n$ newt target set arduino_boot app=@apache-mynewt-core/apps/boot\nTarget targets/arduino_boot successfully set target.app to @apache-mynewt-core/apps/boot\n$ newt target set arduino_boot build_profile=optimized\nTarget targets/arduino_boot successfully set target.build_profile to optimized\
n$ newt target set arduino_boot syscfg=BSP_ARDUINO_ZERO_PRO=1\nTarget targets/arduino_boot successfully set target.syscfg to BSP_ARDUINO_ZERO_PRO=1\n$\n\n\n\n\n\nNote:\n If you have an Arduino Zero instead of an Arduino Zero Pro or Arduino M0 Pro board, replace \nBSP_ARDUINO_ZERO_PRO\n with \nBSP_ARDUINO_ZERO\n in the last \nnewt target set\n command.\n\n\nThese commands perform the following:\n\n\n\n\nCreate a target named \narduino_boot\n for the Arduino Zero Bootloader. \n\n\nSet the application for the \narduino_boot\n target to the default Apache Mynewt\n bootloader (\n@apache-mynewt-core/apps/boot\n)\n\n\nSet the board support package for the target to\n \n@mynewt_arduino_zero/hw/bsp/arduino_zero\n. This is a reference to the downloaded\n Arduino Zero support from Github.\n\n\nUse the \"optimized\" build profile for the \narduino_boot\n target. This\n instructs Newt to generate smaller and more efficient code for this target.\n This setting is necessary due
to the bootloader's strict size constraints.\n\n\nSets the system configuration setting for Board Support Package to support the Arduino Zero Pro. \n\n\n\n\nSee the \nConcepts\n section for more information on setting options.\n\n\n\nCreate a Target for the Blinky Application\n\n\nRun the following \nnewt target\n commands to create the Blinky application target. We name the application target \narduino_blinky\n.\n\n\n$ newt target create arduino_blinky\nTarget targets/arduino_blinky successfully created\n$ newt target set arduino_blinky app=apps/blinky\nTarget targets/arduino_blinky successfully set target.app to apps/blinky\n$ newt target set arduino_blinky bsp=@mynewt_arduino_zero/hw/bsp/arduino_zero\nTarget targets/arduino_blinky successfully set target.bsp to @mynewt_arduino_zero/hw/bsp/arduino_zero\n$ newt target set arduino_blinky build_profile=debug\nTarget targets/arduino_blinky successfully set target.build_profile to debug\n$ newt target set arduino_blinky syscfg=BSP_ARD
UINO_ZERO_PRO=1\nTarget targets/arduino_boot successfully set target.syscfg to BSP_ARDUINO_ZERO_PRO=1\n$\n\n\n\n\n\nNote:\n If you have an Arduino Zero instead of a Arduino Zero Pro board, replace \nBSP_ARDUINO_ZERO_PRO\n with \nBSP_ARDUINO_ZERO\n in the last \nnewt target set\n command.\n\n\n\n\nBuild the Bootloader\n\n\nRun the \nnewt build arduino_boot\n command to build the bootloader:\n\n\n$ newt build arduino_boot\nBuilding target targets/arduino_boot\nCompiling bin/targets/arduino_boot/generated/src/arduino_boot-sysinit-app.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/image_rsa.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/image_ec.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/image_ec256.c\nCompiling bin/targets/arduino_boot/generated/src/arduino_boot-sysflash.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/image_validate.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/bootutil_misc.c\nCompiling repos/apache-mynewt-core/apps/bo
ot/src/boot.c\nCompiling repos/apache-mynewt-core/crypto/mbedtls/src/arc4.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/loader.c\nCompiling repos/apache-mynewt-core/crypto/mbedtls/src/aes.c\n\n ....\n\nArchiving sys_mfg.a\nArchiving sys_sysinit.a\nArchiving util_mem.a\nLinking ~/dev/myproj/bin/targets/arduino_boot/app/apps/boot/boot.elf\nTarget successfully built: targets/arduino_boot\n\n\n\n\n\n\n\nBuild the Blinky Application\n\n\nRun the \nnewt build arduino_blinky\n command to build the Blinky application image:\n\n\n$ newt build arduino_blinky\nBuilding target targets/arduino_blinky\nCompiling repos/apache-mynewt-core/hw/hal/src/hal_flash.c\nCompiling apps/blinky/src/main.c\nCompiling repos/mynewt_arduino_zero/hw/mcu/atmel/samd21xx/src/sam0/drivers/i2s/i2s.c\nCompiling repos/mynewt_arduino_zero/hw/bsp/arduino_zero/src/hal_bsp.c\nCompiling repos/mynewt_arduino_zero/hw/mcu/atmel/samd21xx/src/sam0/drivers/i2s/i2s_callback.c\nCompiling repos/mynewt_arduino_zero/hw/mc
u/atmel/samd21xx/src/sam0/drivers/nvm/nvm.c\n\n ...\n\nArchiving sys_mfg.a\nArchiving sys_sysinit.a\nArchiving util_mem.a\nLinking ~/dev/myproj/bin/targets/arduino_blinky/app/apps/blinky/blinky.elf\nTarget successfully built: targets/arduino_blinky\n\n\n\n\n\n\n\nConnect to the Board\n\n\nConnect your computer to the Arduino Zero (from now on we'll call this the\ntarget) with a Micro-USB cable through the Programming Port as shown below.\nMynewt will load the image onto the board and debug the target through this port. You should see a\ngreen LED come on that indicates the board has power.\n\n\nNo external debugger is required. The Arduino Zero comes with an internal\ndebugger that can be accessed by Mynewt.\n\n\nThe images below show the Arduino Zero Programming Port.\n\n\n\n\n\n\n\n\nLoad the Bootloader onto the Board\n\n\nRun the \nnewt load arduino_boot\n command to load the bootloader onto the board:\n\n\n$ newt load arduino_boot\nLoading bootloader\n$\n\n\n\n\n\nThe boot
loader is loaded onto your board succesfully when the \nnewt load\n command returns to the command prompt after the \nLoading bootloader\n status message. You can proceed to load and run your Blinky application image (See \nRun the Blinky Application\n).\n\n\nIf the \nnewt load\n command outputs the following error messages, you will need to erase the board.\n\n\n$ newt load arduino_boot -v\nLoading bootloader\nError: Downloading ~/dev/myproj/bin/targets/arduino_boot/app/apps/boot/boot.elf.bin to 0x0\nOpen On-Chip Debugger 0.9.0 (2015-11-15-05:39)\nLicensed under GNU GPL v2\nFor bug reports, read\n http://openocd.org/doc/doxygen/bugs.html\nInfo : only one transport option; autoselect \nswd\n\nadapter speed: 500 kHz\nadapter_nsrst_delay: 100\ncortex_m reset_config sysresetreq\nInfo : CMSIS-DAP: SWD Supported\nInfo : CMSIS-DAP: JTAG Supported\nInfo : CMSIS-DAP: Interface Initialised (SWD)\nInfo : CMSIS-DAP: FW Version = 01.1F.0118\nInfo : SWCLK/TCK = 1 SWDIO/TMS = 1 TDI = 1 TDO =
1 nTRST = 0 nRESET = 1\nInfo : CMSIS-DAP: Interface ready\nInfo : clock speed 500 kHz\nInfo : SWD IDCODE 0x0bc11477\nInfo : at91samd21g18.cpu: hardware has 4 breakpoints, 2 watchpoints\nError: Target not halted\n\n\n\n\n\n\nTo erase your board, start a debug session and enter the highlighted commands at the \n(gdb)\n prompts:\n\n\nNote:\n On Windows, openocd and gdb are started in separate Windows Command Prompt terminals, and the terminals are automatically closed when you quit gdb. In addition, the output of openocd is logged to the openocd.log file in your project's base directory instead of the terminal.\n\n\n$ newt debug arduino_blinky\n(gdb) mon at91samd chip-erase\nchip erased\nchip erased\n(gdb) x/32wx 0\n0x0: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n0x10: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n0x20: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n0x30: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n0x40: 0xffffffff 0xffffffff 0xffffffff 0xff
ffffff\n0x50: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n0x60: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n0x70: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n(gdb) q\n\n\n\n\n\n\nRun the \nnewt load arduino_boot\n command again after erasing the board. \n\n\n Reminder if you are using Docker: \n When working with actual hardware, remember that each board has an ID. If you swap boards and do not refresh the USB Device Filter on the VirtualBox UI, the ID might be stale and the Docker instance may not be able to see the board correctly. For example, you may see an error message like \nError: unable to find CMSIS-DAP device\n when you try to load or run an image on the board. In that case, you need to click on the USB link in VirtualBox UI, remove the existing USB Device Filter (e.g. \"Atmel Corp. EDBG CMSIS-DAP[0101]\") by clicking on the \"Removes selected USB filter\" button, and add a new filter by clicking on the \"Adds new USB filter\" button.\n\n\n\n\nRun the Bl
inky Application\n\n\nAfter you load the bootloader successfully onto your board, you can load and run the Blinky application. \n\n\nRun the \nnewt run arduino_blinky 1.0.0\n command to build the arduino_blinky target (if necessary), create an image with version 1.0.0, load the image onto the board, and start a debugger session. \n\n\nNote\n The output of the debug session below is for Mac OS and Linux platforms. On Windows, openocd and gdb are started in separate Windows Command Prompt terminals. The output of openocd is logged to the openocd.log file in your project's base directory and not to the terminal. The openocd and gdb terminals will close automatically when you quit gdb. \n\n\n\n$ newt run arduino_blinky 1.0.0\nApp image succesfully generated: ~/dev/myproj/bin/targets/arduino_blinky/app/apps/blinky/blinky.img\nLoading app image into slot 1\n[~/dev/myproj/repos/mynewt_arduino_zero/hw/bsp/arduino_zero/arduino_zero_debug.sh ~/dev/myproj/repos/mynewt_arduino_zero/hw/bsp/ardu
ino_zero ~/dev/myproj/bin/targets/arduino_blinky/app/apps/blinky/blinky]\nOpen On-Chip Debugger 0.9.0 (2015-11-15-13:10)\nLicensed under GNU GPL v2\nFor bug reports, read\nhttp://openocd.org/doc/doxygen/bugs.html\nInfo : only one transport option; autoselect \nswd\n\nadapter speed: 500 kHz\nadapter_nsrst_delay: 100\ncortex_m reset_config sysresetreq\nInfo : CMSIS-DAP: SWD Supported\nInfo : CMSIS-DAP: JTAG Supported\nInfo : CMSIS-DAP: Interface Initialised (SWD)\nInfo : CMSIS-DAP: FW Version = 01.1F.0118\nInfo : SWCLK/TCK = 1 SWDIO/TMS = 1 TDI = 1 TDO = 1 nTRST = 0 nRESET = 1\nInfo : CMSIS-DAP: Interface ready\nInfo : clock speed 500 kHz\nInfo : SWD IDCODE 0x0bc11477\nInfo : at91samd21g18.cpu: hardware has 4 breakpoints, 2 watchpoints\ntarget state: halted\ntarget halted due to debug-request, current mode: Thread \nxPSR: 0x21000000 pc: 0x0000fca6 psp: 0x20002408\nGNU gdb (GNU Tools for ARM Embedded Processors) 7.8.0.20150604-cvs\nCopyright (C) 2014 Free Software Foundation, Inc.\nLi
cense GPLv3+: GNU GPL version 3 or later \nhttp://gnu.org/licenses/gpl.html\n\nThis is free software: you are free to change and redistribute it.\nThere is NO WARRANTY, to the extent permitted by law. Type \nshow copying\n\nand \nshow warranty\n for details.\nThis GDB was configured as \n--host=x86_64-apple-darwin10 --target=arm-none-eabi\n.\nType \nshow configuration\n for configuration details.\nFor bug reporting instructions, please see:\n\nhttp://www.gnu.org/software/gdb/bugs/\n.\nFind the GDB manual and other documentation resources online at:\n\nhttp://www.gnu.org/software/gdb/documentation/\n.\nFor help, type \nhelp\n.\nType \napropos word\n to search for commands related to \nword\n...\nReading symbols from ~/dev/myproj/bin/targets/arduino_blinky/app/apps/blinky/blinky.elf...(no debugging symbols found)...done.\nInfo : accepting \ngdb\n connection on tcp/3333\nInfo : SAMD MCU: SAMD21G18A (256KB Flash, 32KB RAM)\n0x0000fca6 in os_tick_idle ()\ntarget state: halted\ntarget ha
lted due to debug-request, current mode: Thread \nxPSR: 0x21000000 pc: 0x000000b8 msp: 0x20008000\ntarget state: halted\ntarget halted due to debug-request, current mode: Thread \nxPSR: 0x21000000 pc: 0x000000b8 msp: 0x20008000\n(gdb) r\nThe \nremote\n target does not support \nrun\n. Try \nhelp target\n or \ncontinue\n.\n(gdb) c\nContinuing.\n\n\n\n\n\n\n\nNOTE:\n The 1.0.0 is the version number to assign to the image. You may assign an arbitrary version number. If you are not providing remote upgrade, and are just developing locally, you can provide 1.0.0 for every image version.\n\n\nIf you want the image to run without the debugger connected, simply quit the\ndebugger and restart the board. The image you programmed will come up and run on \nthe Arduino on the next boot! \n\n\n\nYou should see the LED blink!",
"title": "Blinky on Arduino Zero"
},
{
@@ -627,7 +627,7 @@
},
{
"location": "/os/tutorials/blinky_primo/",
- "text": "Blinky, your \"Hello World!\", on Arduino Primo\n\n\nThis tutorial shows you how to create, build, and run the Blinky application on an Arduino Primo board.\n\n\nNote that the Mynewt OS will run on the nRF52 chip in the Arduino Primo board. However, the board support package for the Arduino Primo is different from the nRF52 dev kit board support package.\n\n\n\nPrerequisites\n\n\n\n\nMeet the the prerequisites listed in \nProject Blinky\n.\n\n\nHave an Arduino Primo board.\n\n\nInstall a debugger. Choose one of the two options below: Option 1 requires additional hardware but very easy to set up. \n\n\n\n\n\n\nOption 1\n\n\n\n\nSegger J-Link Debug Probe\n - any model (this tutorial has been tested with J-Link EDU and J-Link Pro)\n\n\nJ-Link 9 pin Cortex-M Adapter\n that allows JTAG, SWD and SWO connections between J-Link and Cortex M based target hardware systems\n\n\nInstall the \nSegger JLINK Software and documentation pack\n. \n\n\n\n\nOption 2\n\n\nThis boa
rd requires a patch version of OpenOCD 0.10.0 that is in development. See \nInstall OpenOCD\n instructions to install it if you do not have this version installed.\n\n\nYou can now use openocd to upload to Arduino Primo board via the USB port itself.\n\n\nCreate a Project\n\n\nCreate a new project if you do not have an existing one. You can skip this step and proceed to \ncreate the targets\n if you already created a project.\n\n\nRun the following commands to create a new project:\n\n\n $ mkdir ~/dev\n $ cd ~/dev\n $ newt new myproj\n Downloading project skeleton from apache/incubator-mynewt-blinky...\n Installing skeleton in myproj...\n Project myproj successfully created.\n $ cd myproj\n $ newt install\n apache-mynewt-core\n $\n\n\n\n\n\n\n\nCreate the Targets\n\n\nCreate two targets for the Arduino Primo board - one for the bootloader and one for the Blinky application.\n\n\nRun the following \nnewt target\n commands, from your project directory, t
o create a bootloader target. We name the target \nprimo_boot\n.\n\n\n$ newt target create primo_boot\n$ newt target set primo_boot app=@apache-mynewt-core/apps/boot bsp=@apache-mynewt-core/hw/bsp/arduino_primo_nrf52 build_profile=optimized\n\n\n\n\n\n\nRun the following \nnewt target\n commands to create a target for the Blinky application. We name the target \nprimoblinky\n.\n\n\n$ newt target create primoblinky\n$ newt target set primoblinky app=apps/blinky bsp=@apache-mynewt-core/hw/bsp/arduino_primo_nrf52 build_prof
<TRUNCATED>
[5/5] incubator-mynewt-site git commit: This closes #183. This closes
#184. Adding instructions to use Visual Studio for Mynewt developers
Posted by ad...@apache.org.
This closes #183. This closes #184. Adding instructions to use Visual Studio for Mynewt developers
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/65dc6d41
Tree: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/tree/65dc6d41
Diff: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/diff/65dc6d41
Branch: refs/heads/asf-site
Commit: 65dc6d41afd9c1d6e78ef694225297cd179743e5
Parents: 72f0a44
Author: aditihilbert <ad...@runtime.io>
Authored: Mon May 22 09:40:25 2017 -0700
Committer: aditihilbert <ad...@runtime.io>
Committed: Mon May 22 09:40:25 2017 -0700
----------------------------------------------------------------------
develop/faq/answers/index.html | 8 +
develop/faq/go_env/index.html | 12 +-
develop/faq/how_to_edit_docs/index.html | 12 +-
develop/faq/ide/index.html | 546 +++++++++++++++++++
develop/faq/pics/debug_new_config_small.png | Bin 0 -> 71855 bytes
develop/faq/pics/gdb_debug_small.png | Bin 0 -> 134895 bytes
develop/faq/pics/gdb_server_small.png | Bin 0 -> 99128 bytes
develop/faq/pics/gdb_small.png | Bin 0 -> 59655 bytes
develop/faq/pics/integrated_terminal_small.png | Bin 0 -> 51077 bytes
develop/faq/pics/launch_small.png | Bin 0 -> 92234 bytes
develop/faq/pics/task_json_small.png | Bin 0 -> 93487 bytes
develop/faq/pics/task_runner_small.png | Bin 0 -> 92407 bytes
develop/faq/pics/task_select_small.png | Bin 0 -> 66049 bytes
develop/faq/pics/task_start_small.png | Bin 0 -> 99242 bytes
develop/mkdocs/search_index.json | 124 ++++-
develop/newt/install/newt_windows/index.html | 9 +-
develop/newtmgr/install_windows/index.html | 2 +-
.../os/get_started/project_create/index.html | 2 +-
develop/os/tutorials/arduino_zero/index.html | 1 +
develop/os/tutorials/blinky_primo/index.html | 14 +-
.../os/tutorials/blinky_stm32f4disc/index.html | 8 +
develop/os/tutorials/olimex/index.html | 6 +-
.../tutorials/project-stm32-slinky/index.html | 9 +
develop/os/tutorials/rbnano2/index.html | 18 +-
.../os/tutorials/wi-fi_on_arduino/index.html | 5 +-
develop/sitemap.xml | 32 +-
faq/pics/debug_new_config_small.png | Bin 0 -> 71855 bytes
faq/pics/gdb_debug_small.png | Bin 0 -> 134895 bytes
faq/pics/gdb_server_small.png | Bin 0 -> 99128 bytes
faq/pics/gdb_small.png | Bin 0 -> 59655 bytes
faq/pics/integrated_terminal_small.png | Bin 0 -> 51077 bytes
faq/pics/launch_small.png | Bin 0 -> 92234 bytes
faq/pics/task_json_small.png | Bin 0 -> 93487 bytes
faq/pics/task_runner_small.png | Bin 0 -> 92407 bytes
faq/pics/task_select_small.png | Bin 0 -> 66049 bytes
faq/pics/task_start_small.png | Bin 0 -> 99242 bytes
latest/faq/answers/index.html | 8 +
latest/faq/go_env/index.html | 12 +-
latest/faq/how_to_edit_docs/index.html | 12 +-
latest/faq/ide/index.html | 546 +++++++++++++++++++
latest/faq/pics/debug_new_config_small.png | Bin 0 -> 71855 bytes
latest/faq/pics/gdb_debug_small.png | Bin 0 -> 134895 bytes
latest/faq/pics/gdb_server_small.png | Bin 0 -> 99128 bytes
latest/faq/pics/gdb_small.png | Bin 0 -> 59655 bytes
latest/faq/pics/integrated_terminal_small.png | Bin 0 -> 51077 bytes
latest/faq/pics/launch_small.png | Bin 0 -> 92234 bytes
latest/faq/pics/task_json_small.png | Bin 0 -> 93487 bytes
latest/faq/pics/task_runner_small.png | Bin 0 -> 92407 bytes
latest/faq/pics/task_select_small.png | Bin 0 -> 66049 bytes
latest/faq/pics/task_start_small.png | Bin 0 -> 99242 bytes
latest/mkdocs/search_index.json | 124 ++++-
latest/newt/install/newt_windows/index.html | 9 +-
latest/newtmgr/install_windows/index.html | 2 +-
latest/os/get_started/project_create/index.html | 2 +-
latest/os/tutorials/arduino_zero/index.html | 1 +
latest/os/tutorials/blinky_primo/index.html | 14 +-
.../os/tutorials/blinky_stm32f4disc/index.html | 8 +
latest/os/tutorials/olimex/index.html | 6 +-
.../tutorials/project-stm32-slinky/index.html | 9 +
latest/os/tutorials/rbnano2/index.html | 18 +-
latest/os/tutorials/wi-fi_on_arduino/index.html | 5 +-
latest/sitemap.xml | 32 +-
sitemap.xml | 26 +-
v0_9_0/faq/pics/debug_new_config_small.png | Bin 0 -> 71855 bytes
v0_9_0/faq/pics/gdb_debug_small.png | Bin 0 -> 134895 bytes
v0_9_0/faq/pics/gdb_server_small.png | Bin 0 -> 99128 bytes
v0_9_0/faq/pics/gdb_small.png | Bin 0 -> 59655 bytes
v0_9_0/faq/pics/integrated_terminal_small.png | Bin 0 -> 51077 bytes
v0_9_0/faq/pics/launch_small.png | Bin 0 -> 92234 bytes
v0_9_0/faq/pics/task_json_small.png | Bin 0 -> 93487 bytes
v0_9_0/faq/pics/task_runner_small.png | Bin 0 -> 92407 bytes
v0_9_0/faq/pics/task_select_small.png | Bin 0 -> 66049 bytes
v0_9_0/faq/pics/task_start_small.png | Bin 0 -> 99242 bytes
v0_9_0/sitemap.xml | 26 +-
74 files changed, 1522 insertions(+), 146 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/develop/faq/answers/index.html
----------------------------------------------------------------------
diff --git a/develop/faq/answers/index.html b/develop/faq/answers/index.html
index 6385c7f..9823050 100644
--- a/develop/faq/answers/index.html
+++ b/develop/faq/answers/index.html
@@ -220,6 +220,14 @@
<li >
+ <a href="../ide/">Using an IDE to Develop Mynewt Applications</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../how_to_edit_docs/">Edit Docs</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/develop/faq/go_env/index.html
----------------------------------------------------------------------
diff --git a/develop/faq/go_env/index.html b/develop/faq/go_env/index.html
index aadb28c..c332cfc 100644
--- a/develop/faq/go_env/index.html
+++ b/develop/faq/go_env/index.html
@@ -220,6 +220,14 @@
<li >
+ <a href="../ide/">Using an IDE to Develop Mynewt Applications</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../how_to_edit_docs/">Edit Docs</a>
</li>
@@ -466,8 +474,8 @@ Build and install the tool. The updated binary will be installed in the <strong>
</li>
<li class="pull-right">
- <a href=../how_to_edit_docs/>
- Next: Edit Docs
+ <a href=../ide/>
+ Next: Using an IDE to Develop Mynewt Applications
<span class="fa fa-arrow-right"></span>
</a>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/develop/faq/how_to_edit_docs/index.html
----------------------------------------------------------------------
diff --git a/develop/faq/how_to_edit_docs/index.html b/develop/faq/how_to_edit_docs/index.html
index a0f2954..eef8d87 100644
--- a/develop/faq/how_to_edit_docs/index.html
+++ b/develop/faq/how_to_edit_docs/index.html
@@ -219,6 +219,14 @@
+ <li >
+ <a href="../ide/">Using an IDE to Develop Mynewt Applications</a>
+ </li>
+
+
+
+
+
<li class="active">
<a href="./">Edit Docs</a>
</li>
@@ -317,9 +325,9 @@
<ul class="nav nav-pills" style="margin-bottom: 10px">
<li>
- <a href=../go_env/>
+ <a href=../ide/>
<span class="fa fa-arrow-left"></span>
- Previous: Setting Up Go to Contribute to Newt and Newtmgr Tools
+ Previous: Using an IDE to Develop Mynewt Applications
</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/develop/faq/ide/index.html
----------------------------------------------------------------------
diff --git a/develop/faq/ide/index.html b/develop/faq/ide/index.html
new file mode 100644
index 0000000..fdc49c9
--- /dev/null
+++ b/develop/faq/ide/index.html
@@ -0,0 +1,546 @@
+<!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/faq/ide/"> -->
+ <link rel="shortcut icon" href="../../img/favicon.ico">
+
+ <title>Using an IDE to Develop Mynewt Applications - 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="Using an IDE to Develop Mynewt Applications">
+
+
+ <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="../../os/introduction/">Mynewt Documentation</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li><a href="
+ ../go_env/
+">Appendix</a>
+
+
+ <ul>
+
+
+
+ <li >
+ <a href="../go_env/">Setting Up Go to Contribute to Newt and Newtmgr Tools</a>
+ </li>
+
+
+
+
+
+ <li class="active">
+ <a href="./">Using an IDE to Develop Mynewt Applications</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../how_to_edit_docs/">Edit Docs</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../answers/">FAQ</a>
+ </li>
+
+
+
+ </ul>
+
+ </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="../go_env/">Appendix</a></li>
+
+
+
+ <li>» Using an IDE to Develop Mynewt Applications</li>
+
+
+
+ </ul>
+</div>
+ </div>
+
+ <h2 id="developing-mynewt-applications-with-visual-studio-code">Developing Mynewt Applications with Visual Studio Code</h2>
+<p>This guide shows you how to set up Visual Studio Code to develop and debug Mynewt applications. Visual Studio Code is supported on Mac OS, Linux, and Windows. This guide shows you how to:</p>
+<ol>
+<li>Install Visual Studio Code. </li>
+<li>Install the C/C++ and debugger extensions.</li>
+<li>Define task configurations to build Mynewt applications.</li>
+<li>Define debugger configurations to debug Mynewt applications. </li>
+<li>Launch the debugger. </li>
+</ol>
+<p>Prerequisites:</p>
+<ul>
+<li>Have Internet connectivity to fetch remote Mynewt components.</li>
+<li>Have a computer to build a Mynewt application.</li>
+<li>Perform <a href="../../os/get_started/native_install_intro/">native installation</a> for the Mynewt tools and toolchains.</li>
+<li>Read the Mynewt OS Concepts 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 Creating Your First Project. </li>
+<li>Complete one of the <a href="../../os/tutorials/blinky/">Blinky Tutorials</a>.</li>
+</ul>
+<p><strong>Notes:</strong> </p>
+<ul>
+<li>This guide is not a tutorial for Visual Studio Code. It assumes you are familiar with Visual Studio Code. If this is your first time using Visual Studio Code, we recommend that you read the Visual Studio Code <a href="https://code.visualstudio.com/docs">documentation and tutorials</a> and evaluate whether you would like to use it to develop Mynewt applications. </li>
+<li>This guide uses Visual Studio Code on Windows. Visual Studio Code is supported on Linux and Mac OS but may have some variations in the keyboard shortcuts and command names for these platforms. </li>
+<li>You can also use the Eclipse IDE to develop Mynewt applications. See <a href="https://www.codecoup.pl/blog/hacking-mynewt-in-eclipse">https://www.codecoup.pl/blog/hacking-mynewt-in-eclipse</a> for more details.</li>
+</ul>
+<h3 id="installing-visual-studio-code">Installing Visual Studio Code</h3>
+<p>Download and install Visual Studio Code from <a href="https://code.visualstudio.com/">https://code.visualstudio.com/</a>.</p>
+<h3 id="installing-the-cc-and-debugger-extensions">Installing the C/C++ and Debugger Extensions</h3>
+<p>You need to install two extensions:</p>
+<ol>
+<li>
+<p>The C/C++ extension from Microsoft. This extension provides language support such as symbol searching, signatuare help, go to definition, and go to declaration.</p>
+</li>
+<li>
+<p>The Native Debug extension from webfreak. This extension provides GDB support. </p>
+</li>
+</ol>
+<p><br>
+To install the C/C++ extension:</p>
+<ol>
+<li>Press <code>Ctrl-P</code> to open the search box.</li>
+<li>Type <code>ext install cpptools</code> in the search box and press Enter. You should see the extension at the top of the list. </li>
+<li>Click <code>Install</code> to install the extension.
+<br></li>
+</ol>
+<p>To install the Native Debugger:</p>
+<ol>
+<li>Press <code>Ctrl-P</code> to open the search box.</li>
+<li>Type <code>ext install webfreak.debug</code> in the search box and press Enter. You should see the Native Debug extension at the top of the list.</li>
+<li>Click <code>Install</code> to install the extension.
+<br></li>
+</ol>
+<h3 id="defining-tasks-for-mynewt-projects">Defining Tasks for Mynewt Projects</h3>
+<p>Two main concepts in Visual Studio Code are workspaces and tasks. A workspace represents a folder that is open. You can open multiple workspaces and switch between workspaces. </p>
+<p>Tasks allow you to integrate the external tools and operations that are used to build or test your project into Visual Studio Code. Tasks are run from and the task results can be analyzed in Visual Studio Code. Tasks are defined within the scope of a workspace. This means that the tasks you define for a workspace only apply to the given workspace.</p>
+<p><br></p>
+<h4 id="associating-a-mynewt-project-to-a-workspace">Associating a Mynewt Project to a Workspace</h4>
+<p>For your Mynewt project, your Visual Studio Code workspace is the Mynewt project base directory. For example, if you create a project named <code>myproj</code> under the <code>~/dev</code> directory, then you open the <code>~/dev/myproj</code> folder for your workspace. </p>
+<p>Select <strong>File</strong> > <strong>Open Folder</strong>, and select the <code>myproj</code> folder from the <code>Select Folder</code> dialog box to open the folder.</p>
+<p><br></p>
+<h4 id="defining-visual-studio-code-tasks-to-build-and-debug-mynewt-applications">Defining Visual Studio Code Tasks to Build and Debug Mynewt Applications</h4>
+<p>You define Visual Studio Code tasks to build and debug your Mynewt targets in Visual Studio Code. We use the Blinky application for the Arduino Zero board from the <a href="../../os/tutorials/arduino_zero/">Blinky On Arduino Zero Tutorial</a> to illustrate how to define the tasks to build and debug the Arduino blinky bootloader and application targets.</p>
+<p>Perform the following steps to create the tasks to build and debug the Arduino blinky bootloader and appliction targets:</p>
+<p>Step 1: Press <code>Ctrl-Shift-P</code>, type <code>task</code> in the search box, and select <strong>Tasks:Configure Task Runner</strong> from the search results. </p>
+<p>Step 2: Select <strong>Others</strong> (scroll down to the bottom of the list) to create a task runner for external commands.
+<br>
+<p align="center"><img src="/faq/pics/task_runner_small.png"></p>
+<br>
+Tasks are defined in the <code>tasks.json</code> file. You should see the <code>.vscode</code> folder created in the <code>MYPROJ</code> folder and a <code>tasks.json</code> file created in the <code>.vscode</code> folder. The <code>tasks.json</code> file has the following default values. </p>
+<p><br>
+<p align="center"><img src="/faq/pics/task_json_small.png"></p>
+<br></p>
+<p>The sample <code>tasks.json</code> file defines a simple task that runs the echo command with "Hello World" as the argument. </p>
+<p>Step 3: Delete the content from the <code>tasks.json</code> file, add the following definitions, and press <code>Ctrl-S</code> to save the file.</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">{
+ "version": "0.1.0",
+ "command": "newt",
+ "echoCommand": true,
+ "isShellCommand": true,
+
+ "tasks":[
+ {
+ "taskName": "build_arduino_boot",
+ "args": ["build", "arduino_boot"],
+ "suppressTaskName": true
+ },
+ {
+ "taskName": "build_arduino_blinky",
+ "args": ["build", "arduino_blinky"],
+ "isBuildCommand": true,
+ "suppressTaskName": true
+ },
+ {
+ "taskName": "create_arduino_blinky",
+ "args": ["create-image", "arduino_blinky", "1.0.0"],
+ "suppressTaskName":true
+ },
+ {
+ "taskName": "debug_arduino_blinky",
+ "args": ["debug", "arduino_blinky", "-n"],
+ "suppressTaskName": true
+ }
+ ]
+}
+</pre></div>
+
+
+<p><br>
+The <code>tasks.json</code> file specifies the tasks that are run to build and debug the Arduino blinky targets. Each task runs a <code>newt</code> command. The <code>newt</code> command to run and the arguments for the <code>newt</code> command are passed in the <code>args</code> property for each task. </p>
+<p>The following tasks are defined in this example:</p>
+<ol>
+<li><strong>build_arduino_boot</strong>: Runs the <code>newt build arduino_boot</code> command to build the arduino_boot target.</li>
+<li>
+<p><strong>build_arduino_blinky</strong>: Runs the <code>newt build arduino_blinky</code> command to build the arduino_blinky target. </p>
+<p><strong>Note:</strong> This task sets the <code>isBuildCommand</code> property to <code>true</code>. This is an optional property that, when set to true, allows you to run the <strong>Tasks: Run Build Task</strong>(<code>Ctrl-Shift-B</code>) command to start the task.</p>
+</li>
+<li>
+<p><strong>create_arduino_blinky</strong>: Runs the <code>newt create-image arduino_blinky</code> command to create the image file.</p>
+</li>
+<li><strong>debug_arduino_blinky</strong>: Runs the <code>newt build arduino_blinky -n</code> command to debug the arduino_blinky target. The <code>-n</code> flag is specified to start only the GDB server and not the GDB client. We will launch the GDB client from Visual Studio Code.</li>
+</ol>
+<p>For more information on tasks and all supported properties, see the <a href="https://code.visualstudio.com/docs/editor/tasks">Visual Studio Code Task documentation</a>.</p>
+<p><br></p>
+<h4 id="running-a-task">Running a Task</h4>
+<p>To run a task, select <code>Ctrl-Shift-P</code>, type <code>task</code>, and select <strong>Tasks: Run Task</strong>. The tasks that you define in the <code>tasks.json</code> file are listed. Select the task to run. </p>
+<p>The following is an example of running the <code>build_arduino_boot</code> task:
+<br>
+<p align="center"><img src="/faq/pics/task_select_small.png"></p>
+<br>
+<br>
+<p align="center"><img src="/faq/pics/task_start_small.png"></p></p>
+<p><br></p>
+<h4 id="defining-tasks-for-other-newt-commands">Defining Tasks for Other Newt Commands</h4>
+<p>Other newt commands, such as the <code>newt load</code> command, do not need to run from within Visual Studio Code. You can define tasks for them as a convenience or run them on the command line from the Visual Studio Code integrated terminal (or an external terminal).</p>
+<p>To create the tasks for the <code>newt load arduino_boot</code> and <code>newt laod arduino_blinky</code> commands, add the following definitions to the <code>tasks.json</code> file:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> {
+ "taskName": "load_arduino_boot",
+ "args": ["load", "arduino_boot"],
+ "suppressTaskName":true
+ },
+ {
+ "taskName": "load_arduino_blinky",
+ "args": ["load", "arduino_blinky"],
+ "suppressTaskName":true
+ },
+</pre></div>
+
+
+<p><br>
+To run the commands from the Visual Studio integrated terminal, press <code>Ctrl-`</code> to launch the integrated terminal and enter the command as shown:
+<br>
+<p align="center"><img src="/faq/pics/integrated_terminal_small.png"></p>
+<br></p>
+<h3 id="defining-debugger-configurations">Defining Debugger Configurations</h3>
+<p>You need to define a debugger configuration to launch the GDB debugger from within Visual Studio Code: </p>
+<p>Step 1: Select <strong>Debug</strong> > <strong>Open Configuration</strong>, and select the <strong>GDB</strong> environment.</p>
+<p><br>
+<p align="center"><img src="/faq/pics/debug_new_config_small.png"></p>
+<br></p>
+<p>You should see a default <code>launch.json</code> file created in the <code>.vscode</code> folder.
+<br>
+<p align="center"><img src="/faq/pics/launch_small.png"></p>
+<br></p>
+<p><br>
+Step 2: Delete the content from the <code>launch.json</code> file, add the following definitions, and press 'Ctrl-S' to save the file.</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">{
+ "version": "0.2.0",
+ "configurations": [
+ {
+ "name": "gdb_arduino_blinky",
+ "type": "gdb",
+ "request": "attach",
+ "executable": "${workspaceRoot}\\bin\\targets\\arduino_blinky\\app\\apps\\blinky\\blinky.elf",
+ "target": ":3333",
+ "cwd": "${workspaceRoot}",
+ "gdbpath": "arm-none-eabi-gdb.exe",
+ "remote": true
+
+ }
+ ]
+}
+</pre></div>
+
+
+<p><br>
+This defines a <code>gdb_arduino_blinky</code> debugger configuration. It specifies: </p>
+<ul>
+<li>The debugger is type <strong>gdb</strong>.</li>
+<li>To use the <code>blinky.elf</code> file for the executable. </li>
+<li>To use port 3333 to connect with the remote target.</li>
+<li>To use arm-none-eabi-gdb for the GDB program.
+<br></li>
+</ul>
+<h3 id="debugging-your-application">Debugging Your Application</h3>
+<p>To debug your application, start the GDB server and launch the GDB session from Visual Studio Code. For the the arduino blinky example, perform the following:</p>
+<p>Step 1: Run the debug_arduino_blinky task to start the GDB server. Perform the following:</p>
+<ol>
+<li>Press <code>Ctrl-Shift-P</code> and type <code>task</code> in the search box. </li>
+<li>Select <strong>Tasks:Run Task</strong> > <strong>debug_arduino_blinky</strong>.</li>
+<li>Press <code>Ctrl-Shift-U</code> to open the Output Panel and see the OpenOCD GDB Server output.
+<br> <br />
+<p align="center"><img src="/faq/pics/gdb_server_small.png"></p>
+<br></li>
+</ol>
+<p>Step 2: Start the GDB session. Perform the following: </p>
+<ol>
+<li>Press <code>Ctrl-Shift-Y</code> to view the Debug Console. </li>
+<li>Press the Debugging icon on the activity bar (Ctrl-Shift-D) to bring up the Debug Side Bar.</li>
+<li>Select <code>gdb_arduino_blinky</code> from the DEBUG drop down menu. </li>
+<li>Press the green play button to start the gdb session.</li>
+</ol>
+<p align="center"><img src="/faq/pics/gdb_small.png"></p>
+
+<p><br>
+Step 3: Debug your application. You should see a debug session similar to the one shown below:
+<p align="center"><img src="/faq/pics/gdb_debug_small.png"></p>
+<br>
+For more information on how to use the Visual Studio Code Debugger, see the <a href="https://code.visualstudio.com/docs/editor/debugging">Visual Studio Code debugging documentation</a>.</p>
+<h3 id="working-with-multiple-mynewt-applications">Working with Multiple Mynewt Applications</h3>
+<p>As mentioned previously, each mynewt project corresponds to a Visual Studio Code workspace. If you have multiple Mynewt application targets defined in same project, you will need to define build and debug tasks for each target in the <code>tasks.json</code> file and debugger configurations for the targets in the <code>launch.json</code> file for the workspace. If you have a different Mynewt project for each mynewt application, you will need to define build and debug tasks in the <code>tasks.json</code> file and the debugger configuration in the <code>launch.json</code> file for each workspace. </p>
+
+ <div class="row">
+
+
+
+
+<ul class="nav nav-pills" style="margin-bottom: 10px">
+ <li>
+
+ <a href=../go_env/>
+ <span class="fa fa-arrow-left"></span>
+ Previous: Setting Up Go to Contribute to Newt and Newtmgr Tools
+ </a>
+
+ </li>
+ <li class="pull-right">
+
+ <a href=../how_to_edit_docs/>
+ Next: Edit Docs
+ <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/65dc6d41/develop/faq/pics/debug_new_config_small.png
----------------------------------------------------------------------
diff --git a/develop/faq/pics/debug_new_config_small.png b/develop/faq/pics/debug_new_config_small.png
new file mode 100755
index 0000000..5d2e287
Binary files /dev/null and b/develop/faq/pics/debug_new_config_small.png differ
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/develop/faq/pics/gdb_debug_small.png
----------------------------------------------------------------------
diff --git a/develop/faq/pics/gdb_debug_small.png b/develop/faq/pics/gdb_debug_small.png
new file mode 100755
index 0000000..5ebfb11
Binary files /dev/null and b/develop/faq/pics/gdb_debug_small.png differ
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/develop/faq/pics/gdb_server_small.png
----------------------------------------------------------------------
diff --git a/develop/faq/pics/gdb_server_small.png b/develop/faq/pics/gdb_server_small.png
new file mode 100755
index 0000000..e6a42d7
Binary files /dev/null and b/develop/faq/pics/gdb_server_small.png differ
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/develop/faq/pics/gdb_small.png
----------------------------------------------------------------------
diff --git a/develop/faq/pics/gdb_small.png b/develop/faq/pics/gdb_small.png
new file mode 100755
index 0000000..f6c35d2
Binary files /dev/null and b/develop/faq/pics/gdb_small.png differ
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/develop/faq/pics/integrated_terminal_small.png
----------------------------------------------------------------------
diff --git a/develop/faq/pics/integrated_terminal_small.png b/develop/faq/pics/integrated_terminal_small.png
new file mode 100755
index 0000000..11414c8
Binary files /dev/null and b/develop/faq/pics/integrated_terminal_small.png differ
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/develop/faq/pics/launch_small.png
----------------------------------------------------------------------
diff --git a/develop/faq/pics/launch_small.png b/develop/faq/pics/launch_small.png
new file mode 100755
index 0000000..5c13dcf
Binary files /dev/null and b/develop/faq/pics/launch_small.png differ
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/develop/faq/pics/task_json_small.png
----------------------------------------------------------------------
diff --git a/develop/faq/pics/task_json_small.png b/develop/faq/pics/task_json_small.png
new file mode 100755
index 0000000..5047f61
Binary files /dev/null and b/develop/faq/pics/task_json_small.png differ
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/develop/faq/pics/task_runner_small.png
----------------------------------------------------------------------
diff --git a/develop/faq/pics/task_runner_small.png b/develop/faq/pics/task_runner_small.png
new file mode 100755
index 0000000..25a70fa
Binary files /dev/null and b/develop/faq/pics/task_runner_small.png differ
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/develop/faq/pics/task_select_small.png
----------------------------------------------------------------------
diff --git a/develop/faq/pics/task_select_small.png b/develop/faq/pics/task_select_small.png
new file mode 100755
index 0000000..35bc304
Binary files /dev/null and b/develop/faq/pics/task_select_small.png differ
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/develop/faq/pics/task_start_small.png
----------------------------------------------------------------------
diff --git a/develop/faq/pics/task_start_small.png b/develop/faq/pics/task_start_small.png
new file mode 100755
index 0000000..f84cd26
Binary files /dev/null and b/develop/faq/pics/task_start_small.png differ
[2/5] incubator-mynewt-site git commit: This closes #183. This closes
#184. Adding instructions to use Visual Studio for Mynewt developers
Posted by ad...@apache.org.
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/latest/mkdocs/search_index.json
----------------------------------------------------------------------
diff --git a/latest/mkdocs/search_index.json b/latest/mkdocs/search_index.json
index 32cc45b..1282385 100644
--- a/latest/mkdocs/search_index.json
+++ b/latest/mkdocs/search_index.json
@@ -222,7 +222,7 @@
},
{
"location": "/newt/install/newt_windows/",
- "text": "Installing Newt on Windows\n\n\nYou can develop and build Mynewt OS applications for your target boards on the Windows platform. This page shows you how to build the newt tool from the lastest source on the master branch of the \nMynewt newt git repository\n. The tool is written in Go (golang).\n\n\nIn Windows, we use MinGW as the development environment to build and run Mynewt OS applications for target boards. MinGW runs the bash shell and provides a Unix-like environment. This provides a uniform way to build Mynewt OS applications. The Mynewt documentation and tutorials use Unix commands and you can use the same Unix commands on MinGW to follow the tutorials. The documentation will note any commands or behaviors that are specific to Windows.\n\n\nThis guide shows you how to perform the following:\n\n\n\n\nInstall MSYS2/MinGW. \n\n\nInstall Git.\n\n\nInstall Go. \n\n\nSetup the Go environment.\n\n\nDownload the source, build, and install the newt tool.\n\n\n
\n\n\n\nStep 1: Installing MSYS2/MinGW\n\n\nMSYS2/MinGW provides a bash shell and tools to build applications that run on Windows. It includes three subsystems:\n\n\n\n\nMSYS2 toolchain to build POSIX applications that run on Windows. \n\n\nMinGW32 toolchains to build 32 bit native Windows applications. \n\n\nMinGW64 toolchains to build 64 bit native Windows applications. \n\n\n\n\nThe subsystems run the bash shell and provide a Unix-like environment. You can also run Windows applications from the shell. We will use the MinGW subsystem.\n\n\nTo install and setup MSYS2 and MinGW:\n\n\n\n\nDownload and run the \nMSYS2 installer\n. Select the 64 bit version if you are running on a 64 bit platform. Follow the prompts and check the \nRun MSYS2 now\n checkbox on the \nInstallation Complete\n dialog. \n\n\n\n\nIn the MSYS2 terminal, run the \npacman -Syuu\n command. If you get a message to run the update again, close the terminal and run the \npacman -Syuu\n command in a new terminal. \
n\n\nTo start a new MSYS2 terminal, select the \"MSYS2 MSYS\" application from the Windows start menu.\n\n\n\n\n\n\nAdd a new user variable named \nMSYS2_PATH_TYPE\n and set the value to \ninherit\n in your Windows environment. This enables the MSYS2 and MinGW bash to inherit your Windows user \nPath\n values. \n\n\nTo add the variable, select properties for your computer \n Advanced system settings \n Environment Variables \n New\n\n\n\n\n\n\nRun the \npacman -Su vim\n command to install the vim editor. \n\n\nNote:\nYou can also use a Windows editor. You can access your files from the \nC:\\\nmsys-install-folder\n\\home\\\nusername\n folder, where \nmsys-install-folder\n is the folder you installed MSYS2 in. For example, if you installed MSYS2 in the \nmsys64\n folder, your files are stored in \nC:\\msys64\\home\\\nusername\n\n\n\n\n\n\nYou will need to start a MinGW terminal to run the commands specified in the Mynewt documentation and tutorials. To start a MinGW terminal, sele
ct the \"MSYS2 Mingw\" application from the start Menu (you can use either MinGW32 or MinGW64). \nIn Windows, we use the MingGW subsystem to build Mynewt tools and applications. \n\n\nStep 2: Installing Git for Windows\n\n\nDownload and install \nGit for Windows\n if it is not already installed.\n\n\nStep 3: Installing Go\n\n\nDownload and install the latest version of \nGo\n. Newt requires Go version 1.7 or higher.\n\n\nStep 4: Setting Up Your Go Environment\n\n\nThis section describes the Go environment and how to setup a Go workspace. Go provides an environment to compile Go code, construct Go packages, and import Go code. You will use Go commands to import the newt 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 \nsrc\n, \npkg\n and \nbin\n: \n\n\n\n\nsrc contains Go source files organized into packages (one package
per directory)\n\n\npkg contains package objects\n\n\nbin contains the Go application executables that Go builds and installs.\n\n\n\n\nThe \nGOPATH\n environment variable specifies the location of your workspace. To setup this workspace environment, create a \ndev\n directory and then a \ngo\n directory under it. Set the GOPATH environment variable to this directory where you will clone the newt repository.\n\n\nStart up a MinGW terminal and run the following commands to set up your Go workspace:\n\n\n$ cd $HOME\n$ mkdir -p dev/go \n$ cd dev/go\n$ export GOPATH=`pwd`\n\n\n\n\n\n\nAdd the following export statements to your ~/.bash_profile file and source the file:\n\n\nexport GOPATH=$HOME/dev/go\nexport PATH=$GOPATH/bin:$PATH\n\n\n\n\n\n\n\nStep 5: Downloading the Source and Installing the Newt Tool\n\n\nThe newt Go package is \nmynewt.apache.org/newt/newt\n and is stored in the \nApache Mynewt newt tool repository mirrored on github\n. We use the \ngo get\n command to download
the source, build, and install the newt tool binary in the \n$GOPATH/bin\n directory. \n\n\n\nDownload the newt package source and install the tool:\n\n\n$cd $GOPATH\n$go get mynewt.apache.org/newt/newt\n$cd $GOPATH/src/mynewt.apache.org/newt\n$ls \nDISCLAIMER RELEASE_NOTES.md util\nINSTALLING.md build.sh viper\nLICENSE newt yaml\nNOTICE newtmgr\nREADME.md newtvm\n\n\n\n\n\n\nCheck that the newt tool is installed and it is in your path:\n\n\n$ls go/bin\n$ ls bin/newt\nbin/newt\n$which go\n/home/\nuser\n/dev/go/bin/newt\n$ newt version\nApache Newt (incubating) version: 1.0.0-dev\n\n\n\n\n\n\nGet information about the newt tool:\n\n\n$newt\nNewt allows you to create your own embedded application based on the Mynewt\noperating system. 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 project
s. 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 tar
get 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 4)\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\nUse \nnewt [command] --help\n for more information about a command.",
+ "text": "Installing Newt on Windows\n\n\nYou can develop and build Mynewt OS applications for your target boards on the Windows platform. This page shows you how to build the newt tool from the lastest source on the master branch of the \nMynewt newt git repository\n. The tool is written in Go (golang).\n\n\nIn Windows, we use MinGW as the development environment to build and run Mynewt OS applications for target boards. MinGW runs the bash shell and provides a Unix-like environment. This provides a uniform way to build Mynewt OS applications. The Mynewt documentation and tutorials use Unix commands and you can use the same Unix commands on MinGW to follow the tutorials. The documentation will note any commands or behaviors that are specific to Windows.\n\n\nThis guide shows you how to perform the following:\n\n\n\n\nInstall MSYS2/MinGW. \n\n\nInstall Git.\n\n\nInstall Go. \n\n\nSetup the Go environment.\n\n\nDownload the source, build, and install the newt tool.\n\n\n
\n\n\n\nStep 1: Installing MSYS2/MinGW\n\n\nMSYS2/MinGW provides a bash shell and tools to build applications that run on Windows. It includes three subsystems:\n\n\n\n\nMSYS2 toolchain to build POSIX applications that run on Windows. \n\n\nMinGW32 toolchains to build 32 bit native Windows applications. \n\n\nMinGW64 toolchains to build 64 bit native Windows applications. \n\n\n\n\nThe subsystems run the bash shell and provide a Unix-like environment. You can also run Windows applications from the shell. We will use the MinGW subsystem.\n\n\nTo install and setup MSYS2 and MinGW:\n\n\n\n\nDownload and run the \nMSYS2 installer\n. Select the 64 bit version if you are running on a 64 bit platform. Follow the prompts and check the \nRun MSYS2 now\n checkbox on the \nInstallation Complete\n dialog. \n\n\n\n\nIn the MSYS2 terminal, run the \npacman -Syuu\n command. If you get a message to run the update again, close the terminal and run the \npacman -Syuu\n command in a new terminal. \
n\n\nTo start a new MSYS2 terminal, select the \"MSYS2 MSYS\" application from the Windows start menu.\n\n\n\n\n\n\nAdd a new user variable named \nMSYS2_PATH_TYPE\n and set the value to \ninherit\n in your Windows environment. This enables the MSYS2 and MinGW bash to inherit your Windows user \nPath\n values. \n\n\nTo add the variable, select properties for your computer \n Advanced system settings \n Environment Variables \n New\n\n\n\n\n\n\nRun the \npacman -Su vim\n command to install the vim editor. \n\n\nNote:\nYou can also use a Windows editor. You can access your files from the \nC:\\\nmsys-install-folder\n\\home\\\nusername\n folder, where \nmsys-install-folder\n is the folder you installed MSYS2 in. For example, if you installed MSYS2 in the \nmsys64\n folder, your files are stored in \nC:\\msys64\\home\\\nusername\n\n\n\n\n\n\nYou will need to start a MinGW terminal to run the commands specified in the Mynewt documentation and tutorials. To start a MinGW terminal, sele
ct the \"MSYS2 Mingw\" application from the start Menu (you can use either MinGW32 or MinGW64). \nIn Windows, we use the MingGW subsystem to build Mynewt tools and applications. \n\n\nStep 2: Installing Git for Windows\n\n\nDownload and install \nGit for Windows\n if it is not already installed.\n\n\nStep 3: Installing Go\n\n\nDownload and install the latest version of \nGo\n. Newt requires Go version 1.7 or higher.\n\n\nStep 4: Setting Up Your Go Environment\n\n\nThis section describes the Go environment and how to setup a Go workspace. Go provides an environment to compile Go code, construct Go packages, and import Go code. You will use Go commands to import the newt 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 \nsrc\n, \npkg\n and \nbin\n: \n\n\n\n\nsrc contains Go source files organized into packages (one package
per directory)\n\n\npkg contains package objects\n\n\nbin contains the Go application executables that Go builds and installs.\n\n\n\n\nThe \nGOPATH\n environment variable specifies the location of your workspace. To setup this workspace environment, create a \ndev\n directory and then a \ngo\n directory under it. Set the GOPATH environment variable to this directory where you will clone the newt repository.\n\n\nStart up a MinGW terminal and run the following commands to set up your Go workspace:\n\n\n$ cd $HOME\n$ mkdir -p dev/go \n$ cd dev/go\n$ export GOPATH=`pwd`\n\n\n\n\n\n\nAdd the following export statements to your ~/.bash_profile file and source the file:\n\n\nexport GOPATH=$HOME/dev/go\nexport PATH=$GOPATH/bin:$PATH\n\n\n\n\n\n\n\nStep 5: Downloading the Source and Installing the Newt Tool\n\n\nThe newt Go package is \nmynewt.apache.org/newt/newt\n and is stored in the \nApache Mynewt newt tool repository mirrored on github\n. We use the \ngo get\n command to download
the source, build, and install the newt tool binary in the \n$GOPATH/bin\n directory. \n\n\n\nDownload the newt package source and install the tool:\n\n\n$cd $GOPATH\n$go get mynewt.apache.org/newt/newt\n$cd $GOPATH/src/mynewt.apache.org/newt\n$ls \nDISCLAIMER RELEASE_NOTES.md util\nINSTALLING.md build.sh viper\nLICENSE newt yaml\nNOTICE newtmgr\nREADME.md newtvm\n\n\n\n\n\n\nCheck that the newt tool is installed and it is in your path:\n\n\n$ls $GOPATH/bin/newt\n~/dev/go/bin/newt\n$which newt\n~/dev/go/bin/newt\n$ newt version\nApache Newt (incubating) version: 1.0.0-dev\n\n\n\n\n\n\nGet information about the newt tool:\n\n\n$newt\nNewt allows you to create your own embedded application based on the Mynewt\noperating system. 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 com
ponents\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 4)\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\nUse \nnewt [command] --help\n for more information about a command.",
"title": "Install Newt on Windows"
},
{
@@ -252,7 +252,7 @@
},
{
"location": "/newt/install/newt_windows/#step-5-downloading-the-source-and-installing-the-newt-tool",
- "text": "The newt Go package is mynewt.apache.org/newt/newt and is stored in the Apache Mynewt newt tool repository mirrored on github . We use the go get command to download the source, build, and install the newt tool binary in the $GOPATH/bin directory. \nDownload the newt package source and install the tool: $cd $GOPATH\n$go get mynewt.apache.org/newt/newt\n$cd $GOPATH/src/mynewt.apache.org/newt\n$ls \nDISCLAIMER RELEASE_NOTES.md util\nINSTALLING.md build.sh viper\nLICENSE newt yaml\nNOTICE newtmgr\nREADME.md newtvm \nCheck that the newt tool is installed and it is in your path: $ls go/bin\n$ ls bin/newt\nbin/newt\n$which go\n/home/ user /dev/go/bin/newt\n$ newt version\nApache Newt (incubating) version: 1.0.0-dev \nGet information about the newt tool: $newt\nNewt allows you to create your own embedded application based on the Mynewt\noperating system. Newt provides both build and package managemen
t 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 [ command-name ]\n For help on command-name . 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 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\nFlags:\n -h, --help Help for newt commands\n -j, --jobs int Number of concurrent build jobs (default 4)\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\nUse newt [command] --help for more information ab
out a command.",
+ "text": "The newt Go package is mynewt.apache.org/newt/newt and is stored in the Apache Mynewt newt tool repository mirrored on github . We use the go get command to download the source, build, and install the newt tool binary in the $GOPATH/bin directory. \nDownload the newt package source and install the tool: $cd $GOPATH\n$go get mynewt.apache.org/newt/newt\n$cd $GOPATH/src/mynewt.apache.org/newt\n$ls \nDISCLAIMER RELEASE_NOTES.md util\nINSTALLING.md build.sh viper\nLICENSE newt yaml\nNOTICE newtmgr\nREADME.md newtvm \nCheck that the newt tool is installed and it is in your path: $ls $GOPATH/bin/newt\n~/dev/go/bin/newt\n$which newt\n~/dev/go/bin/newt\n$ newt version\nApache Newt (incubating) version: 1.0.0-dev \nGet information about the newt tool: $newt\nNewt allows you to create your own embedded application based on the Mynewt\noperating system. 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 [ command-name ]\n For help on command-name . 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 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\nFlags:\n -h, --help Help for newt commands\n -j, --jobs int Number of concurrent build jobs (default 4)\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\nUse newt [command] --help for more information about a
command.",
"title": "Step 5: Downloading the Source and Installing the Newt Tool"
},
{
@@ -407,7 +407,7 @@
},
{
"location": "/os/get_started/project_create/",
- "text": "Creating Your First Mynewt Project\n\n\nThis page shows you how to create a Mynewt project using the \nnewt\n command-line tool. The project is a blinky application that toggles a pin. The application uses the Mynewt's simulated hardware and runs as a native application on Mac OS and Linux. \n\n\nNote:\n The Mynewt simulator is not yet supported on Windows. If you are using the native install option (not the Docker option), you will need to create the blinky application for a target board. We recommend that you read the section on creating a new project and fetching the source repository to understand the Mynewt repository structure, create a new project, and fetch the source dependencies before proceeding to one of the \nBlinky Tutorials\n. \n\n\nThis guide shows you how to:\n\n\n\n\nCreate a new project and fetch the source repository and dependecies.\n\n\nTest the project packages (Not supported on Windows).\n\n\nBuild and run the simulated blinky applicatio
n (Not supported on Windows). \n\n\n\n\n\n\nPrerequisites\n\n\n\n\nHave Internet connectivity to fetch remote Mynewt components.\n\n\nInstall the newt tool: \n\n\nIf you have taken the native install option, see the installation instructions for \nMac OS\n, \nLinux\n, or \nWindows\n. \n\n\nIf you have taken the Docker option, you have already installed Newt.\n\n\n\n\n\n\nInstall the \nnative toolchain\n to compile and build a Mynewt native application. \n\n\n\n\n\n\nCreating a New Project and Fetching the Source Repository\n\n\nThis section describes how to use the newt tool to create a new project and fetch the core mynewt source repository.\n\n\n\n\nCreating a New Project\n\n\nChoose a name for your project. We name the project \nmyproj\n. \n\n\n\nRun the \nnewt new myproj\n command, from your \ndev\n directory, to create a new project:\n\n\nNote:\n This tutorial assumes you created a \ndev\n directory under your home directory. \n\n\n$cd ~/dev\n$ newt new myproj\nDownloading pr
oject skeleton from apache/incubator-mynewt-blinky...\nInstalling skeleton in myproj...\nProject myproj successfully created.\n\n\n\n\n\n\n\nThe newt tool creates a project base directory name \nmyproj\n. All newt tool commands are run from the project base directory. The newt tool populates this new project with a base skeleton of a new Apache Mynewt project in the project base directory. It has the following structure: \n\n\nNote\n: If you do not have \ntree\n, run \nbrew install tree\n to install on Mac OS, \nsudo apt-get install tree\n to install on Linux, and \npacman -Su tree\n from a MinGW terminal to install on Windows.\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\u
2500 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 installs the following files for a project in the project base directory:\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 only \ncomprises the core mynewt repository. Later, you will add more repositories to include other mynewt components.\n\n\nThe file \napps/blinky/pkg.yml\n contains the description of your application and its package dependencies.\n\n\nA \ntarget\n directory that contains the \nmy_blinky_sim\n directory. The \nmy_blinky_sim\n directory \na target information
to build 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 (except the template for \nmain.c\n). See the next step to install the packages.\n\n\n\n\nFetching the Mynewt Source Repository and Dependencies\n\n\nBy default, Mynewt projects rely on a single repository: \napache-mynewt-core\n and uses the source in the master branch. If you need to use a different branch, you need to change the \nvers\n value in the project.yml file: \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 vers to 0-dev will put you on the latest master branch. \nThis branch may not be stable and you may encounter bugs or other problems.\n\n\nNote:\n On Windows platforms, you will need to change
vers to 0-dev and use the latest master branch. Release 1.0.0 is not supported on Windows.\n\n\n\nRun the \nnewt install\n command, from your project base directory (myproj), to fetch the source repository and dependencies: \n\n\n$ newt install\napache-mynewt-core\n\n\n\n\n\nNote:\n It may take a while to download the apache-mynewt-core reposistory. Use the \n-v\n (verbose) option to see the installation progress.\n\n\n\n\nView the core of the Apache Mynewt OS that is downloaded into your local directory. \n\n\n(The actual output will depend on what is in the latest 'master' branch)\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 \u
251c\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\u2502\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\u2502\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\u2500\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 \u
251c\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\u2500\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\n\n
\nTesting the Project Packages\n\n\nNote\n: This is not yet supported on Windows.\n\n\nYou can use the newt tool to execute the unit tests in a package. For example, run the following command to test the \nsys/config\n package in the \napache-mynewt-core\n repo: \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_mk
dir.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/apache-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 installed the latest gcc using homebrew on your Mac, you are probably running gcc-6. Make sure you change the compiler.yml configuration to specify that you are using gcc-6 (See \nNative Install Option\n). You can also downgrade your inst
allation to gcc-5 and use the default gcc compiler configuration for MyNewt:\n\n\n$ brew uninstall gcc-6\n$ brew link gcc-5\n\n\n\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 multilib gcc (e.g. gcc-multilib if you running on a 64-bit Ubuntu).\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/my
proj/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\nBuilding and Running the Simulated Blinky Application\n\n\nThe section shows you how to build and run the blinky application to run on Mynewt's simulated hardware.\n\n\nNote\n: This is not yet supported on Windows. Refer to the \nBlinky Tutorials\n to create a blinky application on a target boards.\n\n\n\n\nBuilding the Application\n\n\nTo build the simulated blinky application, run \nnewt build my_blinky_sim\n:\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\nCo
mpiling 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\nRunning the Blinky Application\n\n\nYou can run the simulated version of your project and see the simulated LED blink. \n\n\nIf you natively install the toolchain execute the binary directly:\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\nIf you are using newt 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_bli
nky_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\n\n\nExploring other Mynewt OS Features\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": "Creating Your First Mynewt Project\n\n\nThis page shows you how to create a Mynewt project using the \nnewt\n command-line tool. The project is a blinky application that toggles a pin. The application uses the Mynewt's simulated hardware and runs as a native application on Mac OS and Linux. \n\n\nNote:\n The Mynewt simulator is not yet supported on Windows. If you are using the native install option (not the Docker option), you will need to create the blinky application for a target board. We recommend that you read the section on creating a new project and fetching the source repository to understand the Mynewt repository structure, create a new project, and fetch the source dependencies before proceeding to one of the \nBlinky Tutorials\n. \n\n\nThis guide shows you how to:\n\n\n\n\nCreate a new project and fetch the source repository and dependecies.\n\n\nTest the project packages (Not supported on Windows).\n\n\nBuild and run the simulated blinky applicatio
n (Not supported on Windows). \n\n\n\n\n\n\nPrerequisites\n\n\n\n\nHave Internet connectivity to fetch remote Mynewt components.\n\n\nInstall the newt tool: \n\n\nIf you have taken the native install option, see the installation instructions for \nMac OS\n, \nLinux\n, or \nWindows\n. \n\n\nIf you have taken the Docker option, you have already installed Newt.\n\n\n\n\n\n\nInstall the \nnative toolchain\n to compile and build a Mynewt native application. \n\n\n\n\n\n\nCreating a New Project and Fetching the Source Repository\n\n\nThis section describes how to use the newt tool to create a new project and fetch the core mynewt source repository.\n\n\n\n\nCreating a New Project\n\n\nChoose a name for your project. We name the project \nmyproj\n. \n\n\n\nRun the \nnewt new myproj\n command, from your \ndev\n directory, to create a new project:\n\n\nNote:\n This tutorial assumes you created a \ndev\n directory under your home directory. \n\n\n$cd ~/dev\n$ newt new myproj\nDownloading pr
oject skeleton from apache/incubator-mynewt-blinky...\nInstalling skeleton in myproj...\nProject myproj successfully created.\n\n\n\n\n\n\n\nThe newt tool creates a project base directory name \nmyproj\n. All newt tool commands are run from the project base directory. The newt tool populates this new project with a base skeleton of a new Apache Mynewt project in the project base directory. It has the following structure: \n\n\nNote\n: If you do not have \ntree\n, run \nbrew install tree\n to install on Mac OS, \nsudo apt-get install tree\n to install on Linux, and \npacman -Su tree\n from a MinGW terminal to install on Windows.\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\u
2500 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 installs the following files for a project in the project base directory:\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 only \ncomprises the core mynewt repository. Later, you will add more repositories to include other mynewt components.\n\n\nThe file \napps/blinky/pkg.yml\n contains the description of your application and its package dependencies.\n\n\nA \ntarget\n directory that contains the \nmy_blinky_sim\n directory. The \nmy_blinky_sim\n directory \na target information
to build 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 (except the template for \nmain.c\n). See the next step to install the packages.\n\n\n\n\nFetching the Mynewt Source Repository and Dependencies\n\n\nBy default, Mynewt projects rely on a single repository: \napache-mynewt-core\n and uses the source in the master branch. If you need to use a different branch, you need to change the \nvers\n value in the project.yml file: \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 vers to 0-dev will put you on the latest master branch. \nThis branch may not be stable and you may encounter bugs or other problems.\n\n\nNote:\n On Windows platforms, you will need to change
vers to 0-dev and use the latest master branch. Release 1.0.0 is not supported on Windows.\n\n\n\nRun the \nnewt install\n command, from your project base directory (myproj), to fetch the source repository and dependencies: \n\n\n$ newt install\napache-mynewt-core\n\n\n\n\n\nNote:\n It may take a while to download the apache-mynewt-core reposistory. Use the \n-v\n (verbose) option to see the installation progress.\n\n\n\n\nView the core of the Apache Mynewt OS that is downloaded into your local directory. \n\n\n(The actual output will depend on what is in the latest 'master' branch)\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 \u
251c\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\u2502\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\u2502\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\u2500\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 \u
251c\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\u2500\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\n\n
\nTesting the Project Packages\n\n\nNote\n: This is not yet supported on Windows.\n\n\nYou can use the newt tool to execute the unit tests in a package. For example, run the following command to test the \nsys/config\n package in the \napache-mynewt-core\n repo: \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_mk
dir.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/apache-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 installed the latest gcc using homebrew on your Mac, you are probably running gcc-6. Make sure you change the compiler.yml configuration to specify that you are using gcc-6 (See \nNative Install Option\n). You can also downgrade your inst
allation to gcc-5 and use the default gcc compiler configuration for MyNewt:\n\n\n$ brew uninstall gcc-6\n$ brew link gcc-5\n\n\n\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 multilib gcc (e.g. gcc-multilib if you running on a 64-bit Ubuntu).\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/my
proj/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\nBuilding and Running the Simulated Blinky Application\n\n\nThe section shows you how to build and run the blinky application to run on Mynewt's simulated hardware.\n\n\nNote\n: This is not yet supported on Windows. Refer to the \nBlinky Tutorials\n to create a blinky application for a target board.\n\n\n\n\nBuilding the Application\n\n\nTo build the simulated blinky application, run \nnewt build my_blinky_sim\n:\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\nCo
mpiling 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\nRunning the Blinky Application\n\n\nYou can run the simulated version of your project and see the simulated LED blink. \n\n\nIf you natively install the toolchain execute the binary directly:\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\nIf you are using newt 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_bli
nky_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\n\n\nExploring other Mynewt OS Features\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!",
"title": "Create Your First Project"
},
{
@@ -442,7 +442,7 @@
},
{
"location": "/os/get_started/project_create/#building-and-running-the-simulated-blinky-application",
- "text": "The section shows you how to build and run the blinky application to run on Mynewt's simulated hardware. Note : This is not yet supported on Windows. Refer to the Blinky Tutorials to create a blinky application on a target boards.",
+ "text": "The section shows you how to build and run the blinky application to run on Mynewt's simulated hardware. Note : This is not yet supported on Windows. Refer to the Blinky Tutorials to create a blinky application for a target board.",
"title": "Building and Running the Simulated Blinky Application"
},
{
@@ -582,7 +582,7 @@
},
{
"location": "/os/tutorials/arduino_zero/",
- "text": "Blinky, your \"Hello World!\", on Arduino Zero\n\n\nThis tutorial shows you how to create, build and run the Blinky application on an Arduino Zero board.\n\n\nPrerequisites\n\n\n\n\nMeet the prerequisites listed in \nProject Blinky\n.\n\n\nHave an Arduino Zero board.\n\nNote: 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.\n\n\nInstall the \nOpenOCD debugger\n.\n\n\n\n\nThis 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.\n\n\n\n\n\n\n\n\nMynewt has not been tested on Arduino M0 which has no internal debugger support.\n\n\n\n\nCreate a Project\n\n\nCreate a new project if you do not have an existing one. You can skip this step and proceed to \nfetch external packages\n if you already created a project. \n\n\nRun the following commands to create a new projec
t: \n\n\n $ mkdir ~/dev\n $ cd ~/dev\n $ newt new myproj\n Downloading project skeleton from apache/incubator-mynewt-blinky...\n Installing skeleton in myproj...\n Project myproj successfully created.\n $ cd myproj\n $ newt install\n apache-mynewt-core\n $\n\n\n\n\n\n\n\n Fetch External Packages\n\n\nMynewt uses source code provided directly from the chip manufacturer for\nlow level operations. Sometimes this code is licensed only for the specific manufacturer of the chipset and cannot live in the Apache Mynewt repository. That happens to be the case for the Arduino Zero board which uses Atmel SAMD21. Runtime's github repository hosts such external third-party packages and the newt tool can fetch them.\n\n\nTo fetch the package with MCU support for Atmel SAMD21 for Arduino Zero from the Runtime git repository, you need to add\nthe repository to the \nproject.yml\n file in your base project directory.\n\n\nHere is an example \nproject.yml\n file with the
Arduino Zero repository\nadded. The sections with \nmynewt_arduino_zero\n that need to be added to\nyour project file are highlighted.\n\n\n$ more project.yml\nproject.name: \nmy_project\n\n\nproject.repositories:\n - apache-mynewt-core\n\n - mynewt_arduino_zero\n\n\nrepository.apache-mynewt-core:\n type: github\n vers: 1-latest\n user: apache\n repo: incubator-mynewt-core\n\n\nrepository.mynewt_arduino_zero:\n\n type: github\n\n vers: 1-latest\n\n user: runtimeco\n\n repo: mynewt_arduino_zero\n\n$\n\n\n\n\n\n\nInstall the project dependencies using the \nnewt install\n command (you can specify \n-v\n for verbose output):\n\n\n$ newt install\napache-mynewt-core\nmynewt_arduino_zero\n$\n\n\n\n\n\n\n\nNOTE:\n If there has been a new release of a repo used in your project since you last installed it, the \n1-latest\n version for the repo in the \nproject.yml\n file will refer to the new release and will not match the installed files. In that case you will
get an error message saying so and you will need to run \nnewt upgrade\n to overwrite the existing files with the latest codebase.\n\n\n\nYou need to create two targets for the Arduino Zero Pro board, one for the bootloader and one for the Blinky application.\n\n\n\nRun the following \nnewt target\n commands, from your project directory, to create a bootloader target. We name the target \narduino_boot\n.\n\n\n$ newt target create arduino_boot\n$ newt target set arduino_boot bsp=@mynewt_arduino_zero/hw/bsp/arduino_zero\nTarget targets/arduino_boot successfully created\n$ newt target set arduino_boot app=@apache-mynewt-core/apps/boot\nTarget targets/arduino_boot successfully set target.app to @apache-mynewt-core/apps/boot\n$ newt target set arduino_boot build_profile=optimized\nTarget targets/arduino_boot successfully set target.build_profile to optimized\n$ newt target set arduino_boot syscfg=BSP_ARDUINO_ZERO_PRO=1\nTarget targets/arduino_boot successfully set target.syscfg to BSP_
ARDUINO_ZERO_PRO=1\n$\n\n\n\n\n\nNote:\n If you have an Arduino Zero instead of an Arduino Zero Pro or Arduino M0 Pro board, replace \nBSP_ARDUINO_ZERO_PRO\n with \nBSP_ARDUINO_ZERO\n in the last \nnewt target set\n command.\n\n\nThese commands perform the following:\n\n\n\n\nCreate a target named \narduino_boot\n for the Arduino Zero Bootloader. \n\n\nSet the application for the \narduino_boot\n target to the default Apache Mynewt\n bootloader (\n@apache-mynewt-core/apps/boot\n)\n\n\nSet the board support package for the target to\n \n@mynewt_arduino_zero/hw/bsp/arduino_zero\n. This is a reference to the downloaded\n Arduino Zero support from Github.\n\n\nUse the \"optimized\" build profile for the \narduino_boot\n target. This\n instructs Newt to generate smaller and more efficient code for this target.\n This setting is necessary due to the bootloader's strict size constraints.\n\n\nSets the system configuration setting for Board Support Package to support the
Arduino Zero Pro. \n\n\n\n\nSee the \nConcepts\n section for more information on setting options.\n\n\n\nCreate a Target for the Blinky Application\n\n\nRun the following \nnewt target\n commands to create the Blinky application target. We name the application target \narduino_blinky\n.\n\n\n$ newt target create arduino_blinky\nTarget targets/arduino_blinky successfully created\n$ newt target set arduino_blinky app=apps/blinky\nTarget targets/arduino_blinky successfully set target.app to apps/blinky\n$ newt target set arduino_blinky bsp=@mynewt_arduino_zero/hw/bsp/arduino_zero\nTarget targets/arduino_blinky successfully set target.bsp to @mynewt_arduino_zero/hw/bsp/arduino_zero\n$ newt target set arduino_blinky build_profile=debug\nTarget targets/arduino_blinky successfully set target.build_profile to debug\n$ newt target set arduino_blinky syscfg=BSP_ARDUINO_ZERO_PRO=1\nTarget targets/arduino_boot successfully set target.syscfg to BSP_ARDUINO_ZERO_PRO=1\n$\n\n\n\n\n\nNote:\n If yo
u have an Arduino Zero instead of a Arduino Zero Pro board, replace \nBSP_ARDUINO_ZERO_PRO\n with \nBSP_ARDUINO_ZERO\n in the last \nnewt target set\n command.\n\n\n\n\nBuild the Bootloader\n\n\nRun the \nnewt build arduino_boot\n command to build the bootloader:\n\n\n$ newt build arduino_boot\nBuilding target targets/arduino_boot\nCompiling bin/targets/arduino_boot/generated/src/arduino_boot-sysinit-app.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/image_rsa.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/image_ec.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/image_ec256.c\nCompiling bin/targets/arduino_boot/generated/src/arduino_boot-sysflash.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/image_validate.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/bootutil_misc.c\nCompiling repos/apache-mynewt-core/apps/boot/src/boot.c\nCompiling repos/apache-mynewt-core/crypto/mbedtls/src/arc4.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src
/loader.c\nCompiling repos/apache-mynewt-core/crypto/mbedtls/src/aes.c\n\n ....\n\nArchiving sys_mfg.a\nArchiving sys_sysinit.a\nArchiving util_mem.a\nLinking ~/dev/myproj/bin/targets/arduino_boot/app/apps/boot/boot.elf\nTarget successfully built: targets/arduino_boot\n\n\n\n\n\n\n\nBuild the Blinky Application\n\n\nRun the \nnewt build arduino_blinky\n command to build the Blinky application image:\n\n\n$ newt build arduino_blinky\nBuilding target targets/arduino_blinky\nCompiling repos/apache-mynewt-core/hw/hal/src/hal_flash.c\nCompiling apps/blinky/src/main.c\nCompiling repos/mynewt_arduino_zero/hw/mcu/atmel/samd21xx/src/sam0/drivers/i2s/i2s.c\nCompiling repos/mynewt_arduino_zero/hw/bsp/arduino_zero/src/hal_bsp.c\nCompiling repos/mynewt_arduino_zero/hw/mcu/atmel/samd21xx/src/sam0/drivers/i2s/i2s_callback.c\nCompiling repos/mynewt_arduino_zero/hw/mcu/atmel/samd21xx/src/sam0/drivers/nvm/nvm.c\n\n ...\n\nArchiving sys_mfg.a\nArchiving sys_sysinit.a\nArchiving util_mem.a\nLi
nking ~/dev/myproj/bin/targets/arduino_blinky/app/apps/blinky/blinky.elf\nTarget successfully built: targets/arduino_blinky\n\n\n\n\n\n\n\nConnect to the Board\n\n\nConnect your computer to the Arduino Zero (from now on we'll call this the\ntarget) with a Micro-USB cable through the Programming Port as shown below.\nMynewt will load the image onto the board and debug the target through this port. You should see a\ngreen LED come on that indicates the board has power.\n\n\nNo external debugger is required. The Arduino Zero comes with an internal\ndebugger that can be accessed by Mynewt.\n\n\nThe images below show the Arduino Zero Programming Port.\n\n\n\n\n\n\n\n\nLoad the Bootloader onto the Board\n\n\nRun the \nnewt load arduino_boot\n command to load the bootloader onto the board:\n\n\n$ newt load arduino_boot\nLoading bootloader\n$\n\n\n\n\n\nThe bootloader is loaded onto your board succesfully when the \nnewt load\n command returns to the command prompt after the \nLoading boo
tloader\n status message. You can proceed to load and run your Blinky application image (See \nRun the Blinky Application\n).\n\n\nIf the \nnewt load\n command outputs the following error messages, you will need to erase the board.\n\n\n$ newt load arduino_boot -v\nLoading bootloader\nError: Downloading ~/dev/myproj/bin/targets/arduino_boot/app/apps/boot/boot.elf.bin to 0x0\nOpen On-Chip Debugger 0.9.0 (2015-11-15-05:39)\nLicensed under GNU GPL v2\nFor bug reports, read\n http://openocd.org/doc/doxygen/bugs.html\nInfo : only one transport option; autoselect \nswd\n\nadapter speed: 500 kHz\nadapter_nsrst_delay: 100\ncortex_m reset_config sysresetreq\nInfo : CMSIS-DAP: SWD Supported\nInfo : CMSIS-DAP: JTAG Supported\nInfo : CMSIS-DAP: Interface Initialised (SWD)\nInfo : CMSIS-DAP: FW Version = 01.1F.0118\nInfo : SWCLK/TCK = 1 SWDIO/TMS = 1 TDI = 1 TDO = 1 nTRST = 0 nRESET = 1\nInfo : CMSIS-DAP: Interface ready\nInfo : clock speed 500 kHz\nInfo : SWD IDCODE 0x0bc11477\nInfo : at91
samd21g18.cpu: hardware has 4 breakpoints, 2 watchpoints\nError: Target not halted\n\n\n\n\n\n\nTo erase your board, start a debug session and enter the highlighted commands at the \n(gdb)\n prompts:\n\n\nNote:\n On Windows, openocd and gdb are started in separate Windows Command Prompt terminals, and the terminals are automatically closed when you quit gdb. In addition, the output of openocd is logged to the openocd.log file in your project's base directory instead of the terminal.\n\n\n$ newt debug arduino_blinky\n(gdb) mon at91samd chip-erase\nchip erased\nchip erased\n(gdb) x/32wx 0\n0x0: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n0x10: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n0x20: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n0x30: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n0x40: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n0x50: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n0x60: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n0x70: 0
xffffffff 0xffffffff 0xffffffff 0xffffffff\n(gdb) q\n\n\n\n\n\n\nRun the \nnewt load arduino_boot\n command again after erasing the board. \n\n\n Reminder if you are using Docker: \n When working with actual hardware, remember that each board has an ID. If you swap boards and do not refresh the USB Device Filter on the VirtualBox UI, the ID might be stale and the Docker instance may not be able to see the board correctly. For example, you may see an error message like \nError: unable to find CMSIS-DAP device\n when you try to load or run an image on the board. In that case, you need to click on the USB link in VirtualBox UI, remove the existing USB Device Filter (e.g. \"Atmel Corp. EDBG CMSIS-DAP[0101]\") by clicking on the \"Removes selected USB filter\" button, and add a new filter by clicking on the \"Adds new USB filter\" button.\n\n\n\n\nRun the Blinky Application\n\n\nAfter you load the bootloader successfully onto your board, you can load and run the Blinky application. \n
\n\nRun the \nnewt run arduino_blinky 1.0.0\n command to build the arduino_blinky target (if necessary), create an image with version 1.0.0, load the image onto the board, and start a debugger session. \n\n\nNote\n The output of the debug session below is for Mac OS and Linux platforms. On Windows, openocd and gdb are started in separate Windows Command Prompt terminals. The output of openocd is logged to the openocd.log file in your project's base directory and not to the terminal. The openocd and gdb terminals will close automatically when you quit gdb. \n\n\n\n$ newt run arduino_blinky 1.0.0\nApp image succesfully generated: ~/dev/myproj/bin/targets/arduino_blinky/app/apps/blinky/blinky.img\nLoading app image into slot 1\n[~/dev/myproj/repos/mynewt_arduino_zero/hw/bsp/arduino_zero/arduino_zero_debug.sh ~/dev/myproj/repos/mynewt_arduino_zero/hw/bsp/arduino_zero ~/dev/myproj/bin/targets/arduino_blinky/app/apps/blinky/blinky]\nOpen On-Chip Debugger 0.9.0 (2015-11-15-13:10)\nLicense
d under GNU GPL v2\nFor bug reports, read\nhttp://openocd.org/doc/doxygen/bugs.html\nInfo : only one transport option; autoselect \nswd\n\nadapter speed: 500 kHz\nadapter_nsrst_delay: 100\ncortex_m reset_config sysresetreq\nInfo : CMSIS-DAP: SWD Supported\nInfo : CMSIS-DAP: JTAG Supported\nInfo : CMSIS-DAP: Interface Initialised (SWD)\nInfo : CMSIS-DAP: FW Version = 01.1F.0118\nInfo : SWCLK/TCK = 1 SWDIO/TMS = 1 TDI = 1 TDO = 1 nTRST = 0 nRESET = 1\nInfo : CMSIS-DAP: Interface ready\nInfo : clock speed 500 kHz\nInfo : SWD IDCODE 0x0bc11477\nInfo : at91samd21g18.cpu: hardware has 4 breakpoints, 2 watchpoints\ntarget state: halted\ntarget halted due to debug-request, current mode: Thread \nxPSR: 0x21000000 pc: 0x0000fca6 psp: 0x20002408\nGNU gdb (GNU Tools for ARM Embedded Processors) 7.8.0.20150604-cvs\nCopyright (C) 2014 Free Software Foundation, Inc.\nLicense GPLv3+: GNU GPL version 3 or later \nhttp://gnu.org/licenses/gpl.html\n\nThis is free software: you are free to change and
redistribute it.\nThere is NO WARRANTY, to the extent permitted by law. Type \nshow copying\n\nand \nshow warranty\n for details.\nThis GDB was configured as \n--host=x86_64-apple-darwin10 --target=arm-none-eabi\n.\nType \nshow configuration\n for configuration details.\nFor bug reporting instructions, please see:\n\nhttp://www.gnu.org/software/gdb/bugs/\n.\nFind the GDB manual and other documentation resources online at:\n\nhttp://www.gnu.org/software/gdb/documentation/\n.\nFor help, type \nhelp\n.\nType \napropos word\n to search for commands related to \nword\n...\nReading symbols from ~/dev/myproj/bin/targets/arduino_blinky/app/apps/blinky/blinky.elf...(no debugging symbols found)...done.\nInfo : accepting \ngdb\n connection on tcp/3333\nInfo : SAMD MCU: SAMD21G18A (256KB Flash, 32KB RAM)\n0x0000fca6 in os_tick_idle ()\ntarget state: halted\ntarget halted due to debug-request, current mode: Thread \nxPSR: 0x21000000 pc: 0x000000b8 msp: 0x20008000\ntarget state: halted\ntarget h
alted due to debug-request, current mode: Thread \nxPSR: 0x21000000 pc: 0x000000b8 msp: 0x20008000\n(gdb) r\nThe \nremote\n target does not support \nrun\n. Try \nhelp target\n or \ncontinue\n.\n(gdb) c\nContinuing.\n\n\n\n\n\n\n\nNOTE:\n The 1.0.0 is the version number to assign to the image. You may assign an arbitrary version number. If you are not providing remote upgrade, and are just developing locally, you can provide 1.0.0 for every image version.\n\n\nIf you want the image to run without the debugger connected, simply quit the\ndebugger and restart the board. The image you programmed will come up and run on \nthe Arduino on the next boot! \n\n\n\nYou should see the LED blink!",
+ "text": "Blinky, your \"Hello World!\", on Arduino Zero\n\n\nThis tutorial shows you how to create, build and run the Blinky application on an Arduino Zero board.\n\n\nPrerequisites\n\n\n\n\nMeet the prerequisites listed in \nProject Blinky\n.\n\n\nHave an Arduino Zero board.\n\nNote: 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.\n\n\nInstall the \nOpenOCD debugger\n.\n\n\n\n\nThis 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.\n\n\n\n\n\n\n\n\nMynewt has not been tested on Arduino M0 which has no internal debugger support.\n\n\n\n\nCreate a Project\n\n\nCreate a new project if you do not have an existing one. You can skip this step and proceed to \nfetch external packages\n if you already created a project. \n\n\nRun the following commands to create a new projec
t: \n\n\n $ mkdir ~/dev\n $ cd ~/dev\n $ newt new myproj\n Downloading project skeleton from apache/incubator-mynewt-blinky...\n Installing skeleton in myproj...\n Project myproj successfully created.\n $ cd myproj\n $ newt install\n apache-mynewt-core\n $\n\n\n\n\n\n\n\n Fetch External Packages\n\n\nMynewt uses source code provided directly from the chip manufacturer for\nlow level operations. Sometimes this code is licensed only for the specific manufacturer of the chipset and cannot live in the Apache Mynewt repository. That happens to be the case for the Arduino Zero board which uses Atmel SAMD21. Runtime's github repository hosts such external third-party packages and the newt tool can fetch them.\n\n\nTo fetch the package with MCU support for Atmel SAMD21 for Arduino Zero from the Runtime git repository, you need to add\nthe repository to the \nproject.yml\n file in your base project directory.\n\n\nHere is an example \nproject.yml\n file with the
Arduino Zero repository\nadded. The sections with \nmynewt_arduino_zero\n that need to be added to\nyour project file are highlighted.\n\n\nNote:\n On Windows platforms: You need to set \nvers\n to \n0-dev\n and use the latest master branch for both repositories.\n\n\n$ more project.yml\nproject.name: \nmy_project\n\n\nproject.repositories:\n - apache-mynewt-core\n\n - mynewt_arduino_zero\n\n\nrepository.apache-mynewt-core:\n type: github\n vers: 1-latest\n user: apache\n repo: incubator-mynewt-core\n\n\nrepository.mynewt_arduino_zero:\n\n type: github\n\n vers: 1-latest\n\n user: runtimeco\n\n repo: mynewt_arduino_zero\n\n$\n\n\n\n\n\n\nInstall the project dependencies using the \nnewt install\n command (you can specify \n-v\n for verbose output):\n\n\n$ newt install\napache-mynewt-core\nmynewt_arduino_zero\n$\n\n\n\n\n\n\n\nNOTE:\n If there has been a new release of a repo used in your project since you last installed it, the \n1-latest\n version for
the repo in the \nproject.yml\n file will refer to the new release and will not match the installed files. In that case you will get an error message saying so and you will need to run \nnewt upgrade\n to overwrite the existing files with the latest codebase.\n\n\n\nYou need to create two targets for the Arduino Zero Pro board, one for the bootloader and one for the Blinky application.\n\n\n\nRun the following \nnewt target\n commands, from your project directory, to create a bootloader target. We name the target \narduino_boot\n.\n\n\n$ newt target create arduino_boot\n$ newt target set arduino_boot bsp=@mynewt_arduino_zero/hw/bsp/arduino_zero\nTarget targets/arduino_boot successfully created\n$ newt target set arduino_boot app=@apache-mynewt-core/apps/boot\nTarget targets/arduino_boot successfully set target.app to @apache-mynewt-core/apps/boot\n$ newt target set arduino_boot build_profile=optimized\nTarget targets/arduino_boot successfully set target.build_profile to optimized\
n$ newt target set arduino_boot syscfg=BSP_ARDUINO_ZERO_PRO=1\nTarget targets/arduino_boot successfully set target.syscfg to BSP_ARDUINO_ZERO_PRO=1\n$\n\n\n\n\n\nNote:\n If you have an Arduino Zero instead of an Arduino Zero Pro or Arduino M0 Pro board, replace \nBSP_ARDUINO_ZERO_PRO\n with \nBSP_ARDUINO_ZERO\n in the last \nnewt target set\n command.\n\n\nThese commands perform the following:\n\n\n\n\nCreate a target named \narduino_boot\n for the Arduino Zero Bootloader. \n\n\nSet the application for the \narduino_boot\n target to the default Apache Mynewt\n bootloader (\n@apache-mynewt-core/apps/boot\n)\n\n\nSet the board support package for the target to\n \n@mynewt_arduino_zero/hw/bsp/arduino_zero\n. This is a reference to the downloaded\n Arduino Zero support from Github.\n\n\nUse the \"optimized\" build profile for the \narduino_boot\n target. This\n instructs Newt to generate smaller and more efficient code for this target.\n This setting is necessary due
to the bootloader's strict size constraints.\n\n\nSets the system configuration setting for Board Support Package to support the Arduino Zero Pro. \n\n\n\n\nSee the \nConcepts\n section for more information on setting options.\n\n\n\nCreate a Target for the Blinky Application\n\n\nRun the following \nnewt target\n commands to create the Blinky application target. We name the application target \narduino_blinky\n.\n\n\n$ newt target create arduino_blinky\nTarget targets/arduino_blinky successfully created\n$ newt target set arduino_blinky app=apps/blinky\nTarget targets/arduino_blinky successfully set target.app to apps/blinky\n$ newt target set arduino_blinky bsp=@mynewt_arduino_zero/hw/bsp/arduino_zero\nTarget targets/arduino_blinky successfully set target.bsp to @mynewt_arduino_zero/hw/bsp/arduino_zero\n$ newt target set arduino_blinky build_profile=debug\nTarget targets/arduino_blinky successfully set target.build_profile to debug\n$ newt target set arduino_blinky syscfg=BSP_ARD
UINO_ZERO_PRO=1\nTarget targets/arduino_boot successfully set target.syscfg to BSP_ARDUINO_ZERO_PRO=1\n$\n\n\n\n\n\nNote:\n If you have an Arduino Zero instead of a Arduino Zero Pro board, replace \nBSP_ARDUINO_ZERO_PRO\n with \nBSP_ARDUINO_ZERO\n in the last \nnewt target set\n command.\n\n\n\n\nBuild the Bootloader\n\n\nRun the \nnewt build arduino_boot\n command to build the bootloader:\n\n\n$ newt build arduino_boot\nBuilding target targets/arduino_boot\nCompiling bin/targets/arduino_boot/generated/src/arduino_boot-sysinit-app.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/image_rsa.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/image_ec.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/image_ec256.c\nCompiling bin/targets/arduino_boot/generated/src/arduino_boot-sysflash.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/image_validate.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/bootutil_misc.c\nCompiling repos/apache-mynewt-core/apps/bo
ot/src/boot.c\nCompiling repos/apache-mynewt-core/crypto/mbedtls/src/arc4.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/loader.c\nCompiling repos/apache-mynewt-core/crypto/mbedtls/src/aes.c\n\n ....\n\nArchiving sys_mfg.a\nArchiving sys_sysinit.a\nArchiving util_mem.a\nLinking ~/dev/myproj/bin/targets/arduino_boot/app/apps/boot/boot.elf\nTarget successfully built: targets/arduino_boot\n\n\n\n\n\n\n\nBuild the Blinky Application\n\n\nRun the \nnewt build arduino_blinky\n command to build the Blinky application image:\n\n\n$ newt build arduino_blinky\nBuilding target targets/arduino_blinky\nCompiling repos/apache-mynewt-core/hw/hal/src/hal_flash.c\nCompiling apps/blinky/src/main.c\nCompiling repos/mynewt_arduino_zero/hw/mcu/atmel/samd21xx/src/sam0/drivers/i2s/i2s.c\nCompiling repos/mynewt_arduino_zero/hw/bsp/arduino_zero/src/hal_bsp.c\nCompiling repos/mynewt_arduino_zero/hw/mcu/atmel/samd21xx/src/sam0/drivers/i2s/i2s_callback.c\nCompiling repos/mynewt_arduino_zero/hw/mc
u/atmel/samd21xx/src/sam0/drivers/nvm/nvm.c\n\n ...\n\nArchiving sys_mfg.a\nArchiving sys_sysinit.a\nArchiving util_mem.a\nLinking ~/dev/myproj/bin/targets/arduino_blinky/app/apps/blinky/blinky.elf\nTarget successfully built: targets/arduino_blinky\n\n\n\n\n\n\n\nConnect to the Board\n\n\nConnect your computer to the Arduino Zero (from now on we'll call this the\ntarget) with a Micro-USB cable through the Programming Port as shown below.\nMynewt will load the image onto the board and debug the target through this port. You should see a\ngreen LED come on that indicates the board has power.\n\n\nNo external debugger is required. The Arduino Zero comes with an internal\ndebugger that can be accessed by Mynewt.\n\n\nThe images below show the Arduino Zero Programming Port.\n\n\n\n\n\n\n\n\nLoad the Bootloader onto the Board\n\n\nRun the \nnewt load arduino_boot\n command to load the bootloader onto the board:\n\n\n$ newt load arduino_boot\nLoading bootloader\n$\n\n\n\n\n\nThe boot
loader is loaded onto your board succesfully when the \nnewt load\n command returns to the command prompt after the \nLoading bootloader\n status message. You can proceed to load and run your Blinky application image (See \nRun the Blinky Application\n).\n\n\nIf the \nnewt load\n command outputs the following error messages, you will need to erase the board.\n\n\n$ newt load arduino_boot -v\nLoading bootloader\nError: Downloading ~/dev/myproj/bin/targets/arduino_boot/app/apps/boot/boot.elf.bin to 0x0\nOpen On-Chip Debugger 0.9.0 (2015-11-15-05:39)\nLicensed under GNU GPL v2\nFor bug reports, read\n http://openocd.org/doc/doxygen/bugs.html\nInfo : only one transport option; autoselect \nswd\n\nadapter speed: 500 kHz\nadapter_nsrst_delay: 100\ncortex_m reset_config sysresetreq\nInfo : CMSIS-DAP: SWD Supported\nInfo : CMSIS-DAP: JTAG Supported\nInfo : CMSIS-DAP: Interface Initialised (SWD)\nInfo : CMSIS-DAP: FW Version = 01.1F.0118\nInfo : SWCLK/TCK = 1 SWDIO/TMS = 1 TDI = 1 TDO =
1 nTRST = 0 nRESET = 1\nInfo : CMSIS-DAP: Interface ready\nInfo : clock speed 500 kHz\nInfo : SWD IDCODE 0x0bc11477\nInfo : at91samd21g18.cpu: hardware has 4 breakpoints, 2 watchpoints\nError: Target not halted\n\n\n\n\n\n\nTo erase your board, start a debug session and enter the highlighted commands at the \n(gdb)\n prompts:\n\n\nNote:\n On Windows, openocd and gdb are started in separate Windows Command Prompt terminals, and the terminals are automatically closed when you quit gdb. In addition, the output of openocd is logged to the openocd.log file in your project's base directory instead of the terminal.\n\n\n$ newt debug arduino_blinky\n(gdb) mon at91samd chip-erase\nchip erased\nchip erased\n(gdb) x/32wx 0\n0x0: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n0x10: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n0x20: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n0x30: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n0x40: 0xffffffff 0xffffffff 0xffffffff 0xff
ffffff\n0x50: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n0x60: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n0x70: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n(gdb) q\n\n\n\n\n\n\nRun the \nnewt load arduino_boot\n command again after erasing the board. \n\n\n Reminder if you are using Docker: \n When working with actual hardware, remember that each board has an ID. If you swap boards and do not refresh the USB Device Filter on the VirtualBox UI, the ID might be stale and the Docker instance may not be able to see the board correctly. For example, you may see an error message like \nError: unable to find CMSIS-DAP device\n when you try to load or run an image on the board. In that case, you need to click on the USB link in VirtualBox UI, remove the existing USB Device Filter (e.g. \"Atmel Corp. EDBG CMSIS-DAP[0101]\") by clicking on the \"Removes selected USB filter\" button, and add a new filter by clicking on the \"Adds new USB filter\" button.\n\n\n\n\nRun the Bl
inky Application\n\n\nAfter you load the bootloader successfully onto your board, you can load and run the Blinky application. \n\n\nRun the \nnewt run arduino_blinky 1.0.0\n command to build the arduino_blinky target (if necessary), create an image with version 1.0.0, load the image onto the board, and start a debugger session. \n\n\nNote\n The output of the debug session below is for Mac OS and Linux platforms. On Windows, openocd and gdb are started in separate Windows Command Prompt terminals. The output of openocd is logged to the openocd.log file in your project's base directory and not to the terminal. The openocd and gdb terminals will close automatically when you quit gdb. \n\n\n\n$ newt run arduino_blinky 1.0.0\nApp image succesfully generated: ~/dev/myproj/bin/targets/arduino_blinky/app/apps/blinky/blinky.img\nLoading app image into slot 1\n[~/dev/myproj/repos/mynewt_arduino_zero/hw/bsp/arduino_zero/arduino_zero_debug.sh ~/dev/myproj/repos/mynewt_arduino_zero/hw/bsp/ardu
ino_zero ~/dev/myproj/bin/targets/arduino_blinky/app/apps/blinky/blinky]\nOpen On-Chip Debugger 0.9.0 (2015-11-15-13:10)\nLicensed under GNU GPL v2\nFor bug reports, read\nhttp://openocd.org/doc/doxygen/bugs.html\nInfo : only one transport option; autoselect \nswd\n\nadapter speed: 500 kHz\nadapter_nsrst_delay: 100\ncortex_m reset_config sysresetreq\nInfo : CMSIS-DAP: SWD Supported\nInfo : CMSIS-DAP: JTAG Supported\nInfo : CMSIS-DAP: Interface Initialised (SWD)\nInfo : CMSIS-DAP: FW Version = 01.1F.0118\nInfo : SWCLK/TCK = 1 SWDIO/TMS = 1 TDI = 1 TDO = 1 nTRST = 0 nRESET = 1\nInfo : CMSIS-DAP: Interface ready\nInfo : clock speed 500 kHz\nInfo : SWD IDCODE 0x0bc11477\nInfo : at91samd21g18.cpu: hardware has 4 breakpoints, 2 watchpoints\ntarget state: halted\ntarget halted due to debug-request, current mode: Thread \nxPSR: 0x21000000 pc: 0x0000fca6 psp: 0x20002408\nGNU gdb (GNU Tools for ARM Embedded Processors) 7.8.0.20150604-cvs\nCopyright (C) 2014 Free Software Foundation, Inc.\nLi
cense GPLv3+: GNU GPL version 3 or later \nhttp://gnu.org/licenses/gpl.html\n\nThis is free software: you are free to change and redistribute it.\nThere is NO WARRANTY, to the extent permitted by law. Type \nshow copying\n\nand \nshow warranty\n for details.\nThis GDB was configured as \n--host=x86_64-apple-darwin10 --target=arm-none-eabi\n.\nType \nshow configuration\n for configuration details.\nFor bug reporting instructions, please see:\n\nhttp://www.gnu.org/software/gdb/bugs/\n.\nFind the GDB manual and other documentation resources online at:\n\nhttp://www.gnu.org/software/gdb/documentation/\n.\nFor help, type \nhelp\n.\nType \napropos word\n to search for commands related to \nword\n...\nReading symbols from ~/dev/myproj/bin/targets/arduino_blinky/app/apps/blinky/blinky.elf...(no debugging symbols found)...done.\nInfo : accepting \ngdb\n connection on tcp/3333\nInfo : SAMD MCU: SAMD21G18A (256KB Flash, 32KB RAM)\n0x0000fca6 in os_tick_idle ()\ntarget state: halted\ntarget ha
lted due to debug-request, current mode: Thread \nxPSR: 0x21000000 pc: 0x000000b8 msp: 0x20008000\ntarget state: halted\ntarget halted due to debug-request, current mode: Thread \nxPSR: 0x21000000 pc: 0x000000b8 msp: 0x20008000\n(gdb) r\nThe \nremote\n target does not support \nrun\n. Try \nhelp target\n or \ncontinue\n.\n(gdb) c\nContinuing.\n\n\n\n\n\n\n\nNOTE:\n The 1.0.0 is the version number to assign to the image. You may assign an arbitrary version number. If you are not providing remote upgrade, and are just developing locally, you can provide 1.0.0 for every image version.\n\n\nIf you want the image to run without the debugger connected, simply quit the\ndebugger and restart the board. The image you programmed will come up and run on \nthe Arduino on the next boot! \n\n\n\nYou should see the LED blink!",
"title": "Blinky on Arduino Zero"
},
{
@@ -627,7 +627,7 @@
},
{
"location": "/os/tutorials/blinky_primo/",
- "text": "Blinky, your \"Hello World!\", on Arduino Primo\n\n\nThis tutorial shows you how to create, build, and run the Blinky application on an Arduino Primo board.\n\n\nNote that the Mynewt OS will run on the nRF52 chip in the Arduino Primo board. However, the board support package for the Arduino Primo is different from the nRF52 dev kit board support package.\n\n\n\nPrerequisites\n\n\n\n\nMeet the the prerequisites listed in \nProject Blinky\n.\n\n\nHave an Arduino Primo board.\n\n\nInstall a debugger. Choose one of the two options below: Option 1 requires additional hardware but very easy to set up. \n\n\n\n\n\n\nOption 1\n\n\n\n\nSegger J-Link Debug Probe\n - any model (this tutorial has been tested with J-Link EDU and J-Link Pro)\n\n\nJ-Link 9 pin Cortex-M Adapter\n that allows JTAG, SWD and SWO connections between J-Link and Cortex M based target hardware systems\n\n\nInstall the \nSegger JLINK Software and documentation pack\n. \n\n\n\n\nOption 2\n\n\nThis boa
rd requires a patch version of OpenOCD 0.10.0 that is in development. See \nInstall OpenOCD\n instructions to install it if you do not have this version installed.\n\n\nYou can now use openocd to upload to Arduino Primo board via the USB port itself.\n\n\nCreate a Project\n\n\nCreate a new project if you do not have an existing one. You can skip this step and proceed to \ncreate the targets\n if you already created a project.\n\n\nRun the following commands to create a new project:\n\n\n $ mkdir ~/dev\n $ cd ~/dev\n $ newt new myproj\n Downloading project skeleton from apache/incubator-mynewt-blinky...\n Installing skeleton in myproj...\n Project myproj successfully created.\n $ cd myproj\n $ newt install\n apache-mynewt-core\n $\n\n\n\n\n\n\n\nCreate the Targets\n\n\nCreate two targets for the Arduino Primo board - one for the bootloader and one for the Blinky application.\n\n\nRun the following \nnewt target\n commands, from your project directory, t
o create a bootloader target. We name the target \nprimo_boot\n.\n\n\n$ newt target create primo_boot\n$ newt target set primo_boot app=@apache-mynewt-core/apps/boot bsp=@apache-mynewt-core/hw/bsp/arduino_primo_nrf52 build_profile=optimized\n\n\n\n\n\n\nRun the following \nnewt target\n commands to create a target for the Blinky application. We name the target \nprimoblinky\n.\n\n\n$ newt target create primoblinky\n$ newt target set primoblinky app=apps/blinky bsp=@apache-mynewt-core/hw/bsp/arduino_primo_nrf52 build_profile=d
<TRUNCATED>
[3/5] incubator-mynewt-site git commit: This closes #183. This closes
#184. Adding instructions to use Visual Studio for Mynewt developers
Posted by ad...@apache.org.
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/develop/newt/install/newt_windows/index.html
----------------------------------------------------------------------
diff --git a/develop/newt/install/newt_windows/index.html b/develop/newt/install/newt_windows/index.html
index a744b87..9a87f91 100644
--- a/develop/newt/install/newt_windows/index.html
+++ b/develop/newt/install/newt_windows/index.html
@@ -491,11 +491,10 @@ README.md newtvm
<p><br>
Check that the newt tool is installed and it is in your path:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ls go/bin
-$ ls bin/newt
-bin/newt
-$which go
-/home/<user>/dev/go/bin/newt
+<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>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/develop/newtmgr/install_windows/index.html
----------------------------------------------------------------------
diff --git a/develop/newtmgr/install_windows/index.html b/develop/newtmgr/install_windows/index.html
index 1f5cbeb..90c482c 100644
--- a/develop/newtmgr/install_windows/index.html
+++ b/develop/newtmgr/install_windows/index.html
@@ -403,7 +403,7 @@ nothing to commit, working directory clean
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
+$which newtmgr
~/dev/go/bin/newtmgr
</pre></div>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/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 76afa39..a149ee2 100644
--- a/develop/os/get_started/project_create/index.html
+++ b/develop/os/get_started/project_create/index.html
@@ -641,7 +641,7 @@ All tests passed
<p><br></p>
<h3 id="building-and-running-the-simulated-blinky-application">Building and Running the Simulated Blinky Application</h3>
<p>The section shows you how to build and run the blinky application to run on Mynewt's simulated hardware.</p>
-<p><strong>Note</strong>: This is not yet supported on Windows. Refer to the <a href="../../tutorials/blinky/">Blinky Tutorials</a> to create a blinky application on a target boards.</p>
+<p><strong>Note</strong>: This is not yet supported on Windows. Refer to the <a href="../../tutorials/blinky/">Blinky Tutorials</a> to create a blinky application for a target board.</p>
<p><br></p>
<h4 id="building-the-application">Building the Application</h4>
<p>To build the simulated blinky application, run <code>newt build my_blinky_sim</code>:</p>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/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 8ea6365..76cc371 100644
--- a/develop/os/tutorials/arduino_zero/index.html
+++ b/develop/os/tutorials/arduino_zero/index.html
@@ -573,6 +573,7 @@ the repository to the <code>project.yml</code> file in your base project directo
<p>Here is an example <code>project.yml</code> file with the Arduino Zero repository
added. The sections with <code>mynewt_arduino_zero</code> that need to be added to
your project file are highlighted.</p>
+<p><strong>Note:</strong> On Windows platforms: You need to set <code>vers</code> to <code>0-dev</code> and use the latest master branch for both repositories.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ more project.yml
project.name: "my_project"
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/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 6c6fa1a..46ae00d 100644
--- a/develop/os/tutorials/blinky_primo/index.html
+++ b/develop/os/tutorials/blinky_primo/index.html
@@ -671,7 +671,7 @@ App image succesfully generated: ~/dev/myproj/bin/targets/primoblinky/app/apps/b
</ul>
<p><img alt="J-Link debug probe to Arduino" src="../pics/primo-jlink.jpg" title="Connecting J-Link debug probe to Arduino Primo" /></p>
<p><strong>Note:</strong> If you are using the OpenOCD debugger, you do not need to attach this connector. </p>
-<h3 id="load-the-bootloader-and-the-blinky-application-image">Load the Bootloader and the Blinky Application Image</h3>
+<h3 id="load-the-bootloader">Load the Bootloader</h3>
<p>Run the <code>newt load primo_boot</code> command to load the bootloader onto the board:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt load primo_boot
Loading bootloader
@@ -679,8 +679,15 @@ $
</pre></div>
-<p><br>
-Run the <code>newt load primoblinky</code> command to load the Blinky application image onto the board.</p>
+<p><strong>Note:</strong> If you are using OpenOCD on a Windows platform and you get an <code>unable to find CMSIS-DAP device</code> error, you will need to download and install the mbed Windows serial port driver from <a href="https://developer.mbed.org/handbook/Windows-serial-configuration">https://developer.mbed.org/handbook/Windows-serial-configuration</a>. Follow the instructions from the site to install the driver. Here are some additional notes about the installation:</p>
+<ol>
+<li>The instructions indicate that the mbed Windows serial port driver is not required for Windows 10. If you are using Windows 10 and get the <code>unable to find CMSIS-DAP device</code> error, we recommend that you install the driver.</li>
+<li>If the driver installation fails, we recommend that you unplug the board, plug it back in, and retry the installation.</li>
+</ol>
+<p>Run the <code>newt load primo_boot</code> command again.</p>
+<p><br></p>
+<h3 id="load-the-blinky-application-image">Load the Blinky Application Image</h3>
+<p>Run the <code>newt load primoblinky</code> command to load the Blinky application image onto the board.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt load primoblinky
Loading app image into slot 1
$
@@ -690,6 +697,7 @@ $
<p>You should see the orange LED (L13), below the ON LED, on the board blink!</p>
<p>Note: If the LED does not blink, try resetting the board.</p>
<p><br></p>
+<h3 id="erase-flash">Erase Flash</h3>
<p>If you want to erase the flash and load the image again, use JLinkExe and issue the <code>erase</code> command when you are using the Jlink debug probe: </p>
<p><strong>Note:</strong> On Windows: Run the <code>jlink</code> command with the same arguments from a Windows Command Prompt terminal.
<br></p>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/develop/os/tutorials/blinky_stm32f4disc/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/blinky_stm32f4disc/index.html b/develop/os/tutorials/blinky_stm32f4disc/index.html
index 259e88f..9d6cb08 100644
--- a/develop/os/tutorials/blinky_stm32f4disc/index.html
+++ b/develop/os/tutorials/blinky_stm32f4disc/index.html
@@ -668,6 +668,14 @@ Loading bootloader
</pre></div>
+<p>Note: If you are using Windows and get an <code>open failed</code> or <code>no device found</code> error, you will need to install the usb driver. Download <a href="http://zadig.akeo.ie">Zadig</a> and run it:</p>
+<ul>
+<li>Select Options > List All Devices.</li>
+<li>Select <code>STM32 STLink</code> from the drop down menu.</li>
+<li>Select the <code>WinUSB</code> driver.</li>
+<li>Click Install Driver.</li>
+<li>Run the <code>newt load stm32f4disc_boot</code> command again.</li>
+</ul>
<p><br>
Run the <code>newt load stm32f4disc_blinky</code> command to load the Blinky application image onto the board.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$newt load stm32f4disc_blinky
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/develop/os/tutorials/olimex/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/olimex/index.html b/develop/os/tutorials/olimex/index.html
index 67815c5..d255252 100644
--- a/develop/os/tutorials/olimex/index.html
+++ b/develop/os/tutorials/olimex/index.html
@@ -682,11 +682,11 @@ Successfully loaded image.
</pre></div>
-<p>Note: If you are using Windows and get the <code>no device found</code> error, you will need to install the usb drivers for your Olimex debugger. Download <a href="http://zadig.akeo.ie">Zadig</a> and run it:</p>
+<p>Note: If you are using Windows and get a <code>no device found</code> error, you will need to install the usb driver. Download <a href="http://zadig.akeo.ie">Zadig</a> and run it:</p>
<ul>
<li>Select Options > List All Devices.</li>
-<li>Select Olimex OpenOCD JTAG ARM-USB-TINY-H from the drop down menu.</li>
-<li>Select the WinUSB drivers.</li>
+<li>Select <code>Olimex OpenOCD JTAG ARM-USB-TINY-H</code> from the drop down menu.</li>
+<li>Select the <code>WinUSB</code> driver.</li>
<li>Click Install Driver.</li>
<li>Run the <code>newt load boot_olimex</code> command again. </li>
</ul>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/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 86a65d7..9a24c01 100644
--- a/develop/os/tutorials/project-stm32-slinky/index.html
+++ b/develop/os/tutorials/project-stm32-slinky/index.html
@@ -622,6 +622,15 @@ $
<p><br>
+Note: If you are using Windows and get a <code>no device found</code> error, you will need to install the usb driver. Download <a href="http://zadig.akeo.ie">Zadig</a> and run it:</p>
+<ul>
+<li>Select Options > List All Devices.</li>
+<li>Select <code>Olimex OpenOCD JTAG ARM-USB-TINY-H</code> from the drop down menu.</li>
+<li>Select the <code>WinUSB</code> driver.</li>
+<li>Click Install Driver.</li>
+<li>Run the <code>newt load stm32_boot</code> command again.</li>
+</ul>
+<p><br>
Run the <code>newt load stm32_slinky</code> command to load the Slinky application image onto the board:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt load stm32_slinky
Loading app image into slot 1
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/develop/os/tutorials/rbnano2/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/rbnano2/index.html b/develop/os/tutorials/rbnano2/index.html
index 8a72861..a6c63ca 100644
--- a/develop/os/tutorials/rbnano2/index.html
+++ b/develop/os/tutorials/rbnano2/index.html
@@ -645,7 +645,7 @@ App image succesfully generated: ~/dev/myproj/bin/targets/rbnano2_blinky/app/app
<p><br></p>
<h3 id="connect-to-the-board">Connect to the Board</h3>
<p>Connect the RedBear Nano 2 USB to a USB port on your computer. You should see an orange LED light up on the board.</p>
-<h3 id="load-the-bootloader-and-the-blinky-application-image">Load the Bootloader and the Blinky Application Image</h3>
+<h3 id="load-the-bootloader">Load the Bootloader</h3>
<p>Run the <code>newt load rbnano2_boot</code> command to load the bootloader onto the board: </p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt load rbnano2_boot
Loading bootloader
@@ -653,8 +653,16 @@ $
</pre></div>
-<p><br>
-Note: The flash memory on the RedBear Nano 2 comes write protected from the factory. If you get an error loading the bootloader and you are using a brand new chip, you need to clear the write protection from the debugger and then load the bootloader again. Run the <code>newt debug rbnano2_blinky</code> command and issue the following commands at the highlighted (gdb) prompts. </p>
+<p><br></p>
+<p><strong>Note:</strong> On Windows platforms, if you get an <code>unable to find CMSIS-DAP device</code> error, you will need to download and install the mbed Windows serial port driver from <a href="https://developer.mbed.org/handbook/Windows-serial-configuration">https://developer.mbed.org/handbook/Windows-serial-configuration</a>. Follow the instructions from the site to install the driver. Here are some additional notes about the installation:</p>
+<ol>
+<li>The instructions indicate that the mbed Windows serial port driver is not required for Windows 10. If you are using Windows 10 and get the <code>unable to find CMSIS-DAP device</code> error, we recommend that you install the driver.</li>
+<li>If the driver installation fails, we recommend that you unplug the board, plug it back in, and retry the installation.</li>
+</ol>
+<p>Run the <code>newt load rbnano2_boot</code> command again.</p>
+<p><br></p>
+<h4 id="clear-the-write-protection-on-the-flash-memory">Clear the Write Protection on the Flash Memory</h4>
+<p>The flash memory on the RedBear Nano 2 comes write protected from the factory. If you get an error loading the bootloader and you are using a brand new chip, you need to clear the write protection from the debugger and then load the bootloader again. Run the <code>newt debug rbnano2_blinky</code> command and issue the following commands at the highlighted (gdb) prompts. </p>
<p><strong>Note:</strong> The output of the debug session below is for Mac OS and Linux platforms. On Windows, openocd and gdb are started in separate Windows Command Prompt terminals, and the terminals are automatically closed when you quit gdb. In addition, the output of openocd is logged to the openocd.log file in your project's base directory instead of the terminal.</p>
<p><br></p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$newt debug rbnano2_blinky
@@ -683,8 +691,10 @@ Error: Failed to read memory at 0x00009ef4
</pre></div>
+<p><br></p>
+<h3 id="load-the-blinky-application-image">Load the Blinky Application Image</h3>
<p><br>
-Run the <code>newt load rbnano2_blinky</code> command to load the Blinky application image onto the board.</p>
+Run the <code>newt load rbnano2_blinky</code> command to load the Blinky application image onto the board:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt load rbnano2_blinky
Loading app image into slot 1
</pre></div>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/develop/os/tutorials/wi-fi_on_arduino/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/wi-fi_on_arduino/index.html b/develop/os/tutorials/wi-fi_on_arduino/index.html
index afc744e..0102794 100644
--- a/develop/os/tutorials/wi-fi_on_arduino/index.html
+++ b/develop/os/tutorials/wi-fi_on_arduino/index.html
@@ -518,13 +518,10 @@ the repository to the <code>project.yml</code> file in your base project directo
low level operations. Sometimes this code is licensed only for the specific manufacturer of the chipset and cannot live in the Apache Mynewt repository. That happens to be the case for the Arduino Zero board which uses Atmel SAMD21. Runtime's github repository hosts such external third-party packages and the Newt tool can fetch them.</p>
<p>To fetch the package with MCU support for Atmel SAMD21 for Arduino Zero from the Runtime git repository, you need to add
the repository to the <code>project.yml</code> file in your base project directory (<code>arduinowifi</code>).</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">user@~/dev/arduinowifi$ vi project.yml
-</pre></div>
-
-
<p>Here is an example <code>project.yml</code> file with the Arduino Zero repository
added. The sections with <code>mynewt_arduino_zero</code> that need to be added to
your project file are highlighted.</p>
+<p><strong>Note:</strong> On Windows platforms: You need to set <code>vers</code> to <code>0-dev</code> and use the latest master branch for both repositories.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ more project.yml
project.name: "my_project"
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/develop/sitemap.xml
----------------------------------------------------------------------
diff --git a/develop/sitemap.xml b/develop/sitemap.xml
index edefac3..b535b74 100644
--- a/develop/sitemap.xml
+++ b/develop/sitemap.xml
@@ -4,7 +4,7 @@
<url>
<loc>http://mynewt.apache.org/</loc>
- <lastmod>2017-05-14</lastmod>
+ <lastmod>2017-05-22</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -13,7 +13,7 @@
<url>
<loc>http://mynewt.apache.org/pages/ble/</loc>
- <lastmod>2017-05-14</lastmod>
+ <lastmod>2017-05-22</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -22,7 +22,7 @@
<url>
<loc>http://mynewt.apache.org/quick-start/</loc>
- <lastmod>2017-05-14</lastmod>
+ <lastmod>2017-05-22</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -30,7 +30,7 @@
<url>
<loc>http://mynewt.apache.org/about/</loc>
- <lastmod>2017-05-14</lastmod>
+ <lastmod>2017-05-22</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -38,7 +38,7 @@
<url>
<loc>http://mynewt.apache.org/talks/</loc>
- <lastmod>2017-05-14</lastmod>
+ <lastmod>2017-05-22</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -46,7 +46,7 @@
<url>
<loc>http://mynewt.apache.org/download/</loc>
- <lastmod>2017-05-14</lastmod>
+ <lastmod>2017-05-22</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -54,7 +54,7 @@
<url>
<loc>http://mynewt.apache.org/community/</loc>
- <lastmod>2017-05-14</lastmod>
+ <lastmod>2017-05-22</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -62,7 +62,7 @@
<url>
<loc>http://mynewt.apache.org/events/</loc>
- <lastmod>2017-05-14</lastmod>
+ <lastmod>2017-05-22</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -71,7 +71,7 @@
<url>
<loc>http://mynewt.apache.org/os/introduction/</loc>
- <lastmod>2017-05-14</lastmod>
+ <lastmod>2017-05-22</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -83,7 +83,7 @@
<url>
<loc>http://mynewt.apache.org/os/get_started/vocabulary/</loc>
- <lastmod>2017-05-14</lastmod>
+ <lastmod>2017-05-22</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -123,19 +123,25 @@
<url>
<loc>http://mynewt.apache.org/faq/go_env/</loc>
- <lastmod>2017-05-14</lastmod>
+ <lastmod>2017-05-22</lastmod>
+ <changefreq>daily</changefreq>
+ </url>
+
+ <url>
+ <loc>http://mynewt.apache.org/faq/ide/</loc>
+ <lastmod>2017-05-22</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/how_to_edit_docs/</loc>
- <lastmod>2017-05-14</lastmod>
+ <lastmod>2017-05-22</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/answers/</loc>
- <lastmod>2017-05-14</lastmod>
+ <lastmod>2017-05-22</lastmod>
<changefreq>daily</changefreq>
</url>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/faq/pics/debug_new_config_small.png
----------------------------------------------------------------------
diff --git a/faq/pics/debug_new_config_small.png b/faq/pics/debug_new_config_small.png
new file mode 100755
index 0000000..5d2e287
Binary files /dev/null and b/faq/pics/debug_new_config_small.png differ
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/faq/pics/gdb_debug_small.png
----------------------------------------------------------------------
diff --git a/faq/pics/gdb_debug_small.png b/faq/pics/gdb_debug_small.png
new file mode 100755
index 0000000..5ebfb11
Binary files /dev/null and b/faq/pics/gdb_debug_small.png differ
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/faq/pics/gdb_server_small.png
----------------------------------------------------------------------
diff --git a/faq/pics/gdb_server_small.png b/faq/pics/gdb_server_small.png
new file mode 100755
index 0000000..e6a42d7
Binary files /dev/null and b/faq/pics/gdb_server_small.png differ
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/faq/pics/gdb_small.png
----------------------------------------------------------------------
diff --git a/faq/pics/gdb_small.png b/faq/pics/gdb_small.png
new file mode 100755
index 0000000..f6c35d2
Binary files /dev/null and b/faq/pics/gdb_small.png differ
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/faq/pics/integrated_terminal_small.png
----------------------------------------------------------------------
diff --git a/faq/pics/integrated_terminal_small.png b/faq/pics/integrated_terminal_small.png
new file mode 100755
index 0000000..11414c8
Binary files /dev/null and b/faq/pics/integrated_terminal_small.png differ
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/faq/pics/launch_small.png
----------------------------------------------------------------------
diff --git a/faq/pics/launch_small.png b/faq/pics/launch_small.png
new file mode 100755
index 0000000..5c13dcf
Binary files /dev/null and b/faq/pics/launch_small.png differ
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/faq/pics/task_json_small.png
----------------------------------------------------------------------
diff --git a/faq/pics/task_json_small.png b/faq/pics/task_json_small.png
new file mode 100755
index 0000000..5047f61
Binary files /dev/null and b/faq/pics/task_json_small.png differ
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/faq/pics/task_runner_small.png
----------------------------------------------------------------------
diff --git a/faq/pics/task_runner_small.png b/faq/pics/task_runner_small.png
new file mode 100755
index 0000000..25a70fa
Binary files /dev/null and b/faq/pics/task_runner_small.png differ
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/faq/pics/task_select_small.png
----------------------------------------------------------------------
diff --git a/faq/pics/task_select_small.png b/faq/pics/task_select_small.png
new file mode 100755
index 0000000..35bc304
Binary files /dev/null and b/faq/pics/task_select_small.png differ
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/faq/pics/task_start_small.png
----------------------------------------------------------------------
diff --git a/faq/pics/task_start_small.png b/faq/pics/task_start_small.png
new file mode 100755
index 0000000..f84cd26
Binary files /dev/null and b/faq/pics/task_start_small.png differ
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/latest/faq/answers/index.html
----------------------------------------------------------------------
diff --git a/latest/faq/answers/index.html b/latest/faq/answers/index.html
index a7dff75..d30bea1 100644
--- a/latest/faq/answers/index.html
+++ b/latest/faq/answers/index.html
@@ -220,6 +220,14 @@
<li >
+ <a href="../ide/">Using an IDE to Develop Mynewt Applications</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../how_to_edit_docs/">Edit Docs</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/latest/faq/go_env/index.html
----------------------------------------------------------------------
diff --git a/latest/faq/go_env/index.html b/latest/faq/go_env/index.html
index 89739e2..96384c0 100644
--- a/latest/faq/go_env/index.html
+++ b/latest/faq/go_env/index.html
@@ -220,6 +220,14 @@
<li >
+ <a href="../ide/">Using an IDE to Develop Mynewt Applications</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../how_to_edit_docs/">Edit Docs</a>
</li>
@@ -466,8 +474,8 @@ Build and install the tool. The updated binary will be installed in the <strong>
</li>
<li class="pull-right">
- <a href=../how_to_edit_docs/>
- Next: Edit Docs
+ <a href=../ide/>
+ Next: Using an IDE to Develop Mynewt Applications
<span class="fa fa-arrow-right"></span>
</a>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/latest/faq/how_to_edit_docs/index.html
----------------------------------------------------------------------
diff --git a/latest/faq/how_to_edit_docs/index.html b/latest/faq/how_to_edit_docs/index.html
index d204e28..7026851 100644
--- a/latest/faq/how_to_edit_docs/index.html
+++ b/latest/faq/how_to_edit_docs/index.html
@@ -219,6 +219,14 @@
+ <li >
+ <a href="../ide/">Using an IDE to Develop Mynewt Applications</a>
+ </li>
+
+
+
+
+
<li class="active">
<a href="./">Edit Docs</a>
</li>
@@ -317,9 +325,9 @@
<ul class="nav nav-pills" style="margin-bottom: 10px">
<li>
- <a href=../go_env/>
+ <a href=../ide/>
<span class="fa fa-arrow-left"></span>
- Previous: Setting Up Go to Contribute to Newt and Newtmgr Tools
+ Previous: Using an IDE to Develop Mynewt Applications
</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/latest/faq/ide/index.html
----------------------------------------------------------------------
diff --git a/latest/faq/ide/index.html b/latest/faq/ide/index.html
new file mode 100644
index 0000000..92dc454
--- /dev/null
+++ b/latest/faq/ide/index.html
@@ -0,0 +1,546 @@
+<!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/faq/ide/"> -->
+ <link rel="shortcut icon" href="../../img/favicon.ico">
+
+ <title>Using an IDE to Develop Mynewt Applications - 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="Using an IDE to Develop Mynewt Applications">
+
+
+ <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="../../os/introduction/">Mynewt Documentation</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li><a href="
+ ../go_env/
+">Appendix</a>
+
+
+ <ul>
+
+
+
+ <li >
+ <a href="../go_env/">Setting Up Go to Contribute to Newt and Newtmgr Tools</a>
+ </li>
+
+
+
+
+
+ <li class="active">
+ <a href="./">Using an IDE to Develop Mynewt Applications</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../how_to_edit_docs/">Edit Docs</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../answers/">FAQ</a>
+ </li>
+
+
+
+ </ul>
+
+ </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="../go_env/">Appendix</a></li>
+
+
+
+ <li>» Using an IDE to Develop Mynewt Applications</li>
+
+
+
+ </ul>
+</div>
+ </div>
+
+ <h2 id="developing-mynewt-applications-with-visual-studio-code">Developing Mynewt Applications with Visual Studio Code</h2>
+<p>This guide shows you how to set up Visual Studio Code to develop and debug Mynewt applications. Visual Studio Code is supported on Mac OS, Linux, and Windows. This guide shows you how to:</p>
+<ol>
+<li>Install Visual Studio Code. </li>
+<li>Install the C/C++ and debugger extensions.</li>
+<li>Define task configurations to build Mynewt applications.</li>
+<li>Define debugger configurations to debug Mynewt applications. </li>
+<li>Launch the debugger. </li>
+</ol>
+<p>Prerequisites:</p>
+<ul>
+<li>Have Internet connectivity to fetch remote Mynewt components.</li>
+<li>Have a computer to build a Mynewt application.</li>
+<li>Perform <a href="../../os/get_started/native_install_intro/">native installation</a> for the Mynewt tools and toolchains.</li>
+<li>Read the Mynewt OS Concepts 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 Creating Your First Project. </li>
+<li>Complete one of the <a href="../../os/tutorials/blinky/">Blinky Tutorials</a>.</li>
+</ul>
+<p><strong>Notes:</strong> </p>
+<ul>
+<li>This guide is not a tutorial for Visual Studio Code. It assumes you are familiar with Visual Studio Code. If this is your first time using Visual Studio Code, we recommend that you read the Visual Studio Code <a href="https://code.visualstudio.com/docs">documentation and tutorials</a> and evaluate whether you would like to use it to develop Mynewt applications. </li>
+<li>This guide uses Visual Studio Code on Windows. Visual Studio Code is supported on Linux and Mac OS but may have some variations in the keyboard shortcuts and command names for these platforms. </li>
+<li>You can also use the Eclipse IDE to develop Mynewt applications. See <a href="https://www.codecoup.pl/blog/hacking-mynewt-in-eclipse">https://www.codecoup.pl/blog/hacking-mynewt-in-eclipse</a> for more details.</li>
+</ul>
+<h3 id="installing-visual-studio-code">Installing Visual Studio Code</h3>
+<p>Download and install Visual Studio Code from <a href="https://code.visualstudio.com/">https://code.visualstudio.com/</a>.</p>
+<h3 id="installing-the-cc-and-debugger-extensions">Installing the C/C++ and Debugger Extensions</h3>
+<p>You need to install two extensions:</p>
+<ol>
+<li>
+<p>The C/C++ extension from Microsoft. This extension provides language support such as symbol searching, signatuare help, go to definition, and go to declaration.</p>
+</li>
+<li>
+<p>The Native Debug extension from webfreak. This extension provides GDB support. </p>
+</li>
+</ol>
+<p><br>
+To install the C/C++ extension:</p>
+<ol>
+<li>Press <code>Ctrl-P</code> to open the search box.</li>
+<li>Type <code>ext install cpptools</code> in the search box and press Enter. You should see the extension at the top of the list. </li>
+<li>Click <code>Install</code> to install the extension.
+<br></li>
+</ol>
+<p>To install the Native Debugger:</p>
+<ol>
+<li>Press <code>Ctrl-P</code> to open the search box.</li>
+<li>Type <code>ext install webfreak.debug</code> in the search box and press Enter. You should see the Native Debug extension at the top of the list.</li>
+<li>Click <code>Install</code> to install the extension.
+<br></li>
+</ol>
+<h3 id="defining-tasks-for-mynewt-projects">Defining Tasks for Mynewt Projects</h3>
+<p>Two main concepts in Visual Studio Code are workspaces and tasks. A workspace represents a folder that is open. You can open multiple workspaces and switch between workspaces. </p>
+<p>Tasks allow you to integrate the external tools and operations that are used to build or test your project into Visual Studio Code. Tasks are run from and the task results can be analyzed in Visual Studio Code. Tasks are defined within the scope of a workspace. This means that the tasks you define for a workspace only apply to the given workspace.</p>
+<p><br></p>
+<h4 id="associating-a-mynewt-project-to-a-workspace">Associating a Mynewt Project to a Workspace</h4>
+<p>For your Mynewt project, your Visual Studio Code workspace is the Mynewt project base directory. For example, if you create a project named <code>myproj</code> under the <code>~/dev</code> directory, then you open the <code>~/dev/myproj</code> folder for your workspace. </p>
+<p>Select <strong>File</strong> > <strong>Open Folder</strong>, and select the <code>myproj</code> folder from the <code>Select Folder</code> dialog box to open the folder.</p>
+<p><br></p>
+<h4 id="defining-visual-studio-code-tasks-to-build-and-debug-mynewt-applications">Defining Visual Studio Code Tasks to Build and Debug Mynewt Applications</h4>
+<p>You define Visual Studio Code tasks to build and debug your Mynewt targets in Visual Studio Code. We use the Blinky application for the Arduino Zero board from the <a href="../../os/tutorials/arduino_zero/">Blinky On Arduino Zero Tutorial</a> to illustrate how to define the tasks to build and debug the Arduino blinky bootloader and application targets.</p>
+<p>Perform the following steps to create the tasks to build and debug the Arduino blinky bootloader and appliction targets:</p>
+<p>Step 1: Press <code>Ctrl-Shift-P</code>, type <code>task</code> in the search box, and select <strong>Tasks:Configure Task Runner</strong> from the search results. </p>
+<p>Step 2: Select <strong>Others</strong> (scroll down to the bottom of the list) to create a task runner for external commands.
+<br>
+<p align="center"><img src="/faq/pics/task_runner_small.png"></p>
+<br>
+Tasks are defined in the <code>tasks.json</code> file. You should see the <code>.vscode</code> folder created in the <code>MYPROJ</code> folder and a <code>tasks.json</code> file created in the <code>.vscode</code> folder. The <code>tasks.json</code> file has the following default values. </p>
+<p><br>
+<p align="center"><img src="/faq/pics/task_json_small.png"></p>
+<br></p>
+<p>The sample <code>tasks.json</code> file defines a simple task that runs the echo command with "Hello World" as the argument. </p>
+<p>Step 3: Delete the content from the <code>tasks.json</code> file, add the following definitions, and press <code>Ctrl-S</code> to save the file.</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">{
+ "version": "0.1.0",
+ "command": "newt",
+ "echoCommand": true,
+ "isShellCommand": true,
+
+ "tasks":[
+ {
+ "taskName": "build_arduino_boot",
+ "args": ["build", "arduino_boot"],
+ "suppressTaskName": true
+ },
+ {
+ "taskName": "build_arduino_blinky",
+ "args": ["build", "arduino_blinky"],
+ "isBuildCommand": true,
+ "suppressTaskName": true
+ },
+ {
+ "taskName": "create_arduino_blinky",
+ "args": ["create-image", "arduino_blinky", "1.0.0"],
+ "suppressTaskName":true
+ },
+ {
+ "taskName": "debug_arduino_blinky",
+ "args": ["debug", "arduino_blinky", "-n"],
+ "suppressTaskName": true
+ }
+ ]
+}
+</pre></div>
+
+
+<p><br>
+The <code>tasks.json</code> file specifies the tasks that are run to build and debug the Arduino blinky targets. Each task runs a <code>newt</code> command. The <code>newt</code> command to run and the arguments for the <code>newt</code> command are passed in the <code>args</code> property for each task. </p>
+<p>The following tasks are defined in this example:</p>
+<ol>
+<li><strong>build_arduino_boot</strong>: Runs the <code>newt build arduino_boot</code> command to build the arduino_boot target.</li>
+<li>
+<p><strong>build_arduino_blinky</strong>: Runs the <code>newt build arduino_blinky</code> command to build the arduino_blinky target. </p>
+<p><strong>Note:</strong> This task sets the <code>isBuildCommand</code> property to <code>true</code>. This is an optional property that, when set to true, allows you to run the <strong>Tasks: Run Build Task</strong>(<code>Ctrl-Shift-B</code>) command to start the task.</p>
+</li>
+<li>
+<p><strong>create_arduino_blinky</strong>: Runs the <code>newt create-image arduino_blinky</code> command to create the image file.</p>
+</li>
+<li><strong>debug_arduino_blinky</strong>: Runs the <code>newt build arduino_blinky -n</code> command to debug the arduino_blinky target. The <code>-n</code> flag is specified to start only the GDB server and not the GDB client. We will launch the GDB client from Visual Studio Code.</li>
+</ol>
+<p>For more information on tasks and all supported properties, see the <a href="https://code.visualstudio.com/docs/editor/tasks">Visual Studio Code Task documentation</a>.</p>
+<p><br></p>
+<h4 id="running-a-task">Running a Task</h4>
+<p>To run a task, select <code>Ctrl-Shift-P</code>, type <code>task</code>, and select <strong>Tasks: Run Task</strong>. The tasks that you define in the <code>tasks.json</code> file are listed. Select the task to run. </p>
+<p>The following is an example of running the <code>build_arduino_boot</code> task:
+<br>
+<p align="center"><img src="/faq/pics/task_select_small.png"></p>
+<br>
+<br>
+<p align="center"><img src="/faq/pics/task_start_small.png"></p></p>
+<p><br></p>
+<h4 id="defining-tasks-for-other-newt-commands">Defining Tasks for Other Newt Commands</h4>
+<p>Other newt commands, such as the <code>newt load</code> command, do not need to run from within Visual Studio Code. You can define tasks for them as a convenience or run them on the command line from the Visual Studio Code integrated terminal (or an external terminal).</p>
+<p>To create the tasks for the <code>newt load arduino_boot</code> and <code>newt laod arduino_blinky</code> commands, add the following definitions to the <code>tasks.json</code> file:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> {
+ "taskName": "load_arduino_boot",
+ "args": ["load", "arduino_boot"],
+ "suppressTaskName":true
+ },
+ {
+ "taskName": "load_arduino_blinky",
+ "args": ["load", "arduino_blinky"],
+ "suppressTaskName":true
+ },
+</pre></div>
+
+
+<p><br>
+To run the commands from the Visual Studio integrated terminal, press <code>Ctrl-`</code> to launch the integrated terminal and enter the command as shown:
+<br>
+<p align="center"><img src="/faq/pics/integrated_terminal_small.png"></p>
+<br></p>
+<h3 id="defining-debugger-configurations">Defining Debugger Configurations</h3>
+<p>You need to define a debugger configuration to launch the GDB debugger from within Visual Studio Code: </p>
+<p>Step 1: Select <strong>Debug</strong> > <strong>Open Configuration</strong>, and select the <strong>GDB</strong> environment.</p>
+<p><br>
+<p align="center"><img src="/faq/pics/debug_new_config_small.png"></p>
+<br></p>
+<p>You should see a default <code>launch.json</code> file created in the <code>.vscode</code> folder.
+<br>
+<p align="center"><img src="/faq/pics/launch_small.png"></p>
+<br></p>
+<p><br>
+Step 2: Delete the content from the <code>launch.json</code> file, add the following definitions, and press 'Ctrl-S' to save the file.</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">{
+ "version": "0.2.0",
+ "configurations": [
+ {
+ "name": "gdb_arduino_blinky",
+ "type": "gdb",
+ "request": "attach",
+ "executable": "${workspaceRoot}\\bin\\targets\\arduino_blinky\\app\\apps\\blinky\\blinky.elf",
+ "target": ":3333",
+ "cwd": "${workspaceRoot}",
+ "gdbpath": "arm-none-eabi-gdb.exe",
+ "remote": true
+
+ }
+ ]
+}
+</pre></div>
+
+
+<p><br>
+This defines a <code>gdb_arduino_blinky</code> debugger configuration. It specifies: </p>
+<ul>
+<li>The debugger is type <strong>gdb</strong>.</li>
+<li>To use the <code>blinky.elf</code> file for the executable. </li>
+<li>To use port 3333 to connect with the remote target.</li>
+<li>To use arm-none-eabi-gdb for the GDB program.
+<br></li>
+</ul>
+<h3 id="debugging-your-application">Debugging Your Application</h3>
+<p>To debug your application, start the GDB server and launch the GDB session from Visual Studio Code. For the the arduino blinky example, perform the following:</p>
+<p>Step 1: Run the debug_arduino_blinky task to start the GDB server. Perform the following:</p>
+<ol>
+<li>Press <code>Ctrl-Shift-P</code> and type <code>task</code> in the search box. </li>
+<li>Select <strong>Tasks:Run Task</strong> > <strong>debug_arduino_blinky</strong>.</li>
+<li>Press <code>Ctrl-Shift-U</code> to open the Output Panel and see the OpenOCD GDB Server output.
+<br> <br />
+<p align="center"><img src="/faq/pics/gdb_server_small.png"></p>
+<br></li>
+</ol>
+<p>Step 2: Start the GDB session. Perform the following: </p>
+<ol>
+<li>Press <code>Ctrl-Shift-Y</code> to view the Debug Console. </li>
+<li>Press the Debugging icon on the activity bar (Ctrl-Shift-D) to bring up the Debug Side Bar.</li>
+<li>Select <code>gdb_arduino_blinky</code> from the DEBUG drop down menu. </li>
+<li>Press the green play button to start the gdb session.</li>
+</ol>
+<p align="center"><img src="/faq/pics/gdb_small.png"></p>
+
+<p><br>
+Step 3: Debug your application. You should see a debug session similar to the one shown below:
+<p align="center"><img src="/faq/pics/gdb_debug_small.png"></p>
+<br>
+For more information on how to use the Visual Studio Code Debugger, see the <a href="https://code.visualstudio.com/docs/editor/debugging">Visual Studio Code debugging documentation</a>.</p>
+<h3 id="working-with-multiple-mynewt-applications">Working with Multiple Mynewt Applications</h3>
+<p>As mentioned previously, each mynewt project corresponds to a Visual Studio Code workspace. If you have multiple Mynewt application targets defined in same project, you will need to define build and debug tasks for each target in the <code>tasks.json</code> file and debugger configurations for the targets in the <code>launch.json</code> file for the workspace. If you have a different Mynewt project for each mynewt application, you will need to define build and debug tasks in the <code>tasks.json</code> file and the debugger configuration in the <code>launch.json</code> file for each workspace. </p>
+
+ <div class="row">
+
+
+
+
+<ul class="nav nav-pills" style="margin-bottom: 10px">
+ <li>
+
+ <a href=../go_env/>
+ <span class="fa fa-arrow-left"></span>
+ Previous: Setting Up Go to Contribute to Newt and Newtmgr Tools
+ </a>
+
+ </li>
+ <li class="pull-right">
+
+ <a href=../how_to_edit_docs/>
+ Next: Edit Docs
+ <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/65dc6d41/latest/faq/pics/debug_new_config_small.png
----------------------------------------------------------------------
diff --git a/latest/faq/pics/debug_new_config_small.png b/latest/faq/pics/debug_new_config_small.png
new file mode 100755
index 0000000..5d2e287
Binary files /dev/null and b/latest/faq/pics/debug_new_config_small.png differ
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/latest/faq/pics/gdb_debug_small.png
----------------------------------------------------------------------
diff --git a/latest/faq/pics/gdb_debug_small.png b/latest/faq/pics/gdb_debug_small.png
new file mode 100755
index 0000000..5ebfb11
Binary files /dev/null and b/latest/faq/pics/gdb_debug_small.png differ
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/latest/faq/pics/gdb_server_small.png
----------------------------------------------------------------------
diff --git a/latest/faq/pics/gdb_server_small.png b/latest/faq/pics/gdb_server_small.png
new file mode 100755
index 0000000..e6a42d7
Binary files /dev/null and b/latest/faq/pics/gdb_server_small.png differ
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/latest/faq/pics/gdb_small.png
----------------------------------------------------------------------
diff --git a/latest/faq/pics/gdb_small.png b/latest/faq/pics/gdb_small.png
new file mode 100755
index 0000000..f6c35d2
Binary files /dev/null and b/latest/faq/pics/gdb_small.png differ
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/latest/faq/pics/integrated_terminal_small.png
----------------------------------------------------------------------
diff --git a/latest/faq/pics/integrated_terminal_small.png b/latest/faq/pics/integrated_terminal_small.png
new file mode 100755
index 0000000..11414c8
Binary files /dev/null and b/latest/faq/pics/integrated_terminal_small.png differ
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/latest/faq/pics/launch_small.png
----------------------------------------------------------------------
diff --git a/latest/faq/pics/launch_small.png b/latest/faq/pics/launch_small.png
new file mode 100755
index 0000000..5c13dcf
Binary files /dev/null and b/latest/faq/pics/launch_small.png differ
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/latest/faq/pics/task_json_small.png
----------------------------------------------------------------------
diff --git a/latest/faq/pics/task_json_small.png b/latest/faq/pics/task_json_small.png
new file mode 100755
index 0000000..5047f61
Binary files /dev/null and b/latest/faq/pics/task_json_small.png differ
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/latest/faq/pics/task_runner_small.png
----------------------------------------------------------------------
diff --git a/latest/faq/pics/task_runner_small.png b/latest/faq/pics/task_runner_small.png
new file mode 100755
index 0000000..25a70fa
Binary files /dev/null and b/latest/faq/pics/task_runner_small.png differ
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/latest/faq/pics/task_select_small.png
----------------------------------------------------------------------
diff --git a/latest/faq/pics/task_select_small.png b/latest/faq/pics/task_select_small.png
new file mode 100755
index 0000000..35bc304
Binary files /dev/null and b/latest/faq/pics/task_select_small.png differ
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/65dc6d41/latest/faq/pics/task_start_small.png
----------------------------------------------------------------------
diff --git a/latest/faq/pics/task_start_small.png b/latest/faq/pics/task_start_small.png
new file mode 100755
index 0000000..f84cd26
Binary files /dev/null and b/latest/faq/pics/task_start_small.png differ