• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 33 subscribers
  • Views 1268 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TUSB9261 in data recovery device

Andrew Tyshchenko
Prodigy 20 points
Other Parts Discussed in Thread: TUSB9261, TUSB9261DEMO

Dear TI representative,

I'm interested in using TUSB9261 USB3.0 to SATA bridge in data recovery equipment.
You may have a look at our company website to get better understanding of target project: http://atola.com/products/insight/disksense.html
Right now we are using USB2.0 Hi-Speed FX2LP interface controller from Cypress and looking for its replacement to improve data reading speed.
Naturally my interest in TUSB9261 is shifted towards handling disks in bad shape and sending ATA commands along with SCSI commands.

We did some evaluation with TUSB9261DEMO board and found it supports ATA PASS-THROUGH(16) command.
According to ATA Command Pass-Through rev.8a (2005) document, this command defines support for a bunch of ATA sub-protocols:
0 Hard Reset
1 SRST
2 Reserved
3 Non-data
4 PIO Data-In
5 PIO Data-Out
6 DMA
7 DMA Queued
8 Device Diagnostic
9 DEVICE RESET
10 UDMA Data In
11 UDMA Data Out
12 FPDMA
13, 14 Reserved
15 Return Response Information

Please answer following questions:
1. Could you please state which of sub-protocols named above are supported by ATA PASS-THROUGH(16) command in TUSB9261?
2. Where can I get a list of all SCSI commands supported by TUSB9261?
3. Does chip allow to read current state of PHY link, perhaps through some vendor-specific SCSI command?
4. How can I obtain firmware source files for the purpose of study and maybe modification?

Thank you.

Andrew Tyshchenko
Atola Technology

  • 0
    TI__Guru* 76130 points

    Hello Andrew,

    We are reviewing your questions and we will reply soon.

    Regards.

  • 0 in reply to Elias Villegas M.
    TI__Expert 4325 points

    The SCSI/ATA translation layer handles SCSI commands from the active mass storage

    class (BOT or UAS) according to the SAT-2 specification. For ATA devices, the SCSI

    block translates READ, WRITE, TEST UNIT READY, SYNCHRONIZE CACHE, ATA

    PASS-THROUGH, START STOP UNIT, commands to their ATA counterparts. -

    Responses for all other commands are generated by the SCSI block for ATA devices.

    For ATAPI devices, all SCSI commands are passed directly to the device as PACKET

    commands. All SCSI commands required by the USB MSC Compliance Specification

    for bootable direct-access block devices (PDT = 0x0) are supported.

    The following SCSI commands are supported for ATA devices (i.e. HDD):

    • INQUIRY (standard, supported VPD pages page, unit serial number, device ID,

    ATA info, block limits, block device characteristics, and logical block provisioning

    VPD page)

    • READ FORMAT CAPACITIES

    • MODE SENSE (6 and 10-byte)

    • MODE SELECT (6 and 10-byte)

    • READ CAPACITY(10 and 16-byte)

    • READ (6, 10, 12, and 16-byte)

    • REQUEST SENSE

    • TEST UNIT READY

    • WRITE (6, 10, 12, and 16-byte)

    • VERIFY (10, 12, and 16-byte)

    • START STOP UNIT

    • REPORT LUNS

    • PREVENT ALLOW MEDIUM REMOVAL

    • SYNCHRONIZE CACHE (10 and 16-byte)

    • UNMAP

    • SEND DIAGNOSTIC (default self-test only)

    • FORMAT UNIT (fmt_data=0, defect_list_format=0 only)

    • SECURITY PROTOCOL IN/OUT

    • ATA PASS-THROUGH (12 and 16-byte)

    For ATAPI devices such as CD/DVD/BD-ROM, all SCSI commands are passed directly

    to the device so command support depends on the device.

  • 0 in reply to Brian Quach
    TI__Expert 4325 points

    1. Could you please state which of sub-protocols named above are supported by ATA PASS-THROUGH(16) command in TUSB9261?

    Codes 0, 1, and 15 are handled by FW.  The others are passed directly to the device.

    3. Does chip allow to read current state of PHY link, perhaps through some vendor-specific SCSI command?

    Yes.  But reading through a SCSI command doesn't make sense because you have to be in U0 to xfer data.
    4. How can I obtain firmware source files for the purpose of study and maybe modification?

    Contact Jorge Llamas to fill out info and pass export control, then we can provide access.

  • 0 in reply to Brian Quach
    Prodigy 20 points

    Hi Brian,

    Thank you for information on firmware internals.

     I have never used UASP earlier, only MSC BOT.

    I know about transfer speed benefit of UASP and like the idea of using it later, but right now I should start with BOT.

    Except speed issue, will I be somehow limited in utilizing chip and firmware functionality when I use BOT comparing to using UASP?

    Also please advice what exactly should I do to contact Jorge Llamas?

    I've found his forum profile ( http://e2e.ti.com/members/227171/default.aspx ), but I don't see anything like "Write a message" button there.

    Thank you.

    Andrew

  • 0 in reply to Andrew Tyshchenko
    TI__Expert 4325 points

    No functionality limitations for BOT.  I'll ask Jorge to contact you directly.

    BR,

    -Brian

  • 0 in reply to Brian Quach
    TI__Expert 7395 points

    Hello Andy,

    Please send me an email to jorge.llamas@ti.com 

    Regards,

    Jorge