Re: [Openocd-development] [EMAIL PROTECTED]: Bug#489785: please addsample config file for cortex M3 target]
On Wed, Jul 09, 2008 at 12:49:50PM +0100, Spen wrote: Could you clean it up a bit exclude interface specific stuff? LM3S8962 does not match LM3S811... I don't know what that means. The problem is more related to ftdi drivers ftdi own drivers require ft2232_device_desc Stellaris Evaluation Board A and libusb requires ft2232_device_desc Stellaris Evaluation Board 1. The seperate is the default reset_config and not required. 2. The flash bank stellaris 0 262144 0 0 0 only needs as the flash size is probed. flash bank stellaris 0 0 0 0 0 I can tweak and commit the scripts, but do we have two variants - ftdi and libusb ftdi interface? Hm, guess so. Debian will only need the free libfdti, the closed-source one is never going to be included/supported, but for non-Debian users both are probably needed (?) Uwe. -- http://www.hermann-uwe.de | http://www.holsham-traders.de http://www.crazy-hacks.org | http://www.unmaintained-free-software.org ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
[Openocd-development] parport.cfg question
Hi, why does src/target/interface/parport.cfg use the parport_port 0xc8b8 config? Shouldn't that be either 0 or 0x3f8 rather? I've never seen that one used anywhere, and it definately doesn't work on my (standard PC) parallel port (0 does work). Thanks, Uwe. -- http://www.hermann-uwe.de | http://www.holsham-traders.de http://www.crazy-hacks.org | http://www.unmaintained-free-software.org ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
[Openocd-development] [PATCH] Fix ep93xx compile on armel / arm
Hi, I've updated the OpenOCD Debian package to r1130 yesterday, and the Debian autobuild daemons found a compile problem with ep93xx on the 'armel' architecture, see http://buildd.debian.org/fetch.cgi?pkg=openocd;ver=0.0%2Br1130-1;arch=armel;stamp=1225973025 The problem is how nanosleep() is being called. I'm actually surprised that it ever worked and doesn't break on other architectures. My Linux nanosleep(2) manpage says this: #include time.h int nanosleep(const struct timespec *req, struct timespec *rem); The /usr/include/time.h file says: extern int nanosleep (__const struct timespec *__requested_time, struct timespec *__remaining); However, in src/jtag/ep93xx.c nanosleep() is always called as struct timespec ep93xx_; nanosleep(ep93xx_); which doesn't really work, as (a) the first argument should be a pointer (not a struct), and (b) there are two arguments, not only one. The fix is probably: nanosleep(ep93xx_, NULL); See attached patch for a fix. I've tested it on an ARM box and confirmed that it really fixes the compile. HTH, Uwe. -- http://www.hermann-uwe.de | http://www.holsham-traders.de http://www.crazy-hacks.org | http://www.unmaintained-free-software.org Index: src/jtag/ep93xx.c === --- src/jtag/ep93xx.c (Revision 1142) +++ src/jtag/ep93xx.c (Arbeitskopie) @@ -40,6 +40,7 @@ #include sys/mman.h #include unistd.h #include fcntl.h +#include time.h static u8 output_value = 0x0; static int dev_mem_fd; @@ -103,7 +104,7 @@ output_value = TDI_BIT; *gpio_data_register = output_value; - nanosleep(ep93xx_); + nanosleep(ep93xx_, NULL); } /* (1) assert or (0) deassert reset lines */ @@ -120,7 +121,7 @@ output_value = SRST_BIT; *gpio_data_register = output_value; - nanosleep(ep93xx_); + nanosleep(ep93xx_, NULL); } int ep93xx_speed(int speed) @@ -218,7 +219,7 @@ */ output_value = TMS_BIT | TRST_BIT | SRST_BIT | VCC_BIT; *gpio_data_register = output_value; - nanosleep(ep93xx_); + nanosleep(ep93xx_, NULL); /* * Configure the direction register. 1 = output, 0 = input. @@ -226,7 +227,7 @@ *gpio_data_direction_register = TDI_BIT | TCK_BIT | TMS_BIT | TRST_BIT | SRST_BIT | VCC_BIT; - nanosleep(ep93xx_); + nanosleep(ep93xx_, NULL); return ERROR_OK; } ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
[Openocd-development] [PATCH] Fix typos.
Fix a bunch of typos.
Uwe.
--
http://www.hermann-uwe.de | http://www.holsham-traders.de
http://www.crazy-hacks.org | http://www.unmaintained-free-software.org
Index: src/tcl/README_ABOUT_TCL.txt
===
--- src/tcl/README_ABOUT_TCL.txt (Revision 1140)
+++ src/tcl/README_ABOUT_TCL.txt (Arbeitskopie)
@@ -11,7 +11,7 @@
The goal of this document is to encourage you to add your own set of
chips to the TCL package - and most importantly you should know where
-you should put them - so they end up in an orginized way.
+you should put them - so they end up in an organized way.
--Duane Ellis.
[EMAIL PROTECTED]
@@ -34,7 +34,7 @@
tcl/cpu/arm/NAME.tcl.
Yes, that is where you should put core specific things.
- Be carefull and learn the difference:
+ Be careful and learn the difference:
THE CORE - is not the entire chip!
@@ -78,9 +78,9 @@
set NAMEVALUE
-It is mostly obious what is going on.
+It is mostly obvious what is going on.
-Execption: The arrays.
+Exception: The arrays.
You would *THINK* Tcl supports arrays.
In fact, multi-dim arrays. That is false.
@@ -126,7 +126,7 @@
== SIDEBAR: About The FOR command ==
In TCL, FOR is a funny thing, it is not what you think it is.
-Syntatically - FOR is a just a command, it is not language
+Syntactically - FOR is a just a command, it is not language
construct like for(;;) in C...
The for command takes 4 parameters.
@@ -135,7 +135,7 @@
(3) the next command
(4) the body command of the FOR loop.
-Notice I used the words command and expresion above.
+Notice I used the words command and expression above.
The FOR command:
1) executes the initial command
@@ -219,7 +219,7 @@
WIDTH - the accessable width.
ie: Some regions of memory are not 'word'
- accessable.
+ accessible.
The function address_info - given an address should
tell you about the address.
@@ -237,7 +237,7 @@
All read memory - and return the contents.
-[ fixme: 7/5/2008 - I need to create memwrite functions]
+[ FIXME: 7/5/2008 - I need to create memwrite functions]
**
***
@@ -294,15 +294,15 @@
Yea, the entire thing is done that way.
IF is a command. SO is FOR and WHILE and DO and the
- others. That is why I keep using the prhase it is a command
+ others. That is why I keep using the phase it is a command
=== END: Sidebar: About commands ===
-Paramter 1 to the IF command is expected to be an expression.
+Parameter 1 to the IF command is expected to be an expression.
As such, I do not need to wrap it in {braces}.
-In this case, the expression is the resul of the CATCH command.
+In this case, the expression is the result of the CATCH command.
CATCH - is an error catcher.
@@ -314,7 +314,7 @@
The ![catch command] is self explaintory.
-The 3rd parameter to IF must be exacty else or elseif [I lied
+The 3rd parameter to IF must be exactly else or elseif [I lied
above, the IF command can take many parameters they just have to
be joined by exactly the words else or elseif.
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] parport.cfg question
On Fri, Nov 07, 2008 at 02:17:39AM +0100, Uwe Hermann wrote: Hi, why does src/target/interface/parport.cfg use the parport_port 0xc8b8 config? Shouldn't that be either 0 or 0x3f8 rather? ^ I mean 0x378 here, of course I've never seen that one used anywhere, and it definately doesn't work on my (standard PC) parallel port (0 does work). Uwe. -- http://www.hermann-uwe.de | http://www.holsham-traders.de http://www.crazy-hacks.org | http://www.unmaintained-free-software.org ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] parport.cfg question
On Fri, Nov 07, 2008 at 02:17:39AM +0100, Uwe Hermann wrote: Hi, why does src/target/interface/parport.cfg use the parport_port 0xc8b8 config? Shouldn't that be either 0 or 0x3f8 rather? I've never seen that one used anywhere, and it definately doesn't work on my (standard PC) parallel port (0 does work). Comments anyone? Here's a patch to change the parallel port I/O port to 0x378 to make it work with most PC parallel ports. Please let me know if the 0xc8b8 is useful/correct on some platform I may not know... Thanks, Uwe. -- http://www.hermann-uwe.de | http://www.holsham-traders.de http://www.crazy-hacks.org | http://www.unmaintained-free-software.org Index: src/target/interface/parport.cfg === --- src/target/interface/parport.cfg (Revision 1172) +++ src/target/interface/parport.cfg (Arbeitskopie) @@ -2,7 +2,9 @@ gdb_port 2001 interface parport -parport_port 0xc8b8 +parport_port 0x378 +# Use the line below if you loaded the Linux 'ppdev' module, for instance. +# parport_port 0 parport_cable wiggler jtag_speed 0 ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] [PATCH] Fix ep93xx compile on armel / arm
On Fri, Nov 07, 2008 at 01:59:36AM +0100, Uwe Hermann wrote: Hi, I've updated the OpenOCD Debian package to r1130 yesterday, and the Debian autobuild daemons found a compile problem with ep93xx on the 'armel' architecture, see http://buildd.debian.org/fetch.cgi?pkg=openocd;ver=0.0%2Br1130-1;arch=armel;stamp=1225973025 The problem is how nanosleep() is being called. I'm actually surprised that it ever worked and doesn't break on other architectures. My Linux nanosleep(2) manpage says this: #include time.h int nanosleep(const struct timespec *req, struct timespec *rem); The /usr/include/time.h file says: extern int nanosleep (__const struct timespec *__requested_time, struct timespec *__remaining); However, in src/jtag/ep93xx.c nanosleep() is always called as struct timespec ep93xx_; nanosleep(ep93xx_); which doesn't really work, as (a) the first argument should be a pointer (not a struct), and (b) there are two arguments, not only one. The fix is probably: nanosleep(ep93xx_, NULL); See attached patch for a fix. I've tested it on an ARM box and confirmed that it really fixes the compile. *ping* Can somebody please review/commit this patch? Thanks! HTH, Uwe. -- http://www.hermann-uwe.de | http://www.holsham-traders.de http://www.crazy-hacks.org | http://www.unmaintained-free-software.org Index: src/jtag/ep93xx.c === --- src/jtag/ep93xx.c (Revision 1142) +++ src/jtag/ep93xx.c (Arbeitskopie) @@ -40,6 +40,7 @@ #include sys/mman.h #include unistd.h #include fcntl.h +#include time.h static u8 output_value = 0x0; static int dev_mem_fd; @@ -103,7 +104,7 @@ output_value = TDI_BIT; *gpio_data_register = output_value; - nanosleep(ep93xx_); + nanosleep(ep93xx_, NULL); } /* (1) assert or (0) deassert reset lines */ @@ -120,7 +121,7 @@ output_value = SRST_BIT; *gpio_data_register = output_value; - nanosleep(ep93xx_); + nanosleep(ep93xx_, NULL); } int ep93xx_speed(int speed) @@ -218,7 +219,7 @@ */ output_value = TMS_BIT | TRST_BIT | SRST_BIT | VCC_BIT; *gpio_data_register = output_value; - nanosleep(ep93xx_); + nanosleep(ep93xx_, NULL); /* * Configure the direction register. 1 = output, 0 = input. @@ -226,7 +227,7 @@ *gpio_data_direction_register = TDI_BIT | TCK_BIT | TMS_BIT | TRST_BIT | SRST_BIT | VCC_BIT; - nanosleep(ep93xx_); + nanosleep(ep93xx_, NULL); return ERROR_OK; } ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development -- http://www.hermann-uwe.de | http://www.holsham-traders.de http://www.crazy-hacks.org | http://www.unmaintained-free-software.org ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
[Openocd-development] [PATCH] Fix compiler warnings / bug
Hi,
I've been doing another update of the OpenOCD Debian package today and
noticed some stuff which may be worth fixing upstream.
One of them is fixing a few compiler warnings (see attached patch) and
likely also one (non-cosmetic) bug (the 'id_buff' change, which seems to
be a buffer overflow).
More patches will follow.
HTH, Uwe.
--
http://www.hermann-uwe.de | http://www.holsham-traders.de
http://www.crazy-hacks.org | http://www.unmaintained-free-software.org
Index: src/helper/jim.c
===
--- src/helper/jim.c (Revision 1292)
+++ src/helper/jim.c (Arbeitskopie)
@@ -49,6 +49,7 @@
#define JIM_DYNLIB /* Dynamic library support for UNIX and WIN32 */
#endif /* JIM_ANSIC */
+#define _GNU_SOURCE /* for vasprintf() */
#include stdio.h
#include stdlib.h
#include string.h
Index: src/jtag/usbprog.c
===
--- src/jtag/usbprog.c (Revision 1292)
+++ src/jtag/usbprog.c (Arbeitskopie)
@@ -93,7 +93,7 @@
struct usbprog_jtag * usbprog_jtag_handle;
-struct usbprog_jtag* usbprog_jtag_open();
+struct usbprog_jtag* usbprog_jtag_open(void);
void usbprog_jtag_close(struct usbprog_jtag *usbprog_jtag);
void usbprog_jtag_init(struct usbprog_jtag *usbprog_jtag);
unsigned char usbprog_jtag_message(struct usbprog_jtag *usbprog_jtag, char *msg, int msglen);
@@ -405,7 +405,7 @@
struct usb_bus *busses;
-struct usbprog_jtag* usbprog_jtag_open()
+struct usbprog_jtag* usbprog_jtag_open(void)
{
struct usb_bus *bus;
struct usb_device *dev;
Index: src/target/target.c
===
--- src/target/target.c (Revision 1292)
+++ src/target/target.c (Arbeitskopie)
@@ -4014,7 +4014,7 @@
static int fastload_num;
static struct FastLoad *fastload;
-static void free_fastload()
+static void free_fastload(void)
{
if (fastload!=NULL)
{
Index: src/flash/nand.c
===
--- src/flash/nand.c (Revision 1292)
+++ src/flash/nand.c (Arbeitskopie)
@@ -375,7 +375,7 @@
int nand_probe(struct nand_device_s *device)
{
u8 manufacturer_id, device_id;
- u8 id_buff[5];
+ u8 id_buff[6];
int retval;
int i;
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
[Openocd-development] [PATCH] manpage updates
Here's a bunch of updates and fixes for the manpage. - Mention that MIPS systems are supported - Mention Jim Tcl engine - Point to info page (not README) for a list of supported stuff - Document missing --pipe option - Fix copy-paste error (flex should have been openocd) Uwe. -- http://www.hermann-uwe.de | http://www.holsham-traders.de http://www.crazy-hacks.org | http://www.unmaintained-free-software.org Index: doc/openocd.1 === --- doc/openocd.1 (Revision 1306) +++ doc/openocd.1 (Arbeitskopie) @@ -1,37 +1,39 @@ -.TH OPENOCD 1 February 29, 2008 +.TH OPENOCD 1 January 08, 2009 .SH NAME openocd \- A free and open on\-chip debugging, in\-system programming and -boundary\-scan testing tool for ARM systems +boundary\-scan testing tool for ARM and MIPS systems .SH SYNOPSIS -.B openocd \fR[\fB\-fsdlchv\fR] [\fB\-\-file\fR filename] [\fB\-\-search\fR dirname] [\fB\-\-debug\fR debuglevel] [\fB\-\-log_output\fR filename] [\fB\-\-command\fR cmd] [\fB\-\-help\fR] [\fB\-\-version\fR] +.B openocd \fR[\fB\-fsdlcphv\fR] [\fB\-\-file\fR filename] [\fB\-\-search\fR dirname] [\fB\-\-debug\fR debuglevel] [\fB\-\-log_output\fR filename] [\fB\-\-command\fR cmd] [\fB\-\-pipe\fR] [\fB\-\-help\fR] [\fB\-\-version\fR] .SH DESCRIPTION .B OpenOCD is an on\-chip debugging, in\-system programming and boundary\-scan -testing tool for ARM systems. +testing tool for various ARM and MIPS systems. .PP The debugger uses an IEEE 1149\-1 compliant JTAG TAP bus master to access -on\-chip debug functionality available on ARM7/9, XScale, Cortex-M3, and -Marvell Feroceon (as found in the Orion SoC family) based -microcontrollers / system\-on\-chip solutions. +on\-chip debug functionality available on ARM based microcontrollers or +system-on-chip solutions. For MIPS systems the EJTAG interface is supported. .PP -User interaction is realized through a telnet command line interface and -a gdb (the GNU debugger) remote protocol server. +User interaction is realized through a telnet command line interface, +a gdb (the GNU debugger) remote protocol server, and a simplified RPC +connection that can be used to interface with OpenOCD's Jim Tcl engine. .PP OpenOCD supports various different types of JTAG interfaces/programmers, -please check the README for the complete list. +please check the \fIopenocd\fR info page for the complete list. .SH OPTIONS .TP .B \-f, \-\-file filename Use configuration file .BR filename . -If this option is omitted, the config file +In order to specify multiple config files, you can use multiple +.B \-\-file +arguments. If this option is omitted, the config file .B openocd.cfg in the current working directory will be used. .TP .B \-s, \-\-search dirname Search for config files and scripts in the directory .BR dirname . -If this option is omitted, openocd searches for config files and scripts +If this option is omitted, OpenOCD searches for config files and scripts in the current directory. .TP .B \-d, \-\-debug debuglevel @@ -58,6 +60,9 @@ Run the command .BR cmd . .TP +.B \-p, \-\-pipe +Use pipes when talking to gdb. +.TP .B \-h, \-\-help Show a help text and exit. .TP @@ -78,10 +83,12 @@ .B openocd is maintained as a Texinfo manual. If the .BR info +(or +.BR pinfo ) and .BR openocd programs are properly installed at your site, the command -.B info flex +.B info openocd should give you access to the complete manual. .PP Also, the OpenOCD wiki contains some more information and examples: ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] First pass at 0.1.0 source distribution
On Fri, Jan 16, 2009 at 09:47:21PM -0800, Rick Altherr wrote: I've built a new source tarball and put it at the same URL. It would be very helpful if someone (or multiple someones) could see if it builds on Linux, FreeBSD, and Windows. Please try enabling all of the USB-based interfaces and any of the others that are applicable to your platform. Tested on Debian unstable with: ./configure --enable-parport --enable-parport_ppdev --enable-ft2232_libftdi --enable-ep93xx --enable-at91rm9200 --enable-usbprog --enable-presto_libftdi --enable-jlink --enable-vsllink --enable-rlink --enable-dummy --enable-gw16012 --enable-amtjtagaccel (the usual set of options I use for building the official Debian package) Compile-tested only. Note: 'make install' doesn't install the manpage, I'll send a patch to fix that. Uwe. -- http://www.hermann-uwe.de | http://www.holsham-traders.de http://www.crazy-hacks.org | http://www.unmaintained-free-software.org ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
[Openocd-development] [PATCH] install manpage upon 'make install', ship it in tarballs
See attached patch. Needs a './bootstrap ./configure make distcheck' after applying the patch to make a new tarball with the manpage included. HTH, Uwe. -- http://www.hermann-uwe.de | http://www.holsham-traders.de http://www.crazy-hacks.org | http://www.unmaintained-free-software.org Index: doc/Makefile.am === --- doc/Makefile.am (Revision 1334) +++ doc/Makefile.am (Arbeitskopie) @@ -1,3 +1,5 @@ info_TEXINFOS = openocd.texi openocd_TEXINFOS = fdl.texi +man_MANS = openocd.1 +EXTRA_DIST = openocd.1 ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Final pass at 0.1.0 source distribution
On Mon, Jan 19, 2009 at 04:04:23PM -0700, Steve Franks wrote: We do install them in a common location, but you still need to tell us which files to load. The standard configs are just installed in the standard search path. So, '-f target/at91r40008.cfg' looks for target/at91r40008.cfg in the current directory and then in the search paths. We split the configs into interfaces, targets, and boards to make it clear which is which. I was just poking around in there, and they're definitely in src, but I'm not seeing where they landed in /usr? The only thing I see is /usr/local/share/openocd/contrib/libdcc - I only mention this in case there was somewhere the install needs tweaked... They're in $PREFIX/lib/openocd/*, e.g. /usr/lib/openocd/*. Uwe. -- http://www.hermann-uwe.de | http://www.holsham-traders.de http://www.crazy-hacks.org | http://www.unmaintained-free-software.org ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
[Openocd-development] --debug broken
Hi, I don't have much time to investigate this right now, but -d / --debug seems to be broken. It _might_ work when you pass e.g. '-d 3' the first time on the command line, but on the next run of the _same_ command line (just changing '-d 3' to e.g. '-d 1') it will not notice the change. OpenOCD still is on loglevel 3, though it should now be 1. The value seems to be cached somewhere, no idea why. Uwe. -- http://www.hermann-uwe.de | http://www.holsham-traders.de http://www.crazy-hacks.org | http://www.unmaintained-free-software.org ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] udev rules for openocd
On Tue, Jan 20, 2009 at 07:53:14AM -0600, lou.openocd...@fixit.nospammail.net
wrote:
And another part for rlink:
# Raisonance RLink
SYSFS{idVendor}==138e, SYSFS{idProduct}==9000, MODE=664, GROUP=plugdev
Does the 4 in 664 make sense?
Yes, you don't want _all_ users to have write access, only those in the
plugdev group.
Uwe.
--
http://www.hermann-uwe.de | http://www.holsham-traders.de
http://www.crazy-hacks.org | http://www.unmaintained-free-software.org
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] udev rules for openocd
On Tue, Jan 20, 2009 at 08:39:14PM +0100, Uwe Hermann wrote:
On Tue, Jan 20, 2009 at 09:07:42AM -0800, Rick Altherr wrote:
I await an updated file that includes all the additional device lines
that have flown by on this list.
Sure, attached.
Oops, forgot one. Updated patch attached.
Uwe.
--
http://www.hermann-uwe.de | http://www.holsham-traders.de
http://www.crazy-hacks.org | http://www.unmaintained-free-software.org
Index: contrib/openocd.udev
===
--- contrib/openocd.udev (Revision 0)
+++ contrib/openocd.udev (Revision 0)
@@ -0,0 +1,25 @@
+BUS!=usb, ACTION!=add, SUBSYSTEM!==usb_device, GOTO=openocd_rules_end
+
+# Olimex ARM-USB-OCD
+SYSFS{idVendor}==15ba, SYSFS{idProduct}==0003, MODE=664, GROUP=plugdev
+
+# Olimex ARM-USB-OCD-TINY
+SYSFS{idVendor}==15ba, SYSFS{idProduct}==0004, MODE=664, GROUP=plugdev
+
+# USBprog with OpenOCD firmware
+SYSFS{idVendor}==1781, SYSFS{idProduct}==0c63, MODE=664, GROUP=plugdev
+
+# Amontec JTAGkey
+SYSFS{idVendor}==0403, SYSFS{idProduct}==cff8, MODE=664, GROUP=plugdev
+
+# Amontec JTAGkey-HiSpeed
+SYSFS{idVendor}==0fbb, SYSFS{idProduct}==1000, MODE=664, GROUP=plugdev
+
+# IAR J-Link USB
+SYSFS{idVendor}==1366, SYSFS{idProduct}==0101, MODE=664, GROUP=plugdev
+
+# Raisonance RLink
+SYSFS{idVendor}==138e, SYSFS{idProduct}==9000, MODE=664, GROUP=plugdev
+
+LABEL=openocd_rules_end
+
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] udev rules for openocd
On Tue, Jan 20, 2009 at 10:15:42AM -0600, lou.openocd...@fixit.nospammail.net wrote: Of course. Why not 0, then? Does it make sense to give everybody read access to the node? Ah, I see. I don't know which one should be used, I don't mind either way. As far as I've seen in /etc/udev/ on my system some packages use 664 and some use 660; it probably doesn't matter much in practice. Uwe. -- http://www.hermann-uwe.de | http://www.holsham-traders.de http://www.crazy-hacks.org | http://www.unmaintained-free-software.org ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
[Openocd-development] [PATCH] Drop gdb/telnet port lines from partport* cfg files
Hi, Please correct me if I'm wrong, but I don't think the parport.cfg and parport_dlc5.cfg files should specify gdb/telnet ports explicitly, none of the other interface files do either. The default ports for telnet/gdb/tcl (//) will then be used instead. Patch attached. Uwe. -- http://www.hermann-uwe.de | http://www.holsham-traders.de http://www.crazy-hacks.org | http://www.unmaintained-free-software.org Index: src/target/interface/parport.cfg === --- src/target/interface/parport.cfg (Revision 1411) +++ src/target/interface/parport.cfg (Arbeitskopie) @@ -1,8 +1,4 @@ -telnet_port -gdb_port 2001 - interface parport parport_port 0xc8b8 parport_cable wiggler jtag_speed 0 - Index: src/target/interface/parport_dlc5.cfg === --- src/target/interface/parport_dlc5.cfg (Revision 1411) +++ src/target/interface/parport_dlc5.cfg (Arbeitskopie) @@ -1,6 +1,3 @@ -telnet_port -gdb_port 2001 - interface parport parport_port /dev/parport0 parport_cable dlc5 ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] OpenOCD flash programming STR9-comStick
Hi, On Mon, Mar 16, 2009 at 12:01:44PM +, David Lange wrote: I found OpenOCD to be a free and command based flash programming tool. I currently have a project running using the Hitex USB stick STR9-comStick. However so far I only was able to download the application using the IDE HiTop. What I am looking for is a tool to automate this via the command line. In the OpenOCD pdf-documentation I found that on page 9 the link to the comstick is exactly the device that I use. Does anyone have experiences using OpenOCD in combination with the STR9-comStick? I have such a device here, but didn't test much so far. What you generally want is to start OpenOCD like this (for example): $ openocd -f /usr/lib/openocd/interface/str9-comstick.cfg -f /usr/lib/openocd/target/str9comstick.cfg Open On-Chip Debugger 1.0 (2009-03-12-01:10) svn:r1409 BUGS? Read /usr/share/doc/openocd/BUGS $URL: http://svn.berlios.de/svnroot/repos/openocd/trunk/src/openocd.c $ 3000 kHz Runtime error, file /usr/lib/openocd/target/str9comstick.cfg, line 19: can't read _CHIPNAME: no such variable However, as you can see this currently results in an error (as of r1409), I guess this needs to be fixed in svn. I didn't have the time to investigate the issue further, yet. Assuming the OpenOCD connection works, you use 'telnet localhost ' to connect to OpenOCD via telnet, where you can the use all commands available. HTH, Uwe. -- http://www.hermann-uwe.de | http://www.holsham-traders.de http://www.crazy-hacks.org | http://www.unmaintained-free-software.org ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
[Openocd-development] [PATCH] LPC2148 _CPUTAPID and random other fixes
Here's a patch for a real _CPUTAPID entry for the LPC2148. I don't know
if they're the same for all LPC214x, this number is from an Olimex
LPC-H2148. The chip on that board is LPC2148FBD64.
Also fix a few cosmetic issues and comments in the file and add
more docs and pointers to the datasheet.
Uwe.
--
http://www.hermann-uwe.de | http://www.holsham-traders.de
http://www.crazy-hacks.org | http://www.unmaintained-free-software.org
Index: src/target/target/lpc2148.cfg
===
--- src/target/target/lpc2148.cfg (Revision 1426)
+++ src/target/target/lpc2148.cfg (Arbeitskopie)
@@ -1,49 +1,51 @@
-
if { [info exists CHIPNAME] } {
- set _CHIPNAME $CHIPNAME
-} else {
- set _CHIPNAME lpc2148
+ set _CHIPNAME $CHIPNAME
+} else {
+ set _CHIPNAME lpc2148
}
-if { [info exists ENDIAN] } {
- set _ENDIAN $ENDIAN
-} else {
- set _ENDIAN little
+if { [info exists ENDIAN] } {
+ set _ENDIAN $ENDIAN
+} else {
+ set _ENDIAN little
}
if { [info exists CPUTAPID ] } {
set _CPUTAPID $CPUTAPID
} else {
- # force an error till we get a good number
- set _CPUTAPID 0x
+ set _CPUTAPID 0x4f1f0f0f
}
-#delays on reset lines
jtag_nsrst_delay 200
jtag_ntrst_delay 200
-# NOTE!!! LPCs need reset pulled while RTCK is low. 0 to activate
+# NOTE!!! LPCs need reset pulled while RTCK is low. 0 to activate
# JTAG, power-on reset is not enough, i.e. you need to perform a
-# reset before being able to talk to the LPC2148, attach is not
-# possible.
+# reset before being able to talk to the LPC2148, attach is not possible.
-#use combined on interfaces or targets that can't set TRST/SRST separately
reset_config trst_and_srst srst_pulls_trst
-#jtag scan chain
jtag newtap $_CHIPNAME cpu -irlen 4 -ircapture 0x1 -irmask 0xf -expected-id $_CPUTAPID
set _TARGETNAME [format %s.cpu $_CHIPNAME]
+
target create $_TARGETNAME arm7tdmi -endian $_ENDIAN -chain-position $_TARGETNAME -variant arm7tdmi-s_r4
+
$_TARGETNAME configure -work-area-virt 0 -work-area-phys 0x4000 -work-area-size 0x4000 -work-area-backup 0
+
$_TARGETNAME configure -event reset-init {
- # Force target into ARM state
+ # Force target into ARM state.
soft_reset_halt
- #do not remap 0x-0x0020 to anything but the flash
- mwb 0xE01FC040 0x01
-
+
+ # Do not remap 0x-0x0020 to anything but the flash (i.e. select
+ # User Flash Mode where interrupt vectors are _not_ remapped,
+ # and reside in flash instead).
+ #
+ # See section 7.1 on page 32 (Memory Mapping control register) in
+ # UM10139: Volume 1: LPC214x User Manual, Rev. 02 -- 25 July 2006.
+ # http://www.standardics.nxp.com/support/documents/microcontrollers/pdf/user.manual.lpc2141.lpc2142.lpc2144.lpc2146.lpc2148.pdf
+ mwb 0xE01FC040 0x01
}
-
-#flash bank lpc2000 base size 0 0 target# variant
+# flash bank lpc2000 base size 0 0 target# variant clock [calc_checksum]
flash bank lpc2000 0x0 0x7d000 0 0 0 lpc2000_v2 14765
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
[Openocd-development] [PATCH] Fix incorrect ixp42x stuff
It's astounding how many ways you can find to misspell ixp42x.
Fix various ixp42x typos in config files. Also, rename an incorrectly
named 'pxi42x.cfg' file.
Untested, but should work. I doubt the current svn files work.
Uwe.
--
http://www.hermann-uwe.de | http://www.holsham-traders.de
http://www.crazy-hacks.org | http://www.unmaintained-free-software.org
Index: src/target/target/nslu2.cfg
===
--- src/target/target/nslu2.cfg (Revision 1427)
+++ src/target/target/nslu2.cfg (Arbeitskopie)
@@ -1,7 +1,7 @@
-# This is for the LinkSys (CYSCO) LSLU2 board
-# It is an Intel XSCALE IPX420 CPU.
+# This is for the LinkSys (CISCO) NSLU2 board
+# It is an Intel XSCALE IXP420 CPU.
-source [find target/ipx42x.cfg]
+source [find target/ixp42x.cfg]
# The _TARGETNAME is set by the above.
$_TARGETNAME configure -work-area-virt 0 -work-area-phys 0x0002 -work-area-size 0x1 -work-area-backup 0
Index: src/target/target/pxi42x.cfg
===
--- src/target/target/pxi42x.cfg (Revision 1427)
+++ src/target/target/pxi42x.cfg (Arbeitskopie)
@@ -1,32 +0,0 @@
-#xscale ixp42x CPU
-
-
-if { [info exists CHIPNAME] } {
- set _CHIPNAME $CHIPNAME
-} else {
- set _CHIPNAME ipx42x
-}
-
-if { [info exists ENDIAN] } {
- set _ENDIAN $ENDIAN
-} else {
- # this defaults to a bigendian
- set _ENDIAN big
-}
-
-if { [info exists CPUTAPID ] } {
- set _CPUTAPID $CPUTAPID
-} else {
- # force an error till we get a good number
- set _CPUTAPID 0x
-}
-
-#use combined on interfaces or targets that can?t set TRST/SRST separately
-reset_config srst_only srst_pulls_trst
-#jtag scan chain
-
-jtag newtap $_CHIPNAME cpu -irlen 7 -ircapture 0x1 -irmask 0x7f -expected-id $_CPUTAPID
-
-set _TARGETNAME [format %s.cpu $_CHIPNAME]
-target create $_TARGETNAME xscale -endian $_ENDIAN -chain-position $_TARGETNAME -variant ipxP42x
-
Index: src/target/target/ixp42x.cfg
===
--- src/target/target/ixp42x.cfg (Revision 0)
+++ src/target/target/ixp42x.cfg (Revision 0)
@@ -0,0 +1,32 @@
+#xscale ixp42x CPU
+
+
+if { [info exists CHIPNAME] } {
+ set _CHIPNAME $CHIPNAME
+} else {
+ set _CHIPNAME ixp42x
+}
+
+if { [info exists ENDIAN] } {
+ set _ENDIAN $ENDIAN
+} else {
+ # this defaults to a bigendian
+ set _ENDIAN big
+}
+
+if { [info exists CPUTAPID ] } {
+ set _CPUTAPID $CPUTAPID
+} else {
+ # force an error till we get a good number
+ set _CPUTAPID 0x
+}
+
+#use combined on interfaces or targets that can?t set TRST/SRST separately
+reset_config srst_only srst_pulls_trst
+#jtag scan chain
+
+jtag newtap $_CHIPNAME cpu -irlen 7 -ircapture 0x1 -irmask 0x7f -expected-id $_CPUTAPID
+
+set _TARGETNAME [format %s.cpu $_CHIPNAME]
+target create $_TARGETNAME xscale -endian $_ENDIAN -chain-position $_TARGETNAME -variant ixp42x
+
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
[Openocd-development] [PATCH] New board configs: Olimex LPC-H2148, Keil MCB2140
Add new board configs: Olimex LPC-H2148, Keil MCB2140. Both boards use an LPC2148, no external flash or RAM. Uwe. -- http://www.hermann-uwe.de | http://www.holsham-traders.de http://www.crazy-hacks.org | http://www.unmaintained-free-software.org Index: src/target/board/olimex_lpc_h2148.cfg === --- src/target/board/olimex_lpc_h2148.cfg (Revision 0) +++ src/target/board/olimex_lpc_h2148.cfg (Revision 0) @@ -0,0 +1,8 @@ +# +# Olimex LPC-H2148 eval board +# +# http://www.olimex.com/dev/lpc-h2148.html +# + +source [find target/lpc2148.cfg] + Index: src/target/board/keil_mcb2140.cfg === --- src/target/board/keil_mcb2140.cfg (Revision 0) +++ src/target/board/keil_mcb2140.cfg (Revision 0) @@ -0,0 +1,8 @@ +# +# Keil MCB2140 eval board +# +# http://www.keil.com/mcb2140/picture.asp +# + +source [find target/lpc2148.cfg] + ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
[Openocd-development] [PATCH] Improve comments of interface files
Add full company name (if any), interface/dongle name, and URL to all interface config files. Please check the infos, I may not have gotten all of them right. Uwe. -- http://www.hermann-uwe.de | http://www.holsham-traders.de http://www.crazy-hacks.org | http://www.unmaintained-free-software.org Index: src/target/interface/usbprog.cfg === --- src/target/interface/usbprog.cfg (Revision 1438) +++ src/target/interface/usbprog.cfg (Arbeitskopie) @@ -1,7 +1,8 @@ # -# USBprog +# Embedded Projects USBprog # # http://embedded-projects.net/index.php?page_id=135 # interface usbprog + Index: src/target/interface/stm32-stick.cfg === --- src/target/interface/stm32-stick.cfg (Revision 1438) +++ src/target/interface/stm32-stick.cfg (Arbeitskopie) @@ -1,5 +1,11 @@ -# ftdi interface +# +# Hitex STM32-PerformanceStick +# +# http://www.hitex.com/index.php?id=340 +# + interface ft2232 ft2232_device_desc STM32-PerformanceStick A ft2232_layout stm32stick ft2232_vid_pid 0x0640 0x002d + Index: src/target/interface/calao-usb-a9260-c01.cfg === --- src/target/interface/calao-usb-a9260-c01.cfg (Revision 1438) +++ src/target/interface/calao-usb-a9260-c01.cfg (Arbeitskopie) @@ -1,11 +1,13 @@ # -# Calao Systems USB-A9260-C01 +# CALAO Systems USB-A9260-C01 # # http://www.calao-systems.com/ # + interface ft2232 ft2232_layout jtagkey ft2232_device_desc USB-A9260 ft2232_vid_pid 0x0403 0x6010 script interface/calao-usb-a9260.cfg script target/at91sam9260minimal.cfg + Index: src/target/interface/signalyzer.cfg === --- src/target/interface/signalyzer.cfg (Revision 1438) +++ src/target/interface/signalyzer.cfg (Arbeitskopie) @@ -1,5 +1,11 @@ -#interface +# +# Xverve Signalyzer Tool (DT-USB-ST) +# +# http://www.signalyzer.com/products/development-tools/signalyzer-tool-dt-usb-st.html +# + interface ft2232 ft2232_device_desc Signalyzer A ft2232_layout signalyzer ft2232_vid_pid 0x0403 0xbca0 + Index: src/target/interface/parport.cfg === --- src/target/interface/parport.cfg (Revision 1438) +++ src/target/interface/parport.cfg (Arbeitskopie) @@ -1,3 +1,7 @@ +# +# Parallel port wiggler (many clones available) on port 0xc8b8 +# + interface parport parport_port 0xc8b8 parport_cable wiggler @@ -2 +6,2 @@ jtag_speed 0 + Index: src/target/interface/calao-usb-a9260-c02.cfg === --- src/target/interface/calao-usb-a9260-c02.cfg (Revision 1438) +++ src/target/interface/calao-usb-a9260-c02.cfg (Arbeitskopie) @@ -1,11 +1,13 @@ # -# Calao Systems USB-A9260-C02 +# CALAO Systems USB-A9260-C02 # # http://www.calao-systems.com/ # + interface ft2232 ft2232_layout jtagkey ft2232_device_desc USB-A9260 A ft2232_vid_pid 0x0403 0x6001 script interface/calao-usb-a9260.cfg script target/at91sam9260minimal.cfg + Index: src/target/interface/at91rm9200.cfg === --- src/target/interface/at91rm9200.cfg (Revision 1438) +++ src/target/interface/at91rm9200.cfg (Arbeitskopie) @@ -1,3 +1,9 @@ -#interface +# +# Various Atmel AT91RM9200 boards +# +# TODO: URL? +# + interface at91rm9200 at91rm9200_device rea_ecr + Index: src/target/interface/turtelizer2.cfg === --- src/target/interface/turtelizer2.cfg (Revision 1438) +++ src/target/interface/turtelizer2.cfg (Arbeitskopie) @@ -1,5 +1,11 @@ -#interface +# +# egnite Turtelizer 2 +# +# http://www.ethernut.de/en/hardware/turtelizer/index.html +# + interface ft2232 ft2232_device_desc Turtelizer JTAG/RS232 Adapter A ft2232_layout turtelizer2 ft2232_vid_pid 0x0403 0xbdc8 + Index: src/target/interface/chameleon.cfg === --- src/target/interface/chameleon.cfg (Revision 1438) +++ src/target/interface/chameleon.cfg (Arbeitskopie) @@ -1,4 +1,9 @@ -#interface +# +# Amontec Chameleon POD +# +# http://www.amontec.com/chameleon.shtml +# + interface parport parport_cable chameleon Index: src/target/interface/dummy.cfg === --- src/target/interface/dummy.cfg (Revision 1438) +++ src/target/interface/dummy.cfg (Arbeitskopie) @@ -1 +1,6 @@ +# +# Dummy interface (for testing purposes) +# + interface dummy + Index: src/target/interface/parport_dlc5.cfg === --- src/target/interface/parport_dlc5.cfg (Revision 1438) +++ src/target/interface/parport_dlc5.cfg (Arbeitskopie) @@ -1,3 +1,9 @@ +# +# Xilinx Parallel Cable III 'DLC 5' (and various clones) +# +# http://www.xilinx.com/itp/xilinx4/data/docs/pac/appendixb.html +# +
[Openocd-development] [PATCH] Add missing STM32 BSTAPID to list of available ones
Add missing STM32 0x06412041, Revision A BSTAPID to list of available ones.
This is checked against revision 8, 11-Feb-2009, of the RM0008 manual
from http://www.st.com/stonline/products/literature/rm/13902.pdf.
Also, I noticed that stm32.cfg will _not_ work for some targets per se,
as it basically does:
set _BSTAPID 0x06410041
set _BSTAPID 0x16410041
set _BSTAPID 0x06414041
which will (unless I'm mistaken) overwrite the variable and only the
last one will take effect. So stm32.cfg shouldn't normally be used
standalone, but rather 'source'd by another (board) file which overrides
the _BSTAPID, correct?
Uwe.
--
http://www.hermann-uwe.de | http://www.holsham-traders.de
http://www.crazy-hacks.org | http://www.unmaintained-free-software.org
Index: src/target/target/stm32.cfg
===
--- src/target/target/stm32.cfg (Revision 1440)
+++ src/target/target/stm32.cfg (Arbeitskopie)
@@ -36,11 +36,13 @@
} else {
# See STM Document RM0008
# Section 26.6.2
- # Medium Density RevA
+ # Low density devices, Rev A
+ set _BSTAPID 0x06412041
+ # Medium density devices, Rev A
set _BSTAPID 0x06410041
- # Rev B and Rev Z
+ # Medium density devices, Rev B and Rev Z
set _BSTAPID 0x16410041
- # High Density Devices, Rev A
+ # High density devices, Rev A
set _BSTAPID 0x06414041
}
jtag newtap $_CHIPNAME bs -irlen 5 -ircapture 0x1 -irmask 0x1 -expected-id $_BSTAPID
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] [PATCH] Oocdlink interface
On Wed, Mar 25, 2009 at 10:42:13PM +0100, joern kaipf wrote: Index: src/target/interface/oocdlink.cfg === --- src/target/interface/oocdlink.cfg (Revision 0) +++ src/target/interface/oocdlink.cfg (Revision 0) It seems this patch was forgotten. Please apply the slightly changed version attached in this mail, I added the name + URL as with the other files now... Uwe. -- http://www.hermann-uwe.de | http://www.holsham-traders.de http://www.crazy-hacks.org | http://www.unmaintained-free-software.org Index: src/target/interface/oocdlink.cfg === --- src/target/interface/oocdlink.cfg (Revision 0) +++ src/target/interface/oocdlink.cfg (Revision 0) @@ -0,0 +1,12 @@ +# +# Joern Kaipf's OOCDLink +# +# http://www.joernonline.de/contrexx2/cms/index.php?page=126 +# + +interface ft2232 +ft2232_device_desc OOCDLink A +ft2232_layout oocdlink +ft2232_vid_pid 0x0403 0xbaf8 +jtag_khz 5 + ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
[Openocd-development] Help with IAR ST Butterfly Min і eval board
Hi, I'm trying to build a config file for the IAR ST Butterfly Minі eval board. This is what I have so far, but it doesn't work quite yet: Index: src/target/board/iar_st_butterfly_mini.cfg === --- src/target/board/iar_st_butterfly_mini.cfg (Revision 0) +++ src/target/board/iar_st_butterfly_mini.cfg (Revision 0) @@ -0,0 +1,11 @@ +# +# IAR ST Butterfly Mini eval board +# +# http://www.iar.com/stmini +# + +set BSTAPID 0x06412041 + +source [find interface/jlink.cfg] +source [find target/stm32.cfg] + Here's what I get: $ ./bin/openocd -f lib/openocd/board/iar_st_butterfly_mini.cfg ./bin/openocd -f lib/openocd/board/iar_st_butterfly_mini.cfg Open On-Chip Debugger 1.0 (2009-04-03-04:32) svn:1447M BUGS? Read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS $URL: http://svn.berlios.de/svnroot/repos/openocd/trunk/src/openocd.c $ 500 kHz Info : J-Link ARM-OB STM32 compiled Jan 13 2009 17:07:17 Info : Vref = 3.300 TCK = 1 TDI = 0 TDO = 1 TMS = 1 SRST = 1 TRST = 1 Info : J-Link JTAG Interface ready Info : JTAG tap: stm32.cpu tap/device found: 0x3ba00477 (Manufacturer: 0x23b, Part: 0xba00, Version: 0x3) Info : JTAG Tap/device matched Info : JTAG tap: stm32.bs tap/device found: 0x06412041 (Manufacturer: 0x020, Part: 0x6412, Version: 0x0) Info : JTAG Tap/device matched Warn : Block read error address 0xe000ed00, count 0x1 Warn : no telnet port specified, using default port Warn : no gdb port specified, using default port Warn : no tcl port specified, using default port Error: AHBAP: dp_select 0x10, ap_csw 0xa202, ap_tar 0xe000edf0 Error: SWJ-DP OVERRUN - check clock or reduce jtag speed Error: AHBAP: dp_select 0x10, ap_csw 0xa202, ap_tar 0xe000ed20 Error: SWJ-DP OVERRUN - check clock or reduce jtag speed Error: AHBAP: dp_select 0x10, ap_csw 0xa202, ap_tar 0xe000ed20 Error: SWJ-DP OVERRUN - check clock or reduce jtag speed Error: AHBAP: dp_select 0x10, ap_csw 0xa202, ap_tar 0xe000ed20 Error: SWJ-DP OVERRUN - check clock or reduce jtag speed Error: AHBAP: dp_select 0x10, ap_csw 0xa202, ap_tar 0xe000ed20 Error: SWJ-DP OVERRUN - check clock or reduce jtag speed Error: AHBAP: dp_select 0x10, ap_csw 0xa202, ap_tar 0xe000ed20 Error: SWJ-DP OVERRUN - check clock or reduce jtag speed [etc. etc.] $ lsusb -v Bus 003 Device 019: ID 1366:0101 Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x1366 idProduct 0x0101 bcdDevice1.00 iManufacturer 1 SEGGER iProduct2 J-Link iSerial 3 123456 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 32 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xc0 Self Powered MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 1 Device Status: 0x0001 Self Powered I tried to set jtag_speed 0 in stm32.cfg, but that didn't help. Also, I applied the recent jlink patch from the mailing list, no difference either. Any ideas where to look? Uwe. -- http://www.hermann-uwe.de | http://www.holsham-traders.de http://www.crazy-hacks.org | http://www.unmaintained-free-software.org ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Help with IAR ST Butterfly Min і eval board
On Fri, Apr 03, 2009 at 05:31:10PM +0200, Freddie Chopin wrote: Uwe Hermann pisze: I tried to set jtag_speed 0 in stm32.cfg, but that didn't help. jtag_speed 0 gives you the maximum possible speed, as jtag_speed is a divisor Oops, true. I tried a few values for jtag_khz, e.g. 100, 10, and 1, still no change: $URL: http://svn.berlios.de/svnroot/repos/openocd/trunk/src/openocd.c $ 1 kHz Info : J-Link ARM-OB STM32 compiled Jan 13 2009 17:07:17 Info : Vref = 3.300 TCK = 1 TDI = 0 TDO = 1 TMS = 1 SRST = 1 TRST = 1 Info : J-Link JTAG Interface ready Info : JTAG tap: stm32.cpu tap/device found: 0x3ba00477 (Manufacturer: 0x23b, Part: 0xba00, Version: 0x3) Info : JTAG Tap/device matched Info : JTAG tap: stm32.bs tap/device found: 0x06412041 (Manufacturer: 0x020, Part: 0x6412, Version: 0x0) Info : JTAG Tap/device matched Error: AHBAP: dp_select 0x0, ap_csw 0xa212, ap_tar 0x Error: SWJ-DP OVERRUN - check clock or reduce jtag speed Error: AHBAP: dp_select 0x10, ap_csw 0xa202, ap_tar 0xe000edf0 Error: SWJ-DP OVERRUN - check clock or reduce jtag speed [...] Uwe. -- http://www.hermann-uwe.de | http://www.holsham-traders.de http://www.crazy-hacks.org | http://www.unmaintained-free-software.org ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
[Openocd-development] [PATCH] Drop non-A variants of ft2232 targets
Unless I'm mistaken, recent OpenOCD versions will automatically work with both A and non-A variants of the ft2232_device_desc variables. For example, ft2232_device_desc Amontec JTAGkey and ft2232_device_desc Amontec JTAGkey A should both work fine, on Windows as well as on Mac OS X and Linux, correct? If that is the case, let's drop all non-A variants, see patch. Also: Let JTAGkey-tiny include JTAGkey, as they're the same. Uwe. -- http://www.hermann-uwe.de | http://www.holsham-traders.de http://www.crazy-hacks.org | http://www.unmaintained-free-software.org Index: src/target/interface/calao-usb-a9260-c01.cfg === --- src/target/interface/calao-usb-a9260-c01.cfg (Revision 1454) +++ src/target/interface/calao-usb-a9260-c01.cfg (Arbeitskopie) @@ -6,7 +6,7 @@ interface ft2232 ft2232_layout jtagkey -ft2232_device_desc USB-A9260 +ft2232_device_desc USB-A9260 A ft2232_vid_pid 0x0403 0x6010 script interface/calao-usb-a9260.cfg script target/at91sam9260minimal.cfg Index: src/target/interface/luminary.cfg === --- src/target/interface/luminary.cfg (Revision 1454) +++ src/target/interface/luminary.cfg (Arbeitskopie) @@ -1,5 +1,5 @@ # -# Luminary Micro LM3S811 Evaluation Kit(s) +# Luminary Micro Stellaris LM3S811 Evaluation Kit # # http://www.luminarymicro.com/products/stellaris_811_evaluation_kits.html # @@ -7,4 +7,5 @@ interface ft2232 ft2232_device_desc Stellaris Evaluation Board A ft2232_layout evb_lm3s811 +ft2232_vid_pid 0x0403 0xbcd9 Index: src/target/interface/olimex-jtag-tiny.cfg === --- src/target/interface/olimex-jtag-tiny.cfg (Revision 1454) +++ src/target/interface/olimex-jtag-tiny.cfg (Arbeitskopie) @@ -4,12 +4,8 @@ # http://www.olimex.com/dev/arm-usb-tiny.html # -# TODO: FIXME -# Linux USB tends to see the device description without the 'A' as in target/olimex-jtag-tiny.cfg, -# but Windows still needs the 'A'. This is a replacement for Linux users. - interface ft2232 -ft2232_device_desc Olimex OpenOCD JTAG TINY +ft2232_device_desc Olimex OpenOCD JTAG TINY A ft2232_layout olimex-jtag ft2232_vid_pid 0x15ba 0x0004 Index: src/target/interface/sheevaplug.cfg === --- src/target/interface/sheevaplug.cfg (Revision 1454) +++ src/target/interface/sheevaplug.cfg (Arbeitskopie) @@ -7,5 +7,6 @@ interface ft2232 ft2232_layout sheevaplug ft2232_vid_pid 0x0403 0x6010 +# TODO: Add ft2232_device_desc? jtag_khz 3000 Index: src/target/interface/flyswatter.cfg === --- src/target/interface/flyswatter.cfg (Revision 1454) +++ src/target/interface/flyswatter.cfg (Arbeitskopie) @@ -5,7 +5,7 @@ # interface ft2232 -ft2232_device_desc Flyswatter +ft2232_device_desc Flyswatter A ft2232_layout flyswatter ft2232_vid_pid 0x0403 0x6010 jtag_speed 1 Index: src/target/interface/olimex-arm-usb-ocd.cfg === --- src/target/interface/olimex-arm-usb-ocd.cfg (Revision 1454) +++ src/target/interface/olimex-arm-usb-ocd.cfg (Arbeitskopie) @@ -5,7 +5,7 @@ # interface ft2232 -ft2232_device_desc Olimex OpenOCD JTAG +ft2232_device_desc Olimex OpenOCD JTAG A ft2232_layout olimex-jtag ft2232_vid_pid 0x15ba 0x0003 Index: src/target/interface/luminary-libftdi.cfg === --- src/target/interface/luminary-libftdi.cfg (Revision 1454) +++ src/target/interface/luminary-libftdi.cfg (Arbeitskopie) @@ -1,11 +0,0 @@ -# -# Luminary Micro Stellaris LM3S811 Evaluation Kit -# -# http://www.luminarymicro.com/products/stellaris_811_evaluation_kits.html -# - -interface ft2232 -ft2232_device_desc Stellaris Evaluation Board -ft2232_layout evb_lm3s811 -ft2232_vid_pid 0x0403 0xbcd9 - Index: src/target/interface/openocd-usb.cfg === --- src/target/interface/openocd-usb.cfg (Revision 1454) +++ src/target/interface/openocd-usb.cfg (Arbeitskopie) @@ -6,7 +6,7 @@ interface ft2232 ft2232_vid_pid 0x0403 0x6010 -ft2232_device_desc Dual RS232 +ft2232_device_desc Dual RS232 A ft2232_layout oocdlink ft2232_latency 2 # 6/(1+n) Mhz TCLK Index: src/target/interface/jtagkey-tiny.cfg === --- src/target/interface/jtagkey-tiny.cfg (Revision 1454) +++ src/target/interface/jtagkey-tiny.cfg (Arbeitskopie) @@ -4,8 +4,6 @@ # http://www.amontec.com/jtagkey-tiny.shtml # -interface ft2232 -ft2232_device_desc Amontec JTAGkey -ft2232_layout jtagkey -ft2232_vid_pid 0x0403 0xcff8 +# The JTAGkey-tiny uses exactly the same config as the JTAGkey. +source [find interface/jtagkey.cfg] Index: src/target/interface/olimex-jtag-tiny-a.cfg
[Openocd-development] [PATCH] STR9-comStick board files for -A1 and -A2 revisions
As per OpenOCD flash programming STR9-comStick thread from a while ago, here are two board files for the different revisions of the Hitex STR9-comStick eval board. Uwe. -- http://www.hermann-uwe.de | http://www.holsham-traders.de http://www.crazy-hacks.org | http://www.unmaintained-free-software.org Index: src/target/board/hitex_str9_comstick_a1.cfg === --- src/target/board/hitex_str9_comstick_a1.cfg (Revision 0) +++ src/target/board/hitex_str9_comstick_a1.cfg (Revision 0) @@ -0,0 +1,11 @@ +# +# Hitex STR9-comStick, revision STR912CS-A1 +# +# http://www.hitex.com/index.php?id=383 +# + +set BSTAPID 0x1457f041 + +source [find interface/str9-comstick.cfg] +source [find target/str9comstick.cfg] + Index: src/target/board/hitex_str9_comstick_a2.cfg === --- src/target/board/hitex_str9_comstick_a2.cfg (Revision 0) +++ src/target/board/hitex_str9_comstick_a2.cfg (Revision 0) @@ -0,0 +1,11 @@ +# +# Hitex STR9-comStick, revision STR912CS-A2 +# +# http://www.hitex.com/index.php?id=383 +# + +set BSTAPID 0x2457f041 + +source [find interface/str9-comstick.cfg] +source [find target/str9comstick.cfg] + ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Help with IAR ST Butterfly Min і eval board
On Fri, Apr 03, 2009 at 05:42:48PM +0200, Magnus Lundin wrote: There is also a problem with error checking in the swjdp_transaction_endcheck that creates a recusive loop with this type of problem. Try the following patch. Hm, slightly different behavior, but still not working I think. Open On-Chip Debugger 1.0 (2009-04-03-20:11) svn:1454M BUGS? Read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS $URL: http://svn.berlios.de/svnroot/repos/openocd/trunk/src/openocd.c $ 1 kHz Info : J-Link ARM-OB STM32 compiled Jan 13 2009 17:07:17 Info : Vref = 3.300 TCK = 1 TDI = 0 TDO = 1 TMS = 1 SRST = 1 TRST = 1 Info : J-Link JTAG Interface ready Info : JTAG tap: stm32.cpu tap/device found: 0x3ba00477 (Manufacturer: 0x23b, Part: 0xba00, Version: 0x3) Info : JTAG Tap/device matched Info : JTAG tap: stm32.bs tap/device found: 0x06412041 (Manufacturer: 0x020, Part: 0x6412, Version: 0x0) Info : JTAG Tap/device matched Error: AHBAP Cached values: dp_select 0x0, ap_csw 0xa212, ap_tar 0x Error: SWJ-DP OVERRUN - check clock or reduce jtag speed Error: Read AHBAP_CSW 0x2352 Error: AHBAP Cached values: dp_select 0x0, ap_csw 0xa212, ap_tar 0x Error: SWJ-DP OVERRUN - check clock or reduce jtag speed Error: Read AHBAP_CSW 0x2352 Warn : Block read error address 0xe000ed00, count 0x1 Warn : no telnet port specified, using default port Warn : no gdb port specified, using default port Warn : no tcl port specified, using default port Error: AHBAP Cached values: dp_select 0x10, ap_csw 0xa202, ap_tar 0xe000edf0 Error: SWJ-DP OVERRUN - check clock or reduce jtag speed Error: Read AHBAP_CSW 0x2342 Error: AHBAP Cached values: dp_select 0x10, ap_csw 0xa202, ap_tar 0xe000edf0 Error: SWJ-DP OVERRUN - check clock or reduce jtag speed Error: Read AHBAP_CSW 0x2342 Error: AHBAP Cached values: dp_select 0x10, ap_csw 0xa202, ap_tar 0xe000edf0 Error: SWJ-DP OVERRUN - check clock or reduce jtag speed Error: Read AHBAP_CSW 0x2342 Error: AHBAP Cached values: dp_select 0x0, ap_csw 0xa212, ap_tar 0x Error: SWJ-DP OVERRUN - check clock or reduce jtag speed Error: Read AHBAP_CSW 0x2342 Warn : Block write error address 0xe0002000, wcount 0x1 Error: AHBAP Cached values: dp_select 0x10, ap_csw 0xa202, ap_tar 0xe000edf0 Error: SWJ-DP OVERRUN - check clock or reduce jtag speed Error: Read AHBAP_CSW 0x2342 Error: AHBAP Cached values: dp_select 0x10, ap_csw 0xa202, ap_tar 0xe000edf0 Error: SWJ-DP OVERRUN - check clock or reduce jtag speed Error: Read AHBAP_CSW 0x2342 target state: halted target halted due to undefined, current mode: Handler SysTick xPSR: 0x010f pc: 0x08001ce0 This time there's no endless loop, the debug output stops here and I can connect via telnet, but can't do much there... init flash probe 0 device id = 0x10006412 STM32 flash size failed, probe inaccurate - assuming 32k flash flash size = 32kbytes flash 'stm32x' found at 0x0800 flash info 0 #0: stm32x at 0x0800, size 0x8000, buswidth 0, chipwidth 0 # 0: 0x (0x400 1kB) protected # 1: 0x0400 (0x400 1kB) protected # 2: 0x0800 (0x400 1kB) protected # 3: 0x0c00 (0x400 1kB) protected # 4: 0x1000 (0x400 1kB) protected # 5: 0x1400 (0x400 1kB) protected # 6: 0x1800 (0x400 1kB) protected # 7: 0x1c00 (0x400 1kB) protected # 8: 0x2000 (0x400 1kB) protected # 9: 0x2400 (0x400 1kB) protected # 10: 0x2800 (0x400 1kB) protected # 11: 0x2c00 (0x400 1kB) protected # 12: 0x3000 (0x400 1kB) protected # 13: 0x3400 (0x400 1kB) protected # 14: 0x3800 (0x400 1kB) protected # 15: 0x3c00 (0x400 1kB) protected # 16: 0x4000 (0x400 1kB) protected # 17: 0x4400 (0x400 1kB) protected # 18: 0x4800 (0x400 1kB) protected # 19: 0x4c00 (0x400 1kB) protected # 20: 0x5000 (0x400 1kB) protected # 21: 0x5400 (0x400 1kB) protected # 22: 0x5800 (0x400 1kB) protected # 23: 0x5c00 (0x400 1kB) protected # 24: 0x6000 (0x400 1kB) protected # 25: 0x6400 (0x400 1kB) protected # 26: 0x6800 (0x400 1kB) protected # 27: 0x6c00 (0x400 1kB) protected # 28: 0x7000 (0x400 1kB) protected # 29: 0x7400 (0x400 1kB) protected # 30: 0x7800 (0x400 1kB) protected # 31: 0x7c00 (0x400 1kB) protected stm32x (Low Density) - Rev: A dump_image foo.dump 0 0x8000 usb_bulk_read failed (requested=937, result=256) jlink_tap_execute, wrong result -1, expected 937 usb_bulk_write failed (requested=3250, result=-110) jlink_tap_execute, wrong result -1, expected 1623 usb_bulk_write failed (requested=3264, result=-110) jlink_tap_execute, wrong result -1, expected 1630 usb_bulk_write failed (requested=3278, result=-110)
Re: [Openocd-development] PXA270
Hi, On Mon, Mar 02, 2009 at 04:40:12PM +0300, Sergey Lapin wrote: But, I have PXA270 board (Colibri PXA270 + Orchid board) on my desk Can you please make a patch to add this as a board cfg file? Thanks, Uwe. -- http://www.hermann-uwe.de | http://www.holsham-traders.de http://www.crazy-hacks.org | http://www.unmaintained-free-software.org ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] [PATCH] Drop non-A variants of ft2232 targets
On Fri, Apr 03, 2009 at 07:52:05PM +0200, Uwe Hermann wrote: Unless I'm mistaken, recent OpenOCD versions will automatically work with both A and non-A variants of the ft2232_device_desc variables. For example, ft2232_device_desc Amontec JTAGkey and ft2232_device_desc Amontec JTAGkey A should both work fine, on Windows as well as on Mac OS X and Linux, correct? If that is the case, let's drop all non-A variants, see patch. Also: Let JTAGkey-tiny include JTAGkey, as they're the same. *ping* Can somebody please review this patch? I think we can safely drop the non-A variants now, but it would be good if someone could confirm that. Thanks, Uwe. -- http://www.hermann-uwe.de | http://www.holsham-traders.de http://www.crazy-hacks.org | http://www.unmaintained-free-software.org ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] [PATCH] Drop unnecessary STM32 BSTAPIDs
On Thu, Apr 23, 2009 at 07:36:59PM +0200, Øyvind Harboe wrote: Hmm... why not delete the files? Possibly add a comment to the stm32 config file for each of the supported targets... I wouldn't do that. It's a good thing to have one explicit board/* file for every eval board so that users can easily use predefined configs. A file such as boards/olimex_stm32_h103.cfg is very obvious for users, they don't have to care about the details of target CPUs, RAM etc. They don't have to ask is my eval board supported by OpenOCD? as such a file answers that question easily. Yes, some of the files are one-liners but that's OK, they're still very helpful for users IMHO. Uwe. -- http://www.hermann-uwe.de | http://www.holsham-traders.de http://www.crazy-hacks.org | http://www.unmaintained-free-software.org ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] C99 compatibility (Was: MSVC compatibility (Was: [PATCH] CMake))
On Thu, Apr 30, 2009 at 08:22:32PM +0200, Nico Coesel wrote: My vote would be for OpenOCD to stay a C program. Same here. Just my 2 cents, Uwe. -- http://www.hermann-uwe.de | http://www.holsham-traders.de http://www.crazy-hacks.org | http://www.unmaintained-free-software.org ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] [PATCH] Add Hitex STR9-comStick config file
On Fri, May 01, 2009 at 12:56:43AM +0200, Uwe Hermann wrote:
Add Hitex STR9-comStick config file. Support both the -A1 and -A2
revisions using the same config file.
Forgot the patch.
Uwe.
--
http://www.hermann-uwe.de | http://www.holsham-traders.de
http://www.crazy-hacks.org | http://www.unmaintained-free-software.org
Index: src/target/target/str9comstick.cfg
===
--- src/target/target/str9comstick.cfg (Revision 1583)
+++ src/target/target/str9comstick.cfg (Arbeitskopie)
@@ -39,9 +39,12 @@
if { [info exists BSTAPID ] } {
set _BSTAPID $BSTAPID
} else {
- set _BSTAPID 0x1457f041
+ # Found on STR9-comStick, revision STR912CS-A1
+ set _BSTAPID1 0x1457f041
+ # Found on STR9-comStick, revision STR912CS-A2
+ set _BSTAPID2 0x2457f041
}
-jtag newtap $_CHIPNAME bs-irlen 5 -ircapture 0x1 -irmask 0x1 -expected-id $_BSTAPID
+jtag newtap $_CHIPNAME bs -irlen 5 -ircapture 0x1 -irmask 0x1 -expected-id $_BSTAPID1 -expected-id $_BSTAPID2
set _TARGETNAME [format %s.cpu $_CHIPNAME]
target create $_TARGETNAME arm966e -endian $_ENDIAN -chain-position $_TARGETNAME -variant arm966e
Index: src/target/board/hitex_str9_comstick.cfg
===
--- src/target/board/hitex_str9_comstick.cfg (Revision 0)
+++ src/target/board/hitex_str9_comstick.cfg (Revision 0)
@@ -0,0 +1,11 @@
+#
+# Hitex STR9-comStick
+#
+# http://www.hitex.com/index.php?id=383
+#
+
+# This works for the STR9-comStick revisions STR912CS-A1 and STR912CS-A2.
+
+source [find interface/str9-comstick.cfg]
+source [find target/str9comstick.cfg]
+
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
[Openocd-development] Debian package: build errors on various architectures
Hi, I uploaded a new Debian package of OpenOCD recently (based on r1583) which produced a number of build warnings (now errors because of -Werror). Haven't had the time to look into the issues, but the build logs could be useful for others: https://buildd.debian.org/pkg.cgi?pkg=openocd Please follow every link in the State column there for a build log, except i386 and powerpc (which build fine). All other architectures fail to build as of r1583. s390 and arm are intentionally not built (at the moment at least). HTH, Uwe. -- http://www.hermann-uwe.de | http://www.holsham-traders.de http://www.crazy-hacks.org | http://www.unmaintained-free-software.org ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Debian package: build errors on various architectures
Hi, On Mon, May 04, 2009 at 11:56:00AM -0700, Zach Welch wrote: The attached patch should fix the cast alignment warnings caused by jim.c on platforms with stricter alignment rules. If you get more problems, please run the builds with --disable-werror so I can try to fix all of them in one pass. Done. I've updated to r1606 and manually added your patch to the build. It may take a bit longer until all architectures have been built, but some are already done. https://buildd.debian.org/pkg.cgi?pkg=openocd https://buildd.debian.org/~luk/status/package.php?p=openocd http://buildd.debian-ports.org/status/package.php?p=openocd Building with gcc-4.4 also needs some additional fixing btw, see for instance http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=527100 (that's not the only error, on i386 there are at least one or two more, no idea for other arches). You can test that with 'make CC=gcc-4.4'. Uwe. -- http://www.hermann-uwe.de | http://www.holsham-traders.de http://www.crazy-hacks.org | http://www.unmaintained-free-software.org ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] [Openocd-svn] r2514 - trunk
On Tue, Jul 14, 2009 at 11:46:59AM +0200, Øyvind Harboe wrote: Or do you mean to say that --disable-parport-ppdev does not work?? I had to specify --disable-parport-ppdev before my parport interface would work under Ubuntu 9.04. Hm, that would be strange. Did you do 'modprobe ppdev'? Uwe. -- http://www.hermann-uwe.de | http://www.holsham-traders.de http://www.crazy-hacks.org | http://www.unmaintained-free-software.org ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
[Openocd-development] OpenOCD 0.2.0 in Debian unstable
Hi, just a quick notification, I uploaded a 0.2.0 package to Debian unstable (well, sort of, it's actually r2529). So far all architectures seem to build fine, didn't check for warnings though (-Werror is disabled in the build). https://buildd.debian.org/pkg.cgi?pkg=openocd Hope that helps, Uwe. -- http://www.hermann-uwe.de | http://www.holsham-traders.de http://www.crazy-hacks.org | http://www.unmaintained-free-software.org ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] [PATCH] Add support for the DLP-USB1232H JTAG module
On Thu, Sep 10, 2009 at 03:00:27AM +0200, Uwe Hermann wrote: I recently got a DLP Design DLP-USB1232H UART/SPI/JTAG module which is based on an FT2232H chip. I originally intended to use it to flash SPI BIOS chips from various mainboards (for details on that setup see http://www.coreboot.org/Flashrom/FT2232SPI_Programmer). However, this module is equally well usable as JTAG programmer if connected to the JTAG target properly. I have successfully wired the module to an Olimex STM32-H103 eval board and flashed a firmware onto that using OpenOCD using the interface config file attached. The nice thing is that everything worked pretty much out of the box, I didn't have to change a single line of code in the OpenOCD source. I documented the details at: http://randomprojects.org/wiki/DLP-USB1232H_and_OpenOCD_based_JTAG_adapter The attached patch adds the respective config file to OpenOCD. *ping* Can this be committed, or is there a technical problem with the patch? It's successfully tested on hardware here. Uwe. -- http://www.hermann-uwe.de | http://www.holsham-traders.de http://www.crazy-hacks.org | http://www.unmaintained-free-software.org ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
[Openocd-development] [PATCH] pull request: Typos and documentation fixes
Hi,
please pull from the doc-fixes branch from my OpenOCD repo:
Clone URL:
git clone git://gitorious.org/openocd/openocd.git
The branch has a bunch of minor typos and documentation fixes.
The git format-patch output is attached for easier review.
Thanks, Uwe.
--
http://www.hermann-uwe.de | http://www.randomprojects.org
http://www.crazy-hacks.org | http://www.unmaintained-free-software.org
From da5f4c32e087bb6725e6f48395087925d900c6d7 Mon Sep 17 00:00:00 2001
From: Uwe Hermann u...@hermann-uwe.de
Date: Tue, 24 Nov 2009 20:01:15 +0100
Subject: [PATCH 1/3] Fix a bunch of typos.
---
src/server/gdb_server.c | 10 +-
src/server/httpd.c |4 ++--
src/server/server.c |2 +-
3 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/src/server/gdb_server.c b/src/server/gdb_server.c
index bd1d047..3c099fa 100644
--- a/src/server/gdb_server.c
+++ b/src/server/gdb_server.c
@@ -53,7 +53,7 @@ static const char *DIGITS = 0123456789abcdef;
static void gdb_log_callback(void *priv, const char *file, unsigned line,
const char *function, const char *string);
-/* number of gdb connections, mainly to supress gdb related debugging spam
+/* number of gdb connections, mainly to suppress gdb related debugging spam
* in helper/log.c when no gdb connections are actually active */
int gdb_actual_connections;
@@ -568,7 +568,7 @@ int gdb_get_packet_inner(struct connection *connection, char *buffer, int *len)
break;
case '+':
/* gdb sends a dummy ack '+' at every remote connect - see remote_start_remote (remote.c)
- * incase anyone tries to debug why they receive this warning every time */
+ * in case anyone tries to debug why they receive this warning every time */
LOG_WARNING(acknowledgment received, but no packet pending);
break;
case '-':
@@ -859,7 +859,7 @@ static int gdb_reg_pos(struct target *target, int pos, int len)
* register might be non-divisible by 8(a byte), in which
* case an entire byte is shown.
*
- * NB! the format on the wire is the target endianess
+ * NB! the format on the wire is the target endianness
*
* The format of reg-value is little endian
*
@@ -2141,7 +2141,7 @@ int gdb_input_inner(struct connection *connection)
target_name(target));
break;
default:
- /* ignore unkown packets */
+ /* ignore unknown packets */
LOG_DEBUG(ignoring 0x%2.2x packet, packet[0]);
gdb_put_packet(connection, NULL, 0);
break;
@@ -2320,7 +2320,7 @@ COMMAND_HANDLER(handle_gdb_breakpoint_override_command)
LOG_USER(force %s breakpoints, (gdb_breakpoint_override_type == BKPT_HARD)?hard:soft);
} else
{
- LOG_USER(breakpoint type is not overriden);
+ LOG_USER(breakpoint type is not overridden);
}
return ERROR_OK;
diff --git a/src/server/httpd.c b/src/server/httpd.c
index 8c1d3db..9fa5879 100644
--- a/src/server/httpd.c
+++ b/src/server/httpd.c
@@ -207,7 +207,7 @@ static void request_completed(void *cls, struct MHD_Connection *connection,
*con_cls = NULL;
}
-/* append to said key in dictonary */
+/* append to said key in dictionary */
static void append_key(struct httpd_request *r, const char *key,
const char *data, size_t off, size_t size)
{
@@ -388,7 +388,7 @@ static int ahc_echo_inner(void * cls, struct MHD_Connection * connection,
r-post = post;
Jim_SetVariableStr(interp, httppostdata, Jim_NewDictObj(interp, NULL, 0));
- /* fill in url query strings in dictonary */
+ /* fill in url query strings in dictionary */
MHD_get_connection_values(connection, MHD_GET_ARGUMENT_KIND,
record_arg, r);
diff --git a/src/server/server.c b/src/server/server.c
index 50bc00e..3ba433e 100644
--- a/src/server/server.c
+++ b/src/server/server.c
@@ -309,7 +309,7 @@ int server_loop(struct command_context *command_context)
while (!shutdown_openocd)
{
- /* monitor sockets for acitvity */
+ /* monitor sockets for activity */
fd_max = 0;
FD_ZERO(read_fds);
--
1.6.5.3
From 4ca4c68798cffe767e0eba3a38a9c4537b382ab6 Mon Sep 17 00:00:00 2001
From: Uwe Hermann u...@hermann-uwe.de
Date: Tue, 24 Nov 2009 20:28:21 +0100
Subject: [PATCH 2/3] Fix some typos in the top-level documentation files.
---
BUGS |2 +-
ChangeLog |2 +-
PATCHES |2 +-
README|4 ++--
TODO | 12 ++--
5 files changed, 11 insertions(+), 11 deletions(-)
diff --git a/BUGS b/BUGS
index 0cb99ae..6967525 100644
--- a/BUGS
+++ b/BUGS
@@ -1,4 +1,4 @@
-// This file is part of the Doyxgen Developer Manual
+// This file is part of the Doxygen Developer Manual
/** @page bugs Bug Reporting
Please report bugs by subscribing to the OpenOCD mailing list and
diff --git a/ChangeLog b/ChangeLog
index d80c896..a8df5d0 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1 +1 @@
-Retired in favour of SVN log.
+Retired in favor of git log.
diff --git a/PATCHES b/PATCHES
index 32f1bda..74a76fd 100644
--- a/PATCHES
+++ b/PATCHES
@@ -1,4 +1,4 @@
-// This file is part
Re: [Openocd-development] [PATCH] pull request: Typos and documentation fixes
On Thu, Nov 26, 2009 at 11:46:03AM -0800, David Brownell wrote: On Thursday 26 November 2009, Zach Welch wrote: For the future, commit messages should have a short subject line and at least one line of description. Agreed with the usual exception: there are minor patches where the subject line suffices, and there's no point in trying to create a second sentence of description. Yep, agreed. One-line short log and multi-line detailed explanations are good to have, except for simple Fix typo cases like this, where just the short one-liner should suffice. It's still displayed nicely in gitk etc. What about attaching the diffs to the pull request emails? Do you want to have those attached, or is please pull from xyz enough? Thanks, Uwe. -- http://www.hermann-uwe.de | http://www.randomprojects.org http://www.crazy-hacks.org | http://www.unmaintained-free-software.org ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
[Openocd-development] [PATCH] Add support for the DLP-USB1232H JTAG module (repost)
Hi,
I posted a patch for a new device which can be used as JTAG programmer
by OpenOCD a few months ago, seems it got lost or forgotten so here'
a repost. I rebased against current git. Old message:
I recently got a DLP Design DLP-USB1232H UART/SPI/JTAG module which is
based on an FT2232H chip. I originally intended to use it to flash SPI
BIOS chips from various mainboards (for details on that setup see
http://www.flashrom.org/FT2232SPI_Programmer).
However, this module is equally well usable as JTAG programmer if
connected to the JTAG target properly. I have successfully wired the
module to an Olimex STM32-H103 eval board and flashed a firmware onto
that using OpenOCD using the interface config file attached.
The nice thing is that everything worked pretty much out of the box, I
didn't have to change a single line of code in the OpenOCD source.
I documented the details at:
http://randomprojects.org/wiki/DLP-USB1232H_and_OpenOCD_based_JTAG_adapter
The attached patch adds the respective config file to OpenOCD.
Uwe.
--
http://www.hermann-uwe.de | http://www.randomprojects.org
http://www.crazy-hacks.org | http://www.unmaintained-free-software.org
From 5e4981d2e3900836ab1e87ad076312275a601e29 Mon Sep 17 00:00:00 2001
From: Uwe Hermann u...@hermann-uwe.de
Date: Fri, 27 Nov 2009 09:55:54 +0100
Subject: [PATCH] Add an interface file for DLP Design DLP-USB1232H.
The DLP Design DLP-USB1232H UART/SPI/JTAG module is based on an FT2232H
chip. Among other things, it can used as JTAG programmer if connected to
the JTAG target properly. I have successfully wired the module to an
Olimex STM32-H103 eval board and flashed a firmware onto that using OpenOCD.
The setup details and schematics are documented at:
http://randomprojects.org/wiki/DLP-USB1232H_and_OpenOCD_based_JTAG_adapter
---
contrib/openocd.udev |1 +
doc/openocd.texi |2 ++
tcl/interface/dlp-usb1232h.cfg | 14 ++
3 files changed, 17 insertions(+), 0 deletions(-)
create mode 100644 tcl/interface/dlp-usb1232h.cfg
diff --git a/contrib/openocd.udev b/contrib/openocd.udev
index bcec6af..393e578 100644
--- a/contrib/openocd.udev
+++ b/contrib/openocd.udev
@@ -28,6 +28,7 @@ ATTRS{idVendor}==0fbb, ATTRS{idProduct}==1000, MODE=664, GROUP=plugdev
# TinCanTools Flyswatter
# OOCD-Link
# Marvell Sheevaplug (early development versions)
+# DLP Design DLP-USB1232H USB-to-UART/FIFO interface module
ATTRS{idVendor}==0403, ATTRS{idProduct}==6010, MODE=664, GROUP=plugdev
# Calao Systems USB-A9260-C02
diff --git a/doc/openocd.texi b/doc/openocd.texi
index bb8f3ab..7b9d3ff 100644
--- a/doc/openocd.texi
+++ b/doc/openocd.texi
@@ -372,6 +372,8 @@ Stellaris eval boards, they can be used to debug other target boards.
@* Axiom AXM-0432 Link @url{http://www.axman.com}
@item @b{cortino}
@* Link @url{http://www.hitex.com/index.php?id=cortino}
+...@item @b{dlp-usb1232h}
+...@* Link @url{http://www.dlpdesign.com/usb/usb1232h.shtml}
@end itemize
@section USB-JTAG / Altera USB-Blaster compatibles
diff --git a/tcl/interface/dlp-usb1232h.cfg b/tcl/interface/dlp-usb1232h.cfg
new file mode 100644
index 000..7432413
--- /dev/null
+++ b/tcl/interface/dlp-usb1232h.cfg
@@ -0,0 +1,14 @@
+#
+# DLP Design DLP-USB1232H USB-to-UART/FIFO interface module
+#
+# http://www.dlpdesign.com/usb/usb1232h.shtml
+#
+# Schematics for OpenOCD usage:
+# http://randomprojects.org/wiki/DLP-USB1232H_and_OpenOCD_based_JTAG_adapter
+#
+
+interface ft2232
+ft2232_device_desc Dual RS232-HS
+ft2232_layout usbjtag
+ft2232_vid_pid 0x0403 0x6010
+
--
1.7.0.3
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
[Openocd-development] [PATCH] Fix a bunch of typos.
Fix a bunch of typos.
Most are in code comments, so nothing should break. UNKOWN_COMMAND and
CMD_UNKOWN are not used elsewhere, so correcting the spelling should
also not break anything.
---
src/flash/nand/mx2.c |2 +-
src/flash/nand/mx3.c |2 +-
src/flash/nor/at91sam3.c |2 +-
src/flash/nor/stellaris.c|2 +-
src/jtag/drivers/buspirate.c |2 +-
src/jtag/drivers/usbprog.c |2 +-
src/server/startup.tcl |2 +-
src/svf/svf.c|2 +-
src/target/armv7m.c |2 +-
src/target/image.c |2 +-
src/target/mips32.c |2 +-
src/target/target.c |2 +-
src/target/target.h |4 ++--
13 files changed, 14 insertions(+), 14 deletions(-)
diff --git a/src/flash/nand/mx2.c b/src/flash/nand/mx2.c
index 6bad4aa..77ae138 100644
--- a/src/flash/nand/mx2.c
+++ b/src/flash/nand/mx2.c
@@ -105,7 +105,7 @@ NAND_DEVICE_COMMAND_HANDLER(imx27_nand_device_command)
mx2_nf_info-flags.target_little_endian =
(nand-target-endianness == TARGET_LITTLE_ENDIAN);
/*
-* testing host endianess
+* testing host endianness
*/
x = 1;
if (*(char *) x == 1)
diff --git a/src/flash/nand/mx3.c b/src/flash/nand/mx3.c
index 41f08b5..45591e3 100644
--- a/src/flash/nand/mx3.c
+++ b/src/flash/nand/mx3.c
@@ -100,7 +100,7 @@ NAND_DEVICE_COMMAND_HANDLER(imx31_nand_device_command)
mx3_nf_info-flags.target_little_endian =
(nand-target-endianness == TARGET_LITTLE_ENDIAN);
/*
- * testing host endianess
+ * testing host endianness
*/
{
int x = 1;
diff --git a/src/flash/nor/at91sam3.c b/src/flash/nor/at91sam3.c
index f895935..0b71e81 100644
--- a/src/flash/nor/at91sam3.c
+++ b/src/flash/nor/at91sam3.c
@@ -2684,7 +2684,7 @@ showall:
(0 == strcmp(clear, CMD_ARGV[0]))) { // quietly
accept both
r = FLASHD_ClrGPNVM((pChip-details.bank[0]), who);
} else {
- command_print(CMD_CTX, Unkown command: %s, CMD_ARGV[0]);
+ command_print(CMD_CTX, Unknown command: %s, CMD_ARGV[0]);
r = ERROR_COMMAND_SYNTAX_ERROR;
}
return r;
diff --git a/src/flash/nor/stellaris.c b/src/flash/nor/stellaris.c
index 6a81047..e57943c 100644
--- a/src/flash/nor/stellaris.c
+++ b/src/flash/nor/stellaris.c
@@ -841,7 +841,7 @@ static int stellaris_protect(struct flash_bank *bank, int
set, int first, int la
* REVISIT DustDevil-A0 parts have an erratum making FMPPE commits
* inadvisable ... it makes future mass erase operations fail.
*/
- LOG_WARNING(Flash protection cannot be removed once commited, commit
is NOT executed !);
+ LOG_WARNING(Flash protection cannot be removed once committed, commit
is NOT executed !);
/* target_write_u32(target, FLASH_FMC, FMC_WRKEY | FMC_COMT); */
/* Wait until erase complete */
diff --git a/src/jtag/drivers/buspirate.c b/src/jtag/drivers/buspirate.c
index 836a4d1..7813f33 100644
--- a/src/jtag/drivers/buspirate.c
+++ b/src/jtag/drivers/buspirate.c
@@ -45,7 +45,7 @@ static void buspirate_scan(bool ir_scan, enum scan_type type,
uint8_t *buffer, int scan_size, struct scan_command *command);
-#define CMD_UNKOWN0x00
+#define CMD_UNKNOWN 0x00
#define CMD_PORT_MODE 0x01
#define CMD_FEATURE 0x02
#define CMD_READ_ADCS 0x03
diff --git a/src/jtag/drivers/usbprog.c b/src/jtag/drivers/usbprog.c
index cc78555..17b0116 100644
--- a/src/jtag/drivers/usbprog.c
+++ b/src/jtag/drivers/usbprog.c
@@ -54,7 +54,7 @@ static void usbprog_path_move(struct pathmove_command *cmd);
static void usbprog_runtest(int num_cycles);
static void usbprog_scan(bool ir_scan, enum scan_type type, uint8_t *buffer,
int scan_size);
-#define UNKOWN_COMMAND 0x00
+#define UNKNOWN_COMMAND0x00
#define PORT_DIRECTION 0x01
#define PORT_SET 0x02
#define PORT_GET 0x03
diff --git a/src/server/startup.tcl b/src/server/startup.tcl
index 7801d1b..64ace40 100644
--- a/src/server/startup.tcl
+++ b/src/server/startup.tcl
@@ -1,6 +1,6 @@
# Defines basic Tcl procs for OpenOCD server modules
-# Handle GDB 'R' packet. Can be overriden by configuration script,
+# Handle GDB 'R' packet. Can be overridden by configuration script,
# but it's not something one would expect target scripts to do
# normally
proc ocd_gdb_restart {target_id} {
diff --git a/src/svf/svf.c b/src/svf/svf.c
index 6acf032..0cca768 100644
--- a/src/svf/svf.c
+++ b/src/svf/svf.c
@@ -402,7 +402,7 @@ COMMAND_HANDLER(handle_svf_command)
svf_buffer_index = 0;
// double the buffer size
- // in case current command cannot be commited, and next command is a
bit scan command
+ // in case current command cannot be committed, and next command is a
bit scan command
// here is 32K bits for this big scan command, it should be
Re: [Openocd-development] Change in openocd[master]: docs: update project url's
On Wed, Oct 12, 2011 at 01:04:26PM +0300, Spencer Oliver (Code Review) wrote: Spencer Oliver has submitted this change and it was merged. Change subject: docs: update project url's .. docs: update project url's Change-Id: I54fc3aff722ed25143aad85e58d19b72fcecbba0 Signed-off-by: Spencer Oliver ntfr...@users.sourceforge.net --- M NEWTAPS M PATCHES.txt M README M doc/manual/primer/patches.txt M doc/manual/server.txt M doc/openocd.texi 6 files changed, 10 insertions(+), 5 deletions(-) Approvals: Spencer Oliver: Verified; Looks good to me, approved Please configure gerrit so that the full patch is posted on the mailing list additionally, as it used to be. I personally read lots of patches and discussions offline (e.g. in a train) in my mail client, and I'm pretty sure I'm not the only one who'd prefer if patches would still end up on the list (and in the list archive) in addition to gerrit. Thanks! Uwe. -- http://hermann-uwe.de | http://sigrok.org http://randomprojects.org | http://unmaintained-free-software.org ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Docs not building
On Thu, Oct 13, 2011 at 04:29:09PM +0200, Akos Vandra wrote: Hi! I tried building the docs from the HEAD (did a git pull, I guess that's the counterpart for svn update), but it gives an error. I might be missing some package, but I don't know what is needed. I have installed texinfo manually, other than that I think I have only the stuff needed to build the code, and what ubuntu comes with. I hope somebody can help me out. Error output is: Making pdf in doc make[1]: Entering directory `/home/akos/Downloads/openocd-git/openocd/doc' TEXINPUTS=.:$TEXINPUTS \ MAKEINFO='/bin/bash /home/akos/Downloads/openocd-git/openocd/missing --run makeinfo -I .' \ texi2dvi --pdf --batch openocd.texi egrep: Invalid range end make[1]: *** [openocd.pdf] Error 1 make[1]: Leaving directory `/home/akos/Downloads/openocd-git/openocd/doc' make: *** [pdf-recursive] Error 1 Could be a texinfo bug, see https://bugs.gentoo.org/show_bug.cgi?id=311885 Uwe. -- http://hermann-uwe.de | http://sigrok.org http://randomprojects.org | http://unmaintained-free-software.org ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
[Openocd-development] gitweb down?
Hi, seems like the gitweb for OpenOCD is down? E.g. the links such as http://openocd.zylin.com/gitweb/?p=openocd.git;a=commit;h=a756b1bcdffef34a6d60d7a2706da9574663f544 no longer work (they did yesterday). There are links from Gerrits pages to the gitweb install, for example (and that's a good thing; please don't drop gitweb, I for one find it very useful; the commitdiff view there is the best one for me to review patches as a whole). If possible, please also change Gerrit to point to a=commitdiff instead of a=commit as above, that's much more useful, IMHO. Thanks. -- http://hermann-uwe.de | http://sigrok.org http://randomprojects.org | http://unmaintained-free-software.org ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
[Openocd-development] Change in openocd[master]: Add an interface file for DLP Design DLP-USB1232H.
Uwe Hermann has uploaded a new change for review. Change subject: Add an interface file for DLP Design DLP-USB1232H. .. Add an interface file for DLP Design DLP-USB1232H. The DLP Design DLP-USB1232H UART/SPI/JTAG module is based on an FTDI FT2232H chip. Among other things, it can used as JTAG programmer if connected to the JTAG target properly. I have successfully wired the module to an Olimex STM32-H103 eval board and flashed a firmware onto that using OpenOCD. The setup details and schematics are documented at: http://randomprojects.org/wiki/DLP-USB1232H_and_OpenOCD_based_JTAG_adapter Change-Id: I5eb9255a61eeece233009bee77d7dc3b5d1afb8b Signed-off-by: Uwe Hermann u...@hermann-uwe.de --- M contrib/openocd.udev M doc/openocd.texi A tcl/interface/dlp-usb1232h.cfg 3 files changed, 17 insertions(+), 0 deletions(-) git pull ssh://openocd.zylin.com:29418/openocd refs/changes/20/20/1 -- To view, visit http://openocd.zylin.com/20 To unsubscribe, visit http://openocd.zylin.com/settings Gerrit-MessageType: newchange Gerrit-Change-Id: I5eb9255a61eeece233009bee77d7dc3b5d1afb8b Gerrit-PatchSet: 1 Gerrit-Project: openocd Gerrit-Branch: master Gerrit-Owner: Uwe Hermann u...@hermann-uwe.de ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
[Openocd-development] Change in openocd[master]: Add a board file for the Glyn Tonga2.
Uwe Hermann has uploaded a new change for review. Change subject: Add a board file for the Glyn Tonga2. .. Add a board file for the Glyn Tonga2. This is a Toshiba TMPA900CMXBG (ARM9) based SO-DIMM CPU module with 64MB DDR SDRAM, 256MB NAND flash, and on-board Ethernet. The board file provides a tonga2_init function which sets up the PLL/clocks and memory (SDRAM and SRAM), which allows writing a boot-loader into RAM via JTAG. Change-Id: I60522b97997bdf50e1f25aebab910d93a98522fb Signed-off-by: Uwe Hermann u...@hermann-uwe.de --- A tcl/board/glyn_tonga2.cfg 1 file changed, 170 insertions(+), 0 deletions(-) git pull ssh://openocd.zylin.com:29418/openocd refs/changes/19/19/1 -- To view, visit http://openocd.zylin.com/19 To unsubscribe, visit http://openocd.zylin.com/settings Gerrit-MessageType: newchange Gerrit-Change-Id: I60522b97997bdf50e1f25aebab910d93a98522fb Gerrit-PatchSet: 1 Gerrit-Project: openocd Gerrit-Branch: master Gerrit-Owner: Uwe Hermann u...@hermann-uwe.de ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
