<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>On 2/28/19 11:54 AM, John Vaughters via TriEmbed wrote:<br>
</p>
<blockquote type="cite"
cite="mid:444260526.6610103.1551372883068@mail.yahoo.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<!--[if gte mso 9]><xml><o:OfficeDocumentSettings><o:AllowPNG/><o:PixelsPerInch>96</o:PixelsPerInch></o:OfficeDocumentSettings></xml><![endif]-->
<div class="ydp9fa9d7e8yahoo-style-wrap"
style="font-family:Helvetica Neue, Helvetica, Arial,
sans-serif;font-size:13px;">
<div><span><span style="font-family: Helvetica Neue, Helvetica,
Arial, sans-serif;">>I'm struggling to understand what
you mean exactly by serial number in this context.</span></span><br>
</div>
<div><span><span style="font-family: Helvetica Neue, Helvetica,
Arial, sans-serif;"><br>
</span></span></div>
<div><span><span style="font-family: Helvetica Neue, Helvetica,
Arial, sans-serif;">Yes, FTDI has a unique serial number.
Although I have heard of duplicates, but that would not be
the norm. I cannot speak for other USB chip sets. </span></span></div>
<br>
</div>
</blockquote>
<p>And TI puts the XDS110 1-8 character ID string in this serial
field, so I'm golden for that. The Beaglebone interfaces might be
programmable and I'll be researching that. Out of the box I get
nothing interesting out of lsusb -v. The proprietary gadgets have
FTDI FT230XQ chips in them but lsusb -v doesn't show a meaningful
serial number for them either, despite the chip datasheet claiming
there is one. Maybe I just need explicit rules for the Beaglebone
and special devices? <br>
</p>
<p>But I'll obviously be able to leverage Udev much more than I
thought!</p>
Thanks,<br>
Pete
<p><br>
</p>
</body>
</html>