srst_pulls_trst is only true on some (broken) LPC2148 boards, a fact
which is already documented in doc/openocd.texi, so it shouldn't be
set unconditionally in the target tcl.
This patch was needed to reflash when an Abort exception occured very
early after reset, before OpenOCD tried to halt the
This is a standard FT2232 device. More info at their web page:
http://shop.ngxtechnologies.com/product_info.php?cPath=26&products_id=30
---
tcl/interface/ngxtech.cfg |6 ++
1 files changed, 6 insertions(+), 0 deletions(-)
create mode 100644 tcl/interface/ngxtech.cfg
diff --git a/tcl/inte
Xiaofan Chen wrote:
> > I've been using an FT2232 JTAG interface with the LPC-H2148 for a
> > while, and can confirm that it works fine.
>
> The problem seems to be with FT2232H based device. Are you
> using an FT2232H based JTAG debugger?
I'm afraid I can't say since I can't find the board. I sp
On Sun, Aug 1, 2010 at 9:01 AM, Peter Stuge wrote:
>
>> I have a brand new Olimex ARM-USM-TINY-H JTAG interface and a
>> Olimex LPC-H2148 prototype board.
>
> I've been using an FT2232 JTAG interface with the LPC-H2148 for a
> while, and can confirm that it works fine.
The problem seems to be wit
Hej Olof,
olof.tang...@telia.com wrote:
> Hi there.
> I need some help to find the root cause of my problems with
> OpenOCD/JTAG interface/processor.
>
> I have a brand new Olimex ARM-USM-TINY-H JTAG interface and a
> Olimex LPC-H2148 prototype board.
I've been using an FT2232 JTAG interface wi
On Sun, Aug 1, 2010 at 2:54 AM, Olof Tångrot wrote:
> Running zadig and installing WinUSB seems to replace the drivers.
That is true.
How did you install the driver? You may need to install WinUSB
to the JTAG interface (interface 0 or both interface 0/1).
> Replacing libfdti.dll with the one fr
Running zadig and installing WinUSB seems to replace the drivers.
Replacing libfdti.dll with the one from libftdi1_05July2010.zip makes
openocd crash.
On Sat, 2010-07-31 at 19:15 +0200, Olof Tångrot wrote:
> I have tested the libftdi-018 DLL with the same result as before.
>
> I will see if sol
I have tested the libftdi-018 DLL with the same result as before.
I will see if solution 2 makes any difference...
On Sat, 2010-07-31 at 17:59 +0800, Xiaofan Chen wrote:
> On Sat, Jul 31, 2010 at 5:11 PM, wrote:
>
> > When I plug in the JTAG interface it is recoginized as 2 instances of
> > Li
Hi Freddie.
I just tested [1000 100, 10 ,1] kHz (under Fedora 12 running a 64-bit
Athlon X2 processor) and the result is the same...
"The Error: couldn't read enough bytes from FT2232 device (0 < 81)."
I don't indend to confuse anyone by the use of linux but under Fedora
the current configuration
I'm trying to chase down problems with the LPC1768.
I've run into an old problem with an error message:
Invalid ACK 0x7 in JTAG-DP transaction
There is a vestige of an old kludge that I've tinkered with in
the attached patch.
However, I have evidence that the timing of how quickly
openocd runs
Try adding -c "jtag_khz 1000" to your OpenOCD command line. Maybe it
will work with fixed speed.
4\/3!!
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
On Sat, Jul 31, 2010 at 5:11 PM, wrote:
> When I plug in the JTAG interface it is recoginized as 2 instances of
> LibUSB-Win32 Devices in the device mangager. The drivers are working
> properly according to the dialog boxes. The
> LED on the USB interface is not lit however. The LPC-H2148 is pow
Hi there.
I need some help to find the root cause of my problems with
OpenOCD/JTAG interface/processor.
I have a brand new Olimex ARM-USM-TINY-H JTAG interface and a
Olimex LPC-H2148 prototype board. The board has been
programmed using the
built in boot loader and works but I can't get OpenOCD
13 matches
Mail list logo
