### Introduction
This guide is intended to assist users in getting quickly setup and evaluating with their AM574x IDK.
### Prerequisites
* [TMDSIDK574](https://www.ti.com/tool/TMDSIDK574)
* 5V DC Power Supply
* Micro-USB Cable
* Windows or Linux PC
### TMDSIDK574 Platform Introduction

There are three ways in which you can load/run applications on the AM57xx platforms:
* **LINUX** - There are number of ways to boot linux on the platform(SD, eMMC, QSPI, etc.), we will discuss SD boot here.
* **RTOS** - There are number of ways to boot RTOS on the platform(SD, QSPI and CCS), we will discuss CCS boot here.
* **NoOS**(baremetal) - You can load/run/debug NoOS application using CCS.
### LINUX Setup
#### Step 1: Preparing the SD card
The IDK comes with preflashed SD card having LINUX images in it. If you want to know more about flashing images to SD card, please go through [this documentation](https://software-dl.ti.com/processor-sdk-linux/esd/docs/06_03_00_106/linux/Overview/Processor_SDK_Linux_create_SD_card_script.html). We need to put the SD card in the SD slot.
#### Step 2: Connect the IDK to your PC
Connect the IDK's **J19 JTAG port** to PC using a micro USB cable.
#### Step 3: Power on the IDK
Connect the 5V DC power regulator plug to the IDK.
#### Step 4: Push the Power ON push button (SW3) to run the IDK.
As discussed [here](https://e2e.ti.com/support/processors/f/791/t/959283), AM57xx default boot is from SD interface, therefore the images on the SD will boot and you will see Linux booting on the console.
You should see the following green LEDs illuminate once powered on:
* **D18(INDUSTRIAL LED2), D19(INDUSTRIAL LED3), D23(STATUS LED1), D13.**
#### Step 5: Your IDK is now ready to use.
### RTOS Setup
As mentioned above, we can load the RTOS application in three ways:
* **SD card** - Please see [this](https://software-dl.ti.com/processor-sdk-rtos/esd/docs/06_03_00_106/rtos/index_overview.html#windows-sd-card-creation-guide) for SD card creation and booting documentation.
* **UNIFLASH** - Please see [this](https://www.ti.com/tool/UNIFLASH) for UNIFLASH documentation.
* **CCS** - You can load/run/debug RTOS application using CCS. We will discuss this method here.
#### Download CCS
The installation images for Code Composer Studio can be obtained from the [CCS Download Site](https://software-dl.ti.com/ccs/esd/documents/ccs_downloads.html).
Select the image that matches the host operating system of the computer that it will be installed on.
#### Install CCS
Note if the installer is in a zip file, it is necessary to extract the archived files before proceeding with the installation.
##### Accept the License Agreement

##### System Check
The installer will check the system to see if it meets the requirements
for installation. Any issues that need to be addressed will be displayed.
Disabling security software is recommended but optional.

##### Select Installation Location
Choose a location to install Code Composer Studio. This location must
not already contain a Code Composer Studio installation. If multiple
versions of Code Composer Studio will be installed then it is
recommended to install them in versioned folders.

##### Select Installation Type
There are two installation types:
* Custom Installation **(Recommended)**: Allows you to choose the device families and debug probes to be supported. Recommended to reduce the installation time, required disk space, and overall CCS performance.
* Full Installation: This will install support for *all* available device families and debug probes.

##### Select Device Support
If a **Custom Installation** was selected, this dialog is used to configure which device families to install support for. When a family is selected on the left hand side, a short description will be displayed on the right. This is useful to help determine which selections to make.
* select **Sitara AMx Processors**.

{{b **Note:** It is possible to add support for device families after installation by running the installer again and pointing it at the existing installation.
}}
##### Select Debug Probe Support
This dialog allows users to enable support for some common third party Debug Probes.
Available options will depend on the device families selected in the previous dialog.

Note that the **Spectrum Digital Debug Probes and Boards** option includes the support
for standard XDS560v2 debug probes.
##### Configure Proxy Server
If the **web installer** is being used, an additional dialog will appear - enter your network proxy server information (if applicable).

##### Progress
As the installation proceeds the progress screen will show what the
installer is doing.

##### Completion
The last screen shown during installation is the successful completion screen. This screen provides options to launch Code Composer Studio and to create a desktop shortcut.

### SDK Setup
The simplest way to download the AM57xx SDK is directly from `ti.com` which can be accessed from [AM57xx SDK](https://www.ti.com/tool/PROCESSOR-SDK-AM57X). You can download the SDK for either RTOS or LINUX OS.
### Running Project Zero (GPIO LED Blink)
{{b **Note:** It is recommended to install the SDK at default location 'C:\ti\' to run the below example as it includes other dependencies like XDCTOOLS, BIOS, etc.}}
This section will provide the steps to run the examples provided by Jacinto Academy which can be accessed from either [TI DevTools](https://dev.ti.com/tirex/explore/) or TI Resource Explorer inside CCS.
We will demonstrate CCS path here.
#### Step 1: Launch CCS.
#### Step 2: In CCS, go to *View → Resource Explorer* to launch Resource Explorer
#### Step 3: In the search bar, type "JACINTO Academy" and press **Enter**

#### Step 4: Select **JACINTO SDK for AM574x** in the Navigation Pane
#### Step 5: Click **Install** to open the **Confirm Installation** window
{{b **Note:** This step will not install SDK to your system, instead it will install JACINTO Academy in which you can refer the examples to start your development.}}

#### Step 6: Check the SDK and the mandatory dependencies and click **Next** to install the packages

#### Step 7: You can check the progress of the installation by clicking the checkmark on the toolbar. You will see "Success" when the installation is complete.

#### Step 8: Go to *JACINTO SDK for AM574x → Examples → gpio_ledBlink*
#### Step 9: Click **Import** to import the project to your CCS workspace

#### Step 10: In the Project Explorer window, select the imported project (**gpio_ledBlink**) and follow below steps for building and loading the project:
* To build the example, right-click the project and click *Rebuild Project*. You will see *Build Finished* on the console if the project builds successfully. The binary will get stored in the *debug* folder of the project.

* To load the project:
1. Launch the target configuration for TMDSIDK574.
2. Connect the A15 core by selecting the core and clicking on connect button.
3. Load an run the binary created in the build step.

See detailed documentation here: [CCS setup guide](https://software-dl.ti.com/processor-sdk-rtos/esd/docs/06_03_00_106/rtos/index_how_to_guides.html#setup-ccs-for-evm-and-processor-sdk-rtos)
#### Step 11: Click **Resume** or *Run → Resume* to run the example
#### Step 12: You should see the red **Industrial LED 0/1/2/3 and Status Led 0/1** LED blinking on your IDK and the following output in the CCS Console and/or UART Terminal
```c
*********************************************
* LED Test *
*********************************************
Testing LED
Blinking LEDs...
Press 'y' to verify pass, 'r' to blink again,
or any other character to indicate failure: y
Received: y
Test PASSED!
```
### Next Steps
Now that you have learned how to run your first application on the TMDSIDK574, we recommend installing the following tools to enable additional functionality with the SDK.
* **OpenSSL** - Required for rebuilding the Secondary Bootloader (SBL).
* **(Linux Only) Mono Runtime** - Required for converting the example binaries to bootable images.