Remove uVisor

Author: Alexander Zilberkant

docs.json

@@ -408,10 +408,6 @@
                         "sources": [{
                                 "type": "markdown",
                                 "url": "https://github.com/ARMmbed/mbed-os-5-docs/blob/development/docs/reference/api/security/TLS.md"
-                            },
-                            {
-                                "type": "markdown",
-                                "url": "https://github.com/ARMmbed/uvisor/blob/master/docs/lib/INTRO.md"
                             }
                         ]
                     },

docs/introduction/examples.md

@@ -39,14 +39,6 @@ A few micro:bit How To videos:
 - [Hashing](https://os.mbed.com/teams/mbed-os-examples/code/mbed-os-example-tls-hashing/): performs hashing of a buffer with SHA-256 using various APIs. It serves as a tutorial for the basic hashing APIs of Mbed TLS.
 - [TLS client](https://os.mbed.com/teams/mbed-os-examples/code/mbed-os-example-tls-tls-client/): downloads a file from an HTTPS server (os.mbed.com) and looks for a specific string in that file.
 
-##### Arm Mbed uVisor
-
-- [Threaded Blinky with uVisor](https://github.com/ARMmbed/mbed-os-example-uvisor-thread): an example threaded application with uVisor security.
-- [IRQ Blinky uVisor](https://github.com/ARMmbed/mbed-os-example-uvisor): an example threaded application with uVisor security and IRQ support.
-- [Threaded REPC with uVisor](https://github.com/ARMmbed/mbed-os-example-uvisor-number-store): using uVisor APIs to build a box that stores a number.
-
-These examples work on the K64F and the GNU Arm Embedded toolchain only.
-
 #### Core features
 
 ##### File system

docs/introduction/terms.md

@@ -16,8 +16,6 @@
 
 **Arm Mbed TLS** - A [comprehensive SSL/TLS solution](/docs/development/reference/tls.html) that makes it easy for developers to include cryptographic and SSL/TLS capabilities in their software and embedded products. As an SSL library, it provides an intuitive API, readable source code and a minimal and highly configurable code footprint.
 
-**Arm Mbed uVisor** - A self-contained [software hypervisor](/docs/development/reference/tls.html#uVisor) that creates independent secure domains on ARM Cortex-M3 and M4 micro-controllers.
-
 ### B
 
 **Bit** - A basic unit of digital information that can be one of two values: `0` (`false`) or `1` (`true`).

docs/reference/api/api.md

@@ -9,7 +9,6 @@ The [APIs](/docs/development/introduction/glossary.html) in this document are or
 - [Network Interfaces](network-interfaces.html): Network interfaces, Ethernet, Wifi, Cellular & Mesh.
 - [Bluetooth](/docs/development/reference/bluetooth.html): bluetooth low energy.
 - [LoRaWAN](/docs/development/reference/lorawan.html): low power wide area network.
-- [Security](/docs/development/reference/security.html): working with Arm Mbed uVisor and Arm Mbed TLS in the context of Mbed OS.
 - [Storage](/docs/development/reference/storage.html): working with the file system.
 
 We also provide guidelines for [contributing to Mbed OS](/docs/development/reference/contributing.html).

docs/reference/api/security/security.md

@@ -4,12 +4,8 @@ Security on Arm Mbed OS is divided into the following parts:
 
 - Mbed TLS. For details, please see our [full documentation](https://tls.mbed.org/).
 - Platform Security Architecture (PSA). For details, please see our [full documentation](https://developer.arm.com/products/architecture/security-architectures/platform-security-architecture).
-- Mbed uVisor. For details, please see our [full documentation](https://docs.mbed.com/docs/uvisor-and-uvisor-lib-documentation/en/latest/).
-
-<span class="warnings">**Warning**: uVisor is superseded by the Secure Partition Manager (SPM) defined in the ARM Platform Security Architecture (PSA). uVisor is deprecated as of Mbed OS 5.10, and being replaced by a native PSA-compliant implementation of SPM.</span>
 
 For information about working with these modules in Mbed OS context, please refer to the following documents:
 
 - [Connection security through Arm Mbed TLS](/docs/development/reference/tls.html).
 - Platform Security Architecture - TBD - under development.
-- [Device security through Arm Mbed uVisor](/docs/development/reference/uvisor.html).

docs/reference/configuration/uVisor.md

@@ -20,7 +20,6 @@ Option | Value | Description |
 `OS_DYNAMIC_MEM_SIZE` | 0 | RTX dynamic memory is disabled. |
 `OS_TICK_FREQ` | 1000 | Mbed OS Tickrate requires 1ms system tick. |
 `OS_STACK_WATERMARK` | 0 or 1 | Watermarking is enabled if `MBED_STACK_STATS_ENABLED` or `MBED_STACK_STATS_ENABLED` are set. |
-`OS_PRIVILEGE_MODE` | 0 or 1 | We set it for 0 if uVisor is enabled, 1 otherwise. |
 
 ### Code structure
 

docs/reference/contributing/target/rtos.md

@@ -109,10 +109,8 @@ You now have set up a debug connection. From here, you can flash debug builds, s
 
 ### Semihosting messages
 
-It's possible to send messages from the development board to your computer over the debug port using [semihosting](http://www.keil.com/support/man/docs/armcc/armcc_pge1358787046598.htm). Some parts of Mbed OS 5 also use this, such as uVisor. To see semihosting messages:
+It's possible to send messages from the development board to your computer over the debug port using [semihosting](http://www.keil.com/support/man/docs/armcc/armcc_pge1358787046598.htm). To see semihosting messages:
 
 1. Install [Netcat](https://en.wikipedia.org/wiki/Netcat).
 2. Connect pyOCD or OpenOCD to your board.
 3. Run `nc localhost 4444`.
-
-<span class="notes">**Note:** uVisor sends most of its messages during startup, so attach Netcat before starting your program.</span>

docs/tools/debug/local_debugging_toolchain.md

@@ -128,7 +128,6 @@ When you use target inheritance, you may alter the values of `extra_labels` usin
 #### `features`, `features_add` and `features_remove`
 
 The list of _features_ enables software features on a platform. Like `extra_labels`, `features` makes the build system aware of additional directories it must scan for resources. Unlike `extra_labels`, the build system recognizes a fixed set of values in the `features` list. The build system recognizes the following features:
- - `UVISOR`.
  - `BLE`.
  - `CLIENT`.
  - `IPV4`.

docs/tools/mbed_targets.md

@@ -230,7 +230,7 @@ $ mbed compile --config -t GCC_ARM -m K64F --prefix target --prefix app
 You can specify macros in your command-line using the -D option. For example:
 
 ```
-$ mbed compile -t GCC_ARM -m K64F -c -DUVISOR_PRESENT
+$ mbed compile -t GCC_ARM -m K64F -c -DDEBUG
 ```
 
 ##### Compile in debug mode