<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hey bingo! That works for both the Beaglebone and the proprietary
device. Two of the cheap Nano knockoffs give "0000:00:14.0" in
both cases, but they'll be the easiest to deal with. <br>
</p>
<p>-Pete<br>
</p>
<div class="moz-cite-prefix">On 2/28/19 12:50 PM, John Vaughters via
TriEmbed wrote:<br>
</div>
<blockquote type="cite"
cite="mid:525039669.6654765.1551376225605@mail.yahoo.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div class="ydp9bcb93cdyahoo-style-wrap"
style="font-family:Helvetica Neue, Helvetica, Arial,
sans-serif;font-size:13px;">
<div>I have not been able to get the FTDI serial number with
"lsusb -v"</div>
<div><br>
</div>
<div>This is how I get the serial #</div>
<div><br>
</div>
<div><span>udevadm info --attribute-walk -n /dev/ttyUSB0</span><br>
</div>
<div><span><br>
</span></div>
<div><span>it churns out alot of info, but look for </span></div>
<div><span><br>
</span></div>
<div><span>ATTRS{serial}=="XXXXXXXX" </span></div>
<div><span><br>
</span></div>
<div><span>X's replaced with serial number.</span></div>
</div>
<div id="yahoo_quoted_2008039833" class="yahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial,
sans-serif;font-size:13px;color:#26282a;">
<div> On Thursday, February 28, 2019, 12:11:50 PM EST, Pete
Soper via TriEmbed <a class="moz-txt-link-rfc2396E" href="mailto:triembed@triembed.org"><triembed@triembed.org></a> wrote: </div>
<div><br>
</div>
<div><br>
</div>
<div>
<div id="yiv3775487165">
<div>
<p>(Rod Radford sent mail enlightening me with the "-v"
option to lsusb that shows per-chip serial numbers for
some USB devices and this is why I thanked "guys"
instead of just John, as I didn't notice Rod had left
out the list.)<br clear="none">
</p>
<div class="yiv3775487165moz-cite-prefix">On 2/28/19
11:54 AM, John Vaughters via TriEmbed wrote:<br
clear="none">
</div>
<blockquote type="cite"> </blockquote>
</div>
<div>
<div class="yiv3775487165ydp9fa9d7e8yahoo-style-wrap"
style="font-family:Helvetica Neue, Helvetica, Arial,
sans-serif;font-size:13px;"><br clear="none">
<div><span><span style="font-family:Helvetica Neue,
Helvetica, Arial, sans-serif;">Well I say I will
move on from Ubuntu, but I still have it, albeit
old. Yet even this old Ubuntu version I have is
more current than RedHat (Centos) 7 on
libraries. So I still use it. Time will tell if
Debian can fully replace Ubuntu. They do a good
job of coordinating alot of software. However my
hope is Debian does too. Time will tell and I am
not in a hurry. Mainly I use Debian for embedded
stuff and I have come to really like it.</span></span></div>
<div><br clear="none">
</div>
</div>
<p>Well Ubuntu is made out of Debian, just not the
stable branch. So in my mind it's already got the high
ground. :-) But it gets back to the old saw: You can
have it fast, you can have it good, you can have it
cheap, pick any two. The stable branch is stable
'cause releases don't happen fast and the extra
testing is not cheap. This may be naive, but it seems
Ubuntu shares an approach with Microsoft (+/-): why
bother with a lot of testing when your users will trip
over and report bugs for you? I can say with absolute
certainty that this is the attitude TI uses for their
tool chain releases for Linux hosts as, on top of a
very casual (but commercially clear-eyed) stance they
don't even bother to test with up to date versions of
Ubuntu! Now when I get hosed by a newly discovered bug
in their tools the first thing I do is try it out on a
Windows system to avoid wasting time. But to be fair I
should repeat that I have never, ever found a code
generation error or linker error with the TI tools
(and I use the TI compilers as well as gcc). My moans
are about host-specific stuff inside Eclipse and some
of their probes and other gadgets that have scandalous
flaws that don't directly affect the quality of a
target system.</p>
<div class="yiv3775487165yqt4842382287"
id="yiv3775487165yqtfd29018"><br clear="none">
</div>
<div class="yiv3775487165yqt4842382287"
id="yiv3775487165yqtfd65966">
<p>-Pete</p>
<p><br clear="none">
</p>
</div>
</div>
</div>
<div class="yqt4842382287" id="yqtfd87219">_______________________________________________<br
clear="none">
Triangle, NC Embedded Computing mailing list<br
clear="none">
<br clear="none">
To post message: <a shape="rect"
ymailto="mailto:TriEmbed@triembed.org"
href="mailto:TriEmbed@triembed.org"
moz-do-not-send="true">TriEmbed@triembed.org</a><br
clear="none">
List info: <a shape="rect"
href="http://mail.triembed.org/mailman/listinfo/triembed_triembed.org"
target="_blank" moz-do-not-send="true">http://mail.triembed.org/mailman/listinfo/triembed_triembed.org</a><br
clear="none">
TriEmbed web site: <a shape="rect"
href="http://TriEmbed.org" target="_blank"
moz-do-not-send="true">http://TriEmbed.org</a><br
clear="none">
To unsubscribe, click link and send a blank message:
mailto:<a shape="rect"
ymailto="mailto:unsubscribe-TriEmbed@bitser.net"
href="mailto:unsubscribe-TriEmbed@bitser.net"
moz-do-not-send="true">unsubscribe-TriEmbed@bitser.net</a>?subject=unsubscribe<br
clear="none">
<br clear="none">
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Triangle, NC Embedded Computing mailing list
To post message: <a class="moz-txt-link-abbreviated" href="mailto:TriEmbed@triembed.org">TriEmbed@triembed.org</a>
List info: <a class="moz-txt-link-freetext" href="http://mail.triembed.org/mailman/listinfo/triembed_triembed.org">http://mail.triembed.org/mailman/listinfo/triembed_triembed.org</a>
TriEmbed web site: <a class="moz-txt-link-freetext" href="http://TriEmbed.org">http://TriEmbed.org</a>
To unsubscribe, click link and send a blank message: <a class="moz-txt-link-freetext" href="mailto:unsubscribe-TriEmbed@bitser.net?subject=unsubscribe">mailto:unsubscribe-TriEmbed@bitser.net?subject=unsubscribe</a>
</pre>
</blockquote>
</body>
</html>