2. Getting Started¶
This section highlights some of the most common resources required to use this SDK and/or its components. This SDK is made up of several components. Component details, including capabilities, features, and limitations, are found in component specific documentation. The links to component specific documentation are indexed on the following page: SDK Components
This SDK supports J722S family of SoCs including devices listed below.
Platform |
Devices |
J722S |
TDA4VEN-Q1, TDA4AEN-Q1 |
2.1. Dependencies¶
This SDK and its components are built for the family of SoC specified above. Some of the demo/example/reference applications provided by SDK, depends on specific board(s), below listed are the boards/hardware dependencies
2.1.1. Hardware Dependencies¶
2.1.1.1. Evaluation Module (EVM)¶
This SDK is intended to run on the following EVM:
For details on configuring the EVM to run this SDK, refer to the EVM Setup for J722S section.
2.1.1.2. JTAG¶
The J722S EVM provides on on-board XDS110 USB debugger as shown here
JTAG would allow one to debug execution on different compute cores, load and run applications, etc…
To be able to load a program via JTAG, the board will have to be configured in No Boot Mode .
Note that while configuring to no-boot mode is mandatory to load and run apps from CCS. It’s not mandatory, once the device is booted.
e.g. When set to operate in mmc/sd boot mode and mmc/sd card include valid images, on powerup/boot completion, JTAG could be be used to connect to enabled compute core.
2.1.1.3. uart terminal¶
Most of the example application provided in the SDK, prints status of the application via the uart terminal.
Recommend to connect an serial cable to the uart terminal Debug UART of the EVM
2.1.2. Software Dependencies (not included in SDK)¶
2.1.2.1. Code Composer Studio (CCS) - Recommend IDE¶
CCS is an integrated development environment (IDE) that supports TI’s Microcontroller and Embedded Processors portfolio. Refer to CCS Setup for J722S for steps to install and configure CCS to work with this SDK.
2.2. Demo Applications¶
The SDK and its components provide multiple applications that demonstrate some of the features of the SoC. Listed below are two different ways to run included demos (prebuilt, or build from source).
2.2.1. Running Prebuilt Demos¶
The easiest way to run a subset of the demos on the EVM is to download the and run the prebuilt demos. The prebuilt demo package includes a prebuilt linux filesystem and boot partition with demo binaries and firmware preintegrated. It is included as a tar ball from the SDK release page and can be extracted to an SD card and loaded on the board via a simple script without the need to download the source package or build anything.
Note
Only Linux-based Vision Apps Demos are available in the prebuilt package. For RTOS-based MCUSW, MCU-PLUS-SDK demos, they must be built from source (see Build Demos from Source).
2.2.2. Build Demos from Source¶
If you would like access to more demos not included in the prebuilt demo package, or you would like to modify or create custom demos, then you will need to at least download the PROCESSOR SDK RTOS source package.
Important
Windows build of SDK is currently not supported for J722S.
2.2.2.1. Building on a Linux PC¶
Important
To build many of the demos in this SDK, the companion HLOS package may also need to be download separatly; either Processor SDK Linux or Processor SDK QNX.
Download and Untar the SDK tar ball ti-processor-sdk-rtos-j722s-evm-xx_xx_xx_xx.tar.gz
cd {path/to/file}
tar xf ti-processor-sdk-rtos-j722s-evm-xx_xx_xx_xx.tar.gz
Different components in the SDK have different demos. Please refer to the below table to get started with which demo domain you are interested in.
Topic |
Documentation Links |
Camera, ADAS, Vision, Linux/QNX, OpenVX, Deep Learning (TIDL) |
See vision apps [LINK] |
RTOS Device Drivers |
See MCU-PLUS-SDK [LINK] |
HS Device Development |
See developing-with-hs-devices |