1.01
- OMAPS00081737 - Race condition can happen in DSKT2_freeAlg
- Also tracked as SDSCM00007366 - DSKT2_freeAlg and lazy
deactivate race condition
- OMAPS00079468 - ACPY3_activate causing DMA transfer when built
with -o3
- OMAPS00078941 - ACPY3_wait() inline version not inlining
- OMAPS00078784 - DSKT2 needs an API to deactivate all algs that have
been lazily deactivated
- Also tracked as SDSCM00006538 - DSKT2's lazy deactivate can cause
problems when power management is introduced
- This was satisfied with the introduction of
DSKT2_deactivateAll()
- OMAPS00079710 - DSKT2 should not try to deactivate an codec instance
that does not provide algDeactivate()
- OMAPS00076836 - DSKT2 can introduce some cache coherence issues
- Also tracked as SDSCM00005847 - DSKT2 doesn't BCACHE_flush
MEM_calloc initialized external, persistant data
- OMAPS00074261 - Support Visual Studio builds of dman3 and acpy3
libraries
- OMAPS00074262 - Fix CPU copy version of ACPY3 library
- Added DSKT2 documentation to the configuration reference guide
The Framework Components packages are available in the "packages/"
subdirectory of the product. If you have a previous release of the
Framework Components product, you can install this release next to it, and
modify your application and/or server builds to use this newer release.
If you're using the EZSDK, this can be done by setting the
FC_INSTALL_DIR variable in the Rules.make file at the
top of the EZSDK distribution directory.
Note, if you're upgrading from a release earlier than Framework Components 3.23.03.17, be
sure to review the Upgrade section for each of the releases between
your current FC release and this one. Previous release notes are
available in the relnotes_archive directory.
The details provided below describe each package's compatibility with the
previous release (framework_components_3_23_03_17).
Note, the Configuration Reference Guide contains
further details about each package.
| Package |
framework_components_3_23_03_17 |
framework_components_3_24_01_12 |
| ti.sdo.fc.dskt2 |
1, 0, 4 |
1, 0, 4 |
| ti.sdo.fc.ecpy |
1, 0, 1 |
1, 0, 1 |
| ti.sdo.fc.edma3 |
3, 0, 0 |
3, 0, 0 |
| ti.sdo.fc.global |
1, 0, 0 |
1, 0, 0 |
| ti.sdo.fc.ires |
2, 0, 0 |
2, 0, 0 |
| ti.sdo.fc.ires.bufres |
1, 0, 0 |
1, 0, 0 |
| ti.sdo.fc.ires.edma3chan |
1, 0, 0 |
1, 0, 0 |
| ti.sdo.fc.ires.hdvicp |
1, 0, 1 |
1, 0, 1 |
| ti.sdo.fc.ires.nullresource |
1, 0, 0 |
1, 0, 0 |
| ti.sdo.fc.ires.tiledmemory |
1, 0, 0 |
1, 0, 0 |
| ti.sdo.fc.ires.vicp |
1, 0, 1 |
1, 0, 1 |
| ti.sdo.fc.memutils |
1, 0, 0 |
1, 0, 0 |
| ti.sdo.fc.rman |
2, 0, 0 |
2, 0, 0 |
| ti.sdo.fc.utils |
1, 0, 3 |
1, 0, 3 |
| ti.sdo.fc.utils.osalsupport |
1, 0, 0 |
1, 0, 0 |
| ti.sdo.tiler |
1, 0, 0 |
1, 0, 0 |
The following packages that were in the previous release have been removed
from this release.
| Package |
Compatibility key |
| ti.sdo.fc.utils.api |
1, 0, 0 |
If migrating from a release prior to FC 3.21, consult previous
releases available in the relnotes_archive directory.
Compatibility Key Definitions
Compatibility keys are intentionally independent of Marketing product
numbers and are intended to:
- Enable tooling to identify incompatibilities between components,
and
- Convey a level of compatibility between different releases to
set end user expectations.
Compatibility keys are composed of 3 comma-delimited numbers - M,S,R
- where:
- M = Major. A difference in M indicates a break in
compatibility.
- S = Source. A difference in S indicates source
compability. That is, the user's source doesn't require change, but
does require rebuilding.
- R = Radix. A difference in R indicates an introduction
of new features, but compatibility with previous interfaces has not
broken. If libraries are provided by the package, an application
must re-link with the new libraries, but not rebuild from source.
This release supports the following devices:
- C6A8149:
- single-processor C674 device, running SYS/BIOS
- single-processor A8 device, running Linux
- single-processor EVE device, running SYS/BIOS
- single-processor Cortex M3 device, running SYS/BIOS
- TI811X:
- single-processor C674 device, running SYS/BIOS
- single-processor Cortex A8 device, running Linux
- single-processor Cortex M3 device, running SYS/BIOS
- TI816X:
- single-processor C674 device, running SYS/BIOS
- single-processor Cortex A8 device, running Linux
- single-processor Cortex M3 device, running SYS/BIOS
- TI814X:
- single-processor C674 device, running SYS/BIOS
- single-processor Cortex A8 device, running Linux/QNX
- single-processor Cortex M3 device, running SYS/BIOS
- TI813X:
- single-processor Cortex A8 device, running Linux
- single-processor Cortex M3 device, running SYS/BIOS
- OMAP4430:
- single-processor C64T device, running SYS/BIOS
- single-processor Cortex A9 device, running Linux
- single-processor Cortex M3 device, running SYS/BIOS
- C6472 C6474:
- Multiple C64P processors, running SYS/BIOS
- C6678 C6670:
- Multiple C66 processors, running SYS/BIOS
- OMAP3530:
- single-processor, DSP-only configuration, running SYS/BIOS
- single-processor Cortex A8 device, running Linux
- OMAP-L138:
- single-processor, DSP-only configuration, running SYS/BIOS
- single-processor ARM9 device, running Linux
This release was built and validated against using the following software
components. Please use the versions below or any other that are compatible with the below:
- XDAIS 7.24.00.04
- XDCtools 3.25.00.48
- SYS/BIOS 6.35.01.29
- EDMA3 Resource Manager 02.11.07.04
- Pre-built binaries were built with the following toolchains:
- qnx.targets.arm.Qnx - 4.4.2
- ti.targets.C64P - 7.2.0
- ti.targets.C674 - 7.2.0
- ti.targets.arm.elf.A8F - 5.0.1
- ti.targets.arm.elf.M3 - 5.0.1
- ti.targets.arm.elf.M4 - 5.0.1
- ti.targets.arp32.elf.ARP32 - 1.0.0
- ti.targets.elf.C64P - 7.2.0
- ti.targets.elf.C64T - 7.2.0
- ti.targets.elf.C66 - 7.2.0
- ti.targets.elf.C674 - 7.2.0
This release was validated using the following hardware platforms. Note
that more devices are supported, but validation was only performed on
a subset:
C674
M3
C66
TI816X
-
For the TI816X platform, there are issues when performing internal
memory transfers using DMA on the C674. The internal memory addresses
seem to be wrongly interpreted when the Channel Controller queue
priorities (or the QUEPRI register) are set to either 3 or 7. When using the ti.sdo.fc.edma3.Settings module, make sure you configure
priorities to be something other than 3 or 7.
ECPY
-
ECPY, the APIs for thew new function library for performing DMA
transfers using the IRES EDMA3CHAN2 handle are "experimental".
New APIs/features will likely be added in upcoming releases/patches.
EDMA3
-
The level of support for devices that have multiple EDMA3 hardware
instances is limited. E.g, OMAP-L138 devices have 2 EDMA3
hardware instances; the DMA related modules of Framework Components
let you configure/access only one of those devices at a time. No
support is available, as yet, for concurrent management/access to mutiple
EDMA3 Transfer Controllers.
Framework Components examples and instructions are located in the
"examples" directory.
This product's version follows a version format, M.mm.pp.bb,
where M is a single digit Major number, mm is 2 digit
minor number, pp is a 2 digit patch number, and b is an
unrestricted set of digits used as an incrementing build counter.
To support multiple side-by-side installations of the product, the
product version is encoded in the top level directory,
ex. framework_components_3_24_01_12.
Subsequent releases of patch upgrades will be identified by the patch
number, ex. FC 3.24.01.XX with directory framework_components_3_24_01_XX.
Typically, these patches only include critical bug fixes.
Questions/issues regarding this release may be posted at the E2E forum at http://e2e.ti.com/support/embedded/default.aspx
Check the following web site for updates: http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/fc/index.html
Last updated: July 23, 2013
