• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 3 answers
  • Subscribers 31 subscribers
  • Views 1062 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.

Original question:

AWR1642: Can I use serial data directly?

IWR1443BOOST: How to clearly identify UART-Ports utilizing Linux on Raspberry Pi3 / discern betwwen aux and data port

6057349
Prodigy 110 points
Part Number: IWR1443BOOST

Hello,

currently I utilize two IWR1443BOOST in combination with a Raspberry Pi3B+.
I'd like to know which parameters should / or could be used to definetly identify the Auxillary and Data ports of the EVMs.

Currently I do have a look at the udev information.

  • udevadm info --name=/dev/ttyACM0 --attribute-walk
  • udevadm info --name=/dev/ttyACM1 --attribute-walk

At windows I noticed from EVM to EVM the COM-Port enumeration for data/auxillary port might change from device to device.
What I'm refering to is not the absolute COM-Port enumeration, but the sequence of auxillary and data COM-Ports.

E.g. on one device, the first COM-Port (let's assume COM36) is the auxillary port, and the second port the data Port (COM37). But on another device the sequence is just the other way around.
Auxillary is COM37 and data COM38.

My question now is, the sequence of the COM-port enumeration refering to an order such as "auxiallary first, then data" purely decided by the OS, or the XDS110 debug probe?


On Debian (RPi3) as already mentioned I do have a look at the udev parameters, to then create a symlink.

May I assume that /dev/ttACM0 is ALWAYS the auxillary port and /dev/ttyACM1 is ALWAYS the data port?

I do identify XDS110 devices acording to the folloing parameters:

  • ATTRS{idVendor}=="0451"
  • ATTRS{manufacturer}=="Texas Instruments"

Individual devices (EVMs) are identified via the device serial

  • ATTRS{serial}=="R0031206"

And I try to identify the ports (Aux / data) via the following parameters

  • SUBSYSTEM=="tty"
  • ATTRS{bInterfaceNumber}=="00"        // where "00" refers to ACM0 (aux) and "03" refers to ACM1 (data) (?)
  • ATTRS{iad_bFirstInterface}=="00"       // where "00" refers to ACM0 (aux) and "03" refers to ACM1 (data) (?)

While on windows the COM-Port oder / sequence seems to be changing from EVM to EVM, it looks like the order / sequence on linux seems to be consistant.

  • Im I right about this?
  • Is the distinction between data and aux ports on linux via udev parameters sufficent as described above to clearly differentiate betweenaux and data port on all possibly connected EVMs?

--Additional-Information-----------------

EVM in use: IWR1443BOOST ES3.0

SDK: 02.01.00.04

XDS110 FW: 02.03.00.14

OS_Windows: Windows 10 (1809 / 17763.615)

OS_Linux: Raspbian GNU/Linux 9 (stretch) / Kernel 4.14.52-v7+

  • 0
    TI__Mastermind 30405 points

    Hi Christian,

    The enumeration order for the control and data com ports is determined by the host OS and is not determined by the XDS110 debug probe. Your application should not depend upon the absolute port id but rather use the device identification string to determine the correct COM port usage. e.g.: You can get the device identification string using the lsusb command on Linux.

    For further support, I would suggest you to post this question in Linux forums. 

    Regards

    -Nitin

  • 0 in reply to Nitin Sakhuja
    Prodigy 110 points

    Hello Nitin,

    thank you very much for your reply.
    Maybe I'm a bit slow on this, but how do I identify the ports of the XDS110 with this information.

    Sure, lsusb does list me the connected devices, and a verbose output of an individual XDS110 does yield a flood of information.
    Never the less, how do I identify individual tty-Ports from this?


    Regards,
    Chris

  • 0 in reply to 6057349
    TI__Mastermind 30405 points

    Hi Christian,

    I would suggest you to post this specific question in the TM4C microcontroller forum which is the chip used on mmWave Carrier card for XDS110 JTAG emulation. This question is related to XDS110 usage with Linux.

    Sure, lsusb does list me the connected devices, and a verbose output of an individual XDS110 does yield a flood of information.
    Never the less, how do I identify individual tty-Ports from this?

    https://e2e.ti.com/support/microcontrollers/other/f/908

    Regards

    -Nitin

  • 0 in reply to Nitin Sakhuja
    TI__Genius 15005 points

    Hi Chris,

    Your method is correct - The first interface would be the Application UART and the second interface would be the Auxiliary Data UART.

    Best Regards,

    Anand