Difference: AMC13DebuggingHints (7 vs. 8)

Revision 810 Oct 2015 - EricHazen

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

Menu of Topics

>
>

AMC13 Debugging Hints

 
Changed:
<
<
>
>
 
Changed:
<
<
>
>

My AMC13 is plugged in but I can't contact it!

 
Changed:
<
<

My AMC13 is plugged in but I can't contact it!

>
>

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:
Line: 71 to 69
  Also, the +12V should read something like 12V.
Changed:
<
<

Point 5 Test Crate

>
>

IP Address set incorrectly or unknown

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

$ cd ...../dev_tools/amc13Config
$ #--- edit systemVars.py to set your MCH IP address ---
$ ./scanCrate.pl
 1: MMC: -none-
 2: MMC: -none-
 3: MMC: -none-
Opening   192.168.20.200...
AMC13Tool2 threw an exception
Address table path "/home/hazen/work/new/amc13/amc13/etc/amc13" set from AMC13_ADDRESS_TABLE_PATH
use_ch false
Created URI from IP address:
  T2: ipbusudp-2.0://192.168.20.200:50001
  T1: ipbusudp-2.0://192.168.20.201:50001
Caught microHAL exception.
 4: MMC: 2.2    IP:    192.168.20.200   192.168.10.100 vv: 0x0000 sv: 0x0000 sn: 0
 5: MMC: -none-
 6: MMC: -none-
 7: MMC: -none-
 8: MMC: -none-
Opening    192.168.1.168...
 9: MMC: 2.1    IP:     192.168.1.168    192.168.1.169 vv: 0x4037 sv: 0x0025 sn: 43
10: MMC: -none-
Opening     192.168.1.56...
11: MMC: 2.2    IP:      192.168.1.56     192.168.1.57 vv: 0x4037 sv: 0xfff9 sn: 227
Opening     192.168.1.42...
12: MMC: 2.2    IP:      192.168.1.42     192.168.1.43 vv: 0x100a sv: 0x0021 sn: 106
Opening    192.168.2.188...
13: MMC: 2.2    IP:     192.168.2.188    192.168.2.189 vv: 0x4037 sv: 0x002d sn: 161

You can see that the board in slot 4 has crazy IP addresses (20.200 and 10.100). You can reset them as follows:

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

This will reset the AMC13 to two successive IP addresses beginning with 192.168.3.248. The applyConfig sets the address immediately. The storeConfig sets it in the EEPROM for next power-up.

If the above fails for some reason you may need to erase the EEPROM attached to the MMC. Connect a mini USB cable (not micro USB) to the front panel, which is the console for the MMC microcontroller. It should enumerate as a usb emulated serial port, maybe /dev/ttyUSB0. (look in dmesg to see).

Then connect using a terminal program (minicom is what I use) set to 19200 baud, 8 data bits, no parity, no hardware or software handshake.

You can type "help" to get a list of commands, but what you want is "eeperase" followed by "yes". After this, cycle the crate or module power and the IP address should be reset to the S/N default (see IPaddressAssignment). Then you can use applyConfig and storeConfig to reset it.

Point 5 Test Crate

  Some helpful hints from Jim.

Line: 92 to 151
 (power on module no. 30)
Changed:
<
<

Talking to the MMC over IPMI

>
>

Talking to the MMC over IPMI

  The IPMI command for graceful reboot is as follows:

 
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