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/17 21:55:43 UTC
[1/2] incubator-mynewt-site git commit: MYNEWT-252
Repository: incubator-mynewt-site
Updated Branches:
refs/heads/master e753d0263 -> 46aa2856b
MYNEWT-252
documentation for nrf52 with new newt commands
This closes #58
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/11afe775
Tree: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/tree/11afe775
Diff: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/diff/11afe775
Branch: refs/heads/master
Commit: 11afe7753d82571d5ca52dd6b06bd7f4b3a91276
Parents: e753d02
Author: Paul Dietrich <pa...@yahoo.com>
Authored: Thu Mar 17 13:05:06 2016 -0700
Committer: aditihilbert <ad...@runtime.io>
Committed: Thu Mar 17 13:34:00 2016 -0700
----------------------------------------------------------------------
docs/os/tutorials/nRF52.md | 284 ++++++++++------------------------------
1 file changed, 68 insertions(+), 216 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/11afe775/docs/os/tutorials/nRF52.md
----------------------------------------------------------------------
diff --git a/docs/os/tutorials/nRF52.md b/docs/os/tutorials/nRF52.md
index d908365..69518d0 100644
--- a/docs/os/tutorials/nRF52.md
+++ b/docs/os/tutorials/nRF52.md
@@ -9,231 +9,83 @@ nRF52 Series chip from Nordic Semiconductors.
* nRF52 Development Kit
* Laptop running Mac OS
+* 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)
+
+#### install jlinkEXE
+
+In order to be able to communicate with the SEGGER J-Link debugger on the dev board, you have to download and install the J-Link GDB Server software on to your laptop. You may download the "Software and documentation pack for Mac OS X" from [https://www.segger.com/jlink-software.html](https://www.segger.com/jlink-software.html).
+
+#### Create a project.
+
+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.
+
+```no-highlight
+ $ mkdir ~/dev
+ $ cd ~/dev
+ $ newt new myproj
+ Downloading project skeleton from apache/incubator-mynewt-blinky...
+ Installing skeleton in myproj...
+ Project myproj successfully created.
+
+ $ cd myproj
+
+ $ newt install -v
+ apache-mynewt-core
+ Downloading repository description for apache-mynewt-core... success!
+ ...
+ apache-mynewt-core successfully installed version 0.7.9-none
+```
+
+#### Create the target
+
+Create a single target for the nrf52. NOTE: The nrf52 mynewt core does not
+yet have bootloader support, so we will create a single image to download
+to the device.
+
+```no-highlight
+$ newt target create blink_nordic
+$ newt target set blink_nordic app=apps/blinky
+$ newt target set blink_nordic bsp=@apache-mynewt-core/hw/bsp/nrf52pdk
+$ newt target set blink_nordic build_profile=debug
+$ newt target show
+targets/blink_nordic
+ app=apps/blinky
+ bsp=@apache-mynewt-core/hw/bsp/nrf52pdk
+ build_profile=debug
+```
+#### Build the image
-#### Step by Step Instructions to build image
-
-* The first step is to download the generic skeleton of the project. The eggs installed are not hardware architecture specific.
-```c
- []user@~/dev]$ newt nest create nordic_blinky
- Downloading nest skeleton from https://www.github.com/mynewt/tadpole... ok!
- Nest nordic_blinky successfully created in ~dev/nordic_blinky
-
- user@~/dev$ cd nordic_blinky/
+```no-highlight
+$ newt build blink_nordic
+...
+Compiling main.c
+Archiving blinky.a
+Linking blinky.elf
+App successfully built: ~/dev/myproj/bin/blink_nordic/apps/blinky/blinky.elf
```
-* Then, the clutch of eggs named larva is added from the nest (also named larva) on the github. This step simply downloads the clutch description file and does not actually install the eggs that constitute the clutch. The clutch description file (`clutch.yml`) will be used to check dependencies during the egg install to ensure completeness. It serves as a reference for all the eggs in the clutch that one can choose from and install.
-```c
- []user@~/dev/nordic_blinky]$ newt nest add-clutch larva https://github.com/mynewt/larva
- Downloading clutch.yml from https://github.com/mynewt/larva/master... ok!
- Verifying clutch.yml format...ok!
- Clutch larva successfully installed to Nest.
-```
-* The next step is to install relevant eggs from the larva nest on github. 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/nordic_blinky]$ newt egg install project/blinky
- Downloading larva from https://github.com/mynewt/larva//master... ok!
- Installing project/blinky
- Installation was a success!
-
-
- [user@~/dev/nordic_blinky]$ newt egg install hw/bsp/nrf52pdk
- Downloading larva from https://github.com/mynewt/larva//master... ok!
- Installing hw/bsp/nrf52pdk
- Installing hw/mcu/nordic/nrf52xxx
- Installing libs/cmsis-core
- Installing compiler/arm-none-eabi-m4
- Installation was a success!
-```
+#### Connect the board
-* It's time to create a target for the project and define the target attributes.
-```c
- [user@~/dev/nordic_blinky]$ newt target create blink_nordic
- Creating target blink_nordic
- Target blink_nordic successfully created!
- [user@~/dev/nordic_blinky]$ newt target set blink_nordic project=blinky
- Target blink_nordic successfully set project to blinky
- [user@~/dev/nordic_blinky]$ newt target set blink_nordic bsp=hw/bsp/nrf52pdk
- Target blink_nordic successfully set bsp to hw/bsp/nrf52pdk
- [user@~/dev/nordic_blinky]$ newt target set blink_nordic compiler_def=debug
- Target blink_nordic successfully set compiler_def to debug
- [user@~/dev/nordic_blinky]$ newt target set blink_nordic compiler=arm-none-eabi-m4
- Target blink_nordic successfully set compiler to arm-none-eabi-m4
- [user@~/dev/nordic_blinky]$ newt target set blink_nordic arch=cortex_m4
- Target blink_nordic successfully set arch to cortex_m4
- [user@~/dev/nordic_blinky]$ newt target show
- blink_nordic
- compiler: arm-none-eabi-m4
- name: blink_nordic
- arch: cortex_m4
- project: blinky
- bsp: hw/bsp/nrf52pdk
- compiler_def: debug
-```
+Connect the evaluation board via micro-USB to your PC via USB cable.
-* Finally, you get to build the target and generate an executable that can now be uploaded to the board via the on-board SEGGER J-Link debugger.
-```c
- [user@~/dev/nordic_blinky]$ newt target build blink_nordic
- Building target blink_nordic (project = blinky)
- Compiling case.c
- Compiling suite.c
- Compiling testutil.c
- Compiling testutil_arch_arm.c
- Archiving libtestutil.a
- Compiling os.c
- Compiling os_callout.c
- Compiling os_eventq.c
- Compiling os_heap.c
- Compiling os_mbuf.c
- Compiling os_mempool.c
- Compiling os_mutex.c
- Compiling os_sanity.c
- Compiling os_sched.c
- Compiling os_sem.c
- Compiling os_task.c
- Compiling os_time.c
- Compiling os_arch_arm.c
- Assembling HAL_CM4.s
- Assembling SVC_Table.s
- Archiving libos.a
- Compiling hal_cputime.c
- Compiling hal_gpio.c
- Compiling hal_uart.c
- Archiving libnrf52xxx.a
- Compiling cmsis_nvic.c
- Compiling hal_bsp.c
- Compiling libc_stubs.c
- Compiling os_bsp.c
- Compiling sbrk.c
- Compiling system_nrf52.c
- Assembling gcc_startup_nrf52.s
- Archiving libnrf52pdk.a
- Compiling main.c
- Building project blinky
- Linking blinky.elf
- Successfully run!
-```
-* In order to be able to communicate with the SEGGER J-Link debugger on the dev board, you have to download and install the J-Link GDB Server software on to your laptop. You may download the "Software and documentation pack for Mac OS X" from [https://www.segger.com/jlink-software.html](https://www.segger.com/jlink-software.html). The command line version of the server is used in the steps below.
-
-* Open a new terminal and start a J-Link session.
-```c
- [user@~/dev/nordic_blinky/project/blinky/bin]$ which JLinkGDBServer
- /usr/local/bin/JLinkGDBServer
- [user@~/dev/nordic_blinky/project/blinky/bin]$ JLinkGDBServer -if SWD
- SEGGER J-Link GDB Server V5.02f Command Line Version
-
- JLinkARM.dll V5.02f (DLL compiled Oct 2 2015 20:55:03)
-
- -----GDB Server start settings-----
- GDBInit file: none
- GDB Server Listening port: 2331
- SWO raw output listening port: 2332
- Terminal I/O port: 2333
- Accept remote connection: yes
- Generate logfile: off
- Verify download: off
- Init regs on start: off
- Silent mode: off
- Single run mode: off
- Target connection timeout: 0 ms
- ------J-Link related settings------
- J-Link Host interface: USB
- J-Link script: none
- J-Link settings file: none
- ------Target related settings------
- Target device: unspecified
- Target interface: SWD
- Target interface speed: 1000kHz
- Target endian: little
-
- Connecting to J-Link...
- J-Link is connected.
- Firmware: J-Link OB-SAM3U128-V2-NordicSemi compiled Aug 28 2015 19:26:24
- Hardware: V1.00
- S/N: 682371959
- Checking target voltage...
- Target voltage: 3.30 V
- Listening on TCP/IP port 2331
- Connecting to target...Connected to target
- Waiting for GDB connection...Connected to 127.0.0.1
-```
+#### Download to the target
-* You need a configuration file for the GDB session to be opened correctly and the image ("blinky.elf") you built for this target downloaded to flash. A sample config script is given below. Alternatively, you could choose to type each command at the gdb prompt.
-```c
- [user@~/dev/nordic_blinky/project/blinky/bin/blink_nordic]$ cat jlink-gdb.cfg
- echo ***Setting up the environment for debugging gdb.***\n
- set complaints 1
- set prompt (gdb)
- set endian little
- echo \n*** Set target charset ASCII\n
- set target-charset ASCII
- echo \n*** Connecting over port #2331 ***\n
- target remote localhost:2331
- echo \n*** Enable flash write and set device to nrf52 ***\n
- monitor flash download=1
- monitor flash device=nRF52
- echo \n*** loading blinky.elf ***\n
- load ~/dev/nordic_blinky/project/blinky/bin/blink_nordic/blinky.elf
- symbol-file ~/dev/nordic_blinky/project/blinky/bin/blink_nordic/blinky.elf
- echo \n*** Resetting target ***\n
- monitor reset
- echo \n*** Halting target ***\n
- monitor halt
-```
-* Start the gdb session and monitor that it loads the image, resets the target, and halts for a command to continue.
-```c
- [user@~/dev/nordic_blinky/project/blinky/bin/blink_nordic]$ arm-none-eabi-gdb -x ~/dev/nordic_blinky/project/blinky/bin/blink_nordic/jlink-gdb.cfg
-
- 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".
-
- ***Setting up the environment for debugging gdb.***
- The target is assumed to be little endian
-
- *** Set target charset ASCII
-
- *** Connecting over port #2331 ***
- 0x00003c34 in ?? ()
-
- *** Enable flash write and set device to nrf52 ***
- Flash download enabled
- Selecting device: nRF52
-
- *** loading blinky.elf ***
- Loading section .text, size 0x5c84 lma 0x0
- Loading section .ARM.extab, size 0x24 lma 0x5c84
- Loading section .ARM.exidx, size 0xd8 lma 0x5ca8
- Loading section .data, size 0x8f8 lma 0x5d80
- Start address 0x48c, load size 26232
- Transfer rate: 12808 KB/sec, 2914 bytes/write.
- During symbol reading, unexpected overlap between:
- (A) section `.text' from `~/dev/nordic_blinky/project/blinky/bin/blink_nordic/blinky.elf' [0x0, 0x5c84)
- (B) section `*COM*' from `~/dev/nordic_blinky/project/blinky/bin/blink_nordic/blinky.elf' [0x0, 0x0).
- Will ignore section B.
-
- *** Resetting target ***
- Resetting target
-
- *** Halting target ***
-```
-* Type 'c' to continue. The LED on the board will start to blink. You will also see some activity in the terminal showing the open J-Link GDB server connection. The LED will continue to blink after you quit out of that connection.
-```c
- (gdb) c
- Continuing.
+Download the executable to the target platform.
+
+```no-highlight
+$ newt -v load blink_nordic
```
+#### Congratulations
+
+You have created, setup, compiled, loaded, and ran your first mynewt application
+for the nrf52 evaluation board.
+
+
[2/2] incubator-mynewt-site git commit: This closes #58. nRF52
tutorial updated with new newt commands. Link in Arduino Zero to first
project fixed. Link to Sim blinky fixed
Posted by ad...@apache.org.
This closes #58. nRF52 tutorial updated with new newt commands. Link in Arduino Zero to first project fixed. Link to Sim blinky fixed
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/46aa2856
Tree: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/tree/46aa2856
Diff: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/diff/46aa2856
Branch: refs/heads/master
Commit: 46aa2856b41c28e5ccec2b55e917ef717fcded59
Parents: 11afe77
Author: aditihilbert <ad...@runtime.io>
Authored: Thu Mar 17 13:55:38 2016 -0700
Committer: aditihilbert <ad...@runtime.io>
Committed: Thu Mar 17 13:55:38 2016 -0700
----------------------------------------------------------------------
docs/os/get_started/project1.md | 172 -----------------------------
docs/os/get_started/project_create.md | 53 ++++++---
docs/os/tutorials/arduino_zero.md | 14 +--
docs/os/tutorials/nRF52.md | 14 +--
4 files changed, 49 insertions(+), 204 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/46aa2856/docs/os/get_started/project1.md
----------------------------------------------------------------------
diff --git a/docs/os/get_started/project1.md b/docs/os/get_started/project1.md
deleted file mode 100644
index ee77f81..0000000
--- a/docs/os/get_started/project1.md
+++ /dev/null
@@ -1,172 +0,0 @@
-## Blinky, Your Hello World!
-
-### Objective
-
-Learn how to use packages from a default application repository of Mynewt to build your first *Hello World* application (Blinky) in the safe haven of a simulation.
-
-This tutorial will guide to achieve the following:
-
-1. Set up the environment on your computer to use Mynewt OS and newt tool.
-2. Download packages for building and testing the project [on a simulated target](#build-test-code-on-simulator).
-
-** Time Requirement**: Allow yourself an hour for this project if you are relatively new to embedded systems and want to understand each step.
-
-
-### What you need
-
-1. Personal Computer with Mac OS (Mac: OS X Yosemite Version 10.10.5) or Linux box (Ubuntu 14.10: Utopic Unicorn)
-2. An account on Github repository and *git* installed on your computer.
-3. It assumed you already installed native tools described [here](native_tools.md)
-
-Also, we assume that you're familiar with UNIX shells.
-
-Let's gets started!
-
-### Install Native and Cross Tools
-
-
-See [Installing Native Tools](../get_started/native_tools.md)
- and [Installing Cross Tools](../get_started/cross_tools.md) for ARM to install
-the tools needed by newt.
-
-
-### Install newt tool
-
-There are two ways to install the *newt* tool on your computer. The easy way (and the recommeded way for this project) is to download the respective *newt* binaries from the links below:
-* Mac OS
-* Linux
-
-Include the *newt* in your $PATH.
-
-Or if you're an adventurer then you can set up the environment on your computer, install the Go language, and build the *newt* tool from source as explained in the tutorials in the Newt Tool Manual. See [Install newt from source on Mac](../../newt/newt_mac.md) and [Install newt from source on Linux](../../newt/newt_linux.md).
-
-### Build test code on simulator
-
-
-1\. Create a new project with newt
-
-```no-highlight
-$ newt new my_project
-Downloading project skeleton from apache/incubator-mynewt-blinky...
-Installing skeleton in my_project...
-Project my_project successfully created.
-$ tree -L 3
-.
-├── DISCLAIMER
-├── LICENSE
-├── NOTICE
-├── README.md
-├── apps
-│ └── blinky
-│ ├── pkg.yml
-│ └── src
-├── project.yml
-└── targets
- ├── my_blinky_sim
- │ ├── pkg.yml
- │ └── target.yml
- └── unittest
- ├── pkg.yml
- └── target.yml
-
-6 directories, 10 files
-$
-```
-
-2\. Install remote dependencies for the new project
-
-```no-highlight
-$ newt install -v
-apache-mynewt-core
-Downloading repository description for apache-mynewt-core... success!
-Downloading repository incubator-mynewt-core (branch: master; commit: mynewt_0_8_0_b2_tag) at https://github.com/apache/incubator-mynewt-core.git
-Cloning into '/var/folders/7l/7b3w9m4n2mg3sqmgw2q1b9p80000gn/T/newt-repo969988348'...
-remote: Counting objects: 17935, done.
-remote: Compressing objects: 100% (234/234), done.
-remote: Total 17935 (delta 101), reused 0 (delta 0), pack-reused 17686
-Receiving objects: 100% (17935/17935), 6.18 MiB | 315.00 KiB/s, done.
-Resolving deltas: 100% (10541/10541), done.
-Checking connectivity... done.
-apache-mynewt-core successfully installed version 0.7.9-none
-```
-
-3\. Next, build the packages for the sim project using the *newt* tool. You should see lots of console output while *newt* is resolving dependencies and compiling the source code. After a minute, it should complete with
-the `Successfully run!` text.
-
-```no-highlight
-$ newt build my_blinky_sim
-Compiling main.c
-Archiving blinky.a
-Compiling flash_map.c
-Compiling hal_flash.c
-Archiving hal.a
-Compiling hal_cputime.c
-Compiling hal_flash.c
-Compiling hal_gpio.c
-Compiling hal_system.c
-Compiling hal_uart.c
-Archiving native.a
-Compiling base64.c
-<snip>
-```
-For extra details, specify the ```-v``` (verbose) option.
-
-4\. Run the blinky target, and enjoy your first successful Apache Mynewt project:
-
-```no-highlight
-$ newt run my_blinky_sim
-<snip>
-Compiling cons_fmt.c
-Compiling cons_tty.c
-Archiving full.a
-Compiling hal_bsp.c
-Compiling os_bsp.c
-Compiling sbrk.c
-Archiving native.a
-Compiling os.c
-Compiling os_callout.c
-Compiling os_eventq.c
-Compiling os_heap.c
-Compiling os_mbuf.c
-Compiling os_mempool.c
-Compiling os_mutex.c
-Compiling os_sanity.c
-Compiling os_sched.c
-Compiling os_sem.c
-Compiling os_task.c
-Compiling os_time.c
-Compiling os_arch_sim.c
-Compiling os_fault.c
-Assembling os_arch_stack_frame.s
-Archiving os.a
-Linking blinky.elf
-No download script for BSP hw/bsp/native
-Debugging /Users/sterling/dev/site/my_project/bin/my_blinky_sim/apps/blinky/blinky.elf
-GNU gdb (GDB) 7.10.1
-Copyright (C) 2015 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 "x86_64-apple-darwin15.2.0".
-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/sterling/dev/site/my_project/bin/my_blinky_sim/apps/blinky/blinky.elf...Reading symbols from /Users/sterling/dev/site/my_project/bin/my_blinky_sim/apps/blinky/blinky.elf.dSYM/Contents/Resources/DWARF/blinky.elf...done.
-done.
-(gdb) r
-```
-
-### Conclusion
-
-In summation, you achieved and learned a fair amount in this hands-on tutorial, all in the simulation environment.
-
-Now you can turn to more fun tutorials where you can get your hands dirty with actual hardware. Be bold and try the Blinky [tutorials on Olimex board](../tutorials/olimex.md).
-
-If you see anything missing or want to send us feeback, please do so by signing up for appropriate mailing lists on our [Community Page](../../community.md)
-
-Keep on hacking and blinking!
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/46aa2856/docs/os/get_started/project_create.md
----------------------------------------------------------------------
diff --git a/docs/os/get_started/project_create.md b/docs/os/get_started/project_create.md
index 26ef364..510dcb6 100644
--- a/docs/os/get_started/project_create.md
+++ b/docs/os/get_started/project_create.md
@@ -1,29 +1,34 @@
-# Creating a Mynewt Project
+## Create Your First Mynewt Project
-This page shows how to create a Mynewt Project using `newt`
+This page shows how to create a Mynewt Project using the `newt` command-line tool.
-# Pre-Requisites
+### Pre-Requisites
-* Ensure you have installed [newt](../../newt/newt_intro) and that the
-newt command is in your system path.
+* Ensure you have installed [newt](../../newt/tutorials/newt_mac.md) and that the
+newt command is in your system path.
* You must have Internet connectivity to fetch remote Mynewt components
* You must [install the compiler tools](project1.md) to
support native compiling to build the project this tutorial creates.
-## Newt New
+<br>
-Chose a project name. For this tutorial we will call this project `myproj`.
-Enter the `newt new myproj` command. Your put
-```no-highlight
+### Newt New
+
+Choose a project name. For this tutorial we will call this project `myproj`.
+Enter the `newt new myproj` command.
+
+```
$ newt new myproj
Downloading project skeleton from apache/incubator-mynewt-blinky...
Installing skeleton in myproj...
Project myproj successfully created.
```
+<br>
+
The `newt` tool has created a project directory structure like the one below:
-```no-highlight
+```
─── myproj
├── DISCLAIMER
├── LICENSE
@@ -44,6 +49,9 @@ The `newt` tool has created a project directory structure like the one below:
└── target.yml
```
+<br>
+
+
`newt` has installed the base files for a project comprising the following.
1. file `project.yml` contains the repository list that the project uses to fetch
@@ -58,16 +66,17 @@ targets.
4. A non-build-able target called `unittest`. This is used
internally by `newt` and is not a formal build target.
- NOTE: the actual code and package files are not installed
-(except the template for `main.c`. See the next step for installing
-the packages.
+**NOTE:** the actual code and package files are not installed
+(except the template for `main.c`). See the next step for installing the packages.
-## Newt Install
+<br>
-change into the `myproj` directory. Then ask newt to install all the
-project package dependencies using `newt install`
+### Newt Install
-```no-highlight
+Change into the `myproj` directory. Then ask newt to install all the
+project package dependencies using `newt install`.
+
+```
$ newt install -v
apache-mynewt-core
Downloading repository description for apache-mynewt-core... success!
@@ -111,6 +120,8 @@ under the specific repository you have included in the base project.
Within each of these directories are the packages required to build your
project for the various targets.
+<br>
+
## Testing the Project
To validate, you can also run all the units test through simulation.
@@ -126,6 +137,8 @@ To validate, you can also run all the units test through simulation.
All tests passed
```
+<br>
+
## Building the Project
To build the project you can use `newt build` using the target
@@ -135,6 +148,8 @@ To build the project you can use `newt build` using the target
App successfully built: /bin/my_blinky_sim/apps/blinky/blinky.elf
```
+<br>
+
You can run the simulated version of your project and see the simulated LED
blink
```no-highlight
@@ -144,8 +159,10 @@ blink
Just do `ctrl-c` to exit.
+<br>
+
## Complete
-Congratulations, you have created your first project. This project contains
+Congratulations, you have created your first project! This project contains
the core OS, a simple application to blink an LED and all of the dependencies
required.
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/46aa2856/docs/os/tutorials/arduino_zero.md
----------------------------------------------------------------------
diff --git a/docs/os/tutorials/arduino_zero.md b/docs/os/tutorials/arduino_zero.md
index e13143c..7d4311b 100644
--- a/docs/os/tutorials/arduino_zero.md
+++ b/docs/os/tutorials/arduino_zero.md
@@ -1,12 +1,12 @@
-# Running Mynewt on Arduino Zero
+## Running Mynewt on Arduino Zero
This tutorial describes how to run Mynewt OS on Arduino Zero.
-## Prerequisites
+### Prerequisites
Before tackling this tutorial, it's best to read about Mynewt in the [Introduction](../get_started/introduction) section of this documentation.
-## Equipment
+### Equipment
You will need the following equipment
@@ -17,7 +17,7 @@ compatible with this tutorial
* A USB cable (Type A to micro B) that can connect the computer to the Arduino
* The Mynewt Release
-## Arduino Boards
+### Arduino Boards
This tutorial has been tested on the following two Arduino Zero boards.
@@ -25,13 +25,13 @@ This tutorial has been tested on the following two Arduino Zero boards.
<img src="http://www.arduino.org//images/products/ArduinoZeroPro-flat-org.jpg" alt="Drawing" style="width: 330px;"/>
-## Steps
+### Steps
Follow these simple steps and your board will be blinking in no time!
-### Install Mynewt and Newt
+#### Install Mynewt and Newt
-If you have not already done so, install Newt as shown in the [Newt install tutorial](../../newt/tutorials/newt_mac.md) and cloned the Mynewt OS repository as shown in the [Get Started tutorial for Blinky](../get_started/project1.md)
+If you have not already done so, install Newt as shown in the [Newt install tutorial](../../newt/tutorials/newt_mac.md) and cloned the Mynewt OS repository as shown in the [Get Started tutorial for Sim Blinky](../get_started/project_create.md)
### Fetch External Packages for Atmel SAMD21
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/46aa2856/docs/os/tutorials/nRF52.md
----------------------------------------------------------------------
diff --git a/docs/os/tutorials/nRF52.md b/docs/os/tutorials/nRF52.md
index 69518d0..1cafdd3 100644
--- a/docs/os/tutorials/nRF52.md
+++ b/docs/os/tutorials/nRF52.md
@@ -12,7 +12,7 @@ nRF52 Series chip from Nordic Semiconductors.
* 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)
-#### install jlinkEXE
+#### Install jlinkEXE
In order to be able to communicate with the SEGGER J-Link debugger on the dev board, you have to download and install the J-Link GDB Server software on to your laptop. You may download the "Software and documentation pack for Mac OS X" from [https://www.segger.com/jlink-software.html](https://www.segger.com/jlink-software.html).
@@ -22,16 +22,16 @@ Create a new project to hold your work. For a deeper understanding, you can rea
[Get Started -- Creating Your First Project](../get_started/project_create.md)
or just follow the commands below.
-```no-highlight
+```
$ mkdir ~/dev
$ cd ~/dev
$ newt new myproj
Downloading project skeleton from apache/incubator-mynewt-blinky...
Installing skeleton in myproj...
Project myproj successfully created.
-
+
$ cd myproj
-
+
$ newt install -v
apache-mynewt-core
Downloading repository description for apache-mynewt-core... success!
@@ -45,7 +45,7 @@ Create a single target for the nrf52. NOTE: The nrf52 mynewt core does not
yet have bootloader support, so we will create a single image to download
to the device.
-```no-highlight
+```
$ newt target create blink_nordic
$ newt target set blink_nordic app=apps/blinky
$ newt target set blink_nordic bsp=@apache-mynewt-core/hw/bsp/nrf52pdk
@@ -59,7 +59,7 @@ targets/blink_nordic
#### Build the image
-```no-highlight
+```
$ newt build blink_nordic
...
Compiling main.c
@@ -76,7 +76,7 @@ Connect the evaluation board via micro-USB to your PC via USB cable.
Download the executable to the target platform.
-```no-highlight
+```
$ newt -v load blink_nordic
```