TIOVX Release Notes

Version: 11.02.00


Contents

  1. Introduction
  2. Licensing
  3. Getting Started
  4. Documentation
  5. What's New
  6. Upgrade and Compatibility Information
  7. Device Support
  8. Validation Information
  9. Fixed Issues
  10. Known Issues
  11. Change Requests
  12. Documentation Change Log
  13. Technical Support
  14. Package Versioning


Introduction

The TIOVX package consists of the Texas Instruments OpenVX conformant implementation for Jacinto7 platform


Licensing

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 here [HTML].


Getting Started

The TIOVX User Guide [HTML] provides the documentation and references necessary to begin development on TI's platforms using TIOVX.


Documentation

Refer to following documentation for further details:

TIOVX User Guide Build instructions, API Guide, tutorials, tool documentation, etc [HTML]
Test Reports Conformance test reports, TI platform test reports [XLSX]
Software Manifest Licenses, terms of use [HTML]
Static Analysis Report C and C++ Taxonomy Report [XLSX]
Bidirectional Traceability Report Traceability reports of MR to FR to Test [XLSX]
FMEA Failure modes and effects analysis of TIOVX framework, platform and utils layers Available upon request.


What's New

ID Summary
TIOVX-2318 Support an object that can hold multiple “vx_tensor” objects

Upgrade and Compatibility Information

File(s) Change description User application change required User application recompile required
include/TI/tivx_ext_obj_array_from_list.h New file for APIs for creating object array from list added NO YES
include/TI/tivx_obj_desc.h Updated object array object descriptor to include member that tracks the creation method used NO YES
include/TI/soc/tivx_config_j721e.h
include/TI/soc/tivx_soc_j721e.h
Updated new defaults for certain global values. NO YES
include/TI/tivx_debug.h Updated existing debug methods and added new one for boundary conditions NO YES

Device Support

SoC Target (OS) Test Plaform
J721E x86_64 (Linux) x86_64 Linux with Ubuntu 22.04
J721E R5F, C6x, C7x running FreeRTOS or SafeRTOS
A72 running Linux Kernel v6.12 or QNX
J721E EVM

Validation Information

This release was built and validated using the following tools:

Build Tools (included in Processor SDK RTOS):

Dependencies (included in Processor SDK RTOS):

Dependencies (NOT included in Processor SDK RTOS):

Refer user guide [HTML] for instructions to install and setup above dependancies.

Fixed Issues

ID Summary
TIOVX-2372 Object Array Copy/Swap/Move Kernel Callback does not check if children are of equal metadata
TIOVX-2366 Stray VX_ZONE_ERROR print in tivxQueueGet while using events
TIOVX-2365 TIOVX Safety Manual: Audit & add all the header file part of the Delivered Artifacts
TIOVX-2361 vxCreateObjectArray insufficient checking
TIOVX-1309 Canny robustness test failing on PC emulation with full conformance test suite

Known Issues

ID Summary
TIOVX-2348 tivx(Map/Unmap)RawImagePatch cache maintains full buffer instead of mapped part
TIOVX-1782 [LINUX] Array test case failing with migration to latest Linux GCC compiler
TIOVX-1453 Linux: APIs like vxSwapImageHandle, tivxReferenceImport and export handles does not consider dma_buf_fd
TIOVX-1023 tivxGraphPipeline.MaxDataRef disabled due to failure caused by boundary condition
TIOVX-569 Bmp utils do not work for loading RGBX images

Change Requests

None


Documentation Change Log

Chapter Description
Copy Swap Kernel Extension Added clarification for Copy Swap Kernel handling of composite data objects
Using Supplementary Data with Exemplars Simplified supplementary data usage section by pointing to official Khronos extension documentation

Technical Support

For technical support and additional assistance, contact 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 2025, Texas Instruments Incorporated