fix(references): fix broken links in Foundational Componenets section

Fixed the processors.wiki links and some broken links in Foundational components section

Signed-off-by: Telukula Jeevan Kumar Sahu <[email protected]>

Author: jeevantelukula

configs/AM335X/AM335X_linux_toc.txt

@@ -93,6 +93,7 @@ linux/Foundational_Components_Virtualization
 linux/Foundational_Components/Virtualization/Docker
 linux/Foundational_Components_Machine_Learning
 linux/Foundational_Components/Machine_Learning/armnn
+linux/Foundational_Components/Machine_Learning/tidl
 linux/Foundational_Components/Machine_Learning/tflite
 linux/Foundational_Components/Machine_Learning/neo
 linux/Foundational_Components/Machine_Learning/tvm

configs/AM437X/AM437X_linux_toc.txt

@@ -94,6 +94,7 @@ linux/Foundational_Components_Virtualization
 linux/Foundational_Components/Virtualization/Docker
 linux/Foundational_Components_Machine_Learning
 linux/Foundational_Components/Machine_Learning/armnn
+linux/Foundational_Components/Machine_Learning/tidl
 linux/Foundational_Components/Machine_Learning/tflite
 linux/Foundational_Components/Machine_Learning/neo
 linux/Foundational_Components/Machine_Learning/tvm

source/common/PRU-ICSS/Getting_Started_with_PSSP.rst

@@ -74,7 +74,7 @@ a few requirements once you have installed to your preferred directory.
 
 #. (**Optional**) Install CCS to the directory of your choosing
    CCS installation instruction for Linux can be found
-   `here <http://processors.wiki.ti.com/index.php/Linux_Host_Support_CCSv7#Installation_Instructions>`__.
+   `here <https://software-dl.ti.com/ccs/esd/documents/ccs_linux_host_support.html>`__.
    Makefiles are provided in order to build all examples in the PRU Software Support
    Package. The ability to build the PRU projects using the Makefiles
    makes CCS optional in a Linux environment.
@@ -88,7 +88,7 @@ a few requirements once you have installed to your preferred directory.
    `here <https://git.ti.com/pru-software-support-package/pru-software-support-package/trees/master>`__.
 #. Install CCS to the directory of your choosing
    Installers can be found
-   `here <http://processors.wiki.ti.com/index.php/Download_CCS#Code_Composer_Studio_Version_7_Downloads>`__.
+   `here <https://www.ti.com/tool/download/CCSTUDIO>`__.
 
 |
 

source/common/PRU-ICSS/Overview.rst

@@ -277,11 +277,11 @@ PRU evaluation hardware can be ordered from ti.com:
 
    * PRU Networking
 
-     * `TMDS64GPEVM <https://www.ti.com/tool/TMDS64GPEVM>`__
+     * `TMDS64EVM <https://www.ti.com/tool/TMDS64EVM>`__
 
    * Generic PRU Development
 
-     * `SK-AM64 <https://www.ti.com/tool/SK-AM64>`__
+     * `SK-AM64 <https://www.ti.com/tool/SK-AM64B>`__
 
  * AM65x
 

source/common/PRU-ICSS/PRU-Hands-on-Labs.rst

@@ -60,7 +60,7 @@ Software
    However, the notation ***<PRU_SW_PATH>*** will be used throughout
    the labs to reference this assumed installation location. If you use
    a different location please modify the steps below.
--  `CCSv6 <http://processors.wiki.ti.com/index.php/Download_CCS#Code_Composer_Studio_Version_6_Downloads>`__
+-  `CCSv6 <ti.com/tool/download/CCSTUDIO>`__
 -  `PRU Code Generation
    Tools <http://software-dl.ti.com/codegen/non-esd/downloads/download.htm#PRU>`__
    (also available through the CCS App Center)
@@ -868,9 +868,8 @@ Configure the Kernel
 .. note::
 
     This step is needed before building the kernel, kernel modules, device
-    tree files, etc. For more information about these steps, see the `Kernel
-    Users
-    Guide <http://software-dl.ti.com/processor-sdk-linux/esd/docs/latest/linux/Foundational_Components_Kernel_Users_Guide.html>`__.
+    tree files, etc. For more information about these steps, see the
+    :ref:`Kernel Users Guide <linux_kernel_users_guide>`.
 
 4. Prepare to build the kernel, kernel modules, device tree files, etc
 

source/linux/Examples_and_Demos/_Hands_on_with_QT.rst

@@ -1,4 +1,5 @@
 .. http://processors.wiki.ti.com/index.php/Sitara_Linux_Training:_Hands_on_with_QT
+.. _hands-on-with-qt:
 .. rubric:: Introduction
    :name: introduction-hands-on-qt
 

source/linux/Examples_and_Demos_Sub-system_Demos.rst

@@ -28,6 +28,8 @@ WLAN and Bluetooth
 ==================
 .. include:: Examples_and_Demos/_WLAN_and_Bluetooth.rst
 
+.. _hands-on-with-qt:
+
 Hands on with QT
 ================
 .. include:: Examples_and_Demos/_Hands_on_with_QT.rst

source/linux/Foundational_Components/Kernel/Kernel_Drivers/SPI.rst

@@ -198,7 +198,7 @@ simple means to send and receive SPI messages the spidev driver can be
 used. Spidev provides a user space accessible means to communicate with
 the SPI interface. Latest documentation regarding spidev driver can be
 found
-`here <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/spi/spidev.rst>`__.
+`here <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/spi/spidev.rst>`_.
 
 Spidev allows users to interact with the spi interface in a variety of
 programming languages that can communicate with kernel ioctls.

source/linux/Foundational_Components/Tools/Code_Composer_Studio/_CCS_Installation.rst

@@ -96,7 +96,7 @@ can be located by browsing to `SDK for Sitara
 Processors <http://www.ti.com/tool/linuxezsdk-sitara>`__ and selecting
 the device being used. The CCS installer can be found on the device's
 SDK installer page under the Optional Addons or directly from the
-`Download CCS <http://processors.wiki.ti.com/index.php/Download_CCS>`__ wiki page.
+`Download CCS <https://www.ti.com/tool/download/CCSTUDIO>`__ page.
 
 .. Image:: /images/SDK_download_page.png
 
@@ -292,8 +292,8 @@ After opening CCS with a new workspace:
 
 #. The *Projects:* list will now be populated with the projects found.
 #. Uncheck the following projects. They are Qt projects and are imported
-   using a different method. For more information, see the `Hands on
-   with QT <Examples_and_Demos_Sub-system_Demos.html#hands-on-with-qt>`__
+   using a different method. For more information, see the :ref:`Hands on
+   with QT <hands-on-with-qt>`
    training.
 
    -  matrix\_browser

source/linux/Foundational_Components/Tools/Code_Composer_Studio/_Kernel_Debugging_with_CCS.rst

@@ -5,9 +5,9 @@
 Starting with Sitara Linux SDK 6.0 the location of the toolchain has
 changed and for non ARM 9 devices a new Linaro based toolchain will be
 used. Details about the change in toolchain location can be found
-`here <http://processors.wiki.ti.com/index.php/Sitara_Linux_SDK_GCC_Toolchain#Updated.C2.A0Linux-Devkit_Structure>`__.
+:ref:`here <overview-getting-started>`.
 Also details about the switch to Linaro can be found
-`here <http://processors.wiki.ti.com/index.php/Sitara_Linux_SDK_GCC_Toolchain#Switch_to_Linaro>`__.
+:ref:`here <overview-getting-started>`.
 
 AM18x users are not affected by the switch to Linaro. Therefore, any
 references to the Linaro toolchain prefix "**arm-linux-gnueabihf**-"
@@ -324,7 +324,7 @@ your emulator and board must be ready.
 
 In this example a Beaglebone (AM3359) was used, together with the Sitara
 support package available at the `CCS download
-page <http://processors.wiki.ti.com/index.php/Download_CCS>`__.
+page <https://www.ti.com/tool/download/CCSTUDIO>`__.
 **Note:** check the `Getting Started
 Guide <http://processors.wiki.ti.com/index.php/GSG:Debugging_projects_v5#Creating_a_Target_Configuration_File>`__
 to learn how to create one.