View PSB7110-FV10_1387266.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

ics for communications enhanced isdn data access controller isar psb 7110 version 1.0 software version #4 data sheet 07.96 t7110-xv10-d3-7600
_________________________________________________psb 7110 siemens aktiengesellschaft page 2 psb 7110 revision history: fehler! textmarke nicht definiert. previous releases: page subjects (changes since last revision) published by siemens ag, bereich halbleiter, product definition, balanstra?e 73, d-81541 mnchen ? siemens ag 1995. all rights reserved. as far as patents or other rights of third parties are concerned, liability is only assumed for components per se, not for applications, processes and circuits implemented within components or assemblies. the information describes the type of component and shall not be considered as assured characteristics. terms of delivery and rights to change design reserved. for questions on technology, delivery, and prices please contact the office of semiconductor group in germany or the siemens companies and representatives worldwide (see address list). due to technical requirements components may contain dangerous substances. for information on the type in question please contact your nearest siemens office, semiconductor group. siemens ag is an approved cecc manufacturer.
_________________________________________________psb 7110 siemens aktiengesellschaft page 3 contents general information ................................ ................................ ................................ ................................ ................... 6 1 features ................................ ................................ ................................ ................................ .............................. 7 1.1 system integration ................................ ................................ ................................ ................................ ........ 8 1.1.1 isdn pc / workstation adapter with so interfaces ................................ ................................ ....... 8 1.1.2 isdn voice/data terminal ................................ ................................ ................................ .............. 9 1.1.3 isdn standalone terminal with pots interface ................................ ................................ ........... 10 1.2 logic symbol ................................ ................................ ................................ ................................ ................ 11 1.3 pin configuration ................................ ................................ ................................ ................................ .......... 12 1.4 device architecture ................................ ................................ ................................ ................................ ....... 13 1.5 pin description ................................ ................................ ................................ ................................ .............. 14 1.6 clock generation ................................ ................................ ................................ ................................ .......... 18 1.7 memory configuration ................................ ................................ ................................ ................................ .. 19 2 functional description ................................ ................................ ................................ ................................ ....... 20 2.1 general functions ................................ ................................ ................................ ................................ ........ 20 2.1.1 clock generation ................................ ................................ ................................ ............................ 21 2.1.2 interfaces ................................ ................................ ................................ ................................ ......... 21 2.1.2.1 iom-2 interface ................................ ................................ ................................ ...................... 21 2.1.2.2 host interface ................................ ................................ ................................ ........................ 21 2.1.2.3 communications interface ................................ ................................ ................................ .... 22 2.2 buffer configuration ................................ ................................ ................................ ................................ ..... 26 2.3 sart configuration ................................ ................................ ................................ ................................ ..... 27 2.3.1 async mode ................................ ................................ ................................ ................................ .. 27 2.3.2 hdlc mode ................................ ................................ ................................ ................................ .... 27 2.3.3 binary mode ................................ ................................ ................................ ................................ .... 28 2.4 pump configuration ................................ ................................ ................................ ................................ ..... 28 2.4.1 fax modulations ................................ ................................ ................................ .............................. 29 2.4.2 datamodem modulations ................................ ................................ ................................ ................ 29 2.4.3 halfduplex modulations ................................ ................................ ................................ ................... 29 2.4.4 v.110 ................................ ................................ ................................ ................................ ............... 29 2.4.5 dtmf ................................ ................................ ................................ ................................ .............. 30 2.4.6 dtmf transmission ................................ ................................ ................................ ........................ 30 2.4.7 bypass mode ................................ ................................ ................................ ................................ ... 30 2.5 iom-2 configuration ................................ ................................ ................................ ................................ ..... 30 3 operational description ................................ ................................ ................................ ................................ ..... 31 3.1 general information ................................ ................................ ................................ ................................ ...... 31 3.1.1 configuration after reset ................................ ................................ ................................ ................ 31 3.1.2 message transfer from host to isar ................................ ................................ ............................. 33 3.1.3 message transfer from isar to host ................................ ................................ ............................. 35 3.1.4 message overview ................................ ................................ ................................ .......................... 37 3.1.5 message structure ................................ ................................ ................................ .......................... 40 3.1.5.1 interrupt status byte ................................ ................................ ................................ .............. 41 3.1.5.2 control registers and parameters ................................ ................................ ........................ 44 3.2 buffer configuration ................................ ................................ ................................ ................................ ..... 45 3.2.1 buffer configuration setup (host ? isar) ................................ ................................ .................... 45 3.2.2 buffer configuration request (host ? isar) ................................ ................................ ................ 46 3.2.3 buffer configuration response (isar ? host) ................................ ................................ ............. 47 3.2.4 buffer control command (host ? isar) ................................ ................................ ........................ 49 3.3 buffer status ................................ ................................ ................................ ................................ ................. 50 3.3.1 buffer status request (host ? isar) ................................ ................................ ........................... 50 3.3.2 buffer status response (isar ? host) ................................ ................................ ........................ 51 3.3.3 buffer status event (isar ? host) ................................ ................................ ................................ 53 3.3.3.1 buffer specific status event (isar ? host) ................................ ................................ ........ 53 3.3.3.2 buffer general status event (isar ? host) ................................ ................................ ........ 54 3.4 sart configuration ................................ ................................ ................................ ................................ ..... 55 3.4.1 sart configuration setup - hdlc (host ? isar) ................................ ................................ ...... 55 3.4.2 sart c onfiguration setup - async (host ? isar) ................................ ................................ .... 57 3.4.3 sart configuration setup - binary (host ? isar) ................................ ................................ ...... 59 3.4.4 sart configuration setup - disable sart (host ? isar) ................................ ......................... 60 3.5 sart data ................................ ................................ ................................ ................................ ................... 61 3.5.1 sart status events with receive data (isar ? host) ................................ ............................... 61 3.5.1.1 sart status events with receive data - hdlc (isar ? host) ................................ ........ 61
_________________________________________________psb 7110 siemens aktiengesellschaft page 4 3.5.1.2 sart status events with receive data - async (isar ? host) ................................ ...... 63 3.5.1.3 sart status events with receive data - binary (isar ? host) ................................ ........ 64 3.5.2 sart control commands with transmit data (host ? isar) ................................ ..................... 65 3.5.2.1 sart control commands with transmit data - hdlc (host ? isar) .............................. 65 3.5.2.2 sart control commands with transmit data - async (host ? isar) ........................... 67 3.5.2.3 sart control commands with transmit data - binary (host ? isar) .............................. 68 3.6 pump configuration ................................ ................................ ................................ ................................ ..... 69 3.6.1 pump configuration setup (host ? isar) ................................ ................................ .................... 69 3.6.1.1 pump configuration setup - fax modulations (host ? isar) ................................ ............ 70 3.6.1.2 pump configuration setup - datamodem modulations (host ? isar) .............................. 71 3.6.1.3 pump configuration setup - halfduplex modulatio ns (host ? isar) ................................ . 74 3.6.1.4 pump configuration setup - v.110 (host ? isar) ................................ ............................. 76 3.6.1.5 pump configuration setup - dtmf (host ? isar) ................................ ............................ 78 3.6.1.6 pump configuration setup - dtmf transmission (host ? isar) ................................ ...... 80 3.6.1.7 pump configuration setup - bypass mode (host ? isar) ................................ ................. 81 3.6.2 pump control command (host ? isar) ................................ ................................ ...................... 82 3.6.2.1 pump control command - fax modulations (host ? isar) ................................ .............. 82 3.6.2.2 pump control command - datamodem modulations (host ? isar) ................................ 85 3.6.2.3 pump control command - halfduplex modulations (ho st ? isar) ................................ ... 85 3.6.2.4 pump control command - v.110 (host ? isar) ................................ ............................... 86 3.6.2.5 pump control command - dtmf (host ? isar) ................................ ............................... 87 3.6.2.6 pump control command - dtmf transmission (host ? isar) ................................ ........ 88 3.6.2.7 pump control command - bypass mode (host ? isar) ................................ ................... 88 3.7 pump status ................................ ................................ ................................ ................................ ................. 89 3.7.1 pump status request (host ? isar) ................................ ................................ ........................... 89 3.7.2 pump status response (isar ? host) ................................ ................................ ........................ 90 3.7.2.1 pump status response - fax modulations (isar ? host) ................................ ................. 90 3.7.2.2 pump status response - datamodem modulations (isar ? host) ................................ .. 92 3.7.2.3 pump st atus response - halfduplex modulations (isar ? host) ................................ ..... 95 3.7.2.4 pump status response - v.110 (isar ? host) ................................ ................................ .. 97 3.7.2.5 pump status response - dtmf (isar ? host) ................................ ................................ . 100 3.7.2.6 pump status response - dtmf transmission (isar ? host) ................................ .......... 101 3.7.2.7 pump status response - bypass mode (isar ? host) ................................ ..................... 102 3.7.2.8 pump status response - pump disabled (isar ? host) ................................ .................. 103 3.7.3 pump status events (isar ? host) ................................ ................................ .............................. 104 3.7.3.1 pump status events - fax modulations (isar ? host) ................................ ...................... 104 3.7.3.2 pump status events - datamodem modu lations (isar ? host) ................................ ........ 106 3.7.3.3 pump status events - halfduplex modulations (isar ? host) ................................ ........... 107 3.7.3.4 pump status events - v.110 (isar ? host) ................................ ................................ ....... 108 3.7.3.5 pump status events - dtmf (isar ? host): ................................ ................................ ..... 111 3.7.3.6 pump status events - dtmf transmission (isar ? host): ................................ ............... 111 3.7.3.7 pump status events - bypass mode (isar ? host): ................................ .......................... 111 3.8 iom-2 configuration ................................ ................................ ................................ ................................ ..... 112 3.8.1 iom-2 configuration setup (host ? isar) ................................ ................................ ................... 112 3.8.2 iom-2 configuration request (host ? isar) ................................ ................................ ............... 115 3.8.3 iom-2 configuration response (isar ? host) ................................ ................................ ............ 116 3.8.4 iom-2 control commands (host ? isar) ................................ ................................ .................... 118 3.9 test / diagnostics path ................................ ................................ ................................ ................................ . 119 3.9.1 general configuration (host ? isar) ................................ ................................ ........................... 119 3.9.2 timer interrupt request (isar ? host) ................................ ................................ ........................ 120 3.9.3 software version request (host ? isar) ................................ ................................ .................... 120 3.9.4 software version response (isar ? host) ................................ ................................ .................. 120 3.9.5 invalid message received (isar ? host) ................................ ................................ ..................... 121 3.9.6 request selftest result (isar ? host) ................................ ................................ ......................... 121 3.9.7 selftest response (isar ? host) ................................ ................................ ................................ . 122 3.10 dsp program download ................................ ................................ ................................ .......................... 123 3.10.1 hardware reset ................................ ................................ ................................ .............................. 123 3.10.2 host interrupt ena ble ................................ ................................ ................................ ...................... 123 3.10.3 verify chip version number ................................ ................................ ................................ ........... 124
_________________________________________________psb 7110 siemens aktiengesellschaft page 5 3.10.4 program code download ................................ ................................ ................................ ............... 125 3.10.5 dsp program start ................................ ................................ ................................ ......................... 129 3.11 fax class 1 implementation ................................ ................................ ................................ ..................... 130 3.11.1 summary of isar fax control commands ................................ ................................ ................... 131 3.11.2 summary of isar fax status events ................................ ................................ ............................. 132 3.11.3 procedure termination ................................ ................................ ................................ ................... 133 3.11.4 fax pump startup procedure ................................ ................................ ................................ ......... 134 3.11.5 hdlc transmission ................................ ................................ ................................ ........................ 135 3.11.6 binary transmission ................................ ................................ ................................ ........................ 136 3.11.7 hdlc reception ................................ ................................ ................................ ............................. 137 3.11.8 binary reception ................................ ................................ ................................ ............................. 138 3.11.9 call termination ................................ ................................ ................................ .............................. 139 3.11.10 procedure terminations ................................ ................................ ................................ .................. 139 3.12 datamod em automode operation ................................ ................................ ................................ ........... 140 4. summary of messages ................................ ................................ ................................ ................................ ....... 142 5. example configuration settings ................................ ................................ ................................ ........................ 146 6. detailed register description ................................ ................................ ................................ ............................ 148 6.1 register address map ................................ ................................ ................................ ................................ .. 148 6.2 register description ................................ ................................ ................................ ................................ ..... 148 7. hardware and software support ................................ ................................ ................................ ....................... 151 8. electrical specification ................................ ................................ ................................ ................................ ....... 153 8.1 absolute maximum ratings ................................ ................................ ................................ .......................... 153 8.2 recommended operating conditions ................................ ................................ ................................ ......... 153 8.3 dc characteristics ................................ ................................ ................................ ................................ ........ 153 8.4 capacitances ................................ ................................ ................................ ................................ ................ 154 8.5 oscillator circuit ................................ ................................ ................................ ................................ ............ 154 8.6 xtal1,2 recommended typical crystal parameters ................................ ................................ ................. 155 8.8 ac characteristics ................................ ................................ ................................ ................................ ........ 156 8.8.1 testi ng waveform ................................ ................................ ................................ ........................... 156 8.8.2 parallel host interface timing ................................ ................................ ................................ ......... 156 8.8.3 external memory interface timing ................................ ................................ ................................ .. 158 8.8.4 iom-2 interface timing ................................ ................................ ................................ ................... 160 8.9 esd capability ................................ ................................ ................................ ................................ ............... 160 9. package outline ................................ ................................ ................................ ................................ .................. 161
_________________________________________________psb 7110 siemens aktiengesellschaft page 6 general information the isar psb 7110, isdn data access controller forms an advanced solution for isdn applications communicating with remote isdn as well as analog terminals. the isar is designed for applications on pc- or workstation platforms, but can also be used in isdn/analog combining terminals. it integrates two data formatting units which support binary framing, hdlc and async, which is an asynchronous data formatting according to itu-t v.14. the data from the formatting units is than input data to a fax/modem modulation or v.110 or transparent framing towards the iom-2 timeslots. the psb 7110 operates on the iom-2 interface in terminal mode (1.536 mhz dcl). it is also designed to operate on line-card iom-2 interfaces (4 mhz dcl). the isdn data access controller uses external ram to implement a 61 byte fifo structure between the host and the data formatting unit. the dsp program is also executed from external memory. the psb 7110 isdn data access controller is a 0.5 micron cmos device offered in a thin quad-flat pack package. it operates from a single 3.6v supply with the option to drive the interface lines by a 5v supply. as isar version 1.0 ensures firmware safety through its program download mechanism, a rom version will be following that will only require external sram of reduced size. this device will be isar version 1.1. important note: software version #4 the isar v1.0 requires download software which is provided separately with the device. this specification describes the functionality of the device with the software download version number 4. see chapter 3.9.4 software version response: svn (software version number) = 04h
_________________________________________________psb 7110 siemens aktiengesellschaft page 7 1 features * two universal formatter supporting async (itu-t v.14), hdlc and binary framing of data for b-channel applications * bit rate adaptation according to v.110 for both b-channels (except during datamodem modulation) * iom-2 terminal mode (1.536 mhz), line card mode (4 mhz) * fax/modemmodulation up to 14400 bps (v.32 bis, v.17) including fallback modes * dtmf generation / detection * 61 byte fifo per direction for host interface communication * external memory interface to connect external sram with a size of 32k x 16 for program and data * mailbox interface for host communication * 3.6v power supply with separate 5v supply for interface pins * thin qfp-package * advanced cmos technology type ordering code package psb 7110f v1.0 q67101-h6748 p-tqfp-100-1
_________________________________________________psb 7110 siemens aktiengesellschaft page 8 1.1 system integration 1.1.1 isdn pc / workstation adapter with so interfaces the isdn pc or workstation adapter is based on the isar. a psb 2186, isac-s te forms the so-transceiver and provides the hdlc controller to perform the d-channel signalling protocol. external circuitry is required for the so interfaces which includes the transformer and protection circuitry. the host interface of the isar is connected to the host bus. isac-s te psb 2186 so interface interface logic host interface iom-2 isar psb7110 s r a m 3 2 k x 1 6 (7110_11) figure 1 isdn pc / workstation adapter the isar supports hdlc based applications like file transfer, access to packet switches (x.75, v.120, ppp). it also supports communication to terminal adapters which perform bit rate adaptation according to v.110. a special feature of the isar is its support for analog fax/modem applications. therefore, pcm data is converted to linear data and handled by a v.32bis / v.17 data pump to support data rates up to 14400 bps.
_________________________________________________psb 7110 siemens aktiengesellschaft page 9 1.1.2 isdn voice/data terminal figure 2 shows a voice data terminal developed on a pc card, where the isar provides its fax and modem functionality within a three chip solution. during isdn calls the arcofi-sp psb 2163 provides for speakerphone functions and includes a dtmf generator. isac-s te psb 2186 so interface interface logic host interface iom-2 isar psb7110 s r a m 3 2 k x 1 6 a r c o f i - s p p s b 2 1 6 3 (7110_14) figure 2 isdn voice/data terminal
_________________________________________________psb 7110 siemens aktiengesellschaft page 10 1.1.3 isdn standalone terminal with pots interface figure 3 shows a standalone terminal that may be connected to the communications interface of a pc providing isar's fax and modem functionality within a microcontroller based solution. the arcofi-ba psb 2161 enables connection of analog terminals, e.g. telephones, to the pots interface. isac-s te psb 2186 so interface m i c r o c o n t r o l l e r pc interface iom-2 isar psb7110 s r a m 3 2 k x 1 6 a r c o f i - b a p s b 2 1 6 1 v.24 interface slic pots (7110_29) figure 3 isdn standalone terminal with pots interface
_________________________________________________psb 7110 siemens aktiengesellschaft page 11 1.2 logic symbol dd du dcl f s c r e s e t c a ( 0 : 1 5 ) c d ( 0 : 1 5 ) cwr# c r d # i o m - 2 i n t e r f a c e e x t e r n a l m e m o r y i n t e r f a c e cds# x t a l 1 p s b 7 1 1 0 x t a l 2 c p s # cs# p a r a l l e l h o s t i n t e r f a c e i n t # a d ( 0 : 7 ) r d # w r # a l e v d d v s s v d d p p o w e r s u p p l y c l k o v r e f r a d j s y s t e m c l o c k i n t e r f a c e e a # c m 0 v s s a v d d a c m 1 g e n e r a l c o n t r o l (7110_18) figure 5 logic symbol
_________________________________________________psb 7110 siemens aktiengesellschaft page 12 1.3 pin configuration as for the rom version isar v1.1 some of the 5 v pins are changed to 3.6 v, the system layout should be designed in a way, that a change from v1.0 to v1.1 only requires a different jumper setting. so pins 34, 41, 52, 58 and 65 can be set either to vddp (v1.0) or vdd (v1.1). c d 0 v s s r e s . r e s . r e s . p u r a d j v r e f r e s e t p u c l k o v d d p v s s v d d a x t a l 1 x t a l 2 v s s a v d d v s s c m 1 c m 0 r e s . r e s . p u p u r e s . a l e c s # r d # w r # a d 7 a d 6 a d 5 a d 4 v d d p v s s v d d a d 3 a d 2 a d 1 a d 0 r e s . i n t # r e s . f s c d c l d u d d c a 1 5 c d 1 5 c a 1 4 c d 1 4 v d d p v s s c a 1 3 c d 1 3 c a 1 2 c d 1 2 ( v d d ) v d d p v s s v d d c a 1 1 c d 1 1 c a 1 0 c d 1 0 ( v d d ) v d d p v s s e a # c d s # c p s # c w r # c r d # c a 9 c d 9 c a 8 1 c a 0 c d 1 c a 1 v s s v d d p c d 2 c a 2 c d 3 c a 3 v s s v d d p ( v d d ) c d 4 c a 4 c d 5 c a 5 v d d v s s v d d p ( v d d ) c d 6 c a 6 c d 7 c a 7 v s s v d d p ( v d d ) c d 8 5 1 p s b 7 1 1 0 v 1 . 0 p - t q f p - 1 0 0 2 6 7 6 (7110_19) figure 6 pinout
_________________________________________________psb 7110 siemens aktiengesellschaft page 13 1.4 device architecture cs# i n t # a d ( 0 : 7 ) r d # w r # a l e c a ( 0 : 1 5 ) c d ( 0 : 1 5 ) cwr# c r d # cds# c p s # r e s e t e a # (7110_15) figure 7 device architecture
_________________________________________________psb 7110 siemens aktiengesellschaft page 14 1.5 pin description parallel host interface pin no. symbol in (i) out (o) function 16 15 14 13 9 8 7 6 ad0 ad1 ad2 ad3 ad4 ad5 ad6 ad7 i/o i/o i/o i/o i/o i/o i/o i/o address/data bus transfers addresses and data between the host and the isar psb 7110. 4 rd# i read this signal indicates a read operation. 5 wr# i write this signal indicates a write operation. 3 cs# i chip select 2 ale i address latch enable a "high" on this line indicates an address on ad(0:7), that will be latched by the isar. this allows the isar to be directly connected to a host with multiplexed address/data bus. 18 int# o (od) interrupt request this signal is activated, when the isar requests an interrupt. this pin is an open drain output only. iom-2 interface pin no. symbol in (i) out (o) function 23 dd i/o data downstream on iom-2/pcm interface. 22 du i/o data upstream on iom-2/pcm interface. 21 dcl i data clock clock frequency is twice the data rate, or equal to the data rate. 20 fsc i frame sync marks the beginning of a physical iom-2 or pcm frame. system clocks pin no. symbol in (i) out (o) function 90 xtal1 i crystal in or clock in if a crystal is used, it is connected between xtal1 and xtal2. if a clock signal is provided (via an external oscillator), this signal is input via xtal1. in this case the xtal2 output is to be left non-connected. 91 xtal2 o crystal out left unconnected if a crystal is not used. 83 vref i not used, connect to vssa or vdda. 82 radj i not used, connect to vssa, vdda or leave open.
_________________________________________________psb 7110 siemens aktiengesellschaft page 15 86 clko o clock out output clock of frequency equal to an internal reference frequency divided by a programmable factor. this function is currently not supported.
_________________________________________________psb 7110 siemens aktiengesellschaft page 16 external memory interface pin no. symbol in (i) out (o) function 75 73 69 67 63 61 56 54 50 48 39 37 32 30 26 24 ca0 ca1 ca2 ca3 ca4 ca5 ca6 ca7 ca8 ca9 ca10 ca11 ca12 ca13 ca14 ca15 o o o o o o o o o o o o o o o o c-bus address used for addressing rom or ram external to the chip. for the recommended external memory configuration two 32kx8 srams are connected to ca0 to ca14. 76 74 70 68 64 62 57 55 51 49 40 38 33 31 27 25 cd0 cd1 cd2 cd3 cd4 cd5 cd6 cd7 cd8 cd9 cd10 cd11 cd12 cd13 cd14 cd15 i/o i/o i/o i/o i/o i/o i/o i/o i/o i/o i/o i/o i/o i/o i/o i/o c-bus data data bus for external rom or ram. for the recommended external memory configuration one 32kx8 sram is connected to cd0 to cd7 and the second sram is connected to cd8 to cd15. 43 ea# i external program access enable must be connected to vdd for regular operation. 47 crd# o c-bus read to external memories this signal must be connected to the rd# input of the external sram. 46 cwr# o c-bus write to external memories this signal must be connected to the wr# input of the external sram. 45 cps# o c-bus select line for external program memory this signal must be connected to the cs# input of the external srams. 44 cds# o c-bus select line for external program memory this signal is not used in isar v1.0 and must be left n.c.
_________________________________________________psb 7110 siemens aktiengesellschaft page 17 general control pin no. symbol in (i) out (o) function 96 95 cm0 cm1 i i clock mode connecting these pins either to vss or vdd will select one of four different options for the generation of the output clock at pin clko 84 reset i reset input power supply pin no. symbol in (i) out (o) function 11 29 35 42 53 59 66 72 77 88 94 vss vss vss vss vss vss vss vss vss vss vss i i i i i i i i i i i ground (common to vdd and vddp) 12 36 60 93 vdd vdd vdd vdd i i i i positive power supply voltage (3.4-3.8 v) 10 28 34 41 52 58 65 71 87 vddp vddp vddp vddp vddp vddp vddp vddp vddp i i i i i i i i i positive power supply voltage (4.5 - 5.5 v) for external interfaces. in isar v1.1 the following vddp pins are changed to vdd (3.6 v): pin no. 34, 41, 52, 58, 65 92 vssa i separate ground (0v) for clock generation unit. 89 vdda i separate positive power supply voltage (3.4 - 3.8 v) for clock generation unit.
_________________________________________________psb 7110 siemens aktiengesellschaft page 18 reserved pins pin no. symbol in (i) out (o) function 1 res. reserved, not to be connected 17 res. reserved, not to be connected 19 res. reserved, not to be connected 78 res. reserved, not to be connected 79 res. reserved, not to be connected 80 res. reserved, not to be connected 81 pu pull up must be connected to vddp accross a 10k pull up resistor. 85 pu pull up must be connected to vddp accross a 10k pull up resistor. 97 res. reserved, not to be connected 98 res. reserved, not to be connected 99 pu pull up must be connected to vddp accross a 10k pull up resistor. 100 pu pull up must be connected to vddp accross a 10k pull up resistor.
_________________________________________________psb 7110 siemens aktiengesellschaft page 19 1.6 clock generation the chip internal clocks are derived from a crystal connected across xtal1 and xtal2 or from an external clock input via pin xtal1. in the isar v1.0 no pll is available. therefore, for the internal dsp clock an external crystal of 30.72 mhz is required and the clock mode pins have to be connected as shown in the figure below, i.e. cm1 = 1 , cm0 = 0 . sram 32k x 16 dd du dcl f s c t r a n s c e i v e r i n t e r f a c e l o g i c ( p n p , i s a ) o r m i c r o c o n t r o l l e r power supply clock generation psb 7110 v1.0 (7110_28) figure 8 clock generation
_________________________________________________psb 7110 siemens aktiengesellschaft page 20 1.7 memory configuration the isar requires external memory with a configuration of 32k x 16 and with 10 ns access time to store operational data and the dsp program which is downloaded after a hardware reset. the figure below shows the recommended configuration with two 32k x 8 srams. since there is a common layout, no additional changes are required when converting to the isar rom version v1.1. (7110_17) figure 9 isar memory interface for both isar versions 1.0 and 1.1 the jumper jp1 has to be set to connect cps# to the cs#-inputs of the srams. to enable compatibility with future versions of the isar, the layout should be designed to enable the different ways to connect the cs#-lines of the srams.
_________________________________________________psb 7110 siemens aktiengesellschaft page 21 2 functional description 2.1 general functions figure 10 depicts the detailed architecture of the psb 7110 isdn data access controller: * one fax/modem engine for v.32 bis, v.17 (14400 bps), including fallback modes * dtmf receiver / transmitter * two v.110 formatter (except during datamodem modulation) * two universal formatters supporting async (itu-t v.14), hdlc and binary modes * external sram interface for program and data memory * communications mailbox with 61 bytes per direction * iom-2 interface for terminal or line-card application v . 1 7 f a x v . 3 2 b i s m o d e m v . 1 1 0 , d t m f t r a n s p a r e n t l o c a l b u s i n t e r f a c e c o m m u n i c a t i o n m a i l b o x 2 x 6 1 b y t e s host interface iom-2 t e s t a n d d i a g n o s t i c s sram 32k x 16 b u f f e r a s y n c , h d l c b i n a r y v . 1 1 0 t r a n s p a r e n t b u f f e r a s y n c , h d l c b i n a r y (7110_21) figure 10 functional blockdiagram of the isdn data access controller
_________________________________________________psb 7110 siemens aktiengesellschaft page 22 2.1.1 clock generation the clock generator provides the internal master clock for the fax/modem engine derived from an input clock or crystal at pins xtal(1:2). other blocks derive their clock signal directly from the iom-2 interface. 2.1.2 interfaces the psb 7110 provides two physical interfaces: the iom-2 interface and the host interface. 2.1.2.1 iom-2 interface the iom-2 interface is a 4-wire interface with two open drain data lines (du and dd), a data clock input (dcl) and a frame sync signal input (fsc), of which the rising edge indicates the start of an iom-2 frame (8 khz). for iom-2 applications the data clock is typically set to twice the data rate. the psb 7110 supports the iom-2 terminal and line-card mode. iom-2 driver the output driver of the dd and du pins is open drain. the output drivers are active for the selected time-slot bits and remain tri-state during the rest of the frame. the control lines fsc and dcl are input. iom-2 timeslots used by the psb 7110 the isar separates iom-2 terminal mode from iom-2 line card mode. in terminal mode, the three channel iom-2 structure is used. in line-card mode, eight iom channels can be programmed with flexible time-slot assignment of the b-channel data. the psb 7110 is able to make extensive use of the iom-2 channels as it is able to access all user data timeslots by programming the timeslot number and bit shift. for detailed information refer to the "iom-2 interface reference guide". 2.1.2.2 host inter face the psb 7110 provides a host interface which consists of an 8-bit multiplexed address/data bus. data transfer is controlled by a chip select signal and read or write control signals. an interrupt line may be activated to indicate to the host that service is required. symbol in (i) out (o) function ad(0:7) i/o address/data bus. transfers addresses and data between the host and the isar psb 7110. rd# i read. this signal indicates a read operation. wr# i write. this signal indicates a write operation. cs# i chip select. ale i address latch enable. a "high" on this line indicates an address on ad(0:7). int# o (od) interrupt request interrupt output line for all mailbox interrupt status. data transfer between the host and the psb 7110 is performed by use of a 61 byte mailbox per direction.
_________________________________________________psb 7110 siemens aktiengesellschaft page 23 2.1.2.3 communications interface the isar provides a communication interface in terms of a 61 byte mailbox per direction, a 16 bit control word and an 8 bit interrupt register. besides that, there is an interrupt mask/status bit (bit 2 of register 75h) and two interrupt acknowledge bits (lsb of address location 50h and 58h respectively). the address map is shown in figure 11 . all other address locations are reserved for further use. 5 0 h 5 8 h 6 0 h 6 1 h i s a r i n t e r r u p t s t a t u s ( i i s ) h o s t w r i t e h o s t r e a d h o s t i n t e r r u p t s t a t u s ( h i s ) i s a r c o n t r o l r e g i s t e r l o w h o s t c o n t r o l r e g i s t e r l o w h o s t c o n t r o l r e g i s t e r h i g h i s a r c o n t r o l r e g i s t e r h i g h a d d r e s s a d 0 . . . a d 7 h i a i i a 4 8 h 4 a h 4 c h m a i l b o x r e a d a d d r e s s m a i l b o x r e a d a d d r e s s m a i l b o x w r i t e a d d r e s s m a i l b o x w r i t e a d d r e s s m a i l b o x i / o d a t a m a i l b o x i / o d a t a m s k s t a bit 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 7 5 h (7110_22) figure 11 host interface registers interrupt mask / status bit (75h write/read) all interrupt sources can be masked by setting the msk-bit to "0", so that no interrupt is indicated to the host. in such a case the status sta-bit can be polled to check whether an interrupt occurred. after reset the interrupt is masked, however, the mask bit affects only the generation of the interrupt, but not the interrupt status bit from being set. when setting the msk-bit, all other bits in reg. 75h are not don't care, but must be set to "0". after reset all interrupts are masked (msk = 0). mailbox the mailbox is implemented as physically two separate 61-byte memory blocks. as for the isar v1.1 (rom version) the mailbox size will be increased, the host can request information about the mailbox size from the isar and so allow for software compatibility with future versions. the mailbox is seen from the host as an i/o device. thus, to read/write a byte from/to the mailbox, the host accesses a single location (mailbox i/o data), which is the same address but physically separate location for read and for write direction. the address is given by an address register directly programmable by the host (mailbox read/write address). this address is autoincremented every time an access by the host to mailbox i/o data is performed. thus, for sequential, fast access, the host only needs to set the start address for the first message byte and all subsequent data bytes can be read/written without reprogramming its address. for random access to the mailbox the host has to reprogram the address register(s).
_________________________________________________psb 7110 siemens aktiengesellschaft page 24 d a t a d a t a r e g . 4 8 r e g . 4 a r e g . 4 c r e g . 4 c host internal bus read address write address 61 byte 61 byte (7110_23) figure 12 mailbox interface communication buffers the isar host interface provides for merging/splitting of two data paths and a test/diagnostics path. each path is buffered both in read- and write-direction. the mailbox is used to access these three buffers. two of them are related to the two isdn b-channels and one channel is mainly used for test purposes. (7110_24) figure 13 communication buffers buffer 1 is used to access the fax/modem engine, a v.110 formatter, a dtmf generator/detector or for transparent access to the iom timeslots. buffer 2 is used to access a v.110 formatter or it provides transparent access to the iom timeslots.
_________________________________________________psb 7110 siemens aktiengesellschaft page 25 buffer 1 and 2 use a sart (synchronous asynchronous receiver transmitter) which supports async, hdlc and binary mode. in async mode, the characters are formatted according to the itu-t v.14 standard by start, parity and stop bits. in hdlc mode, the hdlc bit level functions (flag, crc, zero-bit handling) are performed. binary mode describes a synchronous, transparent mode without formatting. each buffer is controlled by a set of operations which relate to: configuration data status data user data transfer transmit direction for consistent data transfer from the host to the isar, the following protocol should be used. additionally the internal procedure at the isar is shown as well. host isar * read hia-bit, wait until hia=0 (indicates that the host write mailbox registers are available) * polling his-register periodically reset mailbox write address to 0 (only if data is written to the mailbox) * write to host control word and to mailbox * write command to his-register, that causes setting of hia-bit * polling for hia=0 (see first entry) * read his-register, host control word and mailbox * write hia=0 (indicates that the isar has read all mailbox registers, i.e. the host may start a new data transfer) his host interrupt status hia host interrupt acknowledge in transmit direction, these operations are performed by the host by writing the corresponding interrupt status byte into the host interrupt status register (his). additional information may be written to the host control word and to the mailbox if required. the general format of the host control word is for the high byte to contain control, configuration or status information (additionally to the host interrupt status byte) while the low byte is used to indicate the number of valid bytes in the mailbox. once the interrupt status byte as well as control word and mailbox have been written, the host interrupt acknowledge bit (hia) will be set automatically (when writing the host interrupt status) to indicate the new contents to the isar. after isar has completed the evaluation of the mailbox contents, the mailbox is released by the isar when resetting the host interrupt acknowledge bit (hia), so the host may enter new mailbox data.
_________________________________________________psb 7110 siemens aktiengesellschaft page 26 receive direction for data transfer from the isar to the host, the following protocol at the host should be used. additionally the internal procedure at the isar is shown as well. isar host * read iia-bit, wait until iia=0 (indicates that the host can receive another message) * write to isar control word and to mailbox * write command to iis-register, that causes setting of iia-bit and int-line * polling for iia=0 (see first entry) * receives interrupt request from int-line or poll sta bit periodically * read iis-register, isar control word reset mailbox write address to 0 (only if data is read from the mailbox) read mailbox contents * write iia=0 (indicates that the host has read all mailbox registers, i.e. the isar may start a new data transfer) iis isar interrupt status iia isar interrupt acknowledge in receive direction, an interrupt is generated by the isar if enabled (msk=1) or the host can poll the interrupt status in the sta bit if the interrupt is masked (msk=0). the host reads the isar interrupt status register (iis) and the isar control word as well as the mailbox if necessary. after data processing is completed, the mailbox is released by the host when resetting the interrupt acknowledge bit (iia). the most significant byte of the isar control word is used to transfer additional control, configuration or status data. the least significant byte is used to indicate the number of valid bytes in the mailbox.
_________________________________________________psb 7110 siemens aktiengesellschaft page 27 2.2 buffer config uration the mailbox represents the common host interface for all data paths, which are the two b-channel paths and the test diagnostics path. for each data path the read and write direction is buffered with a fifo. the fifo buffers reside in external memory. write buffer read buffer mailbox read-/write buffer host (7110_26) figure 14 buffer configuration buffer control after the host has written a message to the write buffer, the isar will issue a buffer available interrupt to the host if there is still enough free buffer space for another message of the programmed length (i.e. another message may be written to the mailbox). if the host enters messages into the mailbox which exceed the configured message length, the fifo buffer may overflow and data might be lost. if there is no free space available, the host must not write new data to the mailbox. in this case the isar will release a buffer overflow indication and data in the fifo buffers will not be overwritten, i.e. new data get lost. the buffers can be set a priority to determine the sequence of service if several read buffers request for mailbox service simultaneously.
_________________________________________________psb 7110 siemens aktiengesellschaft page 28 2.3 sart configuration the sart (synchronous asynchronous receiver transmitter) can be configured for async character formatting, hdlc bit level formatting and binary mode. i.e. no bit level formatting. 2.3.1 async mode async denotes an asynchronous formatting of data according to itu-t specification v.14. in async mode, the sart adds start, parity and stop bits to each data byte. the following options are programmable: character length: 5,6,7,8 bit no. of stop bits: 1,2 parity: no, odd, even, stick parity overspeed range: 12.5 or 25 % (stop bit deletion: 1 of 8, 1 of 4) the async formatter performs overspeed handling according to v.14. therefore a stop bit may be deleted according to the overspeed range. the async formatter is able to generate a break signal and to detect a break signal of a minimum length of 2m+3 bits of start bit polarity. a special option is included to generate v.42 detection timing. in receive direction the character format is controlled and errors are reported via the mailbox. these errors may be framing error (missing stop bit) and parity error. in receive direction, the character data is extracted, format check is performed and the character data is written to the buffer. if a framing or parity error has been detected or if a break signal has been received, a message can be read from the mailbox by the host even though the programmed message length may not yet be complete, i.e. the new message may be shorter than the programmed length. for configuration setup the host has to distinguish two async modes which do not differ in functionality, but depend on the selected pump mode. 2.3.2 hdlc mode in hdlc mode, the sart generates/handles the hdlc frame formatting. this includes opening and closing flag, crc generation/detection and zero-bit insertion. programmable features are: crc: 16 bit inter frame timefill: '1' or flags bit stream coding: re gular, inverse data underrun operation: abort generation / frame end (crc+flag) generation in transmit direction a frame is started after sart data is available in the transmit fifo buffer. the frame is continued until a frame end mark has been set in a mailbox command. in this case, the hdlc frame is closed by the crc value and a closing flag. in case a buffer underrun occurs, the current hdlc frame is closed either by an abort sequence or by crc and closing flag (programmable). in receive direction, hdlc frames exceeding the programmed message length are transferred to/from the buffer in data blocks of the configured message length. a message of reduced length may be transferred if a frame start, frame end or error condition is detected. in this case the control word contains the result of the crc check, verification of integer number of bytes and check of frame end condition.
_________________________________________________psb 7110 siemens aktiengesellschaft page 29 2.3.3 binary mode in binary mode no character formatting is performed. octets are transferred with the least significant bit or most significant bit transferred first. programmable features are: idle character on data underrun bit swapping (lsb/msb first) in transmit direction, data from the transmit buffer is transmitted with the lsb or msb first. in case of data underrun, i.e. if there's no more data in the transmit buffer, a programmable byte or the last data byte is continuously transmitted. in receive direction, the data stream is received in octets. their contents is transferred to the receive buffer . 2.4 pump configuration pump in general describes the additional formatting of the sart data which is then forwarded to the iom-2 interface. the pump options are: fax modulations datamodem modulations halfduplex modulations v.110 dtmf dtmf transmission bypass (transparent data) all pump modes except v.110 and bypass are only available in channel 1. both modes, v.110 and bypass, are available in channel 1 and 2. it must be noted that v.110 operation is not possible in channel 2, if channel 1 is operating with datamodem modulations (fullduplex modulations). however v.110 can be operated in one channel, if the other channel is configured to any other mode except datamodem modulations, which is fax modulations, v.110, dtmf, dtmf transmission, bypass or halfduplex modulations (without option of fullduplex modulations). the host must ensure that the pump is not configured to datamodem modulations and v.110 simultaneously, which would cause malfunctions for both channels. in dtmf mode the pump is transfering data between the sart unit and the iom-2 interface transparently (like bypass mode) while a dtmf receiver is active to detect dtmf signals. for transmission of dtmf tones the pump must be reconfigured to "dtmf transmission".
_________________________________________________psb 7110 siemens aktiengesellschaft page 30 2.4.1 fax modulations the mode fax modulations allows modulation up to v.17 (14400 bps). programmable parameters are: enabling/disabling of answer/calling tone transmitter output attenuation modulation scheme (v.17, v.29, v.27ter, v.21 channel 2) set by control commands 2.4.2 datamodem modulations the mode datamodem modulations allows modulation up to v.32 bis (14400 bps). programmable parameters are: enabling/disabling of answer/calling tone transmitter output attenuation automode (eia/tia pn-2330) or dedicated mode automode options: fallback options guard tone options mode permission dedicated mode options: fallback options guard tone options modulation mode (v.32bis, v.32, v.23, bell 202, bell 212, v.22 bis, v.22, bell 103, v.21 ch2, v.21) 2.4.3 halfduplex modulations the halfduplex modulations allow modulation up to v.17 (14400 bps). programmable parameters are: enabling/disabling of receive/transmit direction enabling/disabling of echo protector tone transmitter output attenuation modulation scheme (v.17, v.29, v.27ter, v.21) 2.4.4 v.110 the v.110 mode allows the framing of sart data according to the v.110 protocol. the programmable features are: frame format/data rate e-, x-, s-bit control transmitter flow control (x-bits) remote dte status detection delay of synchronisation
_________________________________________________psb 7110 siemens aktiengesellschaft page 31 in transmit direction, the v.110 frame is combined with sart data and the state of e-, x- and s-bits. transmission of the last data byte in the mailbox is indicated to the host (buffer empty condition), which may set control bits. flow control by means of the x-bits is supported, which means that data transfer to the sart unit is stopped if indicated by the remote side. in receive direction, frame synchronization is monitored while the number of frames for synchronisation (normally 1) is programmable. the d-bits are forwarded to the sart and e-, x- and s- bits are forwarded to the host as status events any time they change their state. status conditions of the remote dte can be detected and indicated to the host. 2.4.5 dtmf dtmf mode allows transparent data transfer between sart unit and data pump while a dtmf detector is active, which indicates received dtmf tones to the host. a programmable feature is the signal rejection level below which a dtmf tone will not be detected by the pump. 2.4.6 dtmf transmission in transmit direction, a dtmf tone can be programmed which is output on the timeslot. in this mode no data is transfered between sart unit and iom-2 interface. however, during normal operation (dtmf mode) the pump only needs to be configured to dtmf transmission for the duration of the transmitted dtmf digit, right after that the pump can be reconfigured to normal operation mode. the transmitter output attenuation is programmable. 2.4.7 bypass mode the bypass mode allows the transfer of sart data without additional treatment. in transmit direction, the data from the sart it transfered to the iom timeslot. octet data (binary mode) can be octet aligned to the iom-2 timeslot if programmed (8-bit timeslot length). in receive direction, the data from the iom-2 timeslot is directly transfered to the sart. 2.5 iom-2 configuration the iom-2 configurations are separate for each datapath. via datapath 1 and 2, any timeslot for the output of pump data can be selected. the following programmable functions are available for each datapath : start of timeslot length of timeslot (8 or 16 bit) switching of du/dd lines coding (a-law, m -law or 16-bit linear) it must be noted that the programmed timeslots for both datapaths must not overlap.
_________________________________________________psb 7110 siemens aktiengesellschaft page 32 3 operational description 3.1 general information 3.1.1 configuration after reset the proceeding after hardware reset is shown in figure 15. the dsp program must be downloaded to the external memory of the isar v1.0. as further isar versions will not require the program download, the isar version should be checked first before the download mechanism is started. after download is finished, an automatic selftest is started for memory errors and to check if the clocks from the iom-2 interface are present. the result of this selftest should be requested by the host. before configuration for data transmission/reception is done, the version number of the dsp software should be verified to check which functionality is available. reset check isar version dsp program download necessary? download program to external memory configure data pump configure iom-2 interface configure sart request for sw version number normal operation mode configuration complete download complete no yes done start with data transmission / reception see 3.10 dsp program download see 3.6.1 pump configuration setup see 3.8.1 iom-2 configuration setup see 3.4 sart configuration setup see 3.9.3 software version request isar selftest is performed automatically request for isar selftest result see 3.9.6 request selftest result configure buffer see 3.2.1 buffer configuration setup figure 15 initialisation procedure
_________________________________________________psb 7110 siemens aktiengesellschaft page 33 to establish a link on a data path, the four functional blocks, buffer, sart, data pump and iom-2 interface must be configured first. since the configuration of the data pump will reset the whole data path except buffer configuration, the pump should be configured right after buffer configuration. it is recommended to follow this sequence to provide for proper operation. the table below shows the configuration parameters for each of the four blocks and the reference to the corresponding parameter setting. detailed information about the individual parameters is provided with the corresponding configuration setup messages. functional block configuration parameter parameter setting buffer buffer base priority bbp maximum message length mml data pump pump mode (fax, datamodem, halfduplex modulation, v.110, dtmf, dtmf transmission or bypass) pmod originating / answering mode oam transmitter output attenuation toa calling and answer tones atn, ctn echo protector tone ept guard tone selection gts modulation scheme v23, v23r, ... automode operation amod data rate (v.110) vdr flow control (v.110) fct rejection level (dtmf) rel iom-2 interface iom-2 access enable/disable iom time slot position rtso, rcs ttso, tcs time slot length tsl switching of du/dd lines txd, rxd coding (pcm a-la w, m -law) cod rate conversion rcv sart sart mode (v.14, hdlc, binary, fsk v.14) smode receive / transmit channel disable (halfduplex modulation) hdmc hdlc formatting (hdlc regular/inverted, interframe fill, fcs length, enable/disable fcs, data underrun operation) hio iff flen edf, duo v.14/fsk v.14 formatting (overspeed range, stop bits, parity bits, character size, buffer flush timeout) ovsp, snp, eop, edp nsb, chs, bft binary formatting (data underrun operation, bit swapping, data underrun fillword) duo bsw dufw
_________________________________________________psb 7110 siemens aktiengesellschaft page 34 3.1.2 message transfer from host to isar the procedure to write a message to the isar mailbox is shown in figure 16. the mechanism to access the isar mailbox is the same for all messages, which are: configuration setup configuration request status request control commands control commands along with transmit data write message to isar mailbox read hia-bit mailbox access permitted (hia=0) ? write to ctrl msb write to ctrl lsb (= number n of parameters) no yes write parameter to mailbox another parameter necessary (n>0) ? write host interrupt status byte to his-regsiter (adr. 50h) no yes done n := n - 1 indicates the new message in the mailbox to the isar reset write address register to 0 figure 16 write message transfer
_________________________________________________psb 7110 siemens aktiengesellschaft page 35 when a message is written to the mailbox, the isar will transfer the whole message to the destination buffer which is indicated in the host interrupt status byte (his). during that time another message must not be entered by the host, however due to the mailbox structure, the message transfer is performed rather fast and will not delay any host access. therefore, before any access to the mailbox is done, the host should read the host interrupt acknowledge bit (hia), to verify that the registers are available again (hia=0) and a new message may be written to the mailbox. the control registers (ctrl msb and lsb) should be written first, where the ctrl lsb contains the total number of bytes which will be entered to the mailbox. before any data is written to the mailbox (address 4ch), the write pointer (address 4ah) must be reset to 0. after a byte is written to the mailbox, the write address pointer is autoincremented and doesn't need to be reprogrammed. this allows for fast access to the mailbox. if there are successive messages with the same mailbox contents, the mailbox data does not need to be written again, as this data is still available in the mailbox memory from the previous message. it allows the host to flexibly reprogram the write pointer and its respective memory location only for those mailbox contents which are different from the previous message. important note: it is important to note that the his byte must be entered as the very last byte of the message as this will indicate the new register and mailbox contents to the isar. an access to the his register will terminate the message transfer and automatically set the hia bit which is reset again by the isar as soon as new data can be entered to the mailbox.
_________________________________________________psb 7110 siemens aktiengesellschaft page 36 3.1.3 message transfer from isar to host the procedure to read a message from the isar mailbox is shown in figure 17. the mechanism to access the isar mailbox is the same for all messages, which are: configuration response (initiated by configuration request message) status response (initiated by status request message) status events status events along with receive data read message from isar mailbox int received from isar done read iis register read isar ctrl msb read isar ctrl - lsb (= number n of bytes in the mailbox) another byte to be read from the mailbox (n>0) ? no yes read one byte from the mailbox release mailbox for next data transfer (set iia=0) n := n - 1 indicates to the isar that the whole message has been read from the mailbox reset read address register to 0 check sta bit figure 17 read message transfer
_________________________________________________psb 7110 siemens aktiengesellschaft page 37 if the isar has a message available in the mailbox to be read by the host, it will activate the int-line. to ensure, the interrupt line was not activated due to a hardware malfunction, the interrupt status bit sta should be checked. for the message transfer the isar interrupt status register (iis) should be read first. it defines the type of message and indicates the source where the message was initiated. then the ctrl msb and lsb are read by the host, where the lsb indicates the total number of bytes which are available in the mailbox . before data is read from the mailbox (address 4ch), the read pointer (address 48h) must be reset to 0 to read the data starting with the first byte in sequence. for each read access to the mailbox the read address pointer is autoincremented and does not need to be reprogrammed by the host. this allows for fast access to the mailbox. important note: it is important to note that the iia bit must be reset as the very last register access of the message, as this will indicate to the isar that the message has been completely read. the mailbox is released and may be filled with new contents. it is not necessary to read the mailbox if its content is not required by the host, e.g. if data is not valid. the host can discard the contents by just writing the iia bit as this will release the whole mailbox. a response message is always initiated by the host releasing a request message to the isar (see figure 18). the other messages are initiated by the state machine residing on the host side (messages from host to isar) or residing on the isar (messages from isar to host). figure 18 message directions the isar releases an interrupt request to the host to indicate that a message must be read from the mailbox. the host can mask the interrupt source (bit msk=0) to avoid any interrupt state being indicated to the host by activating the int-line. however, the mask bit affects only the generation of the interrupt, but not the interrupt status from being set (sta bit) which can be polled by the host.
_________________________________________________psb 7110 siemens aktiengesellschaft page 38 3.1.4 message overview the data path for the b-channel consists of fifo buffer, sart, data pump and iom-2 interface. transmit/receive data and configuration, status and control information is exchanged between the host and the isar by a set of messages. buffer configuration configuration setup host t isar the host sets the priority at which each buffer's request will be serviced by the host and the message length at which data will be transfered between the host and the mailbox. configuration request host t isar the host can request the current configuration, i.e. parameter settings such as base priority and message length. configuration response host isar after a configuration request by the host, the isar will respond with the current parameter settings. control commands host t isar the host sends control commands to the isar in order to clear or reset buffers. buffer status status request host t isar the host can request the current status of the buffers, i.e. number of messages and free locations in the buffers. two different types of status responses can be requested. status response host isar after a status request by the host, the isar will respond with the current status information. status events host isar during data transfer the isar indicates to the host, whether the buffer is able to store another message, i.e. if new data can be entered.
_________________________________________________psb 7110 siemens aktiengesellschaft page 39 sart messages are defined for each of the three modes (hdlc, async and binary). sart configuration configuration setup host t isar the host configures the mode (binary, hdlc, async) for the sart and sets further parameters depending on the mode. sart data status events with receive data host isar during data reception the isar indicates to the host, when error conditions or mode specific events occur, e.g. when the end of an hdlc frame was detected. control commands with transmit data host t isar during data transmission the host controls mode specific functions e.g. the hdlc framing (frame start, frame end) and the generation of break signals in async mode. pump messages are defined for all of the seven pump modes (fax modulations, datamodem modulations, halfduplex modulations, v.110, dtmf, dtmf transmission and bypass). pump configuration configuration setup host t isar the host configures the mode (fax modulations, datamodem modulations, halfduplex modulations, v.110, dtmf, dtmf transmission or bypass) for the data pump and sets further parameters depending on the mode. control commands host t isar the host sends control commands to the isar in order to enable/disable the pump and to set mode specific control commands (e.g. dtmf tones to be generated).
_________________________________________________psb 7110 siemens aktiengesellschaft page 40 pump status status request host t isar the host can request the current configuration of the data pump (pump mode, originating/answering mode). status response host isar after a configuration request by the host, the isar will respond with the current parameter settings. status events host isar the isar indicates to the host mode specific events that occur during data transfer, such as dtmf tones received or control bit change in v.110. iom-2 configuration configuration setup host t isar the host configures the length and position of the iom-2 timeslots. configuration request host t isar the host can request the current iom-2 configuration, i.e. the current setting of timeslot-length and position. configuration response host isar after a configuration request by the host, the isar will respond with the current configuration setting. control comman ds host t isar the host sends control commands to the isar for iom-2 control during normal operation. additional messages are available within the test/diagnostics path for general configuration and for dsp program download
_________________________________________________psb 7110 siemens aktiengesellschaft page 41 3.1.5 message structure the messages to transfer configuration, status and control information between the host and isar are described in detail in the next chapters. depending on the kind of message, the structure and message length may be different. all messages consist of: interrupt status byte (his or iis) control register msb (ctrl msb) control register lsb (ctrl lsb) for some messages a certain number of additional bytes must be written to/read from the mailbox: 1st parameter 2nd parameter : n-th parameter 5 0 h 5 8 h 6 0 h 6 1 h i s a r i n t e r r u p t s t a t u s ( i i s ) h o s t w r i t e h o s t r e a d h o s t i n t e r r u p t s t a t u s ( h i s ) i s a r c o n t r o l r e g i s t e r l o w h o s t c o n t r o l r e g i s t e r l o w h o s t c o n t r o l r e g i s t e r h i g h i s a r c o n t r o l r e g i s t e r h i g h a d d r e s s a d 0 . . . a d 7 h i a i i a 4 8 h 4 a h 4 c h m a i l b o x r e a d a d d r e s s m a i l b o x r e a d a d d r e s s m a i l b o x w r i t e a d d r e s s m a i l b o x w r i t e a d d r e s s m a i l b o x i / o d a t a m a i l b o x i / o d a t a m s k s t a bit 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 7 5 h i n t e r r u p t s t a t u s b y t e ( h i s / i i s ) c o n t r o l r e g i s t e r m s b ( c t r l m s b ) c o n t r o l r e g i s t e r l s b ( c t r l l s b ) 1 s t p a r a m e t e r 2 n d p a r a m e t e r n - t h p a r a m e t e r figure 19 message transfer
_________________________________________________psb 7110 siemens aktiengesellschaft page 42 3.1.5.1 interrupt status byte the interrupt status byte has a structure that defines the type of message, i.e. it contains information to which buffer the message is related to, the kind of message and to which functional block of the isar the message is related to: 7 6 5 4 3 2 1 0 his / iis dps msc mds dps ... datapath selection one of the three data paths (0, 1 or 2) of the isar is selected. msc ... message coding msc defines the type of command (e.g. configuration request, configuration response, status event, control command, ...) to perform a certain function. mds ... message destination/source selects one of the four functional blocks on the isar (buffer, sart, data pump and iom-2) to which the message is sent (host ? isar) or from which a message is originated (isar ? host). the coding for the his and iis registers are listed below. it should be noted, that not all combinations of buffer selection (dps), message coding (msc) and message destination/source (mds) are available at the programming interface. it is important to note that the coding for test/diagnostics messages (dps=00) does not conform to the above shown structure of msc and mds. instead these bits fully specify an individual message function. some of the test/diagnostics messages are only used for dsp download and are not valid after regular operation has started (see 3.10 dsp program download)
_________________________________________________psb 7110 siemens aktiengesellschaft page 43 host interrupt status byte (his host ? ? isar) the structure for the his byte is shown below. it should be noted, that not all combinations of buffer selection, message coding and message destination are available at the programming interface. regular operation (b-channel paths 1 and 2): 7 6 5 4 3 2 1 0 datapath selection (dps) 0 1 path 1 1 0 path 2 message coding (msc) 1 0 0 0 0 0 control command and transmit data 0 0 0 1 request for configuration 0 0 1 1 request for status 1 0 0 1 configuration setup 1 0 1 0 control command message destination /source (mds) 0 0 command for buffer 0 1 command for sart 1 0 command for pump 1 1 command for iom-2 test/diagnostics operation (buffer 0): some of the message codings related to the dsp program download procedure (see table below) can only be used before the dsp program has been started and are not valid after regular operation has started. 7 6 5 4 3 2 1 0 datapath selection (dps) 0 0 buffer 0 message coding (msc) 1 1 1 1 0 0 configuration setup 1 1 1 1 1 0 control command 0 1 1 1 0 1 status request 1 0 0 1 1 1 mailbox contains general configuration (wait state setting) 1 0 0 1 0 1 mailbox contains general configuration (timer interrupt on/off) 0 0 0 1 0 1 request selftest result 0 0 0 1 0 1 request for software version number the following message codings are only valid before the dsp program has been started: 0 1 0 1 0 0 request for chip version number 0 0 0 0 1 0 transfer of d-key 0 1 1 1 1 0 transfer of program data 0 0 1 0 0 0 start of dsp program
_________________________________________________psb 7110 siemens aktiengesellschaft page 44 isar interrupt status byte (iis) the structure for the iis byte is shown below. also for iis not all combinations of buffer selection, message coding and message destination are available at the programming interface. one message does not conform to the described structure of dps, msc and mds. it has a general code (iis=0), which is used for normal operation and not for test/diagnostics functions. regular operation (b-channel paths buffer 1 and 2): 7 6 5 4 3 2 1 0 request for data 0 0 0 0 0 0 0 0 indication for buffer available (general code) 7 6 5 4 3 2 1 0 datapath selection (dps) 0 1 path 1 1 0 path 2 message coding (msc) 1 0 0 0 0 0 mailbox contains sart status event and receive data 1 0 0 1 mailbox contains configuration data 1 0 1 0 mailbox contains status event 1 0 1 1 mailbox contains status information message destination/ source (mds) 0 0 indication from buffer 0 1 indication from sart 1 0 indication from pump 1 1 indication from iom-2 test/diagnostics operation (buffer 0): some of the message codings related to the dsp program download procedure (see table below) can only be used before the dsp program has been started and are not valid after regular operation has started. 7 6 5 4 3 2 1 0 datapath selection (dps) 0 0 buffer 0 message coding (msc) 1 1 1 1 0 1 status response 1 1 1 1 1 0 status event 1 0 1 0 1 0 timer interrupt request 1 1 1 1 1 1 invalid message received 1 0 0 1 0 1 selftest response 1 0 0 1 0 1 software version number response the following message codings are only valid before the dsp program has been started: 0 1 0 1 0 1 chip version number response 0 0 0 0 1 1 response for transfer of d-key 0 1 1 1 1 1 response for transfer of program data 0 0 1 0 0 1 response for start of dsp program
_________________________________________________psb 7110 siemens aktiengesellschaft page 45 3.1.5.2 control registers and parameters the most significant byte of the control register (ctrl msb) contains configuration, status or control information which depends on the type of message. c t r l m s b c t r l l s b 1 s t p a r a m e t e r 2 n d p a r a m e t e r n - t h p a r a m e t e r n u m b e r o f p a r a m e t e r s n c o n f i g , s t a t u s o r c o n t r o l i n f o r m a t i o n m a i l b o x i / o d a t a m a i l b o x i / o d a t a m a i l b o x i / o d a t a figure 20 control registers and parameters the least significant byte of the control register (ctrl lsb) is used to indicate the number of bytes transfered via the mailbox (mailbox i/o data). these mailbox data may contain additional configuration, status or control information as well as receive/transmit data (figure 20). important note: isar v1.1 (rom version) will be software compatible to the isar v1.0 (download version), however it should be noted that the length of some messages may differ in a way, that additional parameters may be provided. the message parameters and their sequence within the message specified herein is identical, but a higher value of the ctrl lsb may indicate that further parameters are provided through the mailbox. for some of the messages no additional data is written to/read from the mailbox, in this case the ctrl lsb is set to 0. the structure of the parameters is depending on the type of message being transfered and has no fixed format. therefore it is described with each individual message.
_________________________________________________psb 7110 siemens aktiengesellschaft page 46 3.2 buffer configuration 3.2.1 buffer configuration setup (host ? ? isar) 7 6 5 4 3 2 1 0 dps msc mds his 0 0 15 14 13 12 11 10 9 8 ctrl msb 0 0 0 0 0 bbp 7 6 5 4 3 2 1 0 ctrl lsb 1 7 6 5 4 3 2 1 0 1. parameter mml dps ... datapath selection 00: path 0 01: path 1 10: path 2 msc ... message coding the message coding is different for datapath 0 and datapath 1, 2. 1111: configuration setup for data path 0 (dps=00) 1001: configuration setup for data path 1 or 2 (dps=01 or 10) bbp ... buffer base priority 000: priority is not changed by the configuration command 001: change base priority to 1 (lowest priority) : : 111: change base priority to 7 (highest priority) reset value: bbp = 4 datapaths 1 and 2 (dps = 01, 10) bbp = 5 datapath 0 (dps = 00) mml ... maximum message length the maximum message length is limited to 61 byte. the buffer priority determines the sequence of service if more than one read buffer request for mailbox service at the same time. in such a case the buffer with highest priority is served first and the priority of all pending buffers is increased by one. after being served, the priority of the serviced buffer is reset to its base value, which is selected by the above given configuration command. so a buffer with a higher base priority will be served more often than a buffer with a lower base priority, moreover, the higher the difference of two priority values the more often the one buffer will be serviced first. if the additional value (maximum message length) is omitted (ctrl lsb = 0), only the base priority is changed. in this way the buffer base priority can be reconfigured to a different value during normal operation without any loss of data consistency. by changing the base priority, the current priority is reset to the new base value. for highest throughput and best internal performance it is recommended to use the highest value for mml.
_________________________________________________psb 7110 siemens aktiengesellschaft page 47 3.2.2 buffer configuration request (host ? ? isar) the current configuration can be requested by the host. the request is fully specified by the host interrupt status register (his), i.e. the mailbox control registers are not used (set to 0) and no parameters are required. 7 6 5 4 3 2 1 0 dps msc mds his 0 0 15 14 13 12 11 10 9 8 ctrl msb 0 7 6 5 4 3 2 1 0 ctrl lsb 0 dps ... datapath selection 00: path 0 01: path 1 10: path 2 msc ... message coding the message coding is different for datapath 0 and datapath 1, 2. 0111: configuration request for datapath 0 (dps =00) 0001: configuration request for datapath 1 or 2 (dps=01 or 10)
_________________________________________________psb 7110 siemens aktiengesellschaft page 48 3.2.3 buffer configuration response (isar ? ? host) the isar provides the configuration data, which was requested by the host, via the mailbox. the coding is similar to the configuration setup. 7 6 5 4 3 2 1 0 dps msc mds iis 0 0 15 14 13 12 11 10 9 8 ctrl msb - - - - - bbp 7 6 5 4 3 2 1 0 ctrl lsb 2 7 6 5 4 3 2 1 0 1. parameter mml 7 6 5 4 3 2 1 0 2. parameter mpl dsp ... datapath selection 00: path 0 01: path 1 10: path 2 msc ... message coding the message coding is different for datapath 0 and datapath 1, 2. 1111: configuration response from datapath 0 (dps=00) 1001: configuration response from datapath 1 or 2 (dps=01 or 10) bbp ... current buffer base priority 000: not used 001: base priority of 1 (lowest priority) : : 111: base priority of 7 (highest priority) mml ... currently selected maximum message length mml contains the maximum message length that has been configured by the host. if this value has not been programmed by the host, mml contains the reset value for the maximum possible message length. mpl ... maximum possible message length mpl contains the maximum possible message length that can be configured. mpl is 29 for data path 0 and 61 for data paths 1 and 2. in receive direction the isar gathers all received data words from the sart up to the selected message length, before the message is passed to the mailbox. messages of reduced length may be passed on certain events such like error conditions or hdlc frame end (see 3.5.1 sart status events with receive data). in transmit direction it's the responsibility of the host that transmit messages do not exceed the selected message length, to avoid a buffer overflow and loss of data.
_________________________________________________psb 7110 siemens aktiengesellschaft page 49 if mml exceeds mpl in the configuration setup message (see 3.2.1), mml is internally limited to mpl. therefore it is recommended to issue a buffer configuration request message to verify the currently selected and the maximum possible message length. moreover, this enables the software to automatically adapt to the hardware platform, as the isar v1.1 (rom version) will provide enlarged mailbox and fifo buffers, which will also increase the maximum possible message length that can be read with mpl.
_________________________________________________psb 7110 siemens aktiengesellschaft page 50 3.2.4 buffer control command (host ? ? isar) the io-buffer control commands are interpreted immediately after being received by the isar. 7 6 5 4 3 2 1 0 dps msc mds his 15 14 13 12 11 10 9 8 ctrl msb 0 0 0 0 0 0 crb 7 6 5 4 3 2 1 0 ctrl lsb 0 dps ... datapath selection 00: path 0 01: path 1 10: path 2 msc ... message coding the message coding is different for datapath 0 and datapath 1, 2. 1111: control command for datapath 0 (dps=00) 1010: control command for datapath 1 or 2 (dps=01 or 10) mds ... message destination/source the destination coding is different for datapath 0 and datapath 1, 2. 10: message is addressed to buffer (for dps=00) 00: message is addressed to buffer (for dps=01 or 10) crb ... clear / reset buffers 00: clear receive buffer 01: clear transmit buffer 1x: reset read and write buffers to their initial values (note: bit8 is don't care) the buffer clear commands do not change the settings of the base priority or the message length. the reset command clears both, read and write buffers, and reset them to their initial factory settings.
_________________________________________________psb 7110 siemens aktiengesellschaft page 51 3.3 buffer status 3.3.1 buffer status request (host ? ? isar) the request is fully specified by the host interrupt status register (his) and the mailbox control registers, i.e. additional parameters are not used. the io-buffer status request is serviced immediately after being received by the isar. 7 6 5 4 3 2 1 0 dps msc mds his 15 14 13 12 11 10 9 8 ctrl msb sts 7 6 5 4 3 2 1 0 ctrl lsb 0 dps ... datapath selection 00: path 0 01: path 1 10: path 2 msc ... message coding the message coding is different for datapath 0 and datapath 1, 2. 0111: status request for datapath 0 (dps=00) 0011: status request for datapath 1 or 2 (dps=01 or 10) mds ... message destination/source the destination coding is different for datapath 0 and datapath 1, 2. 01: message is addressed to buffer (for dps=00) 00: message is addressed to buffer (for dps=01 or 10) sts ... status type select the status request will cause the generation of ... 0: ... a status response with additional information about the buffers 1 0: ... a buffer available indication the status response with additional information about messages and free locations in the receive and transmit buffers is described in chapter 3.3.2. the second option allows the host to force the generation of a buffer available indication as specified in chapter 3.3.3. however there is a slight difference in the functionality of the resulting indication message: a buffer available indication that is initiated by the isar, only contains information about those buffers where a transition from "not enough free space" to "enough free space for another message" occurs. all buffers that are not serviced by that time, will not be indicated in a following buffer available indication that results from the status transition of a different buffer. however, a status request with sts 1 0 forces the isar to generate a buffer available indication for the transmit buffer of the selected datapath (specified in the his register), even if there is no state transition for that buffer. this command is useful to force a first data request message from the isar after a datapath is fully configured, although the first request message is automatically generated after sart configuration.
_________________________________________________psb 7110 siemens aktiengesellschaft page 52 3.3.2 buffer status response (isar ? ? host) the isar returns status information about the buffers if requested by the host (see 3.2.1). 7 6 5 4 3 2 1 0 dps msc mds iis 15 14 13 12 11 10 9 8 ctrl msb - - - - rdm3 rdm2 rdm1 rdm0 7 6 5 4 3 2 1 0 ctrl lsb 6 7 6 5 4 3 2 1 0 1. parameter nbrl 7 6 5 4 3 2 1 0 2. parameter nbrm 7 6 5 4 3 2 1 0 3. parameter nmr 7 6 5 4 3 2 1 0 4. parameter nbtl 7 6 5 4 3 2 1 0 5. parameter nbtm 7 6 5 4 3 2 1 0 6. parameter nmt dps ... datapath selection 00: path 0 01: path 1 10: path 2 msc ... message coding the message coding is different for datapath 0 and datapath 1, 2. 1111: status response from datapath 0 (dps=00) 1011: status response from datapath 1 or 2 (dps=01 or 10) mds ... message destination/source the source coding is different for datapath 0 and datapath 1, 2. 01: message is originated from the buffer (for dps=00) 00: message is originated from the buffer (for dps=01 or 10) rdm3, rdm2, rdm1, rdm0 ... request for next data message from channel 3, 2, 1 or 0 if rdm0, rdm1 or rdm2 is set, the corresponding channel 0, 1 or 2 requests for a new data message from the host, i.e. there is enough free buffer space for another message. rdm3 is always set to "1". it is currently not supported but reserved for further use. nbrl ... number of free bytes in the receive buffer - lsb nbrm ... number of free bytes in the receive buffer - msb
_________________________________________________psb 7110 siemens aktiengesellschaft page 53 nmr ... number of messages in the receive buffer nbtl ... number of free bytes in the transmit buffer - lsb nbtm ... number of free bytes in the transmit buffer - msb nmt ... number of messages in the transmit buffer the control register contains additional information about all buffers that currently have buffer space available for a new message. the information is similar as provided in the general status event message which is a kind of "indication for buffer available" (see 3.3.3.2). however, here the current status of all buffers is indicated regardless whether there is a state transition in the individual buffer. detailed information about free locations in receive and transmit buffers and about the number of messages currently stored in the buffers are available from the mailbox. these parameters only refer to the buffer which is associated to the selected data path in iis register. comment: as the his register and the control word are internally also written to the buffers, a message of length n will always require (n+3) buffer locations.
_________________________________________________psb 7110 siemens aktiengesellschaft page 54 3.3.3 buffer status event (isar ? ? host) there are two message types for status events from the buffer: status event that is related to a certain buffer (see 3.3.3.1) indication for buffer available - general code for all buffers (see 3.3.3.2) 3.3.3.1 buffer specific status event (isar ? ? host) 7 6 5 4 3 2 1 0 dps msc mds iis 15 14 13 12 11 10 9 8 ctrl msb stev 7 6 5 4 3 2 1 0 ctrl lsb 0 dps ... datapath selection 00: path 0 01: path 1 10: path 2 msc ... message coding the message coding is different for datapath 0 and datapath 1, 2. 1111: status event from datapath 0 (dps=00) 1010: status event from datapath 1 or 2 (dps=01 or 10) mds ... message destination/source the source coding is different for datapath 0 and datapath 1, 2. 10: message is or iginated from the buffer (for dps=00) 00: message is originated from the buffer (for dps=01 or 10) stev ... status event code 1fh: transmit buffer overflow 2fh: receive buffer overflow
_________________________________________________psb 7110 siemens aktiengesellschaft page 55 3.3.3.2 buffer general status event (isar ? ? host) if a data path is online and the associated write buffer has space available for a new message, the status event message ?buffer available? is generated to request new data from the host. the io-buffer control unit generates write buffer status event messages that cover information about all buffers, thus the iis register contains a general code (iis = 0). in this way the load for transfering messages is decreased significantly, as a single message may request data for more than one datapath. it is the responsibility of the host to dispatch rdmx to the controller routines of the relevant datapath. 7 6 5 4 3 2 1 0 dps msc mds iis 0 0 0 0 0 0 0 0 15 14 13 12 11 10 9 8 ctrl msb 0 0 0 0 rdm3 rdm2 rdm1 rdm0 7 6 5 4 3 2 1 0 ctrl lsb 0 rdm3, rdm2, rdm1, rdm0 ... request for next data message from channel 2, 1 or 0 if bit rdm2, rdm1 or rdm0 is set, the corresponding channel 0, 1 or 2 requests for a new data message from the host. rdm3 is currently not supported but reserved for further use. a status event is generated by the control unit and indicated to the host when at least one of the write buffers changes its state from "not enough free space" to "enough free space for another data message", or when at least one of the write buffers has still enough free space for another message immediately after a new message was written into this buffer. only when either of these two states is met, the status event message is generated. if the request is not serviced by the host, the isar will not generate a new status event message to request data for that path. it should be noticed that the corresponding bit for that buffer remains not set in the control register each time another buffer generates an interrupt to request new data. however a status request message (see 3.3.1) can force the generation of an indication for buffer available for a certain buffer. the general proceeding for data transfer from the host to the transmit buffer would be: after reset the isar will release an initial status event mes sage with rdm0=rdm1=rdm2=rdm3=1 the host configures buffer, data pump, iom-2 interface and sart the host writes the first message to the buffer (buffer is empty after reset) if the remaining buffer space is greater than the programmed message length, there will be an immediate interrupt to the host, who in turn can transfer the next message. if the remaining buffer space is smaller than the programmed message length, there will be no interrupt to the host until data is transmitted from the buffer and enough space is available to accept one complete message. if there is a request for message to the host and the host has no new message to send, the host should store the request information, so for new data it can immediately continue with transfering it to the buffer. the ho st can force the generation of an indication for buffer available for a certain buffer (see 3.3.1).
_________________________________________________psb 7110 siemens aktiengesellschaft page 56 3.4 sart configuration depending on the sart mode (hdlc, async or binary) the message requires a specific coding, which is described in the following three chapters. for sart configuration all parameters have to be set for the corresponding sart mode even though a single parameter may not be different from the previous setting. important note: after configuration of the pump, the configuration information of the sart gets lost, therefore the sart unit must be configured after the pump configuration. 3.4.1 sart configuration setup - hdlc (host ? ? isar) 7 6 5 4 3 2 1 0 dps msc mds his 1 0 0 1 0 1 15 14 13 12 11 10 9 8 ctrl msb hdmc 0 0 smode 7 6 5 4 3 2 1 0 ctrl lsb 1 7 6 5 4 3 2 1 0 1. parameter 0 0 0 hio iff flen edf duo dps ... datapath selection 01: path 1 10: path 2 hdmc ... halfduplex mode configuration 00: receive and transmit channel are enabled (default) 01: receive channel is disabled 10: transmit channel is disabled 11: not used in halfduplex mode the pump would transfer idle bits in the direction that is currently not in use, so the corresponding receive or transmit channel can be selectively disabled to reduce the interrupt load for not valid data. for all other pump modes except halfduplex mode, hdmc must be set to its default value 00. smode ... sart mode 0000: disable sart 0010: v.14 mode 0011: hdlc mode 0100: binary mode 0101: fsk v.14 mode all other codes reserved
_________________________________________________psb 7110 siemens aktiengesellschaft page 57 hio ... hdlc input / output 0: regular 1: inverted "inverted" describes a mode where all bits are changed from "0" to "1" and from "1" to "0" after hdlc formatting. iff ... interframe fill 0: flags 1: "1" flen ... fcs length 0: 16 bit fcs 1: 32 bit fcs (not implemented in isar v1.0) edf ... enable / disable fcs 0: enable fcs (regular hdlc operation) 1: disable fcs this refers to fcs generation in transmit direction and fcs checking in receive direction. duo ... data underrun operation for data underrun in tx direction ... 0: ... abort is generated (default) 1: ... frame end (fcs and final flag) is generated
_________________________________________________psb 7110 siemens aktiengesellschaft page 58 3.4.2 sart configuration setup - async (host ? ? isar) async denotes an asynchronous formatting of data according to itu-t v.14. two separate modes are distinguished for async which depends on the selected modulation scheme at the data pump 7 6 5 4 3 2 1 0 dps msc mds his 1 0 0 1 0 1 15 14 13 12 11 10 9 8 ctrl msb hdmc 0 0 smode 7 6 5 4 3 2 1 0 ctrl lsb 2 7 6 5 4 3 2 1 0 1. parameter 0 ovsp snp eop edp nsb chs 7 6 5 4 3 2 1 0 2. parameter bft dps ... datapath selection 01: path 1 10: path 2 hdmc ... halfduplex mode configuration 00: receive and transmit channels are enabled (default) 01: receive channel is disabled 10: transmit channel is disabled 11: not used in halfduplex mode the pump would transfer idle bits in the direction that is currently not in use, so the corresponding receive or transmit channel can be selectively disabled to reduce the interrupt load for not valid data. for all other pump modes except halfduplex mode, hdmc must be set to its default value 00. smode ... sart mode 0000: disable sart 0010: v.14 mode (used for pump modes v.110, v.32, v.32bis, v.22, v.22bis) 0011: hdlc mode 0100: binary mode 0101: fsk v.14 mode (used for pump modes v.21, v.23, bell 103, bell 202) all other codes reserved there is a difference in the pump modes fsk v.14 and v.14: for fsk v.14 the bit alignment during an idle sequence gets lost, since there is only one frequency for the mark bit and therefore there's no fixed baud rate at the data pump during the idle sequence. for v.14 mode there is a data stream that has a fixed bit alignment, since the modulation scheme provides a fixed baud rate even during idle sequence.
_________________________________________________psb 7110 siemens aktiengesellschaft page 59 important note: fsk v.14 mode must not be used for any other pump modes than v.21, v.23, bell 103 and bell 202.
_________________________________________________psb 7110 siemens aktiengesellschaft page 60 ovsp ... overspeed range (valid only for transmit direction) number of stop bits to be deleted 0: 1 of 8 1: 1 of 4 stop bit deletion during data transmission is initiated by a control command, otherwise all stopbits are generated independent of ovsp setting. it is only valid for v.14 mode and not supported for fsk v.14. overspeed range for the transmitter is an option that can be used to increase the data rate in async mode by means of the overspeed mechanism that is actually defined for compensating different data rates due to missing synchronism between an aysnc-receiver and transmitter. the isar will just omit stopbits and therefore gain a 12.5 or 25% higher data rate. snp ... stick / normal parity 0: normal parity 1: stick parity eop ... even / odd parity 0: odd parity 1: even parity edp ... enable / disable parity bit 0: disable parity 1: enable parity nsb ... number of stop bits 0: 1 stop bit 1: 2 stop bits chs ... character size 00: 5 bit 01: 6 bit 10: 7 bit 11: 8 bit bft ... buffer flush timeout (valid for receive direction only) 0: default value (flush timeout = 32 * symbolrate) 1: flush timeout = 2 * symbolrate 2: = 4 * symbolrate : : 254: = 508 * symbolrate 255: flush timeout disabled the buffer flush counter determines the length of a timer that is started when after a single character an idle sequence is being received. this is to ensure, that async characters are indicated and transfered to the host in case of a long idle sequence even though the message length is not yet complete. if the timeout is disabled, the last datawords remain in the receiver buffer - even during a long idle sequence - until the message length is complete which is then indicated to the host. for fast data rates a value in the range bft = 10 ... 50 is suitable, whereas for slow data rates (v.21 / 300 bps) a lower value is recommended. the bft-value should be selected high enough to avoid a too early buffer flush, which would increase the mailbox load. the symbolrate refers to the selected modulation scheme which is selected for pump configuration.
_________________________________________________psb 7110 siemens aktiengesellschaft page 61 3.4.3 sart configuration setup - binary (host ? ? isar) 7 6 5 4 3 2 1 0 dps msc mds his 1 0 0 1 0 1 15 14 13 12 11 10 9 8 ctrl msb hdmc 0 0 smode 7 6 5 4 3 2 1 0 ctrl lsb 2 7 6 5 4 3 2 1 0 1. parameter 0 0 0 0 0 0 duo bsw 7 6 5 4 3 2 1 0 2. parameter dufw dps ... datapath selection 01: path 1 10: path 2 hdmc ... halfduplex mode configuration 00: receive and transmit channel are enabled (default) 01: receive channel is disabled 10: transmit channel is disabled 11: not used in halfduplex mode the pump would transfer idle bits in the direction that is currently not in use, so the corresponding receive or transmit channel can be selectively disabled to reduce the interrupt load for not valid data. for all other pump modes except halfduplex mode, hdmc must be set to its default value 00. smode ... sart mode 0000: disable sart 0010: v.14 mode 0011: hdlc mode 0100: binary mode 0101: fsk v.14 mode all other codes reserved duo ... data underrun operation for data underrun in tx direction ... 0: ... previous databyte in tx buffer is continuously transmitted 1: ... fillword in mailbox (2nd parameter) is continuously transmitted the fillword functionality can be used to transmit "1" or "0" or any other 8 bit value without continuous message transfer between host and isar.
_________________________________________________psb 7110 siemens aktiengesellschaft page 62 bsw ... bit swapping 0: msb is transmitted/received first 1: lsb is transmitted/received first dufw ... data underrun fill word this fillword is transmitted continuously if a data underrun condition occurs in transmit direction. it is only valid if the duo bit in the first parameter is set. 3.4.4 sart configuration setup - disable sart (host ? ? isar) 7 6 5 4 3 2 1 0 dps msc mds his 1 0 0 1 0 1 15 14 13 12 11 10 9 8 ctrl msb 0 0 0 0 smode 7 6 5 4 3 2 1 0 ctrl lsb 0 dps ... datapath selection 01: path 1 10: path 2 smode ... sart mode 0000: disable sart 0010: v.14 mode 0011: hdlc mode 0100: binary mode 0101: fsk v.14 mode all other codes reserved if the sart is disabled, the data received by the pump is not forwarded to the receive buffer. in transmit direction, a continuous sequence of "1" (marks) are forwarded to the pump if the sart is disabled.
_________________________________________________psb 7110 siemens aktiengesellschaft page 63 3.5 sart data data together with status information or control commands is exchanged by 2 types of operation, which are described in the following two chapters. the parameter mds = 00 indicates that the message is related to the buffer as the user data is transfered to and from the buffers. however, the whole message is described as a sart message, since status information, originated from the sart control unit and control information which is meant for the sart unit is transfered along with it. 3.5.1 sart status events with receive data (isar ? ? host) the sart receiver status, which is always data related, is passed to the host along with any data transfer via the mailbox. the sart status is coded in the ctrl msb, while the ctrl lsb indicates the number of data available in the mailbox . certain sart receive state changes cause an immediate buffer flush event to the associated interface buffer, i.e. any time when such a state changes, all data in the internal fifo buffer is transfered to the host even if the buffer was not yet filled up to the programmed message length. most status bits are related to the last databyte of the mailbox (e.g. parity error). others, like "frame start" in hdlc mode are related to the first databyte in the mailbox. if no bit is set, messages of the predefined length are transfered. 3.5.1.1 sart status events with receive data - hdlc (isar ? ? host) 7 6 5 4 3 2 1 0 dps msc mds iis 1 0 0 0 0 0 15 14 13 12 11 10 9 8 ctrl msb - fed fsd fad rer cer - nmd 7 6 5 4 3 2 1 0 ctrl lsb nom 7 6 5 4 3 2 1 0 1. parameter 1st databyte of the message : 7 6 5 4 3 2 1 0 n. parameter n-th databyte of the message dps ... datapath selection 01: path 1 10: path 2 a status information is valid, if the corresponding bit is set to "1": fed ... frame end detected fsd ... frame start detected fad ... frame abort detected
_________________________________________________psb 7110 siemens aktiengesellschaft page 64 rer ... residue error detected received data is not multiple of 8 bits. cer ... crc error detected mailbox contains all received data. nmd ... no more data (only valid with fax modulations pump mode) nmd indicates that the carrier of the remote fax modem is no longer available. nom ... number of valid bytes in the mailbox indicates the number n of valid data bytes to be read from the mailbox. for the "frame end"-condition, the fcs is contained in the hdlc frame as the last 2 octetts of the message (16 bit fcs). for all conditions indicated in bit 14 - bit 10 (ctrl msb), valid data in the buffer is indicated to the host although the message length may not yet be complete. incomplete hdlc frames indicated in bit 12 - 10 are available in the mailbox including the erroneous data word. however, the host does not need to read such a frame from the buffer, it can skip this frame by only setting the isar interrupt acknowledge bit (iia). for all conditions indicated in bits 12 -10, data in the mailbox is to be skipped by the host.
_________________________________________________psb 7110 siemens aktiengesellschaft page 65 3.5.1.2 sart status events with receive data - async (isar ? ? host) 7 6 5 4 3 2 1 0 dps msc mds iis 1 0 0 0 0 0 15 14 13 12 11 10 9 8 ctrl msb - - bre brs dsd per - - 7 6 5 4 3 2 1 0 ctrl lsb nom 7 6 5 4 3 2 1 0 1. parameter 1st databyte of the message : 7 6 5 4 3 2 1 0 n. parameter n-th databyte of the message dps ... datapath selection 01: path 1 10: path 2 a status information is valid, if the corresponding bit is set to "1": bre ... break signal end detected brs ... break signal start detected dsd ... deleted stopbit detected it is up to the host to decide whether this indicates a frame error or an allowed stop bit deletion due to overspeed range. per ... parity error nom ... number of valid bytes in the mailbox indicates the number n of valid data bytes to be read from the mailbox. break end occurs with the first character in the mailbox, which is not valid. if the message contains more than one character, all characters starting from the second are valid. all other status indications (bit 12 - 10) refer to the last character of the message, so the last character is not valid if one of these bits is set. for all conditions indicated in bit 12 to 10, valid data in the buffer is indicated to the host although the message length may not yet be complete. for characters with a length of 5, 6 or 7 bits the parity bit is transfered together with the character in bit position 5, 6 or 7 respectively. it is not available for 8 bit characters.
_________________________________________________psb 7110 siemens aktiengesellschaft page 66 3.5.1.3 sart status events with receive data - binary (isar ? ? host) 7 6 5 4 3 2 1 0 dps msc mds iis 1 0 0 0 0 0 15 14 13 12 11 10 9 8 ctrl msb - - - - - - - nmd 7 6 5 4 3 2 1 0 ctrl lsb nom 7 6 5 4 3 2 1 0 1. parameter 1st databyte of the message : 7 6 5 4 3 2 1 0 n. parameter n-th databyte of the message dps ... datapath selection 01: path 1 10: path 2 nmd ... no more data (only valid with fax modulations pump mode) nmd=1 indicates that the carrier of the remote fax modem is no longer available. nom ... number of valid bytes in the mailbox indicates the number n of valid data bytes to be read from the mailbox.
_________________________________________________psb 7110 siemens aktiengesellschaft page 67 3.5.2 sart control commands with transmit data (host ? ? isar) the sart transmitters control commands, which are data related, are passed to the isar along with any data transfer via the mailbox. the sart control command is coded in the ctrl msb, while the ctrl lsb indicates the number of data available in the mailbox for transmission. messages without data bytes, i.e. messages with ctrl lsb = 0, will be discarded by the isar. 3.5.2.1 sart control commands with transmit data - hdlc (host ? ? isar) 7 6 5 4 3 2 1 0 dps msc mds his 1 0 0 0 0 0 15 14 13 12 11 10 9 8 ctrl msb 0 fed fst gfa 0 0 0 nmd 7 6 5 4 3 2 1 0 ctrl lsb nom 7 6 5 4 3 2 1 0 1. parameter 1st databyte of the message : 7 6 5 4 3 2 1 0 n. parameter n-th databyte of the message dps ... datapath selection 01: path 1 10: path 2 the control command is valid if the corresponding bit is set to "1":. fed ... frame end the last databyte in the mailbox is indicated as the last of the hdlc frame. fst ... frame start the first databyte in the mailbox is indicated as the first of the hdlc frame. gfa ... generate frame abort initiates the generation of an abort sequence.
_________________________________________________psb 7110 siemens aktiengesellschaft page 68 nmd ... no more data (only for fax modulations pump mode) indicates the end of the data stream and initiates the termination of the current modulation. nmd has the similar effect as the command cmd_escape, the difference is, that nmd will cause the fax pump to turn off the modulation right after the last valid data and so enable to cope with timings related to certain protocols. nmd must not be set, if there is another hdlc frame to be sent right after the current fed, as this would cause the flag sequence to be turned off. after the last message of an hdlc frame has been sent (with fed set), immediately another separate message with nmd must be issued by the host, containing one dummy databyte (ctrl lsb=1), that will be discarded by the isar. nom ... number of valid bytes in the mailbox indicates the number n of valid data bytes in the mailbox to be transmitted.
_________________________________________________psb 7110 siemens aktiengesellschaft page 69 3.5.2.2 sart control co mmands with transmit data - async (host ? ? isar) 7 6 5 4 3 2 1 0 dps msc mds his 1 0 0 0 0 0 15 14 13 12 11 10 9 8 ctrl msb 0 0 sob sab dsb v42 0 0 7 6 5 4 3 2 1 0 ctrl lsb nom 7 6 5 4 3 2 1 0 1. parameter 1st databyte of the message : 7 6 5 4 3 2 1 0 n. parameter n-th databyte of the message dps ... datapath selection 01: path 1 10: path 2 the individual control function is valid if the corresponding bit is set to "1": sob ... stop break signal sab ... start break signal dsb ... delete stopbits v42 ... generate v42 detect sequence nom ... number of valid bytes in the mailbox indicates the number n of valid data bytes in the mailbox to be transmitted. with sab a sequence of at least 2m+3 start bits is initiated and sob enables the host to generate a variable sequence length. if both, sab and sob are set within one message, a break signal of exactly 2m+3 start bits is generated. if dsb is set, every 4th or 8th stopbit is omitted as configured in the sart configuration setup (see 3.4.2). setting of v42 causes the generation of 12 stopbits between each character in the mailbox.
_________________________________________________psb 7110 siemens aktiengesellschaft page 70 3.5.2.3 sart control commands with transmit data - binary (host ? ? isar) 7 6 5 4 3 2 1 0 dps msc mds his 1 0 0 0 0 0 15 14 13 12 11 10 9 8 ctrl msb 0 0 0 0 0 0 0 nmd 7 6 5 4 3 2 1 0 ctrl lsb nom 7 6 5 4 3 2 1 0 1. parameter 1st databyte of the message : 7 6 5 4 3 2 1 0 n. parameter n-th databyte of the message dps ... datapath selection 01: path 1 10: path 2 the control function is valid if the corresponding bit is set to "1": nmd ... no more data (only for fax modulations pump mode) indicates the end of the data stream and initiates the termination of the current modulation. nmd has the similar effect as the command cmd_escape, the difference is, that nmd will cause the fax pump to turn off the modulation right after the last valid data and so enable to cope with timings related to certain protocols. after the last message of a binary data stream has been sent, immediately another separate message with nmd must be issued by the host, containing one dummy databyte (ctrl lsb=1), that will be discarded by the isar. nom ... number of valid bytes in the mailbox indicates the number n of valid data bytes in the mailbox to be transmitted.
_________________________________________________psb 7110 siemens aktiengesellschaft page 71 3.6 pump configuration 3.6.1 pump configuration setup (host ? ? isar) the pump is configured by the host. the host interrupt status register (his) indicates that a new pump configuration is available in the mailbox registers. important note: it is important to note that configuration of the pump will reset the whole data path except buffer configuration, i.e. any configuration of the sart and iom-2 is invalid, therefore the pump should be configured right after buffer configuration and precede sart and iom-2 configuration. the lsb of the control register holds the number of additional parameter words which are passed via the mailbox . the maximum number n of parameter words depends on the pump path mode. the message coding of configuration setup for some of the pump modes is similar in a few of the parameters, however the total message coding is described separately for each of the pump modes which are: pump mode pmod fax modulations datamodem modulations halfduplex modulations v.110 dtmf dtmf transmission bypass 001 010 011 100 101 110 111 as the modulation based pump modes (001, 010, 011) are not available in datapath 2 , the second channel must not be configured to these pump modes. the table below shows to which of the pump modes datapath 2 can be configured. datapath 1 (dps=01) datapath 2 (dps=10) fax modulations datamodem modulations halfduplex modulations v.110 v.110 (see note) dtmf dtmf transmission bypass bypass important note: it is important to note that datapath 2 must not be configured to v.110 if path 1 is configured to datamodem modulations at the same time.
_________________________________________________psb 7110 siemens aktiengesellschaft page 72
_________________________________________________psb 7110 siemens aktiengesellschaft page 73 3.6.1.1 pump configuration setup - fax modulations (host ? ? isar) 7 6 5 4 3 2 1 0 dps msc mds his 0 1 1 0 0 1 1 0 15 14 13 12 11 10 9 8 ctrl msb oam 0 0 0 pmod 7 6 5 4 3 2 1 0 ctrl lsb 2 7 6 5 4 3 2 1 0 1. parameter 0 0 0 toa 7 6 5 4 3 2 1 0 2. parameter 0 0 0 0 0 atn 0 ctn oam ... originating / answering mode 0x: pump is set to answering mode 1x: pump is set to originating mode (note: x=don't care) pmod ... pump path mode select 000: disable all (no mailbox entry) 001: fax modulations 010: datamodem modulations 011: halfduplex modulations 100: v.110 101: dtmf 110: dtmf transmission 111: bypass toa ... transmitter output attenuation 0: 0 db 1: 1 db : : 31: 31 db atn ... answer tone enables or disables the generation of an answer tone when fax procedures are performed. 0: answer tone is disabled 1: answer tone is enabled ctn ... calling tone enables or disables the generation of a calling tone when fax procedures are performed. 0: calling tone is disabled 1: calling tone is enabled
_________________________________________________psb 7110 siemens aktiengesellschaft page 74 3.6.1.2 pump configuration setup - datamodem modulations (host ? ? isar) 7 6 5 4 3 2 1 0 dps msc mds his 0 1 1 0 0 1 1 0 15 14 13 12 11 10 9 8 ctrl msb oam 0 0 0 pmod 7 6 5 4 3 2 1 0 ctrl lsb 6 7 6 5 4 3 2 1 0 1. parameter 0 0 0 toa 7 6 5 4 3 2 1 0 2. parameter 0 v23r v22a v22b v22c 0 v21 bel 7 6 5 4 3 2 1 0 3. parameter amod 0 0 0 0 0 v32b v23b 7 6 5 4 3 2 1 0 4. parameter v32r (lsb) 7 6 5 4 3 2 1 0 5. parameter v32r (msb) 7 6 5 4 3 2 1 0 6. parameter 0 0 0 0 gts atn ctn oam ... originating / answering mode 0x: pump is set to answering mode 1x: pump is set to originating mode (note: x=don't care) pmod ... pump path mode select 000: disable all (no mailbox entry) 001: fax modulations 010: datamodem modulations 011: halfduplex modulations 100: v.110 101: dtmf 110: dtmf tra nsmission 111: bypass
_________________________________________________psb 7110 siemens aktiengesellschaft page 75 toa ... transmitter output attenuation 0: 0 db 1: 1 db : : 31: 31 db v23r ... v.23 reverse, 75 bps / 1200 bps 0: is not permitted 1: is permitted v22a ... v.22bis, 2400 bps 0: is not permitted 1: is permitted v22b ... v.22bis, 1200 bps 0: is not permitted 1: is permitted v22c ... v.22 / bell 212, 1200 bps 0: is not permitted 1: is permitted v21 ... v.21 / bell 103, 300 bps 0: is not permitted 1: is permitted bel ... bell 103, 202 and 212 select bel selects whether in parameters v22c, v21 and v23b the v.xx or the bell xxx modulation is selected. 0: bell modulation is not permitted 1: bell modulation is permitted amod ... automode operation according to eia/tia pn-2330 0: is disabled 1: is enabled v32b ... v.32bis modulation 0: is not permitted 1: is permitted v23b ... v.23 / bell 202, 1200 bps / 75 bps 0: is not permitted 1: is permitted
_________________________________________________psb 7110 siemens aktiengesellschaft page 76 v32r ... v.32 / v.32bis available rates v32r determines the rate signal (specified in itu v.32bis) that is used in the start-up, retrain and renegotiate procedures. the coding is the same as in the above mentioned recommendation, however some of the most commonly used codings are given below. 0000 0101 0001 0001: v.32, 4800 bps 0000 1101 0001 0001: v.32, up to 4800 bps 0000 0011 0001 0001: v.32, 9600 bps 0000 1111 0001 0001: v.32, up to 9600 bps 0000 1001 1101 0001: v.32bis, 7200 bps 0000 1101 1101 0001: v.32bis, up to 7200 bps 0000 1011 1001 0001: v.32bis, 9600 bps 0000 1111 1101 0001: v.32bis, up to 9600 bps 0000 1001 1011 0001: v.32bis, 12000 bps 0000 1111 1111 0001: v.32bis, up to 12000 bps 0000 1001 1001 1001: v.32bis, 14400 bps 0000 1111 1111 1001: v.32bis, up to 14400 bps gts ... guard tone select (for v.22 / v.22bis) 00: guard tone disabled 01: 550 hz guard tone enabled 10: 1800 hz guard tone enabled atn ... v.25 answer tone 0: disabled 1: enabled ctn ... v.25 calling tone 0: disabled 1: enabled the selection of the modulation scheme is contained from the 2nd to the 6th parameter. if automode is selected, any modulation which is masked (set to "0") in one of the parameters, is not tested/used in automode operation. for non automode the permitted modulation parameters are used to select the data modulation. if more than one modulation is permitted, the highest data rate is selected.
_________________________________________________psb 7110 siemens aktiengesellschaft page 77 3.6.1.3 pump configuration setup - halfduplex modulations (host ? ? isar) 7 6 5 4 3 2 1 0 dps msc mds his 0 1 1 0 0 1 1 0 15 14 13 12 11 10 9 8 ctrl msb oam 0 0 0 pmod 7 6 5 4 3 2 1 0 ctrl lsb 3 7 6 5 4 3 2 1 0 1. parameter 0 0 0 toa 7 6 5 4 3 2 1 0 2. parameter v17c v17d v29a v29b v29c v27a v27b v21 7 6 5 4 3 2 1 0 3. parameter 0 0 0 ept 0 0 v17a v17b oam ... originating / answering mode 00: not u sed 01: pump is receiving only 10: pump is transmitting only 11: pump is receiving and transmitting pmod ... pump path mode select 000: disable all (no mailbox entry) 001: fax modulations 010: datamodem modulations 011: halfduplex modulations 100: v.110 101: dtmf 110: dtmf transmission 111: bypass toa ... transmitter output attenuation 0: 0 db 1: 1 db : : 31: 31 db v17c ... v.17, 9600 bps 0: is disabled 1: is enabled
_________________________________________________psb 7110 siemens aktiengesellschaft page 78 v17d ... v.17, 7200 bps 0: is disabled 1: is enabled v29a ... v.29, 9600 bps 0: is disabled 1: is enabled v29b ... v.29, 7200 bps 0: is disabled 1: is enabled v29c ... v.29, 4800 bps 0: is disabled 1: is enabled v27a ... v.27ter, 4800 bps 0: is disabled 1: is enabled v27b ... v.27ter, 2400 bps 0: is disabled 1: is enabled v21 ... v.21 channel 2, 300 bps 0: is disabled 1: is enabled ept ... echo protector tone 0: is disabled 1: is enabled v17a ... v.17, 14400 bps 0: is disabled 1: is enabled v17b ... v.17, 12000 bps 0: is disabled 1: is enabled the selection of the modulation scheme is contained in the 2nd and 3rd parameter. if more than one modulation is enabled, the highest data rate is selected.
_________________________________________________psb 7110 siemens aktiengesellschaft page 79 3.6.1.4 pump configuration setup - v.110 (host ? ? isar) 7 6 5 4 3 2 1 0 dps msc mds his 1 0 0 1 1 0 15 14 13 12 11 10 9 8 ctrl msb 0 0 0 0 0 pmod 7 6 5 4 3 2 1 0 ctrl lsb 2 7 6 5 4 3 2 1 0 1. parameter vdr 7 6 5 4 3 2 1 0 2. parameter 0 0 0 0 0 0 0 fct dps ... datapath selection 01: path 1 10: path 2 pmod ... pump path mode select 000: disable all (no mailbox entry) 001: fax modulations 010: datamodem modulations 011: halfduplex modulations 100: v.110 101: dtmf 110: dtmf transmission 111: bypass vdr ... v.110 data rate 6: 600 bps 7: 1200 bps 8: 2400 bps 9: 4800 bps 12: 9600 bps 16: 19200 bps 24: 38400 bps 32: 48000 bps 40: 56000 bps (default) 41: 56000 bps (alternative) 48: 64000 bps the default and alternative adaptation of 56 kbps to 64 kbps are specified in the itu-t v.110 recommendation.
_________________________________________________psb 7110 siemens aktiengesellschaft page 80 fct ... flow control (x-bits) 0: disabled 1: enabled if enabled, the received x-bits are evaluated by the pump control and data from the mailbox is not forwarded to the sart unit for transmission if indicated by the remote side. additionally, the x-bit change is indicated to the host by means of status events. flow control is only supported for sart mode v.14. important note: in contrast to the recommended initialisation procedure described in chapter 3.1.1, the sequence for configuration with pump mode v.110 is slightly different than for all other modes: if the pump should operate in v.110 mode, the iom-2 interface must be configured as the last functional block, i.e. the sequence for configuration setup should be 1. buffer configuration 2. p ump configuration (v.110) 3. sart configuration 4. iom-2 configuration
_________________________________________________psb 7110 siemens aktiengesellschaft page 81 3.6.1.5 pump configuration setup - dtmf (host ? ? isar) 7 6 5 4 3 2 1 0 dps msc mds his 0 1 1 0 0 1 1 0 15 14 13 12 11 10 9 8 ctrl msb 0 0 0 0 0 pmod 7 6 5 4 3 2 1 0 ctrl lsb 1 7 6 5 4 3 2 1 0 1. parameter rel pmod ... pump path mode select 000: disable all (no mailbox entry) 001: fax modulations 010: datamodem modulations 011: halfduplex modulations 100: v.110 101: dtmf 110: dtmf transmission 111: bypass rel ... rejection level a dtmf signal level which is below rel is not detected by the dtmf receiver. the equation for rel is given below (level is to be inserted without its unit dbm0): rel level = + 253 30 20 as an example, for some of the most commonly used values rel is given below. it is recommended to choose a level between -50 and -40 dbm0 to provide for proper operation.
_________________________________________________psb 7110 siemens aktiengesellschaft page 82 rel level 25: -50.1317 dbm0 28: -49.1474 dbm0 31: -48.2633 dbm0 35: -47.2092 dbm0 40: -46.0493 dbm0 45: -45.0263 dbm0 50: -44.1111 dbm0 56: -43.1268 dbm0 63: -42.1037 dbm0 71: -41.0653 dbm0 80: -40.0287 dbm0 90: -39.0057 dbm0 101: -38.0041 dbm0 113: -37.0289 dbm0 127: -36.0144 dbm0 142: -35.0447 dbm0 160: -34.0081 dbm0 179: -33.0335 dbm0 201: -32.0266 dbm0 226: -31.0083 dbm0 253: -30.0281 db m0 in dtmf mode the octetts received from the iom-2 timeslot are passed transparently through the pump without data formatting, similar to bypass mode. the dtmf receiver is active to detect dtmf tones in the received data stream and to indicate received dtmf digits to the host. the dtmf receiver interprets the octetts received from the iom-2 timeslot as a-law or m -law pcm samples, depending on the iom-2 configuration. in transmit direction data is forwarded similar as in bypass mode. no dtmf transmission is possible in this mode. to transmit dtmf digits the pump has to be configured to dtmf transmission.
_________________________________________________psb 7110 siemens aktiengesellschaft page 83 3.6.1.6 pump configuration setup - dtmf transmission (host ? ? isar) 7 6 5 4 3 2 1 0 dps msc mds his 0 1 1 0 0 1 1 0 15 14 13 12 11 10 9 8 ctrl msb 0 0 0 0 0 pmod 7 6 5 4 3 2 1 0 ctrl lsb 1 7 6 5 4 3 2 1 0 1. parameter 0 0 0 toa pmod ... pump path mode select 000: disable all (no mailbox entry) 001: fax modulations 010: datamodem modulations 011: halfduplex modulations 100: v.110 101: dtmf 110: dtmf transmission 111: bypass toa ... transmitter output attenuation 0: 0 db 1: 1 db : : 31: 31 db
_________________________________________________psb 7110 siemens aktiengesellschaft page 84 3.6.1.7 pump configuration setup - bypass mode (host ? ? isar) 7 6 5 4 3 2 1 0 dps msc mds his 1 0 0 1 1 0 15 14 13 12 11 10 9 8 ctrl msb 0 0 0 0 0 pmod 7 6 5 4 3 2 1 0 ctrl lsb 0 dps ... datapath selection 01: path 1 10: path 2 pmod ... pump path mode select 000: disable all (no mailbox entry) 001: fax modulations 010: datamodem modulations 011: halfduplex modulations 100: v.110 101: dtmf 110: dtmf transmission 111: bypass
_________________________________________________psb 7110 siemens aktiengesellschaft page 85 3.6.2 pump control command (host ? ? isar) 3.6.2.1 pump control command - fax modulations (host ? ? isar) 7 6 5 4 3 2 1 0 dps msc mds his 0 1 1 0 1 0 1 0 15 14 13 12 11 10 9 8 ctrl msb fcmd 7 6 5 4 3 2 1 0 ctrl lsb nom 7 6 5 4 3 2 1 0 1. parameter modc or: 7 6 5 4 3 2 1 0 1. parameter sld fcmd ... fax command contains the one of the fax commands listed below. for some of the commands one additional parameter must be written to the mailbox. a7h: cmd_fth (nom=1, parameter: modc) a5h: cmd_frh (nom=1, parameter: modc) a8h: cmd_ftm (nom=1, parameter: modc) a6h: cmd_frm (nom=1, parameter: modc) ach: cmd_sil_det_on (nom=1, parameter: sld) a2h: cmd_continue (nom=0) a4h: cmd__escape (nom=0) abh: cmd_sil_det_off (nom=0) a9h: cmd_halt (nom=0) nom ... number of additional parameters in the mailbox
_________________________________________________psb 7110 siemens aktiengesellschaft page 86 modc ... modulation code this parameter indicates the particular facsimile modulation and speed selected for the next procedure. 3: 300 bps (v.21 ch2) 24: 2400 bps (v.27ter) 48: 4800 bps (v.27ter) 72: 7200 bps (v.29) 73: 7200 bps (v.17) 74: 7200 bps (v.17 with short train) 96: 9600 bps (v.29) 97: 9600 bps (v.17) 98: 9600 bps (v.17 with short train) 121: 12000 bps (v.17) 122: 12000 bps (v.17 with short train) 145: 14400 bps (v.17) 146: 14400 bps (v.17 with short train) sld ... silence duration this parameter determines the silence detect duration associated with the wait for silence procedure. 0: 0 1: 10 ms 2: 20 ms : : 255: 2550 ms
_________________________________________________psb 7110 siemens aktiengesellschaft page 87 command description: cmd_fth starts transmission of hdlc frames. the additional parameter (nom=1) contains the modulation mode at which data is to be transmitted. if no parameter is provided (nom=0), previous setting of this parameter will be used. cmd_frh starts reception of hdlc frames. the additional parameter (nom=1) contains the modulation mode at which data is to be received. if no parameter is provided (nom=0), previous setting of this parameter will be used. cmd_ftm starts transmission of binary data. the additional parameter (nom=1) contains the modulation mode at which data is to be transmitted. if no parameter is provided (nom=0), previous setting of this parameter will be used. cmd_frm starts reception of binary data. the additional parameter (nom=1) contains the modulation mode at which data is to be received. if no parameter is provided (nom=0), previous setting of this parameter will be used. cmd_sil_det_on starts to wait a determined length of time. the additional parameter (nom=1) contains the silence duration which is to be waited. if no parameter is provided (nom=0), previous setting of this parameter will be used. cmd_continue handshake message from the host to indicate that the host is ready to do the task (transmit/receive) which it selected before. cmd_escape this command is a regular escape in receive modes and a break in transmit modes. cmd_sil_det_off break of silence detection. cmd_halt shut down from fax pump idle state.
_________________________________________________psb 7110 siemens aktiengesellschaft page 88 3.6.2.2 pump control command - datamodem modulations (host ? ? isar) 7 6 5 4 3 2 1 0 dps msc mds his 0 1 1 0 1 0 1 0 15 14 13 12 11 10 9 8 ctrl msb dcmd 7 6 5 4 3 2 1 0 ctrl lsb 0 dcmd ... datamodem command contains one of the following datamodem commands, which are mainly used for debug purposes: ceh: local_renegotiate (only for v.32bis) cfh: local_retrain (only for v.32bis, v.32 and v.22bis) command description: local_renegotiate initiates a v.32bis renegotiation. local_retrain initiates a v.32bis, v.32 or v.22bis retrain respectively (depending on the selected modulation scheme). 3.6.2.3 pump control command - halfduplex modulations (host ? ? isar) there are no control commands defined for this mode.
_________________________________________________psb 7110 siemens aktiengesellschaft page 89 3.6.2.4 pump control command - v.110 (host ? ? isar) 7 6 5 4 3 2 1 0 dps msc mds his 1 0 1 0 1 0 15 14 13 12 11 10 9 8 ctrl msb vcmd 7 6 5 4 3 2 1 0 ctrl lsb nom 7 6 5 4 3 2 1 0 1. parameter 0 0 0 0 x sb sa1 sa0 or: 7 6 5 4 3 2 1 0 1. parameter 0 e1 e2 e3 e4 e5 e6 e7 or: 7 6 5 4 3 2 1 0 1. parameter frc dps ... datapath selection 01: path 1 10: path 2 vcmd ... v.110 command contains one of the v.110 commands listed below. for some of the commands one additional parameter must be written to the mailbox. 10h: remove clamp . data from the mailbox is transmitted (nom=0). 11h: set clamp to 0. instead of data, continuous 0-bits are transmitted as d-bits (nom=0). 13h: set clamp to 1. instead of data, continuous 1-bits are transmitted as d-bits (nom=0). 30h: set s-,x-bits (for transmitter). the s- and x-bit setting is transfered in the 1. parameter (nom=1). 40h: set e-bits (for transmitter). the e-bit setting is transfered in the 1. parameter (nom=1). 50h: delay of synchronisation (for receiver). by default, frame synchronisation is achieved with the first v.110 frame that is received correctly. this command tells the pump control, that more than one v.110 frame must be received correctly to achieve synchronism. the 1. parameter defines the number of additional frames to be received (nom=1).
_________________________________________________psb 7110 siemens aktiengesellschaft page 90 90h: enable mailbox buffer empty indication (for transmitter) if enabled, the isar will release a status event to the host as soon as the last data in the mailbox buffer is transmitted and the host can set control bits after the last valid data has been transmitted. the status event will only be released once for a buffer empty condition, for a further state transition from "not empty " to "empty", the indication has to be reenabled again (nom=0). a0h: disable dte control messages a status change of the remote dte is not indicated by status events (nom=0). however, the host can get status information by releasing a status request message (see 3.7.1). a1h: enable dte control messages (default after pump configuration) remote dte status changes are indicated to the host by means of status events (nom=0). for the v.110 commands "set clamp to 0 / 1" (vcmd = 11h / 13h) data must not be entered to the mailbox for transmission. if a clamp is set and continuous 0-bits or 1-bits are transmitted, mailbox data will be discarded by the isar. nom ... number of additional parameters in the mailbox for some of the commands one additional parameter must be written to the mailbox . the value 0 or 1 for each control bit is directly written to the corresponding bit position within the frame: x ... x-bit sb ... s4-, s9-bit sa1 ... s3-, s8-bit sa0 ... s1-, s6-bit e1-7 ... e1-, .. e7-bit for the 600 bps data rate bit e7 is don't care in the message coding, but is controlled by the pump for multiframe synchronisation. frc ... frame counter denotes the number of additional frames that must be received correctly in order to achieve synchronism. as default (frc=0), one v.110 frame must be received correctly to get synchronised and e.g. if frc=3, four frames are to be received correctly, before data is transfered to the receive buffer. 3.6.2.5 pump control command - dtmf (host ? ? isar) no control commands are defined for dtmf mode. to transmit dtmf tones, the pump has to be reconfigured to dtmf-transmission mode (pmod = 110).
_________________________________________________psb 7110 siemens aktiengesellschaft page 91 3.6.2.6 pump control command - dtmf transmission (host ? ? isar) 7 6 5 4 3 2 1 0 dps msc mds his 0 1 1 0 1 0 1 0 15 14 13 12 11 10 9 8 ctrl msb dcmd 7 6 5 4 3 2 1 0 ctrl lsb 1 7 6 5 4 3 2 1 0 1. parameter tdig dcmd ... dtmf command 5ah: transmit dtmf digit (contained in 1. parameter) all other codes not supported tdig ... transmit dtmf digit 10h: "0" 11h: "1" 12h: "2" 13h: "3" 14h: "4" 15h: "5" 16h: "6" 17h: "7" 18h: "8" 19h: "9" 1ah: "a" 1bh: "b" 1ch: "c" 1dh: "d" 1eh: " * " 1fh: "#" the dtmf transmitter is controlled in this mode only. it should be noted that the iom-2 interface must be configured with rate conversion enabled before any dtmf digits can be transmitted. 3.6.2.7 pump control command - bypass mode (host ? ? isar) there are no control commands defined for this mode.
_________________________________________________psb 7110 siemens aktiengesellschaft page 92 3.7 pump status 3.7.1 pump status request (host ? ? isar) a status register which holds the current status of the data pump path is available on request. the pump status request is fully specified with the host interrupt status register (his). the mailbox control register is not used and should be written to 0. 7 6 5 4 3 2 1 0 dps msc mds his 0 0 1 1 1 0 15 14 13 12 11 10 9 8 ctrl msb 0 7 6 5 4 3 2 1 0 ctrl lsb 0 dps ... datapath selection 01: path 1 10: path 2
_________________________________________________psb 7110 siemens aktiengesellschaft page 93 3.7.2 pump status response (isar ? ? host) 3.7.2.1 pump status response - fax modulations (isar ? ? host) 7 6 5 4 3 2 1 0 dps msc mds his 0 1 1 0 1 1 1 0 15 14 13 12 11 10 9 8 ctrl msb oam 0 0 0 pmod 7 6 5 4 3 2 1 0 ctrl lsb 2 7 6 5 4 3 2 1 0 1. parameter ril 7 6 5 4 3 2 1 0 2. parameter rim oam ... originating / answering mode 0x: pump is in answering mode 1x: pump is in originating mode (note: x=don't care) pmod ... selected pump path mode 000: disable all (no mailbox entry) 001: fax modulations 010: datamodem modulations 011: halfduplex modulations 100: v.110 101: dtmf 110: dtmf transmission 111: bypass ril ... rate index - lsb ril contains the data rate at which the pump is currently operating. 0: no speed defined 5: 300 bps 8: 2400 bps 9: 4800 bps 10: 7200 bps 11: 9600 bps 13: 12000 bps 14: 14400 bps
_________________________________________________psb 7110 siemens aktiengesellschaft page 94 rim ... rate index - msb ril contains the modulation scheme at which the pump is currently operating, the specific data rate is given in ril. if rim is 0, the preceding pump configuration setup was not successful. 0: no modulation scheme configured 41h: v.21 asynchronous (fsk v.14 mode) 82h: v.17 92h: v.29 a2h: v.27ter all other codes not supported.
_________________________________________________psb 7110 siemens aktiengesellschaft page 95 3.7.2.2 pump status response - datamodem modulations (isar ? ? host) 7 6 5 4 3 2 1 0 dps msc mds his 0 1 1 0 1 1 1 0 15 14 13 12 11 10 9 8 ctrl msb oam 0 0 0 pmod 7 6 5 4 3 2 1 0 ctrl lsb 4 7 6 5 4 3 2 1 0 1. parameter ril 7 6 5 4 3 2 1 0 2. parameter rim 7 6 5 4 3 2 1 0 3. parameter - - rrt lrt - rrp con neg 7 6 5 4 3 2 1 0 4. parameter - cld rty tmo - - rrn lrn oam ... originating / answering mode 0x: pump is in answering mode 1x: pump is in originating mode (note: x=don't care) pmod ... selected pump path mode 000: disable all (no mailbox entry) 001: fax modulations 010: datamodem modulations 011: halfduplex modulations 100: v.110 101: dtmf 110: dtmf transmission 111: bypass
_________________________________________________psb 7110 siemens aktiengesellschaft page 96 ril ... rate index - lsb ril contains the data rate at which the pump is currently operating. 0: no speed defined 1: 1200 bps (transmitter), 75 bps (receiver) 3: 75 bps (transmitter, 1200 bps (receiver) 5: 300 bps 6: 600 bps 7: 1200 bps 8: 2400 bps 9: 4800 bps 10: 7200 bps 11: 9600 bps (no trellis) 12: 9600 bps (trellis) 13: 12000 bps 14: 14400 bps all other codes not supported. rim ... rate index - msb ril contains the modulation scheme at which the pump is currently operating, the specific data rate is given in ril. if rim is 0, the preceding pump configuration setup was not successful. 0: no modulation scheme configured 20h: v.32/v.32bis 40h: v.22 41h: v.21 asynchronous (fsk v.14 mode) 51h: bell 103 61h: v.23 71h: bell 202 82h: v. 17 92h: v.29 a2h: v.27ter all other codes not supported.
_________________________________________________psb 7110 siemens aktiengesellschaft page 97 the status information is valid, if the corresponding bit is set: rrt ... remote retrain the pump is in a retrain phase that is initiated by the remote station. lrt ... local retrain the pump is in a retrain phase that is initiated by the local station. rrp ... retrain / renegotiate phase the pump is in a retrain or renegotiate phase. more details are contained in the status bits rrt, lrt, rrn and lrn. con ... connection the pump has established a logical connection to the remote subscriber, i.e. it has passed the training phase and will continue with data transmission/reception.. neg ... negotiation the pump is in the first training phase to establish the modulation. cld ... cleardown this bit is set if there is a reason to terminate and restart the modulation. a reason could be a rate signal without any permitted data rate or a timeout condition for bulk delay (together with setting of tmo). rty ... retry during training phase the remote station has requested for a retrain (v.32bis only). tmo ... timeout during training phase the timing conditions for bulk delay were violated. rrn ... remote renegotiation the pump is in a renegotiate phase that is initiated by the remote station. lrn ... local renegotiation the pump is in a renegotiate phase that is initiated by the local station.
_________________________________________________psb 7110 siemens aktiengesellschaft page 98 3.7.2.3 pump status response - halfduplex modulations (isar ? ? host) 7 6 5 4 3 2 1 0 dps msc mds his 0 1 1 0 1 1 1 0 15 14 13 12 11 10 9 8 ctrl msb oam 0 0 0 pmod 7 6 5 4 3 2 1 0 ctrl lsb 2 7 6 5 4 3 2 1 0 1. parameter ril 7 6 5 4 3 2 1 0 2. parameter rim oam ... originating / answering mode 00: not used 01: pump is receiving only 10: pump is transmitting only 11: pump is receiving and transmit ting pmod ... selected pump path mode 000: disable all (no mailbox entry) 001: fax modulations 010: datamodem modulations 011: halfduplex modulations 100: v.110 101: dtmf 110: dtmf transmission 111: bypass
_________________________________________________psb 7110 siemens aktiengesellschaft page 99 ril ... rate index - lsb ril contains the data rate at which the pump is currently operating. 0: no speed defined 5: 300 bps 8: 2400 bps 9: 4800 bps 10: 7200 bps 11: 9600 bps (no trellis) 12: 9600 bps (trellis) 13: 12000 bps 14: 14400 bps all other codes not supported. rim ... rate index - msb ril contains the modulation scheme at which the pump is currently operating, the specific data rate is given in ril. if rim is 0, the preceding pump configuration setup was not successful. 0: no modulation scheme configured 41h: v.21 asynchronous (fsk v.14 mode) 82h: v.17 92h: v.29 a2h: v.27ter all other codes not supported.
_________________________________________________psb 7110 siemens aktiengesellschaft page 100 3.7.2.4 pump status response - v.110 (isar ? ? host) 7 6 5 4 3 2 1 0 dps msc mds his 1 0 1 1 1 0 15 14 13 12 11 10 9 8 ctrl msb 0 0 0 0 0 pmod 7 6 5 4 3 2 1 0 ctrl lsb 6 7 6 5 4 3 2 1 0 1. parameter ril 7 6 5 4 3 2 1 0 2. parameter rim 7 6 5 4 3 2 1 0 3. parameter - - - rof0 rof1 ron1 rofx ronx 7 6 5 4 3 2 1 0 4. parameter - - - - x sb sa1 sa0 7 6 5 4 3 2 1 0 5. parameter - e1 e2 e3 e4 e5 e6 e7 7 6 5 4 3 2 1 0 6. parameter frc dps ... datapath selection 01: path 1 10: path 2 pmod ... selected pump path mode 000: disable all (no mailbox entry) 001: fax modulations 010: datamodem modulations 011: halfduplex modulations 100: v.110 101: dtmf 110: dtmf transmission 111: bypass
_________________________________________________psb 7110 siemens aktiengesellschaft page 101 ril ... rate index - lsb ril contains the data rate at which the pump is currently operating. 0: no speed defined 6: 600 bps 7: 1200 bps 8: 2400 bps 9: 4800 bps 12: 9600 bps 16: 19200 bps 24: 38400 bps 32: 48000 bps 40: 56000 bps (default) 41: 56000 bps (alternative) 48: 64000 bps all other codes not supported. ril=0 is indicated in v.110 mode if not synchronised. rim ... rate index - msb ril contains the modulation scheme at which the pump is currently operating, the specific data rate is given in ril. if rim is 0, the preceding pump configuration setup was not successful, e.g. a wrong data rate was selected for v.110. 0: no modulation scheme configured c0h: v.110 all other codes not supported.
_________________________________________________psb 7110 siemens aktiengesellschaft page 102 rof0, rof1, ron1, rofx, ronx ... remote dte status contains information about the status of the remote dte. the received d- and sa-bits are sampled and compared against different possibilities. a status change is detected by a match of the comparison and indicated by setting the bits as shown below. several bits in the parameter can be set simultaneously depending on the sampled data, e.g. if rof0 is set, rofx will be set, too. it should be noted, that the status response is not data related, i.e. it contains the remote status that is currently received. status status name sampled data rof0 remote (0, off) d sa 00000000 00000000 11111111 11111111 rof1 remote (1, off) d sa 11111111 11111111 11111111 11111111 ron1 remote (1, on) d sa 11111111 11111111 00000000 00000000 rofx remote (x, off) d sa xxxxxxxx xxxxxxxx 11111111 11111111 ronx remote (x, on) d sa xxxxxxxx xxxxxxxx 00000000 00000000 note: x =don't care the following parameters contain the value for each x-, s- and e-bit, which is currently received: x ... x-bit sb ... s4-, s9-bit sa1 ... s3-, s8-bit sa0 ... s1-, s6-bit e1-e7 ... e1-bit - e7-bit for the 600 bps data rate bit e7 is always set to 1. frc ... frame counter for delay of synchronisation denotes the number of additional frames, which was set by the host, that must be received correctly in order to achieve synchronism. as default (frc=0), one v.110 frame must be received correctly to get synchronised and e.g. if frc=3, four frames are to be received correctly, before data is transfered to the receive buffer.
_________________________________________________psb 7110 siemens aktiengesellschaft page 103 3.7.2.5 pump status response - dtmf (isar ? ? host) 7 6 5 4 3 2 1 0 dps msc mds his 0 1 1 0 1 1 1 0 15 14 13 12 11 10 9 8 ctrl msb 0 0 0 0 0 pmod 7 6 5 4 3 2 1 0 ctrl lsb 2 7 6 5 4 3 2 1 0 1. parameter ril 7 6 5 4 3 2 1 0 2. parameter rim pmod ... selected pump path mode 000: disable all (no mailbox entry) 001: fax modulations 010: datamodem modulations 011: halfduplex modulations 100: v.110 101: dtmf 110: dtmf transmission 111: bypass ril ... rate index - lsb ril contains the data rate at which the pump is currently operating. 48: 64000 bps rim ... rate index - msb ril contains the modulation scheme at which the pump is currently operating, the specific data rate is given in ril. c0h: dtmf mode
_________________________________________________psb 7110 siemens aktiengesellschaft page 104 3.7.2.6 pump status response - dtmf transmission (isar ? ? host) 7 6 5 4 3 2 1 0 dps msc mds his 0 1 1 0 1 1 1 0 15 14 13 12 11 10 9 8 ctrl msb 0 0 0 0 0 pmod 7 6 5 4 3 2 1 0 ctrl lsb 4 7 6 5 4 3 2 1 0 1. parameter 0 7 6 5 4 3 2 1 0 2. parameter 0 7 6 5 4 3 2 1 0 3. parameter 0 7 6 5 4 3 2 1 0 4. parameter 0 pmod ... selected pump path mode 000: disable all (no mailbox entry) 001: fax modulations 010: datamodem modulations 011: halfduplex modulations 100: v.110 101: dtmf 110: dtmf transmission 111: bypass
_________________________________________________psb 7110 siemens aktiengesellschaft page 105 3.7.2.7 pump status response - bypass mode (isar ? ? host) 7 6 5 4 3 2 1 0 dps msc mds his 1 0 1 1 1 0 15 14 13 12 11 10 9 8 ctrl msb 0 0 0 0 0 pmod 7 6 5 4 3 2 1 0 ctrl lsb 2 7 6 5 4 3 2 1 0 1. parameter ril 7 6 5 4 3 2 1 0 2. parameter rim dps ... datapath selection 01: path 1 10: path 2 pmod ... selected pump path mode 000: disable all (no mailbox entry) 001: fax modulations 010: d atamodem modulations 011: halfduplex modulations 100: v.110 101: dtmf 110: dtmf transmission 111: bypass ril ... rate index - lsb ril contains the data rate at which the pump is currently operating. 48: 64000 bps rim ... rate index - msb ril contains the modulation scheme at which the pump is currently operating, the specific data rate is given in ril. c0h: bypass mode
_________________________________________________psb 7110 siemens aktiengesellschaft page 106 3.7.2.8 pump status response - pump disabled (isar ? ? host) 7 6 5 4 3 2 1 0 dps msc mds his 1 0 1 1 1 0 15 14 13 12 11 10 9 8 ctrl msb 0 0 0 0 0 pmod 7 6 5 4 3 2 1 0 ctrl lsb 0 dps ... datapath selection 01: path 1 10: path 2 pmod ... selected pump path mode 000: disable all (no mailbox entry) 001: fax modulations 010: datamodem modulations 011: halfduplex modulations 100: v.110 101: dtmf 110: dtmf transmission 111: bypass
_________________________________________________psb 7110 siemens aktiengesellschaft page 107 3.7.3 pump status events (is ar ? ? host) status events are released to the host by the data pump during data transmission/reception and contain dynamic information specific for the selected pump mode. 3.7.3.1 pump status events - fax modulations (isar ? ? host) 7 6 5 4 3 2 1 0 dps msc mds iis 0 1 1 0 1 0 1 0 15 14 13 12 11 10 9 8 ctrl msb fevt 7 6 5 4 3 2 1 0 ctrl lsb 0 fevt ... fax event contains the one of the following fax events: 02h: 10 ms timer interrupt (if enabled; see 3.8.2 timer interrupt request) bch: rsp_ready b3h: line_tx_hdlc b2h: line_tx_binary b1h: line_rx_hdlc b0h: line_rx_binary b5h: rsp_connect b7h: rsp_disc b9h: rsp_fcerror beh: rsp_sil_det abh: rsp_sil_det_off bah: flags_detect fax event description: rsp_ready response to configuration fax mode originator or answerer. line_tx_hdlc response to cmd_fth in order to indicate that the modulation has been established. line_tx_binary response to cmd_ftm in order to indicate that the modulation has been established. line_rx_hdlc response to cmd_frh in order to indicate that the modulation has been established. line_rx_binary response to cmd_frm in order to indicate that the modulation has been established.
_________________________________________________psb 7110 siemens aktiengesellschaft page 108 rsp_connect indication that the fax pump is ready to receive or transmit data. rsp_disc indication that the fax pump has turned off modulation after transmitting all pending data / after the host issues the command cmd_escape. rsp_fcerror indication that the fax pump has detected a "wrong" modulation before it releases the event rsp_connect. rsp_sil_det indication that the prior selected duration of silence time has occured. rsp_sil_det_of f indication that the fax pump has received an "abandon silence time detection" command from the host. flags_detect indication that the fax pump has detected flags.
_________________________________________________psb 7110 siemens aktiengesellschaft page 109 3.7.3.2 pump status events - datamodem modulations (isar ? ? host) 7 6 5 4 3 2 1 0 dps msc mds iis 0 1 1 0 1 0 1 0 15 14 13 12 11 10 9 8 ctrl msb devt 7 6 5 4 3 2 1 0 ctrl lsb 0 devt ... datamodem automode event contains the one of the following datamodem events: 02h: 10 ms timer interrupt (if enabled; see 3.8.2 timer interrupt request) 18h: connection_on 19h: connection_off 20h: v24_off 21h: cts_on 22h: cts_off 23h: dcd_on 24h: dcd_off 25h: dsr_on 26h: dsr_off cch: remote_retrain cdh: remote_renegotiate d4h: gstn_cleardown
_________________________________________________psb 7110 siemens aktiengesellschaft page 110 3.7.3.3 pump status events - halfduplex modulations (isar ? ? host) 7 6 5 4 3 2 1 0 dps msc mds iis 0 1 1 0 1 0 1 0 15 14 13 12 11 10 9 8 ctrl msb hevt 7 6 5 4 3 2 1 0 ctrl lsb 0 hevt ... halfduplex modulations event contains the one of the following datamodem events: 02h: 10 ms timer interrupt (if enabled; see 3.8.2 timer interrupt request) 18h: connection_on 19h: connection_off 20h: v24_off 21h: cts_on 22h: cts_off 23h: dcd_on 24h: dcd_off 25h: dsr_on 26h: dsr_off d4h: gstn_cleardown
_________________________________________________psb 7110 siemens aktiengesellschaft page 111 3.7.3.4 pump status events - v.110 (isar ? ? host) 7 6 5 4 3 2 1 0 dps msc mds iis 1 0 1 0 1 0 15 14 13 12 11 10 9 8 ctrl msb vevt 7 6 5 4 3 2 1 0 ctrl lsb nom 7 6 5 4 3 2 1 0 1. parameter - - - - x sb sa1 sa0 or: 7 6 5 4 3 2 1 0 1. parameter - e1 e2 e3 e4 e5 e6 e7 or: 7 6 5 4 3 2 1 0 1. parameter - - - rof0 rof1 ron1 rofx ronx dps ... datapath selection 01: path 1 10: path 2 vevt ... v.110 event contains one of the following v.110 events. for some of the events one additional parameter is provided via the mailbox. 02h: 10 ms timer interrupt (if enabled; see 3.8.2 timer interrupt request) 30h: change in s-bits received (nom=1). the s-bits are specified in the first parameter. 40h: change in e-bits received (nom=1). the e-bits are specified in the first parameter. 60h: synchronisation lost (nom=0). this event is released for a change from synchronised to not synchronised. 61h: synchronisation achieved (nom=0). this event is released for a chan ge from not synchronised to synchronised. 70h: change in x-bit from 1 ? 0 received (nom=0). 71h: change in x-bit from 0 ? 1 received (nom=0). 90h: mailbox buffer empty (nom=0) this event indicates to the host, that the last data is transmitted and that the mailbox transmit buffer is empty. this event must be enabled by the host (see 3.6.2.4 pump control command - v.110) and it is generated only once, i.e. for further state transitions from "not empty" to "empty", the generation of the status event must be reenabled again. a0h: dte status (nom=1) the first parameter contains information about the status of the remote dte. the received d- and sa-bits are sampled and compared against different possibilities. a status change is detected by a match of the comparison and indicated to the host. the generation of dte status events can be enabled/disabled by control commands (see 3.6.2.4 pump control command - v.110).
_________________________________________________psb 7110 siemens aktiengesellschaft page 112 nom ... number of valid bytes in the mailbox for certain status events one additional parameter is provided via the mailbox. for the following parameters the received value 0 or 1 for each bit is indicated in the corresponding bit position. the control bits do not represent the real time value that is currently received, but they are data related, i.e. the s-, x- and e-bits are transfered to the host with the corresponding data that was received at the same time. information about control bits that are currently received can be requested by the host (see 3.7.1 pump status request), additionally the real time value for x, which is needed for flow control, is indicated by two separate status events (vevt = 70h and 71h). x ... x-bit sb ... s4-, s9-bit sa1 ... s3-, s8-bit sa0 ... s1-, s6-bit e1-e7 ... e1-bit - e7-bit for the 600 bps data rate bit e7 is always set to 1. frc ... frame counter for delay of synchronisation denotes the number of additional frames, which was set by the host, that must be received correctly in order to achieve synchronism. as default (frc=0), one v.110 frame must be received correctly to get synchronised and e.g. if frc=3, four frames are to be received correctly, before data is transfered to the receive buffer. rof0, rof1, ron1, rofx, ronx ... remote dte status contains information about the status of the remote dte. the received d- and sa-bits are sampled and compared against different possibilities. a status change is detected by a match of the comparison and indicated by setting the bits as shown below. several bits in the parameter can be set simultaneously depending on the sampled data, e.g. if rof0 is set, rofx will be set, too. status status name sampled data rof0 remote (0, off) d sa 00000000 00000000 11111111 11111111 rof1 remote (1, off) d sa 11111111 11111111 11111111 11111111 ron1 remote (1, on) d sa 11111111 11111111 00000000 00000000 rofx remote (x, off) d sa xxxxxxxx xxxxxxxx 11111111 11111111 ronx remote (x, on) d sa xxxxxxxx xxxxxxxx 00000000 00000000 note: x =don't care it should be noted that the dte status information is data related and may not represent the value currently be received.
_________________________________________________psb 7110 siemens aktiengesellschaft page 113 comment: after reset the remote dte status logic is in no state and all status bits (rof0, rof1, ron1, rofx and ronx) are set to 0. the pump will start to search for frame synchronisation. when synchronisation is achieved, the host will receive the remote dte status and the s-, x- and e- bits from the pump by means of status events. this information is related to the last v.110 frame that was received for synchronisation, as this frame was received without any sync error. starting with the subsequent frame, the d-bits of the frame are transfered as valid user data to the sart. the same mechanism for resynchronisation is used if frame synchronisation is temporarily lost.
_________________________________________________psb 7110 siemens aktiengesellschaft page 114 3.7.3.5 pump status events - dtmf (isar ? ? host): 7 6 5 4 3 2 1 0 dps msc mds iis 0 1 1 0 1 0 1 0 15 14 13 12 11 10 9 8 ctrl msb rdig 7 6 5 4 3 2 1 0 ctrl lsb 0 rdig ... received dtmf digit one of the following dtmf digits was detected by dtmf receiver: 10h: "0" 11h: "1" 12h: "2" 13h: "3" 14h: "4" 15h: "5" 16h: "6" 17h: "7" 18h: "8" 19h: "9" 1ah: "a" 1bh: "b" 1ch: "c" 1dh: "d" 1eh: " * " 1fh: "#" 3.7.3.6 pump status events - dtmf tran smission (isar ? ? host): no status events defined for this mode. 3.7.3.7 pump status events - bypass mode (isar ? ? host): no status events defined for this mode.
_________________________________________________psb 7110 siemens aktiengesellschaft page 115 3.8 iom-2 configuration the following commands, requests and responses are used to setup/control the network access of the data paths. the configuration/status/commands of both modem/v.110 channels are similar. the d-channel path iom-2 commands are different and therefore described separately. global iom-2 setup is done by using the ?iom-2 configuration? codes of the test/diagnostics commands. 3.8.1 iom-2 configuration setup (host ? ? isar) 7 6 5 4 3 2 1 0 dps msc mds his 1 0 0 1 1 1 15 14 13 12 11 10 9 8 ctrl msb iom 0 0 0 cod rcv 7 6 5 4 3 2 1 0 ctrl lsb 5 7 6 5 4 3 2 1 0 1. parameter 0 0 0 txd rxd tsl 7 6 5 4 3 2 1 0 2. parameter 0 0 rtso 7 6 5 4 3 2 1 0 3. parameter 0 0 0 0 0 rcs 7 6 5 4 3 2 1 0 4. parameter 0 0 ttso 7 6 5 4 3 2 1 0 5. parameter 0 0 0 0 0 tcs dps ... datapath selection 01: path 1 10: path 2 iom ... iom-2 data access 0: disabled 1: enabled
_________________________________________________psb 7110 siemens aktiengesellschaft page 116 cod ... coding 000: no pcm coding 001: a-law coding 010: m -law coding all other codes reserved a-law and m -law coding is selected for all modulation related pump modes (fax, datamodem and halfduplex modulation, dtmf and dtmf transmission). for all other modes (v.110 and bypass mode) "no pcm coding" must be selected. rcv ... rate conversion rcv refers to internal operation of the device and must be set depending on the pump mode. 0: disabled (for all other pump modes) 1: enabled (for pump modes 001, 010, 011, 101) txd ... transmit path switched to 0: dd-line 1: du-line (reset value) rxd ... receive path switched to 0: dd-line (reset value) 1: du-line tsl ... timeslot length for receive / transmit path 00x: 8 bit wordlength (reset value) 010: 16 bit wordlength (used to operate with 16 linear codec, e.g. arcofi) 011: 16 bit wordlength, splitted into two 8-bit words all other codes currently not supported rtso ... receive time slot offset to fsc 0: 0 bit 1: 8 bit : : 63: 504 bit reset value: rtso = 0 for path 1 rtso = 1 for path 2 rcs ... receive clock shift 0: 0 bit 1: 1 bit : : 7: 7 bit reset value: rcs = 0 for path 1 and 2
_________________________________________________psb 7110 siemens aktiengesellschaft page 117 ttso ... transmit time slot offset to fsc 0: 0 bit 1: 8 bit : : 63: 504 bit reset value: ttso = 0 for path 1 ttso = 1 for path 2 tcs ... transmit clock shift 0: 0 bit 1: 1 bit : : 7: 7 bit reset value: tcs = 0 for path 1 and 2
_________________________________________________psb 7110 siemens aktiengesellschaft page 118 3.8.2 iom-2 configuration request (host ? ? isar) the current configuration can be read on request by the host. the request is fully specified by the host interrupt status register (his), i.e. the control registers and the mailbox are not used for the request command and must be set to 0. 7 6 5 4 3 2 1 0 dps msc mds his 0 0 0 1 1 1 15 14 13 12 11 10 9 8 ctrl msb 0 7 6 5 4 3 2 1 0 ctrl lsb 0 dps ... datapath selection 01: path 1 10: path 2
_________________________________________________psb 7110 siemens aktiengesellschaft page 119 3.8.3 iom-2 configuration response (isar ? ? host) 7 6 5 4 3 2 1 0 dps msc mds iis 1 0 0 1 1 1 15 14 13 12 11 10 9 8 ctrl msb iom 0 0 0 cod rcv 7 6 5 4 3 2 1 0 ctrl lsb 5 7 6 5 4 3 2 1 0 1. parameter 0 0 0 txd rxd tsl 7 6 5 4 3 2 1 0 2. parameter 0 0 rtso 7 6 5 4 3 2 1 0 3. parameter 0 0 0 0 0 rcs 7 6 5 4 3 2 1 0 4. parameter 0 0 ttso 7 6 5 4 3 2 1 0 5. parameter 0 0 0 0 0 tcs dps ... datapath selection 01: path 1 10: path 2 iom ... iom-2 data access 0: disabled 1: enabled cod ... selected coding 000: no pcm coding 001: a-law coding 010: m -law coding all other codes reserved a-law and m -law coding is selected for all modulation related pump modes (fax, datamodem and halfduplex modulation, dtmf and dtmf transmission). for all other modes (v.110 and bypass mode) "no pcm coding" must be selected. the transcoding modes (a-law to m -law and reverse) are intended for future applications. rcv ... selected rate conversion rcv refers to internal operation of the device and must be set depending on the pump mode. 0: disabled (for all other pump modes) 1: enabled (for fax modulations, datamodem modulations, halfduplex modu lations and dtmf-transmission)
_________________________________________________psb 7110 siemens aktiengesellschaft page 120 txd ... transmit path switched to 0: dd-line 1: du-line (reset value) rxd ... receive path switched to 0: dd-line (reset value) 1: du-line tsl ... timeslot length for receive / transmit path 00x: 8 bit wordlength (reset value) 010: 16 bit wordlength 011: 16 bit wordlength, splitted into two 8-bit words all other codes currently not supported rtso ... receive time slot offset to fsc 0: 0 bit 1: 8 bit : : 63: 504 bit reset value: rts o = 0 for buffer 1 rtso = 1 for buffer 2 rcs ... receive clock shift 0: 0 bit 1: 1 bit : : 7: 7 bit reset value: rcs = 0 for buffer 1 and 2 ttso ... transmit time slot offset to fsc 0: 0 bit 1: 8 bit : : 63: 504 bit reset value: ttso = 0 for buffer 1 ttso = 1 for buffer 2 tcs ... transmit clock shift 0: 0 bit 1: 1 bit : : 7: 7 bit reset value: tcs = 0 for buffer 1 and 2
_________________________________________________psb 7110 siemens aktiengesellschaft page 121 3.8.4 iom-2 control commands (host ? ? isar) 7 6 5 4 3 2 1 0 dps msc mds his 1 0 1 0 1 1 15 14 13 12 11 10 9 8 ctrl msb icmd 7 6 5 4 3 2 1 0 ctrl lsb 0 dps ... datapath selection 01: path 1 10: path 2 icmd ... iom-2 control command 00h: stop iom-2 channel all activities on the iom-2 interface are frozen. in transmit direction all bits are written to "1" on the iom-2 timeslot and in receive direction all bits received from the iom-2 timeslot are "1". 01h: restart iom-2 channel after iom-2 activities were stopped (icmd=00), data transfer with from/to the iom-2 timeslots is restarted again with the current configuration settings. this command must not be used before the iom-2 interface is configured. 11h: loop on transmit data is looped back to the receiver input. in this case the configuration for the timeslot position of the receiver is without any effect. additionally, the transmit data itself is written to the programmed transmit timeslot if iom-2 data access is enabled (iom=1). if iom-2 data access is disabled (iom=0), transmit data will not be written to the iom-2 timeslot but only looped back to the receiver input. 10h: loop off the loop of transmit data to the receiver input (activated by icmd=11h) is switched off. regular read/write access to the iom-2 is performed according to the configuration setting. important note: the control commands "stop / restart iom-2 channel" have a different effect than "iom-2 data access enable / disable" (iom-bit) in configuration setup. the current configuration setting is not affected by "stop iom-2 channel", only transfer of user data between the pump and the iom-2 timeslots is stopped, which is resumed by the command "restart iom-2 channel".
_________________________________________________psb 7110 siemens aktiengesellschaft page 122 3.9 test / diagnostics path the test/diagnostics path is used for test and diagnostics, general configuration and control (not related to a specific data path) and as an answer channel for certain status / configuration requests to the data channels. 3.9.1 general configuration (host ? ? isar) there are two types of general configuration setup. it is programming of waitstates for the internal dsp operations, a timer interrupt generated by the isar. waitstate 7 6 5 4 3 2 1 0 dps msc his 0 0 1 0 0 1 1 1 15 14 13 12 11 10 9 8 ctrl msb wss 7 6 5 4 3 2 1 0 ctrl lsb 0 wss ... wait state setting sets the waitstates for the internal dsp operations 30h: 15 waitstates 31h: 14 waitstates : : 3fh: 0 waitstates timer interrupt 7 6 5 4 3 2 1 0 dps msc his 0 0 1 0 0 1 0 1 15 14 13 12 11 10 9 8 ctrl msb cmd 7 6 5 4 3 2 1 0 ctrl lsb 0 cmd ... command for general configuration 20h: timer interrupt off 21h: timer interrupt on if enabled, a 10 ms timer interrupt is generated to the host. this can be used for certain driver software implementations that require hardware interrupts. as this is normally used in applications with data modulations, the interrupt request message is coded as a message related to buffer 1 (see 3.9.2), however, it can be used for purposes within other buffers, too. using the timer interrupt increases the message load between the isar and the host significantly.
_________________________________________________psb 7110 siemens aktiengesellschaft page 123 3.9.2 timer interrupt request (isar ? ? host) the "timer interrupt request" message" is generated once per 10 ms if enabled by the "general configuration" message in chapter 3.9.1. 7 6 5 4 3 2 1 0 dps msc iis 0 1 1 0 1 0 1 0 15 14 13 12 11 10 9 8 ctrl msb 2 7 6 5 4 3 2 1 0 ctrl lsb 0 3.9.3 software version request (host ? ? isar) the host can request the version number of the dsp software by the following request message. 7 6 5 4 3 2 1 0 dps msc his 0 0 0 0 0 1 0 1 15 14 13 12 11 10 9 8 ctrl msb 10h 7 6 5 4 3 2 1 0 ctrl lsb 0 3.9.4 software version response (isar ? ? host) the isar returns the version number of the dsp software if requested by the host. 7 6 5 4 3 2 1 0 dps msc his 0 0 1 0 0 1 0 1 15 14 13 12 11 10 9 8 ctrl msb 10h 7 6 5 4 3 2 1 0 ctrl lsb 1 7 6 5 4 3 2 1 0 1. parameter svn svn ... software version number contains the version number of the dsp software on the device. 04h: download firmware v1.0 all other codes currently not supported.
_________________________________________________psb 7110 siemens aktiengesellschaft page 124 3.9.5 invalid message received (isar ? ? host) if the host issues a message to the isar with an his coding that is not specified, the isar will respond with the following error message to indicate that an invalid message coding was detected. 7 6 5 4 3 2 1 0 dps msc iis 0 0 1 1 1 1 1 1 15 14 13 12 11 10 9 8 ctrl msb inv 7 6 5 4 3 2 1 0 ctrl lsb 0 inv ... invalid his coding contains the invalid his register coding of the message which was released by the host. 3.9.6 request selftest result (isar ? ? host) after download of the dsp program the isar automatically performs a selftest, which will check for memory errors or missing iom-2 clocks. the result of the selftest can be requested by the host and possible error conditions are contained in the "selftest response" message (see 3.9.7). 7 6 5 4 3 2 1 0 dps msc his 0 0 0 0 0 1 0 1 15 14 13 12 11 10 9 8 ctrl msb 40h 7 6 5 4 3 2 1 0 ctrl lsb 0
_________________________________________________psb 7110 siemens aktiengesellschaft page 125 3.9.7 selftest response (isar ? ? host) the selftest result requested by the host (see 3.9.6) will result in a response message containing information about possible error conditions. 7 6 5 4 3 2 1 0 dps msc iis 0 0 1 0 0 1 0 1 15 14 13 12 11 10 9 8 ctrl msb 40h 7 6 5 4 3 2 1 0 ctrl lsb 1 7 6 5 4 3 2 1 0 1. parameter 0 0 0 0 prr mb1 mb0 ioc prr ... program ram/rom error mb1 ... internal memory error (bank 1) mb0 ... internal memory error (bank 0) ioc ... iom-2 clock not available no clock from the iom-2 interface is detected. it is recommended to reset the hardware. without clocks on the iom-2 interface no operation is possible.
_________________________________________________psb 7110 siemens aktiengesellschaft page 126 3.10 dsp program download in the isar psb 7110 v1.0 (development chip) the dsp program is downloaded through the host interface into the external memory. the mechanism is divided into several steps after which the isar is set to normal operation mode. step 1 isar hardware reset step 2 enable host interrupt (msk-bit in register 75h) (only if interrupt operation is intended) step 3 verify chip version number (no program download for rom versions) step 4 download of program code step 5 start of dsp software, switch from program download to normal operation 3.10.1 hardware reset after a hardware reset the isar is started in a download mode, i.e. it is not capable to perform any functions of the normal operating mode. therefore none of the mailbox coding for configuration, status and data exchange is valid. the external access pin ea# must be set to "1", to enable the boot program in internal rom for program download. 3.10.2 host interrupt enable if interrupt operation is intended, the mask bit msk (bit 2) in register 75h has to be set to "1" (all other bits set to "0"), to enable the indication of interrupts to the host. the program download can also be performed by polling since the reaction time of the isar is very short. in this case setting of the msk bit can be omitted and instead the host has to poll the status bit sta of register 75h.
_________________________________________________psb 7110 siemens aktiengesellschaft page 127 3.10.3 verify chip version number in this step the chip version number must be checked. the host should make sure that there is version 1.0 of the isar and not a rom-version of it, as in the latter case no program download is necessary and should be done. in this way only one version of a host software is necessary for an isar system that could use the functionality of either the download version or the rom version. version number request the host requests the chip version number by the following command: 7 6 5 4 3 2 1 0 dps msc his 0 0 0 1 0 1 0 0 15 14 13 12 11 10 9 8 ctrl msb 0 7 6 5 4 3 2 1 0 ctrl lsb 3 7 6 5 4 3 2 1 0 1. parameter 20h 7 6 5 4 3 2 1 0 2. parameter 0 7 6 5 4 3 2 1 0 3. parameter 1 version number response the isar provides the chip version number by the following response: 7 6 5 4 3 2 1 0 dps msc iis 0 0 0 1 0 1 0 1 15 14 13 12 11 10 9 8 ctrl msb 0 7 6 5 4 3 2 1 0 ctrl lsb 1 7 6 5 4 3 2 1 0 1. parameter ver ver ... version number xxxx 0001 : isar v1.0 (x = don't care) after a read request by the host, the isar will immediately respond with the version number, however, a timeout of 100ms can be installed to protect from software malfunctions resulting from system errors.
_________________________________________________psb 7110 siemens aktiengesellschaft page 128 3.10.4 program code download the program code is available in a binary file in which data is stored in 16 bit words. this file is provided together with the isar v1.0 device itself. the file has a logical structure where data is divided into individual blocks of program code and a header belonging to it. each block consists of contiguous program data and a header with the start address, the length of the block and a specific key word. if the dsp code consists of several blocks, the header of a new block follows right after the last word of the preceding block. the structure of several blocks would have the following format (each word is 16 bit). the byte sequence in each word is lowbyte / highbyte: 1. word startaddress block 1 block 1 2. length l of block 1 3. d-key of block 1 4. 1st program word 5. 2nd program word : : (l+3). l-th program word (l+4). startaddress block 2 block 2 (l+5). length m of block 2 (l+6). d-key of block 2 (l+7). 1st program word (l+8). 2nd program word : : (l+m+6). m-th program word (l+m+7). startaddress of block 3 block 3 : : note: only the 8 lsbs of the d-key are valid. transfer of d-key to start the download of one block, the key word (only lsb is valid) has to be written to the mailbox first, which is acknowledged by a response. 7 6 5 4 3 2 1 0 dps msc his 0 0 0 0 0 0 1 0 15 14 13 12 11 10 9 8 ctrl msb dkey 7 6 5 4 3 2 1 0 ctrl lsb 0 dkey ... d-key word the third word of the blockheader contains the d-key. only the least significant byte is written to the mailbox.
_________________________________________________psb 7110 siemens aktiengesellschaft page 129 acknowledgement for transfer of d-key the isar will acknowledge the transfer of d-key by the following message: 7 6 5 4 3 2 1 0 dps msc his 0 0 0 0 0 0 1 1 15 14 13 12 11 10 9 8 ctrl msb 0 7 6 5 4 3 2 1 0 ctrl lsb 0 after the transfer of the d-key by the host, the isar will immediately send a response.
_________________________________________________psb 7110 siemens aktiengesellschaft page 130 transfer of program blocks following the d-key and the appropriate response, the program block can be written to the mailbox. in one message up to 126 codewords (= 252 byte) of the program block can be transfered, so if the program block is larger than 126 words, it has to be divided into messages of a length between 1 and 126 words. the start address in every new message must be corrected in a way that it indicates the start address of the first program codeword of this message. 7 6 5 4 3 2 1 0 dps msc his 0 0 0 1 1 1 1 0 15 14 13 12 11 10 9 8 ctrl msb 0 7 6 5 4 3 2 1 0 ctrl lsb nom 7 6 5 4 3 2 1 0 1. parameter sam 7 6 5 4 3 2 1 0 2. parameter sal 7 6 5 4 3 2 1 0 3. parameter noc 16-bit program codewords starting from here in the sequence first msb, then lsb: 7 6 5 4 3 2 1 0 4. parameter msb of first program word 7 6 5 4 3 2 1 0 5. parameter lsb of first program word nom ... number of valid bytes in the mailbox the number of bytes in the mailbox = 2 * number of codewords + 3 the following parameters contain the startaddress, the number of program codewords in this message and the program codewords. the start address refers to the first program word (4th and 5th parameter). sam ... start address msb contains the msb of the program block start address. sal ... start address lsb contains the lsb of the program block start address. noc ... number of codewords number of 16-bit program words which follow, starting with the 4th parameter. one word means two entries to the mailbox as they are written separately in the sequence msb first and then lsb. the maximum number for noc is 126.
_________________________________________________psb 7110 siemens aktiengesellschaft page 131 acknowledgement for transfer of program blocks the transfer of program data is acknowledged by the following response: 7 6 5 4 3 2 1 0 dps msc iis 0 0 0 1 1 1 1 1 15 14 13 12 11 10 9 8 ctrl msb 0 7 6 5 4 3 2 1 0 ctrl lsb 0 after the transfer of program data by the host, the isar will immediately send a response, however, a timeout of 100ms can be installed to protect from software malfunctions resulting from system errors. all successive program blocks from the binary file are transfered in the same way by first writing the d-key of this block and then writing the codewords in messages of 1 to 126 words length.
_________________________________________________psb 7110 siemens aktiengesellschaft page 132 3.10.5 dsp program start after the program download is completed, the dsp program is started and the isar is switched from download mode to normal operation. this is performed by the following command: 7 6 5 4 3 2 1 0 dps msc his 0 0 0 0 1 0 0 0 15 14 13 12 11 10 9 8 ctrl msb 0 7 6 5 4 3 2 1 0 ctrl lsb 2 7 6 5 4 3 2 1 0 1. parameter ffh 7 6 5 4 3 2 1 0 2. parameter feh the parameters contain the startaddress fffeh of the dsp program. acknowledgement to dsp program start the isar sends the following response to the download finished indication. 7 6 5 4 3 2 1 0 dps msc his 0 0 0 0 1 0 0 1 15 14 13 12 11 10 9 8 ctrl msb 0 7 6 5 4 3 2 1 0 ctrl lsb 0 after the download finished indication by the host, the isar will immediately send a response, however, a timeout of 100ms can be installed to protect from software malfunctions resulting from system errors. download complete after that, the download is completed and normal operation mode is reached. from that point on the above given message codings are no longer valid.
_________________________________________________psb 7110 siemens aktiengesellschaft page 133 3.11 fax class 1 implementation this chapter gives more details on the implementation of fax group 3 on the isar psb 7110. it is expected that the controlling protocol residing on the host is either an implementation of the service class 1 command set (eia/tia-578) or itu-t t.30. it must be noted that for pump mode "fax modulations", the sart unit is not to be configured as described in 3.4 sart configuration. transmission and reception of hdlc framed and binary data is only controlled by pump control commands (see 3.6.2) and pump status events (see 3.7.3), i.e. the sart must not be reconfigured to hdlc or binary mode. however, data is transfered by use of sart data messages together with framing dependent control commands and status events (see 3.5 sart data). fax pump control pump control commands host ? isar 3.6.2 pump status events isar ? host 3.7.3 fax data transfer sart control commands - along with transmit data host ? isar 3.5.2 sart status events - along with receive data isar ? host 3.5.1 for configuration of the whole data path, first the buffer should be configured and then the pump and the iom-2 interface. configuration of sart and pump to the required framing and modulation scheme (e.g. hdlc framing and 300 bps/v.21ch2) is set by single pump control commands as mentioned above. further configuration data (modulation and silence duration) is passed by additional parameters to the pump control commands.
_________________________________________________psb 7110 siemens aktiengesellschaft page 134 3.11.1 summary of isar fax control commands cmd_fth starts transmission of hdlc frames. the additional parameter contains the modulation mode at which data is to be transmitted. it is not mandatory and can be omitted, if the previous setting of this parameter is still valid. cmd_frh starts reception of hdlc frames. the additional parameter contains the modulation mode at which data is to be received. it is not mandatory and can be omitted , if the previous setting of this parameter is still valid. cmd_ftm starts transmission of binary data. the additional parameter contains the modulation mode at which data is to be transmitted. it is not mandatory and can be omitted, if the previous setting of this parameter is still valid. cmd_frm starts reception of binary data. the additional parameter contains the modulation mode at which data is to be received. it is not mandatory and can be omitted, if the previous setting of this parameter is still valid. cmd_sil_det_on starts to wait a determined length of time. the additional parameter contains the silence duration which is to be waited. it is not mandatory and can be omitted , if the previous setting of this parameter is still valid. cmd_continue handshake message from the host to indicate that the host is ready to do the task (transmit/receive) which it selected before. cmd_escape this command is a regular escape in receive modes and a break in transmit modes. cmd_sil_det_off break of silence detection. cmd_halt shut down from fax pump idle state.
_________________________________________________psb 7110 siemens aktiengesellschaft page 135 3.11.2 summary of isar fax status events rsp_ready response to cmd_answer and cmd_originate line_tx_hdlc response to cmd_fth in order to indicate that the modulation has been established. line_tx_binary response to cmd_ftm in order to indicate that the modulation has been established. line_rx_hdlc response to cmd_frh in order to indicate that the modulation has been established. line_rx_binary response to cmd_frm in order to indicate that the modulation has been established. rsp_connect indication that the fax pump is ready to receive or transmit data. rsp_disc indication that the fax pump has turned off modulation after transmitting all pending data / after the host issues the command cmd_escape rsp_fcerror indication that the fax pump has detected a "wrong" modulation before it releases the event rsp_connect. rsp_sil_det indication that the prior selected duration of silence time has occured rsp_sil_det_off indication that the fax pump has received an "abandon silence time detection" command from the host. flags_detect indication that the fax pump has detected flags.
_________________________________________________psb 7110 siemens aktiengesellschaft page 136 3.11.3 procedure termination in response to control commands generated by the host, the fax pump invokes various procedures. another procedure cannot be invoked until the previous procedure has been terminated. procedure termination may either be indicated by the fax pump or commanded by the host. the table below shows the termination indications and commands for each of the procedures. prodedure indication of procedure termination (isar ? host) command for procedure termination (host ? isar) start as originator rsp_ready cmd_escape start as answerer rsp_ready cmd_escape hdlc transmit rsp_disc cmd_escape hdlc receive rsp_fcerror cmd_escape binary transmit rsp_disc cmd_escape binary receive rsp_fcerror cmd_escape wait for silence rsp_sil_det rsp_sil_det_off rsp_sil_det_off when no procedure is currently active, the fax pump is in an idle state. during the idle state, the command cmd_escape will be ignored by the fax pump, however, the host may issue the command cmd_halt to shut down the fax pump. this is normally done when a fax session has ended and the telephone connection is released.
_________________________________________________psb 7110 siemens aktiengesellschaft page 137 3.11.4 fax pump startup procedure the host configures the fax pump either as originator or answerer when a physical connection has been established. after initialisation, the fax pump responds with rsp_ready, indicating, that it is ready for the next procedure. at this point the host must issue either a command cmd_frh or cmd_fth depending upon if the host is answering or originating a facsimile connection. the interaction of the host and the faxpump is as shown in the flow charts for transmission and reception of hdlc and binary data. a t a o r a t d e s t a b l i s h p h y s i c a l c o n n e c t i o n , c o n f i g u r e p u m p t o f a x o r i g i n a t o r / a n s w e r e r e v e n t r s p _ r e a d y ? y e s n o a b o r t c h a r a c t e r f r o m d t e ? n o y e s g e n e r a t e c o m m a n d c m d _ h a l t t e a r d o w n p h y s i c a l c o n n e c t i o n i s s u e " o k " done p r o c e e d a s w i t h " a t + f t h = 3 " i f a n s w e r e r , o r " a t + f r h = 3 " i f o r i g i n a t o r figure 21 startup procedure
_________________________________________________psb 7110 siemens aktiengesellschaft page 138 3.11.5 hdlc transmission a host can control hdlc frame transmission during a fax group 3 session by issuing the command cmd_fth to the fax pump. hdlc transmission is specified by the t.30 procedure during the exchange of control information. some applications may alternatively implement hdlc framing directly, they would then use binary transmission for the transmission of their hdlc bit stream. a t + f t h = < m o d > g e n e r a t e c o m m a n d c m d _ f t h ( s e t p a r a m e t e r < m o d > ) e v e n t l i n e _ t x _ h d l c ? g e n e r a t e c o m m a n d c m d _ c o n t i n u e e v e n t r s p _ c o n n e c t ? n o y e s n o y e s i s s u e " c o n n e c t " e < d l e > < e t x > s e e n ? 5 s e c t i m e o u t e x p i r e d ? b n o y e s n o y e s y e s n o d a t a a v a i l a b l e f r o m d t e ? t r a n s f e r d a t a t o f a x p u m p m a s k f r a m e _ s t a r t o n t o 1 s t b y t e m a s k f r a m e _ e n d o n t o l a s t b y t e l a s t d a t a b y t e s e n t ? b n o y e s n o y e s y e s n o < d l e > < e t x > s e e n ? f i n a l f r a m e ? e figure 22 hdlc transmission
_________________________________________________psb 7110 siemens aktiengesellschaft page 139 3.11.6 binary transmission a host can control binary transmission during a fax group 3 session by issuing the command cmd_ftm to the fax pump. binary transmission is specified by the t.30 procedure during the exchange of image. a t + f t m = < m o d > g e n e r a t e c o m m a n d c m d _ c o n t i n u e g e n e r a t e c o m m a n d c m d _ f t m ( s e t p a r a m e t e r < m o d > ) e v e n t l i n e _ t x _ b i n ? e v e n t r s p _ c o n n e c t ? i s s u e " c o n n e c t " d a t a f r o m d t e ? 5 s e c t i m e o u t e x p i r e d ? t r a n s f e r d t e d a t a t o f a x p u m p b u f f e r e m p t y ? l a s t d a t a w o r d n u l ? < d l e > < e t x > s e e n ? b u f f e r e m p t y ? 5 s e c t i m e o u t e x p i r e d ? < d l e > < e t x > s e e n ? e b b e b n o y e s n o y e s y e s n o y e s y e s y e s n o n o y e s n o n o y e s n o n o y e s n o y e s figure 23 binary transmission
_________________________________________________psb 7110 siemens aktiengesellschaft page 140 3.11.7 hdlc reception a host can control hdlc frame reception during a fax group 3 session by issuing the command cmd_frh to the fax pump. hdlc reception is specified by the t.30 procedure during the exchange of control information. some applications may alternatively implement hdlc framing directly, they would then use binary reception for the reception of their hdlc bit stream. at+frh= generate command cmd_frh (set parameter ) event rsp_connect ? yes no event rsp_fcerror ? yes no no yes a generate continue event line_rx_hdlc ? yes no event rsp_fcerror ? abort character from dte ? yes no no yes a c issue "connect" transfer data from fax pump to dte no yes no no yes abort character from dte ? du_frame_end seen ? no_more_data flag seen ? send to dte a d b done yes no frame received correctly ? issue "ok" generate command cmd_escape no yes same frh command ? different command ? c abort character from dte ? send to dte send to dte no yes yes figure 24 hdlc reception
_________________________________________________psb 7110 siemens aktiengesellschaft page 141 3.11.8 binary reception a host can control binary reception during a fax group 3 session by issuing the command cmd_frm to the fax pump. binary reception is specified by the t.30 procedure during the exchange of image. a t + f r m = < m o d > g e n e r a t e c o m m a n d c m d _ f r m ( s e t p a r a m e t e r < m o d > ) n o y e s n o y e s n o y e s e v e n t l i n e _ r x _ b i n a r y ? e v e n t r s p _ f c e r r o r ? a b o r t c h a r a c t e r f r o m d t e ? a c g e n e r a t e c o m m a n d c m d _ c o n t i n u e n o y e s n o y e s n o y e v e n t r s p _ c o n n e c t ? e v e n t r s p _ f c e r r o r ? a b o r t c h a r a c t e r f r o m d t e ? a c i s s u e " c o n n e c t " t r a n s f e r d a t a f r o m f a x p u m p t o d t e n o y e s n o y e s n o _ m o r e _ d a t a f l a g s e e n ? a b o r t c h a r a c t e r f r o m d t e ? s e n d < d l e > < e t x > t o d t e a d s e n d < d l e > < e t x > t o d t e figure 25 binary reception
_________________________________________________psb 7110 siemens aktiengesellschaft page 142 3.11.9 call termination ath generate command cmd_halt teardown physical connection issue "ok" done figure 26 call termination 3.11.10 procedure terminations g e n e r a t e c m d _ e s c a p e i s s u e " o k " d o n e d c b a g e n e r a t e c m d _ e s c a p e g e n e r a t e c m d _ e s c a p e g e n e r a t e c m d _ e s c a p e i s s u e " e r r o r " i s s u e " f c e r r o r " i s s u e " n o c a r r i e r " d o n e d o n e d o n e i s s u e d u m m y d a t a b y t e w i t h n o _ m o r e _ d a t a f l a g s e t i s s u e " o k " d o n e e figure 27 procedure terminations
_________________________________________________psb 7110 siemens aktiengesellschaft page 143 3.12 datamodem automode operation automode selection is available based on eia/tia pn-2330. when enabled, the datapump will determine the communication standard supported by the remote modem and configure itself according. that means the modulation scheme and the data rate is automatically set without any host control. the following figures show the flowcharts corresponding to the dsp algorithm used in supporting automode originating and answering mode. after the host configures the datapump to datamodem modulations with automode enabled, it can request the selected modulation scheme from the isar as soon as the modulation has been established between both modems. connect to line answering mode send answer tone (2100 hz), monitor signals aa detected or ans timeout (3.6 s)? v.32bis aa send usb1, monitor signals start timer (1000 ms) timeout 1270 hz, 980 hz, s1, sb1 detected or timeout? bell 103 v.21 v.22 v.22bis 1270 hz 980 hz sb1 s1 timeout stop usb1, send ac, start timer (800 ms) aa detected or timeout ? v.32bis aa timeout stop ac, transmit 1650 hz, start timer (2000 ms) 1270 hz, 980 hz detected or timeout ? v.21 980 hz bell 103 1270 hz timeout stop 1650 hz, transmit 1300 hz, start timer (2000 ms) 390 hz detected or timeout ? v.32bis v.23 390 hz timeout s1, sb1 detected or timeout? v.22 v.22bis sb1 s1 send usb1, monitor signals start timer (2000 ms) timeout figure 28 automode answerer
_________________________________________________psb 7110 siemens aktiengesellschaft page 144 connect to line originating mode monitor signals 1650 hz, 1300 hz, 2225 hz, ac, usb1 or ans ? v.23 ac v.32bis v.21 1650 hz 1300 hz monitor signals, start timer (3100 ms) usb1, 2225 hz ac detected or timeout ? v.32bis ac send s1 / sb1, start timer (2140 ms) timeout s1/sb1 detected or timeout ? v.22 / v.22bis s1 or sb1 bell 103 timeout 1 second delay send aa, start timer wait for end of ans -> stop timer 1650 hz, 1300 hz, 2225 hz, ac or usb1 ? v.23 ac v.32bis v.21 1650 hz 1300 hz usb1, 2225 hz timer < 800 ms ? ans no yes figure 29 automode originator note: the signals indicated in both figures relate to the itu-t v.32bis specification.
_________________________________________________psb 7110 siemens aktiengesellschaft page 145 4. summary of messages
_________________________________________________psb 7110 siemens aktiengesellschaft page 146
_________________________________________________psb 7110 siemens aktiengesellschaft page 147
_________________________________________________psb 7110 siemens aktiengesellschaft page 148
_________________________________________________psb 7110 siemens aktiengesellschaft page 149 5. example configuration settings to give a better understanding how to program each of the parameters, some examples are given below for each of the functional blocks. the mechanism to transfer messages from the host to the isar is described in chapter 3.1.2. it should be noted, that the host interrupt status register (his) must only be written as the last register access for the message. buffer configuration set channel 1 to buffer base priority 5 and maximum message length of 32: control reg. msb = 05h control reg. lsb = 01h 1. parameter = 20h his = 64h set channel 2 to buffer base priority 3 without changing the maximum message length: control reg. msb = 03h control reg. lsb = 0 no parameters his = a4h set channel 2 to maximum message length 32 without changing the buffer base priority: control reg. msb = 0 control reg. lsb = 1 1. parameter = 20h his = a4h sart configuration set channel 1 to hdlc mode with regular i/o, "1" as interframe fill16 bit fcs length. in case of data underrun, fcs and final flag should be generated automatically (tx direction): control reg. msb = 03h control reg. lsb = 01h 1. parameter = 09h his = 65h set channel 2 to v.14 mode (synchronous modulation) with 25% overspeed range, even parity, two stop bits, 6 bit character size and a buffer flush timeout of 32: control reg. msb = 02h control reg. lsb = 02h 1. parameter = 5dh 2. parameter = 20h his = a5h
_________________________________________________psb 7110 siemens aktiengesellschaft page 150 pump configuration set channel 1 to faxmodulations in originating mode, 6 db transmitter output attenuation and calling tone enabled: control reg. msb = 81h control reg. lsb = 02h 1. parameter = 06h 2. parameter = 01h his = 66h note: if the pump is set to faxmodulations, the sart must not be configured as this is controlled by fax control commands which support implementation of fax class1 (see 3.11 fax class 1 implementation). set channel 1 to automode data modulation in answering mode with 8 db transmitter output attenuation with answer tone enabled and all modulation schemes are disabled except v.32bis with data rates up to 12000 bps only: control reg. msb = 02h control reg. lsb = 06h 1. parameter = 08h 2. parameter = 0 3. parameter = 82h 4. parameter = 0fh 5. parameter = f1h 6. parameter = 02h his = 66h iom-2 configuration set channel 1 to the first timeslot on the iom-2 interface with 8-bit timeslot length and regular switching of tx/rx paths. pcm data is a-law encoded and rate conversion is enabled (typical iom-2 configuration for pump modes fax, datamodem and halfduplex modulations): control reg. msb = 83h control reg. lsb = 05h 1. parameter = 10h 2. parameter = 0 3. parameter = 0 4. parameter = 0 5. parameter = 0 his = 67h set channel 2 to the third timeslot on the iom-2 interface with 8-bit timeslot length and mapping of transmitter and receiver to dd and du of iom-2 respectively. pcm data is m -law encoded. this configuration might be used e.g. for pump mode dtmf: control reg. msb = 84h control reg. lsb = 05h 1. parameter = 08h 2. parameter = 02h 3. parameter = 0 4. parameter = 02h 5. parameter = 0 his = a7h the configuration of the iom-2 interface has to make sure the the selected timeslots for channel 1 and 2 do not overlap, even if one of the channels is currently disabled by setting the iom-bit to 0.
_________________________________________________psb 7110 siemens aktiengesellschaft page 151 6. detailed register description 6.1 register address map address (hex) read write b7 b6 b5 b4 b3 b2 b1 b0 b7 b6 b5 b4 b3 b2 b1 b0 75 - - - - - msk - - - - - - - sta - - 61 host control register high isar control register high 60 host control register low isar control register low 58 - - - - - - - iia isar interrupt status (iis) 50 host interrupt status (his) - - - - - - - hia 4c mailbox i/o data 4a mailbox write address 48 mailbox read address 6.2 register description interrupt mask bit write address 75h value after reset: xxxx x0xx 7 6 5 4 3 2 1 0 - - - - msk - - msk ... interrupt mask all internal interrupt sources can be masked by setting msk to "0". in this case the interrupt is not indicated by activating the interrupt line, however it remains internally stored and pending until the msk bit is set to "1". interrupt status bit read address 75h value after reset: xxxx x0xx 7 6 5 4 3 2 1 0 - - - - sta - - sta ... interrupt status the sta bit indicates an interrupt status of the isar. if set to "1", an internal interrupt is pending.
_________________________________________________psb 7110 siemens aktiengesellschaft page 152 host / isar control register high write / read address 61h 7 6 5 4 3 2 1 0 the msb of the control word contains configuration, status or control information, depending on the message specified by the his / iis register. host / isar control register low write / read address 60h 7 6 5 4 3 2 1 0 the lsb of the control word contains the number of additional bytes in the mailbox, which depends on the message specified by the his / iis register. isar interrupt acknowledge bit write address 58h 7 6 5 4 3 2 1 0 - - - - - - - iia iia ... isar interrupt acknowledge after reading a complete message from the isar mailbox, the host sets iia to "1" to indicate to the isar, that the current message transfer is complete and a new message transfer may be started. isar interrupt status read address 58h 7 6 5 4 3 2 1 0 iis the isar interrupt status register (iis) contains the source of the interrupt, i.e. buffer 0, 1 or 2, the kind of indication (configuration, status or received data) and the indication source (buffer, sart, pump or iom-2). host interrupt status write address 50h 7 6 5 4 3 2 1 0 his the host interrupt status register (his) contains the destination of the transfered message, i.e. buffer 0, 1 or 2, the kind of command (request message, configuration, control or transmit data) and the functional block (buffer, sart, pump or iom-2).
_________________________________________________psb 7110 siemens aktiengesellschaft page 153 host interrupt acknowledge bit read address 50h 7 6 5 4 3 2 1 0 - - - - - - - hia hia ... host interrupt acknowledge when transfering a message to the isar mailbox, the final write access to the host interrupt register will automatically set the hia bit. the isar will reset hia as soon as the isar is capable to accept another message. mailbox i/o data write / read address 4ch 7 6 5 4 3 2 1 0 the mailbox contains configuration, status and control information in addition to the control register msb as well as transmit and receive data. the number of bytes in the mailbox is indicated in the control register lsb. mailbox write address write / read address 4ch 7 6 5 4 3 2 1 0 this register indicates the current write address on the mailbox buffer. before any data is written to the mailbox , the write address must be reset to 0 by the host. for any access to mailbox i/o data, the address pointer will be autoincremented and does not need to be programmed. this is the recommended way for sequential, fast access to the mailbox. for random access, the host has to reprogram the write address pointer. mailbox read address write / read address 48h 7 6 5 4 3 2 1 0 this register indicates the current read address on the mailbox buffer. before the mailbox contents of a message are read, the read address must be reset to 0 by the host. for any access to mailbox i/o data, the address pointer will be autoincremented and does not need to be programmed. this is the recommended way for sequential, fast access to the mailbox. for random access, the host has to reprogram the read address pointer.
_________________________________________________psb 7110 siemens aktiengesellschaft page 154 7 . hardware and software support for system development based on isar psb 7110, siemens provides a hardware and software package to allow for quick design and fast product to market. moreover, certain software protocols especially related to fax and modem or isdn protocols require very specific knowledge that could cause a long term development phase. the isar reference board package provides a complete software/hardware solution for isdn and analog data communication under windows 95 and windows 3.x . it consists of: isar reference board the isa slot card (see figure 30) shows a complete hw solution for s- and u-interface together with plug and play host interface. iec-q v5.1 peb 2091 iom ? -2 s 0 isar reference board v 2.0 isa-slot-connector analog inout u k0 isac-s te psb 2186 passive interface arcofi-sp psb 2163 isar psb 7110 2 x 32 kbyte sram address/data interface and reset logic national midway nm95ms14p plug 'n play iom ? -2 address & data & reset cs & interrupt data address interrupt & control speaker figure 30 isar reference board capi (common isdn applications interface) the capi provides a hardware independent interface to control the dialling and the b channel protocol. today, this message based interface is the mandatory standard for isdn pc-cards in europe. the siemens capi includes some extensions to control some special hardware features over this interface.
_________________________________________________psb 7110 siemens aktiengesellschaft page 155 com driver this driver simulates an old fax class 1 or data modem on two com ports. one com port can be used for digital and analog connections. the other com port can only be used for digital connections. the com driver is designed for isar-boards. the driver includes the modem datapump controlling for the isar. therefore the driver uses the direct chip access addendum of the capi (defined by the siemens ag). on hw designs without an isar (e.g. boards based on hscx-te psb 21525) the com driver accesses only digital connections. the digital protocol handling is realised in the capi driver. tools the software is ready to use on the isar reference board with installation and configuration tools. additionally there is an example source code for the download of the dsp software. please contact your siemens sales office to get further information on the hard- and software package which is available for isar psb 7110.
_________________________________________________psb 7110 siemens aktiengesellschaft page 156 8. electrical specification 8.1 absolute maximum ratings parameter symbol limit values unit ambient temperature under bias t a 0 to 70 c storage temperature t stg -65 to 125 c supply voltage v dd -0,5 to 4,2 v supply voltage v dda -0,5 to 4,2 v supply voltage v ddp -0,5 to 6,0 v voltage of pin with respect to ground: xtal1, xtal2, vref, radj v s -0,4 to v dd +0,5 v voltage of any other pin with respect to ground v s if v ddp <3v: -0,4 to v dd +0,5 if v ddp >3v: -0,4 to v ddp +0,5 v v note: stresses above those listed here may cause permanent damage to the device. exposure to absolute maximum rating conditions for extended periods may affect device reliability. 8.2 recommended operating conditions v dd = 3,4 to 3,8 v; v ddp = 4,5 to 5,5 v, v ss = 0 v v dda = 3,4 to 3,8 v, v ssa = 0 v; 8.3 dc characteristics conditions: see above (recommended operating conditions); t a = 0 to +70c. all pins except xtal1, xtal2, vref, radj: parameter symbol limit values unit test condition min max high-level input voltage v ih 2,0 v low-level input voltage v il 0,8 v high-level output voltage v oh 2,4 v i oh =-400 a low-level output voltage v ol 0,45 v i ol =7 ma pins du, dd (50 pf) i ol =5 ma pins ca(0:15), cd(0:15), crd#,cwr#,cps#,cds# (30 pf) i ol =2 ma all others (30 pf) input leakage current i li -1 ma 2 a 0 v < v in < v dda (radj) input leakage current i li - 1 2 a 0 v < v in < v dda (vref) input leakage current i li -11 11 a 0 v < v in < v dda (xtal1) input leakage current i li -1 6 a 0 v < v in < v ddp (cm1) input leakage current i li -6 1 a 0 v < v in < v ddp (ale, wr#) input leakage current i li -80 1 a 0 v < v in < v ddp (reset) input leakage current i li -1 1 a 0 v < v in < v ddp (all other pins) output leakage current i lo -1 1 a 0 v < v out < v ddp vdd+vdda supply current idds 170 ma vddp supply current iddps 120 ma
_________________________________________________psb 7110 siemens aktiengesellschaft page 157 the power supply on voltage on v dd -v ss and v dda -v ssa can be applied before or after the power supply on v ddp /v ssp without any damage to the circuit. applying voltages to signal pins when power supply is not active (circuit not under bias) may cause damage - refer to paragraph "absolute maximum ratings". when power supply is switched on, the pads do not reach their stable bias until after 2 s (maximum). 8.4 capacitances parameter symbol limit values unit test condition min max input capacitance c in 7 pf i/o capacitance c i/o 7 pf load capacitance c l 50 pf xtal1,2 8.5 oscillat or circuit mode of vibration: basic harmonic mode of vibration: 3rd harmonic
_________________________________________________psb 7110 siemens aktiengesellschaft page 158 the value for c ld depends on the parameters of the selected crystal and is derived from the following equation: c ld = 2 x c l - c in where c l is the crystal specific load capacitance (see 8.6) and c in is the input capacitance for xtal1 (see 8.4). example: c l = 20 pf ? c ld = 33 pf 8.6 xtal1,2 recommended typical crystal pa rameters mode of vibration: basic harmonic parameter symbol limit values unit motional capacitance c 1 17 ff shunt c 0 5 pf load c l 20 pf resonance resistor r r 50 ohm mode of vibration: 3rd harmonic parameter symbol limit values unit motional capacitance c 1 0.9 ff shunt c 0 3 pf load c l 20 pf resonance resistor r r 70 ohm
_________________________________________________psb 7110 siemens aktiengesellschaft page 159 8.8 ac characteristics 8.8.1 testing waveform conditions as above (recommended operating conditions) at t a = 0 to 70 c. inputs are driven to 2,4 v for a logical "1" and to 0,4 v for a logical "0". timing measurements are made at 2,0 v for a logical "1" and 0,8 v for a logical "0". the ac testing input/output waveforms are shown in the figure below. 8.8.2 parallel host interface timing host interface read cycle host interface write cycle
_________________________________________________psb 7110 siemens aktiengesellschaft page 160 address timing interrupt release timing parameter symbol limit values unit min max ale pulse width taa 50 ns address setup time from ale tal 15 ns address hold time from ale tla 10 ns address latch setup time to wr#, rd# tals 0 ns ale guard time tad 15 ns rd# pulse width trr 110 ns data output delay from rd# trd 110 ns data float from rd# tdf 25 ns rd# control interval tri 70 ns wr# pulse width tww 60 ns data setup time to wr# x cs# tdw 35 ns data hold time from wr# x cs# twd 10 ns wr# control interval twi 70 ns interrupt acknowledge to high-impedance tiat 100 ns
_________________________________________________psb 7110 siemens aktiengesellschaft page 161 8.8.3 external memory interface timing external memory interface write cycle external memory interface read cycle parameter symbol limit values unit min max write cycle time twc 10 ns address setup time tas 0 ns address valid to end of write taw 9 ns write pulse width twp 9 ns write recovery time twr 0 ns data valid to end of write tdw 5 ns data hold time tdh 0 ns read cycle time trc 10 ns address access time taa 10 ns input hold from address change tih 0 ns notes: 1. test conditions shown below assuming output loading specified in figure 31 2. tested with the loading in figure 32.
_________________________________________________psb 7110 siemens aktiengesellschaft page 162 ac test conditions: parameter unit input pulse level 0.45v to 2.4v input rise and fall times 3 ns input and output timing and reference levels 1.5v output load see figures below figure 31 figure 32
_________________________________________________psb 7110 siemens aktiengesellschaft page 163 8.8.4 iom-2 interface timing iom-2 timing with double rate dcl: parameter symbol limit values unit min max dcl period tp 244 ns dcl high twh 100 ns dcl low twl 100 ns frame sync setup tfss 40 ns frame sync hold tfsh 40 ns output data from high impedance to active tozd 100 ns output data delay from clock todd 100 ns output data from active to high impedance todz 80 ns input data setup tids 20 ns input data hold tidh 40 ns 8.9 esd capability in contrast to the general siemens quality profile, the isar v1.0 pins are only capable of 1kv esd (electro static discharge).
_________________________________________________psb 7110 siemens aktiengesellschaft page 164 9 . package outline p-tqfp-100 package with size 14 x 14 mm, pitch 0.5 mm, height 1.4 mm.

▲Up To Search▲

Price & Availability of PSB7110-FV10

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