Arm compiler environment - Revision history

S123950 at 13:27, 19 August 2016

2016-08-19T13:27:48Z

← Older revision		Revision as of 15:27, 19 August 2016
Line 89:		Line 89:
	'''OBS: Only the anchors (with their Cortex-M0 processor), and the newest versions of the tags (with their Cortex-M4 processor), supports programming through USB (DFU protocol).'''		'''OBS: Only the anchors (with their Cortex-M0 processor), and the newest versions of the tags (with their Cortex-M4 processor), supports programming through USB (DFU protocol).'''

			The host-side tool used for programming the devices through USB, is called DFU-Util. <br />
	Either install DFU-Util from the apt-get repository as		Either install DFU-Util from the apt-get repository as

	~~'''~~$ sudo apt-get install dfu-util~~'''~~		$ sudo apt-get install dfu-util

			Or download and extract the tool as described below <br />

	~~The host-side tool used for programming the devices through USB, is called DFU-Util. <br />~~
	The tool can be downloaded at [http://dfu-util.sourceforge.net/releases/ http://dfu-util.sourceforge.net/releases/], and is ready to be used out of the box.		The tool can be downloaded at [http://dfu-util.sourceforge.net/releases/ http://dfu-util.sourceforge.net/releases/], and is ready to be used out of the box.

S123950: /* DFU-Util setup */

2016-08-19T13:26:38Z

DFU-Util setup

← Older revision		Revision as of 15:26, 19 August 2016
Line 87:		Line 87:
	==DFU-Util setup==		==DFU-Util setup==

	'''OBS: Only the anchors, with their Cortex-M0 processor, supports programming through USB (DFU protocol).'''		'''OBS: Only the anchors (with their Cortex-M0 processor), and the newest versions of the tags (with their Cortex-M4 processor), supports programming through USB (DFU protocol).'''

			Either install DFU-Util from the apt-get repository as

			'''$ sudo apt-get install dfu-util'''

	The host-side tool used for programming the devices through USB, is called DFU-Util. <br />		The host-side tool used for programming the devices through USB, is called DFU-Util. <br />

S123950 at 11:53, 31 May 2016

2016-05-31T11:53:55Z

← Older revision		Revision as of 13:53, 31 May 2016
Line 1:		Line 1:
			[[File:ST-Link-V2.png\|thumb\|right\|ST-Link/V2 Programmer]]

	The arm compiler environment for the ST microcontrollers used in the [[3D localization]] project contains a number of software packages, which ones are needed depends on the users demands to debugging.		The arm compiler environment for the ST microcontrollers used in the [[3D localization]] project contains a number of software packages, which ones are needed depends on the users demands to debugging.
	It consists of an arm compiler including accessory binaries, openOCD for SWD usage (programming & debugging through GDB) and DFU-util for programming through USB.		It consists of an arm compiler including accessory binaries, openOCD for SWD usage (programming & debugging through GDB) and DFU-util for programming through USB.

	~~[[File:ST-Link-V2.png\|thumb\|right\|ST-Link/V2 Programmer]]~~

	==Compiler setup - Linux==		==Compiler setup - Linux==

S123950 at 11:53, 31 May 2016

2016-05-31T11:53:36Z

← Older revision		Revision as of 13:53, 31 May 2016
Line 2:		Line 2:
	It consists of an arm compiler including accessory binaries, openOCD for SWD usage (programming & debugging through GDB) and DFU-util for programming through USB.		It consists of an arm compiler including accessory binaries, openOCD for SWD usage (programming & debugging through GDB) and DFU-util for programming through USB.

	~~TODO~~: ~~Add a picture of the~~ ST-Link/V2		[[File:ST-Link-V2.png\|thumb\|right\|ST-Link/V2 Programmer]]

	==Compiler setup - Linux==		==Compiler setup - Linux==

S123950 at 11:51, 31 May 2016

2016-05-31T11:51:04Z

← Older revision		Revision as of 13:51, 31 May 2016
Line 1:		Line 1:
	The arm compiler environment for the ST microcontrollers used in the [[3D localization]] project contains a number of software packages, which ones are needed depends on the users demands to debugging.		The arm compiler environment for the ST microcontrollers used in the [[3D localization]] project contains a number of software packages, which ones are needed depends on the users demands to debugging.
	It consists of an arm compiler including accessory binaries, openOCD for SWD usage (programming & debugging through GDB) and DFU-util for programming through USB.		It consists of an arm compiler including accessory binaries, openOCD for SWD usage (programming & debugging through GDB) and DFU-util for programming through USB.

			TODO: Add a picture of the ST-Link/V2

	==Compiler setup - Linux==		==Compiler setup - Linux==

S123950: /* OpenOCD setup */

2016-05-31T08:49:07Z

OpenOCD setup

← Older revision		Revision as of 10:49, 31 May 2016
Line 73:		Line 73:
	$ /opt/gnuarmeclipse/openocd/0.9.0-201505190955/bin/openocd --version GNU ARM Eclipse 64-bits Open On-Chip Debugger ....		$ /opt/gnuarmeclipse/openocd/0.9.0-201505190955/bin/openocd --version GNU ARM Eclipse 64-bits Open On-Chip Debugger ....

			If you’ll ever need to remove OpenOCD, just remove the /opt/gnuarmeclipse, there are no other components stored in system folders (And the UDEV rule).

	====UDEV Rules====		====UDEV Rules====

S123950: /* ST-Link/V2 */

2016-05-31T08:48:03Z

ST-Link/V2

← Older revision		Revision as of 10:48, 31 May 2016
Line 49:		Line 49:
	====ST-Link/V2====		====ST-Link/V2====

	The hardware used is ST's own ST-Link/V2 programmer, that can be acquired either in a proprietary version from ST, or in a cheap China version from eg. [[www.ebay.de ebay]] (I have only personally tested the cheap China version, which works to perfection).		The hardware used is ST's own ST-Link/V2 programmer, that can be acquired either in a proprietary version from ST, or in a cheap China version from eg. [http://www.ebay.de ebay] (I have only personally tested the cheap China version, which works to perfection).

	====Installing OpenOCD====		====Installing OpenOCD====

S123950: /* ST-Link/V2 */

2016-05-31T08:47:49Z

ST-Link/V2

← Older revision		Revision as of 10:47, 31 May 2016
Line 49:		Line 49:
	====ST-Link/V2====		====ST-Link/V2====

	The hardware used is ST's own ST-Link/V2 programmer, that can be acquired either in a proprietary version from ST, or in a cheap China version from eg. [www.ebay.de ebay] (I have only personally tested the cheap China version, which works to perfection).		The hardware used is ST's own ST-Link/V2 programmer, that can be acquired either in a proprietary version from ST, or in a cheap China version from eg. [[www.ebay.de ebay]] (I have only personally tested the cheap China version, which works to perfection).

	====Installing OpenOCD====		====Installing OpenOCD====

S123950: /* OpenOCD setup */

2016-05-31T08:47:01Z

OpenOCD setup

← Older revision		Revision as of 10:47, 31 May 2016
Line 44:		Line 44:

	==OpenOCD setup==		==OpenOCD setup==

			In order to program the devices through SWD, a hardware programmer and some software are needed.

			====ST-Link/V2====

			The hardware used is ST's own ST-Link/V2 programmer, that can be acquired either in a proprietary version from ST, or in a cheap China version from eg. [www.ebay.de ebay] (I have only personally tested the cheap China version, which works to perfection).

			====Installing OpenOCD====

	The GNU/Linux versions of GNU ARM Eclipse OpenOCD are packed as TGZ archives. Go to the [https://github.com/gnuarmeclipse/openocd/releases GitHub Releases] page and download the latest version named like:		The GNU/Linux versions of GNU ARM Eclipse OpenOCD are packed as TGZ archives. Go to the [https://github.com/gnuarmeclipse/openocd/releases GitHub Releases] page and download the latest version named like:

S123950: /* UDEV Rules */

2016-05-31T08:43:12Z

UDEV Rules

← Older revision		Revision as of 10:43, 31 May 2016
Line 70:		Line 70:
	For the JTAG probes implemented as USB devices (actually most of them), the last installation step on GNU/Linux is to configure the UDEV subsystem. OpenOCD provides an UDEV rules file defining all the supported IDs; to install it, just copy the file to '''/etc/udev/rules.d''' and eventually notify the daemon:		For the JTAG probes implemented as USB devices (actually most of them), the last installation step on GNU/Linux is to configure the UDEV subsystem. OpenOCD provides an UDEV rules file defining all the supported IDs; to install it, just copy the file to '''/etc/udev/rules.d''' and eventually notify the daemon:

	$ sudo cp /opt/gnuarmeclipse/openocd/0.10.0-~~201510281129-dev~~/contrib/99-openocd.rules /etc/udev/rules.d/		$ sudo cp /opt/gnuarmeclipse/openocd/0.9.0-201505190955/contrib/99-openocd.rules /etc/udev/rules.d/
	$ sudo udevadm control --reload-rules		$ sudo udevadm control --reload-rules
	Note: If you previously installed the J-Link binaries, the USB IDs were already added to UDEV. The above OpenOCD rules file also defines the J-Link ID. Apparently UDEV does not complain; if you encounter problems, just comment out the definition in the OpenOCD file.		Note: If you previously installed the J-Link binaries, the USB IDs were already added to UDEV. The above OpenOCD rules file also defines the J-Link ID. Apparently UDEV does not complain; if you encounter problems, just comment out the definition in the OpenOCD file.