From the faq in the manual now all we need is an interactive
troubleshooting module :-)
@item @b{Win32 Pathnames} Why don't backslashes work in Windows paths?
OpenOCD uses Tcl and a backslash is an escape char. Use @{ and @}
around Windows filenames.
@example
> echo \a
> echo @{...@}
\a
> e
>> So:
>>
>> somecmd c:\n
>>
>> must be written:
>>
>> somecmd c:\\n
>
>
> -ENOPATCH
Yeah I was thinking about Edgar's comment that the advice has to be
presented to the user at some opportune time... "Didn't you read page
152315123?"
--
Øyvind Harboe
Visit us at Embedded World, March 2nd-
On Wednesday 10 February 2010, Edgar Grimberg wrote:
> On Wed, Feb 10, 2010 at 10:38 PM, David Brownell wrote:
> >
> > Yes, systematic testing to help uncover regressions is really The Way
> > To Do Things. I'm not sure how complete our test coverage is, though.
>
> One entire category was inten
On Wednesday 10 February 2010, Øyvind Harboe wrote:
> >> I suspect you're mostly referring to Edgar's work. I don't think I've
> >> seen evidence of that from anyone else. :(
> >
> > Actually Laurentiu Cocanu did a most of the hard work here, but
> > Edgar designed these tests.
>
> Let me try to
On Wed, Feb 10, 2010 at 10:58 PM, Øyvind Harboe wrote:
> On Wed, Feb 10, 2010 at 10:38 PM, David Brownell wrote:
>> On Wednesday 10 February 2010, Řyvind Harboe wrote:
>>> > Ideally, an RC2 would be *VERY* short. This release cycle hasn't gone
>>> > as quickly as I wanted, mostly because of unre
On Wed, Feb 10, 2010 at 10:38 PM, David Brownell wrote:
> On Wednesday 10 February 2010, Øyvind Harboe wrote:
>> > Ideally, an RC2 would be *VERY* short. This release cycle hasn't gone
>> > as quickly as I wanted, mostly because of unresolved regressions.
>>
>> And I would also say that there has
On Wed, Feb 10, 2010 at 10:16 PM, David Brownell wrote:
> On Wednesday 10 February 2010, Řyvind Harboe wrote:
>> > I would like to commit this arm11 lockup:
>> >
>> > https://lists.berlios.de/pipermail/openocd-development/2010-February/014665.html
>
> This patch addressees a different issue than t
On Wed, Feb 10, 2010 at 10:38 PM, David Brownell wrote:
> On Wednesday 10 February 2010, Řyvind Harboe wrote:
>> > Ideally, an RC2 would be *VERY* short. This release cycle hasn't gone
>> > as quickly as I wanted, mostly because of unresolved regressions.
>>
>> And I would also say that there has
On Wednesday 10 February 2010, Øyvind Harboe wrote:
> > Ideally, an RC2 would be *VERY* short. This release cycle hasn't gone
> > as quickly as I wanted, mostly because of unresolved regressions.
>
> And I would also say that there has been a very systematic testing effort
> that has uncovered pr
On Wednesday 10 February 2010, Øyvind Harboe wrote:
> > I would like to commit this arm11 lockup:
> >
> > https://lists.berlios.de/pipermail/openocd-development/2010-February/014665.html
This patch addressees a different issue than the bug report you
filed (which seems to me to be a clear case of
> I would like to commit this arm11 lockup:
>
> https://lists.berlios.de/pipermail/openocd-development/2010-February/014665.html
The arm11 target has only recently become robust enough to
recommend for mortals, so bugfixes weigh in more heavily than
regression concerns for this target, IMO.
--
> Ideally, an RC2 would be *VERY* short. This release cycle hasn't gone
> as quickly as I wanted, mostly because of unresolved regressions.
And I would also say that there has been a very systematic testing effort
that has uncovered problems and verified that there aren't others
I would like
On Wednesday 10 February 2010, Edgar Grimberg wrote:
> Hi,
>
> Looking over the trac list, it looks that there are only some minor
> cosmetics tickets to be fixed for this release.
I see tickets #4 (regression in helptext framework), #16 (stm32 unlock
information shortage), and #17 (seems like a
OK to apply?
I checked elsewhere in the code, but I believe this was the last place
in the arm11 code that lacked a timeout
--
Øyvind Harboe
Visit us at Embedded World, March 2nd-4th. IS2T's stand, HALL 10 - 118
http://www.zylin.com/events_embeddedworld.html
US toll free 1-866-980-3434
reset init would get stuck in an infinite loop when
khz was too high, added timeout.
Signed-off-by: Øyvind Harboe
---
src/target/arm11_dbgtap.c | 27 +++
1 files changed, 23 insertions(+), 4 deletions(-)
diff --git a/src/target/arm11_dbgtap.c b/src/target/arm11_dbgtap.
Hi,
Looking over the trac list, it looks that there are only some minor
cosmetics tickets to be fixed for this release.
I believe that we can safely cut a new RC, give it a new round of
tests and prepare for 0.4 final.
Volunteers for bagging and tagging?
Regards,
Edgar
--
Edgar Grimberg
System
>>
>> That's fine, you may have to power cycle before the settings take effect.
>
> I see! Now it works fine! Thanks for help.
>
>> If you have SRST connected that should also work, reseting using the
>> VC_CORERESET will not work.
>
> Should I write the powercycle (or SRST) trick somewhere in the
On Wed, Feb 10, 2010 at 3:58 PM, Spencer Oliver wrote:
> On 10/02/2010 09:07, Edgar Grimberg wrote:
>>
>> Now, how do I turn the readout protection off? I've tried:
>>
>>> stm32x unlock 0
>>
>> Device Security Bit Set
>> stm32x unlocked
>>>
>>> stm32x options_read 0
>>
>> Option Byte: 0x3fe
>>
On 10/02/2010 09:07, Edgar Grimberg wrote:
>
> Now, how do I turn the readout protection off? I've tried:
>
>> stm32x unlock 0
> Device Security Bit Set
> stm32x unlocked
>> stm32x options_read 0
> Option Byte: 0x3fe
> Readout Protection On
> Software Watchdog
> Stop: No reset generated
> Stand
> Just tried this with two separate boards and working ok here.
> Up until the mdw the log is the same as mine, i am using a ftdi based
> adapter. I can try a parport wiggler tomorrow.
I tried with our JTAG debugger and it fails just the same. I'm doing
the parport tests to be on the neutral side.
20 matches
Mail list logo
