On Mon, Jan 25, 2010 at 4:31 PM, Edgar Grimberg
<edgar.grimb...@zylin.com> wrote:
> On Sat, Jan 23, 2010 at 8:01 AM, David Brownell <davi...@pacbell.net> wrote:
>> I fired up GDB against an ARM1136 with current git code and
>> observed the "breakpoints work in Tcl, fail in GDB" problem.
>>
>> So I committed a fix that makes GDB work too, at least on
>> an omap2420 core.
>>
>> It'd be worth verifying this works on other ARM1136 targets.
>
> Now I'm getting some other type of problem on my iMX.31. I try to load:
>
> (gdb) moni reset init
> JTAG tap: imx31.etb tap/device found: 0x2b900f0f (mfg: 0x787, part:
> 0xb900, ver: 0x2)
> JTAG tap: imx31.cpu tap/device found: 0x07b3601d (mfg: 0x00e, part:
> 0x7b36, ver: 0x0)
> TAP imx31.whatchacallit does not have IDCODE
> JTAG tap: imx31.smda tap/device found: 0x2190101d (mfg: 0x00e, part:
> 0x1901, ver: 0x2)
> found ARM1136
> imx31.cpu: ran after reset and before halt ...
> target state: halted
> target halted in ARM state due to debug-request, current mode: Supervisor
> cpsr: 0x200001d3 pc: 0x0040560c
> (gdb) moni debug_level 3
> debug_level: 3
> (gdb) load
> Loading section .rom_vectors, size 0x40 lma 0x87f00000
> Load failed
> (gdb)


This is not a bug, but the way OpenOCD and GDB behave if there is no
RAM at that address. I was using the target/imx31.cfg instead of
board/im31pdk.cfg.

Regards,
Edgar


> 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
> Error: 1911 130835 arm11.c:1072 arm11_write_memory_inner(): use 'arm11
> memwrite burst disable' to disable fast burst mode
> 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.
>
> Edgar
>
>>
>> - Dave
>>
>
>
>
> --
> Edgar Grimberg
> System Developer
> Zylin AS
> ZY1000 JTAG Debugger http://www.zylin.com/zy1000.html
> Phone: (+47) 51 63 25 00
>



-- 
Edgar Grimberg
System Developer
Zylin AS

Visit us at Embedded World, March 2nd-4th. IS2T's stand, HALL 10 - 118
http://www.zylin.com/events_embeddedworld.html

ZY1000 JTAG Debugger http://www.zylin.com/zy1000.html
Phone: (+47) 51 63 25 00
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to