Home

USPIIIi Software Manual

Contents

1. Offset Register Name 320 Interrupt Status ID Out Register STATID 324 VIRQ1 STATUS ID Register V1_STATID 328 VIRQ2 STATUS ID Register V2_STATID 32C VIRQ3 STATUS ID Register V3_STATID 330 VIRQ4 STATUS ID Register V4_STATID 334 VIRQ5 STATUS ID Register V5_STATID 338 VIRQ6 STATUS ID Register V6_STATID 33C VIRQ7 STATUS ID Register V7_STATID 340 PCI Interrupt Map 2 Register LINT_MAP2 344 VME Interrupt Map 1 Register VINT_MAP2 348 Mailbox 0 Register MBOXO 34C Mailbox 1 Register MBOX1 350 Mailbox 2 Register MBOX2 354 Mailbox 3 Register MBOX3 358 Semaphore 0 Register SEMAO 35C Semaphore 1 Register SEMA 360 3FC Reserved 400 Master Control Register MAST_CTL 404 Miscellaneous Control Register MISC_CTL 408 Miscellaneous Status Register MISC_STAT 40C User AM Codes Register USER_AM 410 EFC Reserved FOO VMEbus Slave Image 0 Control Register VSIO_CTL F04 VMEbus Slave Image 0 Base Address Register VSIO_BS F08 VMEbus Slave Image 0 bound Address Register VSIO_BD FOC VMEbus Slave Image 0 Translation Offset Register VSIO_TO Themis Computer 1 USPIlIli Programming Guide Table 1 6 Universe Il Register Map Continued Universe II VME Interface Registers Offset Register Name F10 Reserved F14 VMEbus Slave Image 1 Control Register VSI_CTL F18 VMEbus Slave Image 1 Bound Address Register VSI1_BS F1C VMEbus Slave Image 1 Bound
2. 5 hemis Co USPIIIi m d Themis VM sparc you wish to efault all Themis VME Drivers for SPARC USPIITIi sparc USPIIIi Release 1 1 puter You are about to install the vme 32 64 bit version to use th func he packag driver from t However curre Please ensure After the ins reboot the reboot replaces th he o nt v tha tall sys If the system can you may abort Con Whe pl Usi Processing Processing re should th latform sun4u ng lt gt as the package base the tinue installa riginal Sun ersions of t t the vmemem ation tem usi execu ng 64 rD kernel unix not be instal reboo latio tion n Ly USPIIIi Release 1 process or all 2 2 q 32 64 bi nexus driver e VMEbus interfac CE tionality of the distribution he files will drivers are be not te reboot bit kernel or to use 32 bit ke ted at this time n of the package 1n q Y ts be installed pac sys 9 package path Verifying disk space requi Checking for conflicts with packages already i Checking for setuid setgid programs driver objec kernel drv kage informa tem informat names are al q directory tion ion ready properly in rements This package contains scripts which will be execu E Drivers for SPARC USPIITi During the
3. As an example for a device that supports A24D32 and has a set of registers that are 32 byte long and start at address Oxee00 the following 3 tuple can be used 0x7d Oxee00 32 Multiple register sets are separated by commas VMEbus supports vectored interrupts The interrupts property in the driver configu ration file specifies all the interrupts that the device may generate The interrupts property is an array of 2 tuples VMEbus interrupt level VMEbus vector number For example for a device that generates interrupts at VME level 3 with a vector of 0x84 this two tuple can be used 2 0x84 The VMEbus interrupt level has a value between and 7 and the vector a value between 2 and 254 All VMEbus device drivers must provide reg properties The first two integer elements of this property are used to construct the address part of the device name under devices Only devices that generate interrupts need to provide interrupt properties Themis Computer USPIIli Software Manual 3 5 1 Note that the DDI DKI functions are capable of handling the VMEbus specific fea tures provided that the hardware configuration file is correct e g if the hardware configuration file correctly defines a register set the ddi_map_regs function can be used to map the register set into kernel address space without any extra effort from the driver code Probing Devices Since VME devices are not self identifying drivers for these devices
4. This chapter describes the software used on the Themis USPIIIi This includes the OBP firmware Sun Solaris 8 2 04 Sun Solaris 9 4 04 or later or Sun Solaris 10 Operating Systems The default firmware is Sun s Open Boot Prom OBP that has been modified to support VME OBP will boot the Solaris operating system 3 2 SUN OpenBoot PROM OBP The Themis USPIIIi OBP is based on OBP 4 x from Sun Themis has added several OBP command extensions that are specific to the USPIIIi All other OBP commands are the same as the Sun UltraSPARC IIIi Platform as implemented in the Sun Blade 2500 workstation Specific details of the OBP architecture are defined in the IEEE 1275 specification document Reference materials that describe the OBP include e OpenBoot 4 x Command Reference Sun Part Number 816 1177 10 e OpenBoot Quick Reference 3 x Sun Part Number 806 2908 10 e Writing FCode 3 x Programs Sun Part Number 806 1379 10 Themis Computer USPIIli Software Manual 3 2 1 OBP VME Environment Variables The environment variables see Zable 3 1 below and Table 3 2 on page 3 5 may be set at the ok prompt in OBP by using the setenv command ok setenv variable name value when running Solaris with the command line the syntax may vary depending on the shell used eeprom variable name valu A board RESET is required for the new values to take effect follows eeprom vme32 slave size 0x800000 However this can be inco
5. 105 Low limit 5 You can also change the thresholds by typing usp31_temp c usp3i_temp c Sys local temperature is Therm limit 80 41 48 85 60 34 77 49 38 Thermal Monitoring new value Type the new value or simply hit enter to continue without changing To run the utility in monitor mode type usp3i_temp m Themis Computer 5 7 USPIIli Software Manual 5 3 Voltage Monitoring The USPIIli CPU 0 CPU 1 boards have many built in DC DC converters The volt age output must be set to very specific values in order to get maximum performance As a result it is vital to implement a capability to monitor these critical voltages Design of the USPIIIi contains an I C A D converter on each CPU board that allows us to read the current voltage of the many critical DC DC converters outputs The voltages monitored are listed in Table 5 1 Table 5 1 Voltages Monitored on the CPU 0 and CPU 1 Boards CPU 0 VCC 5V backplane 2 5V DDR memory0 voltage 1 5V Jbus termination voltage VCCPO0 CPU core voltage CPU 1 VCC 5V backplane 2 5V DDR memory voltage 1 5V Jbus termination voltage VCCP1 CPU core voltage To see the current Voltage levels type the OBP command 1 ok themis show voltage CPUO Voltage Voltage on AinO Backplane Voltage on Ainl Memory Voltage on Ain2 Jbus Voltag
6. The Jbus has several agents Each has its own Agent ID JID number which is used in the decoding process The Jbus address space has 43 address bits or 8 Terabytes of address reach This space is broken up into two 42 bit physical spaces one for the memory space cacheable the other for the IO space non cacheable 0x000 0000 0000 Main includes Memory 16GB for CPU0 cacheable memory space 4TB 16GB for CPU1 cacheable memory space 0x400 0000 0000 T O space includes i 4TB Jbus device configuration space PCI address spaces Cfg IO Mem 0x800 0000 0000 Each agent on Jbus has its own 5 bit Jbus ID It has 8 MB of non cacheable address space assigned for its Jbus configuration registers These 8 MB windows are defined by e PA 42 41 10b e PA 40 28 0 0000 0000 0000b e PA 27 23 JID 4 0 e PA 22 00 8MB for Jbus device configuration registers 1 2 Themis Computer 1 USPIlli Programming Guide Jbus Address Map Table 1 1 Jbus ID Assignment Jbus Agent JID 4 0 Jbus Cfg space Start address End address Size Jalapeno CPUO 0x00 0x400 0000 0000 0X400 007f fff 8 MB Jalapeno CPU1 0x01 0x400 0080 0000 0X400 00ff ffff 8 MB Jalapeno CPU2 0x02 0x400 0100 0000 0X400 017f ffff 8 MB Jalapeno CPU3 0x03 0x400 0180 0000 0X400 01ff ffff 8 MB Habaniero 0x08 0x400 0400 0000 0X400 047f ffff 8 MB Tomatillo 0 Slave 0x1c 0x400 0e00 0000 0X400 0e7f ffff 8 MB Tomatillo 1 Mast
7. 0000 A32D32 1000 0000 map in value a32va 100 value register a ter a map 5678 register a lpoke ter a lpeek ter a 1 0040 0000 map out Required after OBP testing is done test a register in VME A24D16 space tack 00 A24D16 10 0000 map in value a24va 100 value register b ter b map register b wpoke ter b wpeek ter b w 10 0000 map out required after OBP testing is done test a register in VME A16D16 space tack a000 A16D16 1000 map in value al6va alva regis 12 re regis regis alva Not 100 value register c ter c map gister c cpoke ter c cpeek ter c c 1000 map out required after OBP testing is done Themis Computer 3 Themis USPIIli Software 3 2 5 3 SUN OpenBoot PROM OBP Constraints Mapping a CPU virtual address to VME address space requires many resources First the MMU maps the CPU virtual address to a PCI physical address Universe II register sets are then used to map the PCI physical address to a VME address For A24 and A16 devices due to its small physical size PCI address space is preal located and the Universe II mapping register the Special PCI Target Image Register at offset 0x188 is dedicated Thus at the end of OBP testing map out for A16 and A24 devices is not required For A32 devices PCI address space and Universe II mapping registers PCI Target Image 0 7 at offset 0x100 to Oxl
8. 1 The jumper is ON and the board set as system controller bit 1 RO Status of the Jumper JP2201 0 The jumper is OFF and the board CANNOT transmit a reset on the VME 1 The jumper is ON and the board CAN assert a reset on the VME bit 2 RO Status of the Jumper JP2301 0 The jumper is OFF and the board CANNOT receive a reset from the VME 1 The jumper is ON and the board COULD be reset by the VME see also programmable bit pld_reg 3 4 below bit 3 RO Status of the Universe controller 0 The Universe is NOT the VME system controller 1 The Universe is currently the VME system controller bit 4 RW Programmable incoming VME reset enable bit 0 A reset on the VME bus cannot reset the board 1 A reset on the VME bus COULD reset the board assuming bit pld 3 2 is also set to 1 Upon power up of the VME backplane this bit is cleared and remains unchanged upon Front panel reset assertion bit 5 RW Programmable enable bit for the Universe local LRST signal 0 Will prevent the Universe from propagating a reset to the IIi board thru the Lrst pin R1 signal 1 Will allow the Universe to propagate a reset into the IIi board thru the Lrst pin R1 signal Upon power up of the VME backplane this bit is cleared and remains unchanged upon Front panel reset assertion bit 6 RW reserved for future use Upon power up o
9. 1 5V Jbus voltage AIN3 gt VCCPO CPU 0 core voltage 1 6 Themis Computer 1 USPIlli Programming Guide I2C Devices Address Map Table 1 3 USPIIli I C Devices Continued Board Device 12C Bus HW Physical Address SW Virtual Address 12C Controller with Description CPU 0 PCF8574 2C 4 0x40 0x40 IC controller PCF8584 on Xbus and IMAX IC to I2C bus expander 2c 4 bus is attached to Port 2 of Imax e Control of User LEDs PO gt User LED 0 P1 gt User LED 1 P2 gt User LED 2 P3 gt User LED 3 P4 to P7 unassigned CPU 0O AT24C64 JIO Master U12601 OxAE OxAE USPIIli system parameters stored in EEPROM CPU 0 MC12430 JIO slave U10601 Pseudo Pseudo Jbus clock generator Memory 0 24LCS52 I2C_2 OxA0 OxB6 IC controller PCF8584 on Xbus and IMAX IC to 12C bus expander 2C 2 bus is attached to Port 0 of Imax e DDR DIMM EEPROM SDF 1st DIMM Memory 0 24LCS52 2C 2 OxA2 OxB8 IC controller PCF8584 on Xbus and IMAX IC to 12C bus expander 2C 2 bus is attached to Port 0 of Imax e DDR DIMM EEPROM SDF 2nd DIMM Memory 0 24LCS52 2c 2 OxA4 OxBA IC controller PCF8584 on Xbus and IMAX IC to I2C bus expander C 2 bus is attached to Port 0 of Imax e DDR DIMM EEPROM SDF 3rd DIMM Memory 0 24LCS52 C 2 OxA6 OxBC IC controller
10. 2 Copy the OBP image file to the root directory of the primary SCSI disk This procedure assumes that Solaris is already installed on the disk and was used to copy the OBP file to the root directory 3 Make sure that auto boot is set to false then shut down Solaris and power the USPIIIi off and on again At the ok prompt issue the following commands 4 ok load no such file Boot device pci ld 700000 scsi 4 disk 0 0 File and args no such file 5 ok go Boot cannot open no such fil Enter filename no such file 6 Send a break key combination see note below Type go to resume 3 8 Themis Computer 3 Themis USPIIli Software J 3 2 5 3 2 5 1 SUN OpenBoot PROM OBP Note The easiest way to send a break key combination is to press STOP A from a Sun keyboard CTRL Break from a PS 2 keyboard or CTRL Break from a HyperTerminal on a Windows XP desktop PC If you are connected to the USPIIIi via TTYA the method for sending a break character is dependent on the terminal or terminal emulator software you are using And in fact some versions of OBP will not accept a break event from the TTYA connection 7 ok load disk usp3i rev3 7 8 Next type the flash update command to write the OBP image to the flash ok flash update Additional OBP commands To view a list of OBP commands that are accessible when the current node is VME refer to Table 2 2 on page 2 3 To set the curr
11. Ebus bridge 7 11 device address map 10 peripheral bus 0 EEPROM 1 1 addresses and data 2 11 environment variables OBP VME 2 1 3 2 3 6 environmental monitoring programs 3 41 usp3i_pld 3 42 usp3i_ temp 3 41 usp3i_uled 3 42 usp3i_ voltage 3 41 Index 1 Themis Computer USPIIli Software Manual F fiber channel controller ISP2312 1 1 firmware 1 1 Flash PROM updating 3 6 3 8 from a SCSI disk 3 8 H hex 3 6 hierarchy Solaris 2 x device 3 25 I I2C ADM1031 device 5 bus topology 1 2 1 5 devices address map 1 6 I2C to I2C bridge expander IMAX 1 9 thermal sensor ADM1031 ID assignment Jbus 3 IDsel assignments 2 In Case Of Difficulties xiv installing THEMIS3ivme 3 17 INT 5 3 Intended Audience xiv interrupt mapping 1 2 3 17 interrupts 3 35 J Jbus address map 1 2 1 3 address space 2 address space mapping to PCI 1 4 configuration space layout 3 ID assignment 1 3 topology 2 JID 1 2 M mapping OBP VME 3 11 VMEbus interrupt 3 17 VMEbus space 3 39 Index 2 medvma 3 24 mmap 3 29 model configurations UPSIIi xiii monitoring devices thermal measurement 5 voltage measurement 5 N native firmware Nexus driver 3 16 O OBP 3 1 accessing the VMEbus 3 27 accessing VME address space from OBP 3 9 additional commands 3 9 commands 2 2 3 device aliases 3 3 support commands 3 6 VME environment variables 3 2 3 6 VME mapping 3 P PCI config
12. PA 0x92 VA 0x92 TOMATILLO GPIO MASTER EEPROM U12601 AT24C64 PA OxAE VA OxAE PCF8591 PA 0x90 VA 0x90 IMAX 87LPC764 PA 0x12 VA 0x12 PCF8574 PA 0x40 VA 0x40 PCs 0 Ad Figure 1 2 1 C Bus Topology Themis Computer 1 5 USPIIli Software Manual 1 4 IC Devices Address Map The following table lists all I C devices on the USPIIIi and provides relevant setting information for each of them Table 1 3 USPIIli 12C Devices Board Device Bus HW Physical Address SW Virtual Address I2C Controller with Description System ADM1031 I2C_1 0x58 0x58 IC controller PCF8584 on Xbus e Temperature monitoring on the system board e Therm output used for the thermal interrupt System ICS951601 2c 1 OxD2 0xD2 IC controller PCF8584 on Xbus e PCI clock generator CPU 0 ADM1031 2c 2 0x5C 0x5C IC controller PCF8584 on Xbus and IMAX IC to 12C bus expander 2C 2 bus is attached to Port 0 of Imax e Temperature monitoring on the CPU 0 board Diode D1 CPU 0 die Diode D2 CPU 0 reference Temp1 CPU 0 PCF8591 2c _4 0x90 0x90 IC controller PCF8584 on Xbus and IMAX IC to 12C bus expander I2C_4 bus is attached to Port 2 of Imax e DC DC voltage monitoring on CPU 0 AINO gt VCC Vme backplane AIN1 gt 2 5V DDR voltage AIN2 gt
13. USPIIIi namely the System board the CPU 0 board and the CPU 1 board Each ADM1031 sensor is able to report three temperatures the first temperature is that of the ADM1031 device itself the second and third temperatures are those of the two remote diodes used as sensors On both the CPU 0 and CPU 1 boards one of the diodes is on the CPU die there fore its temperature can be considered the CPU junction temperature The second diode is a discrete component placed on the board in a location that is given in Fig ure 5 1 on page 5 2 On the System board the two remote diodes are discrete components one placed at the inlet the other at the exhaust Their locations are provided in detail in Figure 5 1 5 1 Themis Computer USPIIli Software Manual Thermal Monitoring VME P1 VME P2 CPU 1 3 42 E E DDR1 E 1 62 Diode bottom side Diode top side i amp C thermal controller alle VME P1 VME P2 TMO a CPU 0 a a a DDR 0 E TM1 o3 S VME P1 VME P2 ema L 22 Z 77 a 1 50 ree PMC Card 0 3 9 10 Figure 5 1 Placement of USPIIli Device
14. gt The termination are forced in the enabled state 1 X gt The termination setting depends on the state of the corresponding sense pins Upon reset those bits are set to 1 PLD register offset 0x0a Description SCSI A B termination power control Width 8 bit Vector name pld_reg 9 i Description bit 0 RW Upon reset this bit is cleared bit 1 RW Upon reset this bit is cleared bit 2 RW Upon reset this bit is cleared bit 3 RW Control the termination power on SCSIA 0 The termination power on SCSI A is enabled 1 The termination power on SCSI A is shutdown bit 4 RW Control the termination power on SCSIB 0 The termination power on SCSI B is enabled 1 The termination power on SCSI B is shutdown bit 5 RO Status of the sense pin on the SCSI B interface 0 NO scsi device plugged onto SCSI B interface 1 a SCSI device is plugged onto SCSI B interface bit 6 RO Read as 0 bit 7 RO Read as 0 PLD register offset OxF0O to OxFF Description Atomic RWM semaphore and Test Width 8 bit Vector name semaphore_reg i Description This register is dedicated for the implementation of a Test And Set function It has a very peculiar behavior which is described in full details hereafter The semaphore register can be accessed in two ways One way
15. xx d probe can t map my registers error d n ddi_get_instance dip retval return DDI_ PROBE FAILURE regs struct my_reg_ str kaddr retval ddi_peekl dip long amp regs gt command long 0 DDI_SUCCESS DDI PROBE SUCCESS DDI_PROBE_FAILURE if retval DDI PROBE SUCCESS retval ddi_peekl dip long amp regs gt parm7 long 0 DDI_SUCCESS DDI_PROBE_SUCCESS DDI_PROBE FAILURE ddi_unmap_regs dip 0 amp kaddr 0 0 return retval Registering Interrupts VMEbus interrupts are vectored When a device interrupts it provides the priority as well as an interrupt vector The kernel uses the information to uniquely identify the interrupt service routine to be called The hardware configuration file must specify each priority vector pair that the device may issue Once this has been done the driver code can call the ddi_add_intr function to register the interrupts On return from this function the fourth argument contains a pointer that points to useful infor mation like the VMEbus interrupt priority and the VMEbus vector number The following code segment provides an example of registering an interrupt with the kernel the code first gets the number of interrupt specifications in the configuration file then it registers an interrupt handler for each interrupt specification static int xxattach dev_info_t dip
16. 5 Control Register VSI5_CTL FA8 amp VMEbus Slave Image 5 Bound Address Register VSI5_BS FAC VMEbus Slave Image 5 Bound Address Register VSI5_BD FBO VMEbus Slave Image 5 Translation Offset Register VSI5_TO FB4 Reserved FB8 VMEbus Slave Image 6 Control Register VSI6_CTL FBC VMEbus Slave Image 6 Bound Address Register VSI6_BS FCO VMEbus Slave Image 6 Bound Address Register VSI6_BD FC4 VMEbus Slave Image 6 Translation Offset Register VSI6_TO FC8 Reserved FCC VMEbus Slave Image 7 Control Register VSI7_CTL FDO VMEbus Slave Image 7 Bound Address Register VSI7_BS FD4 VMEbus Slave Image 7 Bound Address Register VSI7_BD FD8 VMEbus Slave Image 7 Translation Offset Register VSI7_TO FDC FEC Reserved FFO VME CR CSR Reserved FF4 VMEbus CSR Bit Clear Register VCSR_CLR FF8 VMEbus CSR Bit Set Register VCSR_SET FFC VMEbus CSR Address Register VCSR_BS Themis Computer Software Section Chapter OBP Commands 2 1 Themis OBP Commands The USPIIIi incorporates Sun s standard OBP version 4 x as the default firmware Themis has added specific OBP functions to support the additional Fibre Channel and VME functions The VME commands are summarized in the remaining sections of this chapter 2 2 OBP VME Environment Variables The environment variables see Table 2 1 on page 2 2 may be set at the ok prompt in OBP by using the setenv command on a single processor system the prompt appears as ok However on a system with t
17. Address Register VSI1_BD F20 VMEbus Slave Image 1 Translation Offset Register VSI1_TO F24 Reserved F28 VMEbus Slave Image 2 Control Register VSI2_CTL F2C VMEbus Slave Image 2 Bound Address Register VSI2_BS F30 VMEbus Slave Image 2 Bound Address Register VSI2_BD F34 VMEbus Slave Image 2 Translation Offset Register VSI2_TO F38 Reserved F3C VMEbus Slave Image 3 Control Register VSI3_CTL F40 VMEbus Slave Image 3 Bound Address Register VSI3_BS F44 VMEbus Slave Image 3 Bound Address Register VSI3_BD F48 VMEbus Slave Image 3 Translation Offset Register VSI3_TO F4C F60 Reserved F64 Location Monitor Control Register LM_CTL F68 Location Monitor Base Address Register LM_BS F6C Reserved F70 VMEbus Register Access Image Control Register VRAL_CTL F74 ee Sea Access Image Base VRAI BS F78 Reserved F7C Reserved F80 VMEbus CSR Control Register VCSR_CTL F84 VMEbus CSR Translation Offset Register VSCR_TO F88 VMEbus AM Code Error Log Register V_AMERR Themis Computer USPIIli Software Manual Table 1 6 Universe Il Register Map Continued Offset Register Name F8C VMEbus Address Error Log Register VAERR F90 VMEbus Slave Image 4 Control Register VSI4_CTL F94 VMEbus Slave Image 4 Bound Address Register VSI4_BS F98 VMEbus Slave Image 4 Bound Address Register VSI4_BD F9C VMEbus Slave Image 4 Translation Offset Register VSI4_TO FAO Reserved FA4 VMEbus Slave Image
18. OV A s register 0x7ee 0100 0c05 ER temperature condition CPU1 board temperature no OV ER temperature condition 4 11 Themis Computer USPIIli Software Manual system board temperature no OVER temperature condition CPU0O board temperature is below the warning threshold CPU1 board temperature is below the warning threshold system board temperature is below the warning threshold Miscellaneous status register Ox7ee 0100 0c06 SB3901 NOT INSTALLED PLD clock output CLK10HZ set to normal 10HZ System LED turned off User Flash busy executing a programming command JP4001 INSTALLED 1 2set Rombo interface is used to access to the external boot PROM JP3904 NOT INSTALLED JP3905 NOT INSTALLED JP3906 NOT INSTALLED JP3907 NOT INSTALLED SCSI A termination status register 0x7ee 0100 0c07 No SCSI device plugged on front panel SCSI A interface No SCSI device plugged on P2 SCSI A interface SCSI A front panel termination lower section enabled SCSI A front panel termination upper section enabled SCSI A P2 termination lower section enabled SCSI A P2 termination upper section enabled SB1604 NOT INSTALLED System board SCSI termination set to Dallas DS2119 SBX1701 NOT INSTALLED SCSI adaptor termination set to Dallas DS2119 KBM USB TTY A amp B setting register Ox7ee 0100 0c07 Solderbead SB12201 set to 1 2 Solderbead SB2505 s
19. Operating System environment Themis Computer has developed several sample programs that illustrate ways to use the software interface provided These programs are available with the source code and can be used to test the configuration of a VME system They can also be used as example programs for the use of the different features provided by the software interface The following subsections introduce the concepts of accessing the VMEbus from user programs The reader may note that though the examples in this section use VMEbus memory boards the usage can be extended to any type of VMEbus board Using Read Write The vmemem driver from Themis Computer enables you to access any VMEbus address from a user program Depending on the address space used by the particular VMEbus card different device files need to be used Themis Computer USPIIli Software Manual Table 3 6 VME Special Files File Address Size Data Transfer Size EE siea dev vme16d16 16 bits 16 bits 0x0 0xFFFF dev vme24d16 24 bits 16 bits 0x0 0xFFFFFF dev vme32d16 32 bits 16 bits 0x0 0xFFFFFFFF dev vme24d32 24 bits 32 bits 0x0 0xFFFFFF dev vme32d32 32 bits 32 bits 0x0 0xFFFFFFFF For example to access a VME card that supports 24 bit addresses and 32 bit data transfers you need to use the file dev vme24d32 Using dev vmeXXdYY files is very similar to using normal files the user program opens the file uses the memory address
20. PCF8584 on Xbus and IMAX IC to I2C bus expander 2c 2 bus is attached to Port 0 of Imax e DDR DIMM EEPROM SDF 4th DIMM Themis Computer USPIIli Software Manual Table 1 3 USPIlli I C Devices Continued Board Device E Bus HW Physical Address SW Virtual Address I7C Controller with Description CPU 1 ADM1031 2c 3 Ox5A Ox5E IC controller PCF8584 on Xbus and IMAX IC to I2C bus expander 2C 3 bus is attached to Port 1 of Imax e Temperature monitoring on the CPU 1 board Diode D1 CPU 1 die Diode D2 CPU 1 reference Temp2 CPU 1 PCF8591 2c 3 0x92 0x92 IC controller PCF8584 on Xbus and IMAX IC to IC bus expander 2C 3 bus is attached to Port 1 of Imax e DC DC voltage monitoring on CPU 1 AINO gt VCC VME backplane AIN1 gt 2 5V DDR voltage AIN2 gt 1 5V Jbus voltage AIN3 gt VCCP1 CPU 1 core voltage Memory 1 24LCS52 C 3 OxAO OxC6 IC controller PCF8584 on Xbus and IMAX IC to I2C bus expander 2C 3 bus is attached to Port 1 of Imax e DDR DIMM EEPROM SDF 1st DIMM Memory 1 24LCS52 2C 3 OxA2 OxC8 IC controller PCF8584 on Xbus and IMAX IC to 12C bus expander 2c 3 bus is attached to Port 1 of Imax e DDR DIMM EEPROM SDF 2nd DIMM Memory 1 24LCS52 2C 3 OxA4 OxCA IC controller PCF8584 on Xbus and IMAX IC to I2C bus expander 763 bus is attached to Port 1 o
21. PLD register 0x04 to 1 ok 3f 4 pldc lt Enter gt 3 Verify that bit 4 and bit 5 of PLD register 0x04 have been set to 1 ok 4 pldc lt Enter gt k BEY De edoae one Bit values returned are 00111111 4 2 Themis Computer USPIIli Software Manual 4 2 PLD Register Set The following is extracted from the register descriptions written in the VHDL source code of the PLD itself PLD register offset 0x00 Description PLD revision and ID Width 8 bit Vector name pld_reg 0 i Description bits 3 0 Revision of this PLD 0x0 and Oxf are reserved for engineering bits 7 4 CPU family ID 0001 gt Hummingbird 0010 gt Phantom 0011 gt Corsair 0100 gt CPU 3i PLD register offset 0x02 Description User jumper and Boot device jumper Width 8 bit Vector name pld_reg 1 i Description bit 0 RO Status of Jumper JP3901 0 JP3901 jumper is OFF 1 JP3901 jumper is installed bit 1 RO Status of Jumper JP3902 0 JP3902 jumper is OFF Boot device is the external Rombo 1 JP3902 jumper is installed Boot device is the on board OBP flash bit 2 RO Status of Jumper JP3903 0 JP3903 jumper is OFF 1 JP3903 jumper is installed Boot flash WRITE is enabled bit 3 RO Status of Jumper JP3908 0 JP3908 jumper is OFF The shutdown condition will force the board u
22. Register LSI5_TO Themis Computer 1 USPIlIli Programming Guide Table 1 6 Universe Il Register Map Continued Offset Register Name 104 Reserved 1C8 PCI Target Image 6 Control Register LSI6_CTL 1CC PCI Target Image 6 Base Address Register LSI6_BS 1D0 PCI Target Image 6 Bound Address Register LSI6 _BD 1D4 PCI Target Image 6 Translation Offset Register LSI6_TO 1D8 Reserved 1DC PCI Target Image 7 Control Register LSI7_CTL 1E0 PCI Target Image 7 Base Address Register LSI7_BS 1E4 PCI Target Image 7 Bound Address Register LSI7_BD 1E8 PCI Target Image 7 Translation Offset Register LSI7_TO 1EC 1FC Reserved 200 DMA Transfer Control Register DCTL 204 DMA Transfer Byte Count Register DTBC 208 DMA PCI Bus Address Register DLA 20C Reserved 210 DMA VMEbus Address Register DVA 214 Reserved 218 DMA Command Packet Pointer Register DCPP 21C Reserved 220 DMA General Control and Status Register DGCS 224 DMA Linked List Update Enable Register D_LLUE 228 2FC Reserved 300 PCI Interrupt ENABLE Register LINT_EN 304 PCI Interrupt Status Register LINT_STAT 308 PCI Interrupt Map 0 Register LINT_MAPO 30C PCI Interrupt Map 1 Register LINT_MAP1 Themis Computer Universe II VME Interface Registers USPIIli Software Manual Table 1 6 Universe Il Register Map Continued
23. Solaris ccccccceccceeseeeeeesseeeeeeeeeeeeeenaeens 3 15 3 31 VMEbus Nexis Diver 2 ccas ioc Sons Beeches aut a a 3 16 3 3 1 1 Installing the USPI i VME Nexus Driver 0 0 0 eeeeeeeeeeeee 3 17 3 3 1 2 Installing THEMIS3ivme occ secevisceouteAaetasdeeaneiendisets 3 17 3 3 1 3 Removing THEMES S1vitie ccossswlaaes st ecareNteceiss emasentiedseoees 3 20 3 3 2 Utlity DRIVES oseo Secteur tates Paar tui oa anes Se Se Sad Sed ae kal on eau 3 21 3 3 3 Installing the Sample Drivers ssa 7 idee steadiness havyecsdskdelidedead Atatedes woduedvann 3 21 3 3 3 1 Uninstalling the Sample Drivers a 3 ss0ct os etic 3 23 3 3 4 Sample VME Programs and VME Leaf Drivers ccccceseeeseesteeeeees 3 24 3 4 Writing Programs for the VMEbus cccecceeeseesseeesceeeseceeeeeeeeeseecaeceeeeeeeenaeees 3 25 3 4 1 Solaris Device Hierarchy sia eeitssneiisenicatiede aietete sae ates ieee 3 25 3 4 2 Configuring the Software Interface of USPI 0 0 cece ceeeeereeeteees 3 27 3 4 3 Accessing the VMEbus from OBP 4 cscetsncedvisshassecosandostiedeed Mesaedeencbanioas 3 27 3 4 4 Accessing the VMEbus from Solaris 20 0 0 cccceccceeceeseceneceeeeeeeeeeeeenseens 3 27 34 5 Using REA WEIS esc ieceel as cub ae es o a E leit E Rahal cts 3 27 Sail Usme mMap inei K easdocee A aaRS 3 29 3 4 5 2 Slave Mode Access to Another VME Board ccceeeeeeeees 3 29 3 5 Writing VME Device Drivers ssessessssssessesesesressessrssrossessresresseestesressesseesesr
24. Status of the jumper JP3907 signal xjp3907_1 0 The jumper is installed ON 1 The jumper is removed OFF Themis Computer 4 Programmable Logic Device PLD Register Set PLD register offset 0x07 Description SCSI termination status register Width 8 bit Vector name pld_reg 6 i Description bit 0 RO 0 NO SCSI peripheral has been plugged on the Front panel SCSI A connector 1 A SCSI device has been plugged into the front panel SCSI A connector bit 1 RO 0 NO SCSI peripheral has been plugged on SCSI A thru the VME P2 interface 1 A SCSI device has been plugged on the SCSI A bus thru the VME P2 interface bit 2 RO 0 The lower section of the SCSI A front panel termination is disabled 1 The lower section of the SCSI A front panel termination is enabled Lower section SCSI control lines and SCSI data lines 0 7 bit 3 RO 0 The upper section of the SCSI A front panel termination is disabled 1 The upper section of the SCSI A front panel termination is enabled Upper section SCSI data lines 8 15 bit 4 RO 0 The lower section of the SCSI A P2 termination is disabled 1 The lower section of the SCSI A P2 termination is enabled bit 5 RO 0 The upper section of the SCSI A P2 termination is disabled 1 The upper section of the SCSI A P2 termination is enabled bit 6 RO Status of th
25. Table 2 2 VME OBP Comma ds osinean a aa a ae aeaiia 2 3 Table 3 1 OBP Environment Variables sn ssssseeseesesssesseeseseesseeseesresseesresrsseesseserssesse 3 3 Table 3 2 OBP VME Environment Variables cccccssccssscssescsscsssccesncesenscseceseccesnaes 3 5 Table 3 3 Last Of OBP aliases asinine E E E R E cash ne ERR 3 14 Table 3 4 VMEbus Interrupt Mapping seeseseesseessesseesessseeseesresresseesesrssseesreserssresseseess 3 17 Table 3 5 yvmemem Device Driver se ssesesesseseesrsseesresersseesressesersstessesrrssressessessressesse 3 21 Table 3 6 VME Special Piles riri minnannona aa a a hata a 3 28 Table 3 7 Address Spacen EnA E R oa R E 3 33 Table 3 8 Temperature Monitoring Commands ecceececeeeseceteceeeeeeeeeeeeenseenteeeees 3 41 Table 3 9 Voltage Monitoring Commando cc ceceecceesceeeteceeeceeeeeesceceaeceeeeeeeeeseeesaeees 3 42 Table 3 10 User Status LED Commands ccecceccssscssetccssnsssccesacessnscenccssccesacessaceuaes 3 42 Table3 0 PLD Commands 1n i3csvhaslec casei wate E E eh uais sah AR E 3 42 Table 5 1 Voltages Monitored on the CPU 0 and CPU 1 Boards ceceeeeteeseeeteeeee 5 8 x Themis Computer How to Use This Manual Introduction The Themis Computer USPHIi is an UltraSPARC IIIi based multi slot VME com puter see photo below that is SPARC version 9 0 compliant with a VMEbus inter face The software interface for the VMEbus and other on board peripheral devices
26. The EEPROM contains the information that is spe cific to our implementation When the EEPROM is not present or is blank the PCI9030 ASIC will automatically set the PCI configuration registers to their default values It is then possible to program from the PCI bus Utility functions are avail able under OBP to program and or reprogram the content of the EEPROM for the initialization phase of the product Utility functions are also available to fix on site issues without having to return the board to manufacturing for upgrade Table 1 5 EEPROM Addresses and Data EEPROM EEPROM Caras Address Data 0x00 0x9030 PCI device ID 0x02 0x10B5 PCI Vendor ID 0x04 OxCA90 0x06 0x0000 0x08 0x0680 Ox0A 0x0000 The Rev ID should match the original rev ID 0x0C 0x0000 Ox0E 0x0000 0x10 0x0000 0x12 0x0040 0x14 0x0000 0x16 0x0100 0x18 0x4801 Ox1A 0x4801 0x1C 0x0000 0x1E 0x0000 Themis Computer 1 11 USPIIli Software Manual Table 1 5 EEPROM Addresses and Data Continued EEPROM EEPROM Commer Address Data 0x20 0x0000 0x22 0x4c06 0x24 0x0000 0x26 0x0003 0x28 0x0F80 LASORR for User flash 0x2A 0x0000 8 Mbytes memory space No prefetch 0x2C 0x0000 LAS1RR not assigned 0x2E 0x0000 0x30 OxOFFF LAS2RR for TTY C D 0x32 OxFF81 128 Bytes IO space 0x34 OxOFFF LAS3RR for PLD registers 0x36 OxFFO1
27. as an offset for the lseek system call and does a read or write operation at the offset The offset must fall within the physical address range of the file that was opened also there should be a VMEbus device that would respond to the address To access 16 bytes at the VMEbus address 0xa0000 the following code snippet can be used Lente ae int vme_base char buffer 16 if fd open dev vme24d32 O RDWR lt 0 perror In opening file dev vme24d32 return 1 vme_base 0xa0000 if lseek fd vme_base SEEK SET lt 0 perror In lseeking to 0xa0000 close fd return 1 if read fd buffer sizeof buffer sizeof buffer perror In reading 16 bytes close fd return 1 3 28 Themis Computer 3 Themis USPIIli Software 3 4 5 1 3 4 5 2 Writing Programs for the VMEbus In the above example if there is no device on the VMEbus at address 0xa0000 the VMEbus operation will time out and the program will return 1 with errno set to EFAULT Using mmap A faster way to access VMEbus space is to use the mmap 2 system call mmap establishes a mapping between the user process s address space and a memory object represented by an open file The dev vmeXXdYY files can be used for mmap as well For example to access a region of length 1000 bytes in the VMEbus space starting from location 0x500 the following code seg
28. course of installation pkgadd will prompt you for input on optional con figuration The first prompt will ask you to choose the packages to be installed 32 64 bit al to process EMIS3ivme gt from lt THEMIS3ivme file gt t Solaris 9 for Solaris 9 e on the Themis vmeme retained currently used execu rnel CE now stalled nstalled ted with super user permission during the process of installing this package Do you want to continue with the installation of lt TH y EMIS3ivme gt y n Themis Computer 3 Themis USPIIli Software Ins as Ins ve ve ami aa fall tg oO M oooowoovoeweopa Ww w ae ee eb RRL ORG RD eb OD RD SD ABT Gg rPRPrPRPrPEP PEE Et oO c i c i c i e a e i e i eri c s usr s usr s veri opt T opt T opt T opt T opt T opt T opt T opt T opt T opt T opt T opt T opt T opt T opt T opt T opt T opt T opt T v u u u u u u HNN OE AOE OE E YN O O O O O O O O O O 10 rifying c ncl ncl ncl ncl ncl ncl fyi na na na IT E E EEE EEA ERR EAA EA A e talling Themis VMI lt THEMIS3ivme gt Executing preins talling part 1 of 1 fying class lt none gt fying class fying rm su rm su class u ma m su m su m su m su m su m su m su m su m su Rs SS SS SSS Cle Ie Se a Se R a
29. ddi_attach_cmd_t cmd struct xxstat xsp int nbint i if cmd DDI_ATTACH return DDI _FATLURE get the number of interrupt definitions if ddi_dev_nintrs devi amp nbint DDI FAILURE cmn_err CE _WARN xx No interrupts property return DDI _FATLURE 3 35 Themis Computer USPIIli Software Manual for i 0 i lt nbint i Register first with a null handler so that the interrupt routine doesn t grab the mutex KJ if ddi _add_intr dip i amp xsp gt iblock_cookie i NULL u_ int caddr_t nulldev NULL DDI SUCCESS cmn_err CE_WARN xx cannot register interrupt return DDI FAILURE Initialize the mutex now mutex init amp xsp gt mu xx mutex MUTEX DRIVER void xsp gt iblock_cookie i Remove the interrupt and register again with the correct interrupt handler A ddi_remove_intr dip i xsp gt iblock_cookie i if ddi_add_intr dip i amp xsp gt iblock_cookie il amp xsp gt idevice cookie i xxintr NULL DDI SUCCESS cmn_err CE WARN xx cannot register interrupt return DDI FAILURE cmn_err CE_NOTE Registered interrupt d with priority d and vector OxSx i xsp gt idevice_cookie i idev_priority xsp gt idevice_ cookie i idev_vector Themis Computer provides a sample device driver vmeintr to illustr
30. is for testing purpose The other is the normal operating mode For test the address 0b11110xx1 is used For operating mode the address 0b11110xx0 is used The semaphore is dedicated for the management of shared resources among multiple CPU owners Only one CPU can own the shared resources at any given time Bit 0 of the semaphore is used as the busy or owned bit When this bit is set to 1 it means the semaphore is used by somebody and any other pretender to access to the shared resources must wait for Themis Computer USPIIli Software Manual this owned busy bit to be cleared by the owner In order to identify who is the owner to troubleshoot an ownership conflict problem it is suggested to use the two don t care address bits 2 1 as the Owner ID This means that the S W responsible to manage the semaphore resource will assign a different address one out of four for each of the owners maximum of 4 Behavior in operating mode Upon reset the semaphore content is cleared This means no one owns the semaphore When a CPU wants to get ownership of a shared resource it will first get ownership of the semaphore It will do so by polling the semaphore and checking the ownership bit If the ownership bit is read as 0 that means that the semaphore was free and thanks to the H W mechanism implemented in this logic the CPU is now becoming the owner of the semaphore When the read occurs the
31. logic checks if the owned busy bit is set If it is set the address bits 2 1 which by convention identifies the owner is stored into the semaphore bits 2 1 If it is not set the owner ID bits of the semaphore are left unchanged Upon read the semaphore owned busy bit is always set to 1 meaning owned busy is asserted only after the previous content has been provided to the polling CPU The setting of the owned busy bit occurs atomically on the trailing edge of the read access When the CPU wants to release the ownership of the semaphore it simply writes to the semaphore with bit DO set to 0 The write access automatically clears the owner ID to 0 Behavior in test mode The register behaves like any standard REad Write register Only bits 2 0 are writable In test mode bit 2 0 RW Upon reset these bits are cleared bit 7 3 RO Read as 0 In operating mode bit 0 Read to Write 1 Upon reset this bit called Busy bit is cleared A read access automatically sets this bit to 1 AFTER the read has been completed and BEFORE anyone accesses to it A write access will set the bit according to the value on DO bit 2 1 exotic RW Upon reset these bits called Owner ID are cleared On read access address bits 2 1 will be stored in this register bits if the Busy bit is clear at the beginning of the read access If the Busy bit is set at the beginning of the read access these bits ret
32. output by this program can be used by other boards on the VME bus chassis to gain access to this DVMA region For example if a second board on the same chassis needs to access this region one can execute this command Themis Computer 3 Themis USPIIli Software Writing Programs for the VMEbus od x dev vme24d32 slave_address where slave_address is the virtual address output by the program The DVMA region can be accessed from the same system by invoking the ioctl calls implemented by the vmedvma driver The following code segment fills a DVMA region with zeros starting from offset 0x500 struct vme_dvmacopy dma_write char buffer buffer malloc 4096 dma_write id 1 dma_write addr caddr_t buffer dma_write size 4096 dma_write offset 2048 if ioctl fd VDMA WRITE amp dma_write 0 perror In initializing DVMA region close fd return 1 3 31 Themis Computer USPIIli Software Manual 3 5 Writing VME Device Drivers A device driver is a kernel module responsible for managing low level I O opera tions for a particular hardware device Some device drivers manage fake devices that exist only in software A device driver contains all the device specific code to communicate with a device Like the system call interface protects application pro grams from the specifics of the platform the device drivers protect the kernel from the specifics of the de
33. situations where developing a custom device driver may not be necessary It discusses mechanisms by which most device operations can be performed from the user level Driver configuration files pass information about device drivers and their configura tion to the system Since VMEbus devices are not self identifying drivers for these devices need to use driver configuration files to inform the system that the device hardware may be present The configuration file also must specify the device addresses on the VMEbus and any interrupt capabilities that the device may have Themis Computer 3 Themis USPIlIli Software Writing VME Device Drivers The syntax of an entry in the configuration file is name driver name class vme reg interrupts Specifying class as vme indicates to the kernel that the device driver is for a VME bus device and should be attached to the VMEbus nexus driver On USPIIi systems the bus nexus driver is named pcivme Two common properties of interest to VME device drivers are the reg and interrupts properties The reg property is an array of 3 tuples address space offset and length Each 3 tuple describes a contiguous resource registers that can be mapped The value of the address space is derived from the following table Table 3 7 Address Space Address Space Value A16 D16 0x2D A24 D16 0x3D A32 D16 OxD A16 D32 not supported A24 D32 0x7D A32 D32 0x4D
34. vmeintr n vmeintr conf conf sample rv remove sample rv src Makefil rv src vmedvma c rv src vmeintr c e Themis Computer 3 19 USPIIli Software Manual opt THEMIS3ivme drv themis universe h opt THEMIS3ivme drv themis vmebustypes h opt THEMIS3ivme drv themis vmedvma h opt THEMIS3ivme drv themis vmeintr h opt THEMIS3ivme example Makefil opt THEMIS3ivme example dmatest opt THEMIS3ivme example dmatest c opt THEMIS3ivme example sparcv9 dmatest opt THEMIS3ivme example sparcv9 sw_reset_n_ sysfail opt THEMIS3ivme example sparcv9 sysfail test opt THEMIS3ivme example sparcv9 vme_dvma opt THEMIS3ivme example sparcv9 vme_intr opt THEMIS3ivme example sparcv9 vme_mmap opt THEMIS3ivme example sparcv9 vme_rw opt THEMIS3ivme example sw_reset_n_sysfail opt THEMIS3ivme example sw_reset_n_sysfail c opt THEMIS3ivme example sysfail_ test opt THEMIS3ivme example sysfail _test c opt THEMIS3ivme example vme_dvma opt THEMIS3ivme example vme_dvma c opt THEMIS3ivme example vme_intr opt THEMIS3ivme example vme_intr c opt THEMIS3ivme example vme_mmap opt THEMIS3ivme example vme_mmap c opt THEMIS3ivme example vme_rw opt THEMIS3ivme example vme_rw c verifying class lt sample gt Executing postinstall script Reboot client to install driver Reboot client to install driver Reboot client to install driver Reboot client to instal
35. 25 VMEbus Index 4 accessing from OBP 3 27 accessing from Solaris 3 27 interface xi mapping 3 39 Nexus driver 3 16 vmeintr 3 24 voltage measurement 5 voltage monitoring commands 3 42 voltages monitored CPU 0 and CPU 1 Boards 5 8 W warning threshold temperature 5 3 website www themis com xv writing programs 3 25 writing VME device drivers 3 32 X Xbus to I2C bridge 1 9 Themis Computer
36. 256 Bytes IO space 0x38 0x0000 Ox3A 0x0000 0x3C 0x0000 Ox3E 0x0001 Enable Cs0 space address decoding on PCI 0x40 0x0000 0x42 0x0000 Disable Cs1 space address decoding on PCI 0x44 0x0000 0x46 0x0001 Enable Cs2 space address decoding on PCI 0x48 0x0000 Ox4A 0x0001 Enable Cs3 space address decoding on PCI 0x4C 0x0000 0x4E 0x0000 0x50 0x5431 1 12 Themis Computer 1 USPIIli Programming Guide Table 1 5 EEPROM Addresses and Data Continued PCl Ebus Bridge Configuration EEPROM EEPROM EEPROM Connnent Address Data 0x52 0xB8CO 0x54 0x0000 0x56 0x0000 0x58 0x5431 0x5A 0xB8C0 0x5C 0x5431 0x5E 0xB8C0 0x60 0x0000 0x62 0x0000 0x64 0x0080 0x66 0x0001 0x68 0x0000 Ox6A 0x0000 Ox6C 0x0000 Ox6E 0x0081 0x70 0x0000 0x72 0x0101 0x74 0x0030 0x76 0x0040 0x78 0x0078 Ox7A 0x0000 Ox7C 0x0024 Ox7E 0x9240 Themis Computer 1 13 USPIIli Software Manual 1 8 Universe II VME Interface Registers The Universe II Control and Status Registers UCSR facilitate host system configu ration and allow you to control Universe II operational characteristics The registers are divided into the following groups e VMEbus Configuration and Status Registers e Universe II Device Specific Status Registers The Universe II registers have little endian byte ordering e PCI Configuration Space A Universe II register map is s
37. 3 14 through 3 17 Chapter 3 Global changed THEMISvme to THEMIS3ivme on pages 3 16 through 3 20 Chapter 3 Added two paragraphs to the bottom of page 5 3 in Section 5 2 Thermal Monitoring regarding detection of temperature error conditions Chapter 5 Added 1 sentence to the bottom of page 5 7 in Section 5 2 1 Setting Temperature Thresholds regarding the usp3i_temp m utility Chapter 5 Removed references to company internal infrastructure tintin throughout the document Changed single board computer to multi slot VME computer in the introduction of page ix Preface Added a note regarding the look of the ok prompt in Section 2 2 OBP VME Environment Variables on page 2 1 Chapter 2 Added footnote b regarding VME address windows to Zable 2 1 on page 2 2 Chapter 2 Added a note to Section 2 3 Additional VME OBP Commands on page 2 3 regarding OBP commands not available in all versions of OBP Changed Openboot 3 x to Openboot 4 x in Table 2 2 on page 2 3 Chapter 2 Deleted obsolete commands from Table 2 2 on page 2 3 Chapter 2 Reworded the note on in Section 3 2 1 OBP VME Environment Variables on page 3 2 Chapter 3 Revised and added text to the last paragraph on page 3 2 regarding different OBP environment variables in different OBP versions Chapter 3 Deleted the values for the nvramre environment variable in Table 3 1 on page 3 4 Chapter 3 Added a referenc
38. 3 15 device hierarchy 3 25 SPARC version 9 0 xi Sun documentation 1 9 Sun native firmware 7 7 SUN OBP Open Boot Prom See OBP SUN Solaris 3 15 System board xii 5 1 T temperature 3 41 monitoring commands 3 41 thresholds 5 4 temperature sensor controller ADM1031 5 3 THERM output 5 3 TGA3D 3D Graphics board xii Themis website www themis com xv THEMIS3ivme 3 17 3 20 themis show pld command 4 11 themvme 3 6 THERM output 5 3 thermal measurement 5 thermal sensors 5 thresholds temperature 5 4 Tomatillo 2 1 3 TTY C and D ports TTY C D 8 bit bus 7 10 Index 3 Themis Computer USPIIli Software Manual U UCSR access mechanism 4 uninstall sample drivers 3 23 Universe II controller 2 7 register map 5 UNIX commands xiv updating Flash PROM 3 6 3 8 from a SCSI disk 3 8 User Flash AMD29LV065 1 10 User LED I2C driver user status LED commands 3 42 USPI device monitors 5 2 device monitors placement of 5 2 environmental monitoring applications usp3i_pld 3 42 usp3i_temp 3 41 usp3i_uled 3 42 usp3i_voltage 3 41 I2C devices 1 6 installing the VME Nexus driver 3 17 models xiii photo of xi programming guide slot configurations xiii software 3 1 utility drivers 3 27 Vv VME environment variables table 2 2 interface registers 7 14 leaf drivers sample 3 24 P2 Paddle board xii programs sample 3 24 slot configurations xiii special files 3 28 vme_dvma 3 24 vme_intr 3 25 vme rw 3
39. 3f 8 a If your system has a graphics card installed you will also see a screen alias defined for your particular graphics card For example a Themis TGA 100 card screen alias would look like this screen pci lc 600000 pci 2 SUNW XVR 100 2 Themis Computer 3 Themis USPIIli Software Overview of VME Interface Under Solaris 3 3 Overview of VME Interface Under Solaris Great effort has been expended to achieve complete compatibility between Sun VME implementations and the device driver interface implemented for the USPIIi board under Solaris This section is primarily concerned with the implementation and programming of USPIIli specific features that are not common to the Sun UltraSPARC family of workstations and servers It assumes that the reader is familiar with the Sun4u archi tecture and concepts of the VMEbus and the device drivers The VMEbus interface of the USPIIIi is transparently implemented under Solaris 2 The software interface is fully compatible with generic Sun4u VME architecture systems Any VME device driver that conforms to the appropriate Solaris Device Driver Interface will run unmodified on Themis platforms Themis Computer has developed a number of device drivers to provide the neces sary software interface needed by system programmers The drivers can be classified into three categories e VMEbus Nexus driver e Utility drivers e Sample drivers The drivers are described in the
40. 600 8 n 1 9600 8 n 1 screen keyboard false 16384 true boot net disk net false No default No default No default none max false boot 3 4 Themis Computer 3 Themis USPIIli Software SUN OpenBoot PROM OBP Table 3 2 OBP VME Environment Variables Name Value Default Value Description If set to true Universe II is forced to be the system controller If set to false the force system controller true false false system controller status is determined by auto sensing circuitry vme bus request level 0 7 0 Level used to request the VME bus jmereo est mod fairidemand fair When the Universe II requests the VME bus q it can use either fair or demand mode When the Universe II releases the VME vme release mode ror rwd ror bus it can use either ror release on re quest or rwd release when done vme arbitration mode round robin priority round robin PANTANO ModE CSEL EDEN SPIE NE system controller VME bus interrupt level to be serviced by vme irq to service 1 2 3 4 5 6 1 2 3 4 5 6 the VME leaf driver Defines a master window on VME All subse quent VME mappings that fall within this win dow will use this window instead of allocating res aemacicr base 04294967295 0 one of the remaining Universe II register sets to define a new window The best use of this master window is to define it to encompass all ot
41. AG lease fis a a emacs ct ocean beeen arose a oles aas 5 8 MTR Cs a theese a ie ges aes eae leaked cl ead aes ete ee a ied ate el R EEEE I l ix Themis Computer USPIIli Software Manual List of Figures Figure 1 1 Jbus Address Space Mapping to PCI Configuration Space eee 1 4 Figur 1 2 2C Bus Ten Glo sy covcccuasrceaesecud abs nanena aiaia 1 5 Figure 1 3 UCSR Access Mechanistiis iiiisseccsiccscirssiarieds dcssstes nv atagenessstedind Ataewm cased 1 14 Figure 3 1 Nexus Driver Directory Stricture scaccctu deed es micas 3 16 Figure 3 2 USPIM Device Tree csstceticstekaw tars testaaw con a nade dea skis anda aka 3 26 Figure 5 1 Placement of USPIITi Device Monitors 0 cee ceceeseeceeeeceseeeeceeeceaeeeeeneeeneees 5 2 Figure 5 2 Outputs of the Temperature Sensor Controller ceceecceecesecseereeneeeneeeneees 5 3 List of Tables Table 1 1 HTSUS TBA SST OTN ineine nannan eai erases pate a iaai tines 1 3 Table 1 2 Jb s Address Mapi inverse tis cze les onto nie aea a a a A 1 3 Table 1 3 USPI 2C Devices eeen e aE E EE EER E A a a eek 1 6 Table 1 4 USPI Ebs Devices acceeasi anie niat a a 1 10 Table 1 5 EEPROM Addresses and Datta scccicesssicecscectacassatseess Conadecvsty es Sats tdes Meceaneceees 1 11 Table 1 6 Universe I Register Map css sessciycvcassccushaetntedosdexareatelevaertaceesbhceestasawietudeadactes 1 15 Table 2 1 OBP VME Environment Var abl eps csvuuccessvaes ectasiicaactuasaiaasuadateatebed atu asatuiees 2 2
42. ELEASE notes drwxr xr x 6 bin bin 512 Aug 23 15 02 drv drwxr xr x 3 bin bin 512 Aug 23 15 02 example drwxr xr x 3 bin bin 512 Aug 23 15 02 man cd drv ls la total 28 drwxr xr x 6 bin bin 512 Aug 23 15 02 drwxr xr x 6 bin bin 512 Aug 23 15 02 rw r r 1 bin bin 2964 Mar 4 2004 README first drwxr xr x 3 bin bin 512 Aug 23 15 02 bin rwxr xr x 1 bin bin 2474 Mar 4 2004 install sample EWXE Xr X 1 bin bin 1797 Mar 4 2004 remove sample drwxr xr x 2 bin bin 512 Aug 23 15 02 src drwxr xr x 2 bin bin 512 Aug 23 15 02 sys drwxr xr x 2 bin bin 512 Aug 23 15 02 themis install sample KKK KKK KKK KKK KK KKK KKK KKK KKK KKK KKK KKK KKK KKK KKK KKKKKKKKKK x Installation Script for Themis USPIIIi Solaris 9 K sample device drivers x kkkxkxkxkxkxkxkxkxkxkkxkxkxkxkkxkkxkxkxkxkkkxkxkxkkkxkxkxkxkkxkkxkxkkxkkkxkxkxkkkxkkkkx k This script installs the sample device drivers for Solaris 9 to use the VMEbus interface on the Themis USPIITi The script creates symbolic links under dev for the device special files If you want to proceed type y or Y Otherwise press any other key to abort y 3 22 Themis Computer 3 Themis USPIIli Software Overview of VME Interface Under Solaris Replacing vmeintr interrupt driver Replacing vmedvma DVMA driver Updating etc devlink tab Installing new drivers Copying header files Installation completed 3 3 3 1 Uninstalling the Sample Driver
43. GA3 pull up 1 GA3 tied to GN D by the VME64X backplane bit 4 RO Status of VME P1 signal GA4 pin P1 D17 0 GA4 pull up 1 GA4 tied to GN D by the VME64X backplane bit 5 RO Status of VME P1 signal GAP pin P1 D9 0 GAP pull up 1 GAP tied to GND by the VME64X backplane bit 6 RO Read as 0 bit 7 RO Read as 0 Encoding table for the GAx register bits GAP GA4 GA3 GA2 GAI GAO slot ID mere rere rer cocoocoocoococoococococmcrUrCUNCCcCOCcSC OO OOOO m j i a ee FP rRPOOOCOrFRrFRrFP FR ODO ORFF rH OO Por Or OF OF OF OF OF Or Or Oo i Li O GOG e OM m Or O OH Orr OG l OF OSC oom coor rKrcoorraocorFrHoorH 0 0 0 1 Ox01 gt 1 0x02 gt 0x23 gt 0x04 gt 0x25 gt 0x26 gt 0x07 gt 0x08 gt 0x29 gt 9 0x2a gt 10 0x0b gt 11 0x2c gt 12 0x0d gt 13 Ox0e gt 14 0x2f gt 15 0x10 gt 16 0x31 gt 17 0x32 gt 18 0x13 gt 19 0x34 gt 20 0x15 gt 21 0 0 0 0 0 0x00 gt No VME64X compliant OCADNA RWW other values are illegal symptom of a problem Themis Computer 4 Programmable Logic Device PLD Register Set PLD register offset 0x04 Description VME reset control status Width 8 bit Vector name pld_reg 3 i Description bit 0 RO Status of the Jumper JP2101 0 The jumper is OFF and the board set in auto sensing mode
44. ID 0x41 41 Revision m 33 Remote 1 temperature parameters Temperature High limit 100 Temperature Low limit 0 Temperature THERM limit 110 Temperature gt Remote 1 E32 Remote 2 temperature parameters Temperature High limit 100 Temperature Low limit 0 Temperature THERM limit 110 Temperature gt Remote 2 36 Local temperature parameters Temperature High limit 70 Temperature Low limit 0 Temperature THERM limit 80 Temperature gt local 31 CPUO Temperature I2C address 5G Device ADM1031 Analog devices ADM1031 device ID 0x31 se Sal Company ID 0x41 41 Revision Hrag Remote 1 temperature parameters Temperature High limit 105 Temperature Low Limit 5 Temperature THERM limit 125 Temperature gt Remote 1 60 Remote 2 temperature parameters Temperature High limit 105 Temperature Low Limit 3 5 Temperature THERM limit FELS Themis Computer USPIIli Software Manual Temperature gt Remote 2 45 Local temperature parameters Temperature High limit 70 Temperature Low limit 0 Temperature THERM limit 80 Temperature gt local 35 CPU1 Temperature I2C address 5e Device ADM1031 Analog devices ADM1031 device ID 0x31 3T Co
45. LD registers plxdrv is a device driver for the PLX PCI9030 bridge chip that maps the memory space for the Cypress PLD CPLD residing on the ebus see Table 3 11 To add the pl xdrv driver to the system use the following command cp plxdrv usr kernel drv sparcv9 plxdrv add dry i peil0b5 9030 plxdrv Table 3 11 PLD Commands Command Description usp3i_pld Dumps all the PLD registers usp3i_pld g lt offset gt Gets the byte at the specified register offset usp3i_pld p lt offset gt lt value gt Puts the new value at the specified register offset 3 42 Themis Computer Software Section Chapter Programmable Logic Device The USPHIi Programmable Logic Device PLD is accessible through the EBus and has many registers that are used to control a variety of different functions These reg isters are described in the final section of this chapter Access and control of PLD registers require a knowledge of PLD functions described in the following section 4 1 PLD Function Upgrade Certain PLD functions have been added to OBP 3 2 to facilitate the operation and analysis of the USPIIi system These include Enemies Shows PUGS modrere iinet a Displays a list of all functions pld revisIron Status Agi aie ain a See PLD register 0x00 user and boot device jumpers See PLD register 0x02 Jump t stat s ymz S lot eranen na i See PLD register 0x03 yme reset mode sJ nee iene aE ea See PLD r
46. Monitors Themis Computer 5 Device Monitoring Thermal Monitoring The temperature sensor controller ADM1031 provides two outputs One THERM is asserted to report that the temperature has risen above the warning threshold called Therm limit in the ADM1031 datasheet and is deasserted when the temper ature reaches a full 5 C below the Therm limit threshold The other INT or SMBALERT is asserted when the temperature is out of the pro grammable temperature low and high thresholds The behavior of these two signals is illustrated in a simplistic way in Figure 5 2 5 C THERM gt Temperature Tlow Thigh Therm limit Figure 5 2 Outputs of the Temperature Sensor Controller The default behavior of the OBP is to initialize the temperature sensors in non interrupt mode However interrupt mode is enabled if a temperature related error condition occurs during the OBP boot process If this occurs the appro priate CPU1 CPU0 OVER TEMP or SYS OVER TEMP front panel LED lights up indicating an error condition To detect over under temperature conditions under Solaris run the utility usp3i_temp in monitor mode m Upon detection of a temperature error condition the sensor interrupt bit is turned on and the appropriate front panel LED lights up as defined in the previous paragraph 5 3 Themis Computer USPIIli Software Manual 5 4 5 2 1 Setting Temperature Threshold
47. PARC Ile to UltraSPARCIIIi Chapter 3 Updated reference material revision and part numbers in Section 3 2 SUN OpenBoot PROM OBP on page 3 1 Chapter 3 Updated Table 3 2 on page 3 5 to match Table 2 1 on page 2 2 Chapter 3 Changed usp31 rev1 6 to usp31 rev3 7 in step 1 of Section 3 2 4 Updating the System Flash PROM on page 3 6 iii Themis Computer USPIIli Software Manual Version Revision History Deleted Table 3 3 from Section 3 2 5 Additional OBP Commands on page 3 8 and referred the reader to Table 2 2 Chapter 3 Changed Unix system administrator to Themis Technical Support in the last paragraph of Section 3 2 4 Updating the System Flash PROM on page 3 7 Chapter 3 Added Section 3 2 4 2 Updating the System Flash Prom From a SCSI Disk on page 3 8 Chapter 3 In the last paragraph of Section 3 2 5 1 Accessing VME Address Space from OBP on page 3 9 changed reset command to reset all and added the VME select dev command Chapter 3 Changed Sun s Solstice to smosservice and or smdiskless in the 2nd to last paragraph on page 3 14 in Section 3 3 Overview of VME Interface Under Solaris Chapter 3 Added sections 3 3 through 3 5 5 on pages 3 14 through 3 39 to include the VME program documentation from the USP 2 Programmer s Guide manual Chapter 3 Global changed driver names themvme to pcivme and sbvmemem to vmemem on pages
48. USPIIli Software Manual Version 1 3 November 2005 THEMIS P Themis Computer Americas and Pacific Rim Themis Computer Rest of World 47200 Bayside Parkway 5 Rue Irene Joliot Curie Fremont CA 94538 38320 Eybens France Phone 510 252 0870 Phone 33 476 14 77 80 Fax 510 490 5529 Fax 33 476 14 77 89 World Wide Web http www themis com Copyright 2005 Themis Computer Inc ALL RIGHTS RESERVED No part of this publication may be reproduced in any form by photocopy microfilm retrieval system or by any other means now known or hereafter invented without the prior written permission of Themis Computer The information in this publication has been carefully checked and is believed to be accurate However Themis Computer assumes no responsibility for inaccuracies Themis Computer retains the right to make changes to this publication at any time without prior notice Themis Computer does not assume any liability arising from the application or use of this publication or the product s described herein RESTRICTED RIGHTS LEGEND Use duplication or disclosure by the United States Government is subject to the restrictions set forth in DFARS 252 227 7013 c 1 ii and FAR 52 227 19 TRADEMARKS THEMIS is a registered trademark of Themis Computer Inc SOLARIS is a trademark of Sun Microsystems SPARC and UltraSPARC are registered trademarks of SPARC International All other trademarks or registered trademarks use
49. access this memory region from another system on the VMEbus chassis by using this command od x dev vme24d32 0x588 3 38 Themis Computer 3 Themis USPIIli Software 3 5 4 3 5 5 Writing VME Device Drivers Mapping VMEbus Space On some occasions it would be convenient to map a chunk of VMEbus address space into the system s memory From the user level this can be done by doing an mmap operation on the appropriate dev vmeXXdYY file From the driver level mapping VMEbus address space can be done by using the ddi_map_regs function As an example to map two pages of VMEbus space starting at location 0x66000000 the following code segment can be used if ddi_map_regs dip 0 amp map_space 0x66000000 off t 8192 DDI_ SUCCESS return EFAULT On return from the function map_space contains the base address of the kernel vir tual region There are many caveats to using ddi_ map _ regs to map a portion of VMEbus address space e An A32 D32 device can only map a chunk from A32 D32 address space e The address space indicated by offset offset len must be a valid region on the VMEbus e Access to the mapped region should be localized Subsequent access to locations that are far apart will result in many page faults particularly on regions of larger sizes It is prudent to use the ddi_peek and ddi_poke routines to access a region mapped using ddi map _regs Driving Devices W
50. ae E ss u lass ude t ude ude ude ude ude ng c re ma re ma re ma lass n ma n ma n ma fying class MIS3ivme MIS3ivme MIS3ivme MIS3ivme MIS3ivme Ke Ke Ke Ke Ke devlink gt system gt nel nel nel nel nel lt lt E Drivers for SPARC USPIITi Overview of VME Interface Under Solaris 32 64 bit Solaris 9 tall script drv pcivme drv sparcv9 pcivme drv sparcv9 sysfail drv sparcv9 vmedma drv sparcv9 vmemem Ke Ke Ke Ke Ke nel nel nel nel nel drv sysfail drv sysfail conf darv vmedma darv vmedma darv vmemem conf Ke MIS3ivme d MIS3ivme d MIS3ivme d MIS3ivme d MIS3ivme d MIS3ivme d MIS3ivme d MIS3ivme d MIS3ivme d MIS3ivme d MIS3ivme d MIS3ivme d MIS3ivme d MIS3ivme d Tf 1 Py Py By By Ry PY PE PY RY nel lt drv gt lt include gt n7 vmedma 7 lt manpage gt DOC ddi_pee DOC mailbox DOC sw_rese DOC vmein RELEASE rv README rv bin ddi cv bi cv bi cv bi rv bi rv bi rv bi rv bi rv install n spa n spa drv vmemem Ls conf hemis sysfailio h themis vmebustypes h themis vmectlio h themis vmedmaio h themis vmedvma h themis vmeintr h n7 vmedvma 7 n7 vmeintr 7 kpoke DOC DOC t_n_sysfail DOC DOC notes pias peekpoke32 n sparcv9 ddi_peekpoke64 rcv9 vmedvma ccev9 vmeintr n vmedvma n vmedvma n
51. appropriate Solaris Device Driver Interface will run unmodified on Themis platforms This section is intended for system programmers who are not familiar with the Solaris architecture and the concepts of the VMEbus The guide discusses the con cepts of Solaris drivers and VMEbus devices as they pertain to the Themis USPIIIi product The section is intended as a general introduction of the basic concepts of using the USPIIIi product under Solaris Solaris Device Hierarchy Solaris systems support architecture independence of devices by using a layered approach Devices and buses are represented in a data structure resembling an inverted tree Each node in the tree structure has a specific device function Standard devices are associated with leaf nodes The drivers for these devices are called leaf drivers The intermediate nodes in the tree are associated with buses like PCI bus VMEbus etc These nodes are called bus nexus nodes and the drivers associated with Themis Computer USPIIli Software Manual them are called bus nexus drivers The bus nexus driver encapsulates all the architec tural dependencies of a particular bus The leaf driver only needs to know the kind of bus it is connected to The device tree for USPIIi systems is shown below root PCI Bus pcivme esp vmedma vmemem Figure 3 2 USPIIli Device Tree In this diagram root pcivme and PCI bus are bus ne
52. are required to have a probe entry point Usually the probe entry point tries to map the registers and then attempt to access the hardware using any of the peek and poke routines The probe entry point should not initialize the device in any way it also should not ini tialize any of the software state Mapping registers from VMEbus space do not need any special considerations The ddi_map_regs function call can be used to map the registers this function will take care of the VMEbus address space that the register set is in The following code segment is an example of mapping a register set and carefully accessing a byte in the set xxprobe probe for this device x static int xxprobe dev_info_t dip struct my_reg str regs Device registers caddr_t kaddr mapped register address int retval return value If we re self identifying then we re here xy if ddi_dev_is sid dip DDI SUCCESS return DDI PROBE SUCCESS Probe the device by mapping the registers and reading the command register and the parm7 register This assures that something is there The attach routine will try to run more rigorous checks So this simple check is all we really need here x Themis Computer 3 Themis USPIIli Software 3 5 2 Writing VME Device Drivers if retval ddi_map_regs dip 0 amp kaddr 0 0 DDI_SUCCESS cmn err CE_WARN
53. ase and vme32 master size 2 2 Themis Computer 2 OBP Commands Additional VME OBP Commands 2 3 Additional VME OBP Commands The following table describes a list of OBP commands that are accessible when the current node is VME To set the current node to VME execute the OBP command vme select dev mand If this command does not work on your system use the command f Note Some versions of OBP do not employ the vme selelct dev com od peatle GO00007 THEMIS perume Table 2 2 VME OBP Commands Command Description show universe regs Reads and displays all the Universe II registers Reads and places on the OBP stack the Universe II register content located at offset lt offset gt from the Universe II base address Consult the Sun Open Boot 4 x Command Reference for instructions on displaying stack contents for example the com mand showstack lt offset gt universe reg Reads and displays the Universe II register contents lt offset gt universe reg located at offset lt offset gt from the Universe II base address Writes the value lt data gt into the Universe II register lt data gt lt offset gt universe reg located at offset lt offset gt from the Universe II base address 2 3 Themis Computer USPIIli Hardware Manual 2 4 Themis Computer Software Section Chapter Themis USPIIli Software 3 1 Introduction
54. ate the use of interrupts in device drivers This driver is provided along with the source code and a sample configuration file The reader may wish to study the source code for this driver to gain a better understanding of handling interrupts in device drivers 3 36 Themis Computer 3 Themis USPIIli Software 3 5 3 Writing VME Device Drivers Allocating DVMA Space Direct Virtual Memory Access is a facility present on SPARC hardware that allows a device to specify virtual addresses rather than physical addresses for a DMA opera tion The kernel maintains a map that specifies the correspondence between the DVMA address and the physical memory It is the responsibility of the device driver to set up the memory region for DVMA access Setting up a DVMA region is a two step process allocating memory and allocating DMA resources for this memory region The following code segment is an example of setting up a DVMA region of size len bytes While allocating memory and setting it up for DVMA the driver can describe the capabilities of the DMA engine to the kernel by using a ddi_dma_ lim t structure On USPIIli systems the capabilities are as follows static ddi_dma_lim_t limits 0x0 OxELTEEELLE Oxffffftff O7 0x1 0 he caddr_t kmem_base int req_id real_len req len ddi_dma_handle t handle ddi_dma_cookie_t cookie dma_req_t reqp req_len len real_len 0 allocate memory
55. ce registers can be easily programmed from the user program For example to access a device that supports 32 address bits and has 32 bit data with the registers starting at offset 0x7e000000 the user program needs to open dev vme32d32 and lseek to offset 0x7e000000 Please note that the registers of this device could be 8 bit wide 16 bit wide or 32 bit wide If the read write call is issued with the appropriate length the vmemem driver will issue the appropriate ddi_peek or ddi_poke call Themis Computer 3 Themis USPIIli Software 3 5 6 Writing VME Device Drivers Note that the mmap interface of the vmemem driver does not use the ddi_peek ddi_poke calls In such cases access to all nonexistent address space will panic crash the Solaris kernel Devices that issue interrupts pose more of a problem when accessed from the user level In some cases the devices can be programmed to not raise interrupts Input output in such cases may be done by making the user program busy wait In other cases the vmeintr driver can be used to receive the interrupt and signal a user program when the interrupt is raised The user program can then look at the device registers and take appropriate actions Environmental Monitoring Programs The following Solaris application programs have been written specifically for the USPIIIi system usp3i_temp The usp3i_temp application see Zable 3 8 interfaces with the ADM1031 temper ature moni
56. cesses are done using the 8 PCI target image windows For A24 and A16 accesses a special Universe II window is used the special PCI target image The mechanism is the same as for A32 accesses Please refer to the Universe II User s Manual for details 3 2 5 2 VME Mapping Support under OBP Due to the design of Tomatillo whenever a non existing VME location is accessed a parity error is recorded within Tomatillo that causes OBP to fail in the family of peek and poke cpeek wpeek lpeek cpoke wpoke and lpoke To circumvent this problem OBP has been enhanced to use the DMA engine inside the Universe chip to do the peek and poke so that both can still work in the OBP Because peek and poke use virtual addresses map in and map out commands have been enhanced to track the mapping to the VME Bus hence the operations of peek poke memory access etc are transparent to the user Thus the syntax in the OBP reference manual has been preserved in the Themis USPIIi VME node To help you read the mapping the following symbols are defined 7d value A24D32 6d value A16D32 3d value A24D16 2d value A16D16 4d value A32D32 Od value A32D16 Themis Computer USPIIli Software Manual 3 12 Examples To shows a000 a32va regis 1234 regis regis a32va tll r Io shows a0 00 a24va regis 1234 regis regis a24va Not To shows test a register in VME A32D32 space tack
57. d Korn shell Bourne shell and Korn shell supe ruser Website Information Themis Computer s corporate and product information may be accessed on the World Wide Web by browsing the website at http www themis com Xv Themis Computer USPIIli Software Manual xvi Notes Cautions Warnings and Sidebars The following icons and formatted text are included in this document for the reasons described Note A note provides additional information that may be helpful in carrying out a procedure or action operator or equipment This may involve but is not restricted to heavy equip ment or sharp objects To reduce the risk follow the instructions accompanying this symbol 1 Caution A caution describes a procedure or action that may result in injury to the operator or equipment as a result of hazardous voltages To reduce the risk of elec h Warning A warning describes a procedure or action that may cause injury to the trical shock and danger follow the instructions accompanying this symbol Sidebar A sidebar adds detail to the section within which it is placed but is not absolutely vital to the description or procedure of the section Your Comments are Welcome We are interested in improving our documentation and welcome your comments and suggestions You can email your comments to us at docfeedback themis com Please include the document part number in the subject line o
58. d in this publication are the property of their respective owners Themis Customer Support North America South America and Pacific Rim Telephone 510 252 0870 Fax 510 490 5529 E mail support themis com Web Site http Awww themis com USPIITi Software Manual Version 1 3 November 2005 Part Number 110615 023 USPIIli Software Manual Version Revision History Version AES loc tiacis ected od ew hakio outa ieee November 2005 Replaced photo on page ix to reflect new logo Preface How to Use This Manual Changed will add to has added in the second sentence in Section 2 1 Themis OBP Commands on page 2 1 Chapter 2 Reworded paragraph 2 of Section 2 2 OBP VME Environment Variables on page 2 1 Chapter 2 Added a note to Section 2 2 OBP VME Environment Variables on page 2 1 regarding rebooting the system to see modifications to the environment variables Chapter 2 Corrected the following values in Table 2 1 on page 2 2 and Table 3 2 on page 3 5 vme arbitration mode from round robin to round robin priority and vme32 slave base from 0 1048576 to 0 4294901760 Better defined the software used on the USPIIIi in Section 3 1 Introduction on page 3 1 Chapter 3 Revisions to the first paragraph in Section 3 2 SUN OpenBoot PROM OBP on page 3 1 to include the applicable versions of Sun Solaris and delete references to Wind River VxWorks Also changed UltraS
59. d or CPU 1 Themis Computer How to Use This Manual Introduction Table 1 USPIIli Model Configurations ape iti E e oat d PMC Carrier Board 1 only Configuration CP CPUS me vme vme 2PMC Slots 3 PMC Slots Slot 1 Slot2 Slot3 VME Slot2or3 VME Siot2 or 3 USPIIi 1 1 Yes Yes USPIIIi 1 2 Yes Yes Yes USPIIi 2G 1 Yes Yes Yes USPIIi 2G 2 Yes Yes Yes Yes USPIIli 3G2 1 Yes Yes Yes Yes USPIIli 3G2 2 Yes Yes Yes Yes Yes USPIIli 3GP2 1 Yes Yes Yes Yes VME Slot 3 USPIIli 3GP2 2 Yes Yes Yes Yes Yes VME Slot 3 USPIIli 3GP3 1 Yes Yes Yes Yes VME Slot 3 USPIIli 3GP3 2 Yes Yes Yes Yes Yes VME Slot 3 USPIIli 2P2 1 Yes Yes Yes VME Slot 2 USPIIi 2P2 2 Yes Yes Yes Yes VME Slot 2 USPIIli 2P3 1 Yes Yes Yes VME Slot 2 USPIIli 2P3 2 Yes Yes Yes Yes VME Slot 2 xiii Themis Computer USPIIli Software Manual xiv Intended Audience The custom software containing programs documentation and packaging is tar geted for various software users e System Administrators who install the software and perform the necessary software configuration e Users who perform day to day operations on USPIIIi systems e Application programmers who write user level programs to access the VME bus interface devices through the built in VMEbus devices e System programmers device driver writers who develop kernel leve
60. e 3 17 Chapter 3 Revised the fourth paragraph of Section 3 3 1 2 just before the note on page 3 17 Chapter 3 Updated the sample installation log of the VME nexus driver on page 3 18 Chapter 3 Updated the sample installation log of the sample drivers on page 3 21 Chapter 3 Updated the sample uninstallation log of sample drivers on page 3 23 Chapter 3 Deleted explanations of simpledma and testmbi and added explanations for sw_reset_n_sysfail and sysfail_test sample drivers in Section 3 3 4 on page 3 25 Chapter 3 Added the last sentence to Section 3 4 2 on page 3 27 that reads The corresponding variables Chapter 3 Deleted the 3rd and 4th paragraphs including the bulleted list of Section 3 4 3 on page 3 27 Chapter 3 Deleted the last two paragraphs of Section 3 4 5 on page 3 29 Chapter 3 Rewrote the last sentence of the last paragraph of Section 3 4 5 1 on page 3 29 Chapter 3 Changed the reference to Chapter 8 to Section 3 3 4 in the 4th paragraph of Section 3 5 on page 3 32 Chapter 3 Changed the vector values in the 2nd to last paragraph of Section 3 5 Chapter 3 Edited any mention of the SIGBUS signal in regards to accessing nonexistent address space in multiple occurrences throughout Chapter 3 Themis Computer USPIIli Software Manual Version Revision History Added two PLD registers to the list on page 4 1 user and boot device jumpers a
61. e II releases the VME bus it can vme release mode ror rwd ror use either ror release on request or rwd re lease when done vme arbitration mode round robin priority round robin Arbitration mode used if the USPI isthe system controller vme irg to service 1 2 3 4 5 6 1 2 3 4 5 6 VME bus interrupt level to be serviced by the VME leaf driver Defines a master window on VME All subsequent VME mappings that fall within this window will use this win dow instead of allocating one of the remaining Universe vme32 master base 0 4294967295 0 Il register sets to define a new window The best use of this master window is to define it to encompass all other VME device addresses if possible that will be access ed by the USPIlli ec ee eer 04294967295 0 Size of the master VME bus address window Must be less than 1 2 GB If 32 decimal is used space is A32D32 If 24 dec vmeg2miastermode 24 32 ae imal is used space is A24D32 vme32 slave base 0 4294901760 1048576 Slave window base address in A32 mode vme32 slave size 0 4294967295 4294967295 Slave window size in A32 mode vme24 slave base 0 16777216 0 Slave window base address in A24 mode vme24 slave size 0 16777216 16777216 Slave window size in A24 mode a Numerical values are decimal b To avoid self reference the VME address window defined by vme32 slave base and vme32 slave size should not overlap the VME addresss window defined by vme32 master b
62. e on Ain3 CPU core Voltage Voltage on AinO Backplane Voltage on Ainl Memory Voltage on Ain2 Jbus Voltage on Ain3 CPU core 1 ok 5 8 5V input 4980 mV 2 5V input 2578 mV t1 5V input 1503 mV tVcore input 1367 mVCPUL 5V input 4980 mV t2 5V input 2578 mV 1 5V input 1484 mV tVcore input 1386 mV Themis Computer A A D converter 5 8 address map Ebus device 10 I2C devices 1 6 Jbus 1 2 1 3 address space 3 33 mapping to PCI Jbus 4 ADM1031 datasheet 5 3 device 5 sensor 5 3 allocating DVMA space 3 37 AMD device AM29LV065D 1 1 analog voltage I2C converter B bridge expander IMAX 9 bridge Xbus to I2C 9 C commands additional OBP 3 9 additional OBP VME 2 3 OBP 2 1 OBP support 3 6 PLD 3 42 temperature monitoring 3 41 themis show pld 4 11 UNIX xiv user status LED 3 42 voltage monitoring 3 42 Comments are Welcome xvi configuring the USPIIIi software 3 27 CPU junction temperature 5 CPU 0 xii CPU 0 board 5 Index CPU 1 xii CPU 1 board 5 CY37512 programmable logic device 7 7 Cypress PLD CPLD 10 3 42 See also PLD D DC DC converter 5 1 5 8 device aliases OBP 3 3 device drivers 3 39 device monitors 5 2 devices probing 3 34 dmatest 3 24 documentation feedback docfeedback themis com xvi documentation SUN 9 drivers sample 3 21 sample VME leaf 3 24 utility 3 2 VME device 3 32 DVMA space allocating 3 37 E
63. e solder bead SB1604 used to indicate what kind of termination devices are used on the system board 0 means UNITRODE UCC5673 1 means Dallas DS2119 bit 7 RO Status of the solder bead SBX1701 used to indicate what kind of termination devices are used on the SCSI adaptor board 0 means UNITRODE UCC5673 1 means Dallas DS2119 PLD register offset 0x08 Description KBM USB TTY A TTY B physical port setting Width 8 bit Vector name pld_reg 7 i Description bit 1 0 RO These bits provide info on the setting of the PS 2 and USB Case of DIN8 connector 0 1 PS 2 on Front No USB 1 1 PS 2 on P2 No USB 1 0 PS 2 on P2 USB on the front 0 0 No PS 2 USB on the front Case of USB connector 0 1 No PS 2 USB on the front 1 1 PS 2 on P2 USB on the front 1 0 PS 2 on P2 USB on the front 0 0 No PS 2 USB on the front bit 0 RO is the status of the solder bead SB12201 When the solder bead is set to 2 3 this bit is set to 0 When the solder bead is set to 1 2 this bit is set to 1 bit 1 RO is the status of the solder bead SB2505 4 7 Themis Computer USPIIli Software Manual 4 8 When the solder bead is set to 2 3 this bit is set to 1 When the solder bead is set to 1 2 this bit is set to 0 bit 2 RO Read as 0 bit 3 RO 0 The USB
64. e system board warning temperature sensor 0 Temperature below the warning threshold 1 Temperature ABOVE the warning threshold bit 7 RO Read as 0 PLD register offset 0x06 Description miscellaneous amp patch control status register Width 8 bit Vector name pld_reg 5 i Description bit 0 RO 0 means the PLD clock divider is set to normal mode CLK10HZ clock 10 Hz and solder bead SB3901 is not installed 1 means the PLD clock divider is set to test mode CLK10HZ clock 1 MHz and solder bead SB3901 is installed bit 1 RW This bit controls the Enable LED 0 turn off the Enable LED 1 turn on the Enable LED Upon board reset the LED is turned off bit 2 RO User flash status bit 0 The User flash is busy executing a programming command in progress 1 The User flash is ready to accept a new command bit 3 RO Status of the MXAbus multiplexer control signal 0 The MXA bus is used to drive the JTAG bus and is isolate from the XAbus Solder bead SB4000 connected to 2 3 1 The MXA bus is connected to the XA bus Solder bead SB4000 set to 1 2 bit 6 4 RO Status of the Jumpers JP3906 JP3905 JP3904 0 The jumper is installed 1 The jumper is removed Those jumpers are used to set a patch number The generic Ii will have those three jumpers installed bit 7 RO
65. e to the Universe IT VME to PCI Bus Bridge User s Manual after Table 3 2 on page 3 5 Chapter 3 Changed the default value for vme32 slave size in Table 3 2 on page 3 5 Chapter 3 Edited and added text to Section 3 2 3 1 probe scsi all on page 3 6 Chapter 3 Themis Computer USPIIli Software Manual Added a new subhead to Section 3 2 4 3 2 4 1 Updating the System Flash from the Network and renumbered the subsequent subhead pages 3 7 and 3 8 Chapter 3 Added the first sentence in Section 3 2 4 1 stating that the user must have access to a tftp server on page 3 7 Chapter 3 Made multiple edits to Sections 3 2 4 1 and 3 2 4 2 on pages 3 7 through 3 9 Chapter 3 Added a note to Section 3 2 5 on page 3 9 regarding OBP commands and versions Chapter 3 Changed the four Universe II registers bulleted list at the top of page 3 10 in Section 3 2 5 1 Chapter 3 Changed the sample commands just above the note on page 3 10 in Section 3 2 5 1 Chapter 3 Added a note to Section 3 2 5 1 on page 3 10 regarding OBP commands and version Chapter 3 Deleted the last sentence of the 1st paragraph in Section 3 2 5 2 on page 3 11 Chapter 3 Added footnote a to Table 3 3 on page 3 14 Chapter 3 Changed multiple occurrences of Solaris 2 x to Solaris in Chapter 3 Changed SBus to PCI Bus throughout Chapter 3 Added a description of an alternate form of the pkgadd command to Section 3 3 1 2 on pag
66. e8 are managed by the VME Nexus device driver when Solaris is running Thus at the end of OBP testing for A32 devices the resource must be released by executing the map out command Otherwise when Solaris is running certain PCI addresses will be answered by more than one PCI tar get image Also due to the complexity of managing resources using fcode only one map in is supported for all A32 space Subsequent map in for A32 devices will wipe out the mapping established in the previous map in The workaround for this is to map a huge region with a single map in command The VME node can map in more than 1 GByte of VME space in a single command For A24 and A16 devices as many map in commands can be used as the applica tions require and the mapping resources don t need to be freed at the end of testing using the map out command USPIIli OBP Device aliases The devalias command displays the list of OBP aliases for the USPIIIi as shown in Table 3 3 Themis Computer USPIIli Software Manual Table 3 3 List of OBP aliases ok devalias net ide cdrom diskl disk0 disk scsi ttyb ttya pci l1 700000 network 2 pci le 600000 ide d pci ld 700000 scsi 4 disk 6 0 f pci l1d 7 pci l1d 7 pci l1d 7 pci l1d 7 pci le 6 pci le 6 00 00 00 00 00000 scsi 4 disk 1 0 000 scsi 4 disk 0 0 000 scsi 4 disk 0 0 000 scsi 4 00000 isa 7 serial 0 2e8 000 isa 7 serial 0
67. ecial ioctl calls are required to configure the interface Installing the Sample Drivers The sample drivers vmeintr dvma testmbi simpledma are not required for the normal operation of the USPIIIi system and therefore are not installed by the instal lation procedure described Section 3 3 1 2 Installing THEMIS3ivme on page 3 17 You may choose to install these drivers by executing a script provided for that purpose ca cd opt ls la total 10 drwxr xr x drwxr xr x drwxr xr x drwxr xr x drwxr xr x root root root root bin cd THEMIS3ivme ls la total 14 drwxr xr x drwxr xr x 6 5 bin root sys root bin sys bin bin sys 512 512 512 512 512 512 512 Aug Aug Aug Aug Aug Aug Aug 23 23 17 17 23 23 23 15 15 Tess 12 T53 t53 15a 02 04 15 SUNWits 20 SUNWrtvc 02 THEMIS3ivme 02 02 Themis Computer 3 21 USPIIli Software Manual drwxr xr x 2 bin bin 512 Aug 23 15 02 DOC LWXr Xr X 1 bin bin 382 Mar 4 2004 RELEASE notes drwxr xr x 6 bin bin 512 Aug 23 15 02 drv drwxr xXr X 3 bin bin 512 Aug 23 15 02 example drwxr xr x 3 bin bin 512 Aug 23 15 02 man ls la total 14 drwxr xr x 6 bin bin 512 Aug 23 15 02 drwxr xr x 5 root sys 512 Aug 23 15 02 drwxr xr x 2 bin bin 512 Aug 23 15 02 DOC rwxr xr x 1 bin bin 382 Mar 4 2004 R
68. egister 0x04 temperature sensor Status id sakiduaeesseens See PLD register 0x05 miscellaneous stats urie See PLD register 0x06 scsi termination status essessssesrrrserssessse See PLD register 0x07 tty kpm acI T sta tUs Tree ana A See PLD register 0x08 sesi termination COnNtrol esre enia See PLD register 0x09 seSi termpw r Stats erana nae pn ai e See PLD register 0x0a RMW semaphore and test sadn duis delicosied See PLD register 0xf0 COS Gs iiia E a tency iv eteian aheegen tanta Performs a PLD register dump 4 1 Themis Computer USPIIli Software Manual In addition the following functions are available to read and write PLD registers directly as a character c or byte word w or long word 1 pldc offset data akties Read the byte content of the PLD register at offset pidw Y V OETSEt Qata Joyes Read the 16 bit word of the PLD register at offset PLONE y OLTSSE iS data J anien Read the 32 bit word of the PLD register at offset pidet AA data offs t Rai ie haan Write the byte data into the PLD register at offset pldw data offset Se ne Write the 16 bit data into the PLD register at offset pidit data offset Juisi Write the 32 bit data into the PLD register at offset 4 1 1 Examples The following examples illustrate how a typical function works 1 Read PLD register 0x04 ok 4 pldc lt Enter gt Okie AE A hee i e k Bit values returned are 00001111 2 Set bit 4 and bit 5 of
69. ent node to VME execute the OBP command vme select dev Note Some versions of OBP do not employ the vme selelct dev com mand If this command does not work on your system use the command Go perele co0000 THEMIS peivne Accessing VME Address Space from OBP Prior to actually accessing VME from OBP you need to make sure that the Universe II PCI target images are set correctly A PCI target image is actually a window from PCI Bus to VMEbus Each image or window defines a contiguous range of PCI addresses base address and size When a PCI cycle is issued by the USPI CPU with an address falling inside a particular window address range the Universe II will propagate that cycle to the VME The VME cycle will be formed according to the attributes defined in the window registers e VME address e VME Address modifier Please refer to the Universe II User s Manual for details The Themis OBP com mand show universe regs can be used to view the settings of the 8 address win dows Each window is controlled by four Universe II registers 3 9 Themis Computer USPIIli Software Manual e LSx_CTL control register e LSx_BS PCI base address of the window e LSx_BD PCI bound address of the window e LSx_TO Translation register Suppose we want to access VME A32 0xaa00 0000 ok ok aa00 0000 to vme32 master base 1000 0000 to vme32 master size reset all vme select dev show universe regs Note Some ver
70. er 0x1e 0x400 0f00 0000 0X400 0f7f ffff 8 MB Each Jbus agent has its own specific Jbus configuration space layout The table below provides the layout for the Tomatillo Table 1 2 Jbus Address Map Register add to Jbus cfg base Jbus Tomatillo ID register 0x0000 0000 UPAO offset base register 0x0040 0000 UPAO offset mask register 0x0040 0008 UPA1 offset base register 0x0040 0010 UPA1 offset mask register 0x0040 0018 PCI A memory offset base register 0x0040 0040 PCI A memory offset mask register 0x0040 0048 PCI A Cfg offset base register 0x0040 0050 PCI A Cfg offset mask register 0x0040 0058 PCI B memory offset base register 0x0040 0060 PCI B memory offset mask register 0x0040 0068 PCI B Cfg offset base register 0x0040 0070 PCI B Cfg offset mask register 0x0040 0078 Tomatillo CSR 0x0041 0000 PCI A CSR base register 0x0050 0000 PCI B CSR base register 0x0060 0000 Ichip CSR base register 0x0078 0000 Themis Computer USPIIli Software Manual Jbus ADDRESS SPACE High address PCI A Mem base address PCI A IO base address 0x100 0000 PCI A cfg base address PCI space base address for Jbus agent JID a JID x 236 0x600 0000 0000 PCI space base address Hard coded Jb
71. essee 3 32 3 5 1 Probing IC VICES asc fcc Secies ee Se sie e e a Ot anenint tod ea 3 34 3 5 2 Registering Interrupts hee eeccas easter wdguaeeaosccueea stings aumaont wala mame eta iageaan 3 35 3 5 3 Allocating DV MAS Space ssc pheasctras is ceeliiccteismaviabentvn teats gatiasmanead 3 37 3 5 4 Mapping VMEbus Space scatters ann uenienes ui 3 39 3 5 5 Driving Devices Without Writing Device Drivers ceeeeeeeeetees 3 39 3 5 6 Environmental Monitoring Programs 0 cccccescceeceeeseeesceeeeeeeeeeeeeesaeees 3 41 WISP MU COT yee e Pate ple a e n sred a 3 41 UWS PSI Voltage iein oeenn R EAE REA TAANS 3 41 sp3i WIE zedsieseisoreioier Eaa louder aR 3 42 usp3i pldand plxdrv ction een 3 42 viii Themis Computer Table of Contents 4 Programmable Logic Device 236 6 2 c cies estesdes dei Gas eee ae 4 4A PED F nction Upgrade esaeizsicpsee nye dio cea n Gilded ng E E A okenddehs 4 Aad VE RAMAD IES nan on a ccaicmeaayevaeearruaies E E A EAE 4 2 4 2 PED Register Sel ie cinsisaccticctletsvesttedkelcaseise dec loi E ces eastside aaa sadaaate As 4 3 4 3 Output from themis show pld nausea iad ea aulatdns 4 11 5 Device Monitoring n i ee i i a aa ri ai esaia 5 1 Sol ntrod ctonrs nenne n a ese E ei O e a E a 5 1 5 2 Thermal Monitorning 2 scsc6us Saved orcad e a a Jala a Sel ot tant 8s 5 1 5 2 1 Setting Temperature Thresholds asics co kde Qiseacenadced dk iladeelicadiecmiendocteaedel 5 4 5 3 Voltage Monitoring nren ats
72. et to 1 2 USB power rail OK JP4401 NOT INSTALLED TTY B Front panel interface set to RS232 JP4403 NOT INSTALLED TTY B interface accessible on the front panel JP4402 NOT INSTA panel JP2502 INSTALLED AC97 Audio interface accessible on P2 ED TTY A interface accessible on the front 4 12 Themis Computer 4 Programmable Logic Device Output from themis show pld SCSI A termination control register 0x7ee 0100 0c09 SCSI A front panel termination lower section is controlled by the sense pins SCSI A front panel termination upper section is controlled by the sense pins SCSI A P2 termination lower section is controlled by the sense pins SCSI A P2 termination upper section is controlled by the sense pins SCSI A B termination power control register O0x7ee 0100 0c0a SCSI A termination power is enabled SCSI B termination power is enabled No device plugged on the SCSI B interface 4 13 Themis Computer USPIIli Software Manual 4 14 Themis Computer Maintenance Section Chapter Device Monitoring 5 1 Introduction The USPIIIi design contains two categories of monitoring devices e Thermal measurement e DC DC converter voltage measurement 5 2 Thermal Monitoring USPIIIi thermal sensors are all based on the PC ADM1031 device from Analog Devices There are a total of three thermal sensors one on each major board of the
73. f Imax e DDR DIMM EEPROM SDF 3rd DIMM Memory 1 24LCS52 2C 3 OxA6 OxCC IC controller PCF8584 on Xbus and IMAX IC to I2C bus expander C 3 bus is attached to Port 1 of Imax e DDR DIMM EEPROM SDF 4th DIMM 1 8 Themis Computer 1 USPIlIli Programming Guide I2C Devices Address Map The I C to I C bridge expander IMAX is a microcontroller located on the CPU0 board This bridge expander fans out the main primary I C bus called I C_1 in this document in four secondary I C busses called I2C_2 to I2C_5 Those I C busses are attached to Port 0 to 3 respectively of the IMAX bridge The IMAX is itself an I C device programmed by OBP through the Xbus to I C bridge controlled by the Southbridge ASIC on the system board see I C bus topology in Figure 1 2 on page 1 5 The I C address of the IMAX is 0x12 All the programming details are provided by Sun into two documents Those docu ments are e imax_code pdf e imax_info pdf the most relevant for the firmware programmer Because of the change on the I2C topology and the additional devices the address filter bitmap the routing table and the address translation page table in the Imax must be modified at the OBP level 1 9 Themis Computer USPIIli Software Manual 1 5 Ebus Device Address Map Table 1 4 lists all the USPIIi devices located on the Ebus and provides relevant information for each of them The Ebus co
74. f the VME backplane this bit is cleared bit 7 RW 1 When over temp occurs in non battle mode hold board in reset until power is recycled 0 When over temp occurs in non battle mode hold board in reset until temperature drops 5 degrees below shutdown level PLD register offset 0x05 Description Temperature sensor status register Width 8 bit Vector name pld_reg 4 i Description bit 0 RO Status of the CPU0 board over temperature sensor 0 No over temperature condition detected 1 Over temperature condition detected bit 1 RO Status of the CPU1 board over temperature sensor Themis Computer USPIIli Software Manual 4 6 0 No over temperature condition detected 1 Over temperature condition detected bit 2 RO Status of the system board over temperature sensor 0 No over temperature condition detected 1 Over temperature condition detected bit 3 RO Over temperature CPU 0 CPU 1 or System board is detected and latched 0 No 1 Yes bit 4 RO Status of the CPU0 board warning temperature indicator 0 Temperature below the warning threshold 1 Temperature ABOVE the warning threshold bit 5 RO Status of the CPU1 board warning temperature sensor 0 Temperature below the warning threshold 1 Temperature ABOVE the warning threshold bit 6 RO Status of th
75. f your email Themis Computer Software Section Chapter USPIIli Programming Guide 1 1 Introduction This document provides critical information for software programmers who must write the firmware code to control the extra hardware features implemented on the USPIIIi The native firmware from Sun was modified by Themis to accommodate the topology differences between the Sun reference platform the Sun Blade 2500 workstation and the Themis USPIIIi The following is a list of features implemented on the USPHI e User 8MB flash memory AMD device AM29LV065D e TTY C and D ports using the usual SAB 82532 from Infineon formerly Sie mens e User LED IC driver e Analog voltage I C converter e An additional I C thermal sensor ADM1031 dedicated to the second CPU board temperature monitoring e Dual fiber channel controller ISP2312 e VME interface based on the Universe II controller e USPIIIi specific control status registers implemented into a CY37512 pro grammable logic device from Cypress e H W read modify write or test and set semaphores for shared resources 1 1 Themis Computer USPIIli Software Manual Themis modifications include e PCI segments topology and its IDsel assignments e Interrupt assignment mapping which impacts the Tomatillo initialization e I C bus topology and its address map e Jbus topology although it will be transparent to the firmware software 1 2 Jbus Address Map
76. following subsections Themis also provides online manual pages for all the drivers included in the software interface These manual pages include more detailed information on the drivers The USPIIi can run the Solaris OS from either a local disk or from the Ethernet net work as a diskless client In the case of a local disk the Solaris OS will be loaded from the Sun Solaris CD ROM To install the USPIIIi as a diskless client users need to run smosservice and or smdiskless on a boot server system Please refer to Sun s documentation on how to install the Solaris Operating System In order to be able to access VME from Solaris users need to install the Themis VME Nexus driver for the USPIIIi The VME Nexus driver is a Solaris package that is installed removed using the pkgadd 1M pkgrm 1M Solaris command The installation is menu driven and users should always reboot the system in the recon figuration mode boot r right after installing the VME Nexus driver Themis Computer USPIIli Software Manual 3 3 1 VMEbus Nexus Driver The pcivme Nexus driver forms the core of the software interface provided by The mis Computer It is a bus Nexus driver that encapsulates all the architectural features of supporting the Themis USPIIIi board on Solaris systems This driver is config ured to be permanently loaded as the bus Nexus driver for the VMEbus root PCI Bus pcivme esp vmed
77. ftware 3 4 2 3 4 3 3 4 4 3 4 5 Writing Programs for the VMEbus Configuring the Software Interface of USPIlli The USPIIIi board can be accessed in a slave mode from another board on the VME bus chassis This type of access requires specifying the slave base address and the size of the slave access region of the USPIIIi board Distinct values can be specified for 24 bit addresses and 32 bit addresses On a VMEbus chassis with multiple boards each processor board is required to have a non overlapping region for slave mode access The OBP variables vme32 slave base and vme24 slave base can be used to set the slave base addresses of a USPIIIi board The corresponding variables vme32 slave size and vme24 slave size control the size of these slave windows Accessing the VMEbus from OBP It is often convenient to access the VMEbus from the Open Boot PROM For exam ple after adding a new memory board on the chassis the OBP can be used to quickly test the proper installation and configuration of the memory board Further testing of the board can then be done under the Solaris environment For a description of OBP commands themselves please refer to the document named OpenBoot Command Reference Accessing the VMEbus from Solaris This section describes the many features of the software interface provided by The mis Computer The features provide the system programmer with powerful ways of accessing the VMEbus from the Solaris
78. her VME device addresses if possible that will be accessed by the USPIlli Size of the master VME bus address win vme32 master size 0 4294967295 0 dow Must be less than 1 2 GB 2 R If 32 decimal is used space is A32D32 vmgoz master mode aE 24 If 24 decimal is used space is A24D32 vme32 slave base 0 4294901760 1048576 Slave window base address in A32 mode vme32 slave size 0 16777216 16777216 Slave window size in A32 mode vme24 slave base 0 16777216 0 Slave window base address in A24 mode vme24 slave size 0 16777216 16777216 Slave window size in A24 mode a Numerical values are decimal For a more detailed description of the VME values refer to the Universe II VME to PCI Bus Bridge User s Manual P N 80A3010 MAO01_03 available from Tundra Semiconductor Corporation 3 5 Themis Computer USPIIli Software Manual 3 2 2 Setting and Reading VME OBP Environment in Hex Because an OBP environment variable is an integer commands like setenv or printenv use the integer format This makes setting the base address and base size awkward To use hex number format enter general variables to set and read address and base For example ok 200000 to vme24 slave size and ok vme24 slave size h 32 0 Support Commands 3 2 3 1 probe scsi all The command probe scsi all probes the first SCSI bus SCSI A the second SCSI bus SCSI B and the two FC AL ports This command behaves in a similar fa
79. hown in Table 1 6 on page 1 15 VMEbus Configuration and Status registers VCSR Universe Device Specific Registers 4 KBytes UDSR r PCI Configuration space PCICS Figure 1 3 UCSR Access Mechanism 1 14 Themis Computer 1 USPIlIli Programming Guide Table 1 6 Universe Il Register Map Universe II VME Interface Registers Offset Register Name 000 PCI Configuration Space ID Register PCI_ID i EEA BAR 008 PCI Configuration Class Register PCI_CLASS 00C PCI Configuration Miscellaneous 0 Register PCI_MISCO 010 PCI Configuration Base Address 0 Register PCI_BSO 014 PCI Configuration Base Address 1 Register PCI_BS1 018 024 PCI Unimplemented 028 PCI Reserved 02C PCI Reserved 030 PCI Unimplemented 034 PCI Reserved 038 PCI Reserved 03C e Miscellaneous 1 Register PCI_MISC1 040 0FF PCI Unimplemented 100 PCI Target Image 0 Control Register LSIO_CTL 104 PCI Target Image 0 Base Address Register LSIO_BS 108 PCI Target Image 0 Bound Address Register LSIO_BD 10C PCI Target Image 0 Translation Offset Register LSIO_TO 110 Reserved 114 PCI Target Image 1 Control Register LSI1_CTL 118 PCI Target Image 1 Base Address Register LSI1_BS 11C PCI Target Image 1 Bound Address Register LSI1_BD 120 PCI Target Image 1 Translation Offset Register LSI1_TO 124 Reserved 128 PCI Target Image 2 Control Register LSI2_CTL 12C PCI Target I
80. if ddi_mem_alloc xsp gt dip amp limits size _t req_len 0 amp kmem_base uint amp real_len DDI SUCCESS cmn_err CE NOTE ddi mem alloc failed return ENOMEM Themis Computer USPIIli Software Manual set it up for if return EFAULT DMA access ddi_dma_addr_setup xsp gt dip struct as kmem_base real len DDI DMA RDWR DDI DMA DONTWAIT 0 amp limits amp handle DDI_DMA MAPPED ddi _ mem fr kmem_base cmn_err CE NOTE ddi_dma_addr_setup failed extract the virtual address of the memory region this can be obtained from the DMA cookie structure if cmn_err cmn_err caddr_t coo ual address of memory amp cookie real_len ddi_dma_sync DDI SUCCESS NULL DDI_DMA_SYNC_FORDEV failed n is 0x x kmem_base ual address of the DVMA region is 0x x ddi_dma_htoc handle 0 ddi _dma_sync handle 0 DDI_SUCCESS ddi_dma_free handle ddi _ mem fr kmem base cmn _ err CE NOTE return EFAULT CE_NOTE Virt CE NOTE Virt kie dmac_address The address contained in the DMA cookie is the virtual address of the DVMA memory region and can be used to access the memory region over the VMEbus e g if the virtual address printed by the second cmn err statement is 0x588 you can
81. is transparently implemented under Solaris Themis Computer has also developed custom software that enables software programmers to effectively use the powerful features of the VMEbus Interface Themis Computer USPIIli Software Manual xii The USPIIIi has a total of 14 models see Zable 1 All models are based on a combi nation of six different VME boards the USPIIi System board two CPU boards CPU 0 and CPU 1 the TGA3D 3D Graphics board and two PMC Carrier boards one with 2 PMC slots and one with 3 PMC slots In addition several VME backplane connected paddle boards are available for the USPIIIi that provide I O connections through the P2 backplane connector for details see the USPIIIi Hardware Manual Themis P N 110615 022 The USPIIi Hardware Manual also provides information on the hardware design of the USPIIIi system including a product overview OBP commands device monitor ing connector pinouts jumper pin and solder bead configurations circuit board and front panel diagrams LED interpretation and VME slot configurations Note To avoid confusion about the numbering of VME slots in the USPIIIi sys tem represented in Table 1 Themis Computer offers the following explanation Although the USPIII system may require multiple VME slots the System Board is considered to be in logical VME slot 1 even though one or two VME slots to the left of the System Board may be physically occupied by CPU 0 an
82. ithout Writing Device Drivers As mentioned before device drivers protect the rest of the kernel from the specifics of hardware devices Most hardware devices would necessitate the development of a device driver before they can be used on a computer system However the features of the VMEbus and the design and implementation of the Themis Computer software interface for VME alleviate the need for specialized device drivers for most simple VME devices This provides a tremendous advantage to programmers writing appli cations for these simple devices Themis Computer USPIIli Software Manual In Solaris device drivers are dynamically loadable This avoids the need to relink the kernel and reboot the system whenever a driver is modified However a fault in the driver could still cause the kernel to panic resulting in long downtimes for the machine Further an abnormal shutdown of the machine as in the case of kernel panic could cause the disk to be corrupted and some important files to be lost These problems can be avoided if the program driving the device executes in user mode instead of kernel mode This section discusses some ways by which a user program can do device operations that are traditionally performed by a device driver The section is intended to clue the programmer on to the possibilities of accessing devices from user level The reader is encouraged to go through the source code of the sample drivers to gain an insight in
83. l device drivers for VMEbus devices Some functions overlap one another The basic concepts required for many of these functions are common This manual is structured around the basic concepts of using a VMEbus system In Case Of Difficulties If the USPIIIi does not behave as described or if you encounter difficulties installing or configuring the board please call Themis Computer technical support at 1 510 252 0870 fax your questions to 1 510 490 5529 or e mail to support themis com You can also contact us via our web site http www the mis com UNIX Commands This document may not contain information on basic UNIX commands and proce dures such as shutting down the system booting the system and configuring devices Themis Computer How to Use This Manual See one or more of the following for this information e Solaris Handbook for Sun Peripherals which contains Solaris software commands e A Practical Guide to Solaris Copyright 1999 Mark G Sobell e AnswerBook on line documentation for the Solaris software environment e Other software documentation that you received with your system Shell Prompts In UNIX the primary method for telling the computer what to do is to type com mands at a shell prompt The following table shows the default prompts for four dif ferent Solaris software shells Shell Prompt C shell machine_name C shell superuser machine_name Bourne shell an
84. l driver It will be necessary to do a reconfiguration reboot after driver installation Execute reboot r to reboot the 64 bit kernel or execute reboot rD kernel unix to use the 32 bit kernel The new vme drivers will not be functional till a reboot is done Installation of lt THEMIS3ivme gt was successful 3 3 1 3 Removing THEMIS3ivme If you want to remove the software interface of USPIIi for any reason you can exe cute the pkgrm command to remove the THEMIS3ivme package pkgrm THEMIS3ivme pkgrm will remove all the files contained in the package The original contents of VME drivers before the package was installed will be restored 3 20 Themis Computer 3 Themis USPIIli Software 3 3 2 Utility Drivers Overview of VME Interface Under Solaris These drivers are a standard part of the software interface provided by Themis Com puter These drivers provide a useful interface to system programmers who wish to utilize the different features of the VMEbus architecture The vmemem device driver provides the standard dev devices for accessing the VMEbus from user processes Table 3 5 vmemem Device Driver Device File Address Size Data Transfer Size dev vme32d32 32 32 dev vme32d16 32 16 dev vme24d32 24 32 dev vme24d16 24 16 dev vme16d16 16 16 3 3 3 read write and mmap calls are supported and no sp
85. lly support users who wish to write their own VME device driv ers that would function on USPIIIi platforms To aid these users and to illustrate the specific features of the VMEbus architecture Themis provides a number of sample device drivers Themis provides the complete source code and the necessary config uration files for these drivers The drivers are located under the opt THEMIS3ivme directory vmeintr This sample illustrates the vectored interrupt mechanism of the VME bus The vmeintr driver relies on the driver configuration files to specify the inter rupts it should handle Each instance of the driver registers the interrupts with the system Through the ioctls implemented by the driver you can generate interrupts and send them to the appropriate driver instances The interrupt generator and the interrupt receiver need to run on different computers vmedvma This sample driver illustrates the use of Direct Virtual Memory Access within a device driver You can ask the driver to allocate a DMA region on the VMEbus The driver allocates all the necessary resources to support a DVMA transfer to this region The driver also implements mechanisms by which you pro gram can write to or read from the DVMA region Furthermore the VME NEXUS package includes example programs to help users build their own application or test VME The programs are e dmatest This program uses the Universe II DMA engine Several options can be selected by comma
86. ma vmemem Figure 3 1 Nexus Driver Directory Structure Any driver that specifies its class or parent as vme will be attached to the pcivme driver The pcivme driver provides support for all VMEbus operations including VME interrupt processing Direct Virtual Memory Access DVMA on the VME bus mapping of registers on the VMEbus to kernel space mapping of VMEbus memory to user address space through mmap etc The pcivme driver recognizes the standard configuration file for VME device driv ers The configuration of any VME device driver specifies the VMEbus interrupt level and the interrupt vector The mapping of the VMEbus interrupt level to the SPARC interrupt priority level is as follows Themis Computer 3 Themis USPIIli Software Overview of VME Interface Under Solaris Table 3 4 VMEbus Interrupt Mapping System Interrupt Level VMEbus 1 2 3 4 5 6 7 SPARC ip 1 2 3 5 7 9 11 13 3 3 1 1 Installing the USPIIIi VME Nexus Driver 3 3 1 2 J The software interface for USPIIIi is distributed as a software package for Solaris systems The software package is named THEMIS3ivme and can be installed and removed like other standard Solaris software packages by using the pkgadd and pkgrm commands Installing THEMIS3ivme The THEMIS3ivme package is distributed on standard media and can be installed directly from the media To install the package place the installa
87. mage 2 Base Address Register LSI2_BS Themis Computer USPIIli Software Manual Table 1 6 Universe Il Register Map Continued Offset Register Name 130 PCI Target Image 2 Bound Address Register LSI2_BD 134 PCI Target Image 2 Translation Offset Register LSI2_TO 138 Reserved 13C PCI Target Image 3 Control Register LSI3_CTL 140 PCI Target Image 3 Base Address Register LSI3_BS 144 PCI Target Image 3 Bound Address Register LSI3_BD 148 PCI Target Image 3 Translation Offset Register LSI3_TO 14C 16C Reserved 170 Special Cycle Control Register SCYC_CTL 174 Special Cycle PCI Bus Address Register SCYC_ADDR 178 Special Cycle Swap Compare Enable Register SCYC_EN 17C Special Cycle Compare Data Register SCYC_CMP 180 Special Cycle Swap Data Register SCYC_SWP 184 PCI Miscellaneous Register LMISC 188 Special PCI Target Image Register SLSI 18C PCI Command Error Log Register L_CMDERR 190 PCI Address Error Log Register LAERR 194 19C Reserved 1A0 PCI Target Image 4 Control Register LSI4_CTL 1A4 PCI Target Image 4 Base Address Register LSI4_BS 1A8 PCI Target Image 4 Bound Address Register LSI4_BD 1AC PCI Target Image 4 Translation Offset Register LSIl4_TO 1B0 Reserved 1B4 PCI Target Image 5 Control Register LSI5_CTL 1B8 PCI Target Image 5 Base Address Register LSI5_BS 1BC PCI Target Image 5 Bound Address Register LSI5_BD 100 PCI Target Image 5 Translation Offset
88. ment can be used int vme caddr_t pageptr if vme open dev vme32d32 0 RDWR lt 0 perror open error on VME file return if pageptr mmap caddr_t OL roundup 1000 PAGESIZE PROT READ PROT WRITE MAP SHARED vme off t 0x500 amp PAGEMASK caddr_t 1 perror mmap error return Note that the off parameter to mmap is constrained to be aligned at a page bound ary The len parameter does not have a size or alignment constraint The success of mmap does not imply that the specified range of VMEbus is valid and accessible If the region specified by off offtlen is not a valid VMEbus address region access to the region will panic crash the Solaris kernel Slave Mode Access to Another VME Board Memory on the USPIIIi board can be accessed from another board on the VMEbus chassis This type of access is called slave mode access Slave mode access under Solaris is tied to the concept of Direct Virtual Memory Access DVMA DVMA is a facility present on SPARC hardware that allows a device driver to specify virtual addresses rather than physical addresses for a DMA operation The kernel maintains a map that specifies the correspondence between the DVMA address and the physi cal memory Themis Computer USPIIli Software Manual In a typical operation the master issues an address on the VMEbus this address falls within the slave address range of an
89. mpany ID 0x41 41 Revision E 3 Remote 1 temperature parameters Temperature High limit 105 Temperature Low limit F9 Temperature THERM limit FLLS Temperature z Remote 1 59 Remote 2 temperature parameters Temperature High limit 105 Temperature Low limit 5 Temperature THERM limit 115 Temperature gt Remote 2 41 Local temperature parameters Temperature High limit 70 Temperature Low limit 0 Temperature THERM limit 80 Temperature gt Tocai 30 Under Solaris you can dump the temperature of the different sensors using the fol lowing command usp3i_temp Sys local temperature is 38 Therm limit 80 High limit 70 Low limit 0 Sys inlet temperature is 30 Therm limit 80 High limit 70 Low limit 0 5 6 Themis Computer 5 Device Monitoring Sys outlet temperature is Therm limit 80 High limit 70 Low limit 0 CPU 0 local temperature is Therm limit 80 High limit 70 Low limit 0 CPU O di temperature is Therm limit 115 High limit 105 Low limit 5 CPU 0 board temperature is Therm limit 115 High limit 105 Low limit 5 CPU 1 local temperature is Therm limit 80 High limit 70 Low limit 0 CPU 1 di temperature is Therm limit 115 High limit 105 Low limit 5 CPU 1 board temperature is Therm limit 115 High limit
90. n venient when dealing with values that are better represented in hexadecimal such as VME addresses Refer to Section 3 2 2 Setting and Reading VME OBP Envi ronment in Hex on page 3 6 for instructions on how to easily use hexadecimal numbers in the command line Note In OBP all values are in decimal form so you would enter the command as The Solaris command line will accept hexadecimal values if they are preceded by 0x From within Solaris type the command as follows eeprom vme32 slave size 8388608 Table 3 1 shows an example of the results of the printenv command Your results might show more or less environment variables depending on what version of OBP you have 3 2 Themis Computer 3 Themis USPIIli Software SUN OpenBoot PROM OBP Table 3 1 OBP Environment Variables 1 ok printenv Variable Name themis switch value force system controller vme bus request level vme request mod vme release mod vme arbitration mode vme irg to service vme32 master base vme32 master size vme32 master mode vme32 slave base vme32 slave size vme24 slave base Variable Name vme24 slave size extra 64m segments vme init themis cpu count Lest args diag passes therm reset hold audio device system low limit system therm limit system high limit pul low limit pul therm limit pul high limit pu0 low limit c c cpu0 therm limit c pu0 high limit local mac address fcode debug
91. nd RMW semaphore and test Chapter 4 Changed 3 occurrences of System LED to Enable LED in the description of bit 1 under PLD register offset0x06 on Page 4 6 Enhanced and updated the index Made assorted minor revisions and grammatical corrections Version 1 2 fa cin eet a ea a aI eap cid re pea July 2004 Version Librea e A R cea eee ten ee December 2003 Version 1 0 se ces cessecteecsstcdne ede adsense eet ee September 2003 vi Themis Computer Table of Contents How to Use This Manual i 52 csscisecsscoeicesgccssssacintesaageiaa sadesocasentacnacessiacchesdeleeedavdecanenaacentse xi 1 USPIIIi Programming Guide 00 0 0 ccccceccecssececseececseeceseeecseeecneeecsaeeeeneeeeaees 1 1 L1 lt Frit QU Cth ny nean ra ienie i ia iiaiai 1 1 1 2 Jbu s Address Mapri coast taatvecstaile malt a stata latin cue cures aisle o statin ne 1 2 t3 BPO BUS Topology vxsaeissaeshaas tssis eara a Ven A A E A R aE a 1 5 LA lt PCDevices Address Map niicisiroiir totoriai ticle E A T G EEA 1 6 1 5 Ebus Device Address Map s ns sesssseseesessssesseserssessessrssreseessesersseessessessressessessees 1 10 L6 PLEDD Registers einega ne a aa a a a aN 1 10 1 7 PCI Ebus Bridge Configuration EEPROM nssssssssssssessssssessesssssrssressessrssressessessees 1 11 1 8 Universe II VME Interface Registers s 00v55 2iantewninasenentiaa cuentas 1 14 De OBP Command Se n en E E ee os eb A EE ET 2 1 2 Themis OBP Commands
92. nd line parameters e vme_dvma This program sets the USPIIIi to be accessible from VME by enabling a slave window Themis Computer 3 Themis USPIIli Software Writing Programs for the VMEbus e vme_ intr This program uses the example driver vmeintr to send receive VME interrupts vme_mmap This program accesses VME using the Solaris mmap 2 system calls The system calls works by programming the MMU to map VME mem ory within the address space of the calling program Further VME accesses are done using simple references like C language pointers e vme_rw This program accesses VME using the more traditional UNIX approach of doing I Os VME memory is accessed using the UNIX read 2 and write 2 system calls This will result in slower VME transfer speed sw_reset_n_sysfail This program demonstrates the support of programmable VME RESET software reset and sysfail It is an interactive program tthat allows you to explore the supported features sysfail_test This program tests the THEMIS sysfail driver The ioctl func tions include SIOCENSYSF Enable sysfail interrupts SIOCREGSYSF Sends a SIGSEGV if a SYSFAIL interrupt happens SIOCUNREGSYSF Unregister 3 4 3 4 1 Writing Programs for the VMEbus The software interface of the USPIIIi is transparently implemented under Solaris The software interface is fully compatible with the generic Sun4u VME architecture systems Any VME device driver that conforms to the
93. nder reset 1 JP3908 jumper is installed The shutdown condition will not put the board under reset Battle mode bit 4 RO Status of Solder Bead SB3502 the M66en signal for PCI1A 0 The PCI bus PCI1A is running at 33Mhz 1 The PCI bus PCI1A is running at 66Mhz bit 5 RO Status of Solder Bead SB3503 the M66en signal for PCI1B 0 The PCI bus PCI1B is running at 33Mhz 1 The PCI bus PCI1B is running at 66Mhz bit 6 RO Status of the M66en signal for PCI2A 0 The PCI bus PCI2A is running at 33Mhz 1 The PCI bus PCI2A is running at 66Mhz bit 7 RO Status of Solder Bead SB3501 the M66en signal for PCI2B 0 The PCI bus PCI2B is running at 33Mhz 1 The PCI bus PCI2B is running at 66Mhz 4 3 Themis Computer USPIIli Software Manual 4 4 PLD register offset 0x03 Description VME slot geographical ID Width 8 bit Vector name pld_reg 2 i Description bit 0 RO Status of VME P1 signal GAO pin P1 D10 0 GAO pull up 1 GAO tied to GN D by the VME64X backplane bit 1 RO Status of VME P1 signal GA1 pin P1 D11 0 GA1 pull up 1 GAI tied to GN D by the VME64X backplane bit 2 RO Status of VME P1 signal GA2 pin P1 D13 0 GA2 pull up 1 GA2 tied to GN D by the VME64X backplane bit 3 RO Status of VME P1 signal GA3 pin P1 D15 0
94. nt panel termination SCSI A control signals and SCSI A data lines 0 7 0 0 gt The termination are forced in the disabled state 0 1 gt The termination are forced in the enabled state 1 X gt The termination setting depends on the state of the corresponding sense pins Upon reset those bits are set to 1 bit 3 2 RW These bits control the SCSI A upper section of the Front panel termination SCSI A data lines 8 15 0 0 gt The termination are forced in the disabled state 0 1 gt The termination are forced in the enabled state 1 X gt The termination setting depends on the state of the corresponding sense pins Upon reset those bits are set to 1 bit 5 4 RW These bits control the SCSI A lower section of the P2 termination SCSI A control signals and SCSI A data lines 0 7 0 0 gt The termination are forced in the disabled state 0 1 gt The termination are forced in the enabled state 1 X gt The termination setting depends on the state of the corresponding sense pins Themis Computer 4 Programmable Logic Device PLD Register Set Upon reset those bits are set to 1 bit 7 6 RW These bits control the SCSI A upper section of the P2 termination SCSI A data lines 8 15 0 0 gt The termination are forced in the disabled state 0 1
95. ntroller is the PLX9030 which bridges the PCI 2A 33Mhz bus Boot PCI bus to the Ebus peripheral bus Table 1 4 USPIIli Ebus Devices Device Address Board e Part Number Description Size e Reference Des Flash 8Mx8 User Flash AMD29LV065 System e AMD29LV065 0x80 0000 8MBytes e U4701 Attached to CSO of the PLX9030 Serial controller 8 bit bus implementation System e SAB82532 0x80 Implements TTY ports C amp D e U1101 Attached to CS2 of the PLX9030 PLD Cypress Cypress PLD System e CY37512 0x100 Implements miscellaneous registers e U3901 Attached to CS3 of the PLX9030 The base address of each device will be assigned by OBP during the PCI probing process Size information is located in the EEPROM configuration device attached to the PLX9030 The AMD 29LV065 programming algorithm is fully described in the datasheet of this component 1 6 PLD Registers The various registers of the Cypress Programmable Logic Device PLD or CPLD are used to control many different functions of the USPIIIi See Chapter 4 Programmable Logic Device for a full description of the PLD registers Themis Computer 1 USPIIli Programming Guide PCl Ebus Bridge Configuration EEPROM 1 7 PCl Ebus Bridge Configuration EEPROM The Ebus is controlled by the PLX PCI9030 bridge from PLX technology The PCI configuration registers can be downloaded after reset from a non volatile memory EEPROM companion device
96. other board on the chassis The VME controller on the slave board then converts the VME address into an PCI bus virtual address The VME controller then performs a DVMA operation on the PCI bus to access the physical memory location The PCI bus virtual address generated by the VME slave access must be configured in the IOMMU translation table Themis Computer pro vides a driver that performs this configuration the driver allocates a DVMA region and sets it up for VMEbus slave access at a particular VMEbus address The master board simply uses this VMEbus address and generates a slave access operation on the VMEbus The system that allocated the DVMA memory can also access the region by using special ioctl calls provided by the driver Please refer to Section 3 3 4 Sample VME Programs and VME Leaf Drivers on page 3 24 for more information on the vmedvma driver The following code segment sets up a memory region of size 8192 bytes for DVMA access include lt themis vmedvma h gt int fd struct vme_dvmacopy dma_req open the device if fd open dev vmedvma O_RDWR lt 0 perror can t open dev vmedvma exit 1 allocate a DVMA region dma_req size 8192 if ioctl fd VDMA ALLOCATE amp dma_req 0 perror In allocating DVMA close fd return 1 printf Allocated a DVMA region id d at virtual address x n dma_regq id dma_req addr The virtual address
97. power IC U12202 TPS2402 does not report a power failure 1 The USP power IC U12202 TPS2402 reports a power failure bit 4 RO Status of JP4401 which controls the TTY B front panel transceiver mode 0 The TTY B interface transceiver on the front is set to RS422 The jumper JP4401 is ON 1 The TTY B interface transceiver on the front is set to RS232 The jumper JP4401 is OFF bit 5 RO Status of the jumper JP4403 which controls the TTY B port front panel versus P2 0 The TTY B port is accessible on the front panel The jumper JP4403 is OFF 1 The TTY B port is accessible on VME P2 connector The jumper JP4403 is ON bit 6 RO Status of the jumper JP4402 which controls the TTY A port front panel versus P2 0 The TTY A port is accessible on the front panel The jumper JP4402 is OFF 1 The TTY A port is accessible on VME P2 connector The jumper JP4402 is ON bit 7 RO Status of the jumper JP2502 which controls the AC97 port on PMC carrier or on P2 0 The AC97 Audio port is accessible on the PMC carrier The jumper JP2502 is OFF 1 The AC97 Audio port is accessible on VME P2 connector The jumper JP2502 is ON PLD register offset 0x09 Description SCSI_A termination control register Width 8 bit Vector name pld_reg 8 i Description bit 1 0 RW These bits control the SCSI A lower section of the Fro
98. resimini tin eases ee a E E a O ees 2 1 2 2 OBP VME Environment Variables vcicisetscaip nivel evievivane denen niadanainmans deans 2 1 2 3 Additional VME OBP Commands acc ccauk vaecesttecactesiencodea sensaeseshitiann oes ax 2 3 3 Themis USPI SS OU VG AN a tage i eh a ee Se tt ald 3 1 Bell UMPC HOI i e cates alacesre tad ccanasecy cade tea tah a a a E a 3 1 3 2 SUN OpenBoot PROM OBP icigsssseceiceaaietatvalecansecgsaadenadectuastsdeapdevsntetetontecensatecees 3 1 3 2 1 OBP VME Environment Vatiables ccctacdasnsasi sanaieavacearns 3 2 3 2 2 Setting and Reading VME OBP Environment in Hex ss sssessesseesesseseesessee 3 6 3 2 3 Support Commands ss ssssseeseeseesseesseseessressesstesesseestssrsstesseestesresseesresresseesse 3 6 3 231 oprob rsesr al ronn a E A E a n T 3 6 3 2 4 Updating the System Flash PROM osssssosssesssssesessesesssssesseesessessseessesresseesse 3 6 3 2 4 1 Updating the System Flash PROM from the Network 3 7 3 2 4 2 Updating the System Flash Prom From a SCSI Disk 3 8 vii Themis Computer USPIIli Software Manual 3 2 5 Additional OBP commands 3323 scanei cu cedineciieeds antaniadeiasiness 3 9 3 2 5 1 Accessing VME Address Space from OBP eceeeeseeeeeetees 3 9 3 2 5 2 WME Mapping Support under OBP ee ce eeeceeceeereeeteeeeeeeees 3 11 3 2 5 3 USPIIIi OBP Device aliases is ln chestnut eeecpastuieauiatiaecemtecins 3 13 3 3 Overview of VME Interface Under
99. s The following environment variables are used to set the temperature thresholds for the three sensors system low limit 0 system therm limit 80 system high limit 70 cpul low limit 5 cpul therm limit 115 cpul high limit 105 cpu0 Llow limit 5 cpu0 therm limit LIS cpu0 high limit 105 To change the temperature threshold type 1 ok setenv system therm limit 85 To see the current temperature reading on the different sensors type 1 ok env System Board Inlet Outlet Local CPU 0 Die Board Sensor Local Voltage on AinO Backplane Voltage on Ainl Memory Voltage on Ain2 Jbus Voltage on Ain3 CPU core CPU 1 Die Board Sensor Local Voltage on AinO Backplane Voltage on Ainl Memory Voltage on Ain2 Jbus Voltage on Ain3 CPU core 2 6V H1 5V Vcore 5V p26 SV H1 5V Vcore YS ye WH YS He WH input input input input input input input input 33 4980 2578 1503 1347 4980 2578 1484 1386 80 70 115 105 115 105 Q Q mV mV mV mV Q mV mV mV mV Themis Computer 5 Device Monitoring Thermal Monitoring To see a more detailed listing of the sensor temperatures and their threshold settings 1 ok themis show temp System Board Temperature I2C address 58 Device ADM1031 Analog devices ADM1031 device ID 0x31 amal Company
100. s To uninstall the sample drivers cd opt THEMIS3ivme drv ls la total 28 drwxr xr x 6 bin bin 512 Aug 23 15 02 drwxr xr x 6 bin bin 512 Aug 237 15202 zs rw r r 1 bin bin 2964 Mar 4 2004 README first drwxr xr x 3 bin bin 512 Aug 23 15 02 bin rwxr xr x 1 bin bin 2474 Mar 4 2004 install sample rwxr xr x 1 bin bin 1797 Mar 4 2004 remove sample drwxr xr x 2 bin bin 512 Aug 23 15 02 src drwxr Xr x 2 bin bin 512 Aug 23 15 02 sys drwxr xr x 2 bin bin 512 Aug 23 15 02 themis remove sample KKK KKK KKK KKK KKK KKK KKK KKK KKK KKK KKK KKK KKK KK KK KKKKKKKKKEKK i Remove Script for i Themis USPIIIi Solaris 9 X M sample device drivers a4 KKK KKK KKK KK KKK KKK KKK KKK KKK KKK KKK KK KKK KKK KKK KKK KKKKKKEKK This script removes the sample device drivers for Solaris 9 to use the VMEbus interface on the Themis USPIITi If you want to proceed type y or Y Otherwise press any other key to abort y 3 23 Themis Computer USPIIli Software Manual Removing vmeintr interrupt driver Removing vmedvma DVMA driver Updating etc devlink tab Removing installed drivers Removing header files Removal completed 3 3 4 Sample VME Programs and VME Leaf Drivers The software interface provided for the USPIIi platform fully supports standard VMEbus device drivers written for Solaris environments It is the intention of The mis Computer to fu
101. shion to the standard OBP command probe scsi have loopback connectors installed will result in an Link not ready Loss f Note Probing FC AL ports that are not connected to an FC AL drive and do not of Sync error message 3 2 4 Updating the System Flash PROM or corrupted PROM file was downloaded or if you experience a power outage dur ing the process the USPIIli may not be bootable DO NOT interrupt the command while it is in progress Warning Great care must be taken when performing a Flash upgrade If an invalid 3 6 Themis Computer 3 Themis USPIlIli Software SUN OpenBoot PROM OBP 3 2 4 1 Updating the System Flash PROM from the Network To update the system flash PROM from the network you will need to have access to a tftpboot server To update the system flash PROM device 1 First download the OBP image from the tftpboot server To do this type 4000 dload obpimage file For example 1 ok 4000 dload usp3i rev3 7 Boot device pci 1lf 700000 network 2 usp3i rev3 7 File and args 1000 Mbps full duplex Timeout waiting for ARP RARP packet 104000 Server IP address 198 211 242 2 Client IP address 198 211 242 62 2 Next type the flash update command to write the OBP image to the flash 1 ok flash update which results in Update flash with the downloaded OBP image Erasing done Copying Verifying This command writes the previou
102. silent mode scsi initiator id Value 255 false 0 fair ror round robin 1 2 3 4 5 6 0 0 32 1048576 4294967295 0 Value 16777216 1 3735928559 2 T disabled disabled 0 110 100 5 T15 105 5 115 105 true false false 7 Default Value 255 false 0 fair ror round robin 1 2 3 4 5 6 0 0 32 1048576 4294967295 0 Default Value 16777216 1 3735928559 2 1 disabled disabled 0 80 70 5 115 105 5 1S 105 true false false 7 3 3 Themis Computer USPIIli Software Manual Table 3 1 OBP Environment Variables Continued oem logo oem logo oem banner oem banner ansi terminal screen columns screen rows ttyb rts dtr off ttyb ignore cd ttya rts dtr off ttya ignore cd Variable Name ttyb mode ttya mode output device input device auto boot on error load base auto boot boot command diag file diag device boot file boot device use nvramrc Nnvramrc security mode security password security badlogins diag script diag level diag switch rror reset recovery 1 ok false false true 80 34 false true false true Value 9600 8 n 1 9600 8 n 1 screen keyboard false 16384 false boot kadb rv pci l1d 700000 scsi 4 di disk a disk5 false none none min true boot No default false No default false true 80 34 false true false true Default Value 9
103. sions of OBP do not employ the vme selelct dev com mand If this command does not work on your system use the command cd paite 6000007 THEMIS paivme By carefully reviewing the output of the show universe regs command we see that the mapping we defined using the vme32 master base and vme32 mas ter size Themis OBP variables is controlled by the 7th window LS7_ CTL LS7_BS LS7_BD LS7_TO The LS7_BS register contains the base PCI address of that window should be 0x800 0000 Now we can access VME using the OBP space command which permits us to use physical addresses by bypassing the CPU MMU ok 1234 1f 0800 0000 15 spacel writes 1234 to VME address A32 0xaa00 0000 ok 1f 0800 0000 15 spacel reads back from that address 0x 1ff 0000 0000 is the base address of the PCI bus through which VME is accessed 0x15 is the SPARC ASI address space identifier that is defined for PCI accesses Themis Computer 3 Themis USPIIli Software SUN OpenBoot PROM OBP Note The above VME accesses were made using the 0x09 Address modifier code This could be a problem when trying to access other VME boards like the Themis USPHIi 1v since it is programmed to accept supervisor address modifi ers To set the address modifier to be 0x0d supervisor simply enter ok lde universe reg 1000 or lce universe reg This will set the SUPER bit in LSI7_ CTL That was for A32 VME accesses These ac
104. sly downloaded obp image file to flash It is best to update your flash PROM directly after resetting the system Call your Themis Technical Support in case of problems 3 7 Themis Computer USPIIli Software Manual 3 2 4 2 Updating the System Flash Prom From a SCSI Disk and then STOPS It may be necessary for you to temporarily set the OBP variable auto boot to false to prevent Solaris from automatically booting The flash update command described below will only work after a fresh power up to the ok prompt Flash update will not work if you perform a STOP A or Ctrl Break key combination to interrupt the power on self test Solaris boot process Nor will it work if Solaris is already running and you issue a halt or init 0 command to arrive at the ok prompt Note When your system powers up make sure it boots to the ok OBP prompt To update the system flash PROM device using a SCSI disk 1 Download the most recent OBP binary image file from the Themis ftp server Call Themis Customer Support at 510 252 0870 to obtain a user name and pass word that will allow you to access the Themis ftp server To find the OBP image file on the Themis ftp server navigate through the subdi rectories or folders as follows outgoing Release gt obp USPHIi select the folder with the appropriate rev e g rev3 7 gt select the binary file with the appropriate name e g 111068 080 usp3i_obp_revx x_chk_5891 bin
105. tion media in the appropriate slot and execute this command pkgadd d lt media name gt where lt media name gt is the name of the media on your system The pkgadd com mand will copy the contents of the package to the appropriate directories and per form the necessary installation After the command completes the system has to be rebooted for the new software to be operational The pcitvme and the vmemem driv ers will be added to the system Another form of the pkgadd command is pkgadd d lt filename gt where lt filename gt is the name of the binary file containing the package It may be neces sary to use this form of the pkgadd command after downloading a new version of the THEMIS3ivme package from the Themis FTP site You may choose to install sample leaf drivers by executing a script provided for that pur pose The sample drivers are not required for the normal operation of the USPIIIi system however they are required to enable the VME programs to work properly Refer to Sec tion 3 3 4 Sample VME Programs and VME Leaf Drivers on page 3 24 Note The sample drivers will not be installed by this procedure See Section 3 3 3 Installing the Sample Drivers on page 3 21 Themis Computer USPIIli Software Manual 3 18 pkgadd d THEMI S3ivme file The following packages are available 1 THEMIS3ivme Solaris 9 Select package s all packages Processing package instance lt TH 5
106. to how they can be used for user level access In simplistic terms a device can be viewed as a collection of registers that are addressable Almost all of these registers can be either read from or written to Some of them allow both read and write access Access to many of the registers results in effects like resetting the value of the register clearing the interrupt etc Some regis ters require a particular sequence of accessing them Some registers have specific data widths that can be used to access them Though there are some devices that have some very peculiar behavior most devices can be modeled as a collection of registers Such devices if they are VMEbus devices can be programmed and used without the need for a specialized device driver As mentioned before VMEbus addresses are not distinguishable from memory addresses The vmemem driver from Themis Computer which is the device driver for the dev vmeXXdYY files enables a user program to access any address in the VMEbus space This feature can be used to access the registers of a device from a user program The user program needs to open the appropriate dev vmeXXdYY file lseek to the address of the device registers and do a read or write operation The vmemem driver performs the read write operation carefully by using the ddi_peek and ddi_poke calls If the user program opens the appropriate file and the read write access meets the alignment criteria of the device the devi
107. tors that are installed on the System CPUO and CPU1 boards Table 3 8 Temperature Monitoring Commands Command Description usp3i_temp Dumps the temperature and threshold settings This is an interactive method for changing temperature thresholds This change will remain in effect until the next power cycle To make permanent threshold changes use the OBP environment variable see Section 5 2 1 Setting Tem perature Thresholds on page 5 4 usp3i_temp c Causes the system to run in an infinite loop monitoring vsp ar emp abnormal conditions and reporting to the console usp3i_voltage The usp3i_ voltage application see Zable 3 9 interfaces with the PCF8591 device that is used for DC DC voltage monitoring on both CPUO and CPU1 Themis Computer USPIIli Software Manual Table 3 9 Voltage Monitoring Command Command Description Dumps all voltages backplane memory Jbus and usp3i_voltage CPU core usp3i_uled The usp3i_uled application see Table 3 10 interfaces with the PCF8574 device on the CPUO board that controls the four User Status LEDs Table 3 10 User Status LED Commands Command Description usp3i_uled e led Turns ON the specified User LED 1 through 4 usp3i_uled d led Turns OFF the specified User LED 1 through 4 usp3i_pld and plxdrv The usp3i_pld program is an application to get and set bytes in the P
108. uration space 1 4 segments topology 2 PCI Ebus bridge PLD 1 10 4 1 commands 3 42 register set 4 3 registers 7 10 PLD functions 4 dump pld 4 examples 4 2 jumper status vme slot 4 miscellaneous status 4 pldc 4 2 pldc 4 2 pldl 4 2 pldl 4 2 pld revision status 4 pldw 4 2 Themis Computer Index pldw 4 2 scsi termination control 4 scsi termination status 4 scsi termpwr status 4 1 temperature sensor status 4 themis show pld 4 tty kbm ac97 status 4 1 vme reset mode 4 PLX PCI9030 bridge chip 3 42 PLX9030 Ebus controller 7 10 plxdrv application 3 42 PMC Carrier boards xii probing devices 3 34 Programmable Logic Device PLD See PLD or CPLD programming guide programs environmental monitoring 3 41 sample VME 3 24 writing for the VMEbus 3 25 prompts shell xv R read write 3 27 register map Universe II 5 removing THEMIS3ivme 3 20 S SAB 82532 Infineon sample drivers 3 2 sbvmemem 3 21 semaphores shared resources shell prompts xv slave mode 3 29 slot configurations VME xiii SMBALERT 5 3 software configuring the USPIIi 3 27 environmental monitoring programs 3 41 installing THEMIS3ivme 3 7 plxdrv device driver 3 42 programming guide SUN Open Boot PROM See OBP SUN Solaris Operating System 3 5 usp31_pld program 3 42 usp3i_ temp program 3 41 usp3i_uled program 3 42 usp31_ voltage program 3 4 USPI 3 7 VME Nexus driver 3 17 Solaris 3 1
109. urn the ID of the current owner of the semaphore On write access those bits are automatically cleared bit 7 3 RO Read as 0 Themis Computer 4 Programmable Logic Device Output from themis show pld 4 3 Output from themis show pld The following is a typical output response to the themis show pld command 1 ok themis show pld UspIIIi revision ID Revision level Oxf Board ID UspIIIi register Ox7ee 0100 0c00 User jumper and boot device jumper status 0x7ee 0100 0c02 JP3901 INSTALLED JP3902 INSTALLED USPIIIi will boot from the on board system flash JP3903 INSTALLED Enable system flash write JP3908 NOT INSTALLED USPIIIi will go into reset mode under over T temperature condition PCI1A running at 33Mhz PCI1B running at 66Mhz PCI2A running at 33Mhz PCI2B running at 33Mhz No VME64X backplane UspIIIi VME64X slot ID register 0x7ee 0100 0c03 VME reset mode control register Ox7ee 0100 0c04 JP2101 NOT INSTALLED VME SYSCON set using autosensing AJ JP2201 INSTA JP2301 INSTALL CI ED Board CAN assert an outgoing VMEbus sysreset D Board CAN receive an incoming VMEBus sysreset Board is THE VME SYSTEM CONTROLLER The IIIi is isolated from any incoming VME SYSRST UNIVERSE local reset effect has no effect Temperature sensor statu CPUO board temperature no
110. us base address of PCI cfg registers on PCI A segment bus Idsel dev Function fet PCI A configuration space 16MB High address PCI A cfg io offset mask PCI A cfg io offset base PCI A mem offset mask PCI A mem offset base 0x40 0040 Jbus cfg base address for Jbus agent JID oe JID x 273 Low address Figure 1 1 0x400 0000 0000 Jbus cfg base address Hard coded TN Fet t x 2 1 1 l Dev x 2 f Bus x 2 6 Low address Jbus Address Space Mapping to PCI Configuration Space Themis Computer 1 USPIlIli Programming Guide I2C Bus Topology 1 3 IC Bus Topology The USPIIIi has several I C busses numbered 1 to 6 Their topology is provided in Figure 1 2 SOUTHBRIDGE M1535D XBUS PA 0x58 VA 0x58 ICS951601 PA 0xD2 VA 0xD2 SYSTEM BOARD MEMORY 0 PE EEPROM AT24C64 PA 0xA2 VA 0xB8 EEPROM AT24C64 PA 0xA4 VA 0xBA EEPROM AT24C64 PA 0xA6 VA 0xBC ADM1031 PA 0x5C VA 0x5C MEMORY 1 EEPROM U12601 AT24C64 PA 0xA0 VA 0xC6 EEPROM U12601 AT24C64 PA 0xA2 VA 0xC8 EEPROM U12601 AT24C64 PA 0xA4 VA 0xCA PC 3 CPU 1 EEPROM U12601 AT24C64 PA 0xA6 PA 0x5A VA 0xCC VA OxSE PCF8591
111. vices A device driver also provides a standard I O interface to the rest of the system i e a user program should be able to open a device file and issue in most cases a subset of standard system calls to the file The VMEbus interface of Themis Computer s USPIIIi is transparently implemented under Solaris Note that no software support is provided for Solaris 1 x The software interface is fully compatible with the generic Sun4u VME architecture systems Any VME device driver that confirms to the appropriate Solaris Device Driver Interface will run unmodified on Themis platforms This guide is intended to highlight the VMEbus specific features that influence the design of drivers for VMEbus devices It tries to provide basic information and when needed refers to sources for more detailed information on specific concepts A full introduction to the principles of writing device drivers is beyond the scope of this guide The book SunOS 5 x Writing Device Drivers has extensive information on writing device drivers for Solaris systems Themis Computer has developed a number of sample device drivers that illustrate the concepts covered in this chapter Please see Section 3 3 4 Sample VME Pro grams and VME Leaf Drivers on page 3 24 for more information on the sample device drivers These drivers along with user level programs that interface to them are provided in source code format The last section in the guide discusses the
112. wo CPUs such as the UltraSPARC the prompt may be designated as 10 ok or 1 ok For the purposes of this manual future references to the ok prompt will be designated simply as ok f Note The ok prompt appears differently for different systems For example ok setenv variable name value When running Solaris the eeprom command can view or modify environment vari ables the syntax may vary depending on the type of command line shell being used eeprom variable name valu 2 1 Themis Computer USPIIli Hardware Manual J Note Modified environment variables will not take effect until you reboot the system There are a number of ways to reboot the system For example you can execute the OBP command reset al1 or you can recycle power From within Solaris execute the reboot command to shut down the operating system and then reboot Table 2 1 OBP VME Environment Variables Default Variable Name Value Description Value If set to true Universe II is forced to be the system force system controller true false false controller If set to false the system controller sta tus is determined by auto sensing circuitry vme bus request level 0 7 0 Level used to request the VME bus F When the Universe II requests the VME bus it can use vme request mode fair demand fair 3 a fs either fair or demand mode When the Univers
113. xus drivers The pcivme driver encap sulates all the details of the implementation of the VMEbus interface The vmemem driver which is a leaf driver only needs to know that it is connected to the VMEbus Solaris like other UNIX systems represents devices as special files in the file systems These files are advertised by the device driver and are maintained by the drvconfig 1M program Usually the special files are created under the devices directory and represent the hardware layout of a particular machine sysdef 1 and prtconf 1 can be used to view the internal device tree Symbolic links are created from the dev directory to the special files in the devices directory User programs normally use the files from the dev directory VMEbus devices are not self identifying i e they do not provide information about them selves to the system Drivers for VMEbus devices need to have a probe entry so that the kernel can determine if the device is really present Additional information about the device must be provided in a hardware configuration file See driver conf 4 for more information VMEbus interrupts are vectored When a device interrupts it provides the priority as well as an interrupt vector The kernel uses the information to uniquely identify the interrupt ser vice routine to be called The hardware configuration file must specify each priority vector pair that the device may issue Themis Computer 3 Themis USPIIli So

Download Pdf Manuals

Related Search

Related Contents

- Frank`s Hospital Workshop  MT GL - Hermelin Handels  取扱説明書はこちら  BreezeACCESS II System Manual v4.0  Sun StorageTek Backup Manager Administration Guide  Manual de Usuario SERIE FOX 1020  Q-Sec 1 - Le Q-Sec  HP 9483C User's Manual  MODALITA` PER LA RICHIESTA DI ASSISTENZA  WV-ASM100LE - psn  

Copyright © All rights reserved. Failed to retrieve file