diff --git a/source/common/EVM_Hardware_Setup/_TMDXIDK5728_Hardware_Setup.rst b/source/common/EVM_Hardware_Setup/_TMDXIDK5728_Hardware_Setup.rst index e9b43f9d4..6f26f17cb 100644 --- a/source/common/EVM_Hardware_Setup/_TMDXIDK5728_Hardware_Setup.rst +++ b/source/common/EVM_Hardware_Setup/_TMDXIDK5728_Hardware_Setup.rst @@ -40,22 +40,6 @@ designed to help you through the initial setup of the EVM. | representative, create a bootable µSD card (using the included blank | | µSD) and insert it into the EVM** | +--------------------------------------------------------------------------+ -| .. raw:: html | -| | -|
| -| | -| .. raw:: html | -| | -|
| -| | -| .. raw:: html | -| | -|
| -| | -| .. raw:: html | -| | -|
| -| | | .. Image:: /images/IDK_uSD.png | +--------------------------------------------------------------------------+ @@ -63,24 +47,7 @@ designed to help you through the initial setup of the EVM. | **2. Connect the power cable to the power jack on the board and plug in | | to an AC power source** | +--------------------------------------------------------------------------+ -| .. raw:: html | -| | -|
| -| | -| .. raw:: html | -| | -|
| -| | -| .. raw:: html | -| | -|
| -| | -| .. raw:: html | -| | -|
| -| | | .. Image:: /images/Power_cord_connect.png | -| | +--------------------------------------------------------------------------+ Note: When powering this IDK, always use the recommended power supply @@ -97,22 +64,6 @@ VDE, CCC, PSE, etc. | connect to the USB on the host. Connect Ethernet cable to GIG ETH0 if | | Network connectivity is required** | +--------------------------------------------------------------------------+ -| .. raw:: html | -| | -|
| -| | -| .. raw:: html | -| | -|
| -| | -| .. raw:: html | -| | -|
| -| | -| .. raw:: html | -| | -|
| -| | | .. Image:: /images/JTAGUSB_UART.png | +--------------------------------------------------------------------------+ @@ -122,22 +73,6 @@ power on the EVM. +--------------------------------------------------------------------------+ | **4. Select the power ON button to run power the IDK.** | +--------------------------------------------------------------------------+ -| .. raw:: html | -| | -|
| -| | -| .. raw:: html | -| | -|
| -| | -| .. raw:: html | -| | -|
| -| | -| .. raw:: html | -| | -|
| -| | | .. Image:: /images/PowerON.png | +--------------------------------------------------------------------------+ @@ -152,32 +87,7 @@ corresponding to FTDI UARTtoUSB will be turned on. | messages. Connecting to target using emulator has been discussed in the | | section below.** | +-----------------------------------------------+---------------------------------------------+ -| .. raw:: html | .. raw:: html | -| | | -|
|
| -| | | -| .. raw:: html | .. raw:: html | -| | | -|
| class="thumb tnone"> | -| | | -| .. raw:: html | .. raw:: html | -| | | -|
| style="width:302px;"> | -| | | | .. Image:: /images/Serial_connect.jpg | .. Image:: /images/Baudrate.jpg | -| | | -| .. raw:: html | .. raw:: html | -| | | -|
| class="thumbcaption"> | -| | | -| .. raw:: html | .. raw:: html | -| | | -|
|
| -| | | +-----------------------------------------------+---------------------------------------------+ .. rubric:: Connecting IDK EVM to Code Composer Studio @@ -200,18 +110,10 @@ configuration(File->New->Target Configuration file) as shown in the images below and provide appropriate name to the configuration. Select Texas Instuments XDS100v2 emulator and target as IDK\_AM572x. -.. raw:: html +.. note:: -
- -**NOTE** -If you don\`t find the IDK\_AM572x target make sure you have installed -the Sitara Device support version 1.3.x package correctly - -.. raw:: html - -
+ If you don't find the IDK\_AM572x target make sure you have installed + the Sitara Device support version 1.3.x package correctly .. Image:: /images/Target_configuration.png diff --git a/source/linux/Foundational_Components/IPC/_Multiple_Ways_of_ARM-DSP_Communication.rst b/source/linux/Foundational_Components/IPC/_Multiple_Ways_of_ARM-DSP_Communication.rst index 9279af80f..3ad133b49 100644 --- a/source/linux/Foundational_Components/IPC/_Multiple_Ways_of_ARM-DSP_Communication.rst +++ b/source/linux/Foundational_Components/IPC/_Multiple_Ways_of_ARM-DSP_Communication.rst @@ -68,24 +68,8 @@ uses RPMSG framework on the ARM which communicates to the counterpart on the slave core. On the slave core, it uses Codec engine and Frame Component for the video/image codec processing on IVA. -.. raw:: html - -
- -.. raw:: html - -
- .. Image:: /images/Mm_software_overview_v3.png -.. raw:: html - -
- -.. raw:: html - -
- **Overview of the Multimedia Software Stack using DCE** AM57xx as an example has the following accelerators diff --git a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/ADC.rst b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/ADC.rst index 16ed6b6aa..154a33cac 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/ADC.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/ADC.rst @@ -235,16 +235,9 @@ To test ADC, Connect a DC voltage supply to each of the AIN0 through AIN7 pins (based on your channel configuration), and vary voltage between 0 and 1.8v reference voltage. -.. raw:: html +.. caution:: -
- -**CAUTION** Make sure that the voltage supplied does not cross 1.8v - -.. raw:: html - -
+ Make sure that the voltage supplied does not cross 1.8v On loading the module you would see the IIO device created diff --git a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/DCAN.rst b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/DCAN.rst index 0edbcd0fa..35bff3f5f 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/DCAN.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/DCAN.rst @@ -77,28 +77,7 @@ changes. The boards that do require modifications to be enabled for CAN to work will be listed below. +-------------------------------------------------------------+---------------------------------------------+ -| .. raw:: html | .. raw:: html | -| | | -|
|
| -| | | -| .. raw:: html | .. raw:: html | -| | | -|
|
| -| | | -| .. raw:: html | .. raw:: html | -| | | -|
| style="width:598px;"> | -| | | | .. Image:: /images/Am335x-profile-selection.png | .. Image:: /images/Dcan_node.png | -| | | -| .. raw:: html | .. raw:: html | -| | | -|
|
| -| | | -| .. raw:: html | .. raw:: html | -| | | -|
|
| +-------------------------------------------------------------+---------------------------------------------+ | enable) | disabled to okay | +-------------------------------------------------------------+---------------------------------------------+ @@ -123,32 +102,7 @@ seen above. :name: connection-configuration +----------------------------------------+-----------------------------------------------+------------------------------------------------------+ -| .. raw:: html | .. raw:: html | .. raw:: html | -| | | | -|
|
|
| -| | | | -| .. raw:: html | .. raw:: html | .. raw:: html | -| | | | -|
| class="thumb tnone"> | class="thumb tnone"> | -| | | | -| .. raw:: html | .. raw:: html | .. raw:: html | -| | | | -|
| style="width:302px;"> | style="width:302px;"> | -| | | | | .. Image:: /images/Dcan.png | .. Image:: /images/Dcan-header.png | .. Image:: /images/Dcan_header_to_db9.png | -| | | | -| .. raw:: html | .. raw:: html | .. raw:: html | -| | | | -|
| class="thumbcaption"> | class="thumbcaption"> | -| | | | -| .. raw:: html | .. raw:: html | .. raw:: html | -| | | | -|
|
|
| -| | | | +----------------------------------------+-----------------------------------------------+------------------------------------------------------+ | DB9 to DB9 | Header to Header | Header to DB9 | +----------------------------------------+-----------------------------------------------+------------------------------------------------------+ @@ -188,23 +142,7 @@ connecting to. Only exception are the evms that don't include the CAN GND pin. +--------------------------------------------------------------------------+ -| .. raw:: html | -| | -|
| -| | -| .. raw:: html | -| | -|
| -| | | .. Image:: /images/Dcan_j6eco.png | -| | -| .. raw:: html | -| | -|
| -| | -| .. raw:: html | -| | -|
| +--------------------------------------------------------------------------+ | Example of DCAN header on DRA72 EVM | +--------------------------------------------------------------------------+ @@ -233,23 +171,7 @@ the metal lip meant to push some of the exposed wire into and soldering to the correct pins correctly. Use the below diagram as a reference. +-------------------------------------------------------------+------------------------------------------------+ -| .. raw:: html | .. raw:: html | -| | | -|
|
| -| | | -| .. raw:: html | .. raw:: html | -| | | -|
|
| -| | | | .. Image:: /images/DCAN_custom_cable_diagram.png | .. Image:: /images/Custom_cable.png | -| | | -| .. raw:: html | .. raw:: html | -| | | -|
|
| -| | | -| .. raw:: html | .. raw:: html | -| | | -|
|
| +-------------------------------------------------------------+------------------------------------------------+ | Wiring Diagram | Example of completed cable. | +-------------------------------------------------------------+------------------------------------------------+ @@ -518,30 +440,8 @@ Four additional drivers are required to utilize all the CAN features: DCAN driver architecture shown in the figure below, is mainly divided into three layers Viz user space, kernel space and hardware. -.. raw:: html - -
- -.. raw:: html - -
- -.. raw:: html - -
- .. Image:: /images/Dcan_driver_architecture.png -.. raw:: html - -
- -.. raw:: html - -
- - - .. rubric:: **User Space** CAN utils are used as the application binaries for transfer/receive diff --git a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/E5010_JPEG_Encoder.rst b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/E5010_JPEG_Encoder.rst index 65f3415d1..27f6055cd 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/E5010_JPEG_Encoder.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/E5010_JPEG_Encoder.rst @@ -40,14 +40,6 @@ Driver Architecture Below diagram depicts different software layers involved here : -.. raw:: html - -
- -.. raw:: html - -
- .. figure:: /images/E5010_JPEG_driver_stack.png E5010 JPEG Driver software stack diff --git a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/MCAN.rst b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/MCAN.rst index 911f8a94f..96f0304d6 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/MCAN.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/MCAN.rst @@ -66,32 +66,7 @@ Table: Boards M\_CAN Driver is Validated on :name: connection-configuration +------------------------------------------------+------------------------------------------------------+ - | .. raw:: html | .. raw:: html | - | | | - |
|
| - | | | - | .. raw:: html | .. raw:: html | - | | | - |
| class="thumb tnone"> | - | | | - | .. raw:: html | .. raw:: html | - | | | - |
| style="width:302px;"> | - | | | | .. Image:: /images/mcan-diagram-evm-to-evm.png | .. Image:: /images/Dcan_header_to_db9.png | - | | | - | .. raw:: html | .. raw:: html | - | | | - |
| class="thumbcaption"> | - | | | - | .. raw:: html | .. raw:: html | - | | | - |
|
| - | | | +------------------------------------------------+------------------------------------------------------+ | Header to Header | Header to DB9 | +------------------------------------------------+------------------------------------------------------+ @@ -145,23 +120,7 @@ Table: Boards M\_CAN Driver is Validated on to the correct pins correctly. Use the below diagram as a reference. +-------------------------------------------------------------+------------------------------------------------+ - | .. raw:: html | .. raw:: html | - | | | - |
|
| - | | | - | .. raw:: html | .. raw:: html | - | | | - |
|
| - | | | | .. Image:: /images/DCAN_custom_cable_diagram.png | .. Image:: /images/Custom_cable.png | - | | | - | .. raw:: html | .. raw:: html | - | | | - |
|
| - | | | - | .. raw:: html | .. raw:: html | - | | | - |
|
| +-------------------------------------------------------------+------------------------------------------------+ | Wiring Diagram | Example of completed cable. | +-------------------------------------------------------------+------------------------------------------------+ diff --git a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Network/CPSW-EST.rst b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Network/CPSW-EST.rst index ce3170dde..d91305f18 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Network/CPSW-EST.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Network/CPSW-EST.rst @@ -99,16 +99,8 @@ Here are the steps to configure this schedule. A sample wireshark capture for the example above is shown below -.. raw:: html - -
- .. image:: ../../../../../images/wireshark-tas.jpg -.. raw:: html - -
- Packet highlighted are the first packet transmitted during Gate open of Q2/TC2 and are spaced apart by about 500 msec which is the cycle-time of the TAS schedule. Also there are about 9 packets transmitted during the window which is about 12 * 9 = 108 usec within the Gate open interval of 125 usec. .. rubric:: Guard band diff --git a/source/linux/Foundational_Components/PRU-ICSS/Linux_Drivers/RPMsg.rst b/source/linux/Foundational_Components/PRU-ICSS/Linux_Drivers/RPMsg.rst index 17c561737..633b937d0 100644 --- a/source/linux/Foundational_Components/PRU-ICSS/Linux_Drivers/RPMsg.rst +++ b/source/linux/Foundational_Components/PRU-ICSS/Linux_Drivers/RPMsg.rst @@ -60,16 +60,8 @@ ability to rebuild the library if changes are desired. .. rubric:: ARM to PRU :name: arm-to-pru -.. raw:: html - -
- .. Image:: /images/Arm-to-pru.PNG -.. raw:: html - -
- The diagram to the right shows the process that occurs when the ARM sends a message to the PRU. These steps are shown for illustrative purposes as the provided software in the SDK hides them in an @@ -103,16 +95,8 @@ abstraction layer. .. rubric:: PRU to ARM :name: pru-to-arm -.. raw:: html - -
- .. Image:: /images/Pru-to-arm.PNG -.. raw:: html - -
- The diagram to the right shows the process that occurs when the PRU sends a message to the ARM. These steps are shown for illustrative purposes as the provided software in the SDK hides them in an diff --git a/source/linux/Foundational_Components/PRU-ICSS/Linux_Drivers/RemoteProc.rst b/source/linux/Foundational_Components/PRU-ICSS/Linux_Drivers/RemoteProc.rst index 22f75052f..3499c88dd 100644 --- a/source/linux/Foundational_Components/PRU-ICSS/Linux_Drivers/RemoteProc.rst +++ b/source/linux/Foundational_Components/PRU-ICSS/Linux_Drivers/RemoteProc.rst @@ -6,16 +6,8 @@ RemoteProc .. rubric:: Introduction :name: introduction-pru-icss-remoteproc-rpmsg -.. raw:: html - -
- .. Image:: /images/Overview.PNG -.. raw:: html - -
- The host processor on TI's Sitara family of devices is an ARM Cortex-A processor. Typically the ARM core is running Linux based on the :ref:`Processor SDK Linux `. @@ -64,24 +56,8 @@ load firmwares into the PRU cores and then run them. .. rubric:: Step 0 :name: step-0 -.. raw:: html - -
- -.. raw:: html - -
- .. Image:: /images/Step0_2_0_2_11.PNG -.. raw:: html - -
- -.. raw:: html - -
- The four blocks in the image to right represent: The ARM core running Linux, the Linux filesystem where the PRU firmware binaries are initially stored, the PRU subsystem, and DDR memory. This image shows @@ -109,16 +85,8 @@ inserted. .. rubric:: Step 1 :name: step-1 -.. raw:: html - -
- .. Image:: /images/Step1_2_0_2_11.PNG -.. raw:: html - -
- | In this step, the sysfs interface (mentioned above in step 0) is used to specify the name of the firmware to be loaded as well as to signal that the user wants to load and start the PRU cores @@ -134,16 +102,8 @@ inserted. .. rubric:: Step 2 :name: step-2 -.. raw:: html - -
- .. Image:: /images/Step2_2_0_2_11.PNG -.. raw:: html - -
- The pru_rproc module verifies two things before it proceeds with the firmware loading process. @@ -172,16 +132,8 @@ firmware loading process. .. rubric:: Step 3 :name: step-3 -.. raw:: html - -
- .. Image:: /images/Step3_2_0_2_11.PNG -.. raw:: html - -
- - The pru_rproc module configures all of the resources that are being requested by the firmwares - In this case, that includes creating vrings in DDR memory for @@ -195,16 +147,8 @@ firmware loading process. .. rubric:: Step 4 :name: step-4 -.. raw:: html - -
- .. Image:: /images/Step4_2_0_2_11.PNG -.. raw:: html - -
- | The pru_rproc module then loads the binary into the instruction RAM of the PRUs and also copies the resource table into the PRUs data RAM space @@ -221,16 +165,8 @@ firmware loading process. .. rubric:: Step 5 :name: step-5 -.. raw:: html - -
- .. Image:: /images/Step5_2_0_2_11.PNG -.. raw:: html - -
- Now that everything is configured and the application code is in place, the pru_rproc module instructs the PRU cores to begin execution. diff --git a/source/linux/Foundational_Components/Tools/Code_Composer_Studio/_CCS_Installation.rst b/source/linux/Foundational_Components/Tools/Code_Composer_Studio/_CCS_Installation.rst index f841d1a38..870bf32cd 100644 --- a/source/linux/Foundational_Components/Tools/Code_Composer_Studio/_CCS_Installation.rst +++ b/source/linux/Foundational_Components/Tools/Code_Composer_Studio/_CCS_Installation.rst @@ -22,21 +22,13 @@ CCS uses the Eclipse backend and includes the following plugins: - Cross-compile for GCC- allows easy access to the ARM GCC-based compiler included in the Processor Linux SDK -.. raw:: html +.. note:: -
- -**NOTE** -You should download CCS from the Processor Linux SDK Download page -because it comes with the above plug-ins already installed. Otherwise, -you will have to install the plug-ins yourself in order to take -advantage of all the features covered in the wiki help pages and wiki -training pages. - -.. raw:: html - -
+ You should download CCS from the Processor Linux SDK Download page + because it comes with the above plug-ins already installed. Otherwise, + you will have to install the plug-ins yourself in order to take + advantage of all the features covered in the wiki help pages and wiki + training pages. | @@ -132,23 +124,15 @@ to install it now, you can install CCS using the following commands: .. rubric:: CCS Installation Steps :name: ccs-installation-steps -.. raw:: html - -
+.. note:: -**NOTE** -The "Limited 90-day period" language in the CCS installer license -agreement applies only for the case of using high-speed JTAG emulators -(does not apply to use of the XDS100v2 JTAG emulator or an on-board -emulator). If a debug configuration is used that requires a high-speed -JTAG emulator, you will be prompted to register your software for a fee. -All use of CCS (excluding use of high-speed JTAG emulators) is free and -has no 90-day time limit. - -.. raw:: html - -
+ The "Limited 90-day period" language in the CCS installer license + agreement applies only for the case of using high-speed JTAG emulators + (does not apply to use of the XDS100v2 JTAG emulator or an on-board + emulator). If a debug configuration is used that requires a high-speed + JTAG emulator, you will be prompted to register your software for a fee. + All use of CCS (excluding use of high-speed JTAG emulators) is free and + has no 90-day time limit. When the CCS installer runs, you can greatly reduced the install time and installed disk space usage by taking the defaults as they appear in @@ -330,18 +314,10 @@ example we will use the *mem-util* project. .. Image:: /images/CCS_build_memutil.png - .. raw:: html - -
- - **NOTE** - You can use **Project -> Build All** to build all of the projects in - the *Project Explorer*. + .. note:: - .. raw:: html - -
+ You can use **Project -> Build All** to build all of the projects in + the *Project Explorer*. .. rubric:: Installing C/C++ Projects :name: installing-cc-projects @@ -359,19 +335,11 @@ file system: setting up a target filesystem, see `Processor SDK Linux Setup Script <../../Overview/Run_Setup_Scripts.html>`__. - .. raw:: html - -
- - **NOTE** - The top-level Makefile uses the install commands in the component - Makefiles and can be used as a reference for how to invoke the - install commands. - - .. raw:: html + .. note:: -
+ The top-level Makefile uses the install commands in the component + Makefiles and can be used as a reference for how to invoke the + install commands. #. For all file system types, you can also transfer the file using the drag-and-drop method of Remote System Explorer. See the `Remote @@ -417,18 +385,10 @@ build a simple *Hello World* application for the target. #. In the *Command* dialog, set the following values: Tool command prefix: **arm-linux-gnueabihf-**. - .. raw:: html - -
- - **NOTE** - The prefix ends with a "-". This is the prefix of the cross-compiler - tools as will be seen when setting the *Tool command path*. - - .. raw:: html + .. note:: -
+ The prefix ends with a "-". This is the prefix of the cross-compiler + tools as will be seen when setting the *Tool command path*. Tool command path: **/home/sitara/ti-sdk--/linux-devkit/sysroots/ - -.. raw:: html - -
- .. figure:: ../images/MM_D5520MP2_VXE384MP2_SW_overview.png :alt: codec software stack @@ -372,14 +364,6 @@ display the decoded video on the screen. The audio stream is queued and then decoded by the ARM audio GStreamer plugin, and then reaches its destination at the alsasink element to play the decoded audio. -.. raw:: html - -
- -.. raw:: html - -
- .. _gst-dec-playout-fig: .. figure:: ../images/Gst_decode_playout_v2.png @@ -387,16 +371,6 @@ destination at the alsasink element to play the decoded audio. GStreamer Decode Playout -.. raw:: html - -
- -.. raw:: html - -
- -| - Running a GStreamer pipeline ---------------------------- diff --git a/source/linux/How_to_Guides/Host/AM335x_ICEv2_flash_erase.rst b/source/linux/How_to_Guides/Host/AM335x_ICEv2_flash_erase.rst index 56048811b..eaafd0062 100644 --- a/source/linux/How_to_Guides/Host/AM335x_ICEv2_flash_erase.rst +++ b/source/linux/How_to_Guides/Host/AM335x_ICEv2_flash_erase.rst @@ -27,18 +27,10 @@ on a Ubuntu 14.04 host system #. Create a target configuration file in CCS to connect to the AM3359 ICE board - .. raw:: html + .. note:: -
- - **NOTE** - If you already have a target configuration for your AM3359 ICE board - you may skip this step - - .. raw:: html - -
+ If you already have a target configuration for your AM3359 ICE board + you may skip this step - Click **File -> New-> Target Configuration File** - Filename : AM3359-ice-v2.ccxml. Check "Use shared location" to be diff --git a/source/linux/Industrial_Protocols/PTP/_PTP.rst b/source/linux/Industrial_Protocols/PTP/_PTP.rst index e95e75ed4..14c5efb33 100644 --- a/source/linux/Industrial_Protocols/PTP/_PTP.rst +++ b/source/linux/Industrial_Protocols/PTP/_PTP.rst @@ -1254,45 +1254,13 @@ for more details. +--------------------------------------+--------------------------------------+ | Wire on AM571x IDK | Signal | +======================================+======================================+ -| lower yellow wire | .. raw:: html | -| | | -| |
| -| | | -| | timer15 | -| | | -| | .. raw:: html | -| | | -| |
| +| lower yellow wire | timer15 | +--------------------------------------+--------------------------------------+ -| J21-18 right blue wire | .. raw:: html | -| | | -| |
| -| | | -| | pr2\_edc\_latch0\_out | -| | | -| | .. raw:: html | -| | | -| |
| +| J21-18 right blue wire | pr2\_edc\_latch0\_out | +--------------------------------------+--------------------------------------+ -| J21-20 purple wire | .. raw:: html | -| | | -| |
| -| | | -| | pr1\_edc\_latch0\_out | -| | | -| | .. raw:: html | -| | | -| |
| +| J21-20 purple wire | pr1\_edc\_latch0\_out | +--------------------------------------+--------------------------------------+ -| J21-54 left blue wire | .. raw:: html | -| | | -| |
| -| | | -| | pr1\_edc\_sync0\_out | -| | | -| | .. raw:: html | -| | | -| |
| +| J21-54 left blue wire | pr1\_edc\_sync0\_out | +--------------------------------------+--------------------------------------+ Example: See below pictures (J21 is the connector along the top right edge) @@ -1314,35 +1282,11 @@ for more details. +--------------------------------------+--------------------------------------+ | Wire on AM574x IDK | Signal | +======================================+======================================+ -| Center left black wire | .. raw:: html | -| | | -| |
| -| | | -| | timer15 | -| | | -| | .. raw:: html | -| | | -| |
| +| Center left black wire | timer15 | +--------------------------------------+--------------------------------------+ -| J21-13 black wire | .. raw:: html | -| | | -| |
| -| | | -| | pr2\_edc\_latch0\_out | -| | | -| | .. raw:: html | -| | | -| |
| +| J21-13 black wire | pr2\_edc\_latch0\_out | +--------------------------------------+--------------------------------------+ -| J21-17 white wire | .. raw:: html | -| | | -| |
| -| | | -| | pr1\_edc\_sync0\_out | -| | | -| | .. raw:: html | -| | | -| |
| +| J21-17 white wire | pr1\_edc\_sync0\_out | +--------------------------------------+--------------------------------------+ Example: See below pictures (J21 is the connector along the top right edge) diff --git a/source/linux/Industrial_Protocols/_RSTP.rst b/source/linux/Industrial_Protocols/_RSTP.rst index 44fc26335..645014e36 100644 --- a/source/linux/Industrial_Protocols/_RSTP.rst +++ b/source/linux/Industrial_Protocols/_RSTP.rst @@ -31,34 +31,10 @@ https://wiki.linuxfoundation.org/networking/bridge | -.. raw:: html - -
- -.. raw:: html - -
- .. Image:: /images/Cpsw_rstp_mstpd_topology_1.jpg -.. raw:: html - -
- 3 node ring demonstrating port blocking on low cost link -.. raw:: html - -
- -.. raw:: html - -
- -.. raw:: html - -
- | Please note that the topology was tested across CPSW only ports, diff --git a/source/linux/Industrial_Protocols/_RSTP_with_Switch_Firmware.rst b/source/linux/Industrial_Protocols/_RSTP_with_Switch_Firmware.rst index b57d019a8..c67927e5e 100644 --- a/source/linux/Industrial_Protocols/_RSTP_with_Switch_Firmware.rst +++ b/source/linux/Industrial_Protocols/_RSTP_with_Switch_Firmware.rst @@ -17,36 +17,9 @@ indicated in the FDB entry directly without involving the host. To set up a RSTP network with ICSS switch firmware, connect 3 AM571x-IDK as follows: -.. raw:: html - -
- -.. raw:: html - -
- .. Image:: /images/rstp_with_switch_firmware.jpg -.. raw:: html - -
- - -| Example: 3 node ring demonstrating RSTP with switch firmware - -.. raw:: html - -
- -.. raw:: html - -
- -.. raw:: html - -
- -| +Example: 3 node ring demonstrating RSTP with switch firmware .. note::