Filter
Top Products
Diagnostic Testing and Troubleshooting (2635A)
Memory Card I/F PCA (A6) Troubleshooting.
5A
5A-33
• With ’CtS’ (Clear to Send) displayed, use the UP or DOWN arrow key to select
’OFF’. Then press ENTER.
• With ’ECHO’ displayed, use the UP or DOWN arrow key to select ’ON’. Then press
ENTER. Communications setup for Hydra is now complete.
Assuming that the RS-232 interface is functional, send a carriage return or line feed
character to the instrument and it should send back a prompt. With a Static RAM
memory card installed in the instrument, send the following command followed by a
carriage return or line feed:
MCARD_DESTRUCTIVE_TEST? <size> where the <size> parameter is the number
of kbytes (1024 bytes) of the card to test.
Use <size> = 256 for a 256 kbyte card and
<size> = 1024 for a 1 Mbyte card.<end>
This command writes data to the memory card and then reads and compares the data to
the pattern that was written. A maximum of twenty lines of output will be generated, but
all locations on the card are sequentially written and then read. The messages output by
this command are summarized below:
MEMORY CARD IS NOT INSERTED!
The Memory Card Controller doesn’t recognize that the memory card is inserted
in connector A6P1. Verify that A6U1-19 and A6U1-21 are both near 0 volts dc.
MEMORY CARD IS WRITE PROTECTED!
The Memory Card Controller is indicating that the memory card is write
protected. Verify that the switch on the rear edge of the memory card is in the
proper position and that A6U1-22 is near 0 volts dc when the memory card is
powered up.
MEMORY CARD TEST PASSED.
The memory card test passed without detecting any errors.
ADDRESS 0x000000: DATA WAS 0x14, EXPECTED 0xC9
ADDRESS 0x000001: DATA WAS 0x3D, EXPECTED 0x2D
ADDRESS 0x000002: DATA WAS 0xAB, EXPECTED 0xBD
These are typical errors indicating in hexadecimal the address, the data that was
read from the card and the data that was expected. It may be possible to get some
indication of which address or data signals to probe with an oscilloscope to
determine where the fault is.
When probing signals to detect activity, it may be useful to change the <size> parameter
to be 16384 so that it will attempt to test the card as if it is a 16 Mbyte memory card.
This guarantees that error messages will be output, but it will take longer to complete the
test thus allowing more time to probe signals before having to send the memory card test
command again.