You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mynewt.apache.org by GitBox <gi...@apache.org> on 2017/12/01 23:42:29 UTC
[GitHub] aditihilbert closed pull request #343: automated asf-site build
aditihilbert closed pull request #343: automated asf-site build
URL: https://github.com/apache/mynewt-site/pull/343
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git a/latest/mkdocs/search_index.json b/latest/mkdocs/search_index.json
index ab70dda7e..5a99794a7 100644
--- a/latest/mkdocs/search_index.json
+++ b/latest/mkdocs/search_index.json
@@ -162,12 +162,12 @@
},
{
"location": "/newt/install/newt_mac/",
- "text": "Installing Newt on Mac OS\n\n\nNewt is supported on Mac OS X 64 bit platforms and has been tested on Mac OS 10.11 and higher.\n\n\nThis page shows you how to install the following versions of newt:\n\n\n\n\nUpgrade to or install the latest release version (1.2.0).\n\n\nInstall the latest from the master branch (unstable).\n\n\n\n\nSee \nInstalling Previous Releases of Newt\n to install an earlier version of newt.\n\n\nNote:\n If you would like to contribute to the newt tool, see \nSetting Up Go Environment to Contribute to Newt and Newtmgr Tools\n.\n\n\nInstalling Homebrew\n\n\nIf you do not have Homebrew installed, run the following command. You will be prompted for your sudo password.\n\n\n$ ruby -e \n$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)\n\n\n\n\n\n\nYou can also extract (or \ngit clone\n) Homebrew and install it to /usr/local.\n\n\nAdding the Mynewt Homebrew Tap\n\n\nIf this is your first time installing newt, add the \nruntimeco/homebrew-mynewt\n tap:\n\n\n$ brew tap runtimeco/homebrew-mynewt\n$ brew update\n\n\n\n\n\nUpgrading to or Installing the Latest Release Version\n\n\nPerform the following to upgrade or install the latest release version of newt.\n\n\nUpgrading to the Latest Release Version of Newt\n\n\nIf you have installed an earlier version of newt using brew, run the following commands to upgrade to latest version of newt:\n\n\n$ brew update\n$ brew upgrade mynewt-newt\n\n\n\n\n\n\n\nInstalling the Latest Release Version of Newt\n\n\nRun the following command to install the latest release version of newt:\n\n\n$ brew update\n$ brew install mynewt-newt\n==\n Installing mynewt-newt from runtimeco/mynewt\n==\n Downloading https://github.com/runtimeco/binary-releases/raw/master/mynewt-newt-tools_1.2.0/mynewt-newt-1.2.0.sierra.bottle.tar.gz\n==\n Downloading from https://raw.githubusercontent.com/runtimeco/binary-releases/master/mynewt-newt-tools_1.2.0/mynewt-newt-1.2.0.sierra.bottle.tar.gz\n######################################################################## 100.0%\n==\n Pouring mynewt-newt-1.2.0.sierra.bottle.tar.gz\n\ud83c\udf7a /usr/local/Cellar/mynewt-newt/1.2.0: 3 files, 10.7MB\n\n\n\n\n\n\n\nNotes:\n Homebrew bottles for newt are available for Mac OS Sierra, and El Captian. If you are running an earlier version of Mac OS, the installation will install the latest version of Go and compile newt locally.\n\n\n\n\nChecking the Installed Version\n\n\nCheck that you are using the installed version of newt:\n\n\n$which newt\n/usr/local/bin/newt\n$ls -l /usr/local/bin/newt\nlrwxr-xr-x 1 user staff 36 Sep 11 19:04 /usr/local/bin/newt -\n ../Cellar/mynewt-newt/1.2.0/bin/newt\n$newt version\nApache Newt version: 1.2.0\n\n\n\n\n\nNote:\n If you previously built newt from source and the output of \nwhich newt\n shows \"$GOPATH/bin/newt\", you will need to move \"$GOPATH/bin\" after \"/usr/local/bin\" for your PATH in ~/.bash_profile, and source ~/.bash_profile. \n\n\n\nGet information about newt: \n\n\n$ newt help\nNewt allows you to create your own embedded application based on the Mynewt \noperating system. Newt provides both build and package management in a single \ntool, which allows you to compose an embedded application, and set of \nprojects, and then build the necessary artifacts from those projects. For more \ninformation on the Mynewt operating system, please visit \nhttps://mynewt.apache.org/. \n\nPlease use the newt help command, and specify the name of the command you want \nhelp for, for help on how to use a specific command\n\nUsage:\n newt [flags]\n newt [command]\n\nExamples:\n newt\n newt help [\ncommand-name\n]\n For help on \ncommand-name\n. If not specified, print this message.\n\nAvailable Commands:\n build Build one or more targets\n clean Delete build artifacts for one or more targets\n create-image Add image header to target binary\n debug Open debugger session to target\n info Show project info\n install Install project dependencies\n load Load built target to board\n mfg Manufacturing flash image commands\n new Create a new project\n pkg Create and manage packages in the current workspace\n resign-image Re-sign an image.\n run build/create-image/download/debug \ntarget\n\n size Size of target components\n sync Synchronize project dependencies\n target Commands to create, delete, configure, and query targets\n test Executes unit tests for one or more packages\n upgrade Upgrade project dependencies\n vals Display valid values for the specified element type(s)\n version Display the Newt version number\n\nFlags:\n -h, --help Help for newt commands\n -j, --jobs int Number of concurrent build jobs (default 8)\n -l, --loglevel string Log level (default \nWARN\n)\n -o, --outfile string Filename to tee output to\n -q, --quiet Be quiet; only display error output\n -s, --silent Be silent; don\nt output anything\n -v, --verbose Enable verbose output when executing commands\n\nUse \nnewt [command] --help\n for more information about a command.\n\n\n\n\n\n\n\nInstalling Newt from the Master Branch\n\n\nWe recommend that you use the latest release version of newt. If you would like to use the master branch with the latest updates, you can install newt from the HEAD of the master branch. \n\n\n Notes: \n\n\n\n\nThe master branch may be unstable.\n\n\nThis installation will install the latest version of Go on your computer, if it is not installed, and compile newt locally. \n\n\n\n\n\nIf you previously installed newt using brew, unlink the current version:\n\n\n$brew unlink mynewt-newt\n\n\n\n\n\n\nInstall the latest unstable version of newt from the master branch:\n\n\n$ brew install mynewt-newt --HEAD\n==\n Installing mynewt-newt from runtimeco/mynewt\n==\n Cloning https://github.com/apache/mynewt-newt.git\nCloning into \n/Users/wanda/Library/Caches/Homebrew/mynewt-newt--git\n...\nremote: Counting objects: 626, done.\nremote: Compressing objects: 100% (504/504), done.\nremote: Total 626 (delta 155), reused 323 (delta 85), pack-reused 0\nReceiving objects: 100% (626/626), 1.11 MiB | 0 bytes/s, done.\nResolving deltas: 100% (155/155), done.\n==\n Checking out branch master\n==\n go install\n\ud83c\udf7a /usr/local/Cellar/mynewt-newt/HEAD-59b3a5d: 3 files, 10.7MB, built in 7 seconds\n$newt version\nApache Newt version 1.1.0-dev\n\n\n\n\n\n\nTo switch back to the latest stable release version of newt, you can run:\n\n\n$brew switch mynewt-newt 1.2.0\nCleaning /usr/local/Cellar/mynewt-newt/1.2.0\nCleaning /usr/local/Cellar/mynewt-newt/HEAD-59b3a5d\n1 links created for /usr/local/Cellar/mynewt-newt/1.2.0\n$newt version\nApache Newt version: 1.2.0",
+ "text": "Installing Newt on Mac OS\n\n\nNewt is supported on Mac OS X 64 bit platforms and has been tested on Mac OS Sierra.\n\n\nThis page shows you how to install the following versions of newt:\n\n\n\n\nUpgrade to or install the latest release version (1.2.0).\n\n\nInstall the latest from the master branch (unstable).\n\n\n\n\nSee \nInstalling Previous Releases of Newt\n to install an earlier version of newt.\n\n\nNote:\n If you would like to contribute to the newt tool, see \nSetting Up Go Environment to Contribute to Newt and Newtmgr Tools\n.\n\n\nInstalling Homebrew\n\n\nIf you do not have Homebrew installed, run the following command. You will be prompted for your sudo password.\n\n\n$ ruby -e \n$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)\n\n\n\n\n\n\nYou can also extract (or \ngit clone\n) Homebrew and install it to /usr/local.\n\n\nAdding the Mynewt Homebrew Tap\n\n\nIf this is your first time installing newt, add the \nruntimeco/homebrew-mynewt\n tap:\n\n\n$ brew tap runtimeco/homebrew-mynewt\n$ brew update\n\n\n\n\n\nUpgrading to or Installing the Latest Release Version\n\n\nPerform the following to upgrade or install the latest release version of newt.\n\n\nUpgrading to the Latest Release Version of Newt\n\n\nIf you have installed an earlier version of newt using brew, run the following commands to upgrade to latest version of newt:\n\n\n$ brew update\n$ brew upgrade mynewt-newt\n\n\n\n\n\n\n\nInstalling the Latest Release Version of Newt\n\n\nRun the following command to install the latest release version of newt:\n\n\n$ brew update\n$ brew install mynewt-newt\n\n\n\n\n\n\n\nNotes:\n Homebrew bottles for newt are available for Mac OS Sierra. If you are running an earlier version of Mac OS, the installation will install the latest version of Go and compile newt locally.\n\n\n\n\nChecking the Installed Version\n\n\nCheck that you are using the installed version of newt:\n\n\n$which newt\n/usr/local/bin/newt\n$newt version\nApache Newt version: 1.2.0\n\n\n\n\n\nNote:\n If you previously built newt from source and the output of \nwhich newt\n shows \"$GOPATH/bin/newt\", you will need to move \"$GOPATH/bin\" after \"/usr/local/bin\" for your PATH in ~/.bash_profile, and source ~/.bash_profile. \n\n\n\nGet information about newt: \n\n\n$ newt help\nNewt allows you to create your own embedded application based on the Mynewt \noperating system. Newt provides both build and package management in a single \ntool, which allows you to compose an embedded application, and set of \nprojects, and then build the necessary artifacts from those projects. For more \ninformation on the Mynewt operating system, please visit \nhttps://mynewt.apache.org/. \n\nPlease use the newt help command, and specify the name of the command you want \nhelp for, for help on how to use a specific command\n\nUsage:\n newt [flags]\n newt [command]\n\nExamples:\n newt\n newt help [\ncommand-name\n]\n For help on \ncommand-name\n. If not specified, print this message.\n\nAvailable Commands:\n build Build one or more targets\n clean Delete build artifacts for one or more targets\n create-image Add image header to target binary\n debug Open debugger session to target\n info Show project info\n install Install project dependencies\n load Load built target to board\n mfg Manufacturing flash image commands\n new Create a new project\n pkg Create and manage packages in the current workspace\n resign-image Re-sign an image.\n run build/create-image/download/debug \ntarget\n\n size Size of target components\n sync Synchronize project dependencies\n target Commands to create, delete, configure, and query targets\n test Executes unit tests for one or more packages\n upgrade Upgrade project dependencies\n vals Display valid values for the specified element type(s)\n version Display the Newt version number\n\nFlags:\n -h, --help Help for newt commands\n -j, --jobs int Number of concurrent build jobs (default 8)\n -l, --loglevel string Log level (default \nWARN\n)\n -o, --outfile string Filename to tee output to\n -q, --quiet Be quiet; only display error output\n -s, --silent Be silent; don\nt output anything\n -v, --verbose Enable verbose output when executing commands\n\nUse \nnewt [command] --help\n for more information about a command.\n\n\n\n\n\n\n\nInstalling Newt from the Master Branch\n\n\nWe recommend that you use the latest release version of newt. If you would like to use the master branch with the latest updates, you can install newt from the HEAD of the master branch. \n\n\n Notes: \n\n\n\n\nThe master branch may be unstable.\n\n\nThis installation will install the latest version of Go on your computer, if it is not installed, and compile newt locally. \n\n\n\n\n\nIf you previously installed newt using brew, unlink the current version:\n\n\n$brew unlink mynewt-newt\n\n\n\n\n\n\nInstall the latest unstable version of newt from the master branch:\n\n\n$ brew install mynewt-newt --HEAD\n\n\n\n\n\n\nTo switch back to the latest stable release version of newt, you can run:\n\n\n$brew switch mynewt-newt 1.2.0",
"title": "Install Newt on Mac"
},
{
"location": "/newt/install/newt_mac/#installing-newt-on-mac-os",
- "text": "Newt is supported on Mac OS X 64 bit platforms and has been tested on Mac OS 10.11 and higher. This page shows you how to install the following versions of newt: Upgrade to or install the latest release version (1.2.0). Install the latest from the master branch (unstable). See Installing Previous Releases of Newt to install an earlier version of newt. Note: If you would like to contribute to the newt tool, see Setting Up Go Environment to Contribute to Newt and Newtmgr Tools .",
+ "text": "Newt is supported on Mac OS X 64 bit platforms and has been tested on Mac OS Sierra. This page shows you how to install the following versions of newt: Upgrade to or install the latest release version (1.2.0). Install the latest from the master branch (unstable). See Installing Previous Releases of Newt to install an earlier version of newt. Note: If you would like to contribute to the newt tool, see Setting Up Go Environment to Contribute to Newt and Newtmgr Tools .",
"title": "Installing Newt on Mac OS"
},
{
@@ -192,22 +192,22 @@
},
{
"location": "/newt/install/newt_mac/#installing-the-latest-release-version-of-newt",
- "text": "Run the following command to install the latest release version of newt: $ brew update\n$ brew install mynewt-newt\n== Installing mynewt-newt from runtimeco/mynewt\n== Downloading https://github.com/runtimeco/binary-releases/raw/master/mynewt-newt-tools_1.2.0/mynewt-newt-1.2.0.sierra.bottle.tar.gz\n== Downloading from https://raw.githubusercontent.com/runtimeco/binary-releases/master/mynewt-newt-tools_1.2.0/mynewt-newt-1.2.0.sierra.bottle.tar.gz\n######################################################################## 100.0%\n== Pouring mynewt-newt-1.2.0.sierra.bottle.tar.gz\n\ud83c\udf7a /usr/local/Cellar/mynewt-newt/1.2.0: 3 files, 10.7MB Notes: Homebrew bottles for newt are available for Mac OS Sierra, and El Captian. If you are running an earlier version of Mac OS, the installation will install the latest version of Go and compile newt locally.",
+ "text": "Run the following command to install the latest release version of newt: $ brew update\n$ brew install mynewt-newt Notes: Homebrew bottles for newt are available for Mac OS Sierra. If you are running an earlier version of Mac OS, the installation will install the latest version of Go and compile newt locally.",
"title": "Installing the Latest Release Version of Newt"
},
{
"location": "/newt/install/newt_mac/#checking-the-installed-version",
- "text": "Check that you are using the installed version of newt: $which newt\n/usr/local/bin/newt\n$ls -l /usr/local/bin/newt\nlrwxr-xr-x 1 user staff 36 Sep 11 19:04 /usr/local/bin/newt - ../Cellar/mynewt-newt/1.2.0/bin/newt\n$newt version\nApache Newt version: 1.2.0 Note: If you previously built newt from source and the output of which newt shows \"$GOPATH/bin/newt\", you will need to move \"$GOPATH/bin\" after \"/usr/local/bin\" for your PATH in ~/.bash_profile, and source ~/.bash_profile. \nGet information about newt: $ newt help\nNewt allows you to create your own embedded application based on the Mynewt \noperating system. Newt provides both build and package management in a single \ntool, which allows you to compose an embedded application, and set of \nprojects, and then build the necessary artifacts from those projects. For more \ninformation on the Mynewt operating system, please visit \nhttps://mynewt.apache.org/. \n\nPlease use the newt help command, and specify the name of the command you want \nhelp for, for help on how to use a specific command\n\nUsage:\n newt [flags]\n newt [command]\n\nExamples:\n newt\n newt help [ command-name ]\n For help on command-name . If not specified, print this message.\n\nAvailable Commands:\n build Build one or more targets\n clean Delete build artifacts for one or more targets\n create-image Add image header to target binary\n debug Open debugger session to target\n info Show project info\n install Install project dependencies\n load Load built target to board\n mfg Manufacturing flash image commands\n new Create a new project\n pkg Create and manage packages in the current workspace\n resign-image Re-sign an image.\n run build/create-image/download/debug target \n size Size of target components\n sync Synchronize project dependencies\n target Commands to create, delete, configure, and query targets\n test Executes unit tests for one or more packages\n upgrade Upgrade project dependencies\n vals Display valid values for the specified element type(s)\n version Display the Newt version number\n\nFlags:\n -h, --help Help for newt commands\n -j, --jobs int Number of concurrent build jobs (default 8)\n -l, --loglevel string Log level (default WARN )\n -o, --outfile string Filename to tee output to\n -q, --quiet Be quiet; only display error output\n -s, --silent Be silent; don t output anything\n -v, --verbose Enable verbose output when executing commands\n\nUse newt [command] --help for more information about a command.",
+ "text": "Check that you are using the installed version of newt: $which newt\n/usr/local/bin/newt\n$newt version\nApache Newt version: 1.2.0 Note: If you previously built newt from source and the output of which newt shows \"$GOPATH/bin/newt\", you will need to move \"$GOPATH/bin\" after \"/usr/local/bin\" for your PATH in ~/.bash_profile, and source ~/.bash_profile. \nGet information about newt: $ newt help\nNewt allows you to create your own embedded application based on the Mynewt \noperating system. Newt provides both build and package management in a single \ntool, which allows you to compose an embedded application, and set of \nprojects, and then build the necessary artifacts from those projects. For more \ninformation on the Mynewt operating system, please visit \nhttps://mynewt.apache.org/. \n\nPlease use the newt help command, and specify the name of the command you want \nhelp for, for help on how to use a specific command\n\nUsage:\n newt [flags]\n newt [command]\n\nExamples:\n newt\n newt help [ command-name ]\n For help on command-name . If not specified, print this message.\n\nAvailable Commands:\n build Build one or more targets\n clean Delete build artifacts for one or more targets\n create-image Add image header to target binary\n debug Open debugger session to target\n info Show project info\n install Install project dependencies\n load Load built target to board\n mfg Manufacturing flash image commands\n new Create a new project\n pkg Create and manage packages in the current workspace\n resign-image Re-sign an image.\n run build/create-image/download/debug target \n size Size of target components\n sync Synchronize project dependencies\n target Commands to create, delete, configure, and query targets\n test Executes unit tests for one or more packages\n upgrade Upgrade project dependencies\n vals Display valid values for the specified element type(s)\n version Display the Newt version number\n\nFlags:\n -h, --help Help for newt commands\n -j, --jobs int Number of concurrent build jobs (default 8)\n -l, --loglevel string Log level (default WARN )\n -o, --outfile string Filename to tee output to\n -q, --quiet Be quiet; only display error output\n -s, --silent Be silent; don t output anything\n -v, --verbose Enable verbose output when executing commands\n\nUse newt [command] --help for more information about a command.",
"title": "Checking the Installed Version"
},
{
"location": "/newt/install/newt_mac/#installing-newt-from-the-master-branch",
- "text": "We recommend that you use the latest release version of newt. If you would like to use the master branch with the latest updates, you can install newt from the HEAD of the master branch. Notes: The master branch may be unstable. This installation will install the latest version of Go on your computer, if it is not installed, and compile newt locally. \nIf you previously installed newt using brew, unlink the current version: $brew unlink mynewt-newt \nInstall the latest unstable version of newt from the master branch: $ brew install mynewt-newt --HEAD\n== Installing mynewt-newt from runtimeco/mynewt\n== Cloning https://github.com/apache/mynewt-newt.git\nCloning into /Users/wanda/Library/Caches/Homebrew/mynewt-newt--git ...\nremote: Counting objects: 626, done.\nremote: Compressing objects: 100% (504/504), done.\nremote: Total 626 (delta 155), reused 323 (delta 85), pack-reused 0\nReceiving objects: 100% (626/626), 1.11 MiB | 0 bytes/s, done.\nResolving deltas: 100% (155/155), done.\n== Checking out branch master\n== go install\n\ud83c\udf7a /usr/local/Cellar/mynewt-newt/HEAD-59b3a5d: 3 files, 10.7MB, built in 7 seconds\n$newt version\nApache Newt version 1.1.0-dev \nTo switch back to the latest stable release version of newt, you can run: $brew switch mynewt-newt 1.2.0\nCleaning /usr/local/Cellar/mynewt-newt/1.2.0\nCleaning /usr/local/Cellar/mynewt-newt/HEAD-59b3a5d\n1 links created for /usr/local/Cellar/mynewt-newt/1.2.0\n$newt version\nApache Newt version: 1.2.0",
+ "text": "We recommend that you use the latest release version of newt. If you would like to use the master branch with the latest updates, you can install newt from the HEAD of the master branch. Notes: The master branch may be unstable. This installation will install the latest version of Go on your computer, if it is not installed, and compile newt locally. \nIf you previously installed newt using brew, unlink the current version: $brew unlink mynewt-newt \nInstall the latest unstable version of newt from the master branch: $ brew install mynewt-newt --HEAD \nTo switch back to the latest stable release version of newt, you can run: $brew switch mynewt-newt 1.2.0",
"title": "Installing Newt from the Master Branch"
},
{
"location": "/newt/install/newt_linux/",
- "text": "Installing Newt on Linux\n\n\nYou can install the latest release (1.2.0) of the newt tool from a Debian binary package (amd64). You can also download and build the latest release version of newt from source.\n\n\nThis page shows you how to:\n\n\n\n\n\n\nSet up your computer to download Debian binary packages from the runtimeco APT repository.\n\n\nNote:\n The key for signing the repository has changed. If you set up your computer before release 1.1.0, you will need to download and import the public key again.\n\n\n\n\n\n\nInstall the latest release version of newt from a Debian binary package. You can use apt-get to install the package or manually download and install the Debian binary package.\n\n\n\n\n\n\nDownload, build, and install the latest release version of newt from source.\n\n\n\n\n\n\nIf you are installing on an amd64 platform, we recommend that you install from the binary package.\n\n\nSee \nInstalling Previous Releases of Newt\n to install an earlier version of newt.\n\n\nNote:\n We have tested the newt tool binary and apt-get install from the runtimeco APT repository for Ubuntu version 16. Earlier Ubuntu versions (for example: Ubuntu 14) may have incompatibility with the repository. You can manually download and install the Debian binary package.\n\n\nNote:\n See \nSetting Up a Go Environment to Contribute to Newt and Newtmgr Tools\n if you want to:\n\n\n\n\nUse the newt tool with the latest updates from the master branch. The master branch may be unstable and we recommend that you use the latest stable release version.\n\n\nContribute to the newt tool.\n\n\n\n\n\n\nSetting Up Your Computer to use apt-get to Install the Package\n\n\nThe newt Debian packages are stored in a private APT repository on \nhttps://github/runtimeco/debian-mynewt\n. To use apt-get, you must set up the following on your computer to retrieve packages from the repository:\n\n\nNote\n: You only need to perform this setup once on your computer. However, if you previously downloaded and imported the public key for the runtimeco APT repository, you will need to perform step 2 again as the key has changed.\n\n\n\n\nInstall the \napt-transport-https\n package to use HTTPS to retrieve packages. \n\n\nDownload the public key for the runtimeco APT repository and import the key into the apt keychain.\n\n\nAdd the repository for the binary and source packages to the apt source list.\n\n\n\n\n\nInstall the apt-transport-https package:\n\n\n$ sudo apt-get update\n$ sudo apt-get install apt-transport-https\n\n\n\n\n\n\n\nDownload the public key for the runtimeco apt repo (\nNote:\n There is a \n-\n after \napt-key add\n):\n\n\n$ wget -qO - https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/mynewt.gpg.key | sudo apt-key add -\n\n\n\n\n\n\n\nAdd the repository for the binary and source packages to the \nmynewt.list\n apt source list file:\n\n\n$ sudo tee /etc/apt/sources.list.d/mynewt.list \nEOF\ndeb https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest main\nEOF\n\n\n\n\n\n\nUpdate the available packages: \n\n\n$ sudo apt-get update\n\n\n\n\n\n\n\nNote:\n If you are not using Ubuntu version 16, you may see the following errors. We have provided instructions on how to manually download and install the binary package.\n\n\nW: Failed to fetch https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/dists/latest/main/source/Sources Ht\ntpError404\n\n\n\n\n\n\n\nInstalling the Latest Release of Newt from a Binary Package\n\n\nYou can use either apt-get to install the package, or manually download and install the Debian binary package.\n\n\n\n\nMethod 1: Using apt-get to Upgrade or to Install\n\n\nRun the following commands to upgrade or install the latest version of newt:\n\n\n$ sudo apt-get update \n$ sudo apt-get install newt\n\n\n\n\n\nNote:\n If you encounter build errors (such as missing \nsys/mman.h\n), please make sure you have a 32-bit glibc:\n\n\n$ sudo apt-get install gcc-multilib\n\n\n\n\n\n\n\nMethod 2: Downloading and Installing the Debian Package Manually\n\n\nDownload and install the package manually.\n\n\n$ wget https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/pool/main/n/newt/newt_1.2.0-1_amd64.deb\n$ sudo dpkg -i newt_1.2.0-1_amd64.deb\n\n\n\n\n\n\nSee \nChecking the Installed Version of Newt\n to verify that you are using the installed version of newt.\n\n\n\n\nInstalling the Latest Release of Newt from a Source Package\n\n\nIf you are running Linux on a different architecture, you can build and install the latest release version of newt from source.\n\n\n\n1. You need Go version 1.7.6 or higher to build Newt. Currently, the latest Go version that Ubuntu installs is 1.6. Run \ngo version\n to check if you have Go 1.7.6 installed. You can download Go from \nhttps://golang.org/dl/\n.\n\n\n\n2. Download and unpack the newt source:\n\n\n$ wget -P /tmp https://github.com/apache/mynewt-newt/archive/mynewt_1_2_0_tag.tar.gz\n$ tar -xzf /tmp/mynewt_1_2_0_tag.tar.gz\n\n\n\n\n\n\n3. Run the build.sh to build the newt tool.\n\n\n$ cd mynewt-newt-mynewt_1_2_0_tag\n$ ./build.sh\n$ rm /tmp/mynewt_1_2_0_tag.tar.gz\n\n\n\n\n\n\n4. You should see the \nnewt/newt\n executable. Move the executable to a bin directory in your PATH:\n\n\n\n\n\n\nIf you previously built newt from the master branch, you can move the binary to your $GOPATH/bin directory.\n\n\n$ mv newt/newt $GOPATH/bin\n\n\n\n\n\n\n\n\n\nIf you are installing newt for the first time and do not have a Go workspace set up, you can move the binary to /usr/bin or a directory in your PATH:\n\n\n$ mv newt/newt /usr/bin\n\n\n\n\n\n\n\n\n\n\n\n Checking the Installed Version of Newt\n\n\n\n1. Check which newt you are using and that the version is the latest release version.\n\n\n$ which newt\n/usr/bin/newt\n$ newt version\nApache Newt version: 1.2.0\n\n\n\n\n\n\n2. Get information about newt:\n\n\n$ newt\nNewt allows you to create your own embedded application based on the Mynewt \noperating system. Newt provides both build and package management in a single \ntool, which allows you to compose an embedded application, and set of \nprojects, and then build the necessary artifacts from those projects. For more \ninformation on the Mynewt operating system, please visit \nhttps://mynewt.apache.org/. \n\nPlease use the newt help command, and specify the name of the command you want \nhelp for, for help on how to use a specific command\n\nUsage:\n newt [flags]\n newt [command]\n\nExamples:\n newt\n newt help [\ncommand-name\n]\n For help on \ncommand-name\n. If not specified, print this message.\n\nAvailable Commands:\n build Build one or more targets\n clean Delete build artifacts for one or more targets\n create-image Add image header to target binary\n debug Open debugger session to target\n info Show project info\n install Install project dependencies\n load Load built target to board\n mfg Manufacturing flash image commands\n new Create a new project\n pkg Create and manage packages in the current workspace\n resign-image Re-sign an image.\n run build/create-image/download/debug \ntarget\n\n size Size of target components\n sync Synchronize project dependencies\n target Commands to create, delete, configure, and query targets\n test Executes unit tests for one or more packages\n upgrade Upgrade project dependencies\n vals Display valid values for the specified element type(s)\n version Display the Newt version number\n\nFlags:\n -h, --help Help for newt commands\n -j, --jobs int Number of concurrent build jobs (default 8)\n -l, --loglevel string Log level (default \nWARN\n)\n -o, --outfile string Filename to tee output to\n -q, --quiet Be quiet; only display error output\n -s, --silent Be silent; don\nt output anything\n -v, --verbose Enable verbose output when executing commands\n\nUse \nnewt [command] --help\n for more information about a command.",
+ "text": "Installing Newt on Linux\n\n\nYou can install the latest release (1.2.0) of the newt tool from a Debian binary package (amd64). You can also download and build the latest release version of newt from source.\n\n\nThis page shows you how to:\n\n\n\n\n\n\nSet up your computer to download Debian binary packages from the runtimeco APT repository.\n\n\nNote:\n The key for signing the repository has changed. If you set up your computer before release 1.1.0, you will need to download and import the public key again.\n\n\n\n\n\n\nInstall the latest release version of newt from a Debian binary package. You can use apt-get to install the package or manually download and install the Debian binary package.\n\n\n\n\n\n\nDownload, build, and install the latest release version of newt from source.\n\n\n\n\n\n\nIf you are installing on an amd64 platform, we recommend that you install from the binary package.\n\n\nSee \nInstalling Previous Releases of Newt\n to install an earlier version of newt.\n\n\nNote:\n We have tested the newt tool binary and apt-get install from the runtimeco APT repository for Ubuntu version 16. Earlier Ubuntu versions (for example: Ubuntu 14) may have incompatibility with the repository. You can manually download and install the Debian binary package.\n\n\nNote:\n See \nSetting Up a Go Environment to Contribute to Newt and Newtmgr Tools\n if you want to:\n\n\n\n\nUse the newt tool with the latest updates from the master branch. The master branch may be unstable and we recommend that you use the latest stable release version.\n\n\nContribute to the newt tool.\n\n\n\n\n\n\nSetting Up Your Computer to use apt-get to Install the Package\n\n\nThe newt Debian packages are stored in a private APT repository on \nhttps://github/runtimeco/debian-mynewt\n. To use apt-get, you must set up the following on your computer to retrieve packages from the repository:\n\n\nNote\n: You only need to perform this setup once on your computer. However, if you previously downloaded and imported the public key for the runtimeco APT repository, you will need to perform step 2 again as the key has changed.\n\n\n\n\nInstall the \napt-transport-https\n package to use HTTPS to retrieve packages. \n\n\nDownload the public key for the runtimeco APT repository and import the key into the apt keychain.\n\n\nAdd the repository for the binary and source packages to the apt source list.\n\n\n\n\n\nInstall the apt-transport-https package:\n\n\n$ sudo apt-get update\n$ sudo apt-get install apt-transport-https\n\n\n\n\n\n\n\nDownload the public key for the runtimeco apt repo (\nNote:\n There is a \n-\n after \napt-key add\n):\n\n\n$ wget -qO - https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/mynewt.gpg.key | sudo apt-key add -\n\n\n\n\n\n\n\nAdd the repository for the binary and source packages to the \nmynewt.list\n apt source list file:\n\n\n$ sudo tee /etc/apt/sources.list.d/mynewt.list \nEOF\ndeb https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest main\nEOF\n\n\n\n\n\n\nUpdate the available packages: \n\n\n$ sudo apt-get update\n\n\n\n\n\n\n\nNote:\n If you are not using Ubuntu version 16, you may see the following errors. We have provided instructions on how to manually download and install the binary package.\n\n\nW: Failed to fetch https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/dists/latest/main/source/Sources HttpError404\n\n\n\n\n\n\n\nInstalling the Latest Release of Newt from a Binary Package\n\n\nYou can use either apt-get to install the package, or manually download and install the Debian binary package.\n\n\n\n\nMethod 1: Using apt-get to Upgrade or to Install\n\n\nRun the following commands to upgrade or install the latest version of newt:\n\n\n$ sudo apt-get update \n$ sudo apt-get install newt\n\n\n\n\n\nNote:\n If you encounter build errors (such as missing \nsys/mman.h\n), please make sure you have a 32-bit glibc:\n\n\n$ sudo apt-get install gcc-multilib\n\n\n\n\n\n\n\nMethod 2: Downloading and Installing the Debian Package Manually\n\n\nDownload and install the package manually.\n\n\n$wget https://raw.githubusercontent.com/runtimeco/binary-releases/master/mynewt-newt-tools_1.2.0/newt_1.2.0-1_amd64.deb\n$sudo dpkg -i newt_1.2.0-1_amd64.deb\n\n\n\n\n\n\nSee \nChecking the Installed Version of Newt\n to verify that you are using the installed version of newt.\n\n\n\n\nInstalling the Latest Release of Newt from a Source Package\n\n\nIf you are running Linux on a different architecture, you can build and install the latest release version of newt from source.\n\n\n\n1. You need Go version 1.7.6 or higher to build Newt. Currently, the latest Go version that Ubuntu installs is 1.6. Run \ngo version\n to check if you have Go 1.7.6 installed. You can download Go from \nhttps://golang.org/dl/\n.\n\n\n\n2. Download and unpack the newt source:\n\n\n$ wget -P /tmp https://github.com/apache/mynewt-newt/archive/mynewt_1_2_0_tag.tar.gz\n$ tar -xzf /tmp/mynewt_1_2_0_tag.tar.gz\n\n\n\n\n\n\n3. Run the build.sh to build the newt tool.\n\n\n$ cd mynewt-newt-mynewt_1_2_0_tag\n$ ./build.sh\n$ rm /tmp/mynewt_1_2_0_tag.tar.gz\n\n\n\n\n\n\n4. You should see the \nnewt/newt\n executable. Move the executable to a bin directory in your PATH:\n\n\n\n\n\n\nIf you previously built newt from the master branch, you can move the binary to your $GOPATH/bin directory.\n\n\n$ mv newt/newt $GOPATH/bin\n\n\n\n\n\n\n\n\n\nIf you are installing newt for the first time and do not have a Go workspace set up, you can move the binary to /usr/bin or a directory in your PATH:\n\n\n$ mv newt/newt /usr/bin\n\n\n\n\n\n\n\n\n\n\n\n Checking the Installed Version of Newt\n\n\n\n1. Check which newt you are using and that the version is the latest release version.\n\n\n$ which newt\n/usr/bin/newt\n$ newt version\nApache Newt version: 1.2.0\n\n\n\n\n\n\n2. Get information about newt:\n\n\n$ newt\nNewt allows you to create your own embedded application based on the Mynewt \noperating system. Newt provides both build and package management in a single \ntool, which allows you to compose an embedded application, and set of \nprojects, and then build the necessary artifacts from those projects. For more \ninformation on the Mynewt operating system, please visit \nhttps://mynewt.apache.org/. \n\nPlease use the newt help command, and specify the name of the command you want \nhelp for, for help on how to use a specific command\n\nUsage:\n newt [flags]\n newt [command]\n\nExamples:\n newt\n newt help [\ncommand-name\n]\n For help on \ncommand-name\n. If not specified, print this message.\n\nAvailable Commands:\n build Build one or more targets\n clean Delete build artifacts for one or more targets\n create-image Add image header to target binary\n debug Open debugger session to target\n info Show project info\n install Install project dependencies\n load Load built target to board\n mfg Manufacturing flash image commands\n new Create a new project\n pkg Create and manage packages in the current workspace\n resign-image Re-sign an image.\n run build/create-image/download/debug \ntarget\n\n size Size of target components\n sync Synchronize project dependencies\n target Commands to create, delete, configure, and query targets\n test Executes unit tests for one or more packages\n upgrade Upgrade project dependencies\n vals Display valid values for the specified element type(s)\n version Display the Newt version number\n\nFlags:\n -h, --help Help for newt commands\n -j, --jobs int Number of concurrent build jobs (default 8)\n -l, --loglevel string Log level (default \nWARN\n)\n -o, --outfile string Filename to tee output to\n -q, --quiet Be quiet; only display error output\n -s, --silent Be silent; don\nt output anything\n -v, --verbose Enable verbose output when executing commands\n\nUse \nnewt [command] --help\n for more information about a command.",
"title": "Install Newt on Linux"
},
{
@@ -217,7 +217,7 @@
},
{
"location": "/newt/install/newt_linux/#setting-up-your-computer-to-use-apt-get-to-install-the-package",
- "text": "The newt Debian packages are stored in a private APT repository on https://github/runtimeco/debian-mynewt . To use apt-get, you must set up the following on your computer to retrieve packages from the repository: Note : You only need to perform this setup once on your computer. However, if you previously downloaded and imported the public key for the runtimeco APT repository, you will need to perform step 2 again as the key has changed. Install the apt-transport-https package to use HTTPS to retrieve packages. Download the public key for the runtimeco APT repository and import the key into the apt keychain. Add the repository for the binary and source packages to the apt source list. \nInstall the apt-transport-https package: $ sudo apt-get update\n$ sudo apt-get install apt-transport-https Download the public key for the runtimeco apt repo ( Note: There is a - after apt-key add ): $ wget -qO - https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/mynewt.gpg.key | sudo apt-key add - Add the repository for the binary and source packages to the mynewt.list apt source list file: $ sudo tee /etc/apt/sources.list.d/mynewt.list EOF\ndeb https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest main\nEOF \nUpdate the available packages: $ sudo apt-get update Note: If you are not using Ubuntu version 16, you may see the following errors. We have provided instructions on how to manually download and install the binary package. W: Failed to fetch https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/dists/latest/main/source/Sources Ht\ntpError404",
+ "text": "The newt Debian packages are stored in a private APT repository on https://github/runtimeco/debian-mynewt . To use apt-get, you must set up the following on your computer to retrieve packages from the repository: Note : You only need to perform this setup once on your computer. However, if you previously downloaded and imported the public key for the runtimeco APT repository, you will need to perform step 2 again as the key has changed. Install the apt-transport-https package to use HTTPS to retrieve packages. Download the public key for the runtimeco APT repository and import the key into the apt keychain. Add the repository for the binary and source packages to the apt source list. \nInstall the apt-transport-https package: $ sudo apt-get update\n$ sudo apt-get install apt-transport-https Download the public key for the runtimeco apt repo ( Note: There is a - after apt-key add ): $ wget -qO - https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/mynewt.gpg.key | sudo apt-key add - Add the repository for the binary and source packages to the mynewt.list apt source list file: $ sudo tee /etc/apt/sources.list.d/mynewt.list EOF\ndeb https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest main\nEOF \nUpdate the available packages: $ sudo apt-get update Note: If you are not using Ubuntu version 16, you may see the following errors. We have provided instructions on how to manually download and install the binary package. W: Failed to fetch https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/dists/latest/main/source/Sources HttpError404",
"title": "Setting Up Your Computer to use apt-get to Install the Package"
},
{
@@ -232,7 +232,7 @@
},
{
"location": "/newt/install/newt_linux/#method-2-downloading-and-installing-the-debian-package-manually",
- "text": "Download and install the package manually. $ wget https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/pool/main/n/newt/newt_1.2.0-1_amd64.deb\n$ sudo dpkg -i newt_1.2.0-1_amd64.deb \nSee Checking the Installed Version of Newt to verify that you are using the installed version of newt.",
+ "text": "Download and install the package manually. $wget https://raw.githubusercontent.com/runtimeco/binary-releases/master/mynewt-newt-tools_1.2.0/newt_1.2.0-1_amd64.deb\n$sudo dpkg -i newt_1.2.0-1_amd64.deb \nSee Checking the Installed Version of Newt to verify that you are using the installed version of newt.",
"title": "Method 2: Downloading and Installing the Debian Package Manually"
},
{
@@ -242,12 +242,12 @@
},
{
"location": "/newt/install/newt_windows/",
- "text": "Installing Newt on Windows\n\n\nYou can develop and build Mynewt OS applications for your target boards on the Windows platform. This guide shows you how to install the latest release version of newt from binary or from source. The tool is written in Go (golang).\n\n\nIn Windows, we use MinGW as the development environment to build and run Mynewt OS applications for target boards. MinGW runs the bash shell and provides a Unix-like environment. This provides a uniform way to build Mynewt OS applications. The Mynewt documentation and tutorials use Unix commands and you can use the same Unix commands on MinGW to follow the tutorials. The documentation will note any commands or behaviors that are specific to Windows.\n\n\nThis guide shows you how to perform the following:\n\n\n\n\nInstall MSYS2/MinGW. \n\n\nInstall Git.\n\n\nInstall latest release of newt (1.2.0) from binary.\n\n\nInstall latest release of newt from source.\n\n\n\n\nSee \nInstalling Previous Releases of Newt\n to install an earlier version of newt. You still need to set up your MinGW development environment.\n\n\nNote:\n If you would like to contribute to the newt tool, see \nSetting Up Go Environment to Contribute to Newt and Newtmgr Tools\n.\n\n\n\n\nInstalling MSYS2/MinGW\n\n\nMSYS2/MinGW provides a bash shell and tools to build applications that run on Windows. It includes three subsystems:\n\n\n\n\nMSYS2 toolchain to build POSIX applications that run on Windows. \n\n\nMinGW32 toolchains to build 32 bit native Windows applications. \n\n\nMinGW64 toolchains to build 64 bit native Windows applications. \n\n\n\n\nThe subsystems run the bash shell and provide a Unix-like environment. You can also run Windows applications from the shell. We will use the MinGW subsystem.\n\n\nNote:\n You can skip this installation step if you already have MinGW installed (from an earlier MSYS2/MinGW or Git Bash installation), but you must list the \nbin\n path for your installation in your Windows Path. For example: if you installed MSYS2/MinGW in the \n C:\\msys64 \n directory, add \nC:\\msys64\\usr\\bin\n to your Windows Path. If you are using Windows 10 WSL, ensure that you use the \nC:\\msys64\\usr\\bin\\bash.exe\n and not the Windows 10 WSL bash.\n\n\nTo install and setup MSYS2 and MinGW:\n\n\n\n\nDownload and run the \nMSYS2 installer\n. Select the 64 bit version if you are running on a 64 bit platform. Follow the prompts and check the \nRun MSYS2 now\n checkbox on the \nInstallation Complete\n dialog. \n\n\n\n\nIn the MSYS2 terminal, run the \npacman -Syuu\n command. If you get a message to run the update again, close the terminal and run the \npacman -Syuu\n command in a new terminal. \n\n\nTo start a new MSYS2 terminal, select the \"MSYS2 MSYS\" application from the Windows start menu.\n\n\n\n\n\n\nAdd a new user variable named \nMSYS2_PATH_TYPE\n and set the value to \ninherit\n in your Windows environment. This enables the MSYS2 and MinGW bash to inherit your Windows user \nPath\n values. \n\n\nTo add the variable, select properties for your computer \n Advanced system settings \n Environment Variables \n New\n\n\n\n\n\n\nAdd the MinGW \nbin\n path to your Windows Path. For example: if you install MSYS2/MinGW in the \nC:\\msys64\n directory, add \nC:\\msys64\\usr\\bin\n to your Windows Path. \n\n\nNote:\n If you are using Windows 10 WSL, ensure that you use the \nC:\\msys64\\usr\\bin\\bash.exe\n and not the Windows 10 WSL bash.\n\n\n\n\n\n\nRun the \npacman -Su vim\n command to install the vim editor. \n\n\nNote:\nYou can also use a Windows editor. You can access your files from the \nC:\\\nmsys-install-folder\n\\home\\\nusername\n folder, where \nmsys-install-folder\n is the folder you installed MSYS2 in. For example, if you installed MSYS2 in the \nmsys64\n folder, your files are stored in \nC:\\msys64\\home\\\nusername\n\n\n\n\n\n\nRun the \npacman -Su tar\n command to install the tar tool. \n\n\n\n\n\n\nYou will need to start a MinGW terminal to run the commands specified in the Mynewt documentation and tutorials. To start a MinGW terminal, select the \"MSYS2 Mingw\" application from the start Menu (you can use either MinGW32 or MinGW64). \nIn Windows, we use the MinGW subsystem to build Mynewt tools and applications. \n\n\nInstalling Git for Windows\n\n\nDownload and install \nGit for Windows\n if it is not already installed.\n\n\nInstalling the Latest Release of the Newt Tool from Binary\n\n\nYou can install the latest release of newt from binary. It has been tested on Windows 10 64 bit platform. \n\n\n\n1. Start a MinGW terminal.\n\n\n\n2. Download the newt binary tar file:\n\n\n$ wget -P /tmp https://raw.githubusercontent.com/runtimeco/binary-releases/master/mynewt-newt-tools_1.2.0/newt_1_2_0_windows_amd64.tar.gz\n\n\n\n\n\n\n3. Extract the file:\n\n\n\n\n\n\nIf you previously built newt from the master branch, you can extract the file into your $GOPATH/bin directory. Note: This overwrites the current newt.exe in the directory and assumes that you are using $GOPATH/bin for your Go applications.\n\n\n tar -xzf /tmp/newt_1_2_0_windows_amd64.tar.gz -C $GOPATH/bin\n\n\n\n\n\n\n\n\n\nIf you are installing newt for the first time and do not have a Go workspace setup, you can extract into /usr/bin directory:\n\n\n tar -xzf /tmp/newt_1_2_0_windows_amd64.tar.gz -C /usr/bin\n\n\n\n\n\n\n\n\n\n\n4. Verify the installed version of newt. See \nChecking the Installed Version\n.\n\n\n\n\nInstalling the Latest Release of Newt From Source\n\n\nIf you have an older version of Windows or a 32 bit platform, you can build and install the latest release version of newt from source.\n\n\n\n1. If you do not have Go installed, download and install the latest version of \nGo\n. Newt requires Go version 1.7.6 or higher.\n\n\n\n2. Start a MinGw terminal.\n\n\n\n3. Download and unpack the newt source:\n\n\n$ wget -P /tmp https://github.com/apache/mynewt-newt/archive/mynewt_1_2_0_tag.tar.gz\n$ tar -xzf /tmp/mynewt_1_2_0_tag.tar.gz\n\n\n\n\n\n\n4. Run the build.sh to build the newt tool.\n\n\n$ cd mynewt-newt-mynewt_1_2_0_tag \n$ ./build.sh\n$ rm /tmp/mynewt_1_2_0_tag.tar.gz\n\n\n\n\n\n\n5. You should see the \nnewt/newt.exe\n executable. Move the executable to a bin directory in your PATH:\n\n\n\n\n\n\nIf you previously built newt from the master branch, you can move the executable to the $GOPATH/bin directory.\n\n\n$ mv newt/newt.exe $GOPATH/bin\n\n\n\n\n\n\n\n\n\nIf you are installing newt for the first time and do not have a Go workspace set up, you can move the executable to /usr/bin or a directory in your PATH:\n\n\n$ mv newt/newt.exe /usr/bin\n\n\n\n\n\n\n\n\n\n\n\nChecking the Installed Version\n\n\n\n1. Check the version of newt:\n\n\n$ newt version\nApache Newt version: 1.2.0\n\n\n\n\n\n\n2. Get information about newt:\n\n\nNewt allows you to create your own embedded application based on the Mynewt \noperating system. Newt provides both build and package management in a single \ntool, which allows you to compose an embedded application, and set of \nprojects, and then build the necessary artifacts from those projects. For more \ninformation on the Mynewt operating system, please visit \nhttps://mynewt.apache.org/. \n\nPlease use the newt help command, and specify the name of the command you want \nhelp for, for help on how to use a specific command\n\nUsage:\n newt [flags]\n newt [command]\n\nExamples:\n newt\n newt help [\ncommand-name\n]\n For help on \ncommand-name\n. If not specified, print this message.\n\nAvailable Commands:\n build Build one or more targets\n clean Delete build artifacts for one or more targets\n create-image Add image header to target binary\n debug Open debugger session to target\n info Show project info\n install Install project dependencies\n load Load built target to board\n mfg Manufacturing flash image commands\n new Create a new project\n pkg Create and manage packages in the current workspace\n resign-image Re-sign an image.\n run build/create-image/download/debug \ntarget\n\n size Size of target components\n sync Synchronize project dependencies\n target Commands to create, delete, configure, and query targets\n test Executes unit tests for one or more packages\n upgrade Upgrade project dependencies\n vals Display valid values for the specified element type(s)\n version Display the Newt version number\n\nFlags:\n -h, --help Help for newt commands\n -j, --jobs int Number of concurrent build jobs (default 8)\n -l, --loglevel string Log level (default \nWARN\n)\n -o, --outfile string Filename to tee output to\n -q, --quiet Be quiet; only display error output\n -s, --silent Be silent; don\nt output anything\n -v, --verbose Enable verbose output when executing commands\n\nUse \nnewt [command] --help\n for more information about a command.",
+ "text": "Installing Newt on Windows\n\n\nYou can develop and build Mynewt OS applications for your target boards on the Windows platform. This guide shows you how to install the latest release version of newt from binary or from source. The tool is written in Go (golang).\n\n\nIn Windows, we use MinGW as the development environment to build and run Mynewt OS applications for target boards. MinGW runs the bash shell and provides a Unix-like environment. This provides a uniform way to build Mynewt OS applications. The Mynewt documentation and tutorials use Unix commands and you can use the same Unix commands on MinGW to follow the tutorials. The documentation will note any commands or behaviors that are specific to Windows.\n\n\nThis guide shows you how to perform the following:\n\n\n\n\nInstall MSYS2/MinGW. \n\n\nInstall Git.\n\n\nInstall latest release (1.2.0) of newt from binary.\n\n\nInstall latest release of newt from source.\n\n\n\n\nSee \nInstalling Previous Releases of Newt\n to install an earlier version of newt. You still need to set up your MinGW development environment.\n\n\nNote:\n If you would like to contribute to the newt tool, see \nSetting Up Go Environment to Contribute to Newt and Newtmgr Tools\n.\n\n\n\n\nInstalling MSYS2/MinGW\n\n\nMSYS2/MinGW provides a bash shell and tools to build applications that run on Windows. It includes three subsystems:\n\n\n\n\nMSYS2 toolchain to build POSIX applications that run on Windows. \n\n\nMinGW32 toolchains to build 32 bit native Windows applications. \n\n\nMinGW64 toolchains to build 64 bit native Windows applications. \n\n\n\n\nThe subsystems run the bash shell and provide a Unix-like environment. You can also run Windows applications from the shell. We will use the MinGW subsystem.\n\n\nNote:\n You can skip this installation step if you already have MinGW installed (from an earlier MSYS2/MinGW or Git Bash installation), but you must list the \nbin\n path for your installation in your Windows Path. For example: if you installed MSYS2/MinGW in the \n C:\\msys64 \n directory, add \nC:\\msys64\\usr\\bin\n to your Windows Path. If you are using Windows 10 WSL, ensure that you use the \nC:\\msys64\\usr\\bin\\bash.exe\n and not the Windows 10 WSL bash.\n\n\nTo install and setup MSYS2 and MinGW:\n\n\n\n\nDownload and run the \nMSYS2 installer\n. Select the 64 bit version if you are running on a 64 bit platform. Follow the prompts and check the \nRun MSYS2 now\n checkbox on the \nInstallation Complete\n dialog. \n\n\n\n\nIn the MSYS2 terminal, run the \npacman -Syuu\n command. If you get a message to run the update again, close the terminal and run the \npacman -Syuu\n command in a new terminal. \n\n\nTo start a new MSYS2 terminal, select the \"MSYS2 MSYS\" application from the Windows start menu.\n\n\n\n\n\n\nAdd a new user variable named \nMSYS2_PATH_TYPE\n and set the value to \ninherit\n in your Windows environment. This enables the MSYS2 and MinGW bash to inherit your Windows user \nPath\n values. \n\n\nTo add the variable, select properties for your computer \n Advanced system settings \n Environment Variables \n New\n\n\n\n\n\n\nAdd the MinGW \nbin\n path to your Windows Path. For example: if you install MSYS2/MinGW in the \nC:\\msys64\n directory, add \nC:\\msys64\\usr\\bin\n to your Windows Path. \n\n\nNote:\n If you are using Windows 10 WSL, ensure that you use the \nC:\\msys64\\usr\\bin\\bash.exe\n and not the Windows 10 WSL bash.\n\n\n\n\n\n\nRun the \npacman -Su vim\n command to install the vim editor. \n\n\nNote:\nYou can also use a Windows editor. You can access your files from the \nC:\\\nmsys-install-folder\n\\home\\\nusername\n folder, where \nmsys-install-folder\n is the folder you installed MSYS2 in. For example, if you installed MSYS2 in the \nmsys64\n folder, your files are stored in \nC:\\msys64\\home\\\nusername\n\n\n\n\n\n\nRun the \npacman -Su tar\n command to install the tar tool. \n\n\n\n\n\n\nYou will need to start a MinGW terminal to run the commands specified in the Mynewt documentation and tutorials. To start a MinGW terminal, select the \"MSYS2 Mingw\" application from the start Menu (you can use either MinGW32 or MinGW64). \nIn Windows, we use the MinGW subsystem to build Mynewt tools and applications. \n\n\nInstalling Git for Windows\n\n\nDownload and install \nGit for Windows\n if it is not already installed.\n\n\nInstalling the Latest Release of the Newt Tool from Binary\n\n\nYou can install the latest release of newt from binary. It has been tested on Windows 10 64 bit platform. \n\n\n\n1. Start a MinGW terminal.\n\n\n\n2. Download the newt binary tar file:\n\n\n$ wget -P /tmp https://raw.githubusercontent.com/runtimeco/binary-releases/master/mynewt-newt-tools_1.2.0/newt_1_2_0_windows_amd64.tar.gz\n\n\n\n\n\n\n3. Extract the file:\n\n\n\n\n\n\nIf you previously built newt from the master branch, you can extract the file into your $GOPATH/bin directory. Note: This overwrites the current newt.exe in the directory and assumes that you are using $GOPATH/bin for your Go applications.\n\n\n tar -xzf /tmp/newt_1_2_0_windows_amd64.tar.gz -C $GOPATH/bin\n\n\n\n\n\n\n\n\n\nIf you are installing newt for the first time and do not have a Go workspace setup, you can extract into /usr/bin directory:\n\n\n tar -xzf /tmp/newt_1_2_0_windows_amd64.tar.gz -C /usr/bin\n\n\n\n\n\n\n\n\n\n\n4. Verify the installed version of newt. See \nChecking the Installed Version\n.\n\n\n\n\nInstalling the Latest Release of Newt From Source\n\n\nIf you have an older version of Windows or a 32 bit platform, you can build and install the latest release version of newt from source.\n\n\n\n1. If you do not have Go installed, download and install the latest version of \nGo\n. Newt requires Go version 1.7.6 or higher.\n\n\n\n2. Start a MinGw terminal.\n\n\n\n3. Download and unpack the newt source:\n\n\n$ wget -P /tmp https://github.com/apache/mynewt-newt/archive/mynewt_1_2_0_tag.tar.gz\n$ tar -xzf /tmp/mynewt_1_2_0_tag.tar.gz\n\n\n\n\n\n\n4. Run the build.sh to build the newt tool.\n\n\n$ cd mynewt-newt-mynewt_1_2_0_tag \n$ ./build.sh\n$ rm /tmp/mynewt_1_2_0_tag.tar.gz\n\n\n\n\n\n\n5. You should see the \nnewt/newt.exe\n executable. Move the executable to a bin directory in your PATH:\n\n\n\n\n\n\nIf you previously built newt from the master branch, you can move the executable to the $GOPATH/bin directory.\n\n\n$ mv newt/newt.exe $GOPATH/bin\n\n\n\n\n\n\n\n\n\nIf you are installing newt for the first time and do not have a Go workspace set up, you can move the executable to /usr/bin or a directory in your PATH:\n\n\n$ mv newt/newt.exe /usr/bin\n\n\n\n\n\n\n\n\n\n\n\nChecking the Installed Version\n\n\n\n1. Check the version of newt:\n\n\n$ newt version\nApache Newt version: 1.2.0\n\n\n\n\n\n\n2. Get information about newt:\n\n\nNewt allows you to create your own embedded application based on the Mynewt \noperating system. Newt provides both build and package management in a single \ntool, which allows you to compose an embedded application, and set of \nprojects, and then build the necessary artifacts from those projects. For more \ninformation on the Mynewt operating system, please visit \nhttps://mynewt.apache.org/. \n\nPlease use the newt help command, and specify the name of the command you want \nhelp for, for help on how to use a specific command\n\nUsage:\n newt [flags]\n newt [command]\n\nExamples:\n newt\n newt help [\ncommand-name\n]\n For help on \ncommand-name\n. If not specified, print this message.\n\nAvailable Commands:\n build Build one or more targets\n clean Delete build artifacts for one or more targets\n create-image Add image header to target binary\n debug Open debugger session to target\n info Show project info\n install Install project dependencies\n load Load built target to board\n mfg Manufacturing flash image commands\n new Create a new project\n pkg Create and manage packages in the current workspace\n resign-image Re-sign an image.\n run build/create-image/download/debug \ntarget\n\n size Size of target components\n sync Synchronize project dependencies\n target Commands to create, delete, configure, and query targets\n test Executes unit tests for one or more packages\n upgrade Upgrade project dependencies\n vals Display valid values for the specified element type(s)\n version Display the Newt version number\n\nFlags:\n -h, --help Help for newt commands\n -j, --jobs int Number of concurrent build jobs (default 8)\n -l, --loglevel string Log level (default \nWARN\n)\n -o, --outfile string Filename to tee output to\n -q, --quiet Be quiet; only display error output\n -s, --silent Be silent; don\nt output anything\n -v, --verbose Enable verbose output when executing commands\n\nUse \nnewt [command] --help\n for more information about a command.",
"title": "Install Newt on Windows"
},
{
"location": "/newt/install/newt_windows/#installing-newt-on-windows",
- "text": "You can develop and build Mynewt OS applications for your target boards on the Windows platform. This guide shows you how to install the latest release version of newt from binary or from source. The tool is written in Go (golang). In Windows, we use MinGW as the development environment to build and run Mynewt OS applications for target boards. MinGW runs the bash shell and provides a Unix-like environment. This provides a uniform way to build Mynewt OS applications. The Mynewt documentation and tutorials use Unix commands and you can use the same Unix commands on MinGW to follow the tutorials. The documentation will note any commands or behaviors that are specific to Windows. This guide shows you how to perform the following: Install MSYS2/MinGW. Install Git. Install latest release of newt (1.2.0) from binary. Install latest release of newt from source. See Installing Previous Releases of Newt to install an earlier version of newt. You still need to set up your MinGW development environment. Note: If you would like to contribute to the newt tool, see Setting Up Go Environment to Contribute to Newt and Newtmgr Tools .",
+ "text": "You can develop and build Mynewt OS applications for your target boards on the Windows platform. This guide shows you how to install the latest release version of newt from binary or from source. The tool is written in Go (golang). In Windows, we use MinGW as the development environment to build and run Mynewt OS applications for target boards. MinGW runs the bash shell and provides a Unix-like environment. This provides a uniform way to build Mynewt OS applications. The Mynewt documentation and tutorials use Unix commands and you can use the same Unix commands on MinGW to follow the tutorials. The documentation will note any commands or behaviors that are specific to Windows. This guide shows you how to perform the following: Install MSYS2/MinGW. Install Git. Install latest release (1.2.0) of newt from binary. Install latest release of newt from source. See Installing Previous Releases of Newt to install an earlier version of newt. You still need to set up your MinGW development environment. Note: If you would like to contribute to the newt tool, see Setting Up Go Environment to Contribute to Newt and Newtmgr Tools .",
"title": "Installing Newt on Windows"
},
{
@@ -1592,7 +1592,7 @@
},
{
"location": "/os/tutorials/lora/lorawanapp/",
- "text": "LoRaWAN App\n\n\n\n\nObjective\n\n\nThe purpose of this tutorial is to demonstrate how to build the lora app shell application for either a class A or class C lora device and to perform basic functions such as joining and sending data packets to a lora gateway/server.\n\n\nNOTE: This tutorial presumes that you have a running lora gateway and lora network server. No description of the gateway/server is provided. It is expected that the user understands how to configure and operate the gateway/server so that it can communicate with a class A or class C device.\n\n\n\n\nHardware needed\n\n\n\n\nTelenor EE02 module\n\n\nSegger J-Link or similar debugger\n\n\nLORA gateway\n\n\nLaptop running Mac OS\n\n\nIt is assumed you have already installed newt tool. \n\n\nIt is assumed you understand the basics of the mynewt OS\n\n\n3-wire serial cable to connect telenor module to your laptop\n\n\nSome form of terminal emulation application running on your laptop.\n\n\n\n\n\n\nCreate a project.\n\n\nCreate a new project to hold your work. For a deeper understanding, you can read about project creation in \n\nGet Started -- Creating Your First Project\n\nor just follow the commands below.\n\n\n $ mkdir ~/dev\n $ cd ~/dev\n $ newt new mylora\n Downloading project skeleton from apache/mynewt-blinky...\n Installing skeleton in mylora...\n Project mylora successfully created.\n $ cd mylora\n\n\n\n\n\n\n\nInstall Everything\n\n\nNow that you have defined the needed repositories, it's time to install everything so\nthat you can get started.\n\n\n $ newt install -v \n apache-mynewt-core\n Downloading repository description for apache-mynewt-core... success!\n ...\n apache-mynewt-core successfully installed version 1.2.0-none\n ...\n\n\n\n\n\n\n\nCreate the targets\n\n\nCreate two targets - one for the bootloader and one for the lora app shell application. \n\n\n$ newt target create telee02_boot\n$ newt target set telee02_boot bsp=@apache-mynewt-core/hw/bsp/telee02\n$ newt target set telee02_boot app=@apache-mynewt-core/apps/boot\n$ newt target set telee02_boot build_profile=optimized\n\n$ newt target create lora_app_shell_telee02\n$ newt target set lora_app_shell_telee02 bsp=@apache-mynewt-core/hw/bsp/telee02\n$ newt target set lora_app_shell_telee02 app=@apache-mynewt-core/apps/lora_app_shell\n$ newt target set lora_app_shell_telee02 build_profile=optimized\n\n\n\n\n\nThe lora app shell application requires a few additional system configuration variables. \nCreate and edit a file called syscfg.yml in dev/mylora/targets/lora_app_shell. The file\ncontents should be the following:\n\n\n### Package: targets/lora_app_shell_telee02\n\nsyscfg.vals:\n SHELL_CMD_ARGC_MAX: \n20\n\n LORA_MAC_TIMER_NUM: \n4\n\n TIMER_4: \n1\n\n\n\n\n\n\nYou can now \"display\" the targets you created to make sure they are correct:\n\n\n$ newt target show telee02_boot\ntargets/telee02_boot\n app=@apache-mynewt-core/apps/boot\n bsp=@apache-mynewt-core/hw/bsp/telee02\n build_profile=optimized\n\n$ newt target show lora_app_shell_telee02\ntargets/lora_app_shell_telee02\n app=@apache-mynewt-core/apps/lora_app_shell\n bsp=@apache-mynewt-core/hw/bsp/telee02\n build_profile=optimized\n syscfg=LORA_MAC_TIMER_NUM=4:SHELL_CMD_ARGC_MAX=20:TIMER_4=1\n\n\n\n\n\n\nNote: If you've already built and installed a bootloader for your ee02 module then you do\nnot need to create a target for it here, or build and load it as below. \n\n\n\n\nBuild the target executables\n\n\n$ newt clean telee02_boot\n$ newt clean telee02_boot\nBuilding target targets/telee02_boot\nCompiling repos/apache-mynewt-core/boot/bootutil/src/image_rsa.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/image_ec.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/image_ec256.c \n\n . . .\n\nArchiving telee02_boot-sysinit-app.a\nArchiving util_mem.a\nLinking /Users/wes/dev/wes/bin/targets/telee02_boot/app/apps/boot/boot.elf\nTarget successfully built: targets/telee02_boot\n\n$ newt clean lora_app_shell_telee02\n$ newt build lora_app_shell_telee02\nBuilding target targets/lora_app_shell_telee02\nAssembling repos/apache-mynewt-core/hw/bsp/telee02/src/arch/cortex_m4/gcc_startup_nrf52_split.s\nCompiling repos/apache-mynewt-core/encoding/base64/src/hex.c\nCompiling repos/apache-mynewt-core/encoding/base64/src/base64.c\n . . .\n\n\nArchiving util_mem.a\nArchiving util_parse.a\nLinking /Users/wes/dev/wes/bin/targets/lora_app_shell_telee02/app/apps/lora_app_shell/lora_app_shell.elf\nTarget successfully built: targets/lora_app_shell_telee0\n\n\n\n\n\n\nNote: The newt clean step is not necessary but shown here for good measure. \n\n\n\n\nSign and create the application image\n\n\nYou must sign and version your application image to download it using newt to the board. \nUse the newt create-image command to perform this action. You may assign an arbitrary \nversion (e.g. 1.0.0) to the image.\n\n\n$ newt create-image lora_app_shell_telee02 0.0.0\nApp image succesfully generated: /Users/wes/dev/wes/bin/targets/lora_app_shell_telee02/app/apps/lora_app_shell/lora_app_shell.img\n\n\n\n\n\n\nNote: Only the application image requires this step; the bootloader does not \n\n\n\n\nConnect the board\n\n\nConnect the evaluation board via micro-USB to your PC via USB cable. Connect the Segger J-link debugger to the 9-pin\nSWD connector. Connect the UART pins (RX, TX and GND) to the board. Terminal settings 115200, N, 8, 1.\n\n\n\n\nDownload bootloader and application\n\n\n\n\nNote:\n If you want to erase the flash and load the image again, you can use JLinkExe to issue an \nerase\n command.\n\n\n$ JLinkExe -device nRF52 -speed 4000 -if SWD\nSEGGER J-Link Commander V5.12c (Compiled Apr 21 2016 16:05:51)\nDLL version V5.12c, compiled Apr 21 2016 16:05:45\n\nConnecting to J-Link via USB...O.K.\nFirmware: J-Link OB-SAM3U128-V2-NordicSemi compiled Mar 15 2016 18:03:17\nHardware version: V1.00\nS/N: 682863966\nVTref = 3.300V\n\n\nType \nconnect\n to establish a target connection, \n?\n for help\nJ-Link\nerase\nCortex-M4 identified.\nErasing device (0;?i?)...\nComparing flash [100%] Done.\nErasing flash [100%] Done.\nVerifying flash [100%] Done.\nJ-Link: Flash download: Total time needed: 0.363s (Prepare: 0.093s, Compare: 0.000s, Erase: 0.262s, Program: 0.000s, Verify: 0.000s, Restore: 0.008s)\nErasing done.\nJ-Link\nexit\n$\n\n\n\n\n\n$ newt load telee02_boot\nLoading bootloader\n$ newt load lora_app_shell_telee02\nLoading app image into slot 1\n\n\n\n\n\nAssuming you attached the serial port and have a terminal up you should set the following output on the terminal:\n\n\n000002 lora_app_shell\n\n\n\n\n\n\n\nShell Commands\n\n\nThere are a number of shell commands that will allow you to join and send both unconfirmed and confirmed data. If you type 'help' in your terminal you will see the various commands displayed. Here is a screen shot of the output of help\n\n\n000002 lora_app_shell\nhelp\n\n032766 help\n032766 stat \n032767 tasks \n032768 mpool \n032769 date \n032770 las_wr_mib \n032771 las_rd_mib \n032772 las_rd_dev_eui \n032773 las_wr_dev_eui \n032774 las_rd_app_eui \n032775 las_wr_app_eui \n032776 las_rd_app_key \n032777 las_wr_app_key \n032778 las_app_port \n032779 las_app_tx \n032780 las_join \n032781 las_link_chk \n032782 compat\n \n\n\n\n\n\nThe following table lists the commands and gives a brief description of the commands. The lora commands are described in more detail later in the tutorial as well as their syntax (syntax not shown in the table).\n\n\n\n\n\n\n\n\nCommand\n\n\nDescription\n\n\n\n\n\n\n\n\n\n\nhelp\n\n\nDisplay list of available shell commands\n\n\n\n\n\n\nstat\n\n\nDisplay statistics. Syntax: stat \\\nstatistics group>. 'stat' with no group displays avaialable groups\n\n\n\n\n\n\ntasks\n\n\nDisplay OS tasks\n\n\n\n\n\n\nmpool\n\n\nDisplays OS memory pools and memory pool statistics\n\n\n\n\n\n\ndate\n\n\nDisplays current date/time\n\n\n\n\n\n\nlas_wr_mib\n\n\nWrite lora MIB\n\n\n\n\n\n\nlas_rd_mib\n\n\nRead lora MIB\n\n\n\n\n\n\nlas_rd_dev_eui\n\n\nRead lora device EUI\n\n\n\n\n\n\nlas_wr_dev_eui\n\n\nWrite lora device EUI\n\n\n\n\n\n\nlas_rd_app_eui\n\n\nRead lora application EUI\n\n\n\n\n\n\nlas_wr_app_eui\n\n\nWrite lora application EUI\n\n\n\n\n\n\nlas_rd_app_key\n\n\nRead lora application key\n\n\n\n\n\n\nlas_wr_app_key\n\n\nWrite lora application key\n\n\n\n\n\n\nlas_app_port\n\n\nOpen/close lora application port\n\n\n\n\n\n\nlas_app_tx\n\n\nTransmit on lora application port\n\n\n\n\n\n\nlas_join\n\n\nPerform a lora OTA join\n\n\n\n\n\n\nlas_link_chk\n\n\nPerform a lora link check\n\n\n\n\n\n\n\n\nOTA Join\n\n\nBefore sending any application data a lora end device must be joined to its lora network. To perform a lora OTA (over-the-air) join there are some commands that must be issued prior to attempting to join. The reason for these commands is that a lora end device must be configured with a device EUI, application EUI and application key prior to performing an OTA join.\n\n\n598763 compat\n las_wr_app_eui 0x00:0x11:0x22:0x01:0x01:0x00:0x10:10\n\n623106 compat\n las_wr_app_key 03:03:03:03:03:03:03:03:03:03:03:03:03:03:03:03\n\n623758 compat\n las_wr_dev_eui 0x00:0x11:0x22:0x02:0x02:0x00:0x00:0x00\n\n630333 compat\n las_join 1\n\n630634 Attempting to join...\n019802 compat\n Join cb. status=0 attempts=1\n\n\n\n\n\nIf the join is successful the status returned should be 0. If it fails the status will be a non-zero lora status code (lora status error codes are described later in this tutorial).\n\n\nA note about \"endianness\" in the device EUI commands. The first three bytes of the EUI are the OUI and the last 5 bytes are unique (for that OUI). The above example assumes an OUI of 001122. This is not the same order as the address over the air as device addresses are sent \"least significant byte\" first (little endian). The same convention also applies to keys: they are in big-endian order in the command but sent little endian over the air.\n\n\n\nOpening/closing an application port\n\n\nAnother step that must be performed prior to sending application data is to open an application port. All data frames containing application data are sent to a specific port. Port numbers are in the range 1 - 223 as port 0 is reserved for MLME-related activities. Ports 224-255 are reserved for future standardized application extensions.\n\n\nThe lora app shell does not open any application ports by default.\n\n\nTo open and/or close an application port the following commands are used. Note that the application port which you are using to send data must be open if you want to send data (or receive it).\n\n\n115647 compat\n las_app_port open 1\n\n150958 Opened app port 1\n150958 compat\n las_app_port close 1\n\n151882 Closed app port 1\n\n\n\n\n\n\n\nSending data\n\n\nThe lora app shell allows the user to send both unconfirmed and confirmed data. The command to send data is \nlas_app_tx \\\nport> \\\nlen> \\\ntype>\n\n\nNOTE: the current usage for this command shows an optional data rate and retries for this command. That feature has not been implemented and the command will not be accepted if they are separated.\n\n\nWhere:\n port = port number on which to send\n len = size n bytes of app data\n type = 0 for unconfirmed, 1 for confirmed\n\n\nTo send a confirmed data transmission of size 5 bytes on port 10 the command would be: las_app_tx 10 20 1\n\n\nOnce the end device has sent the frame requested there should be a message which contains some additional information. Here is a screen shot using the above example. Note that there will be some delay between seeing the \"Packet sent on port 10\" message and the additional information as the additional information is the \"confirmation\" that the lora stack provides and the confirmation will not be returned until the lora stack is finished transmitting the frame and has received an acknowledgement or has finished waiting for all the receive windows.\n\n\n449751 compat\n las_app_tx 10 5 1\n\n452144 Packet sent on port 10\n452144 compat\n Txd on port 10 type=conf status=0 len=5\n452325 dr:0\n452325 txpower:5\n452325 tries:1\n452326 ack_rxd:1\n452326 tx_time_on_air:330\n452327 uplink_cntr:0\n452327 uplink_freq:903500000\n\n\n\n\n\nThe information contained in the confirmation is the following:\n\n\ndr: The data rate on which the frame was sent.\n\ntxpower: Transmit power level of the device.\n\ntries: # of attempts made to transmit the frame successfully.\n\nack_rxd: Was an acknowledgement received (0 no 1 yes).\n\ntx_time_on_air: The on-air length of the frame (in milliseconds).\n\nuplink_cntr: The frame uplink counter that this frame used.\n\nuplink_freq: The frequency (logical) on which the frame was sent (in Hz).",
+ "text": "LoRaWAN App\n\n\n\n\nObjective\n\n\nThe purpose of this tutorial is to demonstrate how to build the lora app shell application for either a class A or class C lora device and to perform basic functions such as joining and sending data packets to a lora gateway/server.\n\n\nNOTE: This tutorial presumes that you have a running lora gateway and lora network server. No description of the gateway/server is provided. It is expected that the user understands how to configure and operate the gateway/server so that it can communicate with a class A or class C device.\n\n\n\n\nHardware needed\n\n\n\n\nTelenor EE02 module\n\n\nSegger J-Link or similar debugger\n\n\nLORA gateway\n\n\nLaptop running Mac OS\n\n\nIt is assumed you have already installed newt tool. \n\n\nIt is assumed you understand the basics of the mynewt OS\n\n\n3-wire serial cable to connect telenor module to your laptop\n\n\nSome form of terminal emulation application running on your laptop.\n\n\n\n\n\n\nCreate a project.\n\n\nCreate a new project to hold your work. For a deeper understanding, you can read about project creation in \n\nGet Started -- Creating Your First Project\n\nor just follow the commands below.\n\n\n $ mkdir ~/dev\n $ cd ~/dev\n $ newt new mylora\n Downloading project skeleton from apache/mynewt-blinky...\n Installing skeleton in mylora...\n Project mylora successfully created.\n $ cd mylora\n\n\n\n\n\n\n\nInstall Everything\n\n\nNow that you have defined the needed repositories, it's time to install everything so\nthat you can get started.\n\n\n $ newt install -v \n apache-mynewt-core\n Downloading repository description for apache-mynewt-core... success!\n ...\n apache-mynewt-core successfully installed version 1.2.0-none\n ...\n\n\n\n\n\n\n\nCreate the targets\n\n\nCreate two targets - one for the bootloader and one for the lora app shell application. \n\n\n$ newt target create telee02_boot\n$ newt target set telee02_boot bsp=@apache-mynewt-core/hw/bsp/telee02\n$ newt target set telee02_boot app=@apache-mynewt-core/apps/boot\n$ newt target set telee02_boot build_profile=optimized\n\n$ newt target create lora_app_shell_telee02\n$ newt target set lora_app_shell_telee02 bsp=@apache-mynewt-core/hw/bsp/telee02\n$ newt target set lora_app_shell_telee02 app=@apache-mynewt-core/apps/lora_app_shell\n$ newt target set lora_app_shell_telee02 build_profile=optimized\n\n\n\n\n\nThe lora app shell application requires a few additional system configuration variables. \nCreate and edit a file called syscfg.yml in dev/mylora/targets/lora_app_shell. The file\ncontents should be the following:\n\n\n### Package: targets/lora_app_shell_telee02\n\nsyscfg.vals:\n SHELL_CMD_ARGC_MAX: \n20\n\n LORA_MAC_TIMER_NUM: \n4\n\n TIMER_4: \n1\n\n\n\n\n\n\nYou can now \"display\" the targets you created to make sure they are correct:\n\n\n$ newt target show telee02_boot\ntargets/telee02_boot\n app=@apache-mynewt-core/apps/boot\n bsp=@apache-mynewt-core/hw/bsp/telee02\n build_profile=optimized\n\n$ newt target show lora_app_shell_telee02\ntargets/lora_app_shell_telee02\n app=@apache-mynewt-core/apps/lora_app_shell\n bsp=@apache-mynewt-core/hw/bsp/telee02\n build_profile=optimized\n syscfg=LORA_MAC_TIMER_NUM=4:SHELL_CMD_ARGC_MAX=20:TIMER_4=1\n\n\n\n\n\n\nNote: If you've already built and installed a bootloader for your ee02 module then you do\nnot need to create a target for it here, or build and load it as below. \n\n\n\n\nBuild the target executables\n\n\n$ newt clean telee02_boot\n$ newt build telee02_boot\nBuilding target targets/telee02_boot\nCompiling repos/apache-mynewt-core/boot/bootutil/src/image_rsa.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/image_ec.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/image_ec256.c \n\n . . .\n\nArchiving telee02_boot-sysinit-app.a\nArchiving util_mem.a\nLinking /Users/wes/dev/wes/bin/targets/telee02_boot/app/apps/boot/boot.elf\nTarget successfully built: targets/telee02_boot\n\n$ newt clean lora_app_shell_telee02\n$ newt build lora_app_shell_telee02\nBuilding target targets/lora_app_shell_telee02\nAssembling repos/apache-mynewt-core/hw/bsp/telee02/src/arch/cortex_m4/gcc_startup_nrf52_split.s\nCompiling repos/apache-mynewt-core/encoding/base64/src/hex.c\nCompiling repos/apache-mynewt-core/encoding/base64/src/base64.c\n . . .\n\n\nArchiving util_mem.a\nArchiving util_parse.a\nLinking /Users/wes/dev/wes/bin/targets/lora_app_shell_telee02/app/apps/lora_app_shell/lora_app_shell.elf\nTarget successfully built: targets/lora_app_shell_telee0\n\n\n\n\n\n\nNote: The newt clean step is not necessary but shown here for good measure. \n\n\n\n\nSign and create the application image\n\n\nYou must sign and version your application image to download it using newt to the board. \nUse the newt create-image command to perform this action. You may assign an arbitrary \nversion (e.g. 1.0.0) to the image.\n\n\n$ newt create-image lora_app_shell_telee02 0.0.0\nApp image succesfully generated: /Users/wes/dev/wes/bin/targets/lora_app_shell_telee02/app/apps/lora_app_shell/lora_app_shell.img\n\n\n\n\n\n\nNote: Only the application image requires this step; the bootloader does not \n\n\n\n\nConnect the board\n\n\nConnect the evaluation board via micro-USB to your PC via USB cable. Connect the Segger J-link debugger to the 9-pin\nSWD connector. Connect the UART pins (RX, TX and GND) to the board. Terminal settings 115200, N, 8, 1.\n\n\n\n\nDownload bootloader and application\n\n\n\n\nNote:\n If you want to erase the flash and load the image again, you can use JLinkExe to issue an \nerase\n command.\n\n\n$ JLinkExe -device nRF52 -speed 4000 -if SWD\nSEGGER J-Link Commander V5.12c (Compiled Apr 21 2016 16:05:51)\nDLL version V5.12c, compiled Apr 21 2016 16:05:45\n\nConnecting to J-Link via USB...O.K.\nFirmware: J-Link OB-SAM3U128-V2-NordicSemi compiled Mar 15 2016 18:03:17\nHardware version: V1.00\nS/N: 682863966\nVTref = 3.300V\n\n\nType \nconnect\n to establish a target connection, \n?\n for help\nJ-Link\nerase\nCortex-M4 identified.\nErasing device (0;?i?)...\nComparing flash [100%] Done.\nErasing flash [100%] Done.\nVerifying flash [100%] Done.\nJ-Link: Flash download: Total time needed: 0.363s (Prepare: 0.093s, Compare: 0.000s, Erase: 0.262s, Program: 0.000s, Verify: 0.000s, Restore: 0.008s)\nErasing done.\nJ-Link\nexit\n$\n\n\n\n\n\n$ newt load telee02_boot\nLoading bootloader\n$ newt load lora_app_shell_telee02\nLoading app image into slot 1\n\n\n\n\n\nAssuming you attached the serial port and have a terminal up you should set the following output on the terminal:\n\n\n000002 lora_app_shell\n\n\n\n\n\n\n\nShell Commands\n\n\nThere are a number of shell commands that will allow you to join and send both unconfirmed and confirmed data. If you type 'help' in your terminal you will see the various commands displayed. Here is a screen shot of the output of help\n\n\n000002 lora_app_shell\nhelp\n\n032766 help\n032766 stat \n032767 tasks \n032768 mpool \n032769 date \n032770 las_wr_mib \n032771 las_rd_mib \n032772 las_rd_dev_eui \n032773 las_wr_dev_eui \n032774 las_rd_app_eui \n032775 las_wr_app_eui \n032776 las_rd_app_key \n032777 las_wr_app_key \n032778 las_app_port \n032779 las_app_tx \n032780 las_join \n032781 las_link_chk \n032782 compat\n \n\n\n\n\n\nThe following table lists the commands and gives a brief description of the commands. The lora commands are described in more detail later in the tutorial as well as their syntax (syntax not shown in the table).\n\n\n\n\n\n\n\n\nCommand\n\n\nDescription\n\n\n\n\n\n\n\n\n\n\nhelp\n\n\nDisplay list of available shell commands\n\n\n\n\n\n\nstat\n\n\nDisplay statistics. Syntax: stat \\\nstatistics group>. 'stat' with no group displays avaialable groups\n\n\n\n\n\n\ntasks\n\n\nDisplay OS tasks\n\n\n\n\n\n\nmpool\n\n\nDisplays OS memory pools and memory pool statistics\n\n\n\n\n\n\ndate\n\n\nDisplays current date/time\n\n\n\n\n\n\nlas_wr_mib\n\n\nWrite lora MIB\n\n\n\n\n\n\nlas_rd_mib\n\n\nRead lora MIB\n\n\n\n\n\n\nlas_rd_dev_eui\n\n\nRead lora device EUI\n\n\n\n\n\n\nlas_wr_dev_eui\n\n\nWrite lora device EUI\n\n\n\n\n\n\nlas_rd_app_eui\n\n\nRead lora application EUI\n\n\n\n\n\n\nlas_wr_app_eui\n\n\nWrite lora application EUI\n\n\n\n\n\n\nlas_rd_app_key\n\n\nRead lora application key\n\n\n\n\n\n\nlas_wr_app_key\n\n\nWrite lora application key\n\n\n\n\n\n\nlas_app_port\n\n\nOpen/close lora application port\n\n\n\n\n\n\nlas_app_tx\n\n\nTransmit on lora application port\n\n\n\n\n\n\nlas_join\n\n\nPerform a lora OTA join\n\n\n\n\n\n\nlas_link_chk\n\n\nPerform a lora link check\n\n\n\n\n\n\n\n\nOTA Join\n\n\nBefore sending any application data a lora end device must be joined to its lora network. To perform a lora OTA (over-the-air) join there are some commands that must be issued prior to attempting to join. The reason for these commands is that a lora end device must be configured with a device EUI, application EUI and application key prior to performing an OTA join.\n\n\n598763 compat\n las_wr_app_eui 0x00:0x11:0x22:0x01:0x01:0x00:0x10:10\n\n623106 compat\n las_wr_app_key 03:03:03:03:03:03:03:03:03:03:03:03:03:03:03:03\n\n623758 compat\n las_wr_dev_eui 0x00:0x11:0x22:0x02:0x02:0x00:0x00:0x00\n\n630333 compat\n las_join 1\n\n630634 Attempting to join...\n019802 compat\n Join cb. status=0 attempts=1\n\n\n\n\n\nIf the join is successful the status returned should be 0. If it fails the status will be a non-zero lora status code (lora status error codes are described later in this tutorial).\n\n\nA note about \"endianness\" in the device EUI commands. The first three bytes of the EUI are the OUI and the last 5 bytes are unique (for that OUI). The above example assumes an OUI of 001122. This is not the same order as the address over the air as device addresses are sent \"least significant byte\" first (little endian). The same convention also applies to keys: they are in big-endian order in the command but sent little endian over the air.\n\n\n\nOpening/closing an application port\n\n\nAnother step that must be performed prior to sending application data is to open an application port. All data frames containing application data are sent to a specific port. Port numbers are in the range 1 - 223 as port 0 is reserved for MLME-related activities. Ports 224-255 are reserved for future standardized application extensions.\n\n\nThe lora app shell does not open any application ports by default.\n\n\nTo open and/or close an application port the following commands are used. Note that the application port which you are using to send data must be open if you want to send data (or receive it).\n\n\n115647 compat\n las_app_port open 1\n\n150958 Opened app port 1\n150958 compat\n las_app_port close 1\n\n151882 Closed app port 1\n\n\n\n\n\n\n\nSending data\n\n\nThe lora app shell allows the user to send both unconfirmed and confirmed data. The command to send data is \nlas_app_tx \\\nport> \\\nlen> \\\ntype>\n\n\nNOTE: the current usage for this command shows an optional data rate and retries for this command. That feature has not been implemented and the command will not be accepted if they are separated.\n\n\nWhere:\n port = port number on which to send\n len = size n bytes of app data\n type = 0 for unconfirmed, 1 for confirmed\n\n\nTo send a confirmed data transmission of size 5 bytes on port 10 the command would be: las_app_tx 10 20 1\n\n\nOnce the end device has sent the frame requested there should be a message which contains some additional information. Here is a screen shot using the above example. Note that there will be some delay between seeing the \"Packet sent on port 10\" message and the additional information as the additional information is the \"confirmation\" that the lora stack provides and the confirmation will not be returned until the lora stack is finished transmitting the frame and has received an acknowledgement or has finished waiting for all the receive windows.\n\n\n449751 compat\n las_app_tx 10 5 1\n\n452144 Packet sent on port 10\n452144 compat\n Txd on port 10 type=conf status=0 len=5\n452325 dr:0\n452325 txpower:5\n452325 tries:1\n452326 ack_rxd:1\n452326 tx_time_on_air:330\n452327 uplink_cntr:0\n452327 uplink_freq:903500000\n\n\n\n\n\nThe information contained in the confirmation is the following:\n\n\ndr: The data rate on which the frame was sent.\n\ntxpower: Transmit power level of the device.\n\ntries: # of attempts made to transmit the frame successfully.\n\nack_rxd: Was an acknowledgement received (0 no 1 yes).\n\ntx_time_on_air: The on-air length of the frame (in milliseconds).\n\nuplink_cntr: The frame uplink counter that this frame used.\n\nuplink_freq: The frequency (logical) on which the frame was sent (in Hz).",
"title": "LoraWAN app"
},
{
@@ -1627,7 +1627,7 @@
},
{
"location": "/os/tutorials/lora/lorawanapp/#build-the-target-executables",
- "text": "$ newt clean telee02_boot\n$ newt clean telee02_boot\nBuilding target targets/telee02_boot\nCompiling repos/apache-mynewt-core/boot/bootutil/src/image_rsa.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/image_ec.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/image_ec256.c \n\n . . .\n\nArchiving telee02_boot-sysinit-app.a\nArchiving util_mem.a\nLinking /Users/wes/dev/wes/bin/targets/telee02_boot/app/apps/boot/boot.elf\nTarget successfully built: targets/telee02_boot\n\n$ newt clean lora_app_shell_telee02\n$ newt build lora_app_shell_telee02\nBuilding target targets/lora_app_shell_telee02\nAssembling repos/apache-mynewt-core/hw/bsp/telee02/src/arch/cortex_m4/gcc_startup_nrf52_split.s\nCompiling repos/apache-mynewt-core/encoding/base64/src/hex.c\nCompiling repos/apache-mynewt-core/encoding/base64/src/base64.c\n . . .\n\n\nArchiving util_mem.a\nArchiving util_parse.a\nLinking /Users/wes/dev/wes/bin/targets/lora_app_shell_telee02/app/apps/lora_app_shell/lora_app_shell.elf\nTarget successfully built: targets/lora_app_shell_telee0 \nNote: The newt clean step is not necessary but shown here for good measure.",
+ "text": "$ newt clean telee02_boot\n$ newt build telee02_boot\nBuilding target targets/telee02_boot\nCompiling repos/apache-mynewt-core/boot/bootutil/src/image_rsa.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/image_ec.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/image_ec256.c \n\n . . .\n\nArchiving telee02_boot-sysinit-app.a\nArchiving util_mem.a\nLinking /Users/wes/dev/wes/bin/targets/telee02_boot/app/apps/boot/boot.elf\nTarget successfully built: targets/telee02_boot\n\n$ newt clean lora_app_shell_telee02\n$ newt build lora_app_shell_telee02\nBuilding target targets/lora_app_shell_telee02\nAssembling repos/apache-mynewt-core/hw/bsp/telee02/src/arch/cortex_m4/gcc_startup_nrf52_split.s\nCompiling repos/apache-mynewt-core/encoding/base64/src/hex.c\nCompiling repos/apache-mynewt-core/encoding/base64/src/base64.c\n . . .\n\n\nArchiving util_mem.a\nArchiving util_parse.a\nLinking /Users/wes/dev/wes/bin/targets/lora_app_shell_telee02/app/apps/lora_app_shell/lora_app_shell.elf\nTarget successfully built: targets/lora_app_shell_telee0 \nNote: The newt clean step is not necessary but shown here for good measure.",
"title": "Build the target executables"
},
{
@@ -13292,12 +13292,12 @@
},
{
"location": "/newtmgr/install_mac/",
- "text": "Installing Newtmgr on Mac OS\n\n\nNewtmgr is supported on Mac OS X 64 bit platforms and has been tested on Mac OS 10.11 and higher.\n\n\nThis page shows you how to install the following versions of newtmgr:\n\n\n\n\nUpgrade to or install the latest release version (1.2.0).\n\n\nInstall the latest from the master branch (unstable).\n\n\n\n\nSee \nInstalling Previous Releases of Newtmgr\n to install an earlier version of newtmgr.\n\n\nNote:\n If you would like to contribute to the newtmgr tool, see \nSetting Up Go Environment to Contribute to Newt and Newtmgr Tools\n.\n\n\nAdding the Mynewt Homebrew Tap\n\n\nYou should have added the \nruntimeco/homebrew-mynewt\n tap when you installed the \nnewt\n tool. Run the following commands if you have not done so:\n\n\n$ brew tap runtimeco/homebrew-mynewt\n$ brew update\n\n\n\n\n\nUpgrading to or Installing the Latest Release Version\n\n\nPerform the following to upgrade or install the latest release version of newtmgr.\n\n\nUpgrading to the Latest Release Version of Newtmgr\n\n\nIf you have installed an earlier version of newtmgr using brew, run the following commands to upgrade to the latest version of newtmgr:\n\n\n$ brew update\n$ brew upgrade mynewt-newtmgr\n\n\n\n\n\n\n\nInstalling the Latest Release Version of Newtmgr\n\n\nRun the following command to install the latest release version of newtmgr:\n\n\n$ brew update\n$ brew install mynewt-newtmgr\n==\n Installing mynewt-newtmgr from runtimeco/mynewt\n==\n Downloading https://github.com/runtimeco/binary-releases/raw/master/mynewt-newt-tools_1.2.0/mynewt-newtmgr-1.2.0.sierra.bottle.tar.gz\n==\n Downloading from https://raw.githubusercontent.com/runtimeco/binary-releases/master/mynewt-newt-tools_1.2.0/mynewt-newtmgr-1.2.0.sierra.bottle.tar.gz\n######################################################################## 100.0%\n==\n Pouring mynewt-newtmgr-1.2.0.sierra.bottle.tar.gz\n\ud83c\udf7a /usr/local/Cellar/mynewt-newtmgr/1.2.0: 3 files, 17.3MB\n\n\n\n\n\n\n\nNotes:\n Homebrew bottles for newtmgr 1.2.0 are available for Mac OS Sierra, El Captian. If you are running an earlier version of Mac OS, the installation will install the latest version of Go and compile newtmgr locally.\n\n\n\n\nChecking the Installed Version\n\n\nCheck that you are using the installed version of newtmgr:\n\n\n$which newtmgr\n/usr/local/bin/newtmgr\nls -l /usr/local/bin/newtmgr\nlrwxr-xr-x 1 user staff 42 Sep 11 21:15 /usr/local/bin/newtmgr -\n ../Cellar/mynewt-newtmgr/1.2.0/bin/newtmgr\n\n\n\n\n\nNote:\n If you previously built newtmgr from source and the output of \nwhich newtmgr\n shows \"$GOPATH/bin/newtmgr\", you will need to move \"$GOPATH/bin\" after \"/usr/local/bin\" for your PATH in ~/.bash_profile, and source ~/.bash_profile.\n\n\n\nGet information about newtmgr:\n\n\n$ newtmgr help\nUsage:\n newtmgr [flags]\n newtmgr [command]\n\nAvailable Commands:\n config Read or write a config value on a device\n conn Manage newtmgr connection profiles\n crash Send a crash command to a device\n datetime Manage datetime on a device\n echo Send data to a device and display the echoed back data\n fs Access files on a device\n help Help about any command\n image Manage images on a device\n log Manage logs on a device\n mpstat Read mempool statistics from a device\n reset Perform a soft reset of a device\n run Run test procedures on a device\n stat Read statistics from a device\n taskstat Read task statistics from a device\n\nFlags:\n -c, --conn string connection profile to use\n -h, --help help for newtmgr\n -l, --loglevel string log level to use (default \ninfo\n)\n --name string name of target BLE device; overrides profile setting\n -t, --timeout float timeout in seconds (partial seconds allowed) (default 10)\n -r, --tries int total number of tries in case of timeout (default 1)\n\nUse \nnewtmgr [command] --help\n for more information about a command.\n\n\n\n\n\n\n\nInstalling Newtmgr from the Master Branch\n\n\nWe recommend that you use the latest release version of newtmgr. If you would like to use the master branch with the latest updates, you can install newtmgr from the HEAD of the master branch. \n\n\n Notes: \n\n\n\n\nThe master branch may be unstable.\n\n\nThis installation will install the latest version of Go on your computer, if it is not installed, and compile newtmgr locally. \n\n\n\n\n\nIf you already installed newtgmr, unlink the current version:\n\n\n$brew unlink mynewt-newtmgr\n\n\n\n\n\n\nInstall the latest unstable version of newtmgr from the master branch:\n\n\n$brew install mynewt-newtmgr --HEAD\n==\n Installing mynewt-newtmgr from runtimeco/mynewt\n==\n Cloning https://github.com/apache/mynewt-newtmgr.git\nCloning into \n/Users/wanda/Library/Caches/Homebrew/mynewt-newtmgr--git\n...\nremote: Counting objects: 2169, done.\nremote: Compressing objects: 100% (1752/1752), done.\nremote: Total 2169 (delta 379), reused 2042 (delta 342), pack-reused 0\nReceiving objects: 100% (2169/2169), 8.13 MiB | 5.47 MiB/s, done.\nResolving deltas: 100% (379/379), done.\n==\n Checking out branch master\n==\n go get github.com/currantlabs/ble\n==\n go get github.com/raff/goble\n==\n go get github.com/mgutz/logxi/v1\n==\n go install\n\ud83c\udf7a /usr/local/Cellar/mynewt-newtmgr/HEAD-2d5217f: 3 files, 17.3MB, built in 1 minute 10 seconds\n\n\n\n\n\n\nTo switch back to the latest stable release version of newtmgr, you can run:\n\n\n$brew switch mynewt-newtmgr 1.2.0\nCleaning /usr/local/Cellar/mynewt-newtmgr/1.2.0\nCleaning /usr/local/Cellar/mynewt-newtmgr/HEAD-2d5217f\n1 links created for /usr/local/Cellar/mynewt-newtmgr/1.2.0",
+ "text": "Installing Newtmgr on Mac OS\n\n\nNewtmgr is supported on Mac OS X 64 bit platforms and has been tested on Mac OS Sierra.\n\n\nThis page shows you how to install the following versions of newtmgr:\n\n\n\n\nUpgrade to or install the latest release version (1.2.0).\n\n\nInstall the latest from the master branch (unstable).\n\n\n\n\nSee \nInstalling Previous Releases of Newtmgr\n to install an earlier version of newtmgr.\n\n\nNote:\n If you would like to contribute to the newtmgr tool, see \nSetting Up Go Environment to Contribute to Newt and Newtmgr Tools\n.\n\n\nAdding the Mynewt Homebrew Tap\n\n\nYou should have added the \nruntimeco/homebrew-mynewt\n tap when you installed the \nnewt\n tool. Run the following commands if you have not done so:\n\n\n$ brew tap runtimeco/homebrew-mynewt\n$ brew update\n\n\n\n\n\nUpgrading to or Installing the Latest Release Version\n\n\nPerform the following to upgrade or install the latest release version of newtmgr.\n\n\nUpgrading to the Latest Release Version of Newtmgr\n\n\nIf you have installed an earlier version of newtmgr using brew, run the following commands to upgrade to the latest version of newtmgr:\n\n\n$ brew update\n$ brew upgrade mynewt-newtmgr\n\n\n\n\n\n\n\nInstalling the Latest Release Version of Newtmgr\n\n\nRun the following command to install the latest release version of newtmgr:\n\n\n$ brew update\n$ brew install mynewt-newtmgr\n\n\n\n\n\n\n\nNotes:\n Homebrew bottles for newtmgr 1.2.0 are available for Mac OS Sierra. If you are running an earlier version of Mac OS, the installation will install the latest version of Go and compile newtmgr locally.\n\n\n\n\nChecking the Installed Version\n\n\nCheck that you are using the installed version of newtmgr:\n\n\n$which newtmgr\n/usr/local/bin/newtmgr\n\n\n\n\n\nNote:\n If you previously built newtmgr from source and the output of \nwhich newtmgr\n shows \"$GOPATH/bin/newtmgr\", you will need to move \"$GOPATH/bin\" after \"/usr/local/bin\" for your PATH in ~/.bash_profile, and source ~/.bash_profile.\n\n\n\nGet information about newtmgr:\n\n\n$ newtmgr help\nUsage:\n newtmgr [flags]\n newtmgr [command]\n\nAvailable Commands:\n config Read or write a config value on a device\n conn Manage newtmgr connection profiles\n crash Send a crash command to a device\n datetime Manage datetime on a device\n echo Send data to a device and display the echoed back data\n fs Access files on a device\n help Help about any command\n image Manage images on a device\n log Manage logs on a device\n mpstat Read mempool statistics from a device\n reset Perform a soft reset of a device\n run Run test procedures on a device\n stat Read statistics from a device\n taskstat Read task statistics from a device\n\nFlags:\n -c, --conn string connection profile to use\n -h, --help help for newtmgr\n -l, --loglevel string log level to use (default \ninfo\n)\n --name string name of target BLE device; overrides profile setting\n -t, --timeout float timeout in seconds (partial seconds allowed) (default 10)\n -r, --tries int total number of tries in case of timeout (default 1)\n\nUse \nnewtmgr [command] --help\n for more information about a command.\n\n\n\n\n\n\n\nInstalling Newtmgr from the Master Branch\n\n\nWe recommend that you use the latest release version of newtmgr. If you would like to use the master branch with the latest updates, you can install newtmgr from the HEAD of the master branch. \n\n\n Notes: \n\n\n\n\nThe master branch may be unstable.\n\n\nThis installation will install the latest version of Go on your computer, if it is not installed, and compile newtmgr locally. \n\n\n\n\n\nIf you already installed newtgmr, unlink the current version:\n\n\n$brew unlink mynewt-newtmgr\n\n\n\n\n\n\nInstall the latest unstable version of newtmgr from the master branch:\n\n\n$brew install mynewt-newtmgr --HEAD\n\n\n\n\n\n\nTo switch back to the latest stable release version of newtmgr, you can run:\n\n\n$brew switch mynewt-newtmgr 1.2.0",
"title": "Install Newtmgr On Mac OS"
},
{
"location": "/newtmgr/install_mac/#installing-newtmgr-on-mac-os",
- "text": "Newtmgr is supported on Mac OS X 64 bit platforms and has been tested on Mac OS 10.11 and higher. This page shows you how to install the following versions of newtmgr: Upgrade to or install the latest release version (1.2.0). Install the latest from the master branch (unstable). See Installing Previous Releases of Newtmgr to install an earlier version of newtmgr. Note: If you would like to contribute to the newtmgr tool, see Setting Up Go Environment to Contribute to Newt and Newtmgr Tools .",
+ "text": "Newtmgr is supported on Mac OS X 64 bit platforms and has been tested on Mac OS Sierra. This page shows you how to install the following versions of newtmgr: Upgrade to or install the latest release version (1.2.0). Install the latest from the master branch (unstable). See Installing Previous Releases of Newtmgr to install an earlier version of newtmgr. Note: If you would like to contribute to the newtmgr tool, see Setting Up Go Environment to Contribute to Newt and Newtmgr Tools .",
"title": "Installing Newtmgr on Mac OS"
},
{
@@ -13317,22 +13317,22 @@
},
{
"location": "/newtmgr/install_mac/#installing-the-latest-release-version-of-newtmgr",
- "text": "Run the following command to install the latest release version of newtmgr: $ brew update\n$ brew install mynewt-newtmgr\n== Installing mynewt-newtmgr from runtimeco/mynewt\n== Downloading https://github.com/runtimeco/binary-releases/raw/master/mynewt-newt-tools_1.2.0/mynewt-newtmgr-1.2.0.sierra.bottle.tar.gz\n== Downloading from https://raw.githubusercontent.com/runtimeco/binary-releases/master/mynewt-newt-tools_1.2.0/mynewt-newtmgr-1.2.0.sierra.bottle.tar.gz\n######################################################################## 100.0%\n== Pouring mynewt-newtmgr-1.2.0.sierra.bottle.tar.gz\n\ud83c\udf7a /usr/local/Cellar/mynewt-newtmgr/1.2.0: 3 files, 17.3MB Notes: Homebrew bottles for newtmgr 1.2.0 are available for Mac OS Sierra, El Captian. If you are running an earlier version of Mac OS, the installation will install the latest version of Go and compile newtmgr locally.",
+ "text": "Run the following command to install the latest release version of newtmgr: $ brew update\n$ brew install mynewt-newtmgr Notes: Homebrew bottles for newtmgr 1.2.0 are available for Mac OS Sierra. If you are running an earlier version of Mac OS, the installation will install the latest version of Go and compile newtmgr locally.",
"title": "Installing the Latest Release Version of Newtmgr"
},
{
"location": "/newtmgr/install_mac/#checking-the-installed-version",
- "text": "Check that you are using the installed version of newtmgr: $which newtmgr\n/usr/local/bin/newtmgr\nls -l /usr/local/bin/newtmgr\nlrwxr-xr-x 1 user staff 42 Sep 11 21:15 /usr/local/bin/newtmgr - ../Cellar/mynewt-newtmgr/1.2.0/bin/newtmgr Note: If you previously built newtmgr from source and the output of which newtmgr shows \"$GOPATH/bin/newtmgr\", you will need to move \"$GOPATH/bin\" after \"/usr/local/bin\" for your PATH in ~/.bash_profile, and source ~/.bash_profile. \nGet information about newtmgr: $ newtmgr help\nUsage:\n newtmgr [flags]\n newtmgr [command]\n\nAvailable Commands:\n config Read or write a config value on a device\n conn Manage newtmgr connection profiles\n crash Send a crash command to a device\n datetime Manage datetime on a device\n echo Send data to a device and display the echoed back data\n fs Access files on a device\n help Help about any command\n image Manage images on a device\n log Manage logs on a device\n mpstat Read mempool statistics from a device\n reset Perform a soft reset of a device\n run Run test procedures on a device\n stat Read statistics from a device\n taskstat Read task statistics from a device\n\nFlags:\n -c, --conn string connection profile to use\n -h, --help help for newtmgr\n -l, --loglevel string log level to use (default info )\n --name string name of target BLE device; overrides profile setting\n -t, --timeout float timeout in seconds (partial seconds allowed) (default 10)\n -r, --tries int total number of tries in case of timeout (default 1)\n\nUse newtmgr [command] --help for more information about a command.",
+ "text": "Check that you are using the installed version of newtmgr: $which newtmgr\n/usr/local/bin/newtmgr Note: If you previously built newtmgr from source and the output of which newtmgr shows \"$GOPATH/bin/newtmgr\", you will need to move \"$GOPATH/bin\" after \"/usr/local/bin\" for your PATH in ~/.bash_profile, and source ~/.bash_profile. \nGet information about newtmgr: $ newtmgr help\nUsage:\n newtmgr [flags]\n newtmgr [command]\n\nAvailable Commands:\n config Read or write a config value on a device\n conn Manage newtmgr connection profiles\n crash Send a crash command to a device\n datetime Manage datetime on a device\n echo Send data to a device and display the echoed back data\n fs Access files on a device\n help Help about any command\n image Manage images on a device\n log Manage logs on a device\n mpstat Read mempool statistics from a device\n reset Perform a soft reset of a device\n run Run test procedures on a device\n stat Read statistics from a device\n taskstat Read task statistics from a device\n\nFlags:\n -c, --conn string connection profile to use\n -h, --help help for newtmgr\n -l, --loglevel string log level to use (default info )\n --name string name of target BLE device; overrides profile setting\n -t, --timeout float timeout in seconds (partial seconds allowed) (default 10)\n -r, --tries int total number of tries in case of timeout (default 1)\n\nUse newtmgr [command] --help for more information about a command.",
"title": "Checking the Installed Version"
},
{
"location": "/newtmgr/install_mac/#installing-newtmgr-from-the-master-branch",
- "text": "We recommend that you use the latest release version of newtmgr. If you would like to use the master branch with the latest updates, you can install newtmgr from the HEAD of the master branch. Notes: The master branch may be unstable. This installation will install the latest version of Go on your computer, if it is not installed, and compile newtmgr locally. \nIf you already installed newtgmr, unlink the current version: $brew unlink mynewt-newtmgr \nInstall the latest unstable version of newtmgr from the master branch: $brew install mynewt-newtmgr --HEAD\n== Installing mynewt-newtmgr from runtimeco/mynewt\n== Cloning https://github.com/apache/mynewt-newtmgr.git\nCloning into /Users/wanda/Library/Caches/Homebrew/mynewt-newtmgr--git ...\nremote: Counting objects: 2169, done.\nremote: Compressing objects: 100% (1752/1752), done.\nremote: Total 2169 (delta 379), reused 2042 (delta 342), pack-reused 0\nReceiving objects: 100% (2169/2169), 8.13 MiB | 5.47 MiB/s, done.\nResolving deltas: 100% (379/379), done.\n== Checking out branch master\n== go get github.com/currantlabs/ble\n== go get github.com/raff/goble\n== go get github.com/mgutz/logxi/v1\n== go install\n\ud83c\udf7a /usr/local/Cellar/mynewt-newtmgr/HEAD-2d5217f: 3 files, 17.3MB, built in 1 minute 10 seconds \nTo switch back to the latest stable release version of newtmgr, you can run: $brew switch mynewt-newtmgr 1.2.0\nCleaning /usr/local/Cellar/mynewt-newtmgr/1.2.0\nCleaning /usr/local/Cellar/mynewt-newtmgr/HEAD-2d5217f\n1 links created for /usr/local/Cellar/mynewt-newtmgr/1.2.0",
+ "text": "We recommend that you use the latest release version of newtmgr. If you would like to use the master branch with the latest updates, you can install newtmgr from the HEAD of the master branch. Notes: The master branch may be unstable. This installation will install the latest version of Go on your computer, if it is not installed, and compile newtmgr locally. \nIf you already installed newtgmr, unlink the current version: $brew unlink mynewt-newtmgr \nInstall the latest unstable version of newtmgr from the master branch: $brew install mynewt-newtmgr --HEAD \nTo switch back to the latest stable release version of newtmgr, you can run: $brew switch mynewt-newtmgr 1.2.0",
"title": "Installing Newtmgr from the Master Branch"
},
{
"location": "/newtmgr/install_linux/",
- "text": "Installing Newtmgr on Linux\n\n\nYou can install the latest release (1.2.0) of the newtmgr tool from a Debian binary package (amd64). You can also download and build the latest release version of newtmgr from source. \n\n\nThis page shows you how to: \n\n\n\n\n\n\nSet up your computer to download Debian binary packages from the runtimeco APT repository.\n\n\nNote:\n The key for signing the repository has changed. If you set up your computer before release 1.1.0, you will need to download and import the public key again. \n\n\n\n\n\n\nInstall the latest release version of newtmgr from a Debian binary package. You can use apt-get to install the package or manually download and install the Debian binary package.\n\n\n\n\n\n\nDownload, build, and install the latest release version of newtmgr from source. \n\n\n\n\n\n\nSee \nInstalling Previous Releases of Newtgmr\n to install an earlier version of newtmgr.\n\n\nIf you are installing on an amd64 platform, we recommend that you install from the binary package.\n\n\nNote:\n We have tested the newtmgr tool binary and apt-get install from the runtimeco APT repository for Ubuntu version 16. Earlier Ubuntu versions (for example: Ubuntu 14) may have incompatibility with the repository. You can manually download and install the Debian binary package.\n\n\nNote:\n See \nSetting Up a Go Environment to Contribute to Newt and Newtmgr Tools\n if you want to: \n\n\n\n\nUse the newtmgr tool with the latest updates from the master branch. The master branch may be unstable and we recommend that you use the latest stable release version.\n\n\nContribute to the newtmgr tool. \n\n\n\n\n\n\nSetting Up Your Computer to use apt-get to Install the Package\n\n\nThe newtmgr Debian packages are stored in a private APT repository on \nhttps://github/runtimeco/debian-mynewt\n. To use apt-get, you must set up the following on your computer to retrieve packages from the repository:\n\n\nNote\n: You only need to perform this setup once on your computer. However, if you previously downloaded and imported the public key for the runtimeco APT repository, you will need to perform step 2 again as the key has changed.\n\n\n\n\nInstall the \napt-transport-https\n package to use HTTPS to retrieve packages. \n\n\nDownload the public key for the runtimeco APT repository and import the key into the apt keychain.\n\n\nAdd the repository for the binary and source packages to the apt source list.\n\n\n\n\n\n1. Install the apt-transport-https package:\n\n\n$sudo apt-get update\n$sudo apt-get install apt-transport-https\n\n\n\n\n\n\n2. Download the public key for the runtimeco apt repo (\nNote:\n There is a \n-\n after \napt-key add\n):\n\n\nwget -qO - https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/mynewt.gpg.key | sudo apt-key add -\n\n\n\n\n\n\n3. Add the repository for the binary packages to the \nmynewt.list\n apt source list file.\n\n\n$sudo -s\n[sudo] password for \nuser\n:\nroot$ cat \n /etc/apt/sources.list.d/mynewt.list \nEOF\ndeb https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest main\nEOF\nroot$exit\n\n\n\n\n\nNote:\n Do not forget to exit the root shell.\n\n\n\n4. Verify the content of the source list file:\n\n\n$more /etc/apt/sources.list.d/mynewt.list\ndeb https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest main\n\n\n\n\n\n\n5. Update the available packages:\n\n\n$sudo apt-get update\n\n\n\n\n\n\n\nNote:\n If you are not using Ubuntu version 16, you may see the following errors. We have provided instructions on how to manually download and install the binary package.\n\n\nW: Failed to fetch https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/dists/latest/main/source/Sources Ht\ntpError404\n\n\n\n\n\n \n\n\nInstalling the Latest Release of Newtmgr from a Binary Package\n\n\nYou can use either apt-get to install the package, or manually download and install the Debian binary package. \n\n\n\n\nMethod 1: Using apt-get to Upgrade or to Install\n\n\nRun the following commands to upgrade or install the latest version of newtmgr:\n\n\n$ sudo apt-get update \n$ sudo apt-get install newtmgr\n\n\n\n\n\nMethod 2: Downloading and Installing the Debian Package Manually\n\n\nDownload and install the package manually.\n\n\n$wget https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/pool/main/n/newtmgr/newtmgr_1.2.0-1_amd64.deb\n$sudo dpkg -i newtmgr_1.2.0-1_amd64.deb\n\n\n\n\n\nSee \nChecking the Installed Version of Newtmgr\n to verify that you are using the installed version of newtmgr.\n\n\n\n\nInstalling the Latest Release Version of Newtmgr from Source\n\n\nIf you are running Linux on a different architecture, you can build and install the latest release version of newtmgr from source.\n\n\n\n1. Download and install the latest version of \nGo\n. Newtmgr requires Go version 1.7.6 or higher.\n\n\n\n2. Create a Go workspace in the /tmp directory: \n\n\n$ cd /tmp\n$ mkdir go\n$ cd go\n$ export GOPATH=/tmp/go\n\n\n\n\n\n\n3. Run \ngo get\n to download the newtmgr source. Note that \ngo get\n pulls down the HEAD from the master branch in git, builds, and installs newtmgr.\n\n\n$ go get mynewt.apache.org/newtmgr/newtmgr\n$ ls -l /tmp/go/bin/newtmgr\n-rwxr-xr-x 1 user staff 17884488 Jul 29 16:25 /tmp/go/bin/newtmgr\n\n\n\n\n\n\n4. Check out the source from the latest release version:\n\n\n$ cd src/mynewt.apache.org/newtmgr\n$ git checkout mynewt_1_2_0_tag\nNote: checking out \nmynewt_1_2_0_tag\n.\n\n\n\n\n\n 5. Build newtmgr from the latest release version: \n\n\n$ cd newtmgr\n$ go install\n$ ls /tmp/go/bin/newtmgr\n-rwxr-xr-x 1 user staff 17888680 Jul 29 16:28 /tmp/go/bin/newtmgr\n\n\n\n\n\n\n6. If you have a Go workspace, remember to reset your GOPATH to your Go workspace.\n\n\n\n7. Copy the newtmgr executable to a bin directory in your path. You can put it in the /usr/bin or the $GOPATH/bin directory.\n\n\n\n\n Checking the Latest Version of Newtmgr is Installed\n\n\n\n1. Run \nwhich newtmgr\n to verify that you are using the installed version of newtmgr.\n\n\n\n2. Get information about the newtmgr tool:\n\n\n$newtmgr\nNewtmgr helps you manage remote devices running the Mynewt OS\n\nUsage:\n newtmgr [flags]\n newtmgr [command]\n\nAvailable Commands:\n config Read or write a config value on a device\n conn Manage newtmgr connection profiles\n crash Send a crash command to a device\n datetime Manage datetime on a device\n echo Send data to a device and display the echoed back data\n fs Access files on a device\n help Help about any command\n image Manage images on a device\n log Manage logs on a device\n mpstat Read mempool statistics from a device\n reset Perform a soft reset of a device\n run Run test procedures on a device\n stat Read statistics from a device\n taskstat Read task statistics from a device\n\nFlags:\n -c, --conn string connection profile to use\n -h, --help help for newtmgr\n -l, --loglevel string log level to use (default \ninfo\n)\n --name string name of target BLE device; overrides profile setting\n -t, --timeout float timeout in seconds (partial seconds allowed) (default 10)\n -r, --tries int total number of tries in case of timeout (default 1)\n\nUse \nnewtmgr [command] --help\n for more information about a command.",
+ "text": "Installing Newtmgr on Linux\n\n\nYou can install the latest release (1.2.0) of the newtmgr tool from a Debian binary package (amd64). You can also download and build the latest release version of newtmgr from source. \n\n\nThis page shows you how to: \n\n\n\n\n\n\nSet up your computer to download Debian binary packages from the runtimeco APT repository.\n\n\nNote:\n The key for signing the repository has changed. If you set up your computer before release 1.1.0, you will need to download and import the public key again. \n\n\n\n\n\n\nInstall the latest release version of newtmgr from a Debian binary package. You can use apt-get to install the package or manually download and install the Debian binary package.\n\n\n\n\n\n\nDownload, build, and install the latest release version of newtmgr from source. \n\n\n\n\n\n\nSee \nInstalling Previous Releases of Newtgmr\n to install an earlier version of newtmgr.\n\n\nIf you are installing on an amd64 platform, we recommend that you install from the binary package.\n\n\nNote:\n We have tested the newtmgr tool binary and apt-get install from the runtimeco APT repository for Ubuntu version 16. Earlier Ubuntu versions (for example: Ubuntu 14) may have incompatibility with the repository. You can manually download and install the Debian binary package.\n\n\nNote:\n See \nSetting Up a Go Environment to Contribute to Newt and Newtmgr Tools\n if you want to: \n\n\n\n\nUse the newtmgr tool with the latest updates from the master branch. The master branch may be unstable and we recommend that you use the latest stable release version.\n\n\nContribute to the newtmgr tool. \n\n\n\n\n\n\nSetting Up Your Computer to use apt-get to Install the Package\n\n\nThe newtmgr Debian packages are stored in a private APT repository on \nhttps://github/runtimeco/debian-mynewt\n. To use apt-get, you must set up the following on your computer to retrieve packages from the repository:\n\n\nNote\n: You only need to perform this setup once on your computer. However, if you previously downloaded and imported the public key for the runtimeco APT repository, you will need to perform step 2 again as the key has changed.\n\n\n\n\nInstall the \napt-transport-https\n package to use HTTPS to retrieve packages. \n\n\nDownload the public key for the runtimeco APT repository and import the key into the apt keychain.\n\n\nAdd the repository for the binary and source packages to the apt source list.\n\n\n\n\n\n1. Install the apt-transport-https package:\n\n\n$sudo apt-get update\n$sudo apt-get install apt-transport-https\n\n\n\n\n\n\n2. Download the public key for the runtimeco apt repo (\nNote:\n There is a \n-\n after \napt-key add\n):\n\n\nwget -qO - https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/mynewt.gpg.key | sudo apt-key add -\n\n\n\n\n\n\n3. Add the repository for the binary packages to the \nmynewt.list\n apt source list file.\n\n\n$sudo -s\n[sudo] password for \nuser\n:\nroot$ cat \n /etc/apt/sources.list.d/mynewt.list \nEOF\ndeb https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest main\nEOF\nroot$exit\n\n\n\n\n\nNote:\n Do not forget to exit the root shell.\n\n\n\n4. Verify the content of the source list file:\n\n\n$more /etc/apt/sources.list.d/mynewt.list\ndeb https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest main\n\n\n\n\n\n\n5. Update the available packages:\n\n\n$sudo apt-get update\n\n\n\n\n\n\n\nNote:\n If you are not using Ubuntu version 16, you may see the following errors. We have provided instructions on how to manually download and install the binary package.\n\n\nW: Failed to fetch https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/dists/latest/main/source/Sources HttpError404\n\n\n\n\n\n \n\n\nInstalling the Latest Release of Newtmgr from a Binary Package\n\n\nYou can use either apt-get to install the package, or manually download and install the Debian binary package. \n\n\n\n\nMethod 1: Using apt-get to Upgrade or to Install\n\n\nRun the following commands to upgrade or install the latest version of newtmgr:\n\n\n$ sudo apt-get update \n$ sudo apt-get install newtmgr\n\n\n\n\n\nMethod 2: Downloading and Installing the Debian Package Manually\n\n\nDownload and install the package manually.\n\n\n$wget https://raw.githubusercontent.com/runtimeco/binary-releases/master/mynewt-newt-tools_1.2.0/newtmgr_1.2.0-1_amd64.deb\n$sudo dpkg -i newtmgr_1.2.0-1_amd64.deb\n\n\n\n\n\nSee \nChecking the Installed Version of Newtmgr\n to verify that you are using the installed version of newtmgr.\n\n\n\n\nInstalling the Latest Release Version of Newtmgr from Source\n\n\nIf you are running Linux on a different architecture, you can build and install the latest release version of newtmgr from source.\n\n\n\n1. Download and install the latest version of \nGo\n. Newtmgr requires Go version 1.7.6 or higher.\n\n\n\n2. Create a Go workspace in the /tmp directory: \n\n\n$ cd /tmp\n$ mkdir go\n$ cd go\n$ export GOPATH=/tmp/go\n\n\n\n\n\n\n3. Run \ngo get\n to download the newtmgr source. Note that \ngo get\n pulls down the HEAD from the master branch in git, builds, and installs newtmgr.\n\n\n$ go get mynewt.apache.org/newtmgr/newtmgr\n$ ls -l /tmp/go/bin/newtmgr\n-rwxr-xr-x 1 user staff 17884488 Jul 29 16:25 /tmp/go/bin/newtmgr\n\n\n\n\n\n\n4. Check out the source from the latest release version:\n\n\n$ cd src/mynewt.apache.org/newtmgr\n$ git checkout mynewt_1_2_0_tag\nNote: checking out \nmynewt_1_2_0_tag\n.\n\n\n\n\n\n 5. Build newtmgr from the latest release version: \n\n\n$ cd newtmgr\n$ go install\n$ ls /tmp/go/bin/newtmgr\n-rwxr-xr-x 1 user staff 17888680 Jul 29 16:28 /tmp/go/bin/newtmgr\n\n\n\n\n\n\n6. If you have a Go workspace, remember to reset your GOPATH to your Go workspace.\n\n\n\n7. Copy the newtmgr executable to a bin directory in your path. You can put it in the /usr/bin or the $GOPATH/bin directory.\n\n\n\n\n Checking the Latest Version of Newtmgr is Installed\n\n\n\n1. Run \nwhich newtmgr\n to verify that you are using the installed version of newtmgr.\n\n\n\n2. Get information about the newtmgr tool:\n\n\n$newtmgr\nNewtmgr helps you manage remote devices running the Mynewt OS\n\nUsage:\n newtmgr [flags]\n newtmgr [command]\n\nAvailable Commands:\n config Read or write a config value on a device\n conn Manage newtmgr connection profiles\n crash Send a crash command to a device\n datetime Manage datetime on a device\n echo Send data to a device and display the echoed back data\n fs Access files on a device\n help Help about any command\n image Manage images on a device\n log Manage logs on a device\n mpstat Read mempool statistics from a device\n reset Perform a soft reset of a device\n run Run test procedures on a device\n stat Read statistics from a device\n taskstat Read task statistics from a device\n\nFlags:\n -c, --conn string connection profile to use\n -h, --help help for newtmgr\n -l, --loglevel string log level to use (default \ninfo\n)\n --name string name of target BLE device; overrides profile setting\n -t, --timeout float timeout in seconds (partial seconds allowed) (default 10)\n -r, --tries int total number of tries in case of timeout (default 1)\n\nUse \nnewtmgr [command] --help\n for more information about a command.",
"title": "Install Newtmgr On Linux"
},
{
@@ -13342,7 +13342,7 @@
},
{
"location": "/newtmgr/install_linux/#setting-up-your-computer-to-use-apt-get-to-install-the-package",
- "text": "The newtmgr Debian packages are stored in a private APT repository on https://github/runtimeco/debian-mynewt . To use apt-get, you must set up the following on your computer to retrieve packages from the repository: Note : You only need to perform this setup once on your computer. However, if you previously downloaded and imported the public key for the runtimeco APT repository, you will need to perform step 2 again as the key has changed. Install the apt-transport-https package to use HTTPS to retrieve packages. Download the public key for the runtimeco APT repository and import the key into the apt keychain. Add the repository for the binary and source packages to the apt source list. \n1. Install the apt-transport-https package: $sudo apt-get update\n$sudo apt-get install apt-transport-https \n2. Download the public key for the runtimeco apt repo ( Note: There is a - after apt-key add ): wget -qO - https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/mynewt.gpg.key | sudo apt-key add - \n3. Add the repository for the binary packages to the mynewt.list apt source list file. $sudo -s\n[sudo] password for user :\nroot$ cat /etc/apt/sources.list.d/mynewt.list EOF\ndeb https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest main\nEOF\nroot$exit Note: Do not forget to exit the root shell. \n4. Verify the content of the source list file: $more /etc/apt/sources.list.d/mynewt.list\ndeb https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest main \n5. Update the available packages: $sudo apt-get update Note: If you are not using Ubuntu version 16, you may see the following errors. We have provided instructions on how to manually download and install the binary package. W: Failed to fetch https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/dists/latest/main/source/Sources Ht\ntpError404",
+ "text": "The newtmgr Debian packages are stored in a private APT repository on https://github/runtimeco/debian-mynewt . To use apt-get, you must set up the following on your computer to retrieve packages from the repository: Note : You only need to perform this setup once on your computer. However, if you previously downloaded and imported the public key for the runtimeco APT repository, you will need to perform step 2 again as the key has changed. Install the apt-transport-https package to use HTTPS to retrieve packages. Download the public key for the runtimeco APT repository and import the key into the apt keychain. Add the repository for the binary and source packages to the apt source list. \n1. Install the apt-transport-https package: $sudo apt-get update\n$sudo apt-get install apt-transport-https \n2. Download the public key for the runtimeco apt repo ( Note: There is a - after apt-key add ): wget -qO - https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/mynewt.gpg.key | sudo apt-key add - \n3. Add the repository for the binary packages to the mynewt.list apt source list file. $sudo -s\n[sudo] password for user :\nroot$ cat /etc/apt/sources.list.d/mynewt.list EOF\ndeb https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest main\nEOF\nroot$exit Note: Do not forget to exit the root shell. \n4. Verify the content of the source list file: $more /etc/apt/sources.list.d/mynewt.list\ndeb https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest main \n5. Update the available packages: $sudo apt-get update Note: If you are not using Ubuntu version 16, you may see the following errors. We have provided instructions on how to manually download and install the binary package. W: Failed to fetch https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/dists/latest/main/source/Sources HttpError404",
"title": "Setting Up Your Computer to use apt-get to Install the Package"
},
{
@@ -13357,7 +13357,7 @@
},
{
"location": "/newtmgr/install_linux/#method-2-downloading-and-installing-the-debian-package-manually",
- "text": "Download and install the package manually. $wget https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/pool/main/n/newtmgr/newtmgr_1.2.0-1_amd64.deb\n$sudo dpkg -i newtmgr_1.2.0-1_amd64.deb See Checking the Installed Version of Newtmgr to verify that you are using the installed version of newtmgr.",
+ "text": "Download and install the package manually. $wget https://raw.githubusercontent.com/runtimeco/binary-releases/master/mynewt-newt-tools_1.2.0/newtmgr_1.2.0-1_amd64.deb\n$sudo dpkg -i newtmgr_1.2.0-1_amd64.deb See Checking the Installed Version of Newtmgr to verify that you are using the installed version of newtmgr.",
"title": "Method 2: Downloading and Installing the Debian Package Manually"
},
{
diff --git a/latest/newt/install/newt_linux/index.html b/latest/newt/install/newt_linux/index.html
index 9a030c9ad..01b88449e 100644
--- a/latest/newt/install/newt_linux/index.html
+++ b/latest/newt/install/newt_linux/index.html
@@ -488,8 +488,7 @@ <h3 id="setting-up-your-computer-to-use-apt-get-to-install-the-package">Setting
<p><br>
<strong>Note:</strong> If you are not using Ubuntu version 16, you may see the following errors. We have provided instructions on how to manually download and install the binary package.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span></span>W: Failed to fetch https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/dists/latest/main/source/Sources Ht
-tpError404
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span></span>W: Failed to fetch https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/dists/latest/main/source/Sources HttpError404
</pre></div>
@@ -512,8 +511,8 @@ <h4 id="method-1-using-apt-get-to-upgrade-or-to-install">Method 1: Using apt-get
<p><br></p>
<h4 id="method-2-downloading-and-installing-the-debian-package-manually">Method 2: Downloading and Installing the Debian Package Manually</h4>
<p>Download and install the package manually.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span></span>$ wget https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/pool/main/n/newt/newt_1.2.0-1_amd64.deb
-$ sudo dpkg -i newt_1.2.0-1_amd64.deb
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span></span>$wget https://raw.githubusercontent.com/runtimeco/binary-releases/master/mynewt-newt-tools_1.2.0/newt_1.2.0-1_amd64.deb
+$sudo dpkg -i newt_1.2.0-1_amd64.deb
</pre></div>
diff --git a/latest/newt/install/newt_mac/index.html b/latest/newt/install/newt_mac/index.html
index da8d15b61..511438ba2 100644
--- a/latest/newt/install/newt_mac/index.html
+++ b/latest/newt/install/newt_mac/index.html
@@ -428,7 +428,7 @@ <h4>Latest News:</h4> <a href="/download">Apache Mynewt 1.2.0</a> released (Sept
<h2 id="installing-newt-on-mac-os">Installing Newt on Mac OS</h2>
-<p>Newt is supported on Mac OS X 64 bit platforms and has been tested on Mac OS 10.11 and higher.</p>
+<p>Newt is supported on Mac OS X 64 bit platforms and has been tested on Mac OS Sierra.</p>
<p>This page shows you how to install the following versions of newt:</p>
<ul>
<li>Upgrade to or install the latest release version (1.2.0).</li>
@@ -464,24 +464,16 @@ <h4 id="installing-the-latest-release-version-of-newt">Installing the Latest Rel
<p>Run the following command to install the latest release version of newt:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span></span>$ brew update
$ brew install mynewt-newt
-==> Installing mynewt-newt from runtimeco/mynewt
-==> Downloading https://github.com/runtimeco/binary-releases/raw/master/mynewt-newt-tools_1.2.0/mynewt-newt-1.2.0.sierra.bottle.tar.gz
-==> Downloading from https://raw.githubusercontent.com/runtimeco/binary-releases/master/mynewt-newt-tools_1.2.0/mynewt-newt-1.2.0.sierra.bottle.tar.gz
-######################################################################## 100.0%
-==> Pouring mynewt-newt-1.2.0.sierra.bottle.tar.gz
-? /usr/local/Cellar/mynewt-newt/1.2.0: 3 files, 10.7MB
</pre></div>
<p><br>
-<strong>Notes:</strong> Homebrew bottles for newt are available for Mac OS Sierra, and El Captian. If you are running an earlier version of Mac OS, the installation will install the latest version of Go and compile newt locally.</p>
+<strong>Notes:</strong> Homebrew bottles for newt are available for Mac OS Sierra. If you are running an earlier version of Mac OS, the installation will install the latest version of Go and compile newt locally.</p>
<p><br></p>
<h3 id="checking-the-installed-version">Checking the Installed Version</h3>
<p>Check that you are using the installed version of newt:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span></span>$which newt
/usr/local/bin/newt
-$ls -l /usr/local/bin/newt
-lrwxr-xr-x 1 user staff 36 Sep 11 19:04 /usr/local/bin/newt -> ../Cellar/mynewt-newt/1.2.0/bin/newt
$newt version
Apache Newt version: 1.2.0
</pre></div>
@@ -561,30 +553,12 @@ <h3 id="installing-newt-from-the-master-branch">Installing Newt from the Master
<p><br>
Install the latest unstable version of newt from the master branch:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span></span>$ brew install mynewt-newt --HEAD
-==> Installing mynewt-newt from runtimeco/mynewt
-==> Cloning https://github.com/apache/mynewt-newt.git
-Cloning into '/Users/wanda/Library/Caches/Homebrew/mynewt-newt--git'...
-remote: Counting objects: 626, done.
-remote: Compressing objects: 100% (504/504), done.
-remote: Total 626 (delta 155), reused 323 (delta 85), pack-reused 0
-Receiving objects: 100% (626/626), 1.11 MiB | 0 bytes/s, done.
-Resolving deltas: 100% (155/155), done.
-==> Checking out branch master
-==> go install
-? /usr/local/Cellar/mynewt-newt/HEAD-59b3a5d: 3 files, 10.7MB, built in 7 seconds
-$newt version
-Apache Newt version 1.1.0-dev
</pre></div>
<p><br>
To switch back to the latest stable release version of newt, you can run:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span></span>$brew switch mynewt-newt 1.2.0
-Cleaning /usr/local/Cellar/mynewt-newt/1.2.0
-Cleaning /usr/local/Cellar/mynewt-newt/HEAD-59b3a5d
-1 links created for /usr/local/Cellar/mynewt-newt/1.2.0
-$newt version
-Apache Newt version: 1.2.0
</pre></div>
diff --git a/latest/newt/install/newt_windows/index.html b/latest/newt/install/newt_windows/index.html
index 2d9b1378e..5e6c825fe 100644
--- a/latest/newt/install/newt_windows/index.html
+++ b/latest/newt/install/newt_windows/index.html
@@ -434,7 +434,7 @@ <h2 id="installing-newt-on-windows">Installing Newt on Windows</h2>
<ol>
<li>Install MSYS2/MinGW. </li>
<li>Install Git.</li>
-<li>Install latest release of newt (1.2.0) from binary.</li>
+<li>Install latest release (1.2.0) of newt from binary.</li>
<li>Install latest release of newt from source.</li>
</ol>
<p>See <a href="../../../newt/install/prev_releases">Installing Previous Releases of Newt</a> to install an earlier version of newt. You still need to set up your MinGW development environment.</p>
diff --git a/latest/newt/install/prev_releases/index.html b/latest/newt/install/prev_releases/index.html
index 8cf2fce77..b84e54df3 100644
--- a/latest/newt/install/prev_releases/index.html
+++ b/latest/newt/install/prev_releases/index.html
@@ -369,7 +369,7 @@ <h3 id="windows">Windows</h3>
<tbody>
<tr>
<td>1.1.0</td>
-<td><a href="https://raw.githubusercontent.com/runtimeco/binary-releases/master/mynewt-newt-tools_1.1.0/newt_1.1.0-1_amd64.deb">newt_1_1_0_windows_amd64.tar.gz</a></td>
+<td><a href="https://raw.githubusercontent.com/runtimeco/binary-releases/master/mynewt-newt-tools_1.1.0/newt_1_1_0_windows_amd64.tar.gz">newt_1_1_0_windows_amd64.tar.gz</a></td>
</tr>
</tbody>
</table>
diff --git a/latest/newtmgr/install_linux/index.html b/latest/newtmgr/install_linux/index.html
index 18a8fab19..31d4850ba 100644
--- a/latest/newtmgr/install_linux/index.html
+++ b/latest/newtmgr/install_linux/index.html
@@ -472,8 +472,7 @@ <h3 id="setting-up-your-computer-to-use-apt-get-to-install-the-package">Setting
<p><br>
<strong>Note:</strong> If you are not using Ubuntu version 16, you may see the following errors. We have provided instructions on how to manually download and install the binary package.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span></span>W: Failed to fetch https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/dists/latest/main/source/Sources Ht
-tpError404
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span></span>W: Failed to fetch https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/dists/latest/main/source/Sources HttpError404
</pre></div>
@@ -490,7 +489,7 @@ <h4 id="method-1-using-apt-get-to-upgrade-or-to-install">Method 1: Using apt-get
<h4 id="method-2-downloading-and-installing-the-debian-package-manually">Method 2: Downloading and Installing the Debian Package Manually</h4>
<p>Download and install the package manually.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span></span>$wget https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/pool/main/n/newtmgr/newtmgr_1.2.0-1_amd64.deb
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span></span>$wget https://raw.githubusercontent.com/runtimeco/binary-releases/master/mynewt-newt-tools_1.2.0/newtmgr_1.2.0-1_amd64.deb
$sudo dpkg -i newtmgr_1.2.0-1_amd64.deb
</pre></div>
diff --git a/latest/newtmgr/install_mac/index.html b/latest/newtmgr/install_mac/index.html
index 6b2344236..3568bfd1d 100644
--- a/latest/newtmgr/install_mac/index.html
+++ b/latest/newtmgr/install_mac/index.html
@@ -401,7 +401,7 @@ <h4>Latest News:</h4> <a href="/download">Apache Mynewt 1.2.0</a> released (Sept
<h2 id="installing-newtmgr-on-mac-os">Installing Newtmgr on Mac OS</h2>
-<p>Newtmgr is supported on Mac OS X 64 bit platforms and has been tested on Mac OS 10.11 and higher.</p>
+<p>Newtmgr is supported on Mac OS X 64 bit platforms and has been tested on Mac OS Sierra.</p>
<p>This page shows you how to install the following versions of newtmgr:</p>
<ul>
<li>Upgrade to or install the latest release version (1.2.0).</li>
@@ -430,24 +430,16 @@ <h4 id="installing-the-latest-release-version-of-newtmgr">Installing the Latest
<p>Run the following command to install the latest release version of newtmgr:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span></span>$ brew update
$ brew install mynewt-newtmgr
-==> Installing mynewt-newtmgr from runtimeco/mynewt
-==> Downloading https://github.com/runtimeco/binary-releases/raw/master/mynewt-newt-tools_1.2.0/mynewt-newtmgr-1.2.0.sierra.bottle.tar.gz
-==> Downloading from https://raw.githubusercontent.com/runtimeco/binary-releases/master/mynewt-newt-tools_1.2.0/mynewt-newtmgr-1.2.0.sierra.bottle.tar.gz
-######################################################################## 100.0%
-==> Pouring mynewt-newtmgr-1.2.0.sierra.bottle.tar.gz
-? /usr/local/Cellar/mynewt-newtmgr/1.2.0: 3 files, 17.3MB
</pre></div>
<p><br>
-<strong>Notes:</strong> Homebrew bottles for newtmgr 1.2.0 are available for Mac OS Sierra, El Captian. If you are running an earlier version of Mac OS, the installation will install the latest version of Go and compile newtmgr locally.</p>
+<strong>Notes:</strong> Homebrew bottles for newtmgr 1.2.0 are available for Mac OS Sierra. If you are running an earlier version of Mac OS, the installation will install the latest version of Go and compile newtmgr locally.</p>
<p><br></p>
<h3 id="checking-the-installed-version">Checking the Installed Version</h3>
<p>Check that you are using the installed version of newtmgr:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span></span>$which newtmgr
/usr/local/bin/newtmgr
-ls -l /usr/local/bin/newtmgr
-lrwxr-xr-x 1 user staff 42 Sep 11 21:15 /usr/local/bin/newtmgr -> ../Cellar/mynewt-newtmgr/1.2.0/bin/newtmgr
</pre></div>
@@ -504,29 +496,12 @@ <h3 id="installing-newtmgr-from-the-master-branch">Installing Newtmgr from the M
<p><br>
Install the latest unstable version of newtmgr from the master branch:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span></span>$brew install mynewt-newtmgr --HEAD
-==> Installing mynewt-newtmgr from runtimeco/mynewt
-==> Cloning https://github.com/apache/mynewt-newtmgr.git
-Cloning into '/Users/wanda/Library/Caches/Homebrew/mynewt-newtmgr--git'...
-remote: Counting objects: 2169, done.
-remote: Compressing objects: 100% (1752/1752), done.
-remote: Total 2169 (delta 379), reused 2042 (delta 342), pack-reused 0
-Receiving objects: 100% (2169/2169), 8.13 MiB | 5.47 MiB/s, done.
-Resolving deltas: 100% (379/379), done.
-==> Checking out branch master
-==> go get github.com/currantlabs/ble
-==> go get github.com/raff/goble
-==> go get github.com/mgutz/logxi/v1
-==> go install
-? /usr/local/Cellar/mynewt-newtmgr/HEAD-2d5217f: 3 files, 17.3MB, built in 1 minute 10 seconds
</pre></div>
<p><br>
To switch back to the latest stable release version of newtmgr, you can run:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span></span>$brew switch mynewt-newtmgr 1.2.0
-Cleaning /usr/local/Cellar/mynewt-newtmgr/1.2.0
-Cleaning /usr/local/Cellar/mynewt-newtmgr/HEAD-2d5217f
-1 links created for /usr/local/Cellar/mynewt-newtmgr/1.2.0
</pre></div>
diff --git a/latest/newtmgr/prev_releases/index.html b/latest/newtmgr/prev_releases/index.html
index e3427aeb0..c5939ad1c 100644
--- a/latest/newtmgr/prev_releases/index.html
+++ b/latest/newtmgr/prev_releases/index.html
@@ -369,7 +369,7 @@ <h3 id="windows">Windows</h3>
<tbody>
<tr>
<td>1.1.0</td>
-<td><a href="https://raw.githubusercontent.com/runtimeco/binary-releases/master/mynewt-newt-tools_1.1.0/newtmgr_1.1.0-1_amd64.deb">newtmgr_1_1_0_windows_amd64.tar.gz</a></td>
+<td><a href="https://raw.githubusercontent.com/runtimeco/binary-releases/master/mynewt-newt-tools_1.1.0/newtmgr_1_1_0_windows_amd64.tar.gz">newtmgr_1_1_0_windows_amd64.tar.gz</a></td>
</tr>
</tbody>
</table>
diff --git a/latest/os/tutorials/lora/lorawanapp/index.html b/latest/os/tutorials/lora/lorawanapp/index.html
index 6b3988477..eecf5f2a7 100644
--- a/latest/os/tutorials/lora/lorawanapp/index.html
+++ b/latest/os/tutorials/lora/lorawanapp/index.html
@@ -579,7 +579,7 @@ <h3 id="create-the-targets">Create the targets</h3>
<br></p>
<h3 id="build-the-target-executables">Build the target executables</h3>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span></span>$ newt clean telee02_boot
-$ newt clean telee02_boot
+$ newt build telee02_boot
Building target targets/telee02_boot
Compiling repos/apache-mynewt-core/boot/bootutil/src/image_rsa.c
Compiling repos/apache-mynewt-core/boot/bootutil/src/image_ec.c
diff --git a/latest/sitemap.xml b/latest/sitemap.xml
index 9da93ba50..5aeaa1f17 100644
--- a/latest/sitemap.xml
+++ b/latest/sitemap.xml
@@ -4,7 +4,7 @@
<url>
<loc>http://mynewt.apache.org/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -13,13 +13,13 @@
<url>
<loc>http://mynewt.apache.org/pages/ble/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/pages/securitybullets/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -28,7 +28,7 @@
<url>
<loc>http://mynewt.apache.org/quick-start/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -36,7 +36,7 @@
<url>
<loc>http://mynewt.apache.org/about/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -44,7 +44,7 @@
<url>
<loc>http://mynewt.apache.org/talks/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -52,7 +52,7 @@
<url>
<loc>http://mynewt.apache.org/download/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -60,7 +60,7 @@
<url>
<loc>http://mynewt.apache.org/community/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -68,7 +68,7 @@
<url>
<loc>http://mynewt.apache.org/events/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -77,7 +77,7 @@
<url>
<loc>http://mynewt.apache.org/os/introduction/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -89,7 +89,7 @@
<url>
<loc>http://mynewt.apache.org/os/get_started/vocabulary/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -125,7 +125,7 @@
<url>
<loc>http://mynewt.apache.org/known_issues/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -135,37 +135,37 @@
<url>
<loc>http://mynewt.apache.org/newt/install/prev_releases/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/newtmgr/prev_releases/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/go_env/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/ide/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/how_to_edit_docs/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/answers/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
diff --git a/mkdocs/search_index.json b/mkdocs/search_index.json
index ab70dda7e..5a99794a7 100644
--- a/mkdocs/search_index.json
+++ b/mkdocs/search_index.json
@@ -162,12 +162,12 @@
},
{
"location": "/newt/install/newt_mac/",
- "text": "Installing Newt on Mac OS\n\n\nNewt is supported on Mac OS X 64 bit platforms and has been tested on Mac OS 10.11 and higher.\n\n\nThis page shows you how to install the following versions of newt:\n\n\n\n\nUpgrade to or install the latest release version (1.2.0).\n\n\nInstall the latest from the master branch (unstable).\n\n\n\n\nSee \nInstalling Previous Releases of Newt\n to install an earlier version of newt.\n\n\nNote:\n If you would like to contribute to the newt tool, see \nSetting Up Go Environment to Contribute to Newt and Newtmgr Tools\n.\n\n\nInstalling Homebrew\n\n\nIf you do not have Homebrew installed, run the following command. You will be prompted for your sudo password.\n\n\n$ ruby -e \n$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)\n\n\n\n\n\n\nYou can also extract (or \ngit clone\n) Homebrew and install it to /usr/local.\n\n\nAdding the Mynewt Homebrew Tap\n\n\nIf this is your first time installing newt, add the \nruntimeco/homebrew-mynewt\n tap:\n\n\n$ brew tap runtimeco/homebrew-mynewt\n$ brew update\n\n\n\n\n\nUpgrading to or Installing the Latest Release Version\n\n\nPerform the following to upgrade or install the latest release version of newt.\n\n\nUpgrading to the Latest Release Version of Newt\n\n\nIf you have installed an earlier version of newt using brew, run the following commands to upgrade to latest version of newt:\n\n\n$ brew update\n$ brew upgrade mynewt-newt\n\n\n\n\n\n\n\nInstalling the Latest Release Version of Newt\n\n\nRun the following command to install the latest release version of newt:\n\n\n$ brew update\n$ brew install mynewt-newt\n==\n Installing mynewt-newt from runtimeco/mynewt\n==\n Downloading https://github.com/runtimeco/binary-releases/raw/master/mynewt-newt-tools_1.2.0/mynewt-newt-1.2.0.sierra.bottle.tar.gz\n==\n Downloading from https://raw.githubusercontent.com/runtimeco/binary-releases/master/mynewt-newt-tools_1.2.0/mynewt-newt-1.2.0.sierra.bottle.tar.gz\n######################################################################## 100.0%\n==\n Pouring mynewt-newt-1.2.0.sierra.bottle.tar.gz\n\ud83c\udf7a /usr/local/Cellar/mynewt-newt/1.2.0: 3 files, 10.7MB\n\n\n\n\n\n\n\nNotes:\n Homebrew bottles for newt are available for Mac OS Sierra, and El Captian. If you are running an earlier version of Mac OS, the installation will install the latest version of Go and compile newt locally.\n\n\n\n\nChecking the Installed Version\n\n\nCheck that you are using the installed version of newt:\n\n\n$which newt\n/usr/local/bin/newt\n$ls -l /usr/local/bin/newt\nlrwxr-xr-x 1 user staff 36 Sep 11 19:04 /usr/local/bin/newt -\n ../Cellar/mynewt-newt/1.2.0/bin/newt\n$newt version\nApache Newt version: 1.2.0\n\n\n\n\n\nNote:\n If you previously built newt from source and the output of \nwhich newt\n shows \"$GOPATH/bin/newt\", you will need to move \"$GOPATH/bin\" after \"/usr/local/bin\" for your PATH in ~/.bash_profile, and source ~/.bash_profile. \n\n\n\nGet information about newt: \n\n\n$ newt help\nNewt allows you to create your own embedded application based on the Mynewt \noperating system. Newt provides both build and package management in a single \ntool, which allows you to compose an embedded application, and set of \nprojects, and then build the necessary artifacts from those projects. For more \ninformation on the Mynewt operating system, please visit \nhttps://mynewt.apache.org/. \n\nPlease use the newt help command, and specify the name of the command you want \nhelp for, for help on how to use a specific command\n\nUsage:\n newt [flags]\n newt [command]\n\nExamples:\n newt\n newt help [\ncommand-name\n]\n For help on \ncommand-name\n. If not specified, print this message.\n\nAvailable Commands:\n build Build one or more targets\n clean Delete build artifacts for one or more targets\n create-image Add image header to target binary\n debug Open debugger session to target\n info Show project info\n install Install project dependencies\n load Load built target to board\n mfg Manufacturing flash image commands\n new Create a new project\n pkg Create and manage packages in the current workspace\n resign-image Re-sign an image.\n run build/create-image/download/debug \ntarget\n\n size Size of target components\n sync Synchronize project dependencies\n target Commands to create, delete, configure, and query targets\n test Executes unit tests for one or more packages\n upgrade Upgrade project dependencies\n vals Display valid values for the specified element type(s)\n version Display the Newt version number\n\nFlags:\n -h, --help Help for newt commands\n -j, --jobs int Number of concurrent build jobs (default 8)\n -l, --loglevel string Log level (default \nWARN\n)\n -o, --outfile string Filename to tee output to\n -q, --quiet Be quiet; only display error output\n -s, --silent Be silent; don\nt output anything\n -v, --verbose Enable verbose output when executing commands\n\nUse \nnewt [command] --help\n for more information about a command.\n\n\n\n\n\n\n\nInstalling Newt from the Master Branch\n\n\nWe recommend that you use the latest release version of newt. If you would like to use the master branch with the latest updates, you can install newt from the HEAD of the master branch. \n\n\n Notes: \n\n\n\n\nThe master branch may be unstable.\n\n\nThis installation will install the latest version of Go on your computer, if it is not installed, and compile newt locally. \n\n\n\n\n\nIf you previously installed newt using brew, unlink the current version:\n\n\n$brew unlink mynewt-newt\n\n\n\n\n\n\nInstall the latest unstable version of newt from the master branch:\n\n\n$ brew install mynewt-newt --HEAD\n==\n Installing mynewt-newt from runtimeco/mynewt\n==\n Cloning https://github.com/apache/mynewt-newt.git\nCloning into \n/Users/wanda/Library/Caches/Homebrew/mynewt-newt--git\n...\nremote: Counting objects: 626, done.\nremote: Compressing objects: 100% (504/504), done.\nremote: Total 626 (delta 155), reused 323 (delta 85), pack-reused 0\nReceiving objects: 100% (626/626), 1.11 MiB | 0 bytes/s, done.\nResolving deltas: 100% (155/155), done.\n==\n Checking out branch master\n==\n go install\n\ud83c\udf7a /usr/local/Cellar/mynewt-newt/HEAD-59b3a5d: 3 files, 10.7MB, built in 7 seconds\n$newt version\nApache Newt version 1.1.0-dev\n\n\n\n\n\n\nTo switch back to the latest stable release version of newt, you can run:\n\n\n$brew switch mynewt-newt 1.2.0\nCleaning /usr/local/Cellar/mynewt-newt/1.2.0\nCleaning /usr/local/Cellar/mynewt-newt/HEAD-59b3a5d\n1 links created for /usr/local/Cellar/mynewt-newt/1.2.0\n$newt version\nApache Newt version: 1.2.0",
+ "text": "Installing Newt on Mac OS\n\n\nNewt is supported on Mac OS X 64 bit platforms and has been tested on Mac OS Sierra.\n\n\nThis page shows you how to install the following versions of newt:\n\n\n\n\nUpgrade to or install the latest release version (1.2.0).\n\n\nInstall the latest from the master branch (unstable).\n\n\n\n\nSee \nInstalling Previous Releases of Newt\n to install an earlier version of newt.\n\n\nNote:\n If you would like to contribute to the newt tool, see \nSetting Up Go Environment to Contribute to Newt and Newtmgr Tools\n.\n\n\nInstalling Homebrew\n\n\nIf you do not have Homebrew installed, run the following command. You will be prompted for your sudo password.\n\n\n$ ruby -e \n$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)\n\n\n\n\n\n\nYou can also extract (or \ngit clone\n) Homebrew and install it to /usr/local.\n\n\nAdding the Mynewt Homebrew Tap\n\n\nIf this is your first time installing newt, add the \nruntimeco/homebrew-mynewt\n tap:\n\n\n$ brew tap runtimeco/homebrew-mynewt\n$ brew update\n\n\n\n\n\nUpgrading to or Installing the Latest Release Version\n\n\nPerform the following to upgrade or install the latest release version of newt.\n\n\nUpgrading to the Latest Release Version of Newt\n\n\nIf you have installed an earlier version of newt using brew, run the following commands to upgrade to latest version of newt:\n\n\n$ brew update\n$ brew upgrade mynewt-newt\n\n\n\n\n\n\n\nInstalling the Latest Release Version of Newt\n\n\nRun the following command to install the latest release version of newt:\n\n\n$ brew update\n$ brew install mynewt-newt\n\n\n\n\n\n\n\nNotes:\n Homebrew bottles for newt are available for Mac OS Sierra. If you are running an earlier version of Mac OS, the installation will install the latest version of Go and compile newt locally.\n\n\n\n\nChecking the Installed Version\n\n\nCheck that you are using the installed version of newt:\n\n\n$which newt\n/usr/local/bin/newt\n$newt version\nApache Newt version: 1.2.0\n\n\n\n\n\nNote:\n If you previously built newt from source and the output of \nwhich newt\n shows \"$GOPATH/bin/newt\", you will need to move \"$GOPATH/bin\" after \"/usr/local/bin\" for your PATH in ~/.bash_profile, and source ~/.bash_profile. \n\n\n\nGet information about newt: \n\n\n$ newt help\nNewt allows you to create your own embedded application based on the Mynewt \noperating system. Newt provides both build and package management in a single \ntool, which allows you to compose an embedded application, and set of \nprojects, and then build the necessary artifacts from those projects. For more \ninformation on the Mynewt operating system, please visit \nhttps://mynewt.apache.org/. \n\nPlease use the newt help command, and specify the name of the command you want \nhelp for, for help on how to use a specific command\n\nUsage:\n newt [flags]\n newt [command]\n\nExamples:\n newt\n newt help [\ncommand-name\n]\n For help on \ncommand-name\n. If not specified, print this message.\n\nAvailable Commands:\n build Build one or more targets\n clean Delete build artifacts for one or more targets\n create-image Add image header to target binary\n debug Open debugger session to target\n info Show project info\n install Install project dependencies\n load Load built target to board\n mfg Manufacturing flash image commands\n new Create a new project\n pkg Create and manage packages in the current workspace\n resign-image Re-sign an image.\n run build/create-image/download/debug \ntarget\n\n size Size of target components\n sync Synchronize project dependencies\n target Commands to create, delete, configure, and query targets\n test Executes unit tests for one or more packages\n upgrade Upgrade project dependencies\n vals Display valid values for the specified element type(s)\n version Display the Newt version number\n\nFlags:\n -h, --help Help for newt commands\n -j, --jobs int Number of concurrent build jobs (default 8)\n -l, --loglevel string Log level (default \nWARN\n)\n -o, --outfile string Filename to tee output to\n -q, --quiet Be quiet; only display error output\n -s, --silent Be silent; don\nt output anything\n -v, --verbose Enable verbose output when executing commands\n\nUse \nnewt [command] --help\n for more information about a command.\n\n\n\n\n\n\n\nInstalling Newt from the Master Branch\n\n\nWe recommend that you use the latest release version of newt. If you would like to use the master branch with the latest updates, you can install newt from the HEAD of the master branch. \n\n\n Notes: \n\n\n\n\nThe master branch may be unstable.\n\n\nThis installation will install the latest version of Go on your computer, if it is not installed, and compile newt locally. \n\n\n\n\n\nIf you previously installed newt using brew, unlink the current version:\n\n\n$brew unlink mynewt-newt\n\n\n\n\n\n\nInstall the latest unstable version of newt from the master branch:\n\n\n$ brew install mynewt-newt --HEAD\n\n\n\n\n\n\nTo switch back to the latest stable release version of newt, you can run:\n\n\n$brew switch mynewt-newt 1.2.0",
"title": "Install Newt on Mac"
},
{
"location": "/newt/install/newt_mac/#installing-newt-on-mac-os",
- "text": "Newt is supported on Mac OS X 64 bit platforms and has been tested on Mac OS 10.11 and higher. This page shows you how to install the following versions of newt: Upgrade to or install the latest release version (1.2.0). Install the latest from the master branch (unstable). See Installing Previous Releases of Newt to install an earlier version of newt. Note: If you would like to contribute to the newt tool, see Setting Up Go Environment to Contribute to Newt and Newtmgr Tools .",
+ "text": "Newt is supported on Mac OS X 64 bit platforms and has been tested on Mac OS Sierra. This page shows you how to install the following versions of newt: Upgrade to or install the latest release version (1.2.0). Install the latest from the master branch (unstable). See Installing Previous Releases of Newt to install an earlier version of newt. Note: If you would like to contribute to the newt tool, see Setting Up Go Environment to Contribute to Newt and Newtmgr Tools .",
"title": "Installing Newt on Mac OS"
},
{
@@ -192,22 +192,22 @@
},
{
"location": "/newt/install/newt_mac/#installing-the-latest-release-version-of-newt",
- "text": "Run the following command to install the latest release version of newt: $ brew update\n$ brew install mynewt-newt\n== Installing mynewt-newt from runtimeco/mynewt\n== Downloading https://github.com/runtimeco/binary-releases/raw/master/mynewt-newt-tools_1.2.0/mynewt-newt-1.2.0.sierra.bottle.tar.gz\n== Downloading from https://raw.githubusercontent.com/runtimeco/binary-releases/master/mynewt-newt-tools_1.2.0/mynewt-newt-1.2.0.sierra.bottle.tar.gz\n######################################################################## 100.0%\n== Pouring mynewt-newt-1.2.0.sierra.bottle.tar.gz\n\ud83c\udf7a /usr/local/Cellar/mynewt-newt/1.2.0: 3 files, 10.7MB Notes: Homebrew bottles for newt are available for Mac OS Sierra, and El Captian. If you are running an earlier version of Mac OS, the installation will install the latest version of Go and compile newt locally.",
+ "text": "Run the following command to install the latest release version of newt: $ brew update\n$ brew install mynewt-newt Notes: Homebrew bottles for newt are available for Mac OS Sierra. If you are running an earlier version of Mac OS, the installation will install the latest version of Go and compile newt locally.",
"title": "Installing the Latest Release Version of Newt"
},
{
"location": "/newt/install/newt_mac/#checking-the-installed-version",
- "text": "Check that you are using the installed version of newt: $which newt\n/usr/local/bin/newt\n$ls -l /usr/local/bin/newt\nlrwxr-xr-x 1 user staff 36 Sep 11 19:04 /usr/local/bin/newt - ../Cellar/mynewt-newt/1.2.0/bin/newt\n$newt version\nApache Newt version: 1.2.0 Note: If you previously built newt from source and the output of which newt shows \"$GOPATH/bin/newt\", you will need to move \"$GOPATH/bin\" after \"/usr/local/bin\" for your PATH in ~/.bash_profile, and source ~/.bash_profile. \nGet information about newt: $ newt help\nNewt allows you to create your own embedded application based on the Mynewt \noperating system. Newt provides both build and package management in a single \ntool, which allows you to compose an embedded application, and set of \nprojects, and then build the necessary artifacts from those projects. For more \ninformation on the Mynewt operating system, please visit \nhttps://mynewt.apache.org/. \n\nPlease use the newt help command, and specify the name of the command you want \nhelp for, for help on how to use a specific command\n\nUsage:\n newt [flags]\n newt [command]\n\nExamples:\n newt\n newt help [ command-name ]\n For help on command-name . If not specified, print this message.\n\nAvailable Commands:\n build Build one or more targets\n clean Delete build artifacts for one or more targets\n create-image Add image header to target binary\n debug Open debugger session to target\n info Show project info\n install Install project dependencies\n load Load built target to board\n mfg Manufacturing flash image commands\n new Create a new project\n pkg Create and manage packages in the current workspace\n resign-image Re-sign an image.\n run build/create-image/download/debug target \n size Size of target components\n sync Synchronize project dependencies\n target Commands to create, delete, configure, and query targets\n test Executes unit tests for one or more packages\n upgrade Upgrade project dependencies\n vals Display valid values for the specified element type(s)\n version Display the Newt version number\n\nFlags:\n -h, --help Help for newt commands\n -j, --jobs int Number of concurrent build jobs (default 8)\n -l, --loglevel string Log level (default WARN )\n -o, --outfile string Filename to tee output to\n -q, --quiet Be quiet; only display error output\n -s, --silent Be silent; don t output anything\n -v, --verbose Enable verbose output when executing commands\n\nUse newt [command] --help for more information about a command.",
+ "text": "Check that you are using the installed version of newt: $which newt\n/usr/local/bin/newt\n$newt version\nApache Newt version: 1.2.0 Note: If you previously built newt from source and the output of which newt shows \"$GOPATH/bin/newt\", you will need to move \"$GOPATH/bin\" after \"/usr/local/bin\" for your PATH in ~/.bash_profile, and source ~/.bash_profile. \nGet information about newt: $ newt help\nNewt allows you to create your own embedded application based on the Mynewt \noperating system. Newt provides both build and package management in a single \ntool, which allows you to compose an embedded application, and set of \nprojects, and then build the necessary artifacts from those projects. For more \ninformation on the Mynewt operating system, please visit \nhttps://mynewt.apache.org/. \n\nPlease use the newt help command, and specify the name of the command you want \nhelp for, for help on how to use a specific command\n\nUsage:\n newt [flags]\n newt [command]\n\nExamples:\n newt\n newt help [ command-name ]\n For help on command-name . If not specified, print this message.\n\nAvailable Commands:\n build Build one or more targets\n clean Delete build artifacts for one or more targets\n create-image Add image header to target binary\n debug Open debugger session to target\n info Show project info\n install Install project dependencies\n load Load built target to board\n mfg Manufacturing flash image commands\n new Create a new project\n pkg Create and manage packages in the current workspace\n resign-image Re-sign an image.\n run build/create-image/download/debug target \n size Size of target components\n sync Synchronize project dependencies\n target Commands to create, delete, configure, and query targets\n test Executes unit tests for one or more packages\n upgrade Upgrade project dependencies\n vals Display valid values for the specified element type(s)\n version Display the Newt version number\n\nFlags:\n -h, --help Help for newt commands\n -j, --jobs int Number of concurrent build jobs (default 8)\n -l, --loglevel string Log level (default WARN )\n -o, --outfile string Filename to tee output to\n -q, --quiet Be quiet; only display error output\n -s, --silent Be silent; don t output anything\n -v, --verbose Enable verbose output when executing commands\n\nUse newt [command] --help for more information about a command.",
"title": "Checking the Installed Version"
},
{
"location": "/newt/install/newt_mac/#installing-newt-from-the-master-branch",
- "text": "We recommend that you use the latest release version of newt. If you would like to use the master branch with the latest updates, you can install newt from the HEAD of the master branch. Notes: The master branch may be unstable. This installation will install the latest version of Go on your computer, if it is not installed, and compile newt locally. \nIf you previously installed newt using brew, unlink the current version: $brew unlink mynewt-newt \nInstall the latest unstable version of newt from the master branch: $ brew install mynewt-newt --HEAD\n== Installing mynewt-newt from runtimeco/mynewt\n== Cloning https://github.com/apache/mynewt-newt.git\nCloning into /Users/wanda/Library/Caches/Homebrew/mynewt-newt--git ...\nremote: Counting objects: 626, done.\nremote: Compressing objects: 100% (504/504), done.\nremote: Total 626 (delta 155), reused 323 (delta 85), pack-reused 0\nReceiving objects: 100% (626/626), 1.11 MiB | 0 bytes/s, done.\nResolving deltas: 100% (155/155), done.\n== Checking out branch master\n== go install\n\ud83c\udf7a /usr/local/Cellar/mynewt-newt/HEAD-59b3a5d: 3 files, 10.7MB, built in 7 seconds\n$newt version\nApache Newt version 1.1.0-dev \nTo switch back to the latest stable release version of newt, you can run: $brew switch mynewt-newt 1.2.0\nCleaning /usr/local/Cellar/mynewt-newt/1.2.0\nCleaning /usr/local/Cellar/mynewt-newt/HEAD-59b3a5d\n1 links created for /usr/local/Cellar/mynewt-newt/1.2.0\n$newt version\nApache Newt version: 1.2.0",
+ "text": "We recommend that you use the latest release version of newt. If you would like to use the master branch with the latest updates, you can install newt from the HEAD of the master branch. Notes: The master branch may be unstable. This installation will install the latest version of Go on your computer, if it is not installed, and compile newt locally. \nIf you previously installed newt using brew, unlink the current version: $brew unlink mynewt-newt \nInstall the latest unstable version of newt from the master branch: $ brew install mynewt-newt --HEAD \nTo switch back to the latest stable release version of newt, you can run: $brew switch mynewt-newt 1.2.0",
"title": "Installing Newt from the Master Branch"
},
{
"location": "/newt/install/newt_linux/",
- "text": "Installing Newt on Linux\n\n\nYou can install the latest release (1.2.0) of the newt tool from a Debian binary package (amd64). You can also download and build the latest release version of newt from source.\n\n\nThis page shows you how to:\n\n\n\n\n\n\nSet up your computer to download Debian binary packages from the runtimeco APT repository.\n\n\nNote:\n The key for signing the repository has changed. If you set up your computer before release 1.1.0, you will need to download and import the public key again.\n\n\n\n\n\n\nInstall the latest release version of newt from a Debian binary package. You can use apt-get to install the package or manually download and install the Debian binary package.\n\n\n\n\n\n\nDownload, build, and install the latest release version of newt from source.\n\n\n\n\n\n\nIf you are installing on an amd64 platform, we recommend that you install from the binary package.\n\n\nSee \nInstalling Previous Releases of Newt\n to install an earlier version of newt.\n\n\nNote:\n We have tested the newt tool binary and apt-get install from the runtimeco APT repository for Ubuntu version 16. Earlier Ubuntu versions (for example: Ubuntu 14) may have incompatibility with the repository. You can manually download and install the Debian binary package.\n\n\nNote:\n See \nSetting Up a Go Environment to Contribute to Newt and Newtmgr Tools\n if you want to:\n\n\n\n\nUse the newt tool with the latest updates from the master branch. The master branch may be unstable and we recommend that you use the latest stable release version.\n\n\nContribute to the newt tool.\n\n\n\n\n\n\nSetting Up Your Computer to use apt-get to Install the Package\n\n\nThe newt Debian packages are stored in a private APT repository on \nhttps://github/runtimeco/debian-mynewt\n. To use apt-get, you must set up the following on your computer to retrieve packages from the repository:\n\n\nNote\n: You only need to perform this setup once on your computer. However, if you previously downloaded and imported the public key for the runtimeco APT repository, you will need to perform step 2 again as the key has changed.\n\n\n\n\nInstall the \napt-transport-https\n package to use HTTPS to retrieve packages. \n\n\nDownload the public key for the runtimeco APT repository and import the key into the apt keychain.\n\n\nAdd the repository for the binary and source packages to the apt source list.\n\n\n\n\n\nInstall the apt-transport-https package:\n\n\n$ sudo apt-get update\n$ sudo apt-get install apt-transport-https\n\n\n\n\n\n\n\nDownload the public key for the runtimeco apt repo (\nNote:\n There is a \n-\n after \napt-key add\n):\n\n\n$ wget -qO - https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/mynewt.gpg.key | sudo apt-key add -\n\n\n\n\n\n\n\nAdd the repository for the binary and source packages to the \nmynewt.list\n apt source list file:\n\n\n$ sudo tee /etc/apt/sources.list.d/mynewt.list \nEOF\ndeb https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest main\nEOF\n\n\n\n\n\n\nUpdate the available packages: \n\n\n$ sudo apt-get update\n\n\n\n\n\n\n\nNote:\n If you are not using Ubuntu version 16, you may see the following errors. We have provided instructions on how to manually download and install the binary package.\n\n\nW: Failed to fetch https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/dists/latest/main/source/Sources Ht\ntpError404\n\n\n\n\n\n\n\nInstalling the Latest Release of Newt from a Binary Package\n\n\nYou can use either apt-get to install the package, or manually download and install the Debian binary package.\n\n\n\n\nMethod 1: Using apt-get to Upgrade or to Install\n\n\nRun the following commands to upgrade or install the latest version of newt:\n\n\n$ sudo apt-get update \n$ sudo apt-get install newt\n\n\n\n\n\nNote:\n If you encounter build errors (such as missing \nsys/mman.h\n), please make sure you have a 32-bit glibc:\n\n\n$ sudo apt-get install gcc-multilib\n\n\n\n\n\n\n\nMethod 2: Downloading and Installing the Debian Package Manually\n\n\nDownload and install the package manually.\n\n\n$ wget https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/pool/main/n/newt/newt_1.2.0-1_amd64.deb\n$ sudo dpkg -i newt_1.2.0-1_amd64.deb\n\n\n\n\n\n\nSee \nChecking the Installed Version of Newt\n to verify that you are using the installed version of newt.\n\n\n\n\nInstalling the Latest Release of Newt from a Source Package\n\n\nIf you are running Linux on a different architecture, you can build and install the latest release version of newt from source.\n\n\n\n1. You need Go version 1.7.6 or higher to build Newt. Currently, the latest Go version that Ubuntu installs is 1.6. Run \ngo version\n to check if you have Go 1.7.6 installed. You can download Go from \nhttps://golang.org/dl/\n.\n\n\n\n2. Download and unpack the newt source:\n\n\n$ wget -P /tmp https://github.com/apache/mynewt-newt/archive/mynewt_1_2_0_tag.tar.gz\n$ tar -xzf /tmp/mynewt_1_2_0_tag.tar.gz\n\n\n\n\n\n\n3. Run the build.sh to build the newt tool.\n\n\n$ cd mynewt-newt-mynewt_1_2_0_tag\n$ ./build.sh\n$ rm /tmp/mynewt_1_2_0_tag.tar.gz\n\n\n\n\n\n\n4. You should see the \nnewt/newt\n executable. Move the executable to a bin directory in your PATH:\n\n\n\n\n\n\nIf you previously built newt from the master branch, you can move the binary to your $GOPATH/bin directory.\n\n\n$ mv newt/newt $GOPATH/bin\n\n\n\n\n\n\n\n\n\nIf you are installing newt for the first time and do not have a Go workspace set up, you can move the binary to /usr/bin or a directory in your PATH:\n\n\n$ mv newt/newt /usr/bin\n\n\n\n\n\n\n\n\n\n\n\n Checking the Installed Version of Newt\n\n\n\n1. Check which newt you are using and that the version is the latest release version.\n\n\n$ which newt\n/usr/bin/newt\n$ newt version\nApache Newt version: 1.2.0\n\n\n\n\n\n\n2. Get information about newt:\n\n\n$ newt\nNewt allows you to create your own embedded application based on the Mynewt \noperating system. Newt provides both build and package management in a single \ntool, which allows you to compose an embedded application, and set of \nprojects, and then build the necessary artifacts from those projects. For more \ninformation on the Mynewt operating system, please visit \nhttps://mynewt.apache.org/. \n\nPlease use the newt help command, and specify the name of the command you want \nhelp for, for help on how to use a specific command\n\nUsage:\n newt [flags]\n newt [command]\n\nExamples:\n newt\n newt help [\ncommand-name\n]\n For help on \ncommand-name\n. If not specified, print this message.\n\nAvailable Commands:\n build Build one or more targets\n clean Delete build artifacts for one or more targets\n create-image Add image header to target binary\n debug Open debugger session to target\n info Show project info\n install Install project dependencies\n load Load built target to board\n mfg Manufacturing flash image commands\n new Create a new project\n pkg Create and manage packages in the current workspace\n resign-image Re-sign an image.\n run build/create-image/download/debug \ntarget\n\n size Size of target components\n sync Synchronize project dependencies\n target Commands to create, delete, configure, and query targets\n test Executes unit tests for one or more packages\n upgrade Upgrade project dependencies\n vals Display valid values for the specified element type(s)\n version Display the Newt version number\n\nFlags:\n -h, --help Help for newt commands\n -j, --jobs int Number of concurrent build jobs (default 8)\n -l, --loglevel string Log level (default \nWARN\n)\n -o, --outfile string Filename to tee output to\n -q, --quiet Be quiet; only display error output\n -s, --silent Be silent; don\nt output anything\n -v, --verbose Enable verbose output when executing commands\n\nUse \nnewt [command] --help\n for more information about a command.",
+ "text": "Installing Newt on Linux\n\n\nYou can install the latest release (1.2.0) of the newt tool from a Debian binary package (amd64). You can also download and build the latest release version of newt from source.\n\n\nThis page shows you how to:\n\n\n\n\n\n\nSet up your computer to download Debian binary packages from the runtimeco APT repository.\n\n\nNote:\n The key for signing the repository has changed. If you set up your computer before release 1.1.0, you will need to download and import the public key again.\n\n\n\n\n\n\nInstall the latest release version of newt from a Debian binary package. You can use apt-get to install the package or manually download and install the Debian binary package.\n\n\n\n\n\n\nDownload, build, and install the latest release version of newt from source.\n\n\n\n\n\n\nIf you are installing on an amd64 platform, we recommend that you install from the binary package.\n\n\nSee \nInstalling Previous Releases of Newt\n to install an earlier version of newt.\n\n\nNote:\n We have tested the newt tool binary and apt-get install from the runtimeco APT repository for Ubuntu version 16. Earlier Ubuntu versions (for example: Ubuntu 14) may have incompatibility with the repository. You can manually download and install the Debian binary package.\n\n\nNote:\n See \nSetting Up a Go Environment to Contribute to Newt and Newtmgr Tools\n if you want to:\n\n\n\n\nUse the newt tool with the latest updates from the master branch. The master branch may be unstable and we recommend that you use the latest stable release version.\n\n\nContribute to the newt tool.\n\n\n\n\n\n\nSetting Up Your Computer to use apt-get to Install the Package\n\n\nThe newt Debian packages are stored in a private APT repository on \nhttps://github/runtimeco/debian-mynewt\n. To use apt-get, you must set up the following on your computer to retrieve packages from the repository:\n\n\nNote\n: You only need to perform this setup once on your computer. However, if you previously downloaded and imported the public key for the runtimeco APT repository, you will need to perform step 2 again as the key has changed.\n\n\n\n\nInstall the \napt-transport-https\n package to use HTTPS to retrieve packages. \n\n\nDownload the public key for the runtimeco APT repository and import the key into the apt keychain.\n\n\nAdd the repository for the binary and source packages to the apt source list.\n\n\n\n\n\nInstall the apt-transport-https package:\n\n\n$ sudo apt-get update\n$ sudo apt-get install apt-transport-https\n\n\n\n\n\n\n\nDownload the public key for the runtimeco apt repo (\nNote:\n There is a \n-\n after \napt-key add\n):\n\n\n$ wget -qO - https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/mynewt.gpg.key | sudo apt-key add -\n\n\n\n\n\n\n\nAdd the repository for the binary and source packages to the \nmynewt.list\n apt source list file:\n\n\n$ sudo tee /etc/apt/sources.list.d/mynewt.list \nEOF\ndeb https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest main\nEOF\n\n\n\n\n\n\nUpdate the available packages: \n\n\n$ sudo apt-get update\n\n\n\n\n\n\n\nNote:\n If you are not using Ubuntu version 16, you may see the following errors. We have provided instructions on how to manually download and install the binary package.\n\n\nW: Failed to fetch https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/dists/latest/main/source/Sources HttpError404\n\n\n\n\n\n\n\nInstalling the Latest Release of Newt from a Binary Package\n\n\nYou can use either apt-get to install the package, or manually download and install the Debian binary package.\n\n\n\n\nMethod 1: Using apt-get to Upgrade or to Install\n\n\nRun the following commands to upgrade or install the latest version of newt:\n\n\n$ sudo apt-get update \n$ sudo apt-get install newt\n\n\n\n\n\nNote:\n If you encounter build errors (such as missing \nsys/mman.h\n), please make sure you have a 32-bit glibc:\n\n\n$ sudo apt-get install gcc-multilib\n\n\n\n\n\n\n\nMethod 2: Downloading and Installing the Debian Package Manually\n\n\nDownload and install the package manually.\n\n\n$wget https://raw.githubusercontent.com/runtimeco/binary-releases/master/mynewt-newt-tools_1.2.0/newt_1.2.0-1_amd64.deb\n$sudo dpkg -i newt_1.2.0-1_amd64.deb\n\n\n\n\n\n\nSee \nChecking the Installed Version of Newt\n to verify that you are using the installed version of newt.\n\n\n\n\nInstalling the Latest Release of Newt from a Source Package\n\n\nIf you are running Linux on a different architecture, you can build and install the latest release version of newt from source.\n\n\n\n1. You need Go version 1.7.6 or higher to build Newt. Currently, the latest Go version that Ubuntu installs is 1.6. Run \ngo version\n to check if you have Go 1.7.6 installed. You can download Go from \nhttps://golang.org/dl/\n.\n\n\n\n2. Download and unpack the newt source:\n\n\n$ wget -P /tmp https://github.com/apache/mynewt-newt/archive/mynewt_1_2_0_tag.tar.gz\n$ tar -xzf /tmp/mynewt_1_2_0_tag.tar.gz\n\n\n\n\n\n\n3. Run the build.sh to build the newt tool.\n\n\n$ cd mynewt-newt-mynewt_1_2_0_tag\n$ ./build.sh\n$ rm /tmp/mynewt_1_2_0_tag.tar.gz\n\n\n\n\n\n\n4. You should see the \nnewt/newt\n executable. Move the executable to a bin directory in your PATH:\n\n\n\n\n\n\nIf you previously built newt from the master branch, you can move the binary to your $GOPATH/bin directory.\n\n\n$ mv newt/newt $GOPATH/bin\n\n\n\n\n\n\n\n\n\nIf you are installing newt for the first time and do not have a Go workspace set up, you can move the binary to /usr/bin or a directory in your PATH:\n\n\n$ mv newt/newt /usr/bin\n\n\n\n\n\n\n\n\n\n\n\n Checking the Installed Version of Newt\n\n\n\n1. Check which newt you are using and that the version is the latest release version.\n\n\n$ which newt\n/usr/bin/newt\n$ newt version\nApache Newt version: 1.2.0\n\n\n\n\n\n\n2. Get information about newt:\n\n\n$ newt\nNewt allows you to create your own embedded application based on the Mynewt \noperating system. Newt provides both build and package management in a single \ntool, which allows you to compose an embedded application, and set of \nprojects, and then build the necessary artifacts from those projects. For more \ninformation on the Mynewt operating system, please visit \nhttps://mynewt.apache.org/. \n\nPlease use the newt help command, and specify the name of the command you want \nhelp for, for help on how to use a specific command\n\nUsage:\n newt [flags]\n newt [command]\n\nExamples:\n newt\n newt help [\ncommand-name\n]\n For help on \ncommand-name\n. If not specified, print this message.\n\nAvailable Commands:\n build Build one or more targets\n clean Delete build artifacts for one or more targets\n create-image Add image header to target binary\n debug Open debugger session to target\n info Show project info\n install Install project dependencies\n load Load built target to board\n mfg Manufacturing flash image commands\n new Create a new project\n pkg Create and manage packages in the current workspace\n resign-image Re-sign an image.\n run build/create-image/download/debug \ntarget\n\n size Size of target components\n sync Synchronize project dependencies\n target Commands to create, delete, configure, and query targets\n test Executes unit tests for one or more packages\n upgrade Upgrade project dependencies\n vals Display valid values for the specified element type(s)\n version Display the Newt version number\n\nFlags:\n -h, --help Help for newt commands\n -j, --jobs int Number of concurrent build jobs (default 8)\n -l, --loglevel string Log level (default \nWARN\n)\n -o, --outfile string Filename to tee output to\n -q, --quiet Be quiet; only display error output\n -s, --silent Be silent; don\nt output anything\n -v, --verbose Enable verbose output when executing commands\n\nUse \nnewt [command] --help\n for more information about a command.",
"title": "Install Newt on Linux"
},
{
@@ -217,7 +217,7 @@
},
{
"location": "/newt/install/newt_linux/#setting-up-your-computer-to-use-apt-get-to-install-the-package",
- "text": "The newt Debian packages are stored in a private APT repository on https://github/runtimeco/debian-mynewt . To use apt-get, you must set up the following on your computer to retrieve packages from the repository: Note : You only need to perform this setup once on your computer. However, if you previously downloaded and imported the public key for the runtimeco APT repository, you will need to perform step 2 again as the key has changed. Install the apt-transport-https package to use HTTPS to retrieve packages. Download the public key for the runtimeco APT repository and import the key into the apt keychain. Add the repository for the binary and source packages to the apt source list. \nInstall the apt-transport-https package: $ sudo apt-get update\n$ sudo apt-get install apt-transport-https Download the public key for the runtimeco apt repo ( Note: There is a - after apt-key add ): $ wget -qO - https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/mynewt.gpg.key | sudo apt-key add - Add the repository for the binary and source packages to the mynewt.list apt source list file: $ sudo tee /etc/apt/sources.list.d/mynewt.list EOF\ndeb https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest main\nEOF \nUpdate the available packages: $ sudo apt-get update Note: If you are not using Ubuntu version 16, you may see the following errors. We have provided instructions on how to manually download and install the binary package. W: Failed to fetch https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/dists/latest/main/source/Sources Ht\ntpError404",
+ "text": "The newt Debian packages are stored in a private APT repository on https://github/runtimeco/debian-mynewt . To use apt-get, you must set up the following on your computer to retrieve packages from the repository: Note : You only need to perform this setup once on your computer. However, if you previously downloaded and imported the public key for the runtimeco APT repository, you will need to perform step 2 again as the key has changed. Install the apt-transport-https package to use HTTPS to retrieve packages. Download the public key for the runtimeco APT repository and import the key into the apt keychain. Add the repository for the binary and source packages to the apt source list. \nInstall the apt-transport-https package: $ sudo apt-get update\n$ sudo apt-get install apt-transport-https Download the public key for the runtimeco apt repo ( Note: There is a - after apt-key add ): $ wget -qO - https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/mynewt.gpg.key | sudo apt-key add - Add the repository for the binary and source packages to the mynewt.list apt source list file: $ sudo tee /etc/apt/sources.list.d/mynewt.list EOF\ndeb https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest main\nEOF \nUpdate the available packages: $ sudo apt-get update Note: If you are not using Ubuntu version 16, you may see the following errors. We have provided instructions on how to manually download and install the binary package. W: Failed to fetch https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/dists/latest/main/source/Sources HttpError404",
"title": "Setting Up Your Computer to use apt-get to Install the Package"
},
{
@@ -232,7 +232,7 @@
},
{
"location": "/newt/install/newt_linux/#method-2-downloading-and-installing-the-debian-package-manually",
- "text": "Download and install the package manually. $ wget https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/pool/main/n/newt/newt_1.2.0-1_amd64.deb\n$ sudo dpkg -i newt_1.2.0-1_amd64.deb \nSee Checking the Installed Version of Newt to verify that you are using the installed version of newt.",
+ "text": "Download and install the package manually. $wget https://raw.githubusercontent.com/runtimeco/binary-releases/master/mynewt-newt-tools_1.2.0/newt_1.2.0-1_amd64.deb\n$sudo dpkg -i newt_1.2.0-1_amd64.deb \nSee Checking the Installed Version of Newt to verify that you are using the installed version of newt.",
"title": "Method 2: Downloading and Installing the Debian Package Manually"
},
{
@@ -242,12 +242,12 @@
},
{
"location": "/newt/install/newt_windows/",
- "text": "Installing Newt on Windows\n\n\nYou can develop and build Mynewt OS applications for your target boards on the Windows platform. This guide shows you how to install the latest release version of newt from binary or from source. The tool is written in Go (golang).\n\n\nIn Windows, we use MinGW as the development environment to build and run Mynewt OS applications for target boards. MinGW runs the bash shell and provides a Unix-like environment. This provides a uniform way to build Mynewt OS applications. The Mynewt documentation and tutorials use Unix commands and you can use the same Unix commands on MinGW to follow the tutorials. The documentation will note any commands or behaviors that are specific to Windows.\n\n\nThis guide shows you how to perform the following:\n\n\n\n\nInstall MSYS2/MinGW. \n\n\nInstall Git.\n\n\nInstall latest release of newt (1.2.0) from binary.\n\n\nInstall latest release of newt from source.\n\n\n\n\nSee \nInstalling Previous Releases of Newt\n to install an earlier version of newt. You still need to set up your MinGW development environment.\n\n\nNote:\n If you would like to contribute to the newt tool, see \nSetting Up Go Environment to Contribute to Newt and Newtmgr Tools\n.\n\n\n\n\nInstalling MSYS2/MinGW\n\n\nMSYS2/MinGW provides a bash shell and tools to build applications that run on Windows. It includes three subsystems:\n\n\n\n\nMSYS2 toolchain to build POSIX applications that run on Windows. \n\n\nMinGW32 toolchains to build 32 bit native Windows applications. \n\n\nMinGW64 toolchains to build 64 bit native Windows applications. \n\n\n\n\nThe subsystems run the bash shell and provide a Unix-like environment. You can also run Windows applications from the shell. We will use the MinGW subsystem.\n\n\nNote:\n You can skip this installation step if you already have MinGW installed (from an earlier MSYS2/MinGW or Git Bash installation), but you must list the \nbin\n path for your installation in your Windows Path. For example: if you installed MSYS2/MinGW in the \n C:\\msys64 \n directory, add \nC:\\msys64\\usr\\bin\n to your Windows Path. If you are using Windows 10 WSL, ensure that you use the \nC:\\msys64\\usr\\bin\\bash.exe\n and not the Windows 10 WSL bash.\n\n\nTo install and setup MSYS2 and MinGW:\n\n\n\n\nDownload and run the \nMSYS2 installer\n. Select the 64 bit version if you are running on a 64 bit platform. Follow the prompts and check the \nRun MSYS2 now\n checkbox on the \nInstallation Complete\n dialog. \n\n\n\n\nIn the MSYS2 terminal, run the \npacman -Syuu\n command. If you get a message to run the update again, close the terminal and run the \npacman -Syuu\n command in a new terminal. \n\n\nTo start a new MSYS2 terminal, select the \"MSYS2 MSYS\" application from the Windows start menu.\n\n\n\n\n\n\nAdd a new user variable named \nMSYS2_PATH_TYPE\n and set the value to \ninherit\n in your Windows environment. This enables the MSYS2 and MinGW bash to inherit your Windows user \nPath\n values. \n\n\nTo add the variable, select properties for your computer \n Advanced system settings \n Environment Variables \n New\n\n\n\n\n\n\nAdd the MinGW \nbin\n path to your Windows Path. For example: if you install MSYS2/MinGW in the \nC:\\msys64\n directory, add \nC:\\msys64\\usr\\bin\n to your Windows Path. \n\n\nNote:\n If you are using Windows 10 WSL, ensure that you use the \nC:\\msys64\\usr\\bin\\bash.exe\n and not the Windows 10 WSL bash.\n\n\n\n\n\n\nRun the \npacman -Su vim\n command to install the vim editor. \n\n\nNote:\nYou can also use a Windows editor. You can access your files from the \nC:\\\nmsys-install-folder\n\\home\\\nusername\n folder, where \nmsys-install-folder\n is the folder you installed MSYS2 in. For example, if you installed MSYS2 in the \nmsys64\n folder, your files are stored in \nC:\\msys64\\home\\\nusername\n\n\n\n\n\n\nRun the \npacman -Su tar\n command to install the tar tool. \n\n\n\n\n\n\nYou will need to start a MinGW terminal to run the commands specified in the Mynewt documentation and tutorials. To start a MinGW terminal, select the \"MSYS2 Mingw\" application from the start Menu (you can use either MinGW32 or MinGW64). \nIn Windows, we use the MinGW subsystem to build Mynewt tools and applications. \n\n\nInstalling Git for Windows\n\n\nDownload and install \nGit for Windows\n if it is not already installed.\n\n\nInstalling the Latest Release of the Newt Tool from Binary\n\n\nYou can install the latest release of newt from binary. It has been tested on Windows 10 64 bit platform. \n\n\n\n1. Start a MinGW terminal.\n\n\n\n2. Download the newt binary tar file:\n\n\n$ wget -P /tmp https://raw.githubusercontent.com/runtimeco/binary-releases/master/mynewt-newt-tools_1.2.0/newt_1_2_0_windows_amd64.tar.gz\n\n\n\n\n\n\n3. Extract the file:\n\n\n\n\n\n\nIf you previously built newt from the master branch, you can extract the file into your $GOPATH/bin directory. Note: This overwrites the current newt.exe in the directory and assumes that you are using $GOPATH/bin for your Go applications.\n\n\n tar -xzf /tmp/newt_1_2_0_windows_amd64.tar.gz -C $GOPATH/bin\n\n\n\n\n\n\n\n\n\nIf you are installing newt for the first time and do not have a Go workspace setup, you can extract into /usr/bin directory:\n\n\n tar -xzf /tmp/newt_1_2_0_windows_amd64.tar.gz -C /usr/bin\n\n\n\n\n\n\n\n\n\n\n4. Verify the installed version of newt. See \nChecking the Installed Version\n.\n\n\n\n\nInstalling the Latest Release of Newt From Source\n\n\nIf you have an older version of Windows or a 32 bit platform, you can build and install the latest release version of newt from source.\n\n\n\n1. If you do not have Go installed, download and install the latest version of \nGo\n. Newt requires Go version 1.7.6 or higher.\n\n\n\n2. Start a MinGw terminal.\n\n\n\n3. Download and unpack the newt source:\n\n\n$ wget -P /tmp https://github.com/apache/mynewt-newt/archive/mynewt_1_2_0_tag.tar.gz\n$ tar -xzf /tmp/mynewt_1_2_0_tag.tar.gz\n\n\n\n\n\n\n4. Run the build.sh to build the newt tool.\n\n\n$ cd mynewt-newt-mynewt_1_2_0_tag \n$ ./build.sh\n$ rm /tmp/mynewt_1_2_0_tag.tar.gz\n\n\n\n\n\n\n5. You should see the \nnewt/newt.exe\n executable. Move the executable to a bin directory in your PATH:\n\n\n\n\n\n\nIf you previously built newt from the master branch, you can move the executable to the $GOPATH/bin directory.\n\n\n$ mv newt/newt.exe $GOPATH/bin\n\n\n\n\n\n\n\n\n\nIf you are installing newt for the first time and do not have a Go workspace set up, you can move the executable to /usr/bin or a directory in your PATH:\n\n\n$ mv newt/newt.exe /usr/bin\n\n\n\n\n\n\n\n\n\n\n\nChecking the Installed Version\n\n\n\n1. Check the version of newt:\n\n\n$ newt version\nApache Newt version: 1.2.0\n\n\n\n\n\n\n2. Get information about newt:\n\n\nNewt allows you to create your own embedded application based on the Mynewt \noperating system. Newt provides both build and package management in a single \ntool, which allows you to compose an embedded application, and set of \nprojects, and then build the necessary artifacts from those projects. For more \ninformation on the Mynewt operating system, please visit \nhttps://mynewt.apache.org/. \n\nPlease use the newt help command, and specify the name of the command you want \nhelp for, for help on how to use a specific command\n\nUsage:\n newt [flags]\n newt [command]\n\nExamples:\n newt\n newt help [\ncommand-name\n]\n For help on \ncommand-name\n. If not specified, print this message.\n\nAvailable Commands:\n build Build one or more targets\n clean Delete build artifacts for one or more targets\n create-image Add image header to target binary\n debug Open debugger session to target\n info Show project info\n install Install project dependencies\n load Load built target to board\n mfg Manufacturing flash image commands\n new Create a new project\n pkg Create and manage packages in the current workspace\n resign-image Re-sign an image.\n run build/create-image/download/debug \ntarget\n\n size Size of target components\n sync Synchronize project dependencies\n target Commands to create, delete, configure, and query targets\n test Executes unit tests for one or more packages\n upgrade Upgrade project dependencies\n vals Display valid values for the specified element type(s)\n version Display the Newt version number\n\nFlags:\n -h, --help Help for newt commands\n -j, --jobs int Number of concurrent build jobs (default 8)\n -l, --loglevel string Log level (default \nWARN\n)\n -o, --outfile string Filename to tee output to\n -q, --quiet Be quiet; only display error output\n -s, --silent Be silent; don\nt output anything\n -v, --verbose Enable verbose output when executing commands\n\nUse \nnewt [command] --help\n for more information about a command.",
+ "text": "Installing Newt on Windows\n\n\nYou can develop and build Mynewt OS applications for your target boards on the Windows platform. This guide shows you how to install the latest release version of newt from binary or from source. The tool is written in Go (golang).\n\n\nIn Windows, we use MinGW as the development environment to build and run Mynewt OS applications for target boards. MinGW runs the bash shell and provides a Unix-like environment. This provides a uniform way to build Mynewt OS applications. The Mynewt documentation and tutorials use Unix commands and you can use the same Unix commands on MinGW to follow the tutorials. The documentation will note any commands or behaviors that are specific to Windows.\n\n\nThis guide shows you how to perform the following:\n\n\n\n\nInstall MSYS2/MinGW. \n\n\nInstall Git.\n\n\nInstall latest release (1.2.0) of newt from binary.\n\n\nInstall latest release of newt from source.\n\n\n\n\nSee \nInstalling Previous Releases of Newt\n to install an earlier version of newt. You still need to set up your MinGW development environment.\n\n\nNote:\n If you would like to contribute to the newt tool, see \nSetting Up Go Environment to Contribute to Newt and Newtmgr Tools\n.\n\n\n\n\nInstalling MSYS2/MinGW\n\n\nMSYS2/MinGW provides a bash shell and tools to build applications that run on Windows. It includes three subsystems:\n\n\n\n\nMSYS2 toolchain to build POSIX applications that run on Windows. \n\n\nMinGW32 toolchains to build 32 bit native Windows applications. \n\n\nMinGW64 toolchains to build 64 bit native Windows applications. \n\n\n\n\nThe subsystems run the bash shell and provide a Unix-like environment. You can also run Windows applications from the shell. We will use the MinGW subsystem.\n\n\nNote:\n You can skip this installation step if you already have MinGW installed (from an earlier MSYS2/MinGW or Git Bash installation), but you must list the \nbin\n path for your installation in your Windows Path. For example: if you installed MSYS2/MinGW in the \n C:\\msys64 \n directory, add \nC:\\msys64\\usr\\bin\n to your Windows Path. If you are using Windows 10 WSL, ensure that you use the \nC:\\msys64\\usr\\bin\\bash.exe\n and not the Windows 10 WSL bash.\n\n\nTo install and setup MSYS2 and MinGW:\n\n\n\n\nDownload and run the \nMSYS2 installer\n. Select the 64 bit version if you are running on a 64 bit platform. Follow the prompts and check the \nRun MSYS2 now\n checkbox on the \nInstallation Complete\n dialog. \n\n\n\n\nIn the MSYS2 terminal, run the \npacman -Syuu\n command. If you get a message to run the update again, close the terminal and run the \npacman -Syuu\n command in a new terminal. \n\n\nTo start a new MSYS2 terminal, select the \"MSYS2 MSYS\" application from the Windows start menu.\n\n\n\n\n\n\nAdd a new user variable named \nMSYS2_PATH_TYPE\n and set the value to \ninherit\n in your Windows environment. This enables the MSYS2 and MinGW bash to inherit your Windows user \nPath\n values. \n\n\nTo add the variable, select properties for your computer \n Advanced system settings \n Environment Variables \n New\n\n\n\n\n\n\nAdd the MinGW \nbin\n path to your Windows Path. For example: if you install MSYS2/MinGW in the \nC:\\msys64\n directory, add \nC:\\msys64\\usr\\bin\n to your Windows Path. \n\n\nNote:\n If you are using Windows 10 WSL, ensure that you use the \nC:\\msys64\\usr\\bin\\bash.exe\n and not the Windows 10 WSL bash.\n\n\n\n\n\n\nRun the \npacman -Su vim\n command to install the vim editor. \n\n\nNote:\nYou can also use a Windows editor. You can access your files from the \nC:\\\nmsys-install-folder\n\\home\\\nusername\n folder, where \nmsys-install-folder\n is the folder you installed MSYS2 in. For example, if you installed MSYS2 in the \nmsys64\n folder, your files are stored in \nC:\\msys64\\home\\\nusername\n\n\n\n\n\n\nRun the \npacman -Su tar\n command to install the tar tool. \n\n\n\n\n\n\nYou will need to start a MinGW terminal to run the commands specified in the Mynewt documentation and tutorials. To start a MinGW terminal, select the \"MSYS2 Mingw\" application from the start Menu (you can use either MinGW32 or MinGW64). \nIn Windows, we use the MinGW subsystem to build Mynewt tools and applications. \n\n\nInstalling Git for Windows\n\n\nDownload and install \nGit for Windows\n if it is not already installed.\n\n\nInstalling the Latest Release of the Newt Tool from Binary\n\n\nYou can install the latest release of newt from binary. It has been tested on Windows 10 64 bit platform. \n\n\n\n1. Start a MinGW terminal.\n\n\n\n2. Download the newt binary tar file:\n\n\n$ wget -P /tmp https://raw.githubusercontent.com/runtimeco/binary-releases/master/mynewt-newt-tools_1.2.0/newt_1_2_0_windows_amd64.tar.gz\n\n\n\n\n\n\n3. Extract the file:\n\n\n\n\n\n\nIf you previously built newt from the master branch, you can extract the file into your $GOPATH/bin directory. Note: This overwrites the current newt.exe in the directory and assumes that you are using $GOPATH/bin for your Go applications.\n\n\n tar -xzf /tmp/newt_1_2_0_windows_amd64.tar.gz -C $GOPATH/bin\n\n\n\n\n\n\n\n\n\nIf you are installing newt for the first time and do not have a Go workspace setup, you can extract into /usr/bin directory:\n\n\n tar -xzf /tmp/newt_1_2_0_windows_amd64.tar.gz -C /usr/bin\n\n\n\n\n\n\n\n\n\n\n4. Verify the installed version of newt. See \nChecking the Installed Version\n.\n\n\n\n\nInstalling the Latest Release of Newt From Source\n\n\nIf you have an older version of Windows or a 32 bit platform, you can build and install the latest release version of newt from source.\n\n\n\n1. If you do not have Go installed, download and install the latest version of \nGo\n. Newt requires Go version 1.7.6 or higher.\n\n\n\n2. Start a MinGw terminal.\n\n\n\n3. Download and unpack the newt source:\n\n\n$ wget -P /tmp https://github.com/apache/mynewt-newt/archive/mynewt_1_2_0_tag.tar.gz\n$ tar -xzf /tmp/mynewt_1_2_0_tag.tar.gz\n\n\n\n\n\n\n4. Run the build.sh to build the newt tool.\n\n\n$ cd mynewt-newt-mynewt_1_2_0_tag \n$ ./build.sh\n$ rm /tmp/mynewt_1_2_0_tag.tar.gz\n\n\n\n\n\n\n5. You should see the \nnewt/newt.exe\n executable. Move the executable to a bin directory in your PATH:\n\n\n\n\n\n\nIf you previously built newt from the master branch, you can move the executable to the $GOPATH/bin directory.\n\n\n$ mv newt/newt.exe $GOPATH/bin\n\n\n\n\n\n\n\n\n\nIf you are installing newt for the first time and do not have a Go workspace set up, you can move the executable to /usr/bin or a directory in your PATH:\n\n\n$ mv newt/newt.exe /usr/bin\n\n\n\n\n\n\n\n\n\n\n\nChecking the Installed Version\n\n\n\n1. Check the version of newt:\n\n\n$ newt version\nApache Newt version: 1.2.0\n\n\n\n\n\n\n2. Get information about newt:\n\n\nNewt allows you to create your own embedded application based on the Mynewt \noperating system. Newt provides both build and package management in a single \ntool, which allows you to compose an embedded application, and set of \nprojects, and then build the necessary artifacts from those projects. For more \ninformation on the Mynewt operating system, please visit \nhttps://mynewt.apache.org/. \n\nPlease use the newt help command, and specify the name of the command you want \nhelp for, for help on how to use a specific command\n\nUsage:\n newt [flags]\n newt [command]\n\nExamples:\n newt\n newt help [\ncommand-name\n]\n For help on \ncommand-name\n. If not specified, print this message.\n\nAvailable Commands:\n build Build one or more targets\n clean Delete build artifacts for one or more targets\n create-image Add image header to target binary\n debug Open debugger session to target\n info Show project info\n install Install project dependencies\n load Load built target to board\n mfg Manufacturing flash image commands\n new Create a new project\n pkg Create and manage packages in the current workspace\n resign-image Re-sign an image.\n run build/create-image/download/debug \ntarget\n\n size Size of target components\n sync Synchronize project dependencies\n target Commands to create, delete, configure, and query targets\n test Executes unit tests for one or more packages\n upgrade Upgrade project dependencies\n vals Display valid values for the specified element type(s)\n version Display the Newt version number\n\nFlags:\n -h, --help Help for newt commands\n -j, --jobs int Number of concurrent build jobs (default 8)\n -l, --loglevel string Log level (default \nWARN\n)\n -o, --outfile string Filename to tee output to\n -q, --quiet Be quiet; only display error output\n -s, --silent Be silent; don\nt output anything\n -v, --verbose Enable verbose output when executing commands\n\nUse \nnewt [command] --help\n for more information about a command.",
"title": "Install Newt on Windows"
},
{
"location": "/newt/install/newt_windows/#installing-newt-on-windows",
- "text": "You can develop and build Mynewt OS applications for your target boards on the Windows platform. This guide shows you how to install the latest release version of newt from binary or from source. The tool is written in Go (golang). In Windows, we use MinGW as the development environment to build and run Mynewt OS applications for target boards. MinGW runs the bash shell and provides a Unix-like environment. This provides a uniform way to build Mynewt OS applications. The Mynewt documentation and tutorials use Unix commands and you can use the same Unix commands on MinGW to follow the tutorials. The documentation will note any commands or behaviors that are specific to Windows. This guide shows you how to perform the following: Install MSYS2/MinGW. Install Git. Install latest release of newt (1.2.0) from binary. Install latest release of newt from source. See Installing Previous Releases of Newt to install an earlier version of newt. You still need to set up your MinGW development environment. Note: If you would like to contribute to the newt tool, see Setting Up Go Environment to Contribute to Newt and Newtmgr Tools .",
+ "text": "You can develop and build Mynewt OS applications for your target boards on the Windows platform. This guide shows you how to install the latest release version of newt from binary or from source. The tool is written in Go (golang). In Windows, we use MinGW as the development environment to build and run Mynewt OS applications for target boards. MinGW runs the bash shell and provides a Unix-like environment. This provides a uniform way to build Mynewt OS applications. The Mynewt documentation and tutorials use Unix commands and you can use the same Unix commands on MinGW to follow the tutorials. The documentation will note any commands or behaviors that are specific to Windows. This guide shows you how to perform the following: Install MSYS2/MinGW. Install Git. Install latest release (1.2.0) of newt from binary. Install latest release of newt from source. See Installing Previous Releases of Newt to install an earlier version of newt. You still need to set up your MinGW development environment. Note: If you would like to contribute to the newt tool, see Setting Up Go Environment to Contribute to Newt and Newtmgr Tools .",
"title": "Installing Newt on Windows"
},
{
@@ -1592,7 +1592,7 @@
},
{
"location": "/os/tutorials/lora/lorawanapp/",
- "text": "LoRaWAN App\n\n\n\n\nObjective\n\n\nThe purpose of this tutorial is to demonstrate how to build the lora app shell application for either a class A or class C lora device and to perform basic functions such as joining and sending data packets to a lora gateway/server.\n\n\nNOTE: This tutorial presumes that you have a running lora gateway and lora network server. No description of the gateway/server is provided. It is expected that the user understands how to configure and operate the gateway/server so that it can communicate with a class A or class C device.\n\n\n\n\nHardware needed\n\n\n\n\nTelenor EE02 module\n\n\nSegger J-Link or similar debugger\n\n\nLORA gateway\n\n\nLaptop running Mac OS\n\n\nIt is assumed you have already installed newt tool. \n\n\nIt is assumed you understand the basics of the mynewt OS\n\n\n3-wire serial cable to connect telenor module to your laptop\n\n\nSome form of terminal emulation application running on your laptop.\n\n\n\n\n\n\nCreate a project.\n\n\nCreate a new project to hold your work. For a deeper understanding, you can read about project creation in \n\nGet Started -- Creating Your First Project\n\nor just follow the commands below.\n\n\n $ mkdir ~/dev\n $ cd ~/dev\n $ newt new mylora\n Downloading project skeleton from apache/mynewt-blinky...\n Installing skeleton in mylora...\n Project mylora successfully created.\n $ cd mylora\n\n\n\n\n\n\n\nInstall Everything\n\n\nNow that you have defined the needed repositories, it's time to install everything so\nthat you can get started.\n\n\n $ newt install -v \n apache-mynewt-core\n Downloading repository description for apache-mynewt-core... success!\n ...\n apache-mynewt-core successfully installed version 1.2.0-none\n ...\n\n\n\n\n\n\n\nCreate the targets\n\n\nCreate two targets - one for the bootloader and one for the lora app shell application. \n\n\n$ newt target create telee02_boot\n$ newt target set telee02_boot bsp=@apache-mynewt-core/hw/bsp/telee02\n$ newt target set telee02_boot app=@apache-mynewt-core/apps/boot\n$ newt target set telee02_boot build_profile=optimized\n\n$ newt target create lora_app_shell_telee02\n$ newt target set lora_app_shell_telee02 bsp=@apache-mynewt-core/hw/bsp/telee02\n$ newt target set lora_app_shell_telee02 app=@apache-mynewt-core/apps/lora_app_shell\n$ newt target set lora_app_shell_telee02 build_profile=optimized\n\n\n\n\n\nThe lora app shell application requires a few additional system configuration variables. \nCreate and edit a file called syscfg.yml in dev/mylora/targets/lora_app_shell. The file\ncontents should be the following:\n\n\n### Package: targets/lora_app_shell_telee02\n\nsyscfg.vals:\n SHELL_CMD_ARGC_MAX: \n20\n\n LORA_MAC_TIMER_NUM: \n4\n\n TIMER_4: \n1\n\n\n\n\n\n\nYou can now \"display\" the targets you created to make sure they are correct:\n\n\n$ newt target show telee02_boot\ntargets/telee02_boot\n app=@apache-mynewt-core/apps/boot\n bsp=@apache-mynewt-core/hw/bsp/telee02\n build_profile=optimized\n\n$ newt target show lora_app_shell_telee02\ntargets/lora_app_shell_telee02\n app=@apache-mynewt-core/apps/lora_app_shell\n bsp=@apache-mynewt-core/hw/bsp/telee02\n build_profile=optimized\n syscfg=LORA_MAC_TIMER_NUM=4:SHELL_CMD_ARGC_MAX=20:TIMER_4=1\n\n\n\n\n\n\nNote: If you've already built and installed a bootloader for your ee02 module then you do\nnot need to create a target for it here, or build and load it as below. \n\n\n\n\nBuild the target executables\n\n\n$ newt clean telee02_boot\n$ newt clean telee02_boot\nBuilding target targets/telee02_boot\nCompiling repos/apache-mynewt-core/boot/bootutil/src/image_rsa.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/image_ec.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/image_ec256.c \n\n . . .\n\nArchiving telee02_boot-sysinit-app.a\nArchiving util_mem.a\nLinking /Users/wes/dev/wes/bin/targets/telee02_boot/app/apps/boot/boot.elf\nTarget successfully built: targets/telee02_boot\n\n$ newt clean lora_app_shell_telee02\n$ newt build lora_app_shell_telee02\nBuilding target targets/lora_app_shell_telee02\nAssembling repos/apache-mynewt-core/hw/bsp/telee02/src/arch/cortex_m4/gcc_startup_nrf52_split.s\nCompiling repos/apache-mynewt-core/encoding/base64/src/hex.c\nCompiling repos/apache-mynewt-core/encoding/base64/src/base64.c\n . . .\n\n\nArchiving util_mem.a\nArchiving util_parse.a\nLinking /Users/wes/dev/wes/bin/targets/lora_app_shell_telee02/app/apps/lora_app_shell/lora_app_shell.elf\nTarget successfully built: targets/lora_app_shell_telee0\n\n\n\n\n\n\nNote: The newt clean step is not necessary but shown here for good measure. \n\n\n\n\nSign and create the application image\n\n\nYou must sign and version your application image to download it using newt to the board. \nUse the newt create-image command to perform this action. You may assign an arbitrary \nversion (e.g. 1.0.0) to the image.\n\n\n$ newt create-image lora_app_shell_telee02 0.0.0\nApp image succesfully generated: /Users/wes/dev/wes/bin/targets/lora_app_shell_telee02/app/apps/lora_app_shell/lora_app_shell.img\n\n\n\n\n\n\nNote: Only the application image requires this step; the bootloader does not \n\n\n\n\nConnect the board\n\n\nConnect the evaluation board via micro-USB to your PC via USB cable. Connect the Segger J-link debugger to the 9-pin\nSWD connector. Connect the UART pins (RX, TX and GND) to the board. Terminal settings 115200, N, 8, 1.\n\n\n\n\nDownload bootloader and application\n\n\n\n\nNote:\n If you want to erase the flash and load the image again, you can use JLinkExe to issue an \nerase\n command.\n\n\n$ JLinkExe -device nRF52 -speed 4000 -if SWD\nSEGGER J-Link Commander V5.12c (Compiled Apr 21 2016 16:05:51)\nDLL version V5.12c, compiled Apr 21 2016 16:05:45\n\nConnecting to J-Link via USB...O.K.\nFirmware: J-Link OB-SAM3U128-V2-NordicSemi compiled Mar 15 2016 18:03:17\nHardware version: V1.00\nS/N: 682863966\nVTref = 3.300V\n\n\nType \nconnect\n to establish a target connection, \n?\n for help\nJ-Link\nerase\nCortex-M4 identified.\nErasing device (0;?i?)...\nComparing flash [100%] Done.\nErasing flash [100%] Done.\nVerifying flash [100%] Done.\nJ-Link: Flash download: Total time needed: 0.363s (Prepare: 0.093s, Compare: 0.000s, Erase: 0.262s, Program: 0.000s, Verify: 0.000s, Restore: 0.008s)\nErasing done.\nJ-Link\nexit\n$\n\n\n\n\n\n$ newt load telee02_boot\nLoading bootloader\n$ newt load lora_app_shell_telee02\nLoading app image into slot 1\n\n\n\n\n\nAssuming you attached the serial port and have a terminal up you should set the following output on the terminal:\n\n\n000002 lora_app_shell\n\n\n\n\n\n\n\nShell Commands\n\n\nThere are a number of shell commands that will allow you to join and send both unconfirmed and confirmed data. If you type 'help' in your terminal you will see the various commands displayed. Here is a screen shot of the output of help\n\n\n000002 lora_app_shell\nhelp\n\n032766 help\n032766 stat \n032767 tasks \n032768 mpool \n032769 date \n032770 las_wr_mib \n032771 las_rd_mib \n032772 las_rd_dev_eui \n032773 las_wr_dev_eui \n032774 las_rd_app_eui \n032775 las_wr_app_eui \n032776 las_rd_app_key \n032777 las_wr_app_key \n032778 las_app_port \n032779 las_app_tx \n032780 las_join \n032781 las_link_chk \n032782 compat\n \n\n\n\n\n\nThe following table lists the commands and gives a brief description of the commands. The lora commands are described in more detail later in the tutorial as well as their syntax (syntax not shown in the table).\n\n\n\n\n\n\n\n\nCommand\n\n\nDescription\n\n\n\n\n\n\n\n\n\n\nhelp\n\n\nDisplay list of available shell commands\n\n\n\n\n\n\nstat\n\n\nDisplay statistics. Syntax: stat \\\nstatistics group>. 'stat' with no group displays avaialable groups\n\n\n\n\n\n\ntasks\n\n\nDisplay OS tasks\n\n\n\n\n\n\nmpool\n\n\nDisplays OS memory pools and memory pool statistics\n\n\n\n\n\n\ndate\n\n\nDisplays current date/time\n\n\n\n\n\n\nlas_wr_mib\n\n\nWrite lora MIB\n\n\n\n\n\n\nlas_rd_mib\n\n\nRead lora MIB\n\n\n\n\n\n\nlas_rd_dev_eui\n\n\nRead lora device EUI\n\n\n\n\n\n\nlas_wr_dev_eui\n\n\nWrite lora device EUI\n\n\n\n\n\n\nlas_rd_app_eui\n\n\nRead lora application EUI\n\n\n\n\n\n\nlas_wr_app_eui\n\n\nWrite lora application EUI\n\n\n\n\n\n\nlas_rd_app_key\n\n\nRead lora application key\n\n\n\n\n\n\nlas_wr_app_key\n\n\nWrite lora application key\n\n\n\n\n\n\nlas_app_port\n\n\nOpen/close lora application port\n\n\n\n\n\n\nlas_app_tx\n\n\nTransmit on lora application port\n\n\n\n\n\n\nlas_join\n\n\nPerform a lora OTA join\n\n\n\n\n\n\nlas_link_chk\n\n\nPerform a lora link check\n\n\n\n\n\n\n\n\nOTA Join\n\n\nBefore sending any application data a lora end device must be joined to its lora network. To perform a lora OTA (over-the-air) join there are some commands that must be issued prior to attempting to join. The reason for these commands is that a lora end device must be configured with a device EUI, application EUI and application key prior to performing an OTA join.\n\n\n598763 compat\n las_wr_app_eui 0x00:0x11:0x22:0x01:0x01:0x00:0x10:10\n\n623106 compat\n las_wr_app_key 03:03:03:03:03:03:03:03:03:03:03:03:03:03:03:03\n\n623758 compat\n las_wr_dev_eui 0x00:0x11:0x22:0x02:0x02:0x00:0x00:0x00\n\n630333 compat\n las_join 1\n\n630634 Attempting to join...\n019802 compat\n Join cb. status=0 attempts=1\n\n\n\n\n\nIf the join is successful the status returned should be 0. If it fails the status will be a non-zero lora status code (lora status error codes are described later in this tutorial).\n\n\nA note about \"endianness\" in the device EUI commands. The first three bytes of the EUI are the OUI and the last 5 bytes are unique (for that OUI). The above example assumes an OUI of 001122. This is not the same order as the address over the air as device addresses are sent \"least significant byte\" first (little endian). The same convention also applies to keys: they are in big-endian order in the command but sent little endian over the air.\n\n\n\nOpening/closing an application port\n\n\nAnother step that must be performed prior to sending application data is to open an application port. All data frames containing application data are sent to a specific port. Port numbers are in the range 1 - 223 as port 0 is reserved for MLME-related activities. Ports 224-255 are reserved for future standardized application extensions.\n\n\nThe lora app shell does not open any application ports by default.\n\n\nTo open and/or close an application port the following commands are used. Note that the application port which you are using to send data must be open if you want to send data (or receive it).\n\n\n115647 compat\n las_app_port open 1\n\n150958 Opened app port 1\n150958 compat\n las_app_port close 1\n\n151882 Closed app port 1\n\n\n\n\n\n\n\nSending data\n\n\nThe lora app shell allows the user to send both unconfirmed and confirmed data. The command to send data is \nlas_app_tx \\\nport> \\\nlen> \\\ntype>\n\n\nNOTE: the current usage for this command shows an optional data rate and retries for this command. That feature has not been implemented and the command will not be accepted if they are separated.\n\n\nWhere:\n port = port number on which to send\n len = size n bytes of app data\n type = 0 for unconfirmed, 1 for confirmed\n\n\nTo send a confirmed data transmission of size 5 bytes on port 10 the command would be: las_app_tx 10 20 1\n\n\nOnce the end device has sent the frame requested there should be a message which contains some additional information. Here is a screen shot using the above example. Note that there will be some delay between seeing the \"Packet sent on port 10\" message and the additional information as the additional information is the \"confirmation\" that the lora stack provides and the confirmation will not be returned until the lora stack is finished transmitting the frame and has received an acknowledgement or has finished waiting for all the receive windows.\n\n\n449751 compat\n las_app_tx 10 5 1\n\n452144 Packet sent on port 10\n452144 compat\n Txd on port 10 type=conf status=0 len=5\n452325 dr:0\n452325 txpower:5\n452325 tries:1\n452326 ack_rxd:1\n452326 tx_time_on_air:330\n452327 uplink_cntr:0\n452327 uplink_freq:903500000\n\n\n\n\n\nThe information contained in the confirmation is the following:\n\n\ndr: The data rate on which the frame was sent.\n\ntxpower: Transmit power level of the device.\n\ntries: # of attempts made to transmit the frame successfully.\n\nack_rxd: Was an acknowledgement received (0 no 1 yes).\n\ntx_time_on_air: The on-air length of the frame (in milliseconds).\n\nuplink_cntr: The frame uplink counter that this frame used.\n\nuplink_freq: The frequency (logical) on which the frame was sent (in Hz).",
+ "text": "LoRaWAN App\n\n\n\n\nObjective\n\n\nThe purpose of this tutorial is to demonstrate how to build the lora app shell application for either a class A or class C lora device and to perform basic functions such as joining and sending data packets to a lora gateway/server.\n\n\nNOTE: This tutorial presumes that you have a running lora gateway and lora network server. No description of the gateway/server is provided. It is expected that the user understands how to configure and operate the gateway/server so that it can communicate with a class A or class C device.\n\n\n\n\nHardware needed\n\n\n\n\nTelenor EE02 module\n\n\nSegger J-Link or similar debugger\n\n\nLORA gateway\n\n\nLaptop running Mac OS\n\n\nIt is assumed you have already installed newt tool. \n\n\nIt is assumed you understand the basics of the mynewt OS\n\n\n3-wire serial cable to connect telenor module to your laptop\n\n\nSome form of terminal emulation application running on your laptop.\n\n\n\n\n\n\nCreate a project.\n\n\nCreate a new project to hold your work. For a deeper understanding, you can read about project creation in \n\nGet Started -- Creating Your First Project\n\nor just follow the commands below.\n\n\n $ mkdir ~/dev\n $ cd ~/dev\n $ newt new mylora\n Downloading project skeleton from apache/mynewt-blinky...\n Installing skeleton in mylora...\n Project mylora successfully created.\n $ cd mylora\n\n\n\n\n\n\n\nInstall Everything\n\n\nNow that you have defined the needed repositories, it's time to install everything so\nthat you can get started.\n\n\n $ newt install -v \n apache-mynewt-core\n Downloading repository description for apache-mynewt-core... success!\n ...\n apache-mynewt-core successfully installed version 1.2.0-none\n ...\n\n\n\n\n\n\n\nCreate the targets\n\n\nCreate two targets - one for the bootloader and one for the lora app shell application. \n\n\n$ newt target create telee02_boot\n$ newt target set telee02_boot bsp=@apache-mynewt-core/hw/bsp/telee02\n$ newt target set telee02_boot app=@apache-mynewt-core/apps/boot\n$ newt target set telee02_boot build_profile=optimized\n\n$ newt target create lora_app_shell_telee02\n$ newt target set lora_app_shell_telee02 bsp=@apache-mynewt-core/hw/bsp/telee02\n$ newt target set lora_app_shell_telee02 app=@apache-mynewt-core/apps/lora_app_shell\n$ newt target set lora_app_shell_telee02 build_profile=optimized\n\n\n\n\n\nThe lora app shell application requires a few additional system configuration variables. \nCreate and edit a file called syscfg.yml in dev/mylora/targets/lora_app_shell. The file\ncontents should be the following:\n\n\n### Package: targets/lora_app_shell_telee02\n\nsyscfg.vals:\n SHELL_CMD_ARGC_MAX: \n20\n\n LORA_MAC_TIMER_NUM: \n4\n\n TIMER_4: \n1\n\n\n\n\n\n\nYou can now \"display\" the targets you created to make sure they are correct:\n\n\n$ newt target show telee02_boot\ntargets/telee02_boot\n app=@apache-mynewt-core/apps/boot\n bsp=@apache-mynewt-core/hw/bsp/telee02\n build_profile=optimized\n\n$ newt target show lora_app_shell_telee02\ntargets/lora_app_shell_telee02\n app=@apache-mynewt-core/apps/lora_app_shell\n bsp=@apache-mynewt-core/hw/bsp/telee02\n build_profile=optimized\n syscfg=LORA_MAC_TIMER_NUM=4:SHELL_CMD_ARGC_MAX=20:TIMER_4=1\n\n\n\n\n\n\nNote: If you've already built and installed a bootloader for your ee02 module then you do\nnot need to create a target for it here, or build and load it as below. \n\n\n\n\nBuild the target executables\n\n\n$ newt clean telee02_boot\n$ newt build telee02_boot\nBuilding target targets/telee02_boot\nCompiling repos/apache-mynewt-core/boot/bootutil/src/image_rsa.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/image_ec.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/image_ec256.c \n\n . . .\n\nArchiving telee02_boot-sysinit-app.a\nArchiving util_mem.a\nLinking /Users/wes/dev/wes/bin/targets/telee02_boot/app/apps/boot/boot.elf\nTarget successfully built: targets/telee02_boot\n\n$ newt clean lora_app_shell_telee02\n$ newt build lora_app_shell_telee02\nBuilding target targets/lora_app_shell_telee02\nAssembling repos/apache-mynewt-core/hw/bsp/telee02/src/arch/cortex_m4/gcc_startup_nrf52_split.s\nCompiling repos/apache-mynewt-core/encoding/base64/src/hex.c\nCompiling repos/apache-mynewt-core/encoding/base64/src/base64.c\n . . .\n\n\nArchiving util_mem.a\nArchiving util_parse.a\nLinking /Users/wes/dev/wes/bin/targets/lora_app_shell_telee02/app/apps/lora_app_shell/lora_app_shell.elf\nTarget successfully built: targets/lora_app_shell_telee0\n\n\n\n\n\n\nNote: The newt clean step is not necessary but shown here for good measure. \n\n\n\n\nSign and create the application image\n\n\nYou must sign and version your application image to download it using newt to the board. \nUse the newt create-image command to perform this action. You may assign an arbitrary \nversion (e.g. 1.0.0) to the image.\n\n\n$ newt create-image lora_app_shell_telee02 0.0.0\nApp image succesfully generated: /Users/wes/dev/wes/bin/targets/lora_app_shell_telee02/app/apps/lora_app_shell/lora_app_shell.img\n\n\n\n\n\n\nNote: Only the application image requires this step; the bootloader does not \n\n\n\n\nConnect the board\n\n\nConnect the evaluation board via micro-USB to your PC via USB cable. Connect the Segger J-link debugger to the 9-pin\nSWD connector. Connect the UART pins (RX, TX and GND) to the board. Terminal settings 115200, N, 8, 1.\n\n\n\n\nDownload bootloader and application\n\n\n\n\nNote:\n If you want to erase the flash and load the image again, you can use JLinkExe to issue an \nerase\n command.\n\n\n$ JLinkExe -device nRF52 -speed 4000 -if SWD\nSEGGER J-Link Commander V5.12c (Compiled Apr 21 2016 16:05:51)\nDLL version V5.12c, compiled Apr 21 2016 16:05:45\n\nConnecting to J-Link via USB...O.K.\nFirmware: J-Link OB-SAM3U128-V2-NordicSemi compiled Mar 15 2016 18:03:17\nHardware version: V1.00\nS/N: 682863966\nVTref = 3.300V\n\n\nType \nconnect\n to establish a target connection, \n?\n for help\nJ-Link\nerase\nCortex-M4 identified.\nErasing device (0;?i?)...\nComparing flash [100%] Done.\nErasing flash [100%] Done.\nVerifying flash [100%] Done.\nJ-Link: Flash download: Total time needed: 0.363s (Prepare: 0.093s, Compare: 0.000s, Erase: 0.262s, Program: 0.000s, Verify: 0.000s, Restore: 0.008s)\nErasing done.\nJ-Link\nexit\n$\n\n\n\n\n\n$ newt load telee02_boot\nLoading bootloader\n$ newt load lora_app_shell_telee02\nLoading app image into slot 1\n\n\n\n\n\nAssuming you attached the serial port and have a terminal up you should set the following output on the terminal:\n\n\n000002 lora_app_shell\n\n\n\n\n\n\n\nShell Commands\n\n\nThere are a number of shell commands that will allow you to join and send both unconfirmed and confirmed data. If you type 'help' in your terminal you will see the various commands displayed. Here is a screen shot of the output of help\n\n\n000002 lora_app_shell\nhelp\n\n032766 help\n032766 stat \n032767 tasks \n032768 mpool \n032769 date \n032770 las_wr_mib \n032771 las_rd_mib \n032772 las_rd_dev_eui \n032773 las_wr_dev_eui \n032774 las_rd_app_eui \n032775 las_wr_app_eui \n032776 las_rd_app_key \n032777 las_wr_app_key \n032778 las_app_port \n032779 las_app_tx \n032780 las_join \n032781 las_link_chk \n032782 compat\n \n\n\n\n\n\nThe following table lists the commands and gives a brief description of the commands. The lora commands are described in more detail later in the tutorial as well as their syntax (syntax not shown in the table).\n\n\n\n\n\n\n\n\nCommand\n\n\nDescription\n\n\n\n\n\n\n\n\n\n\nhelp\n\n\nDisplay list of available shell commands\n\n\n\n\n\n\nstat\n\n\nDisplay statistics. Syntax: stat \\\nstatistics group>. 'stat' with no group displays avaialable groups\n\n\n\n\n\n\ntasks\n\n\nDisplay OS tasks\n\n\n\n\n\n\nmpool\n\n\nDisplays OS memory pools and memory pool statistics\n\n\n\n\n\n\ndate\n\n\nDisplays current date/time\n\n\n\n\n\n\nlas_wr_mib\n\n\nWrite lora MIB\n\n\n\n\n\n\nlas_rd_mib\n\n\nRead lora MIB\n\n\n\n\n\n\nlas_rd_dev_eui\n\n\nRead lora device EUI\n\n\n\n\n\n\nlas_wr_dev_eui\n\n\nWrite lora device EUI\n\n\n\n\n\n\nlas_rd_app_eui\n\n\nRead lora application EUI\n\n\n\n\n\n\nlas_wr_app_eui\n\n\nWrite lora application EUI\n\n\n\n\n\n\nlas_rd_app_key\n\n\nRead lora application key\n\n\n\n\n\n\nlas_wr_app_key\n\n\nWrite lora application key\n\n\n\n\n\n\nlas_app_port\n\n\nOpen/close lora application port\n\n\n\n\n\n\nlas_app_tx\n\n\nTransmit on lora application port\n\n\n\n\n\n\nlas_join\n\n\nPerform a lora OTA join\n\n\n\n\n\n\nlas_link_chk\n\n\nPerform a lora link check\n\n\n\n\n\n\n\n\nOTA Join\n\n\nBefore sending any application data a lora end device must be joined to its lora network. To perform a lora OTA (over-the-air) join there are some commands that must be issued prior to attempting to join. The reason for these commands is that a lora end device must be configured with a device EUI, application EUI and application key prior to performing an OTA join.\n\n\n598763 compat\n las_wr_app_eui 0x00:0x11:0x22:0x01:0x01:0x00:0x10:10\n\n623106 compat\n las_wr_app_key 03:03:03:03:03:03:03:03:03:03:03:03:03:03:03:03\n\n623758 compat\n las_wr_dev_eui 0x00:0x11:0x22:0x02:0x02:0x00:0x00:0x00\n\n630333 compat\n las_join 1\n\n630634 Attempting to join...\n019802 compat\n Join cb. status=0 attempts=1\n\n\n\n\n\nIf the join is successful the status returned should be 0. If it fails the status will be a non-zero lora status code (lora status error codes are described later in this tutorial).\n\n\nA note about \"endianness\" in the device EUI commands. The first three bytes of the EUI are the OUI and the last 5 bytes are unique (for that OUI). The above example assumes an OUI of 001122. This is not the same order as the address over the air as device addresses are sent \"least significant byte\" first (little endian). The same convention also applies to keys: they are in big-endian order in the command but sent little endian over the air.\n\n\n\nOpening/closing an application port\n\n\nAnother step that must be performed prior to sending application data is to open an application port. All data frames containing application data are sent to a specific port. Port numbers are in the range 1 - 223 as port 0 is reserved for MLME-related activities. Ports 224-255 are reserved for future standardized application extensions.\n\n\nThe lora app shell does not open any application ports by default.\n\n\nTo open and/or close an application port the following commands are used. Note that the application port which you are using to send data must be open if you want to send data (or receive it).\n\n\n115647 compat\n las_app_port open 1\n\n150958 Opened app port 1\n150958 compat\n las_app_port close 1\n\n151882 Closed app port 1\n\n\n\n\n\n\n\nSending data\n\n\nThe lora app shell allows the user to send both unconfirmed and confirmed data. The command to send data is \nlas_app_tx \\\nport> \\\nlen> \\\ntype>\n\n\nNOTE: the current usage for this command shows an optional data rate and retries for this command. That feature has not been implemented and the command will not be accepted if they are separated.\n\n\nWhere:\n port = port number on which to send\n len = size n bytes of app data\n type = 0 for unconfirmed, 1 for confirmed\n\n\nTo send a confirmed data transmission of size 5 bytes on port 10 the command would be: las_app_tx 10 20 1\n\n\nOnce the end device has sent the frame requested there should be a message which contains some additional information. Here is a screen shot using the above example. Note that there will be some delay between seeing the \"Packet sent on port 10\" message and the additional information as the additional information is the \"confirmation\" that the lora stack provides and the confirmation will not be returned until the lora stack is finished transmitting the frame and has received an acknowledgement or has finished waiting for all the receive windows.\n\n\n449751 compat\n las_app_tx 10 5 1\n\n452144 Packet sent on port 10\n452144 compat\n Txd on port 10 type=conf status=0 len=5\n452325 dr:0\n452325 txpower:5\n452325 tries:1\n452326 ack_rxd:1\n452326 tx_time_on_air:330\n452327 uplink_cntr:0\n452327 uplink_freq:903500000\n\n\n\n\n\nThe information contained in the confirmation is the following:\n\n\ndr: The data rate on which the frame was sent.\n\ntxpower: Transmit power level of the device.\n\ntries: # of attempts made to transmit the frame successfully.\n\nack_rxd: Was an acknowledgement received (0 no 1 yes).\n\ntx_time_on_air: The on-air length of the frame (in milliseconds).\n\nuplink_cntr: The frame uplink counter that this frame used.\n\nuplink_freq: The frequency (logical) on which the frame was sent (in Hz).",
"title": "LoraWAN app"
},
{
@@ -1627,7 +1627,7 @@
},
{
"location": "/os/tutorials/lora/lorawanapp/#build-the-target-executables",
- "text": "$ newt clean telee02_boot\n$ newt clean telee02_boot\nBuilding target targets/telee02_boot\nCompiling repos/apache-mynewt-core/boot/bootutil/src/image_rsa.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/image_ec.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/image_ec256.c \n\n . . .\n\nArchiving telee02_boot-sysinit-app.a\nArchiving util_mem.a\nLinking /Users/wes/dev/wes/bin/targets/telee02_boot/app/apps/boot/boot.elf\nTarget successfully built: targets/telee02_boot\n\n$ newt clean lora_app_shell_telee02\n$ newt build lora_app_shell_telee02\nBuilding target targets/lora_app_shell_telee02\nAssembling repos/apache-mynewt-core/hw/bsp/telee02/src/arch/cortex_m4/gcc_startup_nrf52_split.s\nCompiling repos/apache-mynewt-core/encoding/base64/src/hex.c\nCompiling repos/apache-mynewt-core/encoding/base64/src/base64.c\n . . .\n\n\nArchiving util_mem.a\nArchiving util_parse.a\nLinking /Users/wes/dev/wes/bin/targets/lora_app_shell_telee02/app/apps/lora_app_shell/lora_app_shell.elf\nTarget successfully built: targets/lora_app_shell_telee0 \nNote: The newt clean step is not necessary but shown here for good measure.",
+ "text": "$ newt clean telee02_boot\n$ newt build telee02_boot\nBuilding target targets/telee02_boot\nCompiling repos/apache-mynewt-core/boot/bootutil/src/image_rsa.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/image_ec.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/image_ec256.c \n\n . . .\n\nArchiving telee02_boot-sysinit-app.a\nArchiving util_mem.a\nLinking /Users/wes/dev/wes/bin/targets/telee02_boot/app/apps/boot/boot.elf\nTarget successfully built: targets/telee02_boot\n\n$ newt clean lora_app_shell_telee02\n$ newt build lora_app_shell_telee02\nBuilding target targets/lora_app_shell_telee02\nAssembling repos/apache-mynewt-core/hw/bsp/telee02/src/arch/cortex_m4/gcc_startup_nrf52_split.s\nCompiling repos/apache-mynewt-core/encoding/base64/src/hex.c\nCompiling repos/apache-mynewt-core/encoding/base64/src/base64.c\n . . .\n\n\nArchiving util_mem.a\nArchiving util_parse.a\nLinking /Users/wes/dev/wes/bin/targets/lora_app_shell_telee02/app/apps/lora_app_shell/lora_app_shell.elf\nTarget successfully built: targets/lora_app_shell_telee0 \nNote: The newt clean step is not necessary but shown here for good measure.",
"title": "Build the target executables"
},
{
@@ -13292,12 +13292,12 @@
},
{
"location": "/newtmgr/install_mac/",
- "text": "Installing Newtmgr on Mac OS\n\n\nNewtmgr is supported on Mac OS X 64 bit platforms and has been tested on Mac OS 10.11 and higher.\n\n\nThis page shows you how to install the following versions of newtmgr:\n\n\n\n\nUpgrade to or install the latest release version (1.2.0).\n\n\nInstall the latest from the master branch (unstable).\n\n\n\n\nSee \nInstalling Previous Releases of Newtmgr\n to install an earlier version of newtmgr.\n\n\nNote:\n If you would like to contribute to the newtmgr tool, see \nSetting Up Go Environment to Contribute to Newt and Newtmgr Tools\n.\n\n\nAdding the Mynewt Homebrew Tap\n\n\nYou should have added the \nruntimeco/homebrew-mynewt\n tap when you installed the \nnewt\n tool. Run the following commands if you have not done so:\n\n\n$ brew tap runtimeco/homebrew-mynewt\n$ brew update\n\n\n\n\n\nUpgrading to or Installing the Latest Release Version\n\n\nPerform the following to upgrade or install the latest release version of newtmgr.\n\n\nUpgrading to the Latest Release Version of Newtmgr\n\n\nIf you have installed an earlier version of newtmgr using brew, run the following commands to upgrade to the latest version of newtmgr:\n\n\n$ brew update\n$ brew upgrade mynewt-newtmgr\n\n\n\n\n\n\n\nInstalling the Latest Release Version of Newtmgr\n\n\nRun the following command to install the latest release version of newtmgr:\n\n\n$ brew update\n$ brew install mynewt-newtmgr\n==\n Installing mynewt-newtmgr from runtimeco/mynewt\n==\n Downloading https://github.com/runtimeco/binary-releases/raw/master/mynewt-newt-tools_1.2.0/mynewt-newtmgr-1.2.0.sierra.bottle.tar.gz\n==\n Downloading from https://raw.githubusercontent.com/runtimeco/binary-releases/master/mynewt-newt-tools_1.2.0/mynewt-newtmgr-1.2.0.sierra.bottle.tar.gz\n######################################################################## 100.0%\n==\n Pouring mynewt-newtmgr-1.2.0.sierra.bottle.tar.gz\n\ud83c\udf7a /usr/local/Cellar/mynewt-newtmgr/1.2.0: 3 files, 17.3MB\n\n\n\n\n\n\n\nNotes:\n Homebrew bottles for newtmgr 1.2.0 are available for Mac OS Sierra, El Captian. If you are running an earlier version of Mac OS, the installation will install the latest version of Go and compile newtmgr locally.\n\n\n\n\nChecking the Installed Version\n\n\nCheck that you are using the installed version of newtmgr:\n\n\n$which newtmgr\n/usr/local/bin/newtmgr\nls -l /usr/local/bin/newtmgr\nlrwxr-xr-x 1 user staff 42 Sep 11 21:15 /usr/local/bin/newtmgr -\n ../Cellar/mynewt-newtmgr/1.2.0/bin/newtmgr\n\n\n\n\n\nNote:\n If you previously built newtmgr from source and the output of \nwhich newtmgr\n shows \"$GOPATH/bin/newtmgr\", you will need to move \"$GOPATH/bin\" after \"/usr/local/bin\" for your PATH in ~/.bash_profile, and source ~/.bash_profile.\n\n\n\nGet information about newtmgr:\n\n\n$ newtmgr help\nUsage:\n newtmgr [flags]\n newtmgr [command]\n\nAvailable Commands:\n config Read or write a config value on a device\n conn Manage newtmgr connection profiles\n crash Send a crash command to a device\n datetime Manage datetime on a device\n echo Send data to a device and display the echoed back data\n fs Access files on a device\n help Help about any command\n image Manage images on a device\n log Manage logs on a device\n mpstat Read mempool statistics from a device\n reset Perform a soft reset of a device\n run Run test procedures on a device\n stat Read statistics from a device\n taskstat Read task statistics from a device\n\nFlags:\n -c, --conn string connection profile to use\n -h, --help help for newtmgr\n -l, --loglevel string log level to use (default \ninfo\n)\n --name string name of target BLE device; overrides profile setting\n -t, --timeout float timeout in seconds (partial seconds allowed) (default 10)\n -r, --tries int total number of tries in case of timeout (default 1)\n\nUse \nnewtmgr [command] --help\n for more information about a command.\n\n\n\n\n\n\n\nInstalling Newtmgr from the Master Branch\n\n\nWe recommend that you use the latest release version of newtmgr. If you would like to use the master branch with the latest updates, you can install newtmgr from the HEAD of the master branch. \n\n\n Notes: \n\n\n\n\nThe master branch may be unstable.\n\n\nThis installation will install the latest version of Go on your computer, if it is not installed, and compile newtmgr locally. \n\n\n\n\n\nIf you already installed newtgmr, unlink the current version:\n\n\n$brew unlink mynewt-newtmgr\n\n\n\n\n\n\nInstall the latest unstable version of newtmgr from the master branch:\n\n\n$brew install mynewt-newtmgr --HEAD\n==\n Installing mynewt-newtmgr from runtimeco/mynewt\n==\n Cloning https://github.com/apache/mynewt-newtmgr.git\nCloning into \n/Users/wanda/Library/Caches/Homebrew/mynewt-newtmgr--git\n...\nremote: Counting objects: 2169, done.\nremote: Compressing objects: 100% (1752/1752), done.\nremote: Total 2169 (delta 379), reused 2042 (delta 342), pack-reused 0\nReceiving objects: 100% (2169/2169), 8.13 MiB | 5.47 MiB/s, done.\nResolving deltas: 100% (379/379), done.\n==\n Checking out branch master\n==\n go get github.com/currantlabs/ble\n==\n go get github.com/raff/goble\n==\n go get github.com/mgutz/logxi/v1\n==\n go install\n\ud83c\udf7a /usr/local/Cellar/mynewt-newtmgr/HEAD-2d5217f: 3 files, 17.3MB, built in 1 minute 10 seconds\n\n\n\n\n\n\nTo switch back to the latest stable release version of newtmgr, you can run:\n\n\n$brew switch mynewt-newtmgr 1.2.0\nCleaning /usr/local/Cellar/mynewt-newtmgr/1.2.0\nCleaning /usr/local/Cellar/mynewt-newtmgr/HEAD-2d5217f\n1 links created for /usr/local/Cellar/mynewt-newtmgr/1.2.0",
+ "text": "Installing Newtmgr on Mac OS\n\n\nNewtmgr is supported on Mac OS X 64 bit platforms and has been tested on Mac OS Sierra.\n\n\nThis page shows you how to install the following versions of newtmgr:\n\n\n\n\nUpgrade to or install the latest release version (1.2.0).\n\n\nInstall the latest from the master branch (unstable).\n\n\n\n\nSee \nInstalling Previous Releases of Newtmgr\n to install an earlier version of newtmgr.\n\n\nNote:\n If you would like to contribute to the newtmgr tool, see \nSetting Up Go Environment to Contribute to Newt and Newtmgr Tools\n.\n\n\nAdding the Mynewt Homebrew Tap\n\n\nYou should have added the \nruntimeco/homebrew-mynewt\n tap when you installed the \nnewt\n tool. Run the following commands if you have not done so:\n\n\n$ brew tap runtimeco/homebrew-mynewt\n$ brew update\n\n\n\n\n\nUpgrading to or Installing the Latest Release Version\n\n\nPerform the following to upgrade or install the latest release version of newtmgr.\n\n\nUpgrading to the Latest Release Version of Newtmgr\n\n\nIf you have installed an earlier version of newtmgr using brew, run the following commands to upgrade to the latest version of newtmgr:\n\n\n$ brew update\n$ brew upgrade mynewt-newtmgr\n\n\n\n\n\n\n\nInstalling the Latest Release Version of Newtmgr\n\n\nRun the following command to install the latest release version of newtmgr:\n\n\n$ brew update\n$ brew install mynewt-newtmgr\n\n\n\n\n\n\n\nNotes:\n Homebrew bottles for newtmgr 1.2.0 are available for Mac OS Sierra. If you are running an earlier version of Mac OS, the installation will install the latest version of Go and compile newtmgr locally.\n\n\n\n\nChecking the Installed Version\n\n\nCheck that you are using the installed version of newtmgr:\n\n\n$which newtmgr\n/usr/local/bin/newtmgr\n\n\n\n\n\nNote:\n If you previously built newtmgr from source and the output of \nwhich newtmgr\n shows \"$GOPATH/bin/newtmgr\", you will need to move \"$GOPATH/bin\" after \"/usr/local/bin\" for your PATH in ~/.bash_profile, and source ~/.bash_profile.\n\n\n\nGet information about newtmgr:\n\n\n$ newtmgr help\nUsage:\n newtmgr [flags]\n newtmgr [command]\n\nAvailable Commands:\n config Read or write a config value on a device\n conn Manage newtmgr connection profiles\n crash Send a crash command to a device\n datetime Manage datetime on a device\n echo Send data to a device and display the echoed back data\n fs Access files on a device\n help Help about any command\n image Manage images on a device\n log Manage logs on a device\n mpstat Read mempool statistics from a device\n reset Perform a soft reset of a device\n run Run test procedures on a device\n stat Read statistics from a device\n taskstat Read task statistics from a device\n\nFlags:\n -c, --conn string connection profile to use\n -h, --help help for newtmgr\n -l, --loglevel string log level to use (default \ninfo\n)\n --name string name of target BLE device; overrides profile setting\n -t, --timeout float timeout in seconds (partial seconds allowed) (default 10)\n -r, --tries int total number of tries in case of timeout (default 1)\n\nUse \nnewtmgr [command] --help\n for more information about a command.\n\n\n\n\n\n\n\nInstalling Newtmgr from the Master Branch\n\n\nWe recommend that you use the latest release version of newtmgr. If you would like to use the master branch with the latest updates, you can install newtmgr from the HEAD of the master branch. \n\n\n Notes: \n\n\n\n\nThe master branch may be unstable.\n\n\nThis installation will install the latest version of Go on your computer, if it is not installed, and compile newtmgr locally. \n\n\n\n\n\nIf you already installed newtgmr, unlink the current version:\n\n\n$brew unlink mynewt-newtmgr\n\n\n\n\n\n\nInstall the latest unstable version of newtmgr from the master branch:\n\n\n$brew install mynewt-newtmgr --HEAD\n\n\n\n\n\n\nTo switch back to the latest stable release version of newtmgr, you can run:\n\n\n$brew switch mynewt-newtmgr 1.2.0",
"title": "Install Newtmgr On Mac OS"
},
{
"location": "/newtmgr/install_mac/#installing-newtmgr-on-mac-os",
- "text": "Newtmgr is supported on Mac OS X 64 bit platforms and has been tested on Mac OS 10.11 and higher. This page shows you how to install the following versions of newtmgr: Upgrade to or install the latest release version (1.2.0). Install the latest from the master branch (unstable). See Installing Previous Releases of Newtmgr to install an earlier version of newtmgr. Note: If you would like to contribute to the newtmgr tool, see Setting Up Go Environment to Contribute to Newt and Newtmgr Tools .",
+ "text": "Newtmgr is supported on Mac OS X 64 bit platforms and has been tested on Mac OS Sierra. This page shows you how to install the following versions of newtmgr: Upgrade to or install the latest release version (1.2.0). Install the latest from the master branch (unstable). See Installing Previous Releases of Newtmgr to install an earlier version of newtmgr. Note: If you would like to contribute to the newtmgr tool, see Setting Up Go Environment to Contribute to Newt and Newtmgr Tools .",
"title": "Installing Newtmgr on Mac OS"
},
{
@@ -13317,22 +13317,22 @@
},
{
"location": "/newtmgr/install_mac/#installing-the-latest-release-version-of-newtmgr",
- "text": "Run the following command to install the latest release version of newtmgr: $ brew update\n$ brew install mynewt-newtmgr\n== Installing mynewt-newtmgr from runtimeco/mynewt\n== Downloading https://github.com/runtimeco/binary-releases/raw/master/mynewt-newt-tools_1.2.0/mynewt-newtmgr-1.2.0.sierra.bottle.tar.gz\n== Downloading from https://raw.githubusercontent.com/runtimeco/binary-releases/master/mynewt-newt-tools_1.2.0/mynewt-newtmgr-1.2.0.sierra.bottle.tar.gz\n######################################################################## 100.0%\n== Pouring mynewt-newtmgr-1.2.0.sierra.bottle.tar.gz\n\ud83c\udf7a /usr/local/Cellar/mynewt-newtmgr/1.2.0: 3 files, 17.3MB Notes: Homebrew bottles for newtmgr 1.2.0 are available for Mac OS Sierra, El Captian. If you are running an earlier version of Mac OS, the installation will install the latest version of Go and compile newtmgr locally.",
+ "text": "Run the following command to install the latest release version of newtmgr: $ brew update\n$ brew install mynewt-newtmgr Notes: Homebrew bottles for newtmgr 1.2.0 are available for Mac OS Sierra. If you are running an earlier version of Mac OS, the installation will install the latest version of Go and compile newtmgr locally.",
"title": "Installing the Latest Release Version of Newtmgr"
},
{
"location": "/newtmgr/install_mac/#checking-the-installed-version",
- "text": "Check that you are using the installed version of newtmgr: $which newtmgr\n/usr/local/bin/newtmgr\nls -l /usr/local/bin/newtmgr\nlrwxr-xr-x 1 user staff 42 Sep 11 21:15 /usr/local/bin/newtmgr - ../Cellar/mynewt-newtmgr/1.2.0/bin/newtmgr Note: If you previously built newtmgr from source and the output of which newtmgr shows \"$GOPATH/bin/newtmgr\", you will need to move \"$GOPATH/bin\" after \"/usr/local/bin\" for your PATH in ~/.bash_profile, and source ~/.bash_profile. \nGet information about newtmgr: $ newtmgr help\nUsage:\n newtmgr [flags]\n newtmgr [command]\n\nAvailable Commands:\n config Read or write a config value on a device\n conn Manage newtmgr connection profiles\n crash Send a crash command to a device\n datetime Manage datetime on a device\n echo Send data to a device and display the echoed back data\n fs Access files on a device\n help Help about any command\n image Manage images on a device\n log Manage logs on a device\n mpstat Read mempool statistics from a device\n reset Perform a soft reset of a device\n run Run test procedures on a device\n stat Read statistics from a device\n taskstat Read task statistics from a device\n\nFlags:\n -c, --conn string connection profile to use\n -h, --help help for newtmgr\n -l, --loglevel string log level to use (default info )\n --name string name of target BLE device; overrides profile setting\n -t, --timeout float timeout in seconds (partial seconds allowed) (default 10)\n -r, --tries int total number of tries in case of timeout (default 1)\n\nUse newtmgr [command] --help for more information about a command.",
+ "text": "Check that you are using the installed version of newtmgr: $which newtmgr\n/usr/local/bin/newtmgr Note: If you previously built newtmgr from source and the output of which newtmgr shows \"$GOPATH/bin/newtmgr\", you will need to move \"$GOPATH/bin\" after \"/usr/local/bin\" for your PATH in ~/.bash_profile, and source ~/.bash_profile. \nGet information about newtmgr: $ newtmgr help\nUsage:\n newtmgr [flags]\n newtmgr [command]\n\nAvailable Commands:\n config Read or write a config value on a device\n conn Manage newtmgr connection profiles\n crash Send a crash command to a device\n datetime Manage datetime on a device\n echo Send data to a device and display the echoed back data\n fs Access files on a device\n help Help about any command\n image Manage images on a device\n log Manage logs on a device\n mpstat Read mempool statistics from a device\n reset Perform a soft reset of a device\n run Run test procedures on a device\n stat Read statistics from a device\n taskstat Read task statistics from a device\n\nFlags:\n -c, --conn string connection profile to use\n -h, --help help for newtmgr\n -l, --loglevel string log level to use (default info )\n --name string name of target BLE device; overrides profile setting\n -t, --timeout float timeout in seconds (partial seconds allowed) (default 10)\n -r, --tries int total number of tries in case of timeout (default 1)\n\nUse newtmgr [command] --help for more information about a command.",
"title": "Checking the Installed Version"
},
{
"location": "/newtmgr/install_mac/#installing-newtmgr-from-the-master-branch",
- "text": "We recommend that you use the latest release version of newtmgr. If you would like to use the master branch with the latest updates, you can install newtmgr from the HEAD of the master branch. Notes: The master branch may be unstable. This installation will install the latest version of Go on your computer, if it is not installed, and compile newtmgr locally. \nIf you already installed newtgmr, unlink the current version: $brew unlink mynewt-newtmgr \nInstall the latest unstable version of newtmgr from the master branch: $brew install mynewt-newtmgr --HEAD\n== Installing mynewt-newtmgr from runtimeco/mynewt\n== Cloning https://github.com/apache/mynewt-newtmgr.git\nCloning into /Users/wanda/Library/Caches/Homebrew/mynewt-newtmgr--git ...\nremote: Counting objects: 2169, done.\nremote: Compressing objects: 100% (1752/1752), done.\nremote: Total 2169 (delta 379), reused 2042 (delta 342), pack-reused 0\nReceiving objects: 100% (2169/2169), 8.13 MiB | 5.47 MiB/s, done.\nResolving deltas: 100% (379/379), done.\n== Checking out branch master\n== go get github.com/currantlabs/ble\n== go get github.com/raff/goble\n== go get github.com/mgutz/logxi/v1\n== go install\n\ud83c\udf7a /usr/local/Cellar/mynewt-newtmgr/HEAD-2d5217f: 3 files, 17.3MB, built in 1 minute 10 seconds \nTo switch back to the latest stable release version of newtmgr, you can run: $brew switch mynewt-newtmgr 1.2.0\nCleaning /usr/local/Cellar/mynewt-newtmgr/1.2.0\nCleaning /usr/local/Cellar/mynewt-newtmgr/HEAD-2d5217f\n1 links created for /usr/local/Cellar/mynewt-newtmgr/1.2.0",
+ "text": "We recommend that you use the latest release version of newtmgr. If you would like to use the master branch with the latest updates, you can install newtmgr from the HEAD of the master branch. Notes: The master branch may be unstable. This installation will install the latest version of Go on your computer, if it is not installed, and compile newtmgr locally. \nIf you already installed newtgmr, unlink the current version: $brew unlink mynewt-newtmgr \nInstall the latest unstable version of newtmgr from the master branch: $brew install mynewt-newtmgr --HEAD \nTo switch back to the latest stable release version of newtmgr, you can run: $brew switch mynewt-newtmgr 1.2.0",
"title": "Installing Newtmgr from the Master Branch"
},
{
"location": "/newtmgr/install_linux/",
- "text": "Installing Newtmgr on Linux\n\n\nYou can install the latest release (1.2.0) of the newtmgr tool from a Debian binary package (amd64). You can also download and build the latest release version of newtmgr from source. \n\n\nThis page shows you how to: \n\n\n\n\n\n\nSet up your computer to download Debian binary packages from the runtimeco APT repository.\n\n\nNote:\n The key for signing the repository has changed. If you set up your computer before release 1.1.0, you will need to download and import the public key again. \n\n\n\n\n\n\nInstall the latest release version of newtmgr from a Debian binary package. You can use apt-get to install the package or manually download and install the Debian binary package.\n\n\n\n\n\n\nDownload, build, and install the latest release version of newtmgr from source. \n\n\n\n\n\n\nSee \nInstalling Previous Releases of Newtgmr\n to install an earlier version of newtmgr.\n\n\nIf you are installing on an amd64 platform, we recommend that you install from the binary package.\n\n\nNote:\n We have tested the newtmgr tool binary and apt-get install from the runtimeco APT repository for Ubuntu version 16. Earlier Ubuntu versions (for example: Ubuntu 14) may have incompatibility with the repository. You can manually download and install the Debian binary package.\n\n\nNote:\n See \nSetting Up a Go Environment to Contribute to Newt and Newtmgr Tools\n if you want to: \n\n\n\n\nUse the newtmgr tool with the latest updates from the master branch. The master branch may be unstable and we recommend that you use the latest stable release version.\n\n\nContribute to the newtmgr tool. \n\n\n\n\n\n\nSetting Up Your Computer to use apt-get to Install the Package\n\n\nThe newtmgr Debian packages are stored in a private APT repository on \nhttps://github/runtimeco/debian-mynewt\n. To use apt-get, you must set up the following on your computer to retrieve packages from the repository:\n\n\nNote\n: You only need to perform this setup once on your computer. However, if you previously downloaded and imported the public key for the runtimeco APT repository, you will need to perform step 2 again as the key has changed.\n\n\n\n\nInstall the \napt-transport-https\n package to use HTTPS to retrieve packages. \n\n\nDownload the public key for the runtimeco APT repository and import the key into the apt keychain.\n\n\nAdd the repository for the binary and source packages to the apt source list.\n\n\n\n\n\n1. Install the apt-transport-https package:\n\n\n$sudo apt-get update\n$sudo apt-get install apt-transport-https\n\n\n\n\n\n\n2. Download the public key for the runtimeco apt repo (\nNote:\n There is a \n-\n after \napt-key add\n):\n\n\nwget -qO - https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/mynewt.gpg.key | sudo apt-key add -\n\n\n\n\n\n\n3. Add the repository for the binary packages to the \nmynewt.list\n apt source list file.\n\n\n$sudo -s\n[sudo] password for \nuser\n:\nroot$ cat \n /etc/apt/sources.list.d/mynewt.list \nEOF\ndeb https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest main\nEOF\nroot$exit\n\n\n\n\n\nNote:\n Do not forget to exit the root shell.\n\n\n\n4. Verify the content of the source list file:\n\n\n$more /etc/apt/sources.list.d/mynewt.list\ndeb https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest main\n\n\n\n\n\n\n5. Update the available packages:\n\n\n$sudo apt-get update\n\n\n\n\n\n\n\nNote:\n If you are not using Ubuntu version 16, you may see the following errors. We have provided instructions on how to manually download and install the binary package.\n\n\nW: Failed to fetch https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/dists/latest/main/source/Sources Ht\ntpError404\n\n\n\n\n\n \n\n\nInstalling the Latest Release of Newtmgr from a Binary Package\n\n\nYou can use either apt-get to install the package, or manually download and install the Debian binary package. \n\n\n\n\nMethod 1: Using apt-get to Upgrade or to Install\n\n\nRun the following commands to upgrade or install the latest version of newtmgr:\n\n\n$ sudo apt-get update \n$ sudo apt-get install newtmgr\n\n\n\n\n\nMethod 2: Downloading and Installing the Debian Package Manually\n\n\nDownload and install the package manually.\n\n\n$wget https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/pool/main/n/newtmgr/newtmgr_1.2.0-1_amd64.deb\n$sudo dpkg -i newtmgr_1.2.0-1_amd64.deb\n\n\n\n\n\nSee \nChecking the Installed Version of Newtmgr\n to verify that you are using the installed version of newtmgr.\n\n\n\n\nInstalling the Latest Release Version of Newtmgr from Source\n\n\nIf you are running Linux on a different architecture, you can build and install the latest release version of newtmgr from source.\n\n\n\n1. Download and install the latest version of \nGo\n. Newtmgr requires Go version 1.7.6 or higher.\n\n\n\n2. Create a Go workspace in the /tmp directory: \n\n\n$ cd /tmp\n$ mkdir go\n$ cd go\n$ export GOPATH=/tmp/go\n\n\n\n\n\n\n3. Run \ngo get\n to download the newtmgr source. Note that \ngo get\n pulls down the HEAD from the master branch in git, builds, and installs newtmgr.\n\n\n$ go get mynewt.apache.org/newtmgr/newtmgr\n$ ls -l /tmp/go/bin/newtmgr\n-rwxr-xr-x 1 user staff 17884488 Jul 29 16:25 /tmp/go/bin/newtmgr\n\n\n\n\n\n\n4. Check out the source from the latest release version:\n\n\n$ cd src/mynewt.apache.org/newtmgr\n$ git checkout mynewt_1_2_0_tag\nNote: checking out \nmynewt_1_2_0_tag\n.\n\n\n\n\n\n 5. Build newtmgr from the latest release version: \n\n\n$ cd newtmgr\n$ go install\n$ ls /tmp/go/bin/newtmgr\n-rwxr-xr-x 1 user staff 17888680 Jul 29 16:28 /tmp/go/bin/newtmgr\n\n\n\n\n\n\n6. If you have a Go workspace, remember to reset your GOPATH to your Go workspace.\n\n\n\n7. Copy the newtmgr executable to a bin directory in your path. You can put it in the /usr/bin or the $GOPATH/bin directory.\n\n\n\n\n Checking the Latest Version of Newtmgr is Installed\n\n\n\n1. Run \nwhich newtmgr\n to verify that you are using the installed version of newtmgr.\n\n\n\n2. Get information about the newtmgr tool:\n\n\n$newtmgr\nNewtmgr helps you manage remote devices running the Mynewt OS\n\nUsage:\n newtmgr [flags]\n newtmgr [command]\n\nAvailable Commands:\n config Read or write a config value on a device\n conn Manage newtmgr connection profiles\n crash Send a crash command to a device\n datetime Manage datetime on a device\n echo Send data to a device and display the echoed back data\n fs Access files on a device\n help Help about any command\n image Manage images on a device\n log Manage logs on a device\n mpstat Read mempool statistics from a device\n reset Perform a soft reset of a device\n run Run test procedures on a device\n stat Read statistics from a device\n taskstat Read task statistics from a device\n\nFlags:\n -c, --conn string connection profile to use\n -h, --help help for newtmgr\n -l, --loglevel string log level to use (default \ninfo\n)\n --name string name of target BLE device; overrides profile setting\n -t, --timeout float timeout in seconds (partial seconds allowed) (default 10)\n -r, --tries int total number of tries in case of timeout (default 1)\n\nUse \nnewtmgr [command] --help\n for more information about a command.",
+ "text": "Installing Newtmgr on Linux\n\n\nYou can install the latest release (1.2.0) of the newtmgr tool from a Debian binary package (amd64). You can also download and build the latest release version of newtmgr from source. \n\n\nThis page shows you how to: \n\n\n\n\n\n\nSet up your computer to download Debian binary packages from the runtimeco APT repository.\n\n\nNote:\n The key for signing the repository has changed. If you set up your computer before release 1.1.0, you will need to download and import the public key again. \n\n\n\n\n\n\nInstall the latest release version of newtmgr from a Debian binary package. You can use apt-get to install the package or manually download and install the Debian binary package.\n\n\n\n\n\n\nDownload, build, and install the latest release version of newtmgr from source. \n\n\n\n\n\n\nSee \nInstalling Previous Releases of Newtgmr\n to install an earlier version of newtmgr.\n\n\nIf you are installing on an amd64 platform, we recommend that you install from the binary package.\n\n\nNote:\n We have tested the newtmgr tool binary and apt-get install from the runtimeco APT repository for Ubuntu version 16. Earlier Ubuntu versions (for example: Ubuntu 14) may have incompatibility with the repository. You can manually download and install the Debian binary package.\n\n\nNote:\n See \nSetting Up a Go Environment to Contribute to Newt and Newtmgr Tools\n if you want to: \n\n\n\n\nUse the newtmgr tool with the latest updates from the master branch. The master branch may be unstable and we recommend that you use the latest stable release version.\n\n\nContribute to the newtmgr tool. \n\n\n\n\n\n\nSetting Up Your Computer to use apt-get to Install the Package\n\n\nThe newtmgr Debian packages are stored in a private APT repository on \nhttps://github/runtimeco/debian-mynewt\n. To use apt-get, you must set up the following on your computer to retrieve packages from the repository:\n\n\nNote\n: You only need to perform this setup once on your computer. However, if you previously downloaded and imported the public key for the runtimeco APT repository, you will need to perform step 2 again as the key has changed.\n\n\n\n\nInstall the \napt-transport-https\n package to use HTTPS to retrieve packages. \n\n\nDownload the public key for the runtimeco APT repository and import the key into the apt keychain.\n\n\nAdd the repository for the binary and source packages to the apt source list.\n\n\n\n\n\n1. Install the apt-transport-https package:\n\n\n$sudo apt-get update\n$sudo apt-get install apt-transport-https\n\n\n\n\n\n\n2. Download the public key for the runtimeco apt repo (\nNote:\n There is a \n-\n after \napt-key add\n):\n\n\nwget -qO - https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/mynewt.gpg.key | sudo apt-key add -\n\n\n\n\n\n\n3. Add the repository for the binary packages to the \nmynewt.list\n apt source list file.\n\n\n$sudo -s\n[sudo] password for \nuser\n:\nroot$ cat \n /etc/apt/sources.list.d/mynewt.list \nEOF\ndeb https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest main\nEOF\nroot$exit\n\n\n\n\n\nNote:\n Do not forget to exit the root shell.\n\n\n\n4. Verify the content of the source list file:\n\n\n$more /etc/apt/sources.list.d/mynewt.list\ndeb https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest main\n\n\n\n\n\n\n5. Update the available packages:\n\n\n$sudo apt-get update\n\n\n\n\n\n\n\nNote:\n If you are not using Ubuntu version 16, you may see the following errors. We have provided instructions on how to manually download and install the binary package.\n\n\nW: Failed to fetch https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/dists/latest/main/source/Sources HttpError404\n\n\n\n\n\n \n\n\nInstalling the Latest Release of Newtmgr from a Binary Package\n\n\nYou can use either apt-get to install the package, or manually download and install the Debian binary package. \n\n\n\n\nMethod 1: Using apt-get to Upgrade or to Install\n\n\nRun the following commands to upgrade or install the latest version of newtmgr:\n\n\n$ sudo apt-get update \n$ sudo apt-get install newtmgr\n\n\n\n\n\nMethod 2: Downloading and Installing the Debian Package Manually\n\n\nDownload and install the package manually.\n\n\n$wget https://raw.githubusercontent.com/runtimeco/binary-releases/master/mynewt-newt-tools_1.2.0/newtmgr_1.2.0-1_amd64.deb\n$sudo dpkg -i newtmgr_1.2.0-1_amd64.deb\n\n\n\n\n\nSee \nChecking the Installed Version of Newtmgr\n to verify that you are using the installed version of newtmgr.\n\n\n\n\nInstalling the Latest Release Version of Newtmgr from Source\n\n\nIf you are running Linux on a different architecture, you can build and install the latest release version of newtmgr from source.\n\n\n\n1. Download and install the latest version of \nGo\n. Newtmgr requires Go version 1.7.6 or higher.\n\n\n\n2. Create a Go workspace in the /tmp directory: \n\n\n$ cd /tmp\n$ mkdir go\n$ cd go\n$ export GOPATH=/tmp/go\n\n\n\n\n\n\n3. Run \ngo get\n to download the newtmgr source. Note that \ngo get\n pulls down the HEAD from the master branch in git, builds, and installs newtmgr.\n\n\n$ go get mynewt.apache.org/newtmgr/newtmgr\n$ ls -l /tmp/go/bin/newtmgr\n-rwxr-xr-x 1 user staff 17884488 Jul 29 16:25 /tmp/go/bin/newtmgr\n\n\n\n\n\n\n4. Check out the source from the latest release version:\n\n\n$ cd src/mynewt.apache.org/newtmgr\n$ git checkout mynewt_1_2_0_tag\nNote: checking out \nmynewt_1_2_0_tag\n.\n\n\n\n\n\n 5. Build newtmgr from the latest release version: \n\n\n$ cd newtmgr\n$ go install\n$ ls /tmp/go/bin/newtmgr\n-rwxr-xr-x 1 user staff 17888680 Jul 29 16:28 /tmp/go/bin/newtmgr\n\n\n\n\n\n\n6. If you have a Go workspace, remember to reset your GOPATH to your Go workspace.\n\n\n\n7. Copy the newtmgr executable to a bin directory in your path. You can put it in the /usr/bin or the $GOPATH/bin directory.\n\n\n\n\n Checking the Latest Version of Newtmgr is Installed\n\n\n\n1. Run \nwhich newtmgr\n to verify that you are using the installed version of newtmgr.\n\n\n\n2. Get information about the newtmgr tool:\n\n\n$newtmgr\nNewtmgr helps you manage remote devices running the Mynewt OS\n\nUsage:\n newtmgr [flags]\n newtmgr [command]\n\nAvailable Commands:\n config Read or write a config value on a device\n conn Manage newtmgr connection profiles\n crash Send a crash command to a device\n datetime Manage datetime on a device\n echo Send data to a device and display the echoed back data\n fs Access files on a device\n help Help about any command\n image Manage images on a device\n log Manage logs on a device\n mpstat Read mempool statistics from a device\n reset Perform a soft reset of a device\n run Run test procedures on a device\n stat Read statistics from a device\n taskstat Read task statistics from a device\n\nFlags:\n -c, --conn string connection profile to use\n -h, --help help for newtmgr\n -l, --loglevel string log level to use (default \ninfo\n)\n --name string name of target BLE device; overrides profile setting\n -t, --timeout float timeout in seconds (partial seconds allowed) (default 10)\n -r, --tries int total number of tries in case of timeout (default 1)\n\nUse \nnewtmgr [command] --help\n for more information about a command.",
"title": "Install Newtmgr On Linux"
},
{
@@ -13342,7 +13342,7 @@
},
{
"location": "/newtmgr/install_linux/#setting-up-your-computer-to-use-apt-get-to-install-the-package",
- "text": "The newtmgr Debian packages are stored in a private APT repository on https://github/runtimeco/debian-mynewt . To use apt-get, you must set up the following on your computer to retrieve packages from the repository: Note : You only need to perform this setup once on your computer. However, if you previously downloaded and imported the public key for the runtimeco APT repository, you will need to perform step 2 again as the key has changed. Install the apt-transport-https package to use HTTPS to retrieve packages. Download the public key for the runtimeco APT repository and import the key into the apt keychain. Add the repository for the binary and source packages to the apt source list. \n1. Install the apt-transport-https package: $sudo apt-get update\n$sudo apt-get install apt-transport-https \n2. Download the public key for the runtimeco apt repo ( Note: There is a - after apt-key add ): wget -qO - https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/mynewt.gpg.key | sudo apt-key add - \n3. Add the repository for the binary packages to the mynewt.list apt source list file. $sudo -s\n[sudo] password for user :\nroot$ cat /etc/apt/sources.list.d/mynewt.list EOF\ndeb https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest main\nEOF\nroot$exit Note: Do not forget to exit the root shell. \n4. Verify the content of the source list file: $more /etc/apt/sources.list.d/mynewt.list\ndeb https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest main \n5. Update the available packages: $sudo apt-get update Note: If you are not using Ubuntu version 16, you may see the following errors. We have provided instructions on how to manually download and install the binary package. W: Failed to fetch https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/dists/latest/main/source/Sources Ht\ntpError404",
+ "text": "The newtmgr Debian packages are stored in a private APT repository on https://github/runtimeco/debian-mynewt . To use apt-get, you must set up the following on your computer to retrieve packages from the repository: Note : You only need to perform this setup once on your computer. However, if you previously downloaded and imported the public key for the runtimeco APT repository, you will need to perform step 2 again as the key has changed. Install the apt-transport-https package to use HTTPS to retrieve packages. Download the public key for the runtimeco APT repository and import the key into the apt keychain. Add the repository for the binary and source packages to the apt source list. \n1. Install the apt-transport-https package: $sudo apt-get update\n$sudo apt-get install apt-transport-https \n2. Download the public key for the runtimeco apt repo ( Note: There is a - after apt-key add ): wget -qO - https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/mynewt.gpg.key | sudo apt-key add - \n3. Add the repository for the binary packages to the mynewt.list apt source list file. $sudo -s\n[sudo] password for user :\nroot$ cat /etc/apt/sources.list.d/mynewt.list EOF\ndeb https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest main\nEOF\nroot$exit Note: Do not forget to exit the root shell. \n4. Verify the content of the source list file: $more /etc/apt/sources.list.d/mynewt.list\ndeb https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest main \n5. Update the available packages: $sudo apt-get update Note: If you are not using Ubuntu version 16, you may see the following errors. We have provided instructions on how to manually download and install the binary package. W: Failed to fetch https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/dists/latest/main/source/Sources HttpError404",
"title": "Setting Up Your Computer to use apt-get to Install the Package"
},
{
@@ -13357,7 +13357,7 @@
},
{
"location": "/newtmgr/install_linux/#method-2-downloading-and-installing-the-debian-package-manually",
- "text": "Download and install the package manually. $wget https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/pool/main/n/newtmgr/newtmgr_1.2.0-1_amd64.deb\n$sudo dpkg -i newtmgr_1.2.0-1_amd64.deb See Checking the Installed Version of Newtmgr to verify that you are using the installed version of newtmgr.",
+ "text": "Download and install the package manually. $wget https://raw.githubusercontent.com/runtimeco/binary-releases/master/mynewt-newt-tools_1.2.0/newtmgr_1.2.0-1_amd64.deb\n$sudo dpkg -i newtmgr_1.2.0-1_amd64.deb See Checking the Installed Version of Newtmgr to verify that you are using the installed version of newtmgr.",
"title": "Method 2: Downloading and Installing the Debian Package Manually"
},
{
diff --git a/newt/install/newt_linux/index.html b/newt/install/newt_linux/index.html
index 9a030c9ad..01b88449e 100644
--- a/newt/install/newt_linux/index.html
+++ b/newt/install/newt_linux/index.html
@@ -488,8 +488,7 @@ <h3 id="setting-up-your-computer-to-use-apt-get-to-install-the-package">Setting
<p><br>
<strong>Note:</strong> If you are not using Ubuntu version 16, you may see the following errors. We have provided instructions on how to manually download and install the binary package.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span></span>W: Failed to fetch https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/dists/latest/main/source/Sources Ht
-tpError404
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span></span>W: Failed to fetch https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/dists/latest/main/source/Sources HttpError404
</pre></div>
@@ -512,8 +511,8 @@ <h4 id="method-1-using-apt-get-to-upgrade-or-to-install">Method 1: Using apt-get
<p><br></p>
<h4 id="method-2-downloading-and-installing-the-debian-package-manually">Method 2: Downloading and Installing the Debian Package Manually</h4>
<p>Download and install the package manually.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span></span>$ wget https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/pool/main/n/newt/newt_1.2.0-1_amd64.deb
-$ sudo dpkg -i newt_1.2.0-1_amd64.deb
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span></span>$wget https://raw.githubusercontent.com/runtimeco/binary-releases/master/mynewt-newt-tools_1.2.0/newt_1.2.0-1_amd64.deb
+$sudo dpkg -i newt_1.2.0-1_amd64.deb
</pre></div>
diff --git a/newt/install/newt_mac/index.html b/newt/install/newt_mac/index.html
index da8d15b61..511438ba2 100644
--- a/newt/install/newt_mac/index.html
+++ b/newt/install/newt_mac/index.html
@@ -428,7 +428,7 @@ <h4>Latest News:</h4> <a href="/download">Apache Mynewt 1.2.0</a> released (Sept
<h2 id="installing-newt-on-mac-os">Installing Newt on Mac OS</h2>
-<p>Newt is supported on Mac OS X 64 bit platforms and has been tested on Mac OS 10.11 and higher.</p>
+<p>Newt is supported on Mac OS X 64 bit platforms and has been tested on Mac OS Sierra.</p>
<p>This page shows you how to install the following versions of newt:</p>
<ul>
<li>Upgrade to or install the latest release version (1.2.0).</li>
@@ -464,24 +464,16 @@ <h4 id="installing-the-latest-release-version-of-newt">Installing the Latest Rel
<p>Run the following command to install the latest release version of newt:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span></span>$ brew update
$ brew install mynewt-newt
-==> Installing mynewt-newt from runtimeco/mynewt
-==> Downloading https://github.com/runtimeco/binary-releases/raw/master/mynewt-newt-tools_1.2.0/mynewt-newt-1.2.0.sierra.bottle.tar.gz
-==> Downloading from https://raw.githubusercontent.com/runtimeco/binary-releases/master/mynewt-newt-tools_1.2.0/mynewt-newt-1.2.0.sierra.bottle.tar.gz
-######################################################################## 100.0%
-==> Pouring mynewt-newt-1.2.0.sierra.bottle.tar.gz
-? /usr/local/Cellar/mynewt-newt/1.2.0: 3 files, 10.7MB
</pre></div>
<p><br>
-<strong>Notes:</strong> Homebrew bottles for newt are available for Mac OS Sierra, and El Captian. If you are running an earlier version of Mac OS, the installation will install the latest version of Go and compile newt locally.</p>
+<strong>Notes:</strong> Homebrew bottles for newt are available for Mac OS Sierra. If you are running an earlier version of Mac OS, the installation will install the latest version of Go and compile newt locally.</p>
<p><br></p>
<h3 id="checking-the-installed-version">Checking the Installed Version</h3>
<p>Check that you are using the installed version of newt:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span></span>$which newt
/usr/local/bin/newt
-$ls -l /usr/local/bin/newt
-lrwxr-xr-x 1 user staff 36 Sep 11 19:04 /usr/local/bin/newt -> ../Cellar/mynewt-newt/1.2.0/bin/newt
$newt version
Apache Newt version: 1.2.0
</pre></div>
@@ -561,30 +553,12 @@ <h3 id="installing-newt-from-the-master-branch">Installing Newt from the Master
<p><br>
Install the latest unstable version of newt from the master branch:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span></span>$ brew install mynewt-newt --HEAD
-==> Installing mynewt-newt from runtimeco/mynewt
-==> Cloning https://github.com/apache/mynewt-newt.git
-Cloning into '/Users/wanda/Library/Caches/Homebrew/mynewt-newt--git'...
-remote: Counting objects: 626, done.
-remote: Compressing objects: 100% (504/504), done.
-remote: Total 626 (delta 155), reused 323 (delta 85), pack-reused 0
-Receiving objects: 100% (626/626), 1.11 MiB | 0 bytes/s, done.
-Resolving deltas: 100% (155/155), done.
-==> Checking out branch master
-==> go install
-? /usr/local/Cellar/mynewt-newt/HEAD-59b3a5d: 3 files, 10.7MB, built in 7 seconds
-$newt version
-Apache Newt version 1.1.0-dev
</pre></div>
<p><br>
To switch back to the latest stable release version of newt, you can run:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span></span>$brew switch mynewt-newt 1.2.0
-Cleaning /usr/local/Cellar/mynewt-newt/1.2.0
-Cleaning /usr/local/Cellar/mynewt-newt/HEAD-59b3a5d
-1 links created for /usr/local/Cellar/mynewt-newt/1.2.0
-$newt version
-Apache Newt version: 1.2.0
</pre></div>
diff --git a/newt/install/newt_windows/index.html b/newt/install/newt_windows/index.html
index 2d9b1378e..5e6c825fe 100644
--- a/newt/install/newt_windows/index.html
+++ b/newt/install/newt_windows/index.html
@@ -434,7 +434,7 @@ <h2 id="installing-newt-on-windows">Installing Newt on Windows</h2>
<ol>
<li>Install MSYS2/MinGW. </li>
<li>Install Git.</li>
-<li>Install latest release of newt (1.2.0) from binary.</li>
+<li>Install latest release (1.2.0) of newt from binary.</li>
<li>Install latest release of newt from source.</li>
</ol>
<p>See <a href="../../../newt/install/prev_releases">Installing Previous Releases of Newt</a> to install an earlier version of newt. You still need to set up your MinGW development environment.</p>
diff --git a/newt/install/prev_releases/index.html b/newt/install/prev_releases/index.html
index 8cf2fce77..b84e54df3 100644
--- a/newt/install/prev_releases/index.html
+++ b/newt/install/prev_releases/index.html
@@ -369,7 +369,7 @@ <h3 id="windows">Windows</h3>
<tbody>
<tr>
<td>1.1.0</td>
-<td><a href="https://raw.githubusercontent.com/runtimeco/binary-releases/master/mynewt-newt-tools_1.1.0/newt_1.1.0-1_amd64.deb">newt_1_1_0_windows_amd64.tar.gz</a></td>
+<td><a href="https://raw.githubusercontent.com/runtimeco/binary-releases/master/mynewt-newt-tools_1.1.0/newt_1_1_0_windows_amd64.tar.gz">newt_1_1_0_windows_amd64.tar.gz</a></td>
</tr>
</tbody>
</table>
diff --git a/newtmgr/install_linux/index.html b/newtmgr/install_linux/index.html
index 18a8fab19..31d4850ba 100644
--- a/newtmgr/install_linux/index.html
+++ b/newtmgr/install_linux/index.html
@@ -472,8 +472,7 @@ <h3 id="setting-up-your-computer-to-use-apt-get-to-install-the-package">Setting
<p><br>
<strong>Note:</strong> If you are not using Ubuntu version 16, you may see the following errors. We have provided instructions on how to manually download and install the binary package.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span></span>W: Failed to fetch https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/dists/latest/main/source/Sources Ht
-tpError404
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span></span>W: Failed to fetch https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/dists/latest/main/source/Sources HttpError404
</pre></div>
@@ -490,7 +489,7 @@ <h4 id="method-1-using-apt-get-to-upgrade-or-to-install">Method 1: Using apt-get
<h4 id="method-2-downloading-and-installing-the-debian-package-manually">Method 2: Downloading and Installing the Debian Package Manually</h4>
<p>Download and install the package manually.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span></span>$wget https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/pool/main/n/newtmgr/newtmgr_1.2.0-1_amd64.deb
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span></span>$wget https://raw.githubusercontent.com/runtimeco/binary-releases/master/mynewt-newt-tools_1.2.0/newtmgr_1.2.0-1_amd64.deb
$sudo dpkg -i newtmgr_1.2.0-1_amd64.deb
</pre></div>
diff --git a/newtmgr/install_mac/index.html b/newtmgr/install_mac/index.html
index 6b2344236..3568bfd1d 100644
--- a/newtmgr/install_mac/index.html
+++ b/newtmgr/install_mac/index.html
@@ -401,7 +401,7 @@ <h4>Latest News:</h4> <a href="/download">Apache Mynewt 1.2.0</a> released (Sept
<h2 id="installing-newtmgr-on-mac-os">Installing Newtmgr on Mac OS</h2>
-<p>Newtmgr is supported on Mac OS X 64 bit platforms and has been tested on Mac OS 10.11 and higher.</p>
+<p>Newtmgr is supported on Mac OS X 64 bit platforms and has been tested on Mac OS Sierra.</p>
<p>This page shows you how to install the following versions of newtmgr:</p>
<ul>
<li>Upgrade to or install the latest release version (1.2.0).</li>
@@ -430,24 +430,16 @@ <h4 id="installing-the-latest-release-version-of-newtmgr">Installing the Latest
<p>Run the following command to install the latest release version of newtmgr:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span></span>$ brew update
$ brew install mynewt-newtmgr
-==> Installing mynewt-newtmgr from runtimeco/mynewt
-==> Downloading https://github.com/runtimeco/binary-releases/raw/master/mynewt-newt-tools_1.2.0/mynewt-newtmgr-1.2.0.sierra.bottle.tar.gz
-==> Downloading from https://raw.githubusercontent.com/runtimeco/binary-releases/master/mynewt-newt-tools_1.2.0/mynewt-newtmgr-1.2.0.sierra.bottle.tar.gz
-######################################################################## 100.0%
-==> Pouring mynewt-newtmgr-1.2.0.sierra.bottle.tar.gz
-? /usr/local/Cellar/mynewt-newtmgr/1.2.0: 3 files, 17.3MB
</pre></div>
<p><br>
-<strong>Notes:</strong> Homebrew bottles for newtmgr 1.2.0 are available for Mac OS Sierra, El Captian. If you are running an earlier version of Mac OS, the installation will install the latest version of Go and compile newtmgr locally.</p>
+<strong>Notes:</strong> Homebrew bottles for newtmgr 1.2.0 are available for Mac OS Sierra. If you are running an earlier version of Mac OS, the installation will install the latest version of Go and compile newtmgr locally.</p>
<p><br></p>
<h3 id="checking-the-installed-version">Checking the Installed Version</h3>
<p>Check that you are using the installed version of newtmgr:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span></span>$which newtmgr
/usr/local/bin/newtmgr
-ls -l /usr/local/bin/newtmgr
-lrwxr-xr-x 1 user staff 42 Sep 11 21:15 /usr/local/bin/newtmgr -> ../Cellar/mynewt-newtmgr/1.2.0/bin/newtmgr
</pre></div>
@@ -504,29 +496,12 @@ <h3 id="installing-newtmgr-from-the-master-branch">Installing Newtmgr from the M
<p><br>
Install the latest unstable version of newtmgr from the master branch:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span></span>$brew install mynewt-newtmgr --HEAD
-==> Installing mynewt-newtmgr from runtimeco/mynewt
-==> Cloning https://github.com/apache/mynewt-newtmgr.git
-Cloning into '/Users/wanda/Library/Caches/Homebrew/mynewt-newtmgr--git'...
-remote: Counting objects: 2169, done.
-remote: Compressing objects: 100% (1752/1752), done.
-remote: Total 2169 (delta 379), reused 2042 (delta 342), pack-reused 0
-Receiving objects: 100% (2169/2169), 8.13 MiB | 5.47 MiB/s, done.
-Resolving deltas: 100% (379/379), done.
-==> Checking out branch master
-==> go get github.com/currantlabs/ble
-==> go get github.com/raff/goble
-==> go get github.com/mgutz/logxi/v1
-==> go install
-? /usr/local/Cellar/mynewt-newtmgr/HEAD-2d5217f: 3 files, 17.3MB, built in 1 minute 10 seconds
</pre></div>
<p><br>
To switch back to the latest stable release version of newtmgr, you can run:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span></span>$brew switch mynewt-newtmgr 1.2.0
-Cleaning /usr/local/Cellar/mynewt-newtmgr/1.2.0
-Cleaning /usr/local/Cellar/mynewt-newtmgr/HEAD-2d5217f
-1 links created for /usr/local/Cellar/mynewt-newtmgr/1.2.0
</pre></div>
diff --git a/newtmgr/prev_releases/index.html b/newtmgr/prev_releases/index.html
index e3427aeb0..c5939ad1c 100644
--- a/newtmgr/prev_releases/index.html
+++ b/newtmgr/prev_releases/index.html
@@ -369,7 +369,7 @@ <h3 id="windows">Windows</h3>
<tbody>
<tr>
<td>1.1.0</td>
-<td><a href="https://raw.githubusercontent.com/runtimeco/binary-releases/master/mynewt-newt-tools_1.1.0/newtmgr_1.1.0-1_amd64.deb">newtmgr_1_1_0_windows_amd64.tar.gz</a></td>
+<td><a href="https://raw.githubusercontent.com/runtimeco/binary-releases/master/mynewt-newt-tools_1.1.0/newtmgr_1_1_0_windows_amd64.tar.gz">newtmgr_1_1_0_windows_amd64.tar.gz</a></td>
</tr>
</tbody>
</table>
diff --git a/os/tutorials/lora/lorawanapp/index.html b/os/tutorials/lora/lorawanapp/index.html
index 6b3988477..eecf5f2a7 100644
--- a/os/tutorials/lora/lorawanapp/index.html
+++ b/os/tutorials/lora/lorawanapp/index.html
@@ -579,7 +579,7 @@ <h3 id="create-the-targets">Create the targets</h3>
<br></p>
<h3 id="build-the-target-executables">Build the target executables</h3>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span></span>$ newt clean telee02_boot
-$ newt clean telee02_boot
+$ newt build telee02_boot
Building target targets/telee02_boot
Compiling repos/apache-mynewt-core/boot/bootutil/src/image_rsa.c
Compiling repos/apache-mynewt-core/boot/bootutil/src/image_ec.c
diff --git a/sitemap.xml b/sitemap.xml
index 9da93ba50..5aeaa1f17 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -4,7 +4,7 @@
<url>
<loc>http://mynewt.apache.org/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -13,13 +13,13 @@
<url>
<loc>http://mynewt.apache.org/pages/ble/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/pages/securitybullets/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -28,7 +28,7 @@
<url>
<loc>http://mynewt.apache.org/quick-start/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -36,7 +36,7 @@
<url>
<loc>http://mynewt.apache.org/about/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -44,7 +44,7 @@
<url>
<loc>http://mynewt.apache.org/talks/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -52,7 +52,7 @@
<url>
<loc>http://mynewt.apache.org/download/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -60,7 +60,7 @@
<url>
<loc>http://mynewt.apache.org/community/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -68,7 +68,7 @@
<url>
<loc>http://mynewt.apache.org/events/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -77,7 +77,7 @@
<url>
<loc>http://mynewt.apache.org/os/introduction/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -89,7 +89,7 @@
<url>
<loc>http://mynewt.apache.org/os/get_started/vocabulary/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -125,7 +125,7 @@
<url>
<loc>http://mynewt.apache.org/known_issues/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -135,37 +135,37 @@
<url>
<loc>http://mynewt.apache.org/newt/install/prev_releases/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/newtmgr/prev_releases/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/go_env/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/ide/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/how_to_edit_docs/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/answers/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
diff --git a/v0_9_0/sitemap.xml b/v0_9_0/sitemap.xml
index ef87c34ab..facd2ebed 100644
--- a/v0_9_0/sitemap.xml
+++ b/v0_9_0/sitemap.xml
@@ -4,7 +4,7 @@
<url>
<loc>http://mynewt.apache.org/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -12,7 +12,7 @@
<url>
<loc>http://mynewt.apache.org/quick-start/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -20,7 +20,7 @@
<url>
<loc>http://mynewt.apache.org/about/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -28,7 +28,7 @@
<url>
<loc>http://mynewt.apache.org/download/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -36,7 +36,7 @@
<url>
<loc>http://mynewt.apache.org/community/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -44,7 +44,7 @@
<url>
<loc>http://mynewt.apache.org/events/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -53,7 +53,7 @@
<url>
<loc>http://mynewt.apache.org/os/introduction/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -65,7 +65,7 @@
<url>
<loc>http://mynewt.apache.org/os/get_started/vocabulary/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -101,7 +101,7 @@
<url>
<loc>http://mynewt.apache.org/known_issues/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -111,13 +111,13 @@
<url>
<loc>http://mynewt.apache.org/faq/how_to_edit_docs/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/answers/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
diff --git a/v1_0_0/sitemap.xml b/v1_0_0/sitemap.xml
index 11c041591..327a3a9ca 100644
--- a/v1_0_0/sitemap.xml
+++ b/v1_0_0/sitemap.xml
@@ -4,7 +4,7 @@
<url>
<loc>http://mynewt.apache.org/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -13,7 +13,7 @@
<url>
<loc>http://mynewt.apache.org/pages/ble/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -22,7 +22,7 @@
<url>
<loc>http://mynewt.apache.org/quick-start/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -30,7 +30,7 @@
<url>
<loc>http://mynewt.apache.org/about/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -38,7 +38,7 @@
<url>
<loc>http://mynewt.apache.org/talks/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -46,7 +46,7 @@
<url>
<loc>http://mynewt.apache.org/download/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -54,7 +54,7 @@
<url>
<loc>http://mynewt.apache.org/community/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -62,7 +62,7 @@
<url>
<loc>http://mynewt.apache.org/events/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -71,7 +71,7 @@
<url>
<loc>http://mynewt.apache.org/os/introduction/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -83,7 +83,7 @@
<url>
<loc>http://mynewt.apache.org/os/get_started/vocabulary/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -119,7 +119,7 @@
<url>
<loc>http://mynewt.apache.org/known_issues/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -129,25 +129,25 @@
<url>
<loc>http://mynewt.apache.org/faq/go_env/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/ide/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/how_to_edit_docs/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/answers/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
diff --git a/v1_1_0/sitemap.xml b/v1_1_0/sitemap.xml
index 5ed501fae..a8f1ebe98 100644
--- a/v1_1_0/sitemap.xml
+++ b/v1_1_0/sitemap.xml
@@ -4,7 +4,7 @@
<url>
<loc>http://mynewt.apache.org/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -13,13 +13,13 @@
<url>
<loc>http://mynewt.apache.org/pages/ble/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/pages/securitybullets/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -28,7 +28,7 @@
<url>
<loc>http://mynewt.apache.org/quick-start/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -36,7 +36,7 @@
<url>
<loc>http://mynewt.apache.org/about/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -44,7 +44,7 @@
<url>
<loc>http://mynewt.apache.org/talks/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -52,7 +52,7 @@
<url>
<loc>http://mynewt.apache.org/download/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -60,7 +60,7 @@
<url>
<loc>http://mynewt.apache.org/community/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -68,7 +68,7 @@
<url>
<loc>http://mynewt.apache.org/events/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -77,7 +77,7 @@
<url>
<loc>http://mynewt.apache.org/os/introduction/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -89,7 +89,7 @@
<url>
<loc>http://mynewt.apache.org/os/get_started/vocabulary/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -125,7 +125,7 @@
<url>
<loc>http://mynewt.apache.org/known_issues/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -135,25 +135,25 @@
<url>
<loc>http://mynewt.apache.org/faq/go_env/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/ide/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/how_to_edit_docs/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/answers/</loc>
- <lastmod>2017-11-19</lastmod>
+ <lastmod>2017-12-01</lastmod>
<changefreq>daily</changefreq>
</url>
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services