Difference: AMC13DebuggingHints (8 vs. 9)

Revision 925 Apr 2019 - EricHazen

Line: 1 to 1
 
META TOPICPARENT name="HcalDTC"

AMC13 Debugging Hints

Line: 9 to 9
 

Check sensor info (NAT MCH)

If you have an NAT MCH, you can learn a lot about the state of your AMC13 (or other MicroTCA module) with the show_sensorinfo command. First, connect to your MCH using telnet:

Changed:
<
<
[cms2] /home/hazen/amc13_python/src_amc13 > telnet 192.168.1.41

>
>
[cms2] /home/hazen/amc13_python/src_amc13 > telnet 192.168.1.41

 Trying 192.168.1.41... Connected to 192.168.1.41. Escape character is '^]'.

Welcome to NAT-MCH

Changed:
<
<
nat> show_fru
>
>
nat> show_fru
  FRU Information:
Line: 37 to 35
 

The show_fru command lists the "field replaceable units" (i.e. cards) plugged in to the crate. It knows about AMC13's, so they appear by name (in fact it currently mis-identifies MiniCTR2 as AMC13!). We have a MiniCTR2 in slot 4, an AMC13 in slot 9 and another AMC13 in the MCH2 sigte (FRU 30).

Changed:
<
<
nat> show_sensorinfo 30

>
>
nat> show_sensorinfo 30

 Sensor Information for AMC 13 ==================================================== # SDRType Sensor Entity Inst Value State Name
Line: 52 to 48
  5 Full Voltage 0xc1 0x7a 1.1932 ok T2 1.2V 9 Full 0xc0 0xc1 0x7a 0x83 0x00 GPIO 7:0
Changed:
<
<
nat>
>
>
nat>
 

The Hotswap sensor indicates the state of the switch connected to the handle (actually, the MMC state machine driven by it). When the module is correctly plugged in and the handle pushed in, it should read 0x01 as above. The values gleaned from the MMC firmware listing are as follows:

(bit values given as an 'or' in the readout):

Changed:
<
<
  01 - handle closed

>
>
  01 - handle closed

  02 - handle open 04 - quiesced (??) 08 - backend power failure
Line: 72 to 66
 

IP Address set incorrectly or unknown

What IP address is your AMC13 using? You can find out as follows.

Changed:
<
<
$ cd ...../dev_tools/amc13Config

>
>
$ cd ...../dev_tools/amc13Config

 $ #--- edit systemVars.py to set your MCH IP address --- $ ./scanCrate.pl 1: MMC: -none-
Line: 106 to 98
  You can see that the board in slot 4 has crazy IP addresses (20.200 and 10.100). You can reset them as follows:
Changed:
<
<
./applyConfig.py --slot=4 -i 192.168.3.248

>
>
./applyConfig.py --slot=4 -i 192.168.3.248

 ./storeConfig.py --slot=4 -i 192.168.3.248
Line: 134 to 124
 

Point 5 Test Crate

Some helpful hints from Jim.

Changed:
<
<
from hcaldaq12:

>
>
from hcaldaq12:

  telnet 192.168.1.41 h
Line: 150 to 140
 pwr_on 30 (power on module no. 30)
Added:
>
>

Remote Hard reset of AMC13

 
Added:
>
>
It is rumored that the following will reset an AMC moule if you have an NAT MCH:

I have a good news. After discussing this issue with several people and also with colleagues from HCAL, I discovered that NAT-MCH has a hidden set of commands, which you can simply run from telnet. So there is a working solution for the FPGA<->MMC communication getting stuck. The way I do so:

  1. "telnet 192.168.1.41" - connect to the MCH using telnet
  2. "show_pm" - print the list of the units, we will need the FruId from there. So if your FC7 is in slot AMC3, the FruId is 7
  3. "hidden" - print hidden commands:))
  4. "hard_reset 7" - reset the FC7
Description is for FC7 but should apply to AMC13 as well
 

Talking to the MMC over IPMI

The IPMI command for graceful reboot is as follows:

Changed:
<
<
  ipmitool -H 192.168.1.240 -U '' -P '' -T 0x82 -B 0 -b 7 -t 0xa4 raw 0x2c 0x04 0 26 0x02 

>
>
  ipmitool -H 192.168.1.240 -U '' -P '' -T 0x82 -B 0 -b 7 -t 0xa4 raw 0x2c 0x04 0 26 0x02 

 

-- EricHazen - 20 Mar 2012

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback