From b20aca085f9b987119fc5bc98e246488f4e66d00 Mon Sep 17 00:00:00 2001 From: Randolph Sapp Date: Thu, 23 Jul 2026 14:22:52 -0500 Subject: [PATCH 1/2] refactor: use ascii double quotation mark We need to limit the use of Unicode characters because it can negatively effect any other document generation stages. Signed-off-by: Randolph Sapp --- .../PRU-Getting-Started-Labs_Lab3.rst | 4 +- .../PRU-Getting-Started-Labs_Lab5.rst | 2 +- source/common/PRU-ICSS/PRU-Hands-on-Labs.rst | 4 +- .../linux/Release_Specific_Release_Notes.rst | 2 +- .../linux/Release_Specific_Release_Notes.rst | 2 +- .../linux/Release_Specific_Release_Notes.rst | 2 +- .../Application_Notes_dtbo_support.rst | 2 +- .../linux/Release_Specific_Release_Notes.rst | 2 +- .../linux/Release_Specific_Release_Notes.rst | 2 +- .../linux/Release_Specific_Release_Notes.rst | 2 +- .../IPC/_IPC_for_K2x.rst | 6 +-- .../Kernel/Kernel_Drivers/Network/NetCP.rst | 44 +++++++++---------- .../Kernel/Kernel_Drivers/PWM.rst | 2 +- .../Kernel/Kernel_Drivers/VPE.rst | 2 +- .../pm_low_power_modes_socoff.rst | 2 +- .../Tools/Flash_Tools/_Sitara_Uniflash.rst | 12 ++--- .../linux/Foundational_Components/_CMEM.rst | 2 +- ...oundational_Components_Migration_Guide.rst | 4 +- ...nal_Components_Multimedia_D5520_VXE384.rst | 6 +-- ...riables_stored_in_SPI_Flash_from_Linux.rst | 2 +- source/linux/Industrial_Protocols/_CCLINK.rst | 6 +-- ...cessor_SDK_Linux_Getting_Started_Guide.rst | 10 ++--- 22 files changed, 61 insertions(+), 61 deletions(-) diff --git a/source/common/PRU-ICSS/PRU-Getting-Started-Labs_Lab3.rst b/source/common/PRU-ICSS/PRU-Getting-Started-Labs_Lab3.rst index c22563726..171900971 100644 --- a/source/common/PRU-ICSS/PRU-Getting-Started-Labs_Lab3.rst +++ b/source/common/PRU-ICSS/PRU-Getting-Started-Labs_Lab3.rst @@ -106,7 +106,7 @@ Compiling From Linux #. Navigate to the PRU project directory. -#. Run “make” from the terminal. +#. Run "make" from the terminal. * If the PRU_CGT (PRU code generation tools) environment variable was not set, there will be an error. @@ -126,7 +126,7 @@ Compiling From Linux * The generated project files will be available in a folder named **gen** in the project directory - * Previously generated files can be removed with “make clean” + * Previously generated files can be removed with "make clean" .. _pru_getting_started_labs_linux_compiler_settings: diff --git a/source/common/PRU-ICSS/PRU-Getting-Started-Labs_Lab5.rst b/source/common/PRU-ICSS/PRU-Getting-Started-Labs_Lab5.rst index 66cbd6a70..99880e852 100644 --- a/source/common/PRU-ICSS/PRU-Getting-Started-Labs_Lab5.rst +++ b/source/common/PRU-ICSS/PRU-Getting-Started-Labs_Lab5.rst @@ -90,7 +90,7 @@ into the PRU. #. If you clicked on any of the buttons in the previous step, click on "Restart" to get back to the program entry point. -#. Use the “Step Over” or “Step Into” buttons to step through the PRU function +#. Use the "Step Over" or "Step Into" buttons to step through the PRU function to the beginning of the while loop. diff --git a/source/common/PRU-ICSS/PRU-Hands-on-Labs.rst b/source/common/PRU-ICSS/PRU-Hands-on-Labs.rst index 6386a042a..9ba4da5ae 100644 --- a/source/common/PRU-ICSS/PRU-Hands-on-Labs.rst +++ b/source/common/PRU-ICSS/PRU-Hands-on-Labs.rst @@ -579,8 +579,8 @@ Design & Build the PRU Firmware c. Select **PRU tab**, specify a new **Project Name** (e.g., temp_monitor_slave_0 & temp_monitor_master_1), verify that - Compiler version is **TI v2.1.0**, and select “Empty Project.” Note: If - “Empty Project (with main.c)” is selected, you will need to delete + Compiler version is **TI v2.1.0**, and select "Empty Project." Note: If + "Empty Project (with main.c)" is selected, you will need to delete **main.c** in the project directory (added by default). d. Select **Finish**. diff --git a/source/devices/AM62AX/linux/Release_Specific_Release_Notes.rst b/source/devices/AM62AX/linux/Release_Specific_Release_Notes.rst index a68ff943f..f216f1dc2 100644 --- a/source/devices/AM62AX/linux/Release_Specific_Release_Notes.rst +++ b/source/devices/AM62AX/linux/Release_Specific_Release_Notes.rst @@ -14,7 +14,7 @@ Developing a scalable platform solutions has never been easier than with the Pro solutions. To simplify the end user experience, Processor SDK Linux AM62A installer provides everything needed as discussed below -to create the embedded system from “scratch” : +to create the embedded system from "scratch" : - Platform/board-support software and configuration files for Linux - U-Boot and Kernel sources and configuration files diff --git a/source/devices/AM62DX/linux/Release_Specific_Release_Notes.rst b/source/devices/AM62DX/linux/Release_Specific_Release_Notes.rst index 055379aef..0ddfcf542 100644 --- a/source/devices/AM62DX/linux/Release_Specific_Release_Notes.rst +++ b/source/devices/AM62DX/linux/Release_Specific_Release_Notes.rst @@ -14,7 +14,7 @@ Developing a scalable platform solutions has never been easier than with the Pro solutions. To simplify the end user experience, Processor SDK Linux AM62Dx installer provides everything needed as discussed below -to create the embedded system from “scratch” : +to create the embedded system from "scratch" : - Platform/board-support software and configuration files for Linux - U-Boot and Kernel sources and configuration files diff --git a/source/devices/AM62LX/linux/Release_Specific_Release_Notes.rst b/source/devices/AM62LX/linux/Release_Specific_Release_Notes.rst index d80efec34..32ca1c9b7 100644 --- a/source/devices/AM62LX/linux/Release_Specific_Release_Notes.rst +++ b/source/devices/AM62LX/linux/Release_Specific_Release_Notes.rst @@ -14,7 +14,7 @@ Developing a scalable platform solutions has never been easier than with the Pro solutions. To simplify the user experience, Processor SDK Linux AM62L installer provides everything needed as discussed below -to create the embedded system from “scratch” : +to create the embedded system from "scratch" : - Platform/board-support software and configuration files for Linux - U-Boot and Kernel sources and configuration files diff --git a/source/devices/AM62PX/android/Application_Notes_dtbo_support.rst b/source/devices/AM62PX/android/Application_Notes_dtbo_support.rst index 0cdd4933a..29b0accb3 100644 --- a/source/devices/AM62PX/android/Application_Notes_dtbo_support.rst +++ b/source/devices/AM62PX/android/Application_Notes_dtbo_support.rst @@ -43,7 +43,7 @@ The following Device-Tree Overlays are supported: * - 9 - 4x MCAN interfaces (requires external CAN transceivers) * - 10 - - Microtips Technology USA 10.1” WUXGA (1920x1200) OLDI panel + - Microtips Technology USA 10.1" WUXGA (1920x1200) OLDI panel * - 12 - M.2-CC3351 WiFi board on the M.2 connector * - 14 diff --git a/source/devices/AM62PX/linux/Release_Specific_Release_Notes.rst b/source/devices/AM62PX/linux/Release_Specific_Release_Notes.rst index db4938ae1..9e3d08749 100644 --- a/source/devices/AM62PX/linux/Release_Specific_Release_Notes.rst +++ b/source/devices/AM62PX/linux/Release_Specific_Release_Notes.rst @@ -14,7 +14,7 @@ Developing a scalable platform solutions has never been easier than with the Pro solutions. To simplify the user experience, Processor SDK Linux AM62Px installer provides everything needed as discussed below -to create the embedded system from “scratch” : +to create the embedded system from "scratch" : - Platform/board-support software and configuration files for Linux - U-Boot and Kernel sources and configuration files diff --git a/source/devices/AM62X/linux/Release_Specific_Release_Notes.rst b/source/devices/AM62X/linux/Release_Specific_Release_Notes.rst index 840d0a9eb..ca51a2b5d 100644 --- a/source/devices/AM62X/linux/Release_Specific_Release_Notes.rst +++ b/source/devices/AM62X/linux/Release_Specific_Release_Notes.rst @@ -14,7 +14,7 @@ Developing a scalable platform solutions has never been easier than with the Pro solutions. To simplify the end user experience, Processor SDK Linux AM62x installer provides everything needed as discussed below -to create the embedded system from “scratch” : +to create the embedded system from "scratch" : - Platform/board-support software and configuration files for Linux - U-Boot and Kernel sources and configuration files diff --git a/source/devices/AM64X/linux/Release_Specific_Release_Notes.rst b/source/devices/AM64X/linux/Release_Specific_Release_Notes.rst index 9a67b20de..3dd1b18ef 100644 --- a/source/devices/AM64X/linux/Release_Specific_Release_Notes.rst +++ b/source/devices/AM64X/linux/Release_Specific_Release_Notes.rst @@ -14,7 +14,7 @@ Developing a scalable platform solutions has never been easier than with the Pro solutions. To simplify the end user experience, Processor SDK Linux AM64x installer provides everything needed as discussed below -to create the embedded system from “scratch” : +to create the embedded system from "scratch" : - Platform/board-support software and configuration files for Linux - U-Boot and Kernel sources and configuration files diff --git a/source/linux/Foundational_Components/IPC/_IPC_for_K2x.rst b/source/linux/Foundational_Components/IPC/_IPC_for_K2x.rst index c641d4a33..c18344e4d 100644 --- a/source/linux/Foundational_Components/IPC/_IPC_for_K2x.rst +++ b/source/linux/Foundational_Components/IPC/_IPC_for_K2x.rst @@ -397,7 +397,7 @@ The carveouts for the DSP are defined in the Linux dts file. For the K2G EVM, th The memory region "dsp_common_mpm_memory" starts at address 0x9d000000 and has a size of 0x2800000 bytes. This region is where the DSP code/data needs to reside. If they are not in this region, you will see the error "load failed (error: -104)" when trying to load. -The memory region "dsp_common_memory” starts at address 0x9f800000 and has a size of 0x800000. This is a CMA pool, as indicated by the line “compatible = "shared-dma-pool";”, and is reserved for +The memory region "dsp_common_memory" starts at address 0x9f800000 and has a size of 0x800000. This is a CMA pool, as indicated by the line "compatible = "shared-dma-pool";", and is reserved for Virtque region and Rpmsg vring buffers. As of Processor SDK 5.2, the Virtque and vring buffers are allocated by the remoteproc driver from this region and communicated to the slave by update to the resource table. @@ -413,7 +413,7 @@ The resource table contains the definitions of the CMA carveout for the Rpmsg vr MPM Config File --------------- -The MPM configuration file is a JSON format configuration file and is located in the default root file system release as part of Processor SDK Linux. It is labeled “mpm_config.json” and is located in /etc/mpm. +The MPM configuration file is a JSON format configuration file and is located in the default root file system release as part of Processor SDK Linux. It is labeled "mpm_config.json" and is located in /etc/mpm. The following are some details regarding the MPM configuration file: @@ -493,7 +493,7 @@ and add the following: stackMemory: "EXT_DDR", }; -This will place the DSP code, data, and stack memory at address 0x9d000000. We have chosen address 0x9d000000 because that is what is defined in the Linux device tree by default. Refer to the “dsp_common_mpm_memory” block in the previous section “Linux Device Tree.” Note, the length specified here is 0x00100000; this must be less than the size of the dsp_common_mpm_memory pool. +This will place the DSP code, data, and stack memory at address 0x9d000000. We have chosen address 0x9d000000 because that is what is defined in the Linux device tree by default. Refer to the "dsp_common_mpm_memory" block in the previous section "Linux Device Tree." Note, the length specified here is 0x00100000; this must be less than the size of the dsp_common_mpm_memory pool. **Changes to the MPM Config File** 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 2db70361f..2de38874d 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Network/NetCP.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Network/NetCP.rst @@ -2117,9 +2117,9 @@ To enable CPSW: :: //enable unknown unicast flood to host, disable bypass, enable VID=0 processing - echo “port0_unicast_flood=1” > /sys/class/net/eth0/device/ale_control - echo “bypass=0” > /sys/class/net/eth0/device/ale_control - echo “no_port_vlan=1” > /sys/class/net/eth0/device/ale_control + echo "port0_unicast_flood=1" > /sys/class/net/eth0/device/ale_control + echo "bypass=0" > /sys/class/net/eth0/device/ale_control + echo "no_port_vlan=1" > /sys/class/net/eth0/device/ale_control To disable CPSW: @@ -2127,41 +2127,41 @@ To disable CPSW: // disable port 0 flood for unknown unicast; //enable bypass mode - echo “p0_uni_flood_en=0” > /sys/class/net/eth0/device/ale_control - echo “bypass=1” > /sys/class/net/eth0/device/ale_control + echo "p0_uni_flood_en=0" > /sys/class/net/eth0/device/ale_control + echo "bypass=1" > /sys/class/net/eth0/device/ale_control To set port 1 state to forwarding: :: - echo “port_state.1=3” > /sys/class/net/eth0/device/ale_control + echo "port_state.1=3" > /sys/class/net/eth0/device/ale_control To set CPSW to VLAN aware mode: :: - echo “vlan_aware=1” > /sys/class/net/eth0/device/gbe_sw/control - echo “vlan_aware=1” > /sys/class/net/eth0/device/ale_control + echo "vlan_aware=1" > /sys/class/net/eth0/device/gbe_sw/control + echo "vlan_aware=1" > /sys/class/net/eth0/device/ale_control (set these to 0 to disable vlan aware mode) To set port 1’s Ingress VLAN defaults: :: - echo “port_vlan_id=5” > /sys/class/net/eth0/device/gbe_sw/port_vlan/1 - echo “port_cfi=0” > /sys/class/net/eth0/device/gbe_sw/port_vlan/1 - echo “port_vlan_pri=0” > /sys/class/net/eth0/device/gbe_sw/port_vlan/1 + echo "port_vlan_id=5" > /sys/class/net/eth0/device/gbe_sw/port_vlan/1 + echo "port_cfi=0" > /sys/class/net/eth0/device/gbe_sw/port_vlan/1 + echo "port_vlan_pri=0" > /sys/class/net/eth0/device/gbe_sw/port_vlan/1 To set port 1 to use the above default vlan id on ingress: :: - echo “p1_pass_pri_tagged=0” > /sys/class/net/eth0/device/gbe_sw/control + echo "p1_pass_pri_tagged=0" > /sys/class/net/eth0/device/gbe_sw/control To set port 1’s Egress VLAN defaults: - For registered VLANs, the egress policy is set in the - “force\_untag\_egress field” of the ALE entry for that VLAN. This + "force\_untag\_egress field" of the ALE entry for that VLAN. This field is a bit map with one bit per port. Port 0 is the host port. For example, to set VLAN #100 to force untagged @@ -2178,31 +2178,31 @@ egress on port 2 only: :: - echo “unknown_force_untag_egress=7” > /sys/class/net/eth0/device/ale_control + 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 + 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" : :: - echo “drop_untagged.1=0” > /sys/class/net/eth0/device/ale_control + echo "drop_untagged.1=0" > /sys/class/net/eth0/device/ale_control -To set to Port 1 to “Admit unknown VLAN”: +To set to Port 1 to "Admit unknown VLAN": :: - echo “drop_unknown.1=0” > /sys/class/net/eth0/device/ale_control + echo "drop_unknown.1=0" > /sys/class/net/eth0/device/ale_control -To set to Port 1 to “Drop unknown VLAN”: +To set to Port 1 to "Drop unknown VLAN": :: - echo “drop_unknown.1=1” > /sys/class/net/eth0/device/ale_control + echo "drop_unknown.1=1" > /sys/class/net/eth0/device/ale_control .. rubric:: Sample Displays :name: sample-displays diff --git a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/PWM.rst b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/PWM.rst index ea1bb48c8..9db820404 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/PWM.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/PWM.rst @@ -78,7 +78,7 @@ When a PWM channel is exported a pwmX directory will be created in the pwmchipN - **polarity** - Changes the polarity of the PWM signal. The value written is the string “normal” or “inversed”. + Changes the polarity of the PWM signal. The value written is the string "normal" or "inversed". - **enable** diff --git a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/VPE.rst b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/VPE.rst index eb40f62d9..669ffc587 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/VPE.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/VPE.rst @@ -354,6 +354,6 @@ likely omapdrm) instead of allocating by itself via the videobuf2 layer. .. rubric:: Debugging :name: debugging-vpe -Debug log can be enabled in the VPE driver by adding “#define DEBUG” at +Debug log can be enabled in the VPE driver by adding "#define DEBUG" at the first line of drivers/media/platform/ti-vpe/vpe.c. diff --git a/source/linux/Foundational_Components/Power_Management/pm_low_power_modes_socoff.rst b/source/linux/Foundational_Components/Power_Management/pm_low_power_modes_socoff.rst index 9a8b3153a..f624b16b9 100644 --- a/source/linux/Foundational_Components/Power_Management/pm_low_power_modes_socoff.rst +++ b/source/linux/Foundational_Components/Power_Management/pm_low_power_modes_socoff.rst @@ -80,7 +80,7 @@ TI’s K3 Jacinto family of SoCs have a concept of boardcfg that can be used to By default, SOC_OFF mode enabled by default in SDK. IO_ONLY_PLUS_DDR mode can be enabled by changing boardcfg in u-boot at build time. -The low power mode is set statically at build time in “lpm_cfg” section of the power management board config. +The low power mode is set statically at build time in "lpm_cfg" section of the power management board config. In the u-boot source tree the boardcfg is present at: .. ifconfig:: CONFIG_part_variant in ('J7200') diff --git a/source/linux/Foundational_Components/Tools/Flash_Tools/_Sitara_Uniflash.rst b/source/linux/Foundational_Components/Tools/Flash_Tools/_Sitara_Uniflash.rst index b035c9975..935b6c5b1 100644 --- a/source/linux/Foundational_Components/Tools/Flash_Tools/_Sitara_Uniflash.rst +++ b/source/linux/Foundational_Components/Tools/Flash_Tools/_Sitara_Uniflash.rst @@ -373,7 +373,7 @@ problems are encountered. .. image:: /images/Device_manager.png -#. Find the **AM43xx1.2** Device listed in “Other Devices” per below. It +#. Find the **AM43xx1.2** Device listed in "Other Devices" per below. It will have a little yellow exclamation point on it indicating there is currently a problem with the device. **Right click** on it and select **Update Driver Software…**. @@ -430,10 +430,10 @@ problems are encountered. .. Image:: /images/Internet_connection_2.png - **Note: The number next to the “Local Area Connection” will depend on + **Note: The number next to the "Local Area Connection" will depend on the number of network connections the computer has. If this is the only network connection (i.e. the computer does not have an Ethernet - or wireless networking connection), then this would be “1”. In most + or wireless networking connection), then this would be "1". In most cases, computers have either a wired or wireless connection that will take up spot #1. Therefore, the new USB RNDIS Network Connection will be #2. However, if the computer has multiple connections already, @@ -513,10 +513,10 @@ problems are encountered. .. Image:: /images/Local_area_connection_3.png - **Note: The number next to the “Local Area Connection” will depend on + **Note: The number next to the "Local Area Connection" will depend on the number of network connections the computer has. If this is the only network connection (i.e. the computer does not have an Ethernet - or wireless networking connection), then this would be “1”. In most + or wireless networking connection), then this would be "1". In most cases, computers have either a wired or wireless connection that will take up spot #1. Therefore, the new USB RNDIS Network Connection will be #3. However, if the computer has multiple connections already, @@ -545,7 +545,7 @@ problems are encountered. to use another address, you will need to change those configurations as well.** -#. Click “No” if asked to remove other static configurations. Since we +#. Click "No" if asked to remove other static configurations. Since we are using the same IP address for both RNDIS connections, Windows is trying to let us know that this is generally not a good idea. However, in this situation, the configuration ensures that both diff --git a/source/linux/Foundational_Components/_CMEM.rst b/source/linux/Foundational_Components/_CMEM.rst index 88e7f9142..b7cd32f4c 100644 --- a/source/linux/Foundational_Components/_CMEM.rst +++ b/source/linux/Foundational_Components/_CMEM.rst @@ -611,7 +611,7 @@ the kernel. **Q:** Why CMEM failed in physical address > 32bits? **A:** The user space application need to be compiled with -“–D\_FILE\_OFFSET\_BITS=64" to allow physical addresses > 32 bits. +"–D\_FILE\_OFFSET\_BITS=64" to allow physical addresses > 32 bits. | .. rubric:: Licensing diff --git a/source/linux/Foundational_Components_Migration_Guide.rst b/source/linux/Foundational_Components_Migration_Guide.rst index 185feb9ad..9b080d2ed 100644 --- a/source/linux/Foundational_Components_Migration_Guide.rst +++ b/source/linux/Foundational_Components_Migration_Guide.rst @@ -44,8 +44,8 @@ Device types | | do not force authentication for booting, however DMSC is locked. | +-------+-----------------------------------------------------------------------+ | HS-SE | High Security - Security Enforced: This is a SoC/board state after a | -| | customer has successfully blown the keys and set “customer Keys | -| | enable”. In HS-SE device all security features enabled. All secrets | +| | customer has successfully blown the keys and set "customer Keys | +| | enable". In HS-SE device all security features enabled. All secrets | | | within the device are fully protected and all of the security goals | | | are fully enforced. The device also enforces secure booting. | +-------+-----------------------------------------------------------------------+ diff --git a/source/linux/Foundational_Components_Multimedia_D5520_VXE384.rst b/source/linux/Foundational_Components_Multimedia_D5520_VXE384.rst index d9950df0c..75f642100 100644 --- a/source/linux/Foundational_Components_Multimedia_D5520_VXE384.rst +++ b/source/linux/Foundational_Components_Multimedia_D5520_VXE384.rst @@ -518,7 +518,7 @@ result in the driver communicating to the firmware that only 1 reference frame s .. code-block:: text Use 1 Reference Frame for Decode - target # gst-launch-1.0 filesrc location= ! h264parse ! v4l2h264dec extra-controls=”s,max_dec_frame_buffering=1” ! waylandsink + target # gst-launch-1.0 filesrc location= ! h264parse ! v4l2h264dec extra-controls="s,max_dec_frame_buffering=1" ! waylandsink .. note:: This might decrease the display latency if the stream does not depend on more than a single reference frame, @@ -557,13 +557,13 @@ The following pipelines highlight how these controls can be used to control memo Remove additional buffers allocated due to cores present on DECODER target # gst-launch-1.0 filesrc location= ! h264parse ! v4l2h264dec - extra-controls=”s,max_dec_frame_buffering=0,display_pipeline_size=2,img_extra_decode_buffers=0” ! waylandsink + extra-controls="s,max_dec_frame_buffering=0,display_pipeline_size=2,img_extra_decode_buffers=0" ! waylandsink .. code-block:: text Hardcode number of reference frames used target # gst-launch-1.0 filesrc location= ! h264parse ! v4l2h264dec - extra-controls=”s,max_dec_frame_buffering=0,display_pipeline_size=2,img_extra_decode_buffers=0, override_spec_dpb_buffers=2” ! kmssink + extra-controls="s,max_dec_frame_buffering=0,display_pipeline_size=2,img_extra_decode_buffers=0, override_spec_dpb_buffers=2" ! kmssink .. note:: Keep in mind that while this allows for complete control, it is important to understand that changing these values can negatively impact decode diff --git a/source/linux/How_to_Guides/Target/Update_U-Boot_Environment_Variables_stored_in_SPI_Flash_from_Linux.rst b/source/linux/How_to_Guides/Target/Update_U-Boot_Environment_Variables_stored_in_SPI_Flash_from_Linux.rst index 2ccef7f10..87c7671c9 100644 --- a/source/linux/How_to_Guides/Target/Update_U-Boot_Environment_Variables_stored_in_SPI_Flash_from_Linux.rst +++ b/source/linux/How_to_Guides/Target/Update_U-Boot_Environment_Variables_stored_in_SPI_Flash_from_Linux.rst @@ -46,7 +46,7 @@ Please note that all paths are refereneced to the u-boot source within the AMSDK, ti-sdk-am335x-/board-support/u-boot..... Prior to building the The flag in -board-support/u-boot/tools/envfw\_env.h “HAVE\_REDUND” must be +board-support/u-boot/tools/envfw\_env.h "HAVE\_REDUND" must be undefined as only a single env partition has been defined in the AMSDK SPI MTD partitioning. diff --git a/source/linux/Industrial_Protocols/_CCLINK.rst b/source/linux/Industrial_Protocols/_CCLINK.rst index aaa82cbb0..9c4fc210c 100644 --- a/source/linux/Industrial_Protocols/_CCLINK.rst +++ b/source/linux/Industrial_Protocols/_CCLINK.rst @@ -149,8 +149,8 @@ Before running the master sample application, first obtain the IP address of the slave Ethernet port to be tested. Then, modify /usr/share/cclink/MasterParameter.csv to update "Slave1 IP address" using the IP address of the Slave station. After that, run the master -sample application: “Master\_sample -/usr/share/cclink/MasterParameter.csv” +sample application: "Master\_sample +/usr/share/cclink/MasterParameter.csv" The figure below shows the sample output from the console of the master station. @@ -163,7 +163,7 @@ station. :name: slave-sample-application On the slave station, simply run the slave sample application: -“Slave\_sample /usr/share/cclink/SlaveParameter.csv” +"Slave\_sample /usr/share/cclink/SlaveParameter.csv" The figure below shows the sample output from the console of the slave station. diff --git a/source/linux/Overview/Processor_SDK_Linux_Getting_Started_Guide.rst b/source/linux/Overview/Processor_SDK_Linux_Getting_Started_Guide.rst index 5fbcd9855..4a82e5d73 100644 --- a/source/linux/Overview/Processor_SDK_Linux_Getting_Started_Guide.rst +++ b/source/linux/Overview/Processor_SDK_Linux_Getting_Started_Guide.rst @@ -20,7 +20,7 @@ pieces work together. We package all of this together with a working Linux Embedded System that has been built with all of the things mentioned above. -What it really serves as is a “known good” starting point. One of the +What it really serves as is a "known good" starting point. One of the big challenges with starting development on a new platform (not to mention, a new Operating System (OS) for many), is getting an environment set up where you can build and debug code on hardware. The @@ -58,11 +58,11 @@ pieces to simplify things a bit: .. ifconfig:: CONFIG_sdk in ('SITARA') It can also be used on one of the very popular Beaglebones (either the original - “white” or the newer “black”). For K2H/K2K, K2E, and K2L platforms + "white" or the newer "black"). For K2H/K2K, K2E, and K2L platforms which are not using SD cards, U-Boot is loaded to NOR, Linux kernel is fetched from TFTP server, and filesystem is on NFS. -- Everything needed to create the above embedded system from “scratch”: +- Everything needed to create the above embedded system from "scratch": - U-Boot sources and configuration files - Kernel sources and configuration files @@ -104,7 +104,7 @@ with new device drivers and applications. .. note:: For K2H/K2K, K2E, and K2L platforms which are not using SD cards, please - also go ahead and skip down to the “I want to Develop!” (or, `Developing + also go ahead and skip down to the "I want to Develop!" (or, `Developing with the Linux SDK `__ section. So, if you’re not quite there yet, let’s discuss some other options. @@ -194,7 +194,7 @@ which you can start development. Can you use other versions of Ubuntu or even other distributions? Theoretically, yes, as long as you can get it to work and there may - be more “assembly” required. If you can use the Ubuntu version + be more "assembly" required. If you can use the Ubuntu version validated against the SDK, it will be the smoothest path and we will be able to help you more if you do run into trouble. From bfaef7493dcd5fc9b4e0dc9ec54f449f2f419fa1 Mon Sep 17 00:00:00 2001 From: Randolph Sapp Date: Thu, 23 Jul 2026 14:28:02 -0500 Subject: [PATCH 2/2] refactor: use ascii single quotation mark We need to limit the use of Unicode characters because it can negatively effect any other document generation stages. Signed-off-by: Randolph Sapp --- ..._SDK_Android_Software_Developers_Guide.rst | 4 +- source/buildroot/Overview.rst | 2 +- .../How_to_Guides/EVMK2H_Hardware_Setup.rst | 12 ++--- .../ICE_AM335x_Hardware_Setup.rst | 2 +- .../TMDXIDK5728_Hardware_Setup.rst | 2 +- .../_Processor_SDK_Technical_Support.rst | 2 +- source/common/PRU-ICSS/PRU-Hands-on-Labs.rst | 8 ++-- .../AM62AX/linux/Linux_Performance_Guide.rst | 2 +- source/devices/AM62AX/linux/Overview.rst | 4 +- .../linux/Release_Specific_Release_Notes.rst | 6 +-- .../AM62DX/linux/Linux_Performance_Guide.rst | 2 +- .../linux/Release_Specific_Release_Notes.rst | 6 +-- .../AM62LX/linux/Linux_Performance_Guide.rst | 2 +- source/devices/AM62LX/linux/Overview.rst | 4 +- .../linux/Release_Specific_Release_Notes.rst | 6 +-- .../AM62PX/linux/Linux_Performance_Guide.rst | 2 +- source/devices/AM62PX/linux/Overview.rst | 4 +- .../linux/Release_Specific_Release_Notes.rst | 6 +-- .../AM62X/linux/Linux_Performance_Guide.rst | 2 +- source/devices/AM62X/linux/Overview.rst | 4 +- .../linux/Release_Specific_Release_Notes.rst | 6 +-- source/devices/AM64X/linux/Overview.rst | 4 +- .../linux/Release_Specific_Release_Notes.rst | 6 +-- .../linux/RT_Linux_Performance_Guide.rst | 2 +- .../linux/Release_Specific_Release_Notes.rst | 2 +- ...ease_Specific_Kernel_Performance_Guide.rst | 2 +- source/edgeai/sdk_overview.rst | 2 +- .../Application_Demos/Video_Graphics_Test.rst | 2 +- .../IPC/_IPC_for_K2x.rst | 2 +- ...Multiple_Ways_of_ARM-DSP_Communication.rst | 6 +-- .../Kernel/Kernel_Drivers/Camera/VIP.rst | 2 +- .../Kernel/Kernel_Drivers/Display/DSS7.rst | 2 +- .../Kernel_Drivers/Network/CPSW-EST.rst | 2 +- .../Kernel/Kernel_Drivers/Network/NetCP.rst | 8 ++-- .../Kernel_Drivers/PMIC/pmic_tps6594.rst | 4 +- .../pm_low_power_modes_socoff.rst | 2 +- .../Tools/Flash_Tools/_Sitara_Uniflash.rst | 2 +- .../Tools/Pin_Mux_Tools.rst | 2 +- .../Tools/SysConfig_Tools.rst | 2 +- .../linux/Foundational_Components/_OpenCV.rst | 8 ++-- ...undational_Components_Multimedia_wave5.rst | 2 +- .../Target/How_to_Tune_Real_Time_Linux.rst | 8 ++-- .../Target/How_to_boot_quickly.rst | 2 +- ...riables_stored_in_SPI_Flash_from_Linux.rst | 2 +- .../linux/Industrial_Protocols/PTP/_PTP.rst | 2 +- ...cessor_SDK_Linux_Getting_Started_Guide.rst | 44 +++++++++---------- source/linux/index_Edge_AI.rst | 2 +- 47 files changed, 106 insertions(+), 106 deletions(-) diff --git a/source/android/Overview/_Processor_SDK_Android_Software_Developers_Guide.rst b/source/android/Overview/_Processor_SDK_Android_Software_Developers_Guide.rst index ff3db6f59..32fb1f414 100644 --- a/source/android/Overview/_Processor_SDK_Android_Software_Developers_Guide.rst +++ b/source/android/Overview/_Processor_SDK_Android_Software_Developers_Guide.rst @@ -1,5 +1,5 @@ The **Processor Software Development Kit (Processor SDK)** is a unified software platform for TI embedded processors providing easy setup and fast out-of-the-box access to benchmarks and demos. All releases of Processor SDK are -consistent across TI’s broad portfolio, allowing developers to seamlessly reuse and develop software across devices. -Developing a scalable platform solutions has never been easier than with the Processor SDK and TI’s embedded processor +consistent across TI's broad portfolio, allowing developers to seamlessly reuse and develop software across devices. +Developing a scalable platform solutions has never been easier than with the Processor SDK and TI's embedded processor solutions. diff --git a/source/buildroot/Overview.rst b/source/buildroot/Overview.rst index b5c355c22..e10a0ee57 100644 --- a/source/buildroot/Overview.rst +++ b/source/buildroot/Overview.rst @@ -63,7 +63,7 @@ Key Features of Buildroot With a vast library of packages and a flexible configuration system, Buildroot allows for extensive customization of the target system. #. **Efficiency**: - Buildroot’s minimalistic approach ensures that the generated system is lean + Buildroot's minimalistic approach ensures that the generated system is lean and efficient, which is critical for resource-constrained embedded environments. #. **Active Community**: diff --git a/source/common/How_to_Guides/EVMK2H_Hardware_Setup.rst b/source/common/How_to_Guides/EVMK2H_Hardware_Setup.rst index 2b31e2807..1dfb971aa 100644 --- a/source/common/How_to_Guides/EVMK2H_Hardware_Setup.rst +++ b/source/common/How_to_Guides/EVMK2H_Hardware_Setup.rst @@ -231,19 +231,19 @@ with the following steps. #. Open the LM Flash programmer utility. (Default location Start Menu -> All Programs -> Texas Instruments -> Stellaris -> LM Flash Programmer -> LM Flash Programmer ) -#. In the LM Flash Programmer Utility ‘Configuration’ tab, in the - interface section, select ‘Serial (UART)’ from the drop-down box on +#. In the LM Flash Programmer Utility 'Configuration' tab, in the + interface section, select 'Serial (UART)' from the drop-down box on the left. #. 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’ + command earlier), and set the 'Baud Rate' to 115200. +#. Set 'Transfer Size' to 60, and make sure 'Disable Auto Baud Support' is unchecked. .. image:: /images/LMflashProg_Config.png -#. In the ‘Program’ tab, Browse to the location of the binary file +#. In the 'Program' tab, Browse to the location of the binary file containing the firmware update, and select it. -#. Leave all other options as default, and press the ‘Program’ button. +#. Leave all other options as default, and press the 'Program' button. #. After the programming is complete, power off the board. #. Reconnect the jumper. #. Open the HyperTerminal/Console for the BMC COM port. diff --git a/source/common/How_to_Guides/ICE_AM335x_Hardware_Setup.rst b/source/common/How_to_Guides/ICE_AM335x_Hardware_Setup.rst index c767314b2..64340a53c 100644 --- a/source/common/How_to_Guides/ICE_AM335x_Hardware_Setup.rst +++ b/source/common/How_to_Guides/ICE_AM335x_Hardware_Setup.rst @@ -17,7 +17,7 @@ and act as a communication gateway in this case. In addition it can directly operate as a standard remote I/O system or simple sensor connected to an industrial communication network. The embedded emulation logic allows emulation and debug using standard development tools such -as TI’s Code Composer Studio by just using the supplied USB cable. +as TI's Code Composer Studio by just using the supplied USB cable. EVM Layout and Key Components ------------------------------ diff --git a/source/common/How_to_Guides/TMDXIDK5728_Hardware_Setup.rst b/source/common/How_to_Guides/TMDXIDK5728_Hardware_Setup.rst index 6f26f17cb..52b81bd41 100644 --- a/source/common/How_to_Guides/TMDXIDK5728_Hardware_Setup.rst +++ b/source/common/How_to_Guides/TMDXIDK5728_Hardware_Setup.rst @@ -16,7 +16,7 @@ interface to other processors or systems and act as a communication gateway in this case. In addition it can directly operate as a standard remote I/O system or simple sensor connected to an industrial communication network. The embedded emulation logic allows emulation and -debug using standard development tools such as TI’s Code Composer Studio +debug using standard development tools such as TI's Code Composer Studio by just using the supplied USB cable. .. rubric:: EVM Layout and key components diff --git a/source/common/Overview/_Processor_SDK_Technical_Support.rst b/source/common/Overview/_Processor_SDK_Technical_Support.rst index c5db3c4a4..c84889c71 100644 --- a/source/common/Overview/_Processor_SDK_Technical_Support.rst +++ b/source/common/Overview/_Processor_SDK_Technical_Support.rst @@ -30,7 +30,7 @@ Open Source Software Support Disclaimer Processor SDK Linux Automotive integrates various free and open source software (FOSS) to demonstrate the hardware capabilities of Jacinto devices. The FOSS offers many advantages to the customers such as flexibility, interoperability, robustness, reduced development time and support from the respective FOSS community. -TI uses Yocto Project to integrate various software components and to build |__SDK_FULL_NAME__|. Yocto Project has two releases per year in April and October. TI’s Long-term Support (LTS) build for next year is based on current year’s October release of the Yocto Project. During a given year, TI’s LTS version migration only happens once per year and it occurs towards the end of the second quarter. The LTS migration usually signifies newer version of Kernel, U-boot, Toolchain, Yocto Project and etc. For more information on the current release, please refer to the Release Notes in the "Release Specific" section of respective platform. Therefore, the various open source components included in the |__SDK_FULL_NAME__| are only updated once per year. +TI uses Yocto Project to integrate various software components and to build |__SDK_FULL_NAME__|. Yocto Project has two releases per year in April and October. TI's Long-term Support (LTS) build for next year is based on current year's October release of the Yocto Project. During a given year, TI's LTS version migration only happens once per year and it occurs towards the end of the second quarter. The LTS migration usually signifies newer version of Kernel, U-boot, Toolchain, Yocto Project and etc. For more information on the current release, please refer to the Release Notes in the "Release Specific" section of respective platform. Therefore, the various open source components included in the |__SDK_FULL_NAME__| are only updated once per year. While TI integrates the FOSS in |__SDK_FULL_NAME__|, TI does not own, maintain and support the entire FOSS. If users have educational queries, feature enhancement requests or discover a bug on any components, TI encourages the users to reach out to the respective FOSS community for any additional support. Below are helpful resources to seek support on a few of the individual FOSS components. Please keep in mind that we are only showing a few of the components below but the same concept applies to all of the FOSS integrated in the |__SDK_FULL_NAME__|. diff --git a/source/common/PRU-ICSS/PRU-Hands-on-Labs.rst b/source/common/PRU-ICSS/PRU-Hands-on-Labs.rst index 9ba4da5ae..ce517a276 100644 --- a/source/common/PRU-ICSS/PRU-Hands-on-Labs.rst +++ b/source/common/PRU-ICSS/PRU-Hands-on-Labs.rst @@ -240,7 +240,7 @@ Load the PRU Firmware .. image:: /images/Pru_lab1_targetconfig.png -#. Let’s launch the debugger and load the code! +#. Let's launch the debugger and load the code! #. In the "Target Configurations" view, right click the Target Configuration file we just created and select **Launch Selected @@ -676,7 +676,7 @@ Design & Build the PRU Firmware a. Notice that as observed in the PRU master code, the PRU slave first configures the IEP Timer and DigIO and then interrupts the PRU master to - signal that it’s ready to communicate with the temperature sensor. + signal that it's ready to communicate with the temperature sensor. b. Notice that in the **iep_timer_config function**, the PRU slave stores different increments of time required by 1-wire protocol (i.e. @@ -716,7 +716,7 @@ Design & Build the PRU Firmware Load the PRU Firmware """"""""""""""""""""" -10. Let’s launch the debugger and load the code! +10. Let's launch the debugger and load the code! a. Right click the Target Configuration file we created earlier and select **Launch Selected Configuration**. @@ -760,7 +760,7 @@ Debug the PRU Firmware """""""""""""""""""""" 11. During our design discussion, we were unsure how many PRU cycles the - CRC calculation would consume. Let’s actually measure the PRU cycles + CRC calculation would consume. Let's actually measure the PRU cycles using the CCS debugger! a. Click on each PRU core and select the **yellow pause button** to diff --git a/source/devices/AM62AX/linux/Linux_Performance_Guide.rst b/source/devices/AM62AX/linux/Linux_Performance_Guide.rst index 4f548dbb1..7beb50d8f 100644 --- a/source/devices/AM62AX/linux/Linux_Performance_Guide.rst +++ b/source/devices/AM62AX/linux/Linux_Performance_Guide.rst @@ -306,7 +306,7 @@ MultiBench MultiBench™ is a suite of benchmarks that allows processor and system designers to analyze, test, and improve multicore processors. It uses three forms of concurrency: Data decomposition: multiple threads cooperating on achieving a unified goal and -demonstrating a processor’s support for fine grain parallelism. +demonstrating a processor's support for fine grain parallelism. Processing multiple data streams: uses common code running over multiple threads and demonstrating how well a processor scales over scalable data inputs. Multiple workload processing: shows the scalability of general-purpose processing, diff --git a/source/devices/AM62AX/linux/Overview.rst b/source/devices/AM62AX/linux/Overview.rst index 7d67cb5a9..cdae660a9 100644 --- a/source/devices/AM62AX/linux/Overview.rst +++ b/source/devices/AM62AX/linux/Overview.rst @@ -4,8 +4,8 @@ Overview The **Processor Software Development Kit (Processor SDK)** is a unified software platform for TI embedded processors providing easy setup and fast out-of-the-box access to benchmarks and demos. All releases of Processor SDK are -consistent across TI’s broad portfolio, allowing developers to seamlessly reuse and develop software across devices. -Developing a scalable platform solutions has never been easier than with the Processor SDK and TI’s embedded processor +consistent across TI's broad portfolio, allowing developers to seamlessly reuse and develop software across devices. +Developing a scalable platform solutions has never been easier than with the Processor SDK and TI's embedded processor solutions. .. toctree:: diff --git a/source/devices/AM62AX/linux/Release_Specific_Release_Notes.rst b/source/devices/AM62AX/linux/Release_Specific_Release_Notes.rst index f216f1dc2..3e0188c2f 100644 --- a/source/devices/AM62AX/linux/Release_Specific_Release_Notes.rst +++ b/source/devices/AM62AX/linux/Release_Specific_Release_Notes.rst @@ -9,8 +9,8 @@ Overview The **Processor Software Development Kit (Processor SDK)** is a unified software platform for TI embedded processors providing easy setup and fast out-of-the-box access to benchmarks and demos. All releases of Processor SDK are -consistent across TI’s broad portfolio, allowing developers to seamlessly reuse and develop software across devices. -Developing a scalable platform solutions has never been easier than with the Processor SDK and TI’s embedded processor +consistent across TI's broad portfolio, allowing developers to seamlessly reuse and develop software across devices. +Developing a scalable platform solutions has never been easier than with the Processor SDK and TI's embedded processor solutions. To simplify the end user experience, Processor SDK Linux AM62A installer provides everything needed as discussed below @@ -21,7 +21,7 @@ to create the embedded system from "scratch" : - An ARM cross-compiling toolchain as well as other host binaries and components - A Yocto/OE compliant filesystem and sources for example applications - A variety of scripts and Makefiles to automate certain tasks -- Other components needed to build an embedded system that don’t fit neatly into one of the above buckets +- Other components needed to build an embedded system that don't fit neatly into one of the above buckets - Reference Examples, benchmarks diff --git a/source/devices/AM62DX/linux/Linux_Performance_Guide.rst b/source/devices/AM62DX/linux/Linux_Performance_Guide.rst index 720d27c7a..f72411ab1 100644 --- a/source/devices/AM62DX/linux/Linux_Performance_Guide.rst +++ b/source/devices/AM62DX/linux/Linux_Performance_Guide.rst @@ -306,7 +306,7 @@ MultiBench MultiBench™ is a suite of benchmarks that allows processor and system designers to analyze, test, and improve multicore processors. It uses three forms of concurrency: Data decomposition: multiple threads cooperating on achieving a unified goal and -demonstrating a processor’s support for fine grain parallelism. +demonstrating a processor's support for fine grain parallelism. Processing multiple data streams: uses common code running over multiple threads and demonstrating how well a processor scales over scalable data inputs. Multiple workload processing: shows the scalability of general-purpose processing, diff --git a/source/devices/AM62DX/linux/Release_Specific_Release_Notes.rst b/source/devices/AM62DX/linux/Release_Specific_Release_Notes.rst index 0ddfcf542..bfaf4b7d7 100644 --- a/source/devices/AM62DX/linux/Release_Specific_Release_Notes.rst +++ b/source/devices/AM62DX/linux/Release_Specific_Release_Notes.rst @@ -9,8 +9,8 @@ Overview The **Processor Software Development Kit (Processor SDK)** is a unified software platform for TI embedded processors providing easy setup and fast out-of-the-box access to benchmarks and demos. All releases of Processor SDK are -consistent across TI’s broad portfolio, allowing developers to seamlessly reuse and develop software across devices. -Developing a scalable platform solutions has never been easier than with the Processor SDK and TI’s embedded processor +consistent across TI's broad portfolio, allowing developers to seamlessly reuse and develop software across devices. +Developing a scalable platform solutions has never been easier than with the Processor SDK and TI's embedded processor solutions. To simplify the end user experience, Processor SDK Linux AM62Dx installer provides everything needed as discussed below @@ -21,7 +21,7 @@ to create the embedded system from "scratch" : - An ARM cross-compiling toolchain as well as other host binaries and components - A Yocto/OE compliant filesystem and sources for example applications - A variety of scripts and Makefiles to automate certain tasks -- Other components needed to build an embedded system that don’t fit neatly into one of the above buckets +- Other components needed to build an embedded system that don't fit neatly into one of the above buckets - Reference Examples, benchmarks This release supports High Security - Field Securable (HS-FS) devices. For migration guide and other info, refer :ref:`HS-Migration-Guide` diff --git a/source/devices/AM62LX/linux/Linux_Performance_Guide.rst b/source/devices/AM62LX/linux/Linux_Performance_Guide.rst index 647c1df85..7a9dfcca8 100644 --- a/source/devices/AM62LX/linux/Linux_Performance_Guide.rst +++ b/source/devices/AM62LX/linux/Linux_Performance_Guide.rst @@ -325,7 +325,7 @@ MultiBench MultiBench™ is a suite of benchmarks that allows processor and system designers to analyze, test, and improve multicore processors. It uses three forms of concurrency: Data decomposition: multiple threads cooperating on achieving a unified goal and -demonstrating a processor’s support for fine grain parallelism. +demonstrating a processor's support for fine grain parallelism. Processing multiple data streams: uses common code running over multiple threads and demonstrating how well a processor scales over scalable data inputs. Multiple workload processing: shows the scalability of general-purpose processing, diff --git a/source/devices/AM62LX/linux/Overview.rst b/source/devices/AM62LX/linux/Overview.rst index b9cda10f8..7ff5d9b85 100644 --- a/source/devices/AM62LX/linux/Overview.rst +++ b/source/devices/AM62LX/linux/Overview.rst @@ -4,8 +4,8 @@ Overview The **Processor Software Development Kit (Processor SDK)** is a unified software platform for TI embedded processors providing easy setup and fast out-of-the-box access to benchmarks and demos. All releases of Processor SDK are -consistent across TI’s broad portfolio, allowing developers to seamlessly reuse and develop software across devices. -Developing a scalable platform solutions has never been easier than with the Processor SDK and TI’s embedded processor +consistent across TI's broad portfolio, allowing developers to seamlessly reuse and develop software across devices. +Developing a scalable platform solutions has never been easier than with the Processor SDK and TI's embedded processor solutions. .. toctree:: diff --git a/source/devices/AM62LX/linux/Release_Specific_Release_Notes.rst b/source/devices/AM62LX/linux/Release_Specific_Release_Notes.rst index 32ca1c9b7..2de82755c 100644 --- a/source/devices/AM62LX/linux/Release_Specific_Release_Notes.rst +++ b/source/devices/AM62LX/linux/Release_Specific_Release_Notes.rst @@ -9,8 +9,8 @@ Overview The **Processor Software Development Kit (Processor SDK)** is a unified software platform for TI embedded processors providing easy setup and fast out-of-the-box access to benchmarks and demos. All releases of Processor SDK are -consistent across TI’s broad portfolio, allowing developers to seamlessly reuse and develop software across devices. -Developing a scalable platform solutions has never been easier than with the Processor SDK and TI’s embedded processor +consistent across TI's broad portfolio, allowing developers to seamlessly reuse and develop software across devices. +Developing a scalable platform solutions has never been easier than with the Processor SDK and TI's embedded processor solutions. To simplify the user experience, Processor SDK Linux AM62L installer provides everything needed as discussed below @@ -21,7 +21,7 @@ to create the embedded system from "scratch" : - An ARM cross-compiling toolchain as well as other host binaries and components - A Yocto/OE compliant filesystem and sources for example applications - A variety of scripts and Makefiles to automate certain tasks -- Other components needed to build an embedded system that don’t fit neatly into one of the above buckets +- Other components needed to build an embedded system that don't fit neatly into one of the above buckets - Reference Examples, benchmarks This release supports High Security - Field Securable (HS-FS) devices. diff --git a/source/devices/AM62PX/linux/Linux_Performance_Guide.rst b/source/devices/AM62PX/linux/Linux_Performance_Guide.rst index 8965f23a3..a9a7271cb 100644 --- a/source/devices/AM62PX/linux/Linux_Performance_Guide.rst +++ b/source/devices/AM62PX/linux/Linux_Performance_Guide.rst @@ -324,7 +324,7 @@ MultiBench MultiBench™ is a suite of benchmarks that allows processor and system designers to analyze, test, and improve multicore processors. It uses three forms of concurrency: Data decomposition: multiple threads cooperating on achieving a unified goal and -demonstrating a processor’s support for fine grain parallelism. +demonstrating a processor's support for fine grain parallelism. Processing multiple data streams: uses common code running over multiple threads and demonstrating how well a processor scales over scalable data inputs. Multiple workload processing: shows the scalability of general-purpose processing, diff --git a/source/devices/AM62PX/linux/Overview.rst b/source/devices/AM62PX/linux/Overview.rst index 7d67cb5a9..cdae660a9 100644 --- a/source/devices/AM62PX/linux/Overview.rst +++ b/source/devices/AM62PX/linux/Overview.rst @@ -4,8 +4,8 @@ Overview The **Processor Software Development Kit (Processor SDK)** is a unified software platform for TI embedded processors providing easy setup and fast out-of-the-box access to benchmarks and demos. All releases of Processor SDK are -consistent across TI’s broad portfolio, allowing developers to seamlessly reuse and develop software across devices. -Developing a scalable platform solutions has never been easier than with the Processor SDK and TI’s embedded processor +consistent across TI's broad portfolio, allowing developers to seamlessly reuse and develop software across devices. +Developing a scalable platform solutions has never been easier than with the Processor SDK and TI's embedded processor solutions. .. toctree:: diff --git a/source/devices/AM62PX/linux/Release_Specific_Release_Notes.rst b/source/devices/AM62PX/linux/Release_Specific_Release_Notes.rst index 9e3d08749..dbc6b3575 100644 --- a/source/devices/AM62PX/linux/Release_Specific_Release_Notes.rst +++ b/source/devices/AM62PX/linux/Release_Specific_Release_Notes.rst @@ -9,8 +9,8 @@ Overview The **Processor Software Development Kit (Processor SDK)** is a unified software platform for TI embedded processors providing easy setup and fast out-of-the-box access to benchmarks and demos. All releases of Processor SDK are -consistent across TI’s broad portfolio, allowing developers to seamlessly reuse and develop software across devices. -Developing a scalable platform solutions has never been easier than with the Processor SDK and TI’s embedded processor +consistent across TI's broad portfolio, allowing developers to seamlessly reuse and develop software across devices. +Developing a scalable platform solutions has never been easier than with the Processor SDK and TI's embedded processor solutions. To simplify the user experience, Processor SDK Linux AM62Px installer provides everything needed as discussed below @@ -21,7 +21,7 @@ to create the embedded system from "scratch" : - An ARM cross-compiling toolchain as well as other host binaries and components - A Yocto/OE compliant filesystem and sources for example applications - A variety of scripts and Makefiles to automate certain tasks -- Other components needed to build an embedded system that don’t fit neatly into one of the above buckets +- Other components needed to build an embedded system that don't fit neatly into one of the above buckets - Reference Examples, benchmarks This release supports High Security - Field Securable (HS-FS) devices. diff --git a/source/devices/AM62X/linux/Linux_Performance_Guide.rst b/source/devices/AM62X/linux/Linux_Performance_Guide.rst index 1ae273ebb..7a3a17eda 100644 --- a/source/devices/AM62X/linux/Linux_Performance_Guide.rst +++ b/source/devices/AM62X/linux/Linux_Performance_Guide.rst @@ -330,7 +330,7 @@ MultiBench MultiBench™ is a suite of benchmarks that allows processor and system designers to analyze, test, and improve multicore processors. It uses three forms of concurrency: Data decomposition: multiple threads cooperating on achieving a unified goal and -demonstrating a processor’s support for fine grain parallelism. +demonstrating a processor's support for fine grain parallelism. Processing multiple data streams: uses common code running over multiple threads and demonstrating how well a processor scales over scalable data inputs. Multiple workload processing: shows the scalability of general-purpose processing, diff --git a/source/devices/AM62X/linux/Overview.rst b/source/devices/AM62X/linux/Overview.rst index 7d67cb5a9..cdae660a9 100644 --- a/source/devices/AM62X/linux/Overview.rst +++ b/source/devices/AM62X/linux/Overview.rst @@ -4,8 +4,8 @@ Overview The **Processor Software Development Kit (Processor SDK)** is a unified software platform for TI embedded processors providing easy setup and fast out-of-the-box access to benchmarks and demos. All releases of Processor SDK are -consistent across TI’s broad portfolio, allowing developers to seamlessly reuse and develop software across devices. -Developing a scalable platform solutions has never been easier than with the Processor SDK and TI’s embedded processor +consistent across TI's broad portfolio, allowing developers to seamlessly reuse and develop software across devices. +Developing a scalable platform solutions has never been easier than with the Processor SDK and TI's embedded processor solutions. .. toctree:: diff --git a/source/devices/AM62X/linux/Release_Specific_Release_Notes.rst b/source/devices/AM62X/linux/Release_Specific_Release_Notes.rst index ca51a2b5d..42e6121fe 100644 --- a/source/devices/AM62X/linux/Release_Specific_Release_Notes.rst +++ b/source/devices/AM62X/linux/Release_Specific_Release_Notes.rst @@ -9,8 +9,8 @@ Overview The **Processor Software Development Kit (Processor SDK)** is a unified software platform for TI embedded processors providing easy setup and fast out-of-the-box access to benchmarks and demos. All releases of Processor SDK are -consistent across TI’s broad portfolio, allowing developers to seamlessly reuse and develop software across devices. -Developing a scalable platform solutions has never been easier than with the Processor SDK and TI’s embedded processor +consistent across TI's broad portfolio, allowing developers to seamlessly reuse and develop software across devices. +Developing a scalable platform solutions has never been easier than with the Processor SDK and TI's embedded processor solutions. To simplify the end user experience, Processor SDK Linux AM62x installer provides everything needed as discussed below @@ -21,7 +21,7 @@ to create the embedded system from "scratch" : - An ARM cross-compiling toolchain as well as other host binaries and components - A Yocto/OE compliant filesystem and sources for example applications - A variety of scripts and Makefiles to automate certain tasks -- Other components needed to build an embedded system that don’t fit neatly into one of the above buckets +- Other components needed to build an embedded system that don't fit neatly into one of the above buckets - Reference Examples, benchmarks This release supports High Security - Field Securable (HS-FS) devices. For migration guide and other info, refer :ref:`HS-Migration-Guide` diff --git a/source/devices/AM64X/linux/Overview.rst b/source/devices/AM64X/linux/Overview.rst index 7d67cb5a9..cdae660a9 100644 --- a/source/devices/AM64X/linux/Overview.rst +++ b/source/devices/AM64X/linux/Overview.rst @@ -4,8 +4,8 @@ Overview The **Processor Software Development Kit (Processor SDK)** is a unified software platform for TI embedded processors providing easy setup and fast out-of-the-box access to benchmarks and demos. All releases of Processor SDK are -consistent across TI’s broad portfolio, allowing developers to seamlessly reuse and develop software across devices. -Developing a scalable platform solutions has never been easier than with the Processor SDK and TI’s embedded processor +consistent across TI's broad portfolio, allowing developers to seamlessly reuse and develop software across devices. +Developing a scalable platform solutions has never been easier than with the Processor SDK and TI's embedded processor solutions. .. toctree:: diff --git a/source/devices/AM64X/linux/Release_Specific_Release_Notes.rst b/source/devices/AM64X/linux/Release_Specific_Release_Notes.rst index 3dd1b18ef..d6d642762 100644 --- a/source/devices/AM64X/linux/Release_Specific_Release_Notes.rst +++ b/source/devices/AM64X/linux/Release_Specific_Release_Notes.rst @@ -9,8 +9,8 @@ Overview The **Processor Software Development Kit (Processor SDK)** is a unified software platform for TI embedded processors providing easy setup and fast out-of-the-box access to benchmarks and demos. All releases of Processor SDK are -consistent across TI’s broad portfolio, allowing developers to seamlessly reuse and develop software across devices. -Developing a scalable platform solutions has never been easier than with the Processor SDK and TI’s embedded processor +consistent across TI's broad portfolio, allowing developers to seamlessly reuse and develop software across devices. +Developing a scalable platform solutions has never been easier than with the Processor SDK and TI's embedded processor solutions. To simplify the end user experience, Processor SDK Linux AM64x installer provides everything needed as discussed below @@ -21,7 +21,7 @@ to create the embedded system from "scratch" : - An ARM cross-compiling toolchain as well as other host binaries and components - A Yocto/OE compliant filesystem and sources for example applications - A variety of scripts and Makefiles to automate certain tasks -- Other components needed to build an embedded system that don’t fit neatly into one of the above buckets +- Other components needed to build an embedded system that don't fit neatly into one of the above buckets - Reference Examples, benchmarks This release supports SR2.0 High Security - Field Securable (HS-FS) devices. For migration guide and other info, refer :ref:`HS-Migration-Guide` diff --git a/source/devices/AM65X/linux/RT_Linux_Performance_Guide.rst b/source/devices/AM65X/linux/RT_Linux_Performance_Guide.rst index 07cbc8617..05f1c6e69 100644 --- a/source/devices/AM65X/linux/RT_Linux_Performance_Guide.rst +++ b/source/devices/AM65X/linux/RT_Linux_Performance_Guide.rst @@ -258,7 +258,7 @@ MultiBench MultiBench™ is a suite of benchmarks that allows processor and system designers to analyze, test, and improve multicore processors. It uses three forms of concurrency: Data decomposition: multiple threads cooperating on achieving a unified goal and -demonstrating a processor’s support for fine grain parallelism. +demonstrating a processor's support for fine grain parallelism. Processing multiple data streams: uses common code running over multiple threads and demonstrating how well a processor scales over scalable data inputs. Multiple workload processing: shows the scalability of general-purpose processing, diff --git a/source/devices/DRA821A/linux/Release_Specific_Release_Notes.rst b/source/devices/DRA821A/linux/Release_Specific_Release_Notes.rst index 482a7ddcf..8d7cbd5be 100644 --- a/source/devices/DRA821A/linux/Release_Specific_Release_Notes.rst +++ b/source/devices/DRA821A/linux/Release_Specific_Release_Notes.rst @@ -126,7 +126,7 @@ Issues opened in previous releases that were closed on this release LCPD-19772,ATF/Uboot GTC frequency handover bug LCPD-19733,[ti:ti-rt-linux-5.4.y 3364/11241] drivers/pci/endpoint/functions/pci-epf-ntb.c:860 epf_ntb_init_epc_bar_interface() warn: unsigned 'barno' is never less than zero. - LCPD-19731,HSR/PRP : warning: ignoring return value of ‘skb_put_padto' + LCPD-19731,HSR/PRP : warning: ignoring return value of 'skb_put_padto' .. project = LCPD AND issuetype = Bug AND status = Closed AND resolution = Done AND component in ("Audio & Display", Baseport, Connectivity, IPC, "Power & Thermal", "System Integration", Wireless, Graphics, Multimedia, Security) AND closedDate > 2020-11-18 AND createdDate > 2020-11-18 AND (Labels not in (LCPD_K3.14_MAINT, MAINTENANCE, PLSDK_NOT_RN) OR labels is EMPTY) AND OS in (Linux, RT-linux) AND fixversion not in (Upstream) AND Platform in (j7200-evm) ORDER BY key DESC, priority DESC diff --git a/source/devices/J7_Family/linux/Release_Specific_Kernel_Performance_Guide.rst b/source/devices/J7_Family/linux/Release_Specific_Kernel_Performance_Guide.rst index 150bdd4f4..0650092e8 100644 --- a/source/devices/J7_Family/linux/Release_Specific_Kernel_Performance_Guide.rst +++ b/source/devices/J7_Family/linux/Release_Specific_Kernel_Performance_Guide.rst @@ -387,7 +387,7 @@ MultiBench MultiBench™ is a suite of benchmarks that allows processor and system designers to analyze, test, and improve multicore processors. It uses three forms of concurrency: Data decomposition: multiple threads cooperating on achieving a unified goal and -demonstrating a processor’s support for fine grain parallelism. +demonstrating a processor's support for fine grain parallelism. Processing multiple data streams: uses common code running over multiple threads and demonstrating how well a processor scales over scalable data inputs. Multiple workload processing: shows the scalability of general-purpose processing, diff --git a/source/edgeai/sdk_overview.rst b/source/edgeai/sdk_overview.rst index 900950754..99e900998 100644 --- a/source/edgeai/sdk_overview.rst +++ b/source/edgeai/sdk_overview.rst @@ -7,7 +7,7 @@ Overview **Welcome to Processor SDK Linux Edge AI for** |__PART_FAMILY_NAME__| **!** The SDK provides software and tools to let the users effectively balance -deep learning performance with system power and cost on Texas Instrument’s +deep learning performance with system power and cost on Texas Instrument's processors for edge AI applications. We offer a practical embedded inference solution for next-generation vehicles, smart cameras, edge AI boxes, and autonomous machines and robots. In addition to general purpose micro processors, 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 05b808e7d..7eee09fd8 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 @@ -6,7 +6,7 @@ Introduction The video graphics test application demonstrates various video processing, graphics and display capabilities using VIP, GC320, SGX and DSS IPs. Many embedded applications need multiple displays with multiple videos and graphics planes rendered on different screens. Such applications can be developed with or without using a windowing system like Wayland. Using a windowing system demands more system resources like CPU, GPU and DDR bandwidth and increases system complexity. When the system resources are in a crunch and there is no real need to use a windowing system, many users prefer to use no windowing system (alternately called as NULL window or full-screen mode). The video graphics test application demonstrates such application development in full-screen mode using QT. -QT framework is a popular tool to draw the software or hardware accelerated graphics contents. It can manage the display backend of embedded Linux system to render the contents in full-screen mode. It provides creation of a full-screen window by platform-specific means, known as QT Platform Abstraction (QPA). EGLFS is a platform plugin for running Qt5 applications on top of EGL and OpenGL ES 2.0 without an actual windowing system. When having multiple displays connected, QT provides another plugin named eglfs_kms to render the content on multiple displays. In eglfs_kms QPA, DRM Linux Kernel Mode Setting (KMS) API is used to set DSS mode. By default, eglfs_kms provided by QT doesn’t take advantage of the advance capabilities of DSS IP such as scaling, overlaying and alpha-blending of the videos/graphics planes. +QT framework is a popular tool to draw the software or hardware accelerated graphics contents. It can manage the display backend of embedded Linux system to render the contents in full-screen mode. It provides creation of a full-screen window by platform-specific means, known as QT Platform Abstraction (QPA). EGLFS is a platform plugin for running Qt5 applications on top of EGL and OpenGL ES 2.0 without an actual windowing system. When having multiple displays connected, QT provides another plugin named eglfs_kms to render the content on multiple displays. In eglfs_kms QPA, DRM Linux Kernel Mode Setting (KMS) API is used to set DSS mode. By default, eglfs_kms provided by QT doesn't take advantage of the advance capabilities of DSS IP such as scaling, overlaying and alpha-blending of the videos/graphics planes. To enable optimal usage of all the IPs on the AM57x8 devices and to deliver the best performance while running the QT application, we have enhanced the eglfs_kms QPA to leverage the DSS IP advance capabilities. The QPA exposes many callback functions through QPlatformNativeInterface to allow the users to set DSS IP advance properties. This enhanced QPA is packaged in PSDK Linux filesystem. diff --git a/source/linux/Foundational_Components/IPC/_IPC_for_K2x.rst b/source/linux/Foundational_Components/IPC/_IPC_for_K2x.rst index c18344e4d..56b9903e3 100644 --- a/source/linux/Foundational_Components/IPC/_IPC_for_K2x.rst +++ b/source/linux/Foundational_Components/IPC/_IPC_for_K2x.rst @@ -249,7 +249,7 @@ these executable binaries: The Multi-Processor Manager (MPM) Command Line utilities are used to download and start the DSP executables. -Let’s load the example and run the DSP: +Let's load the example and run the DSP: :: 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 3ad133b49..c975d6ec5 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 @@ -21,7 +21,7 @@ is based on C99 C with some additions and restrictions OpenCL supports both data parallel and task parallel programming paradigms. Data parallel execution parallelizes the execution across compute units on a device. Task parallel execution enables asynchronous dispatch of tasks -to each compute unit. For more info, please refer to `OpenCL User’s +to each compute unit. For more info, please refer to `OpenCL User's Guide `__ .. rubric:: Use Cases @@ -103,7 +103,7 @@ In AM57xx, the hardware accelerators are capable of the following - Sample Image Processing Kernels integrated in the DSP gstreamer plugin: Median2x2, Median3x3, Sobel3x3, Conv5x5, Canny -For more info, please refer to the `DCE Developer’s +For more info, please refer to the `DCE Developer's Guide `__ .. rubric:: Use Cases @@ -242,7 +242,7 @@ and DSP processors in a multi-processor environment. +------------+----------------------------------------------------------+-----------------------------------------------------------------------------------+ | | Pros | Cons | +============+==========================================================+===================================================================================+ -| OpenCL | Easy porting | Customer don’t have control over memory layout etc. to handle optimize DSP code | +| OpenCL | Easy porting | Customer don't have control over memory layout etc. to handle optimize DSP code | | | No DSP programming | | | | Standard OpenCL APIs | | +------------+----------------------------------------------------------+-----------------------------------------------------------------------------------+ 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 f50c1b044..9ab124efd 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Camera/VIP.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Camera/VIP.rst @@ -601,7 +601,7 @@ any modifications) into the device. Following points to keep in mind – .depth = 8, }, -.. rubric:: What’s the maximum frame rate possible for W\*H resolution +.. rubric:: What's the maximum frame rate possible for W\*H resolution using VIP? :name: whats-the-maximum-frame-rate-possible-for-wh-resolution-using-vip diff --git a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Display/DSS7.rst b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Display/DSS7.rst index 87dc7f554..072e05f86 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Display/DSS7.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Display/DSS7.rst @@ -734,7 +734,7 @@ Taking as an input a video frame of dimensions ``1000x1000``, this example creat - **Gamma Correction** -Gamma correction or gamma is used to adjust the brightness and color of images on a display. It is applied to ensure that the image appears as intended, with accurate brightness and color representation. Displays, such as LCDs and OLEDs, do not respond linearly to input signals. This means that the display's brightness does not increase linearly with the input voltage. Gamma correction compensates for this non-linear response by applying a non-linear transformation to the input signal. Gamma correction is typically applied using a look-up table (LUT) or a mathematical formula. The LUT or formula maps the input pixel values to output values that have been adjusted to compensate for the display’s non-linear response. DSS7 uses a look-up table for gamma correction. The gamma correction curve is usually represented by a power-law function, where the output value is proportional to the input value raised to a power. +Gamma correction or gamma is used to adjust the brightness and color of images on a display. It is applied to ensure that the image appears as intended, with accurate brightness and color representation. Displays, such as LCDs and OLEDs, do not respond linearly to input signals. This means that the display's brightness does not increase linearly with the input voltage. Gamma correction compensates for this non-linear response by applying a non-linear transformation to the input signal. Gamma correction is typically applied using a look-up table (LUT) or a mathematical formula. The LUT or formula maps the input pixel values to output values that have been adjusted to compensate for the display's non-linear response. DSS7 uses a look-up table for gamma correction. The gamma correction curve is usually represented by a power-law function, where the output value is proportional to the input value raised to a power. .. math:: diff --git a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Network/CPSW-EST.rst b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Network/CPSW-EST.rst index d91305f18..9a923a038 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Network/CPSW-EST.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Network/CPSW-EST.rst @@ -19,7 +19,7 @@ In Linux, EST/TAS offload to hardware is implemented using taprio offload. Time CPSW hardware supports EST configuration or offload. EST is configured through tc command as described in the above manual page. User indicate "flag 2" in the command which is then parsed by taprio scheduler in net core and indicate that the command is to be offloaded to hardware. taprio then offloads the command to the driver by calling ndo_setup_tc() ndo ops. -Driver supports only SetGateStates operation. EST operates on a repeating time interval generated by the CPTS EST function generator. Each Ethernet port has a global EST fetch RAM that can be configured as 2 buffers, each of 64 locations or one large buffer of 128 location. In 2 buffer configuration, a ping pong mechanism is used to hold the active schedule (oper) in one buffer and new (admin) command in the other. Each 22-bit fetch command consists of a 14-bit fetch count (14 MSB’s) and an 8-bit priority fetch allow (8 LSB’s) that will be applied for the fetch count time in wireside clocks. Driver process each of the sched-entry in the offload command and update the fetch RAM. Driver configures duration in sched-entry into the fetch count and Gate mask into the priority fetch bits of the RAM. Then configures the CPTS EST function generator to activate the schedule. Since driver uses 2 buffer configuration for fetch ram, this results in a max cycle time of ~8 msec (64 * 128 usec). +Driver supports only SetGateStates operation. EST operates on a repeating time interval generated by the CPTS EST function generator. Each Ethernet port has a global EST fetch RAM that can be configured as 2 buffers, each of 64 locations or one large buffer of 128 location. In 2 buffer configuration, a ping pong mechanism is used to hold the active schedule (oper) in one buffer and new (admin) command in the other. Each 22-bit fetch command consists of a 14-bit fetch count (14 MSB's) and an 8-bit priority fetch allow (8 LSB's) that will be applied for the fetch count time in wireside clocks. Driver process each of the sched-entry in the offload command and update the fetch RAM. Driver configures duration in sched-entry into the fetch count and Gate mask into the priority fetch bits of the RAM. Then configures the CPTS EST function generator to activate the schedule. Since driver uses 2 buffer configuration for fetch ram, this results in a max cycle time of ~8 msec (64 * 128 usec). CPSW supports a configurable number of priority queues (up to 8) and needs to be switched to this mode from the default round robin mode before EST can be configured. User configures these through ethtool commands:- -L for changing number of queues and --set-priv-flags to disable round robin mode. Driver doesn't enable EST if pf_p0_rx_ptype_rrobin privat flag is set. The flag is common for all ports, and so can't be just overridden by taprio configuration w/o user involvement. Command fails if pf_p0_rx_ptype_rrobin is already set in the driver. Also note that --set-priv-flags ethtool can be execute only when the Ethernet interface is down. So execute ifconfig down or equivalent command before execute the ethtool command. 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 2de38874d..540dcc321 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Network/NetCP.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Network/NetCP.rst @@ -2037,7 +2037,7 @@ Delete the 100-th entry in the table • 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. + • 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. @@ -2062,7 +2062,7 @@ Delete the 100-th entry in the table • 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 + 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 multicast flooding decision. unknown multicast flooding. @@ -2144,7 +2144,7 @@ To set CPSW to VLAN aware mode: echo "vlan_aware=1" > /sys/class/net/eth0/device/ale_control (set these to 0 to disable vlan aware mode) -To set port 1’s Ingress VLAN defaults: +To set port 1's Ingress VLAN defaults: :: @@ -2158,7 +2158,7 @@ To set port 1 to use the above default vlan id on ingress: echo "p1_pass_pri_tagged=0" > /sys/class/net/eth0/device/gbe_sw/control -To set port 1’s Egress VLAN defaults: +To set port 1's Egress VLAN defaults: - For registered VLANs, the egress policy is set in the "force\_untag\_egress field" of the ALE entry for that VLAN. This 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 c4723e1f7..306b1debb 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 @@ -66,7 +66,7 @@ Configs to be enabled in kernel: .. rubric:: CRC feature :name: crc-feature-i2c -.. rubric:: - When drivers are built as ‘modules’ +.. rubric:: - When drivers are built as 'modules' :name: crc-feature-i2c-modules For safety applications, a CRC feature can be enabled from userspace: @@ -96,7 +96,7 @@ To disable CRC feature, the modprobe conf file must be removed: Then, the board must be powered off/on with the mechanical switch to apply the new setting. -.. rubric:: - When drivers are built statically into the kernel (‘built-in’) +.. rubric:: - When drivers are built statically into the kernel ('built-in') :name: crc-feature-i2c-builtin CRC feature can be enabled through the kernel command line parameter: diff --git a/source/linux/Foundational_Components/Power_Management/pm_low_power_modes_socoff.rst b/source/linux/Foundational_Components/Power_Management/pm_low_power_modes_socoff.rst index f624b16b9..a19af36a8 100644 --- a/source/linux/Foundational_Components/Power_Management/pm_low_power_modes_socoff.rst +++ b/source/linux/Foundational_Components/Power_Management/pm_low_power_modes_socoff.rst @@ -76,7 +76,7 @@ Hardware modifications Software modifications ====================== -TI’s K3 Jacinto family of SoCs have a concept of boardcfg that can be used to configure certain parameters at build time. +TI's K3 Jacinto family of SoCs have a concept of boardcfg that can be used to configure certain parameters at build time. By default, SOC_OFF mode enabled by default in SDK. IO_ONLY_PLUS_DDR mode can be enabled by changing boardcfg in u-boot at build time. diff --git a/source/linux/Foundational_Components/Tools/Flash_Tools/_Sitara_Uniflash.rst b/source/linux/Foundational_Components/Tools/Flash_Tools/_Sitara_Uniflash.rst index 935b6c5b1..51cf91ded 100644 --- a/source/linux/Foundational_Components/Tools/Flash_Tools/_Sitara_Uniflash.rst +++ b/source/linux/Foundational_Components/Tools/Flash_Tools/_Sitara_Uniflash.rst @@ -549,7 +549,7 @@ problems are encountered. are using the same IP address for both RNDIS connections, Windows is trying to let us know that this is generally not a good idea. However, in this situation, the configuration ensures that both - interfaces won’t be used at the same time. + interfaces won't be used at the same time. .. Image:: /images/Microsoft_TCP_IP.png diff --git a/source/linux/Foundational_Components/Tools/Pin_Mux_Tools.rst b/source/linux/Foundational_Components/Tools/Pin_Mux_Tools.rst index ddedb0e6b..5312a8a08 100644 --- a/source/linux/Foundational_Components/Tools/Pin_Mux_Tools.rst +++ b/source/linux/Foundational_Components/Tools/Pin_Mux_Tools.rst @@ -21,7 +21,7 @@ can be saved as a pinmux design file which can be reloaded later. :name: disclaimer **NOTE:** Although these utilities are tested and intended to be -accurate, they are provided ‘as is’ and are not guaranteed to provide +accurate, they are provided 'as is' and are not guaranteed to provide accurate results. In the event of a conflict between the device data contained in this software tool and the device datasheet, the datasheet shall take precedence. Please check configuration results against the diff --git a/source/linux/Foundational_Components/Tools/SysConfig_Tools.rst b/source/linux/Foundational_Components/Tools/SysConfig_Tools.rst index 9ad65cc76..75eef84b5 100644 --- a/source/linux/Foundational_Components/Tools/SysConfig_Tools.rst +++ b/source/linux/Foundational_Components/Tools/SysConfig_Tools.rst @@ -38,7 +38,7 @@ The features available vary by the device and software development kit used. :name: disclaimer **NOTE:** Although these utilities are tested and intended to be -accurate, they are provided ‘as is’ and are not guaranteed to provide +accurate, they are provided 'as is' and are not guaranteed to provide accurate results. In the event of a conflict between the device data contained in this software tool and the device datasheet, the datasheet shall take precedence. Please check configuration results against the diff --git a/source/linux/Foundational_Components/_OpenCV.rst b/source/linux/Foundational_Components/_OpenCV.rst index 6feaf31c7..e5297b058 100644 --- a/source/linux/Foundational_Components/_OpenCV.rst +++ b/source/linux/Foundational_Components/_OpenCV.rst @@ -37,7 +37,7 @@ OpenCV implementation is available for the following TI devices: To meet the requirements of real-time processing of images and video OpenCV functions were optimized. -More-ever, TI’s OpenCV implementation of hybrid ARM-DSP devices (AM57X, +More-ever, TI's OpenCV implementation of hybrid ARM-DSP devices (AM57X, K2E, K2H, K2L, K2G) provides very efficient implementation of OpenCV function where signal-processing-rich algorithms are processed by DSP while the ARM processes all other algorithms, controls and manages the @@ -48,7 +48,7 @@ as well as a set of unit tests to verify the performances and the accuracy of the implementation. This document provides instructions show how to load and run unit tests -of TI’s OpenCV implementation. +of TI's OpenCV implementation. ================================= OpenCV Modules Supported By TI @@ -156,7 +156,7 @@ http://downloads.ti.com/mctools/esd/docs/opencl/environment_variables.html Figure 1 shows the decision tree the transparent API executes to determine if the computations will be offloaded to the accelerator -through OpenCL. The boxes that are shaded gray are specific to TI’s +through OpenCL. The boxes that are shaded gray are specific to TI's implementation of OpenCV. The prohibited list allows us to prevent certain OpenCL kernels from executing on the DSP. The kernels are prevented to execute on the DSP if they did not pass the accuracy tests. @@ -292,7 +292,7 @@ Unit Tests Each function in the OpenCV implementation has a unit test associate with the function. -The following instructions show how to load and run unit tests of TI’s +The following instructions show how to load and run unit tests of TI's OpenCV implementation. The screen shots and device dependent instructions in this document are from AM57X build and run and can be used as a reference for build diff --git a/source/linux/Foundational_Components_Multimedia_wave5.rst b/source/linux/Foundational_Components_Multimedia_wave5.rst index c220c8700..b7fac6cdf 100644 --- a/source/linux/Foundational_Components_Multimedia_wave5.rst +++ b/source/linux/Foundational_Components_Multimedia_wave5.rst @@ -601,7 +601,7 @@ ffplay ffprobe ======= ``-show_data`` - Show payload data, as a hexadecimal and ASCII dump. Coupled with -show_packets, it will dump the packets’ data. Coupled with -show_streams, it will dump the codec extradata + Show payload data, as a hexadecimal and ASCII dump. Coupled with -show_packets, it will dump the packets' data. Coupled with -show_streams, it will dump the codec extradata The dump is printed as the "data" field. It may contain newlines ``-show_packets`` Show information about each packet contained in the input multimedia stream diff --git a/source/linux/How_to_Guides/Target/How_to_Tune_Real_Time_Linux.rst b/source/linux/How_to_Guides/Target/How_to_Tune_Real_Time_Linux.rst index 9fda690e0..05a0e9f83 100644 --- a/source/linux/How_to_Guides/Target/How_to_Tune_Real_Time_Linux.rst +++ b/source/linux/How_to_Guides/Target/How_to_Tune_Real_Time_Linux.rst @@ -27,7 +27,7 @@ maximize the time our CPUs can be interrupted by the scheduler and introduce a level determinism to the Linux kernel to control the maximum latency the system will experience when switching contexts. -It’s important to note these patches do not focus on the minimum +It's important to note these patches do not focus on the minimum interrupt latency and can sometimes even increase it in certain situations. @@ -61,7 +61,7 @@ Testing Kernel Performance There are many ways to test or evaluate the performance of your application with the Real-Time Kernel and some of them will be more relevant than others depending on the nature of your application. -However as we’ll explain later it is typically best to test using your +However as we'll explain later it is typically best to test using your application and using stressing tools to examine its behavior under different circumstances. @@ -81,7 +81,7 @@ loads that our application may experience using a tool like stress-ng. stress-ng –cpu-method=all -c20 & -Then we can monitor our application’s performance or use another tool +Then we can monitor our application's performance or use another tool like cyclictest_ to measure the context switch latency the CPUs are experiencing. @@ -179,7 +179,7 @@ strain a resource in the SoC beyond what is acceptable for your application that will only be visible after many hours of testing. -It’s usually a good idea to embed and use monitoring mechanisms inside +It's usually a good idea to embed and use monitoring mechanisms inside your application to gauge the effects of our tuning efforts. Not only will this give us concrete evidence our tuning efforts are working, simulating our application with stress-ng or any other application could diff --git a/source/linux/How_to_Guides/Target/How_to_boot_quickly.rst b/source/linux/How_to_Guides/Target/How_to_boot_quickly.rst index 8742662e0..6fc4b5c39 100644 --- a/source/linux/How_to_Guides/Target/How_to_boot_quickly.rst +++ b/source/linux/How_to_Guides/Target/How_to_boot_quickly.rst @@ -84,7 +84,7 @@ This section details the Out-Of-Box boot sequence: **OPTEE** (Trusted Execution Environment) is designed as a companion to a non-secure Linux kernel running on Arm; Cortex-A cores using the TrustZone technology. -**U-boot** proper is the second stage bootloader. It offers a flexible way to load and start the Linux Kernel and provides a minimal set of tools to interact with the board’s hardware via a command line interface. It runs from DRAM, initializing additional hardware devices (network, USB, DSI/CSI, etc.). Then, it loads and prepares the device tree (FDT). The main task handled by the U-Boot is the loading and starting of the kernel image itself. +**U-boot** proper is the second stage bootloader. It offers a flexible way to load and start the Linux Kernel and provides a minimal set of tools to interact with the board's hardware via a command line interface. It runs from DRAM, initializing additional hardware devices (network, USB, DSI/CSI, etc.). Then, it loads and prepares the device tree (FDT). The main task handled by the U-Boot is the loading and starting of the kernel image itself. **Kernel** runs from DDR and takes over the system completely. diff --git a/source/linux/How_to_Guides/Target/Update_U-Boot_Environment_Variables_stored_in_SPI_Flash_from_Linux.rst b/source/linux/How_to_Guides/Target/Update_U-Boot_Environment_Variables_stored_in_SPI_Flash_from_Linux.rst index 87c7671c9..bf8513b99 100644 --- a/source/linux/How_to_Guides/Target/Update_U-Boot_Environment_Variables_stored_in_SPI_Flash_from_Linux.rst +++ b/source/linux/How_to_Guides/Target/Update_U-Boot_Environment_Variables_stored_in_SPI_Flash_from_Linux.rst @@ -86,7 +86,7 @@ for the configuration file (fw\_env.config) is /etc/. :name: load-fw_printenvfw_setenv-into-target-file-system This creates the executable fw\_printenv, this file must be copied into -the target file system, place in /sbin or the user’s directory. +the target file system, place in /sbin or the user's directory. You must copy fw\_printenv to fw\_setenv to be able to set variables. The program detects the name it was called as and sets the context it diff --git a/source/linux/Industrial_Protocols/PTP/_PTP.rst b/source/linux/Industrial_Protocols/PTP/_PTP.rst index 14c5efb33..657f239a6 100644 --- a/source/linux/Industrial_Protocols/PTP/_PTP.rst +++ b/source/linux/Industrial_Protocols/PTP/_PTP.rst @@ -109,7 +109,7 @@ the repo is hosted here: http://git.ti.com/processor-sdk/linuxptp Hardware Overview ================= -TI’s Sitara devices have support for GMAC and PRU-ICSS ports, as shown +TI's Sitara devices have support for GMAC and PRU-ICSS ports, as shown in the table below. +--------------------------+--------------------------+--------------------------+-----------------------+ diff --git a/source/linux/Overview/Processor_SDK_Linux_Getting_Started_Guide.rst b/source/linux/Overview/Processor_SDK_Linux_Getting_Started_Guide.rst index 4a82e5d73..9eb4bc8a9 100644 --- a/source/linux/Overview/Processor_SDK_Linux_Getting_Started_Guide.rst +++ b/source/linux/Overview/Processor_SDK_Linux_Getting_Started_Guide.rst @@ -11,7 +11,7 @@ system on a TI Processor running Linux. Given this goal, we wanted to provide something that is more than just a typical Board Support Package (BSP) containing a bootloader, Linux kernel, and filesystem. While these are certainly necessary elements, we feel they are just a -starting point, especially for those that aren’t experts in developing +starting point, especially for those that aren't experts in developing with Linux. So, the SDK also contains tools for developing on TI Processors (a validated cross-compiling toolchain, for example), pre-built libraries that you can use without having to rebuild them @@ -40,14 +40,14 @@ to the :ref:`Processor SDK Linux Software Developer's Guide `. If y need, take a look at the active `E2E Processor Support `__ Forum and see if the topic has been covered before. If not, post -a new thread and we’ll do our best to provide some guidance. +a new thread and we'll do our best to provide some guidance. | What would you like to do with the SDK? --------------------------------------- -As described above, the SDK has a lot to it. Let’s break it down to two +As described above, the SDK has a lot to it. Let's break it down to two pieces to simplify things a bit: - The example :ref:`Embedded Linux System `. @@ -86,7 +86,7 @@ pieces to simplify things a bit: - A variety of scripts and Makefiles to automate certain tasks - Other components needed to build an embedded Linux system that - don’t fit neatly into one of the above buckets + don't fit neatly into one of the above buckets With these two pieces more clearly defined, we can now get back to that all important question, "What would you like to do with the SDK?". If @@ -107,13 +107,13 @@ with new device drivers and applications. also go ahead and skip down to the "I want to Develop!" (or, `Developing with the Linux SDK `__ section. -So, if you’re not quite there yet, let’s discuss some other options. -Maybe you’d like to evaluate the SDK a bit to see if it is how you’d +So, if you're not quite there yet, let's discuss some other options. +Maybe you'd like to evaluate the SDK a bit to see if it is how you'd like to get started. If this is not good enough and you really want to get your hands on something, check out the next section which shares how to play with the embedded Linux -system, the first piece of the SDK mentioned earlier. All you’ll need is access +system, the first piece of the SDK mentioned earlier. All you'll need is access to a Linux computer, a SD card, a SD card reader, some free, open-source software, and a supported :ref:`Hardware Platform `. @@ -121,22 +121,22 @@ software, and a supported :ref:`Hardware Platform .. rubric:: Evaluating the SDK Embedded Linux System :name: evaluating-the-sdk-embedded-linux-system -If you’re a hands on person, reading documentation and looking at +If you're a hands on person, reading documentation and looking at presentations gets old fast. So, if you want to see an example of what you can build with the SDK and actually hold it in your hands and play with it (or show it to someone else that needs help understanding what you want to do with it), with minimal effort, you can simply run the SDK Embedded Linux System on a supported :ref:`Hardware platform `. -This will allow you to poke and prod and interact. It’s a powerful way +This will allow you to poke and prod and interact. It's a powerful way to get the imagination active and engaged. .. ifconfig:: CONFIG_sdk in ('SITARA') - If you’ve recently purchased a TI EVM or Starterkit, it should have came + If you've recently purchased a TI EVM or Starterkit, it should have came with a SD card with the SDK on it. If that is the case, simply plug the card in, boot it up, and let your imagination run wild. However, if - you’re like us and the boards you are given never have all of the stuff + you're like us and the boards you are given never have all of the stuff they came with, or if you purchased a `Beaglebone `__ or `Beaglebone @@ -144,7 +144,7 @@ to get the imagination active and engaged. not have a SD card with the SDK on it. Or, maybe, the SDK on your SD card is simply a few revisions old and you want the latest and greatest. If that is the case, check out the :ref:`Create SD Card ` - page. Just remember, you won’t be able to build or change anything, + page. Just remember, you won't be able to build or change anything, simply evaluate the SDK Embedded Linux System as delivered. But, even this is enough to get the imagination going and all some folks want to do. @@ -156,25 +156,25 @@ to get the imagination active and engaged. .. rubric:: Start your Linux Development :name: start-your-linux-development -OK, you’re all in. Either you’ve known this is what you wanted to do, or -you’ve gone through the above steps and you want to do more. It’s time -to develop! Here’s a high level overview: +OK, you're all in. Either you've known this is what you wanted to do, or +you've gone through the above steps and you want to do more. It's time +to develop! Here's a high level overview: -- Get a Linux host up and running if you don’t already have one +- Get a Linux host up and running if you don't already have one - Install the SDK and run some scripts to get everything set up - Put the SDK Embedded Linux System on a SD card or TFTP/NFS to play with - Build something to validate set up – the SDK for example - Add something to the SDK, like a simple Hello World app -After completing these steps, you’ll have a known good baseline from +After completing these steps, you'll have a known good baseline from which you can start development. #. **Configure a Linux Host** If you already have a Linux host machine, go to Step 2. - To do Linux development with the SDK, you’ll need a host PC running + To do Linux development with the SDK, you'll need a host PC running Linux. The Linux host is generally much faster and has a lot more memory (both RAM and hard disk space) than the typical embedded system. While it is certainly possible to do all development @@ -182,7 +182,7 @@ which you can start development. to go and what is supported out of the box with the SDK. There are many, many ways to get access to a Linux host. We simply - can’t validate all possibilities and iterations, therefore we focus + can't validate all possibilities and iterations, therefore we focus on validating using `Ubuntu `__ as the host Linux distribution, running natively. We validate the Long-term Support (LTS) versions of Ubuntu at the time of a SDK release. @@ -200,7 +200,7 @@ which you can start development. Likewise, we would strongly recommend getting a **native 64-bit** Ubuntu LTS machine set up for development. For the cost of a little - bit of hard drive space, Ubuntu can have direct access to the host’s + bit of hard drive space, Ubuntu can have direct access to the host's hardware. Virtual Machines (VMs) have come a long way over the years, and many people use them daily without problems. However, when you are working with a target embedded system (that may be a prototype @@ -210,10 +210,10 @@ which you can start development. disconnecting hardware components, you have to be very diligent about making sure what is connected to what. You might prefer using an hour to get more work done than debugging a perceived problem caused by - the fact the virtual host grabbed a USB port when you weren’t + the fact the virtual host grabbed a USB port when you weren't watching. - When you’re ready to proceed, + When you're ready to proceed, `Ubuntu `__ provides a great overview for how to install natively. diff --git a/source/linux/index_Edge_AI.rst b/source/linux/index_Edge_AI.rst index bb603c99d..21aa473ef 100644 --- a/source/linux/index_Edge_AI.rst +++ b/source/linux/index_Edge_AI.rst @@ -2,7 +2,7 @@ Edge AI ####### - The SDK provides software and tools to let the users effectively balance deep learning performance with system power and cost on Texas Instrument’s processors for edge AI applications. We offer a practical embedded inference solution for next-generation vehicles, smart cameras, edge AI boxes, and autonomous machines and robots. In addition to general purpose micro processors, AM62Ax has integrated micro controllers, DSP, and accelerators for neural network, image, vision, and multimedia processing. With a few simple steps one can run high performance computer vision and deep learning demos using a live camera and display. + The SDK provides software and tools to let the users effectively balance deep learning performance with system power and cost on Texas Instrument's processors for edge AI applications. We offer a practical embedded inference solution for next-generation vehicles, smart cameras, edge AI boxes, and autonomous machines and robots. In addition to general purpose micro processors, AM62Ax has integrated micro controllers, DSP, and accelerators for neural network, image, vision, and multimedia processing. With a few simple steps one can run high performance computer vision and deep learning demos using a live camera and display. The SDK also enables an interplay of multiple open-source components such as GStreamer, OpenVx, OpenCV and deep learning runtime such as TFLite, ONNX and TVM-RT. The reference applications showcase perception based examples such as image classification, object detection and semantic segmentation in both Python and C++ variants. The SDK supports edit-build-debug cycles directly on the target and also on PC to cross compile and build the applications.