TIOVX Release Notes
Version: 11.00.00
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 |
|---|---|
| TIOVX-1606 | TIOVX shall support the Khronos Supplementary Data Extension |
| TIOVX-2108 | TIOVX shall support the Khronos pipelining 2.0 extension |
| TIOVX-2220 | Safe cast support for raw image |
Upgrade and Compatibility Information
| File(s) | Change description | User application change required | User application recompile required |
| include/TI/soc/tivx_soc_< soc >.h | Deprecated the TIVX_TARGET_IPU1_0 and TIVX_TARGET_IPU1_1. Please use the TIVX_TARGET_MCU2_0 / TIVX_TARGET_MCU2_1 instead | YES | YES | include/TI/tivx_event.h | Deprecated the TIVX_EVENT_TIMEOUT_WAIT_FOREVER value. Please use the VX_TIMEOUT_WAIT_FOREVER value instead | YES | YES | include/TI/tivx.h | Deprecated the TIVX_ERROR_EVENT_TIMEOUT value. Please use the VX_ERROR_TIMEOUT value instead | YES | YES | include/VX/vx_khr_pipelining.h | Migrated to the Pipelining 2.0 specification | YES | YES |
The tivxSetGraphPipelineDepth API will be deprecated in the 11.1 SDK. In place of this API, please use the vxSetGraphAttribute with the VX_GRAPH_PIPELINE_DEPTH attribute as is implemented in the Pipelining 2.0 extension.
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):
- C7000 Code Generation Tools version: 5.0.0.LTS
- C6000 Code Generation Tools version: 8.3.7
- GCC ARM Linux Code Generation Tools version: 13.3
- TI ARM LLVM Code Generation Tools version: 3.2.2.LTS
Dependencies (included in Processor SDK RTOS):
- VXLIB version: 1.1.7.0
- Processor SDK RTOS version: 11.00.00
Dependencies (NOT included in Processor SDK RTOS):
- GCC: 11.4.0
- libpng: 1.2
Fixed Issues
| ID | Summary |
|---|---|
| TIOVX-2234 | tivxQueueDelete on RTOS returns failure when flags is set to 0 |
| TIOVX-2229 | vxSetRemapPoint/vxGetRemapPoint buffer mapping is done incorrectly |
| TIOVX-2227 | User data object initialization missing cache ops |
| TIOVX-2226 | Target acquire logic returns incorrect value in case all values are NULL |
| TIOVX-2225 | Queue functions are not using the provided timeouts |
| TIOVX-2217 | PC Emulation: Target kernel fails if previously registered for multiple “targets” |
| TIOVX-2162 | Pipelined graph hangs under certain complex scenarios |
| TIOVX-2154 | Task creation API parameters not documented clearly when used on HLOS |
| TIOVX-2153 | Task creation API includes dead code commented out |
| TIOVX-2071 | The “is_accessible” flag is not changed correctly for non-process callbacks on user kernels |
| TIOVX-2001 | QNX tivxTaskCreate - stack size is showing as 0 when we call pthread_attr_getstacksize |
Known Issues
| ID | Summary |
|---|---|
| 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-1309 | Canny robustness test failing on PC emulation with full conformance test suite |
| 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
| ID | Summary |
|---|---|
| JACINTOREQ-8494 | Defer support for standard spec implementation of raw image |
Documentation Change Log
| Chapter | Description |
|---|---|
| What is and is not in scope for TIOVX safety | Clarified current list of files that are in scope of safety for TIOVX |
| Safety Timeout Feature | Updated section to reflect current support given the upgrade to the Pipelining 2.0 extension |
| Control Callback Information | Provided more detail about requirements for the implementation of control callbacks |
| HLOS Task Implementation | Provided more detail about the implementation of the HLOS-based task API |
| Supported Specifications | Updated list of supported OpenVX specifications and extensions |
| Adding new platform files | Updated documentation to reflect new file paths of platform files |
| Supplementary Data Usage | Clarification of supplementary data usage with exemplar |
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 2024, Texas Instruments Incorporated