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/12 01:41:43 UTC
[GitHub] aditihilbert closed pull request #345: automated asf-site build
aditihilbert closed pull request #345: automated asf-site build
URL: https://github.com/apache/mynewt-site/pull/345
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/faq/ide/index.html b/faq/ide/index.html
index 053444b71..4337a1d7f 100644
--- a/faq/ide/index.html
+++ b/faq/ide/index.html
@@ -421,7 +421,7 @@ <h4 id="defining-visual-studio-code-tasks-to-build-and-debug-mynewt-applications
<li>
<p><strong>create_arduino_blinky</strong>: Runs the <code>newt create-image arduino_blinky</code> command to create the image file.</p>
</li>
-<li><strong>debug_arduino_blinky</strong>: Runs the <code>newt build arduino_blinky -n</code> command to debug the arduino_blinky target. The <code>-n</code> flag is specified to start only the GDB server and not the GDB client. We will launch the GDB client from Visual Studio Code.</li>
+<li><strong>debug_arduino_blinky</strong>: Runs the <code>newt debug arduino_blinky -n</code> command to debug the arduino_blinky target. The <code>-n</code> flag is specified to start only the GDB server and not the GDB client. We will launch the GDB client from Visual Studio Code.</li>
</ol>
<p>For more information on tasks and all supported properties, see the <a href="https://code.visualstudio.com/docs/editor/tasks">Visual Studio Code Task documentation</a>.</p>
<p><br></p>
diff --git a/latest/faq/ide/index.html b/latest/faq/ide/index.html
index 053444b71..4337a1d7f 100644
--- a/latest/faq/ide/index.html
+++ b/latest/faq/ide/index.html
@@ -421,7 +421,7 @@ <h4 id="defining-visual-studio-code-tasks-to-build-and-debug-mynewt-applications
<li>
<p><strong>create_arduino_blinky</strong>: Runs the <code>newt create-image arduino_blinky</code> command to create the image file.</p>
</li>
-<li><strong>debug_arduino_blinky</strong>: Runs the <code>newt build arduino_blinky -n</code> command to debug the arduino_blinky target. The <code>-n</code> flag is specified to start only the GDB server and not the GDB client. We will launch the GDB client from Visual Studio Code.</li>
+<li><strong>debug_arduino_blinky</strong>: Runs the <code>newt debug arduino_blinky -n</code> command to debug the arduino_blinky target. The <code>-n</code> flag is specified to start only the GDB server and not the GDB client. We will launch the GDB client from Visual Studio Code.</li>
</ol>
<p>For more information on tasks and all supported properties, see the <a href="https://code.visualstudio.com/docs/editor/tasks">Visual Studio Code Task documentation</a>.</p>
<p><br></p>
diff --git a/latest/mkdocs/search_index.json b/latest/mkdocs/search_index.json
index 5a99794a7..e15cff403 100644
--- a/latest/mkdocs/search_index.json
+++ b/latest/mkdocs/search_index.json
@@ -13497,7 +13497,7 @@
},
{
"location": "/faq/ide/",
- "text": "Developing Mynewt Applications with Visual Studio Code\n\n\nThis guide shows you how to set up Visual Studio Code to develop and debug Mynewt applications. Visual Studio Code is supported on Mac OS, Linux, and Windows. This guide shows you how to:\n\n\n\n\nInstall Visual Studio Code. \n\n\nInstall the C/C++ and debugger extensions.\n\n\nDefine task configurations to build Mynewt applications.\n\n\nDefine debugger configurations to debug Mynewt applications. \n\n\nLaunch the debugger. \n\n\n\n\nPrerequisites:\n\n\n\n\nHave Internet connectivity to fetch remote Mynewt components.\n\n\nHave a computer to build a Mynewt application.\n\n\n\n\nPerform \nnative installation\n for the Mynewt tools and toolchains.\n\n\nNote:\n For Windows platforms, ensure that the MinGW bash you install is added to your Windows Path. In addition, if you are using Windows 10 WSL, you must have the MinGW bash before the Windows 10 WSL bash in your Windows Path.\n\n\n\n\n\n\nRead the Mynewt OS Concepts section.\n\n\n\n\nCreate a project space (directory structure) and populate it with the core code repository (apache-mynewt-core) or know how to as explained in Creating Your First Project. \n\n\nComplete one of the \nBlinky Tutorials\n.\n\n\n\n\nNotes:\n \n\n\n\n\nThis guide is not a tutorial for Visual Studio Code. It assumes you are familiar with Visual Studio Code. If this is your first time using Visual Studio Code, we recommend that you read the Visual Studio Code \ndocumentation and tutorials\n and evaluate whether you would like to use it to develop Mynewt applications. \n\n\nThis guide uses Visual Studio Code on Windows. Visual Studio Code is supported on Linux and Mac OS but may have some variations in the keyboard shortcuts and command names for these platforms. \n\n\nYou can also use the Eclipse IDE to develop Mynewt applications. See \nhttps://www.codecoup.pl/blog/hacking-mynewt-in-eclipse\n for more details. On Windows platforms, you must also ensure the MinGW bash is set in your Windows Path as described in the prerequisites.\n\n\n\n\nInstalling Visual Studio Code\n\n\nDownload and install Visual Studio Code from \nhttps://code.visualstudio.com/\n.\n\n\nInstalling the C/C++ and Debugger Extensions\n\n\nYou need to install two extensions:\n\n\n\n\n\n\nThe C/C++ extension from Microsoft. This extension provides language support such as symbol searching, signatuare help, go to definition, and go to declaration.\n\n\n\n\n\n\nThe Native Debug extension from webfreak. This extension provides GDB support. \n\n\n\n\n\n\n\nTo install the C/C++ extension:\n\n\n\n\nPress \nCtrl-P\n to open the search box.\n\n\nType \next install cpptools\n in the search box and press Enter. You should see the extension at the top of the list. \n\n\nClick \nInstall\n to install the extension. \n\n\n\n\n\nTo install the Native Debugger:\n\n\n\n\nPress \nCtrl-P\n to open the search box.\n\n\nType \next install webfreak.debug\n in the search box and press Enter. You should see the Native Debug extension at the top of the list.\n\n\nClick \nInstall\n to install the extension. \n\n\n\n\n\nDefining Tasks for Mynewt Projects\n\n\nTwo main concepts in Visual Studio Code are workspaces and tasks. A workspace represents a folder that is open. You can open multiple workspaces and switch between workspaces. \n\n\nTasks allow you to integrate the external tools and operations that are used to build or test your project into Visual Studio Code. Tasks are run from and the task results can be analyzed in Visual Studio Code. Tasks are defined within the scope of a workspace. This means that the tasks you define for a workspace only apply to the given workspace.\n\n\n\n\nAssociating a Mynewt Project to a Workspace\n\n\nFor your Mynewt project, your Visual Studio Code workspace is the Mynewt project base directory. For example, if you create a project named \nmyproj\n under the \n~/dev\n directory, then you open the \n~/dev/myproj\n folder for your workspace. \n\n\nSelect \nFile\n \n \nOpen Folder\n, and select the \nmyproj\n folder from the \nSelect Folder\n dialog box to open the folder.\n\n\n\n\nDefining Visual Studio Code Tasks to Build and Debug Mynewt Applications\n\n\nYou define Visual Studio Code tasks to build and debug your Mynewt targets in Visual Studio Code. We use the Blinky application for the Arduino Zero board from the \nBlinky On Arduino Zero Tutorial\n to illustrate how to define the tasks to build and debug the Arduino blinky bootloader and application targets.\n\n\nPerform the following steps to create the tasks to build and debug the Arduino blinky bootloader and appliction targets:\n\n\nStep 1: Press \nCtrl-Shift-P\n, type \ntask\n, and select \nTasks:Configure Task Runner\n from the search results. \n\n\nStep 2: Select \nOthers\n (scroll down to the bottom of the list) to create a task runner for external commands. \n\n\n\n\n\n\nTasks are defined in the \ntasks.json\n file. You should see the \n.vscode\n folder created in the \nMYPROJ\n folder and a \ntasks.json\n file created in the \n.vscode\n folder. The \ntasks.json\n file has the following default values. \n\n\n\n\n\n\n\n\nThe sample \ntasks.json\n file defines a simple task that runs the echo command with \"Hello World\" as the argument. \n\n\nStep 3: Delete the content from the \ntasks.json\n file, add the following definitions, and press \nCtrl-S\n to save the file.\n\n\n{\n \nversion\n: \n0.1.0\n,\n \ncommand\n: \nnewt\n,\n \nechoCommand\n: true,\n \nisShellCommand\n: true,\n\n \ntasks\n:[\n {\n \ntaskName\n: \nbuild_arduino_boot\n,\n \nargs\n: [\nbuild\n, \narduino_boot\n],\n \nsuppressTaskName\n: true\n },\n {\n \ntaskName\n: \nbuild_arduino_blinky\n,\n \nargs\n: [\nbuild\n, \narduino_blinky\n],\n \nisBuildCommand\n: true, \n \nsuppressTaskName\n: true\n },\n {\n \ntaskName\n: \ncreate_arduino_blinky\n,\n \nargs\n: [\ncreate-image\n, \narduino_blinky\n, \n1.0.0\n],\n \nsuppressTaskName\n:true\n }, \n {\n \ntaskName\n: \ndebug_arduino_blinky\n,\n \nargs\n: [\ndebug\n, \narduino_blinky\n, \n-n\n],\n \nsuppressTaskName\n: true\n }\n ]\n}\n\n\n\n\n\n\nThe \ntasks.json\n file specifies the tasks that are run to build and debug the Arduino blinky targets. Each task runs a \nnewt\n command. The \nnewt\n command to run and the arguments for the \nnewt\n command are passed in the \nargs\n property for each task. \n\n\nThe following tasks are defined in this example:\n\n\n\n\nbuild_arduino_boot\n: Runs the \nnewt build arduino_boot\n command to build the arduino_boot target.\n\n\n\n\nbuild_arduino_blinky\n: Runs the \nnewt build arduino_blinky\n command to build the arduino_blinky target. \n\n\nNote:\n This task sets the \nisBuildCommand\n property to \ntrue\n. This is an optional property that, when set to true, allows you to run the \nTasks: Run Build Task\n(\nCtrl-Shift-B\n) command to start the task.\n\n\n\n\n\n\ncreate_arduino_blinky\n: Runs the \nnewt create-image arduino_blinky\n command to create the image file.\n\n\n\n\ndebug_arduino_blinky\n: Runs the \nnewt build arduino_blinky -n\n command to debug the arduino_blinky target. The \n-n\n flag is specified to start only the GDB server and not the GDB client. We will launch the GDB client from Visual Studio Code.\n\n\n\n\nFor more information on tasks and all supported properties, see the \nVisual Studio Code Task documentation\n.\n\n\n\n\nRunning a Task\n\n\nTo run a task, press \nCtrl-Shift-P\n, type \ntask\n on the search box, and select \nTasks: Run Task\n. The tasks that you define in the \ntasks.json\n file are listed. Select the task to run. \n\n\nThe following is an example of running the \nbuild_arduino_boot\n task:\n\n\n\n\n\n\n\n\n\n\n\n\n\nNote\n:To run the \nbuild_arduino_blinky\n task, you can use the keyboard shortcut \nCtrl-Shift-B\n because the task has the property \nisBuildCommand\n set to true. \n\n\n\n\nDefining Tasks for Other Newt Commands\n\n\nOther newt commands, such as the \nnewt load\n command, do not need to run from within Visual Studio Code. You can define a task for each command as a convenience and run the command as a task, or you can run the newt command on the command line from the Visual Studio Code integrated terminal or an external terminal.\n\n\nTo create the tasks for the \nnewt load arduino_boot\n and \nnewt load arduino_blinky\n commands, add the following definitions to the \ntasks.json\n file:\n\n\n {\n \ntaskName\n: \nload_arduino_boot\n,\n \nargs\n: [\nload\n, \narduino_boot\n],\n \nsuppressTaskName\n:true\n }, \n {\n \ntaskName\n: \nload_arduino_blinky\n,\n \nargs\n: [\nload\n, \narduino_blinky\n],\n \nsuppressTaskName\n:true\n }, \n\n\n\n\n\n\nTo run a command from the Visual Studio integrated terminal, instead of starting a task, press \nCtrl-`\n to launch the integrated terminal and enter the command on the prompt:\n\n\n\n\n\n\n\nDefining Debugger Configurations\n\n\nYou need to define a debugger configuration to launch the GDB debugger from within Visual Studio Code: \n\n\nStep 1: Select \nDebug\n \n \nOpen Configuration\n, and select the \nGDB\n environment.\n\n\n\n\n\n\n\n\nYou should see a default \nlaunch.json\n file created in the \n.vscode\n folder.\n\n\n\n\n\n\n\n\nStep 2: Delete the content from the \nlaunch.json\n file, add the following definitions, and press 'Ctrl-S' to save the file.\n\n\n{\n \nversion\n: \n0.2.0\n,\n \nconfigurations\n: [\n {\n \nname\n: \ngdb_arduino_blinky\n,\n \ntype\n: \ngdb\n,\n \nrequest\n: \nattach\n,\n \nexecutable\n: \n${workspaceRoot}\\\\bin\\\\targets\\\\arduino_blinky\\\\app\\\\apps\\\\blinky\\\\blinky.elf\n,\n \ntarget\n: \n:3333\n,\n \ncwd\n: \n${workspaceRoot}\n,\n \ngdbpath\n: \nC:\\\\Program Files (x86)\\\\GNU Tools ARM Embedded\\\\4.9 2015q2\\\\bin\\\\arm-none-eabi-gdb.exe\n,\n \nremote\n: true\n\n }\n ]\n}\n\n\n\n\n\n\nThis defines a \ngdb_arduino_blinky\n debugger configuration. It specifies: \n\n\n\n\nThe debugger is type \ngdb\n.\n\n\nTo use the \nblinky.elf\n file for the executable. \n\n\nTo use port 3333 to connect with the remote target.\n\n\nTo use arm-none-eabi-gdb for the GDB program. \n\n\n\n\n\nDebugging Your Application\n\n\nTo debug your application, start the GDB server and launch the GDB session from Visual Studio Code. For the the arduino blinky example, perform the following:\n\n\nStep 1: Run the debug_arduino_blinky task to start the GDB server. Perform the following:\n\n\n\n\nPress \nCtrl-Shift-P\n and type \ntask\n in the search box. \n\n\nSelect \nTasks:Run Task\n \n \ndebug_arduino_blinky\n.\n\n\nPress \nCtrl-Shift-U\n to open the Output Panel and see the OpenOCD GDB Server output.\n\n \n\n\n\n\n\n\n\n\nStep 2: Start the GDB session. Perform the following: \n\n\n\n\nPress \nCtrl-Shift-Y\n to view the Debug Console. \n\n\nPress the Debugging icon on the activity bar (Ctrl-Shift-D) to bring up the Debug Side Bar.\n\n\nSelect \ngdb_arduino_blinky\n from the DEBUG drop down menu. \n\n\nPress the green play button to start the gdb session.\n\n\n\n\n\n\n\n\nStep 3: Debug your application. You should see a debug session similar to the one shown below:\n\n\n\n\nFor more information on how to use the Visual Studio Code Debugger, see the \nVisual Studio Code debugging documentation\n.\n\n\nWorking with Multiple Mynewt Applications\n\n\nAs mentioned previously, each mynewt project corresponds to a Visual Studio Code workspace. If you have multiple Mynewt application targets defined in same project, you will need to define build and debug tasks for each target in the \ntasks.json\n file and debugger configurations for the targets in the \nlaunch.json\n file for the workspace. If you have a different Mynewt project for each mynewt application, you will need to define build and debug tasks in the \ntasks.json\n file and the debugger configuration in the \nlaunch.json\n file for each workspace.",
+ "text": "Developing Mynewt Applications with Visual Studio Code\n\n\nThis guide shows you how to set up Visual Studio Code to develop and debug Mynewt applications. Visual Studio Code is supported on Mac OS, Linux, and Windows. This guide shows you how to:\n\n\n\n\nInstall Visual Studio Code. \n\n\nInstall the C/C++ and debugger extensions.\n\n\nDefine task configurations to build Mynewt applications.\n\n\nDefine debugger configurations to debug Mynewt applications. \n\n\nLaunch the debugger. \n\n\n\n\nPrerequisites:\n\n\n\n\nHave Internet connectivity to fetch remote Mynewt components.\n\n\nHave a computer to build a Mynewt application.\n\n\n\n\nPerform \nnative installation\n for the Mynewt tools and toolchains.\n\n\nNote:\n For Windows platforms, ensure that the MinGW bash you install is added to your Windows Path. In addition, if you are using Windows 10 WSL, you must have the MinGW bash before the Windows 10 WSL bash in your Windows Path.\n\n\n\n\n\n\nRead the Mynewt OS Concepts section.\n\n\n\n\nCreate a project space (directory structure) and populate it with the core code repository (apache-mynewt-core) or know how to as explained in Creating Your First Project. \n\n\nComplete one of the \nBlinky Tutorials\n.\n\n\n\n\nNotes:\n \n\n\n\n\nThis guide is not a tutorial for Visual Studio Code. It assumes you are familiar with Visual Studio Code. If this is your first time using Visual Studio Code, we recommend that you read the Visual Studio Code \ndocumentation and tutorials\n and evaluate whether you would like to use it to develop Mynewt applications. \n\n\nThis guide uses Visual Studio Code on Windows. Visual Studio Code is supported on Linux and Mac OS but may have some variations in the keyboard shortcuts and command names for these platforms. \n\n\nYou can also use the Eclipse IDE to develop Mynewt applications. See \nhttps://www.codecoup.pl/blog/hacking-mynewt-in-eclipse\n for more details. On Windows platforms, you must also ensure the MinGW bash is set in your Windows Path as described in the prerequisites.\n\n\n\n\nInstalling Visual Studio Code\n\n\nDownload and install Visual Studio Code from \nhttps://code.visualstudio.com/\n.\n\n\nInstalling the C/C++ and Debugger Extensions\n\n\nYou need to install two extensions:\n\n\n\n\n\n\nThe C/C++ extension from Microsoft. This extension provides language support such as symbol searching, signatuare help, go to definition, and go to declaration.\n\n\n\n\n\n\nThe Native Debug extension from webfreak. This extension provides GDB support. \n\n\n\n\n\n\n\nTo install the C/C++ extension:\n\n\n\n\nPress \nCtrl-P\n to open the search box.\n\n\nType \next install cpptools\n in the search box and press Enter. You should see the extension at the top of the list. \n\n\nClick \nInstall\n to install the extension. \n\n\n\n\n\nTo install the Native Debugger:\n\n\n\n\nPress \nCtrl-P\n to open the search box.\n\n\nType \next install webfreak.debug\n in the search box and press Enter. You should see the Native Debug extension at the top of the list.\n\n\nClick \nInstall\n to install the extension. \n\n\n\n\n\nDefining Tasks for Mynewt Projects\n\n\nTwo main concepts in Visual Studio Code are workspaces and tasks. A workspace represents a folder that is open. You can open multiple workspaces and switch between workspaces. \n\n\nTasks allow you to integrate the external tools and operations that are used to build or test your project into Visual Studio Code. Tasks are run from and the task results can be analyzed in Visual Studio Code. Tasks are defined within the scope of a workspace. This means that the tasks you define for a workspace only apply to the given workspace.\n\n\n\n\nAssociating a Mynewt Project to a Workspace\n\n\nFor your Mynewt project, your Visual Studio Code workspace is the Mynewt project base directory. For example, if you create a project named \nmyproj\n under the \n~/dev\n directory, then you open the \n~/dev/myproj\n folder for your workspace. \n\n\nSelect \nFile\n \n \nOpen Folder\n, and select the \nmyproj\n folder from the \nSelect Folder\n dialog box to open the folder.\n\n\n\n\nDefining Visual Studio Code Tasks to Build and Debug Mynewt Applications\n\n\nYou define Visual Studio Code tasks to build and debug your Mynewt targets in Visual Studio Code. We use the Blinky application for the Arduino Zero board from the \nBlinky On Arduino Zero Tutorial\n to illustrate how to define the tasks to build and debug the Arduino blinky bootloader and application targets.\n\n\nPerform the following steps to create the tasks to build and debug the Arduino blinky bootloader and appliction targets:\n\n\nStep 1: Press \nCtrl-Shift-P\n, type \ntask\n, and select \nTasks:Configure Task Runner\n from the search results. \n\n\nStep 2: Select \nOthers\n (scroll down to the bottom of the list) to create a task runner for external commands. \n\n\n\n\n\n\nTasks are defined in the \ntasks.json\n file. You should see the \n.vscode\n folder created in the \nMYPROJ\n folder and a \ntasks.json\n file created in the \n.vscode\n folder. The \ntasks.json\n file has the following default values. \n\n\n\n\n\n\n\n\nThe sample \ntasks.json\n file defines a simple task that runs the echo command with \"Hello World\" as the argument. \n\n\nStep 3: Delete the content from the \ntasks.json\n file, add the following definitions, and press \nCtrl-S\n to save the file.\n\n\n{\n \nversion\n: \n0.1.0\n,\n \ncommand\n: \nnewt\n,\n \nechoCommand\n: true,\n \nisShellCommand\n: true,\n\n \ntasks\n:[\n {\n \ntaskName\n: \nbuild_arduino_boot\n,\n \nargs\n: [\nbuild\n, \narduino_boot\n],\n \nsuppressTaskName\n: true\n },\n {\n \ntaskName\n: \nbuild_arduino_blinky\n,\n \nargs\n: [\nbuild\n, \narduino_blinky\n],\n \nisBuildCommand\n: true, \n \nsuppressTaskName\n: true\n },\n {\n \ntaskName\n: \ncreate_arduino_blinky\n,\n \nargs\n: [\ncreate-image\n, \narduino_blinky\n, \n1.0.0\n],\n \nsuppressTaskName\n:true\n }, \n {\n \ntaskName\n: \ndebug_arduino_blinky\n,\n \nargs\n: [\ndebug\n, \narduino_blinky\n, \n-n\n],\n \nsuppressTaskName\n: true\n }\n ]\n}\n\n\n\n\n\n\nThe \ntasks.json\n file specifies the tasks that are run to build and debug the Arduino blinky targets. Each task runs a \nnewt\n command. The \nnewt\n command to run and the arguments for the \nnewt\n command are passed in the \nargs\n property for each task. \n\n\nThe following tasks are defined in this example:\n\n\n\n\nbuild_arduino_boot\n: Runs the \nnewt build arduino_boot\n command to build the arduino_boot target.\n\n\n\n\nbuild_arduino_blinky\n: Runs the \nnewt build arduino_blinky\n command to build the arduino_blinky target. \n\n\nNote:\n This task sets the \nisBuildCommand\n property to \ntrue\n. This is an optional property that, when set to true, allows you to run the \nTasks: Run Build Task\n(\nCtrl-Shift-B\n) command to start the task.\n\n\n\n\n\n\ncreate_arduino_blinky\n: Runs the \nnewt create-image arduino_blinky\n command to create the image file.\n\n\n\n\ndebug_arduino_blinky\n: Runs the \nnewt debug arduino_blinky -n\n command to debug the arduino_blinky target. The \n-n\n flag is specified to start only the GDB server and not the GDB client. We will launch the GDB client from Visual Studio Code.\n\n\n\n\nFor more information on tasks and all supported properties, see the \nVisual Studio Code Task documentation\n.\n\n\n\n\nRunning a Task\n\n\nTo run a task, press \nCtrl-Shift-P\n, type \ntask\n on the search box, and select \nTasks: Run Task\n. The tasks that you define in the \ntasks.json\n file are listed. Select the task to run. \n\n\nThe following is an example of running the \nbuild_arduino_boot\n task:\n\n\n\n\n\n\n\n\n\n\n\n\n\nNote\n:To run the \nbuild_arduino_blinky\n task, you can use the keyboard shortcut \nCtrl-Shift-B\n because the task has the property \nisBuildCommand\n set to true. \n\n\n\n\nDefining Tasks for Other Newt Commands\n\n\nOther newt commands, such as the \nnewt load\n command, do not need to run from within Visual Studio Code. You can define a task for each command as a convenience and run the command as a task, or you can run the newt command on the command line from the Visual Studio Code integrated terminal or an external terminal.\n\n\nTo create the tasks for the \nnewt load arduino_boot\n and \nnewt load arduino_blinky\n commands, add the following definitions to the \ntasks.json\n file:\n\n\n {\n \ntaskName\n: \nload_arduino_boot\n,\n \nargs\n: [\nload\n, \narduino_boot\n],\n \nsuppressTaskName\n:true\n }, \n {\n \ntaskName\n: \nload_arduino_blinky\n,\n \nargs\n: [\nload\n, \narduino_blinky\n],\n \nsuppressTaskName\n:true\n }, \n\n\n\n\n\n\nTo run a command from the Visual Studio integrated terminal, instead of starting a task, press \nCtrl-`\n to launch the integrated terminal and enter the command on the prompt:\n\n\n\n\n\n\n\nDefining Debugger Configurations\n\n\nYou need to define a debugger configuration to launch the GDB debugger from within Visual Studio Code: \n\n\nStep 1: Select \nDebug\n \n \nOpen Configuration\n, and select the \nGDB\n environment.\n\n\n\n\n\n\n\n\nYou should see a default \nlaunch.json\n file created in the \n.vscode\n folder.\n\n\n\n\n\n\n\n\nStep 2: Delete the content from the \nlaunch.json\n file, add the following definitions, and press 'Ctrl-S' to save the file.\n\n\n{\n \nversion\n: \n0.2.0\n,\n \nconfigurations\n: [\n {\n \nname\n: \ngdb_arduino_blinky\n,\n \ntype\n: \ngdb\n,\n \nrequest\n: \nattach\n,\n \nexecutable\n: \n${workspaceRoot}\\\\bin\\\\targets\\\\arduino_blinky\\\\app\\\\apps\\\\blinky\\\\blinky.elf\n,\n \ntarget\n: \n:3333\n,\n \ncwd\n: \n${workspaceRoot}\n,\n \ngdbpath\n: \nC:\\\\Program Files (x86)\\\\GNU Tools ARM Embedded\\\\4.9 2015q2\\\\bin\\\\arm-none-eabi-gdb.exe\n,\n \nremote\n: true\n\n }\n ]\n}\n\n\n\n\n\n\nThis defines a \ngdb_arduino_blinky\n debugger configuration. It specifies: \n\n\n\n\nThe debugger is type \ngdb\n.\n\n\nTo use the \nblinky.elf\n file for the executable. \n\n\nTo use port 3333 to connect with the remote target.\n\n\nTo use arm-none-eabi-gdb for the GDB program. \n\n\n\n\n\nDebugging Your Application\n\n\nTo debug your application, start the GDB server and launch the GDB session from Visual Studio Code. For the the arduino blinky example, perform the following:\n\n\nStep 1: Run the debug_arduino_blinky task to start the GDB server. Perform the following:\n\n\n\n\nPress \nCtrl-Shift-P\n and type \ntask\n in the search box. \n\n\nSelect \nTasks:Run Task\n \n \ndebug_arduino_blinky\n.\n\n\nPress \nCtrl-Shift-U\n to open the Output Panel and see the OpenOCD GDB Server output.\n\n \n\n\n\n\n\n\n\n\nStep 2: Start the GDB session. Perform the following: \n\n\n\n\nPress \nCtrl-Shift-Y\n to view the Debug Console. \n\n\nPress the Debugging icon on the activity bar (Ctrl-Shift-D) to bring up the Debug Side Bar.\n\n\nSelect \ngdb_arduino_blinky\n from the DEBUG drop down menu. \n\n\nPress the green play button to start the gdb session.\n\n\n\n\n\n\n\n\nStep 3: Debug your application. You should see a debug session similar to the one shown below:\n\n\n\n\nFor more information on how to use the Visual Studio Code Debugger, see the \nVisual Studio Code debugging documentation\n.\n\n\nWorking with Multiple Mynewt Applications\n\n\nAs mentioned previously, each mynewt project corresponds to a Visual Studio Code workspace. If you have multiple Mynewt application targets defined in same project, you will need to define build and debug tasks for each target in the \ntasks.json\n file and debugger configurations for the targets in the \nlaunch.json\n file for the workspace. If you have a different Mynewt project for each mynewt application, you will need to define build and debug tasks in the \ntasks.json\n file and the debugger configuration in the \nlaunch.json\n file for each workspace.",
"title": "Using an IDE to Develop Mynewt Applications"
},
{
@@ -13527,7 +13527,7 @@
},
{
"location": "/faq/ide/#defining-visual-studio-code-tasks-to-build-and-debug-mynewt-applications",
- "text": "You define Visual Studio Code tasks to build and debug your Mynewt targets in Visual Studio Code. We use the Blinky application for the Arduino Zero board from the Blinky On Arduino Zero Tutorial to illustrate how to define the tasks to build and debug the Arduino blinky bootloader and application targets. Perform the following steps to create the tasks to build and debug the Arduino blinky bootloader and appliction targets: Step 1: Press Ctrl-Shift-P , type task , and select Tasks:Configure Task Runner from the search results. Step 2: Select Others (scroll down to the bottom of the list) to create a task runner for external commands. \nTasks are defined in the tasks.json file. You should see the .vscode folder created in the MYPROJ folder and a tasks.json file created in the .vscode folder. The tasks.json file has the following default values. The sample tasks.json file defines a simple task that runs the echo command with \"Hello World\" as the argument. Step 3: Delete the content from the tasks.json file, add the following definitions, and press Ctrl-S to save the file. {\n version : 0.1.0 ,\n command : newt ,\n echoCommand : true,\n isShellCommand : true,\n\n tasks :[\n {\n taskName : build_arduino_boot ,\n args : [ build , arduino_boot ],\n suppressTaskName : true\n },\n {\n taskName : build_arduino_blinky ,\n args : [ build , arduino_blinky ],\n isBuildCommand : true, \n suppressTaskName : true\n },\n {\n taskName : create_arduino_blinky ,\n args : [ create-image , arduino_blinky , 1.0.0 ],\n suppressTaskName :true\n }, \n {\n taskName : debug_arduino_blinky ,\n args : [ debug , arduino_blinky , -n ],\n suppressTaskName : true\n }\n ]\n} \nThe tasks.json file specifies the tasks that are run to build and debug the Arduino blinky targets. Each task runs a newt command. The newt command to run and the arguments for the newt command are passed in the args property for each task. The following tasks are defined in this example: build_arduino_boot : Runs the newt build arduino_boot command to build the arduino_boot target. build_arduino_blinky : Runs the newt build arduino_blinky command to build the arduino_blinky target. Note: This task sets the isBuildCommand property to true . This is an optional property that, when set to true, allows you to run the Tasks: Run Build Task ( Ctrl-Shift-B ) command to start the task. create_arduino_blinky : Runs the newt create-image arduino_blinky command to create the image file. debug_arduino_blinky : Runs the newt build arduino_blinky -n command to debug the arduino_blinky target. The -n flag is specified to start only the GDB server and not the GDB client. We will launch the GDB client from Visual Studio Code. For more information on tasks and all supported properties, see the Visual Studio Code Task documentation .",
+ "text": "You define Visual Studio Code tasks to build and debug your Mynewt targets in Visual Studio Code. We use the Blinky application for the Arduino Zero board from the Blinky On Arduino Zero Tutorial to illustrate how to define the tasks to build and debug the Arduino blinky bootloader and application targets. Perform the following steps to create the tasks to build and debug the Arduino blinky bootloader and appliction targets: Step 1: Press Ctrl-Shift-P , type task , and select Tasks:Configure Task Runner from the search results. Step 2: Select Others (scroll down to the bottom of the list) to create a task runner for external commands. \nTasks are defined in the tasks.json file. You should see the .vscode folder created in the MYPROJ folder and a tasks.json file created in the .vscode folder. The tasks.json file has the following default values. The sample tasks.json file defines a simple task that runs the echo command with \"Hello World\" as the argument. Step 3: Delete the content from the tasks.json file, add the following definitions, and press Ctrl-S to save the file. {\n version : 0.1.0 ,\n command : newt ,\n echoCommand : true,\n isShellCommand : true,\n\n tasks :[\n {\n taskName : build_arduino_boot ,\n args : [ build , arduino_boot ],\n suppressTaskName : true\n },\n {\n taskName : build_arduino_blinky ,\n args : [ build , arduino_blinky ],\n isBuildCommand : true, \n suppressTaskName : true\n },\n {\n taskName : create_arduino_blinky ,\n args : [ create-image , arduino_blinky , 1.0.0 ],\n suppressTaskName :true\n }, \n {\n taskName : debug_arduino_blinky ,\n args : [ debug , arduino_blinky , -n ],\n suppressTaskName : true\n }\n ]\n} \nThe tasks.json file specifies the tasks that are run to build and debug the Arduino blinky targets. Each task runs a newt command. The newt command to run and the arguments for the newt command are passed in the args property for each task. The following tasks are defined in this example: build_arduino_boot : Runs the newt build arduino_boot command to build the arduino_boot target. build_arduino_blinky : Runs the newt build arduino_blinky command to build the arduino_blinky target. Note: This task sets the isBuildCommand property to true . This is an optional property that, when set to true, allows you to run the Tasks: Run Build Task ( Ctrl-Shift-B ) command to start the task. create_arduino_blinky : Runs the newt create-image arduino_blinky command to create the image file. debug_arduino_blinky : Runs the newt debug arduino_blinky -n command to debug the arduino_blinky target. The -n flag is specified to start only the GDB server and not the GDB client. We will launch the GDB client from Visual Studio Code. For more information on tasks and all supported properties, see the Visual Studio Code Task documentation .",
"title": "Defining Visual Studio Code Tasks to Build and Debug Mynewt Applications"
},
{
diff --git a/latest/sitemap.xml b/latest/sitemap.xml
index 5aeaa1f17..2239773c3 100644
--- a/latest/sitemap.xml
+++ b/latest/sitemap.xml
@@ -4,7 +4,7 @@
<url>
<loc>http://mynewt.apache.org/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -13,13 +13,13 @@
<url>
<loc>http://mynewt.apache.org/pages/ble/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/pages/securitybullets/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -28,7 +28,7 @@
<url>
<loc>http://mynewt.apache.org/quick-start/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -36,7 +36,7 @@
<url>
<loc>http://mynewt.apache.org/about/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -44,7 +44,7 @@
<url>
<loc>http://mynewt.apache.org/talks/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -52,7 +52,7 @@
<url>
<loc>http://mynewt.apache.org/download/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -60,7 +60,7 @@
<url>
<loc>http://mynewt.apache.org/community/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -68,7 +68,7 @@
<url>
<loc>http://mynewt.apache.org/events/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -77,7 +77,7 @@
<url>
<loc>http://mynewt.apache.org/os/introduction/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -89,7 +89,7 @@
<url>
<loc>http://mynewt.apache.org/os/get_started/vocabulary/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -125,7 +125,7 @@
<url>
<loc>http://mynewt.apache.org/known_issues/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -135,37 +135,37 @@
<url>
<loc>http://mynewt.apache.org/newt/install/prev_releases/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/newtmgr/prev_releases/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/go_env/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/ide/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/how_to_edit_docs/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/answers/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
diff --git a/mkdocs/search_index.json b/mkdocs/search_index.json
index 5a99794a7..e15cff403 100644
--- a/mkdocs/search_index.json
+++ b/mkdocs/search_index.json
@@ -13497,7 +13497,7 @@
},
{
"location": "/faq/ide/",
- "text": "Developing Mynewt Applications with Visual Studio Code\n\n\nThis guide shows you how to set up Visual Studio Code to develop and debug Mynewt applications. Visual Studio Code is supported on Mac OS, Linux, and Windows. This guide shows you how to:\n\n\n\n\nInstall Visual Studio Code. \n\n\nInstall the C/C++ and debugger extensions.\n\n\nDefine task configurations to build Mynewt applications.\n\n\nDefine debugger configurations to debug Mynewt applications. \n\n\nLaunch the debugger. \n\n\n\n\nPrerequisites:\n\n\n\n\nHave Internet connectivity to fetch remote Mynewt components.\n\n\nHave a computer to build a Mynewt application.\n\n\n\n\nPerform \nnative installation\n for the Mynewt tools and toolchains.\n\n\nNote:\n For Windows platforms, ensure that the MinGW bash you install is added to your Windows Path. In addition, if you are using Windows 10 WSL, you must have the MinGW bash before the Windows 10 WSL bash in your Windows Path.\n\n\n\n\n\n\nRead the Mynewt OS Concepts section.\n\n\n\n\nCreate a project space (directory structure) and populate it with the core code repository (apache-mynewt-core) or know how to as explained in Creating Your First Project. \n\n\nComplete one of the \nBlinky Tutorials\n.\n\n\n\n\nNotes:\n \n\n\n\n\nThis guide is not a tutorial for Visual Studio Code. It assumes you are familiar with Visual Studio Code. If this is your first time using Visual Studio Code, we recommend that you read the Visual Studio Code \ndocumentation and tutorials\n and evaluate whether you would like to use it to develop Mynewt applications. \n\n\nThis guide uses Visual Studio Code on Windows. Visual Studio Code is supported on Linux and Mac OS but may have some variations in the keyboard shortcuts and command names for these platforms. \n\n\nYou can also use the Eclipse IDE to develop Mynewt applications. See \nhttps://www.codecoup.pl/blog/hacking-mynewt-in-eclipse\n for more details. On Windows platforms, you must also ensure the MinGW bash is set in your Windows Path as described in the prerequisites.\n\n\n\n\nInstalling Visual Studio Code\n\n\nDownload and install Visual Studio Code from \nhttps://code.visualstudio.com/\n.\n\n\nInstalling the C/C++ and Debugger Extensions\n\n\nYou need to install two extensions:\n\n\n\n\n\n\nThe C/C++ extension from Microsoft. This extension provides language support such as symbol searching, signatuare help, go to definition, and go to declaration.\n\n\n\n\n\n\nThe Native Debug extension from webfreak. This extension provides GDB support. \n\n\n\n\n\n\n\nTo install the C/C++ extension:\n\n\n\n\nPress \nCtrl-P\n to open the search box.\n\n\nType \next install cpptools\n in the search box and press Enter. You should see the extension at the top of the list. \n\n\nClick \nInstall\n to install the extension. \n\n\n\n\n\nTo install the Native Debugger:\n\n\n\n\nPress \nCtrl-P\n to open the search box.\n\n\nType \next install webfreak.debug\n in the search box and press Enter. You should see the Native Debug extension at the top of the list.\n\n\nClick \nInstall\n to install the extension. \n\n\n\n\n\nDefining Tasks for Mynewt Projects\n\n\nTwo main concepts in Visual Studio Code are workspaces and tasks. A workspace represents a folder that is open. You can open multiple workspaces and switch between workspaces. \n\n\nTasks allow you to integrate the external tools and operations that are used to build or test your project into Visual Studio Code. Tasks are run from and the task results can be analyzed in Visual Studio Code. Tasks are defined within the scope of a workspace. This means that the tasks you define for a workspace only apply to the given workspace.\n\n\n\n\nAssociating a Mynewt Project to a Workspace\n\n\nFor your Mynewt project, your Visual Studio Code workspace is the Mynewt project base directory. For example, if you create a project named \nmyproj\n under the \n~/dev\n directory, then you open the \n~/dev/myproj\n folder for your workspace. \n\n\nSelect \nFile\n \n \nOpen Folder\n, and select the \nmyproj\n folder from the \nSelect Folder\n dialog box to open the folder.\n\n\n\n\nDefining Visual Studio Code Tasks to Build and Debug Mynewt Applications\n\n\nYou define Visual Studio Code tasks to build and debug your Mynewt targets in Visual Studio Code. We use the Blinky application for the Arduino Zero board from the \nBlinky On Arduino Zero Tutorial\n to illustrate how to define the tasks to build and debug the Arduino blinky bootloader and application targets.\n\n\nPerform the following steps to create the tasks to build and debug the Arduino blinky bootloader and appliction targets:\n\n\nStep 1: Press \nCtrl-Shift-P\n, type \ntask\n, and select \nTasks:Configure Task Runner\n from the search results. \n\n\nStep 2: Select \nOthers\n (scroll down to the bottom of the list) to create a task runner for external commands. \n\n\n\n\n\n\nTasks are defined in the \ntasks.json\n file. You should see the \n.vscode\n folder created in the \nMYPROJ\n folder and a \ntasks.json\n file created in the \n.vscode\n folder. The \ntasks.json\n file has the following default values. \n\n\n\n\n\n\n\n\nThe sample \ntasks.json\n file defines a simple task that runs the echo command with \"Hello World\" as the argument. \n\n\nStep 3: Delete the content from the \ntasks.json\n file, add the following definitions, and press \nCtrl-S\n to save the file.\n\n\n{\n \nversion\n: \n0.1.0\n,\n \ncommand\n: \nnewt\n,\n \nechoCommand\n: true,\n \nisShellCommand\n: true,\n\n \ntasks\n:[\n {\n \ntaskName\n: \nbuild_arduino_boot\n,\n \nargs\n: [\nbuild\n, \narduino_boot\n],\n \nsuppressTaskName\n: true\n },\n {\n \ntaskName\n: \nbuild_arduino_blinky\n,\n \nargs\n: [\nbuild\n, \narduino_blinky\n],\n \nisBuildCommand\n: true, \n \nsuppressTaskName\n: true\n },\n {\n \ntaskName\n: \ncreate_arduino_blinky\n,\n \nargs\n: [\ncreate-image\n, \narduino_blinky\n, \n1.0.0\n],\n \nsuppressTaskName\n:true\n }, \n {\n \ntaskName\n: \ndebug_arduino_blinky\n,\n \nargs\n: [\ndebug\n, \narduino_blinky\n, \n-n\n],\n \nsuppressTaskName\n: true\n }\n ]\n}\n\n\n\n\n\n\nThe \ntasks.json\n file specifies the tasks that are run to build and debug the Arduino blinky targets. Each task runs a \nnewt\n command. The \nnewt\n command to run and the arguments for the \nnewt\n command are passed in the \nargs\n property for each task. \n\n\nThe following tasks are defined in this example:\n\n\n\n\nbuild_arduino_boot\n: Runs the \nnewt build arduino_boot\n command to build the arduino_boot target.\n\n\n\n\nbuild_arduino_blinky\n: Runs the \nnewt build arduino_blinky\n command to build the arduino_blinky target. \n\n\nNote:\n This task sets the \nisBuildCommand\n property to \ntrue\n. This is an optional property that, when set to true, allows you to run the \nTasks: Run Build Task\n(\nCtrl-Shift-B\n) command to start the task.\n\n\n\n\n\n\ncreate_arduino_blinky\n: Runs the \nnewt create-image arduino_blinky\n command to create the image file.\n\n\n\n\ndebug_arduino_blinky\n: Runs the \nnewt build arduino_blinky -n\n command to debug the arduino_blinky target. The \n-n\n flag is specified to start only the GDB server and not the GDB client. We will launch the GDB client from Visual Studio Code.\n\n\n\n\nFor more information on tasks and all supported properties, see the \nVisual Studio Code Task documentation\n.\n\n\n\n\nRunning a Task\n\n\nTo run a task, press \nCtrl-Shift-P\n, type \ntask\n on the search box, and select \nTasks: Run Task\n. The tasks that you define in the \ntasks.json\n file are listed. Select the task to run. \n\n\nThe following is an example of running the \nbuild_arduino_boot\n task:\n\n\n\n\n\n\n\n\n\n\n\n\n\nNote\n:To run the \nbuild_arduino_blinky\n task, you can use the keyboard shortcut \nCtrl-Shift-B\n because the task has the property \nisBuildCommand\n set to true. \n\n\n\n\nDefining Tasks for Other Newt Commands\n\n\nOther newt commands, such as the \nnewt load\n command, do not need to run from within Visual Studio Code. You can define a task for each command as a convenience and run the command as a task, or you can run the newt command on the command line from the Visual Studio Code integrated terminal or an external terminal.\n\n\nTo create the tasks for the \nnewt load arduino_boot\n and \nnewt load arduino_blinky\n commands, add the following definitions to the \ntasks.json\n file:\n\n\n {\n \ntaskName\n: \nload_arduino_boot\n,\n \nargs\n: [\nload\n, \narduino_boot\n],\n \nsuppressTaskName\n:true\n }, \n {\n \ntaskName\n: \nload_arduino_blinky\n,\n \nargs\n: [\nload\n, \narduino_blinky\n],\n \nsuppressTaskName\n:true\n }, \n\n\n\n\n\n\nTo run a command from the Visual Studio integrated terminal, instead of starting a task, press \nCtrl-`\n to launch the integrated terminal and enter the command on the prompt:\n\n\n\n\n\n\n\nDefining Debugger Configurations\n\n\nYou need to define a debugger configuration to launch the GDB debugger from within Visual Studio Code: \n\n\nStep 1: Select \nDebug\n \n \nOpen Configuration\n, and select the \nGDB\n environment.\n\n\n\n\n\n\n\n\nYou should see a default \nlaunch.json\n file created in the \n.vscode\n folder.\n\n\n\n\n\n\n\n\nStep 2: Delete the content from the \nlaunch.json\n file, add the following definitions, and press 'Ctrl-S' to save the file.\n\n\n{\n \nversion\n: \n0.2.0\n,\n \nconfigurations\n: [\n {\n \nname\n: \ngdb_arduino_blinky\n,\n \ntype\n: \ngdb\n,\n \nrequest\n: \nattach\n,\n \nexecutable\n: \n${workspaceRoot}\\\\bin\\\\targets\\\\arduino_blinky\\\\app\\\\apps\\\\blinky\\\\blinky.elf\n,\n \ntarget\n: \n:3333\n,\n \ncwd\n: \n${workspaceRoot}\n,\n \ngdbpath\n: \nC:\\\\Program Files (x86)\\\\GNU Tools ARM Embedded\\\\4.9 2015q2\\\\bin\\\\arm-none-eabi-gdb.exe\n,\n \nremote\n: true\n\n }\n ]\n}\n\n\n\n\n\n\nThis defines a \ngdb_arduino_blinky\n debugger configuration. It specifies: \n\n\n\n\nThe debugger is type \ngdb\n.\n\n\nTo use the \nblinky.elf\n file for the executable. \n\n\nTo use port 3333 to connect with the remote target.\n\n\nTo use arm-none-eabi-gdb for the GDB program. \n\n\n\n\n\nDebugging Your Application\n\n\nTo debug your application, start the GDB server and launch the GDB session from Visual Studio Code. For the the arduino blinky example, perform the following:\n\n\nStep 1: Run the debug_arduino_blinky task to start the GDB server. Perform the following:\n\n\n\n\nPress \nCtrl-Shift-P\n and type \ntask\n in the search box. \n\n\nSelect \nTasks:Run Task\n \n \ndebug_arduino_blinky\n.\n\n\nPress \nCtrl-Shift-U\n to open the Output Panel and see the OpenOCD GDB Server output.\n\n \n\n\n\n\n\n\n\n\nStep 2: Start the GDB session. Perform the following: \n\n\n\n\nPress \nCtrl-Shift-Y\n to view the Debug Console. \n\n\nPress the Debugging icon on the activity bar (Ctrl-Shift-D) to bring up the Debug Side Bar.\n\n\nSelect \ngdb_arduino_blinky\n from the DEBUG drop down menu. \n\n\nPress the green play button to start the gdb session.\n\n\n\n\n\n\n\n\nStep 3: Debug your application. You should see a debug session similar to the one shown below:\n\n\n\n\nFor more information on how to use the Visual Studio Code Debugger, see the \nVisual Studio Code debugging documentation\n.\n\n\nWorking with Multiple Mynewt Applications\n\n\nAs mentioned previously, each mynewt project corresponds to a Visual Studio Code workspace. If you have multiple Mynewt application targets defined in same project, you will need to define build and debug tasks for each target in the \ntasks.json\n file and debugger configurations for the targets in the \nlaunch.json\n file for the workspace. If you have a different Mynewt project for each mynewt application, you will need to define build and debug tasks in the \ntasks.json\n file and the debugger configuration in the \nlaunch.json\n file for each workspace.",
+ "text": "Developing Mynewt Applications with Visual Studio Code\n\n\nThis guide shows you how to set up Visual Studio Code to develop and debug Mynewt applications. Visual Studio Code is supported on Mac OS, Linux, and Windows. This guide shows you how to:\n\n\n\n\nInstall Visual Studio Code. \n\n\nInstall the C/C++ and debugger extensions.\n\n\nDefine task configurations to build Mynewt applications.\n\n\nDefine debugger configurations to debug Mynewt applications. \n\n\nLaunch the debugger. \n\n\n\n\nPrerequisites:\n\n\n\n\nHave Internet connectivity to fetch remote Mynewt components.\n\n\nHave a computer to build a Mynewt application.\n\n\n\n\nPerform \nnative installation\n for the Mynewt tools and toolchains.\n\n\nNote:\n For Windows platforms, ensure that the MinGW bash you install is added to your Windows Path. In addition, if you are using Windows 10 WSL, you must have the MinGW bash before the Windows 10 WSL bash in your Windows Path.\n\n\n\n\n\n\nRead the Mynewt OS Concepts section.\n\n\n\n\nCreate a project space (directory structure) and populate it with the core code repository (apache-mynewt-core) or know how to as explained in Creating Your First Project. \n\n\nComplete one of the \nBlinky Tutorials\n.\n\n\n\n\nNotes:\n \n\n\n\n\nThis guide is not a tutorial for Visual Studio Code. It assumes you are familiar with Visual Studio Code. If this is your first time using Visual Studio Code, we recommend that you read the Visual Studio Code \ndocumentation and tutorials\n and evaluate whether you would like to use it to develop Mynewt applications. \n\n\nThis guide uses Visual Studio Code on Windows. Visual Studio Code is supported on Linux and Mac OS but may have some variations in the keyboard shortcuts and command names for these platforms. \n\n\nYou can also use the Eclipse IDE to develop Mynewt applications. See \nhttps://www.codecoup.pl/blog/hacking-mynewt-in-eclipse\n for more details. On Windows platforms, you must also ensure the MinGW bash is set in your Windows Path as described in the prerequisites.\n\n\n\n\nInstalling Visual Studio Code\n\n\nDownload and install Visual Studio Code from \nhttps://code.visualstudio.com/\n.\n\n\nInstalling the C/C++ and Debugger Extensions\n\n\nYou need to install two extensions:\n\n\n\n\n\n\nThe C/C++ extension from Microsoft. This extension provides language support such as symbol searching, signatuare help, go to definition, and go to declaration.\n\n\n\n\n\n\nThe Native Debug extension from webfreak. This extension provides GDB support. \n\n\n\n\n\n\n\nTo install the C/C++ extension:\n\n\n\n\nPress \nCtrl-P\n to open the search box.\n\n\nType \next install cpptools\n in the search box and press Enter. You should see the extension at the top of the list. \n\n\nClick \nInstall\n to install the extension. \n\n\n\n\n\nTo install the Native Debugger:\n\n\n\n\nPress \nCtrl-P\n to open the search box.\n\n\nType \next install webfreak.debug\n in the search box and press Enter. You should see the Native Debug extension at the top of the list.\n\n\nClick \nInstall\n to install the extension. \n\n\n\n\n\nDefining Tasks for Mynewt Projects\n\n\nTwo main concepts in Visual Studio Code are workspaces and tasks. A workspace represents a folder that is open. You can open multiple workspaces and switch between workspaces. \n\n\nTasks allow you to integrate the external tools and operations that are used to build or test your project into Visual Studio Code. Tasks are run from and the task results can be analyzed in Visual Studio Code. Tasks are defined within the scope of a workspace. This means that the tasks you define for a workspace only apply to the given workspace.\n\n\n\n\nAssociating a Mynewt Project to a Workspace\n\n\nFor your Mynewt project, your Visual Studio Code workspace is the Mynewt project base directory. For example, if you create a project named \nmyproj\n under the \n~/dev\n directory, then you open the \n~/dev/myproj\n folder for your workspace. \n\n\nSelect \nFile\n \n \nOpen Folder\n, and select the \nmyproj\n folder from the \nSelect Folder\n dialog box to open the folder.\n\n\n\n\nDefining Visual Studio Code Tasks to Build and Debug Mynewt Applications\n\n\nYou define Visual Studio Code tasks to build and debug your Mynewt targets in Visual Studio Code. We use the Blinky application for the Arduino Zero board from the \nBlinky On Arduino Zero Tutorial\n to illustrate how to define the tasks to build and debug the Arduino blinky bootloader and application targets.\n\n\nPerform the following steps to create the tasks to build and debug the Arduino blinky bootloader and appliction targets:\n\n\nStep 1: Press \nCtrl-Shift-P\n, type \ntask\n, and select \nTasks:Configure Task Runner\n from the search results. \n\n\nStep 2: Select \nOthers\n (scroll down to the bottom of the list) to create a task runner for external commands. \n\n\n\n\n\n\nTasks are defined in the \ntasks.json\n file. You should see the \n.vscode\n folder created in the \nMYPROJ\n folder and a \ntasks.json\n file created in the \n.vscode\n folder. The \ntasks.json\n file has the following default values. \n\n\n\n\n\n\n\n\nThe sample \ntasks.json\n file defines a simple task that runs the echo command with \"Hello World\" as the argument. \n\n\nStep 3: Delete the content from the \ntasks.json\n file, add the following definitions, and press \nCtrl-S\n to save the file.\n\n\n{\n \nversion\n: \n0.1.0\n,\n \ncommand\n: \nnewt\n,\n \nechoCommand\n: true,\n \nisShellCommand\n: true,\n\n \ntasks\n:[\n {\n \ntaskName\n: \nbuild_arduino_boot\n,\n \nargs\n: [\nbuild\n, \narduino_boot\n],\n \nsuppressTaskName\n: true\n },\n {\n \ntaskName\n: \nbuild_arduino_blinky\n,\n \nargs\n: [\nbuild\n, \narduino_blinky\n],\n \nisBuildCommand\n: true, \n \nsuppressTaskName\n: true\n },\n {\n \ntaskName\n: \ncreate_arduino_blinky\n,\n \nargs\n: [\ncreate-image\n, \narduino_blinky\n, \n1.0.0\n],\n \nsuppressTaskName\n:true\n }, \n {\n \ntaskName\n: \ndebug_arduino_blinky\n,\n \nargs\n: [\ndebug\n, \narduino_blinky\n, \n-n\n],\n \nsuppressTaskName\n: true\n }\n ]\n}\n\n\n\n\n\n\nThe \ntasks.json\n file specifies the tasks that are run to build and debug the Arduino blinky targets. Each task runs a \nnewt\n command. The \nnewt\n command to run and the arguments for the \nnewt\n command are passed in the \nargs\n property for each task. \n\n\nThe following tasks are defined in this example:\n\n\n\n\nbuild_arduino_boot\n: Runs the \nnewt build arduino_boot\n command to build the arduino_boot target.\n\n\n\n\nbuild_arduino_blinky\n: Runs the \nnewt build arduino_blinky\n command to build the arduino_blinky target. \n\n\nNote:\n This task sets the \nisBuildCommand\n property to \ntrue\n. This is an optional property that, when set to true, allows you to run the \nTasks: Run Build Task\n(\nCtrl-Shift-B\n) command to start the task.\n\n\n\n\n\n\ncreate_arduino_blinky\n: Runs the \nnewt create-image arduino_blinky\n command to create the image file.\n\n\n\n\ndebug_arduino_blinky\n: Runs the \nnewt debug arduino_blinky -n\n command to debug the arduino_blinky target. The \n-n\n flag is specified to start only the GDB server and not the GDB client. We will launch the GDB client from Visual Studio Code.\n\n\n\n\nFor more information on tasks and all supported properties, see the \nVisual Studio Code Task documentation\n.\n\n\n\n\nRunning a Task\n\n\nTo run a task, press \nCtrl-Shift-P\n, type \ntask\n on the search box, and select \nTasks: Run Task\n. The tasks that you define in the \ntasks.json\n file are listed. Select the task to run. \n\n\nThe following is an example of running the \nbuild_arduino_boot\n task:\n\n\n\n\n\n\n\n\n\n\n\n\n\nNote\n:To run the \nbuild_arduino_blinky\n task, you can use the keyboard shortcut \nCtrl-Shift-B\n because the task has the property \nisBuildCommand\n set to true. \n\n\n\n\nDefining Tasks for Other Newt Commands\n\n\nOther newt commands, such as the \nnewt load\n command, do not need to run from within Visual Studio Code. You can define a task for each command as a convenience and run the command as a task, or you can run the newt command on the command line from the Visual Studio Code integrated terminal or an external terminal.\n\n\nTo create the tasks for the \nnewt load arduino_boot\n and \nnewt load arduino_blinky\n commands, add the following definitions to the \ntasks.json\n file:\n\n\n {\n \ntaskName\n: \nload_arduino_boot\n,\n \nargs\n: [\nload\n, \narduino_boot\n],\n \nsuppressTaskName\n:true\n }, \n {\n \ntaskName\n: \nload_arduino_blinky\n,\n \nargs\n: [\nload\n, \narduino_blinky\n],\n \nsuppressTaskName\n:true\n }, \n\n\n\n\n\n\nTo run a command from the Visual Studio integrated terminal, instead of starting a task, press \nCtrl-`\n to launch the integrated terminal and enter the command on the prompt:\n\n\n\n\n\n\n\nDefining Debugger Configurations\n\n\nYou need to define a debugger configuration to launch the GDB debugger from within Visual Studio Code: \n\n\nStep 1: Select \nDebug\n \n \nOpen Configuration\n, and select the \nGDB\n environment.\n\n\n\n\n\n\n\n\nYou should see a default \nlaunch.json\n file created in the \n.vscode\n folder.\n\n\n\n\n\n\n\n\nStep 2: Delete the content from the \nlaunch.json\n file, add the following definitions, and press 'Ctrl-S' to save the file.\n\n\n{\n \nversion\n: \n0.2.0\n,\n \nconfigurations\n: [\n {\n \nname\n: \ngdb_arduino_blinky\n,\n \ntype\n: \ngdb\n,\n \nrequest\n: \nattach\n,\n \nexecutable\n: \n${workspaceRoot}\\\\bin\\\\targets\\\\arduino_blinky\\\\app\\\\apps\\\\blinky\\\\blinky.elf\n,\n \ntarget\n: \n:3333\n,\n \ncwd\n: \n${workspaceRoot}\n,\n \ngdbpath\n: \nC:\\\\Program Files (x86)\\\\GNU Tools ARM Embedded\\\\4.9 2015q2\\\\bin\\\\arm-none-eabi-gdb.exe\n,\n \nremote\n: true\n\n }\n ]\n}\n\n\n\n\n\n\nThis defines a \ngdb_arduino_blinky\n debugger configuration. It specifies: \n\n\n\n\nThe debugger is type \ngdb\n.\n\n\nTo use the \nblinky.elf\n file for the executable. \n\n\nTo use port 3333 to connect with the remote target.\n\n\nTo use arm-none-eabi-gdb for the GDB program. \n\n\n\n\n\nDebugging Your Application\n\n\nTo debug your application, start the GDB server and launch the GDB session from Visual Studio Code. For the the arduino blinky example, perform the following:\n\n\nStep 1: Run the debug_arduino_blinky task to start the GDB server. Perform the following:\n\n\n\n\nPress \nCtrl-Shift-P\n and type \ntask\n in the search box. \n\n\nSelect \nTasks:Run Task\n \n \ndebug_arduino_blinky\n.\n\n\nPress \nCtrl-Shift-U\n to open the Output Panel and see the OpenOCD GDB Server output.\n\n \n\n\n\n\n\n\n\n\nStep 2: Start the GDB session. Perform the following: \n\n\n\n\nPress \nCtrl-Shift-Y\n to view the Debug Console. \n\n\nPress the Debugging icon on the activity bar (Ctrl-Shift-D) to bring up the Debug Side Bar.\n\n\nSelect \ngdb_arduino_blinky\n from the DEBUG drop down menu. \n\n\nPress the green play button to start the gdb session.\n\n\n\n\n\n\n\n\nStep 3: Debug your application. You should see a debug session similar to the one shown below:\n\n\n\n\nFor more information on how to use the Visual Studio Code Debugger, see the \nVisual Studio Code debugging documentation\n.\n\n\nWorking with Multiple Mynewt Applications\n\n\nAs mentioned previously, each mynewt project corresponds to a Visual Studio Code workspace. If you have multiple Mynewt application targets defined in same project, you will need to define build and debug tasks for each target in the \ntasks.json\n file and debugger configurations for the targets in the \nlaunch.json\n file for the workspace. If you have a different Mynewt project for each mynewt application, you will need to define build and debug tasks in the \ntasks.json\n file and the debugger configuration in the \nlaunch.json\n file for each workspace.",
"title": "Using an IDE to Develop Mynewt Applications"
},
{
@@ -13527,7 +13527,7 @@
},
{
"location": "/faq/ide/#defining-visual-studio-code-tasks-to-build-and-debug-mynewt-applications",
- "text": "You define Visual Studio Code tasks to build and debug your Mynewt targets in Visual Studio Code. We use the Blinky application for the Arduino Zero board from the Blinky On Arduino Zero Tutorial to illustrate how to define the tasks to build and debug the Arduino blinky bootloader and application targets. Perform the following steps to create the tasks to build and debug the Arduino blinky bootloader and appliction targets: Step 1: Press Ctrl-Shift-P , type task , and select Tasks:Configure Task Runner from the search results. Step 2: Select Others (scroll down to the bottom of the list) to create a task runner for external commands. \nTasks are defined in the tasks.json file. You should see the .vscode folder created in the MYPROJ folder and a tasks.json file created in the .vscode folder. The tasks.json file has the following default values. The sample tasks.json file defines a simple task that runs the echo command with \"Hello World\" as the argument. Step 3: Delete the content from the tasks.json file, add the following definitions, and press Ctrl-S to save the file. {\n version : 0.1.0 ,\n command : newt ,\n echoCommand : true,\n isShellCommand : true,\n\n tasks :[\n {\n taskName : build_arduino_boot ,\n args : [ build , arduino_boot ],\n suppressTaskName : true\n },\n {\n taskName : build_arduino_blinky ,\n args : [ build , arduino_blinky ],\n isBuildCommand : true, \n suppressTaskName : true\n },\n {\n taskName : create_arduino_blinky ,\n args : [ create-image , arduino_blinky , 1.0.0 ],\n suppressTaskName :true\n }, \n {\n taskName : debug_arduino_blinky ,\n args : [ debug , arduino_blinky , -n ],\n suppressTaskName : true\n }\n ]\n} \nThe tasks.json file specifies the tasks that are run to build and debug the Arduino blinky targets. Each task runs a newt command. The newt command to run and the arguments for the newt command are passed in the args property for each task. The following tasks are defined in this example: build_arduino_boot : Runs the newt build arduino_boot command to build the arduino_boot target. build_arduino_blinky : Runs the newt build arduino_blinky command to build the arduino_blinky target. Note: This task sets the isBuildCommand property to true . This is an optional property that, when set to true, allows you to run the Tasks: Run Build Task ( Ctrl-Shift-B ) command to start the task. create_arduino_blinky : Runs the newt create-image arduino_blinky command to create the image file. debug_arduino_blinky : Runs the newt build arduino_blinky -n command to debug the arduino_blinky target. The -n flag is specified to start only the GDB server and not the GDB client. We will launch the GDB client from Visual Studio Code. For more information on tasks and all supported properties, see the Visual Studio Code Task documentation .",
+ "text": "You define Visual Studio Code tasks to build and debug your Mynewt targets in Visual Studio Code. We use the Blinky application for the Arduino Zero board from the Blinky On Arduino Zero Tutorial to illustrate how to define the tasks to build and debug the Arduino blinky bootloader and application targets. Perform the following steps to create the tasks to build and debug the Arduino blinky bootloader and appliction targets: Step 1: Press Ctrl-Shift-P , type task , and select Tasks:Configure Task Runner from the search results. Step 2: Select Others (scroll down to the bottom of the list) to create a task runner for external commands. \nTasks are defined in the tasks.json file. You should see the .vscode folder created in the MYPROJ folder and a tasks.json file created in the .vscode folder. The tasks.json file has the following default values. The sample tasks.json file defines a simple task that runs the echo command with \"Hello World\" as the argument. Step 3: Delete the content from the tasks.json file, add the following definitions, and press Ctrl-S to save the file. {\n version : 0.1.0 ,\n command : newt ,\n echoCommand : true,\n isShellCommand : true,\n\n tasks :[\n {\n taskName : build_arduino_boot ,\n args : [ build , arduino_boot ],\n suppressTaskName : true\n },\n {\n taskName : build_arduino_blinky ,\n args : [ build , arduino_blinky ],\n isBuildCommand : true, \n suppressTaskName : true\n },\n {\n taskName : create_arduino_blinky ,\n args : [ create-image , arduino_blinky , 1.0.0 ],\n suppressTaskName :true\n }, \n {\n taskName : debug_arduino_blinky ,\n args : [ debug , arduino_blinky , -n ],\n suppressTaskName : true\n }\n ]\n} \nThe tasks.json file specifies the tasks that are run to build and debug the Arduino blinky targets. Each task runs a newt command. The newt command to run and the arguments for the newt command are passed in the args property for each task. The following tasks are defined in this example: build_arduino_boot : Runs the newt build arduino_boot command to build the arduino_boot target. build_arduino_blinky : Runs the newt build arduino_blinky command to build the arduino_blinky target. Note: This task sets the isBuildCommand property to true . This is an optional property that, when set to true, allows you to run the Tasks: Run Build Task ( Ctrl-Shift-B ) command to start the task. create_arduino_blinky : Runs the newt create-image arduino_blinky command to create the image file. debug_arduino_blinky : Runs the newt debug arduino_blinky -n command to debug the arduino_blinky target. The -n flag is specified to start only the GDB server and not the GDB client. We will launch the GDB client from Visual Studio Code. For more information on tasks and all supported properties, see the Visual Studio Code Task documentation .",
"title": "Defining Visual Studio Code Tasks to Build and Debug Mynewt Applications"
},
{
diff --git a/sitemap.xml b/sitemap.xml
index 5aeaa1f17..2239773c3 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -4,7 +4,7 @@
<url>
<loc>http://mynewt.apache.org/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -13,13 +13,13 @@
<url>
<loc>http://mynewt.apache.org/pages/ble/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/pages/securitybullets/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -28,7 +28,7 @@
<url>
<loc>http://mynewt.apache.org/quick-start/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -36,7 +36,7 @@
<url>
<loc>http://mynewt.apache.org/about/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -44,7 +44,7 @@
<url>
<loc>http://mynewt.apache.org/talks/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -52,7 +52,7 @@
<url>
<loc>http://mynewt.apache.org/download/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -60,7 +60,7 @@
<url>
<loc>http://mynewt.apache.org/community/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -68,7 +68,7 @@
<url>
<loc>http://mynewt.apache.org/events/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -77,7 +77,7 @@
<url>
<loc>http://mynewt.apache.org/os/introduction/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -89,7 +89,7 @@
<url>
<loc>http://mynewt.apache.org/os/get_started/vocabulary/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -125,7 +125,7 @@
<url>
<loc>http://mynewt.apache.org/known_issues/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -135,37 +135,37 @@
<url>
<loc>http://mynewt.apache.org/newt/install/prev_releases/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/newtmgr/prev_releases/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/go_env/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/ide/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/how_to_edit_docs/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/answers/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
diff --git a/v0_9_0/sitemap.xml b/v0_9_0/sitemap.xml
index facd2ebed..0cb520381 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-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -12,7 +12,7 @@
<url>
<loc>http://mynewt.apache.org/quick-start/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -20,7 +20,7 @@
<url>
<loc>http://mynewt.apache.org/about/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -28,7 +28,7 @@
<url>
<loc>http://mynewt.apache.org/download/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -36,7 +36,7 @@
<url>
<loc>http://mynewt.apache.org/community/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -44,7 +44,7 @@
<url>
<loc>http://mynewt.apache.org/events/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -53,7 +53,7 @@
<url>
<loc>http://mynewt.apache.org/os/introduction/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -65,7 +65,7 @@
<url>
<loc>http://mynewt.apache.org/os/get_started/vocabulary/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -101,7 +101,7 @@
<url>
<loc>http://mynewt.apache.org/known_issues/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -111,13 +111,13 @@
<url>
<loc>http://mynewt.apache.org/faq/how_to_edit_docs/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/answers/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
diff --git a/v1_0_0/sitemap.xml b/v1_0_0/sitemap.xml
index 327a3a9ca..f285bfe89 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-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -13,7 +13,7 @@
<url>
<loc>http://mynewt.apache.org/pages/ble/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -22,7 +22,7 @@
<url>
<loc>http://mynewt.apache.org/quick-start/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -30,7 +30,7 @@
<url>
<loc>http://mynewt.apache.org/about/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -38,7 +38,7 @@
<url>
<loc>http://mynewt.apache.org/talks/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -46,7 +46,7 @@
<url>
<loc>http://mynewt.apache.org/download/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -54,7 +54,7 @@
<url>
<loc>http://mynewt.apache.org/community/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -62,7 +62,7 @@
<url>
<loc>http://mynewt.apache.org/events/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -71,7 +71,7 @@
<url>
<loc>http://mynewt.apache.org/os/introduction/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -83,7 +83,7 @@
<url>
<loc>http://mynewt.apache.org/os/get_started/vocabulary/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -119,7 +119,7 @@
<url>
<loc>http://mynewt.apache.org/known_issues/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -129,25 +129,25 @@
<url>
<loc>http://mynewt.apache.org/faq/go_env/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/ide/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/how_to_edit_docs/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/answers/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
diff --git a/v1_1_0/sitemap.xml b/v1_1_0/sitemap.xml
index a8f1ebe98..9f18263cc 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-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -13,13 +13,13 @@
<url>
<loc>http://mynewt.apache.org/pages/ble/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/pages/securitybullets/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -28,7 +28,7 @@
<url>
<loc>http://mynewt.apache.org/quick-start/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -36,7 +36,7 @@
<url>
<loc>http://mynewt.apache.org/about/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -44,7 +44,7 @@
<url>
<loc>http://mynewt.apache.org/talks/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -52,7 +52,7 @@
<url>
<loc>http://mynewt.apache.org/download/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -60,7 +60,7 @@
<url>
<loc>http://mynewt.apache.org/community/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -68,7 +68,7 @@
<url>
<loc>http://mynewt.apache.org/events/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -77,7 +77,7 @@
<url>
<loc>http://mynewt.apache.org/os/introduction/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -89,7 +89,7 @@
<url>
<loc>http://mynewt.apache.org/os/get_started/vocabulary/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -125,7 +125,7 @@
<url>
<loc>http://mynewt.apache.org/known_issues/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -135,25 +135,25 @@
<url>
<loc>http://mynewt.apache.org/faq/go_env/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/ide/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/how_to_edit_docs/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/answers/</loc>
- <lastmod>2017-12-01</lastmod>
+ <lastmod>2017-12-12</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