On Monday 25 January 2010, Edgar Grimberg wrote: > > Now I'm getting some other type of problem on my iMX.31. I try to load:
This is unrelated to breakpoints ... but it resembles what I saw a few times trying to load code into SRAM. I had thought it was related to some other patches (non-mainline) I've been carrying around, or some of the secure boot mode stuff I've been lucky so far to avoid. It went away, somewhat mysteriously... > (gdb) load > Loading section .rom_vectors, size 0x40 lma 0x87f00000 > Load failed > (gdb) > > And the log: > > > Debug: 1905 130830 gdb_server.c:2145 gdb_input_inner(): received > packet: 'X87f00000,0:<binary-data>' > Debug: 1906 130830 gdb_server.c:2145 gdb_input_inner(): received > packet: 'X87f00000,40:<binary-data>' > Debug: 1907 130830 gdb_server.c:1388 gdb_write_memory_binary_packet(): > addr: 0x87f00000, len: 0x00000040 > Debug: 1908 130830 target.c:1251 target_write_buffer(): writing buffer > of 64 byte at 0x87f00000 > Debug: 1909 130830 arm11.c:948 arm11_write_memory_inner(): ADDR > 87f00000 SIZE 00000004 COUNT 00000010 > Error: 1910 130835 arm11.c:1069 arm11_write_memory_inner(): Data > transfer failed. Expected end address 0x87f00040, got 0x00405614 That's the same error I saw: it was checking the buffer pointer, and the value was not as expected. However: did you check the buffer to see if it had the right data? What I saw was the right data in the buffer... > Error: 1911 130835 arm11.c:1072 arm11_write_memory_inner(): use 'arm11 > memwrite burst disable' to disable fast burst mode Yeah, these next messages (which you removed in another patch) are just annoying noise ... > Error: 1912 130835 gdb_server.c:1211 gdb_error(): unexpected error -4 > Debug: 1913 130936 arm11.c:67 arm11_check_init(): DSCR 4000605b > Debug: 1914 131036 core.c:535 jtag_add_statemove(): cur_state=DRPAUSE > goal_state=DRPAUSE > Debug: 1915 131036 arm11.c:67 arm11_check_init(): DSCR 4000601b > Debug: 1916 131136 core.c:535 jtag_add_statemove(): cur_state=DRPAUSE > goal_state=DRPAUSE > Debug: 1917 131136 arm11.c:67 arm11_check_init(): DSCR 4000601b > > The LOG_DEBUG at the beginning of jtag_add_statemove makes the log a > bit noisy on debug_level 3, even if the system (target + openocd) is > idling. I'm sending a patch to silence the messages. ... and I'll merge that. > > Edgar > > > > > - Dave > > > > > > -- > Edgar Grimberg > System Developer > Zylin AS > ZY1000 JTAG Debugger http://www.zylin.com/zy1000.html > Phone: (+47) 51 63 25 00 > > _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
