Hello all!
I have compiled and set up openocd 0.4.0 for an at91rm9200.
The things that work are:
- connecting to the target
- setting hardware breakpoints
- running the executable
- single stepping in arm mode
- resetting the target
- disassembling the code in flash
Therefore, I think most thin
On 17/06/2010 09:16, Marc Pignat wrote:
---
src/jtag/drivers/ft2232.c | 19 ++-
1 files changed, 10 insertions(+), 9 deletions(-)
diff --git a/src/jtag/drivers/ft2232.c b/src/jtag/drivers/ft2232.c
index bc8463e..9d40b1c 100644
--- a/src/jtag/drivers/ft2232.c
+++ b/src/jtag/
I'm going to leave it to you to follow up and make the decision on whether
to revert here.
I was just committing stuff based upon a consensus in the list that this
was the right direction to go, I don't know this code very well...
--
Øyvind Harboe
US toll free 1-866-980-3434 / International +4
On Friday 02 July 2010 12:15:06 Øyvind Harboe wrote:
> I'm going to leave it to you to follow up and make the decision on whether
> to revert here.
Hi all!
It seems that 2/2 has introduced problems.
It seemed trivial to me, but finally it isn't!
I think we should revert it.
Best regards
Marc
_
- Original Message
Nick wrote:
> the standard configure, make, make install.
What flags did you pass to configure? What support for programmers
was included? Please send config.log, or ./configure output, for
validation.
Make sure you run with --enable-arm-jtag-ew
Optionally also --ena
On Fri, Jul 2, 2010 at 9:14 PM, Nick wrote:
> checking for usb.h usablility ... no
> checking for usb.h presence ... no
> check for usb.h ... no
> configure: error: usb.h is required to build some OpenOCD driver(s)
>
> I have the kernel sources install and the headers as well.
>
> I could not fin
On Fri, Jul 2, 2010 at 9:14 PM, Nick wrote:
> checking for usb.h usablility ... no
> checking for usb.h presence ... no
> check for usb.h ... no
> configure: error: usb.h is required to build some OpenOCD driver(s)
>
> I have the kernel sources install and the headers as well.
>
> I could not fi
I committed the "transport" framework patch; you've
seen it on the list before, the main difference ince
the last post was adding user's guide docs.
(This has been ready for some time, and I got tired of just carrying it
privately. It's groundwork, and shouldn't affect anyone's work; but if it
