TIOVX Release Notes
Version: 11.02.01
Contents
- Introduction
- Licensing
- Getting Started
- Documentation
- What's New
- Upgrade and Compatibility Information
- Device Support
- Validation Information
- Fixed Issues
- Known Issues
- Change Requests
- Documentation Change Log
- Technical Support
- 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 |
|---|---|
| None | None |
Upgrade and Compatibility Information
| File(s) | Change description | User application change required | User application recompile required |
| N/A | N/A | N/A | N/A |
Device Support
| SoC | Target (OS) | Test Plaform |
|---|---|---|
| J722S | x86_64 (Linux) | x86_64 Linux with Ubuntu 22.04 |
| J722S | R5F, C7x running FreeRTOS or SafeRTOS A53 running Linux Kernel v6.12 or QNX |
J722S EVM |
Validation Information
This release was built and validated using the following tools:
Build Tools (included in Processor SDK RTOS):
- C7000 Code Generation Tools version: 5.0.0.LTS
- GCC ARM Linux Code Generation Tools version: 13.3
- TI ARM LLVM Code Generation Tools version: 4.0.4.LTS
Dependencies (included in Processor SDK RTOS):
- VXLIB version: 1.1.7.0
- Processor SDK RTOS version: 11.02.01
Dependencies (NOT included in Processor SDK RTOS):
- GCC: 11.4.0
- libpng: 1.2
Fixed Issues
| ID | Summary |
|---|---|
| TIOVX-2537 | Automation tests don't properly consider name of C7x on J722S |
| TIOVX-2530 | appMemAddTupleToList does not properly handle mmap failures |
| TIOVX-2523 | Some test kernel tests fail/crash when instrumenting C7x on J722S |
| TIOVX-2518 | vxSetGraphScheduleConfig does not properly utilize graph_parameter_index member of graph_parameters_queue_params_list |
| TIOVX-2514 | LDRA build system enables code coverage flags for all remote cores when only instrumenting one of them |
| TIOVX-2510 | tiovx conformance test testGraphPipelineDepth |
| TIOVX-2493 | Negative set image stride test uses wrong variable type to simulate failure |
| TIOVX-2479 | Negative control commands test doesn't initialize array of nodes to NULL |
| TIOVX-2443 | RTOS tivxQueue API's don't check if queue pointer is NULL before dereferencing it |
| TIOVX-2429 | tivxQueueGet ignores timeout value on remote cores if not equal to 0 or forever |
| TIOVX-2403 | ROI input to add sub kernel is not updated leading to memory corruption |
| TIOVX-2397 | Object descriptor access without checking for NULL allows possible seg fault |
| TIOVX-2383 | Remap tests fail when OpenVX host is on R5F |
| TIOVX-2381 | [Framework]: Incorrect array size in ownTargetInit API |
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-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 |
|---|---|
| Requirements of tivxReferenceImportHandle | Added clarification on subimage handling of tivxReferenceImportHandle |
| Build Configuration Examples and Workflows | Created section to explain available build configutations and common workflows |
| Supplementary Data with Composite Objects from Exemplar | Removed outdated info and added link to latest Khronos extension spec |
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