TIOVX Release Notes
Version: 10.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
- Documentation Change Log
- 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] |
FMEA | Failure modes and effects analysis of TIOVX framework, platform and utils layers | Available upon request. |
What's New
ID | Summary |
---|---|
TIOVX-1605 | TIOVX shall support the swap/move/copy extension from Khronos |
TIOVX-1501 | Improve and simplify the code for debug levels in OpenVX |
TIOVX-1493 | [TIOVX]: API to Query Resource State & status |
TIOVX-1185 | [SAFETY] TI OpenVX shall be safety compliant to FSQ process (ASIL B) |
TIOVX-1184 | TIOVX shall report out with explanation benchmark numbers on IPC with OpenVX overhead |
Upgrade and Compatibility Information
File(s) | Change description | User application change required | User application recompile required |
(New) include/TI/tivx_log_stats.h | Separated resource logging items into dedicated file | YES | YES |
source/platform/psdk_j7/common/tivx_perf.c | Added new TIOVX performance APIs into dedicated file | NO | YES |
(New) source/framework/vx_copy_swap.c | Framework support for new swap and move kernels with bidirectional parameters has been added | NO | YES |
include/TI/soc/tivx_config_* source/framework/vx_log_resource |
Support for new configuration parameter TIVX_GRAPH_MAX_PARAM_REFS added | NO | YES |
include/TI/tivx_debug.h (New) source/include/tivx_debug.h |
New APIs for printing debug information based on node, graph, and kernel have been added | NO | 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.6 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: 4.1.0.LTS
- C6000 Code Generation Tools version: 8.3.7
- GCC ARM Linux Code Generation Tools version: 13.3
- TI ARM LLVM Code Generation Tools version: 3.2.2.LTS
Dependencies (included in Processor SDK RTOS):
- VXLIB version: 1.1.7.0
- Processor SDK RTOS version: 10.01.00
Dependencies (NOT included in Processor SDK RTOS):
- GCC: 5.11.0
- libpng: 1.2
Fixed Issues
ID | Summary |
---|---|
TIOVX-2051 | Setting stride alignment does not also update total mem size |
TIOVX-1971 | Improper status check when sending commands/control commands in vx_context |
Known Issues
ID | Summary |
---|---|
TIOVX-2071 | The “is_accessible” flag is not changed correctly for non-process callbacks on user kernels |
TIOVX-2001 | QNX tivxTaskCreate - stack size is showing as 0 when we call pthread_attr_getstacksize |
TIOVX-1782 | [LINUX] Array test case failing with migration to GCC13.2 compiler |
TIOVX-1453 | Linux: APIs like vxSwapImageHandle, tivxReferenceImport and export handles does not consider dma_buf_fd |
TIOVX-1432 | subset of tivxGraphPipeline.ReplicateImage2 test cases fail when run via ssh |
TIOVX-1309 | Canny robustness test failing on PC emulation with full conformance test suite |
TIOVX-1023 | tivxGraphPipeline.MaxDataRef disabled due to failure caused by boundary condition |
TIOVX-569 | Bmp utils do not work for loading RGBX images |
Change Requests
NoneDocumentation Change Log
Chapter | Description |
---|---|
PyTIOVX User Guide | Briefly updated PyTIOVX usage documentation |
What is and is not in scope for TIOVX safety | Clarified list of files that fall outside of the scope of safety for TIOVX |
tivxNodeSendCommand() | Added documentation for real-time sending/receiving node information API |
OpenVX Swap and Move kernel Extension | Added documentation for swap and move kernel extension |
Debug Print Statements | Updated documentation for global debug logging levels |
Maintaining Graph and Node Debug Levels | Added documentation for new graph, node, and kernel print APIs |
Virtual Objects | Clarified spec interpretation on all virtual objects, virtual object arrays, and virtual pyramids |
Available Targets on Each Core | Created SoC-specific tables detailing the targets available on each core |
J721E Linux IPC Overhead Report | Included IPC Overhead Report with updated performance datasheet |
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 2024, Texas Instruments Incorporated