Installing OpenOCD - Revision history

Js at 09:51, 12 November 2021

2021-11-12T09:51:51Z

2021-11-11T09:50:52Z

2019-09-19T10:31:19Z

2019-09-16T09:00:01Z

2019-09-16T08:58:30Z

2019-06-04T07:52:22Z

2019-06-04T07:51:37Z

2019-06-03T10:06:01Z

2019-05-23T11:59:49Z

2019-05-23T11:58:51Z

@@ Line 10: / Line 10: @@
 * OpenOCD Version >= 0.10 with the libftdi driver is required.
-* Prebuild binaries of [https://openocd.org/pages/getting-openocd.html OpenOCD] can be downloaded from [https://github.com/xpack-dev-tools/openocd-xpack/releases here]
+* Prebuild binaries of [https://openocd.org/pages/getting-openocd.html OpenOCD] can be downloaded from [https://github.com/openocd-org/openocd/releases/tag/v0.11.0 here]
 * Install the libusbK driver for the JTAG interface
 ** Download and start [https://zadig.akeo.ie/ Zadig]

@@ Line 10: / Line 10: @@
 * OpenOCD Version >= 0.10 with the libftdi driver is required.
-* Prebuild binaries can be downloaded from [https://github.com/gnu-mcu-eclipse/openocd/releases GNU MCU Eclipse]
+* Prebuild binaries of [https://openocd.org/pages/getting-openocd.html OpenOCD] can be downloaded from [https://github.com/xpack-dev-tools/openocd-xpack/releases here]
 * Install the libusbK driver for the JTAG interface
 ** Download and start [https://zadig.akeo.ie/ Zadig]

@@ Line 79: / Line 79: @@
 * Now you can open a console and use the command:
-* '''mx10spider:''' ''<path\to\file.svf>''
+* '''mx10spider''' ''<path\to\file.svf>''
 <div><ul>

@@ Line 24: / Line 24: @@
 A shell script can be used that starts OpenOCD, runs the svf file and shuts down afterwards, allowing conveniently programming the FPGA using a single terminal command.
-* Create the file '''mx10spider_prog''' under ''.local/bin'' in your home directory and insert the content below.
+* Create the file '''mx10spider''' under ''.local/bin'' in your home directory and insert the content below.
 * If not already done, add ''.local/bin'' to the path variable.
 ** Open ''.profile'' in your home directory with a text editor and add the line:
@@ Line 31: / Line 31: @@
 **: '''$''' source ~/.profile
 * Open a terminal and add the executable flag.
-*: '''$''' chmod +x .local/bin/mx10spider_prog
+*: '''$''' chmod +x .local/bin/mx10spider
 * You are now ready to program the fpga using the command:
-*: '''$''' mx10spider_prog  ''<path/to/file.svf>''
+*: '''$''' mx10spider  ''<path/to/file.svf>''
 * If your project is for example located under ''/opt/quartus_projects/Example'', use one of the following commands:
-*: '''$''' mx10spider_prog /opt/quartus_projects/Example/output_files/Example.svf
+*: '''$''' mx10spider /opt/quartus_projects/Example/output_files/Example.svf
-*: '''$''' mx10spider_prog /opt/quartus_projects/Example/output_files/Example_pof.svf
+*: '''$''' mx10spider /opt/quartus_projects/Example/output_files/Example_pof.svf
 *: for programming the .sof or .pof file respectively.
 <br>
-'''mx10spider_prog:'''
+'''mx10spider:'''
   <nowiki>
 #!/bin/sh

@@ Line 1: / Line 1: @@
-== Installing OpenOCD ==
+== Installing OpenOCD (Linux) ==
 * OpenOCD Version >= 0.10 with the libftdi driver is required.
@@ Line 7: / Line 7: @@
 * If the package version does not work, it is possible to compile OpenOCD from [https://github.com/ntfreak/openocd source (github)].
-== Shell Script For Easier Use ==
+== Installing OpenOCD (Windows) ==
 A shell script can be used that starts OpenOCD, runs the svf file and shuts down afterwards, allowing conveniently programming the FPGA using a single terminal command.
@@ Line 22: / Line 35: @@
 *: '''$''' mx10spider_prog  ''<path/to/file.svf>''
 * If your project is for example located under ''/opt/quartus_projects/Example'', use one of the following commands:
-*: '''$''' mx10spider_prog /opt/quartus_projets/Example/output_files/Example.svf
+*: '''$''' mx10spider_prog /opt/quartus_projects/Example/output_files/Example.svf
-*: '''$''' mx10spider_prog /opt/quartus_projets/Example/output_files/Example_pof.svf
+*: '''$''' mx10spider_prog /opt/quartus_projects/Example/output_files/Example_pof.svf
 *: for programming the .sof or .pof file respectively.
@@ Line 55: / Line 68: @@
 fi
 </nowiki>

@@ Line 60: / Line 60: @@
 Due to a hardware issue on the MX10, in order to get PIC JTAG programming through OpenOCD to work, one has to desolder four resistors on the module.
-[[File:Mx10-resistors-to-remove.pdf | page=1 | left | 750px | thumb | One resistor on the top side of the module.]]
+[[File:Mx10-resistors-to-remove.pdf | page=1 | left | 750px | thumb | One resistor on the top side of the module, marked with a red cross.]]
-[[File:Mx10-resistors-to-remove.pdf | page=2 | center | 750px | thumb | Three resistors on the bottom side of the module.]]
+[[File:Mx10-resistors-to-remove.pdf | page=2 | center | 750px | thumb | Three resistors on the bottom side of the module, each marked with a red cross.]]

← Older revision		Revision as of 07:51, 4 June 2019
Line 56:		Line 56:
	fi		fi
	</nowiki>		</nowiki>
		+
		+	== MX10 Hardware Issue ==
		+
		+	Due to a hardware issue on the MX10, in order to get PIC JTAG programming through OpenOCD to work, one has to desolder four resistors on the module.
		+	[[File:Mx10-resistors-to-remove.pdf \| page=1 \| left \| 750px \| thumb \| One resistor on the top side of the module.]]
		+	[[File:Mx10-resistors-to-remove.pdf \| page=2 \| center \| 750px \| thumb \| Three resistors on the bottom side of the module.]]

@@ Line 44: / Line 44: @@
 elif [ "$1" = "" ]; then
-	echo "\tError: No file specified.\n\tUsage: $me <file.svf>"
+	echo -e "\tError: No file specified.\n\tUsage: $me <file.svf>"
 elif [ "$1" = "-h" ] || [ "$1" = "--help" ]; then
-	echo "\tUtility script to start openocd and run an svf file.\n\tUsage: $me <file.svf>"
+	echo -e "\tUtility script to start openocd and run an svf file.\n\tUsage: $me <file.svf>"
 else
-     echo "\tFile not found: $1\n\tUsage: $me <file.svf>"
+     echo -e "\tFile not found: $1\n\tUsage: $me <file.svf>"
 fi
 </nowiki>

@@ Line 15: / Line 15: @@
 ** Open ''.profile'' in your home directory with a text editor and add the line:
 **: PATH=".local/bin:$PATH"
-** Logout and login again or run following command to reload path variable:
+** Logout and login again or run the following command to reload the path variable:
 **: '''$''' source ~/.profile
 * Open a terminal and add the executable flag.