• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 197 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.

EK-TM4C1294XL: Time Stamp Protocol, GUID and VISA reference number

Danilo A.
Mastermind 28840 points
Part Number: EK-TM4C1294XL

Hi Team,

We have a customer using EK-TM4C1294XL board and wants to know what USB Protocol it uses, the baud rate of the controller and the globally unique identification number (GUID). He also wants to know the VISA reference for the board to communicate with labVIEW software.

I have checked the datasheet and it says that the device conform with IEEE 1588-2002 Timestamp Precision Time Protocol (PTP) protocol. What is the baud rate, GUID and VISA reference number?

Regards,

Danilo

  • 0
    TI__Guru*** 135355 points

    Hello Danilo,

    First off, the IEEE 1588-2002 Timestamp PTP only applies for the Ethernet peripheral. It does not apply to the USB peripheral.

    The USB Controller from a hardware standpoint supports standard USB communication for Device / Host / OTG based on USB 2.0. Specific protocols like Bulk and CDC are defined by software, and TI provides drivers for the most common ones. However for LabVIEW specifically, we do not have a driver provided that interfaces with it. The GUID and VISA would be defined in such a driver. I'm not sure about baud rate you mean here but we have support for standard data transfer rates for USB 2.0 Full Speed.

    As mention, the LabVIEW software has it's own USB protocol which requires a custom driver and while I don't have a TI produced solution, one of our community members shared details about how to do such an implementation a few years back. It's a bit dated, and not something I have ever delved into, but it's a reference point that can be used to start with if the customer decides to develop their own LabVIEW driver.

    Here are the posts: