Seagate F3 ATA VSC R/W

[ozone]

seagate vsc for send ctrl data like sct cmd: 0x0000 0x0001 0x00BE 0x2459 0x0000 0xa0 0x3F

seagate vsc for Read data like sct cmd: 0x0000 0x0001 0x00BF 0x2459 0x0000 0xa0 0x2F

I know the vsc 3f and 2f ,but i can not get the ctrl data. anyone help?
get the ctrl code ,you can read or write rom ram and sa with sata interface directly, It wont use com port.

[fzabkar]

Here is how it was done in the early days:

Reverse Engineering HDD Software using IDE Port Sniffer:
http://www.hddoracle.com/viewtopic.php?f=59&t=611&p=1613

[ozone]

The free version has been limited, just sniffer some seconds. and the author dont reply the email , i dont know why.

[BGman]

The Smart Command Transport (SCT) protocol was introduced just to avoid the VSC sniffing!

[BGman]

But if you have some sort of IDE/SATA hardware port "sniffer" you can still see the "packages" inside the SCT.

SCT was created for it's own objective, to transport S.M.A.R.T. data.

To transport S.M.A.R.T. data between what?

[Amarbir[CDR-Labs]]

But if you have some sort of IDE/SATA hardware port "sniffer" you can still see the "packages" inside the SCT.

SCT was created for it's own objective, to transport S.M.A.R.T. data.

To transport S.M.A.R.T. data between what?

Well,
I hope The HDD and Computer What Else .Do you think or know some other transport also

[BGman]

SCT means Smart Command Transport and not S.M.A.R.T. Command Transport. Do you get it? S.M.A.R.T. data can be transported so easy in a normal way. No need for Action code, Function Code, etc.

[BGman]

The SCT Command Transport feature set provides a method for a host to send commands and data to a device and for a device to send data and status to a host using log pages. Log page E0h is used to issue commands and return status. Log page E1h is used to transport data.

SCT commands piggy-back on the standard ATA commands: SMART READ LOG and SMART WRITE LOG, or READ LOG EXT and WRITE LOG EXT. As viewed through an ATA protocol analyzer, an SCT command is seen as data being transferred by these commands

[fzabkar]

@BGman, I confess I was confused in regard to the meaning of SCT. Thanks for the clarification.

Table A.2 in the ATA standard distinguishes between SMART and SCT feature sets. AIUI, Seagate and WD use the SMART feature set to transport commands and data via vendor specific logs BEh and BFh. The SCT feature set uses standard E0h and E1h logs, although these can themselves transport vendor specific Action Codes.

Attachments

[fzabkar]

The confusion in my case is due to the fact that, while WD uses the SMART feature set, WD's vendor specific command format in log BEh is identical to that used in SCT command/status log E0h (ie Action Code + Function Code + parameter list).

Just to add to the confusion, various documents from t13.org refer to the "SCT Command Transport feature set" and "SMART Command Transport (SCT)". The first is not strictly logical.

[fzabkar]

Well .... At the end of the day it makes no big difference as the way one would use those commands to send data to the drive is more or less the same ...

Exactly. It's really just a "semantic" difference.

[Moltke]

WD's vendor specific command format in log BEh is identical to that used in SCT command/status log E0h (ie Action Code + Function Code + parameter list).

On disks with the WDC mPU (eg Egle), 2 (!) Command systems worked through the 0BEh log

[BGman]

The confusion in my case is due to the fact that, while WD uses the SMART feature set, WD's vendor specific command format in log BEh is identical to that used in SCT command/status log E0h (ie Action Code + Function Code + parameter list).

Why do you want to see VSC everywhere? WD is using SCT for more than 10 years. It started with the new generation ROYL drives, Seagate started with F3> dtives, Samsung started with Trinity drives, Hitachi with ARM drives, Toshiba with xx46GSX, etc. VSC generations of drives were replaced by the SCT generation.
Try to "sniff" VDMarvel for example. You'll get nothing because all VSC's are encapsulated in a small piece of data transfered between the host and the drive...

[Moltke]

TRUE !!!! Later models of WDC mPU would accept commands by 0xBE

With 0BEh worked even PATA drives. (even 10GB)
But the first system of SCT is quite specific.(аnd the "instruction"- command set was small)