Committed.
Thanks!
--
Øyvind Harboe
Embedded software and hardware consulting services
http://www.zylin.com
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
Øyvind Harboe wrote:
Committed take #3 + your patch to the config file to allow
more in depth testing.
A patch to document the event in openocd.texi would
be greatly appreciated!
Something like in attachment?
Best regards
Dirk
Subject: [PATCH] Add post reset event documentation
From: Dirk Be
Committed take #3 + your patch to the config file to allow
more in depth testing.
A patch to document the event in openocd.texi would
be greatly appreciated!
--
Øyvind Harboe
Embedded software and hardware consulting services
http://www.zylin.com
___
Øyvind Harboe wrote:
Take #3...
I committed a fix for a bug where running jtag configure twice would
cause an infinite loop upon event nofitication, but it still bothers me that
jtag configure was invoked twice...
Seems to work for me (configuration patch in attachment):
> openocd -s lib/open
> I committed a fix for a bug where running jtag configure twice would
> cause an infinite loop upon event nofitication, but it still bothers me that
> jtag configure was invoked twice...
Red herring: I had the configure statement listed twice, so I uncovered
and fixed a real bug. No mysteries the
Take #3...
I committed a fix for a bug where running jtag configure twice would
cause an infinite loop upon event nofitication, but it still bothers me that
jtag configure was invoked twice...
--
Øyvind Harboe
Embedded software and hardware consulting services
http://www.zylin.com
### Eclipse Wo
On Wed, Sep 9, 2009 at 1:26 AM, David Brownell wrote:
> On Tuesday 08 September 2009, Ųyvind Harboe wrote:
>> There was a bug in waiting in the code that handled tap
>> events when more than 2 event types were added
>
> I saw that and had a different fix, which handled one
> additional case.
>
On Tuesday 08 September 2009, Øyvind Harboe wrote:
> There was a bug in waiting in the code that handled tap
> events when more than 2 event types were added
I saw that and had a different fix, which handled one
additional case.
But why was the call to the post-reset handler failing?
__
On Monday 07 September 2009, Øyvind Harboe wrote:
> 1. test that a robust post reset event can be written for Beagleboard
> that handles the "100 clocks after reset" problems.
With
jtag configure $_CHIPNAME.jrc -event post-reset "runtest 100"
when I "reset" at tcl I get "There are no en
take #2...
There was a bug in waiting in the code that handled tap
events when more than 2 event types were added
--
Øyvind Harboe
Embedded software and hardware consulting services
http://www.zylin.com
### Eclipse Workspace Patch 1.0
#P openocd
Index: src/flash/str9xpec.c
==
Example of use:
jtag newtap $_CHIPNAME cpu -irlen 4 -ircapture 0x1 -irmask 0xf
-expected-id $_CPUTAPID
jtag configure $_CHIPNAME.cpu -event post-reset {
puts hello!
}
--
Øyvind Harboe
Embedded software and hardware consulting services
http://www.zylin.com
__
Beagleboard needs 100 clocks after reset.
The attached patch adds support for a generic post-reset
event.
Testing & comments needed before committing:
1. test that a robust post reset event can be written for Beagleboard
that handles the "100 clocks after reset" problems.
2. test for regression
12 matches
Mail list logo
