Low level hardware analyze (not for beginners!)
From Zenitel Wiki
Contents
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 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. 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 byte 1 and be "02".
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. Read 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.
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.....