02/05/01 ______________________________________________________________________ FUP -- IBM Option 20/40GB & 120/240GB 4mm DAT Firmware Update Program v2.3 The DDS48160.EXE file will self-extract and build a DOS bootable diskette image. The image contains a batch file that automatically executes a firmware update on the tape drive EEPROM. A SCSI inquiry test is run at the conclusion and will verify that the 8.160 firmware has been correctly applied. _______________________________________________________________________ Firmware Difference List This release note summarizes the firmware changes made to the Scorpion 40 DDS/4 drive and Scorpion 240 DDS/4 Autoloader firmware from version V8110 to version V8160. Loader Changes Number Description Details 1 Modify Tape Reels and Meter Icon Management. 1) Modify Tape Task to Send Tape Reels Messages to LCF. 2) Send message to Tape Task indicating that the drive is either in a loader or standalone configuration. If the drive is a standalone drive, do not send or process Tape Meter and Tape Reels icon management messages. No field impact. 2 Clear Unit Attention on Loader DDS4 Loader. Clear 6/29/00 unit attention for Lun 1 if reported to Lun 0 and vice versa. Loader only reports 6/29/00 to the first lun sending a command. No field impact. 3 Merge LCP E113. Add improved serial port driver and switch debouncing. Small reliability improvement. 4 Add cassette 'wrap' to autoload mode. When in autoload mode 'wrap' from last cassette in magazine back to the first cassette in magazine. Customer request. 5 LCP Version E114 Version E114 from MKE. Includes changes for vertical orientation and also some improvements in the magazine initialization algorithm. Customer request 6 LCP Version E115 Version E115: Ensure backlight LED comes on when magazine is inserted. No field impact, aesthetic improvement 7 Read Element Status Command fails with short allocation lengths Read Element Status command was checking for specific values in allocation length and using allocation length when building response data. This is not per SCSI and was causing problems for Dantz Retrospect s/w, only. Removed checks and made sure there were not problems with expected allocation values. No field impact, no other software was known to be effected. Reliability Improvements/SCSI Issues Number Description Details 1 Drive does not retry messages that have bus parity error after command phase. Fixed potential problem where drive does not respond to a retried message correctly if the first one experienced a bus parity error during command phase. This fix also covers the correct handling of multiple bus parity errors during MESSAGE OUT. No field impact, parity errors rarely occur in the field. 2 Hardware failure detected during POST was not reported to host. If the drive fails a Power On Self Test (POST) it is not properly reported to the host on the first SCSI command which may return the error. 3 Fix Linux Problem Modified the code so that whenever a WIDE negotiation is received, the drive defaults the data transfer mode to ASYNC in compliance with SCSI protocol. 4 Alter Tape Alert Mode Page Change Tape Alert mode page Dexcpt default to be 1. This is the standard default value per Tape Alert spec 3.0. No field impact, not use by software. Reliability Improvements/Tape handling Number Description Details 1 Utilize buffered data to minimize tape motion. Implemented read/rewind buffering optimization feature. 2 Tape Process abort during Head Clean will cause MCP to hang. If abort happen during head clean, MCP sometimes hangs. Fix is to let head clean finish instead of abort while waiting for MCP change modes because head clean could be aborted when Cylinder is running at half speed and causes MCP hang. 3 Update cassette/format info in EEPROM. Save tape type/format information in drive error log. Replaced SC1B field with CassHole and DataFmt fields in EEProm error structure. This lets us know tape type at time of failure. 4 Unecessary head cleans take place with slightly marginal drive/media. Change to reduce head cleaning with marginal drives/media by adding an additional qualifier of a C1 ratio greater than 2:1 to the parameter of a C1 delta of 50 between channels A and B. 5 Preventative Head Clean Improvements. a)fix problem that caused redundant head cleaning in read mode b)Improved implementation of Preventive Head Clean function to consolidate code. 6 Blank Tape Detection Changes A change was made to V8110 to detect a tape which, very intermittently, was detected as blank. The fix could cause new tapes to take an excessive amount of time to be detected as blank. Change is to change from V8110 f/w since new MCP has fixes for the mis-detect blank problem. 7 Preventive Cleaning may be to stringent on slightly worn media. Implemented 2 suggestions for reducing false triggering of preventive head cleaning function caused by high media defects. (1) Increase the moving-average buffer from 64 to 100 C1 samples. (2) Filter sampled C1 data going into the moving-average buffer for groups less than group 20. Reliability Improvements/Media Errors Number Description Details 1 03/53/00 and 04/44/00 - Marginal media handling to address field returns. 1. Create new field for vendor group status in cassette info 2.Add code to detect bad vendor group read and set vendor group status in the cassette info (cass.vendorgroup) 3. Reset cass.vendorgroup after succesfull format. 4. Add code to report GOOD STATUS instead of INITIALIZE FAIL and set vendor group status indicate calibration fail in the cassette info field (cass.vendorgroup) if calibration failure on 1 partition tape. 5. Check new variable, vendorgroup, in cassette info structure and if problems in vendorgroup then reformat on write if at LBA 0 and single partition tape. 2 Handle tape with partial Vendor Group Add code to report blank if incomplete vendor group detected(format was aborted in different cases). This will help prevent 03/53 and 04/44 errors. 3 Aborted Rewind due to Subcode Glitch causes an 03/3B/00 Error (very rare). Add bit map check for areaid during Rewind 4 03/3b/bf condition is not cleared after re-format the tape Sometimes when formatting over a tape which previously failed format a 03/3b/bf occurs.Always clear all failure status if tape reformatted sucessfully Performance Improvements Number Description Details 1 Implement Performance Improvements a) Incorporate performance changes RTOS. b) After a record underrun and reposition, a change was made to issue FWDx1 command to MCP if another data buffer is ready to record or issue PAUSE command if no buffer is ready. 2 Performance: Remove Pause from Read Reposition and optimize reposition point Performance improvement, Remove Pause from Read Reposition Task realignment and optimization performance problems. 1) The C3 task is no longer round-robin, and works using kernel messages. 2) There were two MCP tasks, MCP_ISR and MCP. MCP code was moved to MCP_ISR, so the MCP task is no longer needed. Most of MCP now runs at IRQ time, but there is still a special function that handles MCP printf's within the round robin. 3) Move s_reel_int out of MCP_ISR_Task into Irq_Exec. It simply increments a variable, it's not worth the overhead of sending a message. 4) At the end of Irq_Exec check the interrupt status register. If there are other interrupts pending, they are serviced before exiting. This saves the overhead of entering/exiting Irq_Exec. 5) Lower the SCSI task priority so that it interacts with the other Tasks more evenly. 6) Enable Cache operations for Program Data as well as instructions Performance - DC task is requesting data from the ring buffer too often Enable virtual descriptor mode during write. Firmware -------- Firmware is a term used for the software program which controls the tape drive. All IBM tape drives store firmware in a ROM (read only memory) internal to the drive. Newer tape drives (since about 1993) use a type of ROM called a flash EEPROM (electrically erasable ROM). Most tape drives, with flash EEPROMs, are capable of receiving updated firmware through the SCSI bus. Firmware Files -------------- New firmware is provided in a file. Firmware filenames have the format .HEX or .BIN. For example, V4BT-400.HEX, V5AC-0.HEX, V6580500.BIN, V658A-0.BIN. Firmware is not generally interchangeable between tape drive models. FUP verifies that new firmware matches the tape drive model. Firmware Upgrade Program (FUP) ------------------------------ FUP.EXE (Firmware Update Program) is used, primarily, to update the firmware in a IBM DAT tape drive or loader. FUP transfers the content of a firmware file to a tape drive. The tape replaces its firmware with the new firmware and saves it in an EEPROM. IBM has built the diskette image to be a self-extracting bootable diskette with ASPI support. We recommend that this method is used as it ensures that nothing will be resident in memory that can corrupt either the firmware update or data local to the system. FUP Errors ---------- The following lists common FUP errors and comments. update ERROR: The ASPI Manager was not found. Check your CONFIG.SYS. update ERROR: The tape drive's model is not recognized, and therefore, cannot be updated by FUP in the normal mode. Comment: FUP cannot update firmware in all tape drive models. A newer version of FUP may be available. Or, your drive may contain a special engineering firmware release which is not recognized by FUP. Consult with a IBM representative. update ERROR: "": The firmware file is an invalid version. Try selecting a different firmware file. update ERROR: "": The firmware file does not match the drive model. Try selecting a different firmware file. Comment: The firmware file appears to be incorrect for the tape drive model. Firmware is, generally, not interchangeable between tape drive models. Obtain a new copy of the firmware file intended for your tape drive model then try again. Special engineering release firmware may also cause this error to be shown. If you suspect this is the case, consult a IBM representative. update ERROR: (): Hexfile record error: update ERROR: (): Hexfile syntax error: update ERROR: "": Missing flash boot code update ERROR: "": Firmware image size = bytes: Invalid image size Comment: The firmware file may be corrupt. Obtain a new copy of the firmware file intended for your tape drive model then try again. update ERROR: "": Firmware image size ( bytes) does not match drive requirement ( bytes) Comment: This message may be seen when using "fup /force". The firmware file image is either to small or too large for the EEPROM. Obtain a new copy of the firmware file intended for your tape drive model then try again. update ERROR: Insufficient memory for byte transfer buffer Comment: If using MS-DOS, Windows 3.1x or, Windows 95/98 in MS-DOS only mode, you may need to remove (or comment out unnecessary drivers and/or "terminate-and-stay- resident" (TSR) programs from CONFIG.SYS and AUTOEXEC.BAT to increase memory available to FUP. update ERROR: Cannot update this drive's firmware in Windows 9x Graphics mode (Within a DOS Box). Reboot your system into MS-DOS only mode. Comment: See the section "Windows 95/98 Graphics Mode" above. update ERROR: "": Is an invalid firmware file name Comment: The selected file name does not have a .HEX or .BIN suffix. Try selecting a firmware file a name of .HEX or .BIN update ERROR: A IBM DAT tape drive was NOT found. Make sure tape drive power is turned on, and SCSI bus is properly terminated. Comment: Shutdown and turn power off. Examine cables and connections. Power up and reboot the system. Try again. update ERROR: An error was encountered while Flashing firmware. The drive was not updated. Comment: The tape drive may have rejected the new firmware. Obtain a new copy of the firmware file intended for your tape drive model then try again. update ERROR: An error was encountered while Flashing firmware. The drive was not updated. Comment: If the switch block settings for switches S9 and S10 are not set to the default(OFF) position the drive will not be identified correctly and the flash mechanism will be able to run. Remove power from the device and correct the switches to the default settings and reapply the flash mechanism. ====================================================================== LICENSE AGREEMENT AND WARRANTY DISCLAIMER This is a legal agreement between you the purchaser and International Business Machines, Inc. By accessing FUP, (the "Software"), you agree to be bound by the terms of this agreement. If you do not agree, do not access the software. IBM provides the accompanying object code of the Software and nonexclusively licenses its use to you on the following terms and conditions. IBM grants you a limited access to use one copy of the Software. You may not copy, distribute the Software for resale. You may not reverse engineer, modify, rent, or lease the Software. In addition, you may not disclose the information or data incorporated in the Software to others, in any format. You accept the Software "as is" without any warranty whatsoever. IBM does not warrant that the Software will meet your requirements; that the Software is fit for any particular purpose or that the use of the Software will be error free. IBM EXPRESSLY DISCLAIMS ALL WARRANTIES, WHETHER ORAL OR WRITTEN, EXPRESSED OR IMPLIED, INCLUDING WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT WILL IBM BE LIABLE TO YOU, YOUR CUSTOMERS OR OTHER USERS IN ANY WAY BASED ON USE OF THE SOFTWARE, INCLUDING WITHOUT LIMITATION FOR ANY LOSS OF PROFITS, LOSS OF DATA OR USE OF THE SOFTWARE OR INDIRECT, INCIDENTAL, CONSEQUENTIAL, SPECIAL, OR EXEMPLARY DAMAGES ARISING OUT OF OR IN CONNECTION WITH THE USE OR INABILITY TO USE THE SOFTWARE. ======================================================================