KR100389910B1 - Method for testing compact disk drive - Google Patents

Abstract

PURPOSE: A method for testing a compact disk drive is provided to easily grasp error generated parts without using extra hardware. CONSTITUTION: An interrupt vector address is changed(41). An ATAPI(AT Attachment Packet Interface) basic command is set up(42). Basic selection specification is set up(43). A menu is confirmed(44). It is judged whether the ATAPI basic command is inputted(45). If so, it is judged whether the ATAPI basic command is a parameter change command(46). If so, parameters are changed(47). If not, it is judged whether the ATAPI basic command is an ATA(AT attachment) command(48). If so, the ATA command is transmitted to the corresponding port ID to read and display a state of the corresponding port. If not, it is judged whether the ATAPI basic command is an ATAPI command(49). If so, the interrupt and the state of the corresponding port ID are processed.

Description

How to Test Compact Disk Drives

The present invention relates to a compact disc drive, such as a CD-ROM drive, and more particularly to a method of testing a compact disc drive by a computer program without using separate test equipment.

CD-ROM, like a general music CD, refers to a large-capacity storage medium with a diameter of 12cm and 680MB that can only be played using laser light. Like a hard disk drive, a CD-ROM drive that substantially drives such a CD-ROM has an AT-BUS method, a Small Computers System Interface (SCSI) method, and an Enhanced Integrated Development Environment (IDE), depending on a data transmission method with a computer system. It can be divided into three interface methods such as method.

1 is a schematic system diagram of a typical CD-ROM drive.

Referring to this, the CD-ROM drive includes a spindle motor 12 for rotating the disk 11 seated on the turntable 12t, and a pickup for reading information recorded on the disk 11 by using a laser beam. Predetermined control commands from the device 13, the sled drive shaft 14 for linearly moving the pickup device 13 in a reciprocating manner, the microcomputer 15 for controlling the system as a whole, and the microcomputer 15 DSP (Digital Signal Processor: 16) for receiving and outputting a signal for driving the spindle motor 12, and SSP (Servo) for receiving a predetermined signal from the pickup device 13 and transmitting it to the microcomputer 15. A signal processor 17 and a ROM decoder 18 for transmitting the information received from the DSP 16 to a separate host computer (not shown) through the PC interface 19 are provided.

On the other hand, the CD-ROM drive having such a configuration has conventionally been tested using a CDT (CD-ROM Tester) or seisho measuring equipment. However, since the CDT test method uses a device driver 22 as shown in FIG. 2, if an error occurs during the test, whether the error is an error on the PC 21 side, There is a problem that it is difficult to determine whether the error is in the device driver 22 or the CD-ROM drive 23. In addition, the test method using the seisho measuring device 32 as shown in FIG. 3 requires the installation of a separate hardware 34 for driving the measuring device 32, which is cumbersome to use overall. There is this.

The present invention has been made in view of the above problems, and an object thereof is to provide a test method of a compact disk drive that can easily identify an error occurrence area without requiring additional hardware.

1 is a schematic system configuration diagram of a typical CD-ROM drive.

2 is a system configuration diagram schematically showing a drive test method using a conventional CDT.

3 is a system configuration diagram schematically showing a drive test method using a conventional measuring equipment.

Figure 4 is a flow chart showing the execution of the test method of the compact disk drive according to the present invention.

FIG. 5 is a flow chart illustrating an execution process of a routine for reading and displaying a state of a corresponding port in the method of the present invention. FIG.

6 is a flowchart showing the execution of a routine for processing a corresponding port ID interrupt and status in the method of the present invention.

<Explanation of symbols for the main parts of the drawings>

11 ... disk 12 ... spindle motor

12t ... turn table 13 ... pickup device

14 ... sled drive shaft 15 ... microcomputer

16 ... DSP 17 ... SSP

18 ... ROM decoder 19 ... PC interface

21 ... PC 22 ... Device Driver

32.Measuring equipment 34 ... Separate hardware

In order to achieve the above object, a test method of a compact disk drive according to the present invention includes: changing an interrupt vector address; Setting an ATAPI basic command; Setting basic options; Checking a menu; Determining whether the ATAPI basic command has been entered; Determining whether the ATAPI basic command is a parameter change command; Changing a parameter if the parameter is a change command; Determining whether the command is an ATA command if not a parameter change command; Advancing the program to a routine that reads and displays the state of the corresponding port by transmitting a command to the corresponding port ID if the command is an ATA command; Determining whether the command is an ATA command or an ATAPI command; And if it is an ATAPI command, characterized in that it comprises the step of advancing the program to the routine for processing the corresponding port ID interrupt and status.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings.

4 to 6 are flowcharts showing an execution process of a test method of a compact disk drive according to the present invention.

Referring to FIG. 4, first, the interrupt vector address is changed in correspondence to a compact disk drive (not shown) to be tested (step 41). Here, the new vector address is used to check whether an interrupt of the IDE device has occurred.

When step 41 is completed, the ATAPI basic command is set (step 42), the basic option is set (step 43), and the menu is displayed and confirmed (step 44). Here, for example, on / off automatic detection, target position default, address reading, length (length: number of characters, bytes, bits forming a computer word) and the like are set as the options.

When the command and the option are set in this way, it is determined whether the ATAPI basic command has been input (step 45). In step 45, if no command is entered, the program returns to step 44 to reconfirm the menu, and if the command is entered, determines whether it is a parameter change command (step 46). In step 46, the parameter, for example, the target address, the ID length, etc., is changed if it is a parameter change command (step 47), and the program proceeds back to step 44, and it is determined whether it is an ATA command if not a parameter change command (step 48). . In step 48, if it is an ATA command, it sends a command to the corresponding port ID to advance the program to a routine (see Fig. 5) that reads and displays the state of the corresponding port. (Step 49). In step 49, the program proceeds back to step 44 if it is not an ATAPI command, and the program proceeds to a routine (see FIG. 6) that processes the corresponding port ID interrupt and status if it is an ATAPI command.

5 is a flow chart showing the execution of a routine for reading and displaying the state of the corresponding port.

Referring to FIG. 5, as described above, if the ATA command is performed in step 48 of FIG. 4, the program proceeds to this routine. First, it is determined whether the reset command is ATAPI software (step 501). In step 501, if it is a reset command, an ATAPI command is sent to the corresponding port ID (step 502), the port status is read and displayed (step 503), and the program proceeds back to step 44 in FIG. If it is not a reset command, it is determined whether it is a power mode (step 504). In step 504, the command is sent to the corresponding port ID in step 504 (step 505), the corresponding port ID sector is counted (step 506), and the program proceeds back to step 44. If it is not in the power mode, it is determined whether it is a diagnostic command (step 507). If it is a diagnostic command in step 507, the command is sent to the corresponding port ID (step 508), the port status is read and displayed (step 509), and the program proceeds back to step 44. If it is not a diagnostic command, it is determined whether it is an identification command (step 510). In step 510, if it is an identification command, it sends a command to the corresponding port ID (step 511), receives data from the corresponding port data register, reads it and displays identification data if the condition is good (step 512). Step 44 returns to program progress. If it is not an identification command, it is determined whether it is a specification setting command (step 513). In step 513, if it is a specification setting command, the option is set in the corresponding port ID specification register while the command is sent to the corresponding port ID (step 514) to read and display the corresponding port status (step 515). Return to program progress. If it is not a specification setting command, it is determined whether it is a wait command directly (step 516). In step 516, if a direct wait command is sent to the corresponding port ID (step 517), the port status is read and displayed (step 515), and the program proceeds back to step 44. If it is not a direct wait command, it is determined whether it is a sleep command (step 518). In step 518, if it is a sleep command, a command is sent to the corresponding port ID (step 519), the port status is read and displayed (step 515), and the program proceeds back to step 44. If it is not a sleep command, it is determined whether it is an idle command (step 520). In step 520, if it is an idle command, a command is sent to the corresponding port ID (step 521), the port state is read and displayed (step 515), and the program proceeds back to step 44. If it is not an idle command, it is determined whether it is a no operation (NOP) command (step 522). In step 522, if there is no instruction, the command is sent to the corresponding port ID (step 523), the port state is read and displayed (step 515), and the program proceeds back to step 44. If it is not an instruction, an error message is displayed (step 524), and the program proceeds back to step 44.

6 is a flowchart showing an execution process of a routine for processing a corresponding port ID interrupt and status.

Referring to FIG. 6, as described above, if the ATAPI command is executed in step 49 of FIG. 4, the program proceeds to this routine. First, the request is written to the task file register of the corresponding port ID. (Step 601). The command name is then displayed and the start time is set (step 602). Then, it is determined whether the corresponding port is divided (step 603). In step 603, if the corresponding port is divided, the program proceeds back to check whether the corresponding port is divided. If the corresponding port is not divided, the port ID interrupt is added to the corresponding port ID status to set the phase (phase). Step 604). Then, it is determined whether it is a command face (step 605). In step 605, if it is a command face, a 12 byte command is transmitted to the corresponding port ID, and awaiting the interrupt (step 606), the program proceeds back to step 604. If it is not the command face, it is determined whether it is a message face (step 607). In step 607, if no message phase is performed (step 608), the program proceeds back to step 604. If it is not a message face, it is determined whether it is a data input face (step 609). In step 609, if it is a data reception phase, data is received by the reserved host computer's RAM and waits for the corresponding interrupt (step 610), and the program proceeds back to step 604. Here, the data is received through the data register of the corresponding port by the number of byte entry registers of the corresponding port.

On the other hand, in step 609, it is determined whether or not the data reception pace is a data transmission pace (step 611). If the data is sent out in step 611, the data is sent from the reserved host computer RAM and waited for the corresponding interrupt (step 612), and the program proceeds back to the step 604. Here, the data is transmitted through the data register of the corresponding port by the number of byte entry registers of the corresponding port. In step 611, it is determined whether or not the data sending pace is a status pace (step 613). In step 613, the program progress is returned to the step 604 if it is not in the state phase, and it is determined whether the state of the corresponding port is good in the state phase (step 614). In step 614, if the state of the corresponding port is good, the corresponding buffer is displayed (step 615), and the program proceeds back to step 44 of FIG. If the state of the corresponding port is not good, the detection request command is set (step 616) to return the program to step 44 of FIG.

As described above, the test method of the compact disk drive according to the present invention performs the test of the disk drive by a predetermined test program without using a separate device driver or a measuring device, so that the test is easy to perform the test. It is easy to grasp the error that occurs when In addition, no hardware configuration is required, which reduces the cost of testing.

Claims (5)

(a) changing the interrupt vector address; (b) setting an ATAPI basic command; (c) setting basic options; (d) checking a menu; (e) determining whether the ATAPI basic command is input; (f) determining whether a parameter change command is input if the ATAPI basic command is input; (g) changing the parameter if it is a parameter change command; (h) determining whether the command is an ATA command if not a parameter change command; (i) advancing the program to a routine that reads and displays the status of the port by sending a command to the port ID if the command is ATA; (j) determining whether it is an ATAPI command if not an ATA command; And and (k) advancing a program to a routine for processing the corresponding port ID interrupt and status if it is an ATAPI command. The method of claim 1, further comprising the step of returning program progress to step (d) if the ATAPI basic command is not input in step (e). The method of claim 1, further comprising the step of returning the program progress to step (d) if the step (j) is not an ATAPI command. The routine of claim 1, wherein the routine for reading and displaying the status of the corresponding port of step (i) is Determining whether the command is an ATAPI software reset command; Determining whether it is in power mode; Determining whether it is a diagnostic command; Determining whether it is an identification command; Determining whether the command is a specification command; Determining whether it is a direct wait command; Determining whether it is a sleep command; Determining whether the instruction is idle; Determining whether an instruction is no operation; And And transmitting a command to a corresponding port ID to read and display a status of the corresponding port if the command is a no operation, and displaying an error message if the operation is not a command. The routine of claim 1, wherein the routine for processing the corresponding port ID interrupt and state in step (k) is: Recording a requirement in a task file register of a corresponding port ID; Displaying a predetermined command name and setting a start time; Setting a phase at which the corresponding port ID state is added to the corresponding port ID interrupt; Determining whether it is an instruction face; Determining if it is a message pace; Determining whether it is a data reception pace; Determining whether it is a data sending pace; Determining whether it is in a state pace; Determining whether a state of the corresponding port is good; And And displaying a buffer if the state of the corresponding port is good, and setting the program as a check command to return the program progress to the step (d).