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 2016/03/18 00:52:51 UTC
[1/6] incubator-mynewt-site git commit: MYNEWT-251
Repository: incubator-mynewt-site
Updated Branches:
refs/heads/master 46aa2856b -> 1832c8573
MYNEWT-251
rewrite the STMF3Discovery tutorial for new newt commands
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/7da8ae5b
Tree: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/tree/7da8ae5b
Diff: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/diff/7da8ae5b
Branch: refs/heads/master
Commit: 7da8ae5bf124e3edea03eda195c6b1c6b7482eac
Parents: 7fc4a18
Author: Paul Dietrich <pa...@yahoo.com>
Authored: Thu Mar 17 12:15:34 2016 -0700
Committer: Paul Dietrich <pa...@yahoo.com>
Committed: Thu Mar 17 12:15:34 2016 -0700
----------------------------------------------------------------------
docs/os/tutorials/STM32F303.md | 332 ++++++++++++++++--------------------
1 file changed, 151 insertions(+), 181 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/7da8ae5b/docs/os/tutorials/STM32F303.md
----------------------------------------------------------------------
diff --git a/docs/os/tutorials/STM32F303.md b/docs/os/tutorials/STM32F303.md
index 94ec71e..86f1caa 100644
--- a/docs/os/tutorials/STM32F303.md
+++ b/docs/os/tutorials/STM32F303.md
@@ -1,208 +1,178 @@
-## Blinky on STM32F303 board
+## Blinky on STM32F303 Discovery board
### Objective
-Download a generic firmware skeleton ("bootstrap image") that applies to any hardware and then throw in additional applicable pkgs to generate a build for a specific board, namely the STM32F303VC MCU from STMicroelectronics.
+Create a project with a simple app that blinks an LED on the stmf303
+discovery board. Download the application to the target and watch it blink.
-#### Hardware needed
+### What you need
* Discovery kit with STM32F303VC MCU
-* Laptop running Mac OS
+* Laptop running Mac OSX.
+* It is assumed you have already installed newt tool.
+* It is assumed you already installed native tools as described [here](../get_started/native_tools.md)
+Also, we assume that you're familiar with UNIX shells. Let's gets started!
-#### Step by Step Instructions to build image
+### Create a project
-* The first step is to download the generic skeleton of the project. The pkgs constituting the skeleton are not hardware architecture specific. The skeleton is maintained as an app in a separate repository on Apache. You know it is an app because there is an app.yml file.
+Create a new project to hold your work. For a deeper understanding, you can read about project creation in
+[Get Started -- Creating Your First Project](../get_started/project_create.md)
+or just follow the commands below.
-```c
- [user:~/dev]$ newt app create test_project
- Downloading app skeleton from https://git-wip-us.apache.org/repos/asf/incubator-mynewt-tadpole.git... ok!
- app test_project successfully created in ~/dev/go/test_project
-
- [user:~/dev]$ cd test_project/
- [user:~/dev/test_project]$ ls
- README.md compiler hw libs app.yml
+If you've already created a project from another tutorial, you can re-use
+that 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
+
+```
+Don't forget to change into the `myproj` directory.
+
+### Import External STM32F3 Library support
+
+The STM32F303 support for Mynewt lives in an external repository. Its
+necessary to add another repository to the project. To do this,
+edit the file `project.yml` in the root directory of your project `myproj`
+
+This requires two changes to this file.
+
+1. You must defined the properties of the external repository that you want
+to add
+2. You must include the repository in your project.
+
+Edit the file `project.yml` with your favorite editor and add the
+following repository details in the file (after the core
+repository). This gives newt the information to contact the repository
+and extract its contents. In this case, the repository is on github in
+the runtimeinc collection. Its name is mynewt-stm32f3 and we will accept
+any version up to the latest.
+
+```no-highlight
+repository.mynewt_stm32f3:
+ type: github
+ vers: 0-latest
+ user: runtimeinc
+ repo: mynewt_stm32f3
```
-* Next, the pkg-list named larva is added from the app (also named larva) from another repository on Apache. This step simply downloads the pkg-list description file and does not actually install the pkgs that constitute the pkg-list. The pkg-list description file (`pkg-list.yml`) will be used to check dependencies during the pkg install to ensure completeness. It serves as a reference for all the pkgs in the pkg-list that one can choose from and install.
-```c
- [user:~/dev/test_project]$ newt app add-pkg-list larva https://git-wip-us.apache.org/repos/asf/incubator-mynewt-larva.git
- Downloading pkg-list.yml from https://git-wip-us.apache.org/repos/asf/incubator-mynewt-larva.git/master... ok!
- Verifying pkg-list.yml format...
- ok!
- pkg-list larva successfully installed to app.
+In the same file, add the following highlighted line to the
+`project.repositories` variable. This tells newt to download the
+ repository contents into your project.
+
+```hl_lines="3"
+project.repositories:
+ - apache-mynewt-core
+ - mynewt_stm32f3
```
-* The next step is to install relevant pkgs from the larva app from git server on Apache. The instructions assume that you know what application or project you are interested in (the blinky application, in this case), what hardware you are using (STM32F3DISCOVERY board, in this case) and hence, what board support package you need.
-
-```c
-
- [user:~/dev/test_project]$ newt pkg install project/blinky
- Downloading larva from https://git-wip-us.apache.org/repos/asf/incubator-mynewt-larva/master... ok!
- Installing project/blinky
- Installing libs/console/full
- Installing libs/shell
- Installation was a success!
-
- [user:~/dev/test_project]$ newt pkg install hw/bsp/stm32f3discovery
- Downloading larva from https://git-wip-us.apache.org/repos/asf/incubator-mynewt-larva/master... ok!
- Installing hw/bsp/stm32f3discovery
- Installing hw/mcu/stm/stm32f3xx
- Installing libs/cmsis-core
- Installing compiler/arm-none-eabi-m4
- Installation was a success!
+### Install dependencies
+
+Now you can install this into the project using:
+
+```no-highlight
+$ newt install -v
+Downloading repository description for apache-mynewt-core... success!
+...
+apache-mynewt-core successfully installed version 0.7.9-none
+...
+Downloading repository description for mynewt_stm32f3... success!
+Downloading repository mynewt_stm32f3
+...
+Resolving deltas: 100% (65/65), done.
+Checking connectivity... done.
+mynewt_stm32f3 successfully installed version 0.0.0-none
```
+
+### Create targets
+
+Create two target to build using the stmf3 board support package and the
+app blinky example from mynewt. This output of these commands are not
+shown here from brevity.
+
+The first target is the application image itself. The second
+target the bootloader which allows you to upgrade your mynewt
+applications.
+
+
+```no-highlight
+$ newt target create stmf3_blinky
+$ newt target set stmf3_blinky build_profile=optimized
+$ newt target set stmf3_blinky bsp=@mynewt_stm32f3/hw/bsp/stm32f3discovery
+$ newt target set stmf3_blinky app=apps/blinky
+
+$ newt target create stmf3_boot
+$ newt target set stmf3_boot app=@apache-mynewt-core/apps/boot
+$ newt target set stmf3_boot bsp=@mynewt_stm32f3/hw/bsp/stm32f3discovery
+$ newt target set stmf3_boot build_profile=optimized
+
+$ newt target show
+
+targets/stmf3_blinky
+ app=apps/blinky
+ bsp=@mynewt_stm32f3/hw/bsp/stm32f3discovery
+ build_profile=optimized
+targets/stmf3_boot
+ app=apps/boot
+ bsp=@mynewt_stm32f3/hw/bsp/stm32f3discovery
+ build_profile=optimized
+```
+
+### Build the images
+
+To build the images, use the `newt build` command below.
-* It's time to create a targets for the project and define the target attributes. STM32F3 BSP expects bootloader, so create targets for both blinky and bootloader.
-```c
- [user:~/dev/test_project]$ newt target create blink_f3disc
- Creating target blink_f3disc
- Target blink_f3disc successfully created!
-
- [user:~/dev/test_project]$ newt target set blink_f3disc project=blinky
- Target blink_f3disc successfully set project to blinky
-
- [user:~/dev/test_project]$ newt target set blink_f3disc bsp=hw/bsp/stm32f3discovery
- Target blink_f3disc successfully set bsp to hw/bsp/stm32f3discovery
-
- [user:~/dev/test_project]$ newt target set blink_f3disc compiler_def=debug
- Target blink_f3disc successfully set compiler_def to debug
-
- [user:~/dev/test_project]$ newt target set blink_f3disc compiler=arm-none-eabi-m4
- Target blink_f3disc successfully set compiler to arm-none-eabi-m4
-
- [user:~/dev/test_project]$ newt target set blink_f3disc arch=cortex_m4
- Target blink_f3disc successfully set arch to cortex_m4
-
- [user:~/dev/test_project]$ newt target create boot_f3disc
- Creating target boot_f3disc
- Target boot_f3disc successfully created!
-
- [user:~/dev/test_project]$ newt target set boot_f3disc project=boot
- Target blink_f3disc successfully set project to blinky
-
- [user:~/dev/test_project]$ newt target set boot_f3disc bsp=hw/bsp/stm32f3discovery
- Target boot_f3disc successfully set bsp to hw/bsp/stm32f3discovery
-
- [user:~/dev/test_project]$ newt target set boot_f3disc compiler_def=optimized
- Target boot_f3disc successfully set compiler_def to debug
-
- [user:~/dev/test_project]$ newt target set boot_f3disc compiler=arm-none-eabi-m4
- Target boot_f3disc successfully set compiler to arm-none-eabi-m4
-
- [user:~/dev/test_project]$ newt target set boot_f3disc arch=cortex_m4
- Target boot_f3disc successfully set arch to cortex_m4
-
- [user:~/dev/test_project]$ newt target show blink_f3disc
- blink_f3disc
- arch=cortex_m4
- bsp=hw/bsp/stm32f3discovery
- compiler=arm-none-eabi-m4
- compiler_def=debug
- name=blink_f3disc
- project=blinky
-
- [user:~/dev/test_project]$ newt target show boot_f3disc
- boot_f3disc
- arch=cortex_m4
- bsp=hw/bsp/stm32f3discovery
- compiler=arm-none-eabi-m4
- compiler_def=debug
- name=blink_f3disc
- project=boot
+```no-highlight
+$ newt build stmf3_blinky
+ ...
+Archiving stm32f3discovery.a
+Linking blinky.elf
+App successfully built: ~/dev/myproj/bin/stmf3_blinky/apps/blinky/blinky.elf
+$ newt build stmf3_boot
+Compiling log_shell.c
+Archiving log.a
+Linking boot.elf
+App successfully built: ~/dev/myproj/bin/stmf3_boot/apps/boot/boot.elf
```
-* STM32F3 blinky project is too large to operate with newlib libc. You need to modify project/blinky/pkg.yml, and switch over to using baselibc.
-
-```c
- [user:~/dev/test_project]$ cat project/blinky/pkg.yml
- #
- # Licensed to the Apache Software Foundation (ASF) under one
- # or more contributor license agreements. See the NOTICE file
- # distributed with this work for additional information
- # regarding copyright ownership. The ASF licenses this file
- # to you under the Apache License, Version 2.0 (the
- # "License"); you may not use this file except in compliance
- # with the License. You may obtain a copy of the License at
- #
- # http://www.apache.org/licenses/LICENSE-2.0
- #
- # Unless required by applicable law or agreed to in writing,
- # software distributed under the License is distributed on an
- # "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- # KIND, either express or implied. See the License for the
- # specific language governing permissions and limitations
- # under the License.
- #
-
- pkg.name: project/blinky
- pkg.vers: 0.8.0
- pkg.description: Basic example application which blinks an LED.
- pkg.author: Marko Kiiskila <ma...@runtime.io>
- pkg.homepage: http://mynewt.apache.org/os/get_acclimated/project2/
- pkg.repository: https://git-wip-us.apache.org/repos/asf/incubator-mynewt-larva
- pkg.keywords:
-
- pkg.deps:
- - libs/console/full
- - libs/newtmgr
- - libs/os
- - libs/shell
- - sys/config
- - sys/log
- - sys/stats
- - libs/baselibc
+### Create an application image from the binary
+
+You must sign and version your application image to download it using newt. Use
+the `newt create-image` command to perform this action. Here we assign this
+image an arbitrary version `1.2.3`.
+
+```no-highlight
+$ newt create-image stmf3_blinky 1.2.3
+App image succesfully generated: ~/dev/myproj/bin/stmf3_blinky/apps/blinky/blinky.img
+Build manifest:~/dev/myproj/bin/stmf3_blinky/apps/blinky/manifest.json
```
-* Next, you get to build the targets and generate an executable that can then be uploaded to the board. The STM32F3DISCOVERY board includes an ST-LINK/V2 embedded debug tool interface that will be used to program/debug the board. To program the MCU on the board, simply plug in the two jumpers on CN4, as shown in the picture in red. If you want to learn more about the board you will find the User Manual at [http://www.st.com/st-web-ui/static/active/jp/resource/technical/document/user_manual/DM00063382.pdf](http://www.st.com/st-web-ui/static/active/jp/resource/technical/document/user_manual/DM00063382.pdf)
+### Configure the hardware
+
+
+ The STM32F3DISCOVERY board includes an ST-LINK/V2 embedded debug tool interface that will be used to program/debug the board. To program the MCU on the board, simply plug in the two jumpers on CN4, as shown in the picture in red. If you want to learn more about the board you will find the User Manual at [http://www.st.com/st-web-ui/static/active/jp/resource/technical/document/user_manual/DM00063382.pdf](http://www.st.com/st-web-ui/static/active/jp/resource/technical/document/user_manual/DM00063382.pdf)
* 
-```c
- [user:~/dev/test_project]$ newt target build boot_f3disc
- Building target boot_f3 (project = boot)
- Compiling asprintf.c
- Compiling atoi.c
- ...
- ...
- Assembling startup_stm32f303xc.s
- Archiving libstm32f3discovery.a
- Compiling boot.c
- Building project boot
- Linking boot.elf
- Successfully run!
-
- [user:~/dev/test_project]$ newt target build blink_f3disc
- Building target blink_f3disc (project = blinky)
- Compiling asprintf.c
- Compiling atoi.c
- ...
- ...
- Assembling startup_stm32f303xc.s
- Archiving libstm32f3discovery.a
- Compiling main.c
- Building project blinky
- Linking blinky.elf
- Successfully run!
-
- [user:~/dev/test_project]$ newt target build boot_f3disc
- Building target boot_f3disc (project = boot)
- Building project boot
- Successfully run!
-
- [user:~/dev/test_project]$ newt target create-image blink_f3disc 0.0.1
- Building target blink_f3disc (project = blinky)
- Building project blinky
+### Download the Images
-```
+use the `newt load` command to download the images to the target board.
-* Finally, you have to download the image on to the board. You will see a blue light start to blink.
-```c
- [user:~/dev/test_project]$ newt target download boot_f3disc
- Downloading with /Users/user/dev/test_project/hw/bsp/stm32f3discovery/stm32f3discovery_download.sh
+```no-highlight
+$ newt -v load stmf3_boot
+$ newt -v load stmf3_blinky
+```
- [user:~/dev/test_project]$ newt target download blink_f3disc
- Downloading with /Users/user/dev/test_project/hw/bsp/stm32f3discovery/stm32f3discovery_download.sh
-```
-
+### Congratulations
+
+You have built, downloaded, and run your first application using mynewt for the
+stf32f3 discovery board. One of the LEDs on the LED wheel shoul be blinking
+at 1 Hz.
\ No newline at end of file
[6/6] incubator-mynewt-site git commit: minor modifications to pull
request #56. This closes #56.
Posted by ad...@apache.org.
minor modifications to pull request #56. This closes #56.
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/1832c857
Tree: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/tree/1832c857
Diff: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/diff/1832c857
Branch: refs/heads/master
Commit: 1832c85735025a429fc9cb5631c5b0570d8b141a
Parents: 1fb01dc
Author: aditihilbert <ad...@runtime.io>
Authored: Thu Mar 17 16:52:42 2016 -0700
Committer: aditihilbert <ad...@runtime.io>
Committed: Thu Mar 17 16:52:42 2016 -0700
----------------------------------------------------------------------
docs/os/tutorials/STM32F303.md | 64 ++++++++++++++++++++++++++-----------
1 file changed, 45 insertions(+), 19 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/1832c857/docs/os/tutorials/STM32F303.md
----------------------------------------------------------------------
diff --git a/docs/os/tutorials/STM32F303.md b/docs/os/tutorials/STM32F303.md
index 86f1caa..427a42a 100644
--- a/docs/os/tutorials/STM32F303.md
+++ b/docs/os/tutorials/STM32F303.md
@@ -1,10 +1,14 @@
## Blinky on STM32F303 Discovery board
+<br>
+
### Objective
Create a project with a simple app that blinks an LED on the stmf303
discovery board. Download the application to the target and watch it blink.
+<br>
+
### What you need
* Discovery kit with STM32F303VC MCU
@@ -14,6 +18,8 @@ discovery board. Download the application to the target and watch it blink.
Also, we assume that you're familiar with UNIX shells. Let's gets started!
+<br>
+
### Create a project
Create a new project to hold your work. For a deeper understanding, you can read about project creation in
@@ -23,7 +29,7 @@ or just follow the commands below.
If you've already created a project from another tutorial, you can re-use
that project.
-```no-highlight
+```
$ mkdir ~/dev
$ cd ~/dev
$ newt new myproj
@@ -34,17 +40,20 @@ Project myproj successfully created.
$ cd myproj
```
-Don't forget to change into the `myproj` directory.
+
+**Note:** Don't forget to change into the `myproj` directory.
+
+<br>
### Import External STM32F3 Library support
-The STM32F303 support for Mynewt lives in an external repository. Its
+The STM32F303 support for Mynewt lives in an external repository. It's
necessary to add another repository to the project. To do this,
edit the file `project.yml` in the root directory of your project `myproj`
This requires two changes to this file.
-1. You must defined the properties of the external repository that you want
+1. You must define the properties of the external repository that you want
to add
2. You must include the repository in your project.
@@ -52,10 +61,10 @@ Edit the file `project.yml` with your favorite editor and add the
following repository details in the file (after the core
repository). This gives newt the information to contact the repository
and extract its contents. In this case, the repository is on github in
-the runtimeinc collection. Its name is mynewt-stm32f3 and we will accept
-any version up to the latest.
+the `runtimeinc` collection. Its name is `mynewt-stm32f3` and we will accept
+any version up to the latest. You can look at the contents [here](https://github.com/runtimeinc/mynewt_stm32f3).
-```no-highlight
+```
repository.mynewt_stm32f3:
type: github
vers: 0-latest
@@ -63,6 +72,8 @@ repository.mynewt_stm32f3:
repo: mynewt_stm32f3
```
+<br>
+
In the same file, add the following highlighted line to the
`project.repositories` variable. This tells newt to download the
repository contents into your project.
@@ -73,11 +84,13 @@ project.repositories:
- mynewt_stm32f3
```
+<br>
+
### Install dependencies
Now you can install this into the project using:
-```no-highlight
+```
$ newt install -v
Downloading repository description for apache-mynewt-core... success!
...
@@ -90,19 +103,22 @@ Resolving deltas: 100% (65/65), done.
Checking connectivity... done.
mynewt_stm32f3 successfully installed version 0.0.0-none
```
+
+<br>
+
### Create targets
-Create two target to build using the stmf3 board support package and the
-app blinky example from mynewt. This output of these commands are not
-shown here from brevity.
+Create two targets to build using the stmf3 board support package and the
+app blinky example from mynewt. The output of these commands are not
+shown here for brevity.
The first target is the application image itself. The second
-target the bootloader which allows you to upgrade your mynewt
+target is the bootloader which allows you to upgrade your mynewt
applications.
-```no-highlight
+```
$ newt target create stmf3_blinky
$ newt target set stmf3_blinky build_profile=optimized
$ newt target set stmf3_blinky bsp=@mynewt_stm32f3/hw/bsp/stm32f3discovery
@@ -125,11 +141,13 @@ targets/stmf3_boot
build_profile=optimized
```
+<br>
+
### Build the images
To build the images, use the `newt build` command below.
-```no-highlight
+```
$ newt build stmf3_blinky
...
Archiving stm32f3discovery.a
@@ -143,6 +161,8 @@ Linking boot.elf
App successfully built: ~/dev/myproj/bin/stmf3_boot/apps/boot/boot.elf
```
+<br>
+
### Create an application image from the binary
You must sign and version your application image to download it using newt. Use
@@ -155,6 +175,8 @@ App image succesfully generated: ~/dev/myproj/bin/stmf3_blinky/apps/blinky/blink
Build manifest:~/dev/myproj/bin/stmf3_blinky/apps/blinky/manifest.json
```
+<br>
+
### Configure the hardware
@@ -162,17 +184,21 @@ Build manifest:~/dev/myproj/bin/stmf3_blinky/apps/blinky/manifest.json
* 
+<br>
+
### Download the Images
-use the `newt load` command to download the images to the target board.
+Use the `newt load` command to download the images to the target board.
-```no-highlight
+```
$ newt -v load stmf3_boot
$ newt -v load stmf3_blinky
```
-### Congratulations
+<br>
+
+### Watch the LED blink
-You have built, downloaded, and run your first application using mynewt for the
-stf32f3 discovery board. One of the LEDs on the LED wheel shoul be blinking
+Congratulations! You have built, downloaded, and run your first application using mynewt for the
+stf32f3 discovery board. One of the LEDs on the LED wheel should be blinking
at 1 Hz.
\ No newline at end of file
[3/6] incubator-mynewt-site git commit: rearranged tutorials. Added
intro to tutorials and quick start
Posted by ad...@apache.org.
rearranged tutorials. Added intro to tutorials and quick start
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/b02507e1
Tree: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/tree/b02507e1
Diff: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/diff/b02507e1
Branch: refs/heads/master
Commit: b02507e1f29f9cad4c6e01b2227ce8e9837a0d62
Parents: 46aa285
Author: aditihilbert <ad...@runtime.io>
Authored: Thu Mar 17 16:35:38 2016 -0700
Committer: aditihilbert <ad...@runtime.io>
Committed: Thu Mar 17 16:35:38 2016 -0700
----------------------------------------------------------------------
docs/os/core_os/mutex/mutex.md | 2 +-
docs/os/get_started/get_started.md | 12 ++++
docs/os/tutorials/how_to_edit_docs.md | 104 ++++-------------------------
docs/os/tutorials/tutorials.md | 16 +++++
docs/os/tutorials/unit_test.md | 2 +-
mkdocs.yml | 8 ++-
6 files changed, 48 insertions(+), 96 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/b02507e1/docs/os/core_os/mutex/mutex.md
----------------------------------------------------------------------
diff --git a/docs/os/core_os/mutex/mutex.md b/docs/os/core_os/mutex/mutex.md
index ce123ca..c397aa4 100644
--- a/docs/os/core_os/mutex/mutex.md
+++ b/docs/os/core_os/mutex/mutex.md
@@ -16,7 +16,7 @@ Note that when multiple tasks are waiting on a mutex owned by another task, once
### Data structures
-```c
+```c
struct os_mutex
{
SLIST_HEAD(, os_task) mu_head;
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/b02507e1/docs/os/get_started/get_started.md
----------------------------------------------------------------------
diff --git a/docs/os/get_started/get_started.md b/docs/os/get_started/get_started.md
new file mode 100644
index 0000000..0f45918
--- /dev/null
+++ b/docs/os/get_started/get_started.md
@@ -0,0 +1,12 @@
+## Quick Start
+
+If you are curious about Mynewt and want to get a quick feel for the project, you've come to the right place. We have three sets of instructions for you to try out.
+
+* [Installing Native Tools](native_tools.md) - to run Mynewt OS natively (on your machine)
+* [Creating Your First Project](project_create.md) - on simulated hardware
+* [Installing Cross Tools for ARM](cross_tools.md) - to get prepared to play with hardware
+
+**Send us an email on the dev@ mailing list if you have comments or suggestions!** If you haven't joined the mailing list, you will find the links [here](../../community.md).
+
+<br>
+
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/b02507e1/docs/os/tutorials/how_to_edit_docs.md
----------------------------------------------------------------------
diff --git a/docs/os/tutorials/how_to_edit_docs.md b/docs/os/tutorials/how_to_edit_docs.md
index d1cb3e5..b3229c6 100644
--- a/docs/os/tutorials/how_to_edit_docs.md
+++ b/docs/os/tutorials/how_to_edit_docs.md
@@ -8,9 +8,7 @@ Learn the process of editing docs by adding some content to a test document.
The Mynewt documentation you see on the Apache incubator website is a bunch of HTML files generated using MkDocs which is a simple static site generation tool geared towards building project documentation. You can read about it at [http://www.mkdocs.org](http://www.mkdocs.org). Documentation source files are written in Markdown, and configured with a single YAML configuration file. Markdown is a lightweight markup language with plain text formatting syntax designed so that it can be converted to HTML and many other formats using a tool (which in our case is MkDocs).
-You do not need to install MkDocs unless you want to actually render your documentation in HTML in order to preview it before pushing your content to the remote repository. Typically, using a Markdown editor such as [Mou](http://25.io/mou/) is enough to check how it will look after the document has gone through MkDocs. Go ahead and download [Mou](http://25.io/mou/). If you are on a Windows machine, download the [editor of your choice](http://alternativeto.net/software/mou/?platform=windows).
-
-Currently someone in the project is designated to use MkDocs to generate the HTML pages periodically after changes have been reviewed and accepted into the master branch.
+The HTML pages are generated periodically after changes have been reviewed and accepted into the master branch.
### Access to the Apache repo
@@ -19,104 +17,28 @@ Get an account on Apache. You do not need a committer account to view the websit
If you are not a committer, you may follow the proposed non-committer workflow to share your work. The direct link to the proposed workflow is [https://git-wip-us.apache.org/docs/workflow.html](https://git-wip-us.apache.org/docs/workflow.html). You will find the steps described in more detail later in this tutorial.
-### Making a local copy
-
-* Copy the document source files into a local directory and look at the contents of the copied directory to get an idea of the directory structure. Use http instead of https if you are a non-committer.
-```c
- $ git clone https://git-wip-us.apache.org/repos/asf/incubator-mynewt-site.git
- Cloning into 'incubator-mynewt-site'...
- remote: Counting objects: 330, done.
- remote: Compressing objects: 100% (263/263), done.
- remote: Total 330 (delta 120), reused 0 (delta 0)
- Receiving objects: 100% (330/330), 4.34 MiB | 830.00 KiB/s, done.
- Resolving deltas: 100% (120/120), done.
- Checking connectivity... done.
- $ ls
- incubator-mynewt-site
- $ ls incubator-mynewt-site/
- docs images mkdocs.yml
+### Editing an existing page
+
+* Create a fork on the [github mirror](https://github.com/apache/incubator-mynewt-site).
+*
+* Then create a new branch to work on your documentation and move to that branch.
```
-* Create a new branch to work on your documentation and move to that branch.
-```c
$ git checkout -b <your-branch-name>
```
-### File to be edited
-
-The file you will edit is named try_markdown.md. It is in the incubator-mynewt-site/docs/os/tutorials/ directory.
-
-### Editing an existing page
-
-* Open the application Mou.
-
-* Open the file incubator-mynewt-site/docs/os/tutorials/try_markdown.md in Mou.
-
-* Edit the last item on the list.
-
-* Save and quit the application.
+* Make changes directly on github.com. Generate a pull request. Alternatively, you can edit locally on your machine, push the branch (or the changes in the branch) to your fork on github.com, and then generate a pull request.
### Adding a new page
-If you create a new file somewhere in the `docs` subdirectory to add a new page, you have to add a line in the `mkdocs.yml` file at the correct level. For example, if you add a new module named "Ethernet" by creating a new file named `ethernet.md` in the `modules` subdirectory, you have to insert the following line under `Modules:` in the `mkdocs.yml` file.
-```c
- - 'Ethernet': 'modules/ethernet.md'
-```
-### Pushing changes to remote as a committer
+If you create a new file somewhere in the `docs` subdirectory to add a new page, you have to add a line in the `mkdocs.yml` file at the correct level. For example, if you add a new module named "Wi-Fi" by creating a new file named `wifi.md` in the `network` directory, you have to insert the following line under `Networking User Guide` in the `mkdocs.yml` file (at the same level as the `docs` directory). In this example, a link will show up in the navigation bar on the left under "Networking User Guide" titled "Wi-Fi" and take the user to the contents of the 'wifi.md' file when the link is clicked. ** Note: The change will show up on this [Mynewt site](http://mynewt.apache.org) only after your pull request is merged in and the updated site is generated.**
-If you are not a committer yet, skip this section and proceed to the [next section](#sharing-changes-as-a-non-committer).
-
-* Check whether your remote git repository is set up. If you see the remote location as shown below you can skip the next step.
-```c
- $ git remote -v
- origin https://git-wip-us.apache.org/repos/asf/incubator-mynewt-site.git (fetch)
- origin https://git-wip-us.apache.org/repos/asf/incubator-mynewt-site.git (push)
```
-* If, however, you do not see your remote repository, then set it up as follows.
-
-```c
- $ git remote add origin https://git-wip-us.apache.org/repos/asf/incubator-mynewt-site.git
-```
-* First check the git status. It will show you that the `try_markdown.md` document has been modified. So you will stage a commit, and then commit the change. Finally, you will push the changes to the remote repository.
-
- During staging below using `git add`, we use the `-A` option indicating you want to stage all your modifications. Instead, you can choose to specify only the files that you want to. The commit message (specified after `-m`) should summarize what your changes are about.
-```c
- $ git status
- $ git add -A
- $ git commit -m "My first doc change as a trial run"
- $ git push -u origin <your-branch-name>
-```
-* You can see the changed Markdown file if you traverse the tree on the git repository [ https://git-wip-us.apache.org/repos/asf/incubator-mynewt-site.git]( https://git-wip-us.apache.org/repos/asf/incubator-mynewt-site.git).
-
-* A commit notification automatically goes out to the commits@mynewt.incubator.apache.org mailing list. The "upstream" manager pulls the notified changes, reviews it, and merges it to the master branch if all is well. Otherwise you get an email for further changes.
-
-### Sharing changes as a non-committer
-
-We suggest you follow the proposed non-committer workflow at Apache to share your work. The direct link to the proposed workflow is [https://git-wip-us.apache.org/docs/workflow.html](https://git-wip-us.apache.org/docs/workflow.html).
-
-* Assuming you have made changes to the example file, you will first commit your changes.
-```c
- $ git add -A
- $ git commit -m "My first doc change as a trial run"
+ - 'Wi-Fi': 'wifi.md'
```
-* Once you're ready to share your changes with the rest of the project team, you can use the git format-patch command to produce a patch file (or a nice set of patches in the future) and email the patch file to dev@mynewt.incubator.apache.org. Later on you may attach multiple files in your email to the mailing list as part of an existing thread or a new one. Remember to summarize the issue you have tackled and your work if the commit message is not detailed enough.
-
- If there is a JIRA ticket associated with your work you should post your patch files to the ticket.
-
-```c
- $ git format-patch origin/trunk
-```
-
-* Alternatively, you can use the mirror on github.com to submit a pull request. The mirror is located at [https://github.com/apache/incubator-mynewt-site](https://github.com/apache/incubator-mynewt-site). It is up to you to decide whether to create a fork or a branch to work in and submit pull requests from. Remember you cannot push changes to the master on the github mirror, so you have to create a fork or a branch first. Your pull request will be reviewed by a committer for docs and merged into the master branch when the changes are understood and accepted.
-
-
-### Conversion to HTML
-
-The conversion of the Markdown files to HTML for the website happens manually and statically using MkDocs. You cannot see automatic and immediate rendering in HTML upon making a change in the Markdown file. You can choose to stop here and proceed to changing other Markdown files in your branch.
-
### Local preview of HTML files
-However, you have the option to download MkDocs and do a local conversion yourself to preview the pages using the built-in devserver that comes with MkDocs. But first you will have to install MkDocs for that. In order to install MkDocs you'll need Python installed on your system, as well as the Python package manager, pip. You can check if you have them already (usually you will).
-```c
+You have the option to install MkDocs and do a local conversion yourself to preview the pages using the built-in webserver that comes with MkDocs. In order to install MkDocs you'll need Python installed on your system, as well as the Python package manager, pip. You can check if you have them already (usually you will).
+```
$ python --version
Python 2.7.2
$ pip --version
@@ -124,11 +46,11 @@ However, you have the option to download MkDocs and do a local conversion yourse
$ pip install mkdocs
```
You will then run the built-in webserver from the root of the documentation directory using the command `mkdocs serve`. The root directory for documentation is `incubator-mynewt-site` or the directory with the `mkdocs.yml` file.
-```c
+```
$ ls
docs images mkdocs.yml
$ mkdocs serve
```
-Then go to [http://127.0.0.1:8000](http://127.0.0.1:8000) to preview your pages and see how they will look on the website! Remember that the Myself website itself will not be updated.
+Then go to [http://127.0.0.1:8000](http://127.0.0.1:8000) to preview your pages and see how they will look on the website. **Remember that the Myself website itself will not be updated.**
For more information on MkDocs go to [http://www.mkdocs.org](http://www.mkdocs.org).
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/b02507e1/docs/os/tutorials/tutorials.md
----------------------------------------------------------------------
diff --git a/docs/os/tutorials/tutorials.md b/docs/os/tutorials/tutorials.md
new file mode 100644
index 0000000..2e57243
--- /dev/null
+++ b/docs/os/tutorials/tutorials.md
@@ -0,0 +1,16 @@
+## Tutorials
+
+If the introduction to Mynewt has piqued your interest and you want to familiarize yourself with some of its functionality, this series of tutorials is for you. The lessons are aimed at the beginner.
+
+* [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.
+* [Add a unit Test for a Package](unit_test.md)
+* [Add an air-quality sensor](air_quality_sensor.md)
+* [How to contribute to docs](how_to_edit_docs.md)
+
+**Send us an email on the dev@ mailing list if you have comments or suggestions!** If you haven't joined the mailing list, you will find the links [here](../../community.md).
+
+<br>
+
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/b02507e1/docs/os/tutorials/unit_test.md
----------------------------------------------------------------------
diff --git a/docs/os/tutorials/unit_test.md b/docs/os/tutorials/unit_test.md
index 985085f..c94f819 100644
--- a/docs/os/tutorials/unit_test.md
+++ b/docs/os/tutorials/unit_test.md
@@ -1,4 +1,4 @@
-# How To Write A Test Suite for Your Package
+# Write a Test Suite for a Package
This document presents a tutorial which guides the reader through writing
a test suite for a Mynewt package (new or existing).
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/b02507e1/mkdocs.yml
----------------------------------------------------------------------
diff --git a/mkdocs.yml b/mkdocs.yml
index e680744..f1e0a71 100644
--- a/mkdocs.yml
+++ b/mkdocs.yml
@@ -13,18 +13,20 @@ pages:
- Mynewt OS Manual:
- Introduction: 'os/get_started/introduction.md'
- Get Started:
+ - toc: 'os/get_started/get_started.md'
- 'Installing Native Tools': 'os/get_started/native_tools.md'
- 'Creating Your First Project': 'os/get_started/project_create.md'
- 'Installing Cross Tools for ARM': 'os/get_started/cross_tools.md'
- 'Concepts':
- toc: 'os/get_started/vocabulary.md'
- Tutorials:
+ - toc: 'os/tutorials/tutorials.md'
+ - 'Blinky on Arduino Zero': 'os/tutorials/arduino_zero.md'
- 'Blinky on Olimex': 'os/tutorials/olimex.md'
- 'Blinky on STM32F303': 'os/tutorials/STM32F303.md'
- 'Blinky on nRF52': 'os/tutorials/nRF52.md'
- - 'Blinky on Arduino Zero': 'os/tutorials/arduino_zero.md'
- - 'Unit Testing a Package': 'os/tutorials/unit_test.md'
- - 'Adding an air-quality sensor': 'os/tutorials/air_quality_sensor.md'
+ - 'Write a Test Suite for a Package': 'os/tutorials/unit_test.md'
+ - 'Air-quality Sensor project': 'os/tutorials/air_quality_sensor.md'
- 'Edit Docs': 'os/tutorials/how_to_edit_docs.md'
- OS User Guide:
- OS Core:
[5/6] incubator-mynewt-site git commit: Merge branch 'MYNEWT-251' of
https://github.com/paulfdietrich/incubator-mynewt-site
Posted by ad...@apache.org.
Merge branch 'MYNEWT-251' of https://github.com/paulfdietrich/incubator-mynewt-site
This closes #56
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/1fb01dc5
Tree: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/tree/1fb01dc5
Diff: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/diff/1fb01dc5
Branch: refs/heads/master
Commit: 1fb01dc5ed178e2152e64add810293af3c507e87
Parents: 4f64fe7 7da8ae5
Author: aditihilbert <ad...@runtime.io>
Authored: Thu Mar 17 16:40:24 2016 -0700
Committer: aditihilbert <ad...@runtime.io>
Committed: Thu Mar 17 16:40:24 2016 -0700
----------------------------------------------------------------------
docs/os/tutorials/STM32F303.md | 332 ++++++++++++++++--------------------
1 file changed, 151 insertions(+), 181 deletions(-)
----------------------------------------------------------------------
[2/6] incubator-mynewt-site git commit: MYNEWT-250
Posted by ad...@apache.org.
MYNEWT-250
more changes for Olimex. Had some left over refernces to the
git clone method/
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/2ca1ecdb
Tree: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/tree/2ca1ecdb
Diff: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/diff/2ca1ecdb
Branch: refs/heads/master
Commit: 2ca1ecdb177a12f97a8213f4d60c8fb4b0095bbf
Parents: 7fc4a18
Author: Paul Dietrich <pa...@yahoo.com>
Authored: Thu Mar 17 12:31:42 2016 -0700
Committer: Paul Dietrich <pa...@yahoo.com>
Committed: Thu Mar 17 12:31:42 2016 -0700
----------------------------------------------------------------------
docs/os/tutorials/Olimex.md | 73 ++++++++++++++++++----------------------
1 file changed, 32 insertions(+), 41 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/2ca1ecdb/docs/os/tutorials/Olimex.md
----------------------------------------------------------------------
diff --git a/docs/os/tutorials/Olimex.md b/docs/os/tutorials/Olimex.md
index 0a6f50e..0172188 100644
--- a/docs/os/tutorials/Olimex.md
+++ b/docs/os/tutorials/Olimex.md
@@ -70,18 +70,14 @@ or just follow the commands below.
#### Create a target
-Change directory to ~/dev/core directory and define the *blinky* target inside core, using the *newt* tool. Starting with the target name, assign specific aspects of the project, as shown below, to pull the appropriate packages and build the right bundle or list for the board. For example, we set the build_profile, board support package (bsp), and app.
+Change directory to ~/dev/myproj directory and define the *blinky* target inside myproj, using the *newt* tool. Starting with the target name, assign specific aspects of the project, as shown below, to pull the appropriate packages and build the right bundle or list for the board. For example, we set the build_profile, board support package (bsp), and app.
```no-highlight
$ newt target create blinky
- Target targets/blinky successfully created
$ newt target set blinky build_profile=debug
- Target targets/blinky successfully set target.compiler_def to debug
$ newt target set blinky bsp=@apache-mynewt-core/hw/bsp/olimex_stm32-e407_devboard
- Target targets/blinky successfully set target.bsp to ...
- $ newt target set blinky app=@apache-mynewt-core/apps/blinky
- Target targets/blinky successfully set target.app to apps/blinky
+ $ newt target set blinky app=apps/blinky
$ newt target show blinky
targets/boot_olimex
app=apps/blinky
@@ -98,22 +94,22 @@ Next, let's build the image with the above values assigned. By default, the link
<font color="red">
(We are working to simplify this scheme whereby an executable for a project will correctly elect the linker scripts and generate the relevant image. For example, the scheme will key on project identity such as bootloader, RAM, Flash (default) and build accordingly.) </font>.
-Afer you build the target, you can find the executable *blinky.elf* in the project directory *~/dev/core/bin/blinky/apps/blinky/.*
+Afer you build the target, you can find the executable *blinky.elf* in the project directory *~/dev/myproj/bin/blinky/apps/blinky/.*
```no-highlight
- $ cd ~/dev/core/hw/bsp/olimex_stm32-e407_devboard
+ $ cd ~/dev/myproj/repos/apache-mynewt-core/hw/bsp/olimex_stm32-e407_devboard/
$ diff olimex_stm32-e407_devboard.ld run_from_sram.ld
(some diff will be displayed)
$ cp run_from_sram.ld olimex_stm32-e407_devboard.ld
- $ cd ~/dev/core
+ $ cd ~/dev/myproj
$ newt build blinky
Compiling case.c
Compiling suite.c
...
Linking blinky.elf
- App successfully built:~/dev/core/bin/blinky/apps/blinky/blinky.elf
- $ ls bin/blinky/apps/blinky/
+ App successfully built:~/dev/myproj/bin/blinky/apps/blinky/blinky.elf
+ $ ls ~/dev/myproj/bin/blinky/apps/blinky/
blinky.elf blinky.elf.bin blinky.elf.cmd
blinky.elf.lst blinky.elf.map
```
@@ -168,7 +164,7 @@ To locate the bootloader, the board searches in three places: User Flash Memory,
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 gdb tool and load the image on it. For example,
```no-highlight
- (gdb) set $msp=0x10010000
+ (gdb) set $msp=0x10010000
```
<br>
@@ -176,14 +172,14 @@ Check the value of the msp (main service pointer) register. If it is not 0x10010
Now load the image and type "c" or "continue" from the GNU debugger.
```no-highlight
- (gdb) load ~/dev/core/bin/blinky/apps/blinky/blinky.elf
- Loading section .text, size 0x16b88 lma 0x20000000
- Loading section .ARM.exidx, size 0x18 lma 0x20016b88
- Loading section .data, size 0x9ec lma 0x20016ba0
- Start address 0x200004b8, load size 95628
- Transfer rate: 74 KB/sec, 3825 bytes/write.
- (gdb) c
- Continuing.
+ (gdb) load ~/dev/myproj/bin/blinky/apps/blinky/blinky.elf
+ Loading section .text, size 0x16b88 lma 0x20000000
+ Loading section .ARM.exidx, size 0x18 lma 0x20016b88
+ Loading section .data, size 0x9ec lma 0x20016ba0
+ Start address 0x200004b8, load size 95628
+ Transfer rate: 74 KB/sec, 3825 bytes/write.
+ (gdb) c
+ Continuing.
```
* VoilĂ ! The board's LED should be blinking at 1 Hz. Success!
@@ -203,30 +199,25 @@ If you wish to build the image to run from the onboard flash memory on Olimex bo
By default, the linker script (`olimex_stm32-e407_devboard.ld`) is configured to run from bootloader and flash. However, if you first ran the image from SRAM you had changed `olimex_stm32-e407_devboard.ld` to match `run_from_sram.ld`. You will, therefore, return to defaults with `olimex_stm32-e407_devboard.ld` linker script matching the contents of 'run_from_loader.ld'. Return to the project directory.
```no-highlight
- $ cd ~/dev/core/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
- (some diff will be displayed)
- $ cp run_from_loader.ld olimex_stm32-e407_devboard.ld
- $ cd ~/dev/core
+$ cd ~/dev/myproj/repos/apache-mynewt-core/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
+(some diff will be displayed)
+$ cp run_from_loader.ld olimex_stm32-e407_devboard.ld
+$ cd ~/dev/myproj
```
<br>
* In order to run the image from flash, you need to build the bootloader as well. The bootloader does the initial set up of the Olimex board and then transfers control to the image stored at a location in flash known to it.
-```
+
Let's create boot_olimex:
```no-highlight
$ newt target create boot_olimex
- Creating target boot_olimex
- Target boot_olimex successfully created!
$ newt target set boot_olimex build_profile=optimized
- Target boot_olimex successfully set compiler_def to optimized
- $ newt target set boot_olimex @apache-mynewt-core/hw/bsp/olimex_stm32-e407_devboard
- Target boot_olimex successfully set bsp to ...
+ $ newt target set boot_olimex bsp=@apache-mynewt-core/hw/bsp/olimex_stm32-e407_devboard
$ newt target set boot_olimex app=@apache-mynewt-core/apps/boot
- Target targets/boot_olimex successfully set target.app to apps/boot
$ newt target show boot_olimex
targets/boot_olimex
app=app=@apache-mynewt-core/apps/boot
@@ -241,11 +232,11 @@ Let's create boot_olimex:
```no-highlight
$ newt build boot_olimex
...
- App successfully built: ~/dev/core/bin/boot_olimex/apps/boot/boot_olimex.elf
+ App successfully built: ~/dev/myproj/bin/boot_olimex/apps/boot/boot.elf
$ newt build blinky
...
Linking blinky.elf
- App successfully built: ~/dev/core/bin/blinky/apps/blinky/blinky.elf
+ App successfully built: ~/dev/myproj/bin/blinky/apps/blinky/blinky.elf
```
<br>
@@ -255,15 +246,15 @@ When creating an image, you can assign a version number to your image; here we u
```no-highlight
$ newt create-image blinky 1.2.3
- App image successfully generated: ~/dev/core/bin/blinky/apps/blinky/blinky.img
- Build manifest: ~/dev/core/bin/blinky/apps/blinky/manifest.json
+ App image succesfully generated: ~/dev/myproj/bin/blinky/apps/blinky/blinky.img
+ Build manifest: ~/dev/myproj/bin/blinky/apps/blinky/manifest.json
$ newt load boot_olimex
- Downloading ~/dev/core/bin/boot_olimex/apps/boot/boot.elf.bin to 0x08000000
+ Downloading~/dev/myproj/bin/boot_olimex/apps/boot/boot.elf.bin to 0x08000000
Open On-Chip Debugger 0.9.0 (2015-11-15-13:10)
...
shutdown command invoked
$ newt load blinky
- Downloading ~/dev/core/bin/blinky/apps/blinky/blinky.img to 0x08020000
+ Downloading ~/dev/myproj/bin/blinky/apps/blinky/blinky.img to 0x08020000
Open On-Chip Debugger 0.9.0 (2015-11-15-13:10)
...
shutdown command invoked
@@ -283,8 +274,8 @@ When creating an image, you can assign a version number to your image; here we u
```no-highlight
$ newt debug blinky
- Debugging with ~/dev/core/hw/bsp/olimex_stm32-e407_...
- Debugging ~/dev/core/project/blinky/bin/blinky/blinky.elf
+ Debugging with ~/dev/myproj/hw/bsp/olimex_stm32-e407_...
+ Debugging ~/dev/myproj/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 <http://gnu.org/licenses/gpl.html>
[4/6] incubator-mynewt-site git commit: Merge branch 'MYNEWT-250-a'
of https://github.com/paulfdietrich/incubator-mynewt-site
Posted by ad...@apache.org.
Merge branch 'MYNEWT-250-a' of https://github.com/paulfdietrich/incubator-mynewt-site
This closes #57
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/4f64fe74
Tree: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/tree/4f64fe74
Diff: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/diff/4f64fe74
Branch: refs/heads/master
Commit: 4f64fe7457ca2bbbe8a4b42f2a66995ee0107223
Parents: b02507e 2ca1ecd
Author: aditihilbert <ad...@runtime.io>
Authored: Thu Mar 17 16:35:57 2016 -0700
Committer: aditihilbert <ad...@runtime.io>
Committed: Thu Mar 17 16:39:49 2016 -0700
----------------------------------------------------------------------
docs/os/tutorials/Olimex.md | 73 ++++++++++++++++++----------------------
1 file changed, 32 insertions(+), 41 deletions(-)
----------------------------------------------------------------------