You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mynewt.apache.org by ad...@apache.org on 2017/04/26 00:51:14 UTC

[03/12] incubator-mynewt-site git commit: 1) Updated OpenOCD installation to use 0.10.0 tarball. The linux version is a 32 bit binary. 2) Remove stm discovery tutorial

1) Updated OpenOCD installation to use 0.10.0 tarball. The linux version is a 32 bit binary.
2) Remove stm discovery tutorial


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/737b215e
Tree: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/tree/737b215e
Diff: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/diff/737b215e

Branch: refs/heads/develop
Commit: 737b215e022ea575c5abdb65664544b8bf59a651
Parents: ef77955
Author: cwanda <wa...@happycity.com>
Authored: Tue Apr 18 21:50:40 2017 -0700
Committer: aditihilbert <ad...@runtime.io>
Committed: Tue Apr 25 13:03:34 2017 -0700

----------------------------------------------------------------------
 docs/os/get_started/cross_tools.md | 42 ++++++++++++++++++++-------------
 docs/os/tutorials/tutorials.md     |  8 +------
 2 files changed, 26 insertions(+), 24 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/737b215e/docs/os/get_started/cross_tools.md
----------------------------------------------------------------------
diff --git a/docs/os/get_started/cross_tools.md b/docs/os/get_started/cross_tools.md
index 450952d..efd6f96 100644
--- a/docs/os/get_started/cross_tools.md
+++ b/docs/os/get_started/cross_tools.md
@@ -52,8 +52,6 @@ $ sudo apt-get install gdb-arm-none-eabi
 ## Install Debugger 
 Mynewt uses, depending on the board, either the OpenOCD or SEGGER J-Link debugger. 
 
-<br>
-
 
 ### Install OpenOCD
 OpenOCD (Open On-Chip Debugger) is open-source software that allows your
@@ -61,65 +59,75 @@ computer to interface with the JTAG debug connector on a variety of boards.  A
 JTAG connection lets you debug and test embedded target devices. For more on
 OpenOCD go to [http://openocd.org](http://openocd.org).
 
-OpenOCD version 0.10.0-dev-snapshot that is currently in development is required.  A binary for this version is available to download for Mac OS and Linux
+OpenOCD version 0.10.0 with nrf52 support is required.  A binary for this version is available to download for Mac OS and Linux.
 
+<br>
 #### Install OpenOCD on Mac OS
-Step 1: Download the [binary tarball for Mac OS](https://github.com/runtimeco/openocd-binaries/raw/master/openocd-bin-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4-MacOS.tgz).
+Step 1: Download the [binary tarball for Mac OS](https://github.com/runtimeco/openocd-binaries/raw/master/openocd-bin-0.10.0-MacOS.tgz).
 
 Step 2: Change to the root directory: 
 ```no-highlight 
 $cd / 
 ```
+<br>
 Step 3: Untar the tarball and install into ** /usr/local/bin**.  You will need to replace ** ~/Downloads ** with the directory that the tarball is downloaded to.  
 ```no-highlight
-sudo tar -xf ~/Downloads/openocd-bin-8*-MacOS.tgz ` 
+sudo tar -xf ~/Downloads/openocd-bin-0.10.0-MacOS.tgz ` 
 ```
+<br>
 Step 4: Check the OpenOCD version you are using: 
 
 ```no-highlight
 $which openocd
 /usr/local/bin/openocd
 $openocd -v
-Open On-Chip Debugger 0.10.0-dev-snapshot (2017-04-04-14:18)
+Open On-Chip Debugger 0.10.0
 Licensed under GNU GPL v2
 For bug reports, read
 http://openocd.org/doc/doxygen/bugs.html
 ```
-#### Install OpenOCD on Linux 
 
-Step 1: Download the [binary tarball for Linux 64 bits](https://github.com/runtimeco/openocd-binaries/raw/master/openocd-bin-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4-Linux.tgz). 
+You should see version: **0.10.0**. 
+
+<br>
+#### Install OpenOCD on Linux 
+Step 1: Download the [binary tarball for Linux](https://github.com/runtimeco/openocd-binaries/raw/master/openocd-bin-0.10.0-Linux.tgz)
 
 Step 2: Change to the root directory: 
 ``` 
 $cd / 
 ```
-
+<br>
 Step 3: Untar the tarball and install into ** /usr/local/bin**.  You will need to replace ** ~/Downloads ** with the directory that the tarball is downloaded to.  
 
+** Note:** You must specify the -p option for the tar command.
+
 ```no-highlight
-$sudo tar --no-same-owner -xpf ~/Downloads/openocd-bin-8*-Linux.tgz
+$sudo tar -xpf ~/Downloads/openocd-bin-0.10.0-Linux.tgz
 ```
-
+<br>
 Step 4: Check the OpenOCD version you are using: 
 
 ```no-highlight
 $which openocd
 /usr/local/bin/openocd
 $openocd -v
-Open On-Chip Debugger 0.10.0-dev-snapshot (2017-04-04-14:18)
+Open On-Chip Debugger 0.10.0
 Licensed under GNU GPL v2
 For bug reports, read
 http://openocd.org/doc/doxygen/bugs.html
 ```
-You should see version: ** 0.10.0-dev-snapshot (2017-04-04-14:18) **. 
+You should see version: **0.10.0**. 
+
+If you see any of these error messages:
 
-If you see the following error message:
+* openocd: error while loading shared libraries: libhidapi-hidraw.so.0: cannot open shared object file: No such file or directory
 
-** openocd: error while loading shared libraries: libftdi.so.1: cannot open shared object file: No such file or directory **
+* openocd: error while loading shared libraries: libusb-1.0.so.0: cannot open shared object file: No such file or directory 
 
-run the following to install the library:
+run the following command to install the libraries: 
 ```no-highlight
-$sudo apt-get install libftdi1
+$sudo apt-get install libhidapi-dev:i386
 ```
 <br>
 ###Install SEGGAR J-Link 

http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/737b215e/docs/os/tutorials/tutorials.md
----------------------------------------------------------------------
diff --git a/docs/os/tutorials/tutorials.md b/docs/os/tutorials/tutorials.md
index b66222e..2f16ed1 100644
--- a/docs/os/tutorials/tutorials.md
+++ b/docs/os/tutorials/tutorials.md
@@ -11,7 +11,6 @@ The full list of tutorials can be seen in the navigation bar on the left. New on
 * You have installed Docker container of Newt tool and toolchains or you have installed them natively on your machine
 * You have created a new project space (directory structure) and populated it with the core code repository (apache-mynewt-core) or know how to as explained in [Creating Your First Project](../get_started/project_create).
 * You have at least one of the supported development boards:
-    * [STM32F3 discovery kit from ST Micro](STM32F303.md)
     * [Arduino Zero hardware](arduino_zero.md)
     * [Olimex/STM32F407ZGT6 Cortex-M4 hardware](olimex.md)
     * [nRF52 Development Kit from Nordic Semiconductor](nRF52.md)
@@ -28,13 +27,8 @@ The tutorials fall into a few broad categories. Some examples in each category a
 * Making an LED blink (the "Hello World" equivalent in the electronics world)
     * [Blinky on Arduino Zero hardware](arduino_zero.md)
     * [Blinky on Olimex/STM32F407ZGT6 Cortex-M4 hardware](olimex.md)
-    * [Blinky on STM32F3 discovery kit from ST Micro](STM32F303.md)
     * [Blinky on nRF52 Development Kit from Nordic Semiconductor](nRF52.md) **Note:** This supports BLE.
-
-    <br>
-
-* Tweaking available apps to customize behavior e.g. making a more exciting LED blink pattern
-    * [Pinwheel Blinky on STM32F3 discovery board](pin-wheel-mods.md)
+    * [Blinky on Redbear Nano2](rbnano2.md)
 
     <br>