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/12 20:12:07 UTC
[4/7] incubator-mynewt-site git commit: Instructions for tool
installation on Windows, typo corrections on Wifi tutorial,
notes added in Linux install.
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6e0ec54d/develop/os/introduction/index.html
----------------------------------------------------------------------
diff --git a/develop/os/introduction/index.html b/develop/os/introduction/index.html
index f4069c0..fbbba40 100644
--- a/develop/os/introduction/index.html
+++ b/develop/os/introduction/index.html
@@ -374,11 +374,11 @@ code.</p>
<p>In order to provide all this functionality, and operate in an
extremely low resource environment, Mynewt provides a very fine-grained source
package management and build system tool, called <em>newt</em>.</p>
-<p>You can install <em>newt</em> for <a href="../../newt/install/newt_mac/">Mac OS</a> or <a href="../../newt/install/newt_linux/">Linux</a>.</p>
+<p>You can install <em>newt</em> for <a href="../../newt/install/newt_mac/">Mac OS</a>, <a href="../../newt/install/newt_linux/">Linux</a>, or <a href="../../newt/install/newt_windows/">Windows</a>.</p>
<p><br></p>
<h3 id="newt-manager">Newt Manager</h3>
-<p>In order to enable a user to communicate with remote instances of Mynewt OS and query, configure, and operate them, Mynewt provides an application tool called Newt Manager or <code>newtmgr</code>.</p>
-<p>You can install <em>newtmgr</em> for <a href="../../newtmgr/install_mac/">Mac OS</a> or <a href="../../newtmgr/install_linux/">Linux</a>.</p>
+<p>In order to enable a user to communicate with remote instances of Mynewt OS and query, configure, and operate them, Mynewt provides an application tool called Newt Manager or <em>newtmgr</em>.</p>
+<p>You can install <em>newtmgr</em> for <a href="../../newtmgr/install_mac/">Mac OS</a>, <a href="../../newtmgr/install_linux/">Linux</a>, or <a href="../../newtmgr/install_newtmgr/">Windows</a>.</p>
<p><br></p>
<h3 id="build-your-first-mynewt-app-with-newt">Build your first Mynewt App with Newt</h3>
<p>With the introductions out of the way, now is a good time to <a href="../get_started/get_started/">get set up and
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6e0ec54d/develop/os/tutorials/add_shell/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/add_shell/index.html b/develop/os/tutorials/add_shell/index.html
index 8b14c3e..59aa45a 100644
--- a/develop/os/tutorials/add_shell/index.html
+++ b/develop/os/tutorials/add_shell/index.html
@@ -554,9 +554,19 @@ App image succesfully generated: ~/dev/myproj/bin/targets/myble/app/apps/bletiny
Tutorial for more information on setting up your serial communications.</p>
<p><br></p>
<h3 id="connecting-with-your-app">Connecting with your app</h3>
-<p>Once you have a connection set up, you can connect to your device with <code>minicom -D /dev/tty.usbmodem<port> -b 115200</code> to run connect
-to the console of your app. </p>
-<p>To test and make sure that the Shell is running, first just hit <return>:</p>
+<p>Once you have a connection set up, you can connect to your device as follows: </p>
+<ul>
+<li>
+<p>On Mac OS and Linux platforms, you can run <code>minicom -D /dev/tty.usbserial-<port> -b 115200</code> to connect to the console of your app. Note that on Linux, the format of the port name is <code>/dev/ttyUSB<N></code>, where N is a number. </p>
+</li>
+<li>
+<p>On Windows, you can use a terminal application such as PuTTY to connect to the device. </p>
+<p>If you located your port from a MinGW terminal, the port name format is <code>/dev/ttyS<N></code>, where <code>N</code> is a number. You must map the port name to a Windows COM port: <code>/dev/ttyS<N></code> maps to <code>COM<N+1></code>. For example, <code>/dev/ttyS2</code> maps to <code>COM3</code>. </p>
+<p>You can also use the Windows Device Manager to locate the COM port.</p>
+</li>
+</ul>
+<p><br>
+To test and make sure that the Shell is running, first just hit <return>:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">3534: >
</pre></div>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6e0ec54d/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 7b2bc85..8ea6365 100644
--- a/develop/os/tutorials/arduino_zero/index.html
+++ b/develop/os/tutorials/arduino_zero/index.html
@@ -753,6 +753,7 @@ Error: Target not halted
<p><br>
To erase your board, start a debug session and enter the highlighted commands at the <code>(gdb)</code> prompts:</p>
+<p><strong>Note:</strong> 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>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt debug arduino_blinky
(gdb) mon at91samd chip-erase
chip erased
@@ -777,6 +778,8 @@ Run the <code>newt load arduino_boot</code> command again after erasing the boar
<h3 id="run-the-blinky-application"><a name="runimage"></a>Run the Blinky Application</h3>
<p>After you load the bootloader successfully onto your board, you can load and run the Blinky application. </p>
<p>Run the <code>newt run arduino_blinky 1.0.0</code> 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. </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. 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.
+<br></p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt run arduino_blinky 1.0.0
App image succesfully generated: ~/dev/myproj/bin/targets/arduino_blinky/app/apps/blinky/blinky.img
Loading app image into slot 1
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6e0ec54d/develop/os/tutorials/bletiny_project/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/bletiny_project/index.html b/develop/os/tutorials/bletiny_project/index.html
index 94b4bf7..a936099 100644
--- a/develop/os/tutorials/bletiny_project/index.html
+++ b/develop/os/tutorials/bletiny_project/index.html
@@ -627,13 +627,19 @@ $ newt load myble
If you haven't done so already, make sure you're familiar with the <a href="../../get_started/serial_access/">Serial Port Setup and Configuration</a>
section. </p>
<p><br></p>
-<p>You may use any terminal emulation program to communicate with the board. This tutorial shows a Minicom set up. </p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ minicom -D /dev/tty.usbserial-1a12 -b 115200
-</pre></div>
-
-
-<p><br></p>
-<p>When the Minicom screen comes up, type in <code>?</code></p>
+<p>Once you have a connection set up, you can connect to your device as follows:</p>
+<ul>
+<li>
+<p>On Mac OS and Linux platforms, you can run <code>minicom -D /dev/tty.usbserial-<port> -b 115200</code> to connect to the console of your app. Note that on Linux, the format of the port name is <code>/dev/ttyUSB<N></code>, where N is a number.</p>
+</li>
+<li>
+<p>On Windows, you can run <code>PuTTY</code> to connect to the device.</p>
+<p>If you located your port from a MinGW terminal, the port name format is <code>/dev/ttyS<N></code>, where <code>N</code> is a number. You must map the port name to a Windows COM port: <code>/dev/ttyS<N></code> maps to <code>COM<N+1></code>. For example, <code>/dev/ttyS2</code> maps to <code>COM3</code>.</p>
+<p>You can also use the Windows Device Manager to locate the COM port number.</p>
+</li>
+</ul>
+<p><br>
+This tutorial uses minicom. When the Minicom screen comes up, type in <code>?</code></p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">Welcome to minicom 2.7
OPTIONS:
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6e0ec54d/develop/os/tutorials/blinky_console/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/blinky_console/index.html b/develop/os/tutorials/blinky_console/index.html
index 516ddb3..c544883 100644
--- a/develop/os/tutorials/blinky_console/index.html
+++ b/develop/os/tutorials/blinky_console/index.html
@@ -669,12 +669,22 @@ Loading app image into slot 1
<p><br></p>
<h3 id="set-up-a-serial-connection">Set Up a Serial Connection</h3>
-<p>You'll need a Serial connection to see the output of your program. You can reference the <a href="../../get_started/serial_access/">Serial Port Setup</a>
-Tutorial for more information on setting up your serial communication.</p>
+<p>You'll need a Serial connection to see the output of your program. You can reference the <a href="../../get_started/serial_access/">Serial Port Setup</a> Tutorial for more information on setting up your serial communication.</p>
<p><br></p>
<h3 id="communicate-with-the-application">Communicate with the Application</h3>
-<p>Once you have a connection set up, run <code>minicom -D /dev/tty.usbserial<port> -b 115200</code> to connect to the application console.</p>
-<p>To test and make sure that the Shell is running, first just hit <return>:</p>
+<p>Once you have a connection set up, you can connect to your device as follows:</p>
+<ul>
+<li>
+<p>On Mac OS and Linux platforms, you can run <code>minicom -D /dev/tty.usbserial-<port> -b 115200</code> to connect to the console of your app. Note that on Linux, the format of the port name is <code>/dev/ttyUSB<N></code>, where N is a number.</p>
+</li>
+<li>
+<p>On Windows, you can use a terminal application such as PuTTY to connect to the device.</p>
+<p>If you located your port from a MinGW terminal, the port name format is <code>/dev/ttyS<N></code>, where <code>N</code> is a number. You must map the port name to a Windows COM port: <code>/dev/ttyS<N></code> maps to <code>COM<N+1></code>. For example, <code>/dev/ttyS2</code> maps to <code>COM3</code>.</p>
+<p>You can also use the Windows Device Manager to locate the COM port.</p>
+</li>
+</ul>
+<p><br>
+To test and make sure that the Shell is running, first just hit <return>:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">3534: >
</pre></div>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6e0ec54d/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 a0e803b..6c6fa1a 100644
--- a/develop/os/tutorials/blinky_primo/index.html
+++ b/develop/os/tutorials/blinky_primo/index.html
@@ -690,7 +690,9 @@ $
<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>
-<p><strong>Note:</strong> 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>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>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ JLinkExe -device nRF52 -speed 4000 -if SWD
SEGGER J-Link Commander V5.12c (Compiled Apr 21 2016 16:05:51)
DLL version V5.12c, compiled Apr 21 2016 16:05:45
@@ -718,6 +720,7 @@ $
<p><br></p>
<p>If you are using the OpenOCD debugger, run the <code>newt debug primoblinky</code> command and issue the highlighted command at the (gdb) prompt:</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>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$newt debug primoblinky
[~/dev/myproj/repos/apache-mynewt-core/hw/bsp/arduino_primo_nrf52/primo_debug.sh ~/dev/myproj/repos/apache-mynewt-core/hw/bsp/arduino_primo_nrf52 ~/dev/myproj/bin/targets/primoblinky/app/apps/blinky/blinky]
Open On-Chip Debugger 0.10.0-dev-snapshot (2017-03-28-11:24)
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6e0ec54d/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 00def05..259e88f 100644
--- a/develop/os/tutorials/blinky_stm32f4disc/index.html
+++ b/develop/os/tutorials/blinky_stm32f4disc/index.html
@@ -678,7 +678,9 @@ Loading app image into slot 1
<p>You should see the small green LD4 LED on the board blink!</p>
<p>Note: If the LED does not blink, try resetting your board.</p>
<p><br></p>
-<p><strong>Note:</strong> If you want to erase the flash and load the image again, start a debug session, and enter <code>mon stm32f2x mass_erase 0</code> at the gdb prompt:</p>
+<p>If you want to erase the flash and load the image again, start a debug session, and enter <code>mon stm32f2x mass_erase 0</code> at the gdb prompt:</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 stm32f4disc_blinky
[~/dev/myproj/repos/apache-mynewt-core/hw/bsp/stm32f4discovery/stm32f4discovery_debug.sh ~/dev/myproj/repos/apache-mynewt-core/hw/bsp/stm32f4discovery ~/dev/myproj/bin/targets/stm32f4disc_blinky/app/apps/blinky/blinky]
Open On-Chip Debugger 0.10.0
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6e0ec54d/develop/os/tutorials/nRF52/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/nRF52/index.html b/develop/os/tutorials/nRF52/index.html
index 2e95c97..483addb 100644
--- a/develop/os/tutorials/nRF52/index.html
+++ b/develop/os/tutorials/nRF52/index.html
@@ -681,7 +681,9 @@ Loading app image into slot 1
<p>You should see the LED1 on the board blink!</p>
<p>Note: If the LED does not blink, try resetting your board.</p>
<p><br></p>
-<p><strong>Note:</strong> If you want to erase the flash and load the image again, you can use JLinkExe to issue an <code>erase</code> command.</p>
+<p>If you want to erase the flash and load the image again, you can run <code>JLinkExe</code> to issue an <code>erase</code> command.</p>
+<p><strong>Note:</strong> On Windows: Run the <code>jlink</code> command with the same arguments from a Windows Command Prompt terminal.</p>
+<p><br></p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ JLinkExe -device nRF52 -speed 4000 -if SWD
SEGGER J-Link Commander V5.12c (Compiled Apr 21 2016 16:05:51)
DLL version V5.12c, compiled Apr 21 2016 16:05:45
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6e0ec54d/develop/os/tutorials/olimex/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/olimex/index.html b/develop/os/tutorials/olimex/index.html
index 82ba948..67815c5 100644
--- a/develop/os/tutorials/olimex/index.html
+++ b/develop/os/tutorials/olimex/index.html
@@ -682,7 +682,16 @@ Successfully loaded image.
</pre></div>
-<p>Run the <code>newt load olimex_blinky</code> command to load the blinky application image onto the board:</p>
+<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>
+<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>Click Install Driver.</li>
+<li>Run the <code>newt load boot_olimex</code> command again. </li>
+</ul>
+<p><br>
+Run the <code>newt load olimex_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 -v olimex_blinky
Loading app image into slot 1
Load command: ~/dev/myproj/repos/apache-mynewt-core/hw/bsp/olimex_stm32-e407_devboard/olimex_stm32-e407_devboard_download.sh ~/dev/myproj/repos/apache-mynewt-core/hw/bsp/olimex_stm32-e407_devboard ~/dev/myproj/bin/targets/olimex_blinky/app/apps/blinky/blinky
@@ -695,7 +704,10 @@ The LED should be blinking!</p>
<p><br>
Let's double check that it is indeed booting from flash and making the LED blink from the image in flash. Pull the USB cable off the Olimex JTAG adaptor, severing the debug connection to the JTAG port. Next power off the Olimex board by pulling out the USB cable from the board. Wait for a couple of seconds and plug the USB cable back to the board.</p>
<p>The LED light will start blinking again. Success!</p>
-<p><strong>Note #1:</strong> If you want to download the image to flash and a gdb session opened up, use <code>newt debug blinky</code>. Type <code>c</code> to continue inside the gdb session.</p>
+<p>If you want to download the image to flash and open a gdb session, use <code>newt debug blinky</code>. </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>
+Type <code>c</code> to continue inside the gdb session.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ newt debug blinky
Debugging with ~/dev/myproj/hw/bsp/olimex_stm32-e407_...
Debugging ~/dev/myproj/project/blinky/bin/blinky/blinky.elf
@@ -718,7 +730,7 @@ Let's double check that it is indeed booting from flash and making the LED blink
<p><br></p>
-<p><strong>Note #2:</strong> If you want to erase the flash and load the image again you may use the following commands from within gdb. <code>flash erase_sector 0 0 x</code> tells it to erase sectors 0 through x. When you ask it to display (in hex notation) the contents of the sector starting at location 'lma,' you should see all f's. The memory location 0x8000000 is the start or origin of the flash memory contents and is specified in the olimex_stm32-e407_devboard.ld linker script. The flash memory locations is specific to the processor.</p>
+<p>If you want to erase the flash and load the image again you may use the following commands from within gdb. <code>flash erase_sector 0 0 x</code> tells it to erase sectors 0 through x. When you ask it to display (in hex notation) the contents of the sector starting at location 'lma,' you should see all f's. The memory location 0x8000000 is the start or origin of the flash memory contents and is specified in the olimex_stm32-e407_devboard.ld linker script. The flash memory locations is specific to the processor.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> (gdb) monitor flash erase_sector 0 0 4
erased sectors 0 through 4 on flash bank 0 in 2.296712s
(gdb) monitor mdw 0x08000000 16
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6e0ec54d/develop/os/tutorials/pics/device_manager_ft232H.png
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/pics/device_manager_ft232H.png b/develop/os/tutorials/pics/device_manager_ft232H.png
new file mode 100755
index 0000000..ce7bd59
Binary files /dev/null and b/develop/os/tutorials/pics/device_manager_ft232H.png differ
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6e0ec54d/develop/os/tutorials/pics/device_manager_no_ft232H.png
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/pics/device_manager_no_ft232H.png b/develop/os/tutorials/pics/device_manager_no_ft232H.png
new file mode 100755
index 0000000..ab4c2d4
Binary files /dev/null and b/develop/os/tutorials/pics/device_manager_no_ft232H.png differ
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6e0ec54d/develop/os/tutorials/pics/putty.png
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/pics/putty.png b/develop/os/tutorials/pics/putty.png
new file mode 100755
index 0000000..63c5f10
Binary files /dev/null and b/develop/os/tutorials/pics/putty.png differ
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6e0ec54d/develop/os/tutorials/project-nrf52-slinky/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/project-nrf52-slinky/index.html b/develop/os/tutorials/project-nrf52-slinky/index.html
index 45e39f2..f180187 100644
--- a/develop/os/tutorials/project-nrf52-slinky/index.html
+++ b/develop/os/tutorials/project-nrf52-slinky/index.html
@@ -625,16 +625,31 @@ $
<p><br></p>
<h3 id="connect-newtmgr-with-the-board-using-a-serial-connection">Connect Newtmgr with the Board using a Serial Connection</h3>
<p>Set up a serial connection from your computer to the nRF52-DK board (See <a href="../../get_started/serial_access/">Serial Port Setup</a>). </p>
-<p>Locate the port, in the /dev directory on your computer, that the serial connection uses. It should be of the type <code>tty.usbserial-<some identifier></code>.</p>
+<p>Locate the port, in the /dev directory on your computer, that the serial connection uses. The format of the port name is platform dependent:</p>
+<ul>
+<li>Mac OS uses the format <code>tty.usbserial-<some identifier></code>.</li>
+<li>Linux uses the format <code>TTYUSB<N></code>, where <code>N</code> is a number. For example, TTYUSB2.</li>
+<li>
+<p>MinGW on Windows uses the format <code>ttyS<N></code>, where <code>N</code> is a number. You must map the port name to a Windows COM port: <code>/dev/ttyS<N></code> maps to <code>COM<N+1></code>. For example, <code>/dev/ttyS2</code> maps to <code>COM3</code>. </p>
+<p>You can also use the Windows Device Manager to find the COM port number.</p>
+</li>
+</ul>
+<p><br></p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ ls /dev/tty*usbserial*
/dev/tty.usbserial-1d11
$
</pre></div>
-<p><br>
-Setup a newtmgr connection profile for the serial port. For our example, the port is <code>/dev/tty.usbserial-1d11</code>. </p>
-<p>Run the <code>newtmgr conn add</code> command to define a newtmgr connection profile for the serial port. We name the connection profile <code>nrf52serial</code>. You will need to replace the <code>connstring</code> with the specific port for your serial connection. </p>
+<p><br></p>
+<p>Setup a newtmgr connection profile for the serial port. For our example, the port is <code>/dev/tty.usbserial-1d11</code>. </p>
+<p>Run the <code>newtmgr conn add</code> command to define a newtmgr connection profile for the serial port. We name the connection profile <code>nrf52serial</code>. </p>
+<p><strong>Note</strong>: </p>
+<ul>
+<li>You will need to replace the <code>connstring</code> with the specific port for your serial connection. </li>
+<li>On Windows, you must specify <code>COM<N+1></code> for the connstring if <code>/dev/ttyS<N></code> is the serial port.</li>
+</ul>
+<p><br></p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newtmgr conn add nrf52serial type=serial connstring=/dev/tty.usbserial-1d11
Connection profile nrf52serial successfully added
$
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6e0ec54d/develop/os/tutorials/project-sim-slinky/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/project-sim-slinky/index.html b/develop/os/tutorials/project-sim-slinky/index.html
index 299a828..6f598b2 100644
--- a/develop/os/tutorials/project-sim-slinky/index.html
+++ b/develop/os/tutorials/project-sim-slinky/index.html
@@ -502,7 +502,7 @@
</div>
<h2 id="project-sim-slinky">Project Sim Slinky</h2>
-<p>This tutorial shows you how to create, build and run the Slinky application and communicate with newtmgr for a simulated device.</p>
+<p>This tutorial shows you how to create, build and run the Slinky application and communicate with newtmgr for a simulated device. This is supported on Mac OS and Linux platforms.</p>
<p><br></p>
<h3 id="prerequisites">Prerequisites</h3>
<p>Meet the prerequisites listed in <a href="../project-slinky/">Project Slinky</a>.</p>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6e0ec54d/develop/os/tutorials/project-slinky/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/project-slinky/index.html b/develop/os/tutorials/project-slinky/index.html
index 0d18048..382ab33 100644
--- a/develop/os/tutorials/project-slinky/index.html
+++ b/develop/os/tutorials/project-slinky/index.html
@@ -505,7 +505,7 @@
<h3 id="available-tutorials">Available Tutorials</h3>
<p>Tutorials are available for the following boards:</p>
<ul>
-<li><a href="../../../os/tutorials/project-sim-slinky">Slinky on a simulated device</a>.</li>
+<li><a href="../../../os/tutorials/project-sim-slinky">Slinky on a simulated device</a>. This is supported on Mac OS and Linux platforms.</li>
<li><a href="../../../os/tutorials/project-nrf52-slinky">Slinky on a nRF52</a>.</li>
<li><a href="../../../os/tutorials/project-stm32-slinky">Slinky on an Olimex</a>.
<br></li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6e0ec54d/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 08d5e4d..86a65d7 100644
--- a/develop/os/tutorials/project-stm32-slinky/index.html
+++ b/develop/os/tutorials/project-stm32-slinky/index.html
@@ -639,7 +639,16 @@ $
<li>Connect the GND pin of the USB-TTL serial cable to the GND (Pin 2) of the UEXT connector on the board.</li>
</ul>
<p><br>
-Locate the port, in the /dev directory on your computer, that the serial connection uses. It should be of the type <code>tty.usbserial-<some identifier></code>.</p>
+Locate the port, in the /dev directory on your computer, that the serial connection uses. The format of the port name is platform dependent:</p>
+<ul>
+<li>Mac OS uses the format <code>tty.usbserial-<some identifier></code>.</li>
+<li>Linux uses the format <code>TTYUSB<N></code>, where <code>N</code> is a number. For example, TTYUSB2.</li>
+<li>
+<p>MinGW on Windows uses the format <code>ttyS<N></code>, where <code>N</code> is a number. You must map the port name to a Windows COM port: <code>/dev/ttyS<N></code> maps to <code>COM<N+1></code>. For example, <code>/dev/ttyS2</code> maps to <code>COM3</code>.</p>
+<p>You can also use the Windows Device Manager to find the COM port number.</p>
+</li>
+</ul>
+<p><br></p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ ls /dev/tty*usbserial*
/dev/tty.usbserial-1d13
$
@@ -648,7 +657,13 @@ $
<p><br>
Setup a newtmgr connection profile for the serial port. For our example, the port is <code>/dev/tty.usbserial-1d13</code>.</p>
-<p>Run the <code>newtmgr conn add</code> command to define a newtmgr connection profile for the serial port. We name the connection profile <code>stm32serial</code>. You will need to replace the <code>connstring</code> with the specific port for your serial connection.</p>
+<p>Run the <code>newtmgr conn add</code> command to define a newtmgr connection profile for the serial port. We name the connection profile <code>stm32serial</code>. </p>
+<p><strong>Note</strong>:</p>
+<ul>
+<li>You will need to replace the <code>connstring</code> with the specific port for your serial connection.</li>
+<li>On Windows, you must specify <code>COM<N+1></code> for the connstring if <code>/dev/ttyS<N></code> is the serial port.</li>
+</ul>
+<p><br></p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newtmgr conn add stm32serial type=serial connstring=/dev/tty.usbserial-1d13
Connection profile stm32serial successfully added
$
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6e0ec54d/develop/os/tutorials/rbnano2/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/rbnano2/index.html b/develop/os/tutorials/rbnano2/index.html
index 227d285..8a72861 100644
--- a/develop/os/tutorials/rbnano2/index.html
+++ b/develop/os/tutorials/rbnano2/index.html
@@ -655,6 +655,8 @@ $
<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><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
[~/dev/myproj/repos/apache-mynewt-core/hw/bsp/rb-nano2/rb-nano2_debug.sh ~/dev/myproj/repos/apache-mynewt-core/hw/bsp/rb-nano2 ~/dev/myproj/bin/targets/rbnano2_blinky/app/apps/blinky/blinky]
Open On-Chip Debugger 0.10.0-dev-snapshot (2017-03-28-11:24)
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6e0ec54d/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 6e66832..afc744e 100644
--- a/develop/os/tutorials/wi-fi_on_arduino/index.html
+++ b/develop/os/tutorials/wi-fi_on_arduino/index.html
@@ -657,7 +657,7 @@ $
<p><br></p>
<h3 id="load-the-wi-fi-application-image-onto-the-board">Load the Wi-Fi Application Image onto the Board</h3>
-<p>Run the <code>newt load arduino_wifi</code> command to load the wifi application onto the board:</p>
+<p>Run the <code>newt load mkr1000_wifi</code> command to load the wifi application onto the board:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt load mkr1000_wifi
Loading app image into slot 1
$
@@ -673,7 +673,18 @@ $
<br>
<p>
<br>
-Locate the port, in the /dev directory on your computer, that the serial connection uses. It should be of the type <code>tty.usbserial-<some identifier></code>.</p>
+<br>
+Locate the port, in the /dev directory on your computer, that the serial connection uses. The format of the port name is
+ platform dependent:</p>
+<ul>
+<li>Mac OS uses the format <code>tty.usbserial-<some identifier></code>.</li>
+<li>Linux uses the format <code>TTYUSB<N></code>, where <code>N</code> is a number. For example, TTYUSB2.</li>
+<li>
+<p>MinGW on Windows uses the format <code>ttyS<N></code>, where <code>N</code> is a number. You must map the port name to a Windows COM port: <code>/dev/ttyS<N></code> maps to <code>COM<N+1></code>. For example, <code>/dev/ttyS2</code> maps to <code>COM3</code>.</p>
+<p>You can also use the Windows Device Manager to find the COM port number.</p>
+</li>
+</ul>
+<p><br></p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ ls /dev/tty*usbserial*
/dev/tty.usbserial-1d13
$
@@ -682,6 +693,7 @@ $
<h3 id="start-wi-fi-via-console">Start Wi-Fi via console</h3>
<p>Use a terminal emulation program to communicate with the board over the serial port. This tutorial shows a Minicom set up. Run the minicom command with the serial port you located on your computer:</p>
+<p><strong>Note:</strong> On Windows, you can use the PuTTY application. </p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ minicom -D /dev/tty.usbserial-1d13 -b 115200
</pre></div>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6e0ec54d/develop/sitemap.xml
----------------------------------------------------------------------
diff --git a/develop/sitemap.xml b/develop/sitemap.xml
index 575d20f..513c011 100644
--- a/develop/sitemap.xml
+++ b/develop/sitemap.xml
@@ -4,7 +4,7 @@
<url>
<loc>http://mynewt.apache.org/</loc>
- <lastmod>2017-05-08</lastmod>
+ <lastmod>2017-05-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -13,7 +13,7 @@
<url>
<loc>http://mynewt.apache.org/pages/ble/</loc>
- <lastmod>2017-05-08</lastmod>
+ <lastmod>2017-05-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -22,7 +22,7 @@
<url>
<loc>http://mynewt.apache.org/quick-start/</loc>
- <lastmod>2017-05-08</lastmod>
+ <lastmod>2017-05-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -30,7 +30,7 @@
<url>
<loc>http://mynewt.apache.org/about/</loc>
- <lastmod>2017-05-08</lastmod>
+ <lastmod>2017-05-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -38,7 +38,7 @@
<url>
<loc>http://mynewt.apache.org/talks/</loc>
- <lastmod>2017-05-08</lastmod>
+ <lastmod>2017-05-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -46,7 +46,7 @@
<url>
<loc>http://mynewt.apache.org/download/</loc>
- <lastmod>2017-05-08</lastmod>
+ <lastmod>2017-05-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -54,7 +54,7 @@
<url>
<loc>http://mynewt.apache.org/community/</loc>
- <lastmod>2017-05-08</lastmod>
+ <lastmod>2017-05-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -62,7 +62,7 @@
<url>
<loc>http://mynewt.apache.org/events/</loc>
- <lastmod>2017-05-08</lastmod>
+ <lastmod>2017-05-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -71,7 +71,7 @@
<url>
<loc>http://mynewt.apache.org/os/introduction/</loc>
- <lastmod>2017-05-08</lastmod>
+ <lastmod>2017-05-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -83,7 +83,7 @@
<url>
<loc>http://mynewt.apache.org/os/get_started/vocabulary/</loc>
- <lastmod>2017-05-08</lastmod>
+ <lastmod>2017-05-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -123,19 +123,19 @@
<url>
<loc>http://mynewt.apache.org/faq/go_env/</loc>
- <lastmod>2017-05-08</lastmod>
+ <lastmod>2017-05-12</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/how_to_edit_docs/</loc>
- <lastmod>2017-05-08</lastmod>
+ <lastmod>2017-05-12</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/answers/</loc>
- <lastmod>2017-05-08</lastmod>
+ <lastmod>2017-05-12</lastmod>
<changefreq>daily</changefreq>
</url>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6e0ec54d/latest/faq/go_env/index.html
----------------------------------------------------------------------
diff --git a/latest/faq/go_env/index.html b/latest/faq/go_env/index.html
index 079529b..89739e2 100644
--- a/latest/faq/go_env/index.html
+++ b/latest/faq/go_env/index.html
@@ -458,9 +458,9 @@ Build and install the tool. The updated binary will be installed in the <strong>
<ul class="nav nav-pills" style="margin-bottom: 10px">
<li>
- <a href=../../newtmgr/install_linux/>
+ <a href=../../newtmgr/install_windows/>
<span class="fa fa-arrow-left"></span>
- Previous: Install Newtmgr On Linux
+ Previous: Install Newtmgr On Windows
</a>
</li>