Repository: incubator-mynewt-site Updated Branches: refs/heads/asf-site 98ebdde95 -> bdd8fed45
Removed pre-GA from release banner and roadmap in About page, updated project_create.md file to show correct run command for simulated targets. Project: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/repo Commit: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/commit/bdd8fed4 Tree: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/tree/bdd8fed4 Diff: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/diff/bdd8fed4 Branch: refs/heads/asf-site Commit: bdd8fed459315290041b5c25776436682b6c0d5f Parents: 98ebdde Author: aditihilbert <[email protected]> Authored: Mon May 30 23:38:37 2016 -0700 Committer: aditihilbert <[email protected]> Committed: Mon May 30 23:38:37 2016 -0700 ---------------------------------------------------------------------- about/index.html | 19 +------------------ community/index.html | 2 +- events/index.html | 2 +- index.html | 2 +- main-banner.html | 2 +- mkdocs/search_index.json | 13 +++++++++---- os/get_started/project_create/index.html | 11 ++++++++--- sitemap.xml | 20 ++++++++++---------- 8 files changed, 32 insertions(+), 39 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/bdd8fed4/about/index.html ---------------------------------------------------------------------- diff --git a/about/index.html b/about/index.html index f85c7f7..2643e1f 100644 --- a/about/index.html +++ b/about/index.html @@ -127,7 +127,7 @@ </div><!-- (need this comment because of the inline-blocks) --><div class="col-md-4 v2-vcenter"> <div class="news bg-orange text-center"> - <h4>Pre-GA Mynewt 0.8.0 release is available now. </h4> + <h4>Mynewt 0.8.0 release is available now. </h4> <a href="/download/">Download!</a> </div> </div> @@ -188,7 +188,6 @@ <thead> <tr> <th>Release Version</th> -<th>Descriptor</th> <th>Date</th> <th>Features</th> </tr> @@ -196,98 +195,82 @@ <tbody> <tr> <td>0.9.0</td> -<td>pre-GA release</td> <td>May, 2016</td> <td>* Support images in external flash</td> </tr> <tr> <td></td> <td></td> -<td></td> <td>* HAL for Nordic nRF52, STMicro</td> </tr> <tr> <td></td> <td></td> -<td></td> <td>* Support for low power modes in multiple SoCs</td> </tr> <tr> <td></td> <td></td> -<td></td> <td>* BLE 4.2: LE Secure Connections Pairing, including bonding</td> </tr> <tr> <td></td> <td></td> -<td></td> <td>* BLE 4.2: Host and Controller separation</td> </tr> <tr> <td></td> <td></td> -<td></td> <td>* BLE 4.2: Random private resolvable addresses</td> </tr> <tr> <td>0.10.0</td> -<td>pre-GA release</td> <td>June, 2016</td> <td>* Test coverage improvements</td> </tr> <tr> <td></td> <td></td> -<td></td> <td>* System watchdog</td> </tr> <tr> <td></td> <td></td> -<td></td> <td>* Support for additional Arduino boards</td> </tr> <tr> <td></td> <td></td> -<td></td> <td>* BLE 4.2: Remote configuration, upgrade, factory reset over BLE 4.2</td> </tr> <tr> <td></td> <td></td> -<td></td> <td>* BLE 4.2: Factory reset</td> </tr> <tr> <td></td> <td></td> -<td></td> <td>* BLE 4.2: GATT based BLE profiles for Mynewt</td> </tr> <tr> <td></td> <td></td> -<td></td> <td>* BLE 4.2: Configurability improvements</td> </tr> <tr> <td>0.11.0</td> -<td>pre-GA release</td> <td>July, 2016</td> <td>* Wi-Fi support</td> </tr> <tr> <td></td> <td></td> -<td></td> <td>* Add second scripting module</td> </tr> <tr> <td></td> <td></td> -<td></td> <td>* C++ friendly external header files</td> </tr> </tbody> http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/bdd8fed4/community/index.html ---------------------------------------------------------------------- diff --git a/community/index.html b/community/index.html index fdccd83..7d79853 100644 --- a/community/index.html +++ b/community/index.html @@ -127,7 +127,7 @@ </div><!-- (need this comment because of the inline-blocks) --><div class="col-md-4 v2-vcenter"> <div class="news bg-orange text-center"> - <h4>Pre-GA Mynewt 0.8.0 release is available now. </h4> + <h4>Mynewt 0.8.0 release is available now. </h4> <a href="/download/">Download!</a> </div> </div> http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/bdd8fed4/events/index.html ---------------------------------------------------------------------- diff --git a/events/index.html b/events/index.html index 2508f0d..1185b57 100644 --- a/events/index.html +++ b/events/index.html @@ -127,7 +127,7 @@ </div><!-- (need this comment because of the inline-blocks) --><div class="col-md-4 v2-vcenter"> <div class="news bg-orange text-center"> - <h4>Pre-GA Mynewt 0.8.0 release is available now. </h4> + <h4>Mynewt 0.8.0 release is available now. </h4> <a href="/download/">Download!</a> </div> </div> http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/bdd8fed4/index.html ---------------------------------------------------------------------- diff --git a/index.html b/index.html index 398deb4..2b47463 100644 --- a/index.html +++ b/index.html @@ -127,7 +127,7 @@ </div><!-- (need this comment because of the inline-blocks) --><div class="col-md-4 v2-vcenter"> <div class="news bg-orange text-center"> - <h4>Pre-GA Mynewt 0.8.0 release is available now. </h4> + <h4>Mynewt 0.8.0 release is available now. </h4> <a href="/download/">Download!</a> </div> </div> http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/bdd8fed4/main-banner.html ---------------------------------------------------------------------- diff --git a/main-banner.html b/main-banner.html index 3dea9d3..89dcc7a 100644 --- a/main-banner.html +++ b/main-banner.html @@ -7,7 +7,7 @@ </div><!-- (need this comment because of the inline-blocks) --><div class="col-md-4 v2-vcenter"> <div class="news bg-orange text-center"> - <h4>Pre-GA Mynewt 0.8.0 release is available now. </h4> + <h4>Mynewt 0.8.0 release is available now. </h4> <a href="/download/">Download!</a> </div> </div> http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/bdd8fed4/mkdocs/search_index.json ---------------------------------------------------------------------- diff --git a/mkdocs/search_index.json b/mkdocs/search_index.json index 6582a00..56d0632 100644 --- a/mkdocs/search_index.json +++ b/mkdocs/search_index.json @@ -27,12 +27,12 @@ }, { "location": "/about/", - "text": "Roadmap\n\n\n\n\n\n\n\n\nRelease Version\n\n\nDescriptor\n\n\nDate\n\n\nFeatures\n\n\n\n\n\n\n\n\n\n\n0.9.0\n\n\npre-GA release\n\n\nMay, 2016\n\n\n* Support images in external flash\n\n\n\n\n\n\n\n\n\n\n\n\n* HAL for Nordic nRF52, STMicro\n\n\n\n\n\n\n\n\n\n\n\n\n* Support for low power modes in multiple SoCs\n\n\n\n\n\n\n\n\n\n\n\n\n* BLE 4.2: LE Secure Connections Pairing, including bonding\n\n\n\n\n\n\n\n\n\n\n\n\n* BLE 4.2: Host and Controller separation\n\n\n\n\n\n\n\n\n\n\n\n\n* BLE 4.2: Random private resolvable addresses\n\n\n\n\n\n\n0.10.0\n\n\npre-GA release\n\n\nJune, 2016\n\n\n* Test coverage improvements\n\n\n\n\n\n\n\n\n\n\n\n\n* System watchdog\n\n\n\n\n\n\n\n\n\n\n\n\n* Support for additional Arduino boards\n\n\n\n\n\n\n\n\n\n\n\n\n* BLE 4.2: Remote configuration, upgrade, factory reset over BLE 4.2\n\n\n\n\n\n\n\n\n\n\n\n\n* BLE 4.2: Factory reset\n\n\n\n\n\n\n\n\n\n\n\n\n* BLE 4.2: GATT based BLE profiles for Mynewt\n\n\n\n\n\n\n\n\n\n\n\n\n* BLE 4.2: Configurability improvements\n\n\n\n\n\n\n0.11.0\n\n\npre-GA release\n\n\nJuly, 2016\n\n\n* Wi-Fi support\n\n\n\n\n\n\n\n\n\n\n\n\n* Add second scripting module\n\n\n\n\n\n\n\n\n\n\n\n\n* C++ friendly external header files\n\n\n\n\n\n\n\n\n The detailed roadmap is tracked on \nJIRA for Mynewt\n. \n\n\n\n\nFeature Request\n\n\nThe WISHLIST at the top of the roadmap on \nJIRA for Mynewt\n features all the new ideas awaiting discussion and review. Once the community decides to go ahead with a request, it is scheduled into a release. Generally, effort is made to schedule a requested feature into a particular version no later than 6 weeks prior to the planned release date.\n\n\nIf you have suggestions for a new feature, use case, or implementation improvements, file a JIRA ticket with Issue Type set to \"Wish\". Introduce it in the \ndev@\n mailing list with a link to the JIRA ticket. This assumes you have signed up for an account on JIRA and submitted a request to the dev@ mail ing list for your JIRA username to be added to the Apache Mynewt (MYNEWT) project. \n\n\n\n\nFAQ\n\n\n Questions? \n Click \nhere", + "text": "Roadmap\n\n\n\n\n\n\n\n\nRelease Version\n\n\nDate\n\n\nFeatures\n\n\n\n\n\n\n\n\n\n\n0.9.0\n\n\nMay, 2016\n\n\n* Support images in external flash\n\n\n\n\n\n\n\n\n\n\n* HAL for Nordic nRF52, STMicro\n\n\n\n\n\n\n\n\n\n\n* Support for low power modes in multiple SoCs\n\n\n\n\n\n\n\n\n\n\n* BLE 4.2: LE Secure Connections Pairing, including bonding\n\n\n\n\n\n\n\n\n\n\n* BLE 4.2: Host and Controller separation\n\n\n\n\n\n\n\n\n\n\n* BLE 4.2: Random private resolvable addresses\n\n\n\n\n\n\n0.10.0\n\n\nJune, 2016\n\n\n* Test coverage improvements\n\n\n\n\n\n\n\n\n\n\n* System watchdog\n\n\n\n\n\n\n\n\n\n\n* Support for additional Arduino boards\n\n\n\n\n\n\n\n\n\n\n* BLE 4.2: Remote configuration, upgrade, factory reset over BLE 4.2\n\n\n\n\n\n\n\n\n\n\n* BLE 4.2: Factory reset\n\n\n\n\n\n\n\n\n\n\n* BLE 4.2: GATT based BLE profiles for Mynewt\n\n\n\n\n\n\n\n\n\n\n* BLE 4.2: Configurability improvements\n\n\n\n\n\n\n0.11.0\n\n\nJuly, 2016\n\n\n* Wi-Fi support\n\n\n \n\n\n\n\n\n\n\n* Add second scripting module\n\n\n\n\n\n\n\n\n\n\n* C++ friendly external header files\n\n\n\n\n\n\n\n\n The detailed roadmap is tracked on \nJIRA for Mynewt\n. \n\n\n\n\nFeature Request\n\n\nThe WISHLIST at the top of the roadmap on \nJIRA for Mynewt\n features all the new ideas awaiting discussion and review. Once the community decides to go ahead with a request, it is scheduled into a release. Generally, effort is made to schedule a requested feature into a particular version no later than 6 weeks prior to the planned release date.\n\n\nIf you have suggestions for a new feature, use case, or implementation improvements, file a JIRA ticket with Issue Type set to \"Wish\". Introduce it in the \ndev@\n mailing list with a link to the JIRA ticket. This assumes you have signed up for an account on JIRA and submitted a request to the dev@ mailing list for your JIRA username to be added to the Apache Mynewt (MYNEWT) project. \n\n\n\n\nFAQ\n\n\n Questions? \n Click \nher e", "title": "About" }, { "location": "/about/#roadmap", - "text": "Release Version Descriptor Date Features 0.9.0 pre-GA release May, 2016 * Support images in external flash * HAL for Nordic nRF52, STMicro * Support for low power modes in multiple SoCs * BLE 4.2: LE Secure Connections Pairing, including bonding * BLE 4.2: Host and Controller separation * BLE 4.2: Random private resolvable addresses 0.10.0 pre-GA release June, 2016 * Test coverage improvements * System watchdog * Support for additional Arduino boards * BLE 4.2: Remote configuration, upgrade, factory reset over BLE 4.2 * BLE 4.2: Factory reset * BLE 4.2: GATT based BLE profiles for Mynewt * BLE 4.2: Configurability improvements 0.11.0 pre-GA release July, 2016 * Wi-Fi support * Add second scripting module * C++ friendly external header files The detailed roadmap is tracked on JIRA for Mynewt .", + "text": "Release Version Date Features 0.9.0 May, 2016 * Support images in external flash * HAL for Nordic nRF52, STMicro * Support for low power modes in multiple SoCs * BLE 4.2: LE Secure Connections Pairing, including bonding * BLE 4.2: Host and Controller separation * BLE 4.2: Random private resolvable addresses 0.10.0 June, 2016 * Test coverage improvements * System watchdog * Support for additional Arduino boards * BLE 4.2: Remote configuration, upgrade, factory reset over BLE 4.2 * BLE 4.2: Factory reset * BLE 4.2: GATT based BLE profiles for Mynewt * BLE 4.2: Configurability improvements 0.11.0 July, 2016 * Wi-Fi support * Add second scripting module * C++ friendly external header files The detailed roadmap is tracked on JIRA for Mynewt .", "title": "Roadmap" }, { @@ -327,7 +327,7 @@ }, { "location": "/os/get_started/project_create/", - "text": "Create Your First Mynewt Project\n\n\nThis page shows how to create a Mynewt Project using the \nnewt\n command-line tool.\n\n\n\n\nPre-Requisites\n\n\n\n\nNewt:\n\n\nIf you have taken the Docker route, you have already installed Newt.\n\n\nIf you have taken the native install route, you have to ensure that you have installed the Newt tool following the instructions for \nMac\n or \nLinux\n as appropriate, and that the \nnewt\n command is in your system path. \n\n\n\n\n\n\nYou must have Internet connectivity to fetch remote Mynewt components.\n\n\nYou must \ninstall the compiler tools\n to \nsupport native compiling to build the project this tutorial creates. \n\n\n\n\n\n\nNewt New\n\n\nChoose a project name. For this tutorial we will call this project \nmyproj\n.\nEnter the \nnewt new myproj\n command. \n\n\n$ newt new myproj\nDownloading project skeleton from apache/incubator-mynewt-blinky...\nInstalling skeleton in myproj...\nProject myproj successfully crea ted.\n\n\n\n\n\n\n\nNewt populates this new project with a base skeleton of a new Apache Mynewt \nproject. It has the following structure. \n\n\nNote\n: If you do not have \ntree\n, install it by running \nbrew install tree\n.\n\n\n$ cd myproj\n$ tree \n.\n\u251c\u2500\u2500 DISCLAIMER\n\u251c\u2500\u2500 LICENSE\n\u251c\u2500\u2500 NOTICE\n\u251c\u2500\u2500 README.md\n\u251c\u2500\u2500 apps\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 blinky\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 pkg.yml\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 src\n\u251c\u2500\u2500 project.yml\n\u2514\u2500\u2500 targets\n \u251c\u2500\u2500 my_blinky_sim\n \u2502\u00a0\u00a0 \u251c\u2500\u2500 pkg.yml\n \u2502\u00a0\u00a0 \u2514\u2500\u2500 target.yml\n \u2514\u2500\u2500 unittest\n \u251c\u2500\u2500 pkg.yml\n \u2514\u2500\u2500 target.yml\n\n6 directories, 10 files\n\n\n\n\n\n\n\nThe Newt tool has installed the base files for a project comprising the following:\n\n\n\n\nThe file \ nproject.yml\n contains the repository list that the project uses to fetch\nits packages. Your project is a collection of repositories. In this case, the project just\ncomprises the core mynewt repository. Later you will add more repositories\nto include other mynewt components.\n\n\nThe file \napps/blinky/pkg.yml\n contains the description of your application\nand its package dependencies.\n\n\nA \ntarget\n directory containing \nmy_blinky_sim\n, a target descriptor used to\nbuild a version of myproj. Use \nnewt target show\n to see available build \ntargets.\n\n\nA non-buildable target called \nunittest\n. This is used internally by \nnewt\n and is not a formal build target.\n\n\n\n\nNOTE:\n the actual code and package files are not installed \n(except the template for \nmain.c\n). See the next step for installing the packages.\n\n\n\n\nNewt Install\n\n\nOnce you've switched into your new project's directory, the next step is to fetch\nany dependencies this project has. By d efault, all Newt projects rely on a\nsingle remote repository, apache-mynewt-core. The \nnewt install\n command will\nfetch this repository.\n\n\n$ newt install\napache-mynewt-core\n\n\n\n\n\nNOTE:\n \napache-mynewt-core\n may take a while to download. To see progress,\nuse the \n-v\n (verbose) option to install. \n\n\n\n\nOnce \nnewt install\n has successfully finished, the contents of \napache-mynewt-core\n will have been downloaded into your local directory. You can view them by issuing the following commands in the base directory of the new project:\n\n\n$ tree -L 2 repos/apache-mynewt-core/\n.\n\nsnip\n\n\u251c\u2500\u2500 fs\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 fs\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 nffs\n\u251c\u2500\u2500 hw\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 bsp\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 hal\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 mcu\n\u251c\u2500\u2500 libs\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 baselibc\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 bootu til\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 cmsis-core\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 console\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 elua\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 flash_test\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 imgmgr\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 json\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 mbedtls\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 newtmgr\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 os\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 shell\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 testreport\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 testutil\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 util\n\u251c\u2500\u2500 net\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 nimble\n\nsnip\n\n\n\n\n\n\nAs you can see, the core of the Apache Mynewt operating system has been brought \ninto your local directory. \n\n\n\n\nTest the project's packages\n\n\nYou have already built your first basic project. You can ask Newt to execute the unit tests in a package. For example, to test the \nlibs/os\n pac kage in the \napache-mynewt-core\n repo, call newt as shown below.\n\n\n$ newt test @apache-mynewt-core/libs/os\nTesting package @apache-mynewt-core/libs/os\nCompiling hal_bsp.c\nCompiling os_bsp.c\nCompiling sbrk.c\nArchiving native.a\nCompiling flash_map.c\n\nsnip\n\n\n\n\n\n\n\n\nTo test all the packages in a project, specify \nall\n instead of the package name.\n\n\n$ newt test all\n...lots of compiling and testing...\n...about 2 minutes later ...\nArchiving bootutil.a\nLinking test_bootutil\nExecuting test: /myproj/bin/unittest/libs/bootutil/test_bootutil\nPassed tests: [net/nimble/host fs/nffs libs/os hw/hal libs/mbedtls libs/util sys/config libs/bootutil]\nAll tests passed\n\n\n\n\n\n\n\nBuild the Project\n\n\nTo build and run your new application, simply issue the following command:\n\n\n$ newt build my_blinky_sim \nCompiling base64.c\nCompiling cbmem.c\nCompiling datetime.c\nCompiling tpq.c\nArchiving util.a\nCompiling main.c\nArchiving blinky.a\nCompiling flash_map.c\nComp iling hal_flash.c\nArchiving hal.a\nCompiling cons_fmt.c\nCompiling cons_tty.c\n\nsnip\n\nLinking blinky.elf\nApp successfully built: /Users/sterling/dev/tmp/my_app/bin/my_blinky_sim/apps/blinky/blinky.elf\n\n\n\n\n\n\n\nYou can run the simulated version of your project and see the simulated LED\nblink.\n\n\n./bin/my_blinky_sim/apps/blinky/blinky.elf\nhal_gpio set pin 1 to 0\n\n\n\n\n\nJust press \nctrl-c\n to exit.\n\n\n\n\nComplete\n\n\nCongratulations, you have created your first project! The blinky application\nis not terribly exciting when it is run in the simulator, as there is no LED to\nblink. Apache Mynewt has a lot more functionality than just running simulated\napplications. It provides all the features you'll need to cross-compile your\napplication, run it on real hardware and develop a full featured application.\n\n\nIf you're interested in learning more, a good next step is to dig in to one of\nthe \ntutorials\n and get a Mynewt project running on real hardware.\n\ n\nHappy Hacking!", + "text": "Create Your First Mynewt Project\n\n\nThis page shows how to create a Mynewt Project using the \nnewt\n command-line tool.\n\n\n\n\nPre-Requisites\n\n\n\n\nNewt:\n\n\nIf you have taken the Docker route, you have already installed Newt.\n\n\nIf you have taken the native install route, you have to ensure that you have installed the Newt tool following the instructions for \nMac\n or \nLinux\n as appropriate, and that the \nnewt\n command is in your system path. \n\n\n\n\n\n\nYou must have Internet connectivity to fetch remote Mynewt components.\n\n\nYou must \ninstall the compiler tools\n to \nsupport native compiling to build the project this tutorial creates. \n\n\n\n\n\n\nNewt New\n\n\nChoose a project name. For this tutorial we will call this project \nmyproj\n.\nEnter the \nnewt new myproj\n command. \n\n\n$ newt new myproj\nDownloading project skeleton from apache/incubator-mynewt-blinky...\nInstalling skeleton in myproj...\nProject myproj successfully crea ted.\n\n\n\n\n\n\n\nNewt populates this new project with a base skeleton of a new Apache Mynewt \nproject. It has the following structure. \n\n\nNote\n: If you do not have \ntree\n, install it by running \nbrew install tree\n.\n\n\n$ cd myproj\n$ tree \n.\n\u251c\u2500\u2500 DISCLAIMER\n\u251c\u2500\u2500 LICENSE\n\u251c\u2500\u2500 NOTICE\n\u251c\u2500\u2500 README.md\n\u251c\u2500\u2500 apps\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 blinky\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 pkg.yml\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 src\n\u251c\u2500\u2500 project.yml\n\u2514\u2500\u2500 targets\n \u251c\u2500\u2500 my_blinky_sim\n \u2502\u00a0\u00a0 \u251c\u2500\u2500 pkg.yml\n \u2502\u00a0\u00a0 \u2514\u2500\u2500 target.yml\n \u2514\u2500\u2500 unittest\n \u251c\u2500\u2500 pkg.yml\n \u2514\u2500\u2500 target.yml\n\n6 directories, 10 files\n\n\n\n\n\n\n\nThe Newt tool has installed the base files for a project comprising the following:\n\n\n\n\nThe file \ nproject.yml\n contains the repository list that the project uses to fetch\nits packages. Your project is a collection of repositories. In this case, the project just\ncomprises the core mynewt repository. Later you will add more repositories\nto include other mynewt components.\n\n\nThe file \napps/blinky/pkg.yml\n contains the description of your application\nand its package dependencies.\n\n\nA \ntarget\n directory containing \nmy_blinky_sim\n, a target descriptor used to\nbuild a version of myproj. Use \nnewt target show\n to see available build \ntargets.\n\n\nA non-buildable target called \nunittest\n. This is used internally by \nnewt\n and is not a formal build target.\n\n\n\n\nNOTE:\n the actual code and package files are not installed \n(except the template for \nmain.c\n). See the next step for installing the packages.\n\n\n\n\nNewt Install\n\n\nOnce you've switched into your new project's directory, the next step is to fetch\nany dependencies this project has. By d efault, all Newt projects rely on a\nsingle remote repository, apache-mynewt-core. The \nnewt install\n command will\nfetch this repository.\n\n\n$ newt install\napache-mynewt-core\n\n\n\n\n\nNOTE:\n \napache-mynewt-core\n may take a while to download. To see progress,\nuse the \n-v\n (verbose) option to install. \n\n\n\n\nOnce \nnewt install\n has successfully finished, the contents of \napache-mynewt-core\n will have been downloaded into your local directory. You can view them by issuing the following commands in the base directory of the new project:\n\n\n$ tree -L 2 repos/apache-mynewt-core/\n.\n\nsnip\n\n\u251c\u2500\u2500 fs\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 fs\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 nffs\n\u251c\u2500\u2500 hw\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 bsp\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 hal\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 mcu\n\u251c\u2500\u2500 libs\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 baselibc\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 bootu til\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 cmsis-core\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 console\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 elua\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 flash_test\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 imgmgr\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 json\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 mbedtls\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 newtmgr\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 os\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 shell\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 testreport\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 testutil\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 util\n\u251c\u2500\u2500 net\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 nimble\n\nsnip\n\n\n\n\n\n\nAs you can see, the core of the Apache Mynewt operating system has been brought \ninto your local directory. \n\n\n\n\nTest the project's packages\n\n\nYou have already built your first basic project. You can ask Newt to execute the unit tests in a package. For example, to test the \nlibs/os\n pac kage in the \napache-mynewt-core\n repo, call newt as shown below.\n\n\n$ newt test @apache-mynewt-core/libs/os\nTesting package @apache-mynewt-core/libs/os\nCompiling hal_bsp.c\nCompiling os_bsp.c\nCompiling sbrk.c\nArchiving native.a\nCompiling flash_map.c\n\nsnip\n\n\n\n\n\n\n\n\nTo test all the packages in a project, specify \nall\n instead of the package name.\n\n\n$ newt test all\n...lots of compiling and testing...\n...about 2 minutes later ...\nArchiving bootutil.a\nLinking test_bootutil\nExecuting test: /myproj/bin/unittest/libs/bootutil/test_bootutil\nPassed tests: [net/nimble/host fs/nffs libs/os hw/hal libs/mbedtls libs/util sys/config libs/bootutil]\nAll tests passed\n\n\n\n\n\n\n\nBuild the Project\n\n\nTo build and run your new application, simply issue the following command:\n\n\n$ newt build my_blinky_sim \nCompiling base64.c\nCompiling cbmem.c\nCompiling datetime.c\nCompiling tpq.c\nArchiving util.a\nCompiling main.c\nArchiving blinky.a\nCompiling flash_map.c\nComp iling hal_flash.c\nArchiving hal.a\nCompiling cons_fmt.c\nCompiling cons_tty.c\n\nsnip\n\nLinking blinky.elf\nApp successfully built: /Users/sterling/dev/tmp/my_app/bin/my_blinky_sim/apps/blinky/blinky.elf\n\n\n\n\n\n\n\nRun the Project\n\n\nYou can run the simulated version of your project and see the simulated LED\nblink.\n\n\n$ newt run my_blinky_sim\nNo download script for BSP hw/bsp/native\nDebugging /workspace/bin/my_blinky_sim/apps/blinky/blinky.elf\n\nsnip\n\nReading symbols from /workspace/bin/my_blinky_sim/apps/blinky/blinky.elf...done.\n(gdb)\n\n\n\n\n\nType \nr\n at the \n(gdb)\n prompt to run the project. You will see an output indicating that the \nhal_gpio\n pin is toggling between 1 and 0 in a simulated blink. \n\n\n\n\nComplete\n\n\nCongratulations, you have created your first project! The blinky application\nis not terribly exciting when it is run in the simulator, as there is no LED to\nblink. Apache Mynewt has a lot more functionality than just running simulate d\napplications. It provides all the features you'll need to cross-compile your\napplication, run it on real hardware and develop a full featured application.\n\n\nIf you're interested in learning more, a good next step is to dig in to one of\nthe \ntutorials\n and get a Mynewt project running on real hardware.\n\n\nHappy Hacking!", "title": "Create Your First Project" }, { @@ -357,10 +357,15 @@ }, { "location": "/os/get_started/project_create/#build-the-project", - "text": "To build and run your new application, simply issue the following command: $ newt build my_blinky_sim \nCompiling base64.c\nCompiling cbmem.c\nCompiling datetime.c\nCompiling tpq.c\nArchiving util.a\nCompiling main.c\nArchiving blinky.a\nCompiling flash_map.c\nCompiling hal_flash.c\nArchiving hal.a\nCompiling cons_fmt.c\nCompiling cons_tty.c snip \nLinking blinky.elf\nApp successfully built: /Users/sterling/dev/tmp/my_app/bin/my_blinky_sim/apps/blinky/blinky.elf You can run the simulated version of your project and see the simulated LED\nblink. ./bin/my_blinky_sim/apps/blinky/blinky.elf\nhal_gpio set pin 1 to 0 Just press ctrl-c to exit.", + "text": "To build and run your new application, simply issue the following command: $ newt build my_blinky_sim \nCompiling base64.c\nCompiling cbmem.c\nCompiling datetime.c\nCompiling tpq.c\nArchiving util.a\nCompiling main.c\nArchiving blinky.a\nCompiling flash_map.c\nCompiling hal_flash.c\nArchiving hal.a\nCompiling cons_fmt.c\nCompiling cons_tty.c snip \nLinking blinky.elf\nApp successfully built: /Users/sterling/dev/tmp/my_app/bin/my_blinky_sim/apps/blinky/blinky.elf", "title": "Build the Project" }, { + "location": "/os/get_started/project_create/#run-the-project", + "text": "You can run the simulated version of your project and see the simulated LED\nblink. $ newt run my_blinky_sim\nNo download script for BSP hw/bsp/native\nDebugging /workspace/bin/my_blinky_sim/apps/blinky/blinky.elf snip \nReading symbols from /workspace/bin/my_blinky_sim/apps/blinky/blinky.elf...done.\n(gdb) Type r at the (gdb) prompt to run the project. You will see an output indicating that the hal_gpio pin is toggling between 1 and 0 in a simulated blink.", + "title": "Run the Project" + }, + { "location": "/os/get_started/project_create/#complete", "text": "Congratulations, you have created your first project! The blinky application\nis not terribly exciting when it is run in the simulator, as there is no LED to\nblink. Apache Mynewt has a lot more functionality than just running simulated\napplications. It provides all the features you'll need to cross-compile your\napplication, run it on real hardware and develop a full featured application. If you're interested in learning more, a good next step is to dig in to one of\nthe tutorials and get a Mynewt project running on real hardware. Happy Hacking!", "title": "Complete" http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/bdd8fed4/os/get_started/project_create/index.html ---------------------------------------------------------------------- diff --git a/os/get_started/project_create/index.html b/os/get_started/project_create/index.html index d5e0515..e65a44e 100644 --- a/os/get_started/project_create/index.html +++ b/os/get_started/project_create/index.html @@ -484,14 +484,19 @@ App successfully built: /Users/sterling/dev/tmp/my_app/bin/my_blinky_sim/apps/bl <p><br></p> +<h3 id="run-the-project">Run the Project</h3> <p>You can run the simulated version of your project and see the simulated LED blink.</p> -<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">./bin/my_blinky_sim/apps/blinky/blinky.elf -hal_gpio set pin 1 to 0 +<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt run my_blinky_sim +No download script for BSP hw/bsp/native +Debugging /workspace/bin/my_blinky_sim/apps/blinky/blinky.elf +<snip> +Reading symbols from /workspace/bin/my_blinky_sim/apps/blinky/blinky.elf...done. +(gdb) </pre></div> -<p>Just press <em>ctrl-c</em> to exit.</p> +<p>Type <code>r</code> at the <code>(gdb)</code> prompt to run the project. You will see an output indicating that the <code>hal_gpio</code> pin is toggling between 1 and 0 in a simulated blink. </p> <p><br></p> <h3 id="complete">Complete</h3> <p>Congratulations, you have created your first project! The blinky application http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/bdd8fed4/sitemap.xml ---------------------------------------------------------------------- diff --git a/sitemap.xml b/sitemap.xml index c2797d6..fbdbfbb 100644 --- a/sitemap.xml +++ b/sitemap.xml @@ -4,7 +4,7 @@ <url> <loc>http://mynewt.apache.org/</loc> - <lastmod>2016-05-28</lastmod> + <lastmod>2016-05-30</lastmod> <changefreq>daily</changefreq> </url> @@ -12,7 +12,7 @@ <url> <loc>http://mynewt.apache.org/quick-start/</loc> - <lastmod>2016-05-28</lastmod> + <lastmod>2016-05-30</lastmod> <changefreq>daily</changefreq> </url> @@ -20,7 +20,7 @@ <url> <loc>http://mynewt.apache.org/about/</loc> - <lastmod>2016-05-28</lastmod> + <lastmod>2016-05-30</lastmod> <changefreq>daily</changefreq> </url> @@ -28,7 +28,7 @@ <url> <loc>http://mynewt.apache.org/download/</loc> - <lastmod>2016-05-28</lastmod> + <lastmod>2016-05-30</lastmod> <changefreq>daily</changefreq> </url> @@ -36,7 +36,7 @@ <url> <loc>http://mynewt.apache.org/community/</loc> - <lastmod>2016-05-28</lastmod> + <lastmod>2016-05-30</lastmod> <changefreq>daily</changefreq> </url> @@ -44,7 +44,7 @@ <url> <loc>http://mynewt.apache.org/events/</loc> - <lastmod>2016-05-28</lastmod> + <lastmod>2016-05-30</lastmod> <changefreq>daily</changefreq> </url> @@ -53,7 +53,7 @@ <url> <loc>http://mynewt.apache.org/os/introduction/</loc> - <lastmod>2016-05-28</lastmod> + <lastmod>2016-05-30</lastmod> <changefreq>daily</changefreq> </url> @@ -65,7 +65,7 @@ <url> <loc>http://mynewt.apache.org/os/get_started/vocabulary/</loc> - <lastmod>2016-05-28</lastmod> + <lastmod>2016-05-30</lastmod> <changefreq>daily</changefreq> </url> @@ -105,13 +105,13 @@ <url> <loc>http://mynewt.apache.org/faq/how_to_edit_docs/</loc> - <lastmod>2016-05-28</lastmod> + <lastmod>2016-05-30</lastmod> <changefreq>daily</changefreq> </url> <url> <loc>http://mynewt.apache.org/faq/answers/</loc> - <lastmod>2016-05-28</lastmod> + <lastmod>2016-05-30</lastmod> <changefreq>daily</changefreq> </url>
