Piet Delaney wrote:
> Dirk Behme wrote:
>> Piet Delaney wrote:
>>> Dirk Behme wrote:
David Brownell wrote:
> On Friday 21 August 2009, Dirk Behme wrote:
>> While reading in the git thread the keyword "branch":
>>
>> What's about a "beagle-testing" or similar branch with the pat
Dirk Behme wrote:
> Piet Delaney wrote:
>> Dirk Behme wrote:
>>> David Brownell wrote:
On Friday 21 August 2009, Dirk Behme wrote:
> While reading in the git thread the keyword "branch":
>
> What's about a "beagle-testing" or similar branch with the patches
> mentioned above?
Piet Delaney wrote:
> Dirk Behme wrote:
>> David Brownell wrote:
>>> On Friday 21 August 2009, Dirk Behme wrote:
While reading in the git thread the keyword "branch":
What's about a "beagle-testing" or similar branch with the patches
mentioned above?
>>> Feel free to set up suc
Dirk Behme wrote:
> David Brownell wrote:
>> On Friday 21 August 2009, Dirk Behme wrote:
>>> While reading in the git thread the keyword "branch":
>>>
>>> What's about a "beagle-testing" or similar branch with the patches
>>> mentioned above?
>> Feel free to set up such a GIT branch in a repositor
On Monday 31 August 2009, Dirk Behme wrote:
> >> Is anything like
> >>
> >> if(omap3) {
> >> /*
> >> * Add a bunch of clocks after TLR entry to force SWD reset (newer
> >> * ARM cores; just in case, ~50 cycles), switch on ICEpick power
> >> * domains (for some TI part
Øyvind, Dave,
Øyvind Harboe wrote:
> On Tue, Aug 25, 2009 at 4:33 PM, Dirk Behme wrote:
>> Øyvind Harboe wrote:
>>> I have committed all but 01_openocd_beagle.patch to hopefully get things
>>> moving along
>>>
>>> 01_openocd_beagle.patch is problematic because it modifies the behavior
>>> for
On Tuesday 25 August 2009, Øyvind Harboe wrote:
> > I see no problem ... TAP_RESET is a stable state, and
> > JTAG adapters are allowed to let TCK run freely there.
>
> But that's not what the code is doing. It goes to TAP_RESET,
> then cycles 100 times in runtest idle and then back to TAP_RESET..
> I see no problem ... TAP_RESET is a stable state, and
> JTAG adapters are allowed to let TCK run freely there.
But that's not what the code is doing. It goes to TAP_RESET,
then cycles 100 times in runtest idle and then back to TAP_RESET
I guess I would be more comfortable with a change that
David Brownell wrote:
> On Friday 21 August 2009, Dirk Behme wrote:
>> While reading in the git thread the keyword "branch":
>>
>> What's about a "beagle-testing" or similar branch with the patches
>> mentioned above?
>
> Feel free to set up such a GIT branch in a repository
> you create ... :)
On Friday 21 August 2009, Dirk Behme wrote:
> While reading in the git thread the keyword "branch":
>
> What's about a "beagle-testing" or similar branch with the patches
> mentioned above?
Feel free to set up such a GIT branch in a repository
you create ... :)
___
On Tuesday 25 August 2009, Øyvind Harboe wrote:
> 01_openocd_beagle.patch is problematic because it modifies the behavior
> for *all* targets.
>
> Thoughts?
I see no problem ... TAP_RESET is a stable state, and
JTAG adapters are allowed to let TCK run freely there.
> We need some more general m
On Tue, Aug 25, 2009 at 4:33 PM, Dirk Behme wrote:
> Øyvind Harboe wrote:
>>
>> I have committed all but 01_openocd_beagle.patch to hopefully get things
>> moving along
>>
>> 01_openocd_beagle.patch is problematic because it modifies the behavior
>> for *all* targets.
>>
>> Thoughts?
>
> You mi
Øyvind Harboe wrote:
> I have committed all but 01_openocd_beagle.patch to hopefully get things
> moving along
>
> 01_openocd_beagle.patch is problematic because it modifies the behavior
> for *all* targets.
>
> Thoughts?
You might have noticed that I'm not really an expert of OpenOCD's code
I have committed all but 01_openocd_beagle.patch to hopefully get things
moving along
01_openocd_beagle.patch is problematic because it modifies the behavior
for *all* targets.
Thoughts?
--
Øyvind Harboe
Embedded software and hardware consulting services
http://www.zylin.com
Appended is th
Could you post a list of those patches that are ready to be
committed?
Thanks!
It would be great to focus this list one or a few remaining issues
--
Øyvind Harboe
Embedded software and hardware consulting services
http://www.zylin.com
___
Openocd-
On Sunday 23 August 2009, Dirk Behme wrote:
> Øyvind Harboe wrote:
> > Should these patches be committed as-is?
>
> From user point of view, I would say yes. Additional fixes/clean up
> can go on top of these, then.
>
> But we should let Dave decide, as all patches are from him or at least
> c
On Sunday 23 August 2009, Dirk Behme wrote:
> Having U-Boot running, halt and resume seem to work (but a lot of
> invalid mode warnings). And yes, "soft_reset_halt" still gives a segfault.
>
> What are the next steps which could be done with BeagleBoard?
Fix those segfaults ... minimally by find
On Sunday 23 August 2009, Dirk Behme wrote:
> >> http://lists.berlios.de/pipermail/openocd-development/2009-June/008256.html
Better to merge this version, if any ...
---
src/jtag/core.c |8
1 file changed, 8 insertions(+)
--- a/src/jtag/core.c
+++ b/src/jtag/core.c
@@ -469,6 +469,
Øyvind Harboe wrote:
> Should these patches be committed as-is?
From user point of view, I would say yes. Additional fixes/clean up
can go on top of these, then.
But we should let Dave decide, as all patches are from him or at least
cleaned up by him.
Best regards
Dirk
___
Hi,
I pulled out trunk 2604 and applied 4 patches. On my system, OpenOCD works the
way Dirk email has described.
Best regards,
James
--- On Sun, 8/23/09, Dirk Behme wrote:
> From: Dirk Behme
> Subject: Re: [Openocd-development] OpenOCD + beagle
> To: "David Brownell
Should these patches be committed as-is?
I haven't looked at the Beagleboard in detail yet.
--
Øyvind Harboe
Embedded software and hardware consulting services
http://www.zylin.com
___
Openocd-development mailing list
Openocd-development@lists.berlios
David Brownell wrote:
> On Wednesday 19 August 2009, James Lin wrote:
>
>> Then I tried to apply the patch described in
>>
>> http://lists.berlios.de/pipermail/openocd-development/2009-June/008256.html
>>
>> I don't know if this additional step was necessary but it seemed
>> to get correct mfg, p
On Wednesday 19 August 2009, James Lin wrote:
> Then I tried to apply the patch described in
>
> http://lists.berlios.de/pipermail/openocd-development/2009-June/008256.html
>
> I don't know if this additional step was necessary but it seemed
> to get correct mfg, part, ver.
So it *was* necessa
Hi,
I have tried to follow the information on the following page to run OpenOCD
with Beagleboard & Flyswatter board using Ubuntu 9.04 and got some errors.
http://lists.berlios.de/pipermail/openocd-development/2009-July/009314.html
The log message was
===
Magnus Lundin wrote:
> Hi list,
>
> I know there is a lot of fixing to get a stable 0.2.0 so this is
> clearly for next release.
> But I also know that some folks wants to get going with CortexA8, so
> here it comes.
Great! Many thanks!
Dave, Sergey: This does look like a really *good* starti
Sergey Lapin wrote:
> Hi, all!
>
> Is there any news regarding support of BeagleBoard in OpenOCD?
> Last time I checked, there was none, I'm interested to help, so I
> want to know the status and what can I do.
Recent status of trunk (at least the last time I checked):
https://lists.berlios.de/p
Sergey Lapin skrev:
> On Mon, Jul 6, 2009 at 7:43 PM, Magnus Lundin wrote:
>
>> Wookey skrev:
>>
>>> +++ Sergey Lapin [2009-07-06 19:02 +0400]:
>>>
>>>
Hi, all!
Is there any news regarding support of BeagleBoard in OpenOCD?
Last time I checked, there was none, I'm
On Mon, Jul 6, 2009 at 7:43 PM, Magnus Lundin wrote:
> Wookey skrev:
>> +++ Sergey Lapin [2009-07-06 19:02 +0400]:
>>
>>> Hi, all!
>>>
>>> Is there any news regarding support of BeagleBoard in OpenOCD?
>>> Last time I checked, there was none, I'm interested to help, so I
>>> want to know the status
Wookey skrev:
> +++ Sergey Lapin [2009-07-06 19:02 +0400]:
>
>> Hi, all!
>>
>> Is there any news regarding support of BeagleBoard in OpenOCD?
>> Last time I checked, there was none, I'm interested to help, so I
>> want to know the status and what can I do.
>>
>
> There is a config file for
+++ Sergey Lapin [2009-07-06 19:02 +0400]:
> Hi, all!
>
> Is there any news regarding support of BeagleBoard in OpenOCD?
> Last time I checked, there was none, I'm interested to help, so I
> want to know the status and what can I do.
There is a config file for it in SVN, so I assume there is some
Hi, all!
Is there any news regarding support of BeagleBoard in OpenOCD?
Last time I checked, there was none, I'm interested to help, so I
want to know the status and what can I do.
Thanks a lot,
S.
___
Openocd-development mailing list
Openocd-developmen
31 matches
Mail list logo
