diff --git a/source/buildroot/Overview.rst b/source/buildroot/Overview.rst index 9a6c3647f..021e6cb05 100644 --- a/source/buildroot/Overview.rst +++ b/source/buildroot/Overview.rst @@ -51,14 +51,14 @@ Repository structure ├── external.mk ├── Config.in ├── board - │   ├── ti - │   │   ├── am62x-sk - │   │   ├── common + │ ├── ti + │ │ ├── am62x-sk + │ │ ├── common ├── COPYING ├── README.md ├── configs - │   ├── ti_release_am62x_sk_defconfig - │   └── ti_release_am62x_sk_rt_defconfig + │ ├── ti_release_am62x_sk_defconfig + │ └── ti_release_am62x_sk_rt_defconfig :file:`external.desc`: contains name and description of br2-external tree. 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 1ffca7cb8..5ca7e701a 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 @@ -220,7 +220,7 @@ power supply connected to the DC power jack (J3). Internally, +12V input is converted into required voltage levels using local DC-DC converters Please note that a power supply is included with the 66AK2GX Evaluation -Module. The power supply has the following specs : +Module. The power supply has the following specs : - 12V DC output - 5A output @@ -234,7 +234,7 @@ Module. The power supply has the following specs : This section describes the setup to connect to 66AK2GX GP EVM using Code composer Studio environment and an emulator. -There are two scenarios while connecting to the EVM : +There are two scenarios while connecting to the EVM : - **Connect to EVM without a SD card boot image to boot the EVM** - **Connect to EVM after booting an image from the SD card**. @@ -330,7 +330,7 @@ provided below: .. rubric:: Connecting to target :name: connecting-to-target -**Step1 :** Download Code composer Studio v6.1.3 or for CCSv6.1.2 and +**Step1 :** Download Code composer Studio v6.1.3 or for CCSv6.1.2 and earlier, ensure it contains Keystone device support package version 1.1.5 as described in the how to guide 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 00e40226f..b98f8bd8e 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 @@ -136,7 +136,7 @@ CCS Setup This section describes the setup to connect to 66AK2G02 ICE EVM using Code composer Studio environment and an emulator. -There are two scenarios while connecting to the EVM : +There are two scenarios while connecting to the EVM : - **Connect to EVM without a SD card boot image to boot the EVM** - **Connect to EVM after booting an image from the SD card**. 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 215c1c2a8..b2eb84f2c 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 @@ -160,7 +160,7 @@ scenario, the SBL component provides the same functionality .. rubric:: CCS Setup :name: ccs-setup -There are two scenarios while connecting to the EVM : +There are two scenarios while connecting to the EVM : - **Connect to EVM without a SD card boot image to boot the EVM** - **Connect to EVM after booting an image from the SD card**. @@ -207,7 +207,7 @@ provided below: .. rubric:: Connecting to target :name: connecting-to-target -**Step1 :** Download Code composer Studio and AM572x Sitara CSP package +**Step1 :** Download Code composer Studio and AM572x Sitara CSP package as described in the wiki article mentioned below: `Install Code composer Studio v6 for @@ -301,7 +301,7 @@ in the previous section. CortexA15_0: GEL Output: PHY_STATUSx registers CortexA15_0: GEL Output: Two EMIFs in interleaved mode - (2GB total) CortexA15_0: GEL Output: --->>> DDR3 Initialization is DONE! <<<--- - CortexA15_0: GEL Output: --->>> AM572x Target Connect Sequence DONE !!!!! <<<--- + CortexA15_0: GEL Output: --->>> AM572x Target Connect Sequence DONE !!!!! <<<--- CortexA15_0: GEL Output: --->>> IPU1SS Initialization is in progress ... <<<--- CortexA15_0: GEL Output: --->>> IPU1SS Initialization is DONE! <<<--- CortexA15_0: GEL Output: --->>> IPU2SS Initialization is in progress ... <<<--- diff --git a/source/common/EVM_Hardware_Setup/_AM62Px_EVM_Hardware_Setup.rst b/source/common/EVM_Hardware_Setup/_AM62Px_EVM_Hardware_Setup.rst index 30c8bc5b2..2ccd80bdf 100644 --- a/source/common/EVM_Hardware_Setup/_AM62Px_EVM_Hardware_Setup.rst +++ b/source/common/EVM_Hardware_Setup/_AM62Px_EVM_Hardware_Setup.rst @@ -4,7 +4,7 @@ AM62Px SK EVM Hardware Setup .. rubric:: Description The AM62Px starter kit (SK) evaluation module (EVM) is a stand-alone test and development platform -built around the AM62Px system-on-a-chip (SoC). AM62Px processors are comprised of a quad-core 64-bit +built around the AM62Px system-on-a-chip (SoC). AM62Px processors are comprised of a quad-core 64-bit Arm®-Cortex®-A53 microprocessor, dual-core Arm Cortex-R5F microcontroller (MCU). To know more on how to quickly start Linux on the AM62Px Starter Kit EVM (SK EVM) and run out-of-box demos, you can refer `AM62Px Starter Kit EVM Quick Start Guide. `__ diff --git a/source/common/EVM_Hardware_Setup/_AM62x_EVM_Hardware_Setup.rst b/source/common/EVM_Hardware_Setup/_AM62x_EVM_Hardware_Setup.rst index b7f6d27f1..2c1c7d921 100644 --- a/source/common/EVM_Hardware_Setup/_AM62x_EVM_Hardware_Setup.rst +++ b/source/common/EVM_Hardware_Setup/_AM62x_EVM_Hardware_Setup.rst @@ -4,7 +4,7 @@ AM62x SK EVM Hardware Setup .. rubric:: Description The AM62x starter kit (SK) evaluation module (EVM) is a stand-alone test and development platform -built around the AM62x system-on-a-chip (SoC). AM62x processors are comprised of a quad-core 64-bit +built around the AM62x system-on-a-chip (SoC). AM62x processors are comprised of a quad-core 64-bit Arm®-Cortex®-A53 microprocessor, single-core Arm Cortex-R5F microcontroller (MCU) and an Arm Cortex-M4F MCU. diff --git a/source/common/EVM_Hardware_Setup/_AM64x_EVM_Hardware_Setup.rst b/source/common/EVM_Hardware_Setup/_AM64x_EVM_Hardware_Setup.rst index be78bc608..48812ba40 100644 --- a/source/common/EVM_Hardware_Setup/_AM64x_EVM_Hardware_Setup.rst +++ b/source/common/EVM_Hardware_Setup/_AM64x_EVM_Hardware_Setup.rst @@ -24,7 +24,7 @@ headers, multiple boot options and flexible debug capabilities.The starter kit is equipped with AM64x processor and an optimized feature-set to allow the user to create commercial and industrial solutions using Ethernet-based, USB, and serial wired interfaces, two Ethernet Ports for wired connectivity. Using standard -serial protocols such as UART, I²C, and SPI, the starter kit can interface with +serial protocols such as UART, I2C, and SPI, the starter kit can interface with a multitude of other devices, acting as a communications gateway. For Quick Start Quide `click here. `__ diff --git a/source/common/EVM_Hardware_Setup/_EVMK2H_Hardware_Setup.rst b/source/common/EVM_Hardware_Setup/_EVMK2H_Hardware_Setup.rst index cbe554542..b76272afa 100644 --- a/source/common/EVM_Hardware_Setup/_EVMK2H_Hardware_Setup.rst +++ b/source/common/EVM_Hardware_Setup/_EVMK2H_Hardware_Setup.rst @@ -18,7 +18,7 @@ of the emulator daughter card. The driver can be downloaded from here .. note:: Before testing the usb connection, make sure that the mini-usb cable is plugged into the port on the base board. (and not connected to the daughter card). -After installing the driver and connecting the USB cable, two COM ports +After installing the driver and connecting the USB cable, two COM ports should be visible in the list of COM ports available to connect to in the PC Host terminal console. The lower COM port corresponds to the SoC UART and the higher one corresponds to the MCU UART. @@ -237,7 +237,7 @@ with the following steps. #. Select the BMC COM Port (the same COM port used to issue the ver command earlier), and set the ‘Baud Rate’ to 115200. #. Set ‘Transfer Size’ to 60, and make sure ‘Disable Auto Baud Support’ - is unchecked.  + is unchecked. .. image:: /images/LMflashProg_Config.png @@ -652,5 +652,5 @@ Connecting Target... arm_A15_0: GEL Output: A15 non secure mode entered Users can now load and run code on the cores by using Run -> Load -Program. Happy Debugging !! +Program. Happy Debugging !! diff --git a/source/common/EVM_Hardware_Setup/_J722S_EVM_Hardware_Setup.rst b/source/common/EVM_Hardware_Setup/_J722S_EVM_Hardware_Setup.rst index 588efa693..8f953e351 100644 --- a/source/common/EVM_Hardware_Setup/_J722S_EVM_Hardware_Setup.rst +++ b/source/common/EVM_Hardware_Setup/_J722S_EVM_Hardware_Setup.rst @@ -4,7 +4,7 @@ J722S EVM Hardware Setup .. rubric:: Description The J722S evaluation module (or TDA4VEN and AM67 EVM) is a stand-alone test and development platform -built around the J722S system-on-a-chip (SoC). J722S processors are comprised of a quad-core 64-bit +built around the J722S system-on-a-chip (SoC). J722S processors are comprised of a quad-core 64-bit Arm®-Cortex®-A53 microprocessor, dual-core Arm Cortex-R5F microcontroller (MCU). The EVM gives developers the basic resources needed for most general‐purpose type projects. 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 9e6f5448d..7e50d0a47 100644 --- a/source/common/EVM_Hardware_Setup/_OMAPL137_EVM_Hardware_Setup.rst +++ b/source/common/EVM_Hardware_Setup/_OMAPL137_EVM_Hardware_Setup.rst @@ -77,7 +77,7 @@ Target Configuration .. Image:: /images/OMAPL137_targetConfig.png -- Check "OMAPL137" or "C6747" as Device and save.  +- Check "OMAPL137" or "C6747" as Device and save. .. Tip:: If you don't see "OMAPL137", ensure that you have installed CCS and selected Single Core DSP devices in the installation. 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 bf46f7240..c19d1c17c 100644 --- a/source/common/EVM_Hardware_Setup/_TMDSEVM6657L_EVM_Hardware_Setup.rst +++ b/source/common/EVM_Hardware_Setup/_TMDSEVM6657L_EVM_Hardware_Setup.rst @@ -57,7 +57,7 @@ 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 dip switch 2 of SW9. -| User Switch 2 ON : DHCP +| User Switch 2 ON : DHCP | User Switch 2 OFF: Static IP .. image:: /images/TMD6678LSW9.png @@ -95,7 +95,7 @@ Boot Mode Dip Switch Settings The EVM supports booting image from various devices (EEPROM, NAND or NOR) via IBL (at I2C address 0x51), I2C EEPROM (at I2C address 0x50), -and ROM Boot modes (such as Ethernet, SRIO, PCIe, SPI etc.) which +and ROM Boot modes (such as Ethernet, SRIO, PCIe, SPI etc.) which address the boot source directly from the ROM code. Below is the table showing the boot mode dip switch settings for different boot mode that the EVM supports: @@ -106,7 +106,7 @@ the EVM supports: | | (Pin1, 2, 3, 4, 5, 6, 7, | (Pin1, 2, 3, 4, 5, 6, 7, | | | 8) | 8) | +==========================+==========================+==========================+ -| IBL NOR boot on image 0 | (off, off, on, off, on, | (on, on, on, off, on, | +| IBL NOR boot on image 0 | (off, off, on, off, on, | (on, on, on, off, on, | | (default) | on, on, | on, on, on)\ :sup:`4` | | | on)\ :sup:`1,2,3` | | +--------------------------+--------------------------+--------------------------+ @@ -145,22 +145,22 @@ the EVM supports: **Footnotes:** -| 1. Pin 1 of SW3 is the endian pin, by default, it is set to off (Little Endian)  +| 1. Pin 1 of SW3 is the endian pin, by default, it is set to off (Little Endian) | -| 2. Pin 2-4 of SW3 are the boot mode pins, by default it is set to I2C boot mode (off, on, off) +| 2. Pin 2-4 of SW3 are the boot mode pins, by default it is set to I2C boot mode (off, on, off) | | 3. Pin 5-8 of SW3 and pin 1-2 of SW5 are the boot parameter index pins for I2C boot (paramter index 0/1 for NOR boot image 0/1, parameter index 2/3 for NAND boot image 0/1, parameter index 4 for TFTP boot). By default, image 0 is programmed to offset byte address 0x0 on NOR, and 0x20000 (block 1 start address) on NAND, image 1 is programmed to offset byte address 0x4000000 on NAND. | -| 4. Pin 4 of SW5 is the I2C address pin (off: 0x51, on: 0x50)  for I2C boot mode +| 4. Pin 4 of SW5 is the I2C address pin (off: 0x51, on: 0x50) for I2C boot mode | | 5. This will set the board to boot from SRIO boot mode, with reference clock at 250 MHz, data rate at 3.125 GBs, and lane setup 4-1x ports and DSP System PLL at 100 MHz. | -| 6. This will set the board to boot from Ethernet boot mode, with SerDes clock multiplier x 4, core PLL clock at 100 MHz. +| 6. This will set the board to boot from Ethernet boot mode, with SerDes clock multiplier x 4, core PLL clock at 100 MHz. | | 7. This will set the board to boot form PCIE boot mode, with PCIE in end point mode and DSP System PLL at 100 MHz. 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 2ce68cf2e..05f2e5fc4 100644 --- a/source/common/EVM_Hardware_Setup/_TMDXEVM6670L_EVM_Hardware_Setup.rst +++ b/source/common/EVM_Hardware_Setup/_TMDXEVM6670L_EVM_Hardware_Setup.rst @@ -71,7 +71,7 @@ Boot Mode Dip Switch Settings ----------------------------- The EVM supports booting image from various devices (EEPROM, NAND or -NOR) via IBL, it also supports ROM Boot modes, such as Ethernet, SRIO, +NOR) via IBL, it also supports ROM Boot modes, such as Ethernet, SRIO, PCIe, etc. Below is the table showing the boot mode dip switch settings for different boot mode that the EVM supports: @@ -120,16 +120,16 @@ for different boot mode that the EVM supports: **Footnotes:** -| 1. Pin 1 of SW3 is the endian pin, by default, it is set to off (Little Endian) +| 1. Pin 1 of SW3 is the endian pin, by default, it is set to off (Little Endian) | -| 2. Pin 2-4 of SW3 are the boot mode pins, by default it is set to I2C boot mode (off, on, off) +| 2. Pin 2-4 of SW3 are the boot mode pins, by default it is set to I2C boot mode (off, on, off) | | 3. Pin 1-4 of SW4 and pin 1-2 of SW5 are the boot parameter index pins for I2C boot (paramter index 0/1 for NOR boot image 0/1, parameter index 2/3 for NAND boot image 0/1, parameter index 4 for TFTP boot). By default, image 0 is programmed to offset byte address 0x0 on NOR, and 0x4000 (block 1 start address) on NAND, image 1 is programmed to offset byte address 0xA00000 on NOR, and 0x2000000 on NAND. | -| 4. Pin 4 of SW5 is the I2C address pin (off: 0x51, on: 0x50)  for I2C boot mode +| 4. Pin 4 of SW5 is the I2C address pin (off: 0x51, on: 0x50) for I2C boot mode | | 5. This will set the board to boot from SRIO boot mode, with reference clock at 250 MHz, data rate at 3.125 GBs, and lane setup 4-1x ports and DSP System PLL at 122.88 MHz. 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 14cb89922..39f49342f 100644 --- a/source/common/EVM_Hardware_Setup/_TMDXEVM6678L_EVM_Hardware_Setup.rst +++ b/source/common/EVM_Hardware_Setup/_TMDXEVM6678L_EVM_Hardware_Setup.rst @@ -74,7 +74,7 @@ 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 dip switch 2 of SW9. -| User Switch 2 ON : DHCP +| User Switch 2 ON : DHCP | User Switch 2 OFF: Static IP .. image:: /images/TMD6678LSW9.png @@ -110,7 +110,7 @@ Boot Mode Dip Switch Settings The EVM supports booting image from various devices (EEPROM, NAND or NOR) via IBL (at I2C address 0x51), I2C EEPROM (at I2C address 0x50), -and ROM Boot modes (such as Ethernet, SRIO, PCIe, SPI etc.) which +and ROM Boot modes (such as Ethernet, SRIO, PCIe, SPI etc.) which address the boot source directly from the ROM code. Below is the table showing the boot mode dip switch settings for different boot mode that the EVM supports: @@ -121,7 +121,7 @@ the EVM supports: | | (Pin1, 2, 3, | (Pin1, 2, 3, | (Pin1, 2, 3, | (Pin1, 2, 3, | | | 4) | 4) | 4) | 4) | +================+================+================+================+================+ -| IBL NOR boot | (off, off, on, | (on, on, on, | (on, on, on, | (on, on, on, | +| IBL NOR boot | (off, off, on, | (on, on, on, | (on, on, on, | (on, on, on, | | on image 0 | off)\ :sup:`1, | on)\ :sup:`3` | off)\ :sup:`4` | on) | | (default) | 2` | | | | +----------------+----------------+----------------+----------------+----------------+ @@ -160,10 +160,10 @@ the EVM supports: | **Footnotes:** -1. Pin 1 of SW3 is the endian pin, by default, it is set to off (Little -Endian)  +1. Pin 1 of SW3 is the endian pin, by default, it is set to off (Little +Endian) -2. Pin 2-4 of SW3 are the boot mode pins, by default it is set to I2C +2. Pin 2-4 of SW3 are the boot mode pins, by default it is set to I2C boot mode (off, on, off) 3. Pin 1-4 of SW4 and pin 1-2 of SW5 are the boot parameter index pins @@ -173,7 +173,7 @@ default, image 0 is programmed to offset byte address 0x0 on NOR, and 0x4000 (block 1 start address) on NAND, image 1 is programmed to offset byte address 0xA00000 on NOR, and 0x2000000 on NAND. -4. Pin 4 of SW5 is the I2C address pin (off: 0x51, on: 0x50)  for I2C +4. Pin 4 of SW5 is the I2C address pin (off: 0x51, on: 0x50) for I2C boot mode 5. This will set the board to boot from SRIO boot mode, with reference @@ -181,7 +181,7 @@ clock at 312.5 MHz, data rate at 3.125 GBs, and lane setup 4-1x ports and DSP System PLL at 100 MHz. 6. This will set the board to boot from Ethernet boot mode, with SerDes -clock multiplier x 4, core PLL clock at 100 MHz. +clock multiplier x 4, core PLL clock at 100 MHz. 7. This will set the board to boot form PCIE boot mode, with PCIE in end point mode and DSP System PLL at 100 MHz. diff --git a/source/common/EVM_Hardware_Setup/_TMDXIDK5728_Hardware_Setup.rst b/source/common/EVM_Hardware_Setup/_TMDXIDK5728_Hardware_Setup.rst index 6691e66b2..e9b43f9d4 100644 --- a/source/common/EVM_Hardware_Setup/_TMDXIDK5728_Hardware_Setup.rst +++ b/source/common/EVM_Hardware_Setup/_TMDXIDK5728_Hardware_Setup.rst @@ -183,7 +183,7 @@ corresponding to FTDI UARTtoUSB will be turned on. .. rubric:: Connecting IDK EVM to Code Composer Studio :name: connecting-idk-evm-to-code-composer-studio -**Step1 :** Download Code composer Studio and AM572x Sitara CSP package +**Step1 :** Download Code composer Studio and AM572x Sitara CSP package as described in the wiki article mentioned below: `Install Code composer Studio for @@ -285,11 +285,11 @@ is installed CortexA15_0: GEL Output: DEBUG: EMIF1 channel - Launch full levelling CortexA15_0: GEL Output: DEBUG: Setting LISA maps in non-interleaved dual-EMIF mode CortexA15_0: GEL Output: --->>> DDR3 Initialization is DONE! <<<--- - CortexA15_0: GEL Output: --->>> AM572x Target Connect Sequence DONE !!!!! <<< + CortexA15_0: GEL Output: --->>> AM572x Target Connect Sequence DONE !!!!! <<< | -**Step6** : To connect to the DSP, M4,PRUSS or to IVAHD go to Scripts +**Step6** : To connect to the DSP, M4,PRUSS or to IVAHD go to Scripts menu and under AM572x MULTICORE Initialization enable the corresponding Sub system clock Enable API.For Eg. FOr DSP1 select DSP11SSClkEnable\_API. After running the clock enable option, you can diff --git a/source/common/Industrial_Protocols/HSR_PRP/_Firmware.rst b/source/common/Industrial_Protocols/HSR_PRP/_Firmware.rst index 66fedd80d..2d2cad05a 100644 --- a/source/common/Industrial_Protocols/HSR_PRP/_Firmware.rst +++ b/source/common/Industrial_Protocols/HSR_PRP/_Firmware.rst @@ -216,7 +216,7 @@ Table: **Shared RAM Memory Map** +--------------------------+--------------------------+--------------------------+ | Name of Offset | Description | Offset in Shared RAM | -| | Refer to | (base : 0x140) | +| | Refer to | (base : 0x140) | | | *hsr\_prp\_firmware.h* | | +==========================+==========================+==========================+ | LRE\_CNT\_TX\_A | Number of frames | *4* | diff --git a/source/common/Industrial_Protocols/HSR_PRP/_Firmware_Features.rst b/source/common/Industrial_Protocols/HSR_PRP/_Firmware_Features.rst index 67cb55246..5f06530d9 100644 --- a/source/common/Industrial_Protocols/HSR_PRP/_Firmware_Features.rst +++ b/source/common/Industrial_Protocols/HSR_PRP/_Firmware_Features.rst @@ -44,11 +44,11 @@ Firmware Features Supported - Duplicate discard table on Port to Port path (HSR) - Data integrity (CRC) check during port to port forwarding, except cut through (HSR) -- **QoS scheme** : 3-bit VLAN PCP +- **QoS scheme** : 3-bit VLAN PCP - - No of levels supported : 8 - - Number of host queues : 2 \| 4 QoS levels per host queue - - Number of port queues : 4 \| 2 QoS levels per port queue + - No of levels supported : 8 + - Number of host queues : 2 \| 4 QoS levels per host queue + - Number of port queues : 4 \| 2 QoS levels per port queue - Number of host queues are configurable - **Statistics** @@ -66,4 +66,4 @@ Firmware Features Supported - Single and Two step clock supported - Peer delay Response is always sent as two-step -- **Storm Prevention** : Yes. Configurable per port +- **Storm Prevention** : Yes. Configurable per port diff --git a/source/common/PRU-ICSS/Header_Files.rst b/source/common/PRU-ICSS/Header_Files.rst index 0b19f09ab..be45e4241 100644 --- a/source/common/PRU-ICSS/Header_Files.rst +++ b/source/common/PRU-ICSS/Header_Files.rst @@ -46,7 +46,7 @@ layout is like this: union{ u32 register_name; struct { -bit_field_names : bit_size; +bit_field_names : bit_size; . . . } register_name_bit; }; diff --git a/source/common/PRU-ICSS/PRU-Cape-Hardware-User-Guide.rst b/source/common/PRU-ICSS/PRU-Cape-Hardware-User-Guide.rst index 0da326189..ec5953e16 100644 --- a/source/common/PRU-ICSS/PRU-Cape-Hardware-User-Guide.rst +++ b/source/common/PRU-ICSS/PRU-Cape-Hardware-User-Guide.rst @@ -8,8 +8,8 @@ PRU Cape Hardware User Guide Introduction ^^^^^^^^^^^^ -This document describes the hardware architecture of the PRU Cape  -which is compatible with the Beagle Bone Black development platform.  +This document describes the hardware architecture of the PRU Cape +which is compatible with the Beagle Bone Black development platform. | @@ -147,7 +147,7 @@ Signals Used +------------------------------+------------------------------+------------------------+------------------------+ | PR1\_PRU0\_GPI15 | P8-15 | GPMC\_AD15 | PRU0\_GPI\_15 | +------------------------------+------------------------------+------------------------+------------------------+ -| VDD\_3V3C | P9-3, P9-4  | VDD\_3V3C | VDD\_3V3C | +| VDD\_3V3C | P9-3, P9-4 | VDD\_3V3C | VDD\_3V3C | +------------------------------+------------------------------+------------------------+------------------------+ | DGND | P8-1, P8-2, P9-1,P9-2 | DGND | DGND | +------------------------------+------------------------------+------------------------+------------------------+ @@ -168,7 +168,7 @@ This section describes major functional blocks of the PRU Cape. Audio """"" -The audio portion of the PRU Cape is composed of a Dual 8-bit DAC +The audio portion of the PRU Cape is composed of a Dual 8-bit DAC (DAC082S085) and a dual 105 mW Amplifier (LM4808). The output is then sent to a 3.5 mm Audio jack with a max pk-pk of .89V, following the consumer standard. @@ -201,7 +201,7 @@ the cape, the rest of the EEPROM is available for use. +--------------------------+-------------------------+-----------------------+----------------------+ | **CAPE NAME** | **BBB HEADER NUMBER** | **BBB MODE 0 NAME** | **CAPE USE** | +--------------------------+-------------------------+-----------------------+----------------------+ -| I2C2\_SDA              | P9-20 | I2C2\_SDA | I2C SCL            | +| I2C2\_SDA | P9-20 | I2C2\_SDA | I2C SCL | +--------------------------+-------------------------+-----------------------+----------------------+ | I2C2\_SCL | P9-19 | I2C2\_SCL | I2C SDA | +--------------------------+-------------------------+-----------------------+----------------------+ @@ -223,14 +223,13 @@ IN to allow use of the PRU Subsystem's eCAP IP. | PR1\_PRU0\_GPI15 | P8-15 | GPMC\_AD15 | PRU0\_GPI\_15 | +-----------------------------+-------------------------+------------------------+------------------------+ -  LCD """ -The LCD screen is on a duaghter board with its own built in -controller, model number  NHD-0208AZ-RN-YBW-33V. The LCD is connected to +The LCD screen is on a duaghter board with its own built in +controller, model number NHD-0208AZ-RN-YBW-33V. The LCD is connected to the PRU Cape throught the 2x8 female header in the middle of the cape. -The LCD is a 2x8 Character display operating at 3.3V. +The LCD is a 2x8 Character display operating at 3.3V. | @@ -336,7 +335,7 @@ PRU or any signal that can be accessed through the Cape Headers. UART """" -There is one RS-232 connector (DB9 male) on the PRU Cape. The MAX3232ECD +There is one RS-232 connector (DB9 male) on the PRU Cape. The MAX3232ECD is the line driver/receiver. | diff --git a/source/common/PRU-ICSS/PRU-Hands-on-Labs.rst b/source/common/PRU-ICSS/PRU-Hands-on-Labs.rst index 63a9b7ca9..6386a042a 100644 --- a/source/common/PRU-ICSS/PRU-Hands-on-Labs.rst +++ b/source/common/PRU-ICSS/PRU-Hands-on-Labs.rst @@ -402,7 +402,7 @@ Build the PRU Firmware :: while(1){ - if ((__R31 & SW1) != SW1){ + if ((__R31 & SW1) != SW1){ /* Interrupt PRU1, wait 500ms for cheap "debounce" */ /* TODO: Trigger interrupt - see #defines */ __delay_cycles(100000000); /* 500ms @ 200MHz */ diff --git a/source/common/Release_Specific/_MCSDK_to_Processor_SDK_Migration.rst b/source/common/Release_Specific/_MCSDK_to_Processor_SDK_Migration.rst index e78acc36b..c10259118 100644 --- a/source/common/Release_Specific/_MCSDK_to_Processor_SDK_Migration.rst +++ b/source/common/Release_Specific/_MCSDK_to_Processor_SDK_Migration.rst @@ -356,7 +356,7 @@ application rather than the design of the software. header files as “ti/csl/device/k2?/src/xxxx.h” needs to be changed to “ti/csl/soc/k2?/src/xxxx.h” - One top level include header files per IP replaces multiple CSL files - per IP for the following : + per IP for the following : - , , , , and diff --git a/source/debian/Building_Debian_Image.rst b/source/debian/Building_Debian_Image.rst index 8035aef9f..21b9c5137 100644 --- a/source/debian/Building_Debian_Image.rst +++ b/source/debian/Building_Debian_Image.rst @@ -45,26 +45,26 @@ Repository Structure ├── build.sh ├── builds.toml ├── configs - │   ├── bdebstrap_configs - │   │   ├── bookworm - │   │   │   ├── bookworm-.yaml - │   │   │   └── bookworm-rt-.yaml - │   │   └── trixie - │   │   ├── trixie-.yaml - │   │   └── trixie-rt-.yaml - │   ├── bsp_sources.toml - │   └── machines --> Machine configurations for each BSP version - │   ├── 09.02.00.010.toml - │   └── 10.01.10.04.toml + │ ├── bdebstrap_configs + │ │ ├── bookworm + │ │ │ ├── bookworm-.yaml + │ │ │ └── bookworm-rt-.yaml + │ │ └── trixie + │ │ ├── trixie-.yaml + │ │ └── trixie-rt-.yaml + │ ├── bsp_sources.toml + │ └── machines --> Machine configurations for each BSP version + │ ├── 09.02.00.010.toml + │ └── 10.01.10.04.toml ├── create-sdcard.sh ├── create-wic.sh ├── LICENSE ├── README.md ├── scripts - │   ├── build_bsp.sh - │   ├── build_distro.sh - │   ├── common.sh - │   └── setup.sh + │ ├── build_bsp.sh + │ ├── build_distro.sh + │ ├── common.sh + │ └── setup.sh └── target --> Custom files to deploy in target. ``build.sh``: the "main" script that the user should run to generate Debian images. diff --git a/source/devices/AM335X/linux/Release_Specific_Release_Notes.rst b/source/devices/AM335X/linux/Release_Specific_Release_Notes.rst index 8478bdb62..390de281f 100644 --- a/source/devices/AM335X/linux/Release_Specific_Release_Notes.rst +++ b/source/devices/AM335X/linux/Release_Specific_Release_Notes.rst @@ -216,7 +216,7 @@ Issues Open :name: installation-and-usage The :ref:`Software Developer's Guide ` provides instructions on how to setup up your Linux development -environment, install the SDK and start your development.  It also includes User's Guides for various Example Applications and Code +environment, install the SDK and start your development. It also includes User's Guides for various Example Applications and Code Composer Studio. | diff --git a/source/devices/AM437X/linux/Release_Specific_Release_Notes.rst b/source/devices/AM437X/linux/Release_Specific_Release_Notes.rst index d56d9e1a6..f4425eea3 100644 --- a/source/devices/AM437X/linux/Release_Specific_Release_Notes.rst +++ b/source/devices/AM437X/linux/Release_Specific_Release_Notes.rst @@ -216,7 +216,7 @@ Issues Open :name: installation-and-usage The :ref:`Software Developer's Guide ` provides instructions on how to setup up your Linux development -environment, install the SDK and start your development.  It also includes User's Guides for various Example Applications and Code +environment, install the SDK and start your development. It also includes User's Guides for various Example Applications and Code Composer Studio. | diff --git a/source/devices/AM57X/linux/Release_Specific_Release_Notes.rst b/source/devices/AM57X/linux/Release_Specific_Release_Notes.rst index 2bb2e897b..51398835f 100644 --- a/source/devices/AM57X/linux/Release_Specific_Release_Notes.rst +++ b/source/devices/AM57X/linux/Release_Specific_Release_Notes.rst @@ -297,7 +297,7 @@ RT Linux Kernel Known Issues :name: installation-and-usage The `Software Developer's Guide `__ provides instructions on how to setup up your Linux development -environment, install the SDK and start your development.  It also includes User's Guides for various Example Applications and Code +environment, install the SDK and start your development. It also includes User's Guides for various Example Applications and Code Composer Studio. | diff --git a/source/devices/AM62AX/linux/Overview/Run_Setup_Scripts.rst b/source/devices/AM62AX/linux/Overview/Run_Setup_Scripts.rst index 9e9f8fe78..cbe43ae9d 100644 --- a/source/devices/AM62AX/linux/Overview/Run_Setup_Scripts.rst +++ b/source/devices/AM62AX/linux/Overview/Run_Setup_Scripts.rst @@ -33,11 +33,11 @@ does the following things: :name: how-to-run-the-setup-script The Setup Script (**setup.sh**) is located in the |__SDK_FULL_NAME__| installation -directory.  By default, this directory has a name that has the form +directory. By default, this directory has a name that has the form |__SDK_INSTALL_DIR__|. -Change to that ti-processor-sdk-linux install directory. +Change to that ti-processor-sdk-linux install directory. Then run the script: **./setup.sh** @@ -87,7 +87,7 @@ packages may vary for different releases: .. note:: This part requires you to have administrator priviliges (sudo access). -This step is required for users using Ubuntu 12.04+. By default the +This step is required for users using Ubuntu 12.04+. By default the user does not have the proper permissions to access a serial device ( ex ttyS0, ttyUSB0, etc...). A user must be apart of a "dialout" group to access these serial device without root privileges. diff --git a/source/devices/AM62PX/linux/Overview/Run_Setup_Scripts.rst b/source/devices/AM62PX/linux/Overview/Run_Setup_Scripts.rst index b34c41683..22a49cb03 100644 --- a/source/devices/AM62PX/linux/Overview/Run_Setup_Scripts.rst +++ b/source/devices/AM62PX/linux/Overview/Run_Setup_Scripts.rst @@ -33,11 +33,11 @@ does the following things: :name: how-to-run-the-setup-script The Setup Script (**setup.sh**) is located in the |__SDK_FULL_NAME__| installation -directory.  By default, this directory has a name that has the form +directory. By default, this directory has a name that has the form |__SDK_INSTALL_DIR__|. -Change to that ti-processor-sdk-linux install directory. +Change to that ti-processor-sdk-linux install directory. Then run the script: **./setup.sh** @@ -87,7 +87,7 @@ packages may vary for different releases: .. note:: This part requires you to have administrator priviliges (sudo access). -This step is required for users using Ubuntu 12.04+. By default the +This step is required for users using Ubuntu 12.04+. By default the user does not have the proper permissions to access a serial device ( ex ttyS0, ttyUSB0, etc...). A user must be apart of a "dialout" group to access these serial device without root privileges. diff --git a/source/devices/AM62X/linux/Overview/Run_Setup_Scripts.rst b/source/devices/AM62X/linux/Overview/Run_Setup_Scripts.rst index 607056146..de36ab888 100644 --- a/source/devices/AM62X/linux/Overview/Run_Setup_Scripts.rst +++ b/source/devices/AM62X/linux/Overview/Run_Setup_Scripts.rst @@ -33,11 +33,11 @@ does the following things: :name: how-to-run-the-setup-script The Setup Script (**setup.sh**) is located in the |__SDK_FULL_NAME__| installation -directory.  By default, this directory has a name that has the form +directory. By default, this directory has a name that has the form |__SDK_INSTALL_DIR__|. -Change to that ti-processor-sdk-linux install directory. +Change to that ti-processor-sdk-linux install directory. Then run the script: **./setup.sh** @@ -87,7 +87,7 @@ packages may vary for different releases: .. note:: This part requires you to have administrator priviliges (sudo access). -This step is required for users using Ubuntu 12.04+. By default the +This step is required for users using Ubuntu 12.04+. By default the user does not have the proper permissions to access a serial device ( ex ttyS0, ttyUSB0, etc...). A user must be apart of a "dialout" group to access these serial device without root privileges. diff --git a/source/devices/AM64X/linux/Overview/Create_SD_Card.rst b/source/devices/AM64X/linux/Overview/Create_SD_Card.rst index 7ca7c5c40..1556367cb 100644 --- a/source/devices/AM64X/linux/Overview/Create_SD_Card.rst +++ b/source/devices/AM64X/linux/Overview/Create_SD_Card.rst @@ -17,7 +17,7 @@ Create SD Card with Default Images | 2. The default bootable SD card image (WIC file) is available - at /filesystem/tisdk-default-image-am64xx-evm.wic.xz + at /filesystem/tisdk-default-image-am64xx-evm.wic.xz | diff --git a/source/devices/AM65X/linux/Release_Specific_Release_Notes.rst b/source/devices/AM65X/linux/Release_Specific_Release_Notes.rst index a28b967b6..b29b20a5d 100644 --- a/source/devices/AM65X/linux/Release_Specific_Release_Notes.rst +++ b/source/devices/AM65X/linux/Release_Specific_Release_Notes.rst @@ -238,7 +238,7 @@ Installation and Usage ====================== The :ref:`Software Developer's Guide ` provides instructions on how to setup up your Linux development -environment, install the SDK and start your development.  It also includes User's Guides for various Example Applications and Code +environment, install the SDK and start your development. It also includes User's Guides for various Example Applications and Code Composer Studio. | diff --git a/source/devices/J7_Family/linux/Release_Specific_Release_Notes.rst b/source/devices/J7_Family/linux/Release_Specific_Release_Notes.rst index 421587bef..4a8ea28a6 100644 --- a/source/devices/J7_Family/linux/Release_Specific_Release_Notes.rst +++ b/source/devices/J7_Family/linux/Release_Specific_Release_Notes.rst @@ -252,7 +252,7 @@ Issues opened in previous releases that were closed on this release "LCPD-38644","v4l2 compliance failing with try_fmt","am62axx_sk-fs,am62pxx_sk-fs,am68_sk-fs,am69_sk-fs,j721s2-evm,j722s_evm-fs,j742s2_evm-fs,j784s4-evm" "LCPD-38622","J722S 4 Camera IMX219 GStreamer Pipeline Failure","j722s_evm-fs" "LCPD-38596","Upstream: correct mux node name for can ","j7200-evm,j721s2-evm" - "LCPD-38554","MCAN: add am68, am69, j7-sk in mcan docs ","am68_sk-fs,am69_sk-fs,j721e-sk" + "LCPD-38554","MCAN: add am68, am69, j7-sk in mcan docs","am68_sk-fs,am69_sk-fs,j721e-sk" "LCPD-38528","Documentation: IPC: Update 6.1.y links to 6.6.y","am62pxx_sk-fs,am62xx_sk-fs,j722s_evm-fs" "LCPD-38500","Add J721E SR 2.0 Support (k3conf and u-boot)","j721e-idk-gw" "LCPD-38497","Graceful Shutdown test failing","am69_sk-fs,j7200-evm,j721e-idk-gw,j721s2-evm,j784s4-evm" diff --git a/source/linux/Examples_and_Demos/Application_Demos/Video_Analytics.rst b/source/linux/Examples_and_Demos/Application_Demos/Video_Analytics.rst index daa763d8a..95614b901 100644 --- a/source/linux/Examples_and_Demos/Application_Demos/Video_Analytics.rst +++ b/source/linux/Examples_and_Demos/Application_Demos/Video_Analytics.rst @@ -96,7 +96,7 @@ folder and can be compiled using the SDK's top-level Makefile .. rubric:: OpenCV (running on ARM A15s) :name: opencv-running-on-arm-a15s -| *FLOW: camera color frames from V4L2 driver -> OpenCV based algorithms +| *FLOW: camera color frames from V4L2 driver -> OpenCV based algorithms -> single float converted to 4 discrete values* Video analytics functionality includes simple algorithm to extract @@ -117,12 +117,12 @@ and waves become higher. .. rubric:: OpenCL (running on ARM A15s + C66x) :name: opencl-running-on-arm-a15s-c66x -| *FLOW: 4 discrete values of wind speed (2.5, 4, 7, 10m/s)  -> OpenCL +| *FLOW: 4 discrete values of wind speed (2.5, 4, 7, 10m/s) -> OpenCL based algorithms -> 256x256 float height map matrix (-1, ..., +1 range of vertex heights)* Wave surface simulation is based on generation of Phillips (2D) spectrum -followed by 2D IFFT (256x256). Both operations are executed by OpenCL +followed by 2D IFFT (256x256). Both operations are executed by OpenCL offload to single DSP core. Many details on this algorithm can be found in `graphics.ucsd.edu/courses/rendering/2005/jdewall/tessendorf.pdf `__. @@ -131,13 +131,13 @@ algorithm) using fixed wind direction *(an idea for improvement: wind direction can be controlled using hand gesture).* Height map in form of 256x256 float matrix is generated on output and -used by OpenGL based vertex renderer (performed in next step). Wave +used by OpenGL based vertex renderer (performed in next step). Wave surface simulation consists of two steps: - initial setup defining starting conditions (wind speed and wind direction are used as input in this stage only) - update of wave surface height map (Phillips spectrum modification - generated at t=0, along time axe and 2D IFFT for each time step). + generated at t=0, along time axe and 2D IFFT for each time step). .. rubric:: OpenGL ES (running on ARM A15s + GPU/SGX) :name: opengl-es-running-on-arm-a15s-gpusgx @@ -166,11 +166,11 @@ system and control of above threads* | qt-opencv-multithreaded (`github.com/devernay/qt-opencv-multithreaded `__ - ) is skeleton GUI application providing camera input and some basic + ) is skeleton GUI application providing camera input and some basic image processing algorithms. Additional algorithm (w.r.t baseline) is - hand gesture which starts OpenCV thread and OpenCL simulation thread. + hand gesture which starts OpenCV thread and OpenCL simulation thread. Wave surface window (detached, 600x400) appears only if hand is put - (at 2-3ft) in front of EVM camera. Intensity of waves is defined by + (at 2-3ft) in front of EVM camera. Intensity of waves is defined by how much fingers are spread. | Please wait for 2-3 seconds (after start of Gesture detection) before putting hand in front of camera, to allow good background estimation. @@ -184,13 +184,13 @@ system and control of above threads* The functionality is organized as shows in the files/description below. +------+---------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| | file name |  description | +| | file name | description | +------+---------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | 1 | CameraConnectDialog.cpp/CameraConnectDialog.h | | +------+---------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | 2 | CameraGrab.cpp/CameraGrab.h | Auxilliary camera frame acquisition functions to achieve full FPS | +------+---------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 3 | CameraView.cpp/CameraView.h | Major class instantiated after connecting to camera. This class creates processing thread, wavesimulation thread and also instantiates wave display (3D graphics) widget. | +| 3 | CameraView.cpp/CameraView.h | Major class instantiated after connecting to camera. This class creates processing thread, wavesimulation thread and also instantiates wave display (3D graphics) widget. | +------+---------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | 4 | CaptureThread.cpp/CaptureThread.h | Input (camera) frame buffering. | +------+---------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ @@ -198,7 +198,7 @@ The functionality is organized as shows in the files/description below. +------+---------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | 6 | GeometryEngine.cpp/GeometryEngine.h | Height map mash creation, vertex updates | +------+---------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 7 | Gesture.cpp/Gesture.h | Hand gesture (OpenCV) detection algorith, | +| 7 | Gesture.cpp/Gesture.h | Hand gesture (OpenCV) detection algorith, | +------+---------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | 8 | ImageProcessingSettingsDialog.cpp/ImageProcessingSettingsDialog.h | Settings of parameters used by image processing algorithms. | +------+---------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ @@ -206,7 +206,7 @@ The functionality is organized as shows in the files/description below. +------+---------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | 10 | MainWindow.cpp/MainWindow.h | | +------+---------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 11 | MatToQImage.cpp/MatToQImage.h | Conversion from OpenCV Mat object to QT QImage object | +| 11 | MatToQImage.cpp/MatToQImage.h | Conversion from OpenCV Mat object to QT QImage object | +------+---------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | 12 | ProcessingThread.cpp/ProcessingThread.h | Main processing thread, frame rate dynamics, invokes variois image processing algorithms | +------+---------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ @@ -214,7 +214,7 @@ The functionality is organized as shows in the files/description below. +------+---------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | 14 | WaveDisplayWidget.cpp/WaveDisplayWidget.h | Wave surface 3D rendering (invokes methods from GeometryEngine.cpp) | +------+---------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 15 | WaveSimulationThread.cpp/WaveSimulationThread.h | Wave surface physical simulation thread - host side of OpenCL dispatch. | +| 15 | WaveSimulationThread.cpp/WaveSimulationThread.h | Wave surface physical simulation thread - host side of OpenCL dispatch. | +------+---------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | 16 | Buffers.h | | +------+---------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ @@ -222,7 +222,7 @@ The functionality is organized as shows in the files/description below. +------+---------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | 18 | Config.h | | +------+---------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 19 | phillips.cl | DSP OpenCL phillips spectrum generation kernels and 2D IFFT kernel (invoking dsplib.ae66 optimized 1D FFT). After compilation (by clocl) phillips.dsp\_h is generated, and included in WaveSimulationThread.cpp (ocl kernels are compiled and downloaded in this thread, before run-time operation is started). | +| 19 | phillips.cl | DSP OpenCL phillips spectrum generation kernels and 2D IFFT kernel (invoking dsplib.ae66 optimized 1D FFT). After compilation (by clocl) phillips.dsp\_h is generated, and included in WaveSimulationThread.cpp (ocl kernels are compiled and downloaded in this thread, before run-time operation is started). | +------+---------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | 20 | vshader.glsl | Vertex shader (gets projection matrix, position and texture position as input arguments; generates texture coordinate and height for fragment shader | +------+---------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ @@ -230,9 +230,9 @@ The functionality is organized as shows in the files/description below. +------+---------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | 22 | shaders.qrc | Specify shader filenames | +------+---------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 23 | textures.qrc | Specify texture file (2D block which is linearly interpolated in fragment shader, using position arguments provided by vertex shader) | +| 23 | textures.qrc | Specify texture file (2D block which is linearly interpolated in fragment shader, using position arguments provided by vertex shader) | +------+---------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 24 | qt-opencv-multithreaded.pro | Top level QT make file: phi | +| 24 | qt-opencv-multithreaded.pro | Top level QT make file: phi | +------+---------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | 25 | ImageProcessingSettingsDialog.ui | User interface definition file for modification of algorithm parameters. | +------+---------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ diff --git a/source/linux/Examples_and_Demos/_AM335x_Power_Management_User_Guide.rst b/source/linux/Examples_and_Demos/_AM335x_Power_Management_User_Guide.rst index 9a320149c..ace60e788 100644 --- a/source/linux/Examples_and_Demos/_AM335x_Power_Management_User_Guide.rst +++ b/source/linux/Examples_and_Demos/_AM335x_Power_Management_User_Guide.rst @@ -8,7 +8,7 @@ AM335x Power Management User Guide This article provides a description of the example applications under the Power page of the Matrix application that comes with the Sitara -SDK.  This page is labled "Power" in the top-level Matrix GUI. The +SDK. This page is labled "Power" in the top-level Matrix GUI. The location of the Power icon on the main Matrix app list may be different than shown here, depending on screen size. (Screen shots from SDK 06.00) diff --git a/source/linux/Examples_and_Demos/_ARM_Multimedia_Users_Guide.rst b/source/linux/Examples_and_Demos/_ARM_Multimedia_Users_Guide.rst index 1cb45cec2..a590a9da9 100644 --- a/source/linux/Examples_and_Demos/_ARM_Multimedia_Users_Guide.rst +++ b/source/linux/Examples_and_Demos/_ARM_Multimedia_Users_Guide.rst @@ -161,7 +161,7 @@ buffers, they do not modify the data otherwise. :: - gst-launch-0.10 filesrc location=$filename ! qtdemux name=demux demux.audio_00 ! queue ! ffdec_aac ! alsasink sync=false demux.video_00 ! queue ! ffdec_mpeg4 ! ffmpegcolorspace ! fbdevsink device=/dev/fb0 + gst-launch-0.10 filesrc location=$filename ! qtdemux name=demux demux.audio_00 ! queue ! ffdec_aac ! alsasink sync=false demux.video_00 ! queue ! ffdec_mpeg4 ! ffmpegcolorspace ! fbdevsink device=/dev/fb0 "filename" is defined based on the selected display device which could be LCD of DVI. @@ -180,7 +180,7 @@ as mentioned in the description page below. :: - gst-launch-0.10 filesrc location=$filename ! mpeg4videoparse ! ffdec_mpeg4 ! ffmpegcolorspace ! fbdevsink device=/dev/fb0 + gst-launch-0.10 filesrc location=$filename ! mpeg4videoparse ! ffdec_mpeg4 ! ffmpegcolorspace ! fbdevsink device=/dev/fb0 | @@ -198,7 +198,7 @@ as mentioned in the description page below. :: - gst-launch-0.10 filesrc location=$filename ! h264parse ! ffdec_h264 ! ffmpegcolorspace ! fbdevsink device=/dev/fb0 + gst-launch-0.10 filesrc location=$filename ! h264parse ! ffdec_h264 ! ffmpegcolorspace ! fbdevsink device=/dev/fb0 .. rubric:: AAC Decode :name: aac-decode @@ -214,7 +214,7 @@ mentioned in the description page below. :: - gst-launch-0.10 filesrc location=$filename ! aacparse ! faad ! alsasink + gst-launch-0.10 filesrc location=$filename ! aacparse ! faad ! alsasink .. rubric:: Streaming :name: streaming @@ -226,7 +226,7 @@ the files directory using the pipeline :: - gst-launch souphttpsrc location=http:///files/HistoryOfTI.aac ! aacparse ! faad ! alsasink + gst-launch souphttpsrc location=http:///files/HistoryOfTI.aac ! aacparse ! faad ! alsasink | diff --git a/source/linux/Examples_and_Demos/_Camera_Users_Guide.rst b/source/linux/Examples_and_Demos/_Camera_Users_Guide.rst index 1cdcf9875..0022439a7 100644 --- a/source/linux/Examples_and_Demos/_Camera_Users_Guide.rst +++ b/source/linux/Examples_and_Demos/_Camera_Users_Guide.rst @@ -70,19 +70,19 @@ Contact: `Harishankkar `__ +----------------------+-----------------------------------------+------------+-----------+ | OMAP35xx/AM/DM37xx | Signal Description | Comment | IO Type | +----------------------+-----------------------------------------+------------+-----------+ -| cam\_hs | Camera Horizontal Sync |   | IO | +| cam\_hs | Camera Horizontal Sync | | IO | +----------------------+-----------------------------------------+------------+-----------+ -| cam\_vs | Camera Vertical Sync |   | IO | +| cam\_vs | Camera Vertical Sync | | IO | +----------------------+-----------------------------------------+------------+-----------+ | cam\_xclka | Camera Clock Output a | Optional | O | +----------------------+-----------------------------------------+------------+-----------+ | cam\_xclkb | Camera Clock Output b | Optional | O | +----------------------+-----------------------------------------+------------+-----------+ -| cam\_[d0:12] | Camera/Video Digital Image Data |   | I | +| cam\_[d0:12] | Camera/Video Digital Image Data | | I | +----------------------+-----------------------------------------+------------+-----------+ | cam\_fld | Camera Field ID | Optional | IO | +----------------------+-----------------------------------------+------------+-----------+ -| cam\_pclk | Camera Pixel Clock |   | I | +| cam\_pclk | Camera Pixel Clock | | I | +----------------------+-----------------------------------------+------------+-----------+ | cam\_wen | Camera Write Enable | Optional | I | +----------------------+-----------------------------------------+------------+-----------+ diff --git a/source/linux/Examples_and_Demos/_Hands_on_with_QT.rst b/source/linux/Examples_and_Demos/_Hands_on_with_QT.rst index a3a6ed5bf..c85878f74 100644 --- a/source/linux/Examples_and_Demos/_Hands_on_with_QT.rst +++ b/source/linux/Examples_and_Demos/_Hands_on_with_QT.rst @@ -463,7 +463,7 @@ development. style="margin: 5px; padding: 5px 10px; background-color: #ffffec; border-left: 5px solid #ff6600;"> **IMPORTANT** - Notice there is a red ! icon. Don't worry, lets add in the toolchain + Notice there is a red ! icon. Don't worry, lets add in the toolchain next and it should change to yellow. .. raw:: html @@ -1333,7 +1333,7 @@ style sheets. QPushButton { /**font: bold 16pt; - color: white ; + color: white ; border-image: url(:/pushblueup.png); background-color: transparent; diff --git a/source/linux/Examples_and_Demos/_Matrix_User_Guide.rst b/source/linux/Examples_and_Demos/_Matrix_User_Guide.rst index c4e141c56..bd8d0cb1c 100644 --- a/source/linux/Examples_and_Demos/_Matrix_User_Guide.rst +++ b/source/linux/Examples_and_Demos/_Matrix_User_Guide.rst @@ -45,9 +45,9 @@ Matrix is an HTML 5 based application launcher created to highlight available applications and demos provided in new Software Development Kits. There are two forms of Matrix, local and remote Matrix. All of the example applications and demos are available using either the local or -remote version. The local version launches by default when the target -system is booted and uses the target system's touchscreen interface for -user input. Matrix comes as a 4x3 matrix of icons or as a 4x2 matrix +remote version. The local version launches by default when the target +system is booted and uses the target system's touchscreen interface for +user input. Matrix comes as a 4x3 matrix of icons or as a 4x2 matrix depending on the display resolution. .. Image:: /images/Matrix_2_Main_Menu.png @@ -60,7 +60,7 @@ depending on the display resolution. Local Matrix refers to Matrix being displayed on a display device attached to the target system. The launcher for Matrix is just a -simple QT application that displays a Webkit base browser that points +simple QT application that displays a Webkit base browser that points to the URL http://localhost:80 .. raw:: html @@ -86,14 +86,14 @@ The URL for Remote Matrix is http:// You can find the target's ip address by using local Matrix and clicking on the Settings icon and then on the Network Settings icon. Or using a -terminal logged in to the target system enter the below command: +terminal logged in to the target system enter the below command: :: ifconfig From the output displayed, look in the section that starts with eth0. -You sould see an IP address right after "inet addr". This is the IP +You sould see an IP address right after "inet addr". This is the IP address you should use for remote Matrix. With Remote Matrix you can interact with Matrix on your PC, cellphone, @@ -106,7 +106,7 @@ still look at the display device connected to the target system. :name: matrix-project-webpage The offical website for Matrix is located at -`**gforge.ti.com/gf/project/matrix-gui-v2/** `__ Any +`**gforge.ti.com/gf/project/matrix-gui-v2/** `__ Any comments or bug reports for Matrix should be posted there. .. rubric:: How to Use the Matrix @@ -140,7 +140,7 @@ Below is a summary of all the Matrix web pages: .. rubric:: Example Application Description Page :name: example-application-description-page -Below is an example application description page. Description pages can +Below is an example application description page. Description pages can be used to add additional information that may not be obvious. .. raw:: html @@ -164,7 +164,7 @@ be used to add additional information that may not be obvious. .. rubric:: Coming Soon Page :name: coming-soon-page -- Displayed for Matrix directories that doesn't contain any +- Displayed for Matrix directories that doesn't contain any applications within it. .. rubric:: Application/Script Execution Page @@ -196,14 +196,14 @@ the .desktop files and also the html that is generated from the various php pages. While this provides a substantial performance boost, developers must be aware that any changes to the Matrix apps folder which includes adding, deleting and modifying files can result in many -problems within Matrix. To properly update Matrix with the latest -information, Matrix's caches need to be cleared.  +problems within Matrix. To properly update Matrix with the latest +information, Matrix's caches need to be cleared. -.. rubric:: Automatically Clearing Matrix Cache +.. rubric:: Automatically Clearing Matrix Cache :name: automaticallyclearing-matrix-cache The simpliest way to clear Matrix's cache is to use the Refresh Matrix -application found within Matrix's Settings submenu. Simply running the +application found within Matrix's Settings submenu. Simply running the application will cause Matrix to clear all the cached files and regenerate the .desktops cache file. Once the application is done running, Matrix will be updated with the latest information found from @@ -226,7 +226,7 @@ To clear Matrix's caches you need to perform only two steps: 1. Execute the generate.php file. -In the terminal of the target system, enter the folllowing line of code. +In the terminal of the target system, enter the folllowing line of code. :: @@ -235,7 +235,7 @@ In the terminal of the target system, enter the folllowing line of code. or In a browser enter the following url. Note replace with the -IP address of the target system. +IP address of the target system. :: @@ -257,7 +257,7 @@ Once the above steps are completed, Matrix will be updated. .. rubric:: Launching Matrix :name: launching-matrix -Use the following shell script in the target's terminal window to run +Use the following shell script in the target's terminal window to run Matrix as a background task: :: @@ -267,7 +267,7 @@ Matrix as a background task: This script ensures that the touchscreen has been calibrated and that the Qt Window server is running. -Alternatively, Matrix can be launched manually with this full syntax: +Alternatively, Matrix can be launched manually with this full syntax: :: @@ -296,7 +296,7 @@ Touchscreen** `__ -Blank template icons for Matrix can be found here:  +Blank template icons for Matrix can be found here: `**gforge.ti.com/gf/download/frsrelease/712/5167/blank\_icons\_1.1.tar.gz** `__ .. rubric:: Creating the .Desktop File @@ -390,7 +389,7 @@ The fields and values are case sensitive. .. rubric:: Creating a New Matrix Directory :name: creating-a-new-matrix-directory -You can get all the files including the image discussed below from the +You can get all the files including the image discussed below from the following file: `**Ex\_directory.tar.gz** `__ @@ -412,7 +411,7 @@ Fill the contents of the file with the text shown below: This .desktop above tells Matrix that this .desktop is meant to create a new directory since Type=Directory. The directory should be named "Ex -Demo" and will use the icon located within the ex\_directory directory. +Demo" and will use the icon located within the ex\_directory directory. This new directory should be the 5th icon displayed as long as there aren't any other .desktop files that specify X-MATRIX-DisplayPriority=5 and will be displayed in the Matrix Main Menu. Now any applications that @@ -422,21 +421,21 @@ Category parameter set to ex\_dir. - Note that sometimes Linux will rename the .desktop file to the name specified in the Name field. If this occurs don't worry about trying to force it to use the file name specified. -- If you are writing these files in Windows, be sure to use Unix-style - EOL characters +- If you are writing these files in Windows, be sure to use Unix-style + EOL characters -Now move the .desktop file and image into the ex\_directory directory +Now move the .desktop file and image into the ex\_directory directory that was created. -.. rubric:: Moving the Newly created Directory to the Target's - File System +.. rubric:: Moving the Newly created Directory to the Target's + File System :name: moving-the-newly-createddirectory-to-the-targets-filesystem Open the Linux terminal and go to the directory that contains the ex\_directory. -Enter the below command to copy ex\_directory to -the /usr/share/matrix-gui-2.0/apps/ directory located in the target's +Enter the below command to copy ex\_directory to +the /usr/share/matrix-gui-2.0/apps/ directory located in the target's file system. Depending on the targetNFS directory premissions you might have to include sudo before the cp command. @@ -444,8 +443,8 @@ have to include sudo before the cp command. host $ cp ex_directory ~/ti-processor-sdk-linux-[platformName]-evm-xx.xx.xx.xx/targetNFS/usr/share/matrix-gui-2.0/apps/ -If NFS isn't being used then you need to copy the ex\_directory to -the the /usr/share/matrix-gui-2.0/apps/ directory in the target's +If NFS isn't being used then you need to copy the ex\_directory to +the the /usr/share/matrix-gui-2.0/apps/ directory in the target's filesystem. .. rubric:: Updating Matrix @@ -462,7 +461,7 @@ for your Ex Demo. .. rubric:: Creating a New Application :name: creating-a-new-application -This example is assuming that you completed the \ `**Creating a New +This example is assuming that you completed the \ `**Creating a New Matrix Directory** <#creating-a-new-matrix-directory>`__ example. You can get all the files including the image discussed below from the @@ -491,17 +490,17 @@ Fill the contents of the file with the below text: Type=Application lets Matrix know that this .desktop is for an application. The name of the application is "Test App". The -icon example-icon.png can be found within the ex\_application -directory. The command to execute is a shell script that will be located +icon example-icon.png can be found within the ex\_application +directory. The command to execute is a shell script that will be located within ex\_application. The script that is being ran is a simply shell script that output text to the terminal. Therefore, the ProgramType should be set to console. This application should be added to the Ex -Demo directory from the previous example. Therefore, Categories will be +Demo directory from the previous example. Therefore, Categories will be set to ex\_dir which is the same value that X-MATRIX-CategoryTarget is set to. You could optionally remove the Categories field to have this application displayed in Matrix's Main Menu. This application will also have a description page. The html file to be used is located within the -ex\_application directory. A lock is also being used. Therefore, any +ex\_application directory. A lock is also being used. Therefore, any other application including itself that has the same lock can't run simultaneously. @@ -515,7 +514,7 @@ Create a file named test\_script.sh echo "I am finally awake!" | The newly created script needs to have its permission set to be - executable. Enter the below command to give read, write and execute + executable. Enter the below command to give read, write and execute permission to all users and groups for the script: :: @@ -530,19 +529,19 @@ Create a new file called app\_desc.html

Purpose:

The purpose of this application is to demonstrate the ease in adding a new application to Matrix.

-Now move the .desktop file, script file, the png image located in the -Ex\_application.tar.gz file and the html file into the ex\_application +Now move the .desktop file, script file, the png image located in the +Ex\_application.tar.gz file and the html file into the ex\_application folder. -.. rubric:: Moving the newly created Directory to the Target System +.. rubric:: Moving the newly created Directory to the Target System :name: moving-the-newly-createddirectory-to-the-target-system Open the Linux terminal and go to the directory that contains the ex\_application directory. Enter the below command to copy the ex\_application directory -to /usr/share/matrix-gui-2.0/apps/ located in the target's file system. -Depending on the targetNFS directory permissions you might have to +to /usr/share/matrix-gui-2.0/apps/ located in the target's file system. +Depending on the targetNFS directory permissions you might have to include sudo before the cp command. :: @@ -557,21 +556,21 @@ the target's filesystem. :name: updating-matrix-2 Now in either local or remote Matrix go to the Settings directory and -click and then run the Refresh Matrix application. This will delete all +click and then run the Refresh Matrix application. This will delete all the cache files that Matrix generates and regenerate all the needed files which will include any updates that you have made. -Now if you go back to the Matrix's Main Menu and click on the Ex -Demo directory you should see your newly created application. Click on +Now if you go back to the Matrix's Main Menu and click on the Ex +Demo directory you should see your newly created application. Click on the application's icon and you will see the application's description page. Click the Run button and your application will execute. If you try -to run two instances of this application simultaneously via local and +to run two instances of this application simultaneously via local and remote Matrtix you will get a message saying that the program can't run because a lock exists. Because of X-Matrix-Lock being set to test\_app\_lock, Matrix knows not to run two instances of a -program simultaneously that share the same lock. You can run the +program simultaneously that share the same lock. You can run the application again when the previous application is done running. You have just successfully added a new application to Matrix using all -the possibly parameters!  +the possibly parameters! diff --git a/source/linux/Examples_and_Demos/_WLAN_and_Bluetooth.rst b/source/linux/Examples_and_Demos/_WLAN_and_Bluetooth.rst index 937eb3fdd..ebedd2b78 100644 --- a/source/linux/Examples_and_Demos/_WLAN_and_Bluetooth.rst +++ b/source/linux/Examples_and_Demos/_WLAN_and_Bluetooth.rst @@ -7,7 +7,7 @@ Demos available for the WL127x. Many of the demos are platform-agnostic, others apply specifically to a single platform. The WL127x's dual mode 802.11 b/g/n and *Bluetooth* transceiver -gives users a robust selection of applications. A list of some basic use +gives users a robust selection of applications. A list of some basic use cases preloaded on the EVMs can be seen below: | diff --git a/source/linux/Foundational_Components/Graphics/Rogue/Build_Guide.rst b/source/linux/Foundational_Components/Graphics/Rogue/Build_Guide.rst index 617216d87..d859a5a17 100644 --- a/source/linux/Foundational_Components/Graphics/Rogue/Build_Guide.rst +++ b/source/linux/Foundational_Components/Graphics/Rogue/Build_Guide.rst @@ -94,20 +94,20 @@ In the repository the following structure can be seen: ├── README └── targetfs ├── am62_linux - │   └── lws-generic - │   └── release + │ └── lws-generic + │ └── release ├── am62p_linux - │   └── lws-generic - │   └── release + │ └── lws-generic + │ └── release ├── j721e_linux - │   └── lws-generic - │   └── release + │ └── lws-generic + │ └── release ├── j721s2_linux - │   └── lws-generic - │   └── release + │ └── lws-generic + │ └── release ├── j722s_linux - │   └── lws-generic - │   └── release + │ └── lws-generic + │ └── release └── j784s4_linux └── lws-generic └── release diff --git a/source/linux/Foundational_Components/Graphics/SGX/Build_Guide.rst b/source/linux/Foundational_Components/Graphics/SGX/Build_Guide.rst index b8240fbee..a268313a6 100644 --- a/source/linux/Foundational_Components/Graphics/SGX/Build_Guide.rst +++ b/source/linux/Foundational_Components/Graphics/SGX/Build_Guide.rst @@ -92,19 +92,19 @@ In the repository the following structure can be seen: ├── README.md └── targetfs ├── common - │   ├── 50-pvrsrvctl.rules.template - │   ├── etc - │   └── pvrsrvctl.service.template + │ ├── 50-pvrsrvctl.rules.template + │ ├── etc + │ └── pvrsrvctl.service.template ├── ti335x_linux - │   └── lws-generic + │ └── lws-generic ├── ti343x_linux - │   └── lws-generic + │ └── lws-generic ├── ti437x_linux - │   └── lws-generic + │ └── lws-generic ├── ti443x_linux - │   └── lws-generic + │ └── lws-generic ├── ti572x_linux - │   └── lws-generic + │ └── lws-generic └── ti654x_linux └── lws-generic diff --git a/source/linux/Foundational_Components/Graphics/SGX/SGX_Debug_Info.rst b/source/linux/Foundational_Components/Graphics/SGX/SGX_Debug_Info.rst index 6e9bb0d53..0fc330e24 100644 --- a/source/linux/Foundational_Components/Graphics/SGX/SGX_Debug_Info.rst +++ b/source/linux/Foundational_Components/Graphics/SGX/SGX_Debug_Info.rst @@ -161,7 +161,7 @@ You can print the SGX clock rate in a debug build as below: .. code-block:: c IMG_UINT32 rate = clk_get_rate(psSysSpecData->psSGX_FCK); - PVR_TRACE(("Sgx clock is %dMHz", HZ_TO_MHZ(rate))); + PVR_TRACE(("Sgx clock is %dMHz", HZ_TO_MHZ(rate))); Depending on the TI platform used, this will vary from 200 to 532 MHz. Ensure that SGX is running at the right clock. diff --git a/source/linux/Foundational_Components/IPC/_IPC_for_AM57xx.rst b/source/linux/Foundational_Components/IPC/_IPC_for_AM57xx.rst index 4696c29d7..7cb7986c2 100644 --- a/source/linux/Foundational_Components/IPC/_IPC_for_AM57xx.rst +++ b/source/linux/Foundational_Components/IPC/_IPC_for_AM57xx.rst @@ -79,17 +79,17 @@ CCS is installed at: /mnt/data/user/ti/my_custom_ccs_x.x.x_install ├── ccsvX - │   ├── ccs_base - │   ├── doc - │   ├── eclipse - │   ├── install_info - │   ├── install_logs - │   ├── install_scripts - │   ├── tools - │   ├── uninstall_ccs - │   ├── uninstall_ccs.dat - │   ├── uninstallers - │   └── utils + │ ├── ccs_base + │ ├── doc + │ ├── eclipse + │ ├── install_info + │ ├── install_logs + │ ├── install_scripts + │ ├── tools + │ ├── uninstall_ccs + │ ├── uninstall_ccs.dat + │ ├── uninstallers + │ └── utils ├── Code Composer Studio x.x.x.desktop └── xdctools_x_xx_xx_xx_core ├── bin @@ -158,34 +158,34 @@ Here are the key files that you should see after a successful build: :: ├── dsp1 - │   └── bin - │      ├── debug - │      │   └── server_dsp1.xe66 - │      └── release - │      └── server_dsp1.xe66 + │ └── bin + │ ├── debug + │ │ └── server_dsp1.xe66 + │ └── release + │ └── server_dsp1.xe66 ├── dsp2 - │   └── bin - │      ├── debug - │      │   └── server_dsp2.xe66 - │      └── release - │      └── server_dsp2.xe66 + │ └── bin + │ ├── debug + │ │ └── server_dsp2.xe66 + │ └── release + │ └── server_dsp2.xe66 ├── host - │      ├── debug - │      │   └── app_host - │      └── release - │      └── app_host + │ ├── debug + │ │ └── app_host + │ └── release + │ └── app_host ├── ipu1 - │   └── bin - │      ├── debug - │      │   └── server_ipu1.xem4 - │      └── release - │      └── server_ipu1.xem4 + │ └── bin + │ ├── debug + │ │ └── server_ipu1.xem4 + │ └── release + │ └── server_ipu1.xem4 └── ipu2 -    └── bin -       ├── debug -       │   └── server_ipu2.xem4 -       └── release -       └── server_ipu2.xem4 + └── bin + ├── debug + │ └── server_ipu2.xem4 + └── release + └── server_ipu2.xem4 | @@ -313,14 +313,14 @@ Finally, we can run the example on DSP1: root@am57xx-evm:~# cat /proc/iomem [snip...] - 58060000-58078fff : core - 58820000-5882ffff : l2ram - 58882000-588820ff : /ocp/mmu@58882000 - 80000000-9fffffff : System RAM - 80008000-808d204b : Kernel code - 80926000-809c96bf : Kernel data - a0000000-abffffff : CMEM - ac000000-ffcfffff : System RAM + 58060000-58078fff : core + 58820000-5882ffff : l2ram + 58882000-588820ff : /ocp/mmu@58882000 + 80000000-9fffffff : System RAM + 80008000-808d204b : Kernel code + 80926000-809c96bf : Kernel data + a0000000-abffffff : CMEM + ac000000-ffcfffff : System RAM | @@ -547,30 +547,24 @@ ipc/packages/ti/ipc/remoteproc/rsc\_table\_vayu\_dsp.h DSP_MEM_TEXT, 0, DSP_MEM_TEXT_SIZE, 0, 0, "DSP_MEM_TEXT", }, -   { TYPE_CARVEOUT, DSP_MEM_DATA, 0, DSP_MEM_DATA_SIZE, 0, 0, "DSP_MEM_DATA", }, -   { TYPE_CARVEOUT, DSP_MEM_HEAP, 0, DSP_MEM_HEAP_SIZE, 0, 0, "DSP_MEM_HEAP", }, -   { TYPE_CARVEOUT, DSP_MEM_IPC_DATA, 0, DSP_MEM_IPC_DATA_SIZE, 0, 0, "DSP_MEM_IPC_DATA", }, -   { TYPE_TRACE, TRACEBUFADDR, 0x8000, 0, "trace:dsp", }, -   -   { TYPE_DEVMEM, DSP_MEM_IPC_VRING, PHYS_MEM_IPC_VRING, @@ -856,7 +850,7 @@ ipc\_3\_43\_02\_04/examples/DRA7XX\_linux\_elf/ex02\_messageq/ipu1/IpuAmmu.cfg AMMU.largePages[0].size = AMMU.Large_512M; AMMU.largePages[0].L1_cacheable = AMMU.CachePolicy_CACHEABLE; AMMU.largePages[0].L1_posted = AMMU.PostedPolicy_POSTED; -   + /* Peripheral regions: Large Page (512M); non-cacheable */ /* config large page[1] to map 512MB VA 0x60000000 to L3 0x60000000 */ AMMU.largePages[1].pageEnabled = AMMU.Enable_YES; @@ -865,7 +859,7 @@ ipc\_3\_43\_02\_04/examples/DRA7XX\_linux\_elf/ex02\_messageq/ipu1/IpuAmmu.cfg AMMU.largePages[1].size = AMMU.Large_512M; AMMU.largePages[1].L1_cacheable = AMMU.CachePolicy_NON_CACHEABLE; AMMU.largePages[1].L1_posted = AMMU.PostedPolicy_POSTED; -   + /* Private, Shared and IPC Data regions: Large page (512M); cacheable */ /* config large page[2] to map 512MB VA 0x80000000 to L3 0x80000000 */ AMMU.largePages[2].pageEnabled = AMMU.Enable_YES; @@ -923,25 +917,25 @@ ipc/packages/ti/ipc/remoteproc/rsc\_table\_vayu\_ipu.h #define IPU_MEM_TEXT 0x0 #define IPU_MEM_DATA 0x80000000 -   + #define IPU_MEM_IOBUFS 0x90000000 -   + #define IPU_MEM_IPC_DATA 0x9F000000 #define IPU_MEM_IPC_VRING 0x60000000 #define IPU_MEM_RPMSG_VRING0 0x60000000 #define IPU_MEM_RPMSG_VRING1 0x60004000 #define IPU_MEM_VRING_BUFS0 0x60040000 #define IPU_MEM_VRING_BUFS1 0x60080000 -   + #define IPU_MEM_IPC_VRING_SIZE SZ_1M #define IPU_MEM_IPC_DATA_SIZE SZ_1M -   + #if defined(VAYU_IPU_1) #define IPU_MEM_TEXT_SIZE (SZ_1M) #elif defined(VAYU_IPU_2) #define IPU_MEM_TEXT_SIZE (SZ_1M * 6) #endif -   + #if defined(VAYU_IPU_1) #define IPU_MEM_DATA_SIZE (SZ_1M * 5) #elif defined(VAYU_IPU_2) @@ -961,13 +955,11 @@ ipc/packages/ti/ipc/remoteproc/rsc\_table\_vayu\_ipu.h IPU_MEM_TEXT, 0, IPU_MEM_TEXT_SIZE, 0, 0, "IPU_MEM_TEXT", }, -   { TYPE_CARVEOUT, IPU_MEM_DATA, 0, IPU_MEM_DATA_SIZE, 0, 0, "IPU_MEM_DATA", }, -   { TYPE_CARVEOUT, IPU_MEM_IPC_DATA, 0, @@ -1191,7 +1183,7 @@ To do this, follow these steps. - For **Target**, select ti.targets.elf.C66 - For **Platform**, select ti.platforms.evmDRA7XX - Once the platform is selected, edit its name buy hand and - append :dsp1 to the end. After this it should be + append :dsp1 to the end. After this it should be ti.platforms.evmDRA7XX:dsp1 - Go ahead and leave the **Build-profile** set to debug. - Hit the OK button. @@ -1393,11 +1385,11 @@ before BIOS\_start() .. code-block:: c ipc_main(); -   + if (callIpcStartup) { IpcMgr_ipcStartup(); } -   + /* Start BIOS */ BIOS_start(); return (0); @@ -1567,12 +1559,12 @@ following log on the serial IO console: :: - uart driver and utils example test cases : + uart driver and utils example test cases : Enter 16 characters or press Esc 1234567890123456 <- user input Data received is 1234567890123456 <- loopback from user input - uart driver and utils example test cases : + uart driver and utils example test cases : Enter 16 characters or press Esc | @@ -1639,7 +1631,7 @@ To do this, follow these steps. - For **Target**, select **ti.targets.arm.elf.M4** - For **Platform**, select **ti.platforms.evmDRA7XX** - Once the platform is selected, edit its name buy hand and - append :ipu2 to the end. After this it should be + append :ipu2 to the end. After this it should be ti.platforms.evmDRA7XX:ipu2 - Go ahead and leave the **Build-profile** set to debug. - Hit the OK button. @@ -1855,7 +1847,7 @@ needs to be performed by the M4. | -**Modified Code :** +**Modified Code :** :: @@ -1872,7 +1864,7 @@ adding the following code before Board\_init API call: (CSL_l4per_cm_core_componentRegs *)CSL_MPU_L4PER_CM_CORE_REGS; CSL_FINST(l4PerCmReg->CM_L4PER_UART3_CLKCTRL_REG, L4PER_CM_CORE_COMPONENT_CM_L4PER_UART3_CLKCTRL_REG_MODULEMODE, ENABLE); - while(CSL_L4PER_CM_CORE_COMPONENT_CM_L4PER_UART3_CLKCTRL_REG_IDLEST_FUNC != + while(CSL_L4PER_CM_CORE_COMPONENT_CM_L4PER_UART3_CLKCTRL_REG_IDLEST_FUNC != CSL_FEXT(l4PerCmReg->CM_L4PER_UART3_CLKCTRL_REG, L4PER_CM_CORE_COMPONENT_CM_L4PER_UART3_CLKCTRL_REG_IDLEST)); diff --git a/source/linux/Foundational_Components/IPC/_IPC_for_AM65xx.rst b/source/linux/Foundational_Components/IPC/_IPC_for_AM65xx.rst index 3e0cfbf75..1997ea89f 100644 --- a/source/linux/Foundational_Components/IPC/_IPC_for_AM65xx.rst +++ b/source/linux/Foundational_Components/IPC/_IPC_for_AM65xx.rst @@ -109,22 +109,22 @@ Here are the key files that you should see after a successful build: :: ├── r5f-0 - │   └── bin - │      ├── debug - │      │   └── server_r5f-0.xer5f - │      └── release - │      │   └── server_r5f-0.xer5f + │ └── bin + │ ├── debug + │ │ └── server_r5f-0.xer5f + │ └── release + │ │ └── server_r5f-0.xer5f ├── r5f-1 - │   └── bin - │      ├── debug - │      │   └── server_r5f-1.xer5f - │      └── release - │      │   └── server_r5f-1.xer5f + │ └── bin + │ ├── debug + │ │ └── server_r5f-1.xer5f + │ └── release + │ │ └── server_r5f-1.xer5f ├── host - │      ├── debug - │      │   └── app_host - │      └── release - │      └── app_host + │ ├── debug + │ │ └── app_host + │ └── release + │ └── app_host | diff --git a/source/linux/Foundational_Components/IPC/_Quick_Start_Guide.rst b/source/linux/Foundational_Components/IPC/_Quick_Start_Guide.rst index 8c7022f81..77b69002e 100644 --- a/source/linux/Foundational_Components/IPC/_Quick_Start_Guide.rst +++ b/source/linux/Foundational_Components/IPC/_Quick_Start_Guide.rst @@ -102,7 +102,7 @@ The source code are located in: to set up the build environment. | -| **DSP RTOS :** +| **DSP RTOS :** **1.** Install RTOS Proc SDK at the default location diff --git a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/ADC.rst b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/ADC.rst index 74ac70195..dea09e4f2 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/ADC.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/ADC.rst @@ -379,7 +379,7 @@ Important folders in the iio:deviceX directory are: - in\_voltageX\_en: is this channel enabled? - in\_voltageX\_index: index of this channel in the buffer's chunks -- in\_voltageX\_type : How the ADC stores its data. Reading this file +- in\_voltageX\_type : How the ADC stores its data. Reading this file should return you a string something like below: :: diff --git a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Audio.rst b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Audio.rst index 5a417a732..dae24b77c 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Audio.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Audio.rst @@ -851,7 +851,7 @@ Additional Information #. `ALSA User Space Library `__ #. `Using ALSA Audio - API `__ Author: Paul + API `__ Author: Paul Davis .. rubric:: Software Help diff --git a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Camera/VIP.rst b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Camera/VIP.rst index 6618e69ca..d00c05f77 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Camera/VIP.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Camera/VIP.rst @@ -607,7 +607,7 @@ any modifications) into the device. Following points to keep in mind – .vpdma_fmt = { &vpdma_raw_fmts[VPDMA_DATA_FMT_RAW8], }, }, -   + const struct vpdma_data_format vpdma_raw_fmts[] = { [VPDMA_DATA_FMT_RAW8] = { .type = VPDMA_DATA_FMT_TYPE_YUV, diff --git a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Crypto.rst b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Crypto.rst index 3eec6f57e..95a17d513 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Crypto.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Crypto.rst @@ -28,7 +28,7 @@ devices: For devices with available cryptographic hardware accelerators, a Linux driver and additionally a Cryptodev kernel module (for OpenSSL) is used -to access them.  Other devices use the pure software implementation of these +to access them. Other devices use the pure software implementation of these cryptographic operations. .. ifconfig:: CONFIG_crypto in ('sa2ul') @@ -49,11 +49,11 @@ kernel configuration. .. code-block:: text Symbol: CRYPTO_DEV_SA2UL [=m] - ¦ Type : tristate - ¦ Prompt: Support for TI security accelerator - ¦ Location: - ¦ -> Cryptographic API (CRYPTO [=y]) - ¦ (1) -> Hardware crypto devices (CRYPTO_HW [=y]) + | Type : tristate + | Prompt: Support for TI security accelerator + | Location: + | -> Cryptographic API (CRYPTO [=y]) + | (1) -> Hardware crypto devices (CRYPTO_HW [=y]) To check if sa2ul module is properly installed, run the below command from the Linux command prompt: diff --git a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Network/CPSW.rst b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Network/CPSW.rst index a3de58a87..0d61d9cf8 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Network/CPSW.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Network/CPSW.rst @@ -1075,11 +1075,11 @@ Below commands will be redirected to the phy driver: :: - [ speed %d ] + [ speed %d ] [ duplex half|full ] [ autoneg on|off ] [ wol p|u|m|b|a|g|s|d... ] - [ sopass %x:%x:%x:%x:%x:%x ] + [ sopass %x:%x:%x:%x:%x:%x ] .. note:: @@ -1096,7 +1096,7 @@ Sets the driver message type flags by name or number :: - [ msglvl %d | msglvl type on|off ... ] + [ msglvl %d | msglvl type on|off ... ] # ethtool -s eth0 msglvl drv off # ethtool -s eth0 msglvl ifdown off # ethtool -s eth0 msglvl ifup off diff --git a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Network/NetCP.rst b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Network/NetCP.rst index 0c1b2d924..271faf704 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Network/NetCP.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Network/NetCP.rst @@ -1022,7 +1022,7 @@ NOT the current frequency. if (clock_gettime(clkid, &ts)) { perror("clock_gettime"); } else { - printf("clock time: %ld.%09ld or %s", + printf("clock time: %ld.%09ld or %s", ts.tv_sec, ts.tv_nsec, ctime(&ts.tv_sec)); } @@ -1232,7 +1232,7 @@ asserted low when the polarity bit is low. pfd.timeout.nsec = 0; pfd.timeout.flags = ~PPS_TIME_INVALID; if (ioctl(fd, PPS_FETCH, &pfd)) { - pr_err("failed to fetch PPS: %m"); + pr_err("failed to fetch PPS: %m"); return 0; } @@ -1788,7 +1788,7 @@ PTP EXTTS feature of the Linux PTP infrastructure. /* reading timestamps */ for (i=0; i < 10; i++) { read(fd, &event, sizeof(event)); - printf("event index %u at %lld.%09u\n", event.index, + printf("event index %u at %lld.%09u\n", event.index, event.t.sec, event.t.nsec); } @@ -2032,12 +2032,12 @@ Delete the 100-th entry in the table • version: the ALE version information • enable: 0 to disable the ALE, 1 to enable ALE (should be 1 for normal operations) • clear: set to 1 to clear the table (refer to [1] for description) - • ageout : set to 1 to force age out of entries (refer to [1] for description]) - • p0_uni_flood_en : set to 1 to enable unknown unicasts to be flooded to host port. Set to 0 to not flood such unicasts. Note: if set to 0, CPSW may delay + • ageout : set to 1 to force age out of entries (refer to [1] for description]) + • p0_uni_flood_en : set to 1 to enable unknown unicasts to be flooded to host port. Set to 0 to not flood such unicasts. Note: if set to 0, CPSW may delay sending packets to the SOC host until it learns what mac addresses the host is using. - • vlan_nolearn : set to 1 to prevent VLAN id from being learned along with source address. - • no_port_vlan : set to 1 to allow processing of packets received with VLAN ID=0; set to 0 to replace received packets with VLAN ID=0 to the VLAN set in the port’s default VLAN register. - • oui_deny : 0/1 (refer to [1] for a description of this bit) + • vlan_nolearn : set to 1 to prevent VLAN id from being learned along with source address. + • no_port_vlan : set to 1 to allow processing of packets received with VLAN ID=0; set to 0 to replace received packets with VLAN ID=0 to the VLAN set in the port’s default VLAN register. + • oui_deny : 0/1 (refer to [1] for a description of this bit) • bypass: set to 1 to enable ALE bypass. In this mode the CPSW will not act as switch on receive; instead it will forward all received traffic from external ports to the host port. Set to 0 for normal (switched) operations. • rate_limit_tx: set to 1 for rate limiting to apply to transmit direction, set to 0 for receive direction. Refer to [1] for a description of this bit. @@ -2051,25 +2051,25 @@ Delete the 100-th entry in the table o 3: forwarding • port_state.1: set the port 1 state. • port_state.2: set the port 2 state - • drop_untagged.0 : set to 1 to drop untagged packets received on port 0 (host port) - • drop_untagged.1 : set to 1 to drop untagged packets received on port 1 - • drop_untagged.2 : set to 1 to drop untagged packets received on port 2 - • drop_unknown.0 : set to 1 to drop packets received on port 0 (host port) with unknown VLAN tags. Set to 0 to allows these to be processed - • drop_unknown.1 : set to 1 to drop packets received on port 1 with unknown VLAN tags. Set to 0 to allow these to be processed. - • drop_unknown.2 : set to 1 to drop packets received on port 2 with unknown VLAN tags. Set to 0 to allow these to be processed. - • nolearn.0 : set to 1 to disable address learning for port 0 - • nolearn.1 : set to 1 to disable address learning for port 1 - • nolearn.2 : set to 1 to disable address learning for port 2 - • unknown_vlan_member : this is the port mask for packets received with unknown VLAN IDs. The port mask is a 5 bit number with a bit representing each port. Bit 0 refers to the + • drop_untagged.0 : set to 1 to drop untagged packets received on port 0 (host port) + • drop_untagged.1 : set to 1 to drop untagged packets received on port 1 + • drop_untagged.2 : set to 1 to drop untagged packets received on port 2 + • drop_unknown.0 : set to 1 to drop packets received on port 0 (host port) with unknown VLAN tags. Set to 0 to allows these to be processed + • drop_unknown.1 : set to 1 to drop packets received on port 1 with unknown VLAN tags. Set to 0 to allow these to be processed. + • drop_unknown.2 : set to 1 to drop packets received on port 2 with unknown VLAN tags. Set to 0 to allow these to be processed. + • nolearn.0 : set to 1 to disable address learning for port 0 + • nolearn.1 : set to 1 to disable address learning for port 1 + • nolearn.2 : set to 1 to disable address learning for port 2 + • unknown_vlan_member : this is the port mask for packets received with unknown VLAN IDs. The port mask is a 5 bit number with a bit representing each port. Bit 0 refers to the host port. A ‘1’ in bit position N means include the port in further forwarding decision. (e.g., port mask = 0x7 means ports 0 (internal), 1 and 2 should be included in the forwarding decision). Refer to [1] for more details. - • unknown_mcast_flood= : this is the port mask for packets received with unkwown VLAN ID and unknown (un-registered) destination multicast address. This port_mask will be used in the + • unknown_mcast_flood= : this is the port mask for packets received with unkwown VLAN ID and unknown (un-registered) destination multicast address. This port_mask will be used in the multicast flooding decision. unknown multicast flooding. • unknown_reg_flood: this is the port mask for packets received with unknown VLAN ID and registered (known) destination multicast address. It is used in the multicast forwarding decision. • unknown_force_untag_egress: this is a port mask to control if VLAN tags are stripped off on egress or not. Set to 1 to force tags to be stripped by h/w prior to transmission - • bcast_limit.0 : threshold for broadcast pacing on port 0 . + • bcast_limit.0 : threshold for broadcast pacing on port 0 . • bcast_limit.1: threshold for broadcast pacing on port 1. - • bcast_limit.2 : threshold for broadcast pacing on port 2 . + • bcast_limit.2 : threshold for broadcast pacing on port 2 . • mcast_limit.0: threshold for multicast pacing on port 0 . • mcast_limit.1: threshold for multicast pacing on port 1 .. • mcast_limit.2: threshold for multicast pacing on port 2 . @@ -2179,13 +2179,13 @@ egress on port 2 only: echo “unknown_force_untag_egress=7” > /sys/class/net/eth0/device/ale_control -To set to Port 1 to “Admit tagged” (i.e. drop un-tagged) : +To set to Port 1 to “Admit tagged” (i.e. drop un-tagged) : :: echo “drop_untagged.1=1” > /sys/class/net/eth0/device/ale_control -To set to Port 1 to “Admit all” : +To set to Port 1 to “Admit all” : :: diff --git a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Network/PRUSS.rst b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Network/PRUSS.rst index 967302389..336553197 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Network/PRUSS.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Network/PRUSS.rst @@ -131,7 +131,7 @@ the supplied firmware. .. rubric:: Kernel configuration :name: kernel-configuration -To enable/disable PRU Ethernet driver support, start the Linux Kernel Configuration tool: +To enable/disable PRU Ethernet driver support, start the Linux Kernel Configuration tool: :: diff --git a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/PCIe/PCIe_Root_Complex.rst b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/PCIe/PCIe_Root_Complex.rst index a5311a3ec..34a076f5a 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/PCIe/PCIe_Root_Complex.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/PCIe/PCIe_Root_Complex.rst @@ -478,7 +478,7 @@ including desktop, mobile, server, storage and embedded communications. procedure can be used to boot Linux kernel using this rootfs. Boot EVM to u-boot prompt. Add following env variables to u-boot - environment :- + environment :- :: diff --git a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/QSPI.rst b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/QSPI.rst index 1523240cb..fc3e41fc6 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/QSPI.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/QSPI.rst @@ -431,9 +431,9 @@ Refer :ref:`here ` for UBIFS. root~# ubiformat /dev/mtd9 ubiformat: mtd9 (nor), size 23199744 bytes (22.1 MiB), 354 eraseblocks of 65536 bytes (64.0 KiB), min. I/O size 1 bytes - libscan: scanning eraseblock 353 -- 100 % complete + libscan: scanning eraseblock 353 -- 100% complete ubiformat: 354 eraseblocks are supposedly empty - ubiformat: formatting eraseblock 353 -- 100 % complete + ubiformat: formatting eraseblock 353 -- 100% complete root:~# ubiattach -p /dev/mtd9 [ 270.874428] ubi0: attaching mtd9 [ 270.914131] ubi0: scanning is finished diff --git a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Storage/MMC-SD.rst b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Storage/MMC-SD.rst index 035d9a316..07d28c417 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Storage/MMC-SD.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Storage/MMC-SD.rst @@ -331,7 +331,7 @@ Driver Configuration for pending background operations and give the card some time to service them before they become critical. This feature is already part of the framework and to start using it the User needs to enable: - EXT\_CSD : BKOPS\_EN [163] BIT 0. + EXT\_CSD : BKOPS\_EN [163] BIT 0. **This can be done using the "mmc-utils" tool from user space or using the "mmc" command in U-boot.** diff --git a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Storage/NAND.rst b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Storage/NAND.rst index 07996068b..d3e0bd45e 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Storage/NAND.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Storage/NAND.rst @@ -169,8 +169,8 @@ Refer :ref:`here ` for UBIFS. .. rubric:: **Board specific configurations** :name: board-specific-configurations -| Following table gives details about NAND devices present on various - EVM boards +| Following table gives details about NAND devices present on various + EVM boards +----------+----------+----------+----------+----------+----------+----------+----------+----------+ | EVM | NAND | Size | Bus-Widt | Block-Si | Page-Siz | OOB-Size | ECC | Hardware | @@ -250,7 +250,7 @@ BCH16. So BCH8 ECC Scheme has been used on this board. .. rubric:: Configurations (GPMC Specific) :name: configurations-gpmc-specific -.. rubric:: **How to enable GPMC NAND driver in Linux Kernel ?** +.. rubric:: **How to enable GPMC NAND driver in Linux Kernel ?** :name: how-to-enable-gpmc-nand-driver-in-linux-kernel .. ifconfig:: CONFIG_part_family in ('AM62X_family') @@ -262,7 +262,7 @@ BCH16. So BCH8 ECC Scheme has been used on this board. => setenv name_overlays ti/k3-am62x-lp-sk-nand.dtbo GPMC NAND driver can be enabled/disabled via *Linux Kernel -Configuration* tool. Enable below Configs to enable MTD Support along +Configuration* tool. Enable below Configs to enable MTD Support along with MTD NAND driver support :: diff --git a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/USB/AM62_DWC3.rst b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/USB/AM62_DWC3.rst index 7a7962442..2b8e9a0bc 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/USB/AM62_DWC3.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/USB/AM62_DWC3.rst @@ -80,7 +80,7 @@ Kernel Configuration tool. ... -- Select DesignWare USB3 DRD Core Support and Texas Instruments AM62 +- Select DesignWare USB3 DRD Core Support and Texas Instruments AM62 Platforms :: @@ -93,7 +93,7 @@ Kernel Configuration tool. Texas Instruments AM62 Platforms ... -- Select 'xHCI HCD (USB 3.0) SUPPORT' from  menuconfig in 'USB support' +- Select 'xHCI HCD (USB 3.0) SUPPORT' from menuconfig in 'USB support' :: @@ -103,7 +103,7 @@ Kernel Configuration tool. <*> xHCI HCD (USB 3.0) support ... -- Select 'USB Gadget Support --->' from menuconfig in 'USB support' and +- Select 'USB Gadget Support --->' from menuconfig in 'USB support' and select the needed gadgets. (By default all gadgets are made as modules) diff --git a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/USB/DWC3.rst b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/USB/DWC3.rst index ed99b5d22..62fbfdce4 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/USB/DWC3.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/USB/DWC3.rst @@ -33,7 +33,7 @@ DWC3 is integrated in AM65x, OMAP5, DRA7x and AM437x SoCs from TI. (drivers/extcon/extcon-palmas.c) notifies the events to OMAP glue driver (driver/usb/dwc3/dwc3-omap.c) via the extcon framework. The glue driver writes the events to the software mailbox present in DWC3 glue (SS USB - OTG controller  module in the diagram) which interrupts the core using + OTG controller module in the diagram) which interrupts the core using UTMI+ signals. .. image:: /images/Omap5-dwc3.png @@ -189,7 +189,7 @@ Kernel Configuration tool. ... -- Select DesignWare USB3 DRD Core Support and Texas Instruments OMAP5 +- Select DesignWare USB3 DRD Core Support and Texas Instruments OMAP5 and similar Platforms :: @@ -233,7 +233,7 @@ Kernel Configuration tool. <*> TI PIPE3 PHY Driver ... -- Select 'xHCI HCD (USB 3.0) SUPPORT' from  menuconfig in 'USB support' +- Select 'xHCI HCD (USB 3.0) SUPPORT' from menuconfig in 'USB support' :: @@ -243,7 +243,7 @@ Kernel Configuration tool. <*> xHCI HCD (USB 3.0) support ... -- Select 'USB Gadget Support --->' from menuconfig in 'USB support' and +- Select 'USB Gadget Support --->' from menuconfig in 'USB support' and select the needed gadgets. (By default all gadgets are made as modules) @@ -286,7 +286,7 @@ Kernel Configuration tool. EHCI Debug Device mode (serial) ---> USB Webcam Gadget -.. rubric:: **Configuring DWC3 in gadget only**  +.. rubric:: **Configuring DWC3 in gadget only** :name: configuring-dwc3-in-gadget-only .. ifconfig:: CONFIG_part_family in ('General_family') @@ -425,7 +425,7 @@ Connecting a USB2.0 pendrive to the USB host port gives the following prints [ 479.437774] usb 1-1: ep 0x81 - rounding interval to 128 microframes, ep desc says 255 microframes [ 479.447454] usb 1-1: ep 0x2 - rounding interval to 128 microframes, ep desc says 255 microframes [ 479.458124] usb-storage 1-1:1.0: USB Mass Storage device detected - [ 479.465355] scsi1 : usb-storage 1-1:1.0 + [ 479.465355] scsi1 : usb-storage 1-1:1.0 [ 480.784475] scsi 1:0:0:0: Direct-Access Sony Storage Media 0100 PQ: 0 ANSI: 4 [ 480.801677] sd 1:0:0:0: [sda] 61046784 512-byte logical blocks: (31.2 GB/29.1 GiB) [ 480.820740] sd 1:0:0:0: [sda] Write Protect is off @@ -680,8 +680,8 @@ modes is through a USB Reset. :name: other-resources For general Linux USB subsystem -- `Usbgeneralpage `__ +- `Usbgeneralpage `__ USB Debugging -- `elinux.org/images/1/17/USB\_Debugging\_and\_Profiling\_Techniques.pdf `__ +- `elinux.org/images/1/17/USB\_Debugging\_and\_Profiling\_Techniques.pdf `__ diff --git a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/USB/MUSB.rst b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/USB/MUSB.rst index 5505c6dde..c400f8704 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/USB/MUSB.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/USB/MUSB.rst @@ -190,5 +190,5 @@ Table: - The Mentor USB driver can be built as module or built into kernel. For more information refer to `USB - configuration `__  + configuration `__ diff --git a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/VPE.rst b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/VPE.rst index 709a935b6..eb40f62d9 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/VPE.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/VPE.rst @@ -64,7 +64,7 @@ and deinterlacing: .. rubric:: Unsupported Features/Limitations :name: unsupported-featureslimitations -- Following formats are not supported : YUV444, YVYU, VYUY, NV16, NV61, +- Following formats are not supported : YUV444, YVYU, VYUY, NV16, NV61, NV21, 16bit and Lower RGB formats are not supported. - Passing of custom scaler and CSC coeffficients through user space are not supported. diff --git a/source/linux/Foundational_Components/Kernel/_LTP-DDT_Validation.rst b/source/linux/Foundational_Components/Kernel/_LTP-DDT_Validation.rst index d7e446356..9bbcd5946 100644 --- a/source/linux/Foundational_Components/Kernel/_LTP-DDT_Validation.rst +++ b/source/linux/Foundational_Components/Kernel/_LTP-DDT_Validation.rst @@ -131,7 +131,7 @@ Supported platforms with LTP-DDT .. rubric:: Host Platform Requirements :name: host-platform-requirements -Linux host is required : +Linux host is required : - for compiling LTP-DDT. - to host the NFS server to boot the EVM with NFS as root filesystem @@ -221,7 +221,7 @@ and the platform (option -P) to use. For example: -D : Run test under additional background load on Secondary storage -m : Run test under additional background load on Main memory -i : Run test under additional background load on IO Bus - -n  : Run test with network traffic in background. + -n : Run test with network traffic in background. Please refer to README-DDT file section 8) for more details. diff --git a/source/linux/Foundational_Components/Power_Management/pm_suspend_resume.rst b/source/linux/Foundational_Components/Power_Management/pm_suspend_resume.rst index 254cba35e..5d83c322d 100644 --- a/source/linux/Foundational_Components/Power_Management/pm_suspend_resume.rst +++ b/source/linux/Foundational_Components/Power_Management/pm_suspend_resume.rst @@ -217,7 +217,7 @@ cycle should look like this: PM: noirq resume of devices complete after 39.113 msecs PM: early resume of devices complete after 10.180 msecs net eth0: initializing cpsw version 1.12 (0) - net eth0: phy found : id is : 0x4dd074 + net eth0: phy found : id is : 0x4dd074 PM: resume of devices complete after 368.844 msecs Restarting tasks ... done $ diff --git a/source/linux/Foundational_Components/Tools/Code_Composer_Studio/_GDB_Setup_with_CCS.rst b/source/linux/Foundational_Components/Tools/Code_Composer_Studio/_GDB_Setup_with_CCS.rst index c47c8ac38..4a84af4ef 100644 --- a/source/linux/Foundational_Components/Tools/Code_Composer_Studio/_GDB_Setup_with_CCS.rst +++ b/source/linux/Foundational_Components/Tools/Code_Composer_Studio/_GDB_Setup_with_CCS.rst @@ -29,32 +29,32 @@ prerequisites are met: #. In CCS, select the project you wish to work with by clicking on it and highlighting it. -#. Select the Run -> Debug Configurations menu item.  This opens a +#. Select the Run -> Debug Configurations menu item. This opens a dialog box as shown below. .. Image:: /images/Initial-debug-configurations.png -3. Double click C/C++ Remote Application.  You should then see a new - debug configuration named "helloworld Debug" as shown below.  +3. Double click C/C++ Remote Application. You should then see a new + debug configuration named "helloworld Debug" as shown below. Select your target connection from the Connection drop-down - box.  In the example the target connection is called My Target EVM. + box. In the example the target connection is called My Target EVM. .. Image:: /images/Hello_World_Debug_Configuration.png 4. Click the Search Project button to open the Program Selection dialog - box below.  Click on the "armle - /helloworld/Debug/helloworld" item and + box below. Click on the "armle - /helloworld/Debug/helloworld" item and click OK. .. Image:: /images/Debug-config-2.png -5. Click the "Browse..." button for "Remote Absolute File Path for C/C++ - Application".  Navgate to the executable file on the remote file system.  - For this example, the executable file is found at "/usr/bin/helloworld". +5. Click the "Browse..." button for "Remote Absolute File Path for C/C++ + Application". Navgate to the executable file on the remote file system. + For this example, the executable file is found at "/usr/bin/helloworld". .. Image:: /images/Auto-debug-config-main-tab.png -6. Click the Debugger tab.  On the Debugger page, the Main tab should +6. Click the Debugger tab. On the Debugger page, the Main tab should be selected. Click Browse next to "GDB debugger" and browse to the GDB executable. @@ -64,7 +64,7 @@ GDB should be located at: | | Click browse next to "GDB command file" and browse to the .gdbinit file in the SDK install directory. -| GDB init file should be located at : /.gdbinit +| GDB init file should be located at : /.gdbinit | When you try to browse to the .gdbinit file, you will need to right click and select Show Hidden Files to see the file. @@ -86,21 +86,21 @@ the Debug Configuration window. You are now ready to debug the application! -.. rubric:: Running the Debug Session +.. rubric:: Running the Debug Session :name: running-thedebug-session -1. Make sure that you are setup for the debug build configuration which - contains symbol information.  In the C/C++ perspective, click on the +1. Make sure that you are setup for the debug build configuration which + contains symbol information. In the C/C++ perspective, click on the helloworld project to select it and -   Project -> Build Configurations -> Set Active -> Debug. + Project -> Build Configurations -> Set Active -> Debug. -2. Click the green "bug" icon to build the executable, transfer the +2. Click the green "bug" icon to build the executable, transfer the executable to the target, start gdbserver and and start debugging. -   CCS will change to the CCS Debug perspective. The debug tab will + CCS will change to the CCS Debug perspective. The debug tab will show the running threads and their status. The source code window will - show the program halted at the first executable source code line in the + show the program halted at the first executable source code line in the main() function. The Variables window will show the local variables and their current values. @@ -112,16 +112,16 @@ You are now ready to debug the application! 6. Use the debugger "Step Over" and "Step Into" icons to step through the source code. -7. To resume program execution, click the Run -> Resume menu item.  +7. To resume program execution, click the Run -> Resume menu item. -   NOTE: Do not click the Run -> Debug menu item, as that will attempt + NOTE: Do not click the Run -> Debug menu item, as that will attempt to start a new debug session. -   From here, you can make changes to the C source files, save the + From here, you can make changes to the C source files, save the changes and then just click the green "Bug" icon again and you will be debugging the new executable on the target. -  (Each time you start the debugger the executable is built, + (Each time you start the debugger the executable is built, automatically transferred to the target board and the gdbserver program is started for you.) @@ -129,7 +129,7 @@ You are now ready to debug the application! :name: stopping-the-debug-session When finished debugging the helloworld application, click the Run -> -Resume menu item.   To terminate the program,  click the Terminate icon +Resume menu item. To terminate the program, click the Terminate icon in CCS (this icon is a red square). .. rubric:: Manually Terminating Gdbserver @@ -154,8 +154,8 @@ Once setup, you can follow these steps to terminate gdbserver: 3) Click on "Executable Name" in the table headers to sort the list by executable name. -4) Find the gdbserver process.  Right click on it and select Kill.  This - will open a "Send a Kill Signal" dialog box.  Click the Kill button. +4) Find the gdbserver process. Right click on it and select Kill. This + will open a "Send a Kill Signal" dialog box. Click the Kill button. .. Image:: /images/Shell-processes.png diff --git a/source/linux/Foundational_Components/Tools/Code_Composer_Studio/_Kernel_Debugging_with_CCS.rst b/source/linux/Foundational_Components/Tools/Code_Composer_Studio/_Kernel_Debugging_with_CCS.rst index d067d6be2..a11614c54 100644 --- a/source/linux/Foundational_Components/Tools/Code_Composer_Studio/_Kernel_Debugging_with_CCS.rst +++ b/source/linux/Foundational_Components/Tools/Code_Composer_Studio/_Kernel_Debugging_with_CCS.rst @@ -99,7 +99,7 @@ Capabilities tab in the Preference dialog (select **Window** --> 3. Click on the icon **New launch configuration** (Top left of the pane) -4. Set the fields  **C/C++ Application:** and\ **Project:** +4. Set the fields **C/C++ Application:** and\ **Project:** respectively to the existing project in the workspace and the binary executable file @@ -130,11 +130,11 @@ Capabilities tab in the Preference dialog (select **Window** --> being used, but it is possible to use also CodeSourcery or other toolchain. -   Click browse next to "GDB command file" and browse to the .gdbinit - file in the SDK install directory.  When you try to browse to the - .gdbinit file, you will need + Click browse next to "GDB command file" and browse to the .gdbinit + file in the SDK install directory. When you try to browse to the + .gdbinit file, you will need -   to R-Click -> Show Hidden Files to see the file.   Click the Close + to R-Click -> Show Hidden Files to see the file. Click the Close button and you are now ready to debug the application! - In this example of the 06.00.00.00 SDK, the path is: @@ -458,9 +458,9 @@ expected address (wrong library or version mismatch?) warning: .dynamic section for "/lib/libc.so.6" is not at the expected address (wrong library or version mismatch?) When SDKs setup.sh script, it should automatically generate a .gdbinit -file for you in the base directory of the SDK.  +file for you in the base directory of the SDK. -The file will contain the line: set sysroot /targetNFS. +The file will contain the line: set sysroot /targetNFS. An example would be diff --git a/source/linux/Foundational_Components/Tools/Code_Composer_Studio/_Remote_Explorer_Setup_with_CCS.rst b/source/linux/Foundational_Components/Tools/Code_Composer_Studio/_Remote_Explorer_Setup_with_CCS.rst index 1bde67a8a..2994d651c 100644 --- a/source/linux/Foundational_Components/Tools/Code_Composer_Studio/_Remote_Explorer_Setup_with_CCS.rst +++ b/source/linux/Foundational_Components/Tools/Code_Composer_Studio/_Remote_Explorer_Setup_with_CCS.rst @@ -73,25 +73,25 @@ Connection Wizard. .. Image:: /images/X-New_Connection.png -#. Do NOT click the Finish button.  Click **Next** +#. Do NOT click the Finish button. Click **Next** #. Check **ssh.files** to use the *Secure Shell* protocol for communication .. Image:: /images/Ssh-files.png -#. Do NOT click the Finish button.  Click **Next** +#. Do NOT click the Finish button. Click **Next** #. Check **processes.shell.linux** to use a shell to work with processes on the remote system .. Image:: /images/Processes_.png -#. Do NOT click the Finish button.  Click **Next** +#. Do NOT click the Finish button. Click **Next** #. Check **ssh.shells** to use *Secure Shell* to work will shell commands .. Image:: /images/Shells.png -#. Do NOT click the Finish button.  Click **Next** +#. Do NOT click the Finish button. Click **Next** #. Check **ssh.terminals** to use *Secure Shell* to work with terminals .. Image:: /images/Terminals.png diff --git a/source/linux/Foundational_Components/_CMEM.rst b/source/linux/Foundational_Components/_CMEM.rst index c669c0424..88e7f9142 100644 --- a/source/linux/Foundational_Components/_CMEM.rst +++ b/source/linux/Foundational_Components/_CMEM.rst @@ -165,7 +165,7 @@ section of 'config.bib' of your BSP: :: - CMEM_DSP 89000000 02800000 RESERVED ; 40 MB + CMEM_DSP 89000000 02800000 RESERVED ; 40 MB That reserves 40MB of memory for CMEM, DSPLINK, DSP code as well as DSP heap usage starting at virtual address 0x89000000. There is no @@ -189,28 +189,28 @@ TI EVM3530: ; Make 1 pool available for allocation for block 1 "NumPools0"=dword:7 "NumPools1"=dword:0 -   + "Block0_NumBuffers_Pool0"=dword:20 "Block0_PoolSize_Pool0"=dword:1000 ; size in bytes (hex) "Block0_NumBuffers_Pool1"=dword:8 "Block0_PoolSize_Pool1"=dword:20000 ; size in bytes (hex) "Block0_NumBuffers_Pool2"=dword:5 "Block0_PoolSize_Pool2"=dword:100000 ; size in bytes (hex) -   + "Block0_NumBuffers_Pool3"=dword:1 "Block0_PoolSize_Pool3"=dword:15cfc0 ; size in bytes (hex) "Block0_NumBuffers_Pool4"=dword:1 "Block0_PoolSize_Pool4"=dword:3e800 ; size in bytes (hex) "Block0_NumBuffers_Pool5"=dword:1 "Block0_PoolSize_Pool5"=dword:36ee80 ; size in bytes (hex) -   + "Block0_NumBuffers_Pool6"=dword:3 "Block0_PoolSize_Pool6"=dword:96000 ; size in bytes (hex) -   + ;; "Block1_NumBuffers_Pool1"=dword:2 - ;; "Block1_PoolSize_Pool1"=dword:4000 ; size in bytes (hex) -   -   + ;; "Block1_PoolSize_Pool1"=dword:4000 ; size in bytes (hex) + + ; Physical start + physical end can be use to ask CMEM to map a specific ; range of physical addresses. ; This is a potential security risk. If physical start == 0 then the code @@ -218,7 +218,7 @@ TI EVM3530: ; physical end - physical start == length of allocation. In the special ; case, memory is allocated via a call to AllocPhysMem() (as shown in ; this example). MmMapIoSpace() is used to map the normal case where - ; physical start != 0. + ; physical start != 0. ; ; physical start and end for block 0 "PhysicalStart0"=dword:85000000 @@ -450,13 +450,13 @@ of processes to start as a parameter. Now load the kernel module :: -  % insmod cmemk.ko phys_start=0xcaf01000 phys_end=0xCB601000 pools=4x1000 phys_start_1=0xCB601000 phys_end_1=0xCB701000 pools_1=4x1000 + % insmod cmemk.ko phys_start=0xcaf01000 phys_end=0xCB601000 pools=4x1000 phys_start_1=0xCB601000 phys_end_1=0xCB701000 pools_1=4x1000 (Uses DDR) :: -  % insmod cmemk.ko phys_start=0x40300000 phys_end=0x4033FFFF pools=4x500 phys_start_1=0x4033FFFF phys_end_1=0x4037ffff pools_1=4x500 allowOverlap=1 + % insmod cmemk.ko phys_start=0x40300000 phys_end=0x4033FFFF pools=4x500 phys_start_1=0x4033FFFF phys_end_1=0x4037ffff pools_1=4x500 allowOverlap=1 (Uses OCMC1, for this rebuild the Translate Test app with macro BUFFER\_SIZE = 500 at line #49 in file @@ -465,7 +465,7 @@ test, :: -  % multi_process 3 + % multi_process 3 where 3 is the number of processes to be spawned. @@ -477,13 +477,13 @@ This app tests the address translation. Now load the kernel module :: -  % insmod cmemk.ko phys_start=0xcaf01000 phys_end=0xCB601000 pools=1x3145728 + % insmod cmemk.ko phys_start=0xcaf01000 phys_end=0xCB601000 pools=1x3145728 (Uses DDR) :: -  % insmod cmemk.ko phys_start=0x40300000 phys_end=0x4037ffff pools=1x20000 allowOverlap=1 + % insmod cmemk.ko phys_start=0x40300000 phys_end=0x4037ffff pools=1x20000 allowOverlap=1 (Uses OCMC1, for this rebuild the Translate Test app with macro BUFSIZE = 20000 at line #48 in file (linuxutils)/src/cmem/tests/translate.c) Now @@ -491,7 +491,7 @@ run the Translate test, :: -  % translate + % translate .. rubric:: API Test :name: api-test @@ -502,7 +502,7 @@ Now load the kernel module 'cmemk.ko' with the below command: :: -  % insmod cmemk.ko phys_start=0x87800000 phys_end=0x87F00000 pools=4xBUFSIZE phys_start_1=0x87F00000 phys_end_1=0x88000000 pools_1=4xBUFSIZE + % insmod cmemk.ko phys_start=0x87800000 phys_end=0x87F00000 pools=4xBUFSIZE phys_start_1=0x87F00000 phys_end_1=0x88000000 pools_1=4xBUFSIZE where BUFSIZE is the number of bytes you plan on passing as command line parameter to apitest. If in doubt, use a larger number as BUFSIZE @@ -511,13 +511,13 @@ Now run the API test, :: -  % apitest + % apitest (e.g) With BUFSIZE=10240 :: -  % apitest 10240 + % apitest 10240 .. rubric:: CMEM FAQ :name: cmem-faq diff --git a/source/linux/Foundational_Components/_OpenCV.rst b/source/linux/Foundational_Components/_OpenCV.rst index 421bfef25..01c3c7655 100644 --- a/source/linux/Foundational_Components/_OpenCV.rst +++ b/source/linux/Foundational_Components/_OpenCV.rst @@ -632,7 +632,7 @@ implementation: :: ... - String opts = format("-D CN=%d -D NMIXTURES=%d%s -DTIDSP_MOG2 -D SUBLINE_CACHE=%d", nchannels, nmixtures, bShadowDetection ? " -DSHADOW_DETECT" : "", subline_cache); + String opts = format("-D CN=%d -D NMIXTURES=%d%s -DTIDSP_MOG2 -D SUBLINE_CACHE=%d", nchannels, nmixtures, bShadowDetection ? " -DSHADOW_DETECT" : "", subline_cache); kernel_apply.create("mog2_kernel", ocl::video::bgfg_mog2_oclsrc, opts); ... @@ -716,8 +716,8 @@ modules/video/src/opencl/bgfg\_mog2.cl: TI DSP specific OpenCL implementation ... - cv::String kname = format( "tidsp_gaussian" ) ; - cv::String kdefs = format("-D T=%s -D T1=%s -D cn=%d", ocl::typeToStr(type), ocl::typeToStr(depth), cn) ; + cv::String kname = format( "tidsp_gaussian" ) ; + cv::String kdefs = format("-D T=%s -D T1=%s -D cn=%d", ocl::typeToStr(type), ocl::typeToStr(depth), cn) ; ocl::Kernel k(kname.c_str(), ocl::imgproc::gauss_oclsrc, kdefs.c_str() ); ... @@ -907,7 +907,7 @@ Profiling results of DSP optimized OpenCV OpenCL kernels (SDK 3.1), AM5728 platf -------------------------------------------------------------------------------------- ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -**Single channel, 1200x709, barcode ROI detection use case** +**Single channel, 1200x709, barcode ROI detection use case** ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ .. csv-table:: @@ -1112,17 +1112,17 @@ http://downloads.ti.com/mctools/esd/docs/opencl/memory/host-malloc-extension.htm #include #include #include -   + using namespace std; using namespace cv; using namespace cl; -   + const int NumElements = 512*512; // image size const int NumWorkGroups = 256; const int VectorElements = 4; const int NumVecElements = NumElements / VectorElements; const int WorkGroupSize = NumVecElements / NumWorkGroups; -   + void ProcRawCL(Mat &mat_src, const std::string &kernel_name) { //=============================================================== @@ -1136,7 +1136,7 @@ http://downloads.ti.com/mctools/esd/docs/opencl/memory/host-malloc-extension.htm Mat test_mat1(mat_src.size(), CV_8UC1, ptr_cmem1); Mat test_mat2(mat_src.size(), CV_8UC1, ptr_cmem2); Mat test_mat3(mat_src.size(), CV_8UC1, ptr_cmem3); -   + mat_src.copyTo(test_mat1); threshold(test_mat1, test_mat2, 128.0, 192.0, THRESH_BINARY); imwrite("out_cmem1.jpg", test_mat2); @@ -1146,31 +1146,31 @@ http://downloads.ti.com/mctools/esd/docs/opencl/memory/host-malloc-extension.htm { Context context(CL_DEVICE_TYPE_ACCELERATOR); std::vector devices = context.getInfo(); -   + int d = 0; std::string str; ifstream t(kernel_name); std::string kernelStr((istreambuf_iterator(t)), istreambuf_iterator()); -   + devices[d].getInfo(CL_DEVICE_NAME, &str); cout << "DEVICE: " << str << endl << endl; -   + Program::Sources source(1, std::make_pair(kernelStr.c_str(), kernelStr.length())); Program program = Program(context, source); program.build(devices); -   + Kernel kernel(program, "maskVector"); Buffer bufA (context, CL_MEM_READ_ONLY | CL_MEM_USE_HOST_PTR, bufsize, ptr_cmem2); Buffer bufDst (context, CL_MEM_WRITE_ONLY | CL_MEM_USE_HOST_PTR, bufsize, ptr_cmem1); kernel.setArg(0, bufA); kernel.setArg(1, bufDst); -   + Event ev1; -   + CommandQueue Q(context, devices[d], CL_QUEUE_PROFILING_ENABLE); Q.enqueueNDRangeKernel(kernel, NullRange, NDRange(NumVecElements), NDRange(WorkGroupSize), NULL, &ev1); ev1.wait(); -   + ocl_event_times(ev1, "Kernel Exec"); imwrite("out_cmem2.jpg", test_mat1); } diff --git a/source/linux/Foundational_Components/_OpenVX.rst b/source/linux/Foundational_Components/_OpenVX.rst index 1f3772ee5..e7c312a84 100644 --- a/source/linux/Foundational_Components/_OpenVX.rst +++ b/source/linux/Foundational_Components/_OpenVX.rst @@ -62,26 +62,26 @@ kernels and call them using OpenVX APIs. | | layer also binds TIOVX framework to | | | a specific OS like Linux or TI-RTOS | +--------------------------------------+--------------------------------------+ -| TIOVX Kernel Wrapper | Kernel wrappers allow TI and | +| TIOVX Kernel Wrapper | Kernel wrappers allow TI and | | | customers to integrate a natively | | | implemented kernel into the TIOVX | | | framework. | +--------------------------------------+--------------------------------------+ -| TIOVX Conformance tests | OpenVX conformance test from Khronos | +| TIOVX Conformance tests | OpenVX conformance test from Khronos | | | to make sure an implementation | | | implements OpenVX according to | | | specification. | +--------------------------------------+--------------------------------------+ -There are two versions of VXLIB kernels: without BAM framework, and -with BAM framework. BAM is a low level framework representing directed +There are two versions of VXLIB kernels: without BAM framework, and +with BAM framework. BAM is a low level framework representing directed acyclic graph, where EDMA transfers are heavily utilized to bring 2D memory objects to higher speed L2 memory, thus improving performance almost twofold. -Current release has kernels with BAM framework. This framework +Current release has kernels with BAM framework. This framework achieves higher performance via heavy use of EDMA, which brings blocks -of data from remote DDR memory to local L2, while DSP does the +of data from remote DDR memory to local L2, while DSP does the processing. List of these kernels can be checked in https://git.ti.com/processor-sdk/tiovx/trees/master/kernels/openvx-core/c66x/bam. @@ -91,7 +91,7 @@ https://git.ti.com/processor-sdk/tiovx/trees/master/kernels/openvx-core/c66x/bam There are 44 kernels in current release of VXLIB (typically there are multiple implementations for different data types). -Here is complete list of DSP kernel wrappers (wrappers are part of TIOVX): +Here is complete list of DSP kernel wrappers (wrappers are part of TIOVX): - AbsDiff - AccumulateSquare @@ -147,30 +147,30 @@ Following TIOVX components are present in EVM filesystem: | | | using different test | | | | vectors | +--------------------------+--------------------------+--------------------------+ -| DSP firmware | /lib/firmware/dra7-dsp1- | DSP firmware including | +| DSP firmware | /lib/firmware/dra7-dsp1- | DSP firmware including | | | fw.xe66.openvx, | DSP side of TIOVX | | | | framwork implementation, | | | /lib/firmware/dra7-dsp | IPC implementation, | -| | 2-fw.xe66.openvx | DSP kernels (part of | -| | | VXLIB DSP library) - for | +| | 2-fw.xe66.openvx | DSP kernels (part of | +| | | VXLIB DSP library) - for | | | | DSP1. This firmware is | | | | loaded at boot time, or | | | | using procedure | | | | mentioned below (to | -| | | switch from OCL firmware | -| | | to TIOVX firmware) | +| | | switch from OCL firmware | +| | | to TIOVX firmware) | +--------------------------+--------------------------+--------------------------+ TIOVX release 1.0.0.0 runs exclusively wrt OpenCL, as both firmwares use -common resources DSP cores and CMEM memory. That is: application can be +common resources DSP cores and CMEM memory. That is: application can be either TIOVX-based, or OpenCL -based. Future releases may remove this -limitation and use static split in resources (between OpenCL and +limitation and use static split in resources (between OpenCL and OpenVX). **TIOVX needs CMEM memory with two blocks**: block 0 is big DDR block for exchange of big buffers (>100MB) and block 1 (~1MB) which is used as shared memory visible from all cores to exchange shared data objects (typically in OCMC) -.. rubric:: Switch from OpenCL to OpenVX firmware: +.. rubric:: Switch from OpenCL to OpenVX firmware: :name: switch-from-opencl-to-openvxfirmware Run the command below to switch from OpenCL to OpenVx firmware: @@ -184,7 +184,7 @@ Run the command below to switch from OpenCL to OpenVx firmware: First, it is necessary to copy test vectors from https://git.ti.com/processor-sdk/tiovx/trees/master/conformance_tests/test_data -to EVM filesystem (e.g. ~/tiovx/test\_data).Then run following +to EVM filesystem (e.g. ~/tiovx/test\_data).Then run following commands: :: @@ -235,7 +235,7 @@ Please note that last ~3000 lines of test log include performance data (execution time and number of pixels processed) useful for further evaluation. -.. rubric:: Switch from OpenVX, back to OpenCL firmware: +.. rubric:: Switch from OpenVX, back to OpenCL firmware: :name: switch-from-openvx-back-to-openclfirmware After finishing running the TIOVX test application, switch the firmware back to the default for OpenCL: @@ -249,7 +249,7 @@ After finishing running the TIOVX test application, switch the firmware back to | TIOVX framework implementation is available at https://git.ti.com/processor-sdk/tiovx/trees/master -| TIOVX sample application including IPC implementation based on +| TIOVX sample application including IPC implementation based on standard MessageQ, as well as application running conformance tests, can be found at https://git.ti.com/processor-sdk/tiovx-app/trees/master diff --git a/source/linux/Foundational_Components_Multimedia_IVAHD.rst b/source/linux/Foundational_Components_Multimedia_IVAHD.rst index a948c9d6d..62ff25071 100644 --- a/source/linux/Foundational_Components_Multimedia_IVAHD.rst +++ b/source/linux/Foundational_Components_Multimedia_IVAHD.rst @@ -331,15 +331,15 @@ space conversion. :: 1. Decode-> Scale->Display - target # gst-launch-1.0 -v filesrc location=example_h264.mp4 ! qtdemux ! h264parse ! \ - ducatih264dec ! vpe ! 'video/x-raw, format=(string)NV12, width=(int)720, height=(int)480' ! kmssink + target # gst-launch-1.0 -v filesrc location=example_h264.mp4 ! qtdemux ! h264parse ! \ + ducatih264dec ! vpe ! 'video/x-raw, format=(string)NV12, width=(int)720, height=(int)480' ! kmssink :: 2. Color space conversion: - target # gst-launch-1.0 -v videotestsrc ! 'video/x-raw, format=(string)YUY2, width= \ - (int)1280, height=(int)720' ! vpe ! 'video/x-raw, format=(string)NV12, width=(int)720, height=(int)480' \ -  ! kmssink + target # gst-launch-1.0 -v videotestsrc ! 'video/x-raw, format=(string)YUY2, width= \ + (int)1280, height=(int)720' ! vpe ! 'video/x-raw, format=(string)NV12, width=(int)720, height=(int)480' \ + ! kmssink .. note:: 1. While using playbin for playing the stream, vpe plugin is automatically picked up. However vpe cannot be used @@ -353,18 +353,18 @@ respectively. :: Capture and Display Fullscreen - target # gst-launch-1.0 v4l2src device=/dev/video1 num-buffers=1000 io-mode=4 ! 'video/x-raw, \ - format=(string)YUY2, width=(int)1280, height=(int)720' ! vpe num-input-buffers=8 ! queue ! kmssink + target # gst-launch-1.0 v4l2src device=/dev/video1 num-buffers=1000 io-mode=4 ! 'video/x-raw, \ + format=(string)YUY2, width=(int)1280, height=(int)720' ! vpe num-input-buffers=8 ! queue ! kmssink :: Note: The following pipelines can also be used for NV12 capture-display usecase. Dmabuf is allocated by v4l2src if io-mode=4 and by kmssink and imported by v4l2src if io-mode=5 - target # gst-launch-1.0 v4l2src device=/dev/video1 num-buffers=1000 io-mode=4 ! 'video/x-raw, \ - format=(string)NV12, width=(int)1280, height=(int)720' ! kmssink - target # gst-launch-1.0 v4l2src device=/dev/video1 num-buffers=1000 io-mode=5 ! 'video/x-raw, \ - format=(string)NV12, width=(int)1280, height=(int)720' ! kmssink + target # gst-launch-1.0 v4l2src device=/dev/video1 num-buffers=1000 io-mode=4 ! 'video/x-raw, \ + format=(string)NV12, width=(int)1280, height=(int)720' ! kmssink + target # gst-launch-1.0 v4l2src device=/dev/video1 num-buffers=1000 io-mode=5 ! 'video/x-raw, \ + format=(string)NV12, width=(int)1280, height=(int)720' ! kmssink | @@ -372,8 +372,8 @@ respectively. Capture and Display to a window in wayland 1. refer Wayland/Weston to start the weston - 2. target # gst-launch-1.0 v4l2src device=/dev/video1 num-buffers=1000 io-mode=4 ! 'video/x-raw, \ - format=(string)YUY2, width=(int)1280, height=(int)720' ! vpe num-input-buffers=8 ! queue ! waylandsink + 2. target # gst-launch-1.0 v4l2src device=/dev/video1 num-buffers=1000 io-mode=4 ! 'video/x-raw, \ + format=(string)YUY2, width=(int)1280, height=(int)720' ! vpe num-input-buffers=8 ! queue ! waylandsink :: @@ -382,34 +382,34 @@ respectively. if io-mode=4 and by waylandsink and imported by v4l2src if io-mode=5. Waylandsink supports both shm and drm. A new property use-drm is added to specify drm allocator based bufferpool to be used. When using ducati or vpe plugins, use-drm is set in caps as true. - target # gst-launch-1.0 v4l2src device=/dev/video1 num-buffers=1000 io-mode=4 ! 'video/x-raw, \ - format=(string)NV12, width=(int)1280, height=(int)720' ! waylandsink use-drm=true - target # gst-launch-1.0 v4l2src device=/dev/video1 num-buffers=1000 io-mode=5 ! 'video/x-raw, \ - format=(string)NV12, width=(int)1280, height=(int)720' ! waylandsink use-drm=true + target # gst-launch-1.0 v4l2src device=/dev/video1 num-buffers=1000 io-mode=4 ! 'video/x-raw, \ + format=(string)NV12, width=(int)1280, height=(int)720' ! waylandsink use-drm=true + target # gst-launch-1.0 v4l2src device=/dev/video1 num-buffers=1000 io-mode=5 ! 'video/x-raw, \ + format=(string)NV12, width=(int)1280, height=(int)720' ! waylandsink use-drm=true | :: Capture and Encode into a MP4 file. - target # gst-launch-1.0 -e v4l2src device=/dev/video1 num-buffers=1000 io-mode=4 ! 'video/x-raw, \ - format=(string)YUY2, width=(int)1280, height=(int)720, framerate=(fraction)30/1' ! vpe num-input-buffers=8 ! \ - queue ! ducatimpeg4enc bitrate=4000 ! queue ! mpeg4videoparse ! qtmux ! filesink location=x.mp4 + target # gst-launch-1.0 -e v4l2src device=/dev/video1 num-buffers=1000 io-mode=4 ! 'video/x-raw, \ + format=(string)YUY2, width=(int)1280, height=(int)720, framerate=(fraction)30/1' ! vpe num-input-buffers=8 ! \ + queue ! ducatimpeg4enc bitrate=4000 ! queue ! mpeg4videoparse ! qtmux ! filesink location=x.mp4 :: Note: The following pipeline can be used in usecases where vpe processing is not required. - target # gst-launch-1.0 -e v4l2src device=/dev/video1 num-buffers=1000 io-mode=5 ! 'video/x-raw, \ - format=(string)NV12, width=(int)1280, height=(int)720, framerate=(fraction)30/1' ! ducatimpeg4enc bitrate=4000 ! \ - queue ! mpeg4videoparse ! qtmux ! filesink location=x.mp4 + target # gst-launch-1.0 -e v4l2src device=/dev/video1 num-buffers=1000 io-mode=5 ! 'video/x-raw, \ + format=(string)NV12, width=(int)1280, height=(int)720, framerate=(fraction)30/1' ! ducatimpeg4enc bitrate=4000 ! \ + queue ! mpeg4videoparse ! qtmux ! filesink location=x.mp4 :: Capture and Encode and Display in parallel. - target # gst-launch-1.0 -e v4l2src device=/dev/video1 num-buffers=1000 io-mode=4 ! 'video/x-raw, \ - format=(string)YUY2, width=(int)1280, height=(int)720, framerate=(fraction)30/1' ! vpe num-input-buffers=8 ! tee name=t  ! \ - queue ! ducatimpeg4enc bitrate=4000 ! queue ! mpeg4videoparse ! qtmux ! filesink location=x.mp4 t. ! queue ! kmssink + target # gst-launch-1.0 -e v4l2src device=/dev/video1 num-buffers=1000 io-mode=4 ! 'video/x-raw, \ + format=(string)YUY2, width=(int)1280, height=(int)720, framerate=(fraction)30/1' ! vpe num-input-buffers=8 ! tee name=t ! \ + queue ! ducatimpeg4enc bitrate=4000 ! queue ! mpeg4videoparse ! qtmux ! filesink location=x.mp4 t. ! queue ! kmssink Below provides more gstreamer pipeline examples. @@ -417,7 +417,7 @@ Below provides more gstreamer pipeline examples. :: - target # gst-launch-1.0 filesrc location=waterfall-352-288-nv12-inp.yuv ! videoparse width=352 height=288 format=nv12 ! video/x-raw, width=352, height=288 ! ducatih264enc ! filesink location=waterfall-352-288-nv12-inp_gst.h264 + target # gst-launch-1.0 filesrc location=waterfall-352-288-nv12-inp.yuv ! videoparse width=352 height=288 format=nv12 ! video/x-raw, width=352, height=288 ! ducatih264enc ! filesink location=waterfall-352-288-nv12-inp_gst.h264 The cap filter of "video/x-raw, width=352, height=288" is needed in this pipeline to specify the width and height. Otherwise, variable width and @@ -429,7 +429,7 @@ corrupted. :: - target # gst-launch-1.0 filesrc location= 4k.nv12 ! videoparse width=3840 height=2160 format=nv12 framerate=12/1 ! video/x-raw, width=3840, height=2160 ! ducatih264enc level=51 profile=100 bitrate=16000 ! filesink location=4k.h264 + target # gst-launch-1.0 filesrc location= 4k.nv12 ! videoparse width=3840 height=2160 format=nv12 framerate=12/1 ! video/x-raw, width=3840, height=2160 ! ducatih264enc level=51 profile=100 bitrate=16000 ! filesink location=4k.h264 .. rubric:: Full HD at 60fps Encoding :name: full-hd-at-60fps-encoding @@ -474,13 +474,13 @@ corrupted. :: - target # gst-launch-1.0 filesrc location=.265 ! 'video/x-raw, format=(string)NV12, framerate=(fraction)24/1, width=(int)1280, height=(int)720'  ! h265dec threads=2 ! vpe ! kmssink + target # gst-launch-1.0 filesrc location=.265 ! 'video/x-raw, format=(string)NV12, framerate=(fraction)24/1, width=(int)1280, height=(int)720' ! h265dec threads=2 ! vpe ! kmssink .. rubric:: DSP offloaded image processing pipeline :: - target # gst-launch-1.0 filesrc location=.265 ! 'video/x-raw, format=(string)NV12, framerate=(fraction)24/1, width=(int)1280, height=(int)720'  ! h265dec threads=1 ! videoconvert ! dsp66videokernel kerneltype=1 filtersize=9 lum-only=1 ! videoconvert ! vpe ! 'video/x-raw, format=(string)NV12, width=(int)640, height=(int)480' ! kmssink + target # gst-launch-1.0 filesrc location=.265 ! 'video/x-raw, format=(string)NV12, framerate=(fraction)24/1, width=(int)1280, height=(int)720' ! h265dec threads=1 ! videoconvert ! dsp66videokernel kerneltype=1 filtersize=9 lum-only=1 ! videoconvert ! vpe ! 'video/x-raw, format=(string)NV12, width=(int)640, height=(int)480' ! kmssink This pipeline decodes an H265 clip on ARM A15, offloads the image processing task (Sobel 3x3 kernel) to DSP, and the processed clip is @@ -716,14 +716,14 @@ downloaded and installed. For example, the tool versions used in IPUMM :: - XDCVERSION  ?= xdctools_3_31_02_38_core - BIOSVERSION  ?= bios_6_42_02_29 - IPCVERSION  ?= ipc_3_40_01_08 - CEVERSION  ?= codec_engine_3_24_00_08 - FCVERSION  ?= framework_components_3_40_01_04 - XDAISVERSION  ?= xdais_7_24_00_04 + XDCVERSION ?= xdctools_3_31_02_38_core + BIOSVERSION ?= bios_6_42_02_29 + IPCVERSION ?= ipc_3_40_01_08 + CEVERSION ?= codec_engine_3_24_00_08 + FCVERSION ?= framework_components_3_40_01_04 + XDAISVERSION ?= xdais_7_24_00_04 # TI Compiler Settings - export TMS470CGTOOLPATH ?= $(BIOSTOOLSROOT)/ccsv6/tools/compiler/ti-cgt-arm_5.2.5 + export TMS470CGTOOLPATH ?= $(BIOSTOOLSROOT)/ccsv6/tools/compiler/ti-cgt-arm_5.2.5 Below are direct download links and install instructions for IPUMM 3.00.09.01 build tools. When installing the tools, it is preferable to @@ -925,7 +925,7 @@ shown below. :: FW_NAMES="dra7-dsp1-fw.xe66 dra7-dsp2-fw.xe66 dra7-ipu1-fw.xem4 dra7-ipu2-fw.xem4" - for FW in $FW_NAMES ; do + for FW in $FW_NAMES ; do echo 1 > /sys/class/firmware/$FW/loading cat /lib/firmware/$FW > /sys/class/firmware/$FW/data echo 0 > /sys/class/firmware/$FW/loading diff --git a/source/linux/How_to_Guides/FAQ/How_to_Integrate_Open_Source_Software.rst b/source/linux/How_to_Guides/FAQ/How_to_Integrate_Open_Source_Software.rst index 0d97b2eca..a394f9e0d 100644 --- a/source/linux/How_to_Guides/FAQ/How_to_Integrate_Open_Source_Software.rst +++ b/source/linux/How_to_Guides/FAQ/How_to_Integrate_Open_Source_Software.rst @@ -11,9 +11,9 @@ recipes that were updated while integrating the components to the ├── QT5: - │   ├──Baseline: - │   │ └──meta-qt5:recipes-qt/qt5/: recipes and patches from community - │   │ + │ ├──Baseline: + │ │ └──meta-qt5:recipes-qt/qt5/: recipes and patches from community + │ │ │ └──Arago (TI) updates: │ ├──meta-arago: │ │ ├──meta-arago-distro/recipes-qt/qt5: recipes update and additional patches @@ -31,9 +31,9 @@ recipes that were updated while integrating the components to the │ └──meta-processor-sdk: │ └──recipes-qt/qt5: additional recipe updates and patches ├──Wayland/Weston: - │   ├──Baseline: - │   │ └──oe-core/meta/recipes-graphics/wayland: recipes and patches from community - │   │ + │ ├──Baseline: + │ │ └──oe-core/meta/recipes-graphics/wayland: recipes and patches from community + │ │ │ └──Arago (TI) updates: │ ├──meta-arago: │ │ ├──meta-arago-distro/recipes-graphics/wayland: recipes update and additional patches @@ -44,8 +44,8 @@ recipes that were updated while integrating the components to the Note: There are many modules that depend on wayland. For example: chromium-wayland, qt5/qtwayland, gstreamer1.0-plugins-bad(waylandsink), glmark2 and gtk+3 ├──SGX (Not recommended to modify): - │   ├──Baseline: - │   │ + │ ├──Baseline: + │ │ │ ├──meta-ti: │ │ ├──recipes-graphics/libgles/ti-sgx-ddk-um_ │ │ └──recipes-bsp/powervr-drivers/ti-sgx-ddk-km_ @@ -61,8 +61,8 @@ recipes that were updated while integrating the components to the │ └──meta-processor-sdk: │ └──recipes-graphics/libgles/ti-sgx-ddk-um_version: for non-sgx build only ├──Gstreamer: - │   ├──Baseline: - │   │ + │ ├──Baseline: + │ │ │ ├──meta-openembedded: │ │ └──meta-multimedia/recipes-multimedia/gstreamer-0.10: recipes and patches from community │ │ diff --git a/source/linux/How_to_Guides/Host/AM335x_AM437x_Hardware_Migration_Guide.rst b/source/linux/How_to_Guides/Host/AM335x_AM437x_Hardware_Migration_Guide.rst index 97fc2661f..921d6588f 100644 --- a/source/linux/How_to_Guides/Host/AM335x_AM437x_Hardware_Migration_Guide.rst +++ b/source/linux/How_to_Guides/Host/AM335x_AM437x_Hardware_Migration_Guide.rst @@ -12,7 +12,7 @@ This document explains the differences between the TI AM335x processor and the T Basic Feature Comparison ######################### -The figure and table below show a comparison of the basic features of the AM335x and the AM437x. The remainder of the document presents a comparison of these features in greater detail, and also provides references to the appropriate documentation for further information. +The figure and table below show a comparison of the basic features of the AM335x and the AM437x. The remainder of the document presents a comparison of these features in greater detail, and also provides references to the appropriate documentation for further information. .. Image:: /images/AM335x_AM437x_1.png @@ -189,7 +189,7 @@ Memory Subsystem General Purpose Memory Controller ----------------------------------- -Both AM335x and AM437x support 7 chip selects. +Both AM335x and AM437x support 7 chip selects. External Memory Interface -------------------------- @@ -333,7 +333,7 @@ Table: **AM437x Voltage Rails** +------------------------+------------------------------------------------+-------------------+ | VDDS\_RTC | RTC domain | 1.8V | +------------------------+------------------------------------------------+-------------------+ -| VDDS\_DDR | DDR IO domain (DDR2 / DDR3) | 1.2V - 1.5V | +| VDDS\_DDR | DDR IO domain (DDR2 / DDR3) | 1.2V - 1.5V | +------------------------+------------------------------------------------+-------------------+ | VDDS | Dual voltage IO domains | 1.8V | +------------------------+------------------------------------------------+-------------------+ @@ -379,7 +379,7 @@ Table: **AM437x Voltage Rails** +------------------------+------------------------------------------------+-------------------+ | VDDSHV9 | Dual Voltage IO domain (1.8V/3.3V operation) | 1.8V/3.3V | +------------------------+------------------------------------------------+-------------------+ -| VDDSHV10 | Dual Voltage IO domain (1.8V/3.3V operation) | 1.8V/3.3V | +| VDDSHV10 | Dual Voltage IO domain (1.8V/3.3V operation) | 1.8V/3.3V | +------------------------+------------------------------------------------+-------------------+ | VDDSHV11 | Dual Voltage IO domain (1.8V/3.3V operation) | 1.8V/3.3V | +------------------------+------------------------------------------------+-------------------+ @@ -427,7 +427,7 @@ Table: **AM437x Input Clocks** +------------------+------------------------------------------------------------------------------+---------------------------------------------------+ | CLK\_32K\_RTC | External 32768 Hz crystal with internal 32K Osc or external 32768 Hz clock | 32768 Hz Precise | +------------------+------------------------------------------------------------------------------+---------------------------------------------------+ -| CLK\_32K\_MOSC | Divide down of Master Oscillator Crystal Frequency | Precise 32768 Hz only when using 26 MHz crystal | +| CLK\_32K\_MOSC | Divide down of Master Oscillator Crystal Frequency | Precise 32768 Hz only when using 26 MHz crystal | +------------------+------------------------------------------------------------------------------+---------------------------------------------------+ @@ -573,7 +573,7 @@ Bootmodes | | | |from an SPI EEPROM| | | | |or SPI Flash. | | | | | | -| | | |For both AM335x | +| | | |For both AM335x | | | | |and AM437x, the | | | | |SPI device should | | | | |be connected to | @@ -851,8 +851,8 @@ This table lists different bandwidth restrictions that are needed based on what Communication Interfaces ************************* -MMC/SD  -------- +MMC/SD +------ The MMC/SD modules are binary compatible between the two devices. Except, the CLK32 debounce clock is created by dividing the 96-MHz (48-MHz in AM437x) clock in the PRCM by two and then dividing the resulting 48-MHz (24-MHz in AM437x) clock by a fixed 732.4219 in the Control Module to get a 32-kHz clock. @@ -895,8 +895,8 @@ Real-Time Clock (RTC) The RTC module is identical between the two devices, except for the interface clock source -- AM335x uses CORE\_CLKOUTM4/2, providing a max frequency of 100 MHz. AM437x uses CLK\_M\_OSC, providing a max frequency of 26 MHz. -Ethernet  ---------- +Ethernet +-------- There are small differences between the AM335x and AM437x Ethernet module. @@ -904,22 +904,22 @@ The AM437x module adds support for multi core split processing, connecting the C In AM437x, the cpts\_rft\_clk (IEEE 1588v2 clock) adds DISP\_PLL\_CLK as a third source option. -McSPI  ------- +McSPI +----- AM335x includes 2 McSPI ports, each with two chip select signals. All McSPI have 4 DMA requests to EDMA. AM437x includes 5 McSPI ports. McSPI[0-2] support 4 chip select signals and 8 DMA requests to the eDMA. McSPI[3-4] only support 2 CS signals and 4 DMA requests to the eDMA. -PWM Subsystem (PWMSS)  ----------------------- +PWM Subsystem (PWMSS) +--------------------- The PWM Subsystem contains PWM, eCAP, and eQEP submodules. AM335x has 3 PWMSS instances. AM437x has 6 PWMSS instances, but eCAP3-5 and eQEP3-5 are not used. The PWMSS synchronization of the PWM and eCAP submodules is also different between AM335x and AM437x. -PRU-ICSS - Programmable Real-time Unit Subsystem and Industrial Communications Subsystem  ------------------------------------------------------------------------------------------- +PRU-ICSS - Programmable Real-time Unit Subsystem and Industrial Communications Subsystem +---------------------------------------------------------------------------------------- AM335x has one PRU-ICSS and AM437x has two PRU-ICSS. The PRU-ICSS on AM437x is backwards compatible with the subsystem on AM335x. The table below summarizes the differences between the PRU-ICSS instances on each device. diff --git a/source/linux/How_to_Guides/Host/AM335x_ICEv2_flash_erase.rst b/source/linux/How_to_Guides/Host/AM335x_ICEv2_flash_erase.rst index 806280cc4..56048811b 100644 --- a/source/linux/How_to_Guides/Host/AM335x_ICEv2_flash_erase.rst +++ b/source/linux/How_to_Guides/Host/AM335x_ICEv2_flash_erase.rst @@ -41,7 +41,7 @@ on a Ubuntu 14.04 host system - Click **File -> New-> Target Configuration File** - - Filename : AM3359-ice-v2.ccxml. Check "Use shared location" to be + - Filename : AM3359-ice-v2.ccxml. Check "Use shared location" to be available to anyone who uses the workspace. Click Finish. A window opens up which is to configure the connection details @@ -88,7 +88,7 @@ on a Ubuntu 14.04 host system - The program will give you the following prompts, type the responses and press Enter - - Enter Operation [1 - Flash ] [2 - Erase] : 2 + - Enter Operation [1 - Flash ] [2 - Erase] : 2 - Enter the offset [in Hex]: 0 - Enter size to be erased in Kilo bytes: 64 diff --git a/source/linux/How_to_Guides/Host/Boot_Sequence.rst b/source/linux/How_to_Guides/Host/Boot_Sequence.rst index 28ad4b5f4..a53ed713f 100644 --- a/source/linux/How_to_Guides/Host/Boot_Sequence.rst +++ b/source/linux/How_to_Guides/Host/Boot_Sequence.rst @@ -14,7 +14,7 @@ Boot Sequence .. rubric:: Introduction :name: introduction-boot-sequence - This page describes the boot sequence of an OMAP3 EVM.  + This page describes the boot sequence of an OMAP3 EVM. .. rubric:: General Boot Sequence (Linux system) :name: general-boot-sequence-linux-system @@ -28,41 +28,41 @@ Boot Sequence | - At power-up an OMAP3 device begins booting from internal Boot ROM.  This - code is fixed during the manufacturing process and cannot be altered.  + At power-up an OMAP3 device begins booting from internal Boot ROM. This + code is fixed during the manufacturing process and cannot be altered. The Boot ROM reads boot configuration pins (SW4 on the OMAP3 EVM) which - tell the Boot ROM where to look for the first external bootloader.  The - choices include NAND, UART, and SD/MMC Card.  Control is then passed to - this first external bootloader called x-loader.  The x-loader + tell the Boot ROM where to look for the first external bootloader. The + choices include NAND, UART, and SD/MMC Card. Control is then passed to + this first external bootloader called x-loader. The x-loader application is included in the Linux PSP provided by TI and can be - modified by the end user.  The x-loader application passes control to - u-boot.  U-boot is also a bootloader and is considered the second + modified by the end user. The x-loader application passes control to + u-boot. U-boot is also a bootloader and is considered the second external bootloader in this case. | - U-boot is the application which passes control to the Linux system.  The + U-boot is the application which passes control to the Linux system. The main goal of u-boot is to retrieve the Linux kernel and provide the - kernel with information about the location of the Linux filesystem.  + kernel with information about the location of the Linux filesystem. U-boot can be configured to retrieve the kernel from NAND, SD/MMC Card, - UART or Ethernet (via TFTP).  U-boot can also specify a root filesystem + UART or Ethernet (via TFTP). U-boot can also specify a root filesystem that is located in NAND (jffs2), SRAM (ramdisk), SD/MMC card (ext3 partition) or mounted over IP (NFS). | - U-boot then boots the Linux kernel.  The Linux kernel mounts the Linux + U-boot then boots the Linux kernel. The Linux kernel mounts the Linux root filesystem. .. rubric:: Booting TI SDK :name: booting-ti-sdk - The OMAP3 EVM which includes the TI SDK will come with an SD card.  This + The OMAP3 EVM which includes the TI SDK will come with an SD card. This card has been formatted and partition in such a way that the entire - system comes from this card.  There is a bootable FAT partition which + system comes from this card. There is a bootable FAT partition which contains x-loader (MLO), u-boot (u-boot.bin )and the Linux kernel - (uImage).  There is a separate ext3 partition which contains the Linux + (uImage). There is a separate ext3 partition which contains the Linux root filesystem. A tutorial for making this SD card can be found @@ -87,8 +87,8 @@ Boot Sequence | - When booting from an SD card, the OMAP3 Boot ROM code will search the SD - card for the filename "MLO" when looking for x-loader.  + When booting from an SD card, the OMAP3 Boot ROM code will search the SD + card for the filename "MLO" when looking for x-loader. To boot from this SD card, the switches on SW4 should be set to SD/MMC boot. @@ -96,10 +96,8 @@ Boot Sequence - **SW4 = 00100111 (high to low, i.e. SW4.1 = 1)** - **1 = "On" position on the switch** -   - | A UART terminal application connect to UART 1/2 of the EVM will - display output as the board boots up.  The first section shows output + display output as the board boots up. The first section shows output from x-loader as it boots from the SD/MMC card. :: @@ -112,10 +110,10 @@ Boot Sequence Starting OS Bootloader from MMC... Starting OS Bootloader... - X-loader then passes control to u-boot.  U-boot expects to find - "environment variables" in NAND flash.  When a board is booted for the + X-loader then passes control to u-boot. U-boot expects to find + "environment variables" in NAND flash. When a board is booted for the first time or if the NAND has been erased, u-boot will indicate a - Warning about bad NAND.  U-boot will write a default environment that it + Warning about bad NAND. U-boot will write a default environment that it will then use to continue the boot process. :: @@ -138,11 +136,11 @@ Boot Sequence Hit any key to stop autoboot: 0 The default environment is designed to boot the Linux system from the SD - card, so it is not necessary to stop the boot process.  And the next + card, so it is not necessary to stop the boot process. And the next time that the EVM is booted the default environment will exist in NAND so the "bad NAND" warning will not be displayed. - U-boot allows the user a 2-3 seconds window to stop the boot process.  + U-boot allows the user a 2-3 seconds window to stop the boot process. Hit any key in the UART terminal application and the u-boot prompt will be displayed as shown below: @@ -150,8 +148,8 @@ Boot Sequence OMAP3_EVM # - There are several useful commands to remember here.  To display the - environment variables, type "**printenv**" or just "**pri**".  + There are several useful commands to remember here. To display the + environment variables, type "**printenv**" or just "**pri**". :: @@ -182,13 +180,13 @@ Boot Sequence OMAP3_EVM # | The environment variables shown above are the default variables that - are included with u-boot from the TI SDK.  These will be re-written - any time that the NAND is erased, but otherwise these variables stay - in NAND and can be modified to change how Linux is booted. + are included with u-boot from the TI SDK. These will be re-written + any time that the NAND is erased, but otherwise these variables stay + in NAND and can be modified to change how Linux is booted. | To continue the boot from u-boot, simply type "**boot**" and the process will continue as if you did not stop the boot by hitting a - key.  This is also equivalent to typing "**run bootcmd**".  The + key. This is also equivalent to typing "**run bootcmd**". The **bootcmd** environment variable is actually a sequence of conditional statements (separated by semicolons) which perform checks on the hardware and software to complete the boot process. @@ -209,10 +207,10 @@ Boot Sequence Starting kernel ... Uncompressing Linux..................................................................................................... - .................................................. done, booting the kernel.  + .................................................. done, booting the kernel. | Then there will be a lot of messages from the kernel before getting to - the Linux login prompt.  Just type "root" at the login prompt + the Linux login prompt. Just type "root" at the login prompt :: @@ -223,7 +221,7 @@ Boot Sequence .. rubric:: Closer Look At bootcmd :name: closer-look-at-bootcmd - The bootcmd environment variable is a set of nested conditional + The bootcmd environment variable is a set of nested conditional statements. | @@ -234,10 +232,10 @@ Boot Sequence i; fi; else run nandboot; fi | The first conditional "**if mmc init**" checks to see if the SD/MMC - card exists.  If the card exists, the next conditional "**if run + card exists. If the card exists, the next conditional "**if run loadbootscript**" checks to see if the bootscript boot.scr exists on - the SD card.  If the boot script exists, then it is executed.  The + the SD card. If the boot script exists, then it is executed. The boot script contains the boot arguments and the command to actually - boot the Linux kernel.  So if the bootscript exists and is executed, + boot the Linux kernel. So if the bootscript exists and is executed, it should not return to rest of the bootcmd. diff --git a/source/linux/How_to_Guides/Host/Connect_to_an_EVM_via_Telnet.rst b/source/linux/How_to_Guides/Host/Connect_to_an_EVM_via_Telnet.rst index 6ad879f09..c9cb6d9cc 100644 --- a/source/linux/How_to_Guides/Host/Connect_to_an_EVM_via_Telnet.rst +++ b/source/linux/How_to_Guides/Host/Connect_to_an_EVM_via_Telnet.rst @@ -8,7 +8,7 @@ Connect to an EVM via Telnet The initialization file (/etc/init.d/rcS) starts a telnet server. If your development host is in the same sub-net as the EVM, you can telnet -to it using the IP address assigned in the U-boot environment.  The +to it using the IP address assigned in the U-boot environment. The following is an example from a Linux host. :: @@ -23,7 +23,7 @@ be root and the password should be left blank (just hit Enter). From a Windows XP host, click the Start button, then click Run... Type telnet and click OK. This will open a telnet window. -Type "o < ip-addr >" and hit enter.  Example: +Type "o < ip-addr >" and hit enter. Example: :: diff --git a/source/linux/How_to_Guides/Host/How_to_Build_a_Ubuntu_Linux_host_under_VMware.rst b/source/linux/How_to_Guides/Host/How_to_Build_a_Ubuntu_Linux_host_under_VMware.rst index 15bfdbc4f..e992fd565 100644 --- a/source/linux/How_to_Guides/Host/How_to_Build_a_Ubuntu_Linux_host_under_VMware.rst +++ b/source/linux/How_to_Guides/Host/How_to_Build_a_Ubuntu_Linux_host_under_VMware.rst @@ -19,8 +19,8 @@ provided here.** :name: introduction-build-ubuntu-linux-host-under-vmware This guide demonstrates how to get a virtual Ubuntu Linux machine -running with VMware under Windows 7.  Please use only the 32-bit Ubuntu -14.04 release as this is what is called an LTS (Long Term Support).  +running with VMware under Windows 7. Please use only the 32-bit Ubuntu +14.04 release as this is what is called an LTS (Long Term Support). There are SDK scripts that will be checking for this release identity. **Requirements**: @@ -28,14 +28,14 @@ There are SDK scripts that will be checking for this release identity. - Windows 7 host with internet connection, at least 1G of RAM and 40G of free hard drive space. -The instructions here are for setting up a 40G virtual machine.  The +The instructions here are for setting up a 40G virtual machine. The entire 40G is not taken at once, but as the machine is used and software -is installed, the machine can grow and take up as much as 40G.  +is installed, the machine can grow and take up as much as 40G. -.. rubric:: Download the Ubuntu 14.04 LTS ISO image +.. rubric:: Download the Ubuntu 14.04 LTS ISO image :name: download-the-ubuntu-14.04-ltsiso-image -Get the Ubuntu 14.04 LTS CD ISO image from: +Get the Ubuntu 14.04 LTS CD ISO image from: http://releases.ubuntu.com/14.04/. Select PC (Intel x86) desktop CD under the Desktop CD section. @@ -50,15 +50,15 @@ Get VMware from: http://www.vmware.com Vmware Player is a free download from the website and enables the user to create an entire virtual machine from scratch using just the ISO -image downloaded from Ubuntu.  It is necessary to sign up for an account -at VMware in order to get to the download areas.  The general steps to +image downloaded from Ubuntu. It is necessary to sign up for an account +at VMware in order to get to the download areas. The general steps to getting VMware are as follows: - Login to the vmware website - Select VMware Player from the products menu - Follow the steps to download VMware Player -**NOTE - We have tested with v7.0.0 with no known issues.  As of +**NOTE - We have tested with v7.0.0 with no known issues. As of Feburary, 2015, v7.0.0 is the latest version.** - Run the executable to install VMware @@ -71,19 +71,19 @@ Before starting a new installation it is assumed that the Windows host has a proper internet connection to a DHCP server and that the Windows host has enough hard drive space for the new virtual machine. -The following steps are performed with VMware 7.0.0.  The exact steps +The following steps are performed with VMware 7.0.0. The exact steps with other versions may vary slightly - Start VMware. - From the File menu select "Create a New Virtual Machine..." -- Choose to install the operating system later.  Click "Next". +- Choose to install the operating system later. Click "Next". - Select Linux as the "Guest Operating System" and then choose Ubuntu - as the "Version".  Click "next". + as the "Version". Click "next". - Provide a "Virtual machine name" and "Location" where the machine - will be stored on the Windows host.  The defaults are fine here.  + will be stored on the Windows host. The defaults are fine here. Click "Next". - For "Maximum disk size (GB)" it is good to start with 40G if - possible.  This means that it will take up 40G on the Windows host. + possible. This means that it will take up 40G on the Windows host. Make sure that the Windows host has at least this much before proceeding. It is also a good practice to tell VMware to split the virtual disk into 2G files. This will makes the image easier to copy @@ -107,20 +107,20 @@ connection state". .. rubric:: Adding a serial port to the virtual machine :name: adding-a-serial-port-to-the-virtual-machine -If you plan to use a serial terminal application, a serial port must be -added to the virtual machine.  This port must be a physical serial port -which exists on the host PC.  Click on "Add..." and select "Serial -Port".  Click "Next".  Choose "Use physical serial port on host".  Click -"Next".  Click Finish.  Click "Ok". +If you plan to use a serial terminal application, a serial port must be +added to the virtual machine. This port must be a physical serial port +which exists on the host PC. Click on "Add..." and select "Serial +Port". Click "Next". Choose "Use physical serial port on host". Click +"Next". Click Finish. Click "Ok". | Since this is a physical port on the host PC, it cannot be used by the -host PC and the virtual machine at the same time.  When the virtual +host PC and the virtual machine at the same time. When the virtual machine is started, the serial port will be unavailable for use by the -host PC.  If the serial port is being used at the time that the virtual +host PC. If the serial port is being used at the time that the virtual machine is started, the virtual machine will not be able to access the -serial port after it is booted up.  So if you want the virtual machine +serial port after it is booted up. So if you want the virtual machine to gain control of the physical serial port of the host PC, there can not be any application like hyperterminal or teraterm running on the host PC at the time that the virtual machine is started. @@ -129,37 +129,37 @@ Further instructions for using the serial port with minicom inside of Ubuntu are `here `__. -| Minicom is the preferred application for use with the Sitara SDK.  And +| Minicom is the preferred application for use with the Sitara SDK. And the installation and setup of minicom is done automattically by the - Sitara SDK installer.  + Sitara SDK installer. | -Now click on "Play virtual machine".  Since this is the first time -starting the machine and the Ubuntu ISO image is in the virtual CD +Now click on "Play virtual machine". Since this is the first time +starting the machine and the Ubuntu ISO image is in the virtual CD drive, the Ubuntu OS will install itself in the virtual machine. Click through the Ubuntu installation, making the appropriate choices as -you go.  This will help with SDK installation scripts. +you go. This will help with SDK installation scripts. .. Image:: /images/Vmware-player.PNG | -| The full installation will take 20-30 minutes.  When it completes the - machine will reboot.  The machine will now prompt for the username and +| The full installation will take 20-30 minutes. When it completes the + machine will reboot. The machine will now prompt for the username and password that you created during the installation. After the machine reboots into Ubuntu it is helpful to take the Ubuntu -ISO out of the virtual CD drive.  Click on the VM menu and select -"Settings...".  Click on CD/DVD and change the connection from "Use -ISO image file" to "Use physical drive".  The actual drive letter can be -selected from the drop down list.  If there is no physical drive on the +ISO out of the virtual CD drive. Click on the VM menu and select +"Settings...". Click on CD/DVD and change the connection from "Use +ISO image file" to "Use physical drive". The actual drive letter can be +selected from the drop down list. If there is no physical drive on the host machine, the CD/DVD device can be simply removed from the machine. .. rubric:: Install VMware Tools :name: install-vmware-tools -VMware tools is a very useful addition to VMware.  It allows you to +VMware tools is a very useful addition to VMware. It allows you to resize the VMware screen ,cut-and-paste of text and drag and drop files from the Ubuntu machine to and from the Windows host. @@ -168,26 +168,26 @@ Install VMware Tools .. Image:: /images/Install_vmware_tools.png -The VMware tools are contained in an ISO image that VMware -will automatically mount.  This drive will show up on the Ubuntu +The VMware tools are contained in an ISO image that VMware +will automatically mount. This drive will show up on the Ubuntu desktop as if it were a disk in a DVD drive. .. Image:: /images/Vmware-tools-cd.png -There will be a single tarball on the drive named +There will be a single tarball on the drive named VMwareTools-9.9.0-2304977.tar.gz (or with a slightly different version -number). Extract the tarball somewhere in your /home/ -directory.  You will see that a vmware-tools-distrib folder was +number). Extract the tarball somewhere in your /home/ +directory. You will see that a vmware-tools-distrib folder was created and a file name vmware-install.pl inside. Execute -vmware-install.pl to install VMware Tools.  The Perl script must be -executed as a super-user.  This is done in Ubuntu by pre-pending the -command with "sudo".  When prompted for a password, enter the -password for the user account.  In Ubuntu, there is no "root" -account.  However, the first user account created when Ubuntu is +vmware-install.pl to install VMware Tools. The Perl script must be +executed as a super-user. This is done in Ubuntu by pre-pending the +command with "sudo". When prompted for a password, enter the +password for the user account. In Ubuntu, there is no "root" +account. However, the first user account created when Ubuntu is installed can become a super-user with the "sudo" command. Select all of defaults during installation of VMware Tools. -An example is shown below.  +An example is shown below. :: @@ -199,10 +199,10 @@ An example is shown below.  :name: confirming-a-valid-network-connection After logging into the machine for the first time, bring up a terminal -window.  This can be found under the Applications menu in Ubuntu.  -Applications --> Accessories --> Terminal.  Type **pwd** in this -terminal.  This should return **/home/**.  Now type **ifconfig**.  -This should return information about the network connection.  Under +window. This can be found under the Applications menu in Ubuntu. +Applications --> Accessories --> Terminal. Type **pwd** in this +terminal. This should return **/home/**. Now type **ifconfig**. +This should return information about the network connection. Under **eth0** the IP address should be similar (but not the same) as the IP address owned by the Windows host. @@ -221,7 +221,7 @@ address owned by the Windows host. lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 - inet6 addr: ::1/128 Scope:Host + inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:12 errors:0 dropped:0 overruns:0 frame:0 TX packets:12 errors:0 dropped:0 overruns:0 carrier:0 @@ -230,13 +230,13 @@ address owned by the Windows host. | -.. rubric:: How to Read a USB SD Card Reader in VMware +.. rubric:: How to Read a USB SD Card Reader in VMware :name: how-to-read-a-usbsdcard-reader-in-vmware | Sometimes there will be a need to connect a SD Card to the Virtual Machine (for example, to run the create SD card script provided with the SDK that partitions, formats, and populates a SD card that can be - used with a target board). When a USB card reader with an SD card is + used with a target board). When a USB card reader with an SD card is inserted into the USB slot of the host machine, the virtual machine will automatically detect the drive and mount partitions from the SD card, making the card available to Linux running in the virtual diff --git a/source/linux/How_to_Guides/Host/How_to_Flash_Linux_System_from_U-boot.rst b/source/linux/How_to_Guides/Host/How_to_Flash_Linux_System_from_U-boot.rst index 598d3919a..4ba5cb410 100644 --- a/source/linux/How_to_Guides/Host/How_to_Flash_Linux_System_from_U-boot.rst +++ b/source/linux/How_to_Guides/Host/How_to_Flash_Linux_System_from_U-boot.rst @@ -21,7 +21,7 @@ How to Flash from U-boot Shell This article applies to Sitara SDK 4.0.1 which uses the Platform Support Package (PSP) software version 03.01.00.06 - for AM35x and AM37x devices.   This information is obsolete as newer + for AM35x and AM37x devices. This information is obsolete as newer software has different NAND ECC requirements. .. rubric:: Introduction @@ -29,11 +29,11 @@ How to Flash from U-boot Shell This guide will show how use u-boot to flash the NAND of an OMAP3 EVM (for AM37x, DM37x or OMAP35xx devices) or an AM3517EVM (for AM35x - devices) with Linux system binaries.  + devices) with Linux system binaries. - Assumptions: - #. SD card with system binaries (x-loader, u-boot, Linux kernel) on + #. SD card with system binaries (x-loader, u-boot, Linux kernel) on **boot** partition #. Linux root filesystem in **rootfs** partition of SD card or root filesystem available via NFS @@ -41,35 +41,34 @@ How to Flash from U-boot Shell .. rubric:: Caution :name: caution - The procedures here will erase the NAND flash of the EVM.  This includes - all u-boot environment variables.  Use the "**printenv**" command (or + The procedures here will erase the NAND flash of the EVM. This includes + all u-boot environment variables. Use the "**printenv**" command (or just "**pri**") in u-boot to print a complete list of environment - variables.  Copy and paste these to a text file for safe keeping. + variables. Copy and paste these to a text file for safe keeping. - .. rubric:: Boot EVM into SD/MMC card boot mode + .. rubric:: Boot EVM into SD/MMC card boot mode :name: bootevm-into-sdmmc-card-boot-mode - The SD card must at least have the files MLO, u-boot.bin, and uImage.  - All of these files can also be found in the "./psp/prebuilt-images" + The SD card must at least have the files MLO, u-boot.bin, and uImage. + All of these files can also be found in the "./psp/prebuilt-images" directory in the Sitara SDK installation (with names that include the - platform name and software revision info).  The MLO file is simply a + platform name and software revision info). The MLO file is simply a re-named copy of the file x-load.bin.ift that is produced by rebuilding - x-loader and signing the file.  When the board is booted in SD/MMC card - boot mode, the ROM code looks specifically for the file with the name + x-loader and signing the file. When the board is booted in SD/MMC card + boot mode, the ROM code looks specifically for the file with the name MLO as the primary bootloader. - To boot from this SD card, the boot switches should be set to SD/MMC + To boot from this SD card, the boot switches should be set to SD/MMC boot: **For Mistral OMAP EVM (AM37x, DM37x or OMAP35xx devices)** - | Set SW4 switches #1, #2, #3 and #6 to the ON position and all others + | Set SW4 switches #1, #2, #3 and #6 to the ON position and all others OFF (MMC1, UART3 boot order) | **For LogicPD AM3517EVM (AM35x device)** - | Set SW7 switches #1 and #4 to the ON position and all others OFF.  + | Set SW7 switches #1 and #4 to the ON position and all others OFF. (USB, UART, MMC1, XIP boot order) - |   Start the board and interrupt the boot process when prompted by hitting any key in the UART terminal application: @@ -100,23 +99,17 @@ How to Flash from U-boot Shell Net: smc911x-0 Hit any key to stop autoboot: 0 OMAP3_EVM # - OMAP3_EVM #  - - All of the commands in this guide are performed at the u-boot prompt.  - -   - -   + OMAP3_EVM # -   + All of the commands in this guide are performed at the u-boot prompt. .. rubric:: Run the u-boot commands to flash the NAND :name: run-the-u-boot-commands-to-flash-the-nand All of the following commands are performed at the u-boot prompt. -   These commands are actually a series of u-boot commands that are - connected together with semicolons.  The individual commands can be + These commands are actually a series of u-boot commands that are + connected together with semicolons. The individual commands can be entered separately or simple pasted from here. | @@ -127,33 +120,25 @@ How to Flash from U-boot Shell mw.b 0x81600000 0xff 0x20000;nand erase 0 20000;mmc init;fatload mmc 0 0x81600000 x-load.bin.ift;nandecc hw; nand write.i 0x81600000 0 20000 -   - - Complete uboot write from MMC to NAND (only erases two blocks=256k) :: mw.b 0x81600000 0xff 0x40000;nand erase 80000 40000;mmc init;fatload mmc 0 0x81600000 u-boot.bin;nandecc sw; nand write.i 0x81600000 80000 40000 -   - - Complete kernel write from MMC to NAND (erases 3M) :: mw.b 0x81600000 0xff 0x1400000;nand erase 280000 300000;mmc init;fatload mmc 0 0x81600000 uImage;nandecc sw; nand write.i 0x81600000 280000 300000 -   - -   - - .. rubric:: Put the EVM in NAND boot mode + .. rubric:: Put the EVM in NAND boot mode :name: put-the-evm-in-nandboot-mode -  With the EVM in NAND boot mode and the images flashed in NAND as - detailed above, the SD card does not need to be in the EVM at boot up.  - X-loader and u-boot will run from NAND.  In order to also pull the Linux - kernel (uImage) from NAND it will be necessary to halt the boot process + With the EVM in NAND boot mode and the images flashed in NAND as + detailed above, the SD card does not need to be in the EVM at boot up. + X-loader and u-boot will run from NAND. In order to also pull the Linux + kernel (uImage) from NAND it will be necessary to halt the boot process and edit some u-boot environment variables. | @@ -165,30 +150,28 @@ How to Flash from U-boot Shell **For LogicPD AM3517EVM (AM35x device)** - Set SW7 with switches #1 thru #8 all to the OFF position. (NAND, EMAC, + Set SW7 with switches #1 thru #8 all to the OFF position. (NAND, EMAC, USB, MMC1 boot order) -   - - Save off the original boot command :: setenv bootcmd_original ${bootcmd} - saveenv  + saveenv | - Create command for reading the kernel from NAND and then another - command for doing the boot where the kernel is pulled from NAND and - the root filesystem is from the SD/MMC card.  + command for doing the boot where the kernel is pulled from NAND and + the root filesystem is from the SD/MMC card. :: setenv nand_kernel 'nand read.i ${loadaddr} 280000 300000' setenv nand_mmc_boot 'run nand_kernel;setenv bootargs ${mmcargs}; bootm' - Run this last command to actually perform the boot.  And always save the + Run this last command to actually perform the boot. And always save the environment after making changes. :: @@ -199,7 +182,7 @@ How to Flash from U-boot Shell .. rubric:: Flashing the Root File System to NAND :name: flashing-the-root-file-system-to-nand - A jffs2 file system can be copied into NAND flash.  Copy the file + A jffs2 file system can be copied into NAND flash. Copy the file rootfs.tar.gz to the /home/root directory on the SD Card. Boot the EVM to Linux and enter the following commands: @@ -226,12 +209,12 @@ How to Flash from U-boot Shell .. rubric:: Mounting File System from NFS :name: mounting-file-system-from-nfs - The file system can also be mounted as a Network File System (NFS).  The - NFS is simply a sub-directory of the Linux host development system.  + The file system can also be mounted as a Network File System (NFS). The + NFS is simply a sub-directory of the Linux host development system. - Another command can be made to pull the root filesystem via NFS.  This + Another command can be made to pull the root filesystem via NFS. This command can be combine with the one to pull the bootloaders and kernel - from NAND.  (The IP address and path to the NFS is an example and should + from NAND. (The IP address and path to the NFS is an example and should be changed by the user). :: diff --git a/source/linux/How_to_Guides/Host/How_to_Setup_Ubuntu_1404_Network_Boot.rst b/source/linux/How_to_Guides/Host/How_to_Setup_Ubuntu_1404_Network_Boot.rst index cf69a2e11..c4d66f798 100644 --- a/source/linux/How_to_Guides/Host/How_to_Setup_Ubuntu_1404_Network_Boot.rst +++ b/source/linux/How_to_Guides/Host/How_to_Setup_Ubuntu_1404_Network_Boot.rst @@ -194,10 +194,10 @@ USB there are some additional steps required. .. code:: #!/bin/sh -   + IF=$1 STATUS=$2 -   + if [ "$IF" = "usb0" ] && [ "$STATUS" = "up" ]; then service isc-dhcp-server restart fi @@ -248,7 +248,7 @@ USB there are some additional steps required. .. code:: #!/bin/sh -   + if [ "$IFACE" = usb0 ]; then sudo service isc-dhcp-server restart fi @@ -267,7 +267,7 @@ USB there are some additional steps required. [main] plugins=ifupdown -   + [ifupdown] managed=false diff --git a/source/linux/How_to_Guides/Host/How_to_Setup_a_Samba_Server.rst b/source/linux/How_to_Guides/Host/How_to_Setup_a_Samba_Server.rst index a5942e443..7b4941f25 100644 --- a/source/linux/How_to_Guides/Host/How_to_Setup_a_Samba_Server.rst +++ b/source/linux/How_to_Guides/Host/How_to_Setup_a_Samba_Server.rst @@ -5,10 +5,10 @@ How to Setup a Samba Server .. rubric:: Introduction :name: introduction-samba-server -When using a Virtual machine you may share files & folders via the -Share Foldr feature of that partoicular Virtual Machine.  Another +When using a Virtual machine you may share files & folders via the +Share Foldr feature of that partoicular Virtual Machine. Another alternative, especially if you are using a dedicated Linux host, is to -configure a Samba server on your Linux host.  +configure a Samba server on your Linux host. Samba allows a host to interact with a Microsoft Windows client or server as if it is a Windows file and print server. In other words, if @@ -19,15 +19,15 @@ machine) through windows. .. rubric:: Installing a Samba Server :name: installing-a-samba-server -1.  Samba can be installed by opening a terminal. (Applications -> +1. Samba can be installed by opening a terminal. (Applications -> System Tools -> Terminal) -2.  Switch to root user by typing su and entering the password you set +2. Switch to root user by typing su and entering the password you set during the install. 3. On Fedora install Samba with the yum command: system-config-samba -|     On Ubuntu install Samba using:  sudo apt-get install +| On Ubuntu install Samba using: sudo apt-get install system-config-samba 4. Open the Samba GUI (System -> Administration -> Samba). @@ -81,8 +81,8 @@ configure the network proxy.** 9. Enable the Samba and NFS services -- System -> Administration -> Services  (**NOTE - Not available in - Ubuntu 10.04 LTS.  However the Samba service should start +- System -> Administration -> Services (**NOTE - Not available in + Ubuntu 10.04 LTS. However the Samba service should start automatically**) - Enable the services by browsing through the list on the left and locating nfs and smb. If they are not already enabled, enable them by diff --git a/source/linux/How_to_Guides/Host/Moving_Files_to_the_Target_System.rst b/source/linux/How_to_Guides/Host/Moving_Files_to_the_Target_System.rst index 3030b7d7d..836eb7960 100644 --- a/source/linux/How_to_Guides/Host/Moving_Files_to_the_Target_System.rst +++ b/source/linux/How_to_Guides/Host/Moving_Files_to_the_Target_System.rst @@ -7,18 +7,18 @@ Moving Files to the Target System This guide discusses how applications or other files can be moved to the target file system of the EVM. -.. rubric:: File System on SD card +.. rubric:: File System on SD card :name: file-systemon-sd-card The SD card wic image which comes with the TI SDK has a Linux ext4 partition that is used as the target file system. This partition is readable from a Linux host. In Ubuntu |__LINUX_UBUNTU_VERSION_LONG__| this partition will be mounted on -:file`/media/$USER/rootfs` when the card is used with an SD card reader inserted into a USB port on the Ubuntu host.  +:file`/media/$USER/rootfs` when the card is used with an SD card reader inserted into a USB port on the Ubuntu host. -When the SD card is mounted with a card reader in the Linux host it is possible to perform :command:`cp` commands from the host into sub-directories +When the SD card is mounted with a card reader in the Linux host it is possible to perform :command:`cp` commands from the host into sub-directories under :file:`/media/$USER/rootfs` or just use a browser window to drag and drop the files from the host to the SD card. Switching the SD card back and forth from the EVM to the SD card reader -is time consuming during development.  Using a NFS during development is +is time consuming during development. Using a NFS during development is the preferred method and makes moving files between the host and target trivial. @@ -26,8 +26,8 @@ trivial. :name: file-system-on-network-file-system-nfs When the target file system is served from the Linux development host -machine it is trivial to move files between the host and target.  The -NFS directory is set up on the host machine by the SDK installer.  The +machine it is trivial to move files between the host and target. The +NFS directory is set up on the host machine by the SDK installer. The default location in the SDK environment is :file:`${PSDK_PATH}/targetNFS` This could vary depending on the version of the SDK and how it was installed. An :command:`ls -l` of this directory in the host system will show what will be the root @@ -59,13 +59,13 @@ directory of the target when it boots up. drwxr-xr-x 9 root root 4096 Mar 9 2018 var So from the perspective of the host, the target filesystem is just a -sub-directory of the host.  If the file is in :file:`./targetNFS` on the host, +sub-directory of the host. If the file is in :file:`./targetNFS` on the host, then the same file will show up in the root directory of the target -after the target boots into the NFS.  And if the file is in a +after the target boots into the NFS. And if the file is in a subdirectory of :file:`./targetNFS` (example :file:`./targetNFS/{sub-dir}/`) then it will show up in the /sub-dir directory of the target after the target boots into the NFS. -The top level makefile of the TI SDK supports an install target that +The top level makefile of the TI SDK supports an install target that will copy applications into the NFS of the SDK. See the README file at -the top level of the SDK for information about the install target. +the top level of the SDK for information about the install target. diff --git a/source/linux/Industrial_Protocols/HSR_PRP/_HSR_PRP_for_Linux.rst b/source/linux/Industrial_Protocols/HSR_PRP/_HSR_PRP_for_Linux.rst index d7f3ae0ad..78654aa39 100644 --- a/source/linux/Industrial_Protocols/HSR_PRP/_HSR_PRP_for_Linux.rst +++ b/source/linux/Industrial_Protocols/HSR_PRP/_HSR_PRP_for_Linux.rst @@ -57,18 +57,18 @@ Features supported - Duplicate discard table on Port to Port path (HSR) - Data integrity (CRC) check during port to port forwarding, except cut through (HSR) -- **QoS scheme** : 3-bit VLAN PCP +- **QoS scheme** : 3-bit VLAN PCP - - No of levels supported : 2 - - Number of host queues : 2 \| 2 QoS levels per host queue - - Number of port queues : 2 \| 2 QoS levels per port queue + - No of levels supported : 2 + - Number of host queues : 2 \| 2 QoS levels per host queue + - Number of port queues : 2 \| 2 QoS levels per port queue - **Statistics** - Supports all MIB statistics as per standard - Node Table statistics for debugging -- **Storm Prevention** : Yes. Configurable per port +- **Storm Prevention** : Yes. Configurable per port - **Dual instance of HSR/PRP using two PRU-ICSS on AM571x** @@ -345,7 +345,7 @@ type without having to reboot the board:- * PRP Two feature flags are added to help offload HSR or PRP in the PRU -Ethernet driver :- hsr-rx-offload and prp-rx-offload. PRU Firmware +Ethernet driver :- hsr-rx-offload and prp-rx-offload. PRU Firmware essentially offload the rx side processing of LRE, such as duplicate detection and drop, node table update, stats update etc. To reflect the same, the features are named with a rx-offload suffx to the protocol name. diff --git a/source/linux/Industrial_Protocols/PTP/_PTP.rst b/source/linux/Industrial_Protocols/PTP/_PTP.rst index e2d40dc94..60eb26e0d 100644 --- a/source/linux/Industrial_Protocols/PTP/_PTP.rst +++ b/source/linux/Industrial_Protocols/PTP/_PTP.rst @@ -1619,7 +1619,7 @@ background $ phc2sys -a -m & Lines similar to the following should be displayed after a few seconds -(mixed with the "ptp4l[304.713]: rms ..." lines from ptp4l) : +(mixed with the "ptp4l[304.713]: rms ..." lines from ptp4l) : :: @@ -1830,9 +1830,9 @@ each clock plays in this test is as follows: :: - DUT-2 : AM572x : Master clock - DUT-1 : AM571x : Transparent clock - DUT-3 : AM572x : Slave clock + DUT-2 : AM572x : Master clock + DUT-1 : AM571x : Transparent clock + DUT-3 : AM572x : Slave clock .. note:: In this release BMCA enhanced for HSR is not supported, hence the connection is not a HSR close-loop network. @@ -1852,9 +1852,9 @@ section for HSR) will be used in the setup of the tests. :: - DUT-2 : setup_hsr.sh : dut_2_hsr_oc.cfg - DUT-1 : setup_hsr.sh : dut_1_hsr_oc.cfg - DUT-3 : setup_hsr.sh : dut_3_hsr_oc.cfg + DUT-2 : setup_hsr.sh : dut_2_hsr_oc.cfg + DUT-1 : setup_hsr.sh : dut_1_hsr_oc.cfg + DUT-3 : setup_hsr.sh : dut_3_hsr_oc.cfg - Connect the 3 AM57xx IDKs as shown above. @@ -1938,11 +1938,11 @@ associated with ICSS2 (PRUSS2 timer) is ptp1. lrwxrwxrwx 1 root root 0 Apr 20 19:11 ptp0 -> ../../devices/platform/44000000.ocp/48484000.ethernet/ptp/ptp0 lrwxrwxrwx 1 root root 0 Apr 21 21:18 ptp1 -> ../../devices/platform/pruss2_eth/ptp/ptp1 ptp clock names: - /sys/class/ptp/ptp0 : CTPS timer - /sys/class/ptp/ptp1 : PRUSS2 timer + /sys/class/ptp/ptp0 : CTPS timer + /sys/class/ptp/ptp1 : PRUSS2 timer pps's ptp device: - /sys/class/pps/pps0 : ptp0 - /sys/class/pps/pps1 : ptp1 + /sys/class/pps/pps0 : ptp0 + /sys/class/pps/pps1 : ptp1 root@am57xx-evm:~# Test 2. Without a hybrid clock between Master and Slave Clock diff --git a/source/linux/Overview/Download_and_Install_the_SDK.rst b/source/linux/Overview/Download_and_Install_the_SDK.rst index f0066f392..0efa3e488 100644 --- a/source/linux/Overview/Download_and_Install_the_SDK.rst +++ b/source/linux/Overview/Download_and_Install_the_SDK.rst @@ -55,7 +55,7 @@ Download & Install the SDK Installer on Host version of the SDK. We recommend checking the above site and using the latest version if at all possible. Before running the SDK Installer from the SD card, the SD Card from the EVM box needs to be mounted to your - Linux Host PC (using a USB SD Card reader).  The SDK Installer is found + Linux Host PC (using a USB SD Card reader). The SDK Installer is found in the START\_HERE partition of the SD card. .. ifconfig:: CONFIG_sdk in ('JACINTO','j7_foundational') @@ -111,7 +111,7 @@ for the installer (e.g. text installer, etc.): ./|__SDK_INSTALL_FILE__| --help -.. rubric:: SDK Installer Execution Steps +.. rubric:: SDK Installer Execution Steps :name: sdkinstaller-execution-steps 1. **Confirm** diff --git a/source/linux/Overview/Processor_SDK_Linux_create_SD_card.rst b/source/linux/Overview/Processor_SDK_Linux_create_SD_card.rst index 07c4344a3..1ccb3563d 100644 --- a/source/linux/Overview/Processor_SDK_Linux_create_SD_card.rst +++ b/source/linux/Overview/Processor_SDK_Linux_create_SD_card.rst @@ -245,7 +245,7 @@ can move on to the next step. .. code-block:: text - Would you like to re-partition the drive anyways [y/n] : + Would you like to re-partition the drive anyways [y/n] : - Options: @@ -271,7 +271,7 @@ many partitions you want to create for the SD card. .. code-block:: text - Number of partitions needed [2/3] : + Number of partitions needed [2/3] : - Options: diff --git a/source/linux/Overview/Processor_SDK_Linux_create_SD_card_script.rst b/source/linux/Overview/Processor_SDK_Linux_create_SD_card_script.rst index a95d55cd8..15f1d96a7 100644 --- a/source/linux/Overview/Processor_SDK_Linux_create_SD_card_script.rst +++ b/source/linux/Overview/Processor_SDK_Linux_create_SD_card_script.rst @@ -93,7 +93,7 @@ can move on to the next step. :: - Would you like to re-partition the drive anyways [y/n] : + Would you like to re-partition the drive anyways [y/n] : - Options: @@ -115,7 +115,7 @@ many partitions you want to create for the SD card. :: - Number of partitions needed [2/3] : + Number of partitions needed [2/3] : - Options: @@ -358,7 +358,7 @@ After the SD card has been partitioned you will be prompted to: :: - Enter path where SD card tarballs were downloaded : + Enter path where SD card tarballs were downloaded : Point to the directory containing the following tarball files: diff --git a/source/linux/Overview/Run_Setup_Scripts.rst b/source/linux/Overview/Run_Setup_Scripts.rst index 3d300924b..f639e1ebe 100644 --- a/source/linux/Overview/Run_Setup_Scripts.rst +++ b/source/linux/Overview/Run_Setup_Scripts.rst @@ -33,7 +33,7 @@ does the following things: .. rubric:: BeagleBone Black Users :name: beaglebone-black-users - To run the SDK's setup scripts the following cables are required to be + To run the SDK's setup scripts the following cables are required to be connected to the BeagleBone Black and your Linux PC. Please ensure both are connected before following any of the steps in this guide. @@ -79,12 +79,12 @@ does the following things: :name: how-to-run-the-setup-script The Setup Script (**setup.sh**) is located in the |__SDK_FULL_NAME__| installation -directory.  By default, this directory has a name that has the form +directory. By default, this directory has a name that has the form |__SDK_INSTALL_DIR__|. .. ifconfig:: CONFIG_sdk in ('SITARA') - Change to that ti-processor-sdk-linux install directory. + Change to that ti-processor-sdk-linux install directory. Then run the script: @@ -140,7 +140,7 @@ packages may vary for different releases: This part requires you to have administrator priviliges (sudo access). -A unique step is required for users using Ubuntu 12.04+. By default the +A unique step is required for users using Ubuntu 12.04+. By default the user does not have the proper permissions to access a serial device ( ex ttyS0, ttyUSB0, etc...). A user must be apart of a "dialout" group to access these serial device without root privileges. diff --git a/source/linux/Overview/_Processor_SDK_Linux_GPLv3_Disclaimer.rst b/source/linux/Overview/_Processor_SDK_Linux_GPLv3_Disclaimer.rst index f5d959f21..86eba4f97 100644 --- a/source/linux/Overview/_Processor_SDK_Linux_GPLv3_Disclaimer.rst +++ b/source/linux/Overview/_Processor_SDK_Linux_GPLv3_Disclaimer.rst @@ -4,9 +4,9 @@ GPLv3 Disclaimer .. http://processors.wiki.ti.com/index.php/Processor_SDK_Linux_GPLv3_Disclaimer There are GPLv3 licensed software components contained within the -Processor SDK for Linux on both the target and the host.  The software +Processor SDK for Linux on both the target and the host. The software manifest (software\_manifest.htm) for the Linux SDK is located in the -manifest/ directory of the installed SDK.  All GPLv3 components for both +manifest/ directory of the installed SDK. All GPLv3 components for both target and host are contained in the SDK directory. .. warning:: @@ -21,15 +21,15 @@ run the gplv3-notice script located on the target file system located here: **/etc/init.d/gplv3-notice** The gplv3-notice script will list all Processor SDK Linux installed -packages as shipped.  If you installed additional GPLv3 components this -script may not identify them until the next target reboot.   +packages as shipped. If you installed additional GPLv3 components this +script may not identify them until the next target reboot. | .. rubric:: How to Remove Target side GPLv3 Components :name: how-to-remove-target-side-gplv3-components -The gplv3-notice script also outputs how to remove the packages.  To +The gplv3-notice script also outputs how to remove the packages. To remove individual packages from the target development file system, use the opkg remove command which is: **opkg remove ** diff --git a/source/linux/Release_Specific_PLSDK_Release_Notes.rst b/source/linux/Release_Specific_PLSDK_Release_Notes.rst index e24089f79..dfeaf9e97 100644 --- a/source/linux/Release_Specific_PLSDK_Release_Notes.rst +++ b/source/linux/Release_Specific_PLSDK_Release_Notes.rst @@ -437,7 +437,7 @@ RT Linux Kernel Known Issues :name: installation-and-usage The `Software Developer's Guide `__ provides instructions on how to setup up your Linux development -environment, install the SDK and start your development.  It also includes User's Guides for various Example Applications and Code +environment, install the SDK and start your development. It also includes User's Guides for various Example Applications and Code Composer Studio. | diff --git a/source/system/Demo_User_Guides/Benchmark_Demo_User_Guide.rst b/source/system/Demo_User_Guides/Benchmark_Demo_User_Guide.rst index 55113bfff..0bcab904a 100644 --- a/source/system/Demo_User_Guides/Benchmark_Demo_User_Guide.rst +++ b/source/system/Demo_User_Guides/Benchmark_Demo_User_Guide.rst @@ -48,7 +48,7 @@ Get Started 4. Connect an ethernet cable from your ethernet switch or router to the AM64x EVM -5. Connect your PC to the same ethernet switch or router +5. Connect your PC to the same ethernet switch or router 6. Connect the UART (J26 via USB cable) to the PC's USB port. @@ -63,18 +63,18 @@ Get Started .. Image:: /images/OOB_Linux_ifconfig.png 10. On the PC, open a Internet Browser and enter in the - following: \ http://IP_ADDRESS_OF_AM64x_EVM:8081, for example, http://192.168.86.198:8081 + following: \ http://IP_ADDRESS_OF_AM64x_EVM:8081, for example, http://192.168.86.198:8081 11. The following web page will pop up: .. Image:: /images/OOB_GUI_root.png -12. Click on the "Benchmark Demo":  +12. Click on the "Benchmark Demo": .. Image:: /images/OOB_GUI_stats.png 13. With the current release, the R5F app for each R5F core are fixed. User can only - change the "Options" for each core, then click "LOAD" to refresh the statistics  + change the "Options" for each core, then click "LOAD" to refresh the statistics +-------------+------------------+----------------------+-----------------------------------------------------------+ | **R5 Core** | **App Name** | Default Option | **Description** | @@ -82,7 +82,7 @@ Get Started | 0_0 | ADC and PWM Loop | 8Khz | ADC/PWM benchmark for R5 5 ADC sample read & 1 PWM write | | | | | This is not enabled in current release. | +-------------+------------------+----------------------+-----------------------------------------------------------+ -| 0_1  | CFFT | 1Khz & 128pt | CMSIS CFFT benchmark for R5 | +| 0_1 | CFFT | 1Khz & 128pt | CMSIS CFFT benchmark for R5 | +-------------+------------------+----------------------+-----------------------------------------------------------+ | 1_0 | FIR Filtering | 1Khz | CMSIS FIR filtering benchmark for R5 320pt & 29-tap | +-------------+------------------+----------------------+-----------------------------------------------------------+ @@ -97,11 +97,11 @@ Software Architecture Building Blocks --------------- -- **User Interface:** The GUI was built by using `GUI Composer `__. The +- **User Interface:** The GUI was built by using `GUI Composer `__. The Benchmark Demo is the second page where inputs and outputs can be accessed. -- **Web Server:** The benchmark data is sent between the GUI and the +- **Web Server:** The benchmark data is sent between the GUI and the AM64x via HTTP communication. New data are pulled from the AM64x and sent to the GUI every second, while data sending from the GUI to the AM64x is transmitted every time "Load" is clicked. The data are @@ -113,7 +113,7 @@ Building Blocks MCU+ SDK for more details. - Linux application code handles the IPC RPMsg\_char and the JSON - file update for A53  + file update for A53 - Web server code is built on Node JS @@ -156,13 +156,13 @@ is a JSON string containing the input/output benchmark data. JSON ~~~~ -A JSON file has been used to exchange structured information between the -web server and the A53 Linux application (a user space application -program). It will read the user input such as the input application and +A JSON file has been used to exchange structured information between the +web server and the A53 Linux application (a user space application +program). It will read the user input such as the input application and parameters used to run on the desired R5F core. On the other hand, the A53 Linux application will also get the benchmark data from the R5 cores and then update the JSON file accordingly. The updated JSON file -will then be displayed on the GUI every second.      +will then be displayed on the GUI every second. Build Baremetal Demos and Update SD card ---------------------------------------- @@ -183,11 +183,11 @@ Directory Structure The source code can be found at `[this link] `__. +------+--------------------------------------------------+----------------------------------------------------------------------------------------+ -| | **Directory Name** | **Description** | +| | **Directory Name** | **Description** | +======+==================================================+========================================================================================+ | 1 | apps/benchmark\_demo/webserver\_app/app | GUI code and component files | +------+--------------------------------------------------+----------------------------------------------------------------------------------------+ -| 2 | apps/benchmark\_demo/webserver\_app/linux\_app | Linux application code handles the IPC RPMsg\_char and the JSON file update for A53  | +| 2 | apps/benchmark\_demo/webserver\_app/linux\_app | Linux application code handles the IPC RPMsg\_char and the JSON file update for A53 | +------+--------------------------------------------------+----------------------------------------------------------------------------------------+ | 3 | apps/benchmark\_demo/webserver\_app/webserver | Web server and node files | +------+--------------------------------------------------+----------------------------------------------------------------------------------------+