TIOVX Release Notes
Version: 01.12.00.00
Contents
- Introduction
- Licensing
- Getting Started
- Documentation
- What's New
- Upgrade and Compatibility Information
- Device Support
- Validation Information
- Fixed Issues
- Known Issues
- 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 | [FOLDER] |
Software Manifest | Licenses, terms of use | [HTML] |
What's New
ID | Summary |
---|---|
TIOVX-837 | VDEC shall support I+P H264 sequence with zero memcopy |
TIOVX-773 | VDEC shall support I only H264 sequence with Zero memcopy |
Upgrade and Compatibility Information
File | Change description | User application change required | User application recompile required |
kernels_j7\include\TI\j7_video_encoder.h | Additional parameters added to tivx_video_encoder_params_t for the encoder control API | YES | YES |
kernels_j7\include\TI\j7_video_decoder.h | Application image width and height must be aligned to 64 | YES | YES |
Device Support
SoC | Target (OS) | Test Plaform |
---|---|---|
Jacinto7 | x86_64 (Linux) | x86_64 Linux with Ubuntu 18.04 |
Jacinto7 | R5F, C6x, C7x running TI-RTOS A72 running Linux v5.4 or QNX |
Jacinto7 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: 1.4.2.STS
- C6000 Code Generation Tools version: 8.3.7
- 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.5.0
- TIDL version: 02.00.00.07
- Imaging version: 07.03.00.00
- Processor SDK RTOS version: 07.03.00.00
Dependencies (NOT included in Processor SDK RTOS):
- GCC: 5.4.0
- libpng: 1.2
Fixed Issues
ID | Summary |
---|---|
TIOVX-1091 | Warp matrix index is incorrect in LDC Node |
TIOVX-1082 | Incorrect RGBX format in capture Node |
TIOVX-1031 | Encoder issue when using greater than 2 instances |
TIOVX-1004 | Decoder: Issues when greater than 2 instances are run in parallel |
Known Issues
ID | Summary |
---|---|
TIOVX-1097 | Capture node is cycling only last two enqueued frames/objects |
TIOVX-1087 | MCU 2 Memory Leak in OpenVX Video Codec Tests |
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-1071 | YUV422 Capture fails after capture source is switched without reboot |
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-943 | EncDec: Encoder output cannot be directly connected to decoder |
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 |
TIOVX-968 | OVX Decoder: QCIF (176x144) resolution decoding is not working |
TIOVX-869 | OVX Encoder: QCIF (176x144) resolution encoding is not working |
TIOVX-1101 | RTOS Video Encoder: Multi channel test case not working with VGA (640x480) resolution |
VXLIB-371 | Multiply iS16 iS16 oS16 with 1/255 as scaling factor fails for X86 target |
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 2020, Texas Instruments Incorporated