On Dec 16, 2008, at 10:45 PM, SimonQian wrote:
Hi, It's not problem with OpenOCD, but with arm-none-eabi-gdb.exe. Reference to the discussed topic "Problem with GDB 6.8". My log is similar with Ramon's. I cut some information from his log:Debug: 700 10078 gdb_server.c:1997 gdb_input_inner(): received packet: 'mfffffffe,4' Debug: 701 10078 gdb_server.c:1137 gdb_read_memory_packet(): addr: 0xfffffffe, len: 0x00000004 Debug: 702 10078 target.c:1057 target_read_buffer(): reading buffer of 4 byte at 0xfffffffe Error: 703 10078 target.c:1068 target_read_buffer(): address+size wrapped(0xfffffffe, 0x00000004)Error: 704 10078 gdb_server.c:1098 gdb_error(): unexpected error -4On startup, reg 14(lr, link register) is 0xffffffff, so when step, arm-none-eabi-gdb will set a breakpoint at this position. On cortex-m3, this address will be anded(&) with 0xfffffffe, so arm- none-eabi-gdb will access 0xfffffffe. If OpenOCD return OK to this command "mfffffffe,4", arm-none-eabi- gdb will then send "Z0fffffffe,2" after some memory-reading commands.
Right, GDB is asking for something invalid. OpenOCD returns an error. I would suggest following up with the GDB developers.
-- Rick Altherr [email protected]"He said he hadn't had a byte in three days. I had a short, so I split it with him."
-- Unsigned
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
