diff --git a/source/buildroot/Overview.rst b/source/buildroot/Overview.rst index 9a6c3647f..9eb5b0598 100644 --- a/source/buildroot/Overview.rst +++ b/source/buildroot/Overview.rst @@ -44,7 +44,7 @@ to github repository. Repository structure ==================== -.. code-block:: +.. code-block:: text buildroot-external-TI ├── external.desc diff --git a/source/common/EVM_Hardware_Setup/_AM68_SK_Hardware_Setup.rst b/source/common/EVM_Hardware_Setup/_AM68_SK_Hardware_Setup.rst index ed5fef394..397f29d5c 100644 --- a/source/common/EVM_Hardware_Setup/_AM68_SK_Hardware_Setup.rst +++ b/source/common/EVM_Hardware_Setup/_AM68_SK_Hardware_Setup.rst @@ -8,7 +8,7 @@ AM68 SK is a low cost, small form factor board designed to bring smart cameras, robots and intelligent machines to life. For more information related to the board, full list of peripherals supported, pin settings for boot modes and more -visit AM68 SK `User guide `_ +visit AM68 SK `User guide `__ To run the demos on AM68 SK you will require, @@ -23,7 +23,7 @@ To run the demos on AM68 SK you will require, a. Nominal Output Voltage: 5-20VDC b. Maximum Output Current: 5000 mA - c. Refer to AM68 SK `User guide `_ + c. Refer to AM68 SK `User guide `__ for more details. Connect the components to the EVM as shown in the image. diff --git a/source/common/EVM_Hardware_Setup/_AM69_SK_Hardware_Setup.rst b/source/common/EVM_Hardware_Setup/_AM69_SK_Hardware_Setup.rst index 210b9f4d1..5780418f6 100644 --- a/source/common/EVM_Hardware_Setup/_AM69_SK_Hardware_Setup.rst +++ b/source/common/EVM_Hardware_Setup/_AM69_SK_Hardware_Setup.rst @@ -8,7 +8,7 @@ AM69 SK is a low cost, small form factor board designed to bring smart cameras, robots and intelligent machines to life. For more information related to the board, full list of peripherals supported, pin settings for boot modes and more -visit AM69 SK `User guide `_ +visit AM69 SK `User guide `__ To run the demos on AM69 SK you will require, @@ -23,7 +23,7 @@ To run the demos on AM69 SK you will require, a. Nominal Output Voltage: 5-20VDC b. Maximum Output Current: 5000 mA - c. Refer to AM69 SK `User guide `_ + c. Refer to AM69 SK `User guide `__ for more details. Connect the components to the EVM as shown in the image. 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..6746b522e 100644 --- a/source/common/EVM_Hardware_Setup/_OMAPL137_EVM_Hardware_Setup.rst +++ b/source/common/EVM_Hardware_Setup/_OMAPL137_EVM_Hardware_Setup.rst @@ -1,6 +1,6 @@ OMAP-L137/C6747 EVM Hardware Setup Guide -====================================== +======================================== Setting up the Hardware ----------------------- diff --git a/source/common/EVM_Hardware_Setup/_OMAPL138-C6748_LCDK_Hardware_Setup.rst b/source/common/EVM_Hardware_Setup/_OMAPL138-C6748_LCDK_Hardware_Setup.rst index 9b28cdeb7..6d91a60ef 100644 --- a/source/common/EVM_Hardware_Setup/_OMAPL138-C6748_LCDK_Hardware_Setup.rst +++ b/source/common/EVM_Hardware_Setup/_OMAPL138-C6748_LCDK_Hardware_Setup.rst @@ -111,6 +111,7 @@ Connecting to Target and Loading/Running Program The following GEL outputs should appear in the CCS Console view. **OMAP-L138 LCDK:** + :: ARM9_0: Output: Target Connected. @@ -131,6 +132,7 @@ The following GEL outputs should appear in the CCS Console view. ARM9_0: Output: --------------------------------------------- **C6748 LCDK:** + :: C674X_0: Output: Target Connected. diff --git a/source/debian/Building_Debian_Image.rst b/source/debian/Building_Debian_Image.rst index 1e4c7205b..bd56fdf3f 100644 --- a/source/debian/Building_Debian_Image.rst +++ b/source/debian/Building_Debian_Image.rst @@ -31,7 +31,7 @@ The scripts are hosted at https://github.com/TexasInstruments/ti-bdebstrap To clone the repository, run: -.. code-block:: +.. code-block:: console git clone https://github.com/TexasInstruments/ti-bdebstrap.git @@ -39,7 +39,7 @@ To clone the repository, run: Repository Structure -------------------- -.. code-block:: +.. code-block:: text ti-bdebstrap ├── build.sh @@ -108,13 +108,13 @@ Install Pre-requisite Packages First, ensure that your repositories are up-to-date: -.. code-block:: +.. code-block:: console sudo apt update Then, install packages as follows: -.. code-block:: +.. code-block:: console sudo apt install -y \ pigz expect pv \ @@ -128,13 +128,13 @@ Then, install packages as follows: Ensure that all packages were correctly installed using: -.. code-block:: +.. code-block:: console sudo apt install --fix-broken Finally, install ``toml-cli`` and ``yamllint``: -.. code-block:: +.. code-block:: console pip3 install toml-cli pip3 install yamllint @@ -182,7 +182,7 @@ Building the Image To build an image, you need to run the :file:`build.sh` script: -.. code-block:: +.. code-block:: console sudo ./build.sh @@ -192,7 +192,7 @@ After the build, the RootFS, Boot partition and bsp_sources are stored in :file: Example: to build for ``trixie-am62pxx-evm``, run: -.. code-block:: +.. code-block:: console sudo ./build.sh trixie-am62pxx-evm @@ -205,13 +205,13 @@ This step can be skipped if you do not want to share the generated Image with an To generate an SD Card Image with the generated RootFS and Boot partition files, run: -.. code-block:: +.. code-block:: console ./create-wic.sh Example: to build for ``trixie-am62pxx-evm``, run: -.. code-block:: +.. code-block:: console ./create-wic.sh trixie-am62pxx-evm @@ -222,13 +222,13 @@ Flash Image to SD Card using Script To flash the SD card without generating a wic image, use the :file:`create-sdcard.sh` script. Run it using the below command and follow with the prompts. -.. code-block:: +.. code-block:: console sudo ./create-sdcard.sh For example, if the image is ``trixie-am62pxx-evm``, type: -.. code-block:: +.. code-block:: console sudo ./create-sdcard.sh trixie-am62pxx-evm diff --git a/source/devices/AM57X/linux/Release_Specific_Performance_Guide.rst b/source/devices/AM57X/linux/Release_Specific_Performance_Guide.rst index 54acf4560..14910a868 100644 --- a/source/devices/AM57X/linux/Release_Specific_Performance_Guide.rst +++ b/source/devices/AM57X/linux/Release_Specific_Performance_Guide.rst @@ -721,6 +721,7 @@ OpenSSL Performance | :: + time -v openssl speed -elapsed -evp aes-128-cbc diff --git a/source/devices/J7_Family/linux/Release_Specific_Yocto_layer_Configuration.rst b/source/devices/J7_Family/linux/Release_Specific_Yocto_layer_Configuration.rst index d25ea064a..eff96a8f5 100644 --- a/source/devices/J7_Family/linux/Release_Specific_Yocto_layer_Configuration.rst +++ b/source/devices/J7_Family/linux/Release_Specific_Yocto_layer_Configuration.rst @@ -27,6 +27,7 @@ Yocto Layer Configuration ./oe-layertool-setup.sh -f configs/processor-sdk-linux/ The Linux SDK package also has the above tool cloned at the top level. If you have it installed: + :: cd /yocto-build diff --git a/source/linux/Examples_and_Demos/Application_Demos/Dual_Camera_Demo.rst b/source/linux/Examples_and_Demos/Application_Demos/Dual_Camera_Demo.rst index 713670208..1ef9f1f91 100644 --- a/source/linux/Examples_and_Demos/Application_Demos/Dual_Camera_Demo.rst +++ b/source/linux/Examples_and_Demos/Application_Demos/Dual_Camera_Demo.rst @@ -6,27 +6,23 @@ Below diagram illustrates the video data processing flow of dual camera demo. .. Image:: /images/Dual_camera_demo.png -**Dual camera example demo demonstrates following-** +**Dual camera example demo demonstrates the following** -1. Video capture using V4L2 interface from up to two cameras. -2. QT QWidget based drawing of user interface using linuxfb plugin. linuxfb is fbdev based software drawn QPA. +#. Video capture using V4L2 interface from up to two cameras. +#. QT QWidget based drawing of user interface using linuxfb plugin, where linuxfb is an fbdev based software drawn QPA. #. Hardware accelerated scaling of input video from primary camera to display resolution using DSS IP. #. Hardware accelerated scaling of input video from secondary camera (if connected) to lower resolution using DSS IP. #. Hardware accelerated overlaying of two video planes and graphics plane using DSS IP. #. Scaling of two video planes and overlaying with graphics plane happens on the fly in single pass inside DSS IP using DRM atomic APIs. -#. Snapshot of the screen using JPEG compression running on ARM. The captured images are stored in filesystem under /usr/share/camera-images/ folder -#. The camera and display driver shares video buffer using dmabuf protocol. Capture driver writes captured content to a buffer which is directly read by the display driver without copying the content locally to another buffer (zero copy involved). +#. Snapshot of the screen using JPEG compression running on ARM. The captured images are stored in filesystem under the :file:`/usr/share/camera-images/` folder +#. The camera and display driver shares video buffer using DMA buffers. The capture driver writes content to a buffer which is directly read by the GPU and potentially the display without copying the content locally to another buffer (zero copy involved). #. The application also demonstrates allocating the buffer from either omap_bo (from omapdrm) memory pool or from cmem buffer pool. The option to pick omap_bo or cmem memory pool is provided runtime using cmd line. #. If the application has need to do some CPU based processing on captured buffer, then it is recommended to allocate the buffer using CMEM buffer pool. The reason being omap_bo memory pool doesn't support cache read operation. Due to this any CPU operation involving video buffer read will be 10x to 15x slower. CMEM pool supports cache operation and hence CPU operations on capture video buffer are fast. -#. The application runs in nullDRM/full screen mode (no windows manager like wayland/x11) and the linuxfb QPA runs in fbdev mode. This gives applicationfull control of DRM resource DSS to control and display the video planes. +#. The application runs in nullDRM/full screen mode (no compositors like Weston) and the linuxfb QPA runs in fbdev mode. This gives application full control of DRM resource DSS to control and display the video planes. **Instructions to run dual camera demo** * Since the application need control of DRM resource (DSS) and there can be only one master, make sure that the wayland/weston is not running. -#/etc/init.d/weston stop - -* Run the dual camera application -#dual-camera -platform linuxfb <0/1> - +* Run the dual camera application ``dual-camera -platform linuxfb <0/1>`` * When last argument is set as 0, capture and display driver allocates memory from omap_bo pool. * When it is set to 1, the buffers are allocated from CMEM pool. diff --git a/source/linux/Examples_and_Demos/Application_Demos/Video_Graphics_Test.rst b/source/linux/Examples_and_Demos/Application_Demos/Video_Graphics_Test.rst index 5a7b8680d..05b808e7d 100644 --- a/source/linux/Examples_and_Demos/Application_Demos/Video_Graphics_Test.rst +++ b/source/linux/Examples_and_Demos/Application_Demos/Video_Graphics_Test.rst @@ -50,6 +50,7 @@ The APIs required to achieve scaling, overlaying and alpha-blending using the DS Running the Test ---------------- In order for the users to run the video graphics test, please type the following commands on the EVM: + :: target # insmod /lib/modules//extra/galcore.ko baseAddress=0x80000000 physSize=0x80000000 diff --git a/source/linux/Foundational_Components/IPC/_IPC_for_K2x.rst b/source/linux/Foundational_Components/IPC/_IPC_for_K2x.rst index 748accce2..c641d4a33 100644 --- a/source/linux/Foundational_Components/IPC/_IPC_for_K2x.rst +++ b/source/linux/Foundational_Components/IPC/_IPC_for_K2x.rst @@ -562,8 +562,6 @@ So we will need to add the following lines to place the trace buffer and resourc var Resource = xdc.useModule('ti.ipc.remoteproc.Resource'); Resource.loadSegment = "L2SRAM" -:: - Now follow the steps in `Running the Bundled IPC Examples`_. diff --git a/source/linux/Foundational_Components/IPC/_Multiple_Ways_of_ARM-DSP_Communication.rst b/source/linux/Foundational_Components/IPC/_Multiple_Ways_of_ARM-DSP_Communication.rst index d03b4942f..9279af80f 100644 --- a/source/linux/Foundational_Components/IPC/_Multiple_Ways_of_ARM-DSP_Communication.rst +++ b/source/linux/Foundational_Components/IPC/_Multiple_Ways_of_ARM-DSP_Communication.rst @@ -225,7 +225,6 @@ and DSP processors in a multi-processor environment. `__ -| .. rubric:: User Cases :name: user-cases diff --git a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Camera/CAL.rst b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Camera/CAL.rst index 3ac6a6f51..7a5fb9dea 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Camera/CAL.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Camera/CAL.rst @@ -200,6 +200,7 @@ properly configure the DPHY. .. seealso:: `MIPI CSI-2 Kernel API reference `_ As you can see in the above link, typically the pixel rate is calculated as follows: + :: pixel_rate = link_freq * 2 * nr_of_lanes / bits_per_sample @@ -210,6 +211,7 @@ therefore sensor dependent. This is also the most accurate method. Alternatively, if you trust that your sensor is configured correctly for a specific resolution/pixel format and frame interval then the pixel rate can be calculated using this simplified formula: + :: pixel_rate = total horizontal width * total vertical lines * frame per second @@ -218,6 +220,7 @@ Here total horizontal width and total vertical lines includes blanking. This information is also sensor dependent or at least configuration dependent. For example if we take a look at the ov5640 configuration for 1920x1080\@30 fps: + :: total horizontal width = 2500 @@ -347,11 +350,11 @@ can be enable as follows: - echo 3 >/sys/class/video4linux/video1/dev\_debug This allows V4L2 ioctl calls to be logged. -| + - echo 3 > /sys/module/videobuf2\_core/parameters/debug This allows VB2 buffers operation to be logged. -| + In addition ti-cal also has specific debug log which can be enabled as follows: diff --git a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Network/CPSW-PTP.rst b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Network/CPSW-PTP.rst index f3ab40339..c3069ddde 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Network/CPSW-PTP.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Network/CPSW-PTP.rst @@ -676,6 +676,7 @@ PTP with Transparent Clock (Switch mode) Use the following ptp config file on the device that acts as the transparent clock: **tc-ptp.cfg** + :: [global] 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..69a364e4e 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Network/NetCP.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Network/NetCP.rst @@ -734,6 +734,7 @@ M / (2^S \* D) = 5000 / (2^10 \* 3) hence M = 5000, S = 10, D = 3 + | Note 3: cpts driver keeps a table of M/S/D for some common frequencies diff --git a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/PCIe/PCIe_Backplane.rst b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/PCIe/PCIe_Backplane.rst index 8e9b3f6a6..15948d1ed 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/PCIe/PCIe_Backplane.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/PCIe/PCIe_Backplane.rst @@ -70,7 +70,6 @@ DRA7x boards communicate with each other using J721E as backplane. :name: backplane-configuration .. rubric:: *Backplane DTS Overlay File* - :name: backplane-configuration The following DTS overlay file configures the PCIe controller in EP mode and also contains a device tree node to create a NTB function device: diff --git a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/PMIC/pmic_tps6594.rst b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/PMIC/pmic_tps6594.rst index 58e16e7e0..c4723e1f7 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/PMIC/pmic_tps6594.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/PMIC/pmic_tps6594.rst @@ -71,7 +71,7 @@ Configs to be enabled in kernel: For safety applications, a CRC feature can be enabled from userspace: -.. code-block:: bash +.. code-block:: console echo "options tps6594_i2c enable_crc=true" > /etc/modprobe.d/tps6594.conf; sync; @@ -81,7 +81,7 @@ the new setting. CRC feature will be enabled at module loading. Example of kernel messages for J721S2: -.. code-block:: text +.. code-block:: dmesg [ 5.060454] tps6594 0-0048: CRC feature enabled on primary PMIC [ 5.086440] tps6594 0-004c: CRC feature enabled on secondary PMIC @@ -89,7 +89,7 @@ for J721S2: To disable CRC feature, the modprobe conf file must be removed: -.. code-block:: bash +.. code-block:: console rm /etc/modprobe.d/tps6594.conf; sync; @@ -101,16 +101,16 @@ the new setting. CRC feature can be enabled through the kernel command line parameter: -.. code-block:: bash +.. code-block:: console - tps6594_i2c.enable_crc=Y + tps6594_i2c.enable_crc=Y If the kernel command line is edited from uboot, the new setting can be saved to the persistent storage: -.. code-block:: bash +.. code-block:: console - saveenv + saveenv TPS6594 SPI driver ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ @@ -119,7 +119,7 @@ Driver source location: .. code-block:: text - drivers/mfd/tps6594-spi.c + drivers/mfd/tps6594-spi.c .. rubric:: Kernel configuration options :name: kernel-configuration-options-spi @@ -128,10 +128,10 @@ Configs to be enabled in kernel: .. code-block:: text - CONFIG_SPI_MASTER - CONFIG_MFD_TPS6594_SPI (TPS6594 SPI support) + CONFIG_SPI_MASTER + CONFIG_MFD_TPS6594_SPI (TPS6594 SPI support) -:: +.. code-block:: menuconfig Device Drivers ---> Multifunction device drivers ---> @@ -153,7 +153,7 @@ Driver source location: .. code-block:: text - drivers/pinctrl/pinctrl-tps6594.c + drivers/pinctrl/pinctrl-tps6594.c [WARNING] GPIO indexation is 0-based in linux, whereas it is 1-based in the PMIC TRM. So GPIO5 in linux corresponds to GPIO6 in the TRM. @@ -165,9 +165,9 @@ Configs to be enabled in kernel: .. code-block:: text - CONFIG_PINCTRL_TPS6594 (TPS6594 GPIO support) + CONFIG_PINCTRL_TPS6594 (TPS6594 GPIO support) -:: +.. code-block:: menuconfig Device Drivers ---> Pin controllers ---> @@ -181,46 +181,43 @@ Examples given for AM62A. List all gpiochips present on the system, their names, labels and number of GPIO lines: -.. code-block:: bash +.. code-block:: console - gpiodetect - - [...] - gpiochip4 [tps6594-gpio] (11 lines) + $ gpiodetect + [...] + gpiochip4 [tps6594-gpio] (11 lines) List all lines of specified gpiochips, their names, consumers, direction, active state and additional flags: -.. code-block:: bash - - gpioinfo gpiochip4 - - gpiochip4 - 11 lines: - line 0: unnamed unused input active-high - line 1: unnamed unused input active-high - line 2: unnamed unused input active-high - line 3: unnamed unused output active-high - line 4: unnamed unused input active-high - line 5: unnamed unused output active-high - line 6: unnamed unused input active-high - line 7: unnamed unused input active-high - line 8: unnamed unused input active-high - line 9: unnamed unused input active-high - line 10: unnamed unused input active-high +.. code-block:: console + + $ gpioinfo gpiochip4 + gpiochip4 - 11 lines: + line 0: unnamed unused input active-high + line 1: unnamed unused input active-high + line 2: unnamed unused input active-high + line 3: unnamed unused output active-high + line 4: unnamed unused input active-high + line 5: unnamed unused output active-high + line 6: unnamed unused input active-high + line 7: unnamed unused input active-high + line 8: unnamed unused input active-high + line 9: unnamed unused input active-high + line 10: unnamed unused input active-high Read values of specified GPIO lines: -.. code-block:: bash +.. code-block:: console - gpioget gpiochip4 5 - - 0 + $ gpioget gpiochip4 5 + 0 Set values of specified GPIO lines: -.. code-block:: bash +.. code-block:: console - gpioset gpiochip4 5=1 + gpioset gpiochip4 5=1 .. rubric:: Driver usage (pinctrl) :name: driver-usage-pinctrl @@ -229,38 +226,43 @@ Examples given for AM62A. Get functions available for each pin: -.. code-block:: bash - - cat /sys/kernel/debug/pinctrl/tps6594-pinctrl.1.auto/pinmux-functions - - function 0: gpio, groups = [ GPIO0 GPIO1 GPIO2 GPIO3 GPIO4 GPIO5 GPIO6 GPIO7 GPIO8 GPIO9 GPIO10 ] - function 1: nsleep1, groups = [ GPIO0 GPIO1 GPIO2 GPIO3 GPIO4 GPIO5 GPIO6 GPIO7 GPIO8 GPIO9 GPIO10 ] - function 2: nsleep2, groups = [ GPIO0 GPIO1 GPIO2 GPIO3 GPIO4 GPIO5 GPIO6 GPIO7 GPIO8 GPIO9 GPIO10 ] - function 3: wkup1, groups = [ GPIO0 GPIO1 GPIO2 GPIO3 GPIO4 GPIO5 GPIO6 GPIO7 GPIO8 GPIO9 GPIO10 ] - function 4: wkup2, groups = [ GPIO0 GPIO1 GPIO2 GPIO3 GPIO4 GPIO5 GPIO6 GPIO7 GPIO8 GPIO9 GPIO10 ] - function 5: scl_i2c2-cs_spi, groups = [ GPIO0 GPIO1 ] - function 6: nrstout_soc, groups = [ GPIO0 GPIO10 ] - function 7: trig_wdog, groups = [ GPIO1 GPIO10 ] - function 8: sda_i2c2-sdo_spi, groups = [ GPIO1 ] - function 9: clk32kout, groups = [ GPIO2 GPIO3 GPIO7 ] - function 10: nerr_soc, groups = [ GPIO2 ] - function 11: sclk_spmi, groups = [ GPIO4 ] - function 12: sdata_spmi, groups = [ GPIO5 ] - function 13: nerr_mcu, groups = [ GPIO6 ] - function 14: syncclkout, groups = [ GPIO7 GPIO9 ] - function 15: disable_wdog, groups = [ GPIO7 GPIO8 ] - function 16: pdog, groups = [ GPIO8 ] - function 17: syncclkin, groups = [ GPIO9 ] +.. code-block:: console + + $ cat /sys/kernel/debug/pinctrl/tps6594-pinctrl.1.auto/pinmux-functions + function 0: gpio, groups = [ GPIO0 GPIO1 GPIO2 GPIO3 GPIO4 GPIO5 GPIO6 GPIO7 GPIO8 GPIO9 GPIO10 ] + function 1: nsleep1, groups = [ GPIO0 GPIO1 GPIO2 GPIO3 GPIO4 GPIO5 GPIO6 GPIO7 GPIO8 GPIO9 GPIO10 ] + function 2: nsleep2, groups = [ GPIO0 GPIO1 GPIO2 GPIO3 GPIO4 GPIO5 GPIO6 GPIO7 GPIO8 GPIO9 GPIO10 ] + function 3: wkup1, groups = [ GPIO0 GPIO1 GPIO2 GPIO3 GPIO4 GPIO5 GPIO6 GPIO7 GPIO8 GPIO9 GPIO10 ] + function 4: wkup2, groups = [ GPIO0 GPIO1 GPIO2 GPIO3 GPIO4 GPIO5 GPIO6 GPIO7 GPIO8 GPIO9 GPIO10 ] + function 5: scl_i2c2-cs_spi, groups = [ GPIO0 GPIO1 ] + function 6: nrstout_soc, groups = [ GPIO0 GPIO10 ] + function 7: trig_wdog, groups = [ GPIO1 GPIO10 ] + function 8: sda_i2c2-sdo_spi, groups = [ GPIO1 ] + function 9: clk32kout, groups = [ GPIO2 GPIO3 GPIO7 ] + function 10: nerr_soc, groups = [ GPIO2 ] + function 11: sclk_spmi, groups = [ GPIO4 ] + function 12: sdata_spmi, groups = [ GPIO5 ] + function 13: nerr_mcu, groups = [ GPIO6 ] + function 14: syncclkout, groups = [ GPIO7 GPIO9 ] + function 15: disable_wdog, groups = [ GPIO7 GPIO8 ] + function 16: pdog, groups = [ GPIO8 ] + function 17: syncclkin, groups = [ GPIO9 ] Modify the function for a pin: -.. code-block:: bash +.. code-block:: console + + echo " " > /sys/kernel/debug/pinctrl/tps6594-pinctrl.1.auto/pinmux-select + +Examples: - echo " " > /sys/kernel/debug/pinctrl/tps6594-pinctrl.1.auto/pinmux-select +.. code-block:: console - Examples: - echo "GPIO7 gpio" > /sys/kernel/debug/pinctrl/tps6594-pinctrl.1.auto/pinmux-select - echo "GPIO2 nerr_soc" > /sys/kernel/debug/pinctrl/tps6594-pinctrl.1.auto/pinmux-select + echo "GPIO7 gpio" > /sys/kernel/debug/pinctrl/tps6594-pinctrl.1.auto/pinmux-select + +.. code-block:: console + + echo "GPIO2 nerr_soc" > /sys/kernel/debug/pinctrl/tps6594-pinctrl.1.auto/pinmux-select TPS6594 regulator driver ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ @@ -274,7 +276,7 @@ Driver source location: .. code-block:: text - drivers/regulator/tps6594-regulator.c + drivers/regulator/tps6594-regulator.c .. rubric:: Kernel configuration options :name: kernel-configuration-options-regul @@ -283,9 +285,9 @@ Configs to be enabled in kernel: .. code-block:: text - CONFIG_REGULATOR_TPS6594 (TPS6594 regulator support) + CONFIG_REGULATOR_TPS6594 (TPS6594 regulator support) -:: +.. code-block:: menuconfig Device Drivers ---> Voltage and Current Regulator Support ---> @@ -296,15 +298,15 @@ Configs to be enabled in kernel: Regulator summary can be displayed: -.. code-block:: bash +.. code-block:: console - cat /sys/kernel/debug/regulator/regulator_summary + cat /sys/kernel/debug/regulator/regulator_summary Regulator events, if any, can be seen by running this command: -.. code-block:: bash +.. code-block:: console - cat /proc/interrupts + cat /proc/interrupts TPS6594 ESM driver ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ @@ -319,7 +321,7 @@ Driver source location: .. code-block:: text - drivers/misc/tps6594-esm.c + drivers/misc/tps6594-esm.c .. rubric:: Kernel configuration options :name: kernel-configuration-options-esm @@ -328,9 +330,9 @@ Configs to be enabled in kernel: .. code-block:: text - CONFIG_TPS6594_ESM (TPS6594 ESM support) + CONFIG_TPS6594_ESM (TPS6594 ESM support) -:: +.. code-block:: menuconfig Device Drivers ---> Misc devices ---> @@ -343,9 +345,9 @@ PMIC ESM will be started at module loading. ESM errors, if any, can be seen by running this command: -.. code-block:: bash +.. code-block:: console - cat /proc/interrupts + cat /proc/interrupts TPS6594 RTC driver ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ @@ -354,7 +356,7 @@ Driver source location: .. code-block:: text - drivers/rtc/rtc-tps6594.c + drivers/rtc/rtc-tps6594.c .. rubric:: Kernel configuration options :name: kernel-configuration-options-rtc @@ -363,9 +365,9 @@ Configs to be enabled in kernel: .. code-block:: text - CONFIG_RTC_DRV_TPS6594 (TPS6594 RTC support) + CONFIG_RTC_DRV_TPS6594 (TPS6594 RTC support) -:: +.. code-block:: menuconfig Device Drivers ---> Real Time Clock ---> @@ -379,20 +381,20 @@ device file by the kernel to be used by userspace: .. code-block:: text - /dev/rtcX X - index (zero-based) + /dev/rtcX X - index (zero-based) Read date/time as follow: -.. code-block:: bash +.. code-block:: console - cat /sys/class/rtc/rtc0/date - cat /sys/class/rtc/rtc0/time + cat /sys/class/rtc/rtc0/date + cat /sys/class/rtc/rtc0/time Alarms, if any, can be seen by running this command: -.. code-block:: bash +.. code-block:: console - cat /proc/interrupts + cat /proc/interrupts An example of how to use RTC from a userspace application is given in PFSM driver chapter. @@ -412,7 +414,7 @@ Driver source location: .. code-block:: text - drivers/misc/tps6594-pfsm.c + drivers/misc/tps6594-pfsm.c .. rubric:: Kernel configuration options :name: kernel-configuration-options-pfsm @@ -421,9 +423,9 @@ Configs to be enabled in kernel: .. code-block:: text - CONFIG_TPS6594_PFSM (TPS6594 PFSM support) + CONFIG_TPS6594_PFSM (TPS6594 PFSM support) -:: +.. code-block:: menuconfig Device Drivers ---> Misc devices ---> @@ -437,35 +439,35 @@ device file by the kernel to be used by userspace: .. code-block:: text - /dev/pfsm-X-Y X - chip ID - [0] = TPS6594 - [1] = TPS6593 - [2] = LP8764 + /dev/pfsm-X-Y X - chip ID + [0] = TPS6594 + [1] = TPS6593 + [2] = LP8764 - Y - I2C address or SPI chip select + Y - I2C address or SPI chip select - Example: '/dev/pfsm-1-0x4c' is TPS6593 @ I2C address 0x4c + Example: '/dev/pfsm-1-0x4c' is TPS6593 @ I2C address 0x4c Dump the registers of pages 0 and 1 as follow: .. code-block:: bash - hexdump -C /dev/pfsm-1-0x4c + hexdump -C /dev/pfsm-1-0x4c PFSM events, if any, can be seen by running this command: .. code-block:: bash - cat /proc/interrupts + cat /proc/interrupts For more information, see kernel documentation: .. code-block:: text - Documentation/misc-devices/tps6594-pfsm.rst + Documentation/misc-devices/tps6594-pfsm.rst A userspace code example is also provided: .. code-block:: text - samples/pfsm + samples/pfsm diff --git a/source/linux/Foundational_Components/PRU-ICSS/Linux_Drivers/pru-icssg-pwm.rst b/source/linux/Foundational_Components/PRU-ICSS/Linux_Drivers/pru-icssg-pwm.rst index 3672e9ea7..59fcc8305 100644 --- a/source/linux/Foundational_Components/PRU-ICSS/Linux_Drivers/pru-icssg-pwm.rst +++ b/source/linux/Foundational_Components/PRU-ICSS/Linux_Drivers/pru-icssg-pwm.rst @@ -36,16 +36,16 @@ The PRU PWM Linux kernel driver depends on the PRU-ICSS kernel driver. So the following kernel Kconfig options should be enabled to use the PRU PWM module. -.. code:: +.. code-block:: menuconfig - Device Drivers ---> - SOC (System On Chip) specific Drivers ---> - [*] TI SOC drivers support ---> - TI PRU-ICSS Subsystem Platform drivers + Device Drivers ---> + SOC (System On Chip) specific Drivers ---> + [*] TI SOC drivers support ---> + TI PRU-ICSS Subsystem Platform drivers - Device Drivers ---> - Pulse-Width Modulation (PWM) Support ---> - PRU-ICSS PWM support + Device Drivers ---> + Pulse-Width Modulation (PWM) Support ---> + PRU-ICSS PWM support .. rubric:: PRU PWM Sysfs Usage diff --git a/source/linux/Foundational_Components/PRU-ICSS/Linux_Drivers/pru-sw-uart.rst b/source/linux/Foundational_Components/PRU-ICSS/Linux_Drivers/pru-sw-uart.rst index 81a099577..6e8cf40fb 100644 --- a/source/linux/Foundational_Components/PRU-ICSS/Linux_Drivers/pru-sw-uart.rst +++ b/source/linux/Foundational_Components/PRU-ICSS/Linux_Drivers/pru-sw-uart.rst @@ -42,16 +42,16 @@ in PRU R30 and R31. For details please refer to the kernel device tree binding doc: -.. code:: +.. code-block:: text - Documentation/devicetree/bindings/serial/pru-suart.txt + Documentation/devicetree/bindings/serial/pru-suart.txt The Processor SDK Linux kernel also provides an device tree example for Beaglebone Black: -.. code:: +.. code-block:: text - arch/arm/boot/dts/am335x-boneblack-prusuart.dts + arch/arm/boot/dts/am335x-boneblack-prusuart.dts This example defines the 3 UARTs on PRU0 without hardware flow control and 3 UARTs on PRU1 with hardware flow control. All the UART pins are available on @@ -64,16 +64,16 @@ The PRU Soft UART Linux kernel driver depends on the PRU-ICSS kernel driver. So the following kernel Kconfig options should be enabled to use the PRU Soft UART module. -.. code:: +.. code-block:: menuconfig - Device Drivers ---> - SOC (System On Chip) specific Drivers ---> - [*] TI SOC drivers support ---> - TI PRU-ICSS Subsystem Platform drivers + Device Drivers ---> + SOC (System On Chip) specific Drivers ---> + [*] TI SOC drivers support ---> + TI PRU-ICSS Subsystem Platform drivers - Device Drivers ---> - Character devices ---> - Serial drivers ---> - TI PRU Software UART suppor + Device Drivers ---> + Character devices ---> + Serial drivers ---> + TI PRU Software UART suppor diff --git a/source/linux/Foundational_Components/PRU-ICSS/Linux_Drivers/pruss-uart.rst b/source/linux/Foundational_Components/PRU-ICSS/Linux_Drivers/pruss-uart.rst index 0b6a85a96..5b850fbc2 100644 --- a/source/linux/Foundational_Components/PRU-ICSS/Linux_Drivers/pruss-uart.rst +++ b/source/linux/Foundational_Components/PRU-ICSS/Linux_Drivers/pruss-uart.rst @@ -30,45 +30,45 @@ The PRUSS UART Linux kernel driver depends on the PRU-ICSS kernel drivers. So the following kernel Kconfig options should be enabled to use the PRUSS UART module. -.. code:: +.. code-block:: menuconfig - Device Drivers ---> - SOC (System On Chip) specific Drivers ---> - [*] TI SOC drivers support ---> - TI PRU-ICSS Subsystem Platform drivers + Device Drivers ---> + SOC (System On Chip) specific Drivers ---> + [*] TI SOC drivers support ---> + TI PRU-ICSS Subsystem Platform drivers - Device Drivers ---> - IRQ chip support ---> - TI PRU-ICSS Interrupt Controller + Device Drivers ---> + IRQ chip support ---> + TI PRU-ICSS Interrupt Controller - Device Drivers ---> - Character devices ---> - Serial drivers ---> - TI PRU-ICSS UART support + Device Drivers ---> + Character devices ---> + Serial drivers ---> + TI PRU-ICSS UART support .. rubric:: Example DT configuration From am335x-evmsk.dts -.. code:: +.. code-block:: dts - &pruss_uart { - prus = <&pru0>; - ti,pru-interrupt-map = <0 6 2 2>; - pinctrl-names = "default"; - pinctrl-0 = <&prussuart_pins>; - status = "okay"; - }; + &pruss_uart { + prus = <&pru0>; + ti,pru-interrupt-map = <0 6 2 2>; + pinctrl-names = "default"; + pinctrl-0 = <&prussuart_pins>; + status = "okay"; + }; .. rubric:: Driver Usage Once the driver is probed, kernel log shows the following message. -.. code:: +.. code-block:: dmesg - [ 28.617700] 4a328000.serial: ttyS1 at MMIO 0x4a328000 (irq = 77, base_baud = 12000000) is a 16550A + [ 28.617700] 4a328000.serial: ttyS1 at MMIO 0x4a328000 (irq = 77, base_baud = 12000000) is a 16550A Therefore the device node /dev/ttyS1 is associated to the PRUSS UART, user space application can read/write this serial port. For detalls please refer diff --git a/source/linux/Foundational_Components_IPC64x.rst b/source/linux/Foundational_Components_IPC64x.rst index 4abd11533..aa4efccbe 100644 --- a/source/linux/Foundational_Components_IPC64x.rst +++ b/source/linux/Foundational_Components_IPC64x.rst @@ -378,31 +378,30 @@ rpmsg_char_close() `All remote proc ids are defined in rproc_id.h `__ The below table lists the device enumerations as defined in the rpmsg_char_library. The validiaty of the enumerations wrt AM64x is also specified. -:: - +------------------+--------------------+---------+-----------------------------------+ - | Enumeration ID | Device Name | Valid | Description | - +==================+====================+=========+===================================+ - | R5F_MCU0_0 |N/A | No | R5F SS in MCU domain | - +------------------+--------------------+---------+-----------------------------------+ - | R5F_MCU0_1 |N/A | No | R5F SS in MCU domain | - +------------------+--------------------+---------+-----------------------------------+ - | R5F_MAIN0_0 | 78000000.r5f | Yes | R5F Cluster0 Core0 in Main Domain | - +------------------+--------------------+---------+-----------------------------------+ - | R5F_MAIN0_1 | 78200000.r5f | Yes | R5F Cluster0 Core1 in Main Domain | - +------------------+--------------------+---------+-----------------------------------+ - | R5F_MAIN1_0 | 78400000.r5f | Yes | R5F Cluster1 Core0 in Main Domain | - +------------------+--------------------+---------+-----------------------------------+ - | R5F_MAIN1_1 | 78600000.r5f | Yes | R5F Cluster1 Core1 in Main Domain | - +------------------+--------------------+---------+-----------------------------------+ - | DSP_C66_0 |N/A | No | C66 DSP | - +------------------+--------------------+---------+-----------------------------------+ - | DSP_C66_1 |N/A | No | C66 DSP | - +------------------+--------------------+---------+-----------------------------------+ - | DSP_C71_0 |N/A | No | C71 DSP | - +------------------+--------------------+---------+-----------------------------------+ - | M4F_MCU0_0 | 5000000.m4f | Yes | M4F core in MCU Domain | - +------------------+--------------------+---------+-----------------------------------+ ++------------------+--------------------+---------+-----------------------------------+ +| Enumeration ID | Device Name | Valid | Description | ++==================+====================+=========+===================================+ +| R5F_MCU0_0 | N/A | No | R5F SS in MCU domain | ++------------------+--------------------+---------+-----------------------------------+ +| R5F_MCU0_1 | N/A | No | R5F SS in MCU domain | ++------------------+--------------------+---------+-----------------------------------+ +| R5F_MAIN0_0 | 78000000.r5f | Yes | R5F Cluster0 Core0 in Main Domain | ++------------------+--------------------+---------+-----------------------------------+ +| R5F_MAIN0_1 | 78200000.r5f | Yes | R5F Cluster0 Core1 in Main Domain | ++------------------+--------------------+---------+-----------------------------------+ +| R5F_MAIN1_0 | 78400000.r5f | Yes | R5F Cluster1 Core0 in Main Domain | ++------------------+--------------------+---------+-----------------------------------+ +| R5F_MAIN1_1 | 78600000.r5f | Yes | R5F Cluster1 Core1 in Main Domain | ++------------------+--------------------+---------+-----------------------------------+ +| DSP_C66_0 | N/A | No | C66 DSP | ++------------------+--------------------+---------+-----------------------------------+ +| DSP_C66_1 | N/A | No | C66 DSP | ++------------------+--------------------+---------+-----------------------------------+ +| DSP_C71_0 | N/A | No | C71 DSP | ++------------------+--------------------+---------+-----------------------------------+ +| M4F_MCU0_0 | 5000000.m4f | Yes | M4F core in MCU Domain | ++------------------+--------------------+---------+-----------------------------------+ .. note:: 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..1138b9f47 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 @@ -60,7 +60,7 @@ USB there are some additional steps required. theoretically any system properly ported and configured for AM335x/AM437x. #. Install the necessary services using a terminal on the Linux box. - .. code:: + .. code-block:: console sudo apt-get install isc-dhcp-server atftpd xinetd @@ -71,38 +71,37 @@ USB there are some additional steps required. Edit /etc/dhcp/dhcpd.conf - .. code:: + .. code-block:: text subnet 192.168.2.0 netmask 255.255.255.0 { range dynamic-bootp 192.168.2.2 192.168.2.100; if substring (option vendor-class-identifier, 0, 10) = "AM335x ROM" - { - filename "u-boot-spl-restore.bin"; - } - elsif substring (option vendor-class-identifier, 0, 10) = "DM814x ROM" - { - filename "u-boot-spl-restore.bin"; - } - elsif substring (option vendor-class-identifier, 0, 10) = "AM43xx ROM" - { - filename "u-boot-restore.img"; - } - elsif substring (option vendor-class-identifier, 0, 17) = "AM335x U-Boot SPL" - { - filename "u-boot-restore.img"; - } - elsif substring (option vendor-class-identifier, 0, 10) = "AM43xx U-B" - { - filename "u-boot-restore.img"; - } - else - { - filename "zImage"; - } - + { + filename "u-boot-spl-restore.bin"; + } + elsif substring (option vendor-class-identifier, 0, 10) = "DM814x ROM" + { + filename "u-boot-spl-restore.bin"; + } + elsif substring (option vendor-class-identifier, 0, 10) = "AM43xx ROM" + { + filename "u-boot-restore.img"; + } + elsif substring (option vendor-class-identifier, 0, 17) = "AM335x U-Boot SPL" + { + filename "u-boot-restore.img"; + } + elsif substring (option vendor-class-identifier, 0, 10) = "AM43xx U-B" + { + filename "u-boot-restore.img"; + } + else + { + filename "zImage"; + } range 192.168.2.101 192.168.2.199; - } + } .. note:: This configuration creates a subnet, 192.168.2.0, with a bootp IP Address range of 2 - 100. The isc-dhcp-server will use this @@ -120,27 +119,27 @@ USB there are some additional steps required. Edit /etc/default/atftpd (create the file if necessary) with: - .. code:: + .. code-block:: text - USE_INETD=false - OPTIONS="--tftpd-timeout 300 --retry-timeout 5 --maxthread 100 --verbose=5 --logfile /var/log/atftpd.log --port 69 /tftpboot" + USE_INETD=false + OPTIONS="--tftpd-timeout 300 --retry-timeout 5 --maxthread 100 --verbose=5 --logfile /var/log/atftpd.log --port 69 /tftpboot" - .. note:: This is an example configuration and it can certainly be modified for specific situations. + .. note:: This is an example configuration and it can certainly be modified for specific situations. #. Create directory to store TFTP files (/tftpboot used here) - .. code:: + .. code-block:: console - sudo mkdir /tftpboot - sudo chmod -R 777 /tftpboot - sudo chown -R nobody /tftpboot + sudo mkdir /tftpboot + sudo chmod -R 777 /tftpboot + sudo chown -R nobody /tftpboot Make sure the server is configured to look at the port that you are using. Edit /etc/default/isc-dhcp-server and add the appropriate port (ex. usb0 or eth1) to the INTERFACES option. The example below includes eth0, eth1, and usb0. - .. code:: + .. code-block:: text INTERFACES="eth0 eth1 usb0" @@ -148,7 +147,8 @@ USB there are some additional steps required. Check the interfaces in your PC by using `ip addr` and find the appropriate interface and its IP address. #. Restart the services to pick-up the configuration changes -.. code:: + + .. code-block:: console sudo service isc-dhcp-server restart sudo service atftpd restart @@ -191,13 +191,13 @@ USB there are some additional steps required. - As root, create /etc/NetworkManager/dispatcher.d/99am-usb-dhcp-server - .. code:: + .. code-block:: sh #!/bin/sh   IF=$1 STATUS=$2 -   + if [ "$IF" = "usb0" ] && [ "$STATUS" = "up" ]; then service isc-dhcp-server restart fi @@ -229,7 +229,7 @@ USB there are some additional steps required. A) Configure /etc/network/interfaces by adding the below structure for usb0: - .. code:: + .. code-block:: text allow-hotplug usb0 iface usb0 inet static @@ -245,10 +245,10 @@ USB there are some additional steps required. /etc/network/interfaces). This script restarts the DHCP/BOOTP server automatically. - .. code:: + .. code-block:: sh #!/bin/sh -   + if [ "$IFACE" = usb0 ]; then sudo service isc-dhcp-server restart fi @@ -263,11 +263,11 @@ USB there are some additional steps required. managed by /etc/network/interfaces by adding the below code to /etc/NetworkManager/NetworkManager.conf: - .. code:: + .. code-block:: ini [main] plugins=ifupdown -   + [ifupdown] managed=false 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..d913bfe0e 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 @@ -181,12 +181,14 @@ You can also check which PRU-ICSS an ethernet interface belongs to via command line, e.g. eth2 on different platforms: AM571x: + :: root@am57xx-evm:~# ls -l /sys/class/net/eth2 | grep device lrwxrwxrwx 1 root root 0 Jun 10 11:29 device -> ../../../pruss1_eth AM572x: + :: root@am57xx-evm:~# ls -l /sys/class/net/eth2 | grep device diff --git a/source/linux/Industrial_Protocols/PTP/_PTP.rst b/source/linux/Industrial_Protocols/PTP/_PTP.rst index e2d40dc94..4f689b631 100644 --- a/source/linux/Industrial_Protocols/PTP/_PTP.rst +++ b/source/linux/Industrial_Protocols/PTP/_PTP.rst @@ -203,6 +203,7 @@ boot using the PPS device tree file. the relevant boot command (e.g. 'bootcmd', mmcboot' or 'netboot') 2. Set the device tree file to be used. + :: setenv fdtfile @@ -432,6 +433,7 @@ configuration file: (where eth2/eth3 are the slave interfaces used for the HSR/PRP interface) HSR: + :: [global] @@ -488,6 +490,7 @@ HSR: fault_reset_interval 0 PRP: + :: [global] @@ -552,6 +555,7 @@ configured using a configuration file similar to the one below: (Note: only supported on PRU-ICSS ports using DualEMAC, and supports slave side only) Telecom: + :: # Telecom Profile (G.8275.x) PTP Config File @@ -1363,6 +1367,7 @@ Refer to the sample linuxptp BC configuration files bc.cfg, bc_hsr.cfg and bc_pr as described below: bc.cfg: BC with GMAC and four ICSS ports + :: [global] @@ -1422,6 +1427,7 @@ bc.cfg: BC with GMAC and four ICSS ports fault_reset_interval 0 bc_prp.cfg: BC with GMAC and two PRP ports: + :: [global] @@ -1509,6 +1515,7 @@ bc_prp.cfg: BC with GMAC and two PRP ports: bc_hsr.cfg: BC with GMAC and two HSR ports: + :: [global] @@ -1840,7 +1847,7 @@ Procedure ~~~~~~~~~ The script file -`setup\_hsr.sh `_ +`setup\_hsr.sh `__ and clock configuration files e.g. dut_1_hsr_oc.cfg, dut_2_hsr_oc.cfg, dut_3_hsr_oc.cfg (each identical, same as listed in `PTP Redundancy `__ @@ -1869,7 +1876,7 @@ section for HSR) will be used in the setup of the tests. - Boot IDK into kernel prompt. -- Modify the top fields in `setup\_hsr.sh `_ +- Modify the top fields in `setup\_hsr.sh `__ to reflect the HSR slave ports' MAC addresses and IP address of the DUT's HSR interface. The **ETHA** or **ETHB** fields may also need to be modified if an ICSS diff --git a/source/linux/Industrial_Protocols/_SORTE.rst b/source/linux/Industrial_Protocols/_SORTE.rst index 5db14a1e2..f0b9bfb6f 100644 --- a/source/linux/Industrial_Protocols/_SORTE.rst +++ b/source/linux/Industrial_Protocols/_SORTE.rst @@ -147,6 +147,7 @@ print will be displayed on console: :name: sorte-sample-log-from-am572x-idk **Master** + :: root@am57xx-evm:~# pruss_app_sorte_master_am572x.out @@ -156,6 +157,7 @@ print will be displayed on console: sorte master: 2 SLAVE devices connected **Slave** + :: root@am57xx-evm:~# pruss_app_sorte_slave_am572x.out diff --git a/source/linux/Industrial_Protocols_HSR_PRP.rst b/source/linux/Industrial_Protocols_HSR_PRP.rst index 40af5996a..274860a8b 100644 --- a/source/linux/Industrial_Protocols_HSR_PRP.rst +++ b/source/linux/Industrial_Protocols_HSR_PRP.rst @@ -18,6 +18,7 @@ and PRU-ICSS ports are eth1/eth2): (This acts as a 2 node ring for HSR, or a 2 node point-to-point for PRP) 2 ) Configure ports to have the same MAC address + :: ifconfig eth1 0.0.0.0 down && ifconfig eth2 0.0.0.0 down @@ -26,6 +27,7 @@ and PRU-ICSS ports are eth1/eth2): 3 ) Configure offload feature, and create HSR/PRP interface (for HSR) + :: ethtool -K eth1 hsr-rx-offload on && ethtool -K eth2 hsr-rx-offload on @@ -34,6 +36,7 @@ and PRU-ICSS ports are eth1/eth2): ifconfig hsr0 192.168.2.20 (for PRP) + :: ethtool -K eth1 prp-rx-offload on && ethtool -K eth2 prp-rx-offload on diff --git a/source/system/Demo_User_Guides/Chromium_Browser.rst b/source/system/Demo_User_Guides/Chromium_Browser.rst index b5f9475d6..3dae92433 100644 --- a/source/system/Demo_User_Guides/Chromium_Browser.rst +++ b/source/system/Demo_User_Guides/Chromium_Browser.rst @@ -70,7 +70,7 @@ Graphics Feature Status To see the GPU features that are in use, enter :code:`chrome://gpu` into the Chromium URL/Navigation bar. A web page will be rendered with this information. The below example shows what is enabled/disabled when GPU acceleration is working correctly -.. code-block:: +.. code-block:: text * Canvas: Hardware accelerated * Canvas out-of-process rasterization: Disabled @@ -119,7 +119,7 @@ Pull in the meta-browser and meta-clang layer into a Scarthgap Yocto build. meta-browser should be pinned to commit: -.. code-block:: +.. code-block:: text commit 1ed2254d72a4c25879014c98be287a7e3e22904c Author: Max Ihlenfeldt @@ -129,7 +129,7 @@ meta-browser should be pinned to commit: meta-clang needs to be pinned to HEAD commit of branch "scarthgap", as of the time of writing that equates to this commit: -.. code-block:: +.. code-block:: text commit e7dceb1c92caf7f21ef1d7b49c85328c30cffd90 (HEAD -> scarthgap, origin/scarthgap) Author: Etienne Cordonnier @@ -176,7 +176,7 @@ Where is defined in the :ref:`Build Options section of "Building the S into by default. If you want to build it into another image, then you would need to modify the .bb recipe for the image. Or alternatively add the line: -.. code-block:: console +.. code-block:: text IMAGE_INSTALL:append = " chromium-ozone-wayland" diff --git a/source/system/Demo_User_Guides/Servo_Drive_Demo_User_Guide.rst b/source/system/Demo_User_Guides/Servo_Drive_Demo_User_Guide.rst index 1c9f4aa55..6be42061d 100644 --- a/source/system/Demo_User_Guides/Servo_Drive_Demo_User_Guide.rst +++ b/source/system/Demo_User_Guides/Servo_Drive_Demo_User_Guide.rst @@ -24,13 +24,13 @@ Hardware Prerequisites - TI AM64x GP EVM and power supply - - TI FSI serial interface (FSI) adapter board: `TMDSFSIADAPEVM `_ + - TI FSI serial interface (FSI) adapter board: `TMDSFSIADAPEVM `__ - 3x Seconary Nodes, for each Seconary Node: - TI F280049 Launchpad: `LAUNCHXL-F280049C `_ - - TI FSI serial interface (FSI) adapter board: `TMDSFSIADAPEVM `_ + - TI FSI serial interface (FSI) adapter board: `TMDSFSIADAPEVM `__ - TI GaNFET BoosterPack: `BOOSTXL-3PHGANINV `_