Hi All,
I am not sure I am doing this correctly,
But here are the required patches to support the device in subject.
It is patched against 0.4.0 using beyond compare as I do not use git.
Hope someone can make it part of official code as it has been working
for almost a year now on my system.
On Wed, Sep 15, 2010 at 1:42 AM, Xiaofan Chen xiaof...@gmail.com wrote:
On Tue, Sep 14, 2010 at 12:57 AM, Drasko DRASKOVIC
drasko.drasko...@gmail.com wrote:
On Mon, Sep 13, 2010 at 4:38 PM, Laurent Gauch
laurent.ga...@amontec.com wrote:
Download our new Amontec JTAGkey Driver from :
Dne St 15. září 2010 13:28:56 Moshe Artzi napsal(a):
Thanks for your fast reply,
I invoked those commands and on both commands I get the same error message.
Copy paste from the telnet console:
reset halt; load_image iplntim.bin 0x5c04; resume 0x5c04
JTAG tap: pxa3xx.cpu
Great:-)
-Original Message-
From: Øyvind Harboe [mailto:oyvind.har...@zylin.com]
Sent: 15. september 2010 11:40
To: Flemming Futtrup
Cc: openocd-development@lists.berlios.de
Subject: Re: [Openocd-development] Adding support for SST 39VF6401B
externalflash
Pushed.
Thanks!
--
Øyvind
For end users, I will recommend to use the libusb-win32 inf-wizard.
It is very easy to go through the wizard process and install
libusb-win32 device driver for the USB Jtag debuggers like
FT2232x based device, J-Link or R-Link. By default, it will
list USB Composite Device (like FT2232x) as two
Laurent Gauch wrote:
actually I will recommend to still use D2XX drivers and build your
openocd for d2xx driver. Why :
D2XX driver is actually still faster than libusb driver on Windows ...
Do you know why this is? Have you compared also using libusb-1.0,
which uses WinUSB.sys?
D2XX driver
On Wed, Sep 15, 2010 at 8:23 PM, Peter Stuge pe...@stuge.se wrote:
Laurent Gauch wrote:
actually I will recommend to still use D2XX drivers and build your
openocd for d2xx driver. Why :
D2XX driver is actually still faster than libusb driver on Windows ...
Do you know why this is? Have you
On Wed, Sep 15, 2010 at 8:12 PM, Laurent Gauch
laurent.ga...@amontec.com wrote:
Yes true, but actually I will recommend to still use D2XX drivers and build
your openocd for d2xx driver.
D2XX driver is actually still faster than libusb driver on Windows ...
For this reason, right now it is
On Wed, Sep 15, 2010 at 9:27 PM, Xiaofan Chen xiaof...@gmail.com wrote:
On Wed, Sep 15, 2010 at 8:23 PM, Peter Stuge pe...@stuge.se wrote:
Laurent Gauch wrote:
actually I will recommend to still use D2XX drivers and build your
openocd for d2xx driver. Why :
D2XX driver is actually still
On 09/14/2010 01:45 PM, Drasko DRASKOVIC wrote:
On Tue, Sep 14, 2010 at 10:24 PM, Nived nive...@gmail.com wrote:
Hi,
i am using openocd 0.4.0 to debug an intelmote2 device. I am able to set a
break point and then transfer control to that point. When i do a continue
(c) or a next (n) the
Hi Mike,
On Wed, Sep 15, 2010 at 5:23 PM, Mike Dunn miked...@newsguy.com wrote:
This is odd. I am using OpenOCD on a pxa270 target and I don't see this,
neither through telnet nor gdb. Assumed this was a cache-related problem on
arm946.
Might be... But I introduced cache-flushing on memory
HI all berlios members list.
I'm looking for help.
When i execute some commands wrote in .cfg file (openocd.exe), i encounter
the message *command requires more arguments* which i hadn't understand or
explain exactly where's the problem.
Commands as halt , poll , flash erase_check.
Also, the
My board consists of LPC2212 micro and Flash Spansion S29AL016D.
Yours truly
Kamel Mahjoub
-- Forwarded message --
From: Mahjoub Kamel mahjoubkame...@gmail.com
Date: 2010/9/15
Subject: Message script openocd 0.4.0 windows for In Board flash
programming.
To:
On 09/15/2010 08:47 AM, Drasko DRASKOVIC wrote:
If somebody can confirm this, than we can sign-off cache coherency as
a problem and concentrate on a breakpoint handling.
I sent in a patch a while back to fix this very problem on the xscale; i.e.,
software breakpoints didn't work because of
On 09/15/2010 08:35 AM, Nived wrote:
Mike,
Yes, the intelmote2 is Xscale. Could it be a configuration issue then ?
Perhaps.
I am using the default cfg files pxa270.cfg, crossbow_tech_imote2.cfg and
olimex_arm_usb_tiny_h.cfg.
I'm using the same Olimex i/f as you (finally upgraded from
On Wed, Sep 15, 2010 at 7:58 PM, Mike Dunn miked...@newsguy.com wrote:
On 09/15/2010 08:47 AM, Drasko DRASKOVIC wrote:
I sent in a patch a while back to fix this very problem on the xscale; i.e.,
software breakpoints didn't work because of cache issues. The problem was
clear: execution
On Wed, Sep 15, 2010 at 8:28 PM, Drasko DRASKOVIC
drasko.drasko...@gmail.com wrote:
On Wed, Sep 15, 2010 at 7:58 PM, Mike Dunn miked...@newsguy.com wrote:
On 09/15/2010 08:47 AM, Drasko DRASKOVIC wrote:
I sent in a patch a while back to fix this very problem on the xscale; i.e.,
software
Mike,
Yes, it turns out i was using an older version of OpenOCD, i just tried with
the latest version, and its working fine.
Thanks so much for your help.
Drasko,
i am sorry i can't be of more help with your issue, i hope you find a
solution soon.
- Nived
On Wed, Sep 15, 2010 at 11:56 AM,
Gene Smith wrote, On 09/14/2010 02:26 PM:
Will openocd work with a cortex-r4 core (armv7-r)? I think it is similar
to armv7-a but w/o MMU. The only vendor making a generally available
part with this core is TI TMS570 dual core. I would be using it in a
custom ASIC with a jtag interface.
-gene
19 matches
Mail list logo
