TIOVX Release Notes
Version: 01.07.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:
- TIOVX-663: Framework shall support tivxGetReferenceParent API to get image parent
- TIOVX-665: tivxRawImage type shall support meta information both before and after the pixel information
- TIOVX-697: VISS node shall support GLBCE context save/restore
- TIOVX-623: VPAC LDC node shall support DCC input
- TIOVX-741: Framework shall support TI extension for user data attribute "valid size"
- TIOVX-668: TIOVX shall support TI extension kernel for H.264 video decoder
- TIOVX-661: User guide overhaul and updates.
- TIOVX-681: Change Target names from RESV* to HWA names
- TIOVX-698: Adding support to delay object for object arrays
- TIOVX-715: Change name of j7presi to psdkra as the BUILD_SDK option
Upgrade and Compatibility Information
File | Change description | User application change required | User application recompile required |
kernels_j7\include\TI\j7.h | Adding Jacinto7 specific target names for A72 and C7x instead of A15 and EVE1 | YES | YES |
kernels_j7\include\TI\j7_vpac_viss.h | Adding new config parameter: enable_ctx | YES | YES |
kernels_j7\include\TI\j7_dmpac_dof.h | Adding new input paramter for SOF configuration; removing unneded configuration parameters | YES | YES |
include/TI/tivx_ext_raw_image.h | Changed interface to support meta data before and after image data | 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.0.0.0
- Imaging version: 1.0.0.0
- Processor SDK RTOS Automotive version: 6.1.0.0
Dependencies (NOT included in Processor SDK RTOS Automotive):
- GCC: 5.4.0
- libpng: 1.2
Fixed Issues
Framework Issues
- TIOVX-674: Pipelining breaks when creating graph parameter of replicated output to object array
- TIOVX-650: Pipelining using object arrays WITHOUT replicate node is not working
- TIOVX-656: tivxGraphPipeline.DontReplicateImage fails
- TIOVX-657: Pipelining doesn't work with vxCreateImageFromROI
- TIOVX-699: Delay data reference queue does not get created in certain circumstances
- TIOVX-704: The tivxMaxNodes test case fails on J7 target
- TIOVX-721: NULL pointer error when using replicate node
- TIOVX-734: Several new bugs related to memory changes in vision apps
- TIOVX-660: PyTIOVX scalar kernel generation generates vxAddParameterToKernel incorrectly
- TIOVX-693: PyTIOVX invalid CPU ID macro is inconsistent with framework
- TIOVX-757: PyTIOVX generates incorrect parameters for pyramids
- TIOVX-702: vxuCanny vectors fail on J7 target
- TIOVX-703: tivxCanny fails on J7 target
- TIOVX-673: Channel Combine Test Cases fails for various data types
- TIOVX-719: tivxHwaDmpacSde.NegativeGraphProcessing/210 fails
- TIOVX-729: DMPAC DOF PC simulator doesn't support several HW features
- TIOVX-730: DMPAC DOF node has memory leak
- TIOVX-738: DMPAC DOF node output doesn't match c-model when TEMPORAL predictor is enabled
- TIOVX-737: DMPAC DOF node output not consistent when both predictors are set to TEMPORAL
- TIOVX-732: DMPAC DOF node output incorrect when sparse OF mode enabled on HW
- DMPAC DOF PC simulator node output incorrect when 16 bit output is used
- TIOVX-723: VPAC LDC kernel in PC emulation mode crashes with UYVY input image in ptk_demos
- TIOVX-750: VPAC LDC kernel in PC emulation mode 8bit input/output shifts up to 12 bits when it shouldn't
- TIOVX-751: VPAC LDC kernel in PC emulation mode inverts the X,Y offsets in the mesh table compared to HW
- TIOVX-752: VPAC LDC kernel in PC emulation mode crashes with NV12 output
- TIOVX-756: VPAC LDC kernel in PC emulation mode doesn't match HW output in U16 input mode
- TIOVX-755: VPAC LDC HW node failed when YUYV output enabled
- TIOVX-725: tivxHwaVpacViss.GraphProcessingFileDcc fails DCC verification on J7-EVM
- TIOVX-717: VPAC VISS: Color & Brightness oscillations in multi-camera applications
- TIOVX-740: tivxHwaVpacNfBilateral failing on target
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-24: Some Harris Corners test cases fails for when running entire test suite
- 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-652: Some apps sometimes hangs during exit
- 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 MSC and 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 2019, Texas Instruments Incorporated