14-18
DSP56305 User’s Manual
MOTOROLA
CYCLIC CODE CO-PROCESSOR
CCOP Programming Model
Bit 23, is set). If both PDIE and PCDN bits are set, the CCOP requests a Parity Coding
Done interrupt request from the interrupt controller. When PDIE is cleared, the interrupt
is disabled.
14.4.4.11
Input Buffer Empty bit (INBE)—CCSR Bit 19
The read-only status bit Input Buffer Empty (INBE), when set, indicates that the whole
input path is empty and there are no more data bits to be sent to the CFSRs. INBE is set
when the input FIFO is empty and the shift register/buffer (containing the last FIFO
word) has shifted out all its contents to the CFSRs but yet the Input Counter has not
reached zero, or when the continuous mode is being used (CM bit is set). In this situation
CCOP ceases processing waiting for new data to be input, or the programmer can
explicitly clear PREN causing normal completion of the processing. INBE is cleared after
a data word has been written to the FIFO. INBE does not generate any interrupt. INBE is
set by hardware, software, or CCOP individual reset.
14.4.4.12
Input FIFO Empty bit (INFE)—CCSR Bit 20
The read-only status bit Input FIFO Empty (INFE), when set, indicates that the Data
FIFO Register (CDFR), while operating as the input FIFO, is empty and can be written by
the DSP56300 core. CDFR operates as the input FIFO when CCOP is in the Idle state and
data is expected to be input to FIFO, or when CCOP is in the input or run phase. INFE is
set when the last word of the input FIFO is transferred to the shift register for shifting
into the CFSRs, emptying the input FIFO. It is possible to write up to five data words
(the FIFO depth) each time the INFE is set. INFE is cleared after a data word has been
written to the FIFO. INFE is set by hardware, software, or CCOP individual reset.
14.4.4.13
Output FIFO Not Empty bit (OFNE)—CCSR Bit 21
The read-only status bit Output FIFO Not Empty (OFNE), when set, indicates that the
Data FIFO Register (CDFR), while operating as the output FIFO, has at least one data
word which is ready to be read by the DSP56300 core. CDFR operates as the output FIFO
when CCOP is in the output phase or when CCOP is in the Idle state and data is
expected to be read from FIFO. OFNE is set when the output FIFO is not empty. OFNE is
cleared when the CDFR is read by the DSP56300 core reducing the number of words in
the output FIFO to zero. Since output data bits are written to CDFR in the output phase
only, OFNE is only operational in the Cipher modes (OPM1 = 0) and when CM,CCNT
Bit 23, is cleared. OFNE is cleared by hardware, software, or CCOP individual reset.
14.4.4.14
Cipher Done bit (CIDN)—CCSR Bit 22
The read-only status bit Cipher Done (CIDN), when set, indicates that the Cipher
processing on the input data block was terminated. CIDN is enabled when CCOP
operates in the Cipher modes (OPM1 = 0) and is disabled otherwise. CIDN is set when
the CCOP has completed all phases of the processing (i.e Input, Run, and Output
phases) and all output data has been transferred to the FIFO. If CIDN and CDIE are set, a
Cipher Done interrupt is generated. CIDN is cleared after reading (via CDFR) all the
Summary of Contents for DSP56305
Page 34: ...xxxii DSP56305 User s Manual MOTOROLA ...
Page 40: ...xxxvi DSP56305 User s Manual MOTOROLA ...
Page 41: ...MOTOROLA DSP56305 User s Manual 1 1 SECTION 1 DSP56305 OVERVIEW ...
Page 58: ...1 18 DSP56305 User s Manual MOTOROLA DSP56305 Overview DSP56305 Architecture Overview ...
Page 59: ...MOTOROLA DSP56305 User s Manual 2 1 SECTION 2 SIGNAL CONNECTION DESCRIPTIONS ...
Page 98: ...2 40 DSP56305 User s Manual MOTOROLA Signal Connection Descriptions JTAG OnCE Interface ...
Page 99: ...MOTOROLA DSP56305 User s Manual 3 1 SECTION 3 MEMORY CONFIGURATION ...
Page 119: ...MOTOROLA DSP56305 User s Manual 4 1 SECTION 4 CORE CONFIGURATION ...
Page 144: ...4 26 DSP56305 User s Manual MOTOROLA Core Configuration JTAG Boundary Scan Register BSR ...
Page 145: ...MOTOROLA DSP56305 User s Manual 5 1 SECTION 5 GENERAL PURPOSE I O ...
Page 149: ...HOST INTERFACE HI32 MOTOROLA DSP56305 User s Manual 6 1 SECTION 6 HOST INTERFACE HI32 ...
Page 150: ...6 2 DSP56305 User s Manual MOTOROLA HOST INTERFACE HI32 ...
Page 259: ...MOTOROLA DSP56305 User s Manual 7 1 SECTION 7 ENHANCED SYNCHRONOUS SERIAL INTERFACE ESSI ...
Page 315: ...MOTOROLA DSP56305 User s Manual 8 1 SECTION 8 SERIAL COMMUNICATION INTERFACE SCI ...
Page 347: ...MOTOROLA DSP56305 User s Manual 9 1 SECTION 9 TIMER EVENT COUNTER ...
Page 376: ...9 30 DSP56305 User s Manual MOTOROLA Timer Event Counter Timer Modes of Operation ...
Page 377: ...MOTOROLA DSP56305 User s Manual 10 1 SECTION 10 ON CHIP EMULATION MODULE ...
Page 411: ...MOTOROLA DSP56305 User s Manual 11 1 SECTION 11 JTAG PORT ...
Page 430: ...11 20 DSP56305 User s Manual MOTOROLA JTAG Port DSP56305 Boundary Scan Register ...
Page 431: ...Filter Co Processor MOTOROLA DSP56305 User s Manual 12 1 SECTION 12 FILTER CO PROCESSOR ...
Page 471: ...VITERBI CO PROCESSOR MOTOROLA DSP56305 User s Manual 13 1 SECTION 13 VITERBI CO PROCESSOR ...
Page 522: ...13 52 DSP56305 User s Manual MOTOROLA VITERBI CO PROCESSOR References ...
Page 554: ...14 32 DSP56305 User s Manual MOTOROLA CYCLIC CODE CO PROCESSOR Configuration Examples ...
Page 555: ...MOTOROLA DSP56305 User s Manual A 1 APPENDIX A BOOTSTRAP CODE ...
Page 568: ...A 14 DSP56305 User s Manual MOTOROLA Bootstrap Code ...
Page 569: ...Equates MOTOROLA DSP56305 User s Manual B 1 APPENDIX B EQUATES ...
Page 589: ...MOTOROLA DSP56305 User s Manual C 1 APPENDIX C JTAG BSDL ...
Page 590: ...C 2 DSP56305 User s Manual MOTOROLA JTAG BSDL ...
Page 600: ...C 12 DSP56305 User s Manual MOTOROLA JTAG BSDL ...
Page 601: ...MOTOROLA DSP56305 User s Manual D 1 APPENDIX D PROGRAMMING REFERENCE ...
Page 602: ...D 2 DSP56305 User s Manual MOTOROLA PROGRAMMING REFERENCE ...
Page 661: ...Y MOTOROLA DSP56305 User s Manual Index 11 ...
Page 662: ...Y Index 12 DSP56305 User s Manual MOTOROLA ...