AMC13XG_Debug_Log < BUCMSPublic

Tags: view all tags
*2013-05-29* - hazen

Build MMC v2.1 from tom using default settings in AVR studio 6.1 and flash.
Payload power comes on, MMC messages look ok but can't ping at jumper-based address.
Module is AMC13XG #34, IP addr should be 192.168.1.186.  Charlie is investigating.

Board in slot 3 works; board in slot 4 doesn't.  Here is the "show_sensorinfo" output
from the MCH:

<pre>
==========================================
nat> show_sensorinfo 8
Sensor Information for AMC 4
========================================================
  #   SDRType  Sensor Entity Inst  Value   State  Name
--------------------------------------------------------
  0   MDevLoc          0xc1  0x64                 BU AMC13
  0   Full     0xf2    0xc1  0x64  0x01        Hotswap
  1   Full     Temp    0xc1  0x64  24.25   ok     T2 Temp
  2   Full     Voltage 0xc1  0x64  12.54   ok     +12V
  3   Full     Voltage 0xc1  0x64  3.315   ok     +3.3V
  4   Full     Voltage 0xc1  0x64  1.2000  ok     +1.2V
  5   Full     0x08    0xc1  0x64   0x00     0x01  Pwr Good
  6   Full     0x15    0xc1  0x64   0x00     0x01  Alarm Level
  7   Full     0xc0    0xc1  0x64   0x00     0x00  FPGA Config
--------------------------------------------------------
nat> show_sensorinfo 7
Sensor Information for AMC 3
========================================================
  #   SDRType  Sensor Entity Inst  Value   State  Name
--------------------------------------------------------
  0   MDevLoc          0xc1  0x63                 BU AMC13
  0   Full     0xf2    0xc1  0x63  0x01        Hotswap
  1   Full     Temp    0xc1  0x63  28.50   ok     T2 Temp
  2   Full     Voltage 0xc1  0x63  12.54   ok     +12V
  3   Full     Voltage 0xc1  0x63  3.315   ok     +3.3V
  4   Full     Voltage 0xc1  0x63  1.2000  ok     +1.2V
  5   Full     0x08    0xc1  0x63   0x00     0x02  Pwr Good
  6   Full     0x15    0xc1  0x63   0x00     0x01  Alarm Level
  7   Full     0xc0    0xc1  0x63   0x00     0x35  FPGA Config
--------------------------------------------------------
</pre>

*2013-05-03* - hazen

Looking at JTAG signals on S/N 0x20.
Now moving the T2 board from S/N 19 to S/N 0x21 for testing.  Programming works, as expected.
JTAG signals look quantitatively different,
but the details would require days with a logic analyzer.

*2013-05-02* - hazen

Chris changed the chip on S/N 0x20.  Didn't help.

*2013-04-30* - hazen

Mysteries with MMCs on new T2 boards.  Chips are marked 3A1512 but ID as 3A0512 according to Wu.

 Chip marking:
<pre>
  32UC3A1512-U
  1114 D5CQ5.1
</pre>

   * [[http://www.atmel.com/devices/at32uc3a1512.aspx][Atmel product page]] &ndash; available only in TQFP100 which is what we have
   * [[http://ohm.bu.edu/~hazen/CMS/AMC13DebugData/avr_mismatch.gif][avr_mismatch.gif]] &ndash; screen capture of error when we try to ID the device with AVR Studio 5.1



-- Main.EricHazen - 30 Apr 2013
Topic revision: r3 - 29 May 2013 - EricHazen