On Wed, Jan 13, 2010 at 8:50 AM, David Brownell wrote:
> On Tuesday 12 January 2010, Øyvind Harboe wrote:
>> So I think the best thing is to be able to dump
>> the startup.tcl at this point then, it covers the line #'s
>> in stack traces.
>
> I certainly think that's the best solution all around,
On Tuesday 12 January 2010, Øyvind Harboe wrote:
> So I think the best thing is to be able to dump
> the startup.tcl at this point then, it covers the line #'s
> in stack traces.
I certainly think that's the best solution all around,
for that particular sub-problem.
A command-line flag would suff
Hi Jerry,
could you test the patch to see if it solves your problems?
--
Ø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
From 682beb8ca5506a8fdb3b89fc227942bdee51a6d1 Mon
So I think the best thing is to be able to dump
the startup.tcl at this point then, it covers the line #'s
in stack traces.
--
Ø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 programm
On Tuesday 12 January 2010, Øyvind Harboe wrote:
> > And it wouldn't create new headaches like ending up with
> > an old version of a discrete 'startup.tcl' ... or missing
> > any version whatsoever.
>
> Another thing that I was thinking about: how about using a
> startup.tcl on disk if it is ther
On Tuesday 12 January 2010, Alexei Babich wrote:
> Error: 'arm11 target' JTAG error SCREG OUT 0x1f
> Error: 'arm11 target' JTAG error SCREG OUT 0x1f
> Error: 'arm11 target' JTAG error SCREG OUT 0x1f
> Error: DPM REG READ -- fail -4
> Error: 'arm11 target' JTAG error SCREG OUT 0x1f
> Error: 'arm11 t
On Wed, Jan 13, 2010 at 7:08 AM, David Brownell wrote:
> On Tuesday 12 January 2010, Øyvind Harboe wrote:
>> > What happened to the idea of a command to print that
>> > embedded 'startup.tcl' file on demand?
>>
>> That does not address the problem of stack traces upon
>> errors during e.g. reset.
Hello all.
I sealed Freescale iMX35, connect to JTAG and JTAG 15 seconds later stops
working, here's the log:
---
[imp...@kb33 ~]$ openocd/bin/openocd -f openocd/imx35.cfg -f openocd/parport.cfg
Open On-Chip Debugger 0.4.0-rc1-dev-00017-gd4bef46 (2009-12-30-10:12)
For bug reports, read
htt
On Tuesday 12 January 2010, Øyvind Harboe wrote:
> > What happened to the idea of a command to print that
> > embedded 'startup.tcl' file on demand?
>
> That does not address the problem of stack traces upon
> errors during e.g. reset.
Right, there were several problems. You had fixes for
severa
On Tue, Jan 12, 2010 at 10:54 PM, David Brownell wrote:
> On Monday 11 January 2010, Øyvind Harboe wrote:
>> --- a/src/target/arm7_9_common.c
>> +++ b/src/target/arm7_9_common.c
>> @@ -2723,6 +2723,17 @@ int arm7_9_examine(struct target *target)
>> return retval;
>> }
>>
>> +
>> +int arm7_9
> What happened to the idea of a command to print that
> embedded 'startup.tcl' file on demand?
That does not address the problem of stack traces upon
errors during e.g. reset.
--
Øyvind Harboe
US toll free 1-866-980-3434 / International +47 51 63 25 00
http://www.zylin.com/zy1000.html
ARM7 ARM
On Tuesday 12 January 2010, David Brownell wrote:
> On Tuesday 12 January 2010, Thomas Kindler wrote:
> > David Brownell wrote:
> > >
> > > Could you give the appended patch a try?
> >
> > I'd love to!
> >
> > But right now, I'm stuck with building libftdi under cygwin. In the
> > past, I on
On Tuesday 12 January 2010, Audrius Urmanavicius wrote:
> > Thing is, a watchdog is a global constraint device, so I don't see how
> > guarding it like that only for critical sections would help.
>
>
> ("mission critical section" of algorithm should not be confused here
> with "code critical sec
On Sunday 10 January 2010, Freddie Chopin wrote:
> The short version is like this - after power-up of JTAG and STM32 board,
> the first "load" from gdb just fails with "cannot write
> ..." error. At this moment I'm not sure whether it's a reset of JTAG
> "after power-up" issue (the problem whic
On 2010.01.13 00:06, David Brownell wrote:
> On Tuesday 12 January 2010, Audrius Urmanavicius wrote:
>
>> Hi,
>>
>>
>> On 2010.01.12 05:17, David Brownell wrote:
>>
>>> On Monday 11 January 2010, Michel Catudal wrote:
>>>
>>>
That is correct. As for the watchdog, once you
On Tuesday 12 January 2010, Thomas Kindler wrote:
> David Brownell wrote:
> > On Monday 11 January 2010, Thomas Kindler wrote:
> >>> To clarify: it behaves fine after adding that line,
> >>> no wierdness?
> >> Not really - I still have to do one additional system reset using the
> >> push-button
On Tuesday 12 January 2010, Spencer Oliver wrote:
> - add mips support for target algorithms.
> - added handlers for target_checksum_memory and target_blank_check_memory.
>
> Signed-off-by: Spencer Oliver
At first glance, this sounds more like new-feature than bug-fix;
but right now we want
On Tuesday 12 January 2010, Audrius Urmanavicius wrote:
> Hi,
>
>
> On 2010.01.12 05:17, David Brownell wrote:
> > On Monday 11 January 2010, Michel Catudal wrote:
> >
> >> That is correct. As for the watchdog, once you enable it you can no
> >> longer debug as it keep reseting.
> >>
On Monday 11 January 2010, Øyvind Harboe wrote:
> --- a/src/target/arm7_9_common.c
> +++ b/src/target/arm7_9_common.c
> @@ -2723,6 +2723,17 @@ int arm7_9_examine(struct target *target)
> return retval;
> }
>
> +
> +int arm7_9_check_reset(struct target *target)
> +{
> + struct arm7_9_co
On Monday 11 January 2010, Øyvind Harboe wrote:
> Allow targets to run checks post reset. Used to check
> that e.g. DCC downloads have been enabled.
The only thing that bothered me about this is the notion
that this hook doesn't seem to be needed for other purposes.
Then I realized that it could
- add mips support for target algorithms.
- added handlers for target_checksum_memory and target_blank_check_memory.
Signed-off-by: Spencer Oliver
---
src/target/mips32.c | 302
-
src/target/mips32.h | 10 ++
src/target/mips_m4k.c | 2
Hi,
On 2010.01.12 05:17, David Brownell wrote:
> On Monday 11 January 2010, Michel Catudal wrote:
>
>> That is correct. As for the watchdog, once you enable it you can no
>> longer debug as it keep reseting.
>>
> Isn't there an STM32-specific register to prevent the watchdog
> from
On Monday 11 January 2010, Øyvind Harboe wrote:
> IMHO, embedding into openocd executable is really the root
> cause of this misery in the first place.
It's a clean way to minimize dependencies on external files,
though... as in, eliminating installation bugs like "still
using the 'startup.tcl' ve
Use the correct bitfield to specify the register whose
top halfword gets replaced.
Signed-off-by: David Brownell
---
GCC isn't yet smart about using mov+movt for 32-bit constants,
avoiding pipeline hiccups from constant pools, so these are rare.
Patch affects only Thumb2 decode, and doesn't add
David Brownell wrote:
> On Monday 11 January 2010, Thomas Kindler wrote:
>>> To clarify: it behaves fine after adding that line,
>>> no wierdness?
>> Not really - I still have to do one additional system reset using the
>> push-button. But it's way better than having to power-cycle for my
>> ap
On Monday 11 January 2010, Thomas Kindler wrote:
>
> > To clarify: it behaves fine after adding that line,
> > no wierdness?
>
> Not really - I still have to do one additional system reset using the
> push-button. But it's way better than having to power-cycle for my
> application.
Could yo
26 matches
Mail list logo
