index 017c9d4d15573057baf75ffe14f6b18321c2bf89..cc0e637b6d370190d56486bb81fd4345c8981ba4 100755 (executable)
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html xmlns="http://www.w3.org/TR/REC-html40">
-<head>
- <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
- <meta http-equiv="Content-Type" content="text/html">
- <title>EDMA3 LLD 02.11.11 Release Notes</title>
- <style type="text/css">
-body
-{
- color: #000 ;
- background-color: #fff ;
- margin : 5px 20px 5px 20px;
- font-family: Tahoma, Arial, Helvetica, sans-serif;
- font-size: 10pt ;
-}
-
-a,
-a:link,
-a:visited,
-
-{
- color : #1a41a8 ;
-}
-
-a:hover
-{
- color : #2a3798 ;
-}
-
-img
-{
- text-decoration : none ;
-}
-
-p
-{
- color: #000 ;
-}
-
-table.tagline
-{
- width: 100%;
-}
-
-li
-{
- color : black ;
-}
-
-.title
-{
- text-align : center ;
-}
-
-th
-{
- text-align : left ;
-}
- </style>
-</head>
-<body>
-<table border="0" cellpadding="0" cellspacing="0" width="100%">
- <tbody>
- <tr>
- <td
- style="background: black none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"
- width="222"> <a href="http://www.ti.com/"><img id="_x0000_i1025"
- src="docs/html/tilogo.gif" alt="Texas Instruments" border="0"
- height="54" width="222"> </a></td>
- <td
- style="background: red none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;">
- <img id="_x0000_i1026" src="docs/html/titagline.gif"
- alt="Technology for Innovators(tm)" border="0" height="26" width="314">
- </td>
- </tr>
- </tbody>
-</table>
-<h1 class="title">EDMA3 LLD 02.11.11 Release Notes</h1>
-<h2 class="title">Dec 27, 2013</h2>
-<p>
-This EDMA3 Low Level Driver Release is targeted to the users (device
-drivers
-and applications) for submitting and synchronizing with EDMA3 based DMA
-transfers.
-This release supports DA830,C6748,TCI6498,TI816X,C6472,TCI6486,TI814X,TI816X,TI811X,TCI6608,TCI6616,TCI6614,C6670,C6678,TCI6638K2K,TDA2xx platforms, on
-SYS/BIOS 6 side & OMAPL138 on SYS/BIOS and ARM side. Porting
-instructions
-are also provided to use the package for different platforms and
-Operating
-Systems.
-</p>
-<p>
-<a href="#Introduction">Introduction</a>,
-<a href="#Documentation">Documentation</a>,
-<a href="#Whats_New">What's New</a>,
-<a href="#Upgrade_Info">Upgrade Info</a>,
-<a href="#Device_Support">Device Support</a>,
-<a href="#Compatibility">Compatibility Information</a>,
-<a href="#Validation">Validation Info</a>,
-<a href="#Known_Issues">Known Issues</a>,
-<a href="#Examples">Examples</a>,
-<a href="#Version">Version Information</a>,
-<a href="#Support">Technical Support</a>
-</p>
-<hr>
-<a name="Introduction"></a>
-<h2><a name="Introduction">Introduction</a></h2>
-<p>
-EDMA3 LLD is a single product package containing the following
-stand-alone
-software components:
-</p>
-<ul type="disc">
- <a name="Introduction"> <li> <b>EDMA3 Resource Manager</b> - TI
-mandated library for all EDMA3 peripheral users to acquire and
-configure EDMA3 hardware resources (DMA/QDMA channels, PaRAM Sets, TCCs
-etc.) and DMA Interrupt Service Routines. </li>
- <li> <b>EDMA3 Driver</b> - Functional library providing APIs for
-programming, scheduling and synchronizing with EDMA transfers and many
-more. </li>
- </a>
-</ul>
-<p>
-EDMA3 Resource Manager can be used independently whereas the EDMA3
-Driver requires
-the Resource Manager services internally.
-</p>
-<p>
-EDMA3 LLD (both Resource Manager and the Driver) is a platform
-independent package.
-Hence it can be used across multiple platforms. Porting instructions
-are provided for both the components to do the same.
-</p>
-<p>
-It is also an OS-agnostic package and thus can be used across multiple
-operating
-systems. OS-adaptation layer needs to be provided by the user (in case
-it is needed)
-for OS customization. Instructions to do the same are also provided
-along with
-the package.
-</p>
-<p>
-The Low Level Driver has already been ported (SYS/BIOS Operating
-Systems)
-and tested on various platforms mentioned below. Sample initialization
-libraries,
-which configure the EDMA3 hardware and provide the necessary OS
-abstraction layer,
-are also a part of the package. These libraries are available both for
-the EDMA3
-Resource Manager and EDMA3 Driver. These could be used for proper
-initialization of the software component(s) along with the OS
-adaptation layer
-for the same.
-</p>
-<p>
-The Low Level Driver consists of the following packages:
-</p>
-<ul type="disc">
- <a name="Introduction"> <li> <tt><b>ti.sdo.edma3.rm</b></tt> -
-EDMA3 Resource Manager. </li>
- <li> <tt><b>ti.sdo.edma3.rm.sample</b></tt> - Sample initialization
-library / OS abstraction layer for the Resource Manager. </li>
- <li> <tt><b>ti.sdo.edma3.drv</b></tt> - EDMA3 Driver. </li>
- <li> <tt><b>ti.sdo.edma3.drv.sample</b></tt> - Sample initialization
-library / OS abstraction layer for the Driver. </li>
- </a>
-</ul>
-<p><b>Note: </b>
-<ul type="disc">
- <a name="Introduction"> <li> <b>Address translation is not done in EDMA3 LLD</b> </li>
-<br>If the memory map of the EDMA is different than the host processor programming it,
-EDMA3LLD being a low level driver the address translation is not done by this. It is expected that the application
-will provide the addresses, corresponding to EDMA memory map to configure in PARAM.
-</p>
-</a>
- <a name="Introduction"> <li> <FONT COLOR ='RED'><b>All resources are allocated to all cores in default sample configuration files of EDMA3 LLD</b> </FONT></li>
-<br>The EDMA resources like Channels, PaRAMs and TCCs which are shared by multiple cores (Ex: in TI814X and TI816X),
-The default configuration file allocates all the resources to every core since the resource split is application dependant.
-The applications using EDMA3LLD should appropriately allocate the resources in the config files and build EDMA3LLD libraries.
-</p>
-</a>
- <a name="Introduction"> <li> <b>Building EDMA3LLD libs and examples on windows 7</b> </li>
-<br>On windows 7 there is a permission issue while building the libs and examples.set the environment variable CYGWIN in the command window where you are building <br> examples: $set CYGWIN=nontsec <br>You might have to manually delete the generated files before building.
-</p>
-</a>
- <a name="Introduction"> <li> <b>Platform name Vayu will Change in future release</b> </li>
-<br>The package.xs file uses platform name vayu which will change in future release based on the official name given in BIOS for vayu platform.
-</p>
-</a>
-</ul>
-<a name="Documentation">
-</a>
-<h2><a name="Documentation">Documentation</a></h2>
-<p>The following documentation is available:
-</p>
-<ul type="disc">
- <li><a href="docs/EDMA3_RM_Release_Notes.pdf">EDMA3 Resource Manager
-Release Notes</a></li>
- <li> <a href="packages/ti/sdo/edma3/rm/docs/EDMA3_RM_User_Guide.pdf">EDMA3
-Resource Manager User's Guide</a> </li>
- <li> <a href="docs/EDMA3_Driver_Release_Notes.pdf">EDMA3 Driver
-Release Notes</a> </li>
- <li> <a
- href="packages/ti/sdo/edma3/drv/docs/EDMA3_Driver_User_Guide.pdf">EDMA3
-Driver User's Guide</a> </li>
- <li> EDMA3 Resource Manager Application Programming Interface (API)
-Reference Guide (<a href="packages/ti/sdo/edma3/rm/docs/html/index.html">HTML</a>
-| <a href="packages/ti/sdo/edma3/rm/docs/EDMA3_Resource_Manager.chm">CHM</a>)
- </li>
- <li> EDMA3 Driver Application Programming Interface Reference Guide (<a
- href="packages/ti/sdo/edma3/drv/docs/html/index.html">HTML</a> | <a
- href="packages/ti/sdo/edma3/drv/docs/EDMA3_Driver.chm">CHM</a>) </li>
- <li> <a href="examples/CSL2_DAT_DEMO/docs/CSL_DAT_Adapter.ppt">CSL
-2.x DAT Reference Implementation on EDMA3 Hardware using EDMA3 LLD</a> </li>
-</ul>
-<hr>
-<a name="Whats_New"></a>
-<h2><a name="Whats_New">What's New</a></h2>
-
-<p>
-<a name="Whats_New">The following significant changes have been made since 02.11.11:
-</a></p>
-
-<p><a name="Whats_New">02.11.11 - This release
-</a></p>
-
-<p>
-<a name="Whats_New">The following IRs are implemented:
-</a></p>
-
-<table width="100%">
- <tbody>
- <tr>
- <th>ID</th>
- <th>Headline</th>
- </tr>
- <tr>
- <td width="200">SDOCM00104308</td>
- <td>Ti814x sample app, the unregisterEdma3Interrupts causes an exception because error interrupts were not assigned for M3 builds</td>
- </tr>
- <tr>
- <td width="200">SDOCM00105689</td>
- <td>EDMA3 LLD support for official DRA7xx platform is broken</td>
- </tr>
- <tr>
- <td width="200">SDOCM00105739</td>
- <td>Add Support for EVE internal EDMA in EDMA3 LLD</td>
- </tr>
- </tbody>
-</table>
-
-<p>
-<a name="Whats_New"><FONT COLOR ='RED'>The following IRs are raised on this release:<b>Known Issues</b></FONT>
-</a></p>
-<table width="100%">
- <tbody>
- <tr>
- <th>ID</th>
- <th>Headline</th>
- </tr>
-
- <tr>
- <td width="200"><FONT COLOR ='RED'>SDOCM00078640</FONT></td>
- <td><FONT COLOR ='RED'>ARM 9 support for OMAPL138 is not available on Make based build of EDMA3LLD</FONT></td>
- </tr>
-
- <tr>
- <td width="200"><FONT COLOR ='RED'>SDSCM00039169</FONT></td>
- <td><FONT COLOR ='RED'>EDMA3 Example fails for following Big Endian Simulators targets tci6608-sim/tci6616-sim</FONT></td>
- </tr>
-
- </tbody>
-</table>
-
-<br>
-<hr><a name="Upgrade_Info"></a>
-<h2><a name="Upgrade_Info">Upgrade Information</a></h2>
-<p>
-The EDMA3 LLD packages are available in the "packages/" subdirectory of
-the product.
-If you have a previous release of the EDMA3 LLD product, you can
-install this
-release next to it, and modify your application and/or server builds to
-use this
-newer release.
-</p>
-<hr>
-<a name="Device_Support"></a>
-<h2><a name="Device_Support">Device Support</a></h2>
-<p>
-This release supports and has been tested on the following devices:
-</p>
-<ul>
- <a name="Device_Support"> <li>DA830 EVM:
- <ul type="circle">
- <li>C67x SYS/BIOS</li>
- </ul>
- </li>
- <li>TCI6498 Simulator:</li>
- </a>
- <ul>
- <li>C64X+ SYS/BIOS</li>
- </ul>
- <li>C6748 EVM:</li>
- <li style="margin-left: 40px;" type="circle">C67x SYS/BIOS</li>
- <li type="disc">OMAPL138 EVM:</li>
- <li style="margin-left: 40px;" type="circle">C67x SYS/BIOS</li>
- <li style="margin-left: 40px;" type="circle">ARM 9 SYSBIOS</li>
- <li>TI816X EVM:</li>
- </a>
- <ul>
- <li>C67X SYS/BIOS</li>
- <li>A8 SYS/BIOS</li>
- <li>M3 SYS/BIOS</li>
- </ul>
- <li>C6472 EVM:</li>
- </a>
- <ul>
- <li>C64X+ SYS/BIOS</li>
- </ul>
- <li>TCI6486 EVM:</li>
- </a>
- <ul>
- <li>C64X+ SYS/BIOS</li>
- </ul>
- <li>TI814X EVM:</li>
- </a>
- <ul>
- <li>C67X SYS/BIOS</li>
- <li>A8 SYS/BIOS</li>
- <li>M3 SYS/BIOS</li>
- </ul>
- <li>TI811X EVM:</li>
- </a>
- <ul>
- <li>C67X SYS/BIOS</li>
- <li>A8 SYS/BIOS</li>
- <li>M3 SYS/BIOS</li>
- </ul>
- <li>C6670 EVM:</li>
- </a>
- <ul>
- <li>C66X SYS/BIOS</li>
- </ul>
- <li>C6678 EVM:</li>
- </a>
- <ul>
- <li>C66X SYS/BIOS</li>
- </ul>
- <li>TCI6608 Simulator:</li>
- </a>
- <ul>
- <li>C66X SYS/BIOS</li>
- </ul>
- <li>TCI6616 Simulator:</li>
- </a>
- <ul>
- <li>C66X SYS/BIOS</li>
- </ul>
- <li>TCI6614 EVM:</li>
- </a>
- <ul>
- <li>C66X SYS/BIOS</li>
- </ul>
- <li>TCI6638K2K Simulator:</li>
- </a>
- <ul>
- <li>C66X SYS/BIOS</li>
- </ul>
- <li>TCI6638K2K EVM:</li>
- </a>
- <ul>
- <li>C66X SYS/BIOS</li>
- </ul>
- <li>TDA2XX SIM:</li>
- </a>
- <ul>
- <li>M4 SYS/BIOS</li>
- <li>a15 SYS/BIOS</li>
- <li>c66x SYS/BIOS</li>
- <li>EVE SYS/BIOS</li>
- </ul>
- </ul>
-<hr>
-<a name="Compatibility"></a>
-<h2><a name="Compatibility">Compatibility Information</a></h2>
-<h3><a name="Compatibility">Compatibility Key Definitions</a></h3>
-<p>
-Compatibility keys are intentionally independent of Marketing product
-numbers
-and are intended to:
-</p>
-<ol start="1" type="1">
- <a name="Compatibility"> <li> Enable tooling to identify
-incompatibilities between components, and </li>
- <li> Convey a level of compatibility between different releases to
-set end user expectations. </li>
- </a>
-</ol>
-<p>
-Compatibility keys are composed of 3 comma-delimited numbers - M, S, R
-- where:
-</p>
-<ul type="disc">
- <a name="Compatibility"> <li> <b>M = Major</b>. A difference in M
-indicates a break in compatibility. </li>
- <li> <b>S = Source</b>. A difference in S indicates source
-compatibility. That is, the user's source doesn't require change, but <i>does</i>
-require rebuilding. </li>
- <li> <b>R = Radix</b>. 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. </li>
- </a>
-</ul>
-<hr>
-<a name="Validation"></a>
-<h2><a name="Validation">Validation</a></h2>
-<p>
-This release was built and validated against using the following
-components:
-</p>
-<ul type="disc">
- <a name="Validation"> <li>CCS 5.4.0</li>
- <li>C6x Code Generation Tools version 7.4.2 </li>
- <li>TMS470 Code Generation Tools 5.0.4</li>
- <li>Arm GCC A15 Toolchain (Linaro) 4.7.3</li>
- <li>ARP32 Code Generation Tools 1.0.2</li>
- <li>SYS/BIOS 6.35.03.47</li>
- <li>XDC Tools 3.25.02.70</li>
- <li>TCI6498 Simulator 0.7.1</li>
- </a>
-</ul>
-<p>
-This release was validated in the following configurations:
-</p>
-<ul>
- <li> DA830 EVM:
- <ul type="circle">
- <li>C67x SYS/BIOS</li>
- </ul>
- </li>
- <li> TCI6498 Simulator:
- <ul type="circle">
- <li>C64X+ SYS/BIOS</li>
- </ul>
- </li>
- <li>C6748 EVM:</li>
- <li style="margin-left: 40px;" type="circle">C67x SYS/BIOS</li>
- <li>OMAPL138 EVM:</li>
- <ul>
- <li>C67x SYS/BIOS</li>
- <li>ARM 9 SYSBIOS</li>
- </ul>
- <li>TI816X EVM:</li>
- </a>
- <ul>
- <li>C67X SYS/BIOS</li>
- <li>A8 SYS/BIOS</li>
- <li>M3 SYS/BIOS</li>
- </ul>
- <li>C6472 EVM:</li>
- </a>
- <ul>
- <li>C64X+ SYS/BIOS</li>
- </ul>
- <li>TCI6486 EVM:</li>
- </a>
- <ul>
- <li>C64X+ SYS/BIOS</li>
- </ul>
- <li>TI814X EVM:</li>
- </a>
- <ul>
- <li>C67X SYS/BIOS</li>
- <li>A8 SYS/BIOS</li>
- <li>M3 SYS/BIOS</li>
- </ul>
- <li>TI811X EVM:</li>
- </a>
- <ul>
- <li>C67X SYS/BIOS</li>
- <li>A8 SYS/BIOS</li>
- <li>M3 SYS/BIOS</li>
- </ul>
- <li>C6670 EVM:</li>
- </a>
- <ul>
- <li>C66X SYS/BIOS</li>
- </ul>
- <li>C6678 EVM:</li>
- </a>
- <ul>
- <li>C66X SYS/BIOS</li>
- </ul>
- <li>TCI6608 Simulator:</li>
- </a>
- <ul>
- <li>C66X SYS/BIOS</li>
- </ul>
- <li>TCI6616 Simulator:</li>
- </a>
- <ul>
- <li>C66X SYS/BIOS</li>
- </ul>
- <li>TCI6614 EVM:</li>
- </a>
- <ul>
- <li>C66X SYS/BIOS</li>
- </ul>
- <li>TCI6638K2K Simulator:</li>
- </a>
- <ul>
- <li>C66X SYS/BIOS</li>
- </ul>
- <li>TCI6638K2K EVM:</li>
- </a>
- <ul>
- <li>C66X SYS/BIOS</li>
- </ul>
- <li>TDA2XX SIM:</li>
- </a>
- <ul>
- <li>A15 SYS/BIOS</li>
- <li>M4 SYS/BIOS</li>
- <li>DSP SYS/BIOS</li>
- <li>EVE SYS/BIOS</li>
- </ul>
- </ul>
-<hr><a name="Known_Issues">
-</a>
-<h2><a name="Known_Issues">Known Issues</a></h2>
-<p>
-The following are known issues with the current EDMA3 LLD release:
-</p>
-<h4><a name="Known_Issues">Pre-built instrumented libraries for DA830
-not provided initially.</a></h4>
-<p>Pre-built instrumented EDMA3 libraries for DA830 will not be
-provided
-initially. XDC does not support the same and hence the limitation. See
-IR#
-SDOCM00036738 for more details.
-</p>
-<h4><a name="Known_Issues">EDMA3 hardware does not work properly in
-FIFO mode with all the controllers.</a></h4>
-<p>Very few peripherals support EDMA3 FIFO mode. EMIF controller
-doesn't support
-the same. So EDMA3 CANNOT be used in FIFO mode for doing a
-memory-to-memory data
-transfers, EDMA3 being configured in the FIFO mode. Applications trying
-to use
-EDMA3 in FIFO mode should first check their respective
-peripheral-controller
-document for this mode support.
-</p>
-<h4><a name="Known_Issues">PingPong Example Fails for certain EDMA
-instances for some DSP cores in Release mode only.</a></h4>
-<p>The PingPong example in the package fails for certain EDMA Instances
-for some DSP cores in Release mode only. It passes for Debug mode. See
-IR#
-SDOCM00064758 for more details.
-</p>
-<hr>
-<a name="Examples"></a>
-<h2><a name="Examples">Examples</a></h2>
-<p>
-EDMA3 LLD sample initialization libraries / OS abstraction layers (for
-different
-platforms) are located in:
-</p>
-<ul type="disc">
- <a name="Examples"> <li> For Resource Manager: They could be located
-in <tt>edma3_lld_02_11_11_XX\packages\ti\sdo\edma3\rm\sample\lib</tt>
-folder. </li>
- <li> For EDMA3 Driver: They could be located in <tt>edma3_lld_02_11_11_XX\packages\ti\sdo\edma3\drv\sample\lib</tt>
-folder. </li>
- </a>
-</ul>
-<p>
-EDMA3 LLD stand-alone applications (for different platforms) are
-located in:
-</p>
-<ul type="disc">
- <a name="Examples"> <li> EDMA3 Driver: They could be located in <tt>edma3_lld_02_11_11_XX\examples\edma3_driver\</tt>
-folder. </li>
- </a>
-</ul>
-<ul type="disc">
- <a name="Examples"> <li> CSL2.x DAT Reference Implementation: It
-could be located in <tt>edma3_lld_02_11_11_XX\examples\CSL2_DAT_DEMO\</tt>
-folder. </li>
- </a>
-</ul>
-<hr>
-<a name="Version"></a>
-<h2><a name="Version">Version Information</a></h2>
-<p>
-This product's version follows a version format, <b>M.mm.pp.bb</b>,
-where
-<b>M</b> is a 2 digit major number,
-<b>mm</b> is 2 digit minor number,
-<b>pp</b> is a 2 digit patch number, and
-<b>b</b> is an unrestricted set of digits used as an incrementing build
-counter.
-</p>
-<p>
-To support multiple side-by-side installations of the product, the
-product
-version is encoded in the top level directory, ex. <b>edma3_lld_02_11_11_XX</b>.
-</p>
-<p>Subsequent releases of patch upgrades will be identified by the
-patch number,
-ex. EDMA3 LLD 02.11.11 with directory <b>edma3_lld_02_11_11_YY</b>.
-Typically, these
-patches only include critical bug fixes.
-</p>
-<hr>
-<a name="Support"></a>
-<h2><a name="Support">Technical Support</a></h2>
-<p>
-For technical support, Please post at TI E2E forum <a href="http://e2e.ti.com/support/embedded/f/355.aspx">http://e2e.ti.com/support/embedded/f/355.aspx</a>
-</p>
-<hr>
-<p>Last updated: Dec 27, 2013
-</p>
-</body>
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">\r
+<html xmlns="http://www.w3.org/TR/REC-html40">\r
+<head>\r
+ <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">\r
+ <meta http-equiv="Content-Type" content="text/html">\r
+ <title>EDMA3 LLD 02.12.00.21 Release Notes</title>\r
+ <style type="text/css">\r
+body\r
+{\r
+ color: #000 ;\r
+ background-color: #fff ;\r
+ margin : 5px 20px 5px 20px;\r
+ font-family: Tahoma, Arial, Helvetica, sans-serif;\r
+ font-size: 10pt ;\r
+}\r
+\r
+a,\r
+a:link,\r
+a:visited,\r
+\r
+{\r
+ color : #1a41a8 ;\r
+}\r
+\r
+a:hover\r
+{\r
+ color : #2a3798 ;\r
+}\r
+\r
+img\r
+{\r
+ text-decoration : none ;\r
+}\r
+\r
+p\r
+{\r
+ color: #000 ;\r
+}\r
+\r
+table.tagline\r
+{\r
+ width: 100%;\r
+}\r
+\r
+li\r
+{\r
+ color : black ;\r
+}\r
+\r
+.title\r
+{\r
+ text-align : center ;\r
+}\r
+\r
+th\r
+{\r
+ text-align : left ;\r
+}\r
+ </style>\r
+</head>\r
+<body>\r
+<table border="0" cellpadding="0" cellspacing="0" width="100%">\r
+ <tbody>\r
+ <tr>\r
+ <td\r
+ style="background: black none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"\r
+ width="222"> <a href="http://www.ti.com/"><img id="_x0000_i1025"\r
+ src="docs/html/tilogo.gif" alt="Texas Instruments" border="0"\r
+ height="54" width="222"> </a></td>\r
+ <td\r
+ style="background: red none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;">\r
+ <img id="_x0000_i1026" src="docs/html/titagline.gif"\r
+ alt="Technology for Innovators(tm)" border="0" height="26" width="314">\r
+ </td>\r
+ </tr>\r
+ </tbody>\r
+</table>\r
+<h1 class="title">EDMA3 LLD 02.12.00.21 Release Notes</h1>\r
+<h2 class="title">November 23, 2018</h2>\r
+<p>\r
+This EDMA3 Low Level Driver Release is targeted to the users (device\r
+drivers\r
+and applications) for submitting and synchronizing with EDMA3 based DMA\r
+transfers.\r
+This release supports DA830,C6748,TCI6498,TI816X,C6472,TCI6486,TI814X,TI816X,TI811X,TCI6608,TCI6616,TCI6614,C6670,C6678,TCI6638K2K,TDA2xx,TDA3xx, DRA72x, platforms, on\r
+SYS/BIOS 6 side & OMAPL138 on SYS/BIOS and ARM side. Porting\r
+instructions\r
+are also provided to use the package for different platforms and\r
+Operating\r
+Systems.\r
+</p>\r
+<p>\r
+<a href="#Introduction">Introduction</a>,\r
+<a href="#Documentation">Documentation</a>,\r
+<a href="#Whats_New">What's New</a>,\r
+<a href="#Upgrade_Info">Upgrade Info</a>,\r
+<a href="#Device_Support">Device Support</a>,\r
+<a href="#Compatibility">Compatibility Information</a>,\r
+<a href="#Validation">Validation Info</a>,\r
+<a href="#Known_Issues">Known Issues</a>,\r
+<a href="#Examples">Examples</a>,\r
+<a href="#Version">Version Information</a>,\r
+<a href="#Support">Technical Support</a>\r
+</p>\r
+<hr>\r
+<a name="Introduction"></a>\r
+<h2><a name="Introduction">Introduction</a></h2>\r
+<p>\r
+EDMA3 LLD is a single product package containing the following\r
+stand-alone\r
+software components:\r
+</p>\r
+<ul type="disc">\r
+ <a name="Introduction"> <li> <b>EDMA3 Resource Manager</b> - TI\r
+mandated library for all EDMA3 peripheral users to acquire and\r
+configure EDMA3 hardware resources (DMA/QDMA channels, PaRAM Sets, TCCs\r
+etc.) and DMA Interrupt Service Routines. </li>\r
+ <li> <b>EDMA3 Driver</b> - Functional library providing APIs for\r
+programming, scheduling and synchronizing with EDMA transfers and many\r
+more. </li>\r
+ </a>\r
+</ul>\r
+<p>\r
+EDMA3 Resource Manager can be used independently whereas the EDMA3\r
+Driver requires\r
+the Resource Manager services internally.\r
+</p>\r
+<p>\r
+EDMA3 LLD (both Resource Manager and the Driver) is a platform\r
+independent package.\r
+Hence it can be used across multiple platforms. Porting instructions\r
+are provided for both the components to do the same.\r
+</p>\r
+<p>\r
+It is also an OS-agnostic package and thus can be used across multiple\r
+operating\r
+systems. OS-adaptation layer needs to be provided by the user (in case\r
+it is needed)\r
+for OS customization. Instructions to do the same are also provided\r
+along with\r
+the package.\r
+</p>\r
+<p>\r
+The Low Level Driver has already been ported (SYS/BIOS Operating\r
+Systems)\r
+and tested on various platforms mentioned below. Sample initialization\r
+libraries,\r
+which configure the EDMA3 hardware and provide the necessary OS\r
+abstraction layer,\r
+are also a part of the package. These libraries are available both for\r
+the EDMA3\r
+Resource Manager and EDMA3 Driver. These could be used for proper\r
+initialization of the software component(s) along with the OS\r
+adaptation layer\r
+for the same.\r
+</p>\r
+<p>\r
+The Low Level Driver consists of the following packages:\r
+</p>\r
+<ul type="disc">\r
+ <a name="Introduction"> <li> <tt><b>ti.sdo.edma3.rm</b></tt> -\r
+EDMA3 Resource Manager. </li>\r
+ <li> <tt><b>ti.sdo.edma3.rm.sample</b></tt> - Sample initialization\r
+library / OS abstraction layer for the Resource Manager. </li>\r
+ <li> <tt><b>ti.sdo.edma3.drv</b></tt> - EDMA3 Driver. </li>\r
+ <li> <tt><b>ti.sdo.edma3.drv.sample</b></tt> - Sample initialization\r
+library / OS abstraction layer for the Driver. </li>\r
+ </a>\r
+</ul>\r
+<p><b>Note: </b>\r
+<ul type="disc">\r
+ <a name="Introduction"> <li> <b>Address translation is not done in EDMA3 LLD</b> </li>\r
+<br>If the memory map of the EDMA is different than the host processor programming it,\r
+EDMA3LLD being a low level driver the address translation is not done by this. It is expected that the application\r
+will provide the addresses, corresponding to EDMA memory map to configure in PARAM.\r
+</p>\r
+</a>\r
+ <a name="Introduction"> <li> <FONT COLOR ='RED'><b>All resources are allocated to all cores in default sample configuration files of EDMA3 LLD</b> </FONT></li>\r
+<br>The EDMA resources like Channels, PaRAMs and TCCs which are shared by multiple cores (Ex: in TI814X and TI816X), \r
+The default configuration file allocates all the resources to every core since the resource split is application dependant. \r
+The applications using EDMA3LLD should appropriately allocate the resources in the config files and build EDMA3LLD libraries.\r
+</p>\r
+</a>\r
+ <a name="Introduction"> <li> <b>Building EDMA3LLD libs and examples on windows 7</b> </li>\r
+<br>On windows 7 there is a permission issue while building the libs and examples.set the environment variable CYGWIN in the command window where you are building <br> examples: $set CYGWIN=nontsec <br>You might have to manually delete the generated files before building.\r
+</p>\r
+</a>\r
+</ul>\r
+<a name="Documentation">\r
+</a>\r
+<h2><a name="Documentation">Documentation</a></h2>\r
+<p>The following documentation is available:\r
+</p>\r
+<ul type="disc">\r
+ <li><a href="docs/EDMA3_RM_Release_Notes.pdf">EDMA3 Resource Manager\r
+Release Notes</a></li>\r
+ <li> <a href="packages/ti/sdo/edma3/rm/docs/EDMA3_RM_User_Guide.pdf">EDMA3\r
+Resource Manager User's Guide</a> </li>\r
+ <li> <a href="docs/EDMA3_Driver_Release_Notes.pdf">EDMA3 Driver\r
+Release Notes</a> </li>\r
+ <li> <a\r
+ href="packages/ti/sdo/edma3/drv/docs/EDMA3_Driver_User_Guide.pdf">EDMA3\r
+Driver User's Guide</a> </li>\r
+ <li> EDMA3 Resource Manager Application Programming Interface (API)\r
+Reference Guide (<a href="packages/ti/sdo/edma3/rm/docs/html/index.html">HTML</a>\r
+| <a href="packages/ti/sdo/edma3/rm/docs/EDMA3_Resource_Manager.chm">CHM</a>)\r
+ </li>\r
+ <li> EDMA3 Driver Application Programming Interface Reference Guide (<a\r
+ href="packages/ti/sdo/edma3/drv/docs/html/index.html">HTML</a> | <a\r
+ href="packages/ti/sdo/edma3/drv/docs/EDMA3_Driver.chm">CHM</a>) </li>\r
+ <li> <a href="examples/CSL2_DAT_DEMO/docs/CSL_DAT_Adapter.ppt">CSL\r
+2.x DAT Reference Implementation on EDMA3 Hardware using EDMA3 LLD</a> </li>\r
+</ul>\r
+<hr>\r
+<a name="Whats_New"></a>\r
+<h2><a name="Whats_New">What's New</a></h2>\r
+\r
+<p>\r
+<a name="Whats_New">The following changes have been made since 02.12.00.20:\r
+</a></p>\r
+\r
+<p><a name="Whats_New">This release 02.12.00.21 : This is a minor release with the Misra issues reported due to tool upgradations are fixed\r
+</a></p>\r
+\r
+<br>\r
+<hr><a name="Upgrade_Info"></a>\r
+<h2><a name="Upgrade_Info">Upgrade Information</a></h2>\r
+<p>\r
+The EDMA3 LLD packages are available in the "packages/" subdirectory of\r
+the product.\r
+If you have a previous release of the EDMA3 LLD product, you can\r
+install this\r
+release next to it, and modify your application and/or server builds to\r
+use this\r
+newer release.\r
+</p>\r
+<hr>\r
+<a name="Device_Support"></a>\r
+<h2><a name="Device_Support">Device Support</a></h2>\r
+<p>\r
+This release supports and has been tested on the following devices:\r
+</p>\r
+<ul>\r
+ <a name="Device_Support"> <li>DA830 EVM:\r
+ <ul type="circle">\r
+ <li>C67x SYS/BIOS</li>\r
+ </ul>\r
+ </li>\r
+ <li>TCI6498 Simulator:</li>\r
+ </a>\r
+ <ul>\r
+ <li>C64X+ SYS/BIOS</li>\r
+ </ul>\r
+ <li>C6748 EVM:</li>\r
+ <li style="margin-left: 40px;" type="circle">C67x SYS/BIOS</li>\r
+ <li type="disc">OMAPL138 EVM:</li>\r
+ <li style="margin-left: 40px;" type="circle">C67x SYS/BIOS</li>\r
+ <li style="margin-left: 40px;" type="circle">ARM 9 SYSBIOS</li>\r
+ <li>TI816X EVM:</li>\r
+ </a>\r
+ <ul>\r
+ <li>C67X SYS/BIOS</li>\r
+ <li>A8 SYS/BIOS</li>\r
+ <li>M3 SYS/BIOS</li>\r
+ </ul>\r
+ <li>C6472 EVM:</li>\r
+ </a>\r
+ <ul>\r
+ <li>C64X+ SYS/BIOS</li>\r
+ </ul>\r
+ <li>TCI6486 EVM:</li>\r
+ </a>\r
+ <ul>\r
+ <li>C64X+ SYS/BIOS</li>\r
+ </ul>\r
+ <li>TI814X EVM:</li>\r
+ </a>\r
+ <ul>\r
+ <li>C67X SYS/BIOS</li>\r
+ <li>A8 SYS/BIOS</li>\r
+ <li>M3 SYS/BIOS</li>\r
+ </ul>\r
+ <li>TI811X EVM:</li>\r
+ </a>\r
+ <ul>\r
+ <li>C67X SYS/BIOS</li>\r
+ <li>A8 SYS/BIOS</li>\r
+ <li>M3 SYS/BIOS</li>\r
+ </ul>\r
+ <li>C6670 EVM:</li>\r
+ </a>\r
+ <ul>\r
+ <li>C66X SYS/BIOS</li>\r
+ </ul> \r
+ <li>C6678 EVM:</li>\r
+ </a>\r
+ <ul>\r
+ <li>C66X SYS/BIOS</li>\r
+ </ul> \r
+ <li>TCI6608 Simulator:</li>\r
+ </a>\r
+ <ul>\r
+ <li>C66X SYS/BIOS</li>\r
+ </ul> \r
+ <li>TCI6616 Simulator:</li>\r
+ </a>\r
+ <ul>\r
+ <li>C66X SYS/BIOS</li>\r
+ </ul>\r
+ <li>TCI6614 EVM:</li>\r
+ </a>\r
+ <ul>\r
+ <li>C66X SYS/BIOS</li>\r
+ </ul>\r
+ <li>TCI6638K2K Simulator:</li>\r
+ </a>\r
+ <ul>\r
+ <li>C66X SYS/BIOS</li>\r
+ </ul>\r
+ <li>TCI6638K2K EVM:</li>\r
+ </a>\r
+ <ul>\r
+ <li>C66X SYS/BIOS</li>\r
+ </ul>\r
+ <li>TCI6636K2H EVM:</li>\r
+ </a>\r
+ <ul>\r
+ <li>C66X SYS/BIOS</li>\r
+ <li>A15 Arago</li>\r
+ </ul>\r
+ <li>TDA2XX EVM:</li>\r
+ </a>\r
+ <ul>\r
+ <li>M4 SYS/BIOS</li>\r
+ <li>a15 SYS/BIOS</li>\r
+ <li>c66x SYS/BIOS</li>\r
+ <li>EVE SYS/BIOS</li>\r
+ </ul>\r
+ <li>TDA3XX EVM:</li>\r
+ </a>\r
+ <ul>\r
+ <li>M4 SYS/BIOS</li>\r
+ <li>c66x SYS/BIOS</li>\r
+ <li>EVE SYS/BIOS</li>\r
+ </ul>\r
+ <li>DRA72X EVM:</li>\r
+ </a>\r
+ <ul>\r
+ <li>M4 SYS/BIOS</li>\r
+ <li>a15 SYS/BIOS</li>\r
+ <li>c66x SYS/BIOS</li>\r
+ </ul>\r
+ </ul>\r
+<hr>\r
+<a name="Compatibility"></a>\r
+<h2><a name="Compatibility">Compatibility Information</a></h2>\r
+<h3><a name="Compatibility">Compatibility Key Definitions</a></h3>\r
+<p>\r
+Compatibility keys are intentionally independent of Marketing product\r
+numbers\r
+and are intended to:\r
+</p>\r
+<ol start="1" type="1">\r
+ <a name="Compatibility"> <li> Enable tooling to identify\r
+incompatibilities between components, and </li>\r
+ <li> Convey a level of compatibility between different releases to\r
+set end user expectations. </li>\r
+ </a>\r
+</ol>\r
+<p>\r
+Compatibility keys are composed of 3 comma-delimited numbers - M, S, R\r
+- where:\r
+</p>\r
+<ul type="disc">\r
+ <a name="Compatibility"> <li> <b>M = Major</b>. A difference in M\r
+indicates a break in compatibility. </li>\r
+ <li> <b>S = Source</b>. A difference in S indicates source\r
+compatibility. That is, the user's source doesn't require change, but <i>does</i>\r
+require rebuilding. </li>\r
+ <li> <b>R = Radix</b>. A difference in R indicates an introduction\r
+of new features, but compatibility with previous interfaces has not\r
+broken. If libraries are provided by the package, an application must\r
+re-link with the new libraries, but not rebuild from source. </li>\r
+ </a>\r
+</ul>\r
+<hr>\r
+<a name="Validation"></a>\r
+<h2><a name="Validation">Validation</a></h2>\r
+<p>\r
+This release was built and validated against using the following\r
+components:\r
+</p>\r
+<ul type="disc">\r
+ <a name="Validation"> <li>CCS 5.5, CCS 6 or CCS 7</li>\r
+ <li>C6x Code Generation Tools version 7.4.2 </li>\r
+ <li>TMS470 Code Generation Tools (ELF Format) 16.9.2.LTS</li>
+ <li>TMS470 Code Generation Tools (Coff Format) 5.2.5</li>\r
+ <li>Arm GCC A15 Toolchain 6-2017-q1-update </li>\r
+ <li>ARP32 Code Generation Tools 1.0.7</li>\r
+ <li>SYS/BIOS 6.46.04.53</li>\r
+ <li>XDC Tools 3.32.01.22</li>\r
+ <li>TCI6498 Simulator 0.7.1</li>\r
+ </a>\r
+</ul>\r
+<p>\r
+This release was validated in the following configurations:\r
+</p>\r
+<ul>\r
+ <li> DA830 EVM:\r
+ <ul type="circle">\r
+ <li>C67x SYS/BIOS</li>\r
+ </ul>\r
+ </li>\r
+ <li> TCI6498 Simulator:\r
+ <ul type="circle">\r
+ <li>C64X+ SYS/BIOS</li>\r
+ </ul>\r
+ </li>\r
+ <li>C6748 EVM:</li>\r
+ <li style="margin-left: 40px;" type="circle">C67x SYS/BIOS</li>\r
+ <li>OMAPL138 EVM:</li>\r
+ <ul>\r
+ <li>C67x SYS/BIOS</li>\r
+ <li>ARM 9 SYSBIOS</li>\r
+ </ul>\r
+ <li>TI816X EVM:</li>\r
+ </a>\r
+ <ul>\r
+ <li>C67X SYS/BIOS</li>\r
+ <li>A8 SYS/BIOS</li>\r
+ <li>M3 SYS/BIOS</li>\r
+ </ul>\r
+ <li>C6472 EVM:</li>\r
+ </a>\r
+ <ul>\r
+ <li>C64X+ SYS/BIOS</li>\r
+ </ul>\r
+ <li>TCI6486 EVM:</li>\r
+ </a>\r
+ <ul>\r
+ <li>C64X+ SYS/BIOS</li>\r
+ </ul>\r
+ <li>TI814X EVM:</li>\r
+ </a>\r
+ <ul>\r
+ <li>C67X SYS/BIOS</li>\r
+ <li>A8 SYS/BIOS</li>\r
+ <li>M3 SYS/BIOS</li>\r
+ </ul>\r
+ <li>TI811X EVM:</li>\r
+ </a>\r
+ <ul>\r
+ <li>C67X SYS/BIOS</li>\r
+ <li>A8 SYS/BIOS</li>\r
+ <li>M3 SYS/BIOS</li>\r
+ </ul>\r
+ <li>C6670 EVM:</li>\r
+ </a>\r
+ <ul>\r
+ <li>C66X SYS/BIOS</li>\r
+ </ul> \r
+ <li>C6678 EVM:</li>\r
+ </a>\r
+ <ul>\r
+ <li>C66X SYS/BIOS</li>\r
+ </ul> \r
+ <li>TCI6608 Simulator:</li>\r
+ </a>\r
+ <ul>\r
+ <li>C66X SYS/BIOS</li>\r
+ </ul> \r
+ <li>TCI6616 Simulator:</li>\r
+ </a>\r
+ <ul>\r
+ <li>C66X SYS/BIOS</li>\r
+ </ul>\r
+ <li>TCI6614 EVM:</li>\r
+ </a>\r
+ <ul>\r
+ <li>C66X SYS/BIOS</li>\r
+ </ul>\r
+ <li>TCI6638K2K Simulator:</li>\r
+ </a>\r
+ <ul>\r
+ <li>C66X SYS/BIOS</li>\r
+ </ul>\r
+ <li>TCI6638K2K EVM:</li>\r
+ </a>\r
+ <ul>\r
+ <li>C66X SYS/BIOS</li>\r
+ </ul>\r
+ <li>TCI6636K2H EVM:</li>\r
+ </a>\r
+ <ul>\r
+ <li>C66X SYS/BIOS</li>\r
+ <li>A15 Arago</li>\r
+ </ul>\r
+ <li>TDA2XX EVM:</li>\r
+ </a>\r
+ <ul>\r
+ <li>A15 SYS/BIOS</li>\r
+ <li>M4 SYS/BIOS</li>\r
+ <li>DSP SYS/BIOS</li>\r
+ <li>EVE SYS/BIOS</li>\r
+ </ul>\r
+ <li>TDA3XX SIM:</li>\r
+ </a>\r
+ <ul>\r
+ <li>M4 SYS/BIOS</li>\r
+ <li>DSP SYS/BIOS</li>\r
+ <li>EVE SYS/BIOS</li>\r
+ </ul>\r
+ <li>DRA72X SIM:</li>\r
+ </a>\r
+ <ul>\r
+ <li>A15 SYS/BIOS</li>\r
+ <li>M4 SYS/BIOS</li>\r
+ <li>DSP SYS/BIOS</li>\r
+ </ul>\r
+ </ul>\r
+<hr><a name="Known_Issues">\r
+</a>\r
+<h2><a name="Known_Issues">Known Issues</a></h2>\r
+<p>\r
+The following are known issues with the current EDMA3 LLD release:\r
+</p>\r
+<h4><a name="Known_Issues">Pre-built instrumented libraries for DA830\r
+not provided initially.</a></h4>\r
+<p>Pre-built instrumented EDMA3 libraries for DA830 will not be\r
+provided\r
+initially. XDC does not support the same and hence the limitation. See\r
+IR#\r
+SDOCM00036738 for more details.\r
+</p>\r
+<h4><a name="Known_Issues">EDMA3 hardware does not work properly in\r
+FIFO mode with all the controllers.</a></h4>\r
+<p>Very few peripherals support EDMA3 FIFO mode. EMIF controller\r
+doesn't support\r
+the same. So EDMA3 CANNOT be used in FIFO mode for doing a\r
+memory-to-memory data\r
+transfers, EDMA3 being configured in the FIFO mode. Applications trying\r
+to use\r
+EDMA3 in FIFO mode should first check their respective\r
+peripheral-controller\r
+document for this mode support.\r
+</p>\r
+<h4><a name="Known_Issues">PingPong Example Fails for certain EDMA\r
+instances for some DSP cores in Release mode only.</a></h4>\r
+<p>The PingPong example in the package fails for certain EDMA Instances\r
+for some DSP cores in Release mode only. It passes for Debug mode. See\r
+IR#\r
+SDOCM00064758 for more details.\r
+</p>\r
+<hr>\r
+<a name="Examples"></a>\r
+<h2><a name="Examples">Examples</a></h2>\r
+<p>\r
+EDMA3 LLD sample initialization libraries / OS abstraction layers (for\r
+different\r
+platforms) are located in:\r
+</p>\r
+<ul type="disc">\r
+ <a name="Examples"> <li> For Resource Manager: They could be located\r
+in <tt>edma3_lld_02_12_00_XX\packages\ti\sdo\edma3\rm\sample\lib</tt>\r
+folder. </li>\r
+ <li> For EDMA3 Driver: They could be located in <tt>edma3_lld_02_12_00_XX\packages\ti\sdo\edma3\drv\sample\lib</tt>\r
+folder. </li>\r
+ </a>\r
+</ul>\r
+<p>\r
+EDMA3 LLD stand-alone applications (for different platforms) are\r
+located in:\r
+</p>\r
+<ul type="disc">\r
+ <a name="Examples"> <li> EDMA3 Driver: They could be located in <tt>edma3_lld_02_12_00_XX\examples\edma3_driver\</tt>\r
+folder. </li>\r
+ </a>\r
+</ul>\r
+<ul type="disc">\r
+ <a name="Examples"> <li> CSL2.x DAT Reference Implementation: It\r
+could be located in <tt>edma3_lld_02_12_00_XX\examples\CSL2_DAT_DEMO\</tt>\r
+folder. </li>\r
+ </a>\r
+</ul>\r
+<hr>\r
+<a name="Version"></a>\r
+<h2><a name="Version">Version Information</a></h2>\r
+<p>\r
+This product's version follows a version format, <b>M.mm.pp.bb</b>,\r
+where\r
+<b>M</b> is a 2 digit major number,\r
+<b>mm</b> is 2 digit minor number,\r
+<b>pp</b> is a 2 digit patch number, and\r
+<b>b</b> is an unrestricted set of digits used as an incrementing build\r
+counter.\r
+</p>\r
+<p>\r
+To support multiple side-by-side installations of the product, the\r
+product\r
+version is encoded in the top level directory, ex. <b>edma3_lld_02_12_00_XX</b>.\r
+</p>\r
+<p>Subsequent releases of patch upgrades will be identified by the\r
+patch number,\r
+ex. EDMA3 LLD 02.11.14 with directory <b>edma3_lld_02_12_00_YY</b>.\r
+Typically, these\r
+patches only include critical bug fixes.\r
+</p>\r
+<hr>\r
+<a name="Support"></a>\r
+<h2><a name="Support">Technical Support</a></h2>\r
+<p>\r
+For technical support, Please post at TI E2E forum <a href="http://e2e.ti.com/support/embedded/f/355.aspx">http://e2e.ti.com/support/embedded/f/355.aspx</a>\r
+</p>\r
+<hr>\r
+<p>Last updated: November 23, 2018\r
+</p>\r
+</body>\r
+</html>\r