Enoch wrote:I've noticed that the latest generation of Seagate drives (HDD.15) like the ST4000DM000 series, they no longer have the full diagnostic handler present, only very few commands actually respond anymore.
fzabkar wrote:Enoch wrote:I've noticed that the latest generation of Seagate drives (HDD.15) like the ST4000DM000 series, they no longer have the full diagnostic handler present, only very few commands actually respond anymore.
Can you show us what you've noticed?
Can you also tell us which hardware you are using to access the terminal port? AIUI, the new drives have 1.8V interfaces whereas the typical TTL adapters use 3.3V I/O.
If you are using a USB-RS232 bridge, can you tell us the part number of the bridge IC? How does it show up in USBDeview or UVCView?
What baud rate and port settings do the HDD.15 drives use?
fzabkar wrote:Thanks for the clarification. However, I'd still like to know which bridge chip your TTL adapter is using. This would help those people who are struggling with other drives that have 1.8V I/O levels. The high trigger level for a 3.3V chip is about 2.3V (= 0.7 x 3.3), so this would suggest that such chips would be unsuitable for 1.8V I/O. That's what made me curious about your setup.
The only commands that the drive responds to are: Ctrl-Z (DIAG), Ctrl-R (ONLINE), Ctrl-T (ESLIP) and Ctrl-A (when in DIAG mode) to show a brief "Info" on the HW.
When in DIAG mode, you can do level traversal (/x) and the drive will switch, but any attempt to issue any commands will result in a null response, or an "Invalid command".
Moltke wrote:it is possible that full- job with the RS232-port is disabled through stuff
Moltke wrote:Spildit wrote:Do you know of a way to "activate" or "enable" it by terminal or ATA ?
ST4000DM000 I did not have. have not tried
Enoch wrote:fzabkar wrote:Regardless, Vcc on HDD.15 is 1v8, but the external serial is at the usual 3v3 for external serial comms on most chipsets.
Users browsing this forum: No registered users and 1 guest