TIOVX Release Notes
Version: 01.08.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
Here are a few of the new features supported in this release:
Framework Features
- TIOVX-705: Framework shall support ability to run from multiple processes in Linux
- TIOVX-847: TIOVX shall use POSIX semaphore to protect object descriptor allocation
- TIOVX-848: TIOVX object descriptors shall request unique IPC ports
- TIOVX-845: TIOVX framework shall not allow graph and node events to be created after graph verification
- TIOVX-850: TIOVX pipelining shall allow the same input parameter to be enqueued to multiple nodes
- TIOVX-780: Create documentation for how to add new targets
- Significant number of MISRAC violation fixes (work in progress)
- TIOVX-813: TIOVX MSC node shall support input crop parameters for each output as user config via control command
- TIOVX-672: tivx_vpac_msc_coefficients_params_init shall initialize coefficients based on user provided interpolation type
- TIOVX-706: TIOVX shall support TI extension kernel for H.264 video encoder
- TIOVX-884: TIOVX shall support TI extension kernel for multi-channel H.264 video encode
- TIOVX-809: TIOVX capture node shall support 8 homogeneous cameras from multiple CSI ports
- TIOVX-880: TIDL node shall support trace output parameter for ease of debug
Upgrade and Compatibility Information
File | Change description | User application change required | User application recompile required |
kernels_j7\include\TI\j7_capture.h | Modifying tivx_capture_params_t configuration data structure input for multi-CSI channel support | YES | YES |
kernels_j7\include\TI\j7_vpac_msc.h | tivx_vpac_msc_output_params_t ranges changed for x/y offset, defaults have changed for the init functions, tivx_vpac_msc_coefficients_params_init() takes new parameter for interpolation type | YES | YES |
kernels\include\TI\tivx_nodes.h | Added new optional trace output parameter for TIDL node | YES | YES |
include\TI\*.h | Added const qualifier to several API's (MISRAC) | 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 v4.19 |
Jacinto7 EVM |
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.2.0.STS
- C6000 Code Generation Tools version: 8.3.2
- GCC ARM Linux Code Generation Tools version: 8.3-2019.03
- TI ARM Code Generation Tools version: 18.12.1
Dependencies (included in Processor SDK RTOS Automotive):
- VXLIB version: 1.1.4.0
- TIDL version: 1.1.0.0
- Imaging version: 1.1.0.0
- Processor SDK RTOS Automotive version: 6.2.0.0
Dependencies (NOT included in Processor SDK RTOS Automotive):
- GCC: 5.4.0
- libpng: 1.2
Fixed Issues
PyTIOVX Issues
- TIOVX-868: PyTIOVX: tivxMemShared2TargetPtr incorrect params for non IMAGE, PYRAMID, OBJ ARRAY, THRESHOLD
- TIOVX-878: Pytiovx use case script error when trying to add following node to use case: NodeOpticalFlowPyrLK
- TIOVX-879: PyTIOVX: tensor object not supported for use case generation tool
- TIOVX-788: VPAC VISS Image artifacts
- TIOVX-853: All 3 VPAC MSC driver versions cropStartY not initalized
- TIOVX-854: Test checksum utility improperly sums widths not a multiple of 4 bytes
- TIOVX-856: tivxVpacMscScaleNode overwrites the init_phase x/y, and offset_x,y
- TIOVX-858: VPAC MSC control commands for CROP and OUTPUT must have array of 5 references
- TIOVX-876: tivxVpacMscPyramidNode does not bitmatch between TARGET and EMULATION mode
- TIOVX-866: OVX Decoder: color issues observed with 1080p video streams
Known Issues
- BAM DMA Acceleration is not supported in this version. Expected in future versions.
- VXLIB-371: Multiply iS16 iS16 oS16 with 1/255 as scaling factor fails for X86 target
- TIOVX-164: In x86_64, some replicate with Pyramid testcases fail
- TIOVX-207: tivxMaxNodes test case is failing in x86_64 PC emulation
- TIOVX-569: Bmp utils does not load RGBX properly
- TIOVX-630: tivxHwaVpacViss.testMux fails on target
- TIOVX-869: OVX Encoder: QCIF (176x144) resolution encoding is not working
- TIOVX-873: tivxHwaVideoDecoder allocation fails and asserts
- TIOVX-882: tivx_utils_save_vximage_to_bmpfile cannot save RGB image properly when stride_y is not multiple of 3
- Usage of object arrays while pipelining is not yet fully supported. Please see user guide pipelining section for restrictions.
- Not all valid VISS outputs are fully tested yet
- Test coverage for HWA nodes (especially VISS) still work in progress
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