Debug Board v3 - Revision history

Hns: http://www.oocdlink.com is back again

2010-07-25T11:13:40Z

http://www.oocdlink.com is back again

2009-08-05T22:31:53Z

Grammar

2008-12-30T16:43:42Z

‎USB Hub

2008-11-19T18:10:31Z

Add link to schematics

2008-11-03T10:35:51Z

2008-10-29T20:14:50Z

+cat

2008-10-23T20:14:36Z

‎Suggestions: fix wiki syntax ('Users'->'User')

2008-10-23T20:13:07Z

‎Suggestions: Shameless self-promotion :)

2008-10-22T20:07:48Z

‎Suggestions

2008-10-22T20:06:57Z

‎Hardware connection

@@ Line 48: / Line 48: @@
 === JTAG using FT2232 ===
-Basically, we integrate a USB-JTAG adaptor similar to the [Amontec JTAGkey-tiny].  The actual reference design that we used (Thanks to Joern!) was found at http://www.oocdlink.com (but the domain has gone).
+Basically, we integrate a USB-JTAG adaptor similar to the [Amontec JTAGkey-tiny].  The actual reference design that we used (Thanks to Joern!) was found at http://www.oocdlink.com.
 This provides us full JTAG debugging, at about 150times the speed of the [[wiggler]]

@@ Line 42: / Line 42: @@
 Using the hub, you can have access to the phone, JTAG and serial simultaneously, through a single USB cable.
-You can actually even charge the phone (100mA slow charge) using that downstream port.
+You can charge the phone (100mA slow charge) using that downstream port.
 For the USB hub function, we use the TUSB2046B chip.
@@ Line 55: / Line 55: @@
 * the phone (via debug flex cable)
 * A separate 20-pin header using standard ARM-JTAG pinout
-** this allows the user to use this device as JTAG adaptor even for other arm-based devices
+** Allows users to use this device as JTAG adaptor for other arm-based devices
 === Serial Port ===

@@ Line 44: / Line 44: @@
 You can actually even charge the phone (100mA slow charge) using that downstream port.
-For the ISB hub function, we use the TUSB2046B chip.
+For the USB hub function, we use the TUSB2046B chip.
 === JTAG using FT2232 ===

@@ Line 27: / Line 27: @@
 * [[Debug Board#JTAG using FT2232 | JTAG using FT2232]]
 * [[Debug Board#Serial Port | Serial Port]]
 === USB Hub ===

@@ Line 150: / Line 150: @@
 rmmod ftdi_sio
 modprobe ftdi_sio vendor=0x1457 product=0x5118
@@ Line 180: / Line 181: @@
 ===== Serial Port =====
-The Linux kernel of your host system will create a virtual serial device called '''/dev/ttyUSBx''' where 'x' is a sequentially assigned number.  If you don't have any other USB serial converters attached to your machine, the device name will be '''/dev/ttyUSB0'''.
+The Linux kernel of your host system will create a virtual serial device called '''/dev/ttyUSBx''' where 'x' is a sequentially assigned number.  If you don't have any other USB serial converters attached to your machine, the device name will be '''/dev/ttyUSB1'''
 You can use your favourite terminal emualtor (minicom, cu, zc, ...) just like for any other/real serial port. You may use gdb as well (eg. target remote /dev/ttya).

← Older revision		Revision as of 20:14, 29 October 2008
Line 223:		Line 223:
	[[Category:Neo1973 Hardware]]		[[Category:Neo1973 Hardware]]
	[[Category:Neo1973 Hardware Debugging]]		[[Category:Neo1973 Hardware Debugging]]
		+	[[Category:Neo FreeRunner Hardware]]

@@ Line 172: / Line 172: @@
 === Suggestions ===
-* [[Users:Cfriedt]] 20081021 The Debug Board v3 uses 3.3V signalling levels on J1 (the 20-pin ARM JTAG port). Many other ARM devices use 1.8V signalling. For the next Dboard hardware revision, I would suggest using the same level-shifter as the FlySwatter. The FlySwatter uses two SN74AVC4T245 ([http://elinux.org/upload/4/46/Flyswatter-schematic.pdf ref]) buffers to provide a signalling range of 1.2V to 3.6V ([http://elinux.org/Flyswatter ref]).
+* [[User:Cfriedt]] 20081021 The Debug Board v3 uses 3.3V signalling levels on J1 (the 20-pin ARM JTAG port). Many other ARM devices use 1.8V signalling. For the next Dboard hardware revision, I would suggest using the same level-shifter as the FlySwatter. The FlySwatter uses two SN74AVC4T245 ([http://elinux.org/upload/4/46/Flyswatter-schematic.pdf ref]) buffers to provide a signalling range of 1.2V to 3.6V ([http://elinux.org/Flyswatter ref]).
 === Actually using it ===

← Older revision		Revision as of 20:06, 22 October 2008
Line 169:		Line 169:

	The recommended connection sequence given in [[Debug Board v2#Hardware connection]] may not work for debug board v3 and the FreeRunner. It seems impossible to turn on the FreeRunner after plugging the FreeRunner USB cable into the PC, but before plugging the debug board USB cable into the PC. After the debug board is powered by the PC, the FreeRunner should start.		The recommended connection sequence given in [[Debug Board v2#Hardware connection]] may not work for debug board v3 and the FreeRunner. It seems impossible to turn on the FreeRunner after plugging the FreeRunner USB cable into the PC, but before plugging the debug board USB cable into the PC. After the debug board is powered by the PC, the FreeRunner should start.
		+
		+	=== Suggestions ===
		+
		+	The Debug Board v3 uses 3.3V signalling levels on J1 (the 20-pin ARM JTAG port). Many other ARM devices use 1.8V signalling. For the next Dboard hardware revision, I would suggest using the same level-shifter as the FlySwatter. The FlySwatter uses two SN74AVC4T245 ([http://elinux.org/upload/4/46/Flyswatter-schematic.pdf ref]) buffers to provide a compatibility range of 1.2V and 3.6V ([http://elinux.org/Flyswatter ref]).

	=== Actually using it ===		=== Actually using it ===