diff --git a/docs.json b/docs.json index c786b30ebc..032d405f91 100644 --- a/docs.json +++ b/docs.json @@ -94,7 +94,7 @@ "sources": [] }, { - "title": "Build and debug with Mbed CLI", + "title": "Build with Mbed CLI", "sub_chapters": [{ "title": "Installing Mbed CLI", "intro": { @@ -108,31 +108,17 @@ "path": "docs/quick-start/cli_code.md" }, "sources": [] - }, - { - "title": "Debugging with Mbed CLI", - "intro": { - "path": "docs/quick-start/quick-start-cli-debug.md" - }, - "sources": [] } ] }, { - "title": "Build and debug with the Online Compiler", + "title": "Build with the Online Compiler", "sub_chapters": [{ "title": "Importing and compiling the code", "intro": { "path": "docs/quick-start/quick-start-compiler.md" }, "sources": [] - }, - { - "title": "Debugging with the Online Compiler", - "intro": { - "path": "docs/quick-start/quick-start-online-debug.md" - }, - "sources": [] } ] }, @@ -1115,9 +1101,6 @@ "type": "markdown", "chapters": [{ "title": "Debugging", - "intro": { - "path": "docs/tools/debug/debug_intro.md" - }, "sub_chapters": [{ "title": "Methods", "sources": [{ @@ -1151,6 +1134,9 @@ }, { "title": "Third party tools", + "intro": { + "path": "docs/tools/debug/debug_intro.md" + }, "sources": [{ "path": "docs/tools/debug/eclipse_pyocd.md" }, diff --git a/docs/introduction/introduction.md b/docs/introduction/introduction.md index c85b71d393..4a5a3a99a2 100644 --- a/docs/introduction/introduction.md +++ b/docs/introduction/introduction.md @@ -18,7 +18,7 @@ We release Mbed OS under an Apache 2.0 license, so you can confidently use it in Our [quick start](../quick-start/index.html) guides show how to build an example application for both the full profile and bare metal profile, on Mbed CLI, Mbed Studio and the Mbed Online Compiler. -| [Build with Mbed Studio](https://os.mbed.com/docs/mbed-studio/current/getting-started/index.html) | [Build with Mbed Online Compiler](../quick-start/build-and-debug-with-the-online-compiler.html) | [Build with Mbed CLI](../quick-start/build-and-debug-with-mbed-cli.html) | +| [Build with Mbed Studio](https://os.mbed.com/docs/mbed-studio/current/getting-started/index.html) | [Build with Mbed Online Compiler](../quick-start/build-with-the-online-compiler.html) | [Build with Mbed CLI](../quick-start/build-with-mbed-cli.html) | | --- | --- | --- | | Download our dedicated desktop IDE, including all the necessary tools to work with Mbed OS.
This link will take you to the Mbed Studio documentation site. | Zero-installation web IDE to explore Mbed OS; great for rapid prototyping and education. | Command-line tool requiring manual setup of tools, but providing the greatest degree of flexibility. | diff --git a/docs/program-setup/serial/serial_communication.md b/docs/program-setup/serial/serial_communication.md index 23f1f82434..8c6729bde2 100644 --- a/docs/program-setup/serial/serial_communication.md +++ b/docs/program-setup/serial/serial_communication.md @@ -6,86 +6,85 @@ The Arm Mbed microcontroller on your board can communicate with a host PC over t This allows you to: -- Print out messages to a [host PC terminal (useful for debugging)](#terminal-applications). -- Read input from the host PC keyboard. -- Communicate with applications and programming languages running on the host PC that can communicate with a serial port. Examples are Perl, Python and Java. +- Print out messages to a PC terminal (useful for debugging). +- Read input from a PC keyboard. +- Communicate with applications running on a PC to exchange data. -## Hello, world +## Hello World - printing messages -This program prints a "Hello World" message that you can view on a [terminal application](#using-terminal-applications). Communication over the USB serial port uses the standard serial interface. Specify the internal (USBTX, USBRX) pins to connect to the serial port routed over USB: +This program prints a "Hello World!" message that you can view on a serial terminal. Mbed OS redirects any `printf()` statements to the board's debug USB serial. -[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-snippet-Serial_HelloWorld/tree/v6.0)](https://github.com/ARMmbed/mbed-os-snippet-Serial_HelloWorld/blob/v6.0/main.cpp) +[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-snippet-Serial_STDOUT/tree/v6.0)](https://github.com/ARMmbed/mbed-os-snippet-Serial_STDOUT/blob/v6.0/main.cpp) + +## Viewing output in a serial terminal -## Using terminal applications +Serial terminals run on your host PC. They provide an interface where your Mbed board can print and where you can type characters back to your board. -Terminal applications run on your host PC. They provide a window where your Mbed board can print and where you can type characters back to your board. +Mbed CLI provides a serial terminal that is configured with a default baud rate of `9600`. You can either set it to [open after compilation](#opening-a-serial-terminal-after-compilation), or open it [manually](#manually-opening-a-serial-terminal). -**Serial configuration:** The standard setup for the USB serial port is 9600 baud, 8 bits, 1 stop bit, no parity (9600-8-N-1) +### Opening a serial terminal after compilation -### Installing an application for Windows +You can use one command to compile an application, flash it onto a board and open a serial terminal: -There are many terminal applications for Windows, including: +``` +mbed compile -t -m --flash --sterm +``` -- [CoolTerm](http://freeware.the-meiers.org/) - this is the application we use in this example. We use it often because it usually "just works". -- [Tera Term](http://sourceforge.jp/projects/ttssh2/files). -- [PuTTY](http://www.chiark.greenend.org.uk/~sgtatham/putty/). -- Some Windows PCs come with **Hyperterminal** installed. +When the board is flashed, it starts printing to the terminal (`Hello World!`, in this example). -### Configuring the connection +To close the serial terminal, enter Ctrl + C. -1. Plug in your Mbed board. -1. Open CoolTerm. -1. Click **Connect**. This opens up an 8-n-1 9600 baud connection to the first available serial port. If you have more than one board plugged in, you may need to change the port under **Options > Serial Port > Port**. +
Note: +
- If your application uses a baud rate other than 9600, specify it with `-b BAUDRATE` in the command above. +
- This method only works for a single board. To work with multiple boards, open a serial terminal manually as described below.
-Check your connection parameters: +### Manually opening a serial terminal -1. Select **Options > Serial Port**. -1. You should see 9600 baud, 8 bits, 1 stop bit, no parity (9600-8-N-1). -1. If you do not see your board, click **Re-Scan Peripherals**. +You can open a serial terminal manually, which is useful when the board is already flashed with the desired application (i.e. one built with the [online compiler](../quick-start/build-with-the-online-compiler.html)). -Your terminal program is now configured and connected. +When a single board is connected, run: -## Using terminal applications on Linux +``` +mbed sterm +``` -CoolTerm should work under Linux. If for some reason it doesn't, you can try one of the following: +`mbed sterm` starts message printing. -- [Minicom](https://help.ubuntu.com/community/Minicom). -- [GNU Screen](https://www.gnu.org/software/screen/manual/screen.html). +To close the serial terminal, enter Ctrl + C. -## Minimal Printf +
Note: +
If your application uses a baud rate other than 9600, specify it with `-b BAUDRATE` when opening the serial terminal. +
If you have multiple boards connected: +
1. Run `mbedls` to find the port of the board you want to use. +
2. Run `mbed sterm -p PORT`. +
To list all options, run `mbed sterm -h`
-For low memory devices you may optionally use the [ArmMbed minimal printf library](https://github.com/ARMmbed/minimal-printf). +## Additional examples - reading user inputs -# Additional examples +In addition to printing messages, Mbed OS applications can also read keyboard inputs from the user using the [BufferedSerial](../apis/bufferedserial.html) and [UnbufferedSerial](../apis/unbufferedserial.html) classes. Use your terminal application to interact with the following examples. If you're not sure how to build these examples and run them on your board, please see our [build tools section](../build-tools/index.html). -## Echo back characters you type +### Echo back characters you type [![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-snippet-Serial_EchoBack/tree/v6.0)](https://github.com/ARMmbed/mbed-os-snippet-Serial_EchoBack/blob/v6.0/main.cpp) -## Use the U and D keys to make LED1 brighter or dimmer +### Use the U and D keys to make LED1 brighter or dimmer -**Note:** This example only works if LED1 is on the Pwm pin of the board you are using, such as the NUCLEO-F401RE. +**Note:** This example only works if LED1 is on the Pwm pin of the board you are using, such as the NUCLEO-F401RE. ![](../../images/NUCLEOF401RE.png)The pin map of the NUCLEO-F401RE shows LED1 on the Pwm pin. [![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-snippet-Serial_LEDControl/tree/v6.0)](https://github.com/ARMmbed/mbed-os-snippet-Serial_LEDControl/blob/v6.0/main.cpp) -## Pass characters in both directions +### Pass characters in both directions Tie pins together to see characters echoed back. [![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-snippet-Serial_PassCharacters/tree/v6.0)](https://github.com/ARMmbed/mbed-os-snippet-Serial_PassCharacters/blob/v6.0/main.cpp) -## Using stdin, stdout and stderr - -By default, the C `stdin`, `stdout` and `stderr file` handles map to the PC serial connection: - -[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-snippet-Serial_STDOUT/tree/v6.0)](https://github.com/ARMmbed/mbed-os-snippet-Serial_STDOUT/blob/v6.0/main.cpp) - -## Read to a buffer +### Read to a buffer [![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-snippet-Serial_ReadToBuffer/tree/v6.0)](https://github.com/ARMmbed/mbed-os-snippet-Serial_ReadToBuffer/blob/v6.0/main.cpp) diff --git a/docs/quick-start/further_reading.md b/docs/quick-start/further_reading.md index dcfdd0406b..1c3bd41e2b 100644 --- a/docs/quick-start/further_reading.md +++ b/docs/quick-start/further_reading.md @@ -13,7 +13,7 @@ - [Mbed OS serial communication](../program-setup/serial-communication.html). - Tutorials: - - [Other debugging methods](../debug-test/methods.html). + - [Debugging](../debug-test/methods.html). - [Serial communications](../program-setup/serial-communication.html). - [Optimizing binary size](../apis/platform-tutorials.html). diff --git a/docs/quick-start/quick-start-cli-debug.md b/docs/quick-start/quick-start-cli-debug.md deleted file mode 100644 index 4cf92136ce..0000000000 --- a/docs/quick-start/quick-start-cli-debug.md +++ /dev/null @@ -1,22 +0,0 @@ -

Debugging the quick start

- - -## Using printf - -The easiest way to do basic debugging is to use the `printf` command in your code, then read the output using a serial terminal, such as [PuTTY](http://www.putty.org/) or [CoolTerm](http://freeware.the-meiers.org/). - -For example, add `printf("Hello World!\n\r");` to the top of your main function, and then recompile the program and flash it to your device. - -**Note:** Unless otherwise specified, `printf` defaults to a baud rate of `9600` on Mbed OS. You can modify this value in the `mbed_app.json` file. To configure your terminal client to this baud rate, change the speed option when selecting the port. You can view the [configuration options page](../program-setup/advanced-configuration.html) to learn more about how to configure OS-level options. - -## Exporting to a desktop IDE - -To debug using a desktop IDE such as Keil uVision or Eclipse, use the `mbed export` command to generate project files. - -For example, for a K64F and Keil uVision: - -```console -$ mbed export --ide uvision --target K64F -``` - -**Note:** For a full list of supported exporters, run the `mbed export --supported` command. diff --git a/docs/quick-start/quick-start-compiler.md b/docs/quick-start/quick-start-compiler.md index 088d4b6a02..ba8013adcb 100644 --- a/docs/quick-start/quick-start-compiler.md +++ b/docs/quick-start/quick-start-compiler.md @@ -60,10 +60,3 @@ Alternatively, you may select the import button on the top left hand side of the 1. Open the folder where the executable file was downloaded, and then click and drag (or copy and paste) the file to your Mbed board's USB device folder. 1. Press the board's reset button. - -## Related links - -- [Collaborating with multiple authors](../build-tools/collaborative-work.html). -- [Mbed OS statistics API](../apis/mbed-statistics.html). -- [Mbed OS configuration](../program-setup/advanced-configuration.html). -- [Mbed OS serial communication](../program-setup/serial-communication.html). diff --git a/docs/quick-start/quick-start-online-debug.md b/docs/quick-start/quick-start-online-debug.md deleted file mode 100644 index 8ec581a529..0000000000 --- a/docs/quick-start/quick-start-online-debug.md +++ /dev/null @@ -1,33 +0,0 @@ -

Debugging the quick start

- -## Using printf - -The easiest way to do basic debugging is to use the `printf` command in your code, then read the output using a serial terminal, such as [PuTTY](http://www.putty.org/) or [CoolTerm](http://freeware.the-meiers.org/). - -For example, add `printf("Hello World!\n\r");` to the top of your main function, and then recompile the program and flash it to your device. - -**Note:** Unless otherwise specified, `printf` defaults to a baud rate of `9600` on Mbed OS. You can modify this value in the `mbed_app.json` file. To configure your terminal client to this baud rate, change the speed option when selecting the port. You can view the [configuration options page](../program-setup/advanced-configuration.html) to learn more about how to configure OS-level options. - -To determine which communication port your board connects to: - -1. **On Windows**: - - 1. Open the Device Manager by pressing Windows key + R. - 1. Enter `devmgmt.msc`. - 1. Click **OK**. - 1. Under **Ports (COM & LPT)**: your Mbed board is listed as a `USB Serial Device` next to its COM port. - -1. **On Linux**: Run `dmesg | grep tty` from your command-line. - -1. **On macOS**: Run `ls /dev/tty.*` from your command-line. - -## Exporting to a desktop IDE - -To debug using a desktop IDE such as Keil uVision or Eclipse: - -1. Under **Program Details**, click the **Export** button. -1. Select your export platform and IDE. -1. Click **Export**. -1. Your browser downloads a `.zip` file with the project files. - -![](../images/export_online_compiler.png) diff --git a/docs/quick-start/quick-start.md b/docs/quick-start/quick-start.md index 0ff951a0af..1b522dd88f 100644 --- a/docs/quick-start/quick-start.md +++ b/docs/quick-start/quick-start.md @@ -8,7 +8,7 @@ The quick start offers two versions of Blinky: the full profile version and the ## Please choose how to proceed -| [Build with Mbed Studio](https://os.mbed.com/docs/mbed-studio/current/getting-started/index.html) | [Build with Mbed Online Compiler](../quick-start/build-and-debug-with-the-online-compiler.html) | [Build with Mbed CLI](../quick-start/build-and-debug-with-mbed-cli.html) | +| [Build with Mbed Studio](https://os.mbed.com/docs/mbed-studio/current/getting-started/index.html) | [Build with Mbed Online Compiler](../quick-start/build-with-the-online-compiler.html) | [Build with Mbed CLI](../quick-start/build-with-mbed-cli.html) | | --- | --- | --- | |Download our dedicated desktop IDE, including all the necessary tools to work with Mbed OS.
This link will take you to the Mbed Studio documentation site. | Zero-installation web IDE to explore Mbed OS; great for rapid prototyping and education. | Command-line tool requiring manual setup of tools, but providing the greatest degree of flexibility. | diff --git a/docs/tools/debug/debug_intro.md b/docs/tools/debug/debug_intro.md index ad620459f3..54b8c17b77 100644 --- a/docs/tools/debug/debug_intro.md +++ b/docs/tools/debug/debug_intro.md @@ -1,4 +1,4 @@ -# Debugging +

Debugging with third party tools

There are extensive instructions on debugging Arm Mbed OS applications with [uVision 5](../debug-test/keil-uvision.html), [Eclipse](../debug-test/third-party-tools.html) and [Visual Studio Code](../debug-test/visual-studio-code.html), but you can use any IDE that supports GDB to debug Mbed OS applications. This document gives advice on how to configure these IDEs. Before starting, first [configure your local debug toolchain](setting-up-a-local-debug-toolchain.html). @@ -28,34 +28,6 @@ In your project folder, run: $ mbed export -i make_gcc_arm -m K64F ``` -#### Serial terminal - -You can open a serial terminal to the COM port of a connected Mbed target (usually board) using the `mbed sterm` command. If no COM port is specified, Mbed CLI detects the connected Mbed targets and their COM ports. - -There are various options to `mbed sterm`: - -- `--port ` to specify system COM port to connect to. -- `--baudrate ` to select the communication baudrate, where the default value is 9600. -- `--echo ` to switch local echo (default is `on`). -- `--reset` to reset the connected target by sending Break before opening the serial terminal. - -You can also set default port, baudrate and echo mode using the `TERM_PORT`, `TERM_BAUDRATE` and `TERM_ECHO` Mbed CLI configuration options. - -The following shortcuts are available within the serial terminal: - -- Ctrl+b - Send Break (reset target). -- Ctrl+c - Exit terminal. -- Ctrl+e - Toggle local echo. -- Ctrl+h - Help. -- Ctrl+t - Menu escape key. -- _You can view more shortcuts within the serial terminal's help menu (Ctrl+h)._ - -You can also add the `--sterm` option to `mbed compile -f` to compile a new program, flash the program or firmware image to the connected target and then open the serial terminal to its COM port: - -``` -$ mbed compile -t GCC_ARM -m K64F -f --sterm -``` - ## Building your project You can now configure your IDE to build this project by setting the build command to: diff --git a/docs/tools/debug/debug_with_printf.md b/docs/tools/debug/debug_with_printf.md index da870453ab..6ab3e7c4a6 100644 --- a/docs/tools/debug/debug_with_printf.md +++ b/docs/tools/debug/debug_with_printf.md @@ -1,110 +1,14 @@ # Debugging using printf() statements -An easy way to inspect what your application is doing is to augment your application with log statements. In Arm Mbed, you can use a serial connection to send feedback from your development board back to your computer. This uses the same USB cable that you use to program your device. +An easy way to inspect what your application is doing is to augment your application with `printf()` statements. In Mbed OS, you can use a serial connection to send feedback from your development board back to your computer. ## Prerequisites -### Windows - -Install the serial port driver for your development board: - -- For ST boards: [ST Link Driver](https://os.mbed.com/teams/ST/wiki/ST-Link-Driver). -- For all other boards: [Arm Mbed Windows serial port driver](../program-setup/windows-serial-driver.html) - not required for Windows 10. - -You also need a serial monitor: - -- [TeraTerm](http://sourceforge.jp/projects/ttssh2/files). - -### macOS - -On macOS, all software comes installed by default. - -### Linux - -If you do not have it, install [GNU Screen](https://www.gnu.org/software/screen/). - -## Getting started - -To send data over the serial connection, use the [BufferedSerial](../apis/serial-uart-apis.html) object. - -### Example program - -This program blinks the LED on your development board and prints a message every time the LED changes state: - -[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-snippet-DebugPrintf_BlinksLED/tree/v6.0)](https://github.com/ARMmbed/mbed-os-snippet-DebugPrintf_BlinksLED/blob/v6.0/main.cpp) - - -Compile this program, and flash it on your development board. You now can inspect these messages using a serial monitor. - -### Seeing the log messages - -### Windows - -1. Open TeraTerm. -1. Click *File > New Connection*. -1. Select the *Serial* radio button. -1. Choose your development board from the drop-down menu (often called `mbed Serial Port` or `STLink Virtual Port`). -1. Click *OK*. -1. Log messages appear in the main window. - -![](../../images/printf1.png)Selecting the COM port - -Seeing the output over the serial port - -**Note:** Unsure which COM port is used? In the [device manager](http://www.computerhope.com/issues/ch000833.htm), look under the *Ports* section. - -### macOS - -1. Open a terminal window. -1. Enter `screen /dev/tty.usbm`, and press `Tab` to autocomplete. -1. Press `Enter`. -1. Log messages appear. -1. To exit, press: - - `Ctrl+A` - - `Ctrl+\` - - `y` - -### Linux - -1. Open a terminal window. -1. Find the handler for your device: - - ``` - $ ls /dev/ttyACM* - /dev/ttyACM0 - ``` - -1. Connect to the board by entering `sudo screen /dev/ttyACM0 9600`. -1. Log messages appear. -1. To exit: - 1. Press `Ctrl+A`. - 1. Enter `quit`. - -**Note:** To avoid using `sudo`, set up a udev rule. - -### Setting the baud rate - -By default, the speed at which the microcontroller and your computer communicate (the baud rate) is set to 9600 baud. This setting fits most use cases, but you can change it by calling the `baud` function on the serial object: - -[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-snippet-DebugPrintf_SetBaudRate/tree/v6.0)](https://github.com/ARMmbed/mbed-os-snippet-DebugPrintf_SetBaudRate/blob/v6.0/main.cpp) - - -If you change the baud rate on the device, you also need to change it on your serial monitor: - -1. Windows: - 1. In TeraTerm, go to *Setup > Serial Port*. - 1. Change *Baud rate* to 115200. -1. macOS and Linux: Pass the baud rate as the last argument to the `screen` command: - - ``` - $ screen /dev/ttyACM0 115200 - ``` - -![](../../images/printf3.png)Changing the baud rate +For a tutorial on setting up serial communication, see [Board to PC communication over USB](../program-setup/serial-communication.html). ## Printf() -As seen above, you use the `printf()` function to communicate back to the user: +The `printf()` function is the recommended way to communicate back to the user: 1. The `printf()` functions produce output according to a format string (containing format specifiers) and matching value arguments. 2. The microcontroller's universal asynchronous receiver/transmitter (UART) console peripheral "feeds" output from `printf()` into the interface chip. diff --git a/docs/tools/debug/debugging_mbed_os_apps.md b/docs/tools/debug/debugging_mbed_os_apps.md index 2c87cbd59e..be664c0c52 100644 --- a/docs/tools/debug/debugging_mbed_os_apps.md +++ b/docs/tools/debug/debugging_mbed_os_apps.md @@ -1,14 +1,14 @@ -# Debugging Arm Mbed OS applications +# Debugging methods for Arm Mbed OS applications At the heart of Arm Mbed is the [Online Compiler](../build-tools/mbed-online-compiler.html). 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. +The simplest way to debug your code is to augment your code with [printf](../tutorials/debugging-using-printf-statements.html) statements, which you can observe from your PC using a [serial terminal](../tutorials/serial-comm.html). ## Debugging from an IDE Keil uVision natively supports debugging Mbed OS applications. To set up uVision, read [Debugging with Keil uVision](../debug-test/keil-uvision.html). -Mbed also supports debugging using any IDE that supports GDB. To set up the debugger, first read [Setting up your local debug toolchain](setting-up-a-local-debug-toolchain.html). 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 [Setting up your local debug toolchain](../debug-test/setting-up-a-local-debug-toolchain.html). Then read the section for your specific IDE. The same principles apply to any unlisted IDEs that supports GDB: 1. Producing [debug builds with Arm Mbed CLI](../program-setup/debug-builds-cli.html). 1. Debugging with [Eclipse](../debug-test/third-party-tools.html). diff --git a/redirects.json b/redirects.json index 969b413560..32fee64014 100644 --- a/redirects.json +++ b/redirects.json @@ -50,7 +50,7 @@ "reference/bare-metal-apis.html": "apis/index.html", "reference/configuration-mesh.html": "apis/configuration-mesh.html", "tools/greentea-testing-applications.html": "debug-test/greentea-for-testing-applications.html", - "tools/debugging-arm-mbed-os-applications.html": "debug-test/debugging-arm-mbed-os-applications.html", + "tools/debugging-arm-mbed-os-applications.html": "debug-test/debugging-methods-for-arm-mbed-os-applications.html", "tools/setting-up-a-local-debug-toolchain.html": "debug-test/setting-up-a-local-debug-toolchain.html", "tools/daplink.html": "debug-test/daplink.html", "tools/icetea-testing-applications.html": "debug-test/icetea-test-applications.html", @@ -140,8 +140,8 @@ "porting/testing-with-the-greentea-framework.html": "porting/testing.html", "porting/mbed-os-built-in-tests-detailed-procedure.html": "porting/testing.html", "porting/setting-up-to-debug-mbed-os-programs.html": "porting/porting.html", - "quick-start/online-with-the-online-compiler.html": "quick-start/build-and-debug-with-the-online-compiler.html", - "quick-start/offline-with-mbed-cli.html": "quick-start/build-and-debug-with-mbed-cli.html", + "quick-start/online-with-the-online-compiler.html": "quick-start/build-with-the-online-compiler.html", + "quick-start/offline-with-mbed-cli.html": "quick-start/build-with-mbed-cli.html", "tools/installation-and-setup.html": "build-tools/install-and-set-up.html", "tools/manual-installation.html": "build-tools/install-and-set-up.html", "tools/configuration-options.html": "build-tools/install-and-set-up.html",