I remember it doing USB:<div><br></div><div><a href="http://www.google.com/search?q=bus+pirate">http://www.google.com/search?q=bus+pirate</a></div><div><a href="http://code.google.com/p/the-bus-pirate/">http://code.google.com/p/the-bus-pirate/</a></div>
<div><br></div><div>..Maybe not.</div><div><br></div><div><a href="http://www.google.com/search?q=open+source+usb+analyzer">http://www.google.com/search?q=open+source+usb+analyzer</a></div><div>Or the latter-</div><div><a href="http://www.google.com/search?q=open+source+usb+analyzer+protocol">http://www.google.com/search?q=open+source+usb+analyzer+protocol</a></div>
<div><br></div><div>Hope this is any help at all.</div><div><br></div><div> -- Erik<br><div><br><div class="gmail_quote">On Sun, Nov 7, 2010 at 8:47 PM, Michael Prados <span dir="ltr"><<a href="mailto:mprados@gmail.com">mprados@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">PS There are a few devices out there that plug into PC's to act as<br>
signal analyzers, and these solutions are definitely cheaper than<br>
traditional self-contained analyzers. Here are a few of these:<br>
<br>
<a href="http://www.totalphase.com/solutions/apps/usb_analyzer_guide/?gclid=CJaL-8CjkKUCFQdMgwodikvvMw" target="_blank">http://www.totalphase.com/solutions/apps/usb_analyzer_guide/?gclid=CJaL-8CjkKUCFQdMgwodikvvMw</a><br>
<br>
<a href="http://www.lecroy.com/ProtocolAnalyzer/ProtocolOverview.aspx?seriesid=216&capid=103&mid=511&gclid=CJTDkcOjkKUCFQoBbAodqiCIQA" target="_blank">http://www.lecroy.com/ProtocolAnalyzer/ProtocolOverview.aspx?seriesid=216&capid=103&mid=511&gclid=CJTDkcOjkKUCFQoBbAodqiCIQA</a><br>
<br>
<a href="http://www.saelig.com/UA/UA016.htm" target="_blank">http://www.saelig.com/UA/UA016.htm</a><br>
<br>
<a href="http://myspot.neteze.com/~calfee/" target="_blank">http://myspot.neteze.com/~calfee/</a><br>
<br>
These are still a bit pricey, they don't appear to be open source ,<br>
and it doesn't look like any of them help you with signal integrity<br>
issues. Any one use one of these?<br>
<div><div></div><div class="h5"><br>
<br>
On Sun, Nov 7, 2010 at 7:19 PM, Michael Prados <<a href="mailto:mprados@gmail.com">mprados@gmail.com</a>> wrote:<br>
> Hi All,<br>
><br>
> This has been a topic of increasing interest to me, as USB becomes<br>
> less of an optional luxury in hardware hacking and more of a<br>
> necessity, and it's come up again lately in the context of Adafruit's<br>
> bounty for the Kinect:<br>
><br>
> <a href="http://www.adafruit.com/blog/2010/11/05/our-kinect-arrived-today-you-gonna-get-modified/" target="_blank">http://www.adafruit.com/blog/2010/11/05/our-kinect-arrived-today-you-gonna-get-modified/</a><br>
><br>
> So many devices that I care to use or build have a USB interface, and<br>
> there are a lot of tools out there for embedded device developers to<br>
> add this functionality. That is all well and good when it just works,<br>
> but frequently the reality is less than ideal. Here's some scenarios<br>
> I've had to deal with:<br>
><br>
> * the interface for a USB device is not, or not fully, documented<br>
> * the interface for a USB device is nominally documented, but doesn't<br>
> perform exactly as the documentation suggests<br>
> * environmental noise, connector, or transmission line issues lead to<br>
> signal integrity problems (not to mention PCB design issues!)<br>
> * you make a working system, set it up somewhere where it is difficult<br>
> to maintain, and the USB subsystem stops working. How can you diagnose<br>
> it remotely, or outside of the lab?<br>
><br>
> Traditionally, for signal integrity issues- essentially physical layer<br>
> issues, you need a high-bandwidth oscilloscope. I feel like it is not<br>
> unreasonable for a hacker to get a hold of a 100 MHz scope, which<br>
> might suffice for Full Speed USB, but for High Speed USB at 480<br>
> Mbits/sec, you need a scope at up around 2 GHz or above. Even a used<br>
> scope in this range typically runs $5k and up. And heaven forbid you<br>
> need to debug a problem outside of the lab- are you going to strap<br>
> your nice scope to the top of a car, or a helium balloon?<br>
><br>
> What I really fantasize about for the physical layer is a<br>
> self-diagnosing USB hub. Imagine if your hub could provide even a<br>
> rough estimate of the eye size. Has anyone encountered anything like<br>
> this?<br>
><br>
> So far as the data layer, this is where the USB Analyzer typically<br>
> comes in. It seems to cost about the same as the multi-GHz scopes.<br>
> For this, it really seems like something running on Linux, perhaps<br>
> with special hardware, could do the trick. Anyone encounter something<br>
> like this? I've used Windows based USB monitor software before, but<br>
> I've found this kind of limiting, especially if you can't run this<br>
> software on the host device.<br>
><br>
> All too frequently, I end up resorting to RS-232 or RS-485 when I have<br>
> the choice. This may still be right decision, even in 2010, but I<br>
> hate to be forced into it by the inaccessibility of good USB debug<br>
> tools. Seems like a major barrier to hardware hacking, which is only<br>
> going to get worse if a next generation technology such as USB 3.0 or<br>
> Light Peak gains in popularity.<br>
><br>
> Any one have some good solutions to these problems? I'll probably<br>
> post elsewhere too, but I figured on giving it a try here first.<br>
><br>
> -mike<br>
><br>
><br>
> --<br>
> [REMOVE THIS TEXT BEFORE SENDING AN EMAIL!]<br>
><br>
<br>
<br>
<br>
--<br>
[REMOVE THIS TEXT BEFORE SENDING AN EMAIL!]<br>
_______________________________________________<br>
Noisebridge-discuss mailing list<br>
<a href="mailto:Noisebridge-discuss@lists.noisebridge.net">Noisebridge-discuss@lists.noisebridge.net</a><br>
<a href="https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss" target="_blank">https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss</a><br>
</div></div></blockquote></div><br></div></div>