Skip to content

Commit 599dcca

Browse files
StaticRocketcshilwant
authored andcommitted
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 <rs@ti.com>
1 parent a5eab17 commit 599dcca

47 files changed

Lines changed: 106 additions & 106 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.
Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
The **Processor Software Development Kit (Processor SDK)** is a unified software platform for TI embedded processors
22
providing easy setup and fast out-of-the-box access to benchmarks and demos. All releases of Processor SDK are
3-
consistent across TIs broad portfolio, allowing developers to seamlessly reuse and develop software across devices.
4-
Developing a scalable platform solutions has never been easier than with the Processor SDK and TIs embedded processor
3+
consistent across TI's broad portfolio, allowing developers to seamlessly reuse and develop software across devices.
4+
Developing a scalable platform solutions has never been easier than with the Processor SDK and TI's embedded processor
55
solutions.

source/buildroot/Overview.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -63,7 +63,7 @@ Key Features of Buildroot
6363
With a vast library of packages and a flexible configuration system,
6464
Buildroot allows for extensive customization of the target system.
6565
#. **Efficiency**:
66-
Buildroots minimalistic approach ensures that the generated system is lean
66+
Buildroot's minimalistic approach ensures that the generated system is lean
6767
and efficient, which is critical for resource-constrained embedded
6868
environments.
6969
#. **Active Community**:

source/common/How_to_Guides/EVMK2H_Hardware_Setup.rst

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -231,19 +231,19 @@ with the following steps.
231231
#. Open the LM Flash programmer utility. (Default location Start Menu ->
232232
All Programs -> Texas Instruments -> Stellaris -> LM Flash Programmer
233233
-> LM Flash Programmer )
234-
#. In the LM Flash Programmer Utility Configuration tab, in the
235-
interface section, select Serial (UART) from the drop-down box on
234+
#. In the LM Flash Programmer Utility 'Configuration' tab, in the
235+
interface section, select 'Serial (UART)' from the drop-down box on
236236
the left.
237237
#. Select the BMC COM Port (the same COM port used to issue the ver
238-
command earlier), and set the Baud Rate to 115200.
239-
#. Set Transfer Size to 60, and make sure Disable Auto Baud Support
238+
command earlier), and set the 'Baud Rate' to 115200.
239+
#. Set 'Transfer Size' to 60, and make sure 'Disable Auto Baud Support'
240240
is unchecked.
241241

242242
.. image:: /images/LMflashProg_Config.png
243243

244-
#. In the Program tab, Browse to the location of the binary file
244+
#. In the 'Program' tab, Browse to the location of the binary file
245245
containing the firmware update, and select it.
246-
#. Leave all other options as default, and press the Program button.
246+
#. Leave all other options as default, and press the 'Program' button.
247247
#. After the programming is complete, power off the board.
248248
#. Reconnect the jumper.
249249
#. Open the HyperTerminal/Console for the BMC COM port.

source/common/How_to_Guides/ICE_AM335x_Hardware_Setup.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ and act as a communication gateway in this case. In addition it can
1717
directly operate as a standard remote I/O system or simple sensor
1818
connected to an industrial communication network. The embedded emulation
1919
logic allows emulation and debug using standard development tools such
20-
as TIs Code Composer Studio by just using the supplied USB cable.
20+
as TI's Code Composer Studio by just using the supplied USB cable.
2121

2222
EVM Layout and Key Components
2323
------------------------------

source/common/How_to_Guides/TMDXIDK5728_Hardware_Setup.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ interface to other processors or systems and act as a communication
1616
gateway in this case. In addition it can directly operate as a standard
1717
remote I/O system or simple sensor connected to an industrial
1818
communication network. The embedded emulation logic allows emulation and
19-
debug using standard development tools such as TIs Code Composer Studio
19+
debug using standard development tools such as TI's Code Composer Studio
2020
by just using the supplied USB cable.
2121

2222
.. rubric:: EVM Layout and key components

source/common/Overview/_Processor_SDK_Technical_Support.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ Open Source Software Support Disclaimer
3030
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.
3131

3232

33-
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. TIs Long-term Support (LTS) build for next year is based on current years October release of the Yocto Project. During a given year, TIs 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.
33+
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.
3434

3535
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__|.
3636

source/common/PRU-ICSS/PRU-Hands-on-Labs.rst

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -240,7 +240,7 @@ Load the PRU Firmware
240240

241241
.. image:: /images/Pru_lab1_targetconfig.png
242242

243-
#. Lets launch the debugger and load the code!
243+
#. Let's launch the debugger and load the code!
244244

245245
#. In the "Target Configurations" view, right click the Target
246246
Configuration file we just created and select **Launch Selected
@@ -676,7 +676,7 @@ Design & Build the PRU Firmware
676676

677677
a. Notice that as observed in the PRU master code, the PRU slave first
678678
configures the IEP Timer and DigIO and then interrupts the PRU master to
679-
signal that its ready to communicate with the temperature sensor.
679+
signal that it's ready to communicate with the temperature sensor.
680680

681681
b. Notice that in the **iep_timer_config function**, the PRU slave
682682
stores different increments of time required by 1-wire protocol (i.e.
@@ -716,7 +716,7 @@ Design & Build the PRU Firmware
716716
Load the PRU Firmware
717717
"""""""""""""""""""""
718718

719-
10. Lets launch the debugger and load the code!
719+
10. Let's launch the debugger and load the code!
720720

721721
a. Right click the Target Configuration file we created earlier and
722722
select **Launch Selected Configuration**.
@@ -760,7 +760,7 @@ Debug the PRU Firmware
760760
""""""""""""""""""""""
761761

762762
11. During our design discussion, we were unsure how many PRU cycles the
763-
CRC calculation would consume. Lets actually measure the PRU cycles
763+
CRC calculation would consume. Let's actually measure the PRU cycles
764764
using the CCS debugger!
765765

766766
a. Click on each PRU core and select the **yellow pause button** to

source/devices/AM62AX/linux/Linux_Performance_Guide.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -306,7 +306,7 @@ MultiBench
306306
MultiBench™ is a suite of benchmarks that allows processor and system designers to
307307
analyze, test, and improve multicore processors. It uses three forms of concurrency:
308308
Data decomposition: multiple threads cooperating on achieving a unified goal and
309-
demonstrating a processors support for fine grain parallelism.
309+
demonstrating a processor's support for fine grain parallelism.
310310
Processing multiple data streams: uses common code running over multiple threads and
311311
demonstrating how well a processor scales over scalable data inputs.
312312
Multiple workload processing: shows the scalability of general-purpose processing,

source/devices/AM62AX/linux/Overview.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,8 +4,8 @@ Overview
44

55
The **Processor Software Development Kit (Processor SDK)** is a unified software platform for TI embedded processors
66
providing easy setup and fast out-of-the-box access to benchmarks and demos. All releases of Processor SDK are
7-
consistent across TIs broad portfolio, allowing developers to seamlessly reuse and develop software across devices.
8-
Developing a scalable platform solutions has never been easier than with the Processor SDK and TIs embedded processor
7+
consistent across TI's broad portfolio, allowing developers to seamlessly reuse and develop software across devices.
8+
Developing a scalable platform solutions has never been easier than with the Processor SDK and TI's embedded processor
99
solutions.
1010

1111
.. toctree::

source/devices/AM62AX/linux/Release_Specific_Release_Notes.rst

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -9,8 +9,8 @@ Overview
99

1010
The **Processor Software Development Kit (Processor SDK)** is a unified software platform for TI embedded processors
1111
providing easy setup and fast out-of-the-box access to benchmarks and demos. All releases of Processor SDK are
12-
consistent across TIs broad portfolio, allowing developers to seamlessly reuse and develop software across devices.
13-
Developing a scalable platform solutions has never been easier than with the Processor SDK and TIs embedded processor
12+
consistent across TI's broad portfolio, allowing developers to seamlessly reuse and develop software across devices.
13+
Developing a scalable platform solutions has never been easier than with the Processor SDK and TI's embedded processor
1414
solutions.
1515

1616
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" :
2121
- An ARM cross-compiling toolchain as well as other host binaries and components
2222
- A Yocto/OE compliant filesystem and sources for example applications
2323
- A variety of scripts and Makefiles to automate certain tasks
24-
- Other components needed to build an embedded system that dont fit neatly into one of the above buckets
24+
- Other components needed to build an embedded system that don't fit neatly into one of the above buckets
2525
- Reference Examples, benchmarks
2626

2727

0 commit comments

Comments
 (0)