MATHLIB Release Notes
Version: 02.06.00.00
Contents
- Introduction
- Licensing
- Getting Started
- Documentation
- What's New
- Upgrade and Compatibility Information
- Device Support
- Validation Information
- Fixed Issues
- Deprecation
- Known Issues
- Technical Support
- Package Versioning
Introduction
The MATHLIB package consists of the Texas Instruments optimized kernels for floating point Math algorithms.
Licensing
The licensing information of this library and a complete manifest along with export control information is detailed here [HTML].
Getting Started
The MATHLIB User Guide [USER_GUIDE] provides the documentation and references necessary to begin development on TI's platforms.
Documentation
Refer to following documentation for further details:
| MATHLIB User Guide | Build instructions, API Guide | [USER_GUIDE] |
| Test Reports | Misra C reports, conformance test reports, TI platform test reports | [TEST_RESULTS] |
| Software Manifest | Licenses, terms of use | [HTML] |
What's New
Upgrade and Compatibility Information
| File | Change description | User application change required | User application recompile required |
Device Support
| SoC | Host (OS) | Target (OS) | Test Platform |
| C7x, MMA | No OS | No OS |
Validation Information
This release was built and validated using the following tools:
Build Tools (NOT included in MATHLIB):
- C7x CGT C7000-CGT-3.1.0 LTS
Fixed Issues
- [MMALIB-569] Cos function not producing correct negative values
Known Issues
Technical Support
For technical support, please post your questions on TI E2E Forum for Automotive ADAS SoCs.
For 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 2018, Texas Instruments Incorporated