Perception Toolkit (PTk) Release Notes

BETA Version:


  1. Introduction
  2. Licensing
  3. Getting Started
  4. Documentation
  5. Device Support
  6. Validation Information
  7. Known Issues
  8. Technical Support
  9. Package Versioning


The Texas Instruments Perception Toolkit (PTk) is a software package for accelerating sensing and perception capabilities, particularly for prototyping automotive and robotic applications.

PTk provides a cross-platform API that delivers identical behavior on both PC and embedded platforms.


The licensing information of this library, as well as any third-party components included which are made available under a number of other open-source licenses are enumerated as part of the manifest. A complete manifest along with export control information is detailed in the table below under "Software Manifest".

Getting Started

Currently Unavailable


Refer to following documentation for further details:

PTK User Guide Build instructions, API Guide [HTML]
Software Manifest Licenses, terms of use [HTML]

This beta release reflects on-going development of library components, algorithms, and example applications; as such, detailed documentation is somewhat limited.

Device Support

SoC HOST (OS) Target (OS) Test Plaform
J7 x86_64 (Linux) x86_64 (Linux) x86_64 Linux with Ubuntu 18.04
J7 A72 (Linux) C6x, A72 running Linux v4.19 J721e-evm, J721e-sk

Validation Information

This release was built and validated using the following tools:

Dependencies (NOT included in Processor SDK RTOS Automotive):

Known Issues

  1. None

Technical Support

For technical support and additional assistance, contact your local TI Field Application Engineer.

Package Versioning

Each package version is composed of 4 period-delimited numbers - represented here by the letters M, m, p and b [M.m.p.b]. The table below provides a descriptive reference regarding package version numbering.

Digit Meaning Description
1 (M=Major) Major revision Incremented when the new version is substantially different from the previous For example, a new module added or an existing module's algorithm significantly altered.
2 (m=minor) Minor revision Incremented when the new version has changed but not in a major way. For example, some minor changes in the API or feature set.
3 (p=patch) Patch number Incremented for all other source code changes. This include any packaging support code.
4 (b=build) Build number Incremented for each release delivery to CM. Reset for any change to M, m or p

Copyright 2022, Texas Instruments Incorporated