Change 5.6 to 5.7

Change tools documents from 5.6 to 5.7.

Author: AnotherButler

docs/tools/DAP.md

@@ -2,7 +2,7 @@
 
 DAPlink is an open source project that implements the embedded firmware required for a Cortex debug probe. The project is hosted on GitHub and is published under an Apache 2.0 license, making it attractive for commercial developments.
 
-The software project is complemented by a series of reference designs for creating the DAPLink debug probe hardware, which is available in the <a href="/docs/v5.6/reference/contributing-tools.html#arm-mbed-hdk" target="_blank">HDK documentation</a>.
+The software project is complemented by a series of reference designs for creating the DAPLink debug probe hardware, which is available in the <a href="/docs/v5.7/reference/contributing-tools.html#arm-mbed-hdk" target="_blank">HDK documentation</a>.
 
 ### DAPLink features
 
@@ -29,7 +29,7 @@ DAPLink debug probes appear on the host computer as a USB disk. Program files in
 The DAPLink debug probe also provides a USB serial port, which can be bridged through to a TTL UART on the target system.
 The USB serial port will appear on a Windows machine as a COM port, or on a Linux machine as a /dev/tty interface.
 
-For more information on configuring your host computer to use this feature, please the <a href="/docs/v5.6/tutorials/windows-serial-driver.html" target="_blank">Windows serial driver information</a>.
+For more information on configuring your host computer to use this feature, please the <a href="/docs/v5.7/tutorials/windows-serial-driver.html" target="_blank">Windows serial driver information</a>.
 
 ### Further reading
 

docs/tools/config_system.md

@@ -9,7 +9,7 @@ The Arm Mbed configuration system customizes the compile time configuration of v
 
 The configuration system gathers and interprets all the configurations defined in the source tree. The output of the configuration system is a list of macros that are automatically defined when compiling the code.
 
-<span class="notes">**Note:** In prior releases, the configuration system provided a method for adding custom targets. The Mbed OS tools now look for custom targets in a file named `custom_targets.json` in the root of a project and treat custom targets the same as <a href="/docs/v5.6/tools/adding-and-configuring-targets.html" target="_blank">Mbed targets</a>.</span>
+<span class="notes">**Note:** In prior releases, the configuration system provided a method for adding custom targets. The Mbed OS tools now look for custom targets in a file named `custom_targets.json` in the root of a project and treat custom targets the same as <a href="/docs/v5.7/tools/adding-and-configuring-targets.html" target="_blank">Mbed targets</a>.</span>
 
 #### Defining configuration parameters
 
@@ -91,7 +91,7 @@ In this JSON file:
 - `macros` is a list of extra macros that will be defined when compiling a project that includes this library. A macro can be defined without a value (such as `MYMOD_MACRO1` above) or with a value (such as `MYMOD_MACRO2` above).
 - `target_overrides` is a dictionary with target-specific values for the configuration parameters.
 
-`target_overrides` is used to override the values of the parameters depending on the current compilation target. The keys in `target_overrides` are matched against toolchain *labels*. (You can find a description of Mbed targets in our documentation about <a href="/docs/v5.6/tools/adding-and-configuring-targets.html" target="_blank">adding and configuring targets</a>.) If a key inside `target_overrides` matches one of the target labels, the parameter values are changed according to the value of the key. In the example above:
+`target_overrides` is used to override the values of the parameters depending on the current compilation target. The keys in `target_overrides` are matched against toolchain *labels*. (You can find a description of Mbed targets in our documentation about <a href="/docs/v5.7/tools/adding-and-configuring-targets.html" target="_blank">adding and configuring targets</a>.) If a key inside `target_overrides` matches one of the target labels, the parameter values are changed according to the value of the key. In the example above:
 
 - `config` is always processed first, independent of the target. `config` might define values for some of the parameters. In this case, `buffer_size` will be set to 1024, `queue_size` will be set to 10 and `timer_period` will not have a value.
 - If the library is compiled for the `K64F` target, `timer_period` will be set to 100, and `queue_size` will be set to 40 because they are overridden by the `K64F` key in `target_overrides`. `buffer_size` will be set to 1024, as defined in `config`.
@@ -107,7 +107,7 @@ If the source tree has code for more than one library, each library needs its ow
 
 ##### Configuration data in targets
 
-Like libraries, targets can define their own configuration data. Additionally, targets can override the configuration of the target(s) they inherit from (for more details about how do define a target and target inheritance, check <a href="/docs/v5.6/tools/adding-and-configuring-targets.html" target="_blank">our configuring targets documentation</a>). Target configuration data is defined in `targets.json` using `config`, as described in the section about [defining configuration parameters](#defining-configuration-parameters). An example for a hypothetical `Base` target is given below:
+Like libraries, targets can define their own configuration data. Additionally, targets can override the configuration of the target(s) they inherit from (for more details about how do define a target and target inheritance, check <a href="/docs/v5.7/tools/adding-and-configuring-targets.html" target="_blank">our configuring targets documentation</a>). Target configuration data is defined in `targets.json` using `config`, as described in the section about [defining configuration parameters](#defining-configuration-parameters). An example for a hypothetical `Base` target is given below:
 
 ```
 "Base": {

docs/tools/debug/debug_intro.md

@@ -1,6 +1,6 @@
 ## Debugging
 
-There are extensive instructions on debugging Arm Mbed OS 5 applications with <a href="/docs/v5.6/tutorials/keil-uvision.html" target="_blank">uVision 5</a>, <a href="/docs/v5.6/tutorials/eclipse.html" target="_blank">Eclipse</a> and <a href="/docs/v5.6/tutorials/visual-studio-code.html" target="_blank">Visual Studio Code</a>, but you can use any IDE that supports GDB to debug Mbed OS 5 applications. This document gives advice on how to configure these IDEs. Before starting, first <a href="/docs/v5.6/tools/setting-up-a-local-debug-toolchain.html" target="_blank">configure your local debug toolchain</a>.
+There are extensive instructions on debugging Arm Mbed OS 5 applications with <a href="/docs/v5.7/tutorials/keil-uvision.html" target="_blank">uVision 5</a>, <a href="/docs/v5.7/tutorials/eclipse.html" target="_blank">Eclipse</a> and <a href="/docs/v5.7/tutorials/visual-studio-code.html" target="_blank">Visual Studio Code</a>, but you can use any IDE that supports GDB to debug Mbed OS 5 applications. This document gives advice on how to configure these IDEs. Before starting, first <a href="/docs/v5.7/tools/setting-up-a-local-debug-toolchain.html" target="_blank">configure your local debug toolchain</a>.
 
 ### Exporting your project
 
@@ -39,10 +39,10 @@ The resulting binary will end up at `BUILD\projectname.elf`.
 
 ### Debugging your project
 
-To debug your project, you first need to start a <a href="/docs/v5.6/tools/setting-up-a-local-debug-toolchain.html#running-a-debug-server" target="_blank">debug server</a>. This is often exposed as a setting in your IDE under 'Remote debugging' or 'Debug server'.
+To debug your project, you first need to start a <a href="/docs/v5.7/tools/setting-up-a-local-debug-toolchain.html#running-a-debug-server" target="_blank">debug server</a>. This is often exposed as a setting in your IDE under 'Remote debugging' or 'Debug server'.
 
 - When using pyOCD, set the full path to the `pyocd-gdbserver` binary, and do not set arguments.
-- When using OpenOCD, set the full path to the `openocd` binary, and set the arguments for your development board. (See <a href="/docs/v5.6/tools/setting-up-a-local-debug-toolchain.html#openocd" target="_blank">the instructions</a>.)
+- When using OpenOCD, set the full path to the `openocd` binary, and set the arguments for your development board. (See <a href="/docs/v5.7/tools/setting-up-a-local-debug-toolchain.html#openocd" target="_blank">the instructions</a>.)
 
 Next, you need to configure GDB.
 

docs/tools/debug/debugging_mbed_os_apps.md

@@ -1,21 +1,21 @@
 ## Debugging Arm Mbed OS applications
 
-At the heart of Arm Mbed is the <a href="/docs/v5.6/tools/arm-mbed-online-compiler.html" target="_blank">Online Compiler</a>. While that is incredibly convenient for getting a project started or while prototyping, chances are that at some point you'll miss a debugger, or you'll want to develop while not having an active internet connection. Through debugging, you can do things such as set breakpoints, set watchpoints, view registers, view disassembly, browse memory and examine the callstack. These docs will help you debug your applications.
+At the heart of Arm Mbed is the <a href="/docs/v5.7/tools/arm-mbed-online-compiler.html" target="_blank">Online Compiler</a>. While that is incredibly convenient for getting a project started or while prototyping, chances are that at some point you'll miss a debugger, or you'll want to develop while not having an active internet connection. Through debugging, you can do things such as set breakpoints, set watchpoints, view registers, view disassembly, browse memory and examine the callstack. These docs will help you debug your applications.
 
 The simplest way to debug your code is to augment your code with log statements, which you can observe from your computer.
 
 ### Debugging from an IDE
 
-Keil uVision natively supports debugging Mbed OS applications. To set up uVision, read <a href="/docs/v5.6/tutorials/keil-uvision.html" target="_blank">Debugging with Keil uVision</a>.
+Keil uVision natively supports debugging Mbed OS applications. To set up uVision, read <a href="/docs/v5.7/tutorials/keil-uvision.html" target="_blank">Debugging with Keil uVision</a>.
 
-Mbed also supports debugging using any IDE that supports GDB. To set up the debugger, first read <a href="/docs/v5.6/tools/setting-up-a-local-debug-toolchain.html" target="_blank">Setting up your local debug toolchain</a>. Then read the section for your specific IDE. The same principles apply to any unlisted IDEs that supports GDB:
+Mbed also supports debugging using any IDE that supports GDB. To set up the debugger, first read <a href="/docs/v5.7/tools/setting-up-a-local-debug-toolchain.html" target="_blank">Setting up your local debug toolchain</a>. Then read the section for your specific IDE. The same principles apply to any unlisted IDEs that supports GDB:
 
-1. Producing <a href="/docs/v5.6/tools/debug-builds-with-arm-mbed-cli.html" target="_blank">debug builds with Arm Mbed CLI</a>.
-1. Debugging with <a href="/docs/v5.6/tutorials/eclipse.html" target="_blank">Eclipse</a>.
-1. Debugging with <a href="/docs/v5.6/tutorials/visual-studio-code.html" target="_blank">Visual Studio Code</a>.
-1. Debugging with <a href="/docs/v5.6/tools/debugging.html" target="_blank">other IDEs that support GDB</a>.
+1. Producing <a href="/docs/v5.7/tools/debug-builds-with-arm-mbed-cli.html" target="_blank">debug builds with Arm Mbed CLI</a>.
+1. Debugging with <a href="/docs/v5.7/tutorials/eclipse.html" target="_blank">Eclipse</a>.
+1. Debugging with <a href="/docs/v5.7/tutorials/visual-studio-code.html" target="_blank">Visual Studio Code</a>.
+1. Debugging with <a href="/docs/v5.7/tools/debugging.html" target="_blank">other IDEs that support GDB</a>.
 
 ### Links to other sources
 
 - <a href="https://os.mbed.com/blog/entry/Post-mortem-debugging-with-ARM-mbed/" target="_blank">Using CMSIS-DAP to debug a device after it crashes</a>.
-- <a href="/docs/v5.6/tutorials/debug-microbit.html" target="_blank">Debugging the micro:bit with pyOCD and GDB</a>.
+- <a href="/docs/v5.7/tutorials/debug-microbit.html" target="_blank">Debugging the micro:bit with pyOCD and GDB</a>.

docs/tools/debug/local_debugging_toolchain.md

@@ -102,10 +102,10 @@ Remote debugging using localhost:3333
 
 You now have set up a debug connection. From here, you can flash debug builds, step through code and use any IDE that supports GDB to debug Arm Mbed OS applications. For instructions, see:
 
-1. Producing <a href="/docs/v5.6/tools/debug-builds-with-arm-mbed-cli.html" target="_blank">debug builds with Arm Mbed CLI</a>.
-1. Debugging with <a href="/docs/v5.6/tutorials/eclipse.html" target="_blank">Eclipse</a>.
-1. Debugging with <a href="/docs/v5.6/tutorials/keil-uvision.html" target="_blank">Keil uVision</a>.
-1. Debugging with <a href="/docs/v5.6/tutorials/visual-studio-code.html" target="_blank">Visual Studio Code</a>.
+1. Producing <a href="/docs/v5.7/tools/debug-builds-with-arm-mbed-cli.html" target="_blank">debug builds with Arm Mbed CLI</a>.
+1. Debugging with <a href="/docs/v5.7/tutorials/eclipse.html" target="_blank">Eclipse</a>.
+1. Debugging with <a href="/docs/v5.7/tutorials/keil-uvision.html" target="_blank">Keil uVision</a>.
+1. Debugging with <a href="/docs/v5.7/tutorials/visual-studio-code.html" target="_blank">Visual Studio Code</a>.
 
 ### Semihosting messages
 

docs/tools/mbed_targets.md

@@ -2,7 +2,7 @@
 
 Arm Mbed uses JSON as a description language for its build targets. You can find the JSON description of Mbed targets in `targets/targets.json` and in `custom_targets.json` in the root of a project directory. When you add new targets with `custom_targets.json`, they are added to the list of available targets. 
 
-<span class="notes">**Note:** The Online Compiler does not support this functionality. You need to use <a href="https://os.mbed.com/docs/v5.6/tools/mbed-cli.html" target="_blank">Mbed CLI</a> to take your code offline.</span>
+<span class="notes">**Note:** The Online Compiler does not support this functionality. You need to use <a href="https://os.mbed.com/docs/v5.7/tools/mbed-cli.html" target="_blank">Mbed CLI</a> to take your code offline.</span>
 
 You are not allowed to redefine existing targets in `custom_targets.json`. To better understand how a target is defined, we'll use this example (taken from `targets.json`):
 
@@ -199,7 +199,7 @@ Use this property to pass necessary data for exporting to various third party to
 
 We use the tool <a href="https://github.com/ARMmbed/mbed-os/tree/master/tools/arm_pack_manager" target="_blank">ArmPackManager</a> to parse CMSIS Packs for target information. <a href="https://github.com/ARMmbed/mbed-os/blob/master/tools/arm_pack_manager/index.json" target="_blank">`index.json`</a> stores the parsed information from the <a href="http://www.keil.com/pack/doc/CMSIS/Pack/html/" target="_blank">PDSC (Pack Description</a> retrieved from each CMSIS Pack.
 
-The <a href="/docs/v5.6/reference/contributing-target.html">`"device_name"`</a> attribute it `targets.json` maps from a target in Mbed OS to a device in a CMSIS Pack. To support IAR and uVision exports for your target, you must add a `"device_name"` field in `targets.json` containing this key.
+The <a href="/docs/v5.7/reference/contributing-target.html">`"device_name"`</a> attribute it `targets.json` maps from a target in Mbed OS to a device in a CMSIS Pack. To support IAR and uVision exports for your target, you must add a `"device_name"` field in `targets.json` containing this key.
 
 <a href="http://www.keil.com/pack/Keil.Kinetis_K20_DFP.pdsc" target="_blank">http://www.keil.com/pack/Keil.Kinetis_K20_DFP.pdsc</a> is the PDSC that contains TEENSY_31 device (MK20DX256xxx7). ArmPackManager has parsed this PDSC, and `index.json` stores the device information. The device information begins on line 156 of the `.pdsc` file:
 

docs/tools/offline/build_profiles.md

@@ -9,7 +9,7 @@ Arm Mbed OS 5 supports three primary build profiles: *develop*, *debug* and *rel
 - Hard to follow code flow when using a debugger.
 - Chip goes to sleep when idle:
     * Debugger is likely to drop connection.
-    * Breaks the local file system on the <a href="/docs/v5.6/introduction/how-mbed-works.html#architecture-diagram" target="_blank">Arm Mbed interface</a> on some boards.
+    * Breaks the local file system on the <a href="/docs/v5.7/introduction/how-mbed-works.html#architecture-diagram" target="_blank">Arm Mbed interface</a> on some boards.
 
 ### Debug profile
 
@@ -24,4 +24,4 @@ Arm Mbed OS 5 supports three primary build profiles: *develop*, *debug* and *rel
 - Minimal error information.
 - Chip goes to sleep when going idle:
     - Debugger is likely to drop connection.
-    - Breaks the local file system on the <a href="/docs/v5.6/introduction/how-mbed-works.html#architecture-diagram" target="_blank">Mbed interface</a> on some boards.
+    - Breaks the local file system on the <a href="/docs/v5.7/introduction/how-mbed-works.html#architecture-diagram" target="_blank">Mbed interface</a> on some boards.

docs/tools/offline/cli-create.md

@@ -138,7 +138,7 @@ The arguments for *compile* are:
 
 You can find the compiled binary, ELF image, memory usage and link statistics in the `BUILD` subdirectory of your program.
 
-For more information on build profiles, see <a href="/docs/v5.6/tools/build-profiles.html" target="_blank">our build profiles</a> and <a href="/docs/v5.6/tools/toolchain-profiles.html" target="_blank">toolchain profiles</a> pages.
+For more information on build profiles, see <a href="/docs/v5.7/tools/build-profiles.html" target="_blank">our build profiles</a> and <a href="/docs/v5.7/tools/toolchain-profiles.html" target="_blank">toolchain profiles</a> pages.
 
 #### Compiling static libraries
 
@@ -170,7 +170,7 @@ Image: ../threaded_blinky-out/threaded_blinky.bin
 
 ### The compile configuration system
 
-The <a href="/docs/v5.6/tools/the-configuration-system.html" target="_blank">compile configuration system</a> provides a flexible mechanism for configuring the Mbed program, its libraries and the build target.
+The <a href="/docs/v5.7/tools/the-configuration-system.html" target="_blank">compile configuration system</a> provides a flexible mechanism for configuring the Mbed program, its libraries and the build target.
 
 #### Inspecting the configuration
 

docs/tools/offline/cli-setup.md

@@ -71,7 +71,7 @@ The Windows installer for Mbed CLI for includes the following components:
     - <a href="https://git-scm.com/" target="_blank">Git</a> - version 2.12.2.
     - <a href="https://www.mercurial-scm.org/" target="_blank">Mercurial</a> - version 4.1.1.
 - **GNU Arm Embedded Toolchain** - <a href="https://developer.arm.com/open-source/gnu-toolchain/gnu-rm/downloads" target="_blank">GNU Embedded Toolchain for Arm</a>.
-- **Mbed Windows serial port driver** - <a href="/docs/v5.6/tutorials/windows-serial-driver.html" target="_blank">serial port driver</a>.
+- **Mbed Windows serial port driver** - <a href="/docs/v5.7/tutorials/windows-serial-driver.html" target="_blank">serial port driver</a>.
 
 ##### Install Windows installer for Mbed CLI
 

docs/tools/offline/debug_builds_cli.md

@@ -1,6 +1,6 @@
 <h2 id="debug-builds-cli">Debug builds</h2>
 
-After you've set up your <a href="/docs/v5.6/tools/toolchain-profiles.html" target="_blank">local debug toolchain</a>, you need firmware that includes program symbols (an `.elf` file). Because the Arm Mbed Online Compiler only produces binaries that omit the program symbols, you need to compile locally using <a href="/docs/v5.6/tools/mbed-cli.html" target="_blank">Arm Mbed CLI</a>.
+After you've set up your <a href="/docs/v5.7/tools/toolchain-profiles.html" target="_blank">local debug toolchain</a>, you need firmware that includes program symbols (an `.elf` file). Because the Arm Mbed Online Compiler only produces binaries that omit the program symbols, you need to compile locally using <a href="/docs/v5.7/tools/mbed-cli.html" target="_blank">Arm Mbed CLI</a>.
 
 <span class="notes">**Note:** Make sure to do a clean build when switching to and from debug and release by removing the `BUILD` folder.</span>
 
@@ -26,7 +26,7 @@ $ mbed compile --profile .temp/tools/profiles/debug.json
 
 ### Exporting with debug symbols
 
-You can also enable debug symbols when <a href="/docs/v5.6/tools/exporting.html" target="_blank">exporting your project</a> by using:
+You can also enable debug symbols when <a href="/docs/v5.7/tools/exporting.html" target="_blank">exporting your project</a> by using:
 
 ```
 $ mbed export -i uvision -m K64F --profile mbed-os/tools/profiles/debug.json