![Tandberg Data SLR7-140 PROGRAMMER Manual Download Page 354](http://html1.mh-extra.com/html/tandberg-data/slr7-140-programmer/slr7-140-programmer_manual_3496838354.webp)
Tandberg Data
Write Buffer
31-4
Tandberg SLR Product Line SCSI Functional Specifications
31.7. Download Microcode with Offsets and Save
Mode (7)
In this mode the initiator may split the transfer of
microcode over two or more WRITE BUFFER commands. If the
last WRITE BUFFER command of a set of one or more
commands completes successfully, the microcode shall be
saved in a non-volatile memory space (a Flash EPROM).
The downloaded code will then be effective after each
power-cycle and reset until it is supplanted in another
Download Microcode and Save Mode or Download Microcode
with Offsets and Save Mode operation.
When the Drive detects the receipt of the last WRITE
BUFFER command with mode 7, the Drive shall perform
verification of the complete set of the microcode prior
to returning GOOD status and saving the microcode.
(refer to the Microcode Verification and Save section
later in this chapter).
Note that the transferred microcode will be lost after a
power-cycle or reset as long as it has not been saved.
To ensure that the microcode is not corrupted by another
SCSI command, it is recommended that either the WRITE
BUFFER commands are linked or that the Drive is reserved
by using the RESERVE command. Note that the last WRITE
BUFFER command in Mode 7 must be issued with Link Bit
equal 0.
31.8. Microcode Verification and Save
Before saving any microcode the Drive will perform
several tests on the microcode data to make sure that
the data really are microcode data intended for the
Drive.
The Microcode Version field must match the Drive's
version identifier located in the Drive Flash PROM.
This prevents the possibility of changing the
microcode version of the Drive.
The Mainboard Revision located in the Microcode
Header must be higher or equal the Mainboard Revision
in the Mainboard. This prevents the possibility of
saving microcode meant for a different hardware.
The Microcode ECC check must be correct.
If any of these tests fails the WRITE BUFFER command
will be terminated with a CHECK CONDITION status. The
microcode in the data buffer is not saved and the
current microcode is left unchanged.
If the disconnection is allowed, the Drive will
disconnect from the SCSI-bus before the save operation.
When the save operation has completed successfully, the
Drive will reconnect to the Initiator and send GOOD
status.
If disconnection is not allowed and the verification of
the code was passed through, the drive will give GOOD
status before the save operation is executed.