Attention: It is strongly recommended to begin development by following the steps in the order listed below.

Note: The steps in this user guide show screen shots and descriptions based on Windows. However the steps in Linux would remain the same, unless mentioned otherwise.; ${SDK_INSTALL_PATH} refers to the path where the SDK is installed. Recommend to install in C:/ti in Windows, and ${HOME}/ti in Linux. To install to other locations, refer Installing SDK at non-default location; {some text} refers to a variable string that should be replaced by user and {some text} should not be typed verbatim on the command prompt.; In Windows, use the cmd.exe as command prompt and in Linux, use the bash shell as the command prompt.

Introduction

Getting Started Goals

On successful completion of below steps, you would have achieved the following

All tools needed for development are installed
EVM setup needed for development is verified
CCS IDE setup needed for development is verified
One SDK example has been built using makefile as well as CCS project
One SDK example has been loaded and run on the EVM
Output console logs on CCS and UART are working as expected
One SDK example has been flashed to the EVM flash and the application booted from the flash without CCS.
Use TI OptiFlah memory technology along with Smart Placement tool to improve system level performance with external flash.

Terms and Abbreviations

Term	Description
McSPI Controller	McSPI in communication which generates the clock and initiates the transfer
McSPI Peripheral	McSPI in communication which read and write data based on Controller clock
I2C Controller	I2C device which generates the SCL clock and initiates communication
I2C Target	I2C device which responds to I2C Controller
LIN Commander	LIN device which intiates the transfer
LIN Responder	LIN device which responds to the transfer
PTP Sync Time Source	Ethernet device that periodically broadcasts the current time as a message to the other clocks
PTP Sync Receiver	Ethernet device that is waiting for the master to poll for data to actually send it
EtherCAT MainDevice	EtherCAT device which is allowed to trasfer the data across network
EtherCAT SubDevice	EtherCAT device which reads the data addressed to them bu MainDevice
Ethernet/IP Scanner	Ethernet/IP scanned is the client device responsible for establishing a connection path to an EtherNet/IP Adapter
Ethernet/IP Adapter	Ethernet/IP adapter which receives implicit communication connection requests from an scanner then produces its I/O data at the requested rate. An adapter is also an explicit message server.
IO-Link Controller	IO-Link device which provides the interface to the higher-level controller (PLC) and controls the communication with the connected IO-Link devices. An IO-Link master can have one or more IO-Link ports to which only one device can be connected at a time
IO-Link Device	IO-Link device is a short distance, bi-directional, digital, point-to-point, wired (or wireless), industrial communications networking standard (IEC 61131-9) used for connecting digital sensors and actuators to either a type of industrial fieldbus or a type of industrial Ethernet

Getting Started Steps

Step 1: Download, install SDK and related tools, see Download, Install and Setup SDK and Tools [NEEDS TO BE DONE ONCE when SDK is installed]
Step 2: Download, install and setup CCS for development, see Download, Install and Setup CCS [NEEDS TO BE DONE ONCE when SDK is installed]
Step 3: Setup EVM for program execution, see EVM Setup
Step 4: Build a "hello world" example for the EVM, see Build a Hello World example
Step 5: Load and run the "hello world" example on the EVM, see CCS Launch, Load and Run
Step 6: Flash the "hello world" example on the EVM and boot without CCS, see Flash a Hello World example or Flash a Hello World example using DFU [OPTIONAL and is typically needed after all development via CCS is done]
Step 7: Optimized system level performance using Smart Placement. See Getting Started With Smart Placement.

Next Steps

Now you can explore the SDK by running more examples (see Examples and Demos) and browsing through various developer notes (see Developer Guides), to understand the SDK better and develop your own applications with the SDK.