Peter Huewe: Fixed category

2011-10-27T22:39:18Z

Fixed category

Flameman: /* flashing with openOCD */

2011-06-25T10:15:32Z

‎flashing with openOCD

Flameman: /* Interesting links */

2011-06-25T10:08:44Z

‎Interesting links

Flameman: /* Common problems and Gotchas */

2011-06-25T10:07:50Z

‎Common problems and Gotchas

Flameman: /* doc */

2011-06-25T10:06:32Z

‎doc

Show changes

Flameman: /* App */

2011-06-18T15:27:35Z

‎App

Flameman at 15:26, 18 June 2011

2011-06-18T15:26:42Z

Flameman: /* Introduction */

2011-06-17T09:28:26Z

‎Introduction

Flameman: /* ucOS/2 */

2011-06-17T08:39:08Z

‎ucOS/2

Flameman: /* Tips & Tricks */

2011-06-17T08:38:50Z

‎Tips & Tricks

← Older revision		Revision as of 22:39, 27 October 2011
Line 1,109:		Line 1,109:


−	[[Category:~~arm~~]]	+	[[Category:ARM Development Boards]]

@@ Line 102: / Line 102: @@
 OpenOCD supports flash programming on NXP/Philips LPC2000, Atmel AT91SAM7 and ST STR7 ARM7-controllers (version SVN100). Flash-programming can be done by accessing the OpenOCD-telnet-server but I prefer a method where the flash programming is automated. This is very convenient when working with make. If everything is setup correctly a simple make program will transfer the binary-code into the flash-memory.
-Installing OpenOCD on a MS-Windows-System
+==== Installing OpenOCD on a MS-Windows-System ====
 The methodes described in this small introduction have been tested in a Windows 2000 system with a Wiggler-type JTAG-interface (Olimex ARM-JTAG) and a FTDI2232-based hardware (i.e. JTAGKEY, WINARM-JTAG). The usage of OpenOCD is basicly the same on Linux/Unix-systems.
-    You can get the latest OpenOCD source-code from the berliOS SVN-system and compile and install it yourself. For MS-Windows Michael Fischer provides a precompiled version which includes a setup-software. Links are available from my ARM-projects page (see Links). Sometimes I update a binary for MS-Windows too, see my WinARM page
+You can get the latest OpenOCD source-code from the berliOS SVN-system and compile and install it yourself. For MS-Windows Michael Fischer provides a precompiled version which includes a setup-software.
-    On "modern" MS-Windows-systems like NT, 2000 or XP a special driver must be installed for Wiggler-type hardware interface. This driver is called giveio and is included in the binary distribution from Michael Fischer. The setup-software will ask you if the driver should be installed. But it can also be installed lateron with install-giveio.bat (Administrator priviledges needed for installation only). For FTDI FT2232 based interfaces like the ones from Amontec, Olimex, Signalyzer and myevertool.de the FTDI-drivers must be installed. M. Fischer's package includes the drivers for some devices (the main difference is the VID/PID the "real" hardware-drivers are those available from FTDI with additional inf-files).
 Basicly three files are needed for an automated flash-programming:
@@ Line 114: / Line 116: @@
      a script-file with the flash-commands
-Writing NXP/Philips LPC2000 internal flash-memory
+==== Writing NXP/Philips LPC2000 internal flash-memory ====
 All files mentioned in this section are available for download (see below). A simple example-application is also included in the file archive. Target-controller is a NXP LPC2138 on a Keil LPC2130-board. But the basic method can be used for all LPC2000 controllers after minimal changes.
@@ Line 274: / Line 276: @@
+#
 #  OpenOCD configuration for LPC23xx/LPC24xx
+#
 #  tested with:
@@ Line 414: / Line 413: @@
 Also note that my user-defined commands for flashing do include a verify command. This will fail if OpenOCD has calculated the checksum at flash-address 0x00000014 on-the-fly during flash-programming because of the option calc_checksum given at the bank defintion and the value in the load-image (hex, elf, bin file) does not match the calculated value. Verification failure can be avoided by setting the correct checksum in the assembler-code (.word <checksum> at "reserved" entry in table) so load-image and flash-content after write will match. I do not recomment to remove the calc_checksum option or to disable verify because the target will not start from flash after reset if the checksum at 0x14 is invalid and problems during flash-programming may not be detected.
-My settings for a Debug-Configuration with flash-memory-update in Eclipse using the "Eclipse C/C++ GDB Hardware Debugging" plugin (that's _not_ Zylin's plugin):
+These settings are for a Debug-Configuration with flash-memory-update in Eclipse using the "Eclipse C/C++ GDB Hardware Debugging" plugin (that's _not_ Zylin's plugin)
-Initialisation Commands:
+==== Initialisation Commands: ====
 target remote localhost:3333
@@ Line 427: / Line 426: @@
 monitor debug_level 0
-Run Command
+==== Run Command ====
 stepi
@@ Line 456: / Line 455: @@
 rem set OOCD_INTERFACE=PP
-OpenOCD is called from openocd_go_flash.cmd:
+==== OpenOCD is called from openocd_go_flash.cmd ====
 @echo off
@@ Line 495: / Line 494: @@
 # Flash AT91SAM7S memory using openocd
 # and a FTDI FT2232-based JTAG-interface
+#
@@ Line 583: / Line 579: @@
 shutdown
-An example for a program-target (make program) in the makefile. Make shure the file main.bin is in "raw-binary" format (objcopy format-option binary):
+==== An example for a program-target ====
 program: $(TARGET).$(IMGEXT)
@@ Line 657: / Line 655: @@
-The "reset"-script:
+==== The "reset"-script ====
+#
@@ Line 846: / Line 844: @@
 Create the OpenOCD configuration- and reset-script "on the fly"
-Here a approach to create the needed configuration-script and the reset-script which inlcude the flash-programming command "on the fly" in a makefile.
 The following file uses the makefile-syntax. Basicly it's a makefile but it gets included from the application's makefile. I have choosen this approach since including everything in a single makefile would be a little confusing. This example demonstrates the setup to flash the internal flash-memory of an STMicrosystems STR710 but can be adapted to other targets easily. The content of the file oocd_flashing.mk:
@@ Line 853: / Line 852: @@
+#
 # Auto-create OpenOCD cfg and script
 #############################################
+#
@@ Line 1,073: / Line 1,070: @@
 # uncomment the following:
 #program : $(TARGET).bin oocd_programdoit
 == doc ==

@@ Line 1,094: / Line 1,094: @@
 === Interesting links ===
-http://ics.nxp.com/support/documents/microcontrollers/?scope=LPC2000&type=appnote
+* http://ics.nxp.com/support/documents/microcontrollers/?scope=LPC2000&type=appnote
 === Tips & Tricks ===

← Older revision		Revision as of 10:07, 25 June 2011
Line 1,092:		Line 1,092:
	=== Common problems and Gotchas ===		=== Common problems and Gotchas ===

		+	=== Interesting links ===

		+	http://ics.nxp.com/support/documents/microcontrollers/?scope=LPC2000&type=appnote

	=== Tips & Tricks ===		=== Tips & Tricks ===

@@ Line 108: / Line 108: @@
 == App ==
-=== ucOS/2 ===
+=== ucOS/2 for keil ===
 * early ported, it is running 2 tasks
 === bareboard ===

@@ Line 36: / Line 36: @@
 === Overview ===
-The board (palm m105) consists of:
+The board consists of:
 * '''CPU''' arm7 philips/nx lpc2348-12Mhz [[Media:nxlpc2348-user-man.pdf|nxlpc2348-user-man.pdf]]

@@ Line 15: / Line 15: @@
 * make the board able to boot it
 * have appeal with it
@@ Line 86: / Line 88: @@
 === About devtools ===
 == doc ==

← Older revision		Revision as of 08:38, 17 June 2011
Line 103:		Line 103:

	=== Tips & Tricks ===		=== Tips & Tricks ===
		+
		+
		+	== App ==
		+
		+	=== ucOS/2 ===
		+
		+	early ported, it is running 2 tasks
		+
		+
		+	=== bareboard ===
		+
		+	* rtc
		+	* webserver tcp/ip
		+	* convert the nx board into "usb-memory"


	[[Category:arm]]		[[Category:arm]]

Flameman/knxlpc2348 - Revision history