• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 33 subscribers
  • Views 481 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.

USB 3.0 interface on DM8148 processor

Bryan Busacco
Expert 1215 points
Other Parts Discussed in Thread: TUSB7320, TUSB9261, TUSB1310A, TUSB7340

Considering the DM8148 for a new design and would like SuperSpeed USB.  I see a few options and would like suggestions on the best way to proceed. My product is to be a USB device.

TUSB7320 Host controller

TUSB9261 SATA interface

TUSB1310A PIPE interface

 

If you can suggest which TI device best fits the application and let me know if there is reference material on applying USB 30. to this device or similar device, that will be helpful.

 

Bryan Busacco

  • 0
    TI__Genius 16430 points

    Bryan,

    You specifically use the term "device" for what your customer is trying to accomplish, assuming by device they mean peripheral and not host then the short answer is there is not a clean solution. 

    The TUSB9261 can not be used as it has no way to talk to the DM8148.  The SATA ports on both devices are SATA host implementations and expect to talk to SATA slaves (drives) and two SATA hosts can not talk to each other.

    The TUSB1310A could be an option, but will require an FPGA be used to glue the TUSB1310A to the DM8148.  And the FPGA can not be that simple as it has to be able to support the full USB 3.0 peripheral core as the the TUSB1310A is the physical layer only,  If this path is followed, they would also need to identify the best interface between the FPGA and the processor.

    If the customer actually wants to be a USB 3.0 host controller, then the TUSB7320 (or TUSB7340) are an option.  They would need to configure the PCI Express controller as a root complex and then it would be a seamless interface.  Depending on the OS they are running in the ARM, would then determine the driver availability.  But again, this is only if they want to be a USB host.