[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference vaxaxp::vmsnotes

Title:VAX and Alpha VMS
Notice:This is a new VMSnotes, please read note 2.1
Moderator:VAXAXP::BERNARDO
Created:Wed Jan 22 1997
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:703
Total number of notes:3722

270.0. "DE204 on 2100A ?" by ODIXIE::RREEVES () Mon Mar 03 1997 11:09

        Can I use a DE204 as a second network adapter on a 
        2100A 5/250 running VMS version 6.2-1h2 with the ALPLAN02_062
        patch.
        
        I attempted to read the "readme" file which comes with this patch
        and I don't see a restriction for using this interface card on the 
        2100. 
        
        So, is a DE204 a supported device with this patch under VMS 
        as a second network interface card to a DE435 or not ?
        
        Regards,
        
        Ray
    
T.RTitleUserPersonal
Name
DateLines
270.1Per SPD, DE204 Not SupportedXDELTA::HOFFMANSteve, OpenVMS EngineeringMon Mar 03 1997 11:2418
   I'd definitely install a PCI Ethernet module, if not a PCI FDDI or Fast
   Ethernet module, into this system.

   If you want to know what peripherals are supported, please see the
   Software Product Description (SPD) for the relevent product and release,
   OpenVMS Alpha V6.2-1Hx, in this case.  SPDs are generally present in the
   documentation directories referenced in note 8.*, and in the integrated
   repository (VTX IR, or accessable via WWW).  If the widget is *not*
   listed in the SPD, it's *not* supported.  (Unless you can get one
   of the relevent product managers to indicate to the contrary...)

   Also see the notes conference NOTED::ETHERWORKS.

   The DE204 (EtherWorks III) does not appear to be a supported device
   under OpenVMS, though the DE205 does appear to have support.  (Per
   the V6.2-1H2 (`Zombie') and V7.1 (`Gryphon') SPDs.)

270.2DE205 on an EISA systemSTAR::STOCKDALETue Mar 04 1997 12:32118
The DE203,DE204,DE205 are the same adapter with different media connections,
so the DE205 driver works with any of these.

To run this on a system with an EISA bus, here is some data that I sent to
a customer to use a DE205:

  Note:  This information is covered on pages 256-260 in the "Writing OpenVMS
  Alpha Device Drivers in C" book, by Margie Sherlock and Leonard Szubowicz
  published by Digital Press.

  - Configure the DE205 for the I/O base CSR address, typically address 300,
    320, 340, 360 from the range 100 (hex) to 3E0 (hex).  This can be done on
    a PC using the NICSETUP utility supplied with the device.  Or it can be
    done in an AlphaStation 200,255,400 using the EWRK3_CONFIG utility.

    The EWRK3_CONFIG utility command to set the I/O base address is:

        >>>EWRK3_CONFIG <CR>  - displays a list of adapters
        >>>EWRK3_CONFIG -curaddr 300 -ioaddr 320  - changes the existing
               adapter from address 300 to 320

  - Run the ECU on the target system, and select an available slot for the
    the DE205 and select the configuration file for "Generic ISA slot", then
    F10 to exit and then select "View/edit details" and select the slot that
    was just entered and go to each parameter (IRQ, memory base address, and
    I/O base address) and enter the configuration that you wish to specify.

    The IRQ can be 5, 10, 11, or 15.

    The I/O base would be the preconfigured address from the range 100 to 3E0.

    The memory base address would be a 2k byte range between C0000 and EE000.

  - Install the module (if you have not already done so).

  - Boot the system.

  - Obtain the device CSR address and the adapter number (the TR number):

        $ ANA/SYS
        SDA> read sys$loadable_images:iodef
        SDA> clue config
        get the EISA ADP address
        get the EISA ADP CSR address (EXAM eisa_adp_address + adp$q_csr)
        SDA> exit

  - Construct the configuration command components:

        - Vector for most Alpha systems:     (EISA IRQ * 4)
                 for 2100, 2100a, 8200, 8400 ((EISA IRQ + 7) * 4)

        - Node number:  the slot number you selected when you configured the
                        device with the ECU

        - Adapter number:  the TR number shown in the CLU CONFIG output

        - Driver name:  SYS$ERDRIVER

        - CSR:          The CSR address obtained earlier

  - Write a command file to do this configuration automatically if you are
    so inclined.

Here is an example on a 2100 system, where I installed two DE205s:

  Slot 3, I/O base 300, IRQ 10, mem base D0000
  Slot 4, I/O base 320, IRQ 11, mem base D2000

Obtaining the CSR address:

  $ ANA/SYS
  SDA> read sys$loadable_images:iodef
  SDA> clue config

  Adapter Configuration:
  ----------------------
  TR  Adapter Name (Address)  Hose  Bus          Node  Device Name       HW-Id/SW
  --  ----------------------  ----  -----------  ----  ----------------  --------
   1  KA0902      (809B49C0)     0  CBUS
                                                    0  KA0902_CPU        00000017
                                                    7  KA0902_MEM        00000018
                                                    8  KA0902_IIO        00000019
   2  PCI         (809B4D80)     0  PCI
                                           EWA:     0  TULIP             00021011
                                           PKA:     1  NCR53C810         00011000
                                                    2  MERCURY           04828086
                                           EWB:     6  DC21140           00091011
                                           EWC:     7  TULIP             00021011
                                           EWD:     8  DC21140           00091011
   3  EISA        (809B5480)     0  EISA
                                                    0                    012AA310
                                           ERA:     5  DEPCA             2042A310
                                           IRA:     7  PRO6002           02604F42
                                           GQA:     8  CPQ3011           1130110E
   4  XBUS        (809B59C0)     0  XBUS
                                                    0  EISA_SYSTEM_BOAR  00000016
                                           DVA:     1  AHA1742A_FLOPPY   504F4C46
                                           LRA:     2  VTI82C106_PP      00000015
                                           TTA:     3  NS16450           00016450
  SDA> e (809B5480)+adp$q_csr
  809B5480:  FFFFFFFF 84586000   "......"

Commands to load each adapter (note that I loaded these as ERB0 and ERC0 because I already
had a DE422 installed as ERA0):

  $ mc sysman
  SYSMAN> io connect erb0/driver=sys$erdriver/vector=%x44/node=3/adapter=3/csr=%xFFFFFFFF84586000
  SYSMAN> io connect erc0/driver=sys$erdriver/vector=%x48/node=4/adapter=3/csr=%xFFFFFFFF84586000
  SYSMAN> exit

Caveats:

  The V6.2 SYS$ERDRIVER does not support 2k memory space and the support is not in V6.2, but
  rather it is in a TIMA kit that is on the V6.2 CD.  However, there was a LAN TIMA kit later
  than this one that fixes a bug in user shutdown.  These drivers support 64k memory space
  only.

  V7.1 includes 2k memory support and any bug fixes since V6.2.