BeagleBoard/GSoC/2010 Projects/USBSniffer - Revision history

Peter Huewe: Added to category BeagleBoard and GSOC

2011-04-13T05:33:41Z

Added to category BeagleBoard and GSOC

Drinkcat: /* Abstract */

2010-08-16T11:51:28Z

‎Abstract

Drinkcat: /* Bandwidth allocation */

2010-08-09T09:38:34Z

‎Bandwidth allocation

Drinkcat at 09:26, 9 August 2010

2010-08-09T09:26:59Z

Drinkcat: /* Tested devices */

2010-08-09T07:21:54Z

‎Tested devices

Drinkcat at 07:20, 9 August 2010

2010-08-09T07:20:45Z

Drinkcat: /* Build instructions */

2010-08-09T07:20:24Z

‎Build instructions

Drinkcat: /* Build instructions */

2010-08-09T07:19:58Z

‎Build instructions

Drinkcat: /* Build instructions */

2010-08-09T07:13:08Z

‎Build instructions

Drinkcat: /* Usage instructions */

2010-08-09T07:11:00Z

‎Usage instructions

← Older revision		Revision as of 05:33, 13 April 2011
Line 215:		Line 215:
	... S Bi:2:101:1 -115 1024 <		... S Bi:2:101:1 -115 1024 <
	... C Bi:2:101:1 -121 514 = 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000		... C Bi:2:101:1 -121 514 = 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
		+
		+
		+	[[Category:BeagleBoard]]
		+	[[Category:GSOC]]

@@ Line 14: / Line 14: @@
 The goal of this project is to use the BeagleBoard as an USB sniffer. The host computer would be connected to the slave USB port of the BeagleBoard, and the device to be sniffed on the host USB port.
-The BeagleBoard would then forward USB data, while logging it.
+The BeagleBoard would then forward USB data, while logging it. In basic terms, there is a proxy driver running on the BeagleBoard, that acts both as a USB slave, and claims a USB device. According to the device descriptor, endpoints are activated on the USB slave controller, and packets are then forwarded back and forth between the host and the device.
-This presents the following advantages over a software-based solution: No software modification is required; support of proprietary OSes; allows debugging of new USB stacks; and possibly lower-level debugging of USB frames...
+This presents the following advantages over a software-based solution: No software modification is required; support of proprietary OSes; allows debugging of new USB stacks... However, this doesn't allow low-level debugging of USB transactions, that a hardware solution would allow. Also, the solution can only be as reliable as the USB host controller driver (which is well tested), and as the USB device controller driver (the MUSB driver in the Linux still has some bugs).
 == Build instructions ==

← Older revision		Revision as of 09:38, 9 August 2010
Line 176:		Line 176:
	=== Bandwidth allocation ===		=== Bandwidth allocation ===

		+	One major problem with the device emulation model, using a proxy driver, is about bandwidth allocation.

		+	The USB is polling-based, that is, the controller regularly interrogates all the endpoints of all the devices attached to it.
		+
		+	When a new USB device is added, some bandwidth is allocated for each of its endpoints, depending on some polling interval and packet size defined in the device descriptor. This bandwidth allocation defines the polling schedule, across all the endpoints, for all the devices present on the bus.
		+
		+	If insufficient bandwidth is available, the device may not work. For isochronous endpoints, the device usually defines several interfaces, with different bandwidth requirements (i.e., different packet sizes), and the driver can choose the appropriate interface, according to the bandwidth available on the bus.
		+
		+	One of the problems that could occur with our proxy driver, is that the host may decide to allocate more bandwidth than the bandwidth available on the USB host controller of the BeagleBoard. In that case, bandwidth allocation may fail on the BeagleBoard (with an <tt>ENOSPC</tt>, or <tt>-28</tt> error), and transfers on the affected endpoint would not work. From my experience, this seems to happen only with full-speed devices, that cannot be connected directly to the BeagleBoard, and need an intermediate USB hub.

	== MUSB testing code ==		== MUSB testing code ==

@@ Line 171: / Line 171: @@
 |-
 |}
 == MUSB testing code ==

@@ Line 158: / Line 158: @@
 * Many, for testing (only control is used for firmware loading)
 |style="background-color:#00ff00; font-style:bold" align="center"|OK
-|TBA
+|<tt>>=stable-20100809</tt>
 | Firmware loading using fxload works. The device then resets, and appears as a new device on the BeagleBoard. Restarting <tt>sniff</tt> claims the new device.
 |-
@@ Line 167: / Line 167: @@
 * EP2 OUT, bulk (JTAG emulation)
 |style="background-color:#00ff00; font-style:bold" align="center"|OK
-|TBA (latest stable has a problem with that)
+|<tt>>=stable-20100809</tt>
 | <tt>nios2-terminal</tt> works.
 |-

@@ Line 2: / Line 2: @@
 * Student: Nicolas Boichat
-* Mentors: Hunyue Yau, Laine Walker-Avina, Frans Meulenbroeks
+* Mentors: Hunyue Yau, Frans Meulenbroeks
 BeagleBoard project: [http://beagleboard.org/project/usbsniffer/ usbsniffer]

@@ Line 21: / Line 21: @@
 Latest recommended branches:
-* Kernel tree: <tt>stable-20100726</tt> [http://gitorious.org/beagleboard-usbsniffer/beagleboard-usbsniffer-kernel/commits/stable-20100726], OR
+* Kernel tree:
-<tt>stable-20100809</tt> [http://gitorious.org/beagleboard-usbsniffer/beagleboard-usbsniffer-kernel/commits/stable-20100809]: the latter may fix some problems with some devices, but will affect performance, for example when used with USB mass storage devices.
+**<tt>stable-20100726</tt> [http://gitorious.org/beagleboard-usbsniffer/beagleboard-usbsniffer-kernel/commits/stable-20100726], OR
 * Helper scripts: <tt>stable-20100730</tt> [http://gitorious.org/beagleboard-usbsniffer/helper-scripts/commits/stable-20100730].

@@ Line 20: / Line 20: @@
 == Build instructions ==
-To get the proxy driver to work, you need to follow these steps:
+Latest recommended branches:
-* Clone my kernel git tree. Use the <tt>stable-20100726</tt> branch [http://gitorious.org/beagleboard-usbsniffer/beagleboard-usbsniffer-kernel/commits/stable-20100726]. This can be done using the following commands:
+To get the proxy driver to work, you need to follow these steps:
   git clone git://gitorious.org/beagleboard-usbsniffer/beagleboard-usbsniffer-kernel.git
   cd beagleboard-usbsniffer-kernel
-  git checkout origin/stable-20100726 -b stable-20100726
+  git checkout origin/<i>branch</i> -b <i>branch</i>
 * Do not reconfigure the kernel (unless you need some extra modules): the git tree comes with a ready-made <tt>.config</tt>.
 * Compile and install the kernel.
@@ Line 40: / Line 43: @@
 ** The 2 packages can be found in <tt>$OE_BASE/build/tmp-angstrom_2008_1/deploy/glibc/ipk/armv7a</tt>: <tt>libpcap_1.1.1-r1.5_armv7a.ipk</tt> and <tt>tcpdump_4.1.1-r1.5_armv7a.ipk</tt>.
 ** Copy these on the BeagleBoard, and run <tt>opkg install <i>name</i>.ipk</tt> for both packages.
-* Clone the helper scripts git tree, branch <tt>stable-20100730</tt> [http://gitorious.org/beagleboard-usbsniffer/helper-scripts/commits/stable-20100730]:
+* Clone the helper scripts git tree:
   git clone git://gitorious.org/beagleboard-usbsniffer/helper-scripts.git
   cd helper-scripts/
-  git checkout origin/stable-20100730 -b stable-20100730
+  git checkout origin/<i>branch</i> -b <i>branch</i>
 * Copy the content of the <tt>arm</tt> directory to the BeagleBoard

@@ Line 46: / Line 46: @@
 * Copy the content of the <tt>arm</tt> directory to the BeagleBoard
-=== Usage instructions ===
+== Usage instructions ==
 Then, you have 2 options, the automatic way: