http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/2c998465/chapter1/project1/index.html ---------------------------------------------------------------------- diff --git a/chapter1/project1/index.html b/chapter1/project1/index.html deleted file mode 100644 index e7338ea..0000000 --- a/chapter1/project1/index.html +++ /dev/null @@ -1,1377 +0,0 @@ -<!DOCTYPE html> -<!--[if IE 8]><html class="no-js lt-ie9" lang="en" > <![endif]--> -<!--[if gt IE 8]><!--> <html class="no-js" lang="en" > <!--<![endif]--> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1.0"> - - <title>Blinky, The First Project - Mynewt</title> - - - <link rel="shortcut icon" href="../../img/favicon.ico"> - - - <link href='https://fonts.googleapis.com/css?family=Lato:400,700|Roboto+Slab:400,700|Inconsolata:400,700' rel='stylesheet' type='text/css'> - - <link rel="stylesheet" href="../../css/theme.css" type="text/css" /> - <link rel="stylesheet" href="../../css/theme_extra.css" type="text/css" /> - <link rel="stylesheet" href="../../css/highlight.css"> - <link href="../../extra.css" rel="stylesheet"> - - - <script> - // Current page data - var mkdocs_page_name = "Blinky, The First Project"; - </script> - - <script src="../../js/jquery-2.1.1.min.js"></script> - <script src="../../js/modernizr-2.8.3.min.js"></script> - <script type="text/javascript" src="../../js/highlight.pack.js"></script> - <script src="../../js/theme.js"></script> - - -</head> - -<body class="wy-body-for-nav" role="document"> - - <div class="wy-grid-for-nav"> - - - <nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav"> - <div class="wy-side-nav-search"> - <a href="../.." class="icon icon-home"> Mynewt</a> - <div role="search"> - <form id ="rtd-search-form" class="wy-form" action="../../search.html" method="get"> - <input type="text" name="q" placeholder="Search docs" /> - </form> -</div> - </div> - - <div class="wy-menu wy-menu-vertical" data-spy="affix" role="navigation" aria-label="main navigation"> - <ul class="current"> - - <li> - <li class="toctree-l1 "> - <a class="" href="../..">Home</a> - - </li> -<li> - - <li> - <ul class="subnav"> - <li><span>Chapter1 - Get Started</span></li> - - - - <li class="toctree-l1 "> - <a class="" href="../newt_concepts/">Newt Concepts</a> - - </li> - - - - <li class="toctree-l1 current"> - <a class="current" href="./">Blinky, The First Project</a> - - <ul> - - <li class="toctree-l3"><a href="#blinky-the-first-project">Blinky, the First Project</a></li> - - <li><a class="toctree-l4" href="#objective">Objective</a></li> - - <li><a class="toctree-l4" href="#what-you-need">What you need</a></li> - - <li><a class="toctree-l4" href="#access-to-the-apache-repo">Access to the Apache repo</a></li> - - <li><a class="toctree-l4" href="#getting-your-mac-ready">Getting your Mac Ready</a></li> - - <li><a class="toctree-l4" href="#getting-your-ubuntu-machine-ready">Getting your Ubuntu machine Ready</a></li> - - <li><a class="toctree-l4" href="#getting-your-windows-machine-ready">Getting your Windows machine Ready</a></li> - - <li><a class="toctree-l4" href="#building-test-code-on-simulator">Building test code on simulator</a></li> - - <li><a class="toctree-l4" href="#building-test-code-on-simulator-on-windows-machine">Building test code on simulator on Windows machine</a></li> - - <li><a class="toctree-l4" href="#using-sram-to-make-led-blink">Using SRAM to make LED blink</a></li> - - <li><a class="toctree-l4" href="#using-flash-to-make-led-blink">Using flash to make LED blink</a></li> - - - </ul> - - </li> - - - - <li class="toctree-l1 "> - <a class="" href="../how_to_edit_docs/">How to edit docs</a> - - </li> - - - - <li class="toctree-l1 "> - <a class="" href="../try_markdown/">Sample doc to edit</a> - - </li> - - - </ul> -<li> - - <li> - <ul class="subnav"> - <li><span>Chapter2 - Get Acclimated</span></li> - - - - <li class="toctree-l1 "> - <a class="" href="../../chapter2/vocabulary/">Understanding Newt Terms</a> - - </li> - - - - <li class="toctree-l1 "> - <a class="" href="../../chapter2/project2/">Project 2</a> - - </li> - - - - <li class="toctree-l1 "> - <a class="" href="../../chapter2/project3/">Project 3</a> - - </li> - - - </ul> -<li> - - <li> - <ul class="subnav"> - <li><span>Chapter3 - Newt Tool</span></li> - - - - <li class="toctree-l1 "> - <a class="" href="../../chapter3/newt_ops/">Command structure</a> - - </li> - - - - <li class="toctree-l1 "> - <a class="" href="../../chapter3/newt_tool_reference/">Command list</a> - - </li> - - - </ul> -<li> - - <li> - <ul class="subnav"> - <li><span>Chapter4 - Newt OS</span></li> - - - - <li class="toctree-l1 "> - <a class="" href="../../chapter4/mynewt_os/">Overview</a> - - </li> - - - - <li class="toctree-l1 "> - <a class="" href="../../chapter4/context_switch/">Scheduler/Context Switching</a> - - </li> - - - - <li class="toctree-l1 "> - <a class="" href="../../chapter4/time/">Time</a> - - </li> - - - - <li class="toctree-l1 "> - <a class="" href="../../chapter4/task/">Tasks</a> - - </li> - - - - <li class="toctree-l1 "> - <a class="" href="../../chapter4/event_queue/">Event Queues</a> - - </li> - - - - <li class="toctree-l1 "> - <a class="" href="../../chapter4/semaphore/">Semaphores</a> - - </li> - - - - <li class="toctree-l1 "> - <a class="" href="../../chapter4/mutex/">Mutexes</a> - - </li> - - - - <li class="toctree-l1 "> - <a class="" href="../../chapter4/memory_pool/">Memory Pools</a> - - </li> - - - - <li class="toctree-l1 "> - <a class="" href="../../chapter4/heap/">Heap</a> - - </li> - - - - <li class="toctree-l1 "> - <a class="" href="../../chapter4/mbufs/">Mbufs</a> - - </li> - - - - <li class="toctree-l1 "> - <a class="" href="../../chapter4/sanity/">Sanity</a> - - </li> - - - - <li class="toctree-l1 "> - <a class="" href="../../chapter4/port_os/">Porting to other Platforms</a> - - </li> - - - </ul> -<li> - - <li> - <ul class="subnav"> - <li><span>Chapter5 - Modules</span></li> - - - - <li class="toctree-l1 "> - <a class="" href="../../chapter5/console/">Console</a> - - </li> - - - - <li class="toctree-l1 "> - <a class="" href="../../chapter5/shell/">Shell</a> - - </li> - - - - <li class="toctree-l1 "> - <a class="" href="../../chapter5/bootloader/">Bootloader</a> - - </li> - - - - <li class="toctree-l1 "> - <a class="" href="../../chapter5/filesystem/">File System</a> - - </li> - - - - <li class="toctree-l1 "> - <a class="" href="../../chapter5/testutil/">Test Utilities</a> - - </li> - - - </ul> -<li> - - <li> - <ul class="subnav"> - <li><span>Chapter6 - Packaging it</span></li> - - - - <li class="toctree-l1 "> - <a class="" href="../../chapter6/dist/">Creating Packages</a> - - </li> - - - </ul> -<li> - - </ul> - </div> - - </nav> - - <section data-toggle="wy-nav-shift" class="wy-nav-content-wrap"> - - - <nav class="wy-nav-top" role="navigation" aria-label="top navigation"> - <i data-toggle="wy-nav-top" class="fa fa-bars"></i> - <a href="../..">Mynewt</a> - </nav> - - - <div class="wy-nav-content"> - <div class="rst-content"> - <div role="navigation" aria-label="breadcrumbs navigation"> - <ul class="wy-breadcrumbs"> - <li><a href="../..">Docs</a> »</li> - - - - <li>Chapter1 - Get Started »</li> - - - - <li>Blinky, The First Project</li> - <li class="wy-breadcrumbs-aside"> - - </li> - </ul> - <hr/> -</div> - <div role="main"> - <div class="section"> - - <h2 id="blinky-the-first-project">Blinky, the First Project<a class="headerlink" href="#blinky-the-first-project" title="Permanent link">¶</a></h2> -<h3 id="objective">Objective<a class="headerlink" href="#objective" title="Permanent link">¶</a></h3> -<p>We will show you how you can use eggs from a nest on Mynewt to make an LED on a target board blink. We will call it <strong> Project Blinky</strong>. The goals of this tutorial are threefold:</p> -<ol> -<li>First, you will learn how to set up your environment to be ready to use Mynewt OS and newt tool. </li> -<li>Second, we will walk you through a download of eggs for building and testing <a href="#building-test-code-on-simulator">on a simulated target</a> on a non-Windows machine.</li> -<li>Third, you will download eggs and use tools to create a runtime image for a board to make its LED blink. You have two choices here - you can <a href="#using-sram-to-make-led-blink">download an image to SRAM</a> or you can <a href="#using-flash-to-make-led-blink">download it to flash</a>.</li> -</ol> -<p><strong> Time Requirement</strong>: Allow yourself a couple of hours for this project if you are relatively new to embedded systems and playing with development boards. Those jumpers can be pesky!</p> -<h3 id="what-you-need">What you need<a class="headerlink" href="#what-you-need" title="Permanent link">¶</a></h3> -<ol> -<li>STM32-E407 development board from Olimex. You can order it from <a href="http://www.mouser.com/ProductDetail/Olimex-Ltd/STM32-E407/?qs=UN6GZl1KCcit6Ye0xmPO4A%3D%3D";>http://www.mouser.com</a>, <a href="http://www.digikey.com/product-detail/en/STM32-E407/1188-1093-ND/3726951";>http://www.digikey.com</a>, and other places.</li> -<li>ARM-USB-TINY-H connector with JTAG interface for debugging ARM microcontrollers (comes with the ribbon cable to hook up to the board)</li> -<li>USB A-B type cable to connect the debugger to your personal computer</li> -<li>Personal Computer</li> -</ol> -<p>The instructions assume the user is using a Bourne-compatible shell (e.g. bash or zsh) on your computer. You may already have some of the required packages on your machine. In that -case, simply skip the corresponding installation step in the instructions under <a href="./#getting-your-mac-ready">Getting your Mac Ready</a> or <a href="./#getting-your-ubuntu-machine-ready">Getting your Ubuntu machine Ready</a> or <a href="#getting-your-windows-machine-ready">Getting your Windows machine Ready</a>. While the given instructions should work on other versions, they have been tested for the three specific releases of operating systems noted here:</p> -<ul> -<li>Mac: OS X Yosemite Version 10.10.5</li> -<li>Linux: Ubuntu 14.10 (Utopic Unicorn)</li> -<li>Windows: Windows 10</li> -</ul> -<h3 id="access-to-the-apache-repo">Access to the Apache repo<a class="headerlink" href="#access-to-the-apache-repo" title="Permanent link">¶</a></h3> -<ul> -<li> -<p>Get an account on Apache. You do not need a committer account to view the website or clone the repository but you need it to push changes to it.</p> -</li> -<li> -<p>The latest codebase for the Mynewt OS is on the master branch at https://git-wip-us.apache.org/repos/asf/incubator-mynewt-larva.git</p> -</li> -<li> -<p>The latest codebase for the Newt tool is on the master branch at https://git-wip-us.apache.org/repos/asf/incubator-mynewt-newt.git</p> -</li> -</ul> -<p>The following shows how to clone a Mynewt OS code repository:</p> -<ul> -<li> -<p>Non Committers</p> -<pre><code>$ git clone http://git-wip-us.apache.org/repos/asf/incubator-mynewt-larva.git -</code></pre> -</li> -<li> -<p>Committers</p> -<pre><code>$ git clone https://git-wip-us.apache.org/repos/asf/incubator-mynewt-larva.git -</code></pre> -</li> -</ul> -<h3 id="getting-your-mac-ready">Getting your Mac Ready<a class="headerlink" href="#getting-your-mac-ready" title="Permanent link">¶</a></h3> -<h4 id="installing-homebrew-to-ease-installs-on-os-x">Installing Homebrew to ease installs on OS X<a class="headerlink" href="#installing-homebrew-to-ease-installs-on-os-x" title="Permanent link">¶</a></h4> -<ul> -<li> -<p>Do you have Homebrew? If not, open a terminal on your Mac and paste the following at a Terminal prompt. It will ask you for your sudo password.</p> -<pre><code>$ ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)" -</code></pre> -<p>Alternatively, you can just extract (or <code>git clone</code>) Homebrew and install it to <code>/usr/local</code>.</p> -</li> -</ul> -<h4 id="installing-go">Installing Go<a class="headerlink" href="#installing-go" title="Permanent link">¶</a></h4> -<ul> -<li> -<p>The directory structure must be first readied for using Go. Go code must be kept inside a workspace. A workspace is a directory hierarchy with three directories at its root:</p> -<ul> -<li> -<p>src contains Go source files organized into packages (one package per directory),</p> -</li> -<li> -<p>pkg contains package objects, and</p> -</li> -<li> -<p>bin contains executable commands.</p> -</li> -</ul> -<p>The GOPATH environment variable specifies the location of your workspace. First create a 'dev' directory and then a 'go' directory under it. Set the GOPATH environment variable to this directory where you will soon clone the newt tool repository.</p> -<pre><code>$ cd $HOME -$ mkdir -p dev/go -$ cd dev/go -$ export GOPATH=`pwd` -</code></pre> -<p>Note that you need to add export statements to ~/.bash_profile to export variables permanently. Don't forget to source the file for the change to go into effect.</p> -<pre><code>$ vi ~/.bash_profile -$ source ~/.bash_profile -</code></pre> -</li> -<li> -<p>Next you will use Homebrew to install Go. The summary message at the end of the installation should indicate that it is installed in the /usr/local/Cellar/go/ directory. You will use the Go command 'install' to compile and install packages (called eggs in the Mynewt world) and dependencies. </p> -<pre><code>$ brew install go -==> -... -... -==> *Summary* -ðº /usr/local/Cellar/go/1.5.1: 5330 files, 273M -</code></pre> -<p>Alternatively, you can download the Go package directly from (https://golang.org/dl/) instead of brewing it. Install it in /usr/local directory.</p> -</li> -</ul> -<h4 id="creating-local-repository">Creating local repository<a class="headerlink" href="#creating-local-repository" title="Permanent link">¶</a></h4> -<ul> -<li> -<p>You are ready to download the newt tool repository. You will use Go to copy the directory (currently the asf incubator directory). Be patient as it may take a minute or two. Check the directories installed.</p> -<pre><code>$ go get git-wip-us.apache.org/repos/asf/incubator-mynewt-newt.git/newt -$ ls - bin pkg src -$ ls src -git-wip-us.apache.org github.com gopkg.in -</code></pre> -</li> -<li> -<p>Check that newt.go is in place.</p> -<pre><code>$ ls $GOPATH/src/git-wip-us.apache.org/repos/asf/incubator-mynewt-newt.git/newt -Godeps README.md coding_style.txt newt.go -LICENSE cli design.txt -</code></pre> -</li> -</ul> -<h4 id="building-the-newt-tool">Building the Newt tool<a class="headerlink" href="#building-the-newt-tool" title="Permanent link">¶</a></h4> -<ul> -<li> -<p>You will use Go to run the newt.go program to build the newt tool. The command used is <code>go install</code> which compiles and writes the resulting executable to an output file named <code>newt</code>. It installs the results along with its dependencies in $GOPATH/bin.</p> -<pre><code>$ cd $GOPATH/src/git-wip-us.apache.org/repos/asf/incubator-mynewt-newt.git/newt -$ go install -$ ls "$GOPATH"/bin/ -godep incubator-mynewt-newt.git newt -</code></pre> -</li> -<li> -<p>Try running newt using the compiled binary. For example, check for the version number by typing 'newt version'. See all the possible commands available to a user of newt by typing 'newt -h'.</p> -</li> -</ul> -<p>Note: If you are going to be be modifying the newt tool itself often and wish to compile the program every time you call it, you may want to store the command in a variable in your .bash_profile. So type in <code>export newt="go run $GOPATH/src/git-wip-us.apache.org/repos/asf/incubator-mynewt-newt.git/newt/newt/go"</code> in your .bash_profile and execute it by calling <code>$newt</code> at the prompt instead of <code>newt</code>. Here, you use <code>go run</code> which runs the compiled binary directly without producing an executable. Don't forget to reload the updated bash profile by typing <code>source ~/.bash_profile</code> at the prompt! </p> -<pre><code> $ newt version - Newt version: 1.0 - $ newt -h - Newt allows you to create your own embedded project based on the Mynewt - operating system. Newt provides both build and package management in a - single tool, which allows you to compose an embedded workspace, and set - of projects, and then build the necessary artifacts from those projects. - For more information on the Mynewt operating system, please visit - https://www.github.com/mynewt/documentation. - - 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: - version Display the Newt version number. - target Set and view target information - egg Commands to list and inspect eggs on a nest - nest Commands to manage nests & clutches (remote egg repositories) - help Help about any command - - Flags: - -h, --help=false: help for newt - -l, --loglevel="WARN": Log level, defaults to WARN. - -q, --quiet=false: Be quiet; only display error output. - -s, --silent=false: Be silent; don't output anything. - -v, --verbose=false: Enable verbose output when executing commands. - - - Use "newt help [command]" for more information about a command. -</code></pre> -<ul> -<li>Without creating a project repository you can't do a whole lot with the Newt tool. So you'll have to wait till you have downloaded a nest to try out the tool. </li> -</ul> -<h4 id="getting-the-debugger-ready">Getting the debugger ready<a class="headerlink" href="#getting-the-debugger-ready" title="Permanent link">¶</a></h4> -<ul> -<li> -<p>Before you start building nests and hatching eggs, you need to do one final step in the environment preparation - install gcc / libc that can produce 32-bit executables. So, first install gcc. You will see the brew steps and a final summary confirming install.</p> -<pre><code>$ brew install gcc -... -... -==> Summary -ðº /usr/local/Cellar/gcc/5.2.0: 1353 files, 248M -</code></pre> -</li> -<li> -<p>ARM maintains a pre-built GNU toolchain with a GCC source branch targeted at Embedded ARM Processors namely Cortex-R/Cortex-M processor families. Install the PX4 Toolchain and check the version installed. Make sure that the symbolic link installed by Homebrew points to the correct version of the debugger. If not, you can either change the symbolic link using the "ln -f -s" command or just go ahead and try with the version it points to!</p> -<pre><code>$ brew tap PX4/homebrew-px4 -$ brew update -$ brew install gcc-arm-none-eabi-49 -$ arm-none-eabi-gcc --version -arm-none-eabi-gcc (GNU Tools for ARM Embedded Processors) 4.9.3 20150529 (release) [ARM/embedded-4_9-branch revision 224288] -Copyright (C) 2014 Free Software Foundation, Inc. -This is free software; see the source for copying conditions. There is NO -warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. -$ ls -al /usr/local/bin/arm-none-eabi-gdb -lrwxr-xr-x 1 aditihilbert admin 69 Sep 22 17:16 /usr/local/bin/arm-none-eabi-gdb -> /usr/local/Cellar/gcc-arm-none-eabi-49/20150609/bin/arm-none-eabi-gdb -</code></pre> -<p>Note: If no version is specified, brew will install the latest version available. MynewtOS will eventually work with multiple versions available including the latest releases. However, at present we have tested only with this version and recommend it for getting started. </p> -</li> -<li> -<p>You have to install OpenOCD (Open On-Chip Debugger) which is an open-source software that will allow you to interface with the JTAG debug connector/adaptor for the Olimex board. It lets you program, debug, and test embedded target devices which, in this case, is the Olimex board. Use brew to install it. Brew adds a simlink /usr/local/bin/openocd to the openocd directory in the Cellar. For more on OpenOCD go to <a href="http://openocd.org";>http://openocd.org</a>.</p> -<pre><code>$ brew install open-ocd -$ which openocd -/usr/local/bin/openocd -$ ls -l $(which openocd) -lrwxr-xr-x 1 <user> admin 36 Sep 17 16:22 /usr/local/bin/openocd -> ../Cellar/open-ocd/0.9.0/bin/openocd -</code></pre> -</li> -<li> -<p>Proceed to the <a href="#building-test-code-on-simulator">Building test code on simulator</a> section.</p> -</li> -</ul> -<h3 id="getting-your-ubuntu-machine-ready">Getting your Ubuntu machine Ready<a class="headerlink" href="#getting-your-ubuntu-machine-ready" title="Permanent link">¶</a></h3> -<h4 id="installing-some-prerequisites">Installing some prerequisites<a class="headerlink" href="#installing-some-prerequisites" title="Permanent link">¶</a></h4> -<ul> -<li>Install git, libcurl, and the Go language if you do not have them already.<pre><code>$ sudo apt-get install git -$ sudo apt-get install libcurl4-gnutls-dev -$ sudo apt-get install golang -</code></pre> -</li> -</ul> -<h4 id="creating-local-repository_1">Creating local repository<a class="headerlink" href="#creating-local-repository_1" title="Permanent link">¶</a></h4> -<ul> -<li> -<p>The directory structure must be first readied for using Go. Go code must be kept inside a workspace. A workspace is a directory hierarchy with three directories at its root:</p> -<ul> -<li> -<p>src contains Go source files organized into packages (one package per directory),</p> -</li> -<li> -<p>pkg contains package objects, and</p> -</li> -<li> -<p>bin contains executable commands.</p> -</li> -</ul> -<p>The GOPATH environment variable specifies the location of your workspace. First create a 'dev' directory and then a 'go' directory under it. Set the GOPATH environment variable to this directory where you will soon clone the newt tool repository.</p> -<pre><code>$ cd $HOME -$ mkdir -p dev/go -$ cd dev/go -$ export GOPATH=$PWD -</code></pre> -<p>Note that you need to add export statements to ~/.bashrc (or equivalent) to export variables permanently.</p> -</li> -<li> -<p>You are ready to download the newt tool repository. You will use Go to copy the directory (currently the asf incubator directory). Be patient as it may take a minute or two. Check the directories installed.</p> -<pre><code>$ go get git-wip-us.apache.org/repos/asf/incubator-mynewt-newt.git/newt -$ ls - bin pkg src -$ ls src -git-wip-us.apache.org github.com gopkg.in -</code></pre> -</li> -<li> -<p>Check that newt is in place.</p> -<pre><code>$ ls $GOPATH/src/git-wip-us.apache.org/repos/asf/incubator-mynewt-newt.git/newt -Godeps README.md coding_style.txt newt.go -LICENSE cli design.txt -</code></pre> -</li> -</ul> -<h4 id="building-the-newt-tool_1">Building the newt tool<a class="headerlink" href="#building-the-newt-tool_1" title="Permanent link">¶</a></h4> -<ul> -<li> -<p>You will use Go to run the newt.go program to build the newt tool. The command used is <code>go install</code> which compiles and writes the resulting executable to an output file named <code>newt</code>. It installs the results along with its dependencies in $GOPATH/bin.</p> -<pre><code>$ cd $GOPATH/src/git-wip-us.apache.org/repos/asf/incubator-mynewt-newt.git/newt -$ go install -$ ls "$GOPATH"/bin/ -godep incubator-mynewt-newt.git newt -</code></pre> -</li> -<li> -<p>Try running newt using the compiled binary. For example, check for the version number by typing 'newt version'. See all the possible commands available to a user of newt by typing 'newt -h'.</p> -</li> -</ul> -<p>Note: If you are going to be be modifying the newt tool itself often and wish to compile the program every time you call it, you may want to store the command in a variable in your .bash_profile. So type in <code>export newt="go run $GOPATH/src/git-wip-us.apache.org/repos/asf/incubator-mynewt-newt.git/newt/newt/go"</code> in your ~/.bashrc (or equivalent) and execute it by calling <code>$newt</code> at the prompt instead of <code>newt</code>. Here, you use <code>go run</code> which runs the compiled binary directly without producing an executable. </p> -<pre><code> $ newt version - Newt version: 1.0 - $ newt -h - Newt allows you to create your own embedded project based on the Mynewt - operating system. Newt provides both build and package management in a - single tool, which allows you to compose an embedded workspace, and set - of projects, and then build the necessary artifacts from those projects. - For more information on the Mynewt operating system, please visit - https://www.github.com/mynewt/documentation. - - 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: - version Display the Newt version number. - target Set and view target information - egg Commands to list and inspect eggs on a nest - nest Commands to manage nests & clutches (remote egg repositories) - help Help about any command - - Flags: - -h, --help=false: help for newt - -l, --loglevel="WARN": Log level, defaults to WARN. - -q, --quiet=false: Be quiet; only display error output. - -s, --silent=false: Be silent; don't output anything. - -v, --verbose=false: Enable verbose output when executing commands. - - - Use "newt help [command]" for more information about a command. -</code></pre> -<ul> -<li>Without creating a project repository you can't do a whole lot with the Newt tool. So you'll have to wait till you have downloaded a nest to try out the tool. </li> -</ul> -<h4 id="getting-the-debugger-ready_1">Getting the debugger ready<a class="headerlink" href="#getting-the-debugger-ready_1" title="Permanent link">¶</a></h4> -<ul> -<li> -<p>Before you start building nests and hatching eggs, you need to do one final step in the environment preparation - install gcc / libc that can produce 32-bit executables. You can install these as follows: </p> -<pre><code>$ sudo apt-get install gcc-multilib libc6-i386 -</code></pre> -</li> -<li> -<p>For the LED project on the Olimex hardware, you have to install gcc for AM 4.9.3. This package can be installed with apt-get as documented below. The steps are explained in depth at <a href="https://launchpad.net/~terry.guo/+archive/ubuntu/gcc-arm-embedded";>https://launchpad.net/~terry.guo/+archive/ubuntu/gcc-arm-embedded</a>.</p> -<pre><code>$ sudo apt-get remove binutils-arm-none-eabi gcc-arm-none-eabi -$ sudo add-apt-repository ppa:terry.guo/gcc-arm-embedded -$ sudo apt-get update -$ sudo apt-get install gcc-arm-none-eabi -</code></pre> -</li> -<li> -<p>And finally, you have to install OpenOCD (Open On-Chip Debugger) which is an open-source software that will allow you to interface with the JTAG debug connector/adaptor for the Olimex board. It lets you program, debug, and test embedded target devices which, in this case, is the Olimex board. You have to acquire OpenOCD 0.8.0. </p> -<p>If you are running Ubuntu 15.x, then you are in luck and you can simply run: </p> -<pre><code>$ sudo apt-get install openocd -</code></pre> -<p>Other versions of Ubuntu may not have the correct version of openocd available. In this case, you should download the openocd 0.8.0 package from <a href="https://launchpad.net/ubuntu/vivid/+source/openocd";>https://launchpad.net/ubuntu/vivid/+source/openocd</a>. The direct link to the amd64 build is <a href="http://launchpadlibrarian.net/188260097/openocd_0.8.0-4_amd64.deb";>http://launchpadlibrarian.net/188260097/openocd_0.8.0-4_amd64.deb</a>. </p> -</li> -<li> -<p>Proceed to the <a href="#building-test-code-on-simulator">Building test code on simulator</a> section.</p> -</li> -</ul> -<h3 id="getting-your-windows-machine-ready">Getting your Windows machine Ready<a class="headerlink" href="#getting-your-windows-machine-ready" title="Permanent link">¶</a></h3> -<p><font color="red"> Note: The instructions for Windows machine are still under review. We are working on providing a Docker container to make the prep work easy. </font></p> -<h4 id="installing-some-prerequisites_1">Installing some prerequisites<a class="headerlink" href="#installing-some-prerequisites_1" title="Permanent link">¶</a></h4> -<ul> -<li> -<p>You have to install the following if you do not have them already. The steps below indicate specific folders where each of these programs should be installed. You can choose different locations, but the remainder of this -tutorial for a Windows machine assumes the specified folders. </p> -<ul> -<li>win-builds-i686</li> -<li>win-builds-x86_64</li> -<li>MSYS</li> -<li>gcc for ARM</li> -<li>openocd</li> -<li>zadig</li> -<li>git</li> -<li> -<p>go</p> -<ul> -<li><em>win-builds (mingw64) 1.5 for i686</em></li> -</ul> -<p>Download from <a href="http://win-builds.org/doku.php/download_and_installation_from_windows";>http://win-builds.org/doku.php/download_and_installation_from_windows</a>. Install at: "C:\win-builds-i686".</p> -<p>Be sure to click the i686 option (not x86_64). The defaults for all other options are OK. The installer will want to download a bunch of additional packages. They are not all necessary, but it is simplest to just accept the defaults.</p> -<ul> -<li><em>win-builds (mingw64) 1.5 for x86_64</em></li> -</ul> -<p>Download from <a href="http://win-builds.org/doku.php/download_and_installation_from_windows";>http://win-builds.org/doku.php/download_and_installation_from_windows</a>. Install at "C:\win-builds-x86_64"</p> -<p>Run the installer a second time, but this time click the x86_64 option, NOT i686. The defaults for all other options are OK.</p> -<ul> -<li><em>MSYS</em></li> -</ul> -<p>Start your download from <a href="http://sourceforge.net/projects/mingw-w64/files/External%20binary%20packages%20%28Win64%20hosted%29/MSYS%20%2832-bit%29/MSYS-20111123.zip";>http://sourceforge.net/projects/mingw-w64/files/External%20binary%20packages%20%28Win64%20hosted%29/MSYS%20%2832-bit%29/MSYS-20111123.zip</a></p> -<p>Unzip to "C:\msys"</p> -<ul> -<li><em>gcc for ARM, 4.9.3</em></li> -</ul> -<p>Download the Windows installer from <a href="https://launchpad.net/gcc-arm-embedded/+download";>https://launchpad.net/gcc-arm-embedded/+download</a> and install at "C:\Program Files (x86)\GNU Tools ARM Embedded\4.9 2015q3".</p> -<ul> -<li>OpenOCD 0.8.0 </li> -</ul> -<p>Download OpenOCD 0.8.0 from <a href="http://www.freddiechopin.info/en/download/category/4-openocd";>http://www.freddiechopin.info/en/download/category/4-openocd</a>. Unzip to "C:\openocd".</p> -<ul> -<li>Zadig 2.1.2</li> -</ul> -<p>Download it from <a href="http://zadig.akeo.ie";>http://zadig.akeo.ie</a> and install it at "C:\zadig".</p> -<ul> -<li>Git</li> -</ul> -<p>Click on <a href="https://git-scm.com/download/win";>https://git-scm.com/download/win</a> to start the download. Install at "C:\Program Files (x86)\Git". Specify the "Use Git from the Windows Command Prompt" option. The defaults for all other options are OK.</p> -<ul> -<li>Go</li> -</ul> -<p>Download the release for Microsoft Windows from <a href="https://golang.org/dl/";>https://golang.org/dl/</a> and install it "C:\Go".</p> -</li> -</ul> -</li> -</ul> -<h4 id="creating-local-repository_2">Creating local repository<a class="headerlink" href="#creating-local-repository_2" title="Permanent link">¶</a></h4> -<ul> -<li> -<p>The directory structure must be first readied for using Go. Go code must be kept inside a workspace. A workspace is a directory hierarchy with three directories at its root:</p> -<ul> -<li> -<p>src contains Go source files organized into packages (one package per directory),</p> -</li> -<li> -<p>pkg contains package objects, and</p> -</li> -<li> -<p>bin contains executable commands.</p> -</li> -</ul> -<p>The GOPATH environment variable specifies the location of your workspace. First create a 'dev' directory and then a 'go' directory under it. Set the GOPATH environment variable to this directory and then proceed to create the directory for cloning the newt tool repository.</p> -<pre><code>$ cd c:\ -$ mkdir dev\go -$ cd dev\go -</code></pre> -</li> -<li> -<p>Set the following user environment variables using the steps outlined here.</p> -<ul> -<li>GOPATH: C:\dev\go</li> -<li>PATH: C:\Program Files (x86)\GNU Tools ARM Embedded\4.9 2015q3\bin;%GOPATH%\bin;C:\win-builds-x86_64\bin;C:\win-builds-i686\bin;C:\msys\bin</li> -</ul> -<p>Steps:</p> -<ol> -<li>Right-click the start button</li> -<li>Click "Control panel"</li> -<li>Click "System and Security"</li> -<li>Click "System"</li> -<li>Click "Advanced system settings" in the left panel</li> -<li>Click the "Envoronment Variables..." button</li> -<li>There will be two sets of environment variables: user variables - in the upper half of the screen, and system variables in the lower - half. Configuring the user variables is recommended and tested - (though system variables will work as well).</li> -</ol> -</li> -<li> -<p>Next, install godep. Note that the following command produces no output.</p> -<pre><code>$ go get github.com/tools/godep -</code></pre> -</li> -<li> -<p>Set up the repository for the package building tool "newt" on your local machine. First create the appropriate directory for it and then clone the newt tool repository from the online apache repository (or its github.com mirror) into this newly created directory. Check the contents of the directory.</p> -<pre><code>$ go get git-wip-us.apache.org/repos/asf/incubator-mynewt-newt.git/newt -$ dir - bin pkg src -$ dir src -git-wip-us.apache.org github.com gopkg.in -$ dir -newt -$ cd newt -$ dir -Godeps README.md coding_style.txt newt.go -LICENSE cli design.txt -</code></pre> -</li> -<li> -<p>Check that newt is in place.</p> -<pre><code>$ dir $GOPATH\src\git-wip-us.apache.org\repos\asf\incubator-mynewt-newt.git\newt -Godeps README.md coding_style.txt newt.go -LICENSE cli design.txt -</code></pre> -</li> -</ul> -<h4 id="building-the-newt-tool_2">Building the newt tool<a class="headerlink" href="#building-the-newt-tool_2" title="Permanent link">¶</a></h4> -<ul> -<li> -<ul> -<li> -<p>You will use Go to run the newt.go program to build the newt tool. The command used is <code>go install</code> which compiles and writes the resulting executable to an output file named <code>newt</code>. It installs the results along with its dependencies in $GOPATH/bin.</p> -<p>$ go install -$ ls "$GOPATH"/bin/ -godep incubator-mynewt-newt.git newt</p> -</li> -</ul> -</li> -<li> -<p>Try running newt using the compiled binary. For example, check for the version number by typing 'newt version'. See all the possible commands available to a user of newt by typing 'newt -h'.</p> -<p>Note: If you are going to be be modifying the newt tool itself often and wish to compile the program every time you call it, you may want to define the newt environment variable that allows you to execute the command via <code>%newt%</code>. Use <code>set newt=go run %GOPATH%\src\github.com\mynewt\newt\newt.go</code> or set it from the GUI. Here, you use <code>go run</code> which runs the compiled binary directly without producing an executable.</p> -<pre><code>$ newt version -Newt version: 1.0 -$ newt -h -Newt allows you to create your own embedded project based on the Mynewt -operating system. Newt provides both build and package management in a -single tool, which allows you to compose an embedded workspace, and set -of projects, and then build the necessary artifacts from those projects. -For more information on the Mynewt operating system, please visit -https://www.github.com/mynewt/documentation. - -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: - version Display the Newt version number. - target Set and view target information - egg Commands to list and inspect eggs on a nest - nest Commands to manage nests & clutches (remote egg repositories) - help Help about any command - -Flags: - -h, --help=false: help for newt - -l, --loglevel="WARN": Log level, defaults to WARN. - -q, --quiet=false: Be quiet; only display error output. - -s, --silent=false: Be silent; don't output anything. - -v, --verbose=false: Enable verbose output when executing commands. - -Use "newt help [command]" for more information about a command. -</code></pre> -</li> -<li> -<p>Without creating a project repository you can't do a whole lot with the Newt tool. So you'll have to wait till you have downloaded a nest to try out the tool. </p> -</li> -</ul> -<h4 id="getting-the-debugger-ready_2">Getting the debugger ready<a class="headerlink" href="#getting-the-debugger-ready_2" title="Permanent link">¶</a></h4> -<ul> -<li> -<p>Use Zadig to configure the USB driver for your Olimex debugger. If your debugger is already set up, you can skip this step.</p> -<ol> -<li>Plug in your Olimex debugger.</li> -<li>Start Zadig.</li> -<li>Check the Options -> List All Devices checkbox.</li> -<li>Select "Olimex OpenOCD JTAG ARM-USB-TINY-H" in the dropdown menu.</li> -<li>Select the "WinUSB" driver.</li> -<li>Click the "Install Driver" button.</li> -</ol> -</li> -</ul> -<h4 id="proceed-to-the-building-test-code-on-simulator-on-windows-machine-section">Proceed to the <a href="#building-test-code-on-simulator">Building test code on simulator on Windows machine</a> section.<a class="headerlink" href="#proceed-to-the-building-test-code-on-simulator-on-windows-machine-section" title="Permanent link">¶</a></h4> -<p>Note: Currently, the simulator cannot be run in the Windows machine. We are still working on it. So you will go ahead and <a href="#making-an-led-blink-from-sram">make an LED blink</a> on the Olimex hardware directly. </p> -<p>However, before you skip to the hardware target, you still need to build your first nest as outlined in step 1 in the <a href="#building-test-code-on-simulator">Building test code on simulator</a>.</p> -<h3 id="building-test-code-on-simulator">Building test code on simulator<a class="headerlink" href="#building-test-code-on-simulator" title="Permanent link">¶</a></h3> -<p>Note: Currently, the simulator cannot be run in the Windows machine. We are working on it. If you are on a Windows machine, do step 1 below and then proceed to the <a href="#making-an-led-blink">Making an LED blink</a> on the Olimex hardware directly.</p> -<ol> -<li> -<p>First, you have to create a repository for the project i.e. build your first nest! Go to ~/dev and clone the larva repository from the apache git repository into a local directory named <code>larva</code>.</p> -<p>Substitute DOS commands for Unix commands as necessary in the following steps if your machine is running Windows. The newt tool commands do not change.</p> -<pre><code>$ cd ~/dev -$ git clone https://git-wip-us.apache.org/repos/asf/incubator-mynewt-larva.git larva -$ ls -go larva -$ cd larva -$ ls -LICENSE clutch.yml hw nest.yml project -README.md compiler libs net scripts -</code></pre> -</li> -<li> -<p>You will now create a new target using the newt tool. You can either use the compiled binary <code>newt</code> or run the newt.go program using <code>$newt</code> (assuming you have stored the command in a variable in your .bash_profile or .bashrc). When you do a <code>newt target show</code> or <code>$newt target show</code> it should list all the projects you have created so far. </p> -<pre><code>$ newt target create sim_test -Creating target sim_test -Target sim_test sucessfully created! -$ newt target show -sim_test - name: sim_test - arch: sim -</code></pre> -</li> -<li> -<p>Now continue to populate and build out the sim project.</p> -<pre><code>$ newt target set sim_test project=test -Target sim_test successfully set project to test -$ newt target set sim_test compiler_def=debug -Target sim_test successfully set compiler_def to debug -$ newt target set sim_test bsp=hw/bsp/native -Target sim_test successfully set bsp to hw/bsp/native -$ newt target set sim_test compiler=sim -Target sim_test successfully set compiler to sim -$ newt target show sim_test -sim_test - arch: sim - project: test - compiler_def: debug - bsp: hw/bsp/native - compiler: sim - name: sim_test -</code></pre> -</li> -<li> -<p>Configure newt to use the gnu build tools native to OS X or linux. In order for sim to work properly, it needs to be using 32-bit gcc (gcc-5). Replace -~/dev/larva/compiler/sim/compiler.yml with the compiler/sim/osx-compiler.yml or linux-compiler.yml file, depending on the system. </p> -<p>For a Mac OS X environment:</p> -<pre><code>$ cp compiler/sim/osx-compiler.yml compiler/sim/compiler.yml -</code></pre> -<p>For a Linux machine:</p> -<pre><code>$ cp compiler/sim/linux-compiler.yml compiler/sim/compiler.yml -</code></pre> -</li> -<li> -<p>Next, create (hatch!) the eggs for this project using the newt tool - basically, build the packages for it. You can specify the VERBOSE option if you want to see the gory details. </p> -<pre><code>$ $newt target build sim_test -Successfully run! -</code></pre> -<p>You can specify the VERBOSE option if you want to see the gory details.</p> -<pre><code>$newt -l VERBOSE target build sim_test -2015/09/29 09:46:12 [INFO] Building project test -2015/09/29 09:46:12 [INFO] Loading Package /Users/aditihilbert/dev/larva/libs//bootutil... -2015/09/29 09:46:12 [INFO] Loading Package /Users/aditihilbert/dev/larva/libs//cmsis-core... -2015/09/29 09:46:12 [INFO] Loading Package /Users/aditihilbert/dev/larva/libs//ffs.. -... -Successfully run! -</code></pre> -</li> -<li> -<p>Try running the test suite executable inside this project and enjoy your first successful hatch.</p> -<pre><code>$ ./project/test/bin/sim_test/test.elf -[pass] os_mempool_test_suite/os_mempool_test_case -[pass] os_mutex_test_suite/os_mutex_test_basic -[pass] os_mutex_test_suite/os_mutex_test_case_1 -[pass] os_mutex_test_suite/os_mutex_test_case_2 -[pass] os_sem_test_suite/os_sem_test_basic -[pass] os_sem_test_suite/os_sem_test_case_1 -[pass] os_sem_test_suite/os_sem_test_case_2 -[pass] os_sem_test_suite/os_sem_test_case_3 -[pass] os_sem_test_suite/os_sem_test_case_4 -[pass] os_mbuf_test_suite/os_mbuf_test_case_1 -[pass] os_mbuf_test_suite/os_mbuf_test_case_2 -[pass] os_mbuf_test_suite/os_mbuf_test_case_3 -[pass] gen_1_1/ffs_test_unlink -[pass] gen_1_1/ffs_test_rename -[pass] gen_1_1/ffs_test_truncate -[pass] gen_1_1/ffs_test_append -[pass] gen_1_1/ffs_test_read -[pass] gen_1_1/ffs_test_overwrite_one -[pass] gen_1_1/ffs_test_overwrite_two -[pass] gen_1_1/ffs_test_overwrite_three -... -... -[pass] boot_test_main/boot_test_vb_ns_11 -</code></pre> -</li> -</ol> -<h3 id="building-test-code-on-simulator-on-windows-machine">Building test code on simulator on Windows machine<a class="headerlink" href="#building-test-code-on-simulator-on-windows-machine" title="Permanent link">¶</a></h3> -<p>Coming soon.</p> -<h3 id="using-sram-to-make-led-blink">Using SRAM to make LED blink<a class="headerlink" href="#using-sram-to-make-led-blink" title="Permanent link">¶</a></h3> -<p>You are here because you want to build an image to be run from internal SRAM on the Olimex board.</p> -<h4 id="preparing-the-software">Preparing the Software<a class="headerlink" href="#preparing-the-software" title="Permanent link">¶</a></h4> -<ol> -<li> -<p>Make sure the PATH environment variable includes the $HOME/dev/go/bin directory (or C:\%GOPATH%\bin on Windows machine). </p> -<p>Substitute DOS commands for Unix commands as necessary in the following steps if your machine is running Windows (e.g. <code>cd dev\go</code> instead of <code>cd dev/go</code>). The newt tool commands do not change.</p> -</li> -<li> -<p>You first have to create a repository for the project. Go to the ~dev/larva directory and build out a second project inside larva. The project name is "blinky", in keeping with the objective. Starting with the target name, you have to specify the different aspects of the project to pull the appropriate eggs and build the right package for the board. In this case that means setting the architecture (arch), compiler, board support package (bsp), project, and compiler mode.</p> -<pre><code>$ newt target create blinky -Creating target blinky -Target blinky sucessfully created! -$ newt target set blinky arch=cortex_m4 -Target blinky successfully set arch to arm -$ newt target set blinky compiler=arm-none-eabi-m4 -Target blinky successfully set compiler to arm-none-eabi-m4 -$ newt target set blinky project=blinky -Target blinky successfully set project to blinky -$ newt target set blinky compiler_def=debug -Target blinky successfully set compiler_def to debug -$ newt target set blinky bsp=hw/bsp/olimex_stm32-e407_devboard -Target blinky successfully set bsp to hw/bsp/olimex_stm32-e407_devboard -$ newt target show blinky -blinky - compiler: arm-none-eabi-m4 - project: blinky - compiler_def: debug - bsp: hw/bsp/olimex_stm32-e407_devboard - name: blinky - arch: cortex_m4 -</code></pre> -</li> -<li> -<p>Now you have to build the image. The linker script within the <code>hw/bsp/olimex_stm32-e407_devboard</code> egg builds an image for flash memory by default. Since you want an image for the SRAM, you need to switch that script with <code>run_from_sram.ld</code> in order to get the egg to produce an image for SRAM. <font color="red"> We are working on making it easier to specify where the executable will be run from for a particular project and automatically choose the correct linker scripts and generate the appropriate image. It will be specified as a project identity e.g. bootloader, RAM, flash (default) and the target will build accordingly. </font>. </p> -<p>Once the target is built, you can find the executable "blinky.elf" in the project directory at ~/dev/larva/project/blinky/bin/blinky. It's a good idea to take a little time to understand the directory structure.</p> -<pre><code>$ cd ~/dev/larva/hw/bsp/olimex_stm32-e407_devboard -$ diff olimex_stm32-e407_devboard.ld run_from_sram.ld -$ cp run_from_sram.ld olimex_stm32-e407_devboard.ld -$ cd ~/dev/larva/project/blinky/bin/blinky -$ newt target build blinky -Building target blinky (project = blinky) -Compiling case.c -Compiling suite.c -... -Successfully run! -$ ls -LICENSE clutch.yml hw nest.yml project -README.md compiler libs net scripts -$ cd project -$ ls -bin2img bletest blinky boot ffs2native test -$ cd blinky -$ ls -bin blinky.yml egg.yml src -$ cd bin -$ ls -blinky -$ cd blinky -$ ls -blinky.elf blinky.elf.bin blinky.elf.cmd blinky.elf.lst blinky.elf.map -</code></pre> -</li> -<li> -<p>Check that you have all the scripts needed to get OpenOCD up and talking with the project's specific hardware. Depending on your system (Ubuntu, Windows) you may already have the scripts in your <code>/usr/share/openocd/scripts/</code> directory as they may have been part of the openocd download. If yes, you are all set and can proceed to preparing the hardware.</p> -</li> -</ol> -<p>Otherwise check the <code>~/dev/larva/hw/bsp/olimex_stm32-e407_devboard</code> directory for a file named <code>f407.cfg</code>. That is the config we will use to talk to this specific hardware using OpenOCD. You are all set if you see it.</p> -<pre><code> $ ls ~/dev/larva/hw/bsp/olimex_stm32-e407_devboard - bin olimex_stm32-e407_devboard_debug.sh - boot-olimex_stm32-e407_devboard.ld olimex_stm32-e407_devboard_download.sh - egg.yml run_from_flash.ld - f407.cfg run_from_loader.ld - include run_from_sram.ld - olimex_stm32-e407_devboard.ld src -</code></pre> -<h4 id="preparing-the-hardware-to-boot-from-embedded-sram">Preparing the hardware to boot from embedded SRAM<a class="headerlink" href="#preparing-the-hardware-to-boot-from-embedded-sram" title="Permanent link">¶</a></h4> -<ol> -<li> -<p>Locate the boot jumpers on the board. -<img alt="Alt Layout - Top View" src="../pics/topview.png" /> -<img alt="Alt Layout - Bottom View" src="../pics/bottomview.png" /></p> -</li> -<li> -<p>B1_1/B1_0 and B0_1/B0_0 are PTH jumpers which can be moved relatively easy. Note that the markings on the board may not always be accurate. Always refer to the manual for the correct positioning of jumpers in case of doubt. The two jumpers must always be moved together â they are responsible for the boot mode if bootloader is present. The board can search for bootloader on three places â User Flash Memory, System Memory or the Embedded SRAM. We will configure it to boot from SRAM by jumpering B0_1 and B1_1.</p> -</li> -<li> -<p>Connect USB-OTG#2 in the picture above to a USB port on your computer (or a powered USB hub to make sure there is enough power available to the board). </p> -</li> -<li> -<p>The red PWR LED should be lit. </p> -</li> -<li> -<p>Connect the JTAG connector to the SWD/JTAG interface on the board. The other end of the cable should be connected to the USB port or hub of your computer.</p> -</li> -</ol> -<h4 id="lets-go">Let's Go!<a class="headerlink" href="#lets-go" title="Permanent link">¶</a></h4> -<ol> -<li> -<p>Make sure you are in the blinky project directory with the blinky.elf executable. Run the debug command in the newt tool. You should see some status messages are shown below. There is an inbuilt <code>-c "reset halt"</code> flag that tells it to halt after opening the session.</p> -<pre><code>$ cd dev/larva/project/blinky/bin/blinky -$ newt target debug blinky -Debugging with /Users/aditihilbert/dev/larva/hw/bsp/olimex_stm32-e407_devboard/olimex_stm32-e407_devboard_debug.sh blinky -Debugging /Users/aditihilbert/dev/larva/project/blinky/bin/blinky/blinky.elf -GNU gdb (GNU Tools for ARM Embedded Processors) 7.8.0.20150604-cvs -Copyright (C) 2014 Free Software Foundation, Inc. -License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> -This is free software: you are free to change and redistribute it. -There is NO WARRANTY, to the extent permitted by law. Type "show copying" -and "show warranty" for details. -This GDB was configured as "--host=x86_64-apple-darwin10 --target=arm-none-eabi". -Type "show configuration" for configuration details. -For bug reporting instructions, please see: -<http://www.gnu.org/software/gdb/bugs/>. -Find the GDB manual and other documentation resources online at: -<http://www.gnu.org/software/gdb/documentation/>. -For help, type "help". -Type "apropos word" to search for commands related to "word"... -Reading symbols from /Users/aditihilbert/dev/larva/project/blinky/bin/ blinky/blinky.elf...done. -Open On-Chip Debugger 0.8.0 (2015-09-22-18:21) -Licensed under GNU GPL v2 -For bug reports, read - http://openocd.sourceforge.net/doc/doxygen/bugs.html -Info : only one transport option; autoselect 'jtag' -adapter speed: 1000 kHz -adapter_nsrst_delay: 100 -jtag_ntrst_delay: 100 -Warn : target name is deprecated use: 'cortex_m' -DEPRECATED! use 'cortex_m' not 'cortex_m3' -cortex_m reset_config sysresetreq -Info : clock speed 1000 kHz -Info : JTAG tap: stm32f4x.cpu tap/device found: 0x4ba00477 (mfg: 0x23b, part: 0xba00, ver: 0x4) -Info : JTAG tap: stm32f4x.bs tap/device found: 0x06413041 (mfg: 0x020, part: 0x6413, ver: 0x0) -Info : stm32f4x.cpu: hardware has 6 breakpoints, 4 watchpoints -Info : JTAG tap: stm32f4x.cpu tap/device found: 0x4ba00477 (mfg: 0x23b, part: 0xba00, ver: 0x4) -Info : JTAG tap: stm32f4x.bs tap/device found: 0x06413041 (mfg: 0x020, part: 0x6413, ver: 0x0) -target state: halted -target halted due to debug-request, current mode: Thread -xPSR: 0x01000000 pc: 0x20000250 msp: 0x10010000 -Info : accepting 'gdb' connection from 3333 -Info : device id = 0x10036413 -Info : flash size = 1024kbytes -Reset_Handler () at startup_STM32F40x.s:199 -199 ldr r1, =__etext -</code></pre> -<p>Check the value of the msp (main service pointer) register. If it is not 0x10010000 as indicated above, you will have to manually set it after you open the gdp tool and load the image on it. </p> -<pre><code>(gdb) set $msp=0x10010000 -</code></pre> -<p>Now load the image and type "c" or "continue" from the GNU debugger. </p> -<pre><code>(gdb) load ~/dev/larva/project/blinky/bin/blinky/blinky.elf -Loading section .text, size 0x4294 lma 0x20000000 -Loading section .ARM.extab, size 0x24 lma 0x20004294 -Loading section .ARM.exidx, size 0xd8 lma 0x200042b8 -Loading section .data, size 0x874 lma 0x20004390 -Start address 0x20000250, load size 19460 -Transfer rate: 81 KB/sec, 2432 bytes/write. -(gdb) c -Continuing. -</code></pre> -</li> -<li> -<p>Voilà ! The board's LED should be blinking at 1 Hz.</p> -</li> -</ol> -<h3 id="using-flash-to-make-led-blink">Using flash to make LED blink<a class="headerlink" href="#using-flash-to-make-led-blink" title="Permanent link">¶</a></h3> -<p>You are here because you want to build an image to be run from flash memory on the Olimex board.</p> -<ol> -<li>Configure the board to boot from flash by moving the two jumpers together to B0_0 and B1_0. Refer to the pictures of the board under the section titled <a href="#preparing-the-hardware-to-boot-from-embedded-sram">"Preparing the hardware to boot from embedded SRAM"</a>.</li> -</ol> -<p>You will have to reset the board once the image is uploaded to it.</p> -<ol> -<li> -<p>If you skipped the first option for the project <a href="#using-sram-to-make-led-blink">(downloading an image to SRAM)</a>, then skip this step. Otherwise, continue with this step. </p> -<p>By default, the linker script (<code>olimex_stm32-e407_devboard.ld</code>) is configured to run from bootloader and flash. However, if you first ran the image from SRAM you had changed <code>olimex_stm32-e407_devboard.ld</code> to match <code>run_from_sram.ld</code>. You will therefore return to defaults with <code>olimex_stm32-e407_devboard.ld</code> linker script matching the contents of 'run_from_loader.ld'. Return to the project directory.</p> -<pre><code>$ cd ~/dev/larva/hw/bsp/olimex_stm32-e407_devboard -$ diff olimex_stm32-e407_devboard.ld run_from_sram.ld -$ diff olimex_stm32-e407_devboard.ld run_from_loader.ld -$ cp run_from_loader.ld olimex_stm32-e407_devboard.ld -$ cd ~/dev/larva/project/blinky/bin/blinky -</code></pre> -</li> -<li> -<p>In order to run the image from flash, you need to build the bootloader as well. The bootloader does the initial bring up of the Olimex board and then transfers control to the image stored at a location in flash known to it. The bootloader in turn requires the bin2image tool to check the image header for version information, CRC checks etc. So, we will need to build these two additional targets (bootloader and bin2img).</p> -</li> -</ol> -<p>Let's first create bin2img:</p> -<pre><code> $ newt target create bin2img - Creating target bin2img - Target bin2img successfully created! - $ newt target set bin2img arch=sim - Target bin2img successfully set arch to sim - $ newt target set bin2img compiler=sim - Target bin2img successfully set compiler to sim - $ newt target set bin2img project=bin2img - Target bin2img successfully set project to bin2img - $ newt target set bin2img compiler_def=debug - Target bin2img successfully set compiler_def to debug - $ newt target set bin2img bsp=hw/bsp/native - Target bin2img successfully set bsp to hw/bsp/native - $ newt target show bin2image - $ newt target show bin2img - bin2img - arch: sim - compiler: sim - project: bin2img - compiler_def: debug - bsp: hw/bsp/native - name: bin2img -</code></pre> -<p>And then let's create boot_olimex:</p> -<pre><code> $ newt target create boot_olimex - Creating target boot_olimex - Target boot_olimex successfully created! - $ newt target set boot_olimex arch=cortex_m4 - Target boot_olimex successfully set arch to cortex_m4 - $ newt target set boot_olimex compiler=arm-none-eabi-m4 - Target boot_olimex successfully set compiler to arm-none-eabi-m4 - $ newt target set boot_olimex project=boot - Target boot_olimex successfully set project to boot - $ newt target set boot_olimex compiler_def=optimized - Target boot_olimex successfully set compiler_def to optimized - $ newt target set boot_olimex bsp=hw/bsp/olimex_stm32-e407_devboard - Target boot_olimex successfully set bsp to hw/bsp/olimex_stm32-e407_devboard - $ newt target show boot_olimex - boot_olimex - project: boot - compiler_def: optimized - bsp: hw/bsp/olimex_stm32-e407_devboard - name: boot_olimex - arch: cortex_m4 - compiler: arm-none-eabi-m4 -</code></pre> -<ol> -<li> -<p>Let's build all the three targets now.</p> -<pre><code>$ newt target build bin2img -Building target bin2img (project = bin2img) -Building project bin2img -Successfully run! -$ newt target build boot_olimex -Building target boot_olimex (project = boot) -Building project boot -Successfully run! -$ newt target build blinky -Building target blinky (project = blinky) -Building project blinky -Successfully run! -</code></pre> -</li> -<li> -<p>Go to the project directory and download the bootloader and the image to flash ... in a flash! </p> -<pre><code>$ cd ~/dev/larva/project/blinky/bin/blinky -$ newt target download boot_olimex -Downloading with ~/dev/larva/hw/bsp/olimex_stm32-e407_devboard/olimex_stm32-e407_devboard_download.sh -$ newt target download blinky -Downloading with ~/dev/larva/hw/bsp/olimex_stm32-e407_devboard/olimex_stm32-e407_devboard_download.sh -</code></pre> -</li> -<li> -<p>The LED should be blinking!</p> -</li> -<li> -<p>But wait...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. The debug connection to the JTAG port is now severed. 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>Note #1: If you want to download the image to flash and a gdb session opened up, use <code>newt target debug blinky</code> instead of <code>newt target download blinky</code>.</p> -<pre><code>$ newt target debug blinky -Debugging with ~/dev/larva/hw/bsp/olimex_stm32-e407_devboard/olimex_stm32-e407_devboard_debug.sh blinky -Debugging ~/dev/larva/project/blinky/bin/blinky/blinky.elf -GNU gdb (GNU Tools for ARM Embedded Processors) 7.8.0.20150604-cvs -Copyright (C) 2014 Free Software Foundation, Inc. -License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> -This is free software: you are free to change and redistribute it. -There is NO WARRANTY, to the extent permitted by law. Type "show copying" -and "show warranty" for details. -This GDB was configured as "--host=x86_64-apple-darwin10 --target=arm-none-eabi". -Type "show configuration" for configuration details. -For bug reporting instructions, please see: -<http://www.gnu.org/software/gdb/bugs/>. -Find the GDB manual and other documentation resources online at: -<http://www.gnu.org/software/gdb/documentation/>. -For help, type "help". -Type "apropos word" to search for commands related to "word"... -Reading symbols from /Users/aditihilbert/dev/larva/project/blinky/bin/blinky/blinky.elf...done. -Open On-Chip Debugger 0.8.0 (2015-09-22-18:21) -Licensed under GNU GPL v2 -For bug reports, read - http://openocd.sourceforge.net/doc/doxygen/bugs.html -Info : only one transport option; autoselect 'jtag' -adapter speed: 1000 kHz -adapter_nsrst_delay: 100 -jtag_ntrst_delay: 100 -Warn : target name is deprecated use: 'cortex_m' -DEPRECATED! use 'cortex_m' not 'cortex_m3' -cortex_m reset_config sysresetreq -Info : clock speed 1000 kHz -Info : JTAG tap: stm32f4x.cpu tap/device found: 0x4ba00477 (mfg: 0x23b, part: 0xba00, ver: 0x4) -Info : JTAG tap: stm32f4x.bs tap/device found: 0x06413041 (mfg: 0x020, part: 0x6413, ver: 0x0) -Info : stm32f4x.cpu: hardware has 6 breakpoints, 4 watchpoints -Info : JTAG tap: stm32f4x.cpu tap/device found: 0x4ba00477 (mfg: 0x23b, part: 0xba00, ver: 0x4) -Info : JTAG tap: stm32f4x.bs tap/device found: 0x06413041 (mfg: 0x020, part: 0x6413, ver: 0x0) -target state: halted -target halted due to debug-request, current mode: Thread -xPSR: 0x01000000 pc: 0x08000250 msp: 0x10010000 -Info : accepting 'gdb' connection from 3333 -Info : device id = 0x10036413 -Info : flash size = 1024kbytes -Reset_Handler () at startup_STM32F40x.s:199 -199 ldr r1, =__etext -(gdb) -</code></pre> -<p>Note #2: 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 therefore 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> -<pre><code>(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 -0x08000000: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff -(0x08000020: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff -(0x08000000: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff -(0x08000020: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff -(gdb) monitor flash info 0 - -monitor flash erase_check 0 -</code></pre> -</li> -</ol> - - </div> - </div> - <footer> - - <div class="rst-footer-buttons" role="navigation" aria-label="footer navigation"> - - <a href="../how_to_edit_docs/" class="btn btn-neutral float-right" title="How to edit docs"/>Next <span class="icon icon-circle-arrow-right"></span></a> - - - <a href="../newt_concepts/" class="btn btn-neutral" title="Newt Concepts"><span class="icon icon-circle-arrow-left"></span> Previous</a> - - </div> - - - <hr/> - - <div role="contentinfo"> - <!-- Copyright etc --> - - </div> - - Built with <a href="http://www.mkdocs.org";>MkDocs</a> using a <a href="https://github.com/snide/sphinx_rtd_theme";>theme</a> provided by <a href="https://readthedocs.org";>Read the Docs</a>. -</footer> - - </div> - </div> - - </section> - - </div> - -<div class="rst-versions" role="note" style="cursor: pointer"> - <span class="rst-current-version" data-toggle="rst-current-version"> - - - <span><a href="../newt_concepts/" style="color: #fcfcfc;">« Previous</a></span> - - - <span style="margin-left: 15px"><a href="../how_to_edit_docs/" style="color: #fcfcfc">Next »</a></span> - - </span> -</div> - -</body> -</html>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/2c998465/chapter1/try_markdown/index.html ---------------------------------------------------------------------- diff --git a/chapter1/try_markdown/index.html b/chapter1/try_markdown/index.html deleted file mode 100644 index 8768e0a..0000000 --- a/chapter1/try_markdown/index.html +++ /dev/null @@ -1,424 +0,0 @@ -<!DOCTYPE html> -<!--[if IE 8]><html class="no-js lt-ie9" lang="en" > <![endif]--> -<!--[if gt IE 8]><!--> <html class="no-js" lang="en" > <!--<![endif]--> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1.0"> - - <title>Sample doc to edit - Mynewt</title> - - - <link rel="shortcut icon" href="../../img/favicon.ico"> - - - <link href='https://fonts.googleapis.com/css?family=Lato:400,700|Roboto+Slab:400,700|Inconsolata:400,700' rel='stylesheet' type='text/css'> - - <link rel="stylesheet" href="../../css/theme.css" type="text/css" /> - <link rel="stylesheet" href="../../css/theme_extra.css" type="text/css" /> - <link rel="stylesheet" href="../../css/highlight.css"> - <link href="../../extra.css" rel="stylesheet"> - - - <script> - // Current page data - var mkdocs_page_name = "Sample doc to edit"; - </script> - - <script src="../../js/jquery-2.1.1.min.js"></script> - <script src="../../js/modernizr-2.8.3.min.js"></script> - <script type="text/javascript" src="../../js/highlight.pack.js"></script> - <script src="../../js/theme.js"></script> - - -</head> - -<body class="wy-body-for-nav" role="document"> - - <div class="wy-grid-for-nav"> - - - <nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav"> - <div class="wy-side-nav-search"> - <a href="../.." class="icon icon-home"> Mynewt</a> - <div role="search"> - <form id ="rtd-search-form" class="wy-form" action="../../search.html" method="get"> - <input type="text" name="q" placeholder="Search docs" /> - </form> -</div> - </div> - - <div class="wy-menu wy-menu-vertical" data-spy="affix" role="navigation" aria-label="main navigation"> - <ul class="current"> - - <li> - <li class="toctree-l1 "> - <a class="" href="../..">Home</a> - - </li> -<li> - - <li> - <ul class="subnav"> - <li><span>Chapter1 - Get Started</span></li> - - - - <li class="toctree-l1 "> - <a class="" href="../newt_concepts/">Newt Concepts</a> - - </li> - - - - <li class="toctree-l1 "> - <a class="" href="../project1/">Blinky, The First Project</a> - - </li> - - - - <li class="toctree-l1 "> - <a class="" href="../how_to_edit_docs/">How to edit docs</a> - - </li> - - - - <li class="toctree-l1 current"> - <a class="current" href="./">Sample doc to edit</a> - - <ul> - - <li class="toctree-l3"><a href="#try-markdown">Try Markdown</a></li> - - <li><a class="toctree-l4" href="#heading3">Heading3</a></li> - - - </ul> - - </li> - - - </ul> -<li> - - <li> - <ul class="subnav"> - <li><span>Chapter2 - Get Acclimated</span></li> - - - - <li class="toctree-l1 "> - <a class="" href="../../chapter2/vocabulary/">Understanding Newt Terms</a> - - </li> - - - - <li class="toctree-l1 "> - <a class="" href="../../chapter2/project2/">Project 2</a> - - </li> - - - - <li class="toctree-l1 "> - <a class="" href="../../chapter2/project3/">Project 3</a> - - </li> - - - </ul> -<li> - - <li> - <ul class="subnav"> - <li><span>Chapter3 - Newt Tool</span></li> - - - - <li class="toctree-l1 "> - <a class="" href="../../chapter3/newt_ops/">Command structure</a> - - </li> - - - - <li class="toctree-l1 "> - <a class="" href="../../chapter3/newt_tool_reference/">Command list</a> - - </li> - - - </ul> -<li> - - <li> - <ul class="subnav"> - <li><span>Chapter4 - Newt OS</span></li> - - - - <li class="toctree-l1 "> - <a class="" href="../../chapter4/mynewt_os/">Overview</a> - - </li> - - - - <li class="toctree-l1 "> - <a class="" href="../../chapter4/context_switch/">Scheduler/Context Switching</a> - - </li> - - - - <li class="toctree-l1 "> - <a class="" href="../../chapter4/time/">Time</a> - - </li> - - - - <li class="toctree-l1 "> - <a class="" href="../../chapter4/task/">Tasks</a> - - </li> - - - - <li class="toctree-l1 "> - <a class="" href="../../chapter4/event_queue/">Event Queues</a> - - </li> - - - - <li class="toctree-l1 "> - <a class="" href="../../chapter4/semaphore/">Semaphores</a> - - </li> - - - - <li class="toctree-l1 "> - <a class="" href="../../chapter4/mutex/">Mutexes</a> - - </li> - - - - <li class="toctree-l1 "> - <a class="" href="../../chapter4/memory_pool/">Memory Pools</a> - - </li> - - - - <li class="toctree-l1 "> - <a class="" href="../../chapter4/heap/">Heap</a> - - </li> - - - - <li class="toctree-l1 "> - <a class="" href="../../chapter4/mbufs/">Mbufs</a> - - </li> - - - - <li class="toctree-l1 "> - <a class="" href="../../chapter4/sanity/">Sanity</a> - - </li> - - - - <li class="toctree-l1 "> - <a class="" href="../../chapter4/port_os/">Porting to other Platforms</a> - - </li> - - - </ul> -<li> - - <li> - <ul class="subnav"> - <li><span>Chapter5 - Modules</span></li> - - - - <li class="toctree-l1 "> - <a class="" href="../../chapter5/console/">Console</a> - - </li> - - - - <li class="toctree-l1 "> - <a class="" href="../../chapter5/shell/">Shell</a> - - </li> - - - - <li class="toctree-l1 "> - <a class="" href="../../chapter5/bootloader/">Bootloader</a> - - </li> - - - - <li class="toctree-l1 "> - <a class="" href="../../chapter5/filesystem/">File System</a> - - </li> - - - - <li class="toctree-l1 "> - <a class="" href="../../chapter5/testutil/">Test Utilities</a> - - </li> - - - </ul> -<li> - - <li> - <ul class="subnav"> - <li><span>Chapter6 - Packaging it</span></li> - - - - <li class="toctree-l1 "> - <a class="" href="../../chapter6/dist/">Creating Packages</a> - - </li> - - - </ul> -<li> - - </ul> - </div> - - </nav> - - <section data-toggle="wy-nav-shift" class="wy-nav-content-wrap"> - - - <nav class="wy-nav-top" role="navigation" aria-label="top navigation"> - <i data-toggle="wy-nav-top" class="fa fa-bars"></i> - <a href="../..">Mynewt</a> - </nav> - - - <div class="wy-nav-content"> - <div class="rst-content"> - <div role="navigation" aria-label="breadcrumbs navigation"> - <ul class="wy-breadcrumbs"> - <li><a href="../..">Docs</a> »</li> - - - - <li>Chapter1 - Get Started »</li> - - - - <li>Sample doc to edit</li> - <li class="wy-breadcrumbs-aside"> - - </li> - </ul> - <hr/> -</div> - <div role="main"> - <div class="section"> - - <h2 id="try-markdown">Try Markdown<a class="headerlink" href="#try-markdown" title="Permanent link">¶</a></h2> -<h3 id="heading3">Heading3<a class="headerlink" href="#heading3" title="Permanent link">¶</a></h3> -<h4 id="heading4">Heading4<a class="headerlink" href="#heading4" title="Permanent link">¶</a></h4> -<hr /> -<h5 id="list">List<a class="headerlink" href="#list" title="Permanent link">¶</a></h5> -<ul> -<li> -<p>Start with one # for the largest heading (Heading1). The next smaller heading (Heading2) starts with ##. You can go all the way up to Heading 6 (######).</p> -</li> -<li> -<p>Heading4 (####) and Heading5 (#####) has been styled to show up underlined. Yes, it can be changed. If you are curious, you can look at the extra.css file in your repo branch.</p> -</li> -<li> -<p>It's <strong>very</strong> easy to do <strong>bold</strong> and <em>italics</em>.</p> -</li> -<li> -<p>See how this list has been made using *</p> -</li> -<li> -<p>Click on "Help" in Mou and then on "Markdown Syntax Reference".</p> -</li> -<li> -<p><font color="red"> Substitute a sentence of your own here </font></p> -</li> -<li> -<p><font color="red"> Guinea Pig!!! </font></p> -</li> -</ul> -<hr /> -<blockquote> -<p><font color="red"> Note! </font></p> -<blockquote> -<p>You will not be able to see the change immediately by refreshing your browser right after editign the Markdown file. You can only push the change to the Apache repository. So continue with the steps in <a href="../how_to_edit_docs/">how_to_edit_docs.md</a>.</p> -<p>You can see the change on the website if/when a doc builder on the project team merges your changes to the master branch and generates the pages for the website.</p> -<p>You do have the option to download MkDocs and preview the change by hosting the pages locally using its built-in web server. The steps are described in <a href="../how_to_edit_docs/">how_to_edit_docs.md</a>.</p> -</blockquote> -</blockquote> - - </div> - </div> - <footer> - - <div class="rst-footer-buttons" role="navigation" aria-label="footer navigation"> - - <a href="../../chapter2/vocabulary/" class="btn btn-neutral float-right" title="Understanding Newt Terms"/>Next <span class="icon icon-circle-arrow-right"></span></a> - - - <a href="../how_to_edit_docs/" class="btn btn-neutral" title="How to edit docs"><span class="icon icon-circle-arrow-left"></span> Previous</a> - - </div> - - - <hr/> - - <div role="contentinfo"> - <!-- Copyright etc --> - - </div> - - Built with <a href="http://www.mkdocs.org";>MkDocs</a> using a <a href="https://github.com/snide/sphinx_rtd_theme";>theme</a> provided by <a href="https://readthedocs.org";>Read the Docs</a>. -</footer> - - </div> - </div> - - </section> - - </div> - -<div class="rst-versions" role="note" style="cursor: pointer"> - <span class="rst-current-version" data-toggle="rst-current-version"> - - - <span><a href="../how_to_edit_docs/" style="color: #fcfcfc;">« Previous</a></span> - - - <span style="margin-left: 15px"><a href="../../chapter2/vocabulary/" style="color: #fcfcfc">Next »</a></span> - - </span> -</div> - -</body> -</html> http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/2c998465/chapter2/pics/STM32f3discovery_connector.png ---------------------------------------------------------------------- diff --git a/chapter2/pics/STM32f3discovery_connector.png b/chapter2/pics/STM32f3discovery_connector.png deleted file mode 100644 index 1f4437a..0000000 Binary files a/chapter2/pics/STM32f3discovery_connector.png and /dev/null differ
