JTAG instructions and hints - Revision history

Davy gravy: /* Arm-based boxes */

Davy gravy — Sun, 02 Mar 2008 13:07:08 GMT

Arm-based boxes

← Older revision		Revision as of 13:07, 2 March 2008
Line 24:		Line 24:
	===LS2===		===LS2===
	==Arm-based boxes==		==Arm-based boxes==
-	~~Please see~~ the article at [http://buffalo.nas-central.org/index.php/JTAG_%26_OpenOCD_for_LS-Pro JTAG & OpenOCD for the LS-Pro] for complete details and instructions.	+	===LS Pro and LS Live===
		+	See the article at [http://buffalo.nas-central.org/index.php/JTAG_%26_OpenOCD_for_LS-Pro JTAG & OpenOCD for the LS-Pro] for complete details and instructions.

	===Terastation Pro v2/Terastation Live (arm9)===		===Terastation Pro v2/Terastation Live (arm9)===

Davy gravy: /* Arm-based boxes */

Davy gravy — Sat, 01 Mar 2008 21:53:51 GMT

Arm-based boxes

Show changes

Davy gravy: /* Starting Your LinkStation/KuroPro & OpenOCD, Connecting with Telnet and Getting Flash Access */

Davy gravy — Mon, 25 Feb 2008 13:25:53 GMT

Starting Your LinkStation/KuroPro & OpenOCD, Connecting with Telnet and Getting Flash Access

← Older revision		Revision as of 13:25, 25 February 2008
Line 209:		Line 209:
	The error seems commonplace to most of us that have used it. Until we know otherwise, most of us are assuming it is not a huge problem.		The error seems commonplace to most of us that have used it. Until we know otherwise, most of us are assuming it is not a huge problem.
	OpenOCD is now running.		OpenOCD is now running.
-	*In a second terminal window, start telnet pointed to loopback, port 4444. This window is where you will control the communication and commands to your device via the jtag interface. You will have to halt your processor, verify the flash banks, and probe them (so that they are recognized properly). '''Note that your processor must be halted - this is a requirement for the probing the flash.'''	+	*In a second terminal window, start telnet pointed to loopback, port 4444. This window is where you will control the communication and commands to your device via the jtag interface. You will have to halt your processor (as quickly as is possible), verify the flash banks, and probe them (so that they are recognized properly). '''Note that your processor must be halted - this is a requirement for the probing the flash.'''
	Execute the following commands:		Execute the following commands:
		+	telnet localhost 4444
	halt		halt
	flash banks		flash banks

Davy gravy: /* Background and Required Hardware Software */

Davy gravy — Mon, 25 Feb 2008 12:50:32 GMT

Background and Required Hardware Software

← Older revision		Revision as of 12:50, 25 February 2008
Line 50:		Line 50:
	'''CAUTION : USE AT YOUR OWN RISK. IT IS POSSIBLE TO BRICK ONE'S BOX WITH THESE METHODS. UNBRICKING IS NOT GUARANTEED.'''		'''CAUTION : USE AT YOUR OWN RISK. IT IS POSSIBLE TO BRICK ONE'S BOX WITH THESE METHODS. UNBRICKING IS NOT GUARANTEED.'''
	These directions have been tested and checked on a LSProV2. The OCD software we use is [http://openfacts.berlios.de/index-en.phtml?title=Open_On-Chip_Debugger OpenOCD], created by Dominic Rath.		These directions have been tested and checked on a LSProV2. The OCD software we use is [http://openfacts.berlios.de/index-en.phtml?title=Open_On-Chip_Debugger OpenOCD], created by Dominic Rath.
-	*[http://openfacts.berlios.de/index-en.phtml?title=Open_On-Chip_Debugger OpenOCD]. You should probably work with the version that most of us here have used - [http://downloads.nas-central.org/ALL_LS_KB_ARM9/openocd-lspro.tgz download it from here].	+	*[http://openfacts.berlios.de/index-en.phtml?title=Open_On-Chip_Debugger OpenOCD]. You should probably work with the version that most of us here have used - [http://downloads.nas-central.org/ALL_LS_KB_ARM9/openocd-lspro.tgz download it from here]. You can also build it from svn - see note #4 at the bottom.
	*JTAG adapter like the Olimex ARM-USB-TINY (tested) or a Wiggler (Wigglers and other paraport adapters seem slower than USB).		*JTAG adapter like the Olimex ARM-USB-TINY (tested) or a Wiggler (Wigglers and other paraport adapters 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)

Davy gravy: /* Background and Required Hardware Software */

Davy gravy — Mon, 25 Feb 2008 03:54:47 GMT

Background and Required Hardware Software

← Older revision		Revision as of 03:54, 25 February 2008
Line 48:		Line 48:
	0003c000 (RO) 0003d000 (RO) 0003e000 (RO) 0003f000		0003c000 (RO) 0003d000 (RO) 0003e000 (RO) 0003f000
	====Background and Required Hardware Software====		====Background and Required Hardware Software====
-	CAUTION : USE AT YOUR OWN RISK. IT IS POSSIBLE TO BRICK ONE'S BOX WITH THESE METHODS. UNBRICKING IS NOT GUARANTEED.	+	'''CAUTION : USE AT YOUR OWN RISK. IT IS POSSIBLE TO BRICK ONE'S BOX WITH THESE METHODS. UNBRICKING IS NOT GUARANTEED.'''
	These directions have been tested and checked on a LSProV2. The OCD software we use is [http://openfacts.berlios.de/index-en.phtml?title=Open_On-Chip_Debugger OpenOCD], created by Dominic Rath.		These directions have been tested and checked on a LSProV2. The OCD software we use is [http://openfacts.berlios.de/index-en.phtml?title=Open_On-Chip_Debugger OpenOCD], created by Dominic Rath.
	*[http://openfacts.berlios.de/index-en.phtml?title=Open_On-Chip_Debugger OpenOCD]. You should probably work with the version that most of us here have used - [http://downloads.nas-central.org/ALL_LS_KB_ARM9/openocd-lspro.tgz download it from here].		*[http://openfacts.berlios.de/index-en.phtml?title=Open_On-Chip_Debugger OpenOCD]. You should probably work with the version that most of us here have used - [http://downloads.nas-central.org/ALL_LS_KB_ARM9/openocd-lspro.tgz download it from here].

Davy gravy: /* Setting Up OpenOCD */

Davy gravy — Mon, 25 Feb 2008 03:53:41 GMT

Setting Up OpenOCD

← Older revision		Revision as of 03:53, 25 February 2008
Line 65:		Line 65:
	none /proc/bus/usb usbfs defaults,devmode=0666 0 0		none /proc/bus/usb usbfs defaults,devmode=0666 0 0

-	If you are using a parallel port Wiggler, you should read the literature and docs in the source, as they will guide you on what to do in terms of configuring before building.	+	If you are using a parallel port Wiggler, you should read the literature and docs in the source, as they will guide you on what to do in terms of configuring before building.

Davy gravy: /* Setting Up OpenOCD */

Davy gravy — Mon, 25 Feb 2008 03:53:19 GMT

Setting Up OpenOCD

← Older revision		Revision as of 03:53, 25 February 2008
Line 56:		Line 56:

	====Setting Up OpenOCD====		====Setting Up OpenOCD====
-	*Compiling: 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: 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.
	**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. Then configure, make and make install.		**Build and install OpenOCD. Download it from the downloads on our site, or from svn at the OpenOCD site. Then configure, make and make install.
-	./configure --enable-ft2232_libftdi	+	./configure --enable-ft2232_libftdi
	make		make
	make install		make install
Line 65:		Line 65:
	none /proc/bus/usb usbfs defaults,devmode=0666 0 0		none /proc/bus/usb usbfs defaults,devmode=0666 0 0

-	If you are using a parallel port Wiggler, you should read the literature and docs in the source, as they will guide you on what to do in terms of configuring before building.	+	If you are using a parallel port Wiggler, you should read the literature and docs in the source, as they will guide you on what to do in terms of configuring before building.
		+
		+
		+	*Configuring OpenOCD - Again, see [http://openfacts.berlios.de/index-en.phtml?title=OpenOCD_configuration Configuring OpenOCD] for details. Hints below - here is a config file that was used to flash a LS Pro V2 using OpenOCD svn revision 335, with an Olimex ARM-USB-TINY unit. (Note:The config file in the openocd-package in the downloads section is set up for parallel port Wiggler devices.)
		+	# daemon config
		+	telnet_port 4444
		+	gdb_port 3333
		+	daemon_startup attach
		+
		+
		+	# interface
		+	jtag_speed 0
		+	interface ft2232
		+	ft2232_layout "olimex-jtag"
		+	ft2232_vid_pid 0x15ba 0x0004
		+
		+	# use combined on interfaces or targets that can't set TRST/SRST separately
		+	reset_config srst_only
		+	#reset_config trst_and_srst
		+
		+
		+	# jtag scan chain
		+	#format L IRC IRCM IDCODE (Length, IR Capture, IR Capture Mask, IDCODE)
		+	jtag_device 4 0x1 0xf 0xe
		+
		+
		+	#jtag_nsrst_delay 500
		+	#jtag_ntrst_delay 500
		+
		+
		+
		+	# target configuration
		+	# target <type> <endianess> <reset_mode>
		+	# if chain_pos is not zero it seg faults
		+	target arm926ejs little reset_init 0
		+	#target feroceon little reset_init 0
		+	run_and_halt_time 0 30
		+	#working_area 0 0xc8010000 0x400 nobackup
		+
		+
		+	# flash configuration
		+	# flash bank <driver> <base> <size> <chip_width> <bus_width> [driver_options ...]
		+	#flash bank cfi 0xfffc0000 0x00040000 1 1 0 jedec_probe
		+	flash bank cfi 0xfffc0000 0x00040000 1 1 0 jedec_probe
		+


-	*Configuring OpenOCD - Again, see [http://openfacts.berlios.de/index-en.phtml?title=OpenOCD_configuration Configuring OpenOCD] for details. Hints below.

Davy gravy: /* Reference, Notes and Special Situations */

Davy gravy — Mon, 25 Feb 2008 03:41:51 GMT

Reference, Notes and Special Situations

← Older revision		Revision as of 03:41, 25 February 2008
Line 278:		Line 278:
	Connection closed by foreign host.		Connection closed by foreign host.
	root@bytebaker-i686:/home/davygravy#		root@bytebaker-i686:/home/davygravy#
-	#YMMV. Good Luck.	+	YMMV. Good Luck.

	===Terastation Pro v2/Terastation Live (arm9)===		===Terastation Pro v2/Terastation Live (arm9)===

Davy gravy: /* Starting OpenOCD, Connecting with Telnet and Getting Flash Access */

Davy gravy — Mon, 25 Feb 2008 03:40:28 GMT

Starting OpenOCD, Connecting with Telnet and Getting Flash Access

← Older revision		Revision as of 03:40, 25 February 2008
Line 157:		Line 157:
	dump_binary [DEPRECATED] dump_binary <file> <address> <size>		dump_binary [DEPRECATED] dump_binary <file> <address> <size>

-	====Starting OpenOCD, Connecting with Telnet and Getting Flash Access====	+	====Starting Your LinkStation/KuroPro & OpenOCD, Connecting with Telnet and Getting Flash Access====
-	~~You~~ will need to do both of the following as root (note that some users state that there is an advantage in doing these in rapid succession):	+	*Start your ARM-based LinkStation by '''first''' ''holding the reset button on'', and then pressing the POWER ON/OFF button. After it powers up you will immediately here a musical tone.
		+	*Once you hear the tone, you will need to do both of the following as root (note that some users state that there is an advantage in doing these in rapid succession).
	*In a terminal window, cd to your OpenOCD config file and start it. From this window you will see only diagnostic information, mainly. Change directory to the docs/configs in the openocd directory. Then start openocd, directing it to use the config file that you have set up previously.		*In a terminal window, cd to your OpenOCD config file and start it. From this window you will see only diagnostic information, mainly. Change directory to the docs/configs in the openocd directory. Then start openocd, directing it to use the config file that you have set up previously.
	root@bitbaker-i686:/home/davygravy/Desktop/configs# openocd -f lsp_wig.cfg		root@bitbaker-i686:/home/davygravy/Desktop/configs# openocd -f lsp_wig.cfg
Line 165:		Line 166:
	The error seems commonplace to most of us that have used it. Until we know otherwise, most of us are assuming it is not a huge problem.		The error seems commonplace to most of us that have used it. Until we know otherwise, most of us are assuming it is not a huge problem.
	OpenOCD is now running.		OpenOCD is now running.
-
-
	*In a second terminal window, start telnet pointed to loopback, port 4444. This window is where you will control the communication and commands to your device via the jtag interface. You will have to halt your processor, verify the flash banks, and probe them (so that they are recognized properly). '''Note that your processor must be halted - this is a requirement for the probing the flash.'''		*In a second terminal window, start telnet pointed to loopback, port 4444. This window is where you will control the communication and commands to your device via the jtag interface. You will have to halt your processor, verify the flash banks, and probe them (so that they are recognized properly). '''Note that your processor must be halted - this is a requirement for the probing the flash.'''
	Execute the following commands:		Execute the following commands:
Line 188:		Line 187:
	> flash probe 0		> flash probe 0
	flash 'cfi' found at 0xfffc0000		flash 'cfi' found at 0xfffc0000
-	Once this is done, you have verified that you have proper access to the flash.	+	Once this is done, you have verified that you have proper access to the flash.

	====Erasing and Flashing====		====Erasing and Flashing====

Davy gravy: /* Reference, Notes and Special Situations */

Davy gravy — Mon, 25 Feb 2008 03:30:51 GMT

Reference, Notes and Special Situations

← Older revision		Revision as of 03:30, 25 February 2008
Line 214:		Line 214:
	#For a look at development of OpenOCD, see the [https://lists.berlios.de/pipermail/openocd-development/ OpenOCD Development List Archives]		#For a look at development of OpenOCD, see the [https://lists.berlios.de/pipermail/openocd-development/ OpenOCD Development List Archives]
	#A [http://forum.sparkfun.com/viewforum.php?f=18 forum for OpenOCD users] is hosted by SparkFun - great for posting problems and searching for answers.		#A [http://forum.sparkfun.com/viewforum.php?f=18 forum for OpenOCD users] is hosted by SparkFun - great for posting problems and searching for answers.
-	#Be aware that as of svn r332, Feroceon (not a true ARM926) is still not officially supported by OpenOCD. Success is not guaranteed...at least a handful of us have flashed once or twice, and then been able to proceed with a third flash. Presumably, the processor was in a state that allowed us to do the first flash(es) but for some unknown reason comes to be in some less manageable state. The difficulty for some of us has been getting the processor halted.	+	#Be aware that as of svn r332, Feroceon (not a true ARM926) is still not officially supported by OpenOCD. Success is not guaranteed...at least a handful of us have flashed once or twice, and then been able to proceed with a third flash. Presumably, the processor was in a state that allowed us to do the first flash(es) but for some unknown reason comes to be in some less manageable state. The difficulty for some of us has been getting the processor halted.
		+	#OpenOCD svn revision 335 with a small patch gave success for me, after I patched the source (acknowledgement to bbradley for the patch). In src/target/feroceon.c, find these lines:
		+	/* asserting DBGRQ won't win over the undef exception */
		+	arm7_9->use_dbgrq = 0 ;
		+	change the 0 to 1:
		+	/* asserting DBGRQ won't win over the undef exception */
		+	arm7_9->use_dbgrq = 1 ;
		+	and then compile normally. Note that the 'halt' command didn't work, nor did reset. The only way to get it halted was to do a soft_reset_halt and simultaneously connect pins (RTCK) and (sRST) long enough to get it to halt. ('''Do this at your own risk.''')
		+	root@bytebaker-i686:/home/davygravy# telnet localhost 4444
		+	Trying 127.0.0.1...
		+	Connected to localhost.
		+	Escape character is '^]'.
		+	Open On-Chip Debugger
		+	> halt
		+	requesting target halt...
		+	waiting for target halted...
		+	timed out while waiting for target halted
		+	timed out while waiting for target halted
		+	> reset
		+	> soft_reset_halt
		+	requesting target halt and executing a soft reset
		+	value captured during scan didn't pass the requested check: captured: 0x0f check_value: 0x01 check_mask: 0x0f
		+	in_handler reported a failed check
		+
		+	...
		+
		+	value captured during scan didn't pass the requested check: captured: 0x0f check_value: 0x01 check_mask: 0x0f
		+	in_handler reported a failed check
		+	Target 0 halted
		+	target state: halted
		+	target halted in ARM state due to debug request, current mode: Supervisor
		+	cpsr: 0x000000d3 pc: 0x00000000
		+	MMU: disabled, D-Cache: disabled, I-Cache: disabled
		+	> flash probe 0
		+	probing failed for flash bank '#0' at 0xfffc0000
		+	> flash probe 0
		+	flash 'cfi' found at 0xfffc0000
		+	> flash probe 0
		+	flash 'cfi' found at 0xfffc0000
		+	> flash erase 0 0 63
		+	erased sectors 0 through 63 on flash bank 0 in 2.822007s
		+	> flash erase_check 0
		+	not enough working area available(requested 20, free 0)
		+	no working area available, falling back to slow memory reads
		+	successfully checked erase state
		+	> flash write 0 /home/davygravy/Desktop/configs/lspro-v2flash.bin 0xfffc0000
		+	not enough working area available(requested 96, free 0)
		+	no working area available, can't do block memory writes
		+	Programming at fff80000, count 00040000 bytes remaining
		+	Programming at fff80100, count 0003ff00 bytes remaining
		+	Programming at fff80200, count 0003fe00 bytes remaining
		+
		+	...
		+
		+	Programming at fffbfc00, count 00000400 bytes remaining
		+	Programming at fffbfd00, count 00000300 bytes remaining
		+	Programming at fffbfe00, count 00000200 bytes remaining
		+	Programming at fffbff00, count 00000100 bytes remaining
		+	Fixup 1 unaligned tail bytes
		+	wrote 262144 byte from file /home/davygravy/Desktop/configs/lspro-v2flash.bin to flash bank 0 at offset 0xfffc0000 in 6522.530762s (0.039249 kb/s)
		+	> dump_image currentcontents.bin 0xfffc0000 0x40000
		+	dumped 262144 byte in 18.345442s
		+	> exit
		+	Connection closed by foreign host.
		+	root@bytebaker-i686:/home/davygravy#
		+	#YMMV. Good Luck.

	===Terastation Pro v2/Terastation Live (arm9)===		===Terastation Pro v2/Terastation Live (arm9)===