User Manual Part 1

TROUBLESHOOTING
66 MM101271V1 R2A
Troubleshooting information:
Was ‘DCTEST’ loaded into the Modem daughter board?
Check DPR U3 on Modem Daughter Board. Pin 38 Interrupts the 80C323 on the Modem
Board. Pin 43 interrupts the 860. This test is an interaction between the Modem Board
and the Controller Board so testing with one known good board can isolate the problem.
9.4.3 Modem Board Tests Using Simon
9.4.3.1 LOAD SIMON
Procedure:
Use FactoryTest test 4, subtest 1 to load ‘SIMON.HEX’.
Troubleshooting information:
If SIMON loads properly, you will hear a beep or see the SIMON turn-on banner appear
on the terminal connected to 80C323 Port 0.
Failure to load code in the Modem board (applies to DCTEST also) could be due to
problems with Code RAM U2 and associated logic U17 and U18. Processor U1 must be
held reset (U1-10=3.3V) during a code load. It is unreset when ENTER is sent to Factory
Test after a download.
9.4.3.2 TEST DPR FROM THE MODEM SIDE
Procedure:
Execute SIMON Command ‘TMX 0-1FFD’.
Troubleshooting information:
Assuming SIMON loaded and is running, there must be a problem with DPR U3 or the
Microprocessor (U1)interface to it. Note: Use terminal 2 for SIMON commands.
9.4.3.3 TEST MODEM DATA SRAM
Procedure:
Execute SIMON Command ‘TMX 8000-FFFF’.
Troubleshooting information:
If SIMON is running, U4 is indicated.
9.4.3.4 MODEM BER TEST ON RF MODEM
Procedure:
This is the same test as the shelf RF loopback test. Execute SIMON Command BERDE-
02=1. Correct result is no errors and checksum=027C11.
Troubleshooting information:
SIMON causes a data stream to be generated in RF Modem U9 at U9-21 (RFTXDAT).
This data goes to the Controller Board on J2-30 where it enters the PLD at U27-122