1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
2 <html xmlns="http://www.w3.org/TR/REC-html40">
3 <head>
4 <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
5 <meta http-equiv="Content-Type" content="text/html">
6 <title>EDMA3 LLD 02.11.06 Release Notes</title>
7 <style type="text/css">
8 body
9 {
10 color: #000 ;
11 background-color: #fff ;
12 margin : 5px 20px 5px 20px;
13 font-family: Tahoma, Arial, Helvetica, sans-serif;
14 font-size: 10pt ;
15 }
17 a,
18 a:link,
19 a:visited,
21 {
22 color : #1a41a8 ;
23 }
25 a:hover
26 {
27 color : #2a3798 ;
28 }
30 img
31 {
32 text-decoration : none ;
33 }
35 p
36 {
37 color: #000 ;
38 }
40 table.tagline
41 {
42 width: 100%;
43 }
45 li
46 {
47 color : black ;
48 }
50 .title
51 {
52 text-align : center ;
53 }
55 th
56 {
57 text-align : left ;
58 }
59 </style>
60 </head>
61 <body>
62 <table border="0" cellpadding="0" cellspacing="0" width="100%">
63 <tbody>
64 <tr>
65 <td
66 style="background: black none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"
67 width="222"> <a href="http://www.ti.com/"><img id="_x0000_i1025"
68 src="docs/html/tilogo.gif" alt="Texas Instruments" border="0"
69 height="54" width="222"> </a></td>
70 <td
71 style="background: red none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;">
72 <img id="_x0000_i1026" src="docs/html/titagline.gif"
73 alt="Technology for Innovators(tm)" border="0" height="26" width="314">
74 </td>
75 </tr>
76 </tbody>
77 </table>
78 <h1 class="title">EDMA3 LLD 02.11.06 Release Notes</h1>
79 <h2 class="title">Aug 10, 2012</h2>
80 <p>
81 This EDMA3 Low Level Driver Release is targeted to the users (device
82 drivers
83 and applications) for submitting and synchronizing with EDMA3 based DMA
84 transfers.
85 This release supports DA830,C6748,TCI6498,TI816X,C6472,TCI6486,TI814X,TI816X,TI811X,TCI6608,TCI6616,TCI6614,C6670,C6678 platforms, on
86 SYS/BIOS 6 side & OMAPL138 on SYS/BIOS and ARM side. Porting
87 instructions
88 are also provided to use the package for different platforms and
89 Operating
90 Systems.
91 </p>
92 <p>
93 <a href="#Introduction">Introduction</a>,
94 <a href="#Documentation">Documentation</a>,
95 <a href="#Whats_New">What's New</a>,
96 <a href="#Upgrade_Info">Upgrade Info</a>,
97 <a href="#Device_Support">Device Support</a>,
98 <a href="#Compatibility">Compatibility Information</a>,
99 <a href="#Validation">Validation Info</a>,
100 <a href="#Known_Issues">Known Issues</a>,
101 <a href="#Examples">Examples</a>,
102 <a href="#Version">Version Information</a>,
103 <a href="#Support">Technical Support</a>
104 </p>
105 <hr>
106 <a name="Introduction"></a>
107 <h2><a name="Introduction">Introduction</a></h2>
108 <p>
109 EDMA3 LLD is a single product package containing the following
110 stand-alone
111 software components:
112 </p>
113 <ul type="disc">
114 <a name="Introduction"> <li> <b>EDMA3 Resource Manager</b> - TI
115 mandated library for all EDMA3 peripheral users to acquire and
116 configure EDMA3 hardware resources (DMA/QDMA channels, PaRAM Sets, TCCs
117 etc.) and DMA Interrupt Service Routines. </li>
118 <li> <b>EDMA3 Driver</b> - Functional library providing APIs for
119 programming, scheduling and synchronizing with EDMA transfers and many
120 more. </li>
121 </a>
122 </ul>
123 <p>
124 EDMA3 Resource Manager can be used independently whereas the EDMA3
125 Driver requires
126 the Resource Manager services internally.
127 </p>
128 <p>
129 EDMA3 LLD (both Resource Manager and the Driver) is a platform
130 independent package.
131 Hence it can be used across multiple platforms. Porting instructions
132 are provided for both the components to do the same.
133 </p>
134 <p>
135 It is also an OS-agnostic package and thus can be used across multiple
136 operating
137 systems. OS-adaptation layer needs to be provided by the user (in case
138 it is needed)
139 for OS customization. Instructions to do the same are also provided
140 along with
141 the package.
142 </p>
143 <p>
144 The Low Level Driver has already been ported (SYS/BIOS Operating
145 Systems)
146 and tested on various platforms mentioned below. Sample initialization
147 libraries,
148 which configure the EDMA3 hardware and provide the necessary OS
149 abstraction layer,
150 are also a part of the package. These libraries are available both for
151 the EDMA3
152 Resource Manager and EDMA3 Driver. These could be used for proper
153 initialization of the software component(s) along with the OS
154 adaptation layer
155 for the same.
156 </p>
157 <p>
158 The Low Level Driver consists of the following packages:
159 </p>
160 <ul type="disc">
161 <a name="Introduction"> <li> <tt><b>ti.sdo.edma3.rm</b></tt> -
162 EDMA3 Resource Manager. </li>
163 <li> <tt><b>ti.sdo.edma3.rm.sample</b></tt> - Sample initialization
164 library / OS abstraction layer for the Resource Manager. </li>
165 <li> <tt><b>ti.sdo.edma3.drv</b></tt> - EDMA3 Driver. </li>
166 <li> <tt><b>ti.sdo.edma3.drv.sample</b></tt> - Sample initialization
167 library / OS abstraction layer for the Driver. </li>
168 </a>
169 </ul>
170 <p><b>Note: </b>
171 <ul type="disc">
172 <a name="Introduction"> <li> <b>Address translation is not done in EDMA3 LLD</b> </li>
173 <br>If the memory map of the EDMA is different than the host processor programming it,
174 EDMA3LLD being a low level driver the address translation is not done by this. It is expected that the application
175 will provide the addresses, corresponding to EDMA memory map to configure in PARAM.
176 </p>
177 </a>
178 <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>
179 <br>The EDMA resources like Channels, PaRAMs and TCCs which are shared by multiple cores (Ex: in TI814X and TI816X),
180 The default configuration file allocates all the resources to every core since the resource split is application dependant.
181 The applications using EDMA3LLD should appropriately allocate the resources in the config files and build EDMA3LLD libraries.
182 </p>
183 </a>
184 <a name="Introduction"> <li> <b>Building EDMA3LLD libs and examples on windows 7</b> </li>
185 <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.
186 </p>
187 </a>
188 </ul>
189 <a name="Documentation">
190 </a>
191 <h2><a name="Documentation">Documentation</a></h2>
192 <p>The following documentation is available:
193 </p>
194 <ul type="disc">
195 <li><a href="docs/EDMA3_RM_Release_Notes.pdf">EDMA3 Resource Manager
196 Release Notes</a></li>
197 <li> <a href="packages/ti/sdo/edma3/rm/docs/EDMA3_RM_User_Guide.pdf">EDMA3
198 Resource Manager User's Guide</a> </li>
199 <li> <a href="docs/EDMA3_Driver_Release_Notes.pdf">EDMA3 Driver
200 Release Notes</a> </li>
201 <li> <a
202 href="packages/ti/sdo/edma3/drv/docs/EDMA3_Driver_User_Guide.pdf">EDMA3
203 Driver User's Guide</a> </li>
204 <li> EDMA3 Resource Manager Application Programming Interface (API)
205 Reference Guide (<a href="packages/ti/sdo/edma3/rm/docs/html/index.html">HTML</a>
206 | <a href="packages/ti/sdo/edma3/rm/docs/EDMA3_Resource_Manager.chm">CHM</a>)
207 </li>
208 <li> EDMA3 Driver Application Programming Interface Reference Guide (<a
209 href="packages/ti/sdo/edma3/drv/docs/html/index.html">HTML</a> | <a
210 href="packages/ti/sdo/edma3/drv/docs/EDMA3_Driver.chm">CHM</a>) </li>
211 <li> <a href="examples/CSL2_DAT_DEMO/docs/CSL_DAT_Adapter.ppt">CSL
212 2.x DAT Reference Implementation on EDMA3 Hardware using EDMA3 LLD</a> </li>
213 </ul>
214 <hr>
215 <a name="Whats_New"></a>
216 <h2><a name="Whats_New">What's New</a></h2>
218 <p>
219 <a name="Whats_New">The following significant changes have been made since 02.11.05:
220 </a></p>
222 <p><a name="Whats_New">02.11.06 - This release
223 </a></p>
225 <p>
226 <a name="Whats_New">The following IRs are implemented:
227 </a></p>
229 <table width="100%">
230 <tbody>
231 <tr>
232 <th>ID</th>
233 <th>Headline</th>
234 </tr>
236 <tr>
237 <td width="200">SDOCM00090630</td>
238 <td>Documentation update: workaround for building on windows 7</td>
239 </tr>
241 <tr>
242 <td width="200">SDOCM00092324</td>
243 <td>EDMA_DRV_SAMPLE [C6A811x]: The cross bar event is not initialized for platform C6A811x (J5Eco)</td>
244 </tr>
246 <tr>
247 <td width="200">SDOCM00092758</td>
248 <td>EDMA3 LLD: edma3_drv_bios6_c6472_st_sample and edma3_drv_bios6_c6472be_st_sample projects do not link</td>
249 </tr>
251 <tr>
252 <td width="200">SDOCM00092759</td>
253 <td>EDMA3 LLD: edma3_drv_bios6_c6748_st_sample does not build</td>
254 </tr>
256 </tbody>
257 </table>
259 <p>
260 <a name="Whats_New"><FONT COLOR ='RED'>The following IRs are raised on this release:<b>Known Issues</b></FONT>
261 </a></p>
262 <table width="100%">
263 <tbody>
264 <tr>
265 <th>ID</th>
266 <th>Headline</th>
267 </tr>
269 <tr>
270 <td width="200"><FONT COLOR ='RED'>SDOCM00078640</FONT></td>
271 <td><FONT COLOR ='RED'>ARM 9 support for OMAPL138 is not available on Make based build of EDMA3LLD</FONT></td>
272 </tr>
274 <tr>
275 <td width="200"><FONT COLOR ='RED'>SDSCM00039169</FONT></td>
276 <td><FONT COLOR ='RED'>EDMA3 Example fails for following Big Endian Simulators targets tci6608-sim/tci6616-sim</FONT></td>
277 </tr>
279 </tbody>
280 </table>
282 <br>
283 <hr><a name="Upgrade_Info"></a>
284 <h2><a name="Upgrade_Info">Upgrade Information</a></h2>
285 <p>
286 The EDMA3 LLD packages are available in the "packages/" subdirectory of
287 the product.
288 If you have a previous release of the EDMA3 LLD product, you can
289 install this
290 release next to it, and modify your application and/or server builds to
291 use this
292 newer release.
293 </p>
294 <hr>
295 <a name="Device_Support"></a>
296 <h2><a name="Device_Support">Device Support</a></h2>
297 <p>
298 This release supports and has been tested on the following devices:
299 </p>
300 <ul>
301 <a name="Device_Support"> <li>DA830 EVM:
302 <ul type="circle">
303 <li>C67x SYS/BIOS</li>
304 </ul>
305 </li>
306 <li>TCI6498 Simulator:</li>
307 </a>
308 <ul>
309 <li>C64X+ SYS/BIOS</li>
310 </ul>
311 <li>C6748 EVM:</li>
312 <li style="margin-left: 40px;" type="circle">C67x SYS/BIOS</li>
313 <li type="disc">OMAPL138 EVM:</li>
314 <li style="margin-left: 40px;" type="circle">C67x SYS/BIOS</li>
315 <li style="margin-left: 40px;" type="circle">ARM 9 SYSBIOS</li>
316 <li>TI816X EVM:</li>
317 </a>
318 <ul>
319 <li>C67X SYS/BIOS</li>
320 <li>A8 SYS/BIOS</li>
321 <li>M3 SYS/BIOS</li>
322 </ul>
323 <li>C6472 EVM:</li>
324 </a>
325 <ul>
326 <li>C64X+ SYS/BIOS</li>
327 </ul>
328 <li>TCI6486 EVM:</li>
329 </a>
330 <ul>
331 <li>C64X+ SYS/BIOS</li>
332 </ul>
333 <li>TI814X EVM:</li>
334 </a>
335 <ul>
336 <li>C67X SYS/BIOS</li>
337 <li>A8 SYS/BIOS</li>
338 <li>M3 SYS/BIOS</li>
339 </ul>
340 <li>TI811X EVM:</li>
341 </a>
342 <ul>
343 <li>C67X SYS/BIOS</li>
344 <li>A8 SYS/BIOS</li>
345 <li>M3 SYS/BIOS</li>
346 </ul>
347 <li>C6670 EVM:</li>
348 </a>
349 <ul>
350 <li>C66X SYS/BIOS</li>
351 </ul>
352 <li>C6678 EVM:</li>
353 </a>
354 <ul>
355 <li>C66X SYS/BIOS</li>
356 </ul>
357 <li>TCI6608 Simulator:</li>
358 </a>
359 <ul>
360 <li>C66X SYS/BIOS</li>
361 </ul>
362 <li>TCI6616 Simulator:</li>
363 </a>
364 <ul>
365 <li>C66X SYS/BIOS</li>
366 </ul>
367 <li>TCI6614 EVM:</li>
368 </a>
369 <ul>
370 <li>C66X SYS/BIOS</li>
371 </ul>
372 </ul>
373 <hr>
374 <a name="Compatibility"></a>
375 <h2><a name="Compatibility">Compatibility Information</a></h2>
376 <h3><a name="Compatibility">Compatibility Key Definitions</a></h3>
377 <p>
378 Compatibility keys are intentionally independent of Marketing product
379 numbers
380 and are intended to:
381 </p>
382 <ol start="1" type="1">
383 <a name="Compatibility"> <li> Enable tooling to identify
384 incompatibilities between components, and </li>
385 <li> Convey a level of compatibility between different releases to
386 set end user expectations. </li>
387 </a>
388 </ol>
389 <p>
390 Compatibility keys are composed of 3 comma-delimited numbers - M, S, R
391 - where:
392 </p>
393 <ul type="disc">
394 <a name="Compatibility"> <li> <b>M = Major</b>. A difference in M
395 indicates a break in compatibility. </li>
396 <li> <b>S = Source</b>. A difference in S indicates source
397 compatibility. That is, the user's source doesn't require change, but <i>does</i>
398 require rebuilding. </li>
399 <li> <b>R = Radix</b>. A difference in R indicates an introduction
400 of new features, but compatibility with previous interfaces has not
401 broken. If libraries are provided by the package, an application must
402 re-link with the new libraries, but not rebuild from source. </li>
403 </a>
404 </ul>
405 <hr>
406 <a name="Validation"></a>
407 <h2><a name="Validation">Validation</a></h2>
408 <p>
409 This release was built and validated against using the following
410 components:
411 </p>
412 <ul type="disc">
413 <a name="Validation"> <li>CCS 5.0.2</li>
414 <li>C6x Code Generation Tools version 7.3.1 </li>
415 <li>TMS470 Code Generation Tools 4.9.2</li>
416 <li>SYS/BIOS 6.33.03.33</li>
417 <li>XDC Tools 3.23.01.43</li>
418 <li>TCI6498 Simulator 0.7.1</li>
419 </a>
420 </ul>
421 <p>
422 This release was validated in the following configurations:
423 </p>
424 <ul>
425 <li> DA830 EVM:
426 <ul type="circle">
427 <li>C67x SYS/BIOS</li>
428 </ul>
429 </li>
430 <li> TCI6498 Simulator:
431 <ul type="circle">
432 <li>C64X+ SYS/BIOS</li>
433 </ul>
434 </li>
435 <li>C6748 EVM:</li>
436 <li style="margin-left: 40px;" type="circle">C67x SYS/BIOS</li>
437 <li>OMAPL138 EVM:</li>
438 <ul>
439 <li>C67x SYS/BIOS</li>
440 <li>ARM 9 SYSBIOS</li>
441 </ul>
442 <li>TI816X EVM:</li>
443 </a>
444 <ul>
445 <li>C67X SYS/BIOS</li>
446 <li>A8 SYS/BIOS</li>
447 <li>M3 SYS/BIOS</li>
448 </ul>
449 <li>C6472 EVM:</li>
450 </a>
451 <ul>
452 <li>C64X+ SYS/BIOS</li>
453 </ul>
454 <li>TCI6486 EVM:</li>
455 </a>
456 <ul>
457 <li>C64X+ SYS/BIOS</li>
458 </ul>
459 <li>TI814X EVM:</li>
460 </a>
461 <ul>
462 <li>C67X SYS/BIOS</li>
463 <li>A8 SYS/BIOS</li>
464 <li>M3 SYS/BIOS</li>
465 </ul>
466 <li>TI811X EVM:</li>
467 </a>
468 <ul>
469 <li>C67X SYS/BIOS</li>
470 <li>A8 SYS/BIOS</li>
471 <li>M3 SYS/BIOS</li>
472 </ul>
473 <li>C6670 EVM:</li>
474 </a>
475 <ul>
476 <li>C66X SYS/BIOS</li>
477 </ul>
478 <li>C6678 EVM:</li>
479 </a>
480 <ul>
481 <li>C66X SYS/BIOS</li>
482 </ul>
483 <li>TCI6608 Simulator:</li>
484 </a>
485 <ul>
486 <li>C66X SYS/BIOS</li>
487 </ul>
488 <li>TCI6616 Simulator:</li>
489 </a>
490 <ul>
491 <li>C66X SYS/BIOS</li>
492 </ul>
493 <li>TCI6614 EVM:</li>
494 </a>
495 <ul>
496 <li>C66X SYS/BIOS</li>
497 </ul>
498 </ul>
499 <hr><a name="Known_Issues">
500 </a>
501 <h2><a name="Known_Issues">Known Issues</a></h2>
502 <p>
503 The following are known issues with the current EDMA3 LLD release:
504 </p>
505 <h4><a name="Known_Issues">Pre-built instrumented libraries for DA830
506 not provided initially.</a></h4>
507 <p>Pre-built instrumented EDMA3 libraries for DA830 will not be
508 provided
509 initially. XDC does not support the same and hence the limitation. See
510 IR#
511 SDOCM00036738 for more details.
512 </p>
513 <h4><a name="Known_Issues">EDMA3 hardware does not work properly in
514 FIFO mode with all the controllers.</a></h4>
515 <p>Very few peripherals support EDMA3 FIFO mode. EMIF controller
516 doesn't support
517 the same. So EDMA3 CANNOT be used in FIFO mode for doing a
518 memory-to-memory data
519 transfers, EDMA3 being configured in the FIFO mode. Applications trying
520 to use
521 EDMA3 in FIFO mode should first check their respective
522 peripheral-controller
523 document for this mode support.
524 </p>
525 <h4><a name="Known_Issues">PingPong Example Fails for certain EDMA
526 instances for some DSP cores in Release mode only.</a></h4>
527 <p>The PingPong example in the package fails for certain EDMA Instances
528 for some DSP cores in Release mode only. It passes for Debug mode. See
529 IR#
530 SDOCM00064758 for more details.
531 </p>
532 <hr>
533 <a name="Examples"></a>
534 <h2><a name="Examples">Examples</a></h2>
535 <p>
536 EDMA3 LLD sample initialization libraries / OS abstraction layers (for
537 different
538 platforms) are located in:
539 </p>
540 <ul type="disc">
541 <a name="Examples"> <li> For Resource Manager: They could be located
542 in <tt>edma3_lld_02_11_06_XX\packages\ti\sdo\edma3\rm\sample\lib</tt>
543 folder. </li>
544 <li> For EDMA3 Driver: They could be located in <tt>edma3_lld_02_11_06_XX\packages\ti\sdo\edma3\drv\sample\lib</tt>
545 folder. </li>
546 </a>
547 </ul>
548 <p>
549 EDMA3 LLD stand-alone applications (for different platforms) are
550 located in:
551 </p>
552 <ul type="disc">
553 <a name="Examples"> <li> EDMA3 Driver: They could be located in <tt>edma3_lld_02_11_06_XX\examples\edma3_driver\</tt>
554 folder. </li>
555 </a>
556 </ul>
557 <ul type="disc">
558 <a name="Examples"> <li> CSL2.x DAT Reference Implementation: It
559 could be located in <tt>edma3_lld_02_11_06_XX\examples\CSL2_DAT_DEMO\</tt>
560 folder. </li>
561 </a>
562 </ul>
563 <hr>
564 <a name="Version"></a>
565 <h2><a name="Version">Version Information</a></h2>
566 <p>
567 This product's version follows a version format, <b>M.mm.pp.bb</b>,
568 where
569 <b>M</b> is a 2 digit major number,
570 <b>mm</b> is 2 digit minor number,
571 <b>pp</b> is a 2 digit patch number, and
572 <b>b</b> is an unrestricted set of digits used as an incrementing build
573 counter.
574 </p>
575 <p>
576 To support multiple side-by-side installations of the product, the
577 product
578 version is encoded in the top level directory, ex. <b>edma3_lld_02_11_06_XX</b>.
579 </p>
580 <p>Subsequent releases of patch upgrades will be identified by the
581 patch number,
582 ex. EDMA3 LLD 02.11.06 with directory <b>edma3_lld_02_11_06_YY</b>.
583 Typically, these
584 patches only include critical bug fixes.
585 </p>
586 <hr>
587 <a name="Support"></a>
588 <h2><a name="Support">Technical Support</a></h2>
589 <p>
590 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>
591 </p>
592 <hr>
593 <p>Last updated: Aug 10, 2012
594 </p>
595 </body>
596 </html>