VXLIB Release Notes

Mar 14, 2022

VXLIB Release Notes


  1. Introduction
  2. Licensing
  3. Getting Started
  4. Documentation
  5. What's New
  6. Upgrade and Compatibility Information
  7. Device Support
  8. Validation Information
  9. Known Issues
  10. Technical Support


The VXLIB package comprises the Texas Instruments Vision Library package together with the software tools (SWTOOLS) and all dependent packages in bundle format to simplify the release procedure.


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.

Getting Started

The VXLIB User's Manual provides the documentation and references necessary to integrate VXLIB Library routines into a development platform.


The following documentation is available:

User's Manual [HTML]
Test Report [HTML]
Software Manifest [HTML]
Release Notes Archive [LINK]

What's New

The following new features were added as compared to 1.1.6:

The following support was removed as compared to 1.1.6:

The following issues were resolved:

  1. VXLIB-689: Concerto build warning: No such file or directory

Upgrade and Compatibility Information

This version of VXLIB is compatible with the last released version:


The package compatibility key for this release is found in the packages\ti\vxlib\package.xdc file.

  1. Package compatibility keys are independent of component release versions. For more information visit: Package Versioning and Compatibility

This section contains details about compatibility of APIs between this release and

Interface file Change in user application required? Change details

Device Support

This release supports the following device families:

Validation Information

This release was built and validated using the following tools:

Known Issues

  1. VXLIB-371 : VXLIB_multiply_i16s_i16s_o16s with 1/255 as scaling factor fails for X86 target (low priority)
  2. Need to add bam_plugin support to more kernels.

Technical Support

Questions regarding the VXLIB library should be directed to the Texas Instruments Automotive E2E Forum. Please include the text 'VXLIB' in the title and add 'C66' and VXLIB tags to your post.

Package Versioning and Compatibility

Compatibility Keys

Compatibility keys serve two primary purposes:

  1. Enable tooling to identify incompatibilities between components
  2. Convey a level of compatibility between different releases to set end user expectations.

Each compatibility key is composed of 4 comma-delimited numbers - represented here by the letters M, S, R and P [M,S,R,P]. The table below provides a descriptive reference for compatibility key intention.

Compatibility Key Reference
Key Meaning Description
1 (M=Major) Break in compatibility The package consumer is required to re-write the calling source code to use the package
2 (S=Source) Source compatibility The package consumerís source code doesn't require change, but does require a recompile
3 (R=Radix) Introduction of new features Compatibility with previous interfaces is not broken. If libraries are provided by the package, an application must re-link with the new libraries, but is not required to recompile its source
4 (P=Patch) Bug fixes only If libraries are provided by the package, an application must re-link with the new libraries, but is not required to recompile its source.


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.

Package Version Reference
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 2022, Texas Instruments Incorporated