Hammer How to use Jtag - Revision history

Prpplague at 14:56, 14 November 2007

2007-11-14T14:56:24Z

Prpplague at 14:55, 14 November 2007

2007-11-14T14:55:50Z

Prpplague at 14:33, 14 November 2007

2007-11-14T14:33:53Z

Prpplague at 14:26, 14 November 2007

2007-11-14T14:26:12Z

Prpplague at 23:43, 8 November 2007

2007-11-08T23:43:46Z

Prpplague at 23:42, 8 November 2007

2007-11-08T23:42:46Z

Prpplague at 13:26, 17 September 2007

2007-09-17T13:26:32Z

Prpplague: How to use Jtag moved to Hammer How to use Jtag

2007-09-17T13:26:02Z

How to use Jtag moved to Hammer How to use Jtag

KenMcGuire at 00:55, 16 September 2007

2007-09-16T00:55:30Z

KenMcGuire at 00:00, 16 September 2007

2007-09-16T00:00:41Z

@@ Line 27: / Line 27: @@
 ) then configure the build using the command: ./configure  --enable-ft2232_ftd2xx
-     NOTE: if you receive an error "configure: exit 77" during the configure process please use app-get to install the build-essentials package with the following command: apt-get install build-essential
+     NOTE: if you receive an error "configure: exit 77" during the configure process
 I searched and found the following fix: * apt-get install build-essential

← Older revision		Revision as of 14:55, 14 November 2007
Line 27:		Line 27:

	10) then configure the build using the command: ./configure --enable-ft2232_ftd2xx		10) then configure the build using the command: ./configure --enable-ft2232_ftd2xx
		+	NOTE: if you receive an error "configure: exit 77" during the configure process please use app-get to install the build-essentials package with the following command: apt-get install build-essential
		+
		+	I searched and found the following fix: * apt-get install build-essential

	11) start the build using the command: make		11) start the build using the command: make

@@ Line 7: / Line 7: @@
 ) ubuntu also needs usbfs turned on: mount -t usbfs usbfs /proc/bus/usb (as root)
-) extract the openocd tarball using the command: tar zxvf openocd.tar.gz
+) extract the libftd2xx files using the following command: tar zxvf libftd2xx0.4.13.tar.gz
-) you must extract fd2xx.h and WinTypes.h (from libftd2xx0.4.13.tar.gz) to the openocd/src/jtag/ directory
+) extract the openocd tarball using the command: tar zxvf openocd.tar.gz
-) to recompile openocd, one must first run the command: ./bootstrap
+) copy the fd2xx.h and WinTypes.h files from libftd2xx directory to the openocd/src/jtag/ directory
-) then configure the build using the command: ./configure  --enable-ft2232_ftd2xx
+) copy the libftd2xx.so.0.4.13 file from the libftd2xx directory to /usr/lib directory
-) start the build using the command: make
+) create symlinks for the libftd2xx by using the following commands:
-) put the resulting openocd executable in a dir with hammer.cfg, hammer.ocd, apex.bin (the orig from the cd)
+   cd /usr/lib
-) ./openocd -f hammer.cfg (as root if you are on ubuntu 6.06 LTS)
+) change directory to the openocd source directory
-) This will load apex into ram & run it. then you can flash the original apex.bin back.
+) to recompile openocd, one must first run the command: ./bootstrap

@@ Line 13: / Line 13: @@
 ) to recompile openocd, one must first run the command: ./bootstrap
-) then configure the build using the command: ./configure  --enable-ft2232-ftd2xx
+) then configure the build using the command: ./configure  --enable-ft2232_ftd2xx
 ) start the build using the command: make

← Older revision		Revision as of 23:43, 8 November 2007
Line 1:		Line 1:
		+	files needed:
		+	*[[Media:openocd.tar.gz]]
		+	*[[Media:libftd2xx0.4.13.tar.gz]]

	1) rmmod fdti_sio since the normal ubuntu driver grabs the hardware on plugin		1) rmmod fdti_sio since the normal ubuntu driver grabs the hardware on plugin

@@ Line 1: / Line 1: @@
-) the path to a successful apex reflash was a long and hard one.
+) ubuntu also needs usbfs turned on: mount -t usbfs usbfs /proc/bus/usb (as root)
-) started by needing to compile openocd from source.
+) extract the openocd tarball using the command: tar zxvf openocd.tar.gz
-) also needed to rmmod fdti_sio since the normal ubuntu driver grabs the hardware on plugin.
+) you must extract fd2xx.h and WinTypes.h (from libftd2xx0.4.13.tar.gz) to the openocd/src/jtag/ directory
-a) ubuntu also needs usbfs turned on: mount -t usbfs usbfs /proc/bus/usb (as root)
+) to recompile openocd, one must first run the command: ./bootstrap
-) to recompile openocd, one must first run ./bootstrap
+) then configure the build using the command: ./configure  --enable-ft2232-ftd2xx
-a) then ./configure  --enable-ft2232-ftd2xx
+) start the build using the command: make
-b) then make
+) put the resulting openocd executable in a dir with hammer.cfg, hammer.ocd, apex.bin (the orig from the cd)
-) but before that you must extract fd2xx.h and WinTypes.h (from libftd2xx0.4.10.tar.gz) to the /openocd/src/jtag/ directory..
+) ./openocd -f hammer.cfg (as root if you are on ubuntu 6.06 LTS)
-) put the resulting openocd executable in a dir with hammer.cfg, hammer.ocd, apex.bin (the orig from the cd)
+) This will load apex into ram & run it. then you can flash the original apex.bin back.
-) This will load apex into ram & run it. then you can flash the original apex.bin back.
+note: it seems that openocd likes to be run as root.
-−
-) it seems that openocd likes to be run as root. This may be ubuntu specific, or I may not know my a$$ from a hole in the ground.
-−
-) rebuilding apex from source you need to make menuconfig (generates lots of wierd errors if there is no .config)
-−
-) then select the Samsung S3C2410 platform
-−
-) then the Tin Can Tools Hammer implementation
-−
-) Change other stuff as req'd (ie Environment > Regions > 256k+1024k ==> kernel source 1280k+1024k ==> ramdisk image
-−
-) save changes & make
 [[Category:TCT-Hammer]]
 [[Category:TinCanTools]]

← Older revision		Revision as of 13:26, 17 September 2007
Line 35:		Line 35:

	20) save changes & make		20) save changes & make
		+
		+
		+	[[Category:TCT-Hammer]]
		+	[[Category:TinCanTools]]

← Older revision		Revision as of 00:00, 16 September 2007
Line 1:		Line 1:
	Place holder		Place holder
		+
		+
		+	7) the path to a successful apex reflash was a long and hard one.
		+
		+	8) started by needing to compile openocd from source.
		+
		+	9) also needed to rmmod fdti_sio since the normal ubuntu driver grabs the hardware on plugin.
		+
		+	9a) ubuntu also needs usbfs turned on: mount -t usbfs usbfs /proc/bus/usb (as root)
		+
		+	10) to recompile openocd, one must firs run ./bootstrap
		+
		+	10a) then ./configure --enable-ft2232-ftd2xx
		+
		+	10b) then make
		+
		+	11) but before that you must extract fd2xx.h and WinTypes.h to the /openocd/src/jtag/ directory..
		+
		+	12) put the resulting openocd executable in a dir with hammer.cfg, hammer.ocd, apex.bin (the orig from the cd)
		+
		+	13) ./openocd -f hammer.cfg
		+
		+	14) This will load apex into ram & run it. then you can flash the original apex.bin back.
		+
		+	15) it seems that openocd likes to be run as root.
		+
		+	16) rebuilding apex from source you need to make menuconfig (generates lots of wierd errors if there is no .config)
		+
		+	17) then select the Samsung S3C2410 platform
		+
		+	18) then the Tin Can Tools Hammer implementation
		+
		+	19) Change other stuff as req'd (ie Environment > Regions > 256k+1024k ==> kernel source 1280k+1024k ==> ramdisk image
		+
		+	20) save changes & make