. . ENDSEC The SECTION directive defines the start of a section. All symbols that are defined within a section have the associated with them as their section name. This serves to protect them from like-named symbols elsewhere in the program. By default, a symbol defined inside any given section is private to that section unless the GLOBAL or LOCAL qualifier accompanies the SECTION directive. Any code or data inside a section is considered an indivisible block with respect to relocation. Code or data associated with a section is independently relocatable within the memory space to which it is bound, unless the STATIC qualifier follows the SECTION directive on the instruction line. Symbols within a section are generally distinct from other symbols used elsewhere in the source program, even if the symbol name is the same. This is true as long as the section name associated with each symbol is unique, the symbol is not declared public (XDEF/GLOBAL), and the GLOBAL or LOCAL qualifier is not used in the section declaration. Symbols that are defined outside of a section are considered global symbols and have no explicit section name associated with them. Global symbols may be referenced freely from inside or outside of any section, as long as the global symbol name does not conflict with another symbol by the same name in a given section. MOTOROLA DSP56302EMUM/AD, Preliminary For More Information On This Product, Go to: www.freescale.com C-57 Freescale Semiconductor, Inc. Motorola Assembler Notes Freescale Semiconductor, Inc... If the GLOBAL qualifier follows the

in the SECTION directive, then all symbols defined in the section until the next ENDSEC directive are considered global. The effect is as if every symbol in the section were declared with GLOBAL. This is useful when a section needs to be independently relocatable, but data hiding is not desired. If the STATIC qualifier follows the

in the SECTION directive, then all code and data defined in the section until the next ENDSEC directive are relocated in terms of the immediately enclosing section. The effect with respect to relocation is as if all code and data in the section were defined within the parent section. This is useful when a section needs data hiding, but independent relocation is not required. If the LOCAL qualifier follows the

in the SECTION directive, then all symbols defined in the section until the next ENDSEC directive are visible to the immediately enclosing section. The effect is as if every symbol in the section were defined within the parent section. This is useful when a section needs to be independently relocatable, but data hiding within an enclosing section is not required. The division of a program into sections controls not only labels and symbols, but also macros and DEFINE directive symbols. Macros defined within a section are private to that section and are distinct from macros defined in other sections even if they have the same macro name. Macros defined outside of sections are considered global and may be used within any section. Similarly, DEFINE directive symbols defined within a section are private to that section and DEFINE directive symbols defined outside of any section are globally applied. There are no directives that correspond to XDEF for macros or DEFINE symbols, and therefore, macros and DEFINE symbols defined in a section can never be accessed globally. If global accessibility is desired, the macros and DEFINE symbols should be defined outside of any section. Sections can be nested to any level. When the assembler encounters a nested section, the current section is stacked and the new section is used. When the ENDSEC directive of the nested section is encountered, the assembler restores the old section and uses it. The ENDSEC directive always applies to the most previous SECTION directive. Nesting sections provides a measure of scoping for symbol names, in that symbols defined within a given section are visible to other sections nested within it. For example, if section B is nested inside section A, then a symbol defined in section A can be used in section B without XDEFing in section A or XREFing in section B. This scoping behavior can be turned off and on with the NONS and NS options respectively (see the OPT directive, this chapter). C-58 DSP56302EMUM/AD, Preliminary For More Information On This Product, Go to: www.freescale.com MOTOROLA Freescale Semiconductor, Inc. Motorola Assembler Notes Freescale Semiconductor, Inc... Sections may also be split into separate parts. That is,

can be used multiple times with SECTION and ENDSEC directive pairs. If this occurs, then these separate (but identically named) sections can access each others symbols freely without the use of the XREF and XDEF directives. If the XDEF and XREF directives are used within one section, they apply to all sections with the same section name. The reuse of the section name is allowed to permit the program source to be arranged in an arbitrary manner (for example, all statements that reserve X space storage locations grouped together), but retain the privacy of the symbols for each section. When the assembler operates in relative mode (the default), sections act as the basic grouping for relocation of code and data blocks. For every section defined in the source a set of location counters is allocated for each DSP memory space. These counters are used to maintain offsets of data and instructions relative to the beginning of the section. At link time sections can be relocated to an absolute address, loaded in a particular order, or linked contiguously as specified by the programmer. Sections which are split into parts or among files are logically recombined so that each section can be relocated as a unit. Sections may be relocatable or absolute. In the assembler absolute mode (command line -A option) all sections are considered absolute. A full set of locations counters is reserved for each absolute section unless the GS option is given (see the OPT directive, this chapter). In relative mode, all sections are initially relocatable. However, a section or a part of a section may be made absolute either implicitly by using the ORG directive, or explicitly through use of the MODE directive. Note: A label is not allowed with this directive. Note: See also MODE, ORG, GLOBAL, LOCAL, XDEF, XREF. Example B-72 SECTION Directive SECTION MOTOROLA TABLES ; TABLES will be the section name DSP56302EMUM/AD, Preliminary For More Information On This Product, Go to: www.freescale.com C-59 Freescale Semiconductor, Inc. Motorola Assembler Notes C.3.52 Freescale Semiconductor, Inc... SET Set Symbol to a Value SET SET The SET directive is used to assign the value of the expression in the operand field to the label. The SET directive functions somewhat like the EQU directive. However, labels defined via the SET directive can have their values redefined in another part of the program (but only through the use of another SET directive). The SET directive is useful in establishing temporary or reusable counters within macros. The expression in the operand field of a SET must be absolute and cannot include a symbol that is not yet defined (no forward references are allowed). Note: See also EQU, GSET. Example B-73 SET Directive COUNT C.3.53 SET 0 ; INITIALIZE COUNT STITLE Initialize Program Sub-Title STITLE [] The STITLE directive initializes the program subtitle to the string in the operand field. The subtitle will be printed on the top of all succeeding pages until another STITLE directive is encountered. The subtitle is initially blank. The STITLE directive will not be printed in the source listing. An STITLE directive with no string argument will cause the current subtitle to be blank. Note: A label is not allowed with this directive. Note: See also TITLE. Example B-74 STITLE Directive STITLE C-60 'COLLECT SAMPLES' DSP56302EMUM/AD, Preliminary For More Information On This Product, Go to: www.freescale.com MOTOROLA Freescale Semiconductor, Inc. Motorola Assembler Notes C.3.54 SYMOBJ Write Symbol Information to Object File SYMOBJ [,,...,] The SYMOBJ directive causes information for each to be written to the object file. This directive is recognized but currently performs no operation in COFF assemblers. Note: A label is not allowed with this directive. Freescale Semiconductor, Inc... Example B-75 SYMOBJ SYMOBJ C.3.55 XSTART,HIRTN,ERRPROC TABS Set Listing Tab Stops TABS The TABS directive allows resetting the listing file tab stops from the default value of 8. Note: A label is not allowed with this directive. Note: See also LSTCOL. Example B-76 TABS Directive TABS C.3.56 4 ; Set listing file tab stops to 4 TITLE Initialize Program Title TITLE [] The TITLE directive initializes the program title to the string in the operand field. The program title will be printed on the top of all succeeding pages until another TITLE directive is encountered. The title is initially blank. The TITLE directive will not be printed in the source listing. A TITLE directive with no string argument will cause the current title to be blank. Note: A label is not allowed with this directive. MOTOROLA DSP56302EMUM/AD, Preliminary For More Information On This Product, Go to: www.freescale.com C-61 Freescale Semiconductor, Inc. Motorola Assembler Notes Note: See also STITLE. Example B-77 TITLE Directive TITLE C.3.57 'FIR FILTER' UNDEF Undefine DEFINE Symbol Freescale Semiconductor, Inc... UNDEF [] The UNDEF directive causes the substitution string associated with to be released, and will no longer represent a valid DEFINE substitution. See the DEFINE directive for more information. Note: A label is not allowed with this directive. Note: See also DEFINE. Example B-78 UNDEF Directive UNDEF C.3.58 DEBUG ; UNDEFINES THE DEBUG SUBSTITUTION STRING WARN Programmer Generated Warning WARN [{|}[,{|},...,{|}]] The WARN directive will cause a warning message to be output by the assembler. The total warning count will be incremented as with any other warning. The WARN directive is normally used in conjunction with conditional assembly directives for exceptional condition checking. The assembly proceeds normally after the warning has been printed. An arbitrary number of strings and expressions, in any order but separated by commas with no intervening white space, can be specified optionally to describe the nature of the generated warning. Note: A label is not allowed with this directive. Note: See also FAIL, MSG. Example B-79 WARN Directive WARN C-62 'parameter too large' DSP56302EMUM/AD, Preliminary For More Information On This Product, Go to: www.freescale.com MOTOROLA Freescale Semiconductor, Inc. Motorola Assembler Notes C.3.59 XDEF External Section Symbol Definition XDEF [,,...,] Freescale Semiconductor, Inc... The XDEF directive is used to specify that the list of symbols is defined within the current section, and that those definitions should be accessible by sections with a corresponding XREF directive. This directive is only valid if used within a program section bounded by the SECTION and ENDSEC directives. The XDEF directive must appear before is defined in the section. If the symbols that appear in the operand field are not defined in the section, an error will be generated. Note: A label is not allowed with this directive. Note: See also SECTION, XREF. Example B-80 XDEF Directive SECTION XDEF . . . ENDSEC C.3.60 IO LOOPA ; LOOPA will be accessible by sections with XREF XREF External Section Symbol Reference XREF [,,...,] The XREF directive is used to specify that the list of symbols is referenced in the current section, but is not defined within the current section. These symbols must either have been defined outside of any section or declared as globally accessible within another section using the XDEF directive. If the XREF directive is not used to specify that a symbol is defined globally and the symbol is not defined within the current section, an error will be generated, and all references within the current section to such a symbol will be flagged as undefined. The XREF directive must appear before any reference to in the section. Note: A label is not allowed with this directive. MOTOROLA DSP56302EMUM/AD, Preliminary For More Information On This Product, Go to: www.freescale.com C-63 Freescale Semiconductor, Inc. Motorola Assembler Notes Note: See also SECTION, XDEF. Example B-81 XREF Directive Freescale Semiconductor, Inc... SECTION XREF . . . ENDSEC C.4 FILTER AA,CC,DD ; XDEFed symbols within section STRUCTURED CONTROL STATEMENTS An assembly language provides an instruction set for performing certain rudimentary operations. These operations in turn may be combined into control structures such as loops (FOR, REPEAT, WHILE) or conditional branches (IF-THEN, IF-THEN-ELSE). The assembler, however, accepts formal, high-level directives that specify these control structures, generating the appropriate assembly language instructions for their efficient implementation. This use of structured control statement directives improves the readability of assembly language programs, without compromising the desirable aspects of programming in an assembly language. C.4.1 Structured Control Directives The following directives are used for structured control. Note the leading period, which distinguishes these keywords from other directives and mnemonics. Structured control directives may be specified in either upper or lower case, but they must appear in the opcode field of the instruction line (e.g. they must be preceded either by a label, a space, or a tab). .BREAK .CONTINUE .ELSE .ENDF .IF .ENDI .ENDL .ENDW .FOR .LOOP .REPEAT .UNTIL .WHILE In addition, the following keywords are used in structured control statements: C-64 DSP56302EMUM/AD, Preliminary For More Information On This Product, Go to: www.freescale.com MOTOROLA Freescale Semiconductor, Inc. Motorola Assembler Notes AND BY DO Note: Freescale Semiconductor, Inc... C.4.2 DOWNTO OR THEN TO AND, DO, and OR are reserved assembler instruction mnemonics. Syntax The formats for the .BREAK, .CONTINUE, .FOR, .IF, .LOOP, .REPEAT, and .WHILE statements are given in sections C.4.2.1 through C.4.2.7. Syntactic variables used in the formats are defined as follows: * --A simple or compound expression (section C.4.3). * --Zero or more assembler directives, structured control statements, or executable instructions. Note: An assembler directive occurring within a structured control statement is examined exactly once--at assembly time. Thus the presence of a directive within a .FOR, .LOOP, .REPEAT, or .WHILE statement does not imply repeated occurrence of an assembler directive; nor does the presence of a directive within an .IF-THEN-.ELSE structured control statement imply conditional assembly. * --A user-defined operand whose register/memory location holds the .FOR loop counter. The effective address must use a memory alterable addressing mode (e.g., it cannot be an immediate value). * --The initial value of the .FOR loop counter. The effective address may be any mode, and may represent an arbitrary assembler expression. * --The terminating value of the .FOR loop counter. The effective address may be any mode, and may represent an arbitrary assembler expression. * --The step (increment/decrement) of the .FOR loop counter each time through the loop. If not specified, it defaults to a value of #1. The effective address may be any mode, and may represent an arbitrary assembler expression. * --The terminating value in a .LOOP statement. This can be any arbitrary assembler expression. All structured control statements may be followed by normal assembler comments on the same logical line. MOTOROLA DSP56302EMUM/AD, Preliminary For More Information On This Product, Go to: www.freescale.com C-65 Freescale Semiconductor, Inc. Motorola Assembler Notes C.4.2.1 .BREAK Statement .BREAK The .BREAK statement causes an immediate exit from the innermost enclosing loop construct (.WHILE, .REPEAT, .FOR, .LOOP). A .BREAK statement does not exit an .IF-THEN-.ELSE construct. If a .BREAK is encountered with no loop statement active, a warning is issued. Freescale Semiconductor, Inc... Note: .BREAK should be used with care near .ENDL directives or near the end of DO loops. It generates a jump instruction which is illegal in those contexts. Example B-82 .BREAK Statement .WHILE x:(r1)+ #0;loop until zero is found . . . .IF .BREAK ;causes exit from WHILE loop .ENDI . . ;any instructions here are skipped . .ENDW ;execution resumes here after .BREAK C.4.2.2 .CONTINUE Statement .CONTINUE The .CONTINUE statement causes the next iteration of a looping construct (.WHILE, .REPEAT, .FOR, .LOOP) to begin. This means that the loop expression or operand comparison is performed immediately, bypassing any subsequent instructions. If a .CONTINUE is encountered with no loop statement active, a warning is issued. Note: C-66 .CONTINUE should be used with care near .ENDL directives or near the end of DO loops. It generates a jump instruction which is illegal in those contexts. DSP56302EMUM/AD, Preliminary For More Information On This Product, Go to: www.freescale.com MOTOROLA Freescale Semiconductor, Inc. Motorola Assembler Notes Note: One or more .CONTINUE directives inside a .LOOP construct will generate a NOP instruction just before the loop address. Freescale Semiconductor, Inc... Example B-83 .CONTINUE Statement .REPEAT . . . .IF .CONTINUE .ENDI . . . .UNTIL C.4.2.3 ;causes immediate jump to .UNTIL ;any instructions here are skipped x:(r1)+ #0;evaluation here after .CONTINUE .FOR Statement .FOR = {TO | DOWNTO} [BY ] [DO] .ENDF Initialize to and perform until is greater (TO) or less than (DOWNTO) . Makes use of a user-defined operand, , to serve as a loop counter. .FOR-TO allows counting upward, while .FOR-DOWNTO allows counting downward. The programmer may specify an increment/decrement step size in , or elect the default step size of #1 by omitting the BY clause. A .FOR-TO loop is not executed if is greater than upon entry to the loop. Similarly, a .FOR-DOWNTO loop is not executed if is less than . must be a writable register or memory location. It is initialized at the beginning of the loop, and updated at each pass through the loop. Any immediate operands must be preceded by a pound sign (# ). Memory references must be preceded by a memory space qualifier (X:, Y:, or P:). L memory references are not allowed. Operands must be or refer to single-word values. The logic generated by the .FOR directive makes use of several DSP data registers. In fact, two data registers are used to hold the step and target values, respectively, throughout the loop; they are never reloaded by the generated code. It is recommended that these registers not be used within the body of the loop, or that they be saved and restored prior to loop evaluation. MOTOROLA DSP56302EMUM/AD, Preliminary For More Information On This Product, Go to: www.freescale.com C-67 Freescale Semiconductor, Inc. Motorola Assembler Notes Note: The DO keyword is optional. Example B-84 .FOR Statement .FOR . . . .ENDF Freescale Semiconductor, Inc... C.4.2.4 X:CNT = #0 TO Y:(targ*2)+114; loop on X:CNT .IF Statement .IF [THEN] [.ELSE ] .ENDI If is true, execute following THEN (the keyword THEN is optional); if is false, execute following .ELSE, if present; otherwise, advance to the instruction following .ENDI. Note: In the case of nested .IF-THEN-.ELSE statements, each .ELSE refers to the most recent .IF-THEN sequence. Example B-85 .IF Statement .IF . . . .ENDI C.4.2.5 ; zero bit set? .LOOP Statement .LOOP .ENDL Execute times. This is similar to the .FOR loop construct, except that the initial counter and step value are implied to be #1. It is actually a shorthand method for setting up a hardware DO loop on the DSP, without having to worry about addressing modes or label placement. Since the .LOOP statement generates instructions for a hardware DO loop, the same restrictions apply as to the use of certain instructions near the end of the loop, nesting C-68 DSP56302EMUM/AD, Preliminary For More Information On This Product, Go to: www.freescale.com MOTOROLA Freescale Semiconductor, Inc. Motorola Assembler Notes restrictions, etc. One or more .CONTINUE directives inside a .LOOP construct will generate a NOP instruction just before the loop address. Example B-86 .LOOP Statement Freescale Semiconductor, Inc... .LOOP . . . .ENDL C.4.2.6 LPCNT ; hardware loop LPCNT times .REPEAT Statement .REPEAT .UNTIL is executed repeatedly until is true. When expression becomes true, advance to the next instruction following .UNTIL. The is executed at least once, even if is true upon entry to the .REPEAT loop. Example B-87 .REPEAT Statement .REPEAT . . . .UNTIL C.4.2.7 x:(r1)+ #0; loop until zero is found .WHILE Statement .WHILE [DO] .ENDW The is tested before execution of . While remains true, is executed repeatedly. When evaluates false, advance to the instruction following the .ENDW statement. If is false upon entry to the .WHILE loop, is not executed; execution continues after the .ENDW directive. MOTOROLA DSP56302EMUM/AD, Preliminary For More Information On This Product, Go to: www.freescale.com C-69 Freescale Semiconductor, Inc. Motorola Assembler Notes Note: The DO keyword is optional. Example B-88 .WHILE Statement Freescale Semiconductor, Inc... .WHILE . . . .ENDW C.4.3 x:(r1)+ #0; loop until zero is found Simple and Compound Expressions Expressions are an integral part of .IF, .REPEAT, and .WHILE statements. Structured control statement expressions should not be confused with the assembler expressions. The latter are evaluated at assembly time and will be referred to here as "assembler expressions"; they can serve as operands in structured control statement expressions. The structured control statement expressions described below are evaluated at run time and will be referred to in the following discussion simply as "expressions". A structured control statement expression may be simple or compound. A compound expression consists of two or more simple expressions joined by either AND or OR (but not both in a single compound expression). C.4.3.1 Simple Expressions Simple expressions are concerned with the bits of the Condition Code Register (CCR). These expressions are of two types. The first type merely tests conditions currently specified by the contents of the CCR (section C.4.3.2). The second type sets up a comparison of two operands to set the condition codes, and afterwards tests the codes. C.4.3.2 Condition Code Expressions A variety of tests (identical to those in the Jcc instruction) may be performed, based on the CCR condition codes. The condition codes, in this case, are preset by either a user-generated instruction or a structured operand-comparison expression. Each test is expressed in the structured control statement by a mnemonic enclosed in angle brackets. C-70 DSP56302EMUM/AD, Preliminary For More Information On This Product, Go to: www.freescale.com MOTOROLA Freescale Semiconductor, Inc. Motorola Assembler Notes When processed by the assembler, the expression generates an inverse conditional jump to beyond the matching .ENDx/.UNTIL directive. Example B-89 Condition Code Expression + + Freescale Semiconductor, Inc... + + .IF bne CLR .ENDI Z_L00002 .REPEAT Z_L00034 SUB .UNTIL bge Z_L00002 D1 D7,D0 Z_L00034 ;zero bit set? ;code generated by assembler ;user code ;assembler-generated label ;subtract until D0 < D7 ;assembler-generated label ;user code ;code generated by assembler C.4.3.3 Operand Comparison Expressions Two operands may be compared in a simple expression, with subsequent transfer of control based on that comparison. Such a comparison takes the form: where is a condition mnemonic enclosed in angle brackets (as described in section C.4.3.2), and and are register or memory references, symbols, or assembler expressions. When processed by the assembler, the operands are arranged such that a compare/jump sequence of the following form always results: CMP (J|B)cc , where the jump conditional is the inverse of . Ordinarily is moved to the data register and is moved to the data register prior to the compare. This is not always the case, however: if happens to be and is , an intermediate register is used as a scratch register. In any event, worst case code generation for a given operand comparison expression is generally two moves, a compare, and a conditional jump. Jumps or branches generated by structured control statements are forced long because the number and address of intervening instructions between a control statement and its termination are not known by the assembler. The programmer may circumvent this behavior by use of the SCSJMP directive. Any immediate operands must be preceded by a pound sign (# ). Memory references must be preceded by a memory space qualifier (X:, Y:, or P:). L memory references are not allowed. Operands must be or refer to single-word values. MOTOROLA DSP56302EMUM/AD, Preliminary For More Information On This Product, Go to: www.freescale.com C-71 Freescale Semiconductor, Inc. Motorola Assembler Notes Freescale Semiconductor, Inc... Note that values in the and data registers are not saved before expression evaluation. This means that any user data in those registers will be overwritten each time the expression is evaluated at runtime. The programmer should take care either to save needed contents of the registers, reassign data registers using the SCSREG directive, or not use them at all in the body of the particular structured construct being executed. C.4.3.4 Compound Expressions A compound expression consists of two or more simple expressions (section C.4.3.1) joined by a logical operator (AND or OR). The boolean value of the compound expression is determined by the boolean values of the simple expressions and the nature of the logical operator. Note that the result of mixing logical operators in a compound expression is undefined: .IF .IF X1 B AND AND R1 R2;this is OK X1 B AND OR R5 R6;undefined The simple expressions are evaluated left to right. Note that this means the result of one simple expression could have an impact on the result of subsequent simple expressions, because of the condition code settings stemming from the assembler-generated compare. If the compound expression is an AND expression and one of the simple expressions is found to be false, any further simple expressions are not evaluated. Likewise, if the compound expression is an OR expression and one of the simple expressions is found to be true, any further simple expressions are not evaluated. In these cases, the compound expression is either false or true, respectively, and the condition codes reflect the result of the last simple expression evaluated. C.4.3.5 Statement Formatting The format of structured control statements differs somewhat from normal assembler usage. Whereas a standard assembler line is split into fields separated by blanks or tabs, with no white space inside the fields, structured control statement formats vary depending on the statement being analyzed. In general, all structured control directives are placed in the opcode field (with an optional label in the label field) and white space separates all distinct fields in the statement. Any structured control statement may be followed by a comment on the same logical line. C.4.3.6 Expression Formatting Given an expression of the form: OR C-72 DSP56302EMUM/AD, Preliminary For More Information On This Product, Go to: www.freescale.com MOTOROLA Freescale Semiconductor, Inc. Motorola Assembler Notes there must be white space (blank, tab) between all operands and their associated operators, including boolean operators in compound expressions. Moreover, there must be white space between the structured control directive and the expression, and between the expression and any optional directive modifier (THEN, DO). An assembler expression used as an operand in a structured control statement expression must not have white space in it, since it is parsed by the standard assembler evaluation routines: Freescale Semiconductor, Inc... .IF #@CVI(@SQT(4.0)) #2; no white space in first operand C.4.3.7 .FOR/.LOOP Formatting The .FOR and .LOOP directives represent special cases. The .FOR structured control statement consists of several fields: .FOR = TO BY DO There must be white space between all operands and other syntactic entities such as =, TO, BY, and DO. As with expression formatting, an assembler expression used as an operand must not have white space in it: .FOR X:CNT = #0 TO Y:(targ*2)+1 BY #@CVI(@POW(2.0,@CVF(R))) In the example above, the .FOR loop operands represented as assembler expressions (symbol, function) do not have embedded white space, whereas the loop operands are always separated from structured control statement keywords by white space. The count field of a .LOOP statement must be separated from the .LOOP directive by white space. The count itself may be any arbitrary assembler expression, and therefore must not contain embedded blanks. C.4.4 Assembly Listing Format Structured control statements begin with the directive in the opcode field; any optional label is output in the label field. The rest of the statement is left as is in the operand field, except for any trailing comment; the X and Y data movement fields are ignored. Comments following the statement are output in the comment field (unless the unreported comment delimiter is used). Statements are expanded using the macro facilities of the assembler. Thus the generated code can be sent to the listing by specifying the MEX assembler option, either via the OPT directive or the -O command line option. MOTOROLA DSP56302EMUM/AD, Preliminary For More Information On This Product, Go to: www.freescale.com C-73 Freescale Semiconductor, Inc. Motorola Assembler Notes C.4.5 Effects on the Programmer's Environment Freescale Semiconductor, Inc... During assembly, global labels beginning with "Z_L" are generated. They are stored in the symbol table and should not be duplicated in user-defined labels. Because these non-local labels ordinarily are not visible to the programmer there can be problems when local (underscore) labels are interspersed among structured control statements. The SCL option (see the OPT directive) causes the assembler to maintain the current local label scope when a structured control statement label is encountered. In the.FOR loop, is a user-defined symbol. When exiting the loop, the memory/register assigned to this symbol contains the value which caused the exit from the loop. A compare instruction is produced by the assembler whenever two operands are tested in a structured statement. At runtime, these assembler-generated instructions set the condition codes of the CCR (in the case of a loop, the condition codes are set repeatedly). Any user-written code either within or following a structured statement that references CCR directly (move) or indirectly (conditional jump/transfer) should be attentive to the effect of these instructions. Jumps or branches generated by structured control statements are forced long because the number and address of intervening instructions between a control statement and its termination are not known by the assembler. The programmer may circumvent this behavior by use of the SCSJMP directive. In all structured control statements except those using only a single condition code expression, registers are used to set up the required counters and comparands. In some cases, these registers are effectively reserved; the.FOR loop uses two data registers to hold the step and target values, respectively, and performs no save/restore operations on these registers. The assembler, in fact, does no save/restore processing in any structured control operation; it simply moves the operands into appropriate registers to execute the compare. The SCSREG directive may be used to reassign structured control statement registers. The MEX assembler option (see the OPT directive may be used to send the assembler-generated code to the listing file for examination of possible register use conflicts. C-74 DSP56302EMUM/AD, Preliminary For More Information On This Product, Go to: www.freescale.com MOTOROLA Freescale Semiconductor, Inc. APPENDIX D Freescale Semiconductor, Inc... CODEC PROGRAMMING TUTORIAL MOTOROLA DSP56302EMUM/AD, Preliminary For More Information On This Product, Go to: www.freescale.com D-1 Freescale Semiconductor, Inc. Codec Programming Tutorial INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-3 PROGRAMMING THE CODEC. . . . . . . . . . . . . . . . . . . . . . . D-3 ECHO.ASM PROGRAM DESCRIPTION . . . . . . . . . . . . . . . D-3 Freescale Semiconductor, Inc... D.1 D.2 D.3 D-2 DSP56302EMUM/AD, Preliminary For More Information On This Product, Go to: www.freescale.com MOTOROLA Freescale Semiconductor, Inc. Codec Programming Tutorial D.1 INTRODUCTION Freescale Semiconductor, Inc... OK, you've got a new toy and you can't wait to start developing application. But first you've got the task of reading and understanding all the seemingly endless pages of specifications, manuals, and related documentation. How are you going to get that killer application ready quickly and sold in time to make this month's mortgage? Well, we can't promise help with your banker, but we can save you some time by easing that initial foray into the codec documentation. D.2 PROGRAMMING THE CODEC The good news is that the Crystal Semiconductor CS4215 codec ("COder-DECoder") used on the DSP56302EVM offers a myriad of options that are all user-programmable via software. The bad news is that you have to learn how to program it. A first scan of the CS4215 codec literature might lead you to conclude that the greatest obstacle between you and your goals is in learning to program the myriad of user-programmable features. To help you begin, there is an example program named ECHO.ASM that is included in the software shipped with the DSP56302EVM kit. This program is our effort to isolate the user from the details of programming the various CS4215 codec options. This appendix is provided to lead a new user through ECHO.ASM and help to explain how to use the tools developed to let you communicate most expediently with the analog world. So, let's get started. D.3 ECHO.ASM PROGRAM DESCRIPTION The ECHO.ASM program actually creates one of two versions from the same source code file. One version is the stand-alone program that is examined in this appendix. The other a version is loaded into the FLASH EPROM as a part of the code shipped with the self-test program. A batch file MAKEECHO.BAT included with the software allows the user to create the stand-alone demonstration. A command line entry uses parameters that invoke the DSP56300 assembler program, selects the stand-alone version of the routine, and generates an executable module. The command line, which can either be typed in or executed from a batch file, is: asm56300 -d STANDALONE 1 -a -b -l -g echo.asm MOTOROLA DSP56302EMUM/AD, Preliminary For More Information On This Product, Go to: www.freescale.com D-3 Freescale Semiconductor, Inc. Codec Programming Tutorial The command line entry generates the ECHO.ASM file. The following sections described the contents and format of this file. Begin by viewing the contents of the ECHO.ASM file. Set up the listing format as 132 columns and 60 line per page and display the file, or print it out on a printer. D.3.1 Source Code Description Freescale Semiconductor, Inc... The ECHO.ASM file starts with a banner followed by a general description of the program and copyright notice: Example B-90 Program Description page 132,60 ;**************************************************************************** ; ECHO.ASM Ver.2.0 ; Example program to move audio through CS4215 ; This program uses 2k samples of delay ; to add a noticeable echo to the audio. ; ; Copyright (c) MOTOROLA 1995, 1996 ; Semiconductor Products Sector ; Digital Signal Processing Division ; ;**************************************************************************** This is followed by the following sections of code: * Included files * Constant definitions * Interrupt buffers * Sample program listing D-4 DSP56302EMUM/AD, Preliminary For More Information On This Product, Go to: www.freescale.com MOTOROLA Freescale Semiconductor, Inc. Codec Programming Tutorial D.3.1.1 Included Files The file includes references to four included files: Example B-91 Included Files Freescale Semiconductor, Inc... ;--------------------------------------------IF (STANDALONE==1) nolist include include include include list `ioequ.asm' `intequ.asm' `ada_equ.asm' `vectors.asm' ;****************************************************************************** ; the following EQUates will define the operational parameters ; of the codec. Please refer to the ADA_EQU.ASM source file ; for a description of the parameters selections available. The ; variables defined by the EQUates are sent to the codec via ; the transmit buffer, TX_BUFF. ; ; Since the parameters are defined in ADA_EQU.ASM, these lines must ; follow the include statement. ;****************************************************************************** These files perform the following functions: * IOEQU.ASM defines a standard set of symbolic names for the addresses of the on-chip peripheral registers. * INTEQU.ASM sets up the interrupt definitions. * ADA_EQU.ASM defines the registers, parameters and bit mapping of the CS4215. This is the key to facilitating the selection of the codec's functions. * VECTORS.ASM defines the interrupt vectors required by the interrupt handlers. MOTOROLA DSP56302EMUM/AD, Preliminary For More Information On This Product, Go to: www.freescale.com D-5 Freescale Semiconductor, Inc. Codec Programming Tutorial D.3.1.2 Constant Definitions The next 4 lines of the program construct the constants that define the feature selections which are made during initialization of the codec. Example B-92 Constant Definitions Freescale Semiconductor, Inc... CTRL_WD_12 CTRL_WD_34 CTRL_WD_56 CTRL_WD_78 equ equ equ equ NO_PREAMP+HI_PASS_FILT+SAMP_RATE_48+STEREO+DATA_16;CLB=0 IMMED_3STATE+XTAL1_SELECT+BITS_64+CODEC_MASTER $000000 $000000 TONE_OUTPUT EQU HEADPHONE_EN+LINEOUT_EN+(0*LEFT_ATTN)+(0*RIGHT_ATTN) TONE_INPUT EQU MIC_IN_SELECT+(15*MONITOR_ATTN)+(8*LEFT_GAIN)+(8*RIGHT_GAIN) Among the features initialized at this time are sample rate, data format, clock selection and interface mechanism. These are features which generally require re-initialization when altered. By referring to the ADA_EQU.ASM file, the user can view the constants available for specifying the different feature options. The two lines that follow construct `tone_output' and `tone_input' are the constants that define those feature selections available when the analog subsystem is running. This includes such features as gain, mixer and attenuator settings. D.3.1.3 Interrupt Buffers The CS4215 interrupt routines used by this software are based on 2 four word buffers, one each for transmit data and receive data. The lines shown in allocate eight words of data memory, starting at address x:000000. These are the buffers used by the interrupt handler. Example B-93 Interrupt Buffers ;---Buffer for talking to the CS4215 org D-6 x:0 RX_BUFF_BASE equ * RX_data_1_2 ds 1 RX_data_3_4 ds 1 RX_data_5_6 ds 1 RX_data_7_8 ds 1 ;data ;data ;data ;data time time time time slot slot slot slot 1/2 3/4 5/6 7/8 for for for for RX RX RX RX ISR ISR ISR ISR TX_BUFF_BASE equ * TX_data_1_2 ds 1 TX_data_3_4 ds 1 TX_data_5_6 ds 1 TX_data_7_8 ds 1 ;data ;data ;data ;data time time time time slot slot slot slot 1/2 3/4 5/6 7/8 for for for for TX TX TX TX ISR ISR ISR ISR RX_PTR ds 1 TX_PTR ds 1 ;Pointer for rx buffer ;Pointer for tx buffer DSP56302EMUM/AD, Preliminary For More Information On This Product, Go to: www.freescale.com MOTOROLA Freescale Semiconductor, Inc. Codec Programming Tutorial D.3.1.4 Sample Program This portion of the code starts at P:000000. This code initializes the DSP and codec and performs the example operations. It begins by setting the on-chip PLL multiplier to run the DSP at a higher frequency. The number of external bus wait states is set up (1 one Wait State in all external spaces is selected here). The program runs initializes all the internal registers and buffers. Then a separate program initializes the codec. Finally, the last part of the program processes the analog data as specified. This last part ends the conditional assembly code (ENDIF). Freescale Semiconductor, Inc... Example B-94 Sample Program Listing org P:$100 START main movep #$040005,x:M_PCTL movep #012421,x:M_BCR ENDIF ;------------------------------ ;PLL = 6 x 16.9344Mhz = 101.6Mhz org p: echo movec #0,SP move #0,SC ori #3,mr movep #$040005,x:M_PCTL movep #$11,x:M_TCSR0 move #$40,r6 move #-1,m6 move #RX_BUFF_BASE,x0 move x0,x:RX_PTR move #TX_BUFF_BASE,x0 move x0,x:TX_PTR ; --- INIT THE CODEC --jsr ada_init move #$0400,r4 move #$03FF,m4 MOTOROLA ; ; ; ; ; ; ; clear stack pointer clear stack counter disable interrupts PLL = 16.9344 x 6 = 101.6Mhz turn LED off initialize stack pointer linear addressing ; Initialize the rx pointer ; Initialize the tx pointer ; Jump to initialize the codec ; echo buffer starts at $400 ;...and is 1024 deep DSP56302EMUM/AD, Preliminary For More Information On This Product, Go to: www.freescale.com D-7 Freescale Semiconductor, Inc. Codec Programming Tutorial Example B-94 Sample Program Listing (Continued) ;========================================================================== ; this is where the work gets done... ; loop_1 jset #2,x:M_SSISR0,* ; Wait for frame sync to pass. jclr #2,x:M_SSISR0,* ; Wait for frame sync. Freescale Semiconductor, Inc... move x:RX_BUFF_BASE,a move x:RX_BUFF_BASE+1,b asr a x:(r4),x0 asr b y:(r4),y0 add x0,a add y0,b asr a asr b move a,x:(r4) move b,y:(r4)+ move a,x:TX_BUFF_BASE move b,x:TX_BUFF_BASE+1 move #TONE_OUTPUT,y0 move y0,x:TX_BUFF_BASE+2 move #TONE_INPUT,y0 move y0,x:TX_BUFF_BASE+3 jmp loop_1 IF (STANDALONE==1) nolist include `ada_init.asm' list ENDIF D-8 ; get new samples ; divide them by 2 and get oldest ; samples from buffer ; add the new samples and the old ; reduce magnitude of new data ; save the altered samples ; and bump the pointer ; Put value in left channel tx. ; Put value in right channel tx. ; headphones, line out, mute spkr, no attn. ; no input gain, monitor mute ; Loop back. ; load the code init routines DSP56302EMUM/AD, Preliminary For More Information On This Product, Go to: www.freescale.com MOTOROLA Freescale Semiconductor, Inc. INDEX Freescale Semiconductor, Inc... Symbols " C-7 # C-11 #< C-11 #> C-12 % C-6 * C-8 ++ C-9 ; C-3 ;; C-4 < C-10 << C-9 > C-10 ? C-5 @ C-8 \ C-4 ^ C-6 A A/D converter 4-10 AAR0 4-8 programming 4-7 Address Attribute Pin Polarity Bit, BAAP 4-7 Address Attribute Pin, AA0 4-6 Address Attribute Pin, AA1 4-9 Address Attribute Pin, AA3 4-6 Address Attribute Register (AAR0) 4-8 Address Attribute Register, AAR0 4-7 Address Muxing Bit, BAM 4-7 Address Pins, A(0:17) 4-6, 4-9 Address to Compare Bits, BAC(11:0) 4-8 Addressing I/O short C-9 immediate C-11 long C-10 long immediate C-12 short C-10 short immediate C-11 Analog Circuitry Test 1-9 Analog Input/Output 4-11 Assembler 3-16 mode C-40 option C-42 MOTOROLA warning C-49 assembler 3-3 control 3-12 data definition/storage allocation 3-12, 3-13 directives 3-11 listing control and options 3-14 macros and conditional assembly 3-15 object file control 3-14 options 3-8 significant characters 3-11 structured programming 3-15 symbol definition 3-12, 3-13 assembler control 3-12 assembler directives 3-11 assembler options 3-8 assembling the example program 3-16 assembling the program 3-7 assembly programming 3-3 Audio Codec 4-3 audio codec 4-10 Audio Codec Clock 4-13 Audio Codec Common Headphone Return Pin, HEADC 4-11 Audio Codec Crystals 4-13 Audio Codec Data/Control Select Pin, D/C 4-12 Audio Codec Digital Interface 4-12 Audio Codec Frame Sync Pin, FSYNC 4-12 Audio Codec Left Headphone Output Pin, HEADL 4-11 Audio Codec Left Line Output Pin, LOUTL 4-11 Audio Codec Left Microphone Input Pin, MINL 4-11 Audio Codec Reset Pin, RESET 4-12 Audio Codec Right Headphone Output Pin, HEADR 4-11 Audio Codec Right Line Output Pin, LOUTR 4-11 Audio Codec Right Microphone Input Pin, MINR 4-11 Audio Codec Serial Data Input Pin, SDIN 4-12 Audio Codec Serial Data Output Pin, SDOUT 4-12 Audio Codec Serial Port Clock Pin, SCLK 4-12 audio interface cable 1-4, 1-9 audio source 1-4 DSP56302EMUM/AD For More Information On This Product, Go to: www.freescale.com Index-1 Freescale Semiconductor, Inc. B bootstrap 4-10 Bootstrap, DSP56302 4-10 Buffer address C-13 end C-27 Freescale Semiconductor, Inc... C Checksum C-44, C-45 code example 3-6 codec 4-10 digital interface 4-12 digital interface connections 4-12 codec programming D-1 Command Converter 4-3 command converter 4-14 command format assembler 3-7 Comment C-17 delimiter C-3 object file C-17 unreported C-4 comment field 3-4 Conditional assembly C-34, C-45 Constant define C-17, C-19 storage C-14 Crystal Semiconductor CS4215 4-10 CS4215 4-10 Cycle count C-44, C-45 D D/A converter 4-10 Data Pins, D(0:23) 4-6, 4-9 data transfer fields 3-5 DC Offset 1-11 Debugger 3-3, 3-24 running the 3-26 Debugger software 3-24 Debugger window display 3-25 demonstration running the 2-4 demonstration file 2-1 development process flow 3-3 Directive C-13 .BREAK C-66 .CONTINUE C-66 .FOR C-67 Index-2 .IF C-68 .LOOP C-68 .REPEAT C-69 .WHILE C-69 BADDR C-13 BSB C-13 BSC C-14 BSM C-15 BUFFER C-16 COBJ C-17 COMMENT C-17 DC C-17 DCB C-19 DEFINE C-7, C-19, C-45 DS C-20 DSM C-21 DSR C-22 DUP C-22 DUPA C-23 DUPC C-25 DUPF C-26 END C-27 ENDBUF C-27 ENDIF C-28 ENDM C-28 ENDSEC C-29 EQU C-29 EXITM C-30 FAIL C-31 FORCE C-31 GLOBAL C-32 GSET C-32 HIMEM C-33 IDENT C-33 IF C-34 in loop C-45 INCLUDE C-35 LIST C-35 LOCAL C-36 LOMEM C-37 LSTCOL C-37 MACLIB C-38 MACRO C-39 MODE C-40 MSG C-40 NOLIST C-41 OPT C-42 ORG C-49 PAGE C-52 PMACRO C-53 PRCTL C-54 DSP56302EMUM/AD For More Information On This Product, Go to: www.freescale.com MOTOROLA Freescale Semiconductor, Inc... Freescale Semiconductor, Inc. RADIX C-54 RDIRECT C-55 SCSJMP C-56 SCSREG C-56 SECTION C-57 SET C-60 STITLE C-60 SYMOBJ C-61 TABS C-61 TITLE C-61 UNDEF C-62 WARN C-62 XDEF C-63 XREF C-63 Diskette 3-5, 4-9, 4-10 document description 2 Domain Technologies Debugger 1-3, 1-8, 2-4, 2-5, 3-24 DSP development tools 3-3 DSP Help Line 1-13 DSP Helpline 2 DSP linker 3-16 DSP56002 4-14 DSP56002 Receive Data Pin, RXD 4-14 DSP56002 Transmit Data Pin, TXD 4-14 DSP56300 Family Manual 4-3 DSP56302 3-3 Chip Errata 4-3 Product Specification 1-3 Product Specification, Revision 1.02 4-3 Technical Data 1-3, 4-3 User's Manual 4-3 DSP56302 code example 3-6 DSP56302 Features 4-3 DSP56302EVM additional requirements 1-4 Component Layout 4-4 component layout 1-6, 2-4 connecting to the PC 1-7 contents 1-3 description 4-3 features 4-3 Flash PEROM 4-4 functional block diagram 4-5 installation procedure 1-4 interconnection diagram 1-7 jumper settings 1-6 memory 4-4 power connection 1-7 preparation for installation 1-5 Product Information 1-3 MOTOROLA software installation 1-8 SRAM 4-4 testing the installation 1-9 User's Manual 1-3 E ECHO.ASM file D-3 ESD warning 1-5 ESSI0 4-10 example assembling the 3-16 example program 3-5 Expression address C-44 compound C-72 condition code C-70 formatting C-72 operand comparison C-71 radix C-54 simple C-70 External Access Type Bits, BAT(1:0) 4-7 External Memory Test 1-9 F field comment 3-5 data transfer 3-5 label 3-4 operand 3-5 operation 3-4 X data transfer 3-4 Y data transfer 3-4 File include C-35 listing C-46 filtering 16-bit coefficients 2-5 24-bit coefficients 2-5 Flash PEROM 4-4, 4-9 bootstrap 4-10 connections 4-9 standalone operation 4-9 Flash PEROM Address Pins, A(0:15) 4-9 Flash PEROM Chip Enable Pin, CE 4-9 Flash PEROM Data Pins, I/O(0:7) 4-9 Flash PEROM Output Enable Pin, OE 4-9 Flash PEROM Write Enable Pin, WE 4-9 Flash.asm 4-9 format DSP56302EMUM/AD For More Information On This Product, Go to: www.freescale.com Index-3 Freescale Semiconductor, Inc. assembler command 3-7 source statement 3-4 Function C-8 Long Memory Data Moves 4-7 H Macro call C-46 comment C-45 definition C-39, C-46 directive C-39 end C-28 exit C-30 expansion C-46 library C-38, C-46 purge C-53 Macro argument concatenation operator C-4 local label override operator C-6 return hex value operator C-6 return value operator C-5 MC145407 4-14 MC33078 4-11 MC74HCT241A 4-10 Memory limit C-33, C-37 utilization C-46 Memory space C-46, C-49 Motorola DSP linker 3-16 Motorola software 1-8 M Freescale Semiconductor, Inc... headphones 1-4, 1-9 Host Address Pin, HA2 4-14 host PC 4-14 Host PC Data Terminal Ready Pin, DTR 4-14 Host PC Receive Data Pin, RD 4-14 host PC requirements 1-4 Host PC Transmit Data Pin, TD 4-14 I Include file C-35 installing software 1-8 internet address 2 IRQA 2-4 IRQD 2-5 J J4 4-14 J5 4-14 J7 4-10 J9 4-6 JTAG 4-14 jumper settings 1-6 N K Noise Level 1-11 Number of Bits to Compare Bits, BCN(3:0) 4-8 kit contents 1-3 L O Label local C-46, C-49 label field 3-4 LED, red 4-14 Line continuation C-4 linker 3-3, 3-16 options 3-17 linker directives 3-23 Listing file C-46 format C-37, C-45, C-48, C-52, C-61 sub-title C-60 title C-61 llinker directives 3-23 Location counter C-8, C-49 Index-4 Object file comment C-17 identification C-33 symbol C-48, C-49, C-61 object files 3-3 OnCE commands 4-14 OnCE/JTAG conversion 4-14 operand field 3-5 operand fields 3-5 Operating Mode, DSP56302 4-9 operation field 3-4 Option AE C-43, C-44 assembler operation C-43 DSP56302EMUM/AD For More Information On This Product, Go to: www.freescale.com MOTOROLA Freescale Semiconductor, Inc... Freescale Semiconductor, Inc. CC C-44 CEX C-42, C-44 CK C-44 CL C-42, C-45 CM C-44, C-45 CONST C-44, C-45 CONTC C-45 CONTCK C-44, C-45 CRE C-42, C-45 DEX C-43, C-45 DLD C-44, C-45 DXL C-42, C-45 FC C-42, C-45 FF C-42, C-45 FM C-42, C-45 GL C-44, C-45 GS C-44, C-45 HDR C-43, C-45 IC C-43, C-46 IL C-43, C-46 INTR C-44, C-46 LB C-44, C-46 LDB C-44, C-46 listing format C-42 LOC C-43, C-46 MC C-43, C-46 MD C-43, C-46 message C-43 MEX C-43, C-46 MI C-44, C-46 MSW C-43, C-46 MU C-43, C-46 NL C-43, C-46 NOAE C-46 NOCC C-46 NOCEX C-46 NOCK C-47 NOCL C-47 NOCM C-47 NODEX C-47 NODLD C-47 NODXL C-47 NOFC C-47 NOFF C-47 NOFM C-47 NOGS C-47 NOHDR C-47 NOINTR C-47 NOMC C-47 NOMD C-47 NOMEX C-47 MOTOROLA NOMI C-47 NOMSW C-47 NONL C-47 NONS C-47 NOPP C-47 NOPS C-47 NORC C-47 NORP C-48 NOSCL C-48 NOU C-48 NOUR C-48 NOW C-48 NS C-43, C-48 PP C-42, C-48 PS C-44, C-48 PSM C-44 RC C-42, C-48 reporting C-42 RP C-44, C-48 RSV C-44 S C-43, C-48 SCL C-43, C-48 SCO C-43, C-48 SI C-44 SO C-43, C-48, C-49 SVO C-44 symbol C-43 U C-43, C-49 UR C-43, C-49 W C-43, C-49 WEX C-49 XLL C-43, C-49 XR C-43, C-49 P P Space Enable Bit, BPEN 4-8 Packing Enable Bit, BPAC 4-7 PC 4-14 PC requirements 1-4 PEROM 4-9 bootstrap 4-10 standalone operation 4-9 power supply, external 1-4, 1-7 program assembling the 3-7 example 3-5 writing the 3-4 Program counter C-8, C-49 programming AAR0 4-7 DSP56302EMUM/AD For More Information On This Product, Go to: www.freescale.com Index-5 Freescale Semiconductor, Inc. assembly 3-3 development 3-3 example 3-3 Q Quick Start Guide 2, 1-1 Freescale Semiconductor, Inc... R Read Enable Pin, RD 4-6, 4-9 Reset, DSP56002 4-14 Reset, DSP56302 4-9 RS-232 cable connection 1-7 RS-232 interface 4-14 RS-232 interface cable 1-4 RS-232 serial interface 4-14 running the Debugger program 3-26 running the demonstration 2-1, 2-4 S SCI, DSP56002 4-14 Section C-57 end C-29 global C-32, C-45, C-58 local C-36, C-58 nested C-48 static C-45, C-58 self-test 1-9 Serial Clock Pin, SCK0 4-12 Serial Control Pin 0, SC00 4-12 Serial Control Pin 1, SC01 4-12 Serial Control Pin 2, SC02 4-12 serial interface 4-14 Serial Receive Data Pin, SRD0 4-12 Serial Transmit Data Pin, STD0 4-12 software Domain Technologies 1-8 Motorola 1-8 software installation 1-8 Source file end C-27 source statement format 3-4 SRAM 4-4, 4-5 connections 4-6 SRAM Address Pins, A(0:14) 4-6 SRAM Chip Enable Pin, E 4-6 SRAM Data Pins, DQ(0:7) 4-6 SRAM memory map 4-7 SRAM Output Enable Pin, G 4-6 Index-6 SRAM Write Enable Pin, W 4-6 Stand-Alone Operation 4-9 standalone operation 4-9 Stereo Headphones 4-11 Stereo Input 4-11 Stereo Output 4-11 String concatenation C-9 delimiter C-7 packed C-48 SW2 2-4 SW3 2-5 Symbol case C-46 cross-reference C-45 equate C-29, C-45 global C-45 listing C-48 set C-32, C-60 undefined C-49 T test analysis 1-9, 1-10 self 1-9 test results fail 1-11 pass 1-12 trademark notices 2 tutorial, codec programming D-1 U Unified Memory Map 4-6 W Warning C-49 Windows 1-8 world-wide web address 2 Write Enable Pin, WR 4-6, 4-9 X X data transfer field 3-4 X Space Enable Bit, BXEN 4-8 Y Y data transfer field 3-4 Y Space Enable Bit, BYEN 4-8 DSP56302EMUM/AD For More Information On This Product, Go to: www.freescale.com MOTOROLA