U-boot musb gadget support - Revision history

Russ.Dill@gmail.com: Add ttypersist

2012-03-15T03:34:58Z

Add ttypersist

2010-02-19T17:10:20Z

‎Getting started

2010-02-11T09:37:25Z

2010-01-28T17:51:49Z

2009-07-23T14:57:05Z

‎Getting the source code

2009-05-04T01:21:29Z

‎Getting started

2009-04-02T15:27:32Z

Make code section a code section

2009-04-02T15:25:57Z

Add issues section

2009-01-25T13:24:45Z

2009-01-25T13:24:04Z

← Older revision		Revision as of 03:34, 15 March 2012
Line 56:		Line 56:
	Directly after the last line with a 'GOTO="nm_modem_probe_end"' statement.		Directly after the last line with a 'GOTO="nm_modem_probe_end"' statement.

−	Minicom doesn't work so well if the device drops out from beneath it. Check out [http://gitorious.org/projects/clonetty clonetty] for a workaround~~. It does this by creating a psuedo tty that minicom can open~~.	+	Minicom doesn't work so well if the device drops out from beneath it. Check out [https://github.com/russdill/ttypersist ttypersist] or [http://gitorious.org/projects/clonetty clonetty] for a workaround.

@@ Line 29: / Line 29: @@
 === Getting started ===
-* Load your new u-boot.bin image into the board using any of the existing methods. If you have a beagle running already a working u-boot, you can load it by serial using the 'loady' command and minicom or 'sb' (be sure to have lszrz installed in your distro). Then erasing the u-boot in flash and reflashing the new image with the following commands:
+* Load your new u-boot.bin image into the board using any of the existing methods. If you have a beagle running already a working u-boot, you can load it by serial using the 'loady' command and minicom with 'sb' (be sure to have lszrz installed in your distro). Then erasing the u-boot in flash and reflashing the new image with the following commands:
   nand unlock

@@ Line 1: / Line 1: @@
 [[Category: Linux]]
 [[Category: OMAP]]
 The code for musb gadget support is currently available on the omap3-dev-usb branch of the [http://www.sakoman.net/cgi-bin/gitweb.cgi?p=u-boot-omap3.git;a=summary Beagle U-Boot git repository].

← Older revision		Revision as of 17:51, 28 January 2010
Line 55:		Line 55:
	Directly after the last line with a 'GOTO="nm_modem_probe_end"' statement.		Directly after the last line with a 'GOTO="nm_modem_probe_end"' statement.

−	Minicom doesn't work so well if the device drops out from beneath it. Check out [http://gitorious.org/projects/clonetty clonetty] for a workaround.	+	Minicom doesn't work so well if the device drops out from beneath it. Check out [http://gitorious.org/projects/clonetty clonetty] for a workaround. It does this by creating a psuedo tty that minicom can open.

@@ Line 17: / Line 17: @@
 Checkout the git source for the musb gadget support from the [http://www.sakoman.net/cgi-bin/gitweb.cgi?p=u-boot-omap3.git;a=summary Beagle U-Boot git repository]. Get it by:
-  git clone git://www.sakoman.net/git/u-boot-omap3.git
+  git clone git://gitorious.org/u-boot-omap3/mainline.git
   cd u-boot-omap3
   git checkout --track -b omap3-dev-usb origin/omap3-dev-usb

@@ Line 39: / Line 39: @@
 * Attach a mini-b USB cable to the beagle. Your host should recognize an ACM CDC device (works out of the box on Linux and OS X).
 * If you want to have the u-boot console over USB use the following command:
-  setenv usbtty=cdc_acm
+  setenv usbtty cdc_acm
   saveenv
 Then reboot, then:

@@ Line 50: / Line 50: @@
 Network Manager will see this device as a modem and attempt to send it AT commands. To avoid this, edit /lib/udev/rules.d/77-nm-probe-modem-capabilities.rules and add the following lines:
-ATTRS{idVendor}=="0525", ATTRS{idProduct}=="a4a7", GOTO="nm_modem_probe_end"
+ ATTRS{idVendor}=="0525", ATTRS{idProduct}=="a4a7", GOTO="nm_modem_probe_end"
-ATTRS{idVendor}=="0525", ATTRS{idProduct}=="a4aa", GOTO="nm_modem_probe_end"
+ ATTRS{idVendor}=="0525", ATTRS{idProduct}=="a4aa", GOTO="nm_modem_probe_end"
 Directly after the last line with a 'GOTO="nm_modem_probe_end"' statement.
 Minicom doesn't work so well if the device drops out from beneath it. Check out [http://gitorious.org/projects/clonetty clonetty] for a workaround.

← Older revision		Revision as of 15:25, 2 April 2009
Line 45:		Line 45:

	Now when you plug the device into your Linux host machine you should be able to talk over serial using minicom,putty,etc over /dev/ttyACM0.		Now when you plug the device into your Linux host machine you should be able to talk over serial using minicom,putty,etc over /dev/ttyACM0.
		+
		+	=== Issues ===
		+
		+	Network Manager will see this device as a modem and attempt to send it AT commands. To avoid this, edit /lib/udev/rules.d/77-nm-probe-modem-capabilities.rules and add the following lines:
		+
		+	ATTRS{idVendor}=="0525", ATTRS{idProduct}=="a4a7", GOTO="nm_modem_probe_end"
		+	ATTRS{idVendor}=="0525", ATTRS{idProduct}=="a4aa", GOTO="nm_modem_probe_end"
		+
		+	Directly after the last line with a 'GOTO="nm_modem_probe_end"' statement.
		+
		+	Minicom doesn't work so well if the device drops out from beneath it. Check out [http://gitorious.org/projects/clonetty clonetty] for a workaround.

@@ Line 34: / Line 34: @@
   nand write.i 80000000 80000 160000 #(depending on the your configuration, your start address might be 82000000)
-WARNING: in the previous instructions, please verified that your u-boot image was loaded on the address 80000000 (the last line from the ymodem transmission says where the image was loaded). In some board I have see it uploads to 82000000 instead of 80000000
+WARNING: in the previous instructions, please verified that your u-boot image was loaded on the address 80000000 (the last line from the ymodem transmission says where the image was loaded). On some boards I have see it uploads to 82000000 instead of 80000000
 * Reboot your board