ATAPI InterfaceChapter 5
Erase command
Bit=> | 7 | 6 | 5 | 4 |
| 3 | 2 | 1 | 0 |
Byte |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
0 |
|
|
| Operation code (19h) |
|
|
| ||
|
|
|
|
|
|
|
|
| |
1 |
|
|
| Reserved |
|
|
| 1 (Long) | |
|
|
|
|
|
|
|
|
| |
2 |
|
|
| Reserved |
|
|
|
| |
|
|
|
|
|
|
|
|
| |
3 |
|
|
| Reserved |
|
|
|
| |
|
|
|
|
|
|
|
|
| |
4 |
|
|
| Reserved |
|
|
|
| |
|
|
|
|
|
|
|
|
| |
5 |
|
|
| Reserved |
|
|
|
| |
|
|
|
|
|
|
|
|
|
|
The Erase command is only accepted when the drive is ready and located at either BOP 0/1 or EOD. Erase at BOP causes the drive to write a Control/Filler Frame at the beginning of the current partition, followed by an EOD pattern. (The Use Count field of the Control Frame is incremented from its previous value). This action results in a logical erasure of the current partition. If partition 0 is erased, partition 1 becomes logically erased because of the use count field. Erase at EOD is accepted, but no operation is performed except a write flush if following a WRITE command. This result is because all data following EOD is already logically erased.
The DSC bit is reset (0) after this command is accepted and is set (1) when the command is complete. REQUEST SENSE can then be used to verify successful command completion.
STT8000A Product Manual | Page 39 |