|
|
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.
The DSPLIB User's Manual provides the documentation and references necessary to integrate DSPLIB 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] |
This release of DSPLIB depends on the following libraries:
Version 3.4.0.4:
Version 3.4.0.3:
This version of DSPLIB is compatible with the last released version:
| YES | X |
|---|---|
| NO |
| Note: |
|
This release supports the following device families:
This release was built and validated using the following tools:
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.
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.
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.
Compatibility keys serve two primary purposes:
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.
| 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.
| 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 |