%%{ var target = $args[1]; /* Versioning */ var quality = ["_pre-alpha","_alpha","_beta",""]; var ver = this.version; var ver_string = ver[0] + "_" + ver[1] + "_" + ver[2] + "_" + ver[3] + quality[ver[4]]; /* Get UPPER and lower case bundle name */ var packageL = this.bundlename; var packageU = this.bundlename.toUpperCase(); /* Create documentation names */ var userManualHtml = packageU + "_Users_Manual.html"; var userManualChm = packageU + "_Users_Manual.chm"; var swManifest = packageU + "_Software_Manifest.html"; switch(target) { case "c66x": var testReport = "DSPLIB_C66x_TestReport.html"; break; case "c64Px": var testReport = "DSPLIB_C64Px_TestReport.html"; break; case "c674x": var testReport = "DSPLIB_C674x_TestReport.html"; break; } var releaseNotes = packageL + "_" + ver_string + "_release_notes.html"; /* Create table of supported devices */ var TRGCNT = this.targs.length; var DEVICES = []; var ENDIANS = []; var FORMATS = []; for (var k=0; k * *

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 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__INSTALL_DIR, * where target is C64PX, C674X, or C66X. * *
* *

Fixed Bugs

* No bugs were fixed in this release. * * *
* *

Upgrade and Compatibility Information

* * This version of `packageU` 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: * * * * *
* *

Validation Information

* * 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. * *
* *

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 `packageU` library should be directed to one of the following forums based on * the device that this library is used for: * - E2E Support Forums for AM335x, AM437x, and AM57xx * - E2E Support Forums for K2H, K2K, K2E, K2L, K2G, C665x, and C667x * - E2E Support Forums for OMAP-L13x and C674x * * Please include the text "`packageU`" 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 compatibilityThe package consumer is required to re-write the calling source code to use the package
2 (S=Source)Source compatibilityThe package consumer’s source code doesn't require change, but does require a recompile
3 (R=Radix)Introduction of new featuresCompatibility 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 onlyIf 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 revisionIncremented 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 revisionIncremented 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 numberIncremented for all other source code changes. This include any packaging support * code.
4 (b=build)Build numberIncremented for each release delivery to CM. Reset for any change to M, m or p
* */