Low level hardware analyze (not for beginners!)

Fault finding on broken hardware

This checks can be preformed if the basic operation of the AMC card is still OK. <br\>

• Prosessor and ram is OK
• Ethernet or serial port works
• Linux is able to boot - Login is available.

Even if the status LED's indicate red, Linux can still be available for diagnosis.

First step is to disable the hardware watchdog. If the AlphaCom software is not able to start then the hardware watchdog will continuously reset the card thus AlphaWeb is unavailable.

• If the cards IP address is unknown cold boot the card
• Try AlphaWeb login, if success do an AlphaSys upgrade in case some files is corrupted.

• If the card is still not working do the hardware check listed bellow.

If no AlphaWeb/telnet available enable the Linux console dip switch and use the serial port for further tests.

The following tests are done from console login, either from serial-link or telnet. Super user password required.

MBI test

The MBI version can be read by the following memedit function.

memedit -1 0x56000300 16
56000300:   02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  "................"

The MBI version number is read from byte 1 and should be "02".

If only "FF FF...." or "00 00 00..." the data link to the MBI is broken.

SBI test

If the MBI works communication to the other SBI's through the backplane should work. <br\> Read SBI on first board position.

memedit -1 0x57008100 16
57008100:   01 ac 00 00 00 00 08 01 00 00 00 00 00 00 00 00

The value "ac" should be seen in byte 2. <br\> If no card present in position 1 the reading will be "ff ff ff ..." <br\><br\> Read the local SBI on amcd card in board position 25 (E7/E20/E26).

memedit -1 0x570c8100 16
570C8100:   03 ac 03 01 00 00 00 01 00 00 00 00 00 00 00 00

"03 ac" should be seen. <br\> If output is "ff ff..." or "00 00 ..." the backplane communication is broken or the SBI-FPGA is not loaded correctly.

DSP check

The following command list DSP diagnostics.

cat /proc/dspdrv

Example output on a running system:

DSP drv version: 0210 ; build date: Jan 16 2008 14:03:03 ;
 1024
 DSP1 Main Dev: 0x0fe00001
 DSP2 Main Dev: 0x0fe00002
 DSP0 ctrl Dev: 0x0fe00003
 DSP0 mmap Dev: 0x0fe00005
 DSP0 mmap_buffer: 3337256960
 mmap_buffer[0] = c6ea8000 ; phys 06ea8000;
 DSP1 ctrl Dev: 0x0fe00004
 DSP1 mmap Dev: 0x0fe00006
 DSP1 mmap_buffer: 0
DSP 1 diagnostics
 Ready!
 cnt_8khz = 27165384
 cnt_wait_mcbsp0 = 4270651387
 cnt_wait_mcbsp1 = 3
 cnt_frm_prcss_tm = 4032
 cnt_frm_prcss_tm_max = 4293697236
 cnt_frm_interval = 6249
 cnt_frm_rx_miss = 1
 PCM buffers adresses:
 pcm_tx_input_frame0  = 0x8000107c
 pcm_rx_output_frame0 = 0x80001280
 pcm_tx_input_frame1  = 0x80001484
 pcm_rx_output_frame1 = 0x80001688
 frame_tab_info_tx = 0x80003c78
 frame_tab_info_rx = 0x80003e00
DSP 2 diagnostics
 Ready!
 cnt_8khz = 27165063
 cnt_wait_mcbsp0 = 1832807137
 cnt_wait_mcbsp1 = 2
 cnt_frm_prcss_tm = 1546
 cnt_frm_prcss_tm_max = 4291703462
 cnt_frm_interval = 6252
 PCM buffers adresses:
 pcm_tx_input_frame0  = 0x80001_output_frame0 = 0x80001280
 pcm_tx_input_frame1  = 0x80001484
 pcm_rx_output_frame1 = 0x80001688
 frame_tab_info_tx = 0x80003c78
 frame_tab_info_rx = 0x80003e00

Tone setup diagostic

The following command list the output from tone setup.

cat /tmp/z_amc_tone_setup.log

Example output on a OK system, notice a lot of "OK". If failure communication with the DSP's is in trouble.

d02 OK
d20 OK
d21 OK
d30 OK
#Set up 12 DTMF tones
DTMF0 OK
DTMF1 OK
DTMF2 OK
DTMF3 OK
DTMF4 OK
DTMF5 OK
DTMF6 OK
DTMF7 OK
DTMF8 OK
DTMF9 OK
DTMF* OK
DTMF# OK
#Set up loopback for 12 fader resources
loop0c OK
loop0d OK
loop0e OK
loop0f OK
loop10 OK
 .... and it continues for a while.....

Driver status

MBI IRQ driver

Check the IRQ from the MBI to the IXP. <\br>

cat /proc/mbi_irq

mbi drv Status:
        real irq: 540779
        GPIO-3 state: 1
        wake up count: 0

When the AMC application is running The GPIO-3 should be 1 and "real irq" should be increasing each time the function is called.

Watchdog driver

Watchdog status, you can see the toggling of watchdog pin/LED status etc.

cat /proc/driver/wdog

WatchDog and LED driver version 0202
Device open count: 2
AMC timeout: 20
AMC status: Alive
Data Latch state : ed
   DOG Alive Pin   : High
   WDOG Mode       : 10s/3s
   Master Failure  : Cleared
   Stand-by Request: Cleared
   LED D600     : On - Green
   LED D601     : Off
   LED D602     : Off

Real time clock

Real time clock driver. The current time should be correct.

cat /proc/driver/rtc

Real Time Clock (bq4802) version 0201
Base address: C8852000
RAM Dump:
56 FF 40 FF 11 FF 04 FF
02 04 08 00 00 09 0E 00
Date/Time                  : 04-Apr-2008 11:40:56
Alarm Interupt Enable      : no
Periodic Interupt Enable   : no
Power-fail interupt Enable : no
AIE in backup mode         : no
Update Transfer Inhibit    : yes
RTC enabled                : yes
24h mode                   : yes
Daylight savings enable    : no
Battery valid              : yes

Mac address chip

The mac address chip. Vendor should be Stentofon.

cat /proc/driver/mac

Mac chip driver version 0200
Mac Chip Status:
     FD FF FF FF FF FF FF 00
Mac Chip Dump:
     00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f
     |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
00 - 0F AA 00 00 00 00 00 01 49 44 4E 52 80 01 01 00
01 - 92 08 FF FF FF FF FF FF FF FF FF FF FF FF FF FF
02 - 14 8C 11 00 00 CF 04 00 CB 13 00 53 74 65 6E 74
03 - 6F 66 6F 6E 00 B0 14 FF FF FF FF FF FF FF FF FF
04 - FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
05 - FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
06 - FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
07 - FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
CRC16 Sum of data: A875
Mac chip vendor (type): Stentofon
Mac Chip Content:
Project ID  = 00:00:11:8C
MAC address = 00:13:CB:00:04:CF
MAC string  = Stentofon