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/14 21:26:48 UTC
[1/2] incubator-mynewt-site git commit: changed runtimeinc to
runtimeco in docs, updated install instructions for linux ,
blinky for stm32F4-discovery
Repository: incubator-mynewt-site
Updated Branches:
refs/heads/master 690d31307 -> 5ec12143e
changed runtimeinc to runtimeco in docs, updated install instructions for linux , blinky for stm32F4-discovery
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/189cb93a
Tree: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/tree/189cb93a
Diff: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/diff/189cb93a
Branch: refs/heads/master
Commit: 189cb93a7698627482269b6a721eb357ba745b3b
Parents: 690d313
Author: aditihilbert <ad...@runtime.io>
Authored: Fri May 5 14:24:44 2017 -0700
Committer: aditihilbert <ad...@runtime.io>
Committed: Fri May 5 14:24:44 2017 -0700
----------------------------------------------------------------------
docs/os/get_started/native_install_intro.md | 17 ++
docs/os/tutorials/blinky_stm32f4disc.md | 207 +++++++++++++++++++++++
docs/os/tutorials/pics/stm32f4_disc.jpg | Bin 0 -> 40575 bytes
3 files changed, 224 insertions(+)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/189cb93a/docs/os/get_started/native_install_intro.md
----------------------------------------------------------------------
diff --git a/docs/os/get_started/native_install_intro.md b/docs/os/get_started/native_install_intro.md
new file mode 100644
index 0000000..2cadfa1
--- /dev/null
+++ b/docs/os/get_started/native_install_intro.md
@@ -0,0 +1,17 @@
+# Native Installation
+
+This section shows you how to install tools on Mac OS and Linux platforms to develop, build, run, and debug Mynewt OS applications. You can build Mynewt OS applications to run as a native application on your computer or to run on your target board. These tools include:
+
+* Newt tool - Tool to create, build, load, and debug a mynewt target.
+
+ * See [Installing the Newt Tool on Mac OS](/newt/install/newt_mac.md) to install on Mac OS.
+ * See [Installing the Newt Tool on Linux](/newt/install/newt_linux.md) to install on Linux.
+
+
+<br>
+
+* Native toolchain - Native toolchain to build and run Mynewt OS as a native application on your computer.
+ (See [Installing Native Toolchain](/os/get_started/native_install.md)).
+
+* Cross toolchain for ARM - Cross toolchain for ARM to build and run a Mynewt OS application on a target board
+ (See [Installing Cross Tools for ARMs](/os/get_started/cross_tools.md)).
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/189cb93a/docs/os/tutorials/blinky_stm32f4disc.md
----------------------------------------------------------------------
diff --git a/docs/os/tutorials/blinky_stm32f4disc.md b/docs/os/tutorials/blinky_stm32f4disc.md
new file mode 100644
index 0000000..cf0e74e
--- /dev/null
+++ b/docs/os/tutorials/blinky_stm32f4disc.md
@@ -0,0 +1,207 @@
+## Blinky, your "Hello World!", on STM32F4-Discovery
+This tutorial shows you how to create, build, and run the Blinky application on the STM32F4-Discovery board.
+<br>
+
+<br>
+
+### Prerequisites
+
+* Meet the prerequisites listed in [Project Blinky](/os/tutorials/blinky.md).
+* Have a STM32F4-Discovery board.
+* Have a USB type A to Mini-B cable.
+* Install a patched version of OpenOCD 0.10.0 described in [Install OpenOCD](os/get_started/cross_tools/).
+
+### Create a Project
+Create a new project if you do not have an existing one. You can skip this step and proceed to [create the targets](#create_targets) if you already have a project created.
+
+Run the following commands to create a new project:
+
+```no-highlight
+ $ mkdir ~/dev
+ $ cd ~/dev
+ $ newt new myproj
+ Downloading project skeleton from apache/incubator-mynewt-blinky...
+ Installing skeleton in myproj...
+ Project myproj successfully created.
+ $ cd myproj
+ $ newt install
+ apache-mynewt-core
+ $
+```
+
+<br>
+
+### <a name="create_targets"></a>Create the Targets
+
+Create two targets for the STM32F4-Discovery board - one for the bootloader and one for the Blinky application.
+
+Run the following `newt target` commands, from your project directory, to create a bootloader target. We name the target `stm32f4disc_boot`:
+
+```no-highlight
+$ newt target create stm32f4disc_boot
+$ newt target set stm32f4disc_boot app=@apache-mynewt-core/apps/boot
+$ newt target set stm32f4disc_boot bsp=@apache-mynewt-core/hw/bsp/stm32f4discovery
+$ newt target set stm32f4disc_boot build_profile=optimized
+```
+
+<br>
+Run the following `newt target` commands to create a target for the Blinky application. We name the target `stm32f4disc_blinky`:
+
+```no-highlight
+$ newt target create stm32f4disc_blinky
+$ newt target set stm32f4disc_blinky app=apps/blinky
+$ newt target set stm32f4disc_blinky bsp=@apache-mynewt-core/hw/bsp/stm32f4discovery
+$ newt target set stm32f4disc_blinky build_profile=debug
+```
+<br>
+You can run the `newt target show` command to verify the target settings:
+
+```no-highlight
+$ newt target show
+targets/my_blinky_sim
+ app=apps/blinky
+ bsp=@apache-mynewt-core/hw/bsp/native
+ build_profile=debug
+targets/stm32f4disc_blinky
+ app=apps/blinky
+ bsp=@apache-mynewt-core/hw/bsp/stm32f4discovery
+ build_profile=debug
+targets/stm32f4disc_boot
+ app=@apache-mynewt-core/apps/boot
+ bsp=@apache-mynewt-core/hw/bsp/stm32f4discovery
+ build_profile=optimized
+```
+<br>
+
+### Build the Target Executables
+
+Run the `newt build stm32f4disc_boot` command to build the bootloader:
+
+```no-highlight
+$ newt build stm32f4disc_boot
+Building target targets/stm32f4disc_boot
+Compiling repos/apache-mynewt-core/boot/bootutil/src/image_ec.c
+Compiling repos/apache-mynewt-core/boot/bootutil/src/image_ec256.c
+Compiling repos/apache-mynewt-core/boot/bootutil/src/bootutil_misc.c
+Compiling repos/apache-mynewt-core/apps/boot/src/boot.c
+Compiling repos/apache-mynewt-core/boot/bootutil/src/image_rsa.c
+Compiling repos/apache-mynewt-core/boot/bootutil/src/image_validate.c
+Compiling repos/apache-mynewt-core/boot/bootutil/src/loader.c
+ ...
+
+Archiving sys_flash_map.a
+Archiving sys_mfg.a
+Archiving sys_sysinit.a
+Archiving util_mem.a
+Linking ~/dev/myproj/bin/targets/stm32f4disc_boot/app/apps/boot/boot.elf
+Target successfully built: targets/stm32f4disc_boot
+```
+
+<br>
+Run the `newt build stm32f4disc_blinky` command to build the Blinky application:
+
+```no-highlight
+$newt build stm32f4disc_blinky
+Building target targets/stm32f4disc_blinky
+Compiling apps/blinky/src/main.c
+Compiling repos/apache-mynewt-core/hw/bsp/stm32f4discovery/src/sbrk.c
+Compiling repos/apache-mynewt-core/hw/bsp/stm32f4discovery/src/system_stm32f4xx.c
+Compiling repos/apache-mynewt-core/hw/bsp/stm32f4discovery/src/hal_bsp.c
+Assembling repos/apache-mynewt-core/hw/bsp/stm32f4discovery/src/arch/cortex_m4/startup_STM32F40x.s
+Compiling repos/apache-mynewt-core/hw/cmsis-core/src/cmsis_nvic.c
+Compiling repos/apache-mynewt-core/hw/drivers/uart/src/uart.c
+Compiling repos/apache-mynewt-core/hw/drivers/uart/uart_hal/src/uart_hal.c
+Compiling repos/apache-mynewt-core/hw/hal/src/hal_common.c
+Compiling repos/apache-mynewt-core/hw/hal/src/hal_flash.c
+
+ ...
+
+Archiving sys_sysinit.a
+Archiving util_mem.a
+Linking ~/dev/myproj/bin/targets/stm32f4disc_blinky/app/apps/blinky/blinky.elf
+Target successfully built: targets/stm32f4disc_blinky
+```
+
+
+<br>
+
+### Sign and Create the Blinky Application Image
+
+Run the `newt create-image stm32f4disc_blinky 1.0.0` command to create and sign the application image. You may assign an arbitrary version (e.g. 1.0.0) to the image.
+
+```no-highlight
+$newt create-image stm32f4disc_blinky 1.0.0
+App image succesfully generated: ~/dev/myproj/bin/targets/stm32f4disc_blinky/app/apps/blinky/blinky.img
+```
+
+<br>
+
+### Connect to the Board
+
+Connect a USB type A to Mini-B cable from your computer to the port the board indicated on the diagram:
+
+<br>
+<br>
+
+
+<br>
+
+You should see the small PWR red LED light up.
+
+### Load the Bootloader and the Blinky Application Image
+
+Run the `newt load stm32f4disc_boot` command to load the bootloader onto the board:
+
+```no-highlight
+$newt load stm32f4disc_boot
+Loading bootloader
+```
+<br>
+Run the `newt load stm32f4disc_blinky` command to load the Blinky application image onto the board.
+```no-highlight
+$newt load stm32f4disc_blinky
+Loading app image into slot 1
+```
+
+You should see the small green LD4 LED on the board blink!
+
+Note: If the LED does not blink, try resetting your board.
+
+<br>
+
+**Note:** If you want to erase the flash and load the image again, start a debug session, and enter `mon stm32f2x mass_erase 0` at the gdb prompt:
+```no-highlight
+$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
+Licensed under GNU GPL v2
+For bug reports, read
+ http://openocd.org/doc/doxygen/bugs.html
+Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
+adapter speed: 2000 kHz
+adapter_nsrst_delay: 100
+none separate
+Info : Unable to match requested speed 2000 kHz, using 1800 kHz
+Info : Unable to match requested speed 2000 kHz, using 1800 kHz
+Info : clock speed 1800 kHz
+Info : STLINK v2 JTAG v25 API v2 SWIM v14 VID 0x0483 PID 0x374B
+Info : using stlink api v2
+Info : Target voltage: 2.881129
+Info : stm32f4x.cpu: hardware has 6 breakpoints, 4 watchpoints
+target halted due to debug-request, current mode: Thread
+
+ ...
+
+Reading symbols from ~/dev/myproj/bin/targets/stm32f4disc_blinky/app/apps/blinky/blinky.elf...done.
+target halted due to debug-request, current mode: Thread
+xPSR: 0x41000000 pc: 0x08021e90 psp: 0x20002290
+Info : accepting 'gdb' connection on tcp/3333
+Info : device id = 0x10076413
+Info : flash size = 1024kbytes
+0x08021e90 in __WFI () at repos/apache-mynewt-core/hw/cmsis-core/src/ext/core_cmInstr.h:342
+342 __ASM volatile ("wfi");
+(gdb) mon stm32f2x mass_erase 0
+stm32x mass erase complete
+stm32x mass erase complete
+(gdb)
+```
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/189cb93a/docs/os/tutorials/pics/stm32f4_disc.jpg
----------------------------------------------------------------------
diff --git a/docs/os/tutorials/pics/stm32f4_disc.jpg b/docs/os/tutorials/pics/stm32f4_disc.jpg
new file mode 100755
index 0000000..cbed05f
Binary files /dev/null and b/docs/os/tutorials/pics/stm32f4_disc.jpg differ
[2/2] incubator-mynewt-site git commit: This closes #179 and #180.
Added instructions for installing tools including newt on Windows This closes
#182. Tell Windows user to change vers to 0-dev to get apache-mynewt-core
master branch.
Posted by ad...@apache.org.
This closes #179 and #180. Added instructions for installing tools including newt on Windows
This closes #182. Tell Windows user to change vers to 0-dev to get apache-mynewt-core master branch.
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/5ec12143
Tree: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/tree/5ec12143
Diff: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/diff/5ec12143
Branch: refs/heads/master
Commit: 5ec12143e5822e47a7475d108d6b2454166af52b
Parents: 189cb93
Author: aditihilbert <ad...@runtime.io>
Authored: Fri May 12 12:37:57 2017 -0700
Committer: aditihilbert <ad...@runtime.io>
Committed: Sun May 14 14:26:06 2017 -0700
----------------------------------------------------------------------
docs/newt/install/newt_windows.md | 160 +++++++++++++++++++
docs/newtmgr/install_windows.md | 68 ++++++++
.../os/tutorials/pics/device_manager_ft232H.png | Bin 0 -> 67817 bytes
.../tutorials/pics/device_manager_no_ft232H.png | Bin 0 -> 67365 bytes
docs/os/tutorials/pics/putty.png | Bin 0 -> 56099 bytes
5 files changed, 228 insertions(+)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/5ec12143/docs/newt/install/newt_windows.md
----------------------------------------------------------------------
diff --git a/docs/newt/install/newt_windows.md b/docs/newt/install/newt_windows.md
new file mode 100644
index 0000000..5b9359f
--- /dev/null
+++ b/docs/newt/install/newt_windows.md
@@ -0,0 +1,160 @@
+## Installing Newt on Windows
+
+You 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 [Mynewt newt git repository](https://github.com/apache/incubator-mynewt-newt). The tool is written in Go (golang).
+
+In 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.
+
+This guide shows you how to perform the following:
+
+1. Install MSYS2/MinGW.
+2. Install Git.
+3. Install Go.
+4. Setup the Go environment.
+5. Download the source, build, and install the newt tool.
+
+<br>
+### Step 1: Installing MSYS2/MinGW
+MSYS2/MinGW provides a bash shell and tools to build applications that run on Windows. It includes three subsystems:
+
+* MSYS2 toolchain to build POSIX applications that run on Windows.
+* MinGW32 toolchains to build 32 bit native Windows applications.
+* MinGW64 toolchains to build 64 bit native Windows applications.
+
+The 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.
+
+To install and setup MSYS2 and MinGW:
+
+1. Download and run the [MSYS2 installer](http://www.msys2.org). Select the 64 bit version if you are running on a 64 bit platform. Follow the prompts and check the `Run MSYS2 now` checkbox on the `Installation Complete` dialog.
+2. In the MSYS2 terminal, run the `pacman -Syuu` command. If you get a message to run the update again, close the terminal and run the `pacman -Syuu` command in a new terminal.
+
+ To start a new MSYS2 terminal, select the "MSYS2 MSYS" application from the Windows start menu.
+
+3. Add a new user variable named **MSYS2_PATH_TYPE** and set the value to **inherit** in your Windows environment. This enables the MSYS2 and MinGW bash to inherit your Windows user **Path** values.
+
+ To add the variable, select properties for your computer > Advanced system settings > Environment Variables > New
+
+4. Run the `pacman -Su vim` command to install the vim editor.
+
+ **Note:**You can also use a Windows editor. You can access your files from the **C:\<msys-install-folder>\home\<username>** folder, where **msys-install-folder** is the folder you installed MSYS2 in. For example, if you installed MSYS2 in the **msys64** folder, your files are stored in **C:\msys64\home\<username>**
+
+You will need to start a MinGW terminal to run the commands specified in the Mynewt documentation and tutorials. To start a MinGW terminal, select the "MSYS2 Mingw" application from the start Menu (you can use either MinGW32 or MinGW64).
+In Windows, we use the MingGW subsystem to build Mynewt tools and applications.
+
+### Step 2: Installing Git for Windows
+Download and install [Git for Windows](https://git-for-windows.github.io) if it is not already installed.
+
+
+### Step 3: Installing Go
+Download and install the latest version of [Go](https://golang.org/dl/). Newt requires Go version 1.7 or higher.
+
+###Step 4: Setting Up Your Go Environment
+
+This 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 **src**, **pkg** and **bin**:
+
+* src contains Go source files organized into packages (one package per directory)
+* pkg contains package objects
+* bin contains the Go application executables that Go builds and installs.
+
+The **GOPATH** environment variable specifies the location of your workspace. To setup this workspace environment, create a **dev** directory and then a **go** directory under it. Set the GOPATH environment variable to this directory where you will clone the newt repository.
+
+Start up a MinGW terminal and run the following commands to set up your Go workspace:
+
+```no-highlight
+$ cd $HOME
+$ mkdir -p dev/go
+$ cd dev/go
+$ export GOPATH=`pwd`
+```
+<br>
+Add the following export statements to your ~/.bash_profile file and source the file:
+```no-highlight
+export GOPATH=$HOME/dev/go
+export PATH=$GOPATH/bin:$PATH
+```
+<br>
+
+###Step 5: Downloading the Source and Installing the Newt Tool
+
+The newt Go package is **mynewt.apache.org/newt/newt** and is stored in the [Apache Mynewt newt tool repository mirrored on github](https://github.com/apache/incubator-mynewt-newt). We use the `go get` command to download the source, build, and install the newt tool binary in the **$GOPATH/bin** directory.
+
+<br>
+Download the newt package source and install the tool:
+
+```no-highlight
+$cd $GOPATH
+$go get mynewt.apache.org/newt/newt
+$cd $GOPATH/src/mynewt.apache.org/newt
+$ls
+DISCLAIMER RELEASE_NOTES.md util
+INSTALLING.md build.sh viper
+LICENSE newt yaml
+NOTICE newtmgr
+README.md newtvm
+```
+<br>
+Check that the newt tool is installed and it is in your path:
+
+```no-highlight
+$ls go/bin
+$ ls bin/newt
+bin/newt
+$which go
+/home/<user>/dev/go/bin/newt
+$ newt version
+Apache Newt (incubating) version: 1.0.0-dev
+```
+<br>
+Get information about the newt tool:
+
+```no-highlight
+$newt
+Newt allows you to create your own embedded application based on the Mynewt
+operating system. Newt provides both build and package management in a single
+tool, which allows you to compose an embedded application, and set of
+projects, and then build the necessary artifacts from those projects. For more
+information on the Mynewt operating system, please visit
+https://mynewt.apache.org/.
+
+Please use the newt help command, and specify the name of the command you want
+help for, for help on how to use a specific command
+
+Usage:
+ newt [flags]
+ newt [command]
+
+Examples:
+ newt
+ newt help [<command-name>]
+ For help on <command-name>. If not specified, print this message.
+
+Available Commands:
+ build Build one or more targets
+ clean Delete build artifacts for one or more targets
+ create-image Add image header to target binary
+ debug Open debugger session to target
+ info Show project info
+ install Install project dependencies
+ load Load built target to board
+ mfg Manufacturing flash image commands
+ new Create a new project
+ pkg Create and manage packages in the current workspace
+ run build/create-image/download/debug <target>
+ size Size of target components
+ sync Synchronize project dependencies
+ target Commands to create, delete, configure, and query targets
+ test Executes unit tests for one or more packages
+ upgrade Upgrade project dependencies
+ vals Display valid values for the specified element type(s)
+ version Display the Newt version number
+
+Flags:
+ -h, --help Help for newt commands
+ -j, --jobs int Number of concurrent build jobs (default 4)
+ -l, --loglevel string Log level (default "WARN")
+ -o, --outfile string Filename to tee output to
+ -q, --quiet Be quiet; only display error output
+ -s, --silent Be silent; don't output anything
+ -v, --verbose Enable verbose output when executing commands
+
+Use "newt [command] --help" for more information about a command.
+```
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/5ec12143/docs/newtmgr/install_windows.md
----------------------------------------------------------------------
diff --git a/docs/newtmgr/install_windows.md b/docs/newtmgr/install_windows.md
new file mode 100644
index 0000000..6ec23f1
--- /dev/null
+++ b/docs/newtmgr/install_windows.md
@@ -0,0 +1,68 @@
+## Installing Newtmgr on Windows
+You can build and install the newtmgr tool from the latest source on the master branch. Newtmgr is a Go (golang) package. This guide shows you how to install the tool from source. It assumes that you already installed the [newt tool on Windows](/newt/install/newt_windows/) and have the Windows development environment and Go workspace set up.
+
+###Downloading and Installing the Newtmgr Tool
+The newtmgr Go package is **mynewt.apache.org/newtmgr/newtmgr**. It is stored in the [Apache Mynewt newtmgr tool repository mirrored on github](https://github.com/apache/incubator-mynewt-newtmgr).
+
+
+Run the `go get` command, from your Go workspace, to download, build, and install the newtmgr tool:
+
+```no-highlight
+$cd $GOPATH
+$go get mynewt.apache.org/newtmgr/newtmgr
+$cd $GOPATH/src/mynewt.apache.org/newtmgr
+$ls
+DISCLAIMER NOTICE newtmgr
+LICENSE README.md nmxact
+$git status
+On branch master
+Your branch is up-to-date with 'origin/master'.
+
+nothing to commit, working directory clean
+```
+<br>
+Check that the newtmgr binary is installed and you are using the one from **$GOPATH/bin**:
+
+```no-highlight
+$ls $GOPATH/bin/newtmgr
+~/dev/go/bin/newtmgr
+$which newt
+~/dev/go/bin/newtmgr
+```
+<br>
+Get information about the newtmgr tool:
+
+```no-highlight
+$newtmgr
+Newtmgr helps you manage remote devices running the Mynewt OS
+
+Usage:
+ newtmgr [flags]
+ newtmgr [command]
+
+Available Commands:
+ config Read or write config value on target
+ conn Manage newtmgr connection profiles
+ crash Send crash command to remote endpoint using newtmgr
+ datetime Manage datetime on the device
+ echo Send data to remote endpoint using newtmgr, and receive data back
+ fs Access files on device
+ help Help about any command
+ image Manage images on remote instance
+ log Handles log on remote instance
+ mpstat Read mempool statistics from a remote endpoint
+ reset Performs a soft reset of target device
+ run Run procedures on remote device
+ stat Read statistics from a remote endpoint
+ taskstat Read statistics from a remote endpoint
+
+Flags:
+ -c, --conn string connection profile to use.
+ -n, --devicename string name of target BLE device; overrides profile setting
+ -h, --help help for newtmgr
+ -l, --loglevel string log level to use (default "info")
+ -t, --timeout float timeout in seconds (partial seconds allowed) (defaul t 10)
+ -r, --tries int total number of tries in case of timeout (default 1)
+
+Use "newtmgr [command] --help" for more information about a command.
+```
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/5ec12143/docs/os/tutorials/pics/device_manager_ft232H.png
----------------------------------------------------------------------
diff --git a/docs/os/tutorials/pics/device_manager_ft232H.png b/docs/os/tutorials/pics/device_manager_ft232H.png
new file mode 100755
index 0000000..ce7bd59
Binary files /dev/null and b/docs/os/tutorials/pics/device_manager_ft232H.png differ
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/5ec12143/docs/os/tutorials/pics/device_manager_no_ft232H.png
----------------------------------------------------------------------
diff --git a/docs/os/tutorials/pics/device_manager_no_ft232H.png b/docs/os/tutorials/pics/device_manager_no_ft232H.png
new file mode 100755
index 0000000..ab4c2d4
Binary files /dev/null and b/docs/os/tutorials/pics/device_manager_no_ft232H.png differ
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/5ec12143/docs/os/tutorials/pics/putty.png
----------------------------------------------------------------------
diff --git a/docs/os/tutorials/pics/putty.png b/docs/os/tutorials/pics/putty.png
new file mode 100755
index 0000000..63c5f10
Binary files /dev/null and b/docs/os/tutorials/pics/putty.png differ