Framework Components 1.00

This Framework Components release is specifically targetted to Joule devices.

This release note is divided into the following sections: General Info, Whats_New, Device Support, Known Issues, Directory Contents, Validation Info, Documentation.


General Information

The Framework Components are a collection of framework-independent utility libraries which other software frameworks can build upon.

The current scope of this Framework Components release is only to support Joule devices, although the charter of Framework Components doesn't limit it to Joule.

The Framework Components consists of the following packages:

The Framework Components are provided as libraries, without sources.

Additionally, this release includes an "fctools" directory containing xDAIS interface headers for convenience. These headers are identical to the xDAIS 5.00 Beta 2 Release.


What's New

This is the initial Framework Components 1.00 release.

The DMAN3 package contains an example reference application along with a complete xDAIS compliant algorithm (FCPY_TI) which implements the IDMA3 and uses ACPY3 to exercise DMA services. The reference application is built in two flavors:

  1. DAVINCISIM_BIOS: A DSP/BIOS application harness.
  2. DAVINCISIM_NOBIOS: A Non DSP/BIOS application harness (using RTS instead.)

Both flavors link against the same DMAN3, ACPY3 and algorithm binaries, and share common application layer code. However, the non-BIOS variant includes a custom BIOS adaptation layer which provides the BIOS MEM and HWI functionality needed by DMAN3 and ACPY3 libraries. This thin BIOS adaptation layer is provided as reference only, and can be replaced or customized by other non-BIOS based frameworks where DMAN3/ACPY3 functionality is needed.


Device Support

This release supports and has been tested on the following devices:

DMAN3 and ACPY3 can be configured to run on other Joule devices, (e.g. Himalaya), by configuring DMAN3.qdmaPaRamBase via RTSC or at runtime by setting DMAN3_PARAMS.qdmaPaRamBase. Additionally, when DMAN3 is not configured as a RTSC package the application must set the _DMAN3_EDMA3BASE in the linker cmd file as shown in the DMAN3 fastcopytest example.

Applications which use ACPY3 but don't consume DMAN3 as a RTSC package will need to define DMAN3_EDMA3BASE symbol in their application linker command file. For Davinci and 2430 this should be set as: _DMAN3_EDMA3BASE = 0x01C00000; An example of this usage is shown in ti/sdo/fc/dman3/examples/davincisim_bios/fastcopytest.cmd


Known Issues

DSKT2

ACPY3

ACPY3


Directory Contents

The packages/ti/sdo/fc folder contains:

The packages\ti\fc\dman3\examples folder contains:

More details can be found in the included documentation in the 'docs' folder.

Note that TI has plans on continually updating/optimizing this code. Users are encouraged to take this code as a baseline for further optimization.


Validation

This release was built and validated against using the following components:

C64+


Documentation

The following documentation is available in this release:


Last updated: April 20, 2006