>> ocd_mem2array/ocd_array2mem don't want work on my system, they throw
>> an error:
>> Error: mem2array: no command context
ØH> Fixed in the master branch.
I've installed master branch and mem2array works fine, thanks!
Now I'm trying to write a TCL-function which would write flash from
imag
Merged.
Thanks!
--
Ø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 mailing list
Openocd-development@li
On Sat, Aug 14, 2010 at 8:30 AM, Xiaofan Chen wrote:
> OpenOCD has long worked with LPC-2148. Last time I was
> using a J-Link (V6, V7 and V3, it took some time to get V3 working).
>
I also tried it under Linux with the latest git. Here I am using libftdi-0.18.
Somehow the RCLK support is gone.
simon qian wrote:
> But as I remember, reset_config was really defined as
> "trst_and_srst srst_pulls_trst".
Yes, but I think that was not correct for LPC2148.
> Why it becames "trst_and_srst" in the latest git head?
While developing with the LPC-H2148 board I created a firmware which
would cau
On Sat, Aug 14, 2010 at 8:30 AM, Xiaofan Chen wrote:
> On Sat, Aug 14, 2010 at 1:48 AM, Olof Tångrot wrote:
>> Xiaofan Chen wrote:
>>> I am using the original OpenOCD binaries from Freddie Chopin
>>> under 32bit Vista. The driver is the original Amontec driver
>>> (WHQL, based on FTDI's 2.06.00 v
On Sat, Aug 14, 2010 at 1:48 AM, Olof Tångrot wrote:
> Xiaofan Chen wrote:
>> I am using the original OpenOCD binaries from Freddie Chopin
>> under 32bit Vista. The driver is the original Amontec driver
>> (WHQL, based on FTDI's 2.06.00 version) and libusb-win32
>> filter driver 1.2.1.0. The two c
Just noticed another similar typo, this time in the command's error handling.
I've grep'ed for "ft2232_" in the entire tree and it looks like
they're in the right spots so this should be the last change of this
type.
On Fri, Aug 13, 2010 at 5:37 PM, Øyvind Harboe wrote:
> Merged.
>
> Thanks!
>
>
Merged.
Thanks!
--
Ø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 mailing list
Openocd-development@li
Hi,
There's a small typo in the command examples for the Altera USB
Blaster driver. The doc of the usb_blaster_vid_pid command says:
Currently, only one vid, pid pair may be given, e.g. for Altera
USB-Blaster (default):
ft2232_vid_pid 0x09FB 0x6001
The correct example is:
Thanks for your concern.
I have wanted a long time now to verify that my target is Ok. That is
is why I made some new efforts with my wiggler clone. In a post some
days ago I described that this test gave the same disappointing result,
reading nothing but zeros.
I had hoped to borrow a BDI2000 fro
On Wed, Aug 4, 2010 at 10:23 PM, Olof Tångrot https://lists.berlios.de/mailman/listinfo/openocd-development>> wrote:
>/ I get the same semi functional result as on Fedora 12 (same hardware)
/>/ before as shown below. I also observed that not using the '-c "jtag_khz
/>/ 1000"' locks the (FT2232H
On Wed, Aug 4, 2010 at 10:23 PM, Olof Tångrot wrote:
> I get the same semi functional result as on Fedora 12 (same hardware)
> before as shown below. I also observed that not using the '-c "jtag_khz
> 1000"' locks the (FT2232H ?) hardware somehow. After that my JTAG
> interface won't respond the c
Hi!
I'm using LPC-2478STK Development board with KT-LINK programmer. I finally
managed to get OpenOCD 0.4.0 working with KT-LINK. I started debugging and
it works fine. But I have an error and I can't find out if it serious or
not. I run OpenOCD in following way: openocd-ftd2xx -f interface/kt-li
Merged all three patches.
Thanks!
--
Ø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 mailing list
Openo
14 matches
Mail list logo
