On Tue, Sep 14, 2010 at 12:57 AM, Drasko DRASKOVIC
wrote:
> On Mon, Sep 13, 2010 at 4:38 PM, Laurent Gauch
> wrote:
>> Download our new Amontec JTAGkey Driver from :
>> http://www.amontec.com/download/amontec-jtagkey-driver-d2xx-20091124.zip
>
> Hi Laurent,
> thanks very much. I can confirm that
On Wed, Sep 15, 2010 at 12:22 AM, Nived wrote:
> Hi,
> I have been using software breakpoints to debug, i was using an older
> version of OpenOCD and only recently upgraded to a higher version. I can
> confirm that the issue exists for software breakpoints, how do i check the
> hardware breakpoint
Hi,
I have been using software breakpoints to debug, i was using an older
version of OpenOCD and only recently upgraded to a higher version. I can
confirm that the issue exists for software breakpoints, how do i check the
hardware breakpoints ?
Also i tried setting pc to a higher value, but it sa
On Tue, Sep 14, 2010 at 11:42 PM, Nived wrote:
> Hi,
> I was just about to try the patch in sparkfun.
Try it, maybe it will work for you. And might throw some light on the issue.
> Btw, in one of the mails in
> the thread you mention that you used set $pc = $pc + 4 and it worked. Where
> did you
Hi,
I was just about to try the patch in sparkfun. Btw, in one of the mails in
the thread you mention that you used set $pc = $pc + 4 and it worked. Where
did you use it and why isn't that a work around ?
- Nived
On Tue, Sep 14, 2010 at 4:45 PM, Drasko DRASKOVIC <
drasko.drasko...@gmail.com> wro
On Tue, Sep 14, 2010 at 10:24 PM, Nived 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 execution returns to the same point.
> Is there any particular reaso
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 execution returns to the same point.
Is there any particular reason why this may be happening ?
- Nived
_
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
_
On Tue, Sep 14, 2010 at 1:18 AM, Drasko DRASKOVIC
wrote:
...\openocd-0.5.0-dev-100827221639\drivers\libusb-win32_ft2232_driver-100831.zip
>>>
>>> I do not see it here neither:
>>> http://openocd.git.sourceforge.net/git/gitweb.cgi?p=openocd/openocd;a=tree
>>
>> These archives are included in t
2010-09-14 11:46 keltezéssel, Laurent Gauch írta:
Hi,
the new Marvell PXA270M processor has a new TAPID: 0x89265013.
Attached you will find a patch for target/pxa270.cfg that will handle
this.
I have also attached a board/colibri.cfg file to support the Colibri
PXA270 module by Toradex.
H
Hi,
the new Marvell PXA270M processor has a new TAPID: 0x89265013.
Attached you will find a patch for target/pxa270.cfg that will handle this.
I have also attached a board/colibri.cfg file to support the Colibri
PXA270 module by Toradex.
Hope you can use it!
Best regards,
Áron Takács
Merged.
Thanks!
I deleted the "init" + "reset init" from the colibri.cfg and placed
it in board/
--
Ø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
__
Hi,
the new Marvell PXA270M processor has a new TAPID: 0x89265013.
Attached you will find a patch for target/pxa270.cfg that will handle this.
I have also attached a board/colibri.cfg file to support the Colibri
PXA270 module by Toradex.
Hope you can use it!
Best regards,
Áron Takács
# Tora
On Tue, Sep 14, 2010 at 4:17 AM, Peter Stuge wrote:
> Freddie Chopin wrote:
>> ...\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.
The wdi-simple examp
14 matches
Mail list logo
