Re: [Openocd-development] openocd-0.40.-rc1 -c shutdown returns EXIT_FAIL

On Monday 04 January 2010, Øyvind Harboe wrote: > For 0.4 the best thing I can come up with right now is to call exit() for the > "exit" command and deleting all the kludges higher up in the callstack. Make that "call exit() for 'shutdown'" and I'd agree. The "exit" command is documented as being

Re: [Openocd-development] openocd-0.40.-rc1 -c shutdown returns EXIT_FAIL

On Mon, Jan 4, 2010 at 10:17 PM, David Brownell wrote: > On Monday 04 January 2010, Øyvind Harboe wrote: >> On Mon, Jan 4, 2010 at 8:59 PM, David Brownell wrote: >> > On Monday 04 January 2010, Øyvind Harboe wrote: >> >> >> >> This is a hack of course, but I'm wondering if it is the best >> >> ha

Re: [Openocd-development] Amontec JtagKey2 ??

+++ Alain Mouette [2010-01-04 20:18 -0200]: > Reading one of the leatest messages, I just remembered this: > > > Is JtagKey2 running nicely with OpenOCD? We use it and it works fine (with openocd 0.3) > Does it have restrictions as to chips that will be th

[Openocd-development] Amontec JtagKey2 ??

Reading one of the leatest messages, I just remembered this: Is JtagKey2 running nicely with OpenOCD? Does it have restrictions as to chips that will be that fast? Is is equivalent to FT2232H ? It is a relatively expensive adapter, that is why I would lik

Re: [Openocd-development] freebsd build help

> Hi, > > After a long hiatus, I'm again trying to build things on freebsd. > > Seems I've got a good pull of the git. > > I then run >   ./bootstrap > then >   ./configure --enable-maintainer-mode --enable-ft2232_libftdi > --disable-doxygen-html > then >   gmake > then I get error: >   gmake[2]: E

Re: [Openocd-development] openocd-0.40.-rc1 -c shutdown returns EXIT_FAIL

On Monday 04 January 2010, Øyvind Harboe wrote: > On Mon, Jan 4, 2010 at 8:59 PM, David Brownell wrote: > > On Monday 04 January 2010, Øyvind Harboe wrote: > >> > >> This is a hack of course, but I'm wondering if it is the best > >> hack for 0.4... > > > > I'd like a solution that gets rid of *all

Re: [Openocd-development] openocd-0.40.-rc1 -c shutdown returns EXIT_FAIL

On Mon, Jan 4, 2010 at 8:59 PM, David Brownell wrote: > On Monday 04 January 2010, Øyvind Harboe wrote: >> >> This is a hack of course, but I'm wondering if it is the best >> hack for 0.4... > > I'd like a solution that gets rid of *all* the errors on > execution of the "shutdown" command. > > Is

[Openocd-development] freebsd build help

Hi, After a long hiatus, I'm again trying to build things on freebsd. Seems I've got a good pull of the git. I then run ./bootstrap then ./configure --enable-maintainer-mode --enable-ft2232_libftdi --disable-doxygen-html then gmake then I get error: gmake[2]: Entering directory `/usr

Re: [Openocd-development] openocd-0.40.-rc1 -c shutdown returns EXIT_FAIL

On Monday 04 January 2010, Øyvind Harboe wrote: > > This is a hack of course, but I'm wondering if it is the best > hack for 0.4... I'd like a solution that gets rid of *all* the errors on execution of the "shutdown" command. Is there a reason why shutdown doesn't just cause exit()? - Dave

Re: [Openocd-development] openocd-0.40.-rc1 -c shutdown returns EXIT_FAIL

On Monday 04 January 2010, Øyvind Harboe wrote: > > Thanks for your reply to my email. I guess my point > > was implied: ERROR_COMMAND_CLOSE_CONNECTION is > > returned when openocd does what I ask and it doesn't > > actually represent an error condition. > > To check for such a specific error mess

Re: [Openocd-development] openocd-0.40.-rc1 -c shutdown returns EXIT_FAIL

On Monday 04 January 2010, Øyvind Harboe wrote: > The primary > return value is here used as a poor substitute for an exception > mechanism. Actually, shutting connections is routine, not exceptional. So using an exception mechanism would be wrong. - Dave ___

Re: [Openocd-development] openocd-0.40.-rc1 -c shutdown returns EXIT_FAIL

A better way to address this, IMHO, would be to fix the design problem at it's root. Retire ERROR_SERVER_REMOTE_CLOSED and ERROR_COMMAND_CLOSE_CONNECTION with some more explicit communication mechanism between the layers. The primary return value is here used as a poor substitute for an exception

[Openocd-development] [PATCH] update udev rules for new udev version

Hi, new versions of udev (148+) emit the following warnings: Dec 8 17:06:23 worf udevd[425]: BUS= will be removed in a future udev version, please use SUBSYSTEM= to match the event device, or SUBSYSTEMS= to match a parent device, in /lib/udev/rules.d/60-openocd.rules:1 Dec 8 17:06:23 worf ude

Re: [Openocd-development] openocd-0.40.-rc1 -c shutdown returns EXIT_FAIL

On Mon, Jan 4, 2010 at 1:02 PM, Robert Jenssen wrote: > Hi, > > Thanks for your reply to my email. I guess my point > was implied: ERROR_COMMAND_CLOSE_CONNECTION is > returned when openocd does what I ask and it doesn't > actually represent an error condition. To check for such a specific error m

Re: [Openocd-development] openocd-0.40.-rc1 -c shutdown returns EXIT_FAIL

This is a hack of course, but I'm wondering if it is the best hack for 0.4... -- Øyvind Harboe US toll free 1-866-980-3434 / International +47 51 63 25 00 http://www.zylin.com/zy1000.html ARM7 ARM9 ARM11 XScale Cortex JTAG debugger and flash programmer

[Openocd-development] openocd-0.40.-rc1 -c shutdown returns EXIT_FAIL

Thanks very much for OpenOCD. Here is a minor issue for openocd-0.4.0-rc1: I flash my development board with a shell script command like "openocd -f openocd.cfg -c do_flash -c shutdown". The shutdown command causes function parse_config_file() to return ERROR_COMMAND_CLOSE_CONNECTION, openocd_ma