TIOVX Release Notes
Version: 09.01.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 | [XLSX] |
Software Manifest | Licenses, terms of use | [HTML] |
Static Analysis Report | C and C++ Taxonomy Report | [XLSX] |
Bidirectional Traceability Report | Traceability reports of MR to FR to Test | [XLSX] |
What's New
ID | Summary |
---|---|
TIOVX-736 | TIOVX shall support variable scale ratios for vxGaussianPyramidNode |
TIOVX-1406 | Create "tivx_utils_compare_refs_from_ipc_xfer" API for comparing handles sent acros processes |
Upgrade and Compatibility Information
File | Change description | User application change required | User application recompile required |
include\TI\tivx.h | When using the tivxReferenceExportHandle and tivxReferenceImportHandle API's with the image objects, the returned handles originally treated each plane separately, but now only uses a single pointer along with the size for all planes. This is aligns with how the framework allocates memory for multi-plane images. Please reference the API docs for more information. | YES | YES |
include\TI\tivx_mem.h | The return type of the tivxMemFree API has been changed from "void" to "vx_status" | YES | YES |
include\TI\tivx.h | The tivxGraphParameterEnqueueReadyRef API has been deprecated in favor of the standard vxGraphParameterEnqueueReadyRef API | YES | YES |
Device Support
SoC | Target (OS) | Test Plaform |
---|---|---|
J721E | x86_64 (Linux) | x86_64 Linux with Ubuntu 22.04 |
J721E | R5F, C6x, C7x running FreeRTOS or SafeRTOS A72 running Linux Kernel v6.1 or QNX |
J721E 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
- C6000 Code Generation Tools version: 8.3.7
- GCC ARM Linux Code Generation Tools version: 11.3
- TI ARM LLVM Code Generation Tools version: 3.2.0.LTS
Dependencies (included in Processor SDK RTOS):
- VXLIB version: 1.1.7.0
- Processor SDK RTOS version: 09.01.00
Dependencies (NOT included in Processor SDK RTOS):
- GCC: 5.11.0
- libpng: 1.2
Fixed Issues
ID | Summary |
---|---|
TIOVX-1425 | Add C++ header guard to the utilities of TIOVX |
TIOVX-1404 | [CSITX]: static local variable in CSITX does not allow running two nodes in parallel |
TIOVX-1403 | [DSS M2M] Node does not convert buffer address correctly. |
TIOVX-1399 | [CSIRX]: Overhead in converting physical buffer addresses |
TIOVX-1398 | [CSITX] Node does not convert buffer address correctly. |
TIOVX-1392 | [CSIRX]: Capture node in the OpenVX does not handle captured short/long frames |
TIOVX-1360 | Cache Maintaince operation to be removed for A72 |
TIOVX-1359 | TIDL node shall not free L2 memory in create callback |
TIOVX-1354 | QNX memory utils does not support coherent thread safety for release/reimport |
TIOVX-1352 | Non-host cores are linking host-only symbols in firmware images |
TIOVX-1340 | In TIVX_LOG_RT Tool, No of frames for VISS node is double as compared to other nodes in single-cam application |
TIOVX-1241 | Intermittent, but repeatable failures TIOVX in conformance tests |
Known Issues
ID | Summary |
---|---|
TIOVX-1432 | subset of tivxGraphPipeline.ReplicateImage2 test cases fail when run via ssh |
TIOVX-1428 | Conformance test case failure due to status check given for ownReleaseReferenceInt function call in vxReleaseKernel API |
TIOVX-1344 | Display conformance tests giving wrong output for ADAS image (J721E, J721S2, J784S4) |
TIOVX-1338 | [CSITX]: No clean exit when buffers are not enqueued |
TIOVX-1309 | Canny robustness test failing on PC emulation with full conformance test suite |
TIOVX-1297 | vxScaleImageNode Upsampling output is not as expected for fractional scaling |
TIOVX-1238 | Frame Freeze in QNX when LDC node, Mosaic node and a Display node added to SRV demo |
TIOVX-1023 | tivxGraphPipeline.MaxDataRef disabled due to failure caused by boundary condition |
TIOVX-823 | TIOVX delay parameters with pipelining result in serialization of nodes |
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-6650 | De-scope BAM enablement on J7 to SDK 10.0 | 09.01.00 | 10.00.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 2023, Texas Instruments Incorporated