Andreas,
Last time I sent to you the huge log (don't spend your time with that log,
it's irrational to handle) I wrote that I have one situation before and
after MMU be enabled and I decided to try to get some clues , first with
MMU disabled and here is what I found.
This is the disassembly at kernel start point:
Dump of assembler code for function stext:
0x80008000 <+0>: add r9, pc, #1
=> 0x80008004 <+4>: bx r9
0x80008008 <+8>: ldmibeq r3, {r0, r1, r2, r3, r6, r12, sp, lr, pc}^
0x8000800c <+12>: smlabbhi r0, r9, r3, pc ; <UNPREDICTABLE>
0x80008010 <+16>: svcls 0x0010ee10
I did a single step at first instruction (0x80008000) but not the next and
you will see that it seems to be because size=3.
I removed all arm thumb information from the kernel configuration for not
have mixed instructions.
Make any sense for you gdb request read physical memory with size = 3 ???
Maybe the problem is not openocd but gdb !!!
Have you seen something like this before (gdb screw up the trace) ???
Debug: 1360 186999 gdb_server.c:2048 gdb_input_inner(): received packet:
'm80008008,2'
Debug: 1361 186999 gdb_server.c:1200 gdb_read_memory_packet(): addr:
0x80008008, len: 0x00000002
Debug: 1362 186999 target.c:1769 target_read_buffer(): reading buffer of 2
byte at 0x80008008
Debug: 1363 186999 cortex_a.c:1986 cortex_a8_read_memory(): Reading memory
at address 0x80008008; size 2; count 1
Debug: 1364 186999 cortex_a.c:1939 cortex_a8_read_phys_memory(): Reading
memory at real address 0x80008008; size 2; count 1
Debug: 1365 187001 gdb_server.c:2048 gdb_input_inner(): received packet:
'Z0,80008008,3'
Debug: 1366 187001 gdb_server.c:1394 gdb_breakpoint_watchpoint_packet(): -
Debug: 1367 187001 cortex_a.c:1986 cortex_a8_read_memory(): Reading memory
at address 0x80008008; size 3; count 1
Debug: 1368 187001 cortex_a.c:1939 cortex_a8_read_phys_memory(): Reading
memory at real address 0x80008008; size 3; count 1
Error: 1369 187001 cortex_a.c:1408 cortex_a8_set_breakpoint(): Error @
cortex_a8 read_memory:-601
Error: 1370 187001 breakpoints.c:96 breakpoint_add_internal(): can't add
breakpoint: unknown reason
Debug: 1371 187001 gdb_server.c:1163 gdb_error(): Reporting -601 to GDB as
generic error
Debug: 1372 187001 gdb_server.c:2048 gdb_input_inner(): received packet:
'z1,80008000,4'
Debug: 1373 187001 gdb_server.c:1394 gdb_breakpoint_watchpoint_packet(): -
Debug: 1374 187001 cortex_a.c:1623 cortex_a8_unset_breakpoint(): rbp 0
control 0x1e7 value 0x80008000
Debug: 1375 187005 breakpoints.c:309 breakpoint_free(): free BPID: 6 --> 0
Thank you.
On Sat, Oct 13, 2012 at 1:11 AM, Andreas Fritiofson <
[email protected]> wrote:
> On Sat, Oct 13, 2012 at 3:30 AM, Jorge Ventura
> <[email protected]> wrote:
> > Because the messages are the same, I put a tag to see from each one gdb
> is
> > getting and the tag points to the second where there is a comment that
> > ***should never happen***.
>
> FYI, with debug log enabled (-d3), the source file and line is printed
> for every log message so there's no need to edit code to find out
> where it came from.
>
> Also, a debug log is probably necessary to track the problem down, so
> please post it to the list. Keep the session short if possible, to
> keep the log size down, but don't edit the log.
>
> /Andreas
>
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel
