duane> [about a jtag que command, ie: execute que]
oyvind> [ some concerns - about a jtag que command ]
[snip]
> My thinking was that e.g. drscan would throw this exception and that we didn't
> expose execute queue. Why should expose an asynchronous model for scripting?
> It complicates the API.
Øyvind> The "target_script" command must be supported, it's *old* :-)
I presume you specifically mean the "target_script" - command
functionality as in the file: "startup.tcl".
It was - "handle_target_script_command()" in target.c - in an older openocd.
I believe this is simple.
(A) The old com
Take #2
Perhaps poll() has not been invoked?
--
Øyvind Harboe
http://www.zylin.com/zy1000.html
ARM7 ARM9 XScale Cortex
JTAG debugger and flash programmer
Index: C:/workspace/trunk/src/server/gdb_server.c
===
--- C:/workspace/trunk
On Tuesday 22 July 2008 22:15:08 you wrote:
> > -gdb-gdb-gdb-gdb-
> >--- [EMAIL PROTECTED]:~/arm$
> > ntoarm-gdb
> > /home/vmaster/arm/qnx/workspace/sam9_l9260/Images/startup-at91sam9263ek.s
> >ym GNU gdb 6.7
> > Copyright (C) 2007 Free So
> (gdb) target remote localhost:
> Remote debugging using localhost:
> warning: while parsing target memory map (at line 2): Required element
> is missing
Does this patch remove the warning above?
(Unrelated to the pc=0 upon connect problems I think)
--
Øyvind Harboe
http://www.zylin.
> -gdb-gdb-gdb-gdb
> [EMAIL PROTECTED]:~/arm$
> ntoarm-gdb
> /home/vmaster/arm/qnx/workspace/sam9_l9260/Images/startup-at91sam9263ek.sym
> GNU gdb 6.7
> Copyright (C) 2007 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL versi
Hi list,
is it possible that GDB support in OpenOCD is currently at least partially
broken? Are there known bugs that came with TCL, is this something unrelated,
but known, or is this something new?
I let the OpenOCD attach to a running target (AT91SAM9260, currently executing
u-boot), poll th
sorry for the top posting, my email client is not good with html
My thoughts are that your target should already be halted before gdb
connects, as are using reset_init.
This would be place to start looking.
Regards
Spen
_
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of P
> It would be great if the Flash lock bits are cleared too.
This was thought about a while back, perhaps it needs looking at again.
The solution for gdb is to use the target_script, eg.
target_script 0 gdb_program_config unlock.script
in the unlock.script just put the commands to issue before pro
Hi,
I still getting same error messages like Longfield:
http://forum.sparkfun.com/viewtopic.php?p=46092&sid=52e20118cd881f047a7d534a4be37adb
Following this forum messages I tried to comment out the
"device->idcode = idcode;" line in the src/jtag/jtag.c file, but it
don't solved the problem.
I am
Hi List,
When using the command "flash write_image erase" or the automatic programming
interface of GDB/Insight, the following error occurs:
Debug: 1174 28601 cfi.c:278 cfi_intel_wait_status_busy(): status: 0xa2
Error: 1175 28601 cfi.c:286 cfi_intel_wait_status_busy(): status register:
0xa2
>> cmd_ctx contains current target today. The above definitively moves
>> current target out of cmd_ctx. OK by me, but we need backwards
>> compatibility.
>>
>
> No it does not. The idea is the "command private" variable holds the
> 'current target pointer".
>
> I do not see that something is break
Øyvind Harboe wrote:
> On Tue, Jul 22, 2008 at 5:23 AM, Duane Ellis <[EMAIL PROTECTED]> wrote:
>
>> Duane Ellis wrote:
>>
>>> Øyvind Harboe wrote:
>>>
Would you be interested in porting target_process_reset to Tcl?
>>> Let me read through this code a bit and d
> >
> > try attached patch, not got a working xgcc to test against
> here at the
> > moment.
>
>
> It failed:
>
try this version, have tested on --host-arm-uclinuxeabi and passes my tests.
if you still get problems try a make distclean
Cheers
Spen
build.patch
Description: Binary data
_
Committed.
Only print out gobs of information to log when -d3 is enabled.
The log is part of the user interface and by default it prints out too much
information which drowns normal messages.
If some of the messages are a bit terse without the -d3 context, then
the error messages should be flesh
15 matches
Mail list logo
