Update README with info about mbed-os-tools

Author: bridadan

legacy/mbed-ls/README.md

@@ -1,5 +1,9 @@
-[![Build status](https://circleci.com/gh/ARMmbed/mbed-ls/tree/master.svg?style=svg)](https://circleci.com/gh/ARMmbed/mbed-ls/tree/master)
-[![Coverage Status](https://coveralls.io/repos/github/ARMmbed/mbed-ls/badge.svg?branch=master)](https://coveralls.io/github/ARMmbed/mbed-ls?branch=master)
+# Development moved
+
+The development of Mbed LS has been moved into the [mbed-os-tools](../../mbed_os_tools) package. You can continue to use this module for legacy reasons, however all further development should be continued in the new package.
+
+-------------
+
 [![PyPI version](https://badge.fury.io/py/mbed-ls.svg)](https://badge.fury.io/py/mbed-ls)
 
 # Mbed LS
@@ -31,8 +35,8 @@ $ pip install mbed-ls --upgrade
 Install Mbed LS from sources with the following commands:
 
 ```bash
-$ git clone https://github.com/ARMmbed/mbed-ls.git
-$ cd mbed-ls
+$ git clone https://github.com/ARMmbed/mbed-os-tools.git
+$ cd mbed-os-tools/legacy/mbed-ls
 $ python setup.py install
 ```
 
@@ -400,7 +404,7 @@ Mbed LS currently supports the following types of debuggers:
 
 ### Adding support for DAPLink-compatible platforms (DAPLink, ST-LINK, and CMSIS-DAP)
 
-Add an entry to the `daplink` section of the [`DEFAULT_PLATFORM_DB`](https://github.com/ARMmbed/mbed-ls/blob/master/mbed_lstools/platform_database.py#L45).
+Add an entry to the `daplink` section of the [`DEFAULT_PLATFORM_DB`](../../mbed_os_tools/detect/platform_database.py).
 
 If your platform's name is `NEW_PLATFORM` and it has platform ID of `9999`, the new entry should be:
 
@@ -418,7 +422,7 @@ Please order the entries by the platform ID when adding new platforms.
 
 ### Adding support for J-Link platforms
 
-J-Link detection works differently due to the information present on the platform's filesystem. All new entries should be added to the `jlink` section of the [`DEFAULT_PLATFORM_DB`](https://github.com/ARMmbed/mbed-ls/blob/master/mbed_lstools/platform_database.py#L45).
+J-Link detection works differently due to the information present on the platform's filesystem. All new entries should be added to the `jlink` section of the [`DEFAULT_PLATFORM_DB`](../../mbed_os_tools/detect/platform_database.py).
 
 The following is an example `jlink` platform entry:
 
@@ -447,4 +451,4 @@ If your J-Link platform does not follow this convention, please raise an issue w
 
 The type of debugger present on the platform affects how it is detected. The USB Vendor ID is used to detect which type of debugger is present on the platform.
 
-If a new type of debugger is being introduced to Mbed LS with the platform, you will need to add the Vendor ID to the [identification map](https://github.com/ARMmbed/mbed-ls/blob/master/mbed_lstools/lstools_base.py#L72-L76). You will also need to assign the correct "update from the filesystem" logic [here](https://github.com/ARMmbed/mbed-ls/blob/master/mbed_lstools/lstools_base.py#L226-L230). If the debugger is compatible with the files presented by DAPLink, you may reuse that implementation when updating the device information from the filesystem. If it is not, you may need to write your own update logic. If you need guidance on this, please ask for it when you submit an issue or a pull request.
+If a new type of debugger is being introduced to Mbed LS with the platform, you will need to add the Vendor ID to the [identification map](../../mbed_os_tools/detect/lstools_base.py). You will also need to assign the correct "update from the filesystem" logic [here](../../mbed_os_tools/detect/lstools_base.py). If the debugger is compatible with the files presented by DAPLink, you may reuse that implementation when updating the device information from the filesystem. If it is not, you may need to write your own update logic. If you need guidance on this, please ask for it when you submit an issue or a pull request.