Hardware Diagnostics for Uniflex

Hardware Diagnostics for Uniflex

HARDWARE DIAGNOSTICS for UNIFLEX™ COPYRIGHT © 1982 SOUTHWEST TECHNICAL PRODUCTS CORPORATION CDSBUG DIAGNOSTIC for UNIFLEX™: COPYRIGHT © 1982 SOUTHWEST TECHNICAL PRODUCTS CORPORATION Important Note Most of the enclosed diagnostics will work only with the MP-09 processor board and NOT with the SWIPC MPU-1 processor board. This is due to the lack of an allocate physical resource system call in the UniFlex operating system. Tf this system call is added to UniFlex in the future, all diagnostics will be modified to work with the MPU-l board. UniFlex is a registered trademark of Technical Systems Consultants Diagnostic: CDSBUG CDSBUG is a diagnostic tool designed to assist qualified technical personnel in finding and rectifying malfunctions in the SWIPC CDS Marksman disk units. IMPORTANT NOTE will Improper use of the diagnostic program "CDSBUG" result in loss of information contained on the CDS disk units. Southwest Technical Products Corporation specifically disclaims any responsibility or liability for any such damages incurred or generated by the "CDSBUG" diagnostic for program. This program is not sold or intended the CDS distribution to persons unfamiliar with CDSBUG units or the operation of diagnostic tools. remains the sole property of Southwest Technical Products and may not be reproduced or distributed without prior written permission. CDSBUG (C) Copyright 1982 Southwest Technical Products Corporation * CDSBUG Copyright (C) MCMLXXXII by - Southwest Technical Products This: product. remainsthe property of Southwest. Technical Products Corporation, 219 West Rhapsody, San Antonio, Texas, in 78216, U.S.A., and may not be distributed, copied, stored a retrieval system, or reproduced by any means, without prior written permission of Southwest Technical Products. to The -purchaser of this product is hereby given permission duplicate this product so long as said duplicate copies remain in the sole possession of the purchaser. Use of this the product by any person or corporate person other than purchaser is prohibited. Disclaimer The’ supplied software is intended for use only as described in this manual. The use of undocumented. features or results parameters may cause unpredictable or deleterious for which Southwest Technical Products is not responsible. Although every effort has been made to make the supplied software and its documentation as accurate and functional as possible, Southwest Technical Products Corporation specifically disclaims responsibility for any damages generated. or incurred by said software or documentation. Southwest Technical Products reserves the right to update or change such materials at any time without notice to any person or persons. *UniFlex is a trademark. of Technical Systems Consultants CDSBUG CDSBUG ~- MARKSMAN DIAGNOSTIC PROGRAM Table of Contents Disclaimer ee 6¢«© ee © © «©«@ Table of Contents ... - oo 8 # # © @ © # @ Installation Procedure . Running the CDSBUG Diagnos tic oe #8 e#& # 6 CDSBUG Command Introduction « « +» « « » « » Example 1: Clearing a Read Error .. - Example 2: Configuring a CDS Unit .. » « 10 Example 3: Formatting a CDS Unit . « e e 13 Detailed Command Descriptions . » + « « CDSBUG Command Summary . 7 68 8 « s e eo 28 @ Using the MKFS Program . a 7 + © #8 @ oo # SWIPC Controller Description ...+.+.- » » 29 Example CDS Drivers > «6 31 Primary Controller Status Byte « . +..- e-« 32 Diagnostic Status Byte - « «+ + « « « + + 33 Drive Control Status Byte so ee @# «@ o 8 + » 34 SWTPC Controller Commands (Data Handling) . + « 37 Contoreller NOP. + « 37 Restore Drive ... e ° 37 Unverified Seek . + « 37 Verified Seek .... « + 38 Firmware Version . « «+ 39 Read Block ... + + « + + 40 Format Block .... «+ 41 Write Block .... » » 41 Swap Out to Disk .. o « 42 ‘3 6 Swap In from Disk . * © #@ 8 #@® @ # @ @ 43 Select Virtual Volume o + 44 SWTPC ContrellerCommands (Diagnostic) . » » 6 45 Invalid Diagnostic Command . « + « « « « 45 Format Track »« « « » e A 45 - « Data Loopback Test . 46 « Read. Sector Header *. « 46 Diagnestie Read. e ° 46 + « Diagnostic Write . 47 Sequence Drive Up .- Sequence Drive Down - » 48 ~ Ati - CDSBUG Table of Contents SWTPC Controller Commands (cont.) . «. « 48 Request Drive Status .« .« . + 6 « © « « 48 Request. Drive Diagnostic .«.. « « « « 49 Software .« 2... 2 s+ 5 « ee eo 49 Reset «© « Set Data Sector Spacing « .. « « » « « 50 Set Swap Sector Spacing «. « + » « « 50 Read Configuration Block(s) . « « 51 Write Configuration Blocks . «-e« 51 Read Controller Scratchpad « « . - « « 53 Read Controller Firmware . « « « « 53 Disable Alternate Track Assignment . 54 Reset Marksman Controller ..«. ++ -« 54 -~iv- CDSBUG INSTALLATION PROCEDURE the CDSBUG NEEDED: The distribution diskette for diagnostic. This sided, single diskette is in UniFlex format, single density,, and contains the following files: edsbug -- CDSBUG Diagnostic Program boots/cds -- Boot Block for CDS Disks ~- Make mkfs . File System Program takes over the entire NOTE: The diagnostic program "cpSBUG" ‘terminate the UniFlex operating system. In order to must be RESET. This implies "CDSBUG" program the system on a in. that the "CDSBUG" program must not be run system multi-user mode. the disk To install the CDSBUG diagnostic program, mount containing the CDSBUG onto a disk with a the program "CDSBUG", and copy program that the CDSBUG diagnostic be bootable UniFlex system. It is suggested A and that it belong to the super-user. placed in the "/etc" directory, CDSBUG is shown below: possible procedure for installing the diagnostic the CDSBUG diskette ++ /etc/mount /dev/fdl /usr2 mount - CDSBUG into "/etc" ++ copy /usr2/cdsbug /etc copy -—- MKFS into "/etc” ++ copy /usr2/mkfs /etc copy -—- to "system" ++ owner system /etc/cdsbug give ownership ~-- turn off non-owner perms ++ perms o-rwx /etc/cdsbug -- create boot directary ++ erdir /etc/boots ' -- boots into "/etc" ++ copy /usr2/boots/* /etc/boots copy — ownership to "bin" ++ owner bin /etc/boots/* give CDSBUG RUNNING THE CDSBUG DIAGNOSTIC first be certain no other To run the CDSBUG diagnostic program, to Then use the "/etc/shutup" program users are logged into the system. User mode. The run the CDSBUG take the UniFlex system into Single and return: program by typing "/etc/cdsbug" -- run the CDSBUG diagnostic ++ /etc/cdsbug the screen over the UniFlex system and The CDSBUG program will take should look like this: -- - VERSION 3.1:2 -- SWIPC CDS DIAGNOSTIC MP-09 0000 BLOCK: 00000 ADDRESS: 00000 STATUS: 00 COMMAND:|_| | || | I || | Lot | | Status --------+ | +-- Cursor Controller | F | | Diagnostic Status ---------— —- | | Drive Status. -------~=--- + the is "COMMAND" is followed by the cursor, indicating that program Commands consists of for the next command string to be entered. waiting return and are terminated by the strings of one to nineteen characters, the CDSBUG from left Command strings are interpreted by diagnostic key. be in a time. Several commands may placed to one character at right, in the to 19 characters). Spaces imbedded the same command string (up command string are ignored. block is set by "BLOCK" is the current block number. The current "+" or decremented using the several commands, and may be incremented by disk media typically use or "=" commands. Commands that operate upon the current block number for their manipulations. buffer "ADDRESS" indicates the hexadecimal address of the memory- the 8K buffer for all transactions with The CDSBUG program uses a single shown is a 20-bit physical CDS disk controller. Note that the value address. CDSBUG "STATUS" shows the status of the CDS unit. ‘Two sets of hexadecimal numbers are shown.- The first number is the 8—bit CDS CONTROLLER status. The second number is the 16—bit combined DIAGNOSTIC and DRIVE status. The primary controller status byte provides information about the execution and completion of controller commands, and in general, is used by programs for handshake and error detection. The diagnostic and drive status bytes are used by diagnostic programs to determine the cause and extent any problems with the CDS Disk Unit. The CONTROLLER status is an 8-bit value returned to the $/09 computer from the CDS Disk Unit Controller. Status is presented, whenever a command terminates, an invalid command is issued, the controller goes busy during drive sequencing, and upon detection of any drive error condition. The individual bits are explained in detail in the section on the SWTPC Controller and summarized below: 5. | OD | le ee BIT NUMBER | — | ee -~ DISK ON LINE AND READY — | —— ee -~--------~-~--~~- fo COMMAND END —+ | ~ CONTROLLER BUSY -~--------------- —+ ae UODISK WRITE PROTECTED —--------~------- $-——ee CRC ERROR ~---- nnn none we NWNO RECORD FOUND wee SEEK INCOMPLETE + ------------~ ee Or COMMAND ERROR 4 The diagnostic status byte returns a value dependant upon. the particular command being executed by the CDS controller. For non-diagnostic commands, this byte is the command that resulted in status being presented. Diagnostic commands use this byte to return data to the diagnostic program. Diagnostic status bytes are documented in the detailed command descriptions at the end of this manual. Non-diagnostic command status is summarized below: 00 - No Operation 60 - Format Write 10 - Restore 70 - Sector. Write 20 - UnVerified Seek 80 - Swap Out to Disk 30 ~ Verified Seek 90 - Swap In from Disk 50 - Sector Read AO - Set Virtual Volume CDSBUG Diagnostic commands return status dependant upon their function. For those commands that do not return a value from the controller, . the status consists

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    155 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us