Nived schrieb:
> 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 happenin
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, Drask
On Wed, Sep 15, 2010 at 8:28 PM, Drasko DRASKOVIC
wrote:
> On Wed, Sep 15, 2010 at 7:58 PM, Mike Dunn 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
On Wed, Sep 15, 2010 at 7:58 PM, Mike Dunn 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 failed to halt on so
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 fr
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
Hi Mike,
On Wed, Sep 15, 2010 at 5:23 PM, Mike Dunn 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 write in OPenOCD
co
Mike,
Yes, the intelmote2 is Xscale. Could it be a configuration issue then ? I am
using the default cfg files pxa270.cfg, crossbow_tech_imote2.cfg and
olimex_arm_usb_tiny_h.cfg.
Drasko,
Yes hardware breakpoints are working in my case, so it looks like the same
issue you are facing.
- Nived
On
On 09/14/2010 01:45 PM, Drasko DRASKOVIC wrote:
> 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 ret
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
_
15 matches
Mail list logo
