TIOVX Release Notes
Version: 08.06.00
Contents
- Introduction
- Licensing
- Getting Started
- Documentation
- What's New
- Upgrade and Compatibility Information
- Device Support
- Validation Information
- Fixed Issues
- Known Issues
- Change Requests
- 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 | [HTML] |
| Software Manifest | Licenses, terms of use | [HTML] |
What's New
| ID | Summary |
|---|---|
| TIOVX-1296 | TIOVX shall support query attributes to provide tensor strides and image imagepatch_addressing structure |
Upgrade and Compatibility Information
| File | Change description | User application change required | User application recompile required |
| include\TI\tivx_config.h | Each SoC support in TIOVX now has its own config file used for the max values of each SoC. | NO | YES |
Device Support
| SoC | Target (OS) | Test Plaform |
|---|---|---|
| J721S2 | x86_64 (Linux) | x86_64 Linux with Ubuntu 18.04 |
| J721S2 | R5F, C7x running FreeRTOS or SafeRTOS A72 running Linux Kernel v5.10 or QNX |
J721S2 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: 3.1.0.LTS
- GCC ARM Linux Code Generation Tools version: 9.2-2019.12
- TI ARM Code Generation Tools version: 20.2.0
Dependencies (included in Processor SDK RTOS):
- VXLIB version: 1.1.7.0
- TIDL version: 08.06.00.10
- Imaging version: 08.06.00
- Processor SDK RTOS version: 08.06.00
Dependencies (NOT included in Processor SDK RTOS):
- GCC: 5.4.0
- libpng: 1.2
Fixed Issues
| ID | Summary |
|---|---|
| TIOVX-1304 | Missing links on User Guide page |
| TIOVX-1300 | Creating Nested Graph in A72 Target node create callback results in deadlock |
| TIOVX-1299 | CSITX Instance1 is not working in vision apps |
| TIOVX-1298 | [VISS]: Enabling single 12bit NV12 output does not work |
Known Issues
| ID | Summary |
|---|---|
| TIOVX-1297 | vxScaleImageNode Upsampling output is not as expected for fractional scaling |
| TIOVX-1288 | Kernel.setParameter() data_types not supported for Type.VX_TENSOR |
| TIOVX-1241 | Intermittent, but repeatable failures TIOVX in conformance tests |
| TIOVX-1238 | Frame Freeze in QNX when LDC node, Mosaic node and a Display node added to SRV demo |
| TIOVX-1164 | VISS node does not support histogram module |
| TIOVX-1086 | VISS mux output for R G and B planes hangs if additional outputs are not supplied |
| 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-5018 | De-scope BAM enablement on J7 from 8.6 | 08.06.00 | 09.01.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 2022, Texas Instruments Incorporated