JTAG & OpenOCD for LS-Pro - Revision history

Kenatonline at 11:02, 5 February 2011

Kenatonline — Sat, 05 Feb 2011 11:02:51 GMT

← Older revision		Revision as of 11:02, 5 February 2011
Line 383:		Line 383:
	Manual available in pdf format : [http://buffalo.nas-central.org/download/Users/davy_gravy/openocd_svn-r479.pdf OpenOCD Manual for svn r479]		Manual available in pdf format : [http://buffalo.nas-central.org/download/Users/davy_gravy/openocd_svn-r479.pdf OpenOCD Manual for svn r479]
	{{Template:Articles\|LSPro\|Hardware\|JTAG\|UBoot}}		{{Template:Articles\|LSPro\|Hardware\|JTAG\|UBoot}}
-
-	~~==External Links==~~
-	~~[http://mackeeper.zeobit.com/mac-data-recovery data rescue mac]~~

Roderio at 13:06, 28 October 2010

Roderio — Thu, 28 Oct 2010 13:06:41 GMT

← Older revision		Revision as of 13:06, 28 October 2010
Line 383:		Line 383:
	Manual available in pdf format : [http://buffalo.nas-central.org/download/Users/davy_gravy/openocd_svn-r479.pdf OpenOCD Manual for svn r479]		Manual available in pdf format : [http://buffalo.nas-central.org/download/Users/davy_gravy/openocd_svn-r479.pdf OpenOCD Manual for svn r479]
	{{Template:Articles\|LSPro\|Hardware\|JTAG\|UBoot}}		{{Template:Articles\|LSPro\|Hardware\|JTAG\|UBoot}}
		+
		+	==External Links==
		+	[http://mackeeper.zeobit.com/mac-data-recovery data rescue mac]

Davygravy at 03:35, 9 April 2009

Davygravy — Thu, 09 Apr 2009 03:35:12 GMT

← Older revision		Revision as of 03:35, 9 April 2009
Line 381:		Line 381:
	Manual availabe in pdf format : [http://buffalo.nas-central.org/download/Users/davy_gravy/openocd_svn-r335.pdf OpenOCD Manual for svn r335]		Manual availabe in pdf format : [http://buffalo.nas-central.org/download/Users/davy_gravy/openocd_svn-r335.pdf OpenOCD Manual for svn r335]
	====for OpenOCD svn r479 - with newer commands====		====for OpenOCD svn r479 - with newer commands====
-	Manual ~~availabe~~ in pdf format : [http://buffalo.nas-central.org/download/Users/davy_gravy/openocd_svn-r479.pdf OpenOCD Manual for svn r479]	+	Manual available in pdf format : [http://buffalo.nas-central.org/download/Users/davy_gravy/openocd_svn-r479.pdf OpenOCD Manual for svn r479]
	{{Template:Articles\|LSPro\|Hardware\|JTAG\|UBoot}}		{{Template:Articles\|LSPro\|Hardware\|JTAG\|UBoot}}

Amontec: /* Getting, Compiling and Configuring OpenOCD */

Amontec — Sun, 01 Feb 2009 19:26:11 GMT

Getting, Compiling and Configuring OpenOCD

← Older revision		Revision as of 19:26, 1 February 2009
Line 61:		Line 61:
	ft2232_vid_pid 0x15ba 0x0004		ft2232_vid_pid 0x15ba 0x0004
	# Or for the Amontec JTAGkey		# Or for the Amontec JTAGkey
-	#ft2232_layout "~~olimex-jtag~~"	+	#ft2232_layout "jtagkey"
	#ft2232_vid_pid 0x0403 0xcff8		#ft2232_vid_pid 0x0403 0xcff8

Amontec: /* Getting, Compiling and Configuring OpenOCD */

Amontec — Sun, 01 Feb 2009 19:25:31 GMT

Getting, Compiling and Configuring OpenOCD

← Older revision		Revision as of 19:25, 1 February 2009
Line 35:		Line 35:


-	*'''Compiling OpenOCD''' - See [http://openfacts.berlios.de/index-en.phtml?title=Building_OpenOCD Building OpenOCD] for full details. The directions are listed below for using it with the Olimex JTAG USB TINY adapter, which is ftdi-based. Read the INSTALL file for details on building it for parallel port Wiggler devices.	+	*'''Compiling OpenOCD''' - See [http://openfacts.berlios.de/index-en.phtml?title=Building_OpenOCD Building OpenOCD] for full details. The directions are listed below for using it with the [http://www.amontec.com/jtagkey.shtml Amontec JTAGkey] and the Olimex JTAG USB TINY adapter, which are ftdi-based. Read the INSTALL file for details on building it for parallel port Wiggler devices.
	**Install libftdi (http://www.intra2net.com/opensource/ftdi/) or libftd2xx (http://www.ftdichip.com/Drivers/D2XX.htm). Most accounts seem to indicate that more users have better luck with libftdi (which is available as a package for Ubuntu, for instance.)		**Install libftdi (http://www.intra2net.com/opensource/ftdi/) or libftd2xx (http://www.ftdichip.com/Drivers/D2XX.htm). Most accounts seem to indicate that more users have better luck with libftdi (which is available as a package for Ubuntu, for instance.)
	**Build and install OpenOCD. Download it from the downloads on our site, or from svn at the OpenOCD site. For svn revision 335, a patch was necessary (see Item #5 in the [http://buffalo.nas-central.org/index.php/JTAG_%26_OpenOCD_for_LS-Pro#Notes notes] at the bottom). Then bootstrap, configure, make and make install.		**Build and install OpenOCD. Download it from the downloads on our site, or from svn at the OpenOCD site. For svn revision 335, a patch was necessary (see Item #5 in the [http://buffalo.nas-central.org/index.php/JTAG_%26_OpenOCD_for_LS-Pro#Notes notes] at the bottom). Then bootstrap, configure, make and make install.
Line 60:		Line 60:
	ft2232_layout "olimex-jtag"		ft2232_layout "olimex-jtag"
	ft2232_vid_pid 0x15ba 0x0004		ft2232_vid_pid 0x15ba 0x0004
		+	# Or for the Amontec JTAGkey
		+	#ft2232_layout "olimex-jtag"
		+	#ft2232_vid_pid 0x0403 0xcff8

	# use combined on interfaces or targets that can't set TRST/SRST separately		# use combined on interfaces or targets that can't set TRST/SRST separately

Amontec: /* Hardware */

Amontec — Sun, 01 Feb 2009 19:20:01 GMT

Hardware

← Older revision		Revision as of 19:20, 1 February 2009
Line 22:		Line 22:
	*An LS Pro (or LS Live, though it hasn't been tested on the Live yet) - "...some disassembly required..."		*An LS Pro (or LS Live, though it hasn't been tested on the Live yet) - "...some disassembly required..."
	*JTAG headers already attached to your ARM-based LinkStation's board (see [ Add a JTAG Port] for details - you may want to consider low profile headers)		*JTAG headers already attached to your ARM-based LinkStation's board (see [ Add a JTAG Port] for details - you may want to consider low profile headers)
-	*JTAG adapter like the Olimex ARM-USB-TINY (tested) or a Wiggler (Wigglers and other paraport adapters reportedly work, but seem slower than USB)	+	*JTAG adapter like the Olimex ARM-USB-TINY (tested), the Amontec JTAGkey or a Wiggler (Wigglers and other paraport adapters reportedly work, but seem slower than USB)
	*an x86 desktop/laptop running Linux (tested w/ Ubuntu 7.10)		*an x86 desktop/laptop running Linux (tested w/ Ubuntu 7.10)
-

	===Getting, Compiling and Configuring OpenOCD===		===Getting, Compiling and Configuring OpenOCD===

Davy gravy: /* Getting, Compiling and Configuring OpenOCD */

Davy gravy — Sun, 31 Aug 2008 18:39:08 GMT

Getting, Compiling and Configuring OpenOCD

← Older revision		Revision as of 18:39, 31 August 2008
Line 28:		Line 28:
	===Getting, Compiling and Configuring OpenOCD===		===Getting, Compiling and Configuring OpenOCD===
	The OCD software we use is [http://openfacts.berlios.de/index-en.phtml?title=Open_On-Chip_Debugger OpenOCD], created by Dominic Rath. Read through the docs there for lots of useful information. ''' [http://buffalo.nas-central.org/index.php/JTAG_%26_OpenOCD_for_LS-Pro#Manuals_for_OpenOCD Manuals are also available in pdf form.] ''' In terms of getting OpenOCD source, you basically have two options here:		The OCD software we use is [http://openfacts.berlios.de/index-en.phtml?title=Open_On-Chip_Debugger OpenOCD], created by Dominic Rath. Read through the docs there for lots of useful information. ''' [http://buffalo.nas-central.org/index.php/JTAG_%26_OpenOCD_for_LS-Pro#Manuals_for_OpenOCD Manuals are also available in pdf form.] ''' In terms of getting OpenOCD source, you basically have two options here:
-	*Build it from [http://openfacts.berlios.de/index-en.phtml?title=Building_OpenOCD svn] for the Feroceon support and the latest (perhaps bleeding edge) features (For svn revision 335, a patch was necessary-see Item #5 in the [http://buffalo.nas-central.org/index.php/JTAG_%26_OpenOCD_for_LS-Pro#Notes notes] at the bottom~~), or~~	+	*Build it from [http://openfacts.berlios.de/index-en.phtml?title=Building_OpenOCD svn] for the Feroceon support and the latest (perhaps bleeding edge) features
		+	**Users are encouraged to try rev 953 or later as it seems that the halt problem may be fixed in it - perhaps no patch needed
		+	**For svn revision 335, a patch was necessary-see Item #5 in the [http://buffalo.nas-central.org/index.php/JTAG_%26_OpenOCD_for_LS-Pro#Notes notes] at the bottom
	*build it from our altered pre-Feroceon source, [http://downloads.nas-central.org/ALL_LS_KB_ARM9/openocd-lspro.tgz available for download from here]. Note that the config file in this package, found in docs/configs/lsp_wig.cfg is already set up and tested with parallel port interfaces, like for the Wiggler.		*build it from our altered pre-Feroceon source, [http://downloads.nas-central.org/ALL_LS_KB_ARM9/openocd-lspro.tgz available for download from here]. Note that the config file in this package, found in docs/configs/lsp_wig.cfg is already set up and tested with parallel port interfaces, like for the Wiggler.
	*Don't expect great results from the OpenOCD version that is packaged for Ubuntu or other distros, as it is somewhat dated at this point and doesn't contain the config file that members here have already set up.		*Don't expect great results from the OpenOCD version that is packaged for Ubuntu or other distros, as it is somewhat dated at this point and doesn't contain the config file that members here have already set up.

Davy gravy: /* Flashing U-Boot to Your LS Pro */

Davy gravy — Wed, 23 Apr 2008 11:58:12 GMT

Flashing U-Boot to Your LS Pro

← Older revision		Revision as of 11:58, 23 April 2008
Line 174:		Line 174:
	'''7. Write the UBoot image to flash.''' This may take anywhere from about an hour up to 5 or 6 hours. Do not interrupt the process. Execute the following:		'''7. Write the UBoot image to flash.''' This may take anywhere from about an hour up to 5 or 6 hours. Do not interrupt the process. Execute the following:
	flash write 0 lspstock052207.bin 0xfffc0000		flash write 0 lspstock052207.bin 0xfffc0000
-	The file to be used as an image for flash should be changed to fit your situation (the one shown is for a LS Pro V1).	+	The file to be used as an image for flash should be changed to fit your situation (the one shown is for a LS Pro V1) Note that with this command form it is expecting a full 256kb image. If you don't have a full 256kb image of the new uboot that you may have just built, you can always flash in a stock 256kb image, and then flash the new uboot from within uboot, and then dump out a 256kb image of it using mtd and dd commands.
	> flash write 0 lspstock052207.bin 0xfffc0000		> flash write 0 lspstock052207.bin 0xfffc0000
	wrote file lspstock052207.bin to flash bank 0 at offset 0xfffc0000 in 12107s 811284us		wrote file lspstock052207.bin to flash bank 0 at offset 0xfffc0000 in 12107s 811284us
Line 189:		Line 189:

	'''9. Power down and restart.''' This is the moment of truth. Power down the LS by either holding the power button (safest) or unplugging it. Now restart. A serial cable attachment will be your friend here as it will give an indication of success with the output of Uboot scrolling by.		'''9. Power down and restart.''' This is the moment of truth. Power down the LS by either holding the power button (safest) or unplugging it. Now restart. A serial cable attachment will be your friend here as it will give an indication of success with the output of Uboot scrolling by.
-
-

	==Troubleshooting==		==Troubleshooting==

Davy gravy: /* DISCLAIMER */

Davy gravy — Wed, 09 Apr 2008 21:54:21 GMT

DISCLAIMER

← Older revision		Revision as of 21:54, 9 April 2008
Line 17:		Line 17:
	===DISCLAIMER===		===DISCLAIMER===
	<font color=red size=large> '''CAUTION : USE AT YOUR OWN RISK. IT IS POSSIBLE TO BRICK ONE'S BOX WITH THESE METHODS. UNBRICKING IS NOT GUARANTEED. YOU HAVE BEEN WARNED.''' These directions have been tested and checked on a LSProV2. YMMV.</font>		<font color=red size=large> '''CAUTION : USE AT YOUR OWN RISK. IT IS POSSIBLE TO BRICK ONE'S BOX WITH THESE METHODS. UNBRICKING IS NOT GUARANTEED. YOU HAVE BEEN WARNED.''' These directions have been tested and checked on a LSProV2. YMMV.</font>
-		+	{{Brick\| WARNING: Modifying your LinkStation or Kuro can void your warranty. Incorrect flashing procedures can turn your unit into a Brick. Flashing success is not guaranteed. Do not flash your box unless your are willing to use JTAG to recover it, in the event that there is an unforeseen problem. JTAG recovery generally works well, but is not a guarantee of recovery from bricking one's box.}}

	===Hardware===		===Hardware===

Davy gravy: /* Manuals for OpenOCD */

Davy gravy — Sat, 15 Mar 2008 01:45:08 GMT

Manuals for OpenOCD

← Older revision		Revision as of 01:45, 15 March 2008
Line 375:		Line 375:
	dump_binary [DEPRECATED] dump_binary <file> <address> <size>		dump_binary [DEPRECATED] dump_binary <file> <address> <size>
	===Manuals for OpenOCD===		===Manuals for OpenOCD===
		+	Manuals for the latest versions can be made by cd-ing to the source and doing "make pdf". Ready-made manuals are provided here for your convenience.
	====for OpenOCD svn r335====		====for OpenOCD svn r335====
	Manual availabe in pdf format : [http://buffalo.nas-central.org/download/Users/davy_gravy/openocd_svn-r335.pdf OpenOCD Manual for svn r335]		Manual availabe in pdf format : [http://buffalo.nas-central.org/download/Users/davy_gravy/openocd_svn-r335.pdf OpenOCD Manual for svn r335]