ISER12 Software Manual - esd electronics, Inc.
Contents
1. 16600 9 5 ooo em eso 30 so e io 88 7 39 x 7 so I 198 scm ns s 190 so Ours Ls seo iss o 5 ims zr 5 so turis acne 3 o 109 16 106 Foo 12 16 80 Table 1 5 4 Buffer Channels 1 to 10 26 buffer for channel 2 26 buffer for channel 3 26 buffer for channel 4 26 buffer for channel 5 14 VME ISER12 Software Manual Rev 1 0 Introduction 1 6 Buffer Allocation 1 6 1 Memory Allocation via Semaphore For a multitasking and multiuser memory management the memory allocation ensues via a semaphore which can be accessed by the indivisible assembler command TAS Beginning with the corresponding default channel the semaphore of the channels is occupied On a successful access the corresponding channel is occupied If not the next buffer must be determined by ionext Abort and wait conditions may be a certain number of unsuccessful accesses or the detection of wrap around new pointer lt old pointer After executing the I O instruction either the slave server returns the channel by releasing the semaphore or the master must decide when the channel will be available again 1 6 2 Example of a Buffer Allocation All2. parameterchamel3 __ Fo 4 a o rant parameterchannel 4 Foe s s o 94 parameterchamnel ese omo s 9 s TM parameter channel 6 7 7 o s omo s s o so parameter camels o Leo o o so parameiercnamero Foo a 10 o so Pakan parameter chamei 10 Table 1 5 2 Interrupter Channel and Parameter Channels Buffer Address Channel Header _ oO Header DEZ HEX HEX HEX HEX HEX 7778 oso D f 2 16700 TEUFGS 6 _ Foceso 19 19800 vansmicourer 06 _ 14 s _ 400 receive butler Fors 18 f 5 1c o Table 1 5 3 Transmit and Receive Buffer VME ISER12 Software Manual Rev 1 0 13 Introduction Buffer Address Channel Hende O Header DEZ HEX HEX HEX HEX HEX CEET a oe s surris so ioo 35 2 1996 se BUFF ERE Lus s2 2 vu so 55 3 so eme 3 wo so 4 10 so ES Lupo 3 so Faso sr
3. 17 2 2 Description of the Parameter Channel 19 2 2 1 Structure of the Parameter Channel 19 2 2 2 Description of the 20 2 2 3 Command Handing over via the Parameter Channel 25 2 3 Description of the Interrupter Channel 26 2 3 1 Structure of the Interrupter Channel 26 2 3 2 Description of the Interrupter Channel Cells 28 3 The local VME ISER Server on e ADI eo I Bele d PURSE EUR NIS 31 3 1 Functional Description of the local VME ISER Server 31 T Output Channels e zer we Whe PE EUER VUE 31 Input Channels Lube er T Ud Ur QN 31 3 13 Interrupt ah De UE Meo LaL qa 32 Timie Qut coa kel epu iG d ERU ERE ee a 32 3 1 5 Receive Error 4 iieis utet 34 3 2 Examples for the VME ISER Server evi er e DOR Rv ere xps 35 3 2 1 Example Initialization of the VMEbus Master 35 3 2 2 Example Data Output to Interface 2 without IRQ 36 3 2 3 Example Data Input from Interface 8 37 3 2 4 Example Setting the
4. 0 no receiver overrun recognized Bit 3 1 Rx time out occurred 0 no Rx time out occurred Bit 2 1 character in the local interrupt buffer 0 no character in the local interrupt buffer Bit 1 1 receiver has set handshake to disabled 0 receiver has set handshake to enabled Bit 0 1 receiver disabled 0 receiver enabled errlog enable disable Rx error function read only errlog 00 no Rx error function errlog FF Rx error function enabled errlog is set by the command receive errlog errlog is reset by receive on and receive off 24 VME ISER12 Software Manual Rev 1 0 Channel Description 2 2 3 Command Handing over via the Parameter Channel Via the parameter channel commands can be handed over as well as parameters of the data buffer For this purpose the parameter channel is entered into the Tx server queue and thus being executed synchronously The commands clear and reset are already executed before being entered into the queue The corresponding command is entered into the location iocmmd in the header of the parameter channel Already implemented commands 0000 paraxy 000C clear 000D reset 000E reset Status 0050 receive Off 0051 receive On 0052 receive Errlog FFFF sync Description of the commands paraxy changes interface parameters as e g baud rate handshake clear deletes the locally stored RX data resets the output queue changes no interface p
5. determine the slave interrupt behaviour If ioilev and ioivec 0 then the slave will not generate an interrupt at the end of the instruction corresponding to the channel but only iosema is set analogously Otherwise an IRQ on the VMEbus with the IRQ level ioilev 1 7 will be generated by the IRQ vector ioivec 00 FF contains the consecutive numbering of the channels For the interrupter channel iobnum has a value of 0 VME ISER12 Software Manual Rev 1 0 9 Introduction iolen iobuff iorecl iostio ioldn iomode 10 contains the available data buffer length If the data buffer 15 located within the channel structure default then jolen 500080 128 bytes or 400 respectively External data may have an unlimited length is the pointer to the data buffer of the corresponding pointer channel As default iobuff points to iodata At external data buffers iobuff may point to any local address so that addressing the data buffer must use the actual content of iobuff determines the number of valid data in the data range number of data to be sent or received If iorecl is negative i e the MSB is set the transmission has been stopped with error error codes 8007 time out 801E framing error 801F overrun error 8020 parity error 8046 break detected is not yet supplied and is preset to 500 contains the channel server no 1 10 supports the setting of the data direction transmi
6. ne pl Protocol has been finished without errors m characters have been transmitted to the Rx buffer The VME ISER server returns the Rx buffer to the VME master 8000 m4 8000 ne mi Protocol has been finished with errors m characters have been transmitted to the Rx buffer The VME ISER server returns the Rx buffer to the VME master 40 VME ISER12 Software Manual Rev 1 0 The local VME ISER Server Data Structure irbuf Interrupt Buffer Each VME ISER channel has got an irbuf structure via which the Tx and Rx transfers are processed Into this structure the received data for instance 15 filed It consists mainly of four parts pointer and counter for Tx operation queue for Tx operation 32 entries pointer and counter for Rx operation FIFO for Rx operation 1024 bytes Address Offset HEX 2 0 0000 cescer 0010 cns went T _ 0080 Interrupt B uffer irbuf 04A0 Interrupt B uffer irbuf Table 3 3 1 Relevant cells of the interrupt buffer Usually the following structure elements of the interrupt buffer satisfy the Rx protocol Name Offset eae Meaning HEX ganisa absolute address of the waiting Rx buffer iobuff irwp 18 won current write pointer in the data range irbuf be set by the protocol to synchronise irrp current read pointer in the data range irbufO must be word d me by the protocol c x flags to control
7. 9 1 4 540 RCHACHA EQU 10 1 4 40 MOVEA L CRDADR A0 MOVE L RXBUF DO TAS iosema A0 DO L wait LEA 0 A0 D0 L A0 Now contains the abso channel DO contains the MOVE W anzdata 01 MOVE W 0 1 1 1 0 05 101 Senf vec A0 MOVE W 52700 0mode A0 MOVE L 0 1 0 activate VME ISER server MOVEA L IRCH A2 ADDA L CRDADR A2 TST L RCHACH8 A2 BNE wait L 00 RCHACH2 A2 MOVE W DO x VEER wait until occurring of t MOVE W iorecl A0 01 BEQ exit B MI error SUBQ 1 D1 MOVEA L destin A2 MOVEA L iobuff A0 1 ADDA L CRDADR Al loopl MOVE B 1 2 DBF Dl loopl MOVE B 0 iosema A0 Efe ready error ANDI W 7FFF 01 error routine VME ISER12 Software Manual Rev 1 0 The local VME ISER Server Server 1 Server 2 offset offset Server 9 Server 10 offset offset base address first channel search for free channe see above channel free wait ute address of the actual board relative address maximum number of the data bytes to be read enter into header level 5 vector 60 input end at normal input Cr pointer to data interrup absolute entry free wait enter relative channe write any as a trigger he special IRQ number of received data data received
8. address because of DBxx destination of the data source of the data relative address absolute transfer data bytes release channel mask error number 37 The local VME ISER Server 3 2 4 Example Setting the Parameter of Interface 1 TCHACHI TCHACH2 TCHACHA txbs rxbs chris stpls parts hnds txb rxb chr st pl part hnd 38 EQU 1 1 4 offset server 1 EQU 2 1 4 offset server 2 EQU 10 1 4 offset server 10 EQU 0 desired value Tx Baud EQU txbs41 EQU rxbs l E QU christl EQU stplstl EQU parts l EQU 40 actual value Tx Baud EQU txbtl EQU rxb l EQU chri EQU stpl 1 EQU part 1 MOVEA L CRDADR 0 base address MOVE L PARAI1 DO jparameter channel relative ADDA L D0 A0 absolute address MOVEA L iobuff A0 1 data range parameters ADDA L CRDADR Al absolute address e g set tx baud rate to 300 Baud set rx baud rate to 600 Baud set handshake to XON XOFF MOVE B 7 txbs A1 Baud 300 MOVE B 6 rxbs A1 rx Baud 600 MOVE B 1 hnds Al XON XOFF handshake All other parameters remain unchanged MOVE W 4700 i omode Al output mode MOVE W 0 ioilev Al np IRQ MOVE W 0 iocmmd A1 mode Init parameter enter parameter channel into server queue MOVEA L RCH A2 jpointer to data interrup ADDA L CRDADR A2 absolute TST L 2 entry free BNE wait wait MOVE L 00 TCHA
9. available to the input server then the incoming data will be temporarily stored in the interrupt buffer As long as there are still data in the interrupt buffer an input channel linked in by the VME master will be filled with these data otherwise incoming data are directly transferred into the input channel Exceptions if an input channel with iomode X X08 is processed all data up to now received in the interrupt buffer are deleted and only data received from now on will be handed over at the next READ instruction If iofnam is set to ASCII SCAN data from the interrupt buffer will be handed over until reaching the indicated end condition If the interrupt buffer is clear the end condition will also be set Ifiofnam is set to ASCII PROT the registered protocol will be executed VME ISER12 Software Manual Rev 1 0 31 The local VME ISER Server As a default the interrupt buffer has a length of 1 kbyte The receive handshake is managed corresponding to the free space of the interrupt buffer If the interface is equipped with a handshake at a remaining space of about 10 the handshake is disabled If the free space is about 70 again the handshake will be enabled again 3 1 3 Interrupt Operation If the user needs a VME interrupt from the VME ISER after completing an instruction e g input channel filled or output channel transferred with MODMWA l in iomode then the desired VME interrupt level as well
10. the remaining 7 bits indicates the time out time in multiples of 10 msec e g iotout 0X no time out iotout 85 time out after 50 msec iotout FF time out after 1 2 sec 32 VME ISER12 Software Manual Rev 1 0 The local VME ISER Server Itis possible to set a global time out for all interfaces via the parameter channel which can be different for transmit and receive operation The range of values is 0 32767 the unit is 1 msec If rtime0 or ttime 0 then the corresponding time out function is disabled ttime time out for transmit operation rtime0 time out for receive operation for the first character rtimel time out for receive operation for any further character The time out function is retriggerable i e if a transmit or receive operation takes place the corresponding counter will be reset The chronological interval of these operations is variable FIFO operation and corresponds to the duration of at least one but as a maximum of 8 character times e g 1200 Baud 1 chartime 1 8 1 1200 8 3 msec 8 char times 66 6 msec i e a time out value of less than 67 msec cannot be recommended Moreover in the receive operation it is distinguished between first time out and character to character time out i e the time between instruction input and first character arrival may be longer than the character to character time while the active transfer Actions when a time out occurs If a time out
11. 0B0 00 00 soe 80FO 00 00 00 00 00 00 00 00 00 00 00 00 Table 2 3 1 Interrupter Channel VME ISER12 Software Manual Rev 1 0 27 Channel Description 2 3 2 Description of the Interrupter Channel Cells addr_paral Start addresses of the parameter channels to 10 adr paraA TCHACHA Entries for the Tx server Offset Cell HEX Entry Channel for relative to Tx Server iodata TCHACHI 00 TCHACH3 08 TCHACHS Table 2 3 2 Entries for the Tx server 7 10 Triggering of the local VME ISER Tx Irq s To activate the VME ISER TXx server task which executes the entries in the interrupter channel an access to the local IRQ trigger address must take place This access must ensue as write word to the board relative address tirtrig 080002 28 VME ISER12 Software Manual Rev 1 0 Channel Description RCHACHI RCHACHA Entries for the Rx server Offset Cell HEX Entry Channel relative to for Rx Server iodata RCHACH9 60 Table 2 3 3 Entries for the Rx server 7 10 Triggering the local VME ISER Tx Irq s To activate the VME ISER Rx server task which executes the entries in the interrupter channel an access to the local IRQ trigger address must take place This access must ensue as write word to the board relative address rirtrig 080006 VME ISER12 Software Manual Rev 1 0 29 Channel Description 30 VME ISER12 Soft
12. CH1 A2 enter relative channel address MOVE W write any as a trigger ready VME ISER12 Software Manual Rev 1 0 The local VME ISER Server 3 3 User Protocols 3 3 1 Function Description The user has got the possibility to implement an individual Rx protocol or Rx filter for each channel In order to do this the protocol program has to be loaded in an available RAM area of the VME ISER such as 520000 3FFFF and the entry address of the local user program has to be made available to the local ISER server This can be achieved by specifying the entry address of the respective channel in cell ioentr in the parameter channel If the VME master now requests an Rx element via iofnam P ROT the received characters are buffered in the interrupt buffer followed by the execution of the specified protocol which can check the buffered chain of characters and possibly transmit them to the requested channel If iofnam of the requested channel unequals P ROT the data is transferred normally by means of the standard VME ISER server If iofnam of the requested channel equals P R OT and if the protocol entry ioentr is not available the Rx request will be ignored Itis very important to ensure that the basic configuration of the channel via the parameter channel does not cause conflicts with the requested protocol such as a software handshake in binary protocols 3 3 2 Conditions for the Use of User Specific Rx Protocols F
13. Parameter of Interface 1 38 3 I USET Protocols 4L coh LE Ls ud aL abu uad 39 3 3 1 Function 39 3 3 2 Conditions for the Use of User Specific Rx Protocols Filters 39 3 3 3 Register and Structure Declarations 40 3 3 4 Protocol Embedding for Rx Operation 43 VME ISER12 Software Manual Rev 1 0 1 VME ISER12 Software Manual Rev 1 0 Introduction 1 Introduction 1 1 General This manual describes the serial VMEbus interface boards VME ISER8 and VME ISER12 A large part of the descriptions is valid for the VME ISER8 and VME ISER 12 board In the following both boards are summarized under the concept VME ISER Special data which concern only one of these boards are pointed to in corresponding places The VME ISERS is an intelligent interface board for the VMEbus which locally supervises 8 asynchronous and 2 optionally synchronous or asynchronous serial interfaces The VME ISER12 has got the same number of interfaces as the VME ISERS Two transition modules of type ESP360 can optionally be attached to VME ISER 12 In coherence with these modules the VME ISER12 offers 10 asynchronous and 2 synchronous asynchronous serial interfaces The user operates to a linear memory and is relieved of I O supervision tasks by the local CPU The memory accessible to t
14. SER12 Software Manual Rev 1 0 35 The local VME ISER Server 3 2 2 Example Data Output to Interface 2 without IRQ TCHACHI 2 TCHACHA 36 EQU 1 1 4 offset server 1 EQU 2 1 4 offset server 2 EQU 9 1 4 offset server 9 EQU 10 1 4 offset server A MOVEA L CRDADR 0 base address MOVE L TXBUF2 first channe BSR srchbf search for free channe see above BNE wait no channel free wait Now A0 contains the absolute address of the actua channel DO contains the board relative address MOVEA L iobuff A0 Al rel address data buffer ADDA L CRDADR A1 absolute address MOVE W anzdata D1 number of data bytes MOVE W Dl iorecl A0 enter into header SUBQ 1 D1 because of DBxx L source A2 pointer to transmit data MOVE B A2 1 transfer to VME ISER DBF Dl loop MOVE W 0 ioilev A0 ioilev ioivec 0 MOVE L 0 iofnam AQ clear fname MOVE W 4700 i10mode A0 output no wait activate VME SER server pointer to data interrup ADDA L CRDADR A2 absolute TST L 2 2 entry free BNE wait No wait MOVE L DO TCHACH2 A2 enter relative channel address MOVE W DO TIRTRIG write any as a trigger ready VME ISER12 Software Manual Rev 1 0 3 2 3 Example Data Input from Interface 8 RCHACHI EQU 1 1 4 40 RCHACH2 EQU 2 1 4 40 RCHACH9 EQU
15. VME ISER12 Intelligent Board for 12 serial Interfaces Software Manual VME ISER12 Software Manual Rev 1 0 The information in this document has been carefully checked and is believed to be entirely reliable esd makes no warranty of any kind with regard to the material in this document and assumes no responsibility for any errors that may appear in this document esd reserves the right to make changes without notice to this or any of its products to improve reliability performance or design esd assumes no responsibility for the use of any circuitry other than circuitry which is part of a product of esd gmbh esd does not convey to the purchaser of the product described herein any license under the patent rights of esd gmbh nor the rights of others esd electronic system design gmbh Vahrenwalder Str 205 30165 Hannover Germany Phone 49 511 372 98 0 Fax 49 511 372 98 68 E mail infoGesd electronics com Internet www esd electronics com USA Canada 7667 W Sample Road Suite 127 Coral Springs FL 33065 USA Phone 1 800 504 9856 Fax 1 800 288 8235 E mail sales esd electronics com VME ISER12 Software Manual Rev 1 0 Document file I texte Doku MANUALS VME MSER12 ISER12_01s en6 Date of print 31 10 2000 Described Firmware Version Changes in the Chapters The changes in the user s manual listed below effect changes in the hardware as well as changes in the description of the fa
16. a lodata lodata lodata lodata lodata only for Rx Buffer Table 2 1 1 Internal Channel Structure valid for all types of channels VME ISER12 Software Manual Rev 1 0 17 Channel Description Address Offset HEX 0 4 6 8 A C E 00 00 eF sofo 00 sa oo oo oo o 00 Es o0 oo oo oa o0 8B20 01 00 o 00 00 00 00 00 8830 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 8840 8850 00 00 00 00 0 00 00 00 00 00 00 00 00 00 8860 00 00 0 00 00 00 00 00 00 00 00 00 8870 00 00 00 00 00 00 00 00 00 00 00 00 00 Table 2 1 2 Default Channels example T BUF 01 00 00 00 0 00 0 18 VME ISER12 Software Manual Rev 1 0 Channel Description 2 2 Description of the Parameter Channel 2 2 1 Structure of the Parameter Channel To each serial interface channel a so called parameter channel is assigned In the data range of this parameter channel the actual status of the interface is stored which can be read completely transparently by the VME master The parameter channel is also necessary for the parameterization of the interface For this the actual parameters are input at the corresponding sections of the parameter structure and the parameter channel is handed over to the VME ISER server as transmit channel see also output channels on page 31 By this a synchronization with running trans
17. arameters reset default initialization of the channel reset stat resets the error flags in txstat and rxstat receive off switches the receiver off receive on switches the receiver on no end by error receive errlog switches the receiver on enables the end by error function sync entering the parameter channel as an output without data no data transfer no change of the interface status At heavy duty transmit operation without wat forready MODMWA in iomode 0 the condition output queue full will easily become true thus the master must check for output queue ready in the polling mode However after the next transfer the queue is full again At this condition we recommend to execute a dummy transfer with wait for ready and an activated interrupt mode Thus after a complete execution of the queue the total memory is available to the master again VME ISER12 Software Manual Rev 1 0 25 Channel Description 2 3 Description of the Interrupter Channel 2 3 1 Structure of the Interrupter Channel The task of the interrupter channel is to establish a connection between the VME master program and the local server After allocating a data channel and entering the parameters into the header of this channel the master program must hand over the channel to the local server For this the interrupter channel makes available the cells to TCHACHA and to RCHACHA in its data buffer The master program ent
18. as the interrupt vector must be entered into the cells ioilev and ioivec of the corresponding data channel The VME ISER then generates the specified interrupt If no interrupt generation is desired iolev must be set to 0 In his interrupt routine the user must confirm the interrupt The interrupt confirmation is done as follows The 2 LSB of the interrupt vector determine the bit position in the interrupt acknowledge register This bit must be set to 1 as an acknowledge The board relative address of this register iack is 08601B e g nterrupt Entry MOVE B ioivec D0 actual interrupt vector ANDI B 4503 00 Masking bit 2 to 7 BSET DO iack iserbase Set bits on VME ISER further interrupt routine Setting the IACK bit should happen as soon as possible because on the VME ISER the generation of a new IRQ is prevented as long as the actual interrupt was not confirmed 3 1 4 Time Out Optionally it is possible to abort transmit and receive instructions after a preset time 7 Out Time setting is done via the channel parameter iotout or via the parameters rtime0 rtimel and ttime in the parameter channel The value in iotout corresponds to the channel being executed while rtime0 rtimel and refer to the interface in general The content of iotout overdrives the content in the parameter channel iotout If bit 7 of iotout equals to 0 then a time out via lt iotout gt is disabled If bit 7 equals to 1 then the value of
19. cts only Chapter Changes versus previous version First version Further technical changes are subject to change without notice VME ISER12 Software Manual Rev 1 0 VME ISER12 Software Manual Rev 1 0 Content Content I Introductio fy eo oy ups Ue x poe IN e ERU S Ri SS Visa e ee d ga SSA 3 General hehe da CLA EL EG AQ ars 3 1 2 Channel Overview ves exer sos ee ER exe Rf o eg eue OE Sta ne 4 IX T Channel Types iuuenes Eden qe d po a PERRO e 4 1 2 2 Tasks of the VME Master Servers 4 1 3 Initialization of the System 5 1 4 Th Channel cua sey act Pee hee ee en EE 6 1 4 1 Chaining ot the Channels ud orc e NEE Mex eR 6 1 4 2 Description of the individual Channel Locations 8 1 5 Data Channel Management 12 LSet Genetal E CoP Ese PEELE ew hea EAE 12 1 5 2 Overview to the Channels with Chaining via 12 Lo Buffer Allocation ssn soy EE LA bes i 15 1 6 1 Memory Allocation via Semaphore 15 1 6 2 Example of a Buffer Allocation 15 2 Channel Description 17 2 1 Description of the Data Channels
20. d Note The VME ISER 2 offers a better resolution for the setting of the absolute baud rate than the VME ISER8 because of an additional fundamental frequency to generate the baud rate VME ISER12 Software Manual Rev 1 0 21 Channel Description protoks Protocol mode of channel 9 and 10 UART mode all parameters of the parameter channels 9 and 10 are relevant HDLC mode only the parameter of the channels 9 and 10 which are necessary for the synchronous transmission have to be considered rtime02 txclkmods rxclkmods txbvs encode Table 2 2 3 Protocol mode encodes Signal coding of the serial Interfaces Only the format NRZ No Return to Zero is supported encodes at the moment 22 VME ISER12 Software Manual Rev 1 0 Channel Description Only readable parameter Following parameters serve as status information cannot be written by the user txb rxb chrl stpl part hnd rtime0 rtimel txclkmod rxclkmod txbv rxby protok encode rxfifo rxtout resrv spchrl spchr4 VME ISER12 Software Manual Rev 1 0 transmitter baud rate receiver baud rate Index actual value baud Index actual value baud Index actual value cri bits character Index actual value stpi number of stop bits Index actual value pari parity type Index actual value Andi handshake mode assignment of the indices see page 20 Receive time out for the first character in msec Receive charac
21. d rate 20 23 transmitter status 24 triggering 28 29 ttime 33 Tx buffer 12 13 Tx server 28 txclkmods 21 U UART mode 22 user protocols 39 VME ISER12 Software Manual Rev 1 0 Index V VMEbus interrupt 4 IRQ Level 8 IRQ Vektor 8 master 19 master program 26 31 master server 4 VME ISER12 Software Manual Rev 1 0 47
22. de 20 23 HDLC mode 22 header ioback 9 iobnum 9 iobuff 10 iocmmd 9 iodata 11 iofnam 11 iofor 9 iofree 11 ioilev 9 ioivec 9 ioldn 10 iolen 10 iomode 10 ioname 9 ionext 9 iorecl 10 iorxIn 11 iosema 9 iostat 9 iostio 10 iotyp 9 45 Index I identifier 19 initialization 5 25 input channels 31 interrupt buffer 31 operation 32 slave 9 vector 32 interrupter channel description 26 27 iobnum 9 number 4 type 9 iorecl 34 iorxIn 11 iotout 32 irbuf 41 M memory 3 5 multitasking 15 multiuser 15 overrun error 34 P parameter description 20 parameter index baud 20 chri 20 hndi 20 pari 20 stpi 20 parameter structure 19 parameter channel description 19 20 type 9 Parameter Index baud 20 parameterization 3 9 10 parity 20 34 parity type 20 23 pointer 6 8 9 polling 4 PROT 39 protoks 22 46 R RCHACHx 29 receive channel 10 receive error mode 34 receive mode 8 receive operation 4 11 receive Errlog 25 receive On 25 receiver baud rate 20 23 receiver status 24 reset 25 rirtrig 29 root pointer 4 5 12 rtimeO 33 Rx buffer 12 13 Rx interrupt 23 Rx server 29 Rx time out 23 Rx error 24 rxclkmods 21 S semaphore 9 15 sequential chaining 6 slave server 4 15 star shaped chaining 6 status 19 stop bits 20 23 sync 25 synchronization 19 synchronous 3 T TAS 15 TCHACHXx 28 time out 8 21 32 tirtrig 28 transmit channel 10 19 transmit mode 8 transmitter bau
23. dshake rtime0s Receive time out for the first character in msec 20 VME ISER12 Software Manual Rev 1 0 Channel Description rtimels ttimes rxclkmods txclkmods txbvs rxbvs 0 Receive time out disabled Receive character to character time out in msec 0 no character to character time out Transmit Time Out in msec 0 Transmit Time Out disabled see also section Time out on page 32 Clock mode of the DUSCC SCC channels has to be indicated separately for receive and transmit rxclkmods Function of the Pin RxTxCLK ox Lilien Async Mode c 16x baud rate Table 2 2 2 Evaluation of rxclkmods and txclkmods Pin RxTxCLK DUSCC SCC Pin 39 J3A Pin 3 for channel 9 or DUSCC SCC Pin 10 J3 Pin 3 for channel 10 baud rate absolute range of values 50 asynchronous dimension baud In txbvs and rxbvs the actual baud rate is indicated as absolute number If a baud rate is desired that deviates from the baud rates which can be selected via txb or rxb via Ixbvs or rxbvs the baud rates can be handed over as an absolute value txbs or rxbs set to FF The interface is programmed with the nearest possible baud rate and the real value of the adjusted baud rate is handed back in txbv and rxbv Example Parameter setting with Tx baud rate 115 000 baud at the VME ISER8 Input gt txbs Input 115000 gt txbvs Output gt gt txbv 115200 actual baud rate 115200 bau
24. e Manual Rev 1 0 43 The local VME ISER Server Example for Configuration esn stx etx Protocol For this protocol the following configuration is advisable iorecl 0018 iofnam PROT iomode 8700 ioivev ioilev 2 00 00 no interrupt ioivec ioilev vector level user defined IRQ For the group configuration via the parameter channel txbs 13 115200 baud rxbs 13 115200 baud chrls 00 8 bits char stpls 00 1 stop bit parts 00 no parity hnds 03 no handshake rtimeOs rtimels 50000 or time out in msec 3 44 VME ISER12 Software Manual Rev 1 0 Index A ANCHOR 5 ASCII 5 11 31 asynchronous 3 B base address 5 baud rate 20 23 bits char 20 break 34 buffer allocation 15 buffer channel 9 17 buffer pool 12 BUSERROR 5 card id 4 channel chaining 12 command 8 description 13 14 17 19 header 3 identifier 8 overview 4 release 15 semaphore 8 status 8 9 structure 6 7 10 17 type 3 9 character to character 21 clear 25 command handing over 25 CPU3 5 CPUID 5 D data channel description 17 management 12 type 4 data direction 10 default channel data channel 17 description 18 DTACK signal 5 encodes 22 VME ISER12 Software Manual Rev 1 0 Index E example buffer allocation 15 data input 36 data output 36 initialization 35 parameterization 38 F forward pointer 6 framing error 34 H handshake 20 31 32 handshake mo
25. el Management 1 5 1 General As mentioned above the channels are divided into parameter channels buffer channels default channels and interrupter channels To each serial interface a parameter TX buffer a default Tx buffer an Rx buffer and a number of buffers of the Buffer Pool are allocated The parameter buffer the Tx buffer and the Rx buffer are exclusively allocated to the corresponding interface As a principle the buffers may be used by any channel The pointer chaining results in a priorized buffer allocation to the corresponding interface channels The chaining of the TX buffers and of the buffer channels is displayed in the following tables The forward backward pointer ionext allocates the corresponding Tx buffer channel to a buffer The ionext pointer of the last buffer points to the Tx buffer again This channel distribution has been chosen for a very flexible memory allocation while the searching algorithm remains quick and simple 1 5 2 Overview to the Channels with Chaining via Pointer Channel Root Pointer Address Content Remarks HEX HEX 08000 Start address of the buffer range Table 1 5 1 Channel Root Pointer to Address ANCHOR 12 VME ISER12 Software Manual Rev 1 0 Introduction Buffer Address ChmnlHeer Header DEZ HEX mex HEX HEX HEX Fo 1 1 9 Foam 2 2 o MA Fax s 3 o
26. ers the board relative address of the channel to be accessed DO in the example mentioned above into these cells and activates the VME ISER server by triggering a local interrupt The VME ISER server identifies the data channel by the entry in the interrupter channel and thus can work on it The interrupter channel makes available an entry each both for transmit and receive operation for each of the 10 interfaces The cells TCHACHx RCHACHx serve as status cells as well If the content of the cell is unequal to 00000000 L the corresponding data channel has not yet been integrated into the VME ISER server queue and no new entry may take place As soon as the data channel is integrated into the server management the entry in the interrupter channel is set to 00000000 L This entry delivers no information about the status of the corresponding channel The status can only be obtained from the condition of the cell in the header of the data channel 26 VME ISER12 Software Manual Rev 1 0 Channel Description Address Offset HEX 0 2 4 6 8 A C 4E oo o0 e1 co 00 00 00 oo oo o oo 00 00 o oof oo oo oo oo 00 00 80 o0 so 00 00 00 8030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2040 2050 2060 00 00 8070 00 00 00 00 00 00 00 00 00 00 00 00 00 00 5080 2090 8
27. f the Cells VME ISER12 Software Manual Rev 1 0 7 Introduction 1 4 2 Description of the individual Channel Locations Summary of the channel locations Offset t uw 3o HEX ia pid jiofor 00 longword Poitertonextchannel jioback 04 longword notued ow 8 pod word channel type see below 6 byte ASCH channel identifier as character string liosema 10 bye byte channel semaphore preset 00 byte _____ channel status preset 00 __ ____ word preset 0000 ionext longword forward backward pointer to next channel 18 bye VME rq Level for Slave Irq ioivec oec Me _ byte VME Irq Vektor for Slave Irq LL word number of the specific channel type Polen alen 1C longword length of the data range EE iorecl word number of the data in the data range osto 26 byte 27 me 28 __ word transmit receivemode tout 1 2A timeout I parameter channel 48 reserved for Tx server for Tx server reserved default 50000 omm word mumberafreceneddata a m byte data range 128 byte channel 80 47F bye data range 1 Kbyte channelsy Table 1 4 2 Description of the Channel Cells 8 VME ISER12 Software Manual Rev 1 0 Introduction Explanation
28. he user is organized in so called channels which consist of a header and a data range The length of a channel amounts to 256 bytes 128 bytes net data or 10244128 bytes 1 kbyte net data The structure of the header is identical for all occurring types of channels the different channels differ in corresponding entries in the header of the channel The status of the serial interfaces and the setting of the serial interfaces parameters is transparently readable resetting of the parameter ensues synchronously to the I O transfer VME ISER12 Software Manual Rev 1 0 3 Introduction 1 2 Channel Overview 1 2 1 Channel Types The system consists of following types of channels the parameter channels 1 channel per serial interface the data channel receive channel 1 kbyte 1 transmit channel 1 kbyte 26 transmit channels 128 bytes each the interrupter channel 1 channel per board Channels are software structures which are chained by pointers The ROOT pointer as well as a Card Id are at fixed addresses 1 2 2 Tasks of the VME Master Servers The VME master server for the serial interfaces must essentially fulfill the following tasks Search a free channel and occupy this channel Entry of the transfer mode Data transfer to the VME ISER memory for transmit operation Activation of the slave server local interrupt generation Polling on ready or reactivation by VME interrupt Data transfer from the VME ISER memory fo
29. if in the element iocmmd the command paraxy 0000 is entered Read accesses to the parameters are always possible independently from iocmmd see also Command Transfer via the Parameter Channel on page 25 Writeable and readable parameters txbs Index desired value baud transmitter baud rate rxbs Index desired value baud receiver baud rate chrls Index desired value chri bits char stpls Index desired value stpi number of stop bits parts Index desired value pari parity type hnds Index desired value Andi handshake mode Assignment of the Parameter indices Meaning of the index baud d rate 38400 d rate 19200 d rate 9600 d rate 4800 d rate 2400 ud rate 1200 d rate 600 d d d d d d 300 150 rate 110 rate 15 rate 50 rate variable via txbv rxbv only for channel 9 and 10 12 baud rate 76800 13 baud rate 115200 Meaning of the index chri 0 8 bits per character 1 7 bits per character 2 6 bits per character 3 5 bits per character Meaning of the index stpi 1 stop bit 1 2 stop bits Meaning of the index pari 0 parity no Tx parity 1 Rx Tx parity ODD 2 Rx Tx parity EVEN Meaning of the index hndi 0 hardware handshake DTR CTS 1 software handshake XON XOFF 2 modem operation RTS CTS handshake 3 no handshake 4 RS 485 operation no handshake 5 RS 422 operation XON XOFF han
30. ilters the application program has to be installed in a free memory range between 20000 and 3FFFE theentry address of the server routine has to be specified in the respective parameter channel in cell IOENTR theentry address has to be even the last four bytes before the entry address have to include the ASCII ID P ROT Re entry window freely relocatable 68000 Code no commands for 68020 30 40 no software traps restrictions in the use of registers Register Al contains the pointer to the variables of the respective channel such as irwp ceaddr Register A3 contains the return address In register DO the status of the protocol is returned 0 Prot not yet finished gt 0 number of bytes 0 e g number of bytes bit 15 set CRC error Data registers A2 A4 D1 D2 D4 can be used Al and A3 must not be changed The protocol is entered in supervisory mode on interrupt level 5 or interrupt level 7 VME ISER12 Software Manual Rev 1 0 39 The local VME ISER Server 3 3 3 Register and Structure Declarations Register Ad sb pointer to structure irbuf A3 L return address A2 L A4 L free DO L D1 L D2 L D4 L free When returning from the protocol via has to be supplied with the returned value and the according flags have to be set in the status register Returned values in D0 W DO Flags SH eq Protocol has not been finished yet no further action of the ISER server 0001 m
31. mit and receive jobs can be achieved The parameter structure is separated into 2 different parts parameters which can be written to by the user offset 80 BF parameters which only be read by the user offset FF The parameters txb hnd are formatted as byte and can be interpreted as identifiers for the physical parameterization Address Offset HEX 2 6 8 A C E 0 4 s10 oo 00 s2 ofo 00 00 ofo Parar 8110 f iocmmd 00 oo 01 00 00 00 8120 00 00 81 00 oo 00 00 00 00 8130 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 s140 o0 o0 00 oo Proko o0 00 e150 o0 o0 oo 00 00 oo 00 00 00 00 00 00 00 oo 00 00 e160 90 o0 00 0 oo oo oo 00 00 00 oo oo 00 00 00 o e170 meuren 00 00 00 oo 00 0000 8180 bbs oss cv sui pas ines timeo timet mes Topo reserved mo we 00 00 00 00 0 rxb 81A0 00 00 00 00 00 00 00 00 00 81B0 00 00 00 00 00 00 00 00 00 00 00 eco o6 cw sts pat rimer time op ipo ww o 00 00 00 81E0 00 00 00 00 00 00 00 00 00 81F 0 00 00 00 00 00 00 Table 2 2 1 Parameter Channels example parameter Channel 1 VME ISER12 Software Manual Rev 1 0 19 Channel Description 2 2 2 Description of the Parameter Write accesses to the parameters can only ensue
32. ned via iorecl If several errors occur simultaneously following priority will be obeyed break parity error framing error overrun error Error codes in iorecl 8007 time out 801E framing error 801F overrun error 8020 parity error 8046 break detected The error condition time out is independent of the condition errlog and is released only by the time out cells described before 34 VME ISER12 Software Manual Rev 1 0 The local VME ISER Server 3 2 Examples for the VME ISER Server 3 2 1 Example Initialization of the VMEbus Master Itis recommended to let the initialization routine of the master determine the following addresses once and store them in master local cells CRDADR VMEbus base address of the VME ISER TxBUFF VME ISER relative address of the Tx channels 1 to 10 RxBUFF VME ISER relative address of the Rx channels 1 to 10 PARAn VME ISER relative address of the parameter cannel 1 to 10 IRCH VME ISER relative address of the interrupter channel data buffer iobuff IRCH interrupt acknowledge address absolute TIRTRIG transmit interrupt trigger address absolute RIRTRIG receive interrupt trigger address absolute The master should scan the VME ISER channels starting with the address of ANCHOR and either check for the corresponding ASCII string TBUFxy RBUFxy PARAxy and Irch or determine the channel via the cells iotyp and ioldn As next pointer iofor has to be used VME I
33. o which the characters are to be transferred After all characters have been transferred the number of valid bytes is transferred in DO the MSB can be used as a flag for a faulty protocol According to the configuration the VME ISER server then returns the Rx buffer to the VME master Register Al is the basic address for the current structure irbuf and must not be changed during the protocol Please make sure that the time for the protocol processing is optimized on server level because no further characters can be handled during this time data loss Example DC B PROT entry LEA irbuf 0 A1 A2 A2 pointer to Rx data range MOVE W irrp Al D1 last read pointer MOVE B 0 2 1 00 character from Rx buffer CMPI B char 00 checking the character BNE 5 exit not OK ADD W len 01 next read pointer MOVE L Dl irrp Al transfer LEA 0 A2 D1 W A2 pointer to character chain MOVEA L readce A1 A4 pointer to Rx buffer iobuff MOVEA L iobuff A4 A4 pointer to Rx data range MOVE W len 1 02 transfer length tloop MOVE B 2 4 transfer character chain DBF D2 tloop MOVE W len DO returned value MP A3 to VME ISER server exit MOVEQ 0 D0 flag not ready yet MP A3 When accessing the data range in the interrupt buffer you have to remember that it is a FIFO with 1 k byte length which means that all pointers have to be treated Modulo VME ISER12 Softwar
34. ocate memory on ISER 8 ISER 12 MOVEA L crdadr 0 Base address 5 8 15 12 MOVE L dfltbf 00 buffer address relative to default address BSR srchbuff forward backward buffer BNE no success buffer available sonst in actual absolute address of the channe in DO buffer address relative to base address Transfer END srchbuff MOVE L 00 01 end address e g to start address as final condition srchl TAS iosema A0 00 Semaphore access BEQ 5 srchex was not occupied buffer address in DO MOVE L ionext A0 00 1 DO next channe CMP L D0 01 end condition 2 BGT 5 srchl No go ahead searching TST E 00 flag srchex LEA 0 A0 D0 L A0 absolute address in RTS VME ISER12 Software Manual Rev 1 0 15 Introduction 16 VME ISER12 Software Manual Rev 1 0 Channel Description 2 Channel Description 2 1 Description of the Data Channels Data channels serve for the transfer of transmitted received data and are of the type default channel or buffer channel Before the beginning of a transmit receive transfer a data channel has to be allocated according to the example above Then the header of the channel is supplied with the corresponding parameters if necessary data are input and are handed over to the local CPU Address Offset HEX 4 6 0 2 8 A T 30 lofnam 70 lofree iodata lodata lodat
35. occurs at a transfer the following actions happen as a principle l in the corresponding channel the time out mark is set 8007 iorecl 2 in the parameter channel the time out bit in rxstat or in txstat 15 set The reset of these bits is done via the command reset stat in the parameter channel or at a channel reinitialization The bit is not reset at a successful input or output The channel being worked on is released again i e at a transmit channel without wat the channel will be scrapped The semaphore iosema is reset and the next transmit channel is obtained from the queue At a transmit operation with wat or at a receive channel the master is informed correspondingly The channel status is set to ready and if required an interrupt is generated VME ISER12 Software Manual Rev 1 0 33 The local VME ISER Server 3 1 5 Receive Error Mode Errors occurring in the Rx mode are recorded in rxstat An Rx status reset is performed by the commands reset stat reset or receive errlog Detectable errors are break parity framing and overrun errors If an evaluation of these errors is desired then the receiver error mode must be activated by the command receive errlog If one of the above mentioned errors occurs in the active mode and no receive instruction is effective all characters received in the interrupt buffer will be deleted If an Rx instruction is effective the instruction is aborted and an error code is retur
36. of the individual channel cells iofor ioback iotyp ioname iosema iostat iocmmd ionext supports the memory chaining of the channels iofor always points to the start address of the next channel iofor of the last channel points to the first channel again points to the start address of the preceding channel is the channel identifier and distinguishes the following channel types FFFF interrupter channel 000C parameter channel 0014 default channel not used 0018 buffer 001C buffer channel not used 0114 Tx buffer long 0214 Rx buffer long contains the channel identifier as a 6 bytes ASCII string and a consecutive numbering Irch interrupter channel PARAxy parameter channel with xy 01 02 09 0A TBUFxy transmit buffer long with xy 01 RBUFxy receive buffer long with xy 01 0A Buffxz transmit buffer 128 byte with x 1 A Zz a b Z is covered with the channel semaphore and with the channel status bit Bit 7 semaphore 0 channel is free channel is occupied Bit 6 1 reserved default 0 Bit 0 channel status 0 channel is busy 1 channel is ready is not yet supplied and is preset to 0 is the channel command and is only necessary for setting the interface parameters see interface parameter setting from page 19 is the pointer to the next data channel Is only used for data channels otherwise 0 ioilev und ioivec iobnum
37. r receive operation Channel enable 4 VME ISER12 Software Manual Rev 1 0 Introduction 1 3 Initialization of the System In the following all addresses are indicated relatively to the card base address and must be addressed correspondingly by the VME master CPU After a system reset the local CPU initializes its local memory and rebuilds the channel pointer chain This can take up to 2 sec depending on the memory size After a restart the master CPU should check the following entries read access to the base address of the slave board If the board responds with DTACK signal it is physically available at the correspondent address otherwise a BUSERROR occurs e g via time out because the board is not available gt gt abort of the initialization check of the address CPUID 0998 to 49534552 L The local CPU must have an ASCH entry ISER 49 53 45 552 check of address ANCHOR 099C to unequal to 0 The local CPU inserts the ROOT pointer at the buffer structure default 00008000 L The local CPU has now built up the buffer structure described in the following which enables a communication with the master CPU VME ISER12 Software Manual Rev 1 0 5 Introduction 1 4 The Channel Structure 1 4 1 Chaining of the Channels channels are chained by pointers where it must be distinguished between a memory chaining and a forward backward chaining The memory chaining connects all available channel
38. s after the time 7_Out the channel will be released and the status Time Out is returned via iorecl is reserved for ASCII entries up to 24 bytes Actually following entry will be evaluated On the ASCII string SCAN in the first 4 bytes of iofnam the following return conditions are valid for a receive channel 1 Return of the buffer if lt iorecl gt data have been received 2 Return of the buffer if one of the end conditions specified in lt iomode gt is valid 3 Return of the buffer if no more data are available in the local interrupt buffer i e if the interrupt buffer is empty the receive channel is returned immediately with lt iorecl gt 0 For all other entries into iofnam only the end conditions 1 and 2 are valid With the entry PROT data are received via a special user protocol supports the embedding of an user specific receive protocol only parameter channel The start address of a protocol loaded into a free memory area is registered here is reserved for embedding of a user specific transmit protocol only parameter channel determines the number of valid received data specially in the error case is actually not used and is preset to 500 is the default data buffer of a channel and has a length of 128 bytes or 1 kbyte respectively TBUFxy RBUFxy Writing to memory out of the data buffer limits will destroy the I O structure VME ISER12 Software Manual Rev 1 0 11 Introduction 1 5 Data Chann
39. s while the forward backward chaining only connects those channels related to the corresponding interface Memory Chaining Sequential chaining The root pointer to the first available channel is a longword at the address ANCHOR 0099C the pointer to the next channel forward pointer is longword each time in the location iofor of the channel header The forward pointer of the last channel points back to the first channel As default ANCHOR is set to 00008000 All addresses listed in the tables refer to this base but are relocatable without restrictions The length of a channel normally is 256 bytes and is divided into 128 bytes of header and 128 bytes of data Star shaped chaining from Software Rev iser 50b The star shaped chaining speeds up the snapping of the addresses of the channels In the interrupt channel the successive addresses of all parameter channels can be found In every parameter channel the addresses of the assigned Tx and Rx channels are stored Note The sequential chaining and the star shaped chaining are both available and can be used alternatively 6 VME ISER12 Software Manual Rev 1 0 Introduction Address Offset HEX 40 2 4 6 8 A C E 30 lofnam 40 50 00 iodata lodata lodata lodata lodata lodata User read write cells H User read only cells Table 1 4 1 Internal Channel Structure with READ WRITE Assignment o
40. t receive operation as well as setting the receiving protocol parameters Bit Mnemo Description No 15 MODBWA After transmission of all data no IRQ will be generated the requested channel will automatically be released again by the slave 1 After transmission of all data ready will be set iosema or the indicated IRQ will be generated respectively The requested channel will not be released by the slave MODBOU receive channel 1 Identification transmit channel MODBOU After detection of a cr 0D the reception of this channel will be terminated MODBLF After detection of a If 0A the reception of this channel will be terminated 11 MODBEO 1 After detection of a eot 04 the reception of this channel will be terminated MODBSC suppress command actually not connected MODBNE E no echo actually not connected MODBIN EN no binary transfer binary transfer no end check no software handshake Table 1 4 3 Bits of iomode VME ISER12 Software Manual Rev 1 0 iotout iofnam ioentr iotent iorxin iofree iodata Introduction Bit 7 0 of iomode are reserved as mode extension bits The following combinations are already defined 00 normal I O transfer default 08 only for receive operation All characters in the local buffers will be deleted time out value The MSB bit 7 enables the Time Out supervision of the channel If no transfer into an active channel buffer occur
41. ter to character time out in msec Transmit time out in msec see also section Time out on page 32 read parameter of the clock mode of the DUSCC SCC channels Meaning of the parameter see Table on page 21 baud rate absolute range of values 50 38400 unit Baud in xbv and rxbv the actual baud rate is indicated as an absolute number see also above txbvs rxbvs on page 21 protocol mode of the channels 9 and 10 00 UART mode 01 HDLC mode see also protoks on page 22 signal coding of the serial Interfaces Only the format NRZ No Return to Zero is supported encodes 0 at the moment internal FIFO threshold for Rx interrupt local time for Rx time out in 5 msec units local reserved internal controller commands 23 Channel Description txstat status of the transmitters Bit 7 not used Bit 6 not used Bit 5 not used Bit 4 not used Bit 3 l Tx time out occurred 0 no Tx time out occurred Bit 2 1 Tx queue filled up 0 Tx queue ready Bit 1 1 transmitter disabled by handshake 0 transmitter enabled by handshake Bit 0 1 transmitter disabled 0 transmitter enabled rxstat status of the receivers Bit 7 1 break recognized 0 no break recognized Bit 6 1 parity error recognized 0 no parity error recognized Bit 5 1 framing error recognized 0 no framing error recognized Bit 4 1 receiver overrun recognized data loss
42. the protocol to control the protocol buf 40 interrupt buffer length 400 Table 3 3 2 Relevant structure elements of the interrupt buffer Note Apart from cells irrp prtphs and possibly irwp all other cells are read only for the application program Furthermore a pointer is required from the data channel structure iobuff VME ISER12 Software Manual Rev 1 0 41 The local VME ISER Server Name Offset pace nee Meaning HEX err Offset in data channel Table 3 3 3 Pointer to data range 42 VME ISER12 Software Manual Rev 1 0 The local VME ISER Server 3 3 4 Protocol Embedding for Rx Operation If characters are received they are read out of the controller on interrupt level are possibly checked for signs of software handshake or end signs and filed in the Rx FIFO Then if required by the Rx buffer the user protocol is executed This can now check the characters while knowing the current write pointer irwp and the self administered read pointer irrp If the protocol requirements are not met the returned parameter 0 is transmitted and the protocol is activated again when the following characters are received If the protocol requirements have been met the application program will initiate the transfer of characters into the Rx buffer The pointer to the waiting Rx buffer is in cell readce and is of structure type iobuff In cell iobuff of this structure is the initial address of the data range int
43. ware Manual Rev 1 0 The local VME ISER Server 3 The local VME ISER Server 3 1 Functional Description of the local VME ISER Server Thelocal VME ISER server manages all channels which have been handed over from the VME master program to the VME ISER The server distinguishes basically between input and output channels The execution of a parameter channel is a special form of an output channel 3 1 1 Output Channels The VME ISER server contains a local execution queue for each interface As a default these queues have a depth of 32 entries An output data channel linked in via the interrupter channel will be entered into the queue and the Tx server responsible for the interface obtains the particular channel from the queue and releases the entry again after the complete execution A run over of the queue is prevented by the handshake with the cells TCHACHx if the queue is full the entry of the corresponding data channel is certainly accepted but the cell TCHACHx will not yet be released again This will only happen if space for at least one more entry is available in the queue If the TX server recognizes the actual output channel as a parameter channel no output will occur but the command iocmmd will be executed 3 1 2 Input Channels An interrupt buffer is allocated to each of the 10 serial interfaces as a default The user has no direct access to this buffer If data are received via the interface and there is no input buffer
Download Pdf Manuals
Related Search