DSPLIB 3.4.0.4 Release Notes

January 10, 2022

DSPLIB Release Notes

Contents

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

Introduction

The TI C6000 DSPLIB is an optimized DSP Function Library for C programmers. It includes many C-callable, optimized, general-purpose signal-processing routines. These routines are typically used in computationally-intensive real-time applications where optimal execution speed is critical.


Getting Started

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


Documentation

The following documentation is available:

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

Dependencies

This release of DSPLIB depends on the following libraries:

  1. MATHLIB

What's New

  • DSPLIB test report including benchmarking is based on C6000 Compiler 8.3.2.
  • DSPLIB compilation and build is now part of Proc-SDK build process.
  • TIREX .json metadata is included in the package. It enables CCS v7 and newer to detect and install DSPLIB without going through pop-up installation window and restarting CCS. The installation folder path is COM_TI_MAS_DSPLIB_<target>_INSTALL_DIR, where target is C64PX, C674X, or C66X.

Fixed Bugs

Version 3.4.0.4:

  • PRSDK-5635: fix kernels that failed when compiled with C6000 8.3.x compiler

Version 3.4.0.3:

  • PROC_LIBS-282: Incorrect indexing in the DSPF_sp_fircirc
  • PROC_LIBS-222: Example fft_sp_ex in dsplib_c66x_3_4_0_0 does not give correct results
  • PRSDK-5250: Missing DSPF_sp_fftSPxSP_r2c result in DSPLIB test report

Upgrade and Compatibility Information

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

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

Device Support

This release supports the following device families:

  • C674x DSP (ELF, Little-Endian format)

Validation Information

This release was built and validated using the following tools:

  • XDC Tools version: 3.50.05.12
  • RTSC Packaging Standard version: 2.0
  • C6000 Code Generation Tools version: 8.2.2
  • Code Composer Studio version: 8.1

Please note that the Test Report was still based on Code Generation Tools 7.4.2. The kernel cycle numbers were not measured in this release and may be different from prior releases.


Rebuilding DSPLIB

To rebuild DSPLIB, clone the git repo at https://git.ti.com/ep-processor-libraries/dsplib and follow build instructions in readme.txt in root folder.


Known Issues


Technical Support

Questions regarding the DSPLIB library should be directed to one of the following forums based on the device that this library is used for:

Please include the text "DSPLIB" in the title and add "C66x" or "C674x" or "C64x+" 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.

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.

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