bu_cms_history/SN_152

SiteMap (Historical BU CMS wiki main page)

S/N 152

2008-07-16 (hazen, BU)

Complaint was "Lost firmware many times at CERN, sent to Boston. AOK now? Should probably replace logic board, test extensively, send back.".

As of today, it works intermittently, but log2_conf offset 0 (PCI ID) reads 0x20872 instead of 0x20072 and therefore initialization fails.

Should try a new logic board.

2007-09-17 (hazen, CERN)

Working on DCC in slot 14 (S/N 152) of Dick's lab. Currently, this happens:

  cmsmoe4
 ~/hazen/hcal_3_9_7/TriDAS/hcal/hcalDCC/tool $ ./DCCprogrammer.exe sbs:0 14 -i
  HCAL DCCprogrammer v1.2 rev 12 Feb 2007
  Bus:device sbs:0 specified
  Slot number 14 specified
  Looking for HAL addresstable files in directory /home/daqowner/dist/hal/
  (change by setting PROGRAMMER_HAL_PATH environment variable)
  Device to open: /dev/btp96
  DEBUG - DCCConfigInfo::DCCConfigInfo()
  ERROR - 80f20000 2e030000 6e140000 d1fc0000
  ERROR - ERROR: Motherboard::u2SetUpVsi()-> Values could not be read back. Aborting...
  ERROR - Exception 'Could not read from address fffff800 with width of 4 bytes: BT_EINVAL: Invalid argument  passed to Mirror API function' while setting up LOG1/LOG2.  Usually means DCC initialization failed.
  ERROR - Programmer::checkAccessToFlash: Error reading the manufacturer Id: 0xff
  ** Error accessing flash on DCC in slot 14

First, reprogramming the CPLD:

  ./DCCrepair.exe sbs:0 14 -j log3 dcc_confv2.stapl

OK. However, this doesn't change the problem above. Ask Wu for JAM files for PCI1, PCI2.

Got them! Program all 3 PCI devices from JTAG using DCCrepair, same problem. Seems like a possible hardware problem... give up for now.

2007-09-18 (hazen, CERN)

Try a PCI bus scan:

  ./DCCrepair.exe sbs:0 7 -r -c -b -p

 Bus Dev Alias PCI ID     Device ID  CSR      BAR0     BAR1     BAR2     BAR3     BAR4     BAR5
  0   0  br3 ac21104c  PCI bridge  02100143 00000000 00000000 00020100 02000101 00000000 00000000
  0   1 log3 00030072    DCC LOG3  04000000 00000008 00000000 00000000 00000000 00000000 00000000
  0   2  uv2 00020201          ??  00402f21 00020201 00402f21 00020201 00402f21 00020201 00402f21
  0   3   bc ffffffff          ??
  0   4   lc 00040070  Local Ctrl  04000000 00000000 00000001 00000000 00000000 00000000 00000000
  1   0  br2 ac21104c  PCI bridge  02100143 00000000 00000000 00020201 02000101 00000000 00000000
  1   1 log2 00020872          ??  84000800 00000800 00000800 00000808 00000808 00000800 00000800
  1   2 mip3 00400055         LRB  04000000 00000000 00000000 00000000 00000000 00000000 00000000
  1   3 mip4 00400055         LRB  04000000 00000000 00000000 00000000 00000000 00000000 00000000
  1   4 mip5 00400055         LRB  04000000 00000000 00000000 00000000 00000000 00000000 00000000
  2   0   -- ffffffff          ??
  2   1 log1 00010072    DCC LOG1  04000000 00000000 00000000 00000000 00000000 00000000 00000000
  2   2 mip0 ffffffff          ??
  2   3 mip1 00400055         LRB  04000000 00000000 00000000 00000000 00000000 00000000 00000000
  2   4 mip2 00400055         LRB  04000000 00000000 00000000 00000000 00000000 00000000 00000000

Looks fine.

2008-01-07 (hazen, BU)

   > DCCprogrammer.exe 13 -i
  HCAL DCCprogrammer v1.2 rev 12 Feb 2007
  Slot number 13 specified
  Looking for HAL addresstable files in directory /home/daqowner/dist/hal/
  (change by setting PROGRAMMER_HAL_PATH environment variable)
  V2718 firmware : 2.0
  A2818 firmware : 0.6
  VMELibRelease  : 2.3d
  DEBUG - DCCConfigInfo::DCCConfigInfo()
  INFO - Set up logic board at relative address 0x40140000, absolute 0x6d140000.  DCC firmware revision = 0x2c10
  INFO - This is a DCC v4
  ** Flash access OK **
  ** Firmware Revisions:
          LOG1: 0x0009 (9)
          LOG2: 0x0009 (9)
          LOG3: 0x0012 (18)
          MIP1: 0x001b (27)
          MIP2: 0x001b (27)
          MIP3: 0x001b (27)
          MIP4: 0x001b (27)
          MIP5: 0x001b (27)
        XILINX: 0x2c10 (11280)
          CPLD:   0x00 (status bits=0x00)
     serial no: 152

Hmm... not obvious problems. Try PCI bus scan:

 > DCCrepair.exe  13 -r -c -b -p
  Slot number 13 specified
  Scanning crate on bus caen:0 for cards...
  DCC slot 13 selected
  V2718 firmware : 2.0
  A2818 firmware : 0.6
  VMELibRelease  : 2.3d
  INFO:  busAdapter set up
  VMEDevice created for A24
  VMEDevice created for A32
                          Power Up                  Initialized DCC

  Detailed scan of card in slot 13
  Doing PCI bus reset on motherboard
  PCI configuration information
  VSI0 base of 0x2d000000 will be used to access PCI configuration space
  Configuring PCI bus 0/1 bridge
  Configuring PCI bus 1/2 bridge
  Bus Dev Alias PCI ID     Device ID  CSR      BAR0     BAR1     BAR2     BAR3     BAR4     BAR5
    0   0  br3 ac21104c  PCI bridge  02100143 00000000 00000000 00020100 02000101 00000000 00000000
    0   1 log3 00030072    DCC LOG3  04000000 00000008 00000000 00000000 00000000 00000000 00000000
    0   2  uv2 00020201          ??  00402f21 00020201 00402f21 00020201 00402f21 00020201 00402f21
    0   3   bc --------
    0   4   lc 00040070  Local Ctrl  04000000 00000000 00000001 00000000 00000000 00000000 00000000
    1   0  br2 ac21104c  PCI bridge  02100143 00000000 00000000 00020201 02000101 00000000 00000000
    1   1 log2 00020072    DCC LOG2  04000000 00000000 00000000 00000000 00000000 00000000 00000000
    1   2 mip3 00400055         LRB  04000000 00000000 00000000 00000000 00000000 00000000 00000000
    1   3 mip4 00400055         LRB  04000000 00000000 00000000 00000000 00000000 00000000 00000000
    1   4 mip5 00400055         LRB  04000000 00000000 00000000 00000000 00000000 00000000 00000000
    2   0   -- ffffffff          ??
    2   1 log1 00010072    DCC LOG1  04000000 00000000 00000000 00000000 00000000 00000000 00000000
    2   2 mip0 ffffffff          ??
    2   3 mip1 00400055         LRB  04000000 00000000 00000000 00000000 00000000 00000000 00000000
    2   4 mip2 00400055         LRB  04000000 00000000 00000000 00000000 00000000 00000000 00000000

Seems ok too. Let's update all firmwares to latest versions:

  > DCCrepair.exe 13 -j log3 dcc_confv2.stapl -y
  > DCCprogrammer.exe 13 -p LOG1 pci1vc.hex -y
  > DCCprogrammer.exe 13 -p LOG2 pci2vb.hex -y
  > DCCprogrammer.exe 13 -p LOG3 pci3v15.hex -y
  > DCCprogrammer.exe 13 -p XILINX dccv2c18.mcs -y

All seems OK now:

  > DCCprogrammer.exe 13 -i
  HCAL DCCprogrammer v1.2 rev 12 Feb 2007
  Slot number 13 specified
  Looking for HAL addresstable files in directory /home/daqowner/dist/hal/
  (change by setting PROGRAMMER_HAL_PATH environment variable)
  V2718 firmware : 2.0
  A2818 firmware : 0.6
  VMELibRelease  : 2.3d
  DEBUG - DCCConfigInfo::DCCConfigInfo()
  INFO - Set up logic board at relative address 0x40140000, absolute 0x6d140000.  DCC firmware revision = 0x2c18
  INFO - This is a DCC v4
  ** Flash access OK **
  ** Firmware Revisions:
          LOG1: 0x000c (12)
          LOG2: 0x000b (11)
          LOG3: 0x0015 (21)
          MIP1: 0x001b (27)
          MIP2: 0x001b (27)
          MIP3: 0x001b (27)
          MIP4: 0x001b (27)
          MIP5: 0x001b (27)
        XILINX: 0x2c18 (11288)
          CPLD:   0x02 (status bits=0x00)
     serial no: 152

Take some VME data with spigots 0,1 connected. Looks superficially ok. Set aside for now.