Regarding the MSP430 update for C6678 EVM and the Vadatech AMC Chassis

Brandy Jabkiewicz

Other Parts Discussed in Thread: MSP-FET

Hello,

I think this must be a very simple question, but I am new to the uTCA concept and also to the C6678 EVM.

I have followed this older post: http://e2e.ti.com/support/dsp/c6000_multi-core_dsps/f/639/t/115240.aspx?PageIndex=4

It directs me to update my MSP430 to this newest code and then, I am assuming, I should be able to connect via SRIO to the MCH. Seems quite simple.

However, I get the distinct feeling that when I programmed it the NVRAM did not get programmed correctly. When I ask the chassis what FRU's are registered, I values that seem like they are defaults or even bad values that the MSP430 source code says should have been overwritten.

When I programmed it, I merely built the code and the loaded it via CCSv5 and the MSP-FET 430 UIF programmer. Is there a script or something that I was supposed to run to update the NVRAM. I feel like this was a bit simple and incorrect.

Thanks for you help! Please see below for some sample fru data.

Here is a sample of what my fru info was and my link info:

The FRU name comes up FRU Unknown - odd. But I can use FRU ID #11 to control the EVM's LEDs. So I know this is the right address.

(0x20, FRU# 00)     (0xf0, 0x01)     VT UTCA SHELF     M4 (Active)
(0x82, FRU# 00)     (0xc2, 0x01)     VT UTCA CARRIER   M4 (Active)
(0x82, FRU# 01)     (0xf2, 0x61)     SH FRU DEV1       M4 (Active)
(0x82, FRU# 02)     (0xf2, 0x62)     SH FRU DEV2       M4 (Active)
(0x82, FRU# 03)     (0xc2, 0x61)     VT UTCA MCMC      M4 (Active)
(0x82, FRU# 04)     (0xc2, 0x62)     VT UTCA MCMC      M4 (Active)
(0x82, FRU# 05)     (0xc1, 0x61)     VT AMC719         M4 (Active)
(0x82, FRU# 11)     (0x00, 0x00)     FRU Unknown       M4 (Active)
(0x82, FRU# 40)     (0x1e, 0x61)     VT VT095          M4 (Active)
(0x82, FRU# 41)     (0x1e, 0x62)     VT VT095          M4 (Active)
(0x82, FRU# 50)     (0x0a, 0x61)     VT UTC010         M4 (Active)
(0x82, FRU# 79)     (0xf3, 0x60)     TELCO ALARM       M4 (Active)

I can also use FRU ID#11 to get the AMC Point to Point results. These look like they should be correct - the SRIO is showing available. However the GUID is 0x1BAD1BAD... this is my first hint that something did not go right :)

AMC Point-To-Point Results

--------------------------------------------------------------------------------

OEM Guid Count 01

GUID[00]
0x1bad1bad00000000000000000bad0bad

Record Type :AMC

Channels Defined :3

AMC Channel Descriptor #0

Lane 0 = Port0

Lane 1 = Port1

Lane 2 = Port31

Lane 3 = Port31

AMC Channel Descriptor #1

Lane 0 = Port8

Lane 1 = Port9

Lane 2 = Port10

Lane 3 = Port11

AMC Channel Descriptor #2

Lane 0 = Port4

Lane 1 = Port5

Lane 2 = Port31

Lane 3 = Port31

AMC Link Descriptor #0

Channel
ID 0

Lane Mask 0x1

Link Type AMC.2 Ethernet (0x5)

Link Type
Ext. 1000BASE-BX (SerDES Gigabit)
Ethernet (0x0)

Group ID 0

Asymmetric
Match 0

AMC Link Descriptor #1

Channel
ID 0

Lane Mask 0x2

Link Type AMC.2 Ethernet (0x5)

Link Type
Ext. 1000BASE-BX (SerDES Gigabit)
Ethernet (0x0)

Group ID 0

Asymmetric Match 0

AMC Link Descriptor #2

Channel
ID 1

Lane Mask 0xf

Link Type AMC.4 Serial RapidIO (0x6)

Link Type
Ext. No Extension Specified (0x3)

Group ID 0

Asymmetric
Match 0

AMC Link Descriptor #3

Channel
ID 1

Lane Mask 0xf

Link Type AMC.4 Serial RapidIO (0x6)

Link Type
Ext. 3.125 Gbaud transmission rate
(2.5 Gbps) (0x2)

Group ID 0

Asymmetric
Match 0

AMC Link Descriptor #4

Channel
ID 1

Lane Mask 0xf

Link Type AMC.4 Serial RapidIO (0x6)

Link Type
Ext. 2.5 Gbaud transmission rate
(2.0 Gbps) (0x1)

Group ID 0

Asymmetric
Match 0

AMC Link Descriptor #5

Channel
ID 1

Lane Mask 0xf

Link Type AMC.4 Serial RapidIO (0x6)

Link Type
Ext. 1.25 Gbaud transmission rate
(1.0 Gbps) (0x0)

Group ID 0

Asymmetric
Match 0

AMC Link Descriptor #6

Channel
ID 1

Lane Mask 0x3

Link Type AMC.4 Serial RapidIO (0x6)

Link Type
Ext. No Extension Specified (0x3)

Group ID 0

Asymmetric
Match 0

AMC Link Descriptor #7

Channel
ID 1

Lane Mask 0x3

Link Type AMC.4 Serial RapidIO (0x6)

Link Type
Ext. 3.125 Gbaud transmission rate
(2.5 Gbps) (0x2)

Group ID 0

Asymmetric
Match 0

AMC Link Descriptor #8

Channel
ID 1

Lane Mask 0x3

Link Type AMC.4 Serial RapidIO (0x6)

Link Type
Ext. 2.5 Gbaud transmission rate
(2.0 Gbps) (0x1)

Group ID 0

Asymmetric
Match 0

AMC Link Descriptor #9

Channel
ID 1

Lane Mask 0x3

Link Type AMC.4 Serial RapidIO (0x6)

Link Type
Ext. 1.25 Gbaud transmission rate
(1.0 Gbps) (0x0)

Group ID 0

Asymmetric
Match 0

AMC Link Descriptor #10

Channel
ID 1

Lane Mask 0xc

Link Type AMC.4 Serial RapidIO (0x6)

Link Type
Ext. No Extension Specified (0x3)

Group ID 0

Asymmetric
Match 0

AMC Link Descriptor #11

Channel
ID 1

Lane Mask 0xc

Link Type AMC.4 Serial RapidIO (0x6)

Link Type
Ext. 3.125 Gbaud transmission rate
(2.5 Gbps) (0x2)

Group ID 0

Asymmetric
Match 0

AMC Link Descriptor #12

Channel
ID 1

Lane Mask 0xc

Link Type AMC.4 Serial RapidIO (0x6)

Link Type
Ext. 2.5 Gbaud transmission rate
(2.0 Gbps) (0x1)

Group ID 0

Asymmetric
Match 0

AMC Link Descriptor #13

Channel
ID 1

Lane Mask 0xc

Link Type AMC.4 Serial RapidIO (0x6)

Link Type
Ext. 1.25 Gbaud transmission rate
(1.0 Gbps) (0x0)

Group ID 0

Asymmetric
Match 0

AMC Link Descriptor #14

Channel
ID 1

Lane Mask 0x1

Link Type AMC.4 Serial RapidIO (0x6)

Link Type
Ext. No Extension Specified (0x3)

Group ID 0

Asymmetric
Match 0

AMC Link Descriptor #15

Channel
ID 1

Lane Mask 0x1

Link Type AMC.4 Serial RapidIO (0x6)

Link Type
Ext. 3.125 Gbaud transmission rate
(2.5 Gbps) (0x2)

Group ID 0

Asymmetric
Match 0

AMC Link Descriptor #16

Channel
ID 1

Lane Mask 0x1

Link Type AMC.4 Serial RapidIO (0x6)

Link Type
Ext. 2.5 Gbaud transmission rate
(2.0 Gbps) (0x1)

Group ID 0

Asymmetric
Match 0

AMC Link Descriptor #17

Channel
ID 1

Lane Mask 0x1

Link Type AMC.4 Serial RapidIO (0x6)

Link Type
Ext. 1.25 Gbaud transmission rate
(1.0 Gbps) (0x0)

Group ID 0

Asymmetric
Match 0

AMC Link Descriptor #18

Channel
ID 1

Lane Mask 0x2

Link Type AMC.4 Serial RapidIO (0x6)

Link Type
Ext. No Extension Specified (0x3)

Group ID 0

Asymmetric
Match 0

AMC Link Descriptor #19

Channel
ID 1

Lane Mask 0x2

Link Type AMC.4 Serial RapidIO (0x6)

Link Type Ext. 3.125 Gbaud transmission rate (2.5 Gbps)
(0x2)

Group ID 0

Asymmetric
Match 0

AMC Link Descriptor #20

Channel
ID 1

Lane Mask 0x2

Link Type AMC.4 Serial RapidIO (0x6)

Link Type
Ext. 2.5 Gbaud transmission rate
(2.0 Gbps) (0x1)

Group ID 0

Asymmetric
Match 0

AMC Link Descriptor #21

Channel
ID 1

Lane Mask 0x2

Link Type AMC.4 Serial RapidIO (0x6)

Link Type
Ext. 1.25 Gbaud transmission rate
(1.0 Gbps) (0x0)

Group ID 0

Asymmetric
Match 0

AMC Link Descriptor #22

Channel
ID 1

Lane Mask 0x4

Link Type AMC.4 Serial RapidIO (0x6)

Link Type
Ext. No Extension Specified (0x3)

Group ID 0

Asymmetric
Match 0

AMC Link Descriptor #23

Channel
ID 1

Lane Mask 0x4

Link Type AMC.4 Serial RapidIO (0x6)

Link Type
Ext. 3.125 Gbaud transmission rate
(2.5 Gbps) (0x2)

Group ID 0

Asymmetric
Match 0

AMC Link Descriptor #24

Channel
ID 1

Lane Mask 0x4

Link Type AMC.4 Serial RapidIO (0x6)

Link Type
Ext. 2.5 Gbaud transmission rate
(2.0 Gbps) (0x1)

Group ID 0

Asymmetric
Match 0

AMC Link Descriptor #25

Channel
ID 1

Lane Mask 0x4

Link Type AMC.4 Serial RapidIO (0x6)

Link Type
Ext. 1.25 Gbaud transmission rate
(1.0 Gbps) (0x0)

Group ID 0

Asymmetric
Match 0

AMC Link Descriptor #26

Channel
ID 1

Lane Mask 0x8

Link Type AMC.4 Serial RapidIO (0x6)

Link Type
Ext. No Extension Specified (0x3)

Group ID 0

Asymmetric
Match 0

AMC Link Descriptor #27

Channel
ID 1

Lane Mask 0x8

Link Type AMC.4 Serial RapidIO (0x6)

Link Type
Ext. 3.125 Gbaud transmission rate
(2.5 Gbps) (0x2)

Group ID 0

Asymmetric
Match 0

AMC Link Descriptor #28

Channel ID 1

Lane Mask 0x8

Link Type AMC.4 Serial RapidIO (0x6)

Link Type
Ext. 2.5 Gbaud transmission rate
(2.0 Gbps) (0x1)

Group ID 0

Asymmetric
Match 0

AMC Link Descriptor #29

Channel
ID 1

Lane Mask 0x8

Link Type AMC.4 Serial RapidIO (0x6)

Link Type
Ext. 1.25 Gbaud transmission rate
(1.0 Gbps) (0x0)

Group ID 0

Asymmetric
Match 0

AMC Link Descriptor #30

Channel
ID 2

Lane Mask 0x3

Link Type AMC.1 PCI Express (0x2)

Link Type
Ext. Gen 2-capable (0x2)

Group ID 0

Asymmetric
Match 1

AMC Link Descriptor #31

Channel
ID 2

Lane Mask 0x3

Link Type AMC.1 PCI Express (0x2)

Link Type
Ext. Gen 1-capable (0x0)

Group ID 0

Asymmetric
Match 1

AMC Link Descriptor #32

Channel
ID 2

Lane Mask 0x1

Link Type AMC.1 PCI Express (0x2)

Link Type
Ext. Gen 2-capable (0x2)

Group ID 0

Asymmetric
Match 1

AMC Link Descriptor #33

Channel
ID 2

Lane Mask 0x1

Link Type AMC.1 PCI Express (0x2)

Link Type
Ext. Gen 1-capable (0x0)

Group ID 0

Asymmetric
Match 1

over 13 years ago

0 Rakesh Modi over 13 years ago

Expert 1680 points

Hi Brandy,

For MSP430 MMC code you need not to program NVRAM, as MMC code is not reading data from NVRAM.

Please try to use .out file available with EVM_ipm430_v1.32.zip, without building code.

Please also send me power on log of uTCA chasis, so I can help you more in detail.

Thanks & Regards,

Rakesh Modi

0 Brandy Jabkiewicz over 13 years ago in reply to Rakesh Modi

Mastermind 6325 points

Can you tell me where to find the power on log in the MCH?

0 Brandy Jabkiewicz over 13 years ago in reply to Brandy Jabkiewicz

Mastermind 6325 points

Hello,

I used the binary from the zip file and I still get the same behavoir. The EVMs are still being listed as FRU Unknown. I walked through the code and it really looks like it should be set to "TI EVM".

[root@vtipmi etc]# list_frus_present

   Location        Entity ID/Inst     Device Name      Hotswap State
(0x20, FRU# 00)     (0xf0, 0x01)     VT UTCA SHELF     M4 (Active)
(0x82, FRU# 00)     (0xc2, 0x01)     VT UTCA CARRIER   M4 (Active)
(0x82, FRU# 01)     (0xf2, 0x61)     SH FRU DEV1       M4 (Active)
(0x82, FRU# 02)     (0xf2, 0x62)     SH FRU DEV2       M4 (Active)
(0x82, FRU# 03)     (0xc2, 0x61)     VT UTCA MCMC      M4 (Active)
(0x82, FRU# 04)     (0xc2, 0x62)     VT UTCA MCMC      M4 (Active)
(0x82, FRU# 10)     (0xc1, 0x66)     VT AMC719         M4 (Active)
(0x82, FRU# 12)     (0x00, 0x00)     FRU Unknown       M4 (Active)
(0x82, FRU# 14)     (0x00, 0x00)     FRU Unknown       M4 (Active)
(0x82, FRU# 40)     (0x1e, 0x61)     VT VT095          M4 (Active)
(0x82, FRU# 41)     (0x1e, 0x62)     VT VT095          M4 (Active)
(0x82, FRU# 50)     (0x0a, 0x61)     VT UTC010         M4 (Active)
(0x82, FRU# 79)     (0xf3, 0x60)     TELCO ALARM       M4 (Active)

0 Dan Gold over 13 years ago in reply to Brandy Jabkiewicz

Intellectual 320 points

What Vadatech chassis are you running on ?

What is the output of "read_fru_storage -a 0x82 -f 11" from the Vadatech MCH prompt ? I assume FRU 11 is the EVM card.

Don't worry about programming the NVRAM, the current mmc code doesn't use it. That's why it generates all the FRU data in fru_data_init() instead of reading it in from NVRAM.

Dan

0 Dan Gold over 13 years ago in reply to Dan Gold

Intellectual 320 points

The product name should really show up as "TI Lite EVM" according to the v1.32 code.

Have you run the command on the MCH to show the SRIO connectivity ? On Vadatech PCIe chassis the command is just "pcie". I'm sure there's something similar for SRIO. See if the connectivity is there.

I can't remember the SRIO width supported - does the EVM card do x1, x2, and x4 ?

Dan

0 Brandy Jabkiewicz over 13 years ago in reply to Dan Gold

Mastermind 6325 points

Hi Dan,

Thanks for the interest.

I am working on a Vadatech VT862. I have MCH UTC002 with SRIO on backplane ports 8 to 11. UTC002 has two SRIO switches.

As I was looking through the code, I was pretty sure we were not using the NVRAM but since I can't figure out what is wrong, I didn't want to eliminate it as an option. Additionally, I noticed that the firmware version did not get updated in the code. Can you confirm this? When I do get_device_info, it shows that it is still 1.20 and in the 1.32 release the #define is still 1.20. However this was causing some confusion while trouble shooting with Vadatech as they are not convinced I updated the MMC on the EVM. I told them I would double check.

[root@vtipmi root]# get_device_id -a 0x82 -f 14

(0x82, FRU# 14)

        Device ID                : 0000
        Device Revision          : 0
        Firmware Revision        : 1.20
        IPMI Version             : 2.0
        Device Support
            Sensor               : Yes
            SDR Repository       : Yes
            SEL                  : No
            FRU Inventory        : Yes
            IPMB Event Receiver : No
            IPMB Event Generator : Yes
            Bridge               : No
            Chassis              : No
        Manufacturer ID          : 013121
        Product ID               : 0007
        Auxiliary Revision       : N/A

Here is the command:

[root@vtipmi root]# read_fru_storage -a 0x82 -f 14

(0x82, FRU# 14) Inventory Storage Information

BOARD INFORMATION AREA

Format Version                 : 1
Length                         : 6 (multiples of 8 bytes)
Language Code                  : 0x0
Manufacturing Date/Time        : Mon Jan 1 00:00:00 1996
Board Manufacturer             : Texas Instrumnets
Board Product Name             : TI EVM
Board Serial Number            :
Board Part Number              :
FRU Programmer File ID         :

MULTI-RECORDS AREA

Manufacturer ID : 012634
Version         : 02
Type            : OEM Record (0xc0)
PICMG Record    : AMC Point-to-Point Connectivity Record (0x19)

OEM Guid Count 01
GUID[00] 0x1bad1bad00000000000000000bad0bad
Record Type : AMC
Channels Defined : 3

AMC Channel Descriptor #0
        Lane 0 = Port 0
        Lane 1 = Port 1
        Lane 2 = Port 31
        Lane 3 = Port 31

AMC Channel Descriptor #1
        Lane 0 = Port 8
        Lane 1 = Port 9
        Lane 2 = Port 10
        Lane 3 = Port 11

AMC Channel Descriptor #2
        Lane 0 = Port 4
        Lane 1 = Port 5
        Lane 2 = Port 31
        Lane 3 = Port 31

AMC Link Descriptor #0
        Channel ID          0
        Lane Mask           0x1
        Link Type           AMC.2 Ethernet (0x5)
        Link Type Ext.      1000BASE-BX (SerDES Gigabit) Ethernet (0x0)
        Group ID            0
        Asymmetric Match    0

AMC Link Descriptor #1
        Channel ID          0
        Lane Mask           0x2
        Link Type           AMC.2 Ethernet (0x5)
        Link Type Ext.      1000BASE-BX (SerDES Gigabit) Ethernet (0x0)
        Group ID            0
        Asymmetric Match    0

AMC Link Descriptor #2
        Channel ID          1
        Lane Mask           0xf
        Link Type           AMC.4 Serial RapidIO (0x6)
        Link Type Ext.      No Extension Specified (0x3)
        Group ID            0
        Asymmetric Match    0

AMC Link Descriptor #3
        Channel ID          1
        Lane Mask           0xf
        Link Type           AMC.4 Serial RapidIO (0x6)
        Link Type Ext.      3.125 Gbaud transmission rate (2.5 Gbps) (0x2)
        Group ID            0
        Asymmetric Match    0

AMC Link Descriptor #4
        Channel ID          1
        Lane Mask           0xf
        Link Type           AMC.4 Serial RapidIO (0x6)
        Link Type Ext.      2.5 Gbaud transmission rate (2.0 Gbps) (0x1)
        Group ID            0
        Asymmetric Match    0

AMC Link Descriptor #5
        Channel ID          1
        Lane Mask           0xf
        Link Type           AMC.4 Serial RapidIO (0x6)
        Link Type Ext.      1.25 Gbaud transmission rate (1.0 Gbps) (0x0)
        Group ID            0
        Asymmetric Match    0

AMC Link Descriptor #6
        Channel ID          1
        Lane Mask           0x3
        Link Type           AMC.4 Serial RapidIO (0x6)
        Link Type Ext.      No Extension Specified (0x3)
        Group ID            0
        Asymmetric Match    0

AMC Link Descriptor #7
        Channel ID          1
        Lane Mask           0x3
        Link Type           AMC.4 Serial RapidIO (0x6)
        Link Type Ext.      3.125 Gbaud transmission rate (2.5 Gbps) (0x2)
        Group ID            0
        Asymmetric Match    0

AMC Link Descriptor #8
        Channel ID          1
        Lane Mask           0x3
        Link Type           AMC.4 Serial RapidIO (0x6)
        Link Type Ext.      2.5 Gbaud transmission rate (2.0 Gbps) (0x1)
        Group ID            0
        Asymmetric Match    0

AMC Link Descriptor #9
        Channel ID          1
        Lane Mask           0x3
        Link Type           AMC.4 Serial RapidIO (0x6)
        Link Type Ext.      1.25 Gbaud transmission rate (1.0 Gbps) (0x0)
        Group ID            0
        Asymmetric Match    0

AMC Link Descriptor #10
        Channel ID          1
        Lane Mask           0xc
        Link Type           AMC.4 Serial RapidIO (0x6)
        Link Type Ext.      No Extension Specified (0x3)
        Group ID            0
        Asymmetric Match    0

AMC Link Descriptor #11
        Channel ID          1
        Lane Mask           0xc
        Link Type           AMC.4 Serial RapidIO (0x6)
        Link Type Ext.      3.125 Gbaud transmission rate (2.5 Gbps) (0x2)
        Group ID            0
        Asymmetric Match    0

AMC Link Descriptor #12
        Channel ID          1
        Lane Mask           0xc
        Link Type           AMC.4 Serial RapidIO (0x6)
        Link Type Ext.      2.5 Gbaud transmission rate (2.0 Gbps) (0x1)
        Group ID            0
        Asymmetric Match    0

AMC Link Descriptor #13
        Channel ID          1
        Lane Mask           0xc
        Link Type           AMC.4 Serial RapidIO (0x6)
        Link Type Ext.      1.25 Gbaud transmission rate (1.0 Gbps) (0x0)
        Group ID            0
        Asymmetric Match    0

AMC Link Descriptor #14
        Channel ID          1
        Lane Mask           0x1
        Link Type           AMC.4 Serial RapidIO (0x6)
        Link Type Ext.      No Extension Specified (0x3)
        Group ID            0
        Asymmetric Match    0

AMC Link Descriptor #15
        Channel ID          1
        Lane Mask           0x1
        Link Type           AMC.4 Serial RapidIO (0x6)
        Link Type Ext.      3.125 Gbaud transmission rate (2.5 Gbps) (0x2)
        Group ID            0
        Asymmetric Match    0

AMC Link Descriptor #16
        Channel ID          1
        Lane Mask           0x1
        Link Type           AMC.4 Serial RapidIO (0x6)
        Link Type Ext.      2.5 Gbaud transmission rate (2.0 Gbps) (0x1)
        Group ID            0
        Asymmetric Match    0

AMC Link Descriptor #17
        Channel ID          1
        Lane Mask           0x1
        Link Type           AMC.4 Serial RapidIO (0x6)
        Link Type Ext.      1.25 Gbaud transmission rate (1.0 Gbps) (0x0)
        Group ID            0
        Asymmetric Match    0

AMC Link Descriptor #18
        Channel ID          1
        Lane Mask           0x2
        Link Type           AMC.4 Serial RapidIO (0x6)
        Link Type Ext.      No Extension Specified (0x3)
        Group ID            0
        Asymmetric Match    0

AMC Link Descriptor #19
        Channel ID          1
        Lane Mask           0x2
        Link Type           AMC.4 Serial RapidIO (0x6)
        Link Type Ext.      3.125 Gbaud transmission rate (2.5 Gbps) (0x2)
        Group ID            0
        Asymmetric Match    0

AMC Link Descriptor #20
        Channel ID          1
        Lane Mask           0x2
        Link Type           AMC.4 Serial RapidIO (0x6)
        Link Type Ext.      2.5 Gbaud transmission rate (2.0 Gbps) (0x1)
        Group ID            0
        Asymmetric Match    0

AMC Link Descriptor #21
        Channel ID          1
        Lane Mask           0x2
        Link Type           AMC.4 Serial RapidIO (0x6)
        Link Type Ext.      1.25 Gbaud transmission rate (1.0 Gbps) (0x0)
        Group ID            0
        Asymmetric Match    0

AMC Link Descriptor #22
        Channel ID          1
        Lane Mask           0x4
        Link Type           AMC.4 Serial RapidIO (0x6)
        Link Type Ext.      No Extension Specified (0x3)
        Group ID            0
        Asymmetric Match    0

AMC Link Descriptor #23
        Channel ID          1
        Lane Mask           0x4
        Link Type           AMC.4 Serial RapidIO (0x6)
        Link Type Ext.      3.125 Gbaud transmission rate (2.5 Gbps) (0x2)
        Group ID            0
        Asymmetric Match    0

AMC Link Descriptor #24
        Channel ID          1
        Lane Mask           0x4
        Link Type           AMC.4 Serial RapidIO (0x6)
        Link Type Ext.      2.5 Gbaud transmission rate (2.0 Gbps) (0x1)
        Group ID            0
        Asymmetric Match    0

AMC Link Descriptor #25
        Channel ID          1
        Lane Mask           0x4
        Link Type           AMC.4 Serial RapidIO (0x6)
        Link Type Ext.      1.25 Gbaud transmission rate (1.0 Gbps) (0x0)
        Group ID            0
        Asymmetric Match    0

AMC Link Descriptor #26
        Channel ID          1
        Lane Mask           0x8
        Link Type           AMC.4 Serial RapidIO (0x6)
        Link Type Ext.      No Extension Specified (0x3)
        Group ID            0
        Asymmetric Match    0

AMC Link Descriptor #27
        Channel ID          1
        Lane Mask           0x8
        Link Type           AMC.4 Serial RapidIO (0x6)
        Link Type Ext.      3.125 Gbaud transmission rate (2.5 Gbps) (0x2)
        Group ID            0
        Asymmetric Match    0

AMC Link Descriptor #28
        Channel ID          1
        Lane Mask           0x8
        Link Type           AMC.4 Serial RapidIO (0x6)
        Link Type Ext.      2.5 Gbaud transmission rate (2.0 Gbps) (0x1)
        Group ID            0
        Asymmetric Match    0

AMC Link Descriptor #29
        Channel ID          1
        Lane Mask           0x8
        Link Type           AMC.4 Serial RapidIO (0x6)
        Link Type Ext.      1.25 Gbaud transmission rate (1.0 Gbps) (0x0)
        Group ID            0
        Asymmetric Match    0

AMC Link Descriptor #30
        Channel ID          2
        Lane Mask           0x3
        Link Type           AMC.1 PCI Express (0x2)
        Link Type Ext.      Gen 2-capable (0x2)
        Group ID            0
        Asymmetric Match    1

AMC Link Descriptor #31
        Channel ID          2
        Lane Mask           0x3
        Link Type           AMC.1 PCI Express (0x2)
        Link Type Ext.      Gen 1-capable (0x0)
        Group ID            0
        Asymmetric Match    1

AMC Link Descriptor #32
        Channel ID          2
        Lane Mask           0x1
        Link Type           AMC.1 PCI Express (0x2)
        Link Type Ext.      Gen 2-capable (0x2)
        Group ID            0
        Asymmetric Match    1

AMC Link Descriptor #33
        Channel ID          2
        Lane Mask           0x1
        Link Type           AMC.1 PCI Express (0x2)
        Link Type Ext.      Gen 1-capable (0x0)
        Group ID            0
        Asymmetric Match    1

Manufacturer ID : 012634
Version         : 02
Type            : OEM Record (0xc0)
PICMG Record    : Module Current Requirements Record (0x16)

Current Draw (tenths of Amps) : 30

Manufacturer ID : 012634
Version         : 02
Type            : OEM Record (0xc0)
PICMG Record    : (0x0)

It looks to me that all combinations of SRIO lanes are enabled as well as the PCIe (which we are not using).

Like I said, the two hints I have that things are going well are the "FRU Unknown" and the GUID = 0x1bad1bad...

There is a command to show srio connectivity and when my EVMs get power (which isn't very consistently), I can load the srio chiptochip example and see that I am making a link with the switch.

As for the power up issue, it looks like the PM tries repeatedly to bring it up and then eventually the chassis shows a minor fault and then it quits trying. Sometimes if I put the chassis into hot swap mode and then bring it back, the PM will retry to bring up the EVM and be successful. Sometimes I can reboot the MCH and sometimes I just have to power down the chassis. The attached logs are what I gave vadatech when I told them about this.

logs

Fullscreen 2526.MCState_mmc.log Download

*******************************************************************************
Copyright (C) 2004-2009 by VadaTech Inc., all rights reserved. 

Application   : mcCtrlMCMC
Start Time    : Wed Feb 15 07:05:15 2012
Log Max Size  : 512K bytes
*******************************************************************************
[Wed Feb 15 07:05:15 2012]     INFO: IPMB Bus 0 link-00, rbus 0 (enabled)
[Wed Feb 15 07:05:15 2012]     INFO: IPMB Bus 0 link-00, rbus 1 (enabled)
[Wed Feb 15 07:05:15 2012]     INFO: Sensor Data Repository (SDR)
[Wed Feb 15 07:05:15 2012]     INFO:     Version                 : 2.3
[Wed Feb 15 07:05:15 2012]     INFO:     Size                    : 6 KBytes
[Wed Feb 15 07:05:15 2012]     INFO:     Delete support          : no
[Wed Feb 15 07:05:15 2012]     INFO:     Partial add support     : no
[Wed Feb 15 07:05:15 2012]     INFO:     Reserve support         : yes
[Wed Feb 15 07:05:15 2012]     INFO:     Allocation info support : yes
[Wed Feb 15 07:05:15 2012]     INFO:     Max records             : 86
[Wed Feb 15 07:05:15 2012]     INFO:     Logical storage         : /opt/vadatech/IPMI/MCMC/repository/sdr
[Wed Feb 15 07:05:15 2012]     INFO: FRU 00, IPMB Addr (0x12, FRU 00) at channel 00
[Wed Feb 15 07:05:15 2012]     INFO: Initializing physical FRU storage (RDONLY) entity at busId 4 addr 0x53 offset 0
[Wed Feb 15 07:05:15 2012]     INFO: FRU 00 storage at addr 0x53 is INACTIVE.
[Wed Feb 15 07:05:15 2012]     INFO: FRU 00 storage at addr 0x53, FRU 0 is at ACTIVE state.
[Wed Feb 15 07:05:15 2012]     INFO: FRU 00 storage cache updated from EEPROM at 0x53, offset 0 size 0x243.
[Wed Feb 15 07:05:15 2012]     INFO: Board Information
[Wed Feb 15 07:05:15 2012]     INFO:     Manufacturer  : VadaTech
[Wed Feb 15 07:05:15 2012]     INFO:     Product Name  : MCMC GbE
[Wed Feb 15 07:05:15 2012]     INFO:     Serial Number : 1210252
[Wed Feb 15 07:05:15 2012]     INFO:     Part Number   : UTC002MCMC
[Wed Feb 15 07:05:15 2012]     INFO:     FRU File ID   : Null
[Wed Feb 15 07:05:15 2012]     INFO: FRU 00 Entity(0xc2, 0x62) inventory storage initialized.
[Wed Feb 15 07:05:15 2012]     INFO: FRU 01, Slave Addr 0x12, Entity (0xf2, 0x62)
[Wed Feb 15 07:05:15 2012]     INFO: FRU 02, Slave Addr 0x12, Entity (0xe1, 0x62)
[Wed Feb 15 07:05:15 2012]     INFO: Initializing physical FRU storage (RDWR) entity at busId 4 addr 0x52 offset 0
[Wed Feb 15 07:05:15 2012]     INFO: FRU 02 storage at addr 0x52 is INACTIVE.
[Wed Feb 15 07:05:15 2012]     INFO: FRU 02 storage at addr 0x52, FRU 2 is at ACTIVE state.
[Wed Feb 15 07:05:16 2012]     INFO: FRU 02 storage cache updated from EEPROM at 0x52, offset 0 size 0x403.
[Wed Feb 15 07:05:16 2012]     INFO: Board Information
[Wed Feb 15 07:05:16 2012]     INFO:     Manufacturer  : VadaTech
[Wed Feb 15 07:05:16 2012]     INFO:     Product Name  : Carrier-x12
[Wed Feb 15 07:05:16 2012]     INFO:     Serial Number : 4390010
[Wed Feb 15 07:05:16 2012]     INFO:     Part Number   : VT862
[Wed Feb 15 07:05:16 2012]     INFO:     FRU File ID   : x12
[Wed Feb 15 07:05:16 2012]     INFO: FRU 02 Entity (0xe1, 0x62) inventory storage initialized.
[Wed Feb 15 07:05:16 2012]     INFO: FRU 03, Slave Addr 0x12, Entity (0x0b, 0x62)
[Wed Feb 15 07:05:16 2012]     INFO: Initializing physical FRU storage (RDWR) entity at busId 4 addr 0x50 offset 0
[Wed Feb 15 07:05:16 2012]     INFO: FRU 03 storage at addr 0x50 is INACTIVE.
[Wed Feb 15 07:05:16 2012]     INFO: FRU 03 storage at addr 0x50, FRU 3 is at ACTIVE state.
[Wed Feb 15 07:05:16 2012]     INFO: FRU 03 storage cache updated from EEPROM at 0x50, offset 0 size 0x45d.
[Wed Feb 15 07:05:16 2012]     INFO: Board Information
[Wed Feb 15 07:05:16 2012]     INFO:     Manufacturer  : VadaTech
[Wed Feb 15 07:05:16 2012]     INFO:     Product Name  : UTC002
[Wed Feb 15 07:05:16 2012]     INFO:     Serial Number : 1410002
[Wed Feb 15 07:05:16 2012]     INFO:     Part Number   : DA118.A
[Wed Feb 15 07:05:16 2012]     INFO:     FRU File ID   : RevA-SRIO
[Wed Feb 15 07:05:16 2012]     INFO: FRU 03 Entity (0x0b, 0x62) inventory storage initialized.
[Wed Feb 15 07:05:16 2012]     INFO: FRU 02 storage, partition 1.
[Wed Feb 15 07:05:16 2012]     INFO: Initializing physical FRU storage (RDWR) entity at busId 4 addr 0x52 offset 2048
[Wed Feb 15 07:05:16 2012]     INFO: FRU 01 storage at addr 0x52 is INACTIVE.
[Wed Feb 15 07:05:16 2012]     INFO: FRU 01 storage at addr 0x52, FRU 1 is at ACTIVE state.
[Wed Feb 15 07:05:16 2012]     INFO: FRU 01 storage cache updated from EEPROM at 0x52, offset 2048 size 0x24b.
[Wed Feb 15 07:05:16 2012]     INFO: Board Information
[Wed Feb 15 07:05:16 2012]     INFO:     Manufacturer  : VadaTech
[Wed Feb 15 07:05:16 2012]     INFO:     Product Name  : UTCA Shelf
[Wed Feb 15 07:05:16 2012]     INFO:     Serial Number : 4390010
[Wed Feb 15 07:05:16 2012]     INFO:     Part Number   : VTSH INFO
[Wed Feb 15 07:05:16 2012]     INFO:     FRU File ID   : Null
[Wed Feb 15 07:05:16 2012]     INFO: FRU 01 Entity(0xf2, 0x62) inventory storage initialized.
[Wed Feb 15 07:05:16 2012]     INFO: FRU 01 storage, partition 2.
[Wed Feb 15 07:05:16 2012]     INFO: Management Controller IPMB0 slave address is 0x12
[Wed Feb 15 07:05:16 2012]     INFO: Start Management controller.
[Wed Feb 15 07:05:16 2012]     INFO: Application heartbeat override is currently disabled.
[Wed Feb 15 07:05:16 2012]     INFO: Application heartbeat interval is currently set to 60 seconds.
[Wed Feb 15 07:05:16 2012]     INFO: Application retgistered with Heartbeat monitor
[Wed Feb 15 07:05:16 2012]     INFO: Initialized 4 LEDs
[Wed Feb 15 07:05:16 2012]     INFO: Init sensor 0x70, type 0x01 (enabled).
[Wed Feb 15 07:05:16 2012]     INFO: Init sensor 0x71, type 0x01 (enabled).
[Wed Feb 15 07:05:16 2012]     INFO: Init sensor 0x72, type 0x01 (enabled).
[Wed Feb 15 07:05:16 2012]     INFO: Init sensor 0x74, type 0x01 (enabled).
[Wed Feb 15 07:05:16 2012]     INFO: Init sensor 0x75, type 0x01 (enabled).
[Wed Feb 15 07:05:16 2012]     INFO: Init sensor 0x6a, type 0xca (enabled).
[Wed Feb 15 07:05:16 2012]     INFO: Init sensor 0x6b, type 0xf2 (enabled).
[Wed Feb 15 07:05:16 2012]     INFO: Init sensor 0x6c, type 0xf1 (enabled).
[Wed Feb 15 07:05:16 2012]     INFO: Init sensor 0x6d, type 0xcc (enabled).
[Wed Feb 15 07:05:16 2012]     INFO: Init sensor 0x6e, type 0xcc (enabled).
[Wed Feb 15 07:05:16 2012]     INFO: Init sensor 0x73, type 0x17 (enabled).
[Wed Feb 15 07:05:16 2012]     INFO: Init sensor 0x76, type 0xd6 (enabled).
[Wed Feb 15 07:05:16 2012]     INFO: Init sensor 0x80, type 0xc2 (enabled).
[Wed Feb 15 07:05:16 2012]     INFO: Init sensor 0x81, type 0xc2 (enabled).
[Wed Feb 15 07:05:16 2012]     INFO: Init sensor 0x82, type 0xc2 (enabled).
[Wed Feb 15 07:05:16 2012]     INFO: Init sensor 0x83, type 0xd6 (enabled).
[Wed Feb 15 07:05:16 2012]     INFO: IPMI Message timeout 1000 ms, max retries 8.
[Wed Feb 15 07:05:16 2012]     INFO: FRU 00 at POWER_ONOFF(M1A) state.
[Wed Feb 15 07:05:16 2012]     INFO: FRU 00 Event receiver enabled
[Wed Feb 15 07:05:16 2012]     INFO:     Destination: Channel 0, address (0x20, LUN 0)
[Wed Feb 15 07:05:16 2012]     INFO: MCH Daughter card detected. Merging Ekeying records.
[Wed Feb 15 07:05:16 2012]     INFO: DA FRU information Version(1.0.0).
[Wed Feb 15 07:05:16 2012]     INFO: Generating Clock E-Keying records
[Wed Feb 15 07:05:16 2012]     INFO: No clock info for target 4
[Wed Feb 15 07:05:16 2012]     INFO: No clock info for target 5
[Wed Feb 15 07:05:16 2012]     INFO: No clock info for target 6
[Wed Feb 15 07:05:16 2012]     INFO: No clock info for target 10
[Wed Feb 15 07:05:16 2012]     INFO: FRU 00 at INACTIVE (M1B) state.
[Wed Feb 15 07:05:16 2012]     INFO: Management controller is initialized.
[Wed Feb 15 07:05:18 2012]     INFO: FRU 00 at ACTIVATION_REQUEST (M2) state.
[Wed Feb 15 07:05:18 2012]     INFO: FRU 00 at ACTIVATION_IN_PROGRESS (M3A) state.
[Wed Feb 15 07:05:18 2012]     INFO: FRU 00 at ENABLE_RESOURCES (M3B) state.
[Wed Feb 15 07:05:18 2012]     INFO: FRU 00 at ACTIVE (M4) state.
[Wed Feb 15 07:15:05 2012]     INFO: Registered remote eth0 (IP 192.168.1.252)
[Wed Feb 15 07:15:05 2012]     INFO: Registered remote eth1 (IP 192.168.40.249)
[Wed Feb 15 07:25:16 2012]     INFO: -- MARK --

a84591e31034fac832d29ed8584666c967216836_code-editor-fs">Fullscreen 2e.ti.com/cfs-filesystemfile/__key/communityserver-discussions-components-files/639/6170.MCState_5F00_shelf.log?_=634650860160000000" 6170.MCState_shelf.log">6170.MCState_shelf.log 2e.ti.com/cfs-filesystemfile/__key/communityserver-discussions-components-files/639/6170.MCState_5F00_shelf.log?_=634650860160000000" 6170.MCState_shelf.log">Download 91e31034fac832d29ed8584666c967216836_code-editor" x;min-width:320px;margin:0px;" >******************************************************************************* by VadaTech Inc., all rights reserved. Feb 15 07:05:17 2012 ***************************************************** INFO: NEBS Compliancy is enabled. INFO: Sensor Data Repository (SDR) INFO: Version : 2.3 INFO: Size : 225 KBytes INFO: Delete support : no INFO: Partial add support : no INFO: Reserve support : yes INFO: Allocation info support : yes INFO: Max records : 3198 INFO: Logical storage : /opt/vadatech/IPMI/UTCShelf/repository/sdr INFO: FRU 00, IPMB Addr (0x20, FRU 00) at channel 00 INFO: Initialized FRU 00 Entity (0xf0, 0x01) inventory storage. INFO: FRU 254, (IPMB Addr 0x20, FRU 254) at channel 00 INFO: Remote FRU Storage Entity (0xf2, 0x61) at (IPMB Addr 0x82, FRU 01). INFO: Remote FRU Storage Entity (0xf2, 0x61) at (IPMB Addr 0x82, FRU 02). INFO: Remote FRU Storage Entity (0xf2, 0x62) at (IPMB Addr 0x84, FRU 01). INFO: Remote FRU Storage Entity (0xf2, 0x62) at (IPMB Addr 0x84, FRU 02). INFO: Remote FRU Storage Entity (0xf2, 0x63) at (IPMB Addr 0x86, FRU 01). INFO: Remote FRU Storage Entity (0xf2, 0x63) at (IPMB Addr 0x86, FRU 02). INFO: Remote FRU Storage Entity (0xf2, 0x64) at (IPMB Addr 0x88, FRU 01). INFO: Remote FRU Storage Entity (0xf2, 0x64) at (IPMB Addr 0x88, FRU 02). INFO: Remote FRU Storage Entity (0xf2, 0x65) at (IPMB Addr 0x8a, FRU 01). INFO: Remote FRU Storage Entity (0xf2, 0x65) at (IPMB Addr 0x8a, FRU 02). INFO: Remote FRU Storage Entity (0xf2, 0x66) at (IPMB Addr 0x8c, FRU 01). INFO: Remote FRU Storage Entity (0xf2, 0x66) at (IPMB Addr 0x8c, FRU 02). INFO: Remote FRU Storage Entity (0xf2, 0x67) at (IPMB Addr 0x8e, FRU 01). INFO: Remote FRU Storage Entity (0xf2, 0x67) at (IPMB Addr 0x8e, FRU 02). INFO: Remote FRU Storage Entity (0xf2, 0x68) at (IPMB Addr 0x90, FRU 01). INFO: Remote FRU Storage Entity (0xf2, 0x68) at (IPMB Addr 0x90, FRU 02). INFO: Remote FRU Storage Entity (0xf2, 0x69) at (IPMB Addr 0x92, FRU 01). INFO: Remote FRU Storage Entity (0xf2, 0x69) at (IPMB Addr 0x92, FRU 02). INFO: Remote FRU Storage Entity (0xf2, 0x6a) at (IPMB Addr 0x94, FRU 01). INFO: Remote FRU Storage Entity (0xf2, 0x6a) at (IPMB Addr 0x94, FRU 02). INFO: Remote FRU Storage Entity (0xf2, 0x6b) at (IPMB Addr 0x96, FRU 01). INFO: Remote FRU Storage Entity (0xf2, 0x6b) at (IPMB Addr 0x96, FRU 02). INFO: Remote FRU Storage Entity (0xf2, 0x6c) at (IPMB Addr 0x98, FRU 01). INFO: Remote FRU Storage Entity (0xf2, 0x6c) at (IPMB Addr 0x98, FRU 02). INFO: Remote FRU Storage Entity (0xf2, 0x6d) at (IPMB Addr 0x9a, FRU 01). INFO: Remote FRU Storage Entity (0xf2, 0x6d) at (IPMB Addr 0x9a, FRU 02). INFO: Remote FRU Storage Entity (0xf2, 0x6e) at (IPMB Addr 0x9c, FRU 01). INFO: Remote FRU Storage Entity (0xf2, 0x6e) at (IPMB Addr 0x9c, FRU 02). INFO: Remote FRU Storage Entity (0xf2, 0x6f) at (IPMB Addr 0x9e, FRU 01). INFO: Remote FRU Storage Entity (0xf2, 0x6f) at (IPMB Addr 0x9e, FRU 02). INFO: Remote FRU Storage Entity (0xf2, 0x70) at (IPMB Addr 0xa0, FRU 01). INFO: Remote FRU Storage Entity (0xf2, 0x70) at (IPMB Addr 0xa0, FRU 02). INFO: FRU 254 Entity(0xf2, 0x60) inventory storage initialized. INFO: FRU 01, IPMB Addr (0x82, FRU 00) at channel 16 INFO: FRU 02, IPMB Addr (0x84, FRU 00) at channel 16 INFO: FRU 03, IPMB Addr (0x86, FRU 00) at channel 16 INFO: FRU 04, IPMB Addr (0x88, FRU 00) at channel 16 INFO: FRU 05, IPMB Addr (0x8a, FRU 00) at channel 16 INFO: FRU 06, IPMB Addr (0x8c, FRU 00) at channel 16 INFO: FRU 07, IPMB Addr (0x8e, FRU 00) at channel 16 INFO: FRU 08, IPMB Addr (0x90, FRU 00) at channel 16 INFO: FRU 09, IPMB Addr (0x92, FRU 00) at channel 16 INFO: FRU 10, IPMB Addr (0x94, FRU 00) at channel 16 INFO: FRU 11, IPMB Addr (0x96, FRU 00) at channel 16 INFO: FRU 12, IPMB Addr (0x98, FRU 00) at channel 16 INFO: FRU 13, IPMB Addr (0x9a, FRU 00) at channel 16 INFO: FRU 14, IPMB Addr (0x9c, FRU 00) at channel 16 INFO: FRU 15, IPMB Addr (0x9e, FRU 00) at channel 16 INFO: FRU 16, IPMB Addr (0xa0, FRU 00) at channel 16 INFO: Management Controller IPMB0 slave address is 0x20 INFO: Start Management controller. INFO: Application heartbeat override is currently disabled. INFO: Application heartbeat interval is currently set to 60 seconds. INFO: Application retgistered with Heartbeat monitor INFO: Initialized 4 LEDs INFO: SEL storage at addr(0x50, bus 1, offset 0, size 32768) INFO: System Event Log (SEL) INFO: Version : 2.3 INFO: Size : 32 KBytes INFO: Delete support : no INFO: Partial add support : no INFO: Reserve support : yes INFO: Allocation info support : yes INFO: Max records : 2045 INFO: Physical Address : 0x50 INFO: Offset : 0 INFO: Bus ID : 1 INFO: SEL used space 32640 KBytes with 2040 entries INFO: Init sensor 0x69, type 0xf0 (enabled). INFO: FRU 17, (IPMB Addr 0x82, FRU 79) at channel 16 INFO: FRU 18, (IPMB Addr 0x84, FRU 79) at channel 16 INFO: FRU 19, (IPMB Addr 0x86, FRU 79) at channel 16 INFO: FRU 20, (IPMB Addr 0x88, FRU 79) at channel 16 INFO: FRU 21, (IPMB Addr 0x8a, FRU 79) at channel 16 INFO: FRU 22, (IPMB Addr 0x8c, FRU 79) at channel 16 INFO: FRU 23, (IPMB Addr 0x8e, FRU 79) at channel 16 INFO: FRU 24, (IPMB Addr 0x90, FRU 79) at channel 16 INFO: FRU 25, (IPMB Addr 0x92, FRU 79) at channel 16 INFO: FRU 26, (IPMB Addr 0x94, FRU 79) at channel 16 INFO: FRU 27, (IPMB Addr 0x96, FRU 79) at channel 16 INFO: FRU 28, (IPMB Addr 0x98, FRU 79) at channel 16 INFO: FRU 29, (IPMB Addr 0x9a, FRU 79) at channel 16 INFO: FRU 30, (IPMB Addr 0x9c, FRU 79) at channel 16 INFO: FRU 31, (IPMB Addr 0x9e, FRU 79) at channel 16 INFO: FRU 32, (IPMB Addr 0xa0, FRU 79) at channel 16 INFO: IPMI Message timeout 300 ms, max retries 4. INFO: Local host conn chan(13) (127.0.0.1 port 623) INFO: MGT IP Connection Links: INFO: IP Connection Address 1 : 192.168.16.17 INFO: Subnet Mask 1 : 255.255.255.0 INFO: Gateway Address 1 : 192.168.1.1 INFO: MGT IP conn chan(02) eth0:8(192.168.16.17 port 623) INFO: Cooling is disabled, Shelf fan geography is not configured. INFO: FRU 00 at POWER_ONOFF(M1A) state. INFO: FRU 00 at INACTIVE (M1B) state. INFO: FRU 00 at ACTIVATION_REQUEST (M2) state. INFO: FRU 00 Event receiver enabled INFO: Destination: Channel 0, address (0x20, LUN 0) INFO: FRU 00 at ACTIVATION_IN_PROGRESS (M3A) state. INFO: Management controller is initialized. INFO: FRU 00 at ENABLE_RESOURCES (M3B) state. INFO: FRU 00 at ACTIVE (M4) state. INFO: SDR Merge timer expired. Starting periodic SDR repository monitor. INFO: MGT Failover conn chan(12) eth0(192.168.1.252 port 623) INFO: MGT Failover conn chan(02) eth0:8(192.168.16.17 port 623) INFO: MGT Failover conn chan(11) eth1(192.168.40.250 port 623) INFO: MGT Failover conn chan(10) eth0:1(192.168.16.1 port 623) INFO: FRU 254 storage at addr 0x82, FRU 1 is at ACTIVE state. INFO: Board Information INFO: Manufacturer : VadaTech INFO: Product Name : UTCA Shelf INFO: Serial Number : 4390010 INFO: Part Number : VTSH INFO INFO: FRU File ID : Null INFO: FRU 254 storage cache was updated from remote addr at 0x82, FRU 1. INFO: MicroTCA Shelf Information was updated from Carrier at 0x82. INFO: FRU 254 storage at addr 0x82, FRU 2 is at ACTIVE state. INFO: Board Information INFO: Manufacturer : VadaTech INFO: Product Name : UTCA Shelf INFO: Serial Number : 4390010 INFO: Part Number : VTSH INFO INFO: FRU File ID : Null INFO: FRU 254 storage cache was updated from remote addr at 0x82, FRU 2. INFO: MicroTCA Shelf Information was updated from Carrier at 0x82. INFO: Carrier Location Entries INFO: Carrier ID 01, Slot/Tier(0, 0) IPMB Addr 0x82 INFO: Carrier ID 02, Slot/Tier(0, 0) IPMB Addr 0x84 INFO: Carrier ID 03, Slot/Tier(0, 0) IPMB Addr 0x86 INFO: Carrier ID 04, Slot/Tier(0, 0) IPMB Addr 0x88 INFO: Carrier ID 05, Slot/Tier(0, 0) IPMB Addr 0x8a INFO: Carrier ID 06, Slot/Tier(0, 0) IPMB Addr 0x8c INFO: Carrier ID 07, Slot/Tier(0, 0) IPMB Addr 0x8e INFO: Carrier ID 08, Slot/Tier(0, 0) IPMB Addr 0x90 INFO: Carrier ID 09, Slot/Tier(0, 0) IPMB Addr 0x92 INFO: Carrier ID 10, Slot/Tier(0, 0) IPMB Addr 0x94 INFO: Carrier ID 11, Slot/Tier(0, 0) IPMB Addr 0x96 INFO: Carrier ID 12, Slot/Tier(0, 0) IPMB Addr 0x98 INFO: Carrier ID 13, Slot/Tier(0, 0) IPMB Addr 0x9a INFO: Carrier ID 14, Slot/Tier(0, 0) IPMB Addr 0x9c INFO: Carrier ID 15, Slot/Tier(0, 0) IPMB Addr 0x9e INFO: Carrier ID 16, Slot/Tier(0, 0) IPMB Addr 0xa0 INFO: Shelf Cooling Geography INFO: CU Carrier Number : 01 INFO: CU FRU ID : 40 INFO: CU Cooled FRUs : INFO: Carrier 0x82 : 03 04 05 06 07 08 09 10 11 12 13 14 15 16 50 51 INFO: CU Carrier Number : 01 INFO: CU FRU ID : 41 INFO: CU Cooled FRUs : INFO: Carrier 0x82 : 03 04 05 06 07 08 09 10 11 12 13 14 15 16 50 51 INFO: CU Carrier Number : 02 INFO: CU FRU ID : 40 INFO: CU Cooled FRUs : INFO: Carrier 0x84 : 03 04 05 06 07 08 09 10 11 12 13 14 15 16 50 51 INFO: CU Carrier Number : 02 INFO: CU FRU ID : 41 INFO: CU Cooled FRUs : INFO: Carrier 0x84 : 03 04 05 06 07 08 09 10 11 12 13 14 15 16 50 51 INFO: CU Carrier Number : 03 INFO: CU FRU ID : 40 INFO: CU Cooled FRUs : INFO: Carrier 0x86 : 03 04 05 06 07 08 09 10 11 12 13 14 15 16 50 51 INFO: CU Carrier Number : 03 INFO: CU FRU ID : 41 INFO: CU Cooled FRUs : INFO: Carrier 0x86 : 03 04 05 06 07 08 09 10 11 12 13 14 15 16 50 51 INFO: CU Carrier Number : 04 INFO: CU FRU ID : 40 INFO: CU Cooled FRUs : INFO: Carrier 0x88 : 03 04 05 06 07 08 09 10 11 12 13 14 15 16 50 51 INFO: CU Carrier Number : 04 INFO: CU FRU ID : 41 INFO: CU Cooled FRUs : INFO: Carrier 0x88 : 03 04 05 06 07 08 09 10 11 12 13 14 15 16 50 51 INFO: CU Carrier Number : 05 INFO: CU FRU ID : 40 INFO: CU Cooled FRUs : INFO: Carrier 0x8a : 03 04 05 06 07 08 09 10 11 12 13 14 15 16 50 51 INFO: CU Carrier Number : 05 INFO: CU FRU ID : 41 INFO: CU Cooled FRUs : INFO: Carrier 0x8a : 03 04 05 06 07 08 09 10 11 12 13 14 15 16 50 51 INFO: Total Number of Cooling Regions : 05 INFO: Cooling Management Parameters INFO: Readiness Allowance : 60 secs INFO: Monitor Cycle : 20 secs INFO: Normal Level : 60% (max level) INFO: Increment Level : 05% (max level) INFO: Decrement Level : 03% (max level) INFO: Policy Override : disabled INFO: Cooling Enabled : enabled INFO: Shelf IP Connection Links: INFO: Shelf IP Connection Address 0 : 0.0.0.0 INFO: Subnet Mask 0 : 0.0.0.0 INFO: Gateway Address 0 : 0.0.0.0 INFO: Shelf IP Connection Address 1 : 0.0.0.0 INFO: Subnet Mask 1 : 0.0.0.0 INFO: Gateway Address 1 : 0.0.0.0 INFO: MGT IP Connection Links: INFO: IP Connection Address 1 : 192.168.16.17 INFO: Subnet Mask 1 : 255.255.255.0 INFO: Gateway Address 1 : 192.168.1.1 INFO: MicroTCA Shelf Manager has been configured. INFO: FRU 01 Addr (0x82) MicroTCA Carrier "VT UTCA CARRIER" INFO: FRU 01 at ACTIVE (M4) state. INFO: FRU 33, (IPMB Addr 0x82, FRU 01) at channel 02 INFO: FRU 33 (IPMB Addr 0x82, FRU 01) "SH FRU DEV1" INFO: FRU 33 Entity(0xf2, 0x61) INFO: FRU 33 at ACTIVE (M4) state. INFO: FRU 34, (IPMB Addr 0x82, FRU 02) at channel 02 INFO: FRU 34 (IPMB Addr 0x82, FRU 02) "SH FRU DEV2" INFO: FRU 34 Entity(0xf2, 0x62) INFO: FRU 34 at ACTIVE (M4) state. INFO: FRU 35, (IPMB Addr 0x82, FRU 03) at channel 02 INFO: FRU 35 (IPMB Addr 0x82, FRU 03) "VT UTCA MCMC" INFO: FRU 35 Entity(0xc2, 0x61) INFO: FRU 35 at ACTIVE (M4) state. INFO: FRU 36, (IPMB Addr 0x82, FRU 04) at channel 02 INFO: FRU 36 (IPMB Addr 0x82, FRU 04) "VT UTCA MCMC" INFO: FRU 36 Entity(0xc2, 0x62) INFO: FRU 36 at ACTIVE (M4) state. INFO: FRU 37, (IPMB Addr 0x82, FRU 10) at channel 02 INFO: FRU 37 (IPMB Addr 0x82, FRU 10) "VT AMC719" INFO: FRU 37 Entity(0xc1, 0x66) INFO: FRU 37 at ACTIVE (M4) state. INFO: FRU 38, (IPMB Addr 0x82, FRU 14) at channel 02 INFO: FRU 39, (IPMB Addr 0x82, FRU 40) at channel 02 INFO: FRU 39 (IPMB Addr 0x82, FRU 40) "VT VT095" INFO: FRU 39 Entity(0x1e, 0x61) INFO: FRU 39 at ACTIVE (M4) state. INFO: FRU 40, (IPMB Addr 0x82, FRU 41) at channel 02 INFO: FRU 40 (IPMB Addr 0x82, FRU 41) "VT VT095" INFO: FRU 40 Entity(0x1e, 0x62) INFO: FRU 40 at ACTIVE (M4) state. INFO: FRU 41, (IPMB Addr 0x82, FRU 50) at channel 02 INFO: FRU 41 (IPMB Addr 0x82, FRU 50) "VT UTC010" INFO: FRU 41 Entity(0x0a, 0x61) INFO: FRU 41 at ACTIVE (M4) state. INFO: FRU 17 (IPMB Addr 0x82, FRU 79) "TELCO ALARM" INFO: FRU 17 Entity(0xf3, 0x60) INFO: Telco device discovered on Carrier at 0x82. INFO: FRU(0x82, 79) Telco Capabilities INFO: Critical Alarm Ctrl : yes INFO: Major Alarm Ctrl : yes INFO: Minor Alarm Ctrl : yes INFO: Power Alarm Ctrl : no INFO: Test Mode Enable : yes INFO: Alarm Cutoff Action : yes INFO: Minor Reset : yes INFO: Major Reset : yes INFO: FRU 17 at ACTIVE (M4) state. WARNING: FRU 38 at COMMUNICATION_LOST (M7) state. INFO: FRU 38 at NOT_INSTALLED (M0) state. WARNING: FRU 38 at COMMUNICATION_LOST (M7) state. INFO: Fan Tray at FRU(0x82, 40) Levels Min 5, Max 63, Norm 37 INFO: Fan Tray at FRU(0x82, 41) Levels Min 5, Max 63, Norm 37 INFO: FRU 38 at NOT_INSTALLED (M0) state. WARNING: FRU 38 at COMMUNICATION_LOST (M7) state. INFO: FRU 38 at NOT_INSTALLED (M0) state. WARNING: FRU 38 at COMMUNICATION_LOST (M7) state. INFO: FRU 38 at NOT_INSTALLED (M0) state. WARNING: FRU 38 at COMMUNICATION_LOST (M7) state. INFO: FRU 38 at NOT_INSTALLED (M0) state. WARNING: FRU 38 at COMMUNICATION_LOST (M7) state. INFO: FRU 38 at NOT_INSTALLED (M0) state. WARNING: FRU 38 at COMMUNICATION_LOST (M7) state. INFO: FRU 38 at NOT_INSTALLED (M0) state. WARNING: FRU 38 at COMMUNICATION_LOST (M7) state. INFO: FRU 38 at NOT_INSTALLED (M0) state. WARNING: FRU 38 at COMMUNICATION_LOST (M7) state. INFO: FRU 38 at NOT_INSTALLED (M0) state. WARNING: FRU 38 at COMMUNICATION_LOST (M7) state. INFO: FRU 38 at NOT_INSTALLED (M0) state. INFO: FRU 38 at POWER_ONOFF(M1A) state. INFO: FRU 38 at INACTIVE (M1B) state. INFO: FRU 38 at ACTIVATION_REQUEST (M2) state. INFO: FRU 38 at INACTIVE (M1B) state. INFO: FRU 38 at ACTIVATION_REQUEST (M2) state. INFO: FRU 38 at ACTIVATION_IN_PROGRESS (M3A) state. INFO: FRU 38 at ACTIVE (M4) state. INFO: -- MARK -- = j('#fragment-1a84591e31034fac832d29ed8584666c967216836_code-editor-fs'); = j('#fragment-1a84591e31034fac832d29ed8584666c967216836_code-editor'); function(){ lutionCodeEditor('fullscreen')) { lutionCodeEditor('fullscreen', false); lutionCodeEditor('fullscreen', true);

Fullscreen 2211.MCState_utcc.log Download

*******************************************************************************
Copyright (C) 2004-2009 by VadaTech Inc., all rights reserved. 

Application   : mcCtrlUTCC
Start Time    : Wed Feb 15 07:05:16 2012
Log Max Size  : 1024K bytes
*******************************************************************************
[Wed Feb 15 07:05:16 2012]     INFO: NEBS Compliancy is enabled.
[Wed Feb 15 07:05:16 2012]     INFO: IPMB Bus 0 link-00, rbus 0 (enabled)
[Wed Feb 15 07:05:16 2012]     INFO: IPMB Bus 0 link-00, rbus 1 (enabled)
[Wed Feb 15 07:05:16 2012]     INFO: Sensor Data Repository (SDR)
[Wed Feb 15 07:05:16 2012]     INFO:     Version                 : 2.3
[Wed Feb 15 07:05:16 2012]     INFO:     Size                    : 18 KBytes
[Wed Feb 15 07:05:16 2012]     INFO:     Delete support          : no
[Wed Feb 15 07:05:16 2012]     INFO:     Partial add support     : no
[Wed Feb 15 07:05:16 2012]     INFO:     Reserve support         : yes
[Wed Feb 15 07:05:16 2012]     INFO:     Allocation info support : yes
[Wed Feb 15 07:05:16 2012]     INFO:     Max records             : 254
[Wed Feb 15 07:05:16 2012]     INFO:     Logical storage         : /opt/vadatech/IPMI/UTCC/repository/sdr
[Wed Feb 15 07:05:16 2012]     INFO: FRU 00, IPMB Addr (0x20, FRU 00) at channel 00
[Wed Feb 15 07:05:16 2012]     INFO: Initialized FRU 00 Entity (0xc2, 0x01) inventory storage.
[Wed Feb 15 07:05:16 2012]     INFO: FRU 253, (IPMB Addr 0x20, FRU 253) at channel 00
[Wed Feb 15 07:05:16 2012]     INFO: Remote FRU Storage Entity (0xc2, 0x61) at (IPMB Addr 0x10, FRU 02).
[Wed Feb 15 07:05:16 2012]     INFO: Remote FRU Storage Entity (0xc2, 0x62) at (IPMB Addr 0x12, FRU 02).
[Wed Feb 15 07:05:16 2012]     INFO: FRU 253 Entity(0xe1, 0x60) inventory storage initialized.
[Wed Feb 15 07:05:16 2012]     INFO: FRU 01, (IPMB Addr 0x20, FRU 01) at channel 00
[Wed Feb 15 07:05:16 2012]     INFO: Remote FRU Storage Entity (0xf2, 0x61) at (IPMB Addr 0x10, FRU 01).
[Wed Feb 15 07:05:16 2012]     INFO: FRU 01 Entity(0xf2, 0x61) inventory storage initialized.
[Wed Feb 15 07:05:16 2012]     INFO: FRU 02, (IPMB Addr 0x20, FRU 02) at channel 00
[Wed Feb 15 07:05:16 2012]     INFO: Remote FRU Storage Entity (0xf2, 0x62) at (IPMB Addr 0x12, FRU 01).
[Wed Feb 15 07:05:16 2012]     INFO: FRU 02 Entity(0xf2, 0x62) inventory storage initialized.
[Wed Feb 15 07:05:16 2012]     INFO: FRU 50, (IPMB Addr 0xc2, FRU 00) at channel 00
[Wed Feb 15 07:05:16 2012]     INFO: FRU 51, (IPMB Addr 0xc4, FRU 00) at channel 00
[Wed Feb 15 07:05:16 2012]     INFO: FRU 52, (IPMB Addr 0xc6, FRU 00) at channel 00
[Wed Feb 15 07:05:16 2012]     INFO: FRU 53, (IPMB Addr 0xc8, FRU 00) at channel 00
[Wed Feb 15 07:05:16 2012]     INFO: FRU 40, (IPMB Addr 0xa8, FRU 00) at channel 00
[Wed Feb 15 07:05:16 2012]     INFO: FRU 41, (IPMB Addr 0xaa, FRU 00) at channel 00
[Wed Feb 15 07:05:16 2012]     INFO: FRU 03, (IPMB Addr 0x10, FRU 00) at channel 00
[Wed Feb 15 07:05:16 2012]     INFO: FRU 04, (IPMB Addr 0x12, FRU 00) at channel 00
[Wed Feb 15 07:05:16 2012]     INFO: FRU 05, (IPMB Addr 0x72, FRU 00) at channel 07
[Wed Feb 15 07:05:16 2012]     INFO: FRU 06, (IPMB Addr 0x74, FRU 00) at channel 07
[Wed Feb 15 07:05:16 2012]     INFO: FRU 07, (IPMB Addr 0x76, FRU 00) at channel 07
[Wed Feb 15 07:05:16 2012]     INFO: FRU 08, (IPMB Addr 0x78, FRU 00) at channel 07
[Wed Feb 15 07:05:16 2012]     INFO: FRU 09, (IPMB Addr 0x7a, FRU 00) at channel 07
[Wed Feb 15 07:05:16 2012]     INFO: FRU 10, (IPMB Addr 0x7c, FRU 00) at channel 07
[Wed Feb 15 07:05:16 2012]     INFO: FRU 11, (IPMB Addr 0x7e, FRU 00) at channel 07
[Wed Feb 15 07:05:16 2012]     INFO: FRU 12, (IPMB Addr 0x80, FRU 00) at channel 07
[Wed Feb 15 07:05:16 2012]     INFO: FRU 13, (IPMB Addr 0x82, FRU 00) at channel 07
[Wed Feb 15 07:05:16 2012]     INFO: FRU 14, (IPMB Addr 0x84, FRU 00) at channel 07
[Wed Feb 15 07:05:16 2012]     INFO: FRU 15, (IPMB Addr 0x86, FRU 00) at channel 07
[Wed Feb 15 07:05:16 2012]     INFO: FRU 16, (IPMB Addr 0x88, FRU 00) at channel 07
[Wed Feb 15 07:05:16 2012]     INFO: FRU 29, (IPMB Addr 0xa2, FRU 00) at channel 07
[Wed Feb 15 07:05:16 2012]     INFO: FRU 30, (IPMB Addr 0xa4, FRU 00) at channel 07
[Wed Feb 15 07:05:16 2012]     INFO: Ethernet address negotiation enabled
[Wed Feb 15 07:05:16 2012]     INFO:     Failover nodes IPMB Addr(0x10 <-> 0x12).
[Wed Feb 15 07:05:17 2012]     INFO: Radial IPMB Bus 2:
[Wed Feb 15 07:05:17 2012]     INFO:     HW Addr 0x00, [link 1] Device(/dev/pi2c-14 
[Wed Feb 15 07:05:17 2012]     INFO:     HW Addr 0x00, [link 2] Device(/dev/pi2c-16 
[Wed Feb 15 07:05:17 2012]     INFO:     HW Addr 0x00, [link 3] Device(/dev/pi2c-18 
[Wed Feb 15 07:05:17 2012]     INFO:     HW Addr 0x00, [link 4] Device(/dev/pi2c-20 
[Wed Feb 15 07:05:17 2012]     INFO:     HW Addr 0x00, [link 5] Device(/dev/pi2c-22 
[Wed Feb 15 07:05:17 2012]     INFO:     HW Addr 0x00, [link 6] Device(/dev/pi2c-24 
[Wed Feb 15 07:05:17 2012]     INFO:     HW Addr 0x00, [link 7] Device(/dev/pi2c-26 
[Wed Feb 15 07:05:17 2012]     INFO:     HW Addr 0x00, [link 8] Device(/dev/pi2c-28 
[Wed Feb 15 07:05:17 2012]     INFO:     HW Addr 0x00, [link 9] Device(/dev/pi2c-30 
[Wed Feb 15 07:05:17 2012]     INFO:     HW Addr 0x00, [link 10] Device(/dev/pi2c-32 
[Wed Feb 15 07:05:17 2012]     INFO:     HW Addr 0x00, [link 11] Device(/dev/pi2c-34 
[Wed Feb 15 07:05:17 2012]     INFO:     HW Addr 0x00, [link 12] Device(/dev/pi2c-36 
[Wed Feb 15 07:05:17 2012]     INFO: IPMB Bus 2 link-01, rbus 0 (enabled)
[Wed Feb 15 07:05:17 2012]     INFO: IPMB Bus 2 link-02, rbus 0 (enabled)
[Wed Feb 15 07:05:17 2012]     INFO: IPMB Bus 2 link-03, rbus 0 (enabled)
[Wed Feb 15 07:05:17 2012]     INFO: IPMB Bus 2 link-04, rbus 0 (enabled)
[Wed Feb 15 07:05:17 2012]     INFO: IPMB Bus 2 link-05, rbus 0 (enabled)
[Wed Feb 15 07:05:17 2012]     INFO: IPMB Bus 2 link-06, rbus 0 (enabled)
[Wed Feb 15 07:05:17 2012]     INFO: IPMB Bus 2 link-07, rbus 0 (enabled)
[Wed Feb 15 07:05:17 2012]     INFO: IPMB Bus 2 link-08, rbus 0 (enabled)
[Wed Feb 15 07:05:17 2012]     INFO: IPMB Bus 2 link-09, rbus 0 (enabled)
[Wed Feb 15 07:05:17 2012]     INFO: IPMB Bus 2 link-10, rbus 0 (enabled)
[Wed Feb 15 07:05:17 2012]     INFO: IPMB Bus 2 link-11, rbus 0 (enabled)
[Wed Feb 15 07:05:17 2012]     INFO: IPMB Bus 2 link-12, rbus 0 (enabled)
[Wed Feb 15 07:05:17 2012]     INFO: Management Controller IPMB0 slave address is 0x20
[Wed Feb 15 07:05:17 2012]     INFO: Start Management controller.
[Wed Feb 15 07:05:17 2012]     INFO: Application heartbeat override is currently disabled.
[Wed Feb 15 07:05:17 2012]     INFO: Application heartbeat interval is currently set to 60 seconds.
[Wed Feb 15 07:05:17 2012]     INFO: Application retgistered with Heartbeat monitor
[Wed Feb 15 07:05:17 2012]     INFO: Initialized 0 LEDs
[Wed Feb 15 07:05:17 2012]     INFO: SEL logical storage (size 32768)
[Wed Feb 15 07:05:17 2012]     INFO: System Event Log (SEL)
[Wed Feb 15 07:05:17 2012]     INFO:     Version                 : 2.3
[Wed Feb 15 07:05:17 2012]     INFO:     Size                    : 32 KBytes
[Wed Feb 15 07:05:17 2012]     INFO:     Delete support          : no
[Wed Feb 15 07:05:17 2012]     INFO:     Partial add support     : no
[Wed Feb 15 07:05:17 2012]     INFO:     Reserve support         : yes
[Wed Feb 15 07:05:17 2012]     INFO:     Allocation info support : yes
[Wed Feb 15 07:05:17 2012]     INFO:     Max records             : 2045
[Wed Feb 15 07:05:17 2012]     INFO:     Logical storage         : /opt/vadatech/IPMI/UTCC/repository/sel
[Wed Feb 15 07:05:17 2012]     INFO: SEL used space 0 KBytes with 0 entries
[Wed Feb 15 07:05:17 2012]     INFO: Init sensor 0x69, type 0xf0 (enabled).
[Wed Feb 15 07:05:17 2012]     INFO: Init sensor 0x6a, type 0xf1 (enabled).
[Wed Feb 15 07:05:17 2012]     INFO: Init sensor 0x6b, type 0xcc (enabled).
[Wed Feb 15 07:05:17 2012]     INFO: Init sensor 0x6c, type 0xcc (enabled).
[Wed Feb 15 07:05:17 2012]     INFO: Init sensor 0x7b, type 0xcc (enabled).
[Wed Feb 15 07:05:17 2012]     INFO: Init sensor 0x79, type 0xf0 (enabled).
[Wed Feb 15 07:05:17 2012]     INFO: Init sensor 0x7a, type 0xf0 (enabled).
[Wed Feb 15 07:05:17 2012]     INFO: Init sensor 0x32, type 0xf0 (enabled).
[Wed Feb 15 07:05:17 2012]     INFO: Init sensor 0x33, type 0xf0 (enabled).
[Wed Feb 15 07:05:17 2012]     INFO: Init sensor 0x34, type 0xf0 (enabled).
[Wed Feb 15 07:05:17 2012]     INFO: Init sensor 0x03, type 0xf0 (enabled).
[Wed Feb 15 07:05:17 2012]     INFO: Init sensor 0x04, type 0xf0 (enabled).
[Wed Feb 15 07:05:17 2012]     INFO: Init sensor 0x05, type 0xf0 (enabled).
[Wed Feb 15 07:05:17 2012]     INFO: Init sensor 0x06, type 0xf0 (enabled).
[Wed Feb 15 07:05:17 2012]     INFO: Init sensor 0x07, type 0xf0 (enabled).
[Wed Feb 15 07:05:17 2012]     INFO: Init sensor 0x08, type 0xf0 (enabled).
[Wed Feb 15 07:05:17 2012]     INFO: Init sensor 0x09, type 0xf0 (enabled).
[Wed Feb 15 07:05:17 2012]     INFO: Init sensor 0x0a, type 0xf0 (enabled).
[Wed Feb 15 07:05:17 2012]     INFO: Init sensor 0x0b, type 0xf0 (enabled).
[Wed Feb 15 07:05:17 2012]     INFO: Init sensor 0x0c, type 0xf0 (enabled).
[Wed Feb 15 07:05:17 2012]     INFO: Init sensor 0x0d, type 0xf0 (enabled).
[Wed Feb 15 07:05:17 2012]     INFO: Init sensor 0x0e, type 0xf0 (enabled).
[Wed Feb 15 07:05:17 2012]     INFO: Init sensor 0x0f, type 0xf0 (enabled).
[Wed Feb 15 07:05:17 2012]     INFO: Init sensor 0x10, type 0xf0 (enabled).
[Wed Feb 15 07:05:17 2012]     INFO: Init sensor 0x11, type 0xf0 (enabled).
[Wed Feb 15 07:05:17 2012]     INFO: Init sensor 0x12, type 0xf0 (enabled).
[Wed Feb 15 07:05:17 2012]     INFO: Init sensor 0x28, type 0xf0 (enabled).
[Wed Feb 15 07:05:17 2012]     INFO: Init sensor 0x29, type 0xf0 (enabled).
[Wed Feb 15 07:05:17 2012]     INFO: Init sensor 0x8a, type 0xc1 (enabled).
[Wed Feb 15 07:05:17 2012]     INFO: Init sensor 0x8b, type 0xd8 (enabled).
[Wed Feb 15 07:05:17 2012]     INFO: Init sensor 0x8c, type 0x2b (enabled).
[Wed Feb 15 07:05:17 2012]     INFO: FRU 79, (IPMB Addr 0x20, FRU 79) at channel 16
[Wed Feb 15 07:05:17 2012]     INFO: IPMI Message timeout 300 ms, max retries 4.
[Wed Feb 15 07:05:17 2012]     INFO: Local host conn chan(13) (127.0.0.1 port 624)
[Wed Feb 15 07:05:17 2012]     INFO: FRU 00 at POWER_ONOFF(M1A) state.
[Wed Feb 15 07:05:17 2012]     INFO: FRU 00 Event receiver disabled
[Wed Feb 15 07:05:17 2012]     INFO: FRU 00 at INACTIVE (M1B) state.
[Wed Feb 15 07:05:17 2012]     INFO: FRU 00 at ACTIVATION_REQUEST (M2) state.
[Wed Feb 15 07:05:17 2012]     INFO: FRU 00 at ACTIVATION_IN_PROGRESS (M3A) state.
[Wed Feb 15 07:05:17 2012]     INFO: FRU 00 at ENABLE_RESOURCES (M3B) state.
[Wed Feb 15 07:05:17 2012]     INFO: FRU 00 at ACTIVE (M4) state.
[Wed Feb 15 07:05:17 2012]     INFO: Management controller is initialized.
[Wed Feb 15 07:05:17 2012]     INFO: FRU 00 Event receiver enabled
[Wed Feb 15 07:05:17 2012]     INFO:     Destination: Channel 0, address (0x20, LUN 0)
[Wed Feb 15 07:05:32 2012]     INFO: SDR Merge timer expired. Starting periodic SDR repository monitor.
[Wed Feb 15 07:14:39 2012]     INFO: Sync Carrier FRU inventory from FRU 0x10 0
[Wed Feb 15 07:14:40 2012]     INFO: FRU 253 storage at addr 0x10, FRU 2 is at ACTIVE state.
[Wed Feb 15 07:14:40 2012]     INFO: Board Information
[Wed Feb 15 07:14:40 2012]     INFO:     Manufacturer  : VadaTech
[Wed Feb 15 07:14:40 2012]     INFO:     Product Name  : Carrier-x12
[Wed Feb 15 07:14:40 2012]     INFO:     Serial Number : 4390010
[Wed Feb 15 07:14:40 2012]     INFO:     Part Number   : VT862
[Wed Feb 15 07:14:40 2012]     INFO:     FRU File ID   : x12
[Wed Feb 15 07:14:40 2012]     INFO: FRU 253 storage cache was updated from remote addr at 0x10, FRU 2.
[Wed Feb 15 07:14:40 2012]     INFO: Carrier ID defined by Carrier Information Record : 01
[Wed Feb 15 07:14:40 2012]     INFO: Carrier Slot Entries
[Wed Feb 15 07:14:40 2012]     INFO:     Site(01, 0x0a), IPMB Addr 0x10
[Wed Feb 15 07:14:40 2012]     INFO:     Site(02, 0x0a), IPMB Addr 0x12
[Wed Feb 15 07:14:40 2012]     INFO:     Site(01, 0x07), IPMB Addr 0x72
[Wed Feb 15 07:14:40 2012]     INFO:     Site(02, 0x07), IPMB Addr 0x74
[Wed Feb 15 07:14:40 2012]     INFO:     Site(03, 0x07), IPMB Addr 0x76
[Wed Feb 15 07:14:40 2012]     INFO:     Site(04, 0x07), IPMB Addr 0x78
[Wed Feb 15 07:14:40 2012]     INFO:     Site(05, 0x07), IPMB Addr 0x7a
[Wed Feb 15 07:14:40 2012]     INFO:     Site(06, 0x07), IPMB Addr 0x7c
[Wed Feb 15 07:14:40 2012]     INFO:     Site(07, 0x07), IPMB Addr 0x7e
[Wed Feb 15 07:14:40 2012]     INFO:     Site(08, 0x07), IPMB Addr 0x80
[Wed Feb 15 07:14:40 2012]     INFO:     Site(09, 0x07), IPMB Addr 0x82
[Wed Feb 15 07:14:40 2012]     INFO:     Site(10, 0x07), IPMB Addr 0x84
[Wed Feb 15 07:14:40 2012]     INFO:     Site(25, 0x07), IPMB Addr 0xa2
[Wed Feb 15 07:14:40 2012]     INFO:     Site(26, 0x07), IPMB Addr 0xa4
[Wed Feb 15 07:14:40 2012]     INFO:     Site(01, 0x04), IPMB Addr 0xa8
[Wed Feb 15 07:14:40 2012]     INFO:     Site(02, 0x04), IPMB Addr 0xaa
[Wed Feb 15 07:14:40 2012]     INFO:     Site(01, 0x0b), IPMB Addr 0xc2
[Wed Feb 15 07:14:40 2012]     INFO:     Site(02, 0x0b), IPMB Addr 0xc4
[Wed Feb 15 07:14:40 2012]     INFO: Shelf Fan Geography not defined, setting defaults
[Wed Feb 15 07:14:40 2012]     INFO: Cooling Management Parameters
[Wed Feb 15 07:14:40 2012]     INFO:     Readiness Allowance : 60 secs
[Wed Feb 15 07:14:40 2012]     INFO:     Monitor Cycle       : 20 secs
[Wed Feb 15 07:14:40 2012]     INFO:     Normal Level        : 50% (max level)
[Wed Feb 15 07:14:40 2012]     INFO:     Increment Level     : 05% (max level)
[Wed Feb 15 07:14:40 2012]     INFO:     Decrement Level     : 01% (max level)
[Wed Feb 15 07:14:40 2012]     INFO:     Policy Override     : disabled
[Wed Feb 15 07:14:40 2012]     INFO:     Cooling Enabled     : enabled
[Wed Feb 15 07:14:40 2012]     INFO: No payload power level record in FRU inventory. Using defaults.
[Wed Feb 15 07:14:40 2012]     INFO: Power Module site(1), max override current (watts) : 1152
[Wed Feb 15 07:14:40 2012]     INFO: Power Module site(2), max override current (watts) : 1152
[Wed Feb 15 07:14:40 2012]     INFO: Shelf IP Connection Address   : 192.168.16.17
[Wed Feb 15 07:14:40 2012]     INFO: Carrier IP Connection Address : 192.168.16.1
[Wed Feb 15 07:14:40 2012]     INFO: MCH1 IP Connection Address    : 192.168.16.0
[Wed Feb 15 07:14:40 2012]     INFO: MCH2 IP Connection Address    : 192.168.16.0
[Wed Feb 15 07:14:40 2012]     INFO: Gateway0 Address              : 192.168.1.1
[Wed Feb 15 07:14:40 2012]     INFO: Gateway1 Address              : 0.0.0.0
[Wed Feb 15 07:14:40 2012]     INFO: Subnet Mask                   : 255.255.255.0
[Wed Feb 15 07:14:40 2012]     INFO: MGT IP conn chan(02) eth0:1(192.168.16.1 port 624)
[Wed Feb 15 07:14:40 2012]     INFO: FRU 50 (IPMB Addr 0xc2, FRU 00) "VT UTC010"
[Wed Feb 15 07:14:40 2012]     INFO: FRU 50 Entity(0x0a, 0x61)
[Wed Feb 15 07:14:40 2012]     INFO: FRU 50 at INACTIVE (M1B) state.
[Wed Feb 15 07:14:40 2012]     INFO: Power Feed (Addr 0xc2), Max Payload Power (Watts): 696.00
[Wed Feb 15 07:14:40 2012]     INFO: Power Feed 1 (Channel 01, Addr 0x08) max Power (Watts): 72
[Wed Feb 15 07:14:40 2012]     INFO: Power Feed 1 (Channel 02, Addr 0x09) max Power (Watts): 72
[Wed Feb 15 07:14:40 2012]     INFO: Power Feed 1 (Channel 03, Addr 0x54) max Power (Watts): 92
[Wed Feb 15 07:14:40 2012]     INFO: Power Feed 1 (Channel 04, Addr 0x55) max Power (Watts): 92
[Wed Feb 15 07:14:40 2012]     INFO: Power Feed 1 (Channel 05, Addr 0x39) max Power (Watts): 72
[Wed Feb 15 07:14:40 2012]     INFO: Power Feed 1 (Channel 06, Addr 0x3a) max Power (Watts): 72
[Wed Feb 15 07:14:40 2012]     INFO: Power Feed 1 (Channel 07, Addr 0x3b) max Power (Watts): 72
[Wed Feb 15 07:14:40 2012]     INFO: Power Feed 1 (Channel 08, Addr 0x3c) max Power (Watts): 72
[Wed Feb 15 07:14:40 2012]     INFO: Power Feed 1 (Channel 09, Addr 0x3d) max Power (Watts): 72
[Wed Feb 15 07:14:40 2012]     INFO: Power Feed 1 (Channel 10, Addr 0x3e) max Power (Watts): 72
[Wed Feb 15 07:14:40 2012]     INFO: Power Feed 1 (Channel 11, Addr 0x3f) max Power (Watts): 72
[Wed Feb 15 07:14:40 2012]     INFO: Power Feed 1 (Channel 12, Addr 0x40) max Power (Watts): 72
[Wed Feb 15 07:14:40 2012]     INFO: Power Feed 1 (Channel 13, Addr 0x41) max Power (Watts): 72
[Wed Feb 15 07:14:40 2012]     INFO: Power Feed 1 (Channel 14, Addr 0x42) max Power (Watts): 72
[Wed Feb 15 07:14:40 2012]     INFO: Power Feed 1 (Channel 01, Addr 0x51) max Power (Watts): 72
[Wed Feb 15 07:14:40 2012]     INFO: Power Feed 1 (Channel 02, Addr 0x52) max Power (Watts): 72
[Wed Feb 15 07:14:40 2012]     INFO: Power Module site(1) current role PRIMARY
[Wed Feb 15 07:14:40 2012]     INFO: Power Module site(1) Heartbeat registered.
[Wed Feb 15 07:14:40 2012]     INFO: Power Module site(1) assigned role PRIMARY.
[Wed Feb 15 07:14:40 2012]     INFO: Power Module Heartbeat ping cycle 16 secs.
[Wed Feb 15 07:14:40 2012]     INFO: Power Module site(1) assigned role PRIMARY.
[Wed Feb 15 07:14:43 2012]     INFO: FRU 40 (IPMB Addr 0xa8, FRU 00) "VT VT095"
[Wed Feb 15 07:14:43 2012]     INFO: FRU 40 Entity(0x1e, 0x61)
[Wed Feb 15 07:14:43 2012]     INFO: FRU 40 Telco Capabilities
[Wed Feb 15 07:14:43 2012]     INFO:     Critical Alarm Ctrl : yes
[Wed Feb 15 07:14:43 2012]     INFO:     Major Alarm Ctrl    : yes
[Wed Feb 15 07:14:43 2012]     INFO:     Minor Alarm Ctrl    : yes
[Wed Feb 15 07:14:43 2012]     INFO:     Power Alarm Ctrl    : no
[Wed Feb 15 07:14:43 2012]     INFO:     Test Mode Enable    : yes
[Wed Feb 15 07:14:43 2012]     INFO:     Alarm Cutoff Action : yes
[Wed Feb 15 07:14:43 2012]     INFO:     Minor Reset         : yes
[Wed Feb 15 07:14:43 2012]     INFO:     Major Reset         : yes
[Wed Feb 15 07:14:43 2012]     INFO: FRU 79 at POWER_ONOFF(M1A) state.
[Wed Feb 15 07:14:43 2012]     INFO: FRU 79 at INACTIVE (M1B) state.
[Wed Feb 15 07:14:43 2012]     INFO: FRU 40 active Power Draw (Watts): 60
[Wed Feb 15 07:14:43 2012]     INFO: FRU 40 at ACTIVATION_REQUEST (M2) state.
[Wed Feb 15 07:14:43 2012]     INFO: FRU 41 (IPMB Addr 0xaa, FRU 00) "VT VT095"
[Wed Feb 15 07:14:43 2012]     INFO: FRU 41 Entity(0x1e, 0x62)
[Wed Feb 15 07:14:43 2012]     INFO: FRU 41 active Power Draw (Watts): 60
[Wed Feb 15 07:14:43 2012]     INFO: FRU 41 at ACTIVATION_REQUEST (M2) state.
[Wed Feb 15 07:14:43 2012]     INFO: FRU 03 (IPMB Addr 0x10, FRU 00) "VT UTCA MCMC"
[Wed Feb 15 07:14:43 2012]     INFO: FRU 03 Entity(0xc2, 0x61)
[Wed Feb 15 07:14:43 2012]     INFO: FRU 03 active Power Draw (Watts): 48
[Wed Feb 15 07:14:43 2012]     INFO: FRU 03 at ACTIVATION_REQUEST (M2) state.
[Wed Feb 15 07:14:44 2012]     INFO: FRU 04 (IPMB Addr 0x12, FRU 00) "VT UTCA MCMC"
[Wed Feb 15 07:14:44 2012]     INFO: FRU 04 Entity(0xc2, 0x62)
[Wed Feb 15 07:14:44 2012]     INFO: FRU 04 active Power Draw (Watts): 48
[Wed Feb 15 07:14:44 2012]     INFO: FRU 04 at ACTIVATION_REQUEST (M2) state.
[Wed Feb 15 07:14:44 2012]     INFO: FRU 10 (IPMB Addr 0x7c, FRU 00) "VT AMC719"
[Wed Feb 15 07:14:44 2012]     INFO: FRU 10 Entity(0xc1, 0x66)
[Wed Feb 15 07:14:45 2012]     INFO: FRU 10 at INACTIVE (M1B) state.
[Wed Feb 15 07:14:47 2012]     INFO: MicroTCA Carrier FRU(s) enumeration complete.
[Wed Feb 15 07:14:47 2012]     INFO: Starting Activation Readiness Timers
[Wed Feb 15 07:14:47 2012]     INFO:     Max Descriptors          : 2
[Wed Feb 15 07:14:47 2012]     INFO:     Allowance (Des ID, secs) : (#1, 30 secs) (#1, 30 secs)
[Wed Feb 15 07:14:47 2012]     INFO: Starting Activation Readiness Timers
[Wed Feb 15 07:14:47 2012]     INFO:     Max Descriptors          : 1
[Wed Feb 15 07:14:47 2012]     INFO:     Allowance (Des ID, secs) : (#2, 30 secs)
[Wed Feb 15 07:14:47 2012]     INFO: Starting Activation Readiness Timers
[Wed Feb 15 07:14:47 2012]     INFO:     Max Descriptors          : 1
[Wed Feb 15 07:14:47 2012]     INFO:     Allowance (Des ID, secs) : (#3, 30 secs)
[Wed Feb 15 07:14:47 2012]     INFO: Starting Activation Readiness Timers
[Wed Feb 15 07:14:47 2012]     INFO:     Max Descriptors          : 1
[Wed Feb 15 07:14:47 2012]     INFO:     Allowance (Des ID, secs) : (#4, 30 secs)
[Wed Feb 15 07:14:47 2012]     INFO: Starting Activation Readiness Timers
[Wed Feb 15 07:14:47 2012]     INFO:     Max Descriptors          : 1
[Wed Feb 15 07:14:47 2012]     INFO:     Allowance (Des ID, secs) : (#5, 30 secs)
[Wed Feb 15 07:14:47 2012]     INFO: Shelf Connection: 192.168.16.17 port 623.
[Wed Feb 15 07:14:47 2012]     INFO: FRU 40 at ACTIVATION_IN_PROGRESS (M3A) state.
[Wed Feb 15 07:14:47 2012]     INFO: FRU 40 Enabling EKeying and ports.
[Wed Feb 15 07:14:47 2012]     INFO: FRU 40 at ENABLE_RESOURCES (M3B) state.
[Wed Feb 15 07:14:47 2012]     INFO: Connection established with 127.0.0.1 at 624.
[Wed Feb 15 07:14:47 2012]     INFO: Connection established with 192.168.16.17 at 623.
[Wed Feb 15 07:14:47 2012]     INFO: Cooling management has been disabled.
[Wed Feb 15 07:14:47 2012]     INFO: Alarm/Telco notification disabled.
[Wed Feb 15 07:14:47 2012]     INFO: FRU 00 Event receiver enabled
[Wed Feb 15 07:14:47 2012]     INFO:     Destination: Channel 13, address (0x20, LUN 0)
[Wed Feb 15 07:14:47 2012]     INFO: FRU 40 at power level 1. Power Draw (Watts): 60.
[Wed Feb 15 07:14:47 2012]     INFO: FRU 79 at ACTIVATION_REQUEST (M2) state.
[Wed Feb 15 07:14:47 2012]     INFO: FRU 79 at ACTIVE (M4) state.
[Wed Feb 15 07:14:47 2012]     INFO: FRU 40 at ACTIVE (M4) state.
[Wed Feb 15 07:14:47 2012]     INFO: FRU 41 at ACTIVATION_IN_PROGRESS (M3A) state.
[Wed Feb 15 07:14:47 2012]     INFO: FRU 41 Enabling EKeying and ports.
[Wed Feb 15 07:14:47 2012]     INFO: FRU 41 at ENABLE_RESOURCES (M3B) state.
[Wed Feb 15 07:14:47 2012]     INFO: FRU 41 at power level 1. Power Draw (Watts): 60.
[Wed Feb 15 07:14:47 2012]     INFO: FRU 41 at ACTIVE (M4) state.
[Wed Feb 15 07:14:47 2012]     INFO: FRU 03 at ACTIVATION_IN_PROGRESS (M3A) state.
[Wed Feb 15 07:14:47 2012]     INFO: FRU 03 Enabling EKeying and ports.
[Wed Feb 15 07:14:47 2012]     INFO: FRU 03 at ENABLE_RESOURCES (M3B) state.
[Wed Feb 15 07:14:47 2012]     INFO: FRU 03 at power level 1. Power Draw (Watts): 48.
[Wed Feb 15 07:14:47 2012]     INFO: FRU 03 at ACTIVE (M4) state.
[Wed Feb 15 07:14:47 2012]     INFO: FRU 04 at ACTIVATION_IN_PROGRESS (M3A) state.
[Wed Feb 15 07:14:47 2012]     INFO: FRU 04 Enabling EKeying and ports.
[Wed Feb 15 07:14:47 2012]     INFO: FRU 04 at ENABLE_RESOURCES (M3B) state.
[Wed Feb 15 07:14:47 2012]     INFO: FRU 04 at power level 1. Power Draw (Watts): 48.
[Wed Feb 15 07:14:47 2012]     INFO: FRU 04 at ACTIVE (M4) state.
[Wed Feb 15 07:14:48 2012]     INFO: Power Module site(1) power input not redundant.
[Wed Feb 15 07:14:49 2012]     INFO: FRU 14 at NOT_INSTALLED (M0) state.
[Wed Feb 15 07:14:49 2012]     INFO: FRU 14 at POWER_ONOFF(M1A) state.
[Wed Feb 15 07:14:49 2012]     INFO: FRU 10 active Power Draw (Watts): 29
[Wed Feb 15 07:14:49 2012]     INFO: FRU 10 at ACTIVATION_REQUEST (M2) state.
[Wed Feb 15 07:14:49 2012]     INFO: FRU 10 at ACTIVATION_IN_PROGRESS (M3A) state.
[Wed Feb 15 07:14:49 2012]     INFO: FRU 10 Enabling EKeying and ports.
[Wed Feb 15 07:14:49 2012]     INFO: FRU 10 at ENABLE_RESOURCES (M3B) state.
[Wed Feb 15 07:14:49 2012]     INFO: FRU 10 at power level 1. Power Draw (Watts): 29.
[Wed Feb 15 07:14:49 2012]     INFO: FRU 10 at ACTIVE (M4) state.
[Wed Feb 15 07:14:50 2012]     INFO: FRU 14 at NOT_INSTALLED (M0) state.
[Wed Feb 15 07:14:50 2012]     INFO: FRU 14 at POWER_ONOFF(M1A) state.
[Wed Feb 15 07:14:50 2012]  WARNING: FRU 14 at COMMUNICATION_LOST (M7) state.
[Wed Feb 15 07:14:52 2012]     INFO: FRU 50 at ACTIVATION_REQUEST (M2) state.
[Wed Feb 15 07:14:52 2012]     INFO: FRU 50 at ACTIVATION_IN_PROGRESS (M3A) state.
[Wed Feb 15 07:14:52 2012]     INFO: FRU 50 at ENABLE_RESOURCES (M3B) state.
[Wed Feb 15 07:14:52 2012]     INFO: FRU 50 at ACTIVE (M4) state.
[Wed Feb 15 07:14:53 2012]     INFO: FRU 01 storage at addr 0x10, FRU 1 is at ACTIVE state.
[Wed Feb 15 07:14:53 2012]     INFO: Board Information
[Wed Feb 15 07:14:53 2012]     INFO:     Manufacturer  : VadaTech
[Wed Feb 15 07:14:53 2012]     INFO:     Product Name  : UTCA Shelf
[Wed Feb 15 07:14:53 2012]     INFO:     Serial Number : 4390010
[Wed Feb 15 07:14:53 2012]     INFO:     Part Number   : VTSH INFO
[Wed Feb 15 07:14:53 2012]     INFO:     FRU File ID   : Null
[Wed Feb 15 07:14:53 2012]     INFO: FRU 01 storage cache was updated from remote addr at 0x10, FRU 1.
[Wed Feb 15 07:14:53 2012]     INFO: FRU 01 at POWER_ONOFF(M1A) state.
[Wed Feb 15 07:14:53 2012]     INFO: FRU 01 at INACTIVE (M1B) state.
[Wed Feb 15 07:14:53 2012]     INFO: FRU 01 at ACTIVATION_REQUEST (M2) state.
[Wed Feb 15 07:14:53 2012]     INFO: FRU 01 at ACTIVATION_IN_PROGRESS (M3A) state.
[Wed Feb 15 07:14:53 2012]     INFO: FRU 01 at ACTIVE (M4) state.
[Wed Feb 15 07:14:54 2012]     INFO: FRU 02 storage at addr 0x12, FRU 1 is at ACTIVE state.
[Wed Feb 15 07:14:54 2012]     INFO: Board Information
[Wed Feb 15 07:14:54 2012]     INFO:     Manufacturer  : VadaTech
[Wed Feb 15 07:14:54 2012]     INFO:     Product Name  : UTCA Shelf
[Wed Feb 15 07:14:54 2012]     INFO:     Serial Number : 4390010
[Wed Feb 15 07:14:54 2012]     INFO:     Part Number   : VTSH INFO
[Wed Feb 15 07:14:54 2012]     INFO:     FRU File ID   : Null
[Wed Feb 15 07:14:54 2012]     INFO: FRU 02 storage cache was updated from remote addr at 0x12, FRU 1.
[Wed Feb 15 07:14:54 2012]     INFO: FRU 02 at POWER_ONOFF(M1A) state.
[Wed Feb 15 07:14:54 2012]     INFO: FRU 02 at INACTIVE (M1B) state.
[Wed Feb 15 07:14:54 2012]     INFO: FRU 02 at ACTIVATION_REQUEST (M2) state.
[Wed Feb 15 07:14:54 2012]     INFO: FRU 02 at ACTIVATION_IN_PROGRESS (M3A) state.
[Wed Feb 15 07:14:54 2012]     INFO: FRU 02 at ACTIVE (M4) state.
[Wed Feb 15 07:14:55 2012]     INFO: Original FRU 14 registered (Device ID 0 Product ID 0) does not match with the current (Device ID 0, Product ID 7).
[Wed Feb 15 07:14:55 2012]  WARNING: FRU 14 device ID mismatch. Moving to M0 state
[Wed Feb 15 07:14:55 2012]     INFO: FRU 14 at NOT_INSTALLED (M0) state.
[Wed Feb 15 07:14:55 2012]  WARNING: Enabling event generation for FRU 14 failed.
[Wed Feb 15 07:14:55 2012]     INFO: FRU 14 at POWER_ONOFF(M1A) state.
[Wed Feb 15 07:15:00 2012]     INFO: FRU 14 at NOT_INSTALLED (M0) state.
[Wed Feb 15 07:15:00 2012]     INFO: FRU 14 at POWER_ONOFF(M1A) state.
[Wed Feb 15 07:15:01 2012]  WARNING: FRU 14 at COMMUNICATION_LOST (M7) state.
[Wed Feb 15 07:15:08 2012]     INFO: Original FRU 14 registered (Device ID 0 Product ID 0) does not match with the current (Device ID 0, Product ID 7).
[Wed Feb 15 07:15:08 2012]  WARNING: FRU 14 device ID mismatch. Moving to M0 state
[Wed Feb 15 07:15:08 2012]     INFO: FRU 14 at NOT_INSTALLED (M0) state.
[Wed Feb 15 07:15:08 2012]  WARNING: Enabling event generation for FRU 14 failed.
[Wed Feb 15 07:15:08 2012]     INFO: FRU 14 at POWER_ONOFF(M1A) state.
[Wed Feb 15 07:15:13 2012]     INFO: FRU 14 at NOT_INSTALLED (M0) state.
[Wed Feb 15 07:15:14 2012]     INFO: FRU 14 at POWER_ONOFF(M1A) state.
[Wed Feb 15 07:15:15 2012]  WARNING: FRU 14 at COMMUNICATION_LOST (M7) state.
[Wed Feb 15 07:15:21 2012]     INFO: Original FRU 14 registered (Device ID 0 Product ID 0) does not match with the current (Device ID 0, Product ID 7).
[Wed Feb 15 07:15:21 2012]  WARNING: FRU 14 device ID mismatch. Moving to M0 state
[Wed Feb 15 07:15:21 2012]     INFO: FRU 14 at NOT_INSTALLED (M0) state.
[Wed Feb 15 07:15:22 2012]  WARNING: Enabling event generation for FRU 14 failed.
[Wed Feb 15 07:15:22 2012]     INFO: FRU 14 at POWER_ONOFF(M1A) state.
[Wed Feb 15 07:15:27 2012]     INFO: FRU 14 at NOT_INSTALLED (M0) state.
[Wed Feb 15 07:15:27 2012]     INFO: FRU 14 at POWER_ONOFF(M1A) state.
[Wed Feb 15 07:15:28 2012]  WARNING: FRU 14 at COMMUNICATION_LOST (M7) state.
[Wed Feb 15 07:15:34 2012]     INFO: Original FRU 14 registered (Device ID 0 Product ID 0) does not match with the current (Device ID 0, Product ID 7).
[Wed Feb 15 07:15:34 2012]  WARNING: FRU 14 device ID mismatch. Moving to M0 state
[Wed Feb 15 07:15:35 2012]     INFO: FRU 14 at NOT_INSTALLED (M0) state.
[Wed Feb 15 07:15:35 2012]  WARNING: Enabling event generation for FRU 14 failed.
[Wed Feb 15 07:15:35 2012]     INFO: FRU 14 at POWER_ONOFF(M1A) state.
[Wed Feb 15 07:15:40 2012]     INFO: FRU 14 at NOT_INSTALLED (M0) state.
[Wed Feb 15 07:15:40 2012]     INFO: FRU 14 at POWER_ONOFF(M1A) state.
[Wed Feb 15 07:15:41 2012]  WARNING: FRU 14 at COMMUNICATION_LOST (M7) state.
[Wed Feb 15 07:15:48 2012]     INFO: Original FRU 14 registered (Device ID 0 Product ID 0) does not match with the current (Device ID 0, Product ID 7).
[Wed Feb 15 07:15:48 2012]  WARNING: FRU 14 device ID mismatch. Moving to M0 state
[Wed Feb 15 07:15:48 2012]     INFO: FRU 14 at NOT_INSTALLED (M0) state.
[Wed Feb 15 07:15:48 2012]  WARNING: Enabling event generation for FRU 14 failed.
[Wed Feb 15 07:15:48 2012]     INFO: FRU 14 at POWER_ONOFF(M1A) state.
[Wed Feb 15 07:15:53 2012]     INFO: FRU 14 at NOT_INSTALLED (M0) state.
[Wed Feb 15 07:15:53 2012]     INFO: FRU 14 at POWER_ONOFF(M1A) state.
[Wed Feb 15 07:15:54 2012]  WARNING: FRU 14 at COMMUNICATION_LOST (M7) state.
[Wed Feb 15 07:16:01 2012]     INFO: Original FRU 14 registered (Device ID 0 Product ID 0) does not match with the current (Device ID 0, Product ID 7).
[Wed Feb 15 07:16:01 2012]  WARNING: FRU 14 device ID mismatch. Moving to M0 state
[Wed Feb 15 07:16:01 2012]     INFO: FRU 14 at NOT_INSTALLED (M0) state.
[Wed Feb 15 07:16:01 2012]  WARNING: Enabling event generation for FRU 14 failed.
[Wed Feb 15 07:16:01 2012]     INFO: FRU 14 at POWER_ONOFF(M1A) state.
[Wed Feb 15 07:16:06 2012]     INFO: FRU 14 at NOT_INSTALLED (M0) state.
[Wed Feb 15 07:16:06 2012]     INFO: FRU 14 at POWER_ONOFF(M1A) state.
[Wed Feb 15 07:16:08 2012]  WARNING: FRU 14 at COMMUNICATION_LOST (M7) state.
[Wed Feb 15 07:16:14 2012]     INFO: Original FRU 14 registered (Device ID 0 Product ID 0) does not match with the current (Device ID 0, Product ID 7).
[Wed Feb 15 07:16:14 2012]  WARNING: FRU 14 device ID mismatch. Moving to M0 state
[Wed Feb 15 07:16:14 2012]     INFO: FRU 14 at NOT_INSTALLED (M0) state.
[Wed Feb 15 07:16:15 2012]  WARNING: Enabling event generation for FRU 14 failed.
[Wed Feb 15 07:16:15 2012]     INFO: FRU 14 at POWER_ONOFF(M1A) state.
[Wed Feb 15 07:16:19 2012]     INFO: FRU 14 at NOT_INSTALLED (M0) state.
[Wed Feb 15 07:16:20 2012]     INFO: FRU 14 at POWER_ONOFF(M1A) state.
[Wed Feb 15 07:16:21 2012]  WARNING: FRU 14 at COMMUNICATION_LOST (M7) state.
[Wed Feb 15 07:16:27 2012]     INFO: Original FRU 14 registered (Device ID 0 Product ID 0) does not match with the current (Device ID 0, Product ID 7).
[Wed Feb 15 07:16:27 2012]  WARNING: FRU 14 device ID mismatch. Moving to M0 state
[Wed Feb 15 07:16:28 2012]     INFO: FRU 14 at NOT_INSTALLED (M0) state.
[Wed Feb 15 07:16:28 2012]  WARNING: Enabling event generation for FRU 14 failed.
[Wed Feb 15 07:16:28 2012]     INFO: FRU 14 at POWER_ONOFF(M1A) state.
[Wed Feb 15 07:16:33 2012]     INFO: FRU 14 at NOT_INSTALLED (M0) state.
[Wed Feb 15 07:16:33 2012]     INFO: FRU 14 at POWER_ONOFF(M1A) state.
[Wed Feb 15 07:16:34 2012]  WARNING: FRU 14 at COMMUNICATION_LOST (M7) state.
[Wed Feb 15 07:16:41 2012]     INFO: Original FRU 14 registered (Device ID 0 Product ID 0) does not match with the current (Device ID 0, Product ID 7).
[Wed Feb 15 07:16:41 2012]  WARNING: FRU 14 device ID mismatch. Moving to M0 state
[Wed Feb 15 07:16:41 2012]     INFO: FRU 14 at NOT_INSTALLED (M0) state.
[Wed Feb 15 07:16:41 2012]  WARNING: Enabling event generation for FRU 14 failed.
[Wed Feb 15 07:16:41 2012]     INFO: FRU 14 at POWER_ONOFF(M1A) state.
[Wed Feb 15 07:16:46 2012]     INFO: FRU 14 at NOT_INSTALLED (M0) state.
[Wed Feb 15 07:16:46 2012]     INFO: FRU 14 at POWER_ONOFF(M1A) state.
[Wed Feb 15 07:16:48 2012]  WARNING: FRU 14 at COMMUNICATION_LOST (M7) state.
[Wed Feb 15 07:16:54 2012]     INFO: Original FRU 14 registered (Device ID 0 Product ID 0) does not match with the current (Device ID 0, Product ID 7).
[Wed Feb 15 07:16:54 2012]  WARNING: FRU 14 device ID mismatch. Moving to M0 state
[Wed Feb 15 07:16:54 2012]     INFO: FRU 14 at NOT_INSTALLED (M0) state.
[Wed Feb 15 07:16:54 2012]  WARNING: Enabling event generation for FRU 14 failed.
[Wed Feb 15 07:16:54 2012]     INFO: FRU 14 at POWER_ONOFF(M1A) state.
[Wed Feb 15 07:16:59 2012]     INFO: FRU 14 at NOT_INSTALLED (M0) state.
[Wed Feb 15 07:17:00 2012]     INFO: FRU 14 at POWER_ONOFF(M1A) state.
[Wed Feb 15 07:17:01 2012]  WARNING: FRU 14 at COMMUNICATION_LOST (M7) state.
[Wed Feb 15 07:17:07 2012]     INFO: Original FRU 14 registered (Device ID 0 Product ID 0) does not match with the current (Device ID 0, Product ID 7).
[Wed Feb 15 07:17:07 2012]  WARNING: FRU 14 device ID mismatch. Moving to M0 state
[Wed Feb 15 07:17:07 2012]     INFO: FRU 14 at NOT_INSTALLED (M0) state.
[Wed Feb 15 07:17:08 2012]  WARNING: Enabling event generation for FRU 14 failed.
[Wed Feb 15 07:17:08 2012]     INFO: FRU 14 at POWER_ONOFF(M1A) state.
[Wed Feb 15 07:17:12 2012]     INFO: FRU 14 (IPMB Addr 0x84, FRU 00) ""
[Wed Feb 15 07:17:12 2012]     INFO: FRU 14 Entity(0x00, 0x00)
[Wed Feb 15 07:17:13 2012]     INFO: FRU 14 at INACTIVE (M1B) state.
[Wed Feb 15 07:17:14 2012]     INFO: FRU 14 active Power Draw (Watts): 36
[Wed Feb 15 07:17:14 2012]     INFO: FRU 14 at ACTIVATION_REQUEST (M2) state.
[Wed Feb 15 07:17:14 2012]     INFO: FRU 14 at INACTIVE (M1B) state.
[Wed Feb 15 07:19:19 2012]     INFO: FRU 14 active Power Draw (Watts): 36
[Wed Feb 15 07:19:19 2012]     INFO: FRU 14 at ACTIVATION_REQUEST (M2) state.
[Wed Feb 15 07:19:20 2012]     INFO: FRU 14 at ACTIVATION_IN_PROGRESS (M3A) state.
[Wed Feb 15 07:19:20 2012]     INFO: FRU 14 Enabling EKeying and ports.
[Wed Feb 15 07:19:20 2012]     INFO: FRU 14 at ENABLE_RESOURCES (M3B) state.
[Wed Feb 15 07:19:20 2012]     INFO: FRU 14 at power level 1. Power Draw (Watts): 36.
[Wed Feb 15 07:19:20 2012]     INFO: FRU 14 at ACTIVE (M4) state.

I think the big problem is that I haven't worked with a uTCA of any kind so I am still learning all the commands and the communication structure. TI asked for a power up log, but I am not sure what it is that they want :)

Thanks agian for chiming in - you seem to be the expert! Even Vadatech was saying so :)

Brandy

0 Brandy Jabkiewicz over 13 years ago in reply to Brandy Jabkiewicz

Mastermind 6325 points

Here is a small portion of some of the srio commands I know about.

Shows that Pin 3 is disabled. The is actual supposed to be enable - according to the fru data. Pin 2 lines up with AMC Slot 8 which is where one of my EVMs are. This only happens when I have inconsistencies powering on. Pin 0 aligns with AMC Slot 10 which is where my other EVM is. This one powered up easily.

[root@vtipmi root]# ekey -D srio61
Pin 0: State: Enabled   Direction: Bidirectional Speed: 2 Width: 4
Pin 1: State: Disabled Direction: Bidirectional Speed: 2 Width: 0
Pin 2: State: Disabled Direction: Bidirectional Speed: 2 Width: 0
Pin 3: State: Disabled Direction: Bidirectional Speed: 2 Width: 0
Pin 4: State: Disabled Direction: Bidirectional Speed: 2 Width: 0
Pin 5: State: Enabled   Direction: Bidirectional Speed: 2 Width: 4
Pin 6: State: Enabled   Direction: Bidirectional Speed: 2 Width: 4
Pin 7: State: Enabled   Direction: Bidirectional Speed: 2 Width: 4
Pin 8: State: Enabled   Direction: Bidirectional Speed: 2 Width: 4
Pin 9: State: Disabled Direction: Bidirectional Speed: 2 Width: 0

This is the other command I know. It shows when links are enabled on the swithch. AMC-6 is my power PC. 8 and 10 are my EVMs but they don't have any code running to link yet.

[root@vtipmi root]# vtsrio -s
Slot      Link    Speed
--------- ------- -----------
AMC-1     No      3.125 Gbps
AMC-2     No      3.125 Gbps
AMC-3     No      3.125 Gbps
AMC-4     No      3.125 Gbps
AMC-5     No      3.125 Gbps
AMC-6     Yes     2.5   Gbps
AMC-7     No      3.125 Gbps
AMC-8     No      3.125 Gbps
AMC-9     No      3.125 Gbps
AMC10     No      3.125 Gbps
AMC11     No      3.125 Gbps
AMC12     No      3.125 Gbps
QSFP      No      3.125 Gbps
UPDATE    No      3.125 Gbps
X1_A      Yes     3.125 Gbps
X1_B      Yes     3.125 Gbps
X1_C      Yes     3.125 Gbps
X2_A      Yes     3.125 Gbps
X2_B      Yes     3.125 Gbps
X2_C      Yes     3.125 Gbps

So now I have to forcefully enable Pin 2. (Don't ask me why -e is for 3...)

[root@vtipmi root]# ekey -D srio61 -e 3
Pin 0: State: Enabled   Direction: Bidirectional Speed: 2 Width: 4
Pin 1: State: Disabled Direction: Bidirectional Speed: 2 Width: 0
Pin 2: State: Enabled   Direction: Bidirectional Speed: 2 Width: 4
Pin 3: State: Disabled Direction: Bidirectional Speed: 2 Width: 0
Pin 4: State: Disabled Direction: Bidirectional Speed: 2 Width: 0
Pin 5: State: Enabled   Direction: Bidirectional Speed: 2 Width: 4
Pin 6: State: Enabled   Direction: Bidirectional Speed: 2 Width: 4
Pin 7: State: Enabled   Direction: Bidirectional Speed: 2 Width: 4
Pin 8: State: Enabled   Direction: Bidirectional Speed: 2 Width: 4
Pin 9: State: Disabled Direction: Bidirectional Speed: 2 Width: 0

Then I load my applications on the DSPs and run them. They show a link now.

[root@vtipmi root]# vtsrio -s
Slot      Link    Speed
--------- ------- -----------
AMC-1     No      3.125 Gbps
AMC-2     No      3.125 Gbps
AMC-3     No      3.125 Gbps
AMC-4     No      3.125 Gbps
AMC-5     No      3.125 Gbps
AMC-6     Yes     2.5   Gbps
AMC-7     No      3.125 Gbps
AMC-8     Yes     3.125 Gbps
AMC-9     No      3.125 Gbps
AMC10     Yes     3.125 Gbps
AMC11     No      3.125 Gbps
AMC12     No      3.125 Gbps
QSFP      No      3.125 Gbps
UPDATE    No      3.125 Gbps
X1_A      Yes     3.125 Gbps
X1_B      Yes     3.125 Gbps
X1_C      Yes     3.125 Gbps
X2_A      Yes     3.125 Gbps
X2_B      Yes     3.125 Gbps
X2_C      Yes     3.125 Gbps

And that is it. Just a link but no messages will come across. I am starting to go through the srio register setup on the EVM to make sure I understand each of those.

Thanks again for any hints or tips!

Brandy

0 Dan Gold over 13 years ago in reply to Brandy Jabkiewicz

Intellectual 320 points

I don't really know much about SRIO, I've worked with Vadatech XAUI and PCIe chassis in the past. Hopefully if everything else gets straightened out, the SRIO will come up. Straight out of the box, the EVM code can bring up PCIe links, that's how I tested ours. Does the initial code also bring up SRIO links ? At least then you would know if the links come up automagically

1) seeing the entity id of 0 and device name unknown (output of list_frus_present) is usually indicative of a problem in the board/sensor area data. I see that the latest code is not the one originally released - ipmi.h and mmc.c were modified slightly for the name and serial number changes... (and the Texas Instruments manufacturer name is still mis-spelled :-))

The board manufacturer and product name come from the board area struct. When you do the list_frus_present command, the device name there comes from the device id string in the sdr1 record in mmc.c. So list_frus_present should actually show TI-LC_EVM for the device name. Also looking at sdr1 shows the entity id and instance (0xc1/0x68) that should be returned, but are 0 in your output. Thus it looks like either the MCH isn't querying for that record (doubtful, Vadatech MCH code is very good), or the MMC code isn't handling the query (or initialization) correctly, and returning bad data to the MCH when it queries for it. You may end up getting very good with the debugger (as I had to) and just set breakpoints on MCH queries for data records and see what it's returning. You might also (before running the code) just dump the sdr1 record and stop after module_sensor_init() and make sure the sdr_entry_table looks correct. Maybe also look in the code where sdr_table_entry[0] is returned to the MCH, set a breakpoint and see what's actually being returned.

Get very familiar with sensor.c, in particular ipmi_get_device_sdr* functions :-) Set breakpoints on those and see exactly what is being returned.

Vadatech has a ViewTrace IPMI analyzer to see all the IPMI transactions going on the bus, but it's pretty pricey. If you already have it that's great, if not, you can get by without it.

2) the 1.20 vs 1.32 version might be as simple as hex vs decimal. The minor version is 0x20 (32 in decimal). See how Vadatech is printing it out, i.e. %x.%x would give you 1.20. You don't have the code, so you'll either have to ask them or just put your own minor version in, compile, and then see what shows up.

3) Check with TI about the initial code and see if it brings up a serial link

4) The MC state utcc log shows anomalies for the FRU in the EVM card - it says something about coming up with one value, then it being changed - doesn't look correct. Again, probably issues with the MMC code

5) If you would rather just see prints on the screen, you can enable the MMC output on a serial port. It requires changing the jumpers, as well as installing 2 resistors on the Tx/Rx lines for the MMC uart. Grab a hardware person, shouldn't take them more than a few minutes. You don't have to do it to every board, just the one you use for debug :-)

hope this helps,

Dan

0 Brandy Jabkiewicz over 13 years ago in reply to Dan Gold

Mastermind 6325 points

Hello Dan,

I can answer 3, it only brings up a link when I run a sample SRIO program on the link. I think the periphal is disabled until explicitedly enabled by a register.

As for debugging, if I use break points, it is very difficult becuase as soon as I break, the UART ISR gets backed up and I am no longer able to step through the code. For the UART, I would like to do this but I don't think I have enough information. There does not seem to be a connector or anything on the EVM C6678 and I can not find any reference to this subject matter in advantech's docs or google. Do you have a reference link for me?

<EDIT: Never mind, I worked out the UART stuff from the schematic - you are right, quite simple!>

Thanks,

Brandy

0 Dan Gold over 13 years ago in reply to Brandy Jabkiewicz

Intellectual 320 points

If it brings up the link when you run a sample program, then the SRIO link problem is probably in your application ? Sorry, I'm not very familiar with the SRIO stuff...

As far as the MMC goes, (as you pointed out) everything you need is in the schematic, glad you found it. For debugging, it's a bit painful as you found out. Here are the various things I did to debug the MMC code.

1. Add lots of prints (using DPRINTF) and don't use the debugger. You basically instrument all the functions you want and output, then just run the code and see what the output looks like. Just keep adding more prints and output where needed. Luckily the code is small and doesn't take long to compile and run. Unfortunately you'll run into a design flaw on the board - it's annoying but nothing we can do. You won't see any UART output until the 12V payload power signal is supplied to the card. This only happens after the card sends the handle closed msg and goes to active state. This is because the RS232 converter needs 12V (implicitly). The schematic shows the chip getting 3.3V Aux, but the 3.3V aux is derived from the 12V :-( So be glad at least your card gets into the active state :-)

2. Turn off the DRPINTF define and only use the debugger. As you have already seen the UART interrupts cause problems when single stepping. Even if you disable the UART interrupts, you will get I2C interrupts all the time, because the MCH is constantly querying all cards in the system. That's how it knows when cards disappear (and you see state M7 Communication Lost when doing list_frus_present). They key with using the debugger is not to single step (because you'll always have a uart or i2c interrupt pending), but set lots of breakpoints and do a 'go' to the next breakpoint. Since the i2c buffer isn't very big, you may need to set a breakpoint (at say ipmi_get_device_sdr() and the subsequent spots inside it) and then use 'go' to see what lines you hit. Same with the other functions in sensor.c. Then you'll reboot, and disable the top level breakpoint and see the next one you hit etc... that's what I ended up doing, combination of this and the DRPINTF above.

I would expecially check sensor.c in the calls to get_sdr and get_sdr_info and make sure they are returning correct things, and look at the sdr_entry_table[] to make sure it is correct and being correctly accessed, since that is where the device/entity/instance will come from.

Dan

0 Brandy Jabkiewicz over 13 years ago in reply to Dan Gold

Mastermind 6325 points

Phew! Problems solved. Finally. Thanks everyone for your help! Although I am not exactly sure why the FRU registeration is perfect, we have finally gotten SRIO to work on the Vadatech Chassis with the UTC002 MCH.

Here are some things that I came across.

1. Sometimes the MCH was not enabling the SRIO back plane even though it gave power and registered the EVMs in the FRU structure. To check this use the ekey command.

ex.

[root@vtipmi root]# ekey -D srio61
Pin 0: State: Disabled Direction: Bidirectional Speed: 2 Width: 0
Pin 1: State: Disabled Direction: Bidirectional Speed: 2 Width: 0
Pin 2: State: Disabled Direction: Bidirectional Speed: 2 Width: 0
Pin 3: State: Disabled Direction: Bidirectional Speed: 2 Width: 0
Pin 4: State: Disabled Direction: Bidirectional Speed: 2 Width: 0
Pin 5: State: Enabled   Direction: Bidirectional Speed: 2 Width: 4
Pin 6: State: Enabled   Direction: Bidirectional Speed: 2 Width: 4
Pin 7: State: Enabled   Direction: Bidirectional Speed: 2 Width: 4
Pin 8: State: Enabled   Direction: Bidirectional Speed: 2 Width: 4
Pin 9: State: Disabled Direction: Bidirectional Speed: 2 Width: 0
[root@vtipmi root]# ekey -D srio61 -e1 -e3
Pin 0: State: Enabled   Direction: Bidirectional Speed: 2 Width: 4
Pin 1: State: Disabled Direction: Bidirectional Speed: 2 Width: 0
Pin 2: State: Enabled   Direction: Bidirectional Speed: 2 Width: 4
Pin 3: State: Disabled Direction: Bidirectional Speed: 2 Width: 0
Pin 4: State: Disabled Direction: Bidirectional Speed: 2 Width: 0
Pin 5: State: Enabled   Direction: Bidirectional Speed: 2 Width: 4
Pin 6: State: Enabled   Direction: Bidirectional Speed: 2 Width: 4
Pin 7: State: Enabled   Direction: Bidirectional Speed: 2 Width: 4
Pin 8: State: Enabled   Direction: Bidirectional Speed: 2 Width: 4
Pin 9: State: Disabled Direction: Bidirectional Speed: 2 Width: 0
[root@vtipmi root]#
Now they are enable.

2. The MCH was also not enabling the input and output on the ports by default. It would show a link but it was not turning on the ports for input and output. This can be done a few ways:

a) Maintanence packets directly to the switch (writing register 15C for port 0) to enable the input and output ports

b) Using the srio_reg command on the MCH to write to register 15C (for port 0) to enable the input and output ports.

This register can be found in both the TI specification and the specification of the switch (which for the UTC002 gen 1 is a CPS-Q10, gen 2 is different.)

3. The programs will only work if the ackIDs in both the switch and the DSP are aligned. This is similar to above and can be done with maintanence packets or with srio_reg. Without aligning the IDs, the chassis must be power cycled everytime you restart the DSP. There is an app note that will be coming out soon regarding the recommended procedure. Here is what I did:

a) Each device’s SP(n)_LM_RESP register will contain the link response data from step number 1. This data indicates the attached link partner’s expected inbound ACKID value.

b) The DSP software can read the SP(n)_LM_RESP register and copy the expected partner’s inbound ACKID to its own outbound and outstanding ACKID values in the local SP(n)_ACKID_STAT register.

c) The DSP can then send a maintenance packet to the link partner’s SP(n)_ACKID_STAT register to program the ACKIDs to match expected values of the DSP. When the maintenance packet is sent, it will overwrite all the fields of this register, so the value written should be: outstanding = outbound = DSP’s expected inbound ACKID value, and the inbound = 1 + ACKID from step 3.

ACKIDs are now aligned and data packets can be exchanged normally.

Processors

Processors forum

Regarding the MSP430 update for C6678 EVM and the Vadatech AMC Chassis