TIOVX Release Notes

Version: 08.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. Technical Support
  13. 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 [HTML]
Software Manifest Licenses, terms of use [HTML]


What's New

ID Summary
TIOVX-804 TIOVX shall support concurrent operation of 2 capture nodes, where each one is mapped to a different CSI port

Upgrade and Compatibility Information

File Change description User application change required User application recompile required
kernels_j7\include\TI\j7.h This file is deprecated and will be removed in PSDK 8.4 ... please remove its inclusion and just include TI/tivx.h. YES YES
kernels_j7\include\TI\j7.h Additional functions declaration added: tivxTVMLoadKernels / tivxTVMUnLoadKernels NO YES


Device Support

SoC Target (OS) Test Plaform
J721E x86_64 (Linux) x86_64 Linux with Ubuntu 18.04
J721E R5F, C6x, C7x running FreeRTOS
A72 running Linux Kernel v5.10 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

TIOVX-1190 tiovx/conformance_tests/test_data is only filled with git lfs versions of the files
TIOVX-1188 Code error in tivx_queue.c which could result in a deadlock scenario
TIOVX-1174 Release notes of TIOVX has broken links for test report and license
TIOVX-1172 Documentation for custom kernels was not generated
TIOVX-1171 Semaphore_create fails in single camera example
TIOVX-1168 tivxHwaVpacVIss*2a=NULL tests fail when running after a camera demo
TIOVX-1151 Display frames are repeated when display input image is connected to another m2m node

Known Issues

ID Summary
TIOVX-1164 VISS node does not support histogram module
TIOVX-1117 Failure observed when running 8+ tasks involving custom use case
TIOVX-1086 VISS mux output for R G and B planes hangs if additional outputs are not supplied
TIOVX-1072 tivxCmdTimeout.ValidTimeoutSet for A72 fails for QNX
TIOVX-1023 tivxGraphPipeline.MaxDataRef disabled due to failure caused by boundary condition
TIOVX-1005 MSC Test Case: Bitmatch validation fails when multiple conformance test instances are run in parallel
TIOVX-823 TIOVX delay parameters with pipelining result in serialization of nodes
TIOVX-630 tivxHwaVpacViss.testMux conformance test fails on target
TIOVX-569 Bmp utils do not work for loading RGBX images
VXLIB-371 Multiply iS16 iS16 oS16 with 1/255 as scaling factor fails for X86 target

Change Requests

ID Headline Original Fix Version New Fix Version
JACINTOREQ-1949 De-scope BAM enablement on J7 from 8.2 08.02.00 08.05.00
JACINTOREQ-2446 VPAC TIOVX Scope Change 08.02.00 09.00.00

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 2021, Texas Instruments Incorporated