IBM 6400 Series, Maintenance Information Manual

Page: 147 / 422

CMX Controller Board Handshake Sequences
147
with the I/O clock, the error blink code 4-3-4 is sent to the diagnostic LED
on the CMX board.
•
Read Operator Panel Keys — The operator panel keys are read to
determine if the user is requesting that the printer be placed in download
mode, diagnostic mode, or debug SIMM disabled. If Cancel and Start are
pressed during start-up, the printer is placed in download mode. If Eject/
Restore and Stop are pressed during start-up, the printer is placed in
diagnostic mode. If any other combination of keys are pressed, the debug
SIMM is disabled. Key states are put in an internal register in the VX
ASIC.
•
Detect DRAM — The VX ASIC supports up to four banks of DRAM
totalling up to 32 Megabytes. Boot code detects how much DRAM is
located in each bank, and relocates the banks to create one contiguous
block of DRAM. The size and location of each bank is then displayed on
the debug terminal through the debug serial port.
•
Test DRAM — DRAM is tested by writing a pseudo–random number
sequence to all the DRAM, then reading the pattern back to verify it
against what was originally written. If an error is detected, the message
“ERROR: DRAM AT ADDRESS XXXXXXXX” is displayed on the LCD.
When finished, the DRAM test sets all memory to zero.
•
Inform the EC Processor — The first 8 Kilobytes of DRAM are reserved
for the EC processor, which must be notified when DRAM is ready to be
used. This is done by putting the message “DCS1” in the ECDC
communications register in the VX ASIC.
•
Detect Ethernet Adapter — An Ethernet adapter must be detected early
in the power up sequence so the printer can tell the adapter it has been
detected and continue with its own power up sequence. An Ethernet
adapter takes a long time to complete its internal diagnostic tests, so the
boot code allows the adapter to power up in parallel with the printer to
reduce its effect on overall boot time.
•
Load Boot Messages — The boot code scans flash memory for OEM
boot messages and loads them into DRAM. The manufacturer’s boot
code is the same for all OEMs, and contains a set of default messages.
Boot messages for specific OEMs are stored in the DC code, not the boot
code.
•
Load Boot Code into DRAM — Flash memory cannot be accessed
while flash is being detected, cleared, or programmed. This prevents boot
code from running in flash because the opcodes cannot be fetched. This
is solved by copying the program into DRAM and executing the program
out of DRAM. The boot code is position–independent in order for the
program to operate at a different address. The interrupt vector table is
also move to DRAM and the vectors are changed to reflect the new
address.
•
Detect Flash — The boot code supports many different kinds of flash
memory, permitting any mixture of flash in the four memory banks. The
only requirement is that flash must exist in bank 0 and have boot code
programmed on it. The boot code displays flash configuration,
manufacturer’s part number, size, and start address out the debug serial
port.