Keil Studio replaced by Keil Studio Cloud

Elise-Kaminski · Elise-Kaminski · commit a29e1a6f1765 · 2023-02-02T14:30:42.000Z
diff --git a/docs.json b/docs.json
@@ -94,7 +94,7 @@
                     "sources": []
                 },
                 {
-                  "title": "Build with Keil Studio",
+                  "title": "Build with Keil Studio Cloud",
                   "intro": {
                     "path": "docs/quick-start/keil-studio.md"
                   },
@@ -987,7 +987,7 @@
                     "sources": []
                 },
                 {
-                    "title": "Keil Studio",
+                    "title": "Keil Studio Cloud",
                     "sources": [{
                         "path": "docs/tools/Studio/keil-studio.md"
                     }]
diff --git a/docs/api/connectivity/lorawan/lorawan.md b/docs/api/connectivity/lorawan/lorawan.md
@@ -1,6 +1,6 @@
 <h1 id="lorawaninterface">LoRaWANInterface</h1>
 
-The [LoRaWANInterface](../mbed-os-api-doxy/class_lo_ra_w_a_n_interface.html) provides a C++ API for connecting to the internet over a LoRa network. This subsection explains the `LoRaWANInterface` API reference and then presents an example that you can directly import to Keil Studio.
+The [LoRaWANInterface](../mbed-os-api-doxy/class_lo_ra_w_a_n_interface.html) provides a C++ API for connecting to the internet over a LoRa network. This subsection explains the `LoRaWANInterface` API reference and then presents an example that you can directly import to Keil Studio Cloud.
 
 To configure this class, please see the [LoRa configuration documentation](../apis/lorawan-configuration.html).
 
diff --git a/docs/api/connectivity/tutorials/intro-to-lora.md b/docs/api/connectivity/tutorials/intro-to-lora.md
@@ -208,19 +208,19 @@ Now that the device is registered in The Things Network, you can start writing c
 
 ### Importing the demo application
 
-Mbed comes with [tools](../build-tools/index.html) which you can use to build applications. In this tutorial, we are going to use Keil Studio, Arm's zero-installation web IDE.
+Mbed comes with [tools](../build-tools/index.html) which you can use to build applications. In this tutorial, we are going to use , Arm's zero-installation web IDE.
 
-1. Go to [studio.keil.arm.com](https://studio.keil.arm.com/auth/login/) and log into Keil Studio using your Arm or Mbed account. If you do not have an Arm or Mbed account, sign up from the login page.
+1. Go to [studio.keil.arm.com](https://studio.keil.arm.com/auth/login/) and log into Keil Studio Cloud using your Arm or Mbed account. If you do not have an Arm or Mbed account, sign up from the login page.
 1. Open a new browser window and go to [mbed-os-example-lorawan](https://github.com/ARMmbed/mbed-os-example-lorawan).
 1. Copy the URL of the example project.
-1. In Keil Studio, select **File** > **Clone**.
+1. In Keil Studio Cloud, select **File** > **Clone**.
     The **Clone** dialog box displays.
 1. Paste the URL and click **Add project**.
-    Keil Studio clones the project with the version of Mbed OS it was originally created with. The project is set as the active project by default.
+    Keil Studio Cloud clones the project with the version of Mbed OS it was originally created with. The project is set as the active project by default.
 
 ### Setting keys
 
-In Keil Studio:
+In Keil Studio Cloud:
 
 1. Open the `mbed_app.json` file. This file contains the configuration for the application and holds the authentication keys.
 1. If you have a SX1272 or SX1276 **shield** (not if you have a module), set your radio type under `lora-radio`.
@@ -231,7 +231,7 @@ In Keil Studio:
 
 #### Sending the value of the PIR sensor
 
-To send the current value of the PIR sensor (whether it sees movement), in Keil Studio:
+To send the current value of the PIR sensor (whether it sees movement), in Keil Studio Cloud:
 
 1. Open `main.cpp`.
 1. Replace the function `send_message()` with:
@@ -257,7 +257,7 @@ To send the current value of the PIR sensor (whether it sees movement), in Keil
 
 Now you can verify if the setup works by flashing this application to your board.
 
-1. In Keil Studio, connect your board to your computer. The first time you connect your board, you have to click the **Connect to target hardware** button to the right of the **Target hardware** drop-down list. After the first successful connection, Keil Studio detects the board and suggests a matching target hardware.
+1. In Keil Studio Cloud, connect your board to your computer. The first time you connect your board, you have to click the **Connect to target hardware** button to the right of the **Target hardware** drop-down list. After the first successful connection, Keil Studio Cloud detects the board and suggests a matching target hardware.
 1. Click the **Run project** button to build the project and flash it to the board.
     You can see the device joining and then sending messages in the The Things Network console, under the **Live data** tab:
 
@@ -281,7 +281,7 @@ Call `send_message` whenever you want (for example after the state of the sensor
 
 You can also send data back to the device. Because LoRaWAN (in Class-A mode, which you're using here) is not continuously connected to the network, you need to wait for a receive (RX) window to occur to receive data. An RX window opens after a transmission. So you need to *send* to the network before you can receive a message. If you send a message from The Things Network to your device, the network automatically queues the message and delivers it in the next RX window.
 
-You can toggle the LED on your development board over LoRa. In Keil Studio:
+You can toggle the LED on your development board over LoRa. In Keil Studio Cloud:
 
 1. Open `main.cpp`.
 1. Replace the `receive_message` function with:
diff --git a/docs/api/connectivity/tutorials/light-control.md b/docs/api/connectivity/tutorials/light-control.md
@@ -17,7 +17,7 @@ This tutorial requires:
 
 ## Import the application
 
-With Keil Studio, click the **Import into Keil Studio Cloud** button below:
+With Keil Studio Cloud, click the **Import into Keil Studio Cloud** button below:
 
 [![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-example-mesh-minimal)](https://github.com/ARMmbed/mbed-os-example-mesh-minimal/blob/mbed-os-6.7.0/mesh_led_control_example.cpp)
 
@@ -105,7 +105,7 @@ To change the RF driver, set the preferred RF driver `provide_default` value to
 
 1. Compile the application:
 
-   - With Keil Studio, click the **Build project** button.
+   - With Keil Studio Cloud, click the **Build project** button.
 
    - With Mbed CLI, invoke `mbed compile`, and specify the name of your target and toolchain:
 
@@ -114,14 +114,14 @@ To change the RF driver, set the preferred RF driver `provide_default` value to
    ```
 
    Your PC may take a few minutes to compile your code.
-   With Keil Studio, the compiled binary is automatically downloaded after a successful build. Check your **Downloads** folder.
+   With Keil Studio Cloud, the compiled binary is automatically downloaded after a successful build. Check your **Downloads** folder.
    With Mbed CLI, the compiled binary is next to the source code, in your local copy of the example.
 
 1. Connect your Mbed device to the computer over USB.
 
 1. Flash the code:
 
-  - With Keil Studio, click the **Run project** button to flash the code to your device and start the program.
+  - With Keil Studio Cloud, click the **Run project** button to flash the code to your device and start the program.
 
   - With Mbed CLI:
       1. Copy the binary file to the Mbed device.
diff --git a/docs/api/drivers/tutorials/alarm-tutorial.md b/docs/api/drivers/tutorials/alarm-tutorial.md
@@ -4,11 +4,11 @@ This tutorial is for an alarm application that uses a simple countdown mechanism
 
 The LEDs provide some feedback to the user: when setting the alarm, the LEDs blink to show the input was recognised. When the alarm is fully set, the LEDs blink the configured delay once, before letting the device go into sleep mode.
 
-<span class="tips">**Tip:** You can complete this tutorial with Keil Studio or [Mbed CLI](../tools/installation-and-setup.html).</span>
+<span class="tips">**Tip:** You can complete this tutorial with Keil Studio Cloud or [Mbed CLI](../tools/installation-and-setup.html).</span>
 
 ## Import the example application
 
-With Keil Studio, click the **Import into Keil Studio Cloud** button below:
+With Keil Studio Cloud, click the **Import into Keil Studio Cloud** button below:
 
 [![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-snippet-Alarm/tree/v6.7)](https://github.com/ARMmbed/mbed-os-snippet-Alarm/blob/v6.7/main.cpp)
 
@@ -23,7 +23,7 @@ cd mbed-os-example-alarm
 
 1. Compile the application:
 
-   - With Keil Studio, click the **Build project** button.
+   - With Keil Studio Cloud, click the **Build project** button.
 
    - With Mbed CLI, invoke `mbed compile`, and specify the name of your target and toolchain (`GCC_ARM`, `ARM`, `IAR`). For example, for the ARM Compiler 5 and FRDM-K64F:
 
@@ -32,14 +32,14 @@ cd mbed-os-example-alarm
    ```
 
    Your PC may take a few minutes to compile your code.
-   With Keil Studio, the compiled binary is automatically downloaded after a successful build. Check your **Downloads** folder.
+   With Keil Studio Cloud, the compiled binary is automatically downloaded after a successful build. Check your **Downloads** folder.
    With Mbed CLI, the compiled binary is next to the source code, in your local copy of the example.
 
 1. Connect your Mbed device to the computer over USB.
 
 1. Flash the code:
 
-  - With Keil Studio, click the **Run project** button to flash the code to your device and start the program.
+  - With Keil Studio Cloud, click the **Run project** button to flash the code to your device and start the program.
 
   - With Mbed CLI:
       1. Copy the binary file to the Mbed device.
diff --git a/docs/bare_metal/bare_metal.md b/docs/bare_metal/bare_metal.md
@@ -4,7 +4,7 @@ Bare metal is a profile of Mbed OS for ultraconstrained hardware: compact and wi
 
 The bare metal profile implements a subset of Mbed OS's RTOS APIs that are useful in non-threaded applications, such as semaphores (calling the release API from interrupts) and tickers (to set up a recurring interrupt). It does not include [Keil RTX](https://www2.keil.com/mdk5/cmsis/rtx), and is therefore suitable for applications that do not require complex thread management. Instead of the RTOS's scheduler, all activities are polled or interrupt-driven. This simplifies application code and allows using APIs that are not thread safe. Just as important, you can use the code-optimized versions of the C standard libraries, `microlib` and `newlib-nano`, which are much smaller than the thread safe equivalents the full profile requires.
 
-The Mbed OS build tools - Keil Studio, Mbed Studio and Mbed CLI - all support working with the bare metal profile.
+The Mbed OS build tools - Keil Studio Cloud, Mbed Studio and Mbed CLI - all support working with the bare metal profile.
 
 ## Features
 
diff --git a/docs/debugging-testing/debug/common_issues.md b/docs/debugging-testing/debug/common_issues.md
@@ -4,9 +4,9 @@ When you start using Mbed OS, you may find small challenges in a few cases. This
 
 ## Use the latest tools
 
-### Keil Studio and Mbed Studio
+### Keil Studio Cloud and Mbed Studio
 
-Keil Studio and Mbed Studio come with a built-in debugger. For instructions on using the debugger mode and debugger tools, please see the [Keil Studio](https://developer.arm.com/documentation/102497/1-5/Monitor-and-debug/Debug-a-project-with-Keil-Studio/Introduction) or [Mbed Studio](https://os.mbed.com/docs/mbed-studio/current/monitor-debug/debugging-with-mbed-studio.html) documentation.
+Keil Studio Cloud and Mbed Studio come with a built-in debugger. For instructions on using the debugger mode and debugger tools, please see the [Keil Studio Cloud](https://developer.arm.com/documentation/102497/1-5/Monitor-and-debug/Debug-a-project-with-Keil-Studio/Introduction) or [Mbed Studio](https://os.mbed.com/docs/mbed-studio/current/monitor-debug/debugging-with-mbed-studio.html) documentation.
 
 ### Mbed CLI
 
diff --git a/docs/debugging-testing/debug/debugging_mbed_os_apps.md b/docs/debugging-testing/debug/debugging_mbed_os_apps.md
@@ -1,13 +1,13 @@
 # Debugging methods for Arm Mbed OS applications
 
-At the heart of Arm Mbed is Keil Studio. 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 Keil Studio Cloud. 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 [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 Studio, Mbed Studio and Keil µVision natively support debugging Mbed OS applications:
-* To set up Keil Studio, read the [Keil Studio documentation](https://developer.arm.com/documentation/102497/1-5/Monitor-and-debug/Debug-a-project-with-Keil-Studio/Introduction).
+Keil Studio Cloud, Mbed Studio and Keil µVision natively support debugging Mbed OS applications:
+* To set up Keil Studio Cloud, read the [Keil Studio Cloud documentation](https://developer.arm.com/documentation/102497/1-5/Monitor-and-debug/Debug-a-project-with-Keil-Studio/Introduction).
 * To set up Mbed Studio, read the [Mbed Studio documentation](https://os.mbed.com/docs/mbed-studio/current/monitor-debug/debugging-with-mbed-studio.html).
 * To set up µVision, read [Debugging with Keil µVision](../debug-test/keil-uvision.html).
 
diff --git a/docs/introduction/introduction.md b/docs/introduction/introduction.md
@@ -16,12 +16,12 @@ We release Mbed OS under an Apache 2.0 license, so you can confidently use it in
 
 ## Getting started
 
-Our [quick start](../quick-start/index.html) guides show how to build an example application for both the full profile and bare metal profile, with Keil Studio, Mbed Studio and Mbed CLI.
+Our [quick start](../quick-start/index.html) guides show how to build an example application for both the full profile and bare metal profile, with Keil Studio Cloud, Mbed Studio and Mbed CLI.
 
-| [Build with Keil Studio](https://developer.arm.com/documentation/102497/1-5/Tutorials/Get-started-with-an-Mbed-OS-Blinky-example) | [Build with Mbed Studio](https://os.mbed.com/docs/mbed-studio/current/getting-started/index.html) | [Build with Mbed CLI 1](../quick-start/build-with-mbed-cli.html) |
+| [Build with Keil Studio Cloud](https://developer.arm.com/documentation/102497/1-5/Tutorials/Get-started-with-an-Mbed-OS-Blinky-example) | [Build with Mbed Studio](https://os.mbed.com/docs/mbed-studio/current/getting-started/index.html) | [Build with Mbed CLI 1](../quick-start/build-with-mbed-cli.html) |
 | --- | --- | --- |
 | Replaces the Mbed Online Compiler. Our zero-installation web IDE to explore Mbed OS and CMSIS; great for rapid prototyping and education. <br>This link will take you to Arm Developer | Our dedicated desktop IDE. Includes all the necessary tools to work with Mbed OS. <br>This link will take you to the Mbed Studio documentation site. | Command-line tool requiring manual setup of tools, but providing the greatest degree of flexibility. |
 
 ## Recently updated documentation
 
-- Mbed Online Compiler replaced by Keil Studio.
+- Mbed Online Compiler replaced by Keil Studio Cloud.
diff --git a/docs/introduction/terms.md b/docs/introduction/terms.md
@@ -6,13 +6,13 @@
 
 **Application** - An executable software module built out of libraries that acts as a final product.
 
-**Arm Keil Studio** - A web development environment for Mbed OS and CMSIS programs. Keil Studio [has its own documentation](https://developer.arm.com/documentation/102497/1-5/Arm-Keil-Studio).
+**Arm Keil Studio Cloud** - A web development environment for Mbed OS and CMSIS programs. Keil Studio Cloud [has its own documentation](https://developer.arm.com/documentation/102497/1-5/Arm-Keil-Studio).
 
 **Arm Mbed CLI** - The name of the Arm Mbed [command-line tool](../build-tools/mbed-cli-1.html), packaged as `mbed-cli`.
 
 **Arm Mbed interface** - The extra chip that sits on all [Mbed Enabled development boards](index.html). It's what makes the target chip (for example, K64F) look like a USB drive. It usually runs a separate piece of software that generally doesn't change. That software is usually `DAPLink`, `CMSIS-DAP` or `STLink`.
 
-**Arm Mbed Online Compiler** - This tool is deprecated. Please use [Keil Studio](https://studio.keil.arm.com/) or [Mbed Studio](https://os.mbed.com/studio/).
+**Arm Mbed Online Compiler** - This tool is deprecated. Please use [Keil Studio Cloud](https://studio.keil.arm.com/) or [Mbed Studio](https://os.mbed.com/studio/).
 
 **Arm Mbed OS** - Arm's [operating system](https://os.mbed.com/docs) for the Internet of Things.
 
@@ -42,7 +42,7 @@
 
 **Build Script** - A build automation and generation utility.
 
-**Build target** or **target** - A destination for a software build, for example an MCU, development board or custom board. Build targets are defined in either `targets.json` or `custom_targets.json`. A build (with Keil Studio, Mbed Studio and Mbed CLI) is always done for a specific target.
+**Build target** or **target** - A destination for a software build, for example an MCU, development board or custom board. Build targets are defined in either `targets.json` or `custom_targets.json`. A build (with Keil Studio Cloud, Mbed Studio and Mbed CLI) is always done for a specific target.
 
 **Byte** - A unit of digital information that consists of 8 bits (see `Bit`).
 
diff --git a/docs/introduction/tools.md b/docs/introduction/tools.md
@@ -2,7 +2,7 @@
 
 The Mbed product suite includes the tools you need to work with Mbed OS, whatever your skill level.
 
-For most users we recommend **Keil Studio**, which is our web IDE. Keil Studio lets you write and build applications using a web browser with no additional setup.
+For most users we recommend **Keil Studio Cloud**, which is our web IDE. Keil Studio Cloud lets you write and build applications using a web browser with no additional setup.
 
 If you prefer to work in a desktop environment, use our desktop IDE **Mbed Studio**. Mbed Studio includes the dependencies and tools you need to work with Mbed OS, including access to Arm Compiler 6 to build your code and pyOCD to debug it. For experienced developers, we also include the Mbed command line tools (such as Mbed CLI) with the Mbed Studio installation.
 
diff --git a/docs/program-setup/build-profiles-rules/build_profiles.md b/docs/program-setup/build-profiles-rules/build_profiles.md
@@ -1,6 +1,6 @@
 # Build profiles
 
-Arm Mbed OS defines three collections of toolchain flags used during the build. These are __build profiles__.  The three build profiles are *develop*, *debug* and *release*. Keil Studio uses the *release* build profile for deploying programs (build and flash) and the *debug* build profile for debugging. When building from Mbed CLI, you may select the __build profile__ by passing your desired build profile, by name or path, to the `--profile` argument.
+Arm Mbed OS defines three collections of toolchain flags used during the build. These are __build profiles__.  The three build profiles are *develop*, *debug* and *release*. Keil Studio Cloud uses the *release* build profile for deploying programs (build and flash) and the *debug* build profile for debugging. When building from Mbed CLI, you may select the __build profile__ by passing your desired build profile, by name or path, to the `--profile` argument.
 
 ## Develop
 
diff --git a/docs/program-setup/concepts/managed-unmanaged-bootloader.md b/docs/program-setup/concepts/managed-unmanaged-bootloader.md
@@ -24,7 +24,7 @@ The Mbed OS bootloader is a hybrid of the boot selector and a bootloader, but it
 
 ### Managed and unmanaged bootloader tool integration
 
-Mbed tools (Keil Studio, Mbed Studio or Mbed CLI) can manage bootloaders where:
+Mbed tools (Keil Studio Cloud, Mbed Studio or Mbed CLI) can manage bootloaders where:
 
 - The bootloader comes before the application in ROM.
 - The application starts immediately after the bootloader.
diff --git a/docs/program-setup/mbed_targets.md b/docs/program-setup/mbed_targets.md
diff --git a/docs/program-setup/serial/serial_communication.md b/docs/program-setup/serial/serial_communication.md
diff --git a/docs/quick-start/keil-studio.md b/docs/quick-start/keil-studio.md
diff --git a/docs/quick-start/quick-start.md b/docs/quick-start/quick-start.md
diff --git a/docs/tools/Studio/keil-studio.md b/docs/tools/Studio/keil-studio.md
diff --git a/docs/tools/tools_intro.md b/docs/tools/tools_intro.md
