From 5de9b4f09d67392e62b4da27e938eec64c348fee Mon Sep 17 00:00:00 2001 From: Randolph Sapp Date: Wed, 4 Dec 2024 11:51:32 -0600 Subject: [PATCH] fix(images): use absolute path for resources in include Use absolute paths for the resources in include files since the relative paths will be different depending on where these files are included. Manually verified, but created with: find source/ -name '_*.rst' -exec sed -n 's;\(\.\./\)\+images/;/images/;' {} \; Signed-off-by: Randolph Sapp --- .../_66AK2G02_GP_EVM_Hardware_Setup.rst | 32 +++++------ .../_66AK2G02_ICE_EVM_Hardware_setup.rst | 26 ++++----- .../_AM572x_GP_EVM_Hardware_Setup.rst | 30 +++++----- .../_AM68_SK_Hardware_Setup.rst | 4 +- .../_AM69_SK_Hardware_Setup.rst | 4 +- .../_EVMK2E_Hardware_Setup.rst | 12 ++-- .../_EVMK2H_Hardware_Setup.rst | 20 +++---- .../_ICE_AM335x_Hardware_Setup.rst | 14 ++--- .../_ICE_AMIC110_EVM_Hardware_Setup.rst | 18 +++--- .../_OMAPL137_EVM_Hardware_Setup.rst | 2 +- .../_OMAPL138-C6748_LCDK_Hardware_Setup.rst | 6 +- .../_TMDSEVM6657L_EVM_Hardware_Setup.rst | 12 ++-- .../_TMDX654_EVM_Hardware_Setup.rst | 34 +++++------ .../_TMDXEVM6670L_EVM_Hardware_Setup.rst | 10 ++-- .../_TMDXEVM6678L_EVM_Hardware_Setup.rst | 14 ++--- .../_TMDXIDK5728_Hardware_Setup.rst | 16 +++--- .../_Boot_Monitor_Users_Guide.rst | 2 +- source/linux/Industrial_Protocols/_CCLINK.rst | 2 +- .../DSP_Software/DSP_Debug_and_Trace/_UIA.rst | 2 +- .../DSP_Software/_DSP_Optimized_Libraries.rst | 4 +- .../_Create_SD_Card_Linux.rst | 4 +- .../_Create_SD_Card_Windows.rst | 24 ++++---- .../_Audio_Benchmark_Starterkit.rst | 10 ++-- .../_Audio_Pre_Processing.rst | 8 +-- .../_Bare_Metal_Examples.rst | 36 ++++++------ .../_Big_Data_IPC_Examples.rst | 6 +- .../_Can_Eth_Gateway_Demo.rst | 12 ++-- .../_Gravity_Simulator_Demo.rst | 4 +- .../_Image_Processing_Demo.rst | 56 +++++++++---------- .../_Jailhouse_Hypervisor.rst | 2 +- .../_Performance_Audio.rst | 6 +- .../_Posix_SMP_Demo.rst | 8 +-- .../_RTOS_Examples.rst | 38 ++++++------- .../_RTOS_Template_App.rst | 18 +++--- .../_SimpleLink_WiFi_Demo.rst | 32 +++++------ ..._Porting_Guide_for_AM57xx_Speed_Grades.rst | 10 ++-- .../_Setup_CCS_for_EVM_and_PSDK_RTOS.rst | 34 +++++------ .../Host/Setup/_TI_RTOS_Tips_and_Tricks.rst | 18 +++--- ...ng_PDK_and_IPC_to_load_from_ARM_AM57xx.rst | 12 ++-- ...bugging_Tools_and_Techniques_on_AM57xx.rst | 10 ++-- .../_C66x_Reset_from_A15_Running_Linux.rst | 16 +++--- ...External_Input_Trigger_Interrupt_AM57x.rst | 10 ++-- .../Target/_Run_IPC_Examples_on_AM572x.rst | 8 +-- source/rtos/Overview/_Directory_Structure.rst | 4 +- .../Overview/_Examples_and_Demonstrations.rst | 2 +- .../rtos/Overview/_Getting_Started_Guide.rst | 6 +- source/rtos/Overview/_Software_Stack.rst | 2 +- .../_BOOT_AM57x.rst | 6 +- .../_BOOT_AM65x_J721E.rst | 6 +- .../_BOOT_C66x.rst | 6 +- .../_BOOT_K2G.rst | 4 +- .../_BOOT_OMAPL13x.rst | 4 +- .../_Diagnostics.rst | 14 ++--- .../_Uniflash.rst | 2 +- .../Device_Drivers/_EMAC.rst | 4 +- .../Device_Drivers/_HYPLNK.rst | 2 +- .../Device_Drivers/_IPCLLD.rst | 12 ++-- .../Device_Drivers/_MCASP.rst | 18 +++--- .../Device_Drivers/_SCICLIENT.rst | 4 +- .../Device_Drivers/_USB.rst | 44 +++++++-------- .../Device_Drivers/_VPS_Drivers.rst | 4 +- .../_Debug_with_ICSS_EMAC_LLD.rst | 12 ++-- .../_Develop_with_ICSS_EMAC_LLD.rst | 2 +- .../_Multi_Core_System_Analyzer.rst | 4 +- .../_XDS100_Emulator_Info.rst | 16 +++--- .../_XDS560_Emulator_Info.rst | 28 +++++----- 66 files changed, 426 insertions(+), 426 deletions(-) diff --git a/source/common/EVM_Hardware_Setup/_66AK2G02_GP_EVM_Hardware_Setup.rst b/source/common/EVM_Hardware_Setup/_66AK2G02_GP_EVM_Hardware_Setup.rst index a7c228152..1ffca7cb8 100644 --- a/source/common/EVM_Hardware_Setup/_66AK2G02_GP_EVM_Hardware_Setup.rst +++ b/source/common/EVM_Hardware_Setup/_66AK2G02_GP_EVM_Hardware_Setup.rst @@ -54,7 +54,7 @@ features of EVM are: .. rubric:: EVM Layout and Key Components :name: evm-layout-and-key-components -.. Image:: ../../../images/TI_K2GEVM.png +.. Image:: /images/TI_K2GEVM.png .. rubric:: JTAG debug probes (aka Emulators) supported :name: jtag-debug-probes-aka-emulators-supported @@ -83,13 +83,13 @@ mode. | **For EVM Out of box experience uses SD/MMC boot as shown in the image**: -.. Image:: ../../../images/Boot_switch_SDboot.jpg +.. Image:: /images/Boot_switch_SDboot.jpg | | **For Debugging over emulator use "No Boot/Sleep" Setting as shown below**: -.. Image:: ../../../images/Boot_Switch_NoBoot.jpg +.. Image:: /images/Boot_Switch_NoBoot.jpg :scale: 50% | @@ -172,7 +172,7 @@ connector to the USB mini-B interface near to the audio line in on the EVM, and the USB connector to your PC. This enables XDS-2xx emulation and is directly useable by CCS. -.. Image:: ../../../images/XDS200_connect.png +.. Image:: /images/XDS200_connect.png | @@ -258,7 +258,7 @@ this update. update the Keystone Device Support package by going into the Help->Check For Updates -.. Image:: ../../../images/Check_for_Updates.png +.. Image:: /images/Check_for_Updates.png **Step 2** Select Keystone2 device support package. Follow menu options to continue with the update @@ -267,7 +267,7 @@ to continue with the update and check that Keystone2 device support package v1.1.5 or later are installed as shown below -.. Image:: ../../../images/KeystoneII_device_support_package.png +.. Image:: /images/KeystoneII_device_support_package.png **Note:** The package can be downloaded separately from the link below and manually unzipped into CCSv6 installation. @@ -308,7 +308,7 @@ and manually unzipped into CCSv6 installation. Launch CCS and create new target configuration(File->New->Target Configuration file) as shown in the images below -.. Image:: ../../../images/CCS_target_configuration.png +.. Image:: /images/CCS_target_configuration.png Provide appropriate name to the configuration. Select Spectrum digital XDS200 emulator and target as K2G GPEVM. @@ -318,7 +318,7 @@ installed the CCSv6.1.3 package or for CCSv6.1.2 and earlier ensure that you have done the software update correctly as shown in the how to section below. -.. Image:: ../../../images/K2G_GPEVM_Target_configuration.jpg +.. Image:: /images/K2G_GPEVM_Target_configuration.jpg In advance settings, make sure that the gel files are populated correctly. The following GEL files and their corresponding cores are @@ -348,7 +348,7 @@ in the previous section ConfiguringTargetConfigFile_ **Step5**: Launch Target configuration you just created. -.. Image:: ../../../images/K2G_Launch_targetConfig.png +.. Image:: /images/K2G_Launch_targetConfig.png **Step6**:K2G can be a DSP or an ARM master boot device so connect to the C66x or the A15\_0. @@ -378,7 +378,7 @@ in the previous section ConfiguringTargetConfigFile_ Launch CCS and create new target configuration(File->New->Target Configuration file) as shown in the images below -.. Image:: ../../../images/CCS_target_configuration.png +.. Image:: /images/CCS_target_configuration.png Provide appropriate name to the configuration. Select Spectrum digital XDS200 emulator and target as 66AK2G02. @@ -388,7 +388,7 @@ installed the CCSv6.1.3 package or for CCSv6.1.2 and earlier ensure that you have done the software update correctly as shown in the how to section below. -.. Image:: ../../../images/K2G_GPEVM_Target_configuration_alternate.jpg +.. Image:: /images/K2G_GPEVM_Target_configuration_alternate.jpg In advance settings, make sure that the no gel files are populated. @@ -404,7 +404,7 @@ in the previous section ConfiguringTargetConfigFile_ **Step5**: Launch Target configuration you just created. -.. Image:: ../../../images/K2G_Launch_targetConfig.png +.. Image:: /images/K2G_Launch_targetConfig.png **Step6**:K2G will boot with ARM master boot from the SD card so connect to the A15\_0. There will be no output on the console when you @@ -479,7 +479,7 @@ machine. the interface section, select ‘Serial (UART)’ from the drop-down box on the left.Refer to the image provided below: -.. Image:: ../../../images/LMflashProg_Config.png +.. Image:: /images/LMflashProg_Config.png **Step 7** Select the BMC COM Port and set the ‘Baud Rate’ to 115200. @@ -491,7 +491,7 @@ the left.Refer to the image provided below: "Silicon Labs CP210x: USB to UART Bridge: Standard COM Port (COM##)" as shown below: -.. Image:: ../../../images/BMCUARTPort.png +.. Image:: /images/BMCUARTPort.png **Note:** BMC outputs boot logs to serial console when EVM is powered ON. Connect the ‘USB to SoC UART0’ port to standard serial console @@ -503,7 +503,7 @@ Support’ is unchecked. **Step 9** In the 'Program' tab, select the binary image file bmc\_evmKS2\_K2G.bin in the section 'Select.bin file'. -.. Image:: ../../../images/LMflashProg_program.png +.. Image:: /images/LMflashProg_program.png **Step 10** Leave all other options as default, and press the ‘Program’ button. @@ -548,7 +548,7 @@ Steps to update the XDS200 firmware on the EVM are archived on the article - Remove FB3 and connect a wire from R64.2 ‘rVCC\_VBUS\_XDS’ and R67.2 ‘VCC5V0\_DCDC’ as shown in the image below: -.. Image:: ../../../images/R64_to_R67_HWMod.png +.. Image:: /images/R64_to_R67_HWMod.png :scale: 70% .. rubric:: Update the EVM for improved USB performance diff --git a/source/common/EVM_Hardware_Setup/_66AK2G02_ICE_EVM_Hardware_setup.rst b/source/common/EVM_Hardware_Setup/_66AK2G02_ICE_EVM_Hardware_setup.rst index 8a23bc8e7..00e40226f 100644 --- a/source/common/EVM_Hardware_Setup/_66AK2G02_ICE_EVM_Hardware_setup.rst +++ b/source/common/EVM_Hardware_Setup/_66AK2G02_ICE_EVM_Hardware_setup.rst @@ -47,10 +47,10 @@ The key features of the EVM are: EVM Layout and Key Components ----------------------------------- -.. Image:: ../../../images/TI_K2G_ICE_EVM_TOP.png +.. Image:: /images/TI_K2G_ICE_EVM_TOP.png :scale: 50% -.. Image:: ../../../images/TI_K2G_ICE_EVM_BOTTOM.png +.. Image:: /images/TI_K2G_ICE_EVM_BOTTOM.png :scale: 50% Supported JTAG Debug Probes (Emulators) @@ -73,14 +73,14 @@ mode. **For the EVM Out-of-Box experience, use SD/MMC boot mode as shown in the image below**: -.. Image:: ../../../images/K2GICE_Boot_MODE.png +.. Image:: /images/K2GICE_Boot_MODE.png :scale: 50% | The table below lists all of the boot modes supported on the ICE EVM. -.. Image:: ../../../images/K2G_ICE_BOOTSW.png +.. Image:: /images/K2G_ICE_BOOTSW.png :scale: 50% Connecting an Emulator @@ -104,7 +104,7 @@ Users can connect to the target SoC via CCS by connecting the USB cable, supplie | -.. Image:: ../../../images/ICE_K2G_connect.png +.. Image:: /images/ICE_K2G_connect.png :scale: 50% | @@ -159,7 +159,7 @@ specific target files hence we recommend this update. required to update the Keystone Device Support package by going into the Help->Check For Updates -.. Image:: ../../../images/Check_for_Updates.png +.. Image:: /images/Check_for_Updates.png :scale: 50% 2. Select Keystone2 device support package. Follow menu options @@ -169,7 +169,7 @@ to continue with the update. and check that Keystone2 device support package v1.1.9 or later are installed as shown below. -.. Image:: ../../../images/KeystoneII_device_support_package.png +.. Image:: /images/KeystoneII_device_support_package.png :scale: 50% .. Note:: The package can be downloaded separately from the link below and manually unzipped into CCS installation. @@ -202,14 +202,14 @@ Connect without an SD Card Boot Image Launch CCS and create a new target configuration (File->New->Target Configuration file) as shown in the images below. -.. Image:: ../../../images/CCS_target_configuration.png +.. Image:: /images/CCS_target_configuration.png :scale: 50% Provide an appropriate name to the configuration. Select Spectrum Digital XDS100 emulator and target as K2G ICE EVM. .. Note:: If you don't find the K2GICE target make sure you have installed CCSv7.1 or higher. If using CCSv 7.0 or CCSv6.1.x and earlier, ensure that you have done the software update correctly as shown in the how to section below. -.. Image:: ../../../images/K2G_ICE_target_configuration.png +.. Image:: /images/K2G_ICE_target_configuration.png :scale: 50% In advanced settings, make sure that the GEL files are populated correctly. The following GEL files and their corresponding cores are provided below. @@ -235,7 +235,7 @@ the previous section "Configuring target configuration files." 5. Launch the newly created target configuration. -.. Image:: ../../../images/K2G_Launch_targetConfig.png +.. Image:: /images/K2G_Launch_targetConfig.png :scale: 50% 6. K2G can be a DSP or an ARM master boot device @@ -264,14 +264,14 @@ Connect with an SD Card Boot Image 1. Launch CCS and create a new target configuration (File->New->Target Configuration file) as shown in the images below. -.. Image:: ../../../images/CCS_target_configuration.png +.. Image:: /images/CCS_target_configuration.png :scale: 50% Provide an appropriate name to the configuration. Select Spectrum digital XDS100 emulator and target as 66AK2G02. .. Note:: If you don't find the K2GICE target make sure you have installed CCSv7.1 or higher. If using CCSv 7.0 or CCSv6.1.x and earlier, ensure that you have done the software update correctly as shown in the how to section below. -.. Image:: ../../../images/K2G_GPEVM_Target_configuration_alternate.jpg +.. Image:: /images/K2G_GPEVM_Target_configuration_alternate.jpg :scale: 50% In advanced settings, make sure that no GEL files are populated. @@ -288,7 +288,7 @@ section "Configuring target configuration files". 5. Launch the newly created target configuration. -.. Image:: ../../../images/K2G_Launch_targetConfig.png +.. Image:: /images/K2G_Launch_targetConfig.png :scale: 50% 6. K2G will boot with ARM master boot from the SD card so connect to the A15\_0. There will be no output on the console when you diff --git a/source/common/EVM_Hardware_Setup/_AM572x_GP_EVM_Hardware_Setup.rst b/source/common/EVM_Hardware_Setup/_AM572x_GP_EVM_Hardware_Setup.rst index 707a8a497..215c1c2a8 100644 --- a/source/common/EVM_Hardware_Setup/_AM572x_GP_EVM_Hardware_Setup.rst +++ b/source/common/EVM_Hardware_Setup/_AM572x_GP_EVM_Hardware_Setup.rst @@ -22,7 +22,7 @@ and dual ARM Cortex-M4 cores. .. rubric:: Contents of the kit :name: contents-of-the-kit -.. Image:: ../../../images/EVM_modules.png +.. Image:: /images/EVM_modules.png **Module:** @@ -44,7 +44,7 @@ and dual ARM Cortex-M4 cores. .. rubric:: EVM Layout and Key Components :name: evm-layout-and-key-components -.. Image:: ../../../images/AM572X_GP_EVM_Overview.png +.. Image:: /images/AM572X_GP_EVM_Overview.png .. rubric:: JTAG debug probes (aka Emulators) supported :name: jtag-debug-probes-aka-emulators-supported @@ -74,7 +74,7 @@ UART cable from the FTDI website: .. rubric:: Setting boot switches :name: setting-boot-switches -.. Image:: ../../../images/Boot_Switches.png +.. Image:: /images/Boot_Switches.png Other Boot Pin configurations: `GP EVM Boot Options `__ @@ -94,15 +94,15 @@ panel in order to get access to the JTAG pins. Refer to the image below for how to safely separate the processor module from the LCD panel. -+-------------------------------------------------------+-------------------------------------------------+ -| .. Image:: ../../../images/X15_PModule_disconnect.jpg | .. Image:: ../../../images/JMI_0065.jpg | -+-------------------------------------------------------+-------------------------------------------------+ ++-----------------------------------------------+---------------------------------+ +| .. Image:: /images/X15_PModule_disconnect.jpg | .. Image:: /images/JMI_0065.jpg | ++-----------------------------------------------+---------------------------------+ | | Image for how to connect the XDS200 Emulator to the 20 pin header is shown below: -.. Image:: ../../../images/GPEVM_XDS200.jpg +.. Image:: /images/GPEVM_XDS200.jpg :scale: 50% .. rubric:: Powering up the EVM @@ -111,7 +111,7 @@ from the LCD panel. .. rubric:: Power Supply specifications :name: power-supply-specifications -.. Image:: ../../../images/CUI_Isolated_Power_Supply.png +.. Image:: /images/CUI_Isolated_Power_Supply.png Please note that a power supply is NOT included with the AM572x Evaluation Module and needs to be purchased separately. A power supply @@ -155,7 +155,7 @@ scenario, the SBL component provides the same functionality .. rubric:: Connect Power to the EVM :name: connect-power-to-the-evm -.. Image:: ../../../images/Push_Power_EVM.png +.. Image:: /images/Push_Power_EVM.png .. rubric:: CCS Setup :name: ccs-setup @@ -181,7 +181,7 @@ GPEVM\_AM572x\_SiRevA target make sure you have installed the CCSv6 package with support for Sitara Processors and done the software update correctly from the Help Menu to get the latest Sitara CSP package. -.. Image:: ../../../images/GPEVM_Target_configuration.jpg +.. Image:: /images/GPEVM_Target_configuration.jpg | @@ -345,7 +345,7 @@ MULTICORE Initialization** enable the corresponding sub system clock. For example, enable ``DSP11SSClkEnable_API`` for the first DSP core. After running the clock enable option, you can connect to the core. -.. Image:: ../../../images/Multicore-Enable.jpg +.. Image:: /images/Multicore-Enable.jpg If you wish to run TI RTOS code on DSP, please also run the `Timer Suspend Control @@ -379,7 +379,7 @@ installed the CCSv6.1.1 package and done the software update correctly. | -.. Image:: ../../../images/COnfigure_targetConfigFiles_SDboot.png +.. Image:: /images/COnfigure_targetConfigFiles_SDboot.png .. rubric:: GEL file options :name: gel-file-options @@ -433,7 +433,7 @@ Due to this issue the SYS/BIOS developers will need to configure an additional CCS configuration check to connect the GPTimer suspend control signal to the DSP as shown in the image below: -.. Image:: ../../../images/GPtimer5_DSPConnect.png +.. Image:: /images/GPtimer5_DSPConnect.png .. rubric:: Other How-To Options :name: other-how-to-options @@ -443,7 +443,7 @@ control signal to the DSP as shown in the image below: Connecting FTDI cable to the 6 pin UART header for serial debug -.. Image:: ../../../images/GP_EVM_UART.jpg +.. Image:: /images/GP_EVM_UART.jpg :scale: 50% **Note:** Pin 1 corresponds to ground. @@ -459,7 +459,7 @@ Flow Control: Off For ethernet connectivity connect the ethernet cable to the top serial port which is port 0 on the GP EVM. -.. Image:: ../../../images/AM572x_GP_EVM_Ethernet_connect.jpg +.. Image:: /images/AM572x_GP_EVM_Ethernet_connect.jpg :scale: 50% You can connect the other end of the cable directly to the host or diff --git a/source/common/EVM_Hardware_Setup/_AM68_SK_Hardware_Setup.rst b/source/common/EVM_Hardware_Setup/_AM68_SK_Hardware_Setup.rst index 3c66fb9b1..49ad5e2ea 100644 --- a/source/common/EVM_Hardware_Setup/_AM68_SK_Hardware_Setup.rst +++ b/source/common/EVM_Hardware_Setup/_AM68_SK_Hardware_Setup.rst @@ -30,7 +30,7 @@ To run the demos on AM68 SK you will require, Connect the components to the EVM as shown in the image. -.. figure:: ../../../images/AM68_SK_Hardware_Setup/am68_sk.jpg +.. figure:: /images/AM68_SK_Hardware_Setup/am68_sk.jpg :scale: 30 :align: center @@ -38,7 +38,7 @@ Connect the components to the EVM as shown in the image. Set the boot pins to SD boot mode as shown in the following image. -.. figure:: ../../../images/AM68_SK_Hardware_Setup/am68_sk_bootpins.jpg +.. figure:: /images/AM68_SK_Hardware_Setup/am68_sk_bootpins.jpg :scale: 20 :align: center diff --git a/source/common/EVM_Hardware_Setup/_AM69_SK_Hardware_Setup.rst b/source/common/EVM_Hardware_Setup/_AM69_SK_Hardware_Setup.rst index 59851faef..2ff34b659 100644 --- a/source/common/EVM_Hardware_Setup/_AM69_SK_Hardware_Setup.rst +++ b/source/common/EVM_Hardware_Setup/_AM69_SK_Hardware_Setup.rst @@ -30,7 +30,7 @@ To run the demos on AM69 SK you will require, Connect the components to the EVM as shown in the image. -.. figure:: ../../../images/AM69_SK_Hardware_Setup/am69_sk.jpg +.. figure:: /images/AM69_SK_Hardware_Setup/am69_sk.jpg :scale: 30 :align: center @@ -38,7 +38,7 @@ Connect the components to the EVM as shown in the image. Set the boot pins to SD boot mode as shown in the following image. -.. figure:: ../../../images/AM69_SK_Hardware_Setup/am69_sk_bootpins.jpg +.. figure:: /images/AM69_SK_Hardware_Setup/am69_sk_bootpins.jpg :scale: 20 :align: center diff --git a/source/common/EVM_Hardware_Setup/_EVMK2E_Hardware_Setup.rst b/source/common/EVM_Hardware_Setup/_EVMK2E_Hardware_Setup.rst index c9b96d9eb..b3f44dd00 100644 --- a/source/common/EVM_Hardware_Setup/_EVMK2E_Hardware_Setup.rst +++ b/source/common/EVM_Hardware_Setup/_EVMK2E_Hardware_Setup.rst @@ -14,7 +14,7 @@ Using the Ethernet cable supplied, connect one end of the cable to the Ethernet Port 0 (At bottom one) on the EVM and the other end to your PC. The below picture shows which Ethernet Port is port 0: -.. image:: ../../../images/Evmk2e-image001.jpg +.. image:: /images/Evmk2e-image001.jpg Connect the JTAG interface ^^^^^^^^^^^^^^^^^^^^^^^^^^ @@ -37,7 +37,7 @@ K2E Set the boot mode switch SW1 MSB LSB SW1 - 1(OFF) 2(OFF) 3(ON) 4(OFF) -.. image:: ../../../images/Evmk2e-image002.jpg +.. image:: /images/Evmk2e-image002.jpg .. note:: Here a switch on “ON” position should be considered as “1”. @@ -50,7 +50,7 @@ K2E Set the boot mode switch SW1 MSB LSB SW1 - 1(ON) 2(ON) 3(ON) 4(ON) -.. image:: ../../../images/Evmk2e-image003.jpg +.. image:: /images/Evmk2e-image003.jpg Attach the serial port cable to the SoC UART port ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ @@ -179,7 +179,7 @@ You can check the version by: #. At BMC prompt type 'ver' (no quotes). #. Check BMC version -.. image:: ../../../images/Evmk2e-image005.jpg +.. image:: /images/Evmk2e-image005.jpg If an in-field update is needed, downloaded the latest version `here `__ @@ -204,7 +204,7 @@ Prepare EVM for in-field update `here `__) to update the firmware, as detailed in the steps below. -.. image:: ../../../images/Evmk2e-image006.jpg +.. image:: /images/Evmk2e-image006.jpg Perform in-field update """"""""""""""""""""""""""""""""""""""""""""""""" @@ -233,7 +233,7 @@ Perform in-field update #. If step 9 was done after power was applied, just type "ver" at BMC prompt. -.. image:: ../../../images/Evmk2e-image007.jpg +.. image:: /images/Evmk2e-image007.jpg UCD Power Management Update ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ diff --git a/source/common/EVM_Hardware_Setup/_EVMK2H_Hardware_Setup.rst b/source/common/EVM_Hardware_Setup/_EVMK2H_Hardware_Setup.rst index 5852c4671..cbe554542 100644 --- a/source/common/EVM_Hardware_Setup/_EVMK2H_Hardware_Setup.rst +++ b/source/common/EVM_Hardware_Setup/_EVMK2H_Hardware_Setup.rst @@ -69,7 +69,7 @@ to your PC. This picture shows which Ethernet Port is 0: -.. image:: ../../../images/K2H_ENET0.jpg +.. image:: /images/K2H_ENET0.jpg Connect the JTAG interface ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ @@ -193,7 +193,7 @@ application.** | -.. image:: ../../../images/Bmc_ver_screenshot.JPG +.. image:: /images/Bmc_ver_screenshot.JPG | @@ -239,7 +239,7 @@ with the following steps. #. Set ‘Transfer Size’ to 60, and make sure ‘Disable Auto Baud Support’ is unchecked.  - .. image:: ../../../images/LMflashProg_Config.png + .. image:: /images/LMflashProg_Config.png #. In the ‘Program’ tab, Browse to the location of the binary file containing the firmware update, and select it. @@ -252,7 +252,7 @@ with the following steps. #. If step 9 was done after power was applied, just type "ver" at BMC prompt. -.. image:: ../../../images/K2EVM.jpg +.. image:: /images/K2EVM.jpg DIP Switch and Bootmode Configurations ----------------------------------------- @@ -502,7 +502,7 @@ Connect to EVMK2H using CCS Launch CCS on your host machine. Select View Tab and select the "Target configuration" -.. image:: ../../../images/New_TargetConfig.png +.. image:: /images/New_TargetConfig.png | @@ -510,7 +510,7 @@ Create New Target configuration in CCS by selecting appropriate emulator. For Default on board emulator select "Texas instruments XDS2xx Debug Probe" and select the target device as 66AK2H12. -.. image:: ../../../images/K2H_TargetConfig.png +.. image:: /images/K2H_TargetConfig.png Go to the Advanced Tab where you will see all the cores on the SOC listed. In order to initialize the clocks and external DDR memory on the @@ -519,12 +519,12 @@ populate the Gel Select A15\_0 and then hit Browse and locate the GEL in the CCS installation under the following path: CCS\_INSTALL/ccs\_base/emulation/boards/xtcievmk2x/gel -.. image:: ../../../images/ARM_GEL.png +.. image:: /images/ARM_GEL.png DSP developers, can also select C66x\_0 and populate the DSP GEL file that is found in the same location. -.. image:: ../../../images/DSP_GEL.png +.. image:: /images/DSP_GEL.png Going back to the Basic Tab, Save the configuration. For additional sanity check, you can also test connection. @@ -537,9 +537,9 @@ Right click on the target configuration and Select "Launch Target configuration". Wait for CCS debug View to launch and display the eight C66x cores and 4 A15 cores. -.. image:: ../../../images/Launch_TargetConfig.png +.. image:: /images/Launch_TargetConfig.png -.. image:: ../../../images/Connect_A15.png +.. image:: /images/Connect_A15.png Start by connecting to A15\_0 and C66x\_0. when you connect to the cores, you will see the GEL script logs in the console window, which diff --git a/source/common/EVM_Hardware_Setup/_ICE_AM335x_Hardware_Setup.rst b/source/common/EVM_Hardware_Setup/_ICE_AM335x_Hardware_Setup.rst index f5c9a1e55..c767314b2 100644 --- a/source/common/EVM_Hardware_Setup/_ICE_AM335x_Hardware_Setup.rst +++ b/source/common/EVM_Hardware_Setup/_ICE_AM335x_Hardware_Setup.rst @@ -22,7 +22,7 @@ as TI’s Code Composer Studio by just using the supplied USB cable. EVM Layout and Key Components ------------------------------ -.. Image:: ../../../images/ICE_V2_marked.png +.. Image:: /images/ICE_V2_marked.png :scale: 50% Quick Start Guide @@ -36,7 +36,7 @@ shown above. 2. Connect the power cable to the power jack on the board and plug it into an AC power source. -.. Image:: ../../../images/ICE335924V.png +.. Image:: /images/ICE335924V.png :scale: 50% Once powered on, the POWER ON LED (D16) and Industrial Output LEDs @@ -48,7 +48,7 @@ Once powered on, the POWER ON LED (D16) and Industrial Output LEDs 3. Connect the microUSB cable to the USB JTAG/Console port on the ICE board and connect to the USB on the host. Connect an Ethernet cable to ETH0 if network connectivity is required. -.. Image:: ../../../images/ICE3359USB.png +.. Image:: /images/ICE3359USB.png :scale: 50% .. Note:: The serial port will not show up on the host PC until the board is powered on. @@ -59,10 +59,10 @@ software baud rate to 115200 to view the log messages. Connecting to the target using the on-board emulator is discussed in the section below. -.. Image:: ../../../images/Serial_connect.jpg +.. Image:: /images/Serial_connect.jpg :scale: 50% -.. Image:: ../../../images/Baudrate.jpg +.. Image:: /images/Baudrate.jpg :scale: 50% Boot Configuration @@ -90,14 +90,14 @@ Instruments XDS100v2 USB Debug Probe and the ICE\_AM3359 as shown below. .. Note:: If the ICE\_AM3359 target is not listed, make sure the latest Sitara Device Support package is installed by going to Help->Check for Updates. -.. Image:: ../../../images/ICE3359TargetConfig.png +.. Image:: /images/ICE3359TargetConfig.png :scale: 50% 4. Click Save to save the target configuration. Then press Test Connection to test the connection. If successful, a message should be seen similar to the one below. -.. Image:: ../../../images/ICE3359Test.png +.. Image:: /images/ICE3359Test.png :scale: 50% 5. Launch the target configuration and connect diff --git a/source/common/EVM_Hardware_Setup/_ICE_AMIC110_EVM_Hardware_Setup.rst b/source/common/EVM_Hardware_Setup/_ICE_AMIC110_EVM_Hardware_Setup.rst index fe07b7c36..c8af2275e 100644 --- a/source/common/EVM_Hardware_Setup/_ICE_AMIC110_EVM_Hardware_Setup.rst +++ b/source/common/EVM_Hardware_Setup/_ICE_AMIC110_EVM_Hardware_Setup.rst @@ -12,10 +12,10 @@ the Sitara AMIC110 ARM Cortex-A8 processor SoC from Texas Instruments.™ EVM Layout and Key Components ------------------------------ -.. Image:: ../../../images/ICEAMIC110TopLayout.PNG +.. Image:: /images/ICEAMIC110TopLayout.PNG :scale: 50% -.. Image:: ../../../images/ICEAMIC110BottomLayout.PNG +.. Image:: /images/ICEAMIC110BottomLayout.PNG :scale: 50% Quick Start Guide @@ -32,25 +32,25 @@ and connectors shown above. or the XDS200 emulators may be used for this purpose and can be purchased from the TI store: `XDS200 `__ and `XDS110 `__. -.. Image:: ../../../images/ICEAMIC110JTAG.PNG +.. Image:: /images/ICEAMIC110JTAG.PNG :scale: 50% 3. Connect the pin header connector of the included TTL-232R-3V3 serial cable to J3 on the ICE board. Ensure that pin 1 of the serial cable (black wire, marked with a triangle) is connected to pin 1 of J3, which is indicated by a dot on the silk screen. Connect the USB connector of the serial cable to a PC host port. The datasheet for this cable can found at http://www.ftdichip.com/Support/Documents/DataSheets/Cables/DS_TTL-232R_CABLES.pdf -.. Image:: ../../../images/ICEAMIC110TTL.PNG +.. Image:: /images/ICEAMIC110TTL.PNG :scale: 50% 4. Connect a CAT5 Ethernet cable from a PC running TwinCAT software to ECAT IN/PHY1 (J6) of the ICE board. If you have multiple ICE boards in a chain, please connect another CAT5 Ethernet cable from ECAT OUT/PHY2 (J7) to PHY1 of the next ICE board. PHY2 of the last ICE board in the chain is left open. -.. Image:: ../../../images/ICEAMIC110ETHERNET.PNG +.. Image:: /images/ICEAMIC110ETHERNET.PNG :scale: 50% 5. Connect the recommended power supply (CUI Inc. SMI18-5-V-P5, procurable at: http://www.digikey.com/product-detail/en/cui-inc/SMI18-5-V-P5/102-3571-ND/5415042) or equivalent (Output voltage/current: 5 Volts DC +/- 10% @ 1.2 Amps; Output connector: 2.1-mm ID, 5.5-mm OD barrel plug, center positive) power supply to J8 on the ICE board. Apply power to the power supply to power up the ICE board. Do not hot plug the 5-V supply into the ICE board. -.. Image:: ../../../images/ICEAMIC1105V.PNG +.. Image:: /images/ICEAMIC1105V.PNG :scale: 50% Once the ICE board is powered on, the ON LED (D15) and LED4 (D19) will @@ -59,7 +59,7 @@ turn on. 6. The AMIC110 ICE can now be connected to from the host machine via UART. The serial port should be setup as shown below. -.. Image:: ../../../images/Baudrate.jpg +.. Image:: /images/Baudrate.jpg :scale: 50% Boot Configuration @@ -83,13 +83,13 @@ the appropriate emulator and the ICE\_AMIC110 as the target as shown below. .. Note:: If the ICE\_AMIC110 target is not listed, make sure the Sitara Device Support package v1.3.6 or greater is installed. -.. Image:: ../../../images/ICEAMIC110TargetConfig.PNG +.. Image:: /images/ICEAMIC110TargetConfig.PNG :scale: 50% 4. Click Save to save the target configuration. Then press Test Connection to test the connection. If successful, a message should be seen similar to the one below. -.. Image:: ../../../images/ICEAMIC110Test.PNG +.. Image:: /images/ICEAMIC110Test.PNG :scale: 50% 5. Launch the target configuration and diff --git a/source/common/EVM_Hardware_Setup/_OMAPL137_EVM_Hardware_Setup.rst b/source/common/EVM_Hardware_Setup/_OMAPL137_EVM_Hardware_Setup.rst index d204cc929..9e6f5448d 100644 --- a/source/common/EVM_Hardware_Setup/_OMAPL137_EVM_Hardware_Setup.rst +++ b/source/common/EVM_Hardware_Setup/_OMAPL137_EVM_Hardware_Setup.rst @@ -74,7 +74,7 @@ Target Configuration - Specify a file name or use default. - Select "Spectrum Digital XDS510USB Emulator" as Connection. **If using CCS 9.0 or later, you will need an external emulator as noted above.** -.. Image:: ../images/OMAPL137_targetConfig.png +.. Image:: /images/OMAPL137_targetConfig.png - Check "OMAPL137" or "C6747" as Device and save.  diff --git a/source/common/EVM_Hardware_Setup/_OMAPL138-C6748_LCDK_Hardware_Setup.rst b/source/common/EVM_Hardware_Setup/_OMAPL138-C6748_LCDK_Hardware_Setup.rst index 6d1132fa8..9b28cdeb7 100644 --- a/source/common/EVM_Hardware_Setup/_OMAPL138-C6748_LCDK_Hardware_Setup.rst +++ b/source/common/EVM_Hardware_Setup/_OMAPL138-C6748_LCDK_Hardware_Setup.rst @@ -79,7 +79,7 @@ Creating a Target Configuration File - For Board or Device, select LCDKC6748 or LCDKOMAPL138 as shown in the following image, and click Save. -.. Image:: ../images/lcdk_targetConfig.png +.. Image:: /images/lcdk_targetConfig.png | @@ -87,12 +87,12 @@ Creating a Target Configuration File **OMAP-L138 LCDK GEL File:** -.. Image:: ../images/lcdk_omapl138_gel.png +.. Image:: /images/lcdk_omapl138_gel.png :scale: 100% **C6748 LCDK GEL File:** -.. Image:: ../images/lcdk_c6748_gel.png +.. Image:: /images/lcdk_c6748_gel.png :scale: 100% diff --git a/source/common/EVM_Hardware_Setup/_TMDSEVM6657L_EVM_Hardware_Setup.rst b/source/common/EVM_Hardware_Setup/_TMDSEVM6657L_EVM_Hardware_Setup.rst index 28f7550d6..bf46f7240 100644 --- a/source/common/EVM_Hardware_Setup/_TMDSEVM6657L_EVM_Hardware_Setup.rst +++ b/source/common/EVM_Hardware_Setup/_TMDSEVM6657L_EVM_Hardware_Setup.rst @@ -16,7 +16,7 @@ Hardware Setup Overview The picture below shows the TMDXEVM6657L EVM and the locations of relevant switches and connectors. -.. image:: ../images/TMDSEVM6657L-image.jpg +.. image:: /images/TMDSEVM6657L-image.jpg Hardware Setup Steps @@ -40,7 +40,7 @@ CCS. If you are using a different JTAG, connect it now. The Endian mode should be set to Little Endian. SW3 also contains the boot device settings. -.. image:: ../images/TMD6657LSW3.png +.. image:: /images/TMD6657LSW3.png :scale: 60% | @@ -49,7 +49,7 @@ boot device settings. The boot mode settings below enable NOR boot by loading the boot loader from EEPROM address 0x51. -.. image:: ../images/TMD6657LSW3-6.png +.. image:: /images/TMD6657LSW3-6.png :scale: 60% **5. Set User Switch for the demo application** @@ -60,7 +60,7 @@ controlled by setting dip switch 2 of SW9. | User Switch 2 ON : DHCP | User Switch 2 OFF: Static IP -.. image:: ../images/TMD6678LSW9.png +.. image:: /images/TMD6678LSW9.png :scale: 60% **6. Attach the serial port cable** @@ -70,12 +70,12 @@ this on the platforms are set to use the USB by default. We recommend changing them to use the DB-9 as there are no known issues with this approach. -.. image:: ../images/TMDXEVM6657L-shunts.jpg +.. image:: /images/TMDXEVM6657L-shunts.jpg :scale: 70% | -.. image:: ../images/TMDXEVM6657LCOMSEL.png +.. image:: /images/TMDXEVM6657LCOMSEL.png :scale: 70% COM\_SEL1: Select UART over 3-Pin Header diff --git a/source/common/EVM_Hardware_Setup/_TMDX654_EVM_Hardware_Setup.rst b/source/common/EVM_Hardware_Setup/_TMDX654_EVM_Hardware_Setup.rst index a731872d7..4793d2cdf 100644 --- a/source/common/EVM_Hardware_Setup/_TMDX654_EVM_Hardware_Setup.rst +++ b/source/common/EVM_Hardware_Setup/_TMDX654_EVM_Hardware_Setup.rst @@ -7,7 +7,7 @@ EVM Layout and Key Components Refer to the image below which highlights the key components available on the AM65x EVM. -.. image:: ../../../images/TMDX654_EVM_Hardware_Setup/AM65x_IDK_Diagram.png +.. image:: /images/TMDX654_EVM_Hardware_Setup/AM65x_IDK_Diagram.png The complete feature set for the AM65x EVM is described in AM65x EVM User Manual. This section only provides description @@ -25,20 +25,20 @@ For Lauterbach or emulators with MIPI60 or TI14 pin connector, an adapter must b .. Warning:: Do not connect an XDS560 emulator to the J16 application board connector. This may damage the EVM and the emulator pod. -.. image:: ../../../images/TMDX654_EVM_Hardware_Setup/AM65x_JTAG.png +.. image:: /images/TMDX654_EVM_Hardware_Setup/AM65x_JTAG.png :width: 600px | If you are using an external emulator pod, you must select which connector sources the clock. The AM65x EVM can support the MIPI60 or cTI20 connector. The JTAG select jumper must be set correctly to specify the clock source as either the MIPI60 or the cTI20 connector. -.. image:: ../../../images/TMDX654_EVM_Hardware_Setup/AM65x_Clock_Select.png +.. image:: /images/TMDX654_EVM_Hardware_Setup/AM65x_Clock_Select.png BOOTMODE Switches ^^^^^^^^^^^^^^^^^^ -.. image:: ../../../images/TMDX654_EVM_Hardware_Setup/AM65x_Boot_Modes.png +.. image:: /images/TMDX654_EVM_Hardware_Setup/AM65x_Boot_Modes.png **MCU BOOTMODE shown:** @@ -63,7 +63,7 @@ BOOTMODE[18:0] = 000000000 0000000000 MCUBOOTMODE[8:0]= 000000011 (SLEEP BOOT) BOOTMODE[18:0] = 000000100 0000000110 MCUBOOTMODE[8:0]= 000000011 (SD BOOT) -.. image:: ../../../images/TMDX654_EVM_Hardware_Setup/AM65x_Boot_Switches.png +.. image:: /images/TMDX654_EVM_Hardware_Setup/AM65x_Boot_Switches.png For full details on supported boot modes, please refer to the table below. @@ -136,7 +136,7 @@ UART Connection * Third COM port – Wakeup UART * Fourth COM port – SoC MAIN UART1 -.. image:: ../../../images/TMDX654_EVM_Hardware_Setup/AM65x_Tera_Term.png +.. image:: /images/TMDX654_EVM_Hardware_Setup/AM65x_Tera_Term.png 3. Open a serial console (e.g Tera Term) on host PC, connect to COM port on which EVM UART port is connected and set the following configuration. @@ -199,7 +199,7 @@ http://processors.wiki.ti.com/index.php/Download_CCS Ensure that at least "Sitara AMx Processors" is selected: - .. image:: ../../../images/TMDX654_EVM_Hardware_Setup/AM65x_CCS_Install.png + .. image:: /images/TMDX654_EVM_Hardware_Setup/AM65x_CCS_Install.png @@ -209,12 +209,12 @@ Install the latest Emulation Package and Device Support Package 1. In CCS, navigate to Help -> Check for Updates and select "Sitara device support" and "TI Emulators" and click Next. - .. image:: ../../../images/TMDX654_EVM_Hardware_Setup/CCS_Check_for_Updates.PNG + .. image:: /images/TMDX654_EVM_Hardware_Setup/CCS_Check_for_Updates.PNG 2. Click "Next" again, select "I accept the terms of the license agreements" and click Finish to begin the installation. - .. image:: ../../../images/TMDX654_EVM_Hardware_Setup/CCS_Updating_Software.png + .. image:: /images/TMDX654_EVM_Hardware_Setup/CCS_Updating_Software.png 3. You may be prompted to restart CCS for the updates to take effect. Click "Restart Now" when prompted to complete the installation. @@ -249,12 +249,12 @@ Creating the Target Configuration 3. Populate the Target Configuration File name, set the location, and click Finish. - .. image:: ../../../images/TMDX654_EVM_Hardware_Setup/AM65x_Target_Configuration.png + .. image:: /images/TMDX654_EVM_Hardware_Setup/AM65x_Target_Configuration.png 4. Select "Texas Instruments XDS110 USB Debug Probe" for the Connection and "GPEVM_AM65x" for the Board or Device. - .. image:: ../../../images/TMDX654_EVM_Hardware_Setup/AM65x_Target_Configuration2.png + .. image:: /images/TMDX654_EVM_Hardware_Setup/AM65x_Target_Configuration2.png .. Note:: The GEL files are automatically populated in the Target Configuration when selecting an EVM instead of an SOC. The SOC option is generally used for custom board bring up or secondary boot debugging. @@ -262,7 +262,7 @@ Creating the Target Configuration 5. Navigate to the "Advanced" tab to ensure the GEL files are populated in the "initialization script" field for the various cores. - .. image:: ../../../images/TMDX654_EVM_Hardware_Setup/AM65x_Target_Configuration3.png + .. image:: /images/TMDX654_EVM_Hardware_Setup/AM65x_Target_Configuration3.png The initialization script for the Cortex M3 will setup the MCU domain and Main domain PLL clocks, PSC registers, and bring the R5 and Cortex A53 cores out of reset. @@ -270,7 +270,7 @@ The initialization script for the Cortex A53 and Cortex R5 will perform a simila 6. Save the Target Configuration. - .. image:: ../../../images/TMDX654_EVM_Hardware_Setup/AM65x_Target_Configuration4.png + .. image:: /images/TMDX654_EVM_Hardware_Setup/AM65x_Target_Configuration4.png Connecting to the Cores on AM65x @@ -284,7 +284,7 @@ In CCS Editor View, go to View -> Target Configuration, and right click on the c .. Note:: When connecting to the M3 core for the first time, you may be prompted with a firmware update. Please click "Update" to update the emulator firmware. -.. image:: ../../../images/TMDX654_EVM_Hardware_Setup/AM65x_FW_Update.png +.. image:: /images/TMDX654_EVM_Hardware_Setup/AM65x_FW_Update.png On AM65x DMSC_Cortex_M3 is the boot master and is the first core that wakes up and starts the R5F ROM. Upon launching the target configuration, **connect to DMSC_Cortex_M3 first**, as this will automatically perform the PSC and PLL initialization. The following GEL output will appear in the CCS Console:: @@ -538,7 +538,7 @@ The following files are provided as part for the SciClient tools: AM65x Advanced Debug Script Flow -.. image:: ../../../images/TMDX654_EVM_Hardware_Setup/AM65x_Advanced_Flow.png +.. image:: /images/TMDX654_EVM_Hardware_Setup/AM65x_Advanced_Flow.png | @@ -588,11 +588,11 @@ At the end of the setup, the R5F and A53 are in a clean state to load code and d In the debug view after completing the basic CCS setup, Click on Debug Configurations from the button as show below: -.. image:: ../../../images/TMDX654_EVM_Hardware_Setup/CCS_Debug_Config.png +.. image:: /images/TMDX654_EVM_Hardware_Setup/CCS_Debug_Config.png Select the CCXML file from the left-hand side and populate the path to the launch_am65xx.js file in the "Initialization Script" free form field and click on "Apply". -.. image:: ../../../images/TMDX654_EVM_Hardware_Setup/CCS_Debug_XML.png +.. image:: /images/TMDX654_EVM_Hardware_Setup/CCS_Debug_XML.png Once you Launch the CCXML file, the java script will automatically run and connect to R5F. diff --git a/source/common/EVM_Hardware_Setup/_TMDXEVM6670L_EVM_Hardware_Setup.rst b/source/common/EVM_Hardware_Setup/_TMDXEVM6670L_EVM_Hardware_Setup.rst index 1a8fb81b8..2ce68cf2e 100644 --- a/source/common/EVM_Hardware_Setup/_TMDXEVM6670L_EVM_Hardware_Setup.rst +++ b/source/common/EVM_Hardware_Setup/_TMDXEVM6670L_EVM_Hardware_Setup.rst @@ -15,7 +15,7 @@ Hardware Setup Overview The picture below shows the TMDXEVM6670L EVM and the locations of relevant switches and connectors. -.. image:: ../images/TMD6670L.jpg +.. image:: /images/TMD6670L.jpg Hardware Setup Steps @@ -35,21 +35,21 @@ Hardware Setup Steps | **3. Verify Endian mode in the SW3 settings** | The Endian mode should be set to Little Endian. SW3 also contains the boot device settings. -.. image:: ../images/TMD6678LSW3.png +.. image:: /images/TMD6678LSW3.png :scale: 40% | | **4. Verify boot mode in the SW3 - SW6 settings** | The boot mode settings below enable NOR boot by loading the boot loader from EEPROM address 0x51. -.. image:: ../images/TMD6678LSW3-6.png +.. image:: /images/TMD6678LSW3-6.png :scale: 40% | | **5. Set User Switch 2 for the demo application** | The application needs an IP address. It can use either a static IP address (pre-configured) or it can request one using DHCP. This is controlled by setting User Switch 2 to ON for DHCP and OFF for Static. See SW9. -.. image:: ../images/TMD6670LSW9.png +.. image:: /images/TMD6670LSW9.png | | **6. Attach the serial port cable** @@ -57,7 +57,7 @@ Hardware Setup Steps | To change the shunts refer to the picture below. -.. image:: ../images/TMD6670LShunts.jpg +.. image:: /images/TMD6670LShunts.jpg .. note:: If the USB serial port output does not work, ensure that the cable is connected directly to a USB port on the PC/laptop rather than going through an extender or USB hub. diff --git a/source/common/EVM_Hardware_Setup/_TMDXEVM6678L_EVM_Hardware_Setup.rst b/source/common/EVM_Hardware_Setup/_TMDXEVM6678L_EVM_Hardware_Setup.rst index 2e4c84bd1..14cb89922 100644 --- a/source/common/EVM_Hardware_Setup/_TMDXEVM6678L_EVM_Hardware_Setup.rst +++ b/source/common/EVM_Hardware_Setup/_TMDXEVM6678L_EVM_Hardware_Setup.rst @@ -15,13 +15,13 @@ Hardware Setup Overview The picture below shows the TMDXEVM6678L EVM and the locations of relevant switches and connectors. -.. image:: ../images/TMDXEVM6678L-image.jpg +.. image:: /images/TMDXEVM6678L-image.jpg :scale: 60 % | .. note:: Please refer to the following picture for the alpha/beta Lite EVM boards. -.. image:: ../images/TMD6678L.jpg +.. image:: /images/TMD6678L.jpg Hardware Setup Steps @@ -54,7 +54,7 @@ boot device settings. | -.. image:: ../images/TMD6678LSW3.png +.. image:: /images/TMD6678LSW3.png :scale: 40 % @@ -64,7 +64,7 @@ boot device settings. The boot mode settings below enable NOR boot by loading the boot loader from EEPROM address 0x51. -.. image:: ../images/TMD6678LSW3-6.png +.. image:: /images/TMD6678LSW3-6.png :scale: 40 % | @@ -77,7 +77,7 @@ controlled by setting dip switch 2 of SW9. | User Switch 2 ON : DHCP | User Switch 2 OFF: Static IP -.. image:: ../images/TMD6678LSW9.png +.. image:: /images/TMD6678LSW9.png :scale: 50 % | @@ -89,12 +89,12 @@ this on the platforms are set to use the USB by default. We recommend changing them to use the DB-9 as there are no known issues with this approach. -.. image:: ../images/TMDXEVM6678L-shunts.jpg +.. image:: /images/TMDXEVM6678L-shunts.jpg .. note:: If the USB serial port output does not work, ensure that the cable is connected directly to a USB port on the PC/laptop rather than going through an extender or USB hub. .. note:: For the shunts on the alpha/beta Lite EVM, please refer to the picture below for the setting -.. image:: ../images/TMD6678LShunts.jpg +.. image:: /images/TMD6678LShunts.jpg | | **7. Connect the power cable** diff --git a/source/common/EVM_Hardware_Setup/_TMDXIDK5728_Hardware_Setup.rst b/source/common/EVM_Hardware_Setup/_TMDXIDK5728_Hardware_Setup.rst index 4dff37e74..6691e66b2 100644 --- a/source/common/EVM_Hardware_Setup/_TMDXIDK5728_Hardware_Setup.rst +++ b/source/common/EVM_Hardware_Setup/_TMDXIDK5728_Hardware_Setup.rst @@ -22,7 +22,7 @@ by just using the supplied USB cable. .. rubric:: EVM Layout and key components :name: evm-layout-and-key-components -.. Image:: ../../../images/AM572x_IDK_layout.png +.. Image:: /images/AM572x_IDK_layout.png - PRU1ETH0 and PRU2ETH0 are not enabled by default @@ -56,7 +56,7 @@ designed to help you through the initial setup of the EVM. | | |
| | | -| .. Image:: ../../../images/IDK_uSD.png | +| .. Image:: /images/IDK_uSD.png | +--------------------------------------------------------------------------+ +--------------------------------------------------------------------------+ @@ -79,7 +79,7 @@ designed to help you through the initial setup of the EVM. | | |
| | | -| .. Image:: ../../../images/Power_cord_connect.png | +| .. Image:: /images/Power_cord_connect.png | | | +--------------------------------------------------------------------------+ @@ -113,7 +113,7 @@ VDE, CCC, PSE, etc. | | |
| | | -| .. Image:: ../../../images/JTAGUSB_UART.png | +| .. Image:: /images/JTAGUSB_UART.png | +--------------------------------------------------------------------------+ **Note:** The serial port will not show up on the host PC until you @@ -138,7 +138,7 @@ power on the EVM. | | |
| | | -| .. Image:: ../../../images/PowerON.png | +| .. Image:: /images/PowerON.png | +--------------------------------------------------------------------------+ After, you power on the EVM the Status, Industrial LED2, Industrial LED3 @@ -167,7 +167,7 @@ corresponding to FTDI UARTtoUSB will be turned on. | class="thumbinner" | class="thumbinner" | | style="width:402px;"> | style="width:302px;"> | | | | -| .. Image:: ../../../images/Serial_connect.jpg | .. Image:: ../../../images/Baudrate.jpg | +| .. Image:: /images/Serial_connect.jpg | .. Image:: /images/Baudrate.jpg | | | | | .. raw:: html | .. raw:: html | | | | @@ -213,7 +213,7 @@ the Sitara Device support version 1.3.x package correctly
-.. Image:: ../../../images/Target_configuration.png +.. Image:: /images/Target_configuration.png | | **Step4:** In advance settings, Make sure that the corresponding IDK @@ -297,7 +297,7 @@ connect to the core. | -.. Image:: ../../../images/Multicore-Enable.jpg +.. Image:: /images/Multicore-Enable.jpg .. rubric:: Related Links :name: related-links diff --git a/source/linux/Foundational_Components/Boot_Monitor/_Boot_Monitor_Users_Guide.rst b/source/linux/Foundational_Components/Boot_Monitor/_Boot_Monitor_Users_Guide.rst index 6df3a9a7a..2cae740f1 100644 --- a/source/linux/Foundational_Components/Boot_Monitor/_Boot_Monitor_Users_Guide.rst +++ b/source/linux/Foundational_Components/Boot_Monitor/_Boot_Monitor_Users_Guide.rst @@ -19,7 +19,7 @@ ARM cortex A15 requires certain functions to be executed in the PL1 privilege level. Boot monitor code provides this service. A high level architecture of the boot monitor software is shown below -.. image:: ../images/Boot-kernel-arch.jpg +.. image:: /images/Boot-kernel-arch.jpg :scale: 80% Boot monitor code is built as a standalone image and is loaded into diff --git a/source/linux/Industrial_Protocols/_CCLINK.rst b/source/linux/Industrial_Protocols/_CCLINK.rst index e9375b021..aaa82cbb0 100644 --- a/source/linux/Industrial_Protocols/_CCLINK.rst +++ b/source/linux/Industrial_Protocols/_CCLINK.rst @@ -155,7 +155,7 @@ sample application: “Master\_sample The figure below shows the sample output from the console of the master station. -.. Image:: ../images/Cclink_master_screeshot_linux.png +.. Image:: /images/Cclink_master_screeshot_linux.png | diff --git a/source/rtos/DSP_Software/DSP_Debug_and_Trace/_UIA.rst b/source/rtos/DSP_Software/DSP_Debug_and_Trace/_UIA.rst index 29ff454aa..79b2d8ce1 100644 --- a/source/rtos/DSP_Software/DSP_Debug_and_Trace/_UIA.rst +++ b/source/rtos/DSP_Software/DSP_Debug_and_Trace/_UIA.rst @@ -13,7 +13,7 @@ visualization in Code Composer Studio. In a multi core system, data from all cores are correlated to a single timeline. -.. Image:: ../images/SA.png +.. Image:: /images/SA.png Unified Instrumentation Architecture (UIA) ------------------------------------------ diff --git a/source/rtos/DSP_Software/_DSP_Optimized_Libraries.rst b/source/rtos/DSP_Software/_DSP_Optimized_Libraries.rst index 71c71d7aa..ea79ce16b 100644 --- a/source/rtos/DSP_Software/_DSP_Optimized_Libraries.rst +++ b/source/rtos/DSP_Software/_DSP_Optimized_Libraries.rst @@ -128,7 +128,7 @@ Using Libraries in Processor-SDK RTOS The following diagram illustrates the software stack of various components including libraries provided with the Processor-SDK RTOS. -.. Image:: ../images/Lib_sw_stack_rtos.jpg +.. Image:: /images/Lib_sw_stack_rtos.jpg Using Libraries in Processor-SDK Linux -------------------------------------- @@ -139,7 +139,7 @@ libraries on the host (ARM) side, and the actual computation may be executed on ARM or DSP according to configuration and problem size. This is explained in detail in each library's documentation page. -.. Image:: ../images/Linalg.jpg +.. Image:: /images/Linalg.jpg Delivery Format =============== diff --git a/source/rtos/Development_Tools/_Create_SD_Card_Linux.rst b/source/rtos/Development_Tools/_Create_SD_Card_Linux.rst index e942edb02..60b79bd00 100644 --- a/source/rtos/Development_Tools/_Create_SD_Card_Linux.rst +++ b/source/rtos/Development_Tools/_Create_SD_Card_Linux.rst @@ -155,9 +155,9 @@ installer, you will see - AM335x/AM437x: -.. Image:: ../images/AM437x-SD-Card-Example.png +.. Image:: /images/AM437x-SD-Card-Example.png - AM57x: -.. Image:: ../images/AM57x-SD-Card-Example.png +.. Image:: /images/AM57x-SD-Card-Example.png diff --git a/source/rtos/Development_Tools/_Create_SD_Card_Windows.rst b/source/rtos/Development_Tools/_Create_SD_Card_Windows.rst index c29bb7d4f..bc4b9362b 100644 --- a/source/rtos/Development_Tools/_Create_SD_Card_Windows.rst +++ b/source/rtos/Development_Tools/_Create_SD_Card_Windows.rst @@ -79,27 +79,27 @@ Use the software for writing an image to disk to write the .img file to the SD c - Launch the disk writer software. In the screenshots below, we are using *Win32 Disk Imager*. -.. Image:: ../images/Win32_Disk_Imager_open.png +.. Image:: /images/Win32_Disk_Imager_open.png - Choose the image file for the SDK that you want to write. -.. Image:: ../images/Win32_disk_imager_select_a_disk_image.png +.. Image:: /images/Win32_disk_imager_select_a_disk_image.png - Choose the SD card as the "Device". - Write the image to the SD card by click "Write". You will likely get the below confirmation box. This command will overwrite whatever disk you point it to, please make sure and choose the correct disk. -.. Image:: ../images/Win32_disk_imager_Confirm_overwrite.png +.. Image:: /images/Win32_disk_imager_Confirm_overwrite.png - You should see the following status bar as the image is being written to the disk: -.. Image:: ../images/Win32_Disk_Imager_writing_to_disk.png +.. Image:: /images/Win32_Disk_Imager_writing_to_disk.png - When the write is complete, you will get the following notification: -.. Image:: ../images/Win32_Disk_Imager_Complete.png +.. Image:: /images/Win32_Disk_Imager_Complete.png - You can now close the image writing program by click "Exit". @@ -124,13 +124,13 @@ You can follow the instructions provide below: 3. Run the SD Card Formatter 4.0 for SD/SDHC/SDXC Portable executable. The executable should automatically detect the SD card plugged via reader as a new 'removable disk' and populate the drive corresponding to the removable disk. Else you will need to manually point it to the new disk. -.. Image:: ../images/SDFormatter_screenshot.png +.. Image:: /images/SDFormatter_screenshot.png 4. Choose default settings (as shown above)if it is new SD card and Click on 'Format'. For previously used SD cards, you can choose "FULL" by clicking on Options menu to erase and format the SD card. 5. You should see a pop up window that indicates progress of the formatting tool. The Quick format option usually takes a few seconds. The following message will be displayed when the formatting is completed. -.. Image:: ../images/SDF_Format_complete.png +.. Image:: /images/SDF_Format_complete.png 6. Copy the MLO (boot loader) to the formatted SD Card. @@ -179,11 +179,11 @@ This method works with all the platforms. However, this method requires the PDK | Here's an example using Windows 7: -.. Image:: ../images/Win7_eject_disk.png +.. Image:: /images/Win7_eject_disk.png -.. Image:: ../images/Win7_eject_disk_detail.png +.. Image:: /images/Win7_eject_disk_detail.png -.. Image:: ../images/Win7_device_can_be_safely_removed.png +.. Image:: /images/Win7_device_can_be_safely_removed.png | @@ -202,9 +202,9 @@ installer, you will see - AM335x/AM437x: -.. Image:: ../images/AM437x-SD-Card-Example.png +.. Image:: /images/AM437x-SD-Card-Example.png - AM57x: -.. Image:: ../images/AM57x-SD-Card-Example.png +.. Image:: /images/AM57x-SD-Card-Example.png diff --git a/source/rtos/Examples_and_Demonstrations/_Audio_Benchmark_Starterkit.rst b/source/rtos/Examples_and_Demonstrations/_Audio_Benchmark_Starterkit.rst index e8f4527f1..1753b5955 100644 --- a/source/rtos/Examples_and_Demonstrations/_Audio_Benchmark_Starterkit.rst +++ b/source/rtos/Examples_and_Demonstrations/_Audio_Benchmark_Starterkit.rst @@ -44,7 +44,7 @@ release under the directory path the image below. Detailed description of the directory structure is given below: -.. Image:: ../images/Audben_dirStructure.png +.. Image:: /images/Audben_dirStructure.png - prebuilt-binaries - directory contains prebuilt out files to run the benchmarks. - bootimages - SD card boot files to run the benchmarks using SD boot. @@ -157,7 +157,7 @@ For Other supported options, please type All available options are provided below: -.. Image:: ../images/Make_help.png +.. Image:: /images/Make_help.png Using CCS Projects ------------------ @@ -240,14 +240,14 @@ Description of arguments: Launch CCS and Import the CCS Project using the Project->Import Existing CCS Project and browse to the audio-benchmark-starterkit folder -.. Image:: ../images/CCS_Project_Browse.png +.. Image:: /images/CCS_Project_Browse.png **Step 4: Build Imported CCS Benchmark Projects** Right click on the Benchmark Project File and Build the project as shown below: -.. Image:: ../images/Build_Benchmark.png +.. Image:: /images/Build_Benchmark.png How to Run the Benchmarks ========================= @@ -344,7 +344,7 @@ on the SD card. Benchmark App output on UART console ==================================== -.. Image:: ../images/FFTbenchmark_sdBoot.png +.. Image:: /images/FFTbenchmark_sdBoot.png Benchmark Starterkit Implementation ----------------------------------- diff --git a/source/rtos/Examples_and_Demonstrations/_Audio_Pre_Processing.rst b/source/rtos/Examples_and_Demonstrations/_Audio_Pre_Processing.rst index 5f7b6a97a..bca667901 100644 --- a/source/rtos/Examples_and_Demonstrations/_Audio_Pre_Processing.rst +++ b/source/rtos/Examples_and_Demonstrations/_Audio_Pre_Processing.rst @@ -9,7 +9,7 @@ the integration of Beamforming (BF), Adaptive Spectral Noise Reduction (ASNR), Multiple Source Selection (MSS) and Dynamic Range Compression (DRC) components and provides a framework for application development. -.. Image:: ../images/Aud_pre_processing_arch.png +.. Image:: /images/Aud_pre_processing_arch.png The key functions in this use case include: @@ -440,7 +440,7 @@ Import Raw Audio Data File using Adobe Audition - File --> Import --> Raw Data... - The following dialog will pop up -.. Image:: ../images/Aud_pre_processing_import.png +.. Image:: /images/Aud_pre_processing_import.png - Select the raw audio file and input the correct parameters - Click OK @@ -450,11 +450,11 @@ Before and After Comparison - Before audio pre-processing (t8/y16L7g3m7090_1.pcm) -.. Image:: ../images/Aud_pre_processing_before.png +.. Image:: /images/Aud_pre_processing_before.png - After audio pre-processing (t8/fileOutput.bin) -.. Image:: ../images/Aud_pre_processing_after.png +.. Image:: /images/Aud_pre_processing_after.png | diff --git a/source/rtos/Examples_and_Demonstrations/_Bare_Metal_Examples.rst b/source/rtos/Examples_and_Demonstrations/_Bare_Metal_Examples.rst index b2b65d569..dec7ab0cd 100644 --- a/source/rtos/Examples_and_Demonstrations/_Bare_Metal_Examples.rst +++ b/source/rtos/Examples_and_Demonstrations/_Bare_Metal_Examples.rst @@ -44,7 +44,7 @@ Click Finish after you are done to allow CCS to auto generate the project from the template. -.. Image:: ../images/AM65x_Create_CCS_Project.png +.. Image:: /images/AM65x_Create_CCS_Project.png 6. The generated CCS project contains source file **main.c**, ARM assembly code **startup_ARMCA53.S** and a linker command file **AM65X.lds**. @@ -106,7 +106,7 @@ After connecting to the M3, right click on **CortexA53_0_0** and connect to it. 15. Load and run hello_world.out example file on the Cortex-A53. You should see a Hello_world string displayed in the CCS console window. -.. Image:: ../images/AM65x_CCS_Hello_World.PNG +.. Image:: /images/AM65x_CCS_Hello_World.PNG ARM Cortex-A15 ============== @@ -146,7 +146,7 @@ templates and examples, select **Basic Examples-> Hello World** Click Finish after you are done to allow CCS to auto generate the project from the template **Basic Examples-> Hello World**. -.. Image:: ../images/NewCCSProject_Hello_world.png +.. Image:: /images/NewCCSProject_Hello_world.png 5. The generated CCS project contains source file **main.c**, ARM assembly code **startup_ARMCA15.S** and a linker command file @@ -254,7 +254,7 @@ configurations --> AM572_DDR3_532MHz_config 11. Load and run hello_world.out example file. You should see **Hello_world** string displayed on CCS console window. -.. Image:: ../images/HelloWorldOutput.jpg +.. Image:: /images/HelloWorldOutput.jpg .. note:: @@ -296,7 +296,7 @@ build **little** endian **ELF** binary for the A9 core. Click Finish after you are done to allow CCS to auto generate the project from the template **Basic Examples-> Hello World**. -.. Image:: ../images/Bare-Metal_A9_templateselect.jpg +.. Image:: /images/Bare-Metal_A9_templateselect.jpg 5. The generated CCS project contains source file **main.c**, ARM assembly code **startup_ARMCA8.S** and a linker command file @@ -382,7 +382,7 @@ in the GEL will initialize the clocks and DDR. 10. Load and run hello_world_a9.out file. You should see **Hello World!** string displayed on CCS console window. -.. Image:: ../images/Hello_world_a9.jpg +.. Image:: /images/Hello_world_a9.jpg .. note:: If the example does not load correctly in the first attempt, reload and @@ -407,7 +407,7 @@ build **little** endian **ELF** binary for the A8 core. Click Finish after you are done to allow CCS to auto generate the project from the template **Basic Examples-> Hello World**. -.. Image:: ../images/Bare-Metal_A8_templateselect.jpg +.. Image:: /images/Bare-Metal_A8_templateselect.jpg 5. The generated CCS project contains source file **hello.c**, ARM assembly code **startup_ARMCA8.S** and a linker command file @@ -487,7 +487,7 @@ functionality in the GEL will initialize the clocks and DDR. 10. Load and run hello_world_a8.out file. You should see **Hello World!** string displayed on CCS console window. -.. Image:: ../images/Hello_world_a8.jpg +.. Image:: /images/Hello_world_a8.jpg .. note:: If the example does not load correctly in the first attempt, reload and @@ -521,7 +521,7 @@ Under Project templates and examples, select **Basic Examples -> Hello World** Click Finish after you are done to allow CCS to auto generate the project from the template. -.. Image:: ../images/AM65x_Create_CCS_Project_R5.png +.. Image:: /images/AM65x_Create_CCS_Project_R5.png 5. The generated CCS project contains source file **hello.c**, and linker command file **linker_r5.lds**. @@ -553,7 +553,7 @@ After connecting to the M3, right click on **MCU_PULSAR_Cortex_R5_0** and connec 11. Load and run hello_world.out example file on the Cortex-R5. You should see a Hello_world string displayed in the CCS console window. -.. Image:: ../images/AM65x_CCS_Hello_World_R5.PNG +.. Image:: /images/AM65x_CCS_Hello_World_R5.PNG | @@ -575,7 +575,7 @@ The Default settings uses "TI ARM compiler 5.x.x" tool chain for cortex M4 and sets the build for **little** endian **ELF** binary for the M4 core. -.. Image:: ../images/Bare-Metal_M4_templateselect.jpg +.. Image:: /images/Bare-Metal_M4_templateselect.jpg 5. The generated CCS project contains only one source file **hello.c**. Ensure the main.c file contains the following code @@ -678,7 +678,7 @@ You should see the following log in the Console Hello_Example_m4.out file. You should see **Hello World** string displayed on console window. -.. Image:: ../images/Hello_world_m4.jpg +.. Image:: /images/Hello_world_m4.jpg .. note:: @@ -699,14 +699,14 @@ As a sample we will use the OMAP-L138 device to describe the steps. 3. Select Target as OMAP-L1x --> ARM9 and appropriate target board as shown in the image below. -.. Image:: ../images/omapl13x_arm9_hello_nonos_ccs.png +.. Image:: /images/omapl13x_arm9_hello_nonos_ccs.png 4. In the ARM9 tab, provide a name for the project, such as "hello_world_arm9" and use the default settings for the project as shown in the image below. Ensure OMAPL138.cmd is selected for the linker command file. -.. Image:: ../images/omapl13x_arm9_hello_nonos_ccs2.png +.. Image:: /images/omapl13x_arm9_hello_nonos_ccs2.png 5. Click Finish after you are done to allow CCS to auto generate the project from the @@ -835,7 +835,7 @@ World**. The Default settings uses "TI CG Tools compiler 8.x.x" tool chain for C66x and sets the build for **little** endian **ELF** binary for the C66x core. -.. Image:: ../images/Bare-Metal_C66x_templateselect.jpg +.. Image:: /images/Bare-Metal_C66x_templateselect.jpg 5. The generated CCS project contains only one source file **hello.c**. Ensure the main.c file contains the following code @@ -940,7 +940,7 @@ You should see the following log in the Console 10. Select and Connect to C66x_DSP1. Load and run hello_world_dsp.out file. You should see **Hello World** string displayed on console window. -.. Image:: ../images/Hello_world_dsp.jpg +.. Image:: /images/Hello_world_dsp.jpg | @@ -973,7 +973,7 @@ World**. The Default settings uses "TI CG Tools compiler 8.x.x" tool chain for C674x and sets the build for **little** endian **ELF** binary for the C674x core. -.. Image:: ../images/Baremetal_helloWorld_ProjectCreate_step1.png +.. Image:: /images/Baremetal_helloWorld_ProjectCreate_step1.png 5. The generated CCS project contains only one source file **hello.c**. Ensure the main.c file contains the following code @@ -1102,7 +1102,7 @@ power up the DSP. You should see the following log in the console. 11. Select and Connect to C674x. Load and run hello_world_dsp.out file. You should see **Hello World** string displayed on console window. -.. Image:: ../images/Hello_world_dsp674x.png +.. Image:: /images/Hello_world_dsp674x.png | diff --git a/source/rtos/Examples_and_Demonstrations/_Big_Data_IPC_Examples.rst b/source/rtos/Examples_and_Demonstrations/_Big_Data_IPC_Examples.rst index c4c680b24..06deab7dc 100644 --- a/source/rtos/Examples_and_Demonstrations/_Big_Data_IPC_Examples.rst +++ b/source/rtos/Examples_and_Demonstrations/_Big_Data_IPC_Examples.rst @@ -21,7 +21,7 @@ Architecture Overview The following block diagram shows the various functional blocks used in the example on the cores running TI-RTOS/BIOS. -.. Image:: ../images/Big_Data_IPC_RTOS_Software_blocks.png +.. Image:: /images/Big_Data_IPC_RTOS_Software_blocks.png For the small message IPC, sharedRegion and Heap, the modules in the Standard TI IPC package are used. @@ -89,7 +89,7 @@ Architecture Updates for Linux The following block diagram shows the various functional blocks used in the example on the host running linux. -.. Image:: ../images/Big_DATA_IPC_Linux_Software_blocks.png +.. Image:: /images/Big_DATA_IPC_Linux_Software_blocks.png The SharedRegion and HeapMem modules are not currently supported for Linux in the TI Standard IPC package. @@ -402,7 +402,7 @@ Parity= None, Flow Control= Off ) The application will be loaded and run automatically and the "Host: Test Passed" message will be printed to the UART console. -.. Image:: ../images/BigDataIPC_Rtos_Demo.png +.. Image:: /images/BigDataIPC_Rtos_Demo.png K2H, K2K, K2L, K2E Boards ^^^^^^^^^^^^^^^^^^^^^^^^^ diff --git a/source/rtos/Examples_and_Demonstrations/_Can_Eth_Gateway_Demo.rst b/source/rtos/Examples_and_Demonstrations/_Can_Eth_Gateway_Demo.rst index 888d1c5a8..e5f0cd724 100644 --- a/source/rtos/Examples_and_Demonstrations/_Can_Eth_Gateway_Demo.rst +++ b/source/rtos/Examples_and_Demonstrations/_Can_Eth_Gateway_Demo.rst @@ -23,7 +23,7 @@ applications are used for transmitting & receiving the Ethernet frames from/to PC, similarly for CAN message reception & transmission, any compatible CAN tool can be used. -.. Image:: ../images/can-eth-gateway.png +.. Image:: /images/can-eth-gateway.png :height: 1000px :width: 1500px :scale: 50 % @@ -177,7 +177,7 @@ AM65x EVM/IDK Board Set up * Carefully remove the IDK application board by removing the four screws and gently separating the board from the connectors. * On the top of the board, solder a 120 ohm resistor to the footprint for R252. - .. Image:: ../images/am65x_evm_idk_board_changes_for_mcan_interface1.png + .. Image:: /images/am65x_evm_idk_board_changes_for_mcan_interface1.png :height: 500px :width: 800px :scale: 50 % @@ -186,7 +186,7 @@ AM65x EVM/IDK Board Set up * On the bottom of the board, solder a 120 ohm resistor to the footprint for R130. - .. Image:: ../images/am65x_evm_idk_board_changes_for_mcan_interface2.png + .. Image:: /images/am65x_evm_idk_board_changes_for_mcan_interface2.png :height: 500px :width: 800px :scale: 50 % @@ -225,7 +225,7 @@ CAN FD adapter PCAN-USB FD allows the connection of CAN FD and CAN networks to a * Bit rates may vary from use-case to use-case. * Click on Ok button. - .. Image:: ../images/pcan_view_device_selection.png + .. Image:: /images/pcan_view_device_selection.png :height: 500px :width: 500px :scale: 50 % @@ -242,7 +242,7 @@ CAN FD adapter PCAN-USB FD allows the connection of CAN FD and CAN networks to a * Cycle Time as ‘2000’ * Data: as use-case needs - .. Image:: ../images/CanEth_PCANViewTransmitMessageConfig.png + .. Image:: /images/CanEth_PCANViewTransmitMessageConfig.png :height: 500px :width: 600px :scale: 50 % @@ -262,7 +262,7 @@ CAN FD adapter PCAN-USB FD allows the connection of CAN FD and CAN networks to a * Bit Rate text box shall show ‘5 Mbit/s’ after programming above values. * Click on ‘Ok’ and then again on ‘Ok’ - .. Image:: ../images/CanEth_PCANViewBitRateConfig.png + .. Image:: /images/CanEth_PCANViewBitRateConfig.png :height: 500px :width: 800px :scale: 50 % diff --git a/source/rtos/Examples_and_Demonstrations/_Gravity_Simulator_Demo.rst b/source/rtos/Examples_and_Demonstrations/_Gravity_Simulator_Demo.rst index f08feecda..232ae5466 100644 --- a/source/rtos/Examples_and_Demonstrations/_Gravity_Simulator_Demo.rst +++ b/source/rtos/Examples_and_Demonstrations/_Gravity_Simulator_Demo.rst @@ -102,7 +102,7 @@ Terminal Screenshot Below is a screenshot of the terminal after one simulation: -.. Image:: ../images/Gravit-screenshot_version_01_00_00.png +.. Image:: /images/Gravit-screenshot_version_01_00_00.png Display Output ============== @@ -115,7 +115,7 @@ Display Output Below is an example display of a 500-particle simulation: -.. Image:: ../images/Gravit-displayshot_version_01_00_00.jpg +.. Image:: /images/Gravit-displayshot_version_01_00_00.jpg Useful References ================= diff --git a/source/rtos/Examples_and_Demonstrations/_Image_Processing_Demo.rst b/source/rtos/Examples_and_Demonstrations/_Image_Processing_Demo.rst index 2703d4b74..349f5a23c 100644 --- a/source/rtos/Examples_and_Demonstrations/_Image_Processing_Demo.rst +++ b/source/rtos/Examples_and_Demonstrations/_Image_Processing_Demo.rst @@ -244,41 +244,41 @@ The CCS is used to load the program and run on ARM-A15 (HOST), C66x Core - Connect to CortexA15_0 (Host) [Push "Power" button right before connect to CortexA15_0] -.. Image:: ../images/Am572x_connect_a15.jpg +.. Image:: /images/Am572x_connect_a15.jpg - Connect to C66xx_DSP1 -.. Image:: ../images/Am572x_connect_dsp1.jpg +.. Image:: /images/Am572x_connect_dsp1.jpg - Connect to C66xx_DSP2 -.. Image:: ../images/Am572x_connect_dsp2.jpg +.. Image:: /images/Am572x_connect_dsp2.jpg - Load image_processing_evmam572x_dsp1.out to C66xx_DSP1 using JTAG -.. Image:: ../images/Am572x_load_dsp1.jpg +.. Image:: /images/Am572x_load_dsp1.jpg - Run image_processing_evmam572x_dsp1.out on C66xx_DSP1 - Load image_processing_evmam572x_dsp2.out to C66xx_DSP2 using JTAG -.. Image:: ../images/Am572x_load_dsp2.jpg +.. Image:: /images/Am572x_load_dsp2.jpg - Run image_processing_evmam572x_dsp2.out on C66xx_DSP2 - Loaded image_processing_evmam572x_host.out to CortexA15_0 -.. Image:: ../images/Am572x_load_host.jpg +.. Image:: /images/Am572x_load_host.jpg - Run image_processing_evmc6678l_master.out on CortexA15_0 - The HOST will display the IP address on CCS CIO -.. Image:: ../images/Am572x_cio.jpg +.. Image:: /images/Am572x_cio.jpg - Users can use internet browser to access this IP address - The Image Processing Demo page will be displayed - Provide values for the "Number of Cores" and "Select Image to Process" fields -.. Image:: ../images/Am572x_web_1.jpg +.. Image:: /images/Am572x_web_1.jpg The HOST will read the image via NDK, partition it according to the number of cores, send the messages to DSP cores (Slaves) via IPC @@ -288,7 +288,7 @@ HOST will be notified by DSP cores via IPC MessageQ. Subsequently, the HOST will write the input and output images to the Image Processing Demo page using NDK. -.. Image:: ../images/Am572x_web_2.jpg +.. Image:: /images/Am572x_web_2.jpg | @@ -318,7 +318,7 @@ below: - Provide values for the "Number of Cores" and "Select Image to Process" fields -.. Image:: ../images/Am572x_web_1.jpg +.. Image:: /images/Am572x_web_1.jpg The HOST will read the image via NDK, partition it according to the number of cores, send the messages to DSP cores (Slaves) via IPC @@ -328,7 +328,7 @@ HOST will be notified by DSP cores via IPC MessageQ. Subsequently, the HOST will write the input and output images to the Image Processing Demo page using NDK. -.. Image:: ../images/Am572x_web_2.jpg +.. Image:: /images/Am572x_web_2.jpg C6678 EVM or C6657 EVM ^^^^^^^^^^^^^^^^^^^^^^ @@ -340,33 +340,33 @@ C665x. - Launch CCS and connect to C6678 EVM using proper target configuration - Connect to C66x Core 0 (Host) -.. Image:: ../images/C6678_connect_core0.jpg +.. Image:: /images/C6678_connect_core0.jpg - Loaded image_processing_evmc6678l_master.out to C66x Core 0 -.. Image:: ../images/C6678_load_master.jpg +.. Image:: /images/C6678_load_master.jpg - Run image_processing_evmc6678l_master.out on C66xx_0 - Group C66x Core 1-N into a group (Group 1, Slave) - Connect to Group 1 -.. Image:: ../images/C6678_connect_group1.jpg +.. Image:: /images/C6678_connect_group1.jpg - Load image_processing_evmc6678l_slave.out to Group 1 using JTAG -.. Image:: ../images/C6678_load_slave.jpg +.. Image:: /images/C6678_load_slave.jpg - Run image_processing_evmc6678l_slave.out on Group 1 - The HOST will display the IP address on CCS CIO -.. Image:: ../images/C6678_cio.jpg +.. Image:: /images/C6678_cio.jpg - Users can use internet browser to access this IP address - The Image Processing Demo page will be displayed - Provide values for the "Number of Cores" and "Select Image to Process" fields -.. Image:: ../images/Demo_web_page_1.jpg +.. Image:: /images/Demo_web_page_1.jpg The HOST will read the image via NDK, partition it according to the number of cores, send the messages to DSP cores (Slaves) via IPC @@ -376,7 +376,7 @@ HOST will be notified by DSP cores via IPC MessageQ. Subsequently, the HOST will write the input and output images to the Image Processing Demo page using NDK. -.. Image:: ../images/Demo_web_page_2.jpg +.. Image:: /images/Demo_web_page_2.jpg K2H EVM ^^^^^^^ @@ -387,42 +387,42 @@ master and C66xx_0 - C66xx_7 will be configured as slaves. - Launch CCS and connect to K2H EVM using proper target configuration - Connect to arm_A15_0 (Host) -.. Image:: ../images/K2h_connect_a15.jpg +.. Image:: /images/K2h_connect_a15.jpg - Group C66xx_0 to C66xx_7 into a group (Group 1, Slaves) -.. Image:: ../images/K2h_from_group1.jpg +.. Image:: /images/K2h_from_group1.jpg - Connect to Group 1 -.. Image:: ../images/K2h_connect_group1.jpg +.. Image:: /images/K2h_connect_group1.jpg - Load image_processing_evmk2hk_slave.out to Group 1 using JTAG -.. Image:: ../images/K2h_load_group1.jpg +.. Image:: /images/K2h_load_group1.jpg - Run image_processing_evmk2hk_slave.out on Group 1 -.. Image:: ../images/K2h_run_group1.jpg +.. Image:: /images/K2h_run_group1.jpg - Loaded image_processing_evmk2hk_master_arm.out to arm_A15_0 -.. Image:: ../images/K2h_load_a15.jpg +.. Image:: /images/K2h_load_a15.jpg - Run image_processing_evmk2hk_master_arm.out on arm_A15_0 -.. Image:: ../images/K2h_run_a15.jpg +.. Image:: /images/K2h_run_a15.jpg - The HOST will display the IP address on CCS CIO -.. Image:: ../images/K2h_cio.jpg +.. Image:: /images/K2h_cio.jpg - Users can use internet browser to access this IP address - The Image Processing Demo page will be displayed - Provide values for the "Number of Cores" and "Select Image to Process" fields -.. Image:: ../images/K2h_web_1.jpg +.. Image:: /images/K2h_web_1.jpg The HOST will read the image via NDK, partition it according to the number of cores, send the messages to DSP cores (Slaves) via IPC @@ -432,5 +432,5 @@ HOST will be notified by DSP cores via IPC MessageQ. Subsequently, the HOST will write the input and output images to the Image Processing Demo page using NDK. -.. Image:: ../images/K2h_web_2.jpg +.. Image:: /images/K2h_web_2.jpg diff --git a/source/rtos/Examples_and_Demonstrations/_Jailhouse_Hypervisor.rst b/source/rtos/Examples_and_Demonstrations/_Jailhouse_Hypervisor.rst index 2b50dc5a7..c818437de 100644 --- a/source/rtos/Examples_and_Demonstrations/_Jailhouse_Hypervisor.rst +++ b/source/rtos/Examples_and_Demonstrations/_Jailhouse_Hypervisor.rst @@ -12,7 +12,7 @@ Linux OS and is known as the "root cell". Other cells borrow CPUs and devices from the root cell as they are created. | -.. Image:: ../images/Jailhouse.png +.. Image:: /images/Jailhouse.png *The picture above shows the jailhouse on a system a) before the jailhouse is enabled; b) after the jailhouse is enabled; c) after a cell diff --git a/source/rtos/Examples_and_Demonstrations/_Performance_Audio.rst b/source/rtos/Examples_and_Demonstrations/_Performance_Audio.rst index e3dc569a5..0890b71d3 100644 --- a/source/rtos/Examples_and_Demonstrations/_Performance_Audio.rst +++ b/source/rtos/Examples_and_Demonstrations/_Performance_Audio.rst @@ -8,7 +8,7 @@ This demo implements and integrates audio I/O, framework, auto-detection, decodi processing (ASP) and encoding - the foundational building blocks of any performance audio application. The system block diagram below shows the structure of the demo. -.. Image:: ../images/pa_k2g_layout.png +.. Image:: /images/pa_k2g_layout.png :scale: 100 % This demo utilizes Processor SDK features/components: @@ -48,7 +48,7 @@ Hardware Setup - Connect a COM port on PC to UART0 port on K2G EVM using a RS-232 cable. - Connect XDS2xx USB Onboard Debug Probe to a PC USB port using the USB cable delivered with the EVM. -.. Image:: ../images/pa_k2g_EVM_DC_setup.png +.. Image:: /images/pa_k2g_EVM_DC_setup.png :scale: 70 % Optional Setup for HDMI @@ -68,7 +68,7 @@ Optional Setup for HDMI from HSR41P J8 “HDMI OUT”. - Connect 5V AC to USB power supply to IFB power connector J1. -.. Image:: ../images/pa_k2g_EVM_DC_HDMI_setup.png +.. Image:: /images/pa_k2g_EVM_DC_HDMI_setup.png :scale: 70 % Software and Tools Setup diff --git a/source/rtos/Examples_and_Demonstrations/_Posix_SMP_Demo.rst b/source/rtos/Examples_and_Demonstrations/_Posix_SMP_Demo.rst index dd1432015..41d12d6a6 100644 --- a/source/rtos/Examples_and_Demonstrations/_Posix_SMP_Demo.rst +++ b/source/rtos/Examples_and_Demonstrations/_Posix_SMP_Demo.rst @@ -99,7 +99,7 @@ run using the SBL with UART or using CCS with UART or ROV (UART display for newer versions and ROV for older versions). To run using UART, hook up to the board using UART and run the .out file. -.. Image:: ../images/Posix-demo-uart.PNG +.. Image:: /images/Posix-demo-uart.PNG To run using CCS, use the following steps. Each binary has an associated \\*.rov.xs file located in the same directory--enabling the CCS ROV tool. @@ -137,11 +137,11 @@ If using Processor-SDK 3.0 or later, SysMin module to inspect the output of the demo. If you see the below message, please specify the XDC and SYSBIOS versions: -.. Image:: ../images/Use_rov_1.jpg +.. Image:: /images/Use_rov_1.jpg -.. Image:: ../images/Use_rov_2.png +.. Image:: /images/Use_rov_2.png -.. Image:: ../images/Posix-smp2.png +.. Image:: /images/Posix-smp2.png The output buffer shown in the ROV contains the different stages of the demo's progression: diff --git a/source/rtos/Examples_and_Demonstrations/_RTOS_Examples.rst b/source/rtos/Examples_and_Demonstrations/_RTOS_Examples.rst index 3e9983f92..eb80cf181 100644 --- a/source/rtos/Examples_and_Demonstrations/_RTOS_Examples.rst +++ b/source/rtos/Examples_and_Demonstrations/_RTOS_Examples.rst @@ -73,7 +73,7 @@ Keystone 2 family of devices. - The K2G, K2E and K2H devices, can be located under Unclassified devices in the Resource Explorer. Refer below Screenshot for Keystone II -.. Image:: ../images/KSII_RS.png +.. Image:: /images/KSII_RS.png 1. Create a work space folder (\ti\am_572x_hello_workspace) under ti folder to be used for Hello Example project, and start CCS. You may be @@ -85,14 +85,14 @@ Finish** 3. On SYS/BIOS scroll down to AM572X --> Cortex A --> Generic Example --> click on Hello Example. -.. Image:: ../images/Sys_bios_hello_example_screen_1.jpg +.. Image:: /images/Sys_bios_hello_example_screen_1.jpg 4. To import Hello Example, on the right window click on step 1. Import The Example to CCS Project. 5. On New CCS Project window enter project name and then click Next. -.. Image:: ../images/Sys_bios_hello_example_screen_2.jpg +.. Image:: /images/Sys_bios_hello_example_screen_2.jpg 6. On RSTC window select platform name: **ti.platforms.evmAM572X** and check that the target is set to **gnu.targets.arm.A15F** @@ -157,14 +157,14 @@ Finish** 3. On SYS/BIOS scroll down to AM4378 --> Cortex A --> Generic Example --> click on Hello Example. -.. Image:: ../images/RTOS_CortexA9_HelloWorld.png +.. Image:: /images/RTOS_CortexA9_HelloWorld.png 4. To import Hello Example, on the right window click on step 1. Import The Example to CCS Project. 5. On New CCS Project window enter project name and then click Next. -.. Image:: ../images/HelloWorld_cortexA9.png +.. Image:: /images/HelloWorld_cortexA9.png 6. On RSTC window select platform name: **ti.platforms.evmAM437X** and check that the target is set to **gnu.targets.arm.A9F** @@ -234,7 +234,7 @@ Resource Explorer (Examples). 3. On SYS/BIOS scroll down to AM3352 --> Cortex A --> Generic Example --> click on Hello Example. -.. Image:: ../images/RTOS_CortexA8_HelloWorld.png +.. Image:: /images/RTOS_CortexA8_HelloWorld.png 4. To import Hello Example, on the right window click on step 1. Import The Example to CCS Project. @@ -242,7 +242,7 @@ The Example to CCS Project. 5. On New CCS Project window enter project name and then click Next. -.. Image:: ../images/HelloWorld_cortexA8.png +.. Image:: /images/HelloWorld_cortexA8.png 6. On RSTC window select platform name: **ti.platforms.evmAM335X** and check that the target is set to **gnu.targets.arm.A8F** @@ -349,14 +349,14 @@ Finish** 3. on SYS/BIOS scroll down to AM572X --> Cortex M --> Generic Example --> click on Hello Example. -.. Image:: ../images/SYSBIOS_hello_world_M4_template.jpg +.. Image:: /images/SYSBIOS_hello_world_M4_template.jpg 4. To import Hello Example, on the right window click on step 1. Import The Example to CCS Project. 5. Go to Project Explorer window and click on project properties. -.. Image:: ../images/SYSBIOS_M4_platformSelect.jpg +.. Image:: /images/SYSBIOS_M4_platformSelect.jpg 6. On RSTC window select platform name: **ti.platforms.evmAM572X** and check that the target is set to **gnu.targets.arm.elf.M4** @@ -396,14 +396,14 @@ Finish** 3. On SYS/BIOS scroll down to OMAP-L1x --> LCDKOMAPL138 --> TI Target Examples --> Generic Examples --> click on Hello Example. -.. Image:: ../images/omapl13x_arm9_hello_rtos_tirex.png +.. Image:: /images/omapl13x_arm9_hello_rtos_tirex.png 4. To import Hello Example, on the right window click on step 1. Import The Example to CCS Project. 5. On New CCS Project window enter project name and then click Next. -.. Image:: ../images/omapl13x_arm9_hello_rtos_ccs.png +.. Image:: /images/omapl13x_arm9_hello_rtos_ccs.png 6. On RSTC window select platform name: **ti.platforms.evmOMAPL138** and check that the target is set to **ti.targets.arm.elf.Arm9** @@ -441,14 +441,14 @@ Keystone I and Keystone 2 family of devices. under C66x Multi-core DSP devies in the Resource Explorer. Refer below screenshot -.. Image:: ../images/KSI_RS.png +.. Image:: /images/KSI_RS.png .. note:: - The K2G, K2E and K2H devices, can be located under Unclassified devices in the Resource Explorer. Refer below screen shot -.. Image:: ../images/KSII_RS.png +.. Image:: /images/KSII_RS.png 1. Create a work space folder (\ti\am_572x_hello_workspace) under ti folder to be used for Hello Example project, and start CCS. You may be @@ -460,14 +460,14 @@ Finish** 3. on SYS/BIOS scroll down to AM572X --> C66x --> Generic Example --> click on Hello Example. -.. Image:: ../images/SYSBIOS_hello_world_dsp_template.jpg +.. Image:: /images/SYSBIOS_hello_world_dsp_template.jpg 4. To import Hello Example, on the right window click on step 1. Import The Example to CCS Project. 5. On New CCS Project window enter project name and then click Next. -.. Image:: ../images/SYSBIOS_DSP_platformSelect.jpg +.. Image:: /images/SYSBIOS_DSP_platformSelect.jpg 6. On RSTC window select platform name: **ti.platforms.evmAM572X** and check that the target is set to **ti.targets.elf.C66** (Auto populated) @@ -521,19 +521,19 @@ described here: 3. on SYS/BIOS scroll down to C6748 /OMAPL1x and select --> C674x --> Generic Example --> click on Hello Example. -.. Image:: ../images/OMAPL138_SYSBIOS_TI_RTOS_CCSv7.png +.. Image:: /images/OMAPL138_SYSBIOS_TI_RTOS_CCSv7.png 4. To import Hello Example, on the right window click on step 1. Import The Example to CCS Project. 5. On New CCS Project window enter project name and then click Next. -.. Image:: ../images/Create_Project_Step1.png +.. Image:: /images/Create_Project_Step1.png 6. On RSTC window select platform name: **ti.platforms.evmc6748** and check that the target is set to **ti.targets.elf.C674** (Auto populated) -.. Image:: ../images/Create_Project_Step2.png +.. Image:: /images/Create_Project_Step2.png 7. Click Finish. Your project should show up on Project Explorer window. @@ -571,7 +571,7 @@ power up the DSP You should see the following log in the Console 13. Connect to C674x_DSP1 Load and run Hello Example out file. You should see **Hello World** string displayed on console window. -.. Image:: ../images/Hello_world_dsp674x_rtos.png +.. Image:: /images/Hello_world_dsp674x_rtos.png | diff --git a/source/rtos/Examples_and_Demonstrations/_RTOS_Template_App.rst b/source/rtos/Examples_and_Demonstrations/_RTOS_Template_App.rst index 190902268..93544e9f1 100644 --- a/source/rtos/Examples_and_Demonstrations/_RTOS_Template_App.rst +++ b/source/rtos/Examples_and_Demonstrations/_RTOS_Template_App.rst @@ -171,7 +171,7 @@ Preferences --> Code Composer Studio --> Products* menu. This menu will allow you define product discovery paths and rediscover, install, and unistall products. -.. image:: ../images/install-discovered-products.png +.. image:: /images/install-discovered-products.png :scale: 70 % For more info on setting up CCS. Check out @@ -203,7 +203,7 @@ menu. Then click *Browse...* to locate the template app which can be found at: **processor_sdk_rtos__/demos/rtos_template_app///**. This will create a copy of the project in your CCS workspace. -.. image:: ../images/import-ccs-project.png +.. image:: /images/import-ccs-project.png :scale: 70 % After project import is complete you will see the Template Application under @@ -254,12 +254,12 @@ Example connections for the AM572x EVM are provided below: Front ^^^^^ -.. image:: ../images/am572x-evm-hw-setup-front.jpg +.. image:: /images/am572x-evm-hw-setup-front.jpg :scale: 50 % Back ^^^^ -.. image:: ../images/am572x-evm-hw-setup-back.jpg +.. image:: /images/am572x-evm-hw-setup-back.jpg :scale: 44 % Task 4 - Loading and Running the Template Application @@ -279,7 +279,7 @@ the *board* is the name of your EVM (either *EVMAM3358*, *EVMAM437X*, or For example, here is the target configuration for the AM572x EVM using an XDS200 Debug Probe: -.. image:: ../images/am572x-evm-target-config.png +.. image:: /images/am572x-evm-target-config.png :scale: 70 % After setup is complete, clike the *Save* button to save your target @@ -307,7 +307,7 @@ the target configuration that you created earlier and click *Launch Selected Configuration*. This action will switch CCS into the debug perspective. Your CCS instance should look similar to below: -.. image:: ../images/ccs-debug-pers.png +.. image:: /images/ccs-debug-pers.png :scale: 70 % In the top left corner of CCS you should see a list of all of the available @@ -345,13 +345,13 @@ the *Browse project...* button and choose the **[rtos or baremetal]_template_app__.out** executable. Then click *OK* to load the executable. -.. image:: ../images/load-executable.png +.. image:: /images/load-executable.png You should now see the **main.c** file open in CCS and the program halted at the beginning of the ``main()`` function. At this point you can click on the *Resume (F8)* |resume| button to start executing the Template Application. -.. |resume| image:: ../images/resume-button.png +.. |resume| image:: /images/resume-button.png The application will begin running and print progress over the UART. You should see the following text printed to your serial terminal:: @@ -400,7 +400,7 @@ Next, click the *Terminate* |terminate| button to disconnect from the target. At this point you have successfully imported, built, and run the Template Application. -.. |terminate| image:: ../images/terminate-button.png +.. |terminate| image:: /images/terminate-button.png Task 5 - Examining the Template Application ------------------------------------------------ diff --git a/source/rtos/Examples_and_Demonstrations/_SimpleLink_WiFi_Demo.rst b/source/rtos/Examples_and_Demonstrations/_SimpleLink_WiFi_Demo.rst index 8125683c4..5586e77fe 100644 --- a/source/rtos/Examples_and_Demonstrations/_SimpleLink_WiFi_Demo.rst +++ b/source/rtos/Examples_and_Demonstrations/_SimpleLink_WiFi_Demo.rst @@ -28,9 +28,9 @@ Hardware - Blue wires between CC3120 BP and AMIC110 ICE - Serial UART cable (provided in EVM kit) - Connection Diagram -.. Image:: ../images/sl_wifi_demo_connection.jpg +.. Image:: /images/sl_wifi_demo_connection.jpg - Picture of connected EVMs -.. Image:: ../images/sl_wifi_demo_connected.jpg +.. Image:: /images/sl_wifi_demo_connected.jpg Software @@ -60,7 +60,7 @@ are providing the INT and RESET signals. The following diagram shows the overview of the demo: -.. Image:: ../images/sl_wifi_demo_overview.jpg +.. Image:: /images/sl_wifi_demo_overview.jpg The source files are organized as follows: @@ -94,7 +94,7 @@ Please follow below step by step procedure to build the application. .. note:: This will create executable binary under /network_terminal_AMIC110_ICE_RTOS_RTOS_ccs/Debug/network_terminal_AMIC110_ICE_RTOS_RTOS_ccs.out -.. Image:: ../images/sl_wifi_demo_ccs_import.jpg +.. Image:: /images/sl_wifi_demo_ccs_import.jpg How to Build the SimpleLink WiFi Plugin Demo using makefile on Windows @@ -172,19 +172,19 @@ To load and run SimpleLink WiFi Plugin Demo: Now the network terminal demo will run and print progress through the UART. - The inital display on the UART -.. Image:: ../images/sl_wifi_demo_uart_init.jpg +.. Image:: /images/sl_wifi_demo_uart_init.jpg - Enter "help" at UART prompt -.. Image:: ../images/sl_wifi_demo_uart_help.jpg +.. Image:: /images/sl_wifi_demo_uart_help.jpg - Enter "scan -n 10" at UART prompt -.. Image:: ../images/sl_wifi_demo_uart_scan.jpg +.. Image:: /images/sl_wifi_demo_uart_scan.jpg - Enter " wlanconnect -s "dir645" -t WPA/WPA2 -p "12345678" " at UART prompt -.. Image:: ../images/sl_wifi_demo_uart_wlanconnect.jpg +.. Image:: /images/sl_wifi_demo_uart_wlanconnect.jpg - Enter "ping 192.168.0.1" at UART prompt -.. Image:: ../images/sl_wifi_demo_uart_ping.jpg +.. Image:: /images/sl_wifi_demo_uart_ping.jpg .. note:: This demo uses the D-Link DIR-645 wirless router with DHCP server. "dir645" is its SSID. "12345678" is its @@ -205,28 +205,28 @@ To load and run SimpleLink WiFi Plugin Demo: #. Send the bootloader_boot_uart_a8host_debug.bin under pdk__/packages/ti/starterware/binary/bootloader/bin/am335x-evm/gcc using the XMODEM. -.. Image:: ../images/sl_uart_boot_1st.jpg +.. Image:: /images/sl_uart_boot_1st.jpg #. Upon completion, then send the network_terminal.bin under processor_sdk_rtos__/demos/simplelink-wifi-demo/bin/am335x/a8/debug using the XMODEM. -.. Image:: ../images/sl_uart_boot_2nd.jpg +.. Image:: /images/sl_uart_boot_2nd.jpg Now the network terminal demo will run and print progress through the UART. - The inital display on the UART -.. Image:: ../images/sl_wifi_demo_uart_init.jpg +.. Image:: /images/sl_wifi_demo_uart_init.jpg - Enter "help" at UART prompt -.. Image:: ../images/sl_wifi_demo_uart_help.jpg +.. Image:: /images/sl_wifi_demo_uart_help.jpg - Enter "scan -n 10" at UART prompt -.. Image:: ../images/sl_wifi_demo_uart_scan.jpg +.. Image:: /images/sl_wifi_demo_uart_scan.jpg - Enter " wlanconnect -s "dir645" -t WPA/WPA2 -p "12345678" " at UART prompt -.. Image:: ../images/sl_wifi_demo_uart_wlanconnect.jpg +.. Image:: /images/sl_wifi_demo_uart_wlanconnect.jpg - Enter "ping 192.168.0.1" at UART prompt -.. Image:: ../images/sl_wifi_demo_uart_ping.jpg +.. Image:: /images/sl_wifi_demo_uart_ping.jpg .. note:: This demo uses the D-Link DIR-645 wirless router with DHCP server. "dir645" is its SSID. "12345678" is its diff --git a/source/rtos/How_to_Guides/Host/Porting/_PSDK_RTOS_Porting_Guide_for_AM57xx_Speed_Grades.rst b/source/rtos/How_to_Guides/Host/Porting/_PSDK_RTOS_Porting_Guide_for_AM57xx_Speed_Grades.rst index 573db6446..fb50d6da5 100644 --- a/source/rtos/How_to_Guides/Host/Porting/_PSDK_RTOS_Porting_Guide_for_AM57xx_Speed_Grades.rst +++ b/source/rtos/How_to_Guides/Host/Porting/_PSDK_RTOS_Porting_Guide_for_AM57xx_Speed_Grades.rst @@ -37,12 +37,12 @@ Comparison of AM572x, AM571x and AM570x devices **Quick Feature Set comparison between devices in Sitara AM57xx family :** -.. Image:: ../images/AM572x_AM571X_AM570x_Comparison.png +.. Image:: /images/AM572x_AM571X_AM570x_Comparison.png | | **Supported OPP on AM57xx devices:** -.. Image:: ../images/AM57xx_OPP.png +.. Image:: /images/AM57xx_OPP.png Code Composer Studio (CCS) and Emulation support ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ @@ -78,13 +78,13 @@ IDK platform **Step 1: Select the AM570x part number that is populated on your custom platform:** -.. Image:: ../images/AM5708_EVM_target_configurations.png +.. Image:: /images/AM5708_EVM_target_configurations.png **Step 2: Setup the GEL files for the SOC** Go to the Advanced Tab as shown in the previous screenshot and update startup GEL file in the A15 Core as shown in the screenshot below -.. Image:: ../images/Advanced_settings_GEL_setup.png +.. Image:: /images/Advanced_settings_GEL_setup.png Board Library Changes to Consider for Using Processor SDK RTOS ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ @@ -99,7 +99,7 @@ to setup the MPU to 1.5, 1.176 and 1GHz. For AM570x devices, we support the "J" and the "D" variant which support the following max speeds on the DPLLs: -.. Image:: ../images/AM5706_Speed_Grades.png +.. Image:: /images/AM5706_Speed_Grades.png When using the "J" speed grade, ensure that the DPLLs in the board set the DPLL to OPP_NOM and not for OPP_OD or OPP_HIGH. diff --git a/source/rtos/How_to_Guides/Host/Setup/_Setup_CCS_for_EVM_and_PSDK_RTOS.rst b/source/rtos/How_to_Guides/Host/Setup/_Setup_CCS_for_EVM_and_PSDK_RTOS.rst index 1d6306946..e483acfef 100644 --- a/source/rtos/How_to_Guides/Host/Setup/_Setup_CCS_for_EVM_and_PSDK_RTOS.rst +++ b/source/rtos/How_to_Guides/Host/Setup/_Setup_CCS_for_EVM_and_PSDK_RTOS.rst @@ -18,7 +18,7 @@ CCS and SDK installed in same directory After installing the Processor-SDK RTOS, start CCS and it will automatically detect the newly installed components (*products*): -.. Image:: ../images/CCS-discovered-products.png +.. Image:: /images/CCS-discovered-products.png | CCS and SDK installed in different directories """"""""""""""""""""""""""""""""""""""""""""""" @@ -34,7 +34,7 @@ Go to product preference From CCS, select "Window -> Preferences": -.. Image:: ../images/CCS-GP57x-EVM-Custom-Preferences.png +.. Image:: /images/CCS-GP57x-EVM-Custom-Preferences.png | Enter path to SDK ''''''''''''''''''' @@ -43,7 +43,7 @@ In the Preferences window, select "Code Composer Studio -> RTSC -> Products" in the panel on the left. Then, press the "Add" button on the panel on the right: -.. Image:: ../images/CCS-GP57x-EVM-Custom-Add.png +.. Image:: /images/CCS-GP57x-EVM-Custom-Add.png | Verify components '''''''''''''''''' @@ -51,7 +51,7 @@ Verify components Next, verify the newly discovered products. If everything is correct, press the "Finish" button on the bottom: -.. Image:: ../images/CCS-GP57x-EVM-Custom-Finish.png +.. Image:: /images/CCS-GP57x-EVM-Custom-Finish.png | Restart CCS '''''''''''' @@ -59,7 +59,7 @@ Restart CCS When prompted, restart CCS for changes to take effect. You will see newly discovered products from the custom path. -.. Image:: ../images/CCS-GP57x-EVM-Custom-Confirm.png +.. Image:: /images/CCS-GP57x-EVM-Custom-Confirm.png | Install Latest Emulation Package and Sitara Device Support Package @@ -67,12 +67,12 @@ Install Latest Emulation Package and Sitara Device Support Package 1. In CCS, navigate to Help -> Check for Updates and select "Sitara device support" and "TI Emulators" and click Next. - .. image:: ../images/TMDX654_EVM_Hardware_Setup/CCS_Check_for_Updates.PNG + .. image:: /images/TMDX654_EVM_Hardware_Setup/CCS_Check_for_Updates.PNG 2. Click "Next" again, select "I accept the terms of the license agreements" and click Finish to begin the installation. - .. image:: ../images/TMDX654_EVM_Hardware_Setup/CCS_Updating_Software.png + .. image:: /images/TMDX654_EVM_Hardware_Setup/CCS_Updating_Software.png 3. You may be prompted to restart CCS for the updates to take effect. Click "Restart Now" when prompted to complete the installation. @@ -122,7 +122,7 @@ Open new target configuration file From CCS, select "File -> New -> Target Configuration File": -.. Image:: ../images/CCS-GP437x-EVM-New-Target.png +.. Image:: /images/CCS-GP437x-EVM-New-Target.png | Select target configuration options '''''''''''''''''''''''''''''''''''' @@ -133,7 +133,7 @@ MicroUSB AB connector. Select - **Connection**: Texas Instruments XDS100v2 USB Debug Probe - **Board or Device**: EVMAM437X -.. Image:: ../images/CCS-GP437x-EVM-Configure-Target.png +.. Image:: /images/CCS-GP437x-EVM-Configure-Target.png | **Useful Tip** @@ -243,7 +243,7 @@ Save target configuration Next, save the target configuration by pressing the **Save** button: -.. Image:: ../images/CCS-GP437x-EVM-Save-Target.png +.. Image:: /images/CCS-GP437x-EVM-Save-Target.png | Test target configuration '''''''''''''''''''''''''' @@ -252,14 +252,14 @@ Next, test the target configuration by pressing the **Test Connection** button. This will confirm that you have successfully created an emulator connection with your board. -.. Image:: ../images/AM4-GP-test-connection.png +.. Image:: /images/AM4-GP-test-connection.png | View target configurations ''''''''''''''''''''''''''' From CCS, select "View -> Target Configurations": -.. Image:: ../images/CCS-GP437x-EVM-View-Target.png +.. Image:: /images/CCS-GP437x-EVM-View-Target.png | Launch target configuration '''''''''''''''''''''''''''' @@ -267,7 +267,7 @@ Launch target configuration Open "User Defined" list and right click on the target configuration file that was just saved and select "Launch Selected Configuration": -.. Image:: ../images/CCS-GP437x-EVM-Launch-Target.png +.. Image:: /images/CCS-GP437x-EVM-Launch-Target.png | Connect target ''''''''''''''' @@ -275,7 +275,7 @@ Connect target After launch, you can connect to a core. For GP AM437x EVM, select **Cortex A9** and select "Connect Target": -.. Image:: ../images/CCS-GP437x-EVM-Connnect-Target.png +.. Image:: /images/CCS-GP437x-EVM-Connnect-Target.png | @@ -286,7 +286,7 @@ After connecting to target, check the console for status. Typically, the end of the configuration will indicate success or failure. For GP AM437x EVM, you will see the message "AM437x GP EVM Initialization is Done": -.. Image:: ../images/CCS-GP437x-EVM-Run-Target.png +.. Image:: /images/CCS-GP437x-EVM-Run-Target.png | Additional Notes for AM57x """"""""""""""""""""""""""" @@ -310,7 +310,7 @@ MULTICORE Initialization** enable the corresponding sub system clock. For example, enable ``DSP11SSClkEnable_API`` for the first DSP core. After running the clock enable option, you can connect to the core. -.. Image:: ../images/Multicore-Enable.jpg +.. Image:: /images/Multicore-Enable.jpg | Timer Suspend Control Options for DSP ''''''''''''''''''''''''''''''''''''''' @@ -333,7 +333,7 @@ Due to this issue the SYS/BIOS developers will need to configure an additional CCS configuration check to connect the GPTimer suspend control signal to the DSP as shown in the image below: -.. Image:: ../images/GPtimer5_DSPConnect.png +.. Image:: /images/GPtimer5_DSPConnect.png | diff --git a/source/rtos/How_to_Guides/Host/Setup/_TI_RTOS_Tips_and_Tricks.rst b/source/rtos/How_to_Guides/Host/Setup/_TI_RTOS_Tips_and_Tricks.rst index e78fdbeeb..f177a2ea6 100644 --- a/source/rtos/How_to_Guides/Host/Setup/_TI_RTOS_Tips_and_Tricks.rst +++ b/source/rtos/How_to_Guides/Host/Setup/_TI_RTOS_Tips_and_Tricks.rst @@ -77,7 +77,7 @@ Where does TI RTOS application get the Platform definition and memory sections o When creating a TI RTOS project, the user is required to specify the Platform and target core as part of their RTSC setup as shown below. This shows an example that is created for evmAM335x platform. -.. Image:: ../images/Platfrom_configuration.png +.. Image:: /images/Platfrom_configuration.png :scale: 50 % Selection of the platform essentially tell the build tools that the platform defintion should be picked up from the platform for evmAM335x from the directory path bios_x_xx_xx_xx\packages\ti\platforms\evmAM3359. If you open the Platform.xdc file under the folder path, you can see the default settings provided for this platform. This file combines the baseline AM335x SOC definition under bios_x_xx_xx_xx\packages\ti\catalog\arm\cortexa with the board specific setting like clockrate, DDR memory range. @@ -301,12 +301,12 @@ What are the different clock and timer modules in TI RTOS that you should be awa **BIOS Timer Architecture** -.. Image:: ../images/BIOS_Timer_Architecture.png +.. Image:: /images/BIOS_Timer_Architecture.png :scale: 50 % **BIOS Clock Architecture** -.. Image:: ../images/BIOS_Clock_Architecture.png +.. Image:: /images/BIOS_Clock_Architecture.png :scale: 50 % @@ -457,7 +457,7 @@ In order to get the UIA loggging enabled, you need to include the UIA module and **System analyzer view :** -.. Image:: ../images/System_Analyzer_Execution_log.png +.. Image:: /images/System_Analyzer_Execution_log.png **For more information refer to :** `System Analyzer wiki `__ @@ -484,15 +484,15 @@ Real Time analysis(RTA) agent #. Run the application. #. In the Raw Logs window, you can see the informational, warning, and error messages sent by the calls to Log module APIs in log.c. The messages that begin with **LM** are diagnostics provided by XDCtools. Messages that begin with “WARNING” come from calls to Log_warning2. Messages that begin with “ERROR” come from calls to Log_error2. Messages that begin with “../log.c” come from calls to Log_info0 and Log_info2 (depending on the number of arguments). -.. Image:: ../images/SYSBIOS_Diag.jpg +.. Image:: /images/SYSBIOS_Diag.jpg :scale: 50 % -.. Image:: ../images/SYSBIOS_Rawlog.jpg +.. Image:: /images/SYSBIOS_Rawlog.jpg :scale: 50 % -.. Image:: ../images/Rta_exec2.png +.. Image:: /images/Rta_exec2.png -.. Image:: ../images/SYSBIOS_CPUload.jpg +.. Image:: /images/SYSBIOS_CPUload.jpg :scale: 50 % For advanced debugging options we recommend following the instructions on the `BIOS_6_Real-Time_Analysis_(RTA)_in_CCSv4 `__ wiki @@ -504,7 +504,7 @@ RTOS Object View(ROV) #. Load your application for debugging. Select the device you want to debug before opening ROV. #. In the ROV window, expand the tree to see the ti.sysbios.knl.Task module. The right pane shows a list of the Task threads in the application. As you advance from breakpoint to breakpoint, you see the run mode of the threads change. -.. Image:: ../images/1.7.6_Image.png +.. Image:: /images/1.7.6_Image.png :scale: 50 % For more details on ROV tools, refer to the `Runtime Object Viewer(ROV) `__ article on RTSC website. diff --git a/source/rtos/How_to_Guides/Host/System_Integration/_Create_DSP_and_IPU_FW_using_PDK_and_IPC_to_load_from_ARM_AM57xx.rst b/source/rtos/How_to_Guides/Host/System_Integration/_Create_DSP_and_IPU_FW_using_PDK_and_IPC_to_load_from_ARM_AM57xx.rst index dfdc56158..1e7a1c288 100644 --- a/source/rtos/How_to_Guides/Host/System_Integration/_Create_DSP_and_IPU_FW_using_PDK_and_IPC_to_load_from_ARM_AM57xx.rst +++ b/source/rtos/How_to_Guides/Host/System_Integration/_Create_DSP_and_IPU_FW_using_PDK_and_IPC_to_load_from_ARM_AM57xx.rst @@ -121,7 +121,7 @@ the remotecores(DSP's and M4's) run a RTOS. In the normal operation, boot loader(U-Boot/SPL) boots and loads the A15 with the HLOS. The A15 boots the DSP and the M4 cores. -.. Image:: ../images/Normal-boot.png +.. Image:: /images/Normal-boot.png In this sequence, the interval between the Power on Reset and the remotecores (i.e. the DSP's and the M4's) executing is dependent on the @@ -136,7 +136,7 @@ The figure below illustrates how remoteproc/rpmsg driver from ARM Linux kernel communicates with IPC driver on slave processor (e.g. DSP, IPU, etc) running RTOS. -.. Image:: ../images/LinuxIPC_with_RTOS_Slave.png +.. Image:: /images/LinuxIPC_with_RTOS_Slave.png In order to setup IPC on slave cores, we provide some pre-built examples in IPC package that can be run from ARM Linux. The subsequent sections @@ -463,7 +463,7 @@ its local EDMA. They both serve the same purpose of translating virtual addresses (i.e. the addresses as viewed by the DSP subsystem) into physical addresses (i.e. addresses as viewed from the L3 interconnect). -.. Image:: ../images/LinuxIpcDspMmu.png +.. Image:: /images/LinuxIpcDspMmu.png .. rubric:: DSP Physical Addresses :name: dsp-physical-addresses @@ -740,7 +740,7 @@ The first column tells us whether the mapping is a Level 1 or Level 2 descriptor. All the lines above are a first level descriptor, so we look at the associated format from the TRM: -.. Image:: ../images/LinuxIpcPageTableDescriptor1.png +.. Image:: /images/LinuxIpcPageTableDescriptor1.png The "da" ("device address") column reflects the virtual address. It is *derived* from the index into the table, i.e. there does not exist a @@ -775,7 +775,7 @@ Subsystems, it's helpful to recognize that there are two distinct/independent levels of memory translation. Here's a snippet from the TRM to illustrate: -.. Image:: ../images/LinuxIpcIpuMmu.png +.. Image:: /images/LinuxIpcIpuMmu.png .. rubric:: Cortex M4 IPU Physical Addresses :name: cortex-m4-ipu-physical-addresses @@ -1950,7 +1950,7 @@ examples setup the memory access using these MMUs which the users need to manage when integrating the components. This difference is highlighted below: -.. Image:: ../images/IPU_MMU_Peripheral_access.png +.. Image:: /images/IPU_MMU_Peripheral_access.png - PDK examples use addresses (0x4X000000) to peripheral registers and use following MMU setting diff --git a/source/rtos/How_to_Guides/Host/System_Integration/_IPC_Debugging_Tools_and_Techniques_on_AM57xx.rst b/source/rtos/How_to_Guides/Host/System_Integration/_IPC_Debugging_Tools_and_Techniques_on_AM57xx.rst index 8229f64cd..c9a5d720b 100644 --- a/source/rtos/How_to_Guides/Host/System_Integration/_IPC_Debugging_Tools_and_Techniques_on_AM57xx.rst +++ b/source/rtos/How_to_Guides/Host/System_Integration/_IPC_Debugging_Tools_and_Techniques_on_AM57xx.rst @@ -620,14 +620,14 @@ type of exception that occurred, but often provides a fault address to identify A dump of the register contents at the time of the exception is also provided. -.. image:: ../images/RegisterDump.PNG +.. image:: /images/RegisterDump.PNG **Stack Trace** The stack trace is also provided (see Figure 6). This can be used in conjunction with the source code and the map file or CCS to get more information about what was executing at the time of the crash. -.. image:: ../images/StackTraceDump.PNG +.. image:: /images/StackTraceDump.PNG MMU Faults """""""""" @@ -671,7 +671,7 @@ an access to an un-mapped area. Here is an example fault dump: -.. image:: ../images/StackTraceDump2.PNG +.. image:: /images/StackTraceDump2.PNG From the crash dump, the fault address is 0x96000000. The address will not be found in the resource table, which is why the fault occurred. @@ -695,13 +695,13 @@ Find the corresponding function by looking this address up in the map file for t PC address is invalid due to an issue such as stack corruption, then this may not yield useful results. In this case, something useful is found: -.. image:: ../images/SourceInsightCrashDump.PNG +.. image:: /images/SourceInsightCrashDump.PNG Alternatively, use CCS to see the location of the fault. If CCS was already connected to the remote core before the fault happened, the core will have halted in the abort function. From here, directly set the PC address and see the line that caused the fault: -.. image:: ../images/CCSFault.PNG +.. image:: /images/CCSFault.PNG Use this technique at any time after booting the remote core to see what a PC address corresponds to. It will display the line that caused the error. This may, however, prevent proper execution because the diff --git a/source/rtos/How_to_Guides/Target/_C66x_Reset_from_A15_Running_Linux.rst b/source/rtos/How_to_Guides/Target/_C66x_Reset_from_A15_Running_Linux.rst index 40cf33523..b04b46fbe 100644 --- a/source/rtos/How_to_Guides/Target/_C66x_Reset_from_A15_Running_Linux.rst +++ b/source/rtos/How_to_Guides/Target/_C66x_Reset_from_A15_Running_Linux.rst @@ -15,35 +15,35 @@ Linux running on the A15. 1) Once Linux has booted, launch the target configuration. -.. Image:: ../images/Outofreset_1_lali.JPG +.. Image:: /images/Outofreset_1_lali.JPG 2) With the target configuration launched, right click on K2x.ccxml and select “Show all cores” -.. Image:: ../images/Outofreset_2_lali.JPG +.. Image:: /images/Outofreset_2_lali.JPG 3) This will bring up the Non-Debuggable Devices section. Right click and connect the CS_DAP_Debug_SS core. -.. Image:: ../images/Outofreset_3_lali.JPG +.. Image:: /images/Outofreset_3_lali.JPG 4) Go to Tools>GEL files and load the evmk2x.gel file by right clicking on the GEL file window. The Gel file would typically be located in the CCS installation under \\ccsv6\\ccs_base\\emulation\\boards\\evmk2x\\gel\\ -.. Image:: ../images/Outofreset_4_lali.png +.. Image:: /images/Outofreset_4_lali.png 5) Once the GEL has been successfully loaded, go to Scripts>default and select K2x_TakeDSPOutofReset. -.. Image:: ../images/Outofreset_5_lali.png +.. Image:: /images/Outofreset_5_lali.png 6) At this point the console would indicate that the DSP is out of reset. -.. Image:: ../images/Outofreset_6_lali.png +.. Image:: /images/Outofreset_6_lali.png 7) Now the DSP cores can be right-clicked and connected successfully. -.. Image:: ../images/Outofreset_7_lali.png +.. Image:: /images/Outofreset_7_lali.png Target Configuration -------------------- @@ -54,5 +54,5 @@ Target Configuration the gel is NOT preloaded on the DSP core in the ccxml by leaving the initialization script blank. -.. Image:: ../images/Outofreset_8_lali.JPG +.. Image:: /images/Outofreset_8_lali.JPG diff --git a/source/rtos/How_to_Guides/Target/_External_Input_Trigger_Interrupt_AM57x.rst b/source/rtos/How_to_Guides/Target/_External_Input_Trigger_Interrupt_AM57x.rst index 740a95431..fb5dece50 100644 --- a/source/rtos/How_to_Guides/Target/_External_Input_Trigger_Interrupt_AM57x.rst +++ b/source/rtos/How_to_Guides/Target/_External_Input_Trigger_Interrupt_AM57x.rst @@ -13,8 +13,8 @@ user guide `__, the card has 3 p • The Pin 4 signal is labeled as GPMC_CS0 and is connected to AM572x chip ball T1 as shown in the schematic: -.. Image:: ../images/J21_gpio_input.png -.. Image:: ../images/gpmc_cs0_t1.png +.. Image:: /images/J21_gpio_input.png +.. Image:: /images/gpmc_cs0_t1.png • From the AM5728 datasheet, T1 ball can be configured as GPMC_CS0 or GPIO2_19 based on different PINMUX modes. @@ -34,12 +34,12 @@ The default PinMux file has to be modified for GPIO2_19 pin usage: • Use the PinMux Utility to open the default PinMux file pdk_am57xx_1_0_x\\packages\\ti\\board\\src\\idkAM572x\\idkAM572x_SR2.0.pinmux (for the latest Rev 1.3B EVM) • Select GPIO, then MyGPIO2: -.. Image:: ../images/pinmux_gpio_1.png +.. Image:: /images/pinmux_gpio_1.png • Then, scroll down, set gpio2_19 with ball #T1, pull up and Rx direction. • Finally, select Category filter as “SR2.0 – Platform Development Kit (PDK) and download the generated files. -.. Image:: ../images/pinmux_gpio_2.png +.. Image:: /images/pinmux_gpio_2.png • Four new files should be generated, with the only difference being a new pin configuration added in boardPadDelayInit.c file: @@ -136,7 +136,7 @@ Test **Test Setup** The test setup using AM572x IDK EVM is depicted below: -.. Image:: ../images/gpio_test.png +.. Image:: /images/gpio_test.png • The EVM is powered with a +5V power supply • A micro USB cable is connected to the host PC for on-board XDS100v2 JTAG connection and UART console. diff --git a/source/rtos/How_to_Guides/Target/_Run_IPC_Examples_on_AM572x.rst b/source/rtos/How_to_Guides/Target/_Run_IPC_Examples_on_AM572x.rst index 8a7a7d1f5..0df7f0976 100644 --- a/source/rtos/How_to_Guides/Target/_Run_IPC_Examples_on_AM572x.rst +++ b/source/rtos/How_to_Guides/Target/_Run_IPC_Examples_on_AM572x.rst @@ -125,7 +125,7 @@ variable name and its value. 12. Suspend (halt) DSP1 to view test messages on ROV Viewable Modules -->LoggerBuf Refer below image of ROV log messages. -.. Image:: ../images/Hello_dsp2.png +.. Image:: /images/Hello_dsp2.png 13. Suspend (halt) DSP2 and click on ROV icon to view log messages. @@ -181,7 +181,7 @@ World example environment varaible settings for reference. 12. Suspend (halt) ARM Cortex_A15 to view test messages on ROV Viewable Modules -->LoggerBuf Refer the following ROV message queue screenshot -.. Image:: ../images/MesgQ_arm0.png +.. Image:: /images/MesgQ_arm0.png 13. Suspend (halt) DSP1 and click on ROV icon to view log messages. @@ -240,7 +240,7 @@ wait on multiple input sources. 12. Suspend (halt) ARM CortexA15_0 to view test messages on ROV Viewable Modules -->LoggerBuf. Refer the following image of ROV log messages -.. Image:: ../images/Notify_peer_arm0.png +.. Image:: /images/Notify_peer_arm0.png 13. Suspend (halt) DSP2 and click on ROV icon to view log messages. @@ -302,7 +302,7 @@ sure there is no space between variable name and its value. 14. Halt DSP1 to view test messages on ROV Viewable Modules -->LoggerBuf Refer below image of ROV log messages -.. Image:: ../images/Ping_dsp1.png +.. Image:: /images/Ping_dsp1.png 15. Suspend (halt) DSP2 and click on ROV icon to view log messages. diff --git a/source/rtos/Overview/_Directory_Structure.rst b/source/rtos/Overview/_Directory_Structure.rst index c2c01e51a..c66ea899c 100644 --- a/source/rtos/Overview/_Directory_Structure.rst +++ b/source/rtos/Overview/_Directory_Structure.rst @@ -15,7 +15,7 @@ Software Component Directories ================================ Here is a sample directory layout for the AM57x RTOS SDK: -.. Image:: ../images/Processor-SDK-RTOS-directories.png +.. Image:: /images/Processor-SDK-RTOS-directories.png | @@ -33,7 +33,7 @@ The default SDK Install Path is ``C:\TI`` for Windows and This directory contains the following top-level directories and files; here is an example for AM57x: -.. Image:: ../images/Processor-SDK-RTOS-directory-top.png +.. Image:: /images/Processor-SDK-RTOS-directory-top.png These directories contain the collateral and tools applicable for RTOS: diff --git a/source/rtos/Overview/_Examples_and_Demonstrations.rst b/source/rtos/Overview/_Examples_and_Demonstrations.rst index 795917c1d..cd080cbfe 100644 --- a/source/rtos/Overview/_Examples_and_Demonstrations.rst +++ b/source/rtos/Overview/_Examples_and_Demonstrations.rst @@ -278,7 +278,7 @@ X The default SDK Install Path is ``C:\TI`` for Windows and ``/home/[user]/ti`` for Linux. -.. Image:: ../images/Processor-SDK-RTOS-directory-top.png +.. Image:: /images/Processor-SDK-RTOS-directory-top.png | diff --git a/source/rtos/Overview/_Getting_Started_Guide.rst b/source/rtos/Overview/_Getting_Started_Guide.rst index a5becb095..2752e808b 100644 --- a/source/rtos/Overview/_Getting_Started_Guide.rst +++ b/source/rtos/Overview/_Getting_Started_Guide.rst @@ -258,7 +258,7 @@ http://www.freedownloadmanager.org/. Code Composer Studio ----------------------- -.. Image:: ../images/Ccsv7splash.jpg +.. Image:: /images/Ccsv7splash.jpg The Processor-SDK RTOS uses *Code Composer Studio* as the host integrated development environment for development and debug. All @@ -282,7 +282,7 @@ download page for your platform (see links in below section). When installing CCS, you can choose to control what is installed for processor architecture. -.. Image:: ../images/Processor-SDK_CCSv7-Setup-Processor-Support.png +.. Image:: /images/Processor-SDK_CCSv7-Setup-Processor-Support.png The minimum required for the SDK are the following items @@ -318,7 +318,7 @@ The relevant update will be named For example, an update for Sitara devices will look like: -.. Image:: ../images/Processor-SDK_CCS-Emu-Update.png +.. Image:: /images/Processor-SDK_CCS-Emu-Update.png Processor-SDK for RTOS ------------------------ diff --git a/source/rtos/Overview/_Software_Stack.rst b/source/rtos/Overview/_Software_Stack.rst index 4118b3d3c..5b9f2ad05 100644 --- a/source/rtos/Overview/_Software_Stack.rst +++ b/source/rtos/Overview/_Software_Stack.rst @@ -16,7 +16,7 @@ quickly utilize different peripherals accessible from an SOC. Software Block Diagram ======================== -.. Image:: ../images/RTOS-Software-Architecture.png +.. Image:: /images/RTOS-Software-Architecture.png | diff --git a/source/rtos/PDK_Platform_Software/Boot_Board_and_EVM_Abstractions/_BOOT_AM57x.rst b/source/rtos/PDK_Platform_Software/Boot_Board_and_EVM_Abstractions/_BOOT_AM57x.rst index 0e88fdaa6..344233a2a 100644 --- a/source/rtos/PDK_Platform_Software/Boot_Board_and_EVM_Abstractions/_BOOT_AM57x.rst +++ b/source/rtos/PDK_Platform_Software/Boot_Board_and_EVM_Abstractions/_BOOT_AM57x.rst @@ -104,7 +104,7 @@ The Am57xImageGen script uses out2rprc and multicoreImageGen format conversion tools to create the final application image. Graphical view of the multicore application image is provided below: -.. Image:: ../images/Multicore_app_image.png +.. Image:: /images/Multicore_app_image.png The script creates the bootable image in 2 steps @@ -590,7 +590,7 @@ at $(TI_PDK_INSTALL_DIR)/packages/ti/boot/sbl/binary/[BOARD]/mmcsd) On Successful bootup you should see the following logs on the UART console for a AM572x based board. -.. Image:: ../images/Sbl_example.jpg +.. Image:: /images/Sbl_example.jpg .. note:: MPU Core 0 example does a sequential check of mailbox messages sent from @@ -618,7 +618,7 @@ memory utilization in the boot loader. The SBL memory map is shown below -.. Image:: ../images/SBL_memory_map.png +.. Image:: /images/SBL_memory_map.png .. note:: - After the application boots and is running on the SOC, it is free to diff --git a/source/rtos/PDK_Platform_Software/Boot_Board_and_EVM_Abstractions/_BOOT_AM65x_J721E.rst b/source/rtos/PDK_Platform_Software/Boot_Board_and_EVM_Abstractions/_BOOT_AM65x_J721E.rst index e19b41687..c7f930335 100644 --- a/source/rtos/PDK_Platform_Software/Boot_Board_and_EVM_Abstractions/_BOOT_AM65x_J721E.rst +++ b/source/rtos/PDK_Platform_Software/Boot_Board_and_EVM_Abstractions/_BOOT_AM65x_J721E.rst @@ -102,14 +102,14 @@ The SBL is in turn used by the board framework to load and start diagnostics Block Diagram ^^^^^^^^^^^^^^^^ -.. Image:: ../images/k3_sbl_arch_block_diag.png +.. Image:: /images/k3_sbl_arch_block_diag.png .. _am655x-sbl-memory-usage: Memory Map ^^^^^^^^^^^ -.. Image:: ../images/k3_sbl_mem_usage.png +.. Image:: /images/k3_sbl_mem_usage.png .. _am655x-sbl-directory-structure: @@ -258,7 +258,7 @@ Two utilities - out2rprc and multicoreImageGen are used to convert an applicatio image(s) into an image loadable by the SBL. The structure of a multicore application image is provided below: -.. Image:: ../images/Multicore_app_image.png +.. Image:: /images/Multicore_app_image.png **RPRC File Header Format** diff --git a/source/rtos/PDK_Platform_Software/Boot_Board_and_EVM_Abstractions/_BOOT_C66x.rst b/source/rtos/PDK_Platform_Software/Boot_Board_and_EVM_Abstractions/_BOOT_C66x.rst index 470d11b22..877100002 100644 --- a/source/rtos/PDK_Platform_Software/Boot_Board_and_EVM_Abstractions/_BOOT_C66x.rst +++ b/source/rtos/PDK_Platform_Software/Boot_Board_and_EVM_Abstractions/_BOOT_C66x.rst @@ -265,7 +265,7 @@ Boot Modes NAND Boot """""""""""" -.. Image:: ../images/Nandboot.jpg +.. Image:: /images/Nandboot.jpg NAND boot is a multi-stage process which is designed to boot an application from NAND flash after reset. Figure below illustrates the @@ -290,7 +290,7 @@ modified and re-programmed to EEPROM. NOR Boot """""""""""" -.. Image:: ../images/Norboot.jpg +.. Image:: /images/Norboot.jpg NOR boot is a multi-stage process which is designed to boot an application from NOR flash after reset. Figure below illustrates the @@ -312,7 +312,7 @@ parameter index dip switch, maximum 2 boot images can be supported. TFTP Boot """""""""""" -.. Image:: ../images/Emacboot.jpg +.. Image:: /images/Emacboot.jpg EMAC boot is a multi-stage process which is designed to boot an application from TFTP server after reset. Figure below illustrates the diff --git a/source/rtos/PDK_Platform_Software/Boot_Board_and_EVM_Abstractions/_BOOT_K2G.rst b/source/rtos/PDK_Platform_Software/Boot_Board_and_EVM_Abstractions/_BOOT_K2G.rst index e74572dae..92ef98ee4 100644 --- a/source/rtos/PDK_Platform_Software/Boot_Board_and_EVM_Abstractions/_BOOT_K2G.rst +++ b/source/rtos/PDK_Platform_Software/Boot_Board_and_EVM_Abstractions/_BOOT_K2G.rst @@ -141,7 +141,7 @@ Booting via SD Card | Below is an example of K2G SBL successfully booting the diagnostic application: -.. Image:: ../images/K2g_boot_diag.jpg +.. Image:: /images/K2g_boot_diag.jpg QSPI Boot Mode """""""""""""""" @@ -219,7 +219,7 @@ SBL uses the last 0x40000 memory from MSMC RAM memory. The SBL memory map is shown below: -.. Image:: ../images/SBL_mem_k2g.jpg +.. Image:: /images/SBL_mem_k2g.jpg .. note:: app should not have loadable sections residing in SBL memory region to diff --git a/source/rtos/PDK_Platform_Software/Boot_Board_and_EVM_Abstractions/_BOOT_OMAPL13x.rst b/source/rtos/PDK_Platform_Software/Boot_Board_and_EVM_Abstractions/_BOOT_OMAPL13x.rst index 3ecd5e3f8..2d367ca60 100644 --- a/source/rtos/PDK_Platform_Software/Boot_Board_and_EVM_Abstractions/_BOOT_OMAPL13x.rst +++ b/source/rtos/PDK_Platform_Software/Boot_Board_and_EVM_Abstractions/_BOOT_OMAPL13x.rst @@ -206,7 +206,7 @@ Booting via SPI Below is an example of OMAPL137 SBL successfully booting the GPIO LED blink application -.. Image:: ../images/Omapl137_boot_example.jpg +.. Image:: /images/Omapl137_boot_example.jpg | @@ -328,7 +328,7 @@ Booting via MMCSD Below is an example of OMAPL138 SBL successfully booting the GPIO LED blink application -.. Image:: ../images/Omapl138_boot_example.png +.. Image:: /images/Omapl138_boot_example.png | diff --git a/source/rtos/PDK_Platform_Software/Boot_Board_and_EVM_Abstractions/_Diagnostics.rst b/source/rtos/PDK_Platform_Software/Boot_Board_and_EVM_Abstractions/_Diagnostics.rst index 4c79d2f85..30882865d 100644 --- a/source/rtos/PDK_Platform_Software/Boot_Board_and_EVM_Abstractions/_Diagnostics.rst +++ b/source/rtos/PDK_Platform_Software/Boot_Board_and_EVM_Abstractions/_Diagnostics.rst @@ -196,7 +196,7 @@ To do so: You should see the following screen when board is bootted with diagnostic binaries in SD card: -.. Image:: ../images/Diag-screen1.jpg +.. Image:: /images/Diag-screen1.jpg The framework diagnostic application should be loaded through SBL, and gives you the options: @@ -207,11 +207,11 @@ gives you the options: Below is an example of running a diagnostic application: -.. Image:: ../images/Diag-screen2.jpg +.. Image:: /images/Diag-screen2.jpg Result of return from above run: -.. Image:: ../images/Diag-screen3.png +.. Image:: /images/Diag-screen3.png Loading through SPI Flash ^^^^^^^^^^^^^^^^^^^^^^^^^^^ @@ -246,7 +246,7 @@ SPI flash. To do so: Sample CCS output of SPI flash writer is shown below: -.. Image:: ../images/Spi_flash_writer_output.jpg +.. Image:: /images/Spi_flash_writer_output.jpg | @@ -260,7 +260,7 @@ Sample CCS output of SPI flash writer is shown below: You should see the following screen: -.. Image:: ../images/Amic110_ice_spi_boot_diag1.jpg +.. Image:: /images/Amic110_ice_spi_boot_diag1.jpg | | The framework diagnostic application should be loaded through SBL, and @@ -272,12 +272,12 @@ You should see the following screen: Below is an example of running a diagnostic application: -.. Image:: ../images/Amic110_ice_spi_boot_diag2.jpg +.. Image:: /images/Amic110_ice_spi_boot_diag2.jpg | | Result of return from above run: -.. Image:: ../images/Amic110_ice_spi_boot_diag3.jpg +.. Image:: /images/Amic110_ice_spi_boot_diag3.jpg | diff --git a/source/rtos/PDK_Platform_Software/Boot_Board_and_EVM_Abstractions/_Uniflash.rst b/source/rtos/PDK_Platform_Software/Boot_Board_and_EVM_Abstractions/_Uniflash.rst index ebcc5ee69..f200d2b30 100644 --- a/source/rtos/PDK_Platform_Software/Boot_Board_and_EVM_Abstractions/_Uniflash.rst +++ b/source/rtos/PDK_Platform_Software/Boot_Board_and_EVM_Abstractions/_Uniflash.rst @@ -154,7 +154,7 @@ Manual loading of the flash programmer through CCS is required for few cases. Below diagram shows the execution steps for flashing the application images based on the Uniflash supported mode for downloading the flash programmer. -.. Image:: ../images/Uniflash_Execution_Steps.png +.. Image:: /images/Uniflash_Execution_Steps.png :width: 650px :align: center :height: 1000px diff --git a/source/rtos/PDK_Platform_Software/Device_Drivers/_EMAC.rst b/source/rtos/PDK_Platform_Software/Device_Drivers/_EMAC.rst index 0e0ed24dc..8a23ef598 100644 --- a/source/rtos/PDK_Platform_Software/Device_Drivers/_EMAC.rst +++ b/source/rtos/PDK_Platform_Software/Device_Drivers/_EMAC.rst @@ -140,7 +140,7 @@ Note that prior to running these tests on Maxwell with interposer card, please h .. rubric:: Interposer Layout :name: Interposer Layout -.. Image:: ../images/Interposer.png +.. Image:: /images/Interposer.png Example and Test Applications ------------------------------ @@ -530,7 +530,7 @@ EMAC Test applications demonstrates the key features of the driver. EMAC Test applications can also be run via SBL. To run via SBL, please following the instructions as specified in the following link: `SBL User Guide `__ -.. _files: :download:`<../images/Pcap.zip>` +.. _files: :download:`` Additional References ---------------------- diff --git a/source/rtos/PDK_Platform_Software/Device_Drivers/_HYPLNK.rst b/source/rtos/PDK_Platform_Software/Device_Drivers/_HYPLNK.rst index 3575a3961..bad61d4f8 100644 --- a/source/rtos/PDK_Platform_Software/Device_Drivers/_HYPLNK.rst +++ b/source/rtos/PDK_Platform_Software/Device_Drivers/_HYPLNK.rst @@ -86,7 +86,7 @@ and the cable is also required. Below is a picture showing how a K2H EVM is connected to a 6678 EVM via breakout card and cable. -.. Image:: ../images/K2-k1-hyplnk.jpg +.. Image:: /images/K2-k1-hyplnk.jpg +-----------------+-----------------+-----------------+-----------------+ | Name | Description | EVM | Expected | diff --git a/source/rtos/PDK_Platform_Software/Device_Drivers/_IPCLLD.rst b/source/rtos/PDK_Platform_Software/Device_Drivers/_IPCLLD.rst index 622aa94c9..7626bd420 100644 --- a/source/rtos/PDK_Platform_Software/Device_Drivers/_IPCLLD.rst +++ b/source/rtos/PDK_Platform_Software/Device_Drivers/_IPCLLD.rst @@ -54,7 +54,7 @@ It can also be cloned using following git command: The file and directory oraganization are as below. - .. image:: ../images/ipclld_file_org.png + .. image:: /images/ipclld_file_org.png :height: 944 :width: 435 @@ -170,7 +170,7 @@ Remote firmware can be loading using CCS or using uBoot SPL. * Run the script using following command (example below is for J721E, use the appropriate one for your target) - loadJSFile("PDK_INSTALL_DIR/packages/ti/drv/sciclient/tools/ccsLoadDmsc/j721e/launch.js") - .. image:: ../images/ipclld_LoadingSysFw_sciclient.png + .. image:: /images/ipclld_LoadingSysFw_sciclient.png :height: 160 :width: 941 * Connect the cores @@ -181,7 +181,7 @@ Remote firmware can be loading using CCS or using uBoot SPL. * Run the cores. * After running the cores, the sample output should look something like below. - .. image:: ../images/ipclld_Sample_output_mpu.png + .. image:: /images/ipclld_Sample_output_mpu.png :height: 377 :width: 672 @@ -221,13 +221,13 @@ In this section ipc_echo_test is used to demonstrate, but same instructions appl - modprobe rpmsg_client_sample count=5 - .. image:: ../images/ipclld_Linux_Start.png + .. image:: /images/ipclld_Linux_Start.png :height: 270 :width: 581 3) After running the sample app, it should display something below - .. image:: ../images/ipclld_linux_output.png + .. image:: /images/ipclld_linux_output.png :height: 796px :width: 983px @@ -257,7 +257,7 @@ Typical Data-Flow in IPCLLD communication between two cores Following picture illustrates the data flow between two cores using mailbox IP as transport. -.. image:: ../images/ipclld_data_flow.png +.. image:: /images/ipclld_data_flow.png :height: 470 :width: 687 diff --git a/source/rtos/PDK_Platform_Software/Device_Drivers/_MCASP.rst b/source/rtos/PDK_Platform_Software/Device_Drivers/_MCASP.rst index bd1983524..561d1d79a 100644 --- a/source/rtos/PDK_Platform_Software/Device_Drivers/_MCASP.rst +++ b/source/rtos/PDK_Platform_Software/Device_Drivers/_MCASP.rst @@ -94,7 +94,7 @@ simplicity. This is applicable if only one serializer and one timeslot is used. The samples are ordered in the order they received or sent. -.. Image:: ../images/1SLOT_1SER.PNG +.. Image:: /images/1SLOT_1SER.PNG .. rubric:: Mcasp_BufferFormat_1SER_MULTISLOT_INTERLEAVED :name: mcasp_bufferformat_1ser_multislot_interleaved @@ -105,7 +105,7 @@ memory as below. Different timeslots' samples are denoted by different colors and are labelled t1,t2..tn according to the time they arrive at the serializer. -.. Image:: ../images/1SER_MULTISLOT_INTERLEAVED.PNG +.. Image:: /images/1SER_MULTISLOT_INTERLEAVED.PNG .. rubric:: Mcasp_BufferFormat_1SER_MULTISLOT_NON_INTERLEAVED :name: mcasp_bufferformat_1ser_multislot_non_interleaved @@ -116,7 +116,7 @@ of the timeslot and stored in the memory as shown below. Different timeslots' samples are denoted by different colors and are labelled t1,t2..tn according to the time they arrive at the serializer. -.. Image:: ../images/1SER_MULTISLOT_NON_INTERLEAVED.PNG +.. Image:: /images/1SER_MULTISLOT_NON_INTERLEAVED.PNG NOTE: if the non-interleaved format is used, the Mcasp_ChanParams-> hwFifoEventDMARatio must be set to 1. @@ -131,7 +131,7 @@ below Different serializers' samples are denoted by different colors and are labelled S1,S2..Sn according to the time they arrive at the serializer. -.. Image:: ../images/1SER_MULTISER_1SLOT_SER_INTERLEAVED_2.PNG +.. Image:: /images/1SER_MULTISER_1SLOT_SER_INTERLEAVED_2.PNG | @@ -145,7 +145,7 @@ as shown below Different serializers' samples are denoted by different colors and are labelled S1,S2..Sn according to the time they arrive at the serializer. -.. Image:: ../images/1SER_MULTISER_1SLOT_SER_NON_INTERLEAVED.PNG +.. Image:: /images/1SER_MULTISER_1SLOT_SER_NON_INTERLEAVED.PNG .. rubric:: Mcasp_BufferFormat_MULTISER_MULTISLOT_SEMI_INTERLEAVED_1 :name: mcasp_bufferformat_multiser_multislot_semi_interleaved_1 @@ -157,7 +157,7 @@ example, there are 3 serializers and 2 timeslots per serializers whose samples are noted by Ln (left) and Rn (right). Different serializers' samples are denoted by different colors. -.. Image:: ../images/1SER_MULTISER_MULTISLOT_SEMI_INTERLEAVED_1_UPDATED.PNG +.. Image:: /images/1SER_MULTISER_MULTISLOT_SEMI_INTERLEAVED_1_UPDATED.PNG .. rubric:: Mcasp_BufferFormat_MULTISER_MULTISLOT_SEMI_INTERLEAVED_2 :name: mcasp_bufferformat_multiser_multislot_semi_interleaved_2 @@ -169,7 +169,7 @@ shown below. In this example, there are 3 serializers and 2 timeslots per serializers whose samples are noted by Ln (left) and Rn (right).Different serializers' samples are denoted by different colors. -.. Image:: ../images/1SER_MULTISER_MULTISLOT_SEMI_INTERLEAVED_2.PNG +.. Image:: /images/1SER_MULTISER_MULTISLOT_SEMI_INTERLEAVED_2.PNG NOTE: if the non-interleaved format is used, the Mcasp_ChanParams-> hwFifoEventDMARatio must be set to 1. @@ -191,12 +191,12 @@ the Mcasp_wordBitsSelect_LSB option is used. On the receiving side, the serializer holds the 32 bit data whose LSB 16 bits are picked up and packed in to the system memory. The MSB 16 bits are ignored. -.. Image:: ../images/WordSelect_LSB.PNG +.. Image:: /images/WordSelect_LSB.PNG If the Mcasp_wordBitsSelect_MSB option is used, the serializer's MSB-16bits are packed in to the system memory. The LSBs are ignored. -.. Image:: ../images/WordSelect_MSB.PNG +.. Image:: /images/WordSelect_MSB.PNG .. rubric:: Priming :name: priming diff --git a/source/rtos/PDK_Platform_Software/Device_Drivers/_SCICLIENT.rst b/source/rtos/PDK_Platform_Software/Device_Drivers/_SCICLIENT.rst index 487418117..e1ddd18e2 100644 --- a/source/rtos/PDK_Platform_Software/Device_Drivers/_SCICLIENT.rst +++ b/source/rtos/PDK_Platform_Software/Device_Drivers/_SCICLIENT.rst @@ -124,13 +124,13 @@ Modify for J721E: - Connect the Javascript to the CCXML file with the steps shown below: (Note: this step needs to be repeated if you switch workspaces or clean your workspace).The Javascript is run on re-launch of the ccxml. If you would like to run the Javascript without relaunch then you can look ahead to the section: "Re-running the script once ccxml is already launched." Click on Debug Configurations from the button as follows: -.. image:: ../images/sciclient_ccsLoad1.png +.. image:: /images/sciclient_ccsLoad1.png :height: 300 :width: 600 - Select the CCXML file from the left-hand side and populate the path to the launch_am65xx.js file in the "Initialization Script" free form field and click on "Apply". -.. image:: ../images/sciclient_ccsLoad2.png +.. image:: /images/sciclient_ccsLoad2.png :height: 300 :width: 600 diff --git a/source/rtos/PDK_Platform_Software/Device_Drivers/_USB.rst b/source/rtos/PDK_Platform_Software/Device_Drivers/_USB.rst index 5b26d1fd7..32b85d80d 100644 --- a/source/rtos/PDK_Platform_Software/Device_Drivers/_USB.rst +++ b/source/rtos/PDK_Platform_Software/Device_Drivers/_USB.rst @@ -32,7 +32,7 @@ application. After the host PC enumerates this EVM-thumb drive, the PC will see a USB storage device. This EVM-thumb drive is not yet formatted with any file system and requires user to format it before use. -.. Image:: ../images/USB_MSC_device.PNG +.. Image:: /images/USB_MSC_device.PNG The following screen shots show what one would expect when running the device mode demo application and plugging in a USB cable from the EVM @@ -40,14 +40,14 @@ USB port #0 to a PC running Windows Printout from demo application: -.. Image:: ../images/Device_mode_printout.png +.. Image:: /images/Device_mode_printout.png The MSC device is detected in Windows, and a FAT formatted USB drive named "PDK-USBDEV" should be seen in the "Window Explorer". The content of the drive is just a readme.txt file. This USB drive can be manipulated like any other removable USB drive. -.. Image:: ../images/Windows_pdk_usb.png +.. Image:: /images/Windows_pdk_usb.png Windows might show a message saying it should be scanned and fixed. We can just ignore it and just continue without scanning. @@ -62,7 +62,7 @@ manipulate files on the attached MMCSD card on the EVM. This is how it looks. Its code is similar to that of the USB device MSC example but with the call back functions calling MMCSD API's instead of RamDisk APIs -.. Image:: ../images/Usb_device_mmcsd.PNG +.. Image:: /images/Usb_device_mmcsd.PNG | @@ -75,14 +75,14 @@ interface via the EVM via UART for interaction with the example. The shell provides some basic commands to manipulate the content of the attached USB disk drive. -.. Image:: ../images/USB_MSC_host.PNG +.. Image:: /images/USB_MSC_host.PNG | Screenshot of a MSC host mode example running in RTOS after plugging in a USB thumb drive into USB port #1 -.. Image:: ../images/Host_shell_screen_shot.png +.. Image:: /images/Host_shell_screen_shot.png | @@ -99,7 +99,7 @@ mode of operation is currently supported on AM335X GP EVM, OMAP-L137 EVM and OMAP-L138 LCDK. | -.. Image:: ../images/Am335x_usb_ac_bd.jpg +.. Image:: /images/Am335x_usb_ac_bd.jpg | @@ -121,12 +121,12 @@ The bulk demo application requires a host PC with USB host plugged to the USB de port on the EVM. Depending on the platform, the USB device port might be USB port #0 or #1. -.. Image:: ../images/USB_MSC_device.PNG +.. Image:: /images/USB_MSC_device.PNG Please refer to PDK user guide for how to generate USB example projects. Once the demo application is loaded and run, the EVM UART console shows the following: -.. Image:: ../images/usb_dev_bulk_console.png +.. Image:: /images/usb_dev_bulk_console.png A Python host PC example application is provided in ti/drv/usb/example/usb_dev/bulk/usb_dev_bulk_host_application.py @@ -146,7 +146,7 @@ It does the following: A screen shot of what the Python test script outputs -.. Image:: ../images/usb_dev_bulk_host_tool_output.png +.. Image:: /images/usb_dev_bulk_host_tool_output.png The USB bulk demo application configures the USB endpoints as high speed endpoints with 512B packet size. @@ -218,13 +218,13 @@ Below diagram is the sequence of API calls that starts the USB device MSC application. All USB events are handled internally in the LLD and in the interrupt context. -.. Image:: ../images/USB_MSC_device_API_flow.PNG +.. Image:: /images/USB_MSC_device_API_flow.PNG User provided disk functions will be called from the LLD to handle the actual physical disk access. The overview of USB Device MSC example application: -.. Image:: ../images/USB_MSC_device_example_blocks.PNG +.. Image:: /images/USB_MSC_device_example_blocks.PNG The content of the file: usb_msc_structs.c can be replaced with customer USB device information (PID/VID, device names, etc.) @@ -238,11 +238,11 @@ example can display and manipulate content of the USB device. The following is how the USB host MSC example demo is organized: -.. Image:: ../images/USB_MSC_host_example_blocks.PNG +.. Image:: /images/USB_MSC_host_example_blocks.PNG The following is the sequence of the APIs that were used: -.. Image:: ../images/USB_MSC_host_API_flow.PNG +.. Image:: /images/USB_MSC_host_API_flow.PNG | @@ -258,7 +258,7 @@ Below diagram is the sequence of API calls that starts the USB device audio application. All USB events are handled internally in the LLD and in the interrupt context. -.. Image:: ../images/USB_Audio_class_flowchart.jpg +.. Image:: /images/USB_Audio_class_flowchart.jpg | @@ -268,7 +268,7 @@ in the interrupt context. Sequence of API calls as long as what the example application looks like are described bellow -.. Image:: ../images/usb_device_generic_bulk_example_application.png +.. Image:: /images/usb_device_generic_bulk_example_application.png - Main APIs that are used to read/write from and to the USB bulk device are USBD_bulkRead() and USBD_bulkWrite(). These two functions will block the caller until they finish their operation. @@ -449,14 +449,14 @@ platform supported. **AM335x GP EVM** -.. Image:: ../images/Am335x_usb_ac_setup.jpg +.. Image:: /images/Am335x_usb_ac_setup.jpg **OMAPL137 EVM** -.. Image:: ../images/Omapl137_usb_ac_setup.jpg +.. Image:: /images/Omapl137_usb_ac_setup.jpg **OMAPL138 LCDK** -.. Image:: ../images/Omapl138_usb_ac_setup.jpg +.. Image:: /images/Omapl138_usb_ac_setup.jpg **How to Run the Demo** @@ -475,18 +475,18 @@ platform supported. - Run the program (loaded previously) by pressing F8 - The CCS ConsoleIO will display the following: -.. Image:: ../images/CCS_console_output.png +.. Image:: /images/CCS_console_output.png - Right click on the "Speaker Icon" on the USB Host (right side of the toolbar), then select "Playback devices" - Wait until the "Speakers USB Audio Device" shows up in the "Sound" dialog -.. Image:: ../images/Sound.png +.. Image:: /images/Sound.png - Select the "Speakers USB Audio Device" in the "Sound" dialog, then click the "Configure" -.. Image:: ../images/Speaker_setup.png +.. Image:: /images/Speaker_setup.png - Click the "Test" in "Speaker Setup", you should hear the testing tone in the headphone connected to the EVM diff --git a/source/rtos/PDK_Platform_Software/Device_Drivers/_VPS_Drivers.rst b/source/rtos/PDK_Platform_Software/Device_Drivers/_VPS_Drivers.rst index 3a8912ced..d43503607 100644 --- a/source/rtos/PDK_Platform_Software/Device_Drivers/_VPS_Drivers.rst +++ b/source/rtos/PDK_Platform_Software/Device_Drivers/_VPS_Drivers.rst @@ -238,8 +238,8 @@ program expects the bgr888 file, please load frames. Below shows the first frame. If GP EVM is used, only the left upper corner of the video is displayed as it only has an 800x480 LCD. -.. Image:: ../images/488px-Yuyv422.png -.. Image:: ../images/488px-Gbr888.png +.. Image:: /images/488px-Yuyv422.png +.. Image:: /images/488px-Gbr888.png The test runs bunch of test cases as shown in the test example menu. diff --git a/source/rtos/PDK_Platform_Software/PRU_ICSS_Drivers/ICSS_EMAC_LLD/_Debug_with_ICSS_EMAC_LLD.rst b/source/rtos/PDK_Platform_Software/PRU_ICSS_Drivers/ICSS_EMAC_LLD/_Debug_with_ICSS_EMAC_LLD.rst index e4ca0324a..41bc8b4a9 100644 --- a/source/rtos/PDK_Platform_Software/PRU_ICSS_Drivers/ICSS_EMAC_LLD/_Debug_with_ICSS_EMAC_LLD.rst +++ b/source/rtos/PDK_Platform_Software/PRU_ICSS_Drivers/ICSS_EMAC_LLD/_Debug_with_ICSS_EMAC_LLD.rst @@ -78,7 +78,7 @@ ii. Restart the application by selecting Run->Restart 9. Run the application by selecting Menu->Run->Resume. This will execute the application. -.. Image:: ../images/De1.png +.. Image:: /images/De1.png NOTE @@ -412,7 +412,7 @@ ICSSEMAC_HwAttrs. For AM335x, the addresses are: -.. Image:: ../images/Dramaddr.png +.. Image:: /images/Dramaddr.png | | **Example:** For example, if storm prevention counter location needs @@ -431,7 +431,7 @@ Hence enter 0x4a301f8c in the Memory Browser and check the content. If the value is 01, storm prevention functionality is enabled and if it is 00, it is disabled. -.. Image:: ../images/Stormprev.png +.. Image:: /images/Stormprev.png | | Similarly, the value would be 0x4a302000 + 0x1f8c (DRAM base address @@ -440,7 +440,7 @@ the value is 01, storm prevention functionality is enabled and if it is For AM437x, the DRAM base addresses are as follows: -.. Image:: ../images/Dramaddram4.png +.. Image:: /images/Dramaddram4.png | @@ -456,7 +456,7 @@ Using ROV to Debug RTOS To view ROV tab, goto Tools -> RTOS Object View (ROV) and halt the debug session. -.. Image:: ../images/Rov.png +.. Image:: /images/Rov.png | @@ -566,7 +566,7 @@ The network performance can be measured from the console output upon running the above tests. Consider the log when send.exe application is run for a few minutes till it stabilizes as below: -.. Image:: ../images/Ndksend.png +.. Image:: /images/Ndksend.png Here, 8192 bytes are being sent at 12800000 bytes/s. As NDK performance is measured at MBPS (Megabits per second), conversion is: diff --git a/source/rtos/PDK_Platform_Software/PRU_ICSS_Drivers/ICSS_EMAC_LLD/_Develop_with_ICSS_EMAC_LLD.rst b/source/rtos/PDK_Platform_Software/PRU_ICSS_Drivers/ICSS_EMAC_LLD/_Develop_with_ICSS_EMAC_LLD.rst index e2f9d7e61..a38709151 100644 --- a/source/rtos/PDK_Platform_Software/PRU_ICSS_Drivers/ICSS_EMAC_LLD/_Develop_with_ICSS_EMAC_LLD.rst +++ b/source/rtos/PDK_Platform_Software/PRU_ICSS_Drivers/ICSS_EMAC_LLD/_Develop_with_ICSS_EMAC_LLD.rst @@ -1211,7 +1211,7 @@ of acceptance/rejection. The mechanism is shown below in the diagram -.. Image:: ../images/Storm_Prevention_architecture_Industrial.jpeg +.. Image:: /images/Storm_Prevention_architecture_Industrial.jpeg The Storm prevention implementation is similar in both PRU's but implemented separately, so it's possible to turn it off selectively for diff --git a/source/rtos/Tools/Code_Composer_Studio/_Multi_Core_System_Analyzer.rst b/source/rtos/Tools/Code_Composer_Studio/_Multi_Core_System_Analyzer.rst index 22dbf114e..c5aa9d192 100644 --- a/source/rtos/Tools/Code_Composer_Studio/_Multi_Core_System_Analyzer.rst +++ b/source/rtos/Tools/Code_Composer_Studio/_Multi_Core_System_Analyzer.rst @@ -13,7 +13,7 @@ visualization in Code Composer Studio. In a multi core system, data from all cores are correlated to a single timeline. -.. Image:: ../images/SA.png +.. Image:: /images/SA.png .. rubric:: Unified Instrumentation Architecture (UIA) :name: unified-instrumentation-architecture-uia @@ -201,7 +201,7 @@ MCSDK. xdc.PACKAGE_NOT_FOUND: can't locate the package 'ti.sysbios.knl'"* - To overcome this, please unzip -.. Image:: ../images/UIAMetaData.zip +.. Image:: /images/UIAMetaData.zip /packages/ti/uia/runtime/ to update the UIAMetaData.xs file. Then delete the folder from your project and rebuild. diff --git a/source/rtos/Tools/Code_Composer_Studio/_XDS100_Emulator_Info.rst b/source/rtos/Tools/Code_Composer_Studio/_XDS100_Emulator_Info.rst index e2aba5235..16e8ba5c6 100644 --- a/source/rtos/Tools/Code_Composer_Studio/_XDS100_Emulator_Info.rst +++ b/source/rtos/Tools/Code_Composer_Studio/_XDS100_Emulator_Info.rst @@ -552,7 +552,7 @@ If Windows refuses to update the driver, they need to be fully removed. - Repeat for *XDS100 Channel B* - Do the procedure above to reinstall the drivers -.. Image:: ../images/Xds100onWin10-sysdevices.png +.. Image:: /images/Xds100onWin10-sysdevices.png .. rubric:: Roadmap :name: roadmap @@ -950,7 +950,7 @@ for every action
-.. Image:: ../images/Xds100v2_adaptiveb.jpg +.. Image:: /images/Xds100v2_adaptiveb.jpg .. raw:: html @@ -963,7 +963,7 @@ for every action
-.. Image:: ../images/Xds100v2_dm365_timeout.jpg +.. Image:: /images/Xds100v2_dm365_timeout.jpg .. raw:: html @@ -1104,7 +1104,7 @@ emulators. Please see `Activating CCS#Generate_and_Install_a_License_File `__ for details. -.. Image:: ../images/CCSV4xds100license.jpg +.. Image:: /images/CCSV4xds100license.jpg | @@ -1272,7 +1272,7 @@ device manager will look like the image in v4 `__ :name: q-i-got-an-error-connecting-to-the-target-error-0x80000240-151-fatal-error-during-initialization-ocs-when-trying-to-connect-to-the-target-in-code-composer-studio-v4 -.. Image:: ../images/Xds100v1poderror.jpg +.. Image:: /images/Xds100v1poderror.jpg - A: This can occur for several reasons. With XDS100 systems, this can occur because the EEPROM was not programmed properly. Please check @@ -1285,7 +1285,7 @@ device manager will look like the image in -151 SC_ERR_POD_OPEN error with `Dbgjtag `__. :name: q-i-was-following-debugging-jtag-connectivity-problems-and-i-a--151-sc_err_pod_open-error-with-dbgjtag. -.. Image:: ../images/Xds100v1nopiddbgjtagpodfail.jpg +.. Image:: /images/Xds100v1nopiddbgjtagpodfail.jpg - A: This can occur for several reasons. With XDS100 systems, this can occur because the EEPROM was not programmed properly. Please check @@ -1453,7 +1453,7 @@ device manager will look like the image in FAQ `__ entry. -.. Image:: ../images/Xd100damagedvidpid.jpg +.. Image:: /images/Xd100damagedvidpid.jpg - Expected XDS100 VID/PID should be as described in the sections `how to make an @@ -1497,7 +1497,7 @@ section Program to program the correct settings #. Close MPROG -.. Image:: ../images/MPROG_3.5.jpg +.. Image:: /images/MPROG_3.5.jpg You should now be able to follow the directions `Here `__ diff --git a/source/rtos/Tools/Code_Composer_Studio/_XDS560_Emulator_Info.rst b/source/rtos/Tools/Code_Composer_Studio/_XDS560_Emulator_Info.rst index 58291740e..2d1056b44 100644 --- a/source/rtos/Tools/Code_Composer_Studio/_XDS560_Emulator_Info.rst +++ b/source/rtos/Tools/Code_Composer_Studio/_XDS560_Emulator_Info.rst @@ -81,12 +81,12 @@ Wiki page for more information and board requirements. Generally, in CCS 3.3 Setup, you may need to select the create board option to enable the rev D capabilities. This can be seen in the screen shot below. -.. Image:: ../images/Ccsetup-02.jpg +.. Image:: /images/Ccsetup-02.jpg Once this is done, in the connnection properties, it is possible to select the "Adaptive Clocking" options. -.. Image:: ../images/Ccsetup-04.jpg +.. Image:: /images/Ccsetup-04.jpg For devices that support EMU Boot modes the XDS560 Rev D cable drives the selected EMU pin polarity on the rising edge of nTRST or TVD. The @@ -96,7 +96,7 @@ Mode” selection options).To determine if your device supports boot modes, which modes are supported and the proper polarity for each boot mode see your device’s data sheet. -.. Image:: ../images/Ccsetup-05.jpg +.. Image:: /images/Ccsetup-05.jpg The XDS560 Rev D cable supports a remote system reset capability. The SYSRST signal from the 20-pin Emulator header on your board must be @@ -317,7 +317,7 @@ TMDSADP1414
-.. Image:: ../images/TMDSADP1414.jpg +.. Image:: /images/TMDSADP1414.jpg .. raw:: html @@ -335,7 +335,7 @@ TMDSADP1414-ISO
-.. Image:: ../images/TMDSADP1414-ISO.jpg +.. Image:: /images/TMDSADP1414-ISO.jpg .. raw:: html @@ -353,7 +353,7 @@ TMDSADP1420
-.. Image:: ../images/TMDSADP1420.jpg +.. Image:: /images/TMDSADP1420.jpg .. raw:: html @@ -371,7 +371,7 @@ TMDSADP1460
-.. Image:: ../images/TMDSADP1460.jpg +.. Image:: /images/TMDSADP1460.jpg .. raw:: html @@ -389,7 +389,7 @@ TMDSADPEMU-20A
-.. Image:: ../images/TMDSADPEMU-20A.png +.. Image:: /images/TMDSADPEMU-20A.png .. raw:: html @@ -407,7 +407,7 @@ TMDSADPEMU-20T
-.. Image:: ../images/TMDSADPEMU-20T.png +.. Image:: /images/TMDSADPEMU-20T.png .. raw:: html @@ -426,7 +426,7 @@ MDL-ADA2
-.. Image:: ../images/MDL-ADA2_cables.jpg +.. Image:: /images/MDL-ADA2_cables.jpg .. raw:: html @@ -479,12 +479,12 @@ Q: Does the XDS560 support ARM Adaptive clocking? - A: For CCSv3.3 with Service Release 12 and above, you can setup for adaptive clocking as in the photo below: -.. Image:: ../images/Ccsv33adaptive.jpg +.. Image:: /images/Ccsv33adaptive.jpg - A: For CCS v4.x, you can setup adaptive clocking as in the photo below: -.. Image:: ../images/Ccsv4adaptive.jpg +.. Image:: /images/Ccsv4adaptive.jpg Q: What is the difference between `XDS510 `__ and XDS560? ---------------------------------------------------------------------------- @@ -553,7 +553,7 @@ Q: Are there lower cost options? Q: Why does my Windows Device Manager show a warning for the TI XDS560 PCI Emulator? ------------------------------------------------------------------------------------ -.. Image:: ../images/560pcierror.jpg +.. Image:: /images/560pcierror.jpg - A: The Windows Device Manager is showing this error because a TI XDS560 PCI emulator is not installed. Windows cannot start the driver @@ -608,7 +608,7 @@ Q: How do I get loopback in a Blackhawk XDS560 with a 20 pin cable (Rev D) cable - In CCS v4.x, you need to select the loopback option. -.. Image:: ../images/Bh560m-revd-loopbackenable.jpg +.. Image:: /images/Bh560m-revd-loopbackenable.jpg Q: Can I use Boundary Scan with XDS560? ---------------------------------------