[Openocd-development] Quick fix for libftdi

2010-03-22 Thread Francois Lorrain
Hello, it looks like the latest ftdi code checks for ftdi->usb_dev not null before doing anything else. this breaks the libftdi driver for windows (cross-compiled using mingw32 on debian) here is the ftdi code : int ftdi_set_interface(struct ftdi_context *ftdi, enum ftdi_interface interface) {

[Openocd-development] gdb_port ignored in config files ?

2009-06-23 Thread Francois Lorrain
Hello, Now with the latest improvments, I am able to build openocd again under cygwin. But it looks like the gdb_port command insist on using as port, I have it set to 2332 in my config file but openocd is still listening on . If I try to change it from the telnet interface : Open On-Ch

Re: [Openocd-development] Compile issue on mingw on current svn

2009-05-15 Thread Francois Lorrain
On Wed, May 13, 2009 at 9:03 PM, Spencer Oliver wrote: >> >> No, I still have the same problem with r1776. >> >> there are some uint32_t uses in replacement.h which are not recognized >> - I don't have an elf.h system include. >> >> export CPPFLAGS="-IC:/libusb-win32-device-bin-0.1.12.1/include" >

Re: [Openocd-development] Compile issue on mingw on current svn

2009-05-13 Thread Francois Lorrain
On Wed, May 13, 2009 at 1:21 PM, Zach Welch wrote: > On Wed, 2009-05-13 at 03:17 -0700, Zach Welch wrote: >> On Wed, 2009-05-13 at 12:00 +0200, Francois Lorrain wrote: >> [snip] >> > 2)  It looks like the stdint.h need to be included in system.h, not >> > types

[Openocd-development] Compile issue on mingw on current svn

2009-05-13 Thread Francois Lorrain
Hello, Trying to compile the SVN version after the recent changes on windows I am compiling a mingw version using the cygwin tools with mingw32-make, mingw32-gcc - it has worked for me before. I have a couple of issue with one blocking from finishing the compilation. 1) I have a small local patc

Re: [Openocd-development] Crash while singlestepping

2009-04-10 Thread Francois Lorrain
Hello, Just a "me too" email I have seen the issue with trying to debug thumb code on an ARM7 target. The arm_simulate_step tries to guess the "next" address to put a breakpoint at this address but it sometime crashes. I have tried to debug further but I have not been very succesful. Regards Fr

[Openocd-development] Crash in OpenOCD while stepping over some thumb code

2009-02-03 Thread Francois Lorrain
Hello, I am using OpenOCD with an Olimex ARM-USB-OCD to debug an ARM7 platform. The OpenOCD is from Rev 1362 with some personal patches but unrelated to the code below ... OpenOCD is crashing on me at : bt #0 buf_get_u32 (buffer=0x73677261 , first=0, num=32) at ../../src/helper/binarybuffer.h:5

[Openocd-development] mingw32 build error, cannot find ftd2xx

2009-01-12 Thread Francois Lorrain
Hello, This is a different issue which prevents me from building openocd with the mingw32-gcc compiler on cygwin. without this patch, the ftd2xx library is accessed using the cygwin path /cygwin/c/ftdi-2.04.06 but mingw32-gcc does not understand cygwin path. Regards Francois Index: configure.

[Openocd-development] Looks like a typo in configure.in : LDFLAGS is ignored during configure.

2009-01-12 Thread Francois Lorrain
Hello, Looks like a typo in configure.in - the configure process ignore LDFLAGS in the environment. Here is a patch Index: configure.in === --- configure.in(revision 1312) +++ configure.in(working copy) @@ -464,12 +

Re: [Openocd-development] new arm7_9_common.c.patch

2008-10-28 Thread Francois Lorrain
Hello, Just a remark, it breaks the feroceon.c build - I am not using it and the fix is trivial void feroceon_enable_single_step(target_t *target, u32 pc) { adding the u32 pc as an extra parameter fixes the error although the feroceon target might need your update too. Regards Francois On Sat

[Openocd-development] Another problem with the J-LINK with an ARM7TDMI

2008-10-21 Thread Francois Lorrain
Hello, I am trying to get the OpenOCD to work with an ARM7TDMI - custom SoC. OpenOCD works fine with the Olimex ARM-USB-OCD but I'd like to be able to use the J-Link because it support the RTCK clock. I am using the latest SVN version 1022. I can communicate with the J-Link without problem - so

[Openocd-development] Problem with J-link and OpenOCD

2008-08-07 Thread Francois Lorrain
Hello, I am working with a patched OpenOCD on an ARM7 SoC, I have made some modifications to support flash download and flash software breakpoints and it works decently with an Olimex ARM-USB-OCD. I am trying to get the same setup working with a JLink but I have some problems, namely : Debug: