View MK50H27DIP_6263743.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

mk50h27 signalling system 7 link controller section 1 - features complete level 2 implementation of ss7. compatible with 1988 ccitt, at&t, ansi, and bellcore signalling system number 7 link level protocols. optional operation to comply with japanese ttc jt-q703 specification requirements pin-for-pin and architecturally compatible with mk50h25 (x.25/lapd), mk50h29 (sdlc), and mk50h28(frame relay). system clock rates up to 33 mhz (mk50h27 - 33), or 25 mhz (mk50h27 - 25). data rate up to 4 mbps continuous for ss7 protocol processing, 20 mbps for transparent hdlc mode, or up to 51 mbps bursted (gapped data clocks, non-continuous data). on chip dma control with programmable burst length. dma transfer rate of up to 13.3 mbytes/sec us- ing optional 5 sysclk dma cycle (150 ns) at 33 mhz sysclk. buffer management includes: - initialization block - separate receive and transmit rings - variable descriptor ring and window sizes. selectable bec or pcr retransmission meth- ods, including forced retransmission for pcr. handles all 7 ss7 timers, plus the additional signal unit interval timers for japanese ss7. handles all ss7 frame formatting: - zero bit insert and delete - fcs generation and detection - frame delimiting with flags programmable minimum signal unit spacing (number of flags between su's) handles all sequencing and link control. selectable fcs of 16 or 32 bits. testing facilities: - internal loopback - silent loopback - optional internal data clock generation - self test. programmable for full or half duplex operation programmable watchdog timers for rclk and tclk (to detect absence of data clocks) available in 52 pin plcc, 84 pin plcc(for use with external rom), or 48 pin dip packages. section 2 - introduction the sgs - thomson ss7 signalling link control- ler (mk50h27) is a vlsi semiconductor device which provides a complete level 2 data communi- cation control conforming to the ccitt, ansi, bellcore, and at&t versions of ss7, as well as options to allow conformance to ttc jt-q703 (japanese ss7). this includes signal unit format- ting, transparency (so-called obit-stuffingo), error recovery by two types of retransmission, error monitoring, sequence number control, link status control, and fill in signal unit generation. one of the outstanding features of the mk50h27 is its buffer management which includes on-chip dma. this feature allows users to handle multi- ple msu's of receive and transmit data at a time. (a conventional data link control chip plus a sepa- rate dma chip would handle data for only a single block at a time.) the mk50h27 will move multiple blocks of receive and transmit data directly into september 1997 dip48 plcc 52 1/56
introduction (continued) and out of memory through the host's bus. a possible system configuration for the mk50h27 is shown in figure 1. for added flexibility a transparent mode provides an hdlc transport mechanism without link layer support. in this mode no protocol processing is done, all data received between opening flag and crc is written to the shared memory buffer and it is up to the user to take care of the upper level software. the mk50h27 may be used with any of several popular microprocessors, such as: 68040 ... 68000, 6800, z8000, z80, 80486 ... 8086, i960, etc. the mk50h27 may be operated in either full or half duplex mode. in half duplex mode, the rts and cts modem control pins are provided. in full duplex mode, these pins become user program- mable i/o pins. all signal pins on the mk50h27 are ttl compatible. this has the advantage of making the mk50h27 independent of the physical interface. as shown in figure 1, line drivers and receivers are used for electrical connection to the physical layer. vss-gnd dal07 dal06 dal05 dal04 dal03 dal02 dal01 dal00 read intr dali dalo das bmo, byte, busrel bmi, busako hold, busrq ale, as cs adr ready reset vss-gnd 24 hlda 1 2 3 4 5 6 7 8 9 10 11 12 13 14 48 47 46 45 44 43 42 41 40 39 38 37 36 23 22 21 20 19 18 17 16 15 35 34 33 32 31 30 29 28 27 26 25 tclk a18 a19 a20 a21 a22 a23 rd dsr, cts td sysclk rclk dtr, rts vcc (+5v) dal08 dal09 dal10 dal11 dal12 dal13 dal14 dal15 a16 a17 m k 5 0 h 2 7 dip48 pin connection (top view) mk50h27 2/56
vss dal07 dal06 dal05 dal04 dal03 dal02 dal01 dal00 read intr dali dalo das 8 7 1 52 47 46 34 33 21 20 bmo/byte/busrel no connect bm1/busako hold/busrq ale/as hlda cs adr ready reset vss(gnd) tclk no connect dtr/rts rclk sysclk td dsr/cts rd a23 no connect a22 a21 a20 a19 a18 a17 a16 dal15 dal13 dal14 vcc dal08 dal09 dal10 dal11 dal12 no connect mk50h27q plcc52 pin connection (top view) mk50h27 3/56
signal name pin(s) type description dal<15:00> 2-9 40-47 [2-10 44-51] io/3s the time multiplexed data/address bus. during the address portion of a memory transfer, dal<15:00> contains the lower 16 bits of the memory address. during the data portion of a memory transfer, dal<15:00> contains the read or write data, depending on the type of transfer. read 10 [11] io/3s read indicates the type of operation that the bus controller is performing during a bus transaction. read is driven by the mk50h27 only while it is the bus master. read is valid during the entire bus transaction and is tristated at all other times. mk50h27 as a bus slave : read = high - data is placed on the dal lines by the chip. read = low - data is taken off the dal lines by the chip. mk50h27 as a bus master : read = high - data is taken off the dal lines by the chip. read = low - data is placed on the dal lines by the chip. intr 11 [12] o/od interrupt is an attention interrupt line that indicates that one or more of the following csr0 status flags is set: miss, merr, rint, tint or pint. interrupt is enabled by csr0<09>, inea=1. dali 12 [13] o/3s dal in is an external bus transceiver control line. dali is driven by the mk50h27 only while it is the bus master. dali is asserted by the mk50h27 when it reads from the dal lines during the data portion of a read transfer. dali is not asserted during a write transfer. dalo 13 [14] o/3s dal out is an external bus transceiver control line. dalo is driven by the mk50h27 only while it is the bus master. dalo is asserted by the mk50h27 when it drives the dal lines during the address portion of a read transfer or for the duration of a write transfer. das 14 [15] io/3s data strobe defines the data portion of a bus transaction. by definition, data is stable and valid at the low to high transition of das. this signal is driven by the mk50h27 while it is the bus master. during the bus slave operation, this pin is used as an input. at all other times the signal is tristated. bmo byte busrel 15 [16] io/3s i/o pins 15 and 16 are programmable through csr4. if bit 06 of csr4 is set to a one, pin 15 becomes input busrel and is used by the host to signal the mk50h27 to terminate a dma burst after the current bus transfer has completed. if bit 06 is clear then pin 15 is an output and behaves as described below for pin 16. bm1 busako 16 [18] o/3s pins 15 and 16 are programmable through bit 00 of csr4 (bcon). if csr4<00> bcon = 0, i/o pin 15 = bmo (o/3s) i/o pin 16 = bm1 (o/3s) byte mask<1:0> indicates the byte(s) on the dal to be read or written during this bus transaction. mk50h27 drives these lines only as a bus master. mk50h27 ignores the bm lines when it is a bus slave. byte selection is done as outlined in the following table. bm1 bm0 type of transfer low low entire word low high upper byte (dal<15:08>) high low lower byte (dal<07:00>) high high none table 1 - pin description legend: i input only o output only io input / output 3s 3-state od open drain (no internal pull-up) note: pin out for 52 pin plcc is shown in brackets. mk50h27 4/56
table 1: pin description (continued) signal name pin(s) type description if csr4<00> bcon = 1, i/o pin 15 = byte (o/3s) i/o pin 16 = busako (o) byte selection is done using the byte line and dal<00> latched during the address portion of the bus transaction. mk50h27 drives byte only as a bus master and ignores it when a bus slave. byte selection is done as outlined in the following table. byte dal<00> type of transfer low low entire word low high illegal condition high low lower byte high high upper byte busako is a bus request daisy chain output. if mk50h27 is not requesting the bus and it receives hlda, busako will be driven low. if mk50h27 is requesting the bus when it receives hlda, busako will remain high note: all transfers are entire word unless the mk50h27 is configured for 8 bit operation. hold busrq 17 [19] io/od pin 17 is configured through bit 0 of csr4. if csr4<00> bcon = 0, i/o pin 17 = hold hold request is asserted by mk50h27 when it requires a dma cycle, if hlda is inactive, regardless of the previous state of the hold pin. hold is held low for the entire ensuing bus transaction. if csr4<00> bcon = 1, i/o pin 17 = busrq busrq is asserted by mk50h27 when it requires a dma cycle if the prior state of the busrq pin was high and hlda is inactive. busrq is held low for the entire ensuing bus transaction. ale as 18 [20] o/3s the active level of address strobe is programmable through csr4. the address portion of a bus transfer occurs while this signal is at its asserted level. this signal is driven by mk50h27 while it is the bus master. at all other times, the signal is tristated. if csr4<01> acon = 0, i/o pin 18 = ale address latch enable is used to demultiplex the dal lines and define the address portion of the transfer. as ale, the signal transitions from high to low during the address portion of the transfer and remains low during the data portion. if csr4<01> acon = 1, i/o pin 18 = as as as, the signal pulses low during the address portion of the bus transfer. the low to high transition of as can be used by a slave device to strobe the address into a register. as is effectively the inversion of ale. hlda 19 [21] i hold acknowledge is the response to hold. when hlda is low in response to mk50h27's assertion of hold, the mk50h27 is the bus master. hlda should be deasserted only after hold has been released by the mk50h27. cs 20 [22] i chip select indicates, when low, that the mk50h27 is the slave device for the data transfer. cs must be valid throughout the entire transaction. adr 21 [23] i address selects the register address port or the register data port. it must be valid throughout the data portion of the transfer and is only used by the chip when cs is low. adr port low register data port high register address port ready 22 [24] io/od when the mk50h27 is a bus master, ready is an asynchronous acknowledgement from the bus memory that memory will accept data in a write cycle or that memory has put data on the dal lines in a read cycle. mk50h27 5/56
table 1: pin description (continued) signal name pin(s) type description as a bus slave, the mk50h27 asserts ready when it has put data on the dal lines during a read cycle or is about to take data from the dal lines during a write cycle. ready is a response to das and it will be released after das or cs is negated. reset 23 [25] i reset is the bus signal that will cause mk50h27 to cease operation, clear its internal logic and enter an idle state with the stop bit of csr0 set. tclk 25 [28] i transmit clock. a 1x clock input for transmitter timing. td changes on the falling edge of tclk. the frequency of tclk may not be greater than the frequency of syscl dtr rts 26 [29] io data terminal ready, request to send. modem control pin. pin 26 is configurable through csr5. this pin can be programmed to behave as output rts or as programmable io pin dtr. if configured as rts, the mk50h27 will assert this pin if it has data to send and throughout the transmission of a signal unit. rclk 27 [30] i receive clock. a 1x clock input for receiver timing. rd is sampled on the rising edge of rclk. the frequency of rclk may not be greater than the frequency of sysclk. sysclk 28 [31] i system clock. system clock used for internal timing of the mk50h27. sysclk should be a square wave, of frequency up to 33 mhz. td 29 [32] o transmit data. transmit serial data output. dsr cts 30 [33] io data set ready, clear to send. modem control pin. pin 30 is configurable through csr5. this pin can be programmed to behave as input cts or as programmable io pin dsr. if configured as cts, the mk50h27 will transmit all ones while cts is high. rd 31 [34] i receive data. received serial data input. a<23:16> 32-39 [37-43] o/3s address bits <23:16> used in conjunction with dal<15:00> to produce a 24 bit address. mk50h27 drives these lines only as a bus master. a23-a20 may be driven continuously as described in the csr4<7> bae bit. vss-gnd 1,24 [1,26] ground pins vcc 48 [52] power supply pin +5.0 vdc + 5% section 3 operational description the sgs-thomson mk50h27 multi-logical link communications controller device is a vlsi prod- uct intended for high performance data communi- cation applications requiring sdlc link level con- trol. the mk50h27 will perform all frame formatting, such as: frame delimiting with flags, fcs (crc) generation and detection, and zero bit insertion and deletion for transparency. the mk50h27 also handles all supervisory (s) and unnumbered (u) frames (see tables a & b). the mk50h27 also includes a buffer management mechanism that allows the user to transmit and/or receive multiple frames for each active channel or dlci. contained in the buffer management is an on-chip dual channel dma: one channel for re- ceive and one channel for transmit. the mk50h27 can be used with any popular 16 or 8 bit microprocessor. a possible system con- figuration for the mk50h27 is shown in figure 1. this document assumes that the processor has a byte addressable memory organization. the mk50h27 will move multiple blocks of re- ceive and transmit data directly in and out of memory through the host's bus. the mk50h27 may be operated in full or half du- plex mode. in half duplex mode the rts and cts modem control pins are provided. in full du- plex mode, these pins become user programma- ble i/o pins. all signal pins on the mk50h27 are ttl compat- ible. this has the advantage of making the mk50h27 independent of the physical interface. as shown in fig. 1, line drivers and receivers are used for electrical connection to the physical layer. mk50h27 6/56
host processor (68020, i960, z8000, etc) 16-bit data bus including 24-bit address and bus control memory (multiple data blocks) mk50h27 rd td line drivers and receivers (such as rs-449, rs-232c, v.35) data comm. connector electrical i/o (such as rs-232c, rs-423, rs-422) tclk rclk dsr, cts dtr, rts figure 1: possible system configuration for thr mk50h27 mk50h27 7/56
dali dalo hlda hold ale, as bm0 bm1 das read intr adr ready dtr, rts dsr, cts cs firmware rom micro controller timers dma controller control / status registers 0 - 5 sysclk internal bus receiver fifo transmitter fifo receiver transmitter loopback test rd rclk tclk td vss - gnd reset vcc dal <15:00> a <23:16> figure 2: mk50h27 simplified block diagram mk50h27 8/56
3.1 functional blocks refer to the block diagram in figure 2. the mk50h27 is primarily initialized and control- led through six 16-bit control and status regis- ters (csr0 thru csr5). the csr's are accessed through two bus addressable ports, the register address port (rap), and the register data port (rdp). the mk50h27 may also generate an in- terrupt(s) to the host. these interrupts are en- abled and disabled through csr0. the on-chip microcontroller is used to control the movement of parallel receive and transmit data, and to handle the address field filtering. 3.1.1 microcontroller the microcontroller controls all of the other blocks of the mk50h27. the microcontroller performs frame processing and protocol processing. all primitive processing and generation is also done here. the microcode rom contains the control program of the microcontroller. 3.1.2 receiver serial receive data comes into the receiver (fig- ure 2). the receiver is responsible for: 1. leading and trailing flag detection. 2. deletion of zeroes inserted for transparency. 3. detection of idle and abort sequences. 4. detection of good & bad ck (check bit seq.) 5. monitoring receiver fifo status. 6. detection of receiver over-run. 7. odd byte detection. note: if frames are received that have an odd number of bytes then the last byte of the frame is said to be an odd byte. 8. detection of non-octet aligned frames. such frames are treated as invalid. 3.1.3 transmitter the transmitter is responsible for: 1. serialization of outgoing data. 2. generating and appending the ck (crc). 3. framing outgoing frame with flags. 4. zero bit insertion for transparency. 5. transmitter under-run detection. 6. transmission of odd byte. 7. rts/cts control. 3.1.4 check bit sequence or cyclic redundancy check the ck (crc) on the transmitter or receiver may be either 16 bit or 32 bit, and is user selectable. for full duplex operation, both the receiver and transmitter have individual ck computation cir- cuits. the characteristics of the ck are: transmitted polarity: inverted transmitted order: high order bit first pre-set value: all 1's polynomial 16 bit: x 16 +x 12 +x 5 +1 remainder 16 bit (if received correctly): high order bit-->0001 1101 0000 1111 polynomial 32 bit: x 32 +x 26 +x 23 +x 22 +x 16 +x 12 +x 11 +x 10 + x 8 +x 7 +x 5 +x 4 +x 2 +x+1 remainder 32 bit (if received correctly): high order bit--> 1100 0111 0000 0100 1101 1101 0111 1011 3.1.5 receive fifo the receive fifo buffers the data received by the receiver. this performs two major functions. first, it resynchronizes the data from the receive clock to the system clock. second, it allows the microcontroller time to finish whatever it may be doing before it has to process the received data. the receive fifo holds the data from the receiver without interrupting the microcontroller for service until it contains enough data to reach the water- mark level, or an end of frame is received. this watermark level can be programmed in csr4 (fwm) to occur when the fifo contains at least 18 or more bytes; 34 or more bytes; or 50 or more bytes. this programmability , along with the programmable burst length of the dma controller, enables the user to define how often and for how long the mk50h27 must use the host bus. for more information, see csr4. for example, if the watermark level is set at 34 bytes and the burst length is limited to 8 word transfers at a time, the mk50h27 will request control of the host bus as soon as 34 bytes are received and again after every 16 subsequent bytes. 3.1.6 transmit fifo the transmit fifo buffers the data to be trans- mitted by the mk50h27. this also performs two major functions. first, it resynchronizes the data from the system clock to the transmit clock. sec- ond, it allows the microcontroller and dma con- troller to burst read data from the host's memory buffers; making both the mk50h27 and the host bus more efficient. mk50h27 9/56
the transmit fifo has a watermark scheme simi- lar to the one described for the receive fifo above, and uses the same fwm value selections in csr4 for the watermark. once filled to within fwm of being full (by dma from tx buffer in shared memory), the transmit fifo will not inter- rupt the microcontroller until it empties enough to fall below the watermark level. 3.1.7 dma controller the mk50h27 has an on-chip dma controller cir- cuit. this allows it to access memory without re- quiring host software intervention. whenever the mk50h27 requires access to the host memory it will negotiate for mastership of the bus. upon gaining control of the bus the mk50h27 will begin transferring data to or from memory. the mk50h27 will perform memory transfers until either it has nothing more to transfer, it has reached its dma burst limit (user programmable), or the busrel pin is driven low. in any case, it will complete all bus transfers before releasing bus mastership back to the host. if during a memory transfer, the memory does not respond within 256 sclk cycles, the mk50h27 will re- lease ownership of the bus immediately and the merr bit will be set in csr0. the dma burst limit can be programmed by the user through csr4. in 16 bit mode the limit can be set to 1 word, 8 words, or unlimited word transfers. in 8 bit mode,it can be set to 2 bytes, 16 bytes, or un- limited byte transfers. for high speed data lines (i.e. > 1 mbps) a burst limit of 8 words or 16 bytes is suggested to allow maximum throughput. the byte ordering of the dma transfers can be programmed to account for differences in proces- sor architectures or host programming languages. byte ordering can be programmed separately for data and control information. data information is defined as all contents of data buffers; control in- formation is defined as anything else in the shared memory space (i.e. initialization block, de- scriptors, etc). for more information see section 4.1.2.5 on control status register 4. 3.1.8 bus slave circuitry the mk50h27 contains a bank of internal con- trol/status registers (csr0-5) which can be ac- cessed by the host as a peripheral. the host can read or write to these registers like any other bus slave. the contents of these registers are listed in section 4 and bus signal timing is described in figures 9 and 10. 3.2 buffer management overview refer to fig. 3. 3.2.1 initalization block chip initialization information is located in a block of memory called the initialization block. the in- itialization block consists of 200 contiguous words of memory starting on a word boundary. this memory is assembled by the host, and is ac- cessed by the mk50h27 during initialization. the initialization block is comprised of: a. mode of operation. b. counter/timer preset values. c. protocol parameters or options d. location and size of receive and transmit de- scriptor rings. e. optional transmit window size value f. location of status buffer. g. optional jt-q703 signal unit interval timer values h. statistics and error counters. 3.2.2 the circular queue the basic organization of the buffer management is a circular queue of tasks in memory called de- scriptor rings. there are separate rings to de- scribe the transmit and receive operations. up to 128 buffers may be queued-up on a descriptor ring awaiting execution by the mk50h27. the descriptor ring has a descriptor assigned to each buffer. each descriptor holds a pointer for the starting address of the buffer, and holds a value for the length of the buffer in bytes. each descriptor also contains two control bits called owna and ownb, which denote whether the mk50h27, the host, or an i/o accelera- tion processor ( if present ) oownso the buff- er. for transmit, when the mk50h27 owns the buffer, the mk50h27 is allowed and commanded to transmit the buffer. when the mk50h27 does not own the buffer, it will not transmit that buffer. for receive, when the mk50h27 owns a buffer, it may place received data into that buffer. con- versely, when the mk50h27 does not own a re- ceive buffer, it will not place received data into that buffer. the mk50h27 buffer management mechanism will handle frames which are longer than the length of an individual buffer. this is done by a chaining method which utilizes multiple buffers. the mk50h27 tests the next descriptor in the de- scriptor ring in a olook aheado manner. if the frame is too long for one buffer, the next buffer will be used after filling the first buffer; that is, ochainedo. the mk50h27 will then olook aheado to the next buffer, and chain that buffer if neces- sary, and so on.the operational parameters for the buffer management are defined by the user in the initialization block. the parameters defined include the basic mode of operation, protocol op- tions, the number of entries for the transmitter mk50h27 10/56
and receiver descriptor rings, etc. the starting address for the initialization block, iadr, is de- fined in the csr2 and csr3 registers inside the mk50h27. 3.2.3 signal unit repertoire the frame format supported by the mk50h27 is shown in table a. each signal unit (su) may consist of a programmable number of leading flag patterns (01111110), backward sequence num- ber, backward indicator bit, forward sequence number, forward indicator bit, lenght indicator field, followed by signalling information octet, service information field, or status field, de- pending on su type, and then ended with a ck (crc) of either 16 or 32 bits, and a trailing flag pattern. the number of leading flags transmitted is programmable through the mode register in the initialization block. received signal units may have as few as one flag between adjacent signal units the symbols and definitions for the signal unit types handled by the mk50h27 are: table a - mk50h27 signal unit repertoire name definition msu message signal unit lssu link status signal unit fisu fill in signal unit f flag sequence (01111110) fsn forward sequence number bsn backward sequence number fib forward indicator bit bib backward indicator bit li lenght indicator x reserved - programmed as zeroes pri priority indication (jt-q703 only) sio signalling information octe sif service information field sf status field ck check bit sequence (crc) mk50h27 11/56
message signal unit (msu) link status signal unit (lssu) f ck sif sio x li fib fsn bib bsn f 8 16/32 8n,n>=2 8 2 6 1 7 1 7 8 fck 8 16/32 sf x li fib fsn bib bsn f 26 17 1 7 8 8/16 values for sf: 0 - sio, 1 - sin, 2 - sie, out of alignment normal alignment emergency x li fib fsn bib bsn f 2 6 171 7 8 fill-in signal unit (fisu) fck 8 16/32 right-most fields are transmitted first 3 - sios, 4 - sipo, 5 - sib, out-of-service processor outage congestion (busy) table a - mk50h27 signal unit repertoire mk50h27 12/56
receiver descriptor rings descriptor 0 buffer status buffer address buffer size buffer msg count descriptor 1 descriptor m transmit descriptor rings descriptor 0 buffer status buffer address buffer size buffer msg count descriptor 1 descriptor n buffer n buffer 1 buffer 0 transmit buffer buffer m buffer 1 buffer 0 receive buffer csr 2, csr3 pointer to initializat ion block initializat ion block mode timer values protocol rx descriptor tx descriptor status buffer addres s status buffer parameters pointer pointer statistic s figure 3: mk50h27 memory management structure mk50h27 13/56
section 4 programming specification this section defines the control and status reg- isters and the memory data structures required to program the mk50h27. 4.1 control and status registers there are six control and status registers (csr's) resident within the mk50h27. the csr's are accessed through two bus address- able ports, an address port (rap), and a data port (rdp), thus requiring only two locations in the system memory or i/o map. 4.1.1 accessingthe control & status registers the csr's are read (or written) in a two step op- eration. the address of the csr is written into the address port (rap) during a bus slave transac- tion. during a subsequent bus slave transaction, the data being read from (or written into) the data port (rdp) is read from (or written into) the csr selected in the rap. once written, the address in rap remains unchanged until rewritten or upon a bus reset. a control i/o pin (adr) is provided to distinguish the address port from the data port. adr port l register data port (rdp) h register address port (rap) 4.1.1.1 register address port (rap) h b y e t 00000000 b m 8 000 csr <2:0> 1 5 1 4 1 3 0 7 0 8 1 0 1 1 1 2 0 1 0 2 0 3 0 4 0 5 0 0 0 9 0 6 bit name description 15:08 reserved must be written as zeroes 07 bm8 when set, places chip into 8 bit mode. csr's, init block, and data transfers are all 8 bit transfers; this provides compatibility with 8 bitmicroprocessors. when clear, all transfers are 16 bit transfers. this bit must be set to the same value each time it is written, changing this bit during normal operation will achieve unexpected results. bm8 is read/write and cleared on bus reset. 06:04 reserved must be written as zeroes 03:01 cs3<2:0> csr address select bits. read/write. selects the csr to be accessed through the rdp. rap is cleared by bus reset. csr<2:0> csr 0 csr0 1 csr1 2 csr2 3 csr3 4 csr4 5 csr5 00 hbyte determines which byte is addressed for 8 bit mode. if set, the high byte of the register referred to by csr<2:0> is addressed, otherwise the low byte is addressed. this bit is only meaningful in 8 bit mode and must be written as zero if bm8=0. hbyte is read/write and cleared on bus reset. mk50h27 14/56
csr data 1 5 1 0 1 4 0 9 1 2 1 1 0 8 0 3 0 7 0 2 0 6 0 5 0 4 0 1 0 0 1 3 4.1.1.2 register data port (rdp) bit name description 15:00 csr data writing data to the rdp loads data into the csr selected by rap. reading the data from rdp reads the data from the csr selected in rap. 4.1.2 control and status register definition 4.1.2.1 control and status register 0 (csr0) rap<3:1> = 0 bit name description 15 tdmd transmit demand, when set, causes mk50h27 to access the transmit descriptor ring without waiting for the transmit polltime inter- val to elapse. tdmd need not be set to transmit a msu, it merely has- tens mk50h27's response to a transmit descriptor ring entry inser- tion by the host. tdmd is write with one only and cleared by the microcode after it is used. it may read as a o1o for a short time after it is written because the microcode may have been busy when tdmd was set. it is also cleared by bus reset. writing a o0o in this bit has no effect. 14 poff poff, when set, indicates that mk50h27 is operating in the power off phase of operation. all external activity is disabled and internal logic is reset. mk50h27 remains inactive except for primitive processing until a power on primitive is issued. poff is read only and set by bus reset or a power off primitive. writing to this bit has no effect. 13 dtx transmitter ring disable prevents the mk50h27 from further access to the transmitter descriptor ring and terminates transmitter polling. no transmissions are attempted after finishing transmission of any signal unit in transmission at the time of dtx being set. txon acknow- ledges changes to dtx, see below. dtx is read/write. 1 5 1 4 1 3 0 7 0 8 1 0 1 1 1 2 0 1 0 2 0 3 0 4 0 5 0 0 0 9 0 6 0 r i n t t i n t p i n t t u r m i s s m e r r r o r i n t r r x o n t x o n i n e a p o f f t d m d d t x d r x mk50h27 15/56
4.1.2.1 control and status register 0 (csr0) bit name description 12 drx disable the receiver prevents the mk50h27 from further access to the receiver descriptor ring. no received signal units are accepted after finishing reception of any signal unit in reception at the time of drx being set. rxon acknowledges changes to drx, see be- low. drx is read/write. 11 txon transmitter on indicates that the transmit ring access is enabled. txon is set as the power on primitive is issued if the dtx bit is o0o or afterward as dtx is cleared. txon is cleared upon recognition of dtx being set, by sending a power off primitive in csr1, or by a bus reset. if txon is clear, the host may modify the transmit descriptor ring entries regardless of the state of the owna bits. txon is read only; writing to this bit has no effect. 10 rxon receiver on indicates that the receive ring access is enabled. rxon is set as the power on primitive is issued if drx=0, or after- ward as drx is cleared. rxon is cleared upon recognition of drx being set, by sending a power off primitive in csr1, or by a bus reset. rxon is read only; writing to this bit has no effect. 09 inea interrupt enable allows the intr i/o pin to be driven low when the interrupt flag is set. if inea = 1 and intr = 1 the intr i/o pin will be low. if inea = 0 the intr i/o pin will be high, regardless of the state of the interrupt flag. inea is read/write set by writing a o1o into this bit and is cleared by writing a o0o into this bit, by bus re- set, or while in the power off phase. inea may not be set while in the power off phase. 08 intr interrupt flag indicates that one or more of the following interrupt causing conditions has occurred: miss, merr, rint, tint, pint. if inea = 1 and intr = 1 the intr i/o pin will be low. intr is read only, writing this bit has no effect. intr is cleared as the specific interrupting condition bits are cleared. intr is also cleared by bus reset or by issuing a power off primitive. 07 merr memory error is set when the mk50h27 is the bus master and ready has not been asserted within 256 sysclks (25.6 usec @ 10mhz) after asserting the address on thedal lines. when a mem- ory error is detected, the mk50h27 releases the bus, the receiver and transmitter are turned off, and an interrupt is generated if inea = 1. merr is read/clear only and is set by the chip and cleared by writing a o1o into the bit. writing a o0o has no effect. it is cleared by bus reset or by issuing a power off primitive. 06 miss missed msu is set when the receiver loses a msu because it does not own a receive buffer indicating loss of data. when miss is set, an interrupt will be generated if inea = 1. miss is read/clear only and is set by mk50h27 and cleared by writing a o1o into the bit. writ- ing a o0o has no effect. it is also cleared by bus reset or by issu- ing a power off primitive. 05 ror receiver overrun indicates that the receiver fifo was full when the receiver was ready to input data to the receiver fifo. the sig- nal unit being received is lost but is recoverable according to the link level protocol. when ror is set, an interrupt is generated if inea = 1. ror is read/clear only and is set by mk50h27 and cleared by writing a o1o into the bit. writing a o0o has no effect. it is also cleared by bus reset or by issuing a power off primitive. mk50h27 16/56
04 tur transmitter underrun indicates that the mk50h27 has aborted a signal unit since data was late from memory. this condition is reached when the transmitter and transmitter fifo both become empty while transmitting a signal unit. when tur is set, an interrupt is generated if inea = 1. tur is read/clear only and is set by mk50h27 and cleared by writing a o1o into the bit. writing a o0o has no effect. it is also cleared by reset or by issuing a power off primi- tive. 03 pint primitive interrupt is set after the chip updates the primitive register to issue a provider primitive. when pint is set, an interrupt is generated if inea =1. pint is read/clear only and is set by mk50h27 and cleared by writing a o1o into the bit. writing a o0o has no effect. it is also cleared by reset or by issuing a power off primitive. 02 tint transmitter interrupt is set after the chip updates an entry in the transmit descriptor ring. when tint is set, an interrupt is generated if inea =1. tint is read/clear only and is set by mk50h27 and cleared by writing a o1o into the bit. writing a o0o has no effect. it is also cleared by reset or by issuing a poweroff primitive. 01 rint receiver interrupt is set after the mk50h27 updates an entry in the receive descriptor ring. when rint is set, an interrupt is gener- ated if inea =1. rint is read/clear only and is set by mk50h27 and cleared by writing a o1o into the bit. writing a o0o has no effect. it is cleared by bus reset or by issuing a power off primitive. 00 0 this bit is read only and will always read as a zero. 4.1.2.2 control and status register 1 (csr1) rap <3:1> = 1 bit name description 15 uerr user primitive error is set by the mk50h27 when a primitive is issued by the user which is in conflict with the current status of the link. uerr is read/clear only and is set by mk50h27 and cleared by writing a o1o into the bit. writing a o0o in this bit has no effect. it is also cleared by bus reset. 14 uav user primitive available is set by the user when a primitive is written into uprim. it is cleared by the mk50h27 after the primitive has been processed. this bit is also cleared by a bus reset. 13:08 uprim user primitive is written by the user, in conjunction with setting uav, to control the mk50h27 link procedures. the following primitives are available: 0 power off: causes the mk50h27 to enter the power off state. all dma activity ceases, the transmitter transmits all ones, and all received data is ignored. valid in all states except power off. 1 power on: valid only in the power off phase and must be issued after the init primitive and prior to the start primitive. causes the mk50h27 to exit the power off phase and to enter the out of service phase and 1 5 1 0 1 4 0 9 1 2 1 1 0 8 0 3 0 7 0 2 0 6 0 5 0 4 0 1 0 0 1 3 uprim <5:0> pprim <5:0> u e r r u a v p a v p l o s t mk50h27 17/56
to continuouslytransmit sios signal units. 2 init: instructs the mk50h27 to read the initialization block from memory. valid only in the power off mode. 3 trans: instructs the mk50h27 to enter the hdlc transparent phase of operation. data frames are transmitted and received out of the de- scriptor rings but no protocol processing is done. address and control fields are not prepended to the frames, but ck processing works normally. hdlc transparent mode may be exited only with a power off primitive or by a bus reset. valid only in the power off phase. 4 status request: instructs the mk50h27 to write the current link status into the status buffer. valid in all states, but only after the init primitive has been previously issued. 5 self-test request: instructs the mk50h27 to perform the built in internal self test. valid only in the power off phase. see section 4.4.8 for the self test procedure. 6 stop: forces all dma activity to cease. causes the mk50h27 to enter the out of service phase and to continuously transmit sios signal units. valid in all phases except the power off and out of service phase. 7 start: initial alignment begins and the descriptor rings are reset. start should only be issued when in the out of service phase, after the in- itialization block has been read. 8 local processor outage: issued to the mk50h27 to indicate that level 3 or higher levels cannot accept signalling messages. all subsequent msu's are ignored by the mk50h27 & sipo signal units are transmit- ted. 9 local processor recovered: indicates end of local processor outage condition. the mk50h27 may resume transmitting fisus and msus. 10 emergency: indicates that the emergency proving period is to be used for initial alignment. 11 emergency ceases: indicates that the normal proving period is to be used for initial alignment (this is the default proving period). 12 retrieve bsnt: causes the entire status buffer to be updated including the last transmitted backward sequence number (bsnt). when completed, pprim 18 will be issued. 13 retrieval request and fsnc: indicates that the fsnc has been written to the status buffer and requests the mk50h27 to update the retransmission buffer. the mk50h27 should then place the up- dated retransmission index into the status buffer. 14 congestion: causes the mk50h27 to enter a congestion state and send sib signal units at t5 timer interval. it is recommended that the drx bit in csr0 also be set when issuing this primitive so that msus can- not be received during congestion. 15 clear congestion: this primitive should be used only to clear the congestion state caused by uprim 14. if drx is set, it should be cleared just prior to issuing this primitive. if congestion state was en- tered due to a missed signal unit then the congestion state should be cleared by clearing miss. 16 start sending sios: if jss7e=1, this primitive can be used to resume sending of sios signal units, stopped by issuance of uprim 17. valid only in out of service phase when jss7e=1 (csr2). 17 stop sending sios: if jss7e=1, this primitive can be used to stop the transmission of sios signal units while the mk50h27 is in the out of service phase. ttc specification jt-q703 requires that transmission of sios stop some period of time after going out of service; this primi- tive provides the mechanism for meeting that requiremnt. transmis- mk50h27 18/56
sion of sios can be resumed by issuing uprim 16 described above. valid only in out of service phase when jss7e=1 (csr2). 07 plost provider primitive lost is set by mk50h27 when a provider primitive cannot be issued because the pav bit is still set from the pre- vious provider primitive. plost is cleared when pav is cleared and by a bus reset. writing to this bit has no affect. 06 pav provider primitive available is set by the mk50h27 when a new provider primitive has been placed in pprim. pprim is read/clear only and is set by the chip and cleared by writing a o1o to the bit or by bus reset. under normal operation the host should clear the pav bit after pprim is read. 05:00 pprim provider primitive is written by the mk50h27, in conjunction with setting the pav bit, to inform the user of link control condi- tions. valid provider primitives are as follows: 0 init confirmation: indicates that the initialization has completed. 1 in service: indicates that alignment has completed successfully. 2 in service yellow: indicates alignment completed succesfully with ccitt yellow book definitions for sins & sies (sf = 9 & 10 respectively). this primitive will occur only if enabled by ryel=1 in protocol options. 3 transmit clock watchdog timer expired: indicates that the watchdog timer for tclk has expired due to no transition on tclk for more than the number of sysclk cycles as selected by csr4<15:14>. 4 receive clock watchdog timer expired: indicates that the watchdog timer for rclk has expired due to no transition on rclk for more than the number of sysclk cycles as selected by csr4<13:12>. 5 received su timer timeout: indicates that no signal units have been received within the previous 32xtp time (where tp is the poll timer). this primitive is only issued if rsute=1 (csr2<12>). 8 alignment out of service: indicates that a transfer to out of service phase has occured, due to an alignment failure. alignment will fail if aerm is exceeded, timer t2 times out, or timer t3 times out. 9 lssu out of service: indicates that a transfer to the out of service phase has occured, due to a received lssu. 10 t1 out of service: indicates that a transfer to the out of service phase has occured, due to a timer t1 time out. 11 transmit out of service: indicates that a transfer to the out of service phase has occured, due to a transmit link failure. the trans- mit link will fail if timers t6 or t7 time out. ` 12 receive out of service: indicates that a transfer to the out of service phase has occured due to receive link failure. a receive link failure will occur when more than 2 out of 3 signal units have a fib or bsn error. 13 suerm out of service: indicates that a transfer to the out of service phase has occured, due to suerm being exceeded. 16 remote processor outage: indicates that a sipo has been received indicating that a remote processor outage condition has occured. 17 remote processor outage recovered: an fisu or an msu has been received since remote processor outage condition has been reported. 18 received message bsnt: indicates that the mk50h27 has written the bsnt to the status buffer as requested by uprim 12. 19 retrieval complete: retrieval request and fsnc completed successfully. the pointer to the retransmission buffer is available in status buffer. 20 remote processor busy: an sib has been received indicating that the remote node has entered into congestion. 21 remote processor busy recovered: the remote node has acknowledged mk50h27 19/56
the receipt of an msu after having entered congestion. this primitive indicates that the remote node congestion has abated. 4.1.2.3 control and status register 2 (csr2) rap<3:1> = 2 bit name description 15 cycle setting this bit selects a shorter dma cycle (5 vs 6 sysclks for bursting or 5 vs 7 sysclks for single dma). see figures 7a and 8a for details. 14 esen extended scaler enable. setting this bit enables the use of the 16-bit timer pre-scaler at iadr+24 rather than the 8-bit scaler at iadr+02. using the 16-bit scaler allows longer timer values at higher sysclk rates. set esen=0 for backward compatibility with the mk50h27. 13 0 reserved, must be written as zeroes. 12 rsute received su timer enable. setting this bit enables a timer for detecting more than 32xtp time between received signal units. if rsute=1, pprim=5 will be issued upon expiry of the received su timer. a typi- cal use for rsut is to detect breaking of the serial data connection. 11:09 0 reserved, must be written as zeroes. 08 jss7e japanese ss7 enable. setting this bit enables ttc jt-q703 compliance. when jss7e=1 the mk50h27 will align using only sies, timers tf, ts, to, ta, and te will be activated appropriately, and the suerm will act in accordance with jt-q703 requiring interchanging the location of the t and d fields in the initialization block. if jss7e=1 the mk50h27 will not comply with all ccitt/itu, ansi, or at&t specifications. 07:00 iadr the high order 8 bits of the address of the first word (lowest address) in the initialization block. iadr must be written by the host prior to issuing an init primitive. 4.1.2.4 control and status register 3 (csr3) rap<3:1> = 3 bit name description 15:00 iadr the low order 16 bits of the address of the first word (lowest address) in the initialization block. must be written by the host prior to issu- ing an init primitive. the initialization block must begin on a word boundary. 1 5 1 0 1 4 0 9 1 2 1 1 0 8 0 3 0 7 0 2 0 6 0 5 0 4 0 1 0 0 1 3 iadr<23:16> 0 000 c y c l e e s e n r s u t e j s s 7 e 1 5 1 0 1 4 0 9 1 2 1 1 0 8 0 3 0 7 0 2 0 6 0 5 0 4 0 1 0 0 1 3 0 iadr <15:00> mk50h27 20/56
4.1.2.5 control and status register 4 (csr4) csr4 allows redefinition of the bus master interface. rap<3:1> = 4 bit name description 15:12 xwd0/1, rwd0/1 these bits enable and determine the timer values for the transmit and receive watchdog timers. these timers are independently program- mable and are reset by any transition on the tclk and rclk pins re- spectively. the watchdog timers will expire after approximately wn sysclk cycles (if not reset by transition on tclk / rclk pins) and provider primitive 3 or 4 will be issued. the following table shows the selections for wn: xwd1/rwd1 xwd0/rwd0 wn 0 0 disabled 012 18 102 19 112 20 11:10 0 reserved, must be written as zero. 09:08 fwm these bits define the fifo watermarks. fifo watermarks prevent the mk50h27 from performing dma transfers to/from the data buffers until the fifos contain a minimum amount of data or space for data. for receive data, data will only be transferred to the data buffers after the fifo has at least n 16-bit words or an end of signal unit has been reached. conversely, for transmit data, data will only be transferred from the data buffers when the transmit fifo has room for at least n words of data. n is defined as follows: fwm<1:0> n 11 1 word 10* 9 words 01 17 words 00 25 words * suggested setting 07 bae bus address enable: if bae is set then the a23-a20 pins are driven by the mk50h27 constantly providing the ability to use a23-a20 for memory bus selection. if clear, a23-a20 behave identically to a19- a16. 06 busr if this bit is set, pin 15 becomes input busrel. if this bit is clear then pin 15 is either bm0 or byte depending on bit 00. for more information see the description for pin 15 in this document. busr is read/write and cleared on bus reset. 05 bswpc this bit determines the byte ordering of all onon-datao dma transfers. 1 5 1 0 1 4 0 9 1 2 1 1 0 8 0 3 0 7 0 2 0 6 0 5 0 4 0 1 0 0 1 3 b s w p c b u r s t 1 : 0 b s w p d a c o n b c o n f w m b a e b u s r x w d 1 x w d 0 r w d 1 r w d 0 0 0 mk50h27 21/56
onon-data dma transfers refers to any dma transfers that access memory other than the data buffers themselves. this includes the initialization block, descriptors, and status buffer. it has no effect on data dma transfers. bswpc allows the mk50h27 to operate with memory organizations that have bits 07:00 at even addresses and with bits 15:08 at odd addressses or vice versa. bswpc is read/write and cleared by bus reset. with bswpc = 1: address address this memory organization is used with the 8086 family of microproces- sors. with bswpc = 0: address address this memory organization is used with the 68000 and the z8000 microprocessors. 04:03 burst this field determines the maximum number of data transfers performed each time control of the host bus is obtained. burst is read/write and cleared on bus reset. * suggested setting 02 bswpd this bit determines the byte ordering of all data dma transfers. data transfers are those to or from a data buffer. bswpd has no ef- fect on non-data transfers. the effect of bswpd on data transfers is the same as that of bswpc on non-data transfers (see above). for most applications, including most 68000 based sys- tems, this bit should be set. 01 acon ale control defines the assertive state of pin 18 when the mk50h27 is a bus master. acon is read/ write and cleared by bus reset. 00 bcon byte control redefines the byte mask and hold i/o pins. bcon is read/write and cleared by bus reset. burst <1:0> 8 bit mode 16 bit mode 00 2 bytes 1 words 10* 16 bytes 8 words 01 unlimited unlimited 8 ... 15 xx0 xx1 0 . . . 7 8...15 xx1 xx1 0 . . . 7 acon pin18 name 0 asserted high ale 1 asserted low as bcon pin16 pin15 pin17 0 bm1 bm0 hold 1 busako byte busrq mk50h27 22/56
4.1.2.6 control and status register 5 (csr5) csr5 facilitates control and monitoring of modem controls. rap<3:1> = 5 bit name description 15:05 0 reserved, must be written as zeroes. 4 rtsen rts/cts enable is a read/write bit used to configure pins 26 and 30. if this bit is set, pin 26 becomes rts and pin 30 becomes cts. rts is driven low whenever the mk50h27 has data to trans- mit and is kept low during transmission. rts will be driven high after the closing flag of a signal unit is transmited if either no other frames are in the fifo or if the minimum signal unit spacing is higher than 2 (see mode register). the mk50h27 will not begin transmission and td will remain high if cts is high. if rtsen = 0 then pins 26 and 30 become programmable i/o pins dtr and dsr. the direction and behavior of dsr and dtr are controlled by the following bits. 3 dtrd dtr direction is a read/write bit used to control the direction of the dtr pin. if dtrd = 0, the dtr pin becomes an input pin and the dtr bit reflects the current value of the pin; if dtrd = 1, the dtr pin is an output pin controlled by the dtr bit below. 2 dsrd dsr direction is a read/write bit used to control the direction of the dsr pin. if dsrd = 0, the dsr pin becomes an input pin and the dsr bit reflects the current value of the pin; if dsrd = 1, the dsr pin is an output pin controlled by the dsr bit below. 1 dtr data terminal ready is used to control or observe the dtr i/o pin depending on the value of dtrd. if dtrd = 0, this bit be- comes read only and always equals the current value of the dtr pin. if dtrd = 1, this bit becomes read/write and any value written to this bit appears on the dtr pin. 0 dsr data set ready is used to control or observe the dsr i/o pin depending on the value of dsrd. if dsrd = 0, this bit be- comes read only and always equals the current value of the dsr pin. if dsrd = 1 this bit becomes read/write and any value written to this bit appears on the dsr pin. 1 5 1 0 1 4 0 9 1 2 1 1 0 8 0 3 0 7 0 2 0 6 0 5 0 4 0 1 0 0 1 3 000000000 d t r d d s r d d t r d s r r t s e n x e d g e 0 mk50h27 23/56
4.2 initialization block mk50h27 initialization includes the reading of the initialization block in memory to obtain the operating parameters. the initialization block is defined below. upon receiving an init primitive, por- tions of the initialization block are read by the mk50h27. the remainder of the initialization block will be read as needed by the mk50h27. statistics status buffer address tdra <15:00> tlen - tdra <23:16> rdra <15:00> rlen - rdra <23:16> protocol parameters counter / timer periods mode base address higher addr iadr+00 iadr+02 iadr+26 iadr+36 iadr+38 iadr+40 iadr+42 iadr+44 iadr+50 thru iadr+198 figure 4: initialization block mk50h27 24/56
4.2.1 mode register the mode register allows alteration of the mk50h27's operating parameters. bit name description 15:11 mfs<4:0> minimum frame spacing defines the minimum number of flag sequences transmitted between adjacent frames transmitted by the mk50h27. this only affects frames transmitted by the mk50h27 and does not restrict the spacing of the frames received by the mk50h27. when using rts/cts control this field defines the number of flags transmitted at the beginning of the frame after cts is driven low (minus one for the trailing flag). see the fol- lowing table for encoding of this field. 10 extcf extended control force. must be reset to zero for both ss7 and hdlc transparent mode 09 extaf extended address force. if set along with exta, the receiver will assume the address to be two otets long regardless of the first bit of the address. see exta below. must be set to a 1 for ss7 operation. must be reset to a zero for hdlc transparent mode. 08 dace disable address and control field extraction. dace should be written with o0o for normal ss7 operation and with o1o for hdlc transparent mode. the mk50h27 however, has a feature to allow shifting of the alignment of the data in the msu buffers. if dace is set to o1o for ss7 mode, the received li will be placed in the first byte of the receive buff- er, followed by the sio in the second byte and so on. if dace = 1, on transmit the li must be placed in the first byte of the transmit buffer rather than in the sul field of the transmit descriptor entry (tmd2). 07 extc extended control field. must be reset to zero for both ss7 and hdlc transparent mode. 06 exta extended address field. must be set to a 1 for ss7 operation. must be reset to a zero for hdlc transparent mode. 1 5 1 4 1 3 0 7 0 8 1 0 1 1 1 2 0 1 0 2 0 3 0 4 0 5 0 0 0 9 0 6 lback <2:0> mfs <4:0> f e x t c e x t a f d a c e e x t c e x t a d r c k d t c k c k s iadr + 00 number of flags mfs<4:0> number of flags mfs<4:0> 1 2 4 6 8 10 12 14 16 18 20 22 24 26 28 30 1 0 2 4 9 18 5 11 22 12 25 19 7 15 31 30 32 34 36 38 40 42 44 46 48 50 52 54 56 58 60 62 28 24 17 3 6 13 27 23 14 29 26 21 10 20 8 16 mk50h27 25/56
05 drck disable receiver ck. when drck = 0, the receiver will extract and check the ck field at the end of each signal unit. when drck = 1, the receiver continues to extract the last 16 or 32 bits of each signal unit, depending on cks, but no check is performed to determine whether the ck is correct. the ck is not stored into the receive buffer. 04 dtck disable transmitter ck. when dtck = 0, the transmitter will generate and append the ck to each signal unit. when dtck = 1, the ck logic is disabled, and no ck is generated with transmitted sig- nal units. setting dtck=1 is useful in loopback testing for check- ing the ability of the receiver to detect an incorrect ck. 03 cks ck select. when cks = 1, the 16 bit ck is selected otherwise the 32 bit ck is used. 02:00 lback loopback control puts the mk50h27 into one of several loopback configurations. 4.2.2 timers there are ten independent counter-timers defined in ss7. the upper 8 bits of iadr+02 are used as a scaler for t1 through t7, and tp. the scaler is driven by a clock which is 1/32 of sysclk. n1 is the maximum number of signal units allowed for retransmission (transmission window size) and n2 is the maximum number of bytes allowed for retransmission. the value for n1 is set to 128. the host will write the period of n2, t1-t7, and tp into the initialization block. timer description scaler timer prescaler. timers t1-t7 and tp are scaled by this number. the prescaler is incremented once every 32 system clock pulses. when it reaches zero the timers are incremented and the prescaler is reset. this field is interpreted as the two's comple- ment of the prescaler period. the mk50h27 multiplies this value by 16 when it is read into the device. note: a prescale value of one gives the smallest amount of scaling to the timers (512 clock pulses), zero gives the largest (131584 clock pulses). n2 octet window size. n2 gives the maximum number of msu octets allowed for retransmission. n2 includes the opening and clos- ing flags, bsn/bib, fsn/fib, li, and the ck octets. this value is expressed as a positive integer. bits <14:8> of iadr + 02 represent the most significant bits of n2. t1 aligned ready timer period. t1 determines the maximum time the mk50h27 will stay in the aligned ready state before sig- nalling link failure. represented as two's complement. t2 not aligned timer period. t2 determines the maximum time the mk50h27 will wait in the not aligned state before signalling link failure. represented as two's complement. lback description 0 normal operation. no loopback. 4 simple loopback. receive data and clock are driven internally by transmit data and clock. transmit clock must be supplied externally 5 clockless loopback. receive data is driven internally by transmit data. transmit and receive clocks are driven by sysclk divided by 8. 6 silent loopback. same as simple loopback with td pin forced to all ones. 7 silent clockless loopback. combination of silent and clockless loopbacks. receive data is driven internally by transmit data, transmit and receive clocks are driven by sysclk divided by 8. the td pin is forced to all ones. mk50h27 26/56
t3 aligned timeout timer period. t3 determines the maximum time the mk50h27 will wait in the aligned state before signalling link failure. represented as two's complement. t4n normal proving period. t4n determines the length of the normal proving period as defined in ccitt q.703. represented as two's complement. t4e emergency proving period. t4e determines the length of the emergency proving period as defined in ccitt q.703. represented as two's complement. t5 busy transmit period. t5 determines the amount of time the mk50h27 will wait between transmissions of status indication obo while in congestion state. represented as two's complement. t6 excessive busy timer period. t6 determines the amount of time the mk50h27 will allow a remote site to remain in the congested state before signalling link failure. represented as two's complement. t7 excessive acknowledge timer period. t7 determines the maximum amount of time the mk50h27 will wait for an expected acknowledgement of an msu before signalling link failure. repre- sented as two's complement. tp transmit polling period. this scaled timer determines the length of time between transmit signal unit checks. unless tdmd (see csr0) is set or a signal unit is received on the link, no at- tempt to transmit a signal unit in the transmit descriptor ring is made until tp expires. at tp expiration all transmit signal units in the transmit descriptor ring are sent. represented as two's complement. reserved/ 16-bit scaler can be programmed as all zeroes for compatibliity with existing mk50h27 applications. however, if esen=1 (csr2<14>), then this field is de- fined as a 16-bit scaler for all of the timers, and it will be used instead of the scaler at iadr+02. this prescaler is incremented once every 32 system clock pulses. when it reaches zero the timers are incre- mented and the prescaler is reset. this field is interpreted as the two's complement of the prescaler period. this 16-bit scaler is not multiplied by 16 when read into the mk50h27. timers for optional ttc jt-q703 compliance tf fisu sending interval timer. this timer, located at iadr + 144 will determine the amount of time between transmission of fisus when in ttc jt-q703 compliant mode (csr2<08> jss7e=1). represented as two's complement. ts sios sending interval timer. this timer, located at iadr + 146 will determine the amount of time between transmission of sios signal units when in ttc jt-q703 compliant mode (csr2<08> jss7e=1). represented as two's complement. to sio sending interval timer. this timer, located at iadr + 148 will determine the amount of time between transmission of siosignal units when in ttc jt-q703 compliant mode (csr2<08> jss7e=1). repre- sented as two's complement. ta sie sending interval timer. this timer, located at iadr + 150 will determine the amount of time between transmission of sie signal units when in ttc jt-q703 compliant mode (csr2<08> jss7e=1). repre- sented as two's complement. note: the tf, ts, to, & ta timers are only active and valid when jss7e=1 (csr2<08>). mk50h27 27/56
0 14 counter n2 8 7 scaler 0 counter n2 15 15 15 15 15 15 15 15 15 15 0 0 0 0 0 0 0 0 0 0 timer t1 timer t2 timer t3 timer t4n timer t4e timer t5 timer t6 timer t7 timer tp reserved / 15 0 iadr + 02 iadr + 04 iadr + 06 iadr + 08 iadr + 10 iadr + 12 iadr + 14 iadr + 16 iadr + 18 iadr + 20 iadr + 22 iadr + 24 16-bit scaler (if esen=1) mk50h27 28/56
4.2.3 protocol parameters parm description po protocol options. defines the ss7 protocol options to be used. bit name definition 00 dbusy dbusy = 1: disables busy mechanisms on both transmit and receive. missed msu interrupts (csr0<06>, miss) are not affected by this bit. 01 xyel xyel= 0: transmitted sins and sies conform to ccitt red/blue book definitions (sf = 1 and 2 respectively). xyel= 1: transmitted sins and sies conform to ccitt yellow book defini- tions (sf = 9 & 10 respectively). 02 ryel ryel= 0: only ccitt red/blue book definitions for received sins and sies are accepted. ryel= 1: either ccitt yellow or red/blue book definitions for re- ceived sins and sies are accepted. 03 rmode defines the retransmission method to be used. rmode = 0: specifies basic error recovery (bec). rmode = 1: specifies preventive cyclic redundancy(pcr). 04 becdouble provides double transmission of all msus in bec. all msu's including those sent during negative acknowledgement are transmit- ted twice. if rmode= 0 then the following definitions apply: becdouble = 0: specifies normal bec. becdouble = 1: specifies bec with doubletransmission. note: becdouble must be 0 if rmode = 1. 05 ermen enables the aerm and suerm error rate monitors. ermen = 0: disables the aerm and suerm. ermen = 1: enables the aerm and suerm. 06 octen enables octet counting. octen = 0: disables octet counting. octen = 1: enables octet counting. 07 2/3en enables 2/3 errored fib/bsn error monitoring. 2/3en = 0: disables 2/3 error monitoring. 2/3en = 1: enables 2/3 error monitoring. 08 ansit6/t7 selects ansi or itu compliance for ss7 t6 & t7 timers ansit6/t7 =0: t6 & t7 timer operation complies with itu q.703 ansit6/t7 =1: t6 & t7 timer operation complies with ansi t1.111.3 15-09 reserved must be programmed with all zeroes. 15 15 15 15 0 0 0 0 iadr + 26 iadr + 28 iadr + 30 iadr + 32 iadr + 34 0 14 m 0 tin tie 87 d tm 87 po mk50h27 29/56
t/ ttc d suerm threshold. number of consecutive signal units received in error that will cause an error rate high indication. when operating in ttc compliant mode (csr2 jss7e=1), this field should contain the d value (typically 16) used for ttc jt-q703 suerm operation. m proving abort limit. number of consecutive aborted proving periods that cause the mk50h27 to return to the out-of-service state. d/ ttc t suerm error rate. the lowest acceptable number of signal units per signal unit error. when operating in ttc compliant mode (csr2 jss7e=1), this field should contain the t suerm threshold value (typically 285) used for ttc jt-q703 suerm operation. this field should be expressed as a two's complement value. tin normal aerm threshold. number of signal unit errors that cause the abortion of a normal proving period. tie emergency aerm threshold. number of signal unit errors that cause the abortion of an emergency proving period. m maximum frame length. number of bytes allowed in the information portion of received msus before octect counting begins. note: the operation of the suerm (signal unit error rate monitor) is different between ccitt / itu compliant systems and ttc jt-q703 compliant systems. although both suerm schemes operate based upon a leaky bucket principle, there are some major differences in their implementation. for ccitt/itu q.703 the suerm count is incremented by 1 for each errored su received until a thresh- old t (typically 64) is reached, at which time a link failure is declared.. for every d (typically 256) good sus received the suerm count, cs, is decremented by 1 (not to go less than 0). for ttc jt-q703 the suerm count is updated once every monitor time te (typically 24 ms) regardless of the number of sus received during the time te. if the last su received was errored, then the suerm count is incremented by d (typically 16) when te expires. if the last su received was good, then the suerm count is decremented by 1 (not to go less than 0) when te expires. if the suerm count should ever reach the threshold t (typically 285), then a link failure is declared. for the mk50h27 the value used for time te is the same value as programmed for time tf (typically 24 ms for both). due to this difference in suerm operation, the fields in the mk50h27 initialization block that are used for d and t are exchanged if jss7e=1 selecting japanese ss7 (ttc jt-q703 compliance). mk50h27 30/56
4.2.4 receive descriptor ring pointer bit name description 15 0 reserved, must be written as a zero. 14:12 rlen receive ring length is the number of entries in the receive descriptor ring expressed as a power of two. rlen number of entries 01 12 24 38 416 532 664 7 128 11:08 0 reserved, must be written as zeroes. 07:00/15:00 rdra receive descriptor ring address is the base address (lowest address) of the receive descriptor ring. the receive de- scriptor address must begin on a word boundary. 4.2.5 transmit descriptor ring pointer 1 5 1 4 1 3 0 7 0 8 1 0 1 1 1 2 0 1 0 2 0 3 0 4 0 5 0 0 0 9 0 6 iadr + 36 iadr + 38 rdra<15:00> 0 0 rlen 0 0 0 0 rdra<23:16> 1 5 1 4 1 3 0 7 0 8 1 0 1 1 1 2 0 1 0 2 0 3 0 4 0 5 0 0 0 9 0 6 iadr + 40 iadr + 42 tdra<15:00> 0 0 tlen 0 0 0 0 tdra<23:16> mk50h27 31/56
4.2.5 transmit descriptor ring pointer (continued) bit name description 15 0 reserved, must be written as a zero. 14:12 tlen transmit ring length is the number of entries in the transmit ring expressed as a power of two. tlen number of entries 01 12 24 38 416 532 664 7 128 11:08 0 reserved, must be written as a zero. 07:00/15:00 tdra transmit descriptor ring address is the base address (lowest address) of the transmit descriptor ring. the transmit descriptor ring address must begin on a word boundary. 4.2.6 status buffer address bit name description 15:08 tws transmit window size is used to determine the maximum number of msus that can be transmitted without acknowledgement. for com- pliance with japanese ttc jt-q703 this value should typically be 40. for compliance with ccitt/itu q.703 this value should be 127. for compatibility with the original mk50h27, this field may be programmed with all zeroes, causing the mk50h27 to use a default value of 127 as did the mk50h27. 07:00/15:00 sba status buffer address points to the status buffer into which link status information is placed upon the issuance of the status request primitive by the host. the status buffer must be- gin on a word boundary. 1 5 1 4 1 3 0 7 0 8 0 0 1 1 1 2 0 1 0 2 0 3 0 4 0 5 0 0 0 9 0 6 iadr + 44 iadr + 46 sba<15:00> sba<23:16> 0 tws <15:08> mk50h27 32/56
4.2.7 reserved bit name description 15:00 0 reserved, must be written as zeroes. 4.2.8 statistics a significant portion of the initialization buffer is reserved for statistical information collected by the mk50h27. when a statistic is updated, the mk50h27 will read the appropriate statistic, increment it, and then write it back out to memory. these statistics are intended for the use of the host cpu for statistical analysis. the mk50h27 will only increment these counters; it is up to the user to clear and preset these counters. the statistics collected are: memory address error counter iadr + 50 sl failure - number of link failures due to abnormal fib/bsn received. iadr + 52 sl failure - number of link failures due to excessive delays of acknowledgementcaused by timer t7 time out. iadr + 54 sl failure - number of link failures due to excessive suerm error rate. iadr + 56 sl failure - number of link failures due to excessive congestion caused by timer t6 time out. iadr + 58 number of alignment failures due to timers t2 or t3 timing out. iadr + 60 number of alignment failues due to aerm exceeded. iadr + 62 number of negative acknowledgements received. iadr + 64 number of signal units in error. iadr + 66 - 122 reserved. must be programmed as zeroes. iadr + 124 number of sib's transmitted. iadr + 126 number of sib's received. iadr + 128 number of forced retransmissions caused by n1. iadr + 130 number of forced retransmissions caused by n2. iadr + 132 number of msu's retransmitted. iadr + 134 number of msu octets retransmitted. this value includes the opening and closing flags, bsn/bib, fsn/fib, li, and the ck octets. iadr + 136 - 198 reserved. must be programmed as zeroes. note: iadr+144 - 151 used for ttc jt-q703 compliant timers tf, ts, to, and ta if jss7e=1. see page 27 for details. 1 5 1 4 1 3 0 7 0 8 0 0 1 1 1 2 0 1 0 2 0 3 0 4 0 5 0 0 0 9 0 6 iadr + 48 reserved mk50h27 33/56
4.3 receive and transmit descriptor rings each descriptor ring in memory is a 4 word entry. the following is the format of the receive and transmit descriptors. 4.3.1 receive message descriptor entry 4.3.1.1 receive message descriptor 0 (rmd0) bit name description 15 owna when this bit is a zero either the host or the i/o acceleration processor owns this descriptor. when this bit is a one the mk50h27 owns this descriptor. the chip clears the owna bit af- ter filling the buffer pointed to by the descriptor entry provided a valid signal unit has been received. the host sets the owna bit after emptying the buffer. once the mk50h27, host, or i/o accelera- tion processor has relinquished ownership of a buffer, it may not change any field in the four words that comprise the descriptor entry. 14 ownb this bit determines whether the host or the layer 3 i/o processor owns the buffer when owna is a zero. the mk50h27 never uses this bit. this bit is provided to facilitate use of a layer 3 i/o processor. 13 slf start of long signal unit indicates that this is the first buffer used by mk50h27 for this signal unit. it is used for data chaining buffers. slf is set by the mk50h27. note: a olong signal unito is any msu which needs data chaining. 12 elf end of long signal unit indicates that this the last buffer used by mk50h27 for this signal unit. it is used for data chaining buffers. if both slf and elf were set, the signal unit would fit into one buffer and no data chaining would be required. elf is set by the mk50h27. 11:08 0 reserved, must be written as zeroes for ccitt/itu compliant operation. 11:10 prin these bits indicate the content of the priority indication bits of the received frame when jss7e=1 (ttc jt-q703 compliant mode). 07:00 rbadr the high order 8 address bits of the buffer pointed to by this descriptor. this field is written by the host and unchanged by mk50h27. 1 5 1 4 1 3 0 7 0 8 1 0 1 1 1 2 0 1 0 2 0 3 0 4 0 5 0 0 0 9 0 6 rbadr<23:16> o w n a o w n b s l f e l f 00 prin mk50h27 34/56
4.3.1.2 receive message descriptor 1 (rmd1) bit name description 15:01 rbadr the low order 16 address bits of the receive buffer pointed to by this descriptor. rbadr is written by the host cpu and unchanged by mk50h27. the receive buffers must be word aligned. 4.3.1.3 receive message descriptor 2 (rmd2) bit name description 15:00 bcnt buffer byte count is the length of the buffer pointed to by this descriptor expressed in two's complement. this field is written to by the host and unchanged by mk50h27. the value of bcnt must be an even number. 4.3.1.4 receive message descriptor 3 (rmd3) bit name description 15:00 mcnt message byte count is the length, in bytes, of the received signal unit. mcnt is valid only when elf is set to a one. mcnt is written by mk50h27 and read by the host. if elf is set to a zero the entire buffer has been utilized and the message byte count is given in bcnt above. the value of this field is expressed in two's comple- ment. 1 5 1 4 1 3 0 7 0 8 1 0 1 1 1 2 0 1 0 2 0 3 0 4 0 5 0 0 0 9 0 6 mcnt<15:00> 1 5 1 4 1 3 0 7 0 8 1 0 1 1 1 2 0 1 0 2 0 3 0 4 0 5 0 0 0 9 0 6 bcnt<15:00> 0 1 1 5 1 4 1 3 0 7 0 8 1 0 1 1 1 2 0 1 0 2 0 3 0 4 0 5 0 0 0 9 0 6 rbadr<15:00> 0 mk50h27 35/56
4.3.2 transmit message descriptor entry 4.3.2.1 transmit message descriptor 0 (tmd0) bit name description 15 owna when this bit is a zero either the host or the slave processor owns this descriptor. when this bit is a one the mk50h27 owns this descriptor. the host sets the owna bit after filling the buffer pointed to by the descriptor entry. the mk50h27 releases the descriptor after transmitting the buffer and receiving the proper acknow- ledgement from the receiver. after the mk50h27, host, or i/o ac- celeration processor has relinquished ownership of a buffer, it may not change any field in the four words that comprise the descriptor entry. 14 ownb this bit determines whether the host or the layer 3 i/o processor owns the buffer when owna is a zero. the mk50h27 never uses this bit. this bit is provided to facilitate use of a layer 3 i/o processor. 13 slf start of long signal unit indicates that this is the first buffer used by the mk50h27 for this signal unit. it is used for data chaining buffers. slf is set by the host. when not chaining, slf should be set to a one. note: a olong signal unito is any msu which needs data chaining. 12 elf end of long signal unit indicates that this is the last buffer used by the mk50h27 for this signal unit. it is used for data chaining buffers. if both slf and elf were set the signal unit would fit into one buffer and no data chaining would be required. elf is set by the host. when not chaining, elf should be set to a one. 11:08 0 reserved, must be written as zeroes for ccitt/itu operation. 11:10 prin these bits determine the content of the priority indication bits of the transmitted frame when jss7e=1 (ttc jt-q703 compliant mode). 07:00 tbadr the high order 8 address bits of the buffer pointed to by this descriptor. this field is written by the host and unchanged by mk50h27. 4.3.2.2 transmit message descriptor 1 (tmd1) bit name description 15:00 tbadr the low order 16 address bits of the buffer pointed to by this descriptor tbadr is written by the host and unchanged by mk50h27. the least significant bit is zero since the descriptor must be word aligned. 1 5 1 4 1 3 0 7 0 8 1 0 1 1 1 2 0 1 0 2 0 3 0 4 0 5 0 0 0 9 0 6 tbadr<15:00> 0 1 5 1 0 1 4 0 9 1 2 1 1 0 8 0 3 0 7 0 2 0 6 0 5 0 4 0 1 0 0 1 3 00 tbadr<23:16> o w n a o w n b s l f e l f prin mk50h27 36/56
4.3.2.3 transmit message descriptor 2 (tmd2) bit name description 15:00 sul signal unit length. only required when in the first descriptor of a signal unit (slf = 1) and when dace = 0. contains the length of the sif and the sio fields of the signal unit, in octets, to be transmit- ted. the value of this field is expressed as a positive integer. 4.3.2.4 transmit message descriptor 3 (tmd3) bit name description 15:00 mcnt message byte count is the length, in octets, of the data contained in the corresponding buffer. the value of this field is expressed in two's complement. 1 5 1 4 1 3 0 7 0 8 1 0 1 1 1 2 0 1 0 2 0 3 0 4 0 5 0 0 0 9 0 6 mcnt<15:00> 1 5 1 4 1 3 0 7 0 8 1 0 1 1 1 2 0 1 0 2 0 3 0 4 0 5 0 0 0 9 0 6 sul<15:00> mk50h27 37/56
1 5 1 4 1 3 0 7 0 8 1 0 1 1 1 2 0 1 0 2 0 3 0 4 0 5 0 0 0 9 0 6 rtidx phase tx state rx state tidx ridx bsnt bsnr b i b t b i b r fsnt/fsnc fsnr f i b t f i b r rfsn fsnx number of octets retransmitted reserved reserved release number firmware sba + 00 sba + 02 sba + 04 sba + 06 sba + 08 sba + 10 sba + 14 sba + 12 sba + 16-48 figure 4a: mk50h27 status buffer mk50h27 38/56
4.3.3 status buffer field description bibt the value of the last bib transmitted. bsnt the value of the last bsn transmitted. 0 bsnt 127. bibr the value of the last bib received. bsnr the value of the last bsn received. 0 bsnr 127. fibt the value of the last fib transmitted. fsnt/fsnc under normal operation this is the value of the last fsn transmitted. if a uprim 13 is to be issued in csr1 then the fsnc value to be read by the mk50h27 must be placed here by the host. 0 fsnt/fsnc 127. fibr the value of the last fib received. fsnr the value of the last fsn received. 0 fsnr 127. rfsn the value of the oldest unacknowledged fsnt in the retransmission buffer. 0 rfsn 127. fsnx the value of the next expected fsn to be received. 0 fsnx 127. tidx index to the descriptor of the current transmission buffer. ridx index to the descriptor of the current receive buffer. rtidx index to the first descriptor of the retransmission buffer. phase indicates the current phase of operation for the device. 0:power off. 2:out of service. 4: initial alignment not aligned. 5:initial alignment aligned. 6:initial alignment proving. 7:alignment not ready. 8:alignment ready. 9:in service. 10:processor outage. 11:transparent mode. 12:memory error. tx state indicates the current state of the transmitter. 0: the transmitter is waiting to transmit a signal unit. 1:a signal unit is currently being transmitted. 2:a signal unit transmission has completed. rx state indicates the current state of the receiver. 0:the receiver is expecting the beginning of a signal unit. 1:a msu is being transferred to the receive buffer(s). 2:end of frame detected. 3:receive data being ignored. 4:buffer chaining requested. firmware release indicates the release number of the firmware within the mk50h27. number number of octets this value represents the lower two bytes of the total number of octets retransmitted retransmitted. the number of octets retransmitted statistics counter represents the upper two bytes of the total number of octets re- transmitted. this two byte status buffer value together with the two byte error counter value provide a 32 bit value for the total num- ber of octets retransmitted. reserved must be programmed as zeroes. mk50h27 39/56
4.4 detailed programming procedures 4.4.1 initialization the following procedure should be followed to intialize the mk50h27: 1. setup bus control information in csr4. 2. setup the initialization block and desciptor rings. 3. load the address of the initialization block information into csr's 2 and 3. 4. issue the init primitive through csr1 instructing the mk50h27 to read the initialization block pointed to by csr's 2 and 3. 5. wait for the init confirmation primitive from the mk50h27. 6. for ss7 operation, issue the pon primitive through csr1, sios's will now be continuously transmit- ted. for hdlc transparent mode, issue the trans primitive through csr1, flags will now be conti- nously transmitted. 7. enable interrupts in csr0 if desired. 4.4.2 alignment 1. for ss7 operation issue the start primitive through csr1 to begin alignment. 2. wait for the in service provider primitive. 4.4.3 sending data use the following procedure to send a msu: 1. wait for the owna bit of the current transmit descriptor to be cleared, if it is not already. 2. fill the buffer associated with the current transmit descriptor with the data to be sent, or set the de- scriptor buffer address to any already filled buffer. 3. repeat steps 1 and 2 for the next buffer if chaining is necessary, setting slf, elf and mcnt appro- priately. 4. set the owna bit for each descriptor used. 4.4.4 receiving data the following procedure should be followed when receiving a msu: 1. make sure the owna bit of the current receive descriptor is clear. 2. read data out of the buffer associated with the current receive descriptor. 3. set the owna bit of the current receive descriptor. 4. if the elf bit of the current receive descriptor is clear, then go on to the next descriptor and repeat the above steps appending data from each buffer until a descriptor with the elf bit set is reached. 4.4.5 link disconnection the following procedure should be followed to disconnect an established link: 1. for ss7 operation, issue the stop primitive through csr1. the mk50h27 will enter the out of service state and continuously transmit sios's. 4.4.6 disabling the mk50h27 the following procedure should be followed to disable the mk50h27: 1. issue the poff primitive through csr1. this will disable the mk50h27 from receiving or transmit- ting. the td pin will be held high while the mk50h27 is in the power off state. the poff bit in csr0 will be set and interrupts will be disabled. if a link is currently established, then data may be lost. 4.4.7 re-enabling the mk50h27 the same procedure should be followed for re-enabling the mk50h27 as was used to initalize upon power up. if the initialization block and the hardware configuration have not changed, then steps 1,2,3, 4 and 5 of the intialization sequence may be omitted. mk50h27 40/56
4.4.8 mk50h27 internal self test the mk50h27 contains an easy to use internal self test designed to test, with a high fault coverage, all of the major blocks of the device except the dma controller. it is suggested that a loopback test also be performed to more completely test the dma controller. the following procedure should be followed to execute the internal self test: 1. reset the device using the reset pin. 2. set bit 04 of csr4. 3. issue a self test request through csr1. 4. poll csr1, waiting for the pav bit in csr1 to be set by the mk50h27. 5. after the pav bit is set, read csr1. the success or failure of the test is indicated in the pprim field as follows: pprim result 00 passed self test. 17 failed the reset test of the self test. 18 failed the self test in the micro controller ram. 19 failed the self test in the alu. 20 failed the self test in the timers. 21 failed the self test in the transmitter and/or receiver. 22 failed the self test in the csr's and/or bus master. otherwise failed device. 6. if the pav bit is not set within 75 msec (sysclk = 10mhz), then the mk50h27 is unable to respond to the self test request and will not complete successfully. if the self test passes, then it may be immediately reexecuted from step 3, otherwise re-execution should proceed from step 1. mk50h27 41/56
section 5 electrical specifications absolute maximum ratings symbol parameter value unit t ub temperature under bias -25 to +100 c t stg storage temperature -65 to +150 c v g voltage on any pin with respect to ground -0.5 to v cc +0.5 v p tot power dissipation 0.5 w stresses above those listed under oabsolute maximum ratingo may cause permanent damage to the above device. this is a stress rating only and functional operation of the device at these or any other condition above those indicated in the operational sections of this specification is not implied. exposure to absolute maximum rating conditions for ex- tended periods may affect device reliability. dc characteristics t a =0 cto70 c, v cc =+5v 5 percent unless otherwise specified. symbol parameter min. typ. max. units v il -0.5 +0.8 v v ih +2.0 v cc +0.5 v v ol @ iol = 3.2 ma +0.5 v v oh @ ioh= -0.4 ma +2.4 v i il @ vin = 0.4 to v cc +10 ma i cc @ tsct = 100 ns 50 m a capacitance f = 1mhz symbol parameter min. typ. max. units c in capacitance on input pins 10 pf c out capacitance on output pins 10 pf c io capacitance on i/o pins 20 pf ac timing specifications t a =0 cto70 c, v cc =+5v 5 percent, unless otherwise specified. mk50h27 -16 -25 -33 -16/25/33 no signal symbol parameter test condition min. min. min. max. units 1 sysclk t sct sysclk period 60 40 30 10000 ns 2 sysclk t scl sysclk low time 24 16 12 ns 3 sysclk t sch sysclk high time 24 16 12 ns 4 sysclk t scr rise time of sysclk 0 0 0 8 ns 5 sysclk t scf fall time of sysclk 0 0 0 8 ns 6 tclk t tct tclk period 20 20 20 ns 7 tclk t tcl tclk low time 8 8 8 ns 8 tclk t tch tclk high time 8 8 8 ns 9 tclk t tcr rise time of tclk cl = 50 pf 0 0 0 8 ns 10 tclk t tcf fall time of tclk 0 0 0 8 ns 11 td t tdp td data propagation delay after the falling edge of tclk cl = 50 pf 13 ns 12 td t tdh td data hold time after the falling edge of tclk 555 ns mk50h27 42/56
ac timing specifications continued - mk50h27 -25 t a =0 cto70 c, v cc =+5v 5 percent, unless otherwise specified. no signal symbol parameter notes min. typ. max. units 13 rclk t rct rclk period 20 ns 14 rclk t rch rclk high time 8 ns 15 rclk t rcl rclk low time 8 ns 16 rclk t rcr rise time of rclk 0 8 ns 17 rclk t rcf fall time of rclk 0 8 ns 18 rd t rdr rd data rise time 0 8 ns 19 rd t rdf rd data fall time 0 8 ns 20 rd t rdh rd hold time after rising edge of rclk 2 ns 21 rd t rds rd setup time prior to rising edge of rclk 8ns 22 ale/das t doff bus master driver disable output delay 0 20 ns 23 ale/das t don bus master driver enable after rising edge t1 sysclk output delay 0 20 ns 24 hlda t hha delay to falling edge of hlda from falling edge of hold (bus master) 0ns 25 hlda t hlah hlda input setup time 10 ns 26 hlda t hlas delay to rising edge hlda from rising edge hold 10 ns 27 a t xas address setup time output delay 30 ns 28 a t xah address hold time output delay 20 ns 29 dal t as address setup time output delay 35 ns 30 dal t ah address hold time output delay 0 20 ns 31 dal t rdas data setup time (bus master read) 15 ns 32 dal t rdah data hold time (bus master read) 10 ns 33 dal t wah address hold time (bus master write) output delay 15 ns 34 dal t wds data setup time (bus master write) output delay 25 ns 35 dal t wdh data hold time (bus master write) output delay 25 ns 36 dal t srds data setup time (bus slave read) 25 ns 37 dal t srdh data hold time (bus slave read) 25 ns 38 dal t swdh data hold time (bus slave write) 10 ns 39 dal t swds data setup time (bus slave write) 10 ns 40 ale t ales ale setup time output delay 30 ns 41 ale t alhb ale hold time (asserted to de- asserted) (dma burst) output delay 15 ns 42 ale t alhs ale hold time (asserted to 3-state) (single dma cycle) output delay 20 ns 43 das t dass das setup time from falling edge of t2 sysclk (bus master) output delay 25 ns 44 das t dash das hold time from rising edge of sysclk (bus master) output delay 5 15 ns 4 5 dali/dalo bm)/bm1 t bmde bus master driver enable (from 3- state to driven) (bus master) output delay 25 ns 46 dali t ris dali setup time (bus master read) output delay 15 ns 47 dali t rih dali hold time (bus master read) output delay 25 ns 48 dali t bmdd bus master driver disable (from driven to 3-state) (bus master) output delay 20 ns mk50h27 -25 mk50h27 43/56
mk50h27 -25 ac timing specifications continued - mk50h27 -25 t a =0 cto70 c, v cc =+5v 5 percent, unless otherwise specified. no signal symbol parameter notes min. typ. max. units 49 dalo t ros dalo setup time (bus master read) output delay 30 ns 50 dalo t roh dalo hold time (bus master read) output delay 30 ns 52 cs t csh cs hold time 10 ns 53 cs t css cs setup time 10 ns 54 adr t sah adr hold time 10 ns 55 adr t sas adr setup time 10 ns 56 das t sdas das input setup time (bus slave) 10 ns 57 das t sdsh das input hold time (bus slave) 10 ns 58 ready t rdys ready setup time (bus slave) output delay 15 ns 59 ready t sryh ready hold time after rising edge of das (bus slave read) 15 ns 60 ready t rsh ready setup time (bus master) 18 ns 61 ready t srs ready hold time (bus master) 10 ns 62 read t reds read setup time (bus slave) 10 ns 63 read t redh read hold time (bus slave) 10 ns 64 hold t hlds hold setup time (bus master) output delay 15 ns 65 hold t hldh hold hold time (bus master) output delay 35 ns mk50h27 44/56
c l 0.4 ma cr cr cr cr 1 2 3 4 r1 = 1.2 k cr1 - cr4 = 1n914 or equiv test point from output under test r1 = 1.4 k c l vcc vcc c = 50pf min @ 1 mhz l from output under test note: this load is used on all outputs except intr, hold, ready. note: this load is used on open drain outputs intr, hold, ready. figure 5a: ttl output load diagram figure 5b: open drain output load diagram rclk 13 15 14 16 17 21 20 19 18 rd 12 6 87 10 11 9 td tclk o0o o.8 v o.8 v 90 % o1o 2.0 v 2.0 v 10 % output input float timing measurements are made at the following voltages, unless otherwise specified: figure 6: mk50h27 serial link timing diagram mk50h27 45/56
a 16-23 ale sysclk address bm0,1 ready das hlda hold notes: 2. output delay times are the maximum delay from the specifed edge to a valid output. 3. the bus master cycle time will increase from a minimum, in 1 sysclk increments until the slave device returns ready. 64 24 25 65 26 27 40 23 23 43 44 41 42 28 22 60 61 t0 t1 t2 t3 t4 t5 t6 dal0-15 read dalo dali 29 30 50 32 45 data in addr 31 49 48 47 46 48 1. the shaded sysclk periods t0 and t5 will be removed when setting csr2 bit 15, cycle =1 to select the shorter dma cycle as shown in figure 7a. figure 7: mk50h27 bus master timing (read) (for cycle = 0, csr2<15>) mk50h27 46/56
a 16-23 ale sysclk bm0,1 ready das hlda hold 64 24 25 65 26 27 40 23 23 44 41 42 28 22 t1 t2 t3 t4 t5 dal0-15 read dalo dali 29 30 50 32 45 data in addr 31 49 48 47 46 48 address 60 61 43 notes: 2. output delay times are the maximum delay from the specifed edge to a valid output. 3. the bus master cycle time will increase from a minimum, in 1 sysclk increments until the slave device returns ready. 1. this reduced dma cycle time is selected by setting csr2 bit 15, cycle =1. figure 7a: mk50h27 reduced cycle bus master timing (read) (for cycle = 1, csr2<15>) mk50h27 47/56
a 16-23 ale sysclk address bm0,1 ready das hlda hold notes: 2. output delay times are the maximum delay from the specifed edge to a valid output. 3. the bus master cycle time will increase from a minimum, in 1 sysclk increments until the slave device returns ready. 64 24 25 65 26 27 40 23 23 43 44 41 42 28 22 60 61 48 48 t0 t1 t2 t3 t4 t5 t6 data addr dal0-15 read dalo dali 29 34 33 35 45 1. the shaded sysclk periods t0 and t5 will be removed when setting csr2 bit 15, cycle =1 to select the shorter dma cycle as shown in figure 8a. figure 8: mk50h27 bus master timing diagram (write) (for cycle = 0, csr2<15>) mk50h27 48/56
a 16-23 ale sysclk bm0,1 ready das hlda hold 25 65 26 27 40 23 23 43 44 41 42 28 22 60 61 48 48 t1 t2 t3 t4 t5 data addr dal0-15 read dalo dali 29 34 33 35 45 address 64 24 notes: 2. output delay times are the maximum delay from the specifed edge to a valid output. 3. the bus master cycle time will increase from a minimum, in 1 sysclk increments until the slave device returns ready. 1. this reduced dma cycle time is selected by setting csr2 bit 15, cycle = 1. times t0 and t5 from the standard dma cycle are removed for this reduced timing. figure 8a mk50h27 reduced cycle bus master timing (write) (for cycle = 1, csr2<15>) mk50h27 49/56
a 16-23 ale sysclk bm0,1 ready das hlda hold 25 27 40 23 23 43 44 27 t1 t2 t3 t4 t5 dal0-15 read dalo dali 29 45 address 64 24 65 26 41 42 22 61 48 t1 t2 t3 t4 t5 address 40 41 43 44 60 data addr 34 33 48 35 34 data addr 29 61 60 28 figure 8b: bus master burst timing (reduced cycle - write) mk50h27 50/56
sysclk adr ready dal data out cs das read (read) 0-15 1. input setup and hold times are in minimum values required to or from the particular edge specified in order to be recognized in that cycle. 2. output delay times are from the specified edge to a valid output. notes: 53 52 55 54 56 57 58 59 62 63 36 37 figure 9: mk50h27 bus slave timing diagram (read) mk50h27 51/56
sysclk adr das read (write) dal0-15 data in cs ready 1. input setup and hold times are the minimum values required to or from the particular edge specified in order to be recognized in that cycle. 2. output delay times are from the specified edge to a valid output. notes: 53 52 54 55 56 57 58 59 62 63 39 38 figure 10: mk50h27 bus slave timing diagram (write) mk50h27 52/56
ordering information mk50h27 q xx speed sort 25 = 25mhz sysclk package n = plastic dip (48 pins) q = plastic j-leaded chip carrier (52 pins) part# protocol 50h27 = ss7 layer 2 protocol mk50h27 53/56
dip48 package mechanical data dim. mm inch min. typ. max. min. typ. max. a1 0.63 0.025 b 0.45 0.018 b1 0.23 0.31 0.009 0.012 b2 1.27 0.050 d 62.74 2.470 e 15.2 16.68 0.598 0.657 e 2.54 0.100 e3 58.42 2.300 f 14.1 0.555 i 4.445 0.175 l 3.3 0.130 mk50h27 54/56
plcc52 package mechanical data dim. mm inch min. typ. max. min. typ. max. a 4.20 5.08 0.165 0.20 a1 0.51 0.020 a3 2.29 3.30 0.090 0.13 b 0.33 0.53 0.013 0.021 b1 0.66 0.81 0.026 0.032 c 0.25 0.01 d 19.94 20.19 0.785 0.795 d1 19.05 19.20 0.750 0.756 d2 17.53 18.54 0.690 0.730 d3 15.24 0.60 e 19.94 20.19 0.785 0.795 e1 19.05 19.20 0.750 0.756 e2 17.53 18.54 0.690 0.730 e3 15.24 0.60 e 1.27 0.05 l 0.64 0.025 l1 1.53 0.060 mk50h27 55/56
information furnished is believed to be accurate and reliable. however, sgs-thomson microelectronics assumes no responsibility for the consequences of use of such information nor for any infringement of patents or other rights of third parties which may result from its use. no license is granted by implication or otherwise under any patent or patent rights of sgs-thomson microelectronics. specification mentioned in this publication are subject to change without notice. this publication supersedes and replaces all information previously supplied. sgs- thomson microelectronics products are not authorized for use as critical components in life support devices or systems without express written approval of sgs-thomson microelectronics. ? 1997 sgs-thomson microelectronics printed in italy all rights reserved sgs-thomson microelectronics group of companies australia - brazil - canada - china - france - germany - hong kong - italy - japan - korea - malaysia - malta - morocco - the netherlands - singapore - spain - sweden - switzerland - taiwan - thailand - united kingdom - u.s.a. mk50h27 56/56

▲Up To Search▲

Price & Availability of MK50H27DIP

	To Download MK50H27DIP Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .