On Tue, Sep 14, 2010 at 12:58 AM, Freddie Chopin wrote:
>> However, can you please point me to the drivers (inf files) if they
>> are already present in OpenOCD tree, so that I do not have to use
>> http://sourceforge.net/apps/trac/libusb-win32/wiki tools at all.
>
> ...\OpenOCD\0.4.0\drivers\libu
Freddie Chopin wrote:
> ...\OpenOCD\0.4.0\drivers\libusb-win32_ft2232_driver-100223.zip
> ...\openocd-0.5.0-dev-100827221639\drivers\libusb-win32_ft2232_driver-100831.zip
Maybe http://libusb.org/wiki/libwdi and the Zadig source can be used
to make an even more easy-to-use package.
Oh, and how do
do not try to interpret "retval" into a string, just
amend a bit about the context of the already reported
error.
Signed-off-by: Øyvind Harboe
---
src/target/breakpoints.c | 36 +++-
1 files changed, 7 insertions(+), 29 deletions(-)
diff --git a/src/target/brea
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 everyone,
Version 2 of this patch. Code added to breakpoints.c was removed from previous
patch, and item 3 added, per discussion with Ãyvind regarding error reporting.
Item 4 added, which I just noticed.
I tried to use a software breakpoint in thumb code on the xscale for the first
time rece
On 2010-09-12 15:04, Mahjoub Kamel wrote:
There are a syntax error in "flash bank" command, but i didn t know,
after many essays where is it exactly and how could i correct it?
Could you please help me on this question?
Instead of writing your own config, use existing ones and modify them
(if
On Mon, Sep 13, 2010 at 8:27 PM, Mike Dunn wrote:
> Hi Øyvind,
>
> Thanks for indulging me. Don't mean to drag this out, but let me see if I
> understand...
>
> 1) error are reported when they occur (which would put them down in the target
> or interface code most of the time, I would guess).
>
Hi Øyvind,
Thanks for indulging me. Don't mean to drag this out, but let me see if I
understand...
1) error are reported when they occur (which would put them down in the target
or interface code most of the time, I would guess).
2) return codes are basically considered by the common (target/in
Merged.
--
Ø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@lists.berli
This one looks ready to go to me.
--
Ø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
On Mon, Sep 13, 2010 at 5:40 PM, Mike Dunn wrote:
> Hi Øyvind,
>
> On 09/12/2010 12:23 PM, Øyvind Harboe wrote:
>> A general observation: wouldn't it be better to properly report
>> the error at the failure site rather than try to interpret errors?
> I always assumed that for a project like OpenO
On Mon, Sep 13, 2010 at 7:07 PM, Freddie Chopin wrote:
> On 2010-09-13 19:00, Drasko DRASKOVIC wrote:
>>>
>>> ...\OpenOCD\0.4.0\drivers\libusb-win32_ft2232_driver-100223.zip
>>
>> It does not exist here :
>>
>> http://openocd.git.sourceforge.net/git/gitweb.cgi?p=openocd/openocd;a=tree;hb=8afd2309a
On 2010-09-13 19:00, Drasko DRASKOVIC wrote:
...\OpenOCD\0.4.0\drivers\libusb-win32_ft2232_driver-100223.zip
It does not exist here :
http://openocd.git.sourceforge.net/git/gitweb.cgi?p=openocd/openocd;a=tree;hb=8afd2309a4e18b222da189eb51f46339f17201d5
or
...\openocd-0.5.0-dev-100827221639\dri
On Mon, Sep 13, 2010 at 6:58 PM, Freddie Chopin wrote:
> On 2010-09-13 18:53, Drasko DRASKOVIC wrote:
>>
>> However, can you please point me to the drivers (inf files) if they
>> are already present in OpenOCD tree, so that I do not have to use
>> http://sourceforge.net/apps/trac/libusb-win32/wiki
On 2010-09-13 18:53, Drasko DRASKOVIC wrote:
However, can you please point me to the drivers (inf files) if they
are already present in OpenOCD tree, so that I do not have to use
http://sourceforge.net/apps/trac/libusb-win32/wiki tools at all.
...\OpenOCD\0.4.0\drivers\libusb-win32_ft2232_drive
On Mon, Sep 13, 2010 at 4:38 PM, Laurent Gauch
wrote:
> The Amontec JTAGkey-2 High-Speed USB JTAG Cable is based FTDI FT2232H and
> need newer drivers.
>
> Download our new Amontec JTAGkey Driver from :
> http://www.amontec.com/download/amontec-jtagkey-driver-d2xx-20091124.zip
>
> Go to device ma
On Mon, Sep 13, 2010 at 6:21 PM, Freddie Chopin wrote:
> On 2010-09-13 18:16, Drasko DRASKOVIC wrote:
>>
>> I did not install libusb-win32, though. I thought that it is included
>> in the binary... Does it has to be installed separatly (manually) ? Do
>> we need Filter Driver also , or only Device
On 2010-09-13 18:16, Drasko DRASKOVIC wrote:
I did not install libusb-win32, though. I thought that it is included
in the binary... Does it has to be installed separatly (manually) ? Do
we need Filter Driver also , or only Device Driver from libusb-win32 ?
It's not the .dll you're missing - the
On Mon, Sep 13, 2010 at 6:09 PM, Drasko DRASKOVIC
wrote:
> On Mon, Sep 13, 2010 at 5:48 PM, Freddie Chopin wrote:
>> On 2010-09-13 16:18, Drasko DRASKOVIC wrote:
>>>
>>> I tried several methods to install OpenOCD on Windows - all without
>>> success.
>>
>> You should have tried just one - the pre
On Mon, Sep 13, 2010 at 5:48 PM, Freddie Chopin wrote:
> On 2010-09-13 16:18, Drasko DRASKOVIC wrote:
>>
>> I tried several methods to install OpenOCD on Windows - all without
>> success.
>
> You should have tried just one - the prebuilt binaries from my webpage (;
>
> http://www.freddiechopin.inf
On 2010-09-13 16:18, Drasko DRASKOVIC wrote:
I tried several methods to install OpenOCD on Windows - all without success.
You should have tried just one - the prebuilt binaries from my webpage (;
http://www.freddiechopin.info/
Just remember to install libusb-win32 drivers, NOT the drivers fro
Hi Øyvind,
On 09/12/2010 12:23 PM, Øyvind Harboe wrote:
> A general observation: wouldn't it be better to properly report
> the error at the failure site rather than try to interpret errors?
I always assumed that for a project like OpenOCD, which manages and performs
operations on a set of simili
The Amontec JTAGkey-2 High-Speed USB JTAG Cable is based FTDI FT2232H
and need newer drivers.
Download our new Amontec JTAGkey Driver from :
http://www.amontec.com/download/amontec-jtagkey-driver-d2xx-20091124.zip
Go to device manager of Windows and update both channel A and channel B
of Amont
Hi all,
I tried several methods to install OpenOCD on Windows - all without success.
First I tried explanation given here :
http://forum.sparkfun.com/viewtopic.php?t=11221
I was capable to install OpenOCD v.0.4.0, but only after moving
ftd3xx.lib to i386/libftd.a. But with this installation my Am
Yes, it is compiled with the PPDEV option as a module and it is
loaded. It's not an access problem, I'm running the command as root and
from the config file the parport loads well.
parport_port 0
with the 0x378 address it doesn't work eventhough it is configured that
way in BIOS. I've chec
25 matches
Mail list logo
