TIOVX Release Notes
Version: 01.01.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 J7 Pre-Silicon 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 |
[HTML]
|
TIOVX User Guide for J7 PreSi |
Build instructions, additional information related to J7 Pre Si platform |
[HTML]
|
TIOVX Tutorial Guide |
Step by step tutorials to get started with OpenVX and TIOVX |
[HTML]
|
PyTIOVX User Guide |
OpenVX application code generator tool |
[HTML]
|
Test Reports |
Misra C reports, conformance test reports, TI platform test reports |
[FOLDER]
|
Software Manifest |
Licenses, terms of use |
[HTML]
|
What's New
Here are a few of the new features supported in this release:
-
[TIOVX-82] - Support TI Extension OVX node for J7 VPAC.VISS processing for 64b PC emulation mode
-
[TIOVX-83] - Support TI Extension OVX node for J7 VPAC.LDC processing for 64b PC emulation mode
-
[TIOVX-84] - Support TI Extension OVX node for J7 VPAC.MSC processing for 64b PC emulation mode
-
[TIOVX-85] - Support TI Extension OVX node for J7 VPAC.NF processing for 64b PC emulation mode
-
[TIOVX-86] - Support TI Extension OVX node for J7 DMPAC.DOF processing for 64b PC emulation mode
-
[TIOVX-87] - Support TI Extension OVX node for J7 DMPAC.SDE processing for 64b PC emulation mode
-
[TIOVX-88] - Support tivx function to do format conversion based on VPAC/DMPAC C model requirements
-
[TIOVX-163] - Build: Add 64b emulation mode support
-
[TIOVX-166] - Build: Support for TIOVX to optionally build separate workarea directories for both custom applications and custom kernels
-
[TIOVX-167] - Support for loading and saving PNG images to and from vx_image objects
-
[TIOVX-168] - Support TI Extension OVX node to visualize DOF output
-
[TIOVX-170] - Support ability for target kernel registration using kernel name string as input instead of kernel enumeration
-
[TIOVX-190] - Support ability for user to query node target
Upgrade and Compatibility Information
File |
Change description |
User application change required |
User application recompile required |
include\TI\tivx.h |
Added new TI specific attribute TIVX_NODE_TARGET_STRING for node object |
NO |
NO |
include\TI\tivx.h |
Added new API tivxCreateNodeByKernelName to create a node using kernel name as input |
NO |
NO |
include\TI\tivx_obj_desc.h |
Changed value of #define TIVX_KERNEL_MAX_PARAMS Added more fields in tivx_obj_desc_node_t |
NO |
YES |
include\TI\tivx_queue.h |
Added new APIs tivxQueuePeek, tivxQueueIsEmpty |
NO |
NO |
include\TI\tivx_target_kernel.h |
Added new APIs tivxAddTargetKernelByName |
NO |
NO |
Device Support
SoC |
HOST (OS) |
Target (OS) |
Test Plaform |
J7 PreSi | x86_64 (Linux) |
x86_64 (Linux) |
x86_64 Linux PC |
Validation Information
This release was built and validated using the following tools:
Build Tools (included in Processor SDK RTOS Automotive):
-
C7000 Code Generation Tools version: 1.0.0A18023
Dependencies (included in Processor SDK RTOS Automotive):
-
VXLIB version: 1.1.1.0
-
Processor SDK RTOS Automotive version: 0.1.0.0
Dependencies (NOT included in Processor SDK RTOS Automotive):
-
GCC: 5.4.0
-
libpng: 1.2
-
OpenCV: 2.4.9
Refer user guide [HTML]
for instructions to install and setup above dependancies.
Fixed Issues
-
[TIOVX-157] - "make clean" does not clean generated libs in lib folder
-
[TIOVX-165] - Heterogeneous target support for the same kernel
-
[TIOVX-180] - Error Logs in Conformance Tests
-
[TIOVX-181] - vxCreateScalar should allow for NULL pointers but throws error from vxCopyScalar
-
[TIOVX-182] - vxQueryLUT option VX_LUT_OFFSET is not supported
-
[TIOVX-183] - vxSetMetaFormatAttribute in kernel host validate are called incorrectly
-
[TIOVX-185] - Metas not set for low image output of Laplacian Pyramid kernel
-
[TIOVX-194] - Remove error prints from target
-
[TIOVX-195] - Off-by-one error for querying VX_CONTEXT_UNIQUE_KERNEL_TABLE
-
[TIOVX-197] - Halfscale Gaussian Validate missing width/height verification
-
[TIOVX-205] - Laplacian Pyramid validate fails per 1.1 spec
-
[TIOVX-206] - Laplacian Reconstruct validate fails per 1.1 spec
-
[TIOVX-208] - Laplacian Pyramid validate does not verify output image size
-
[TIOVX-209] - Laplacian Reconstruct validate does not verify input image size
Known Issues
-
VXLIB-371: Multiply iS16 iS16 oS16 with 1/255 as scaling factor fails for X86 target
-
TIOVX-24: Some Harris Corners test cases fails for when running entire test suite
-
TIOVX-148: Performance numbers errors. There are some kernels that have graph performance faster than node performance.
-
TIOVX-155: Test case failures on TDA2 without BAM for Harris Corner test
-
TIOVX-164: In x86_64, some replicate with Pyramid testcases fail
-
TIOVX-207: tivxMaxNodes test case is failing in x86_64 PC emulation
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 2018, Texas Instruments Incorporated