Info: openocd.c:82 main(): Open On-Chip Debugger (2006-10-12 18:00 CEST)
Error: ft2232.c:1033 ft2232_init(): unable to open ftdi device: 2
Error: ft2232.c:1048 ft2232_init(): ListDevices: 2
Error: ft2232.c:1050 ft2232_init(): 0: Olimex OpenOCD JTAG B
Error: ft2232.c:1050 ft2232_init(): 1: ˆS>
jadavjd:
Info: openocd.c:82 main(): Open On-Chip Debugger (2006-10-12 18:00 CEST)
Error: ft2232.c:1033 ft2232_init(): unable to open ftdi device: 2
Error: ft2232.c:1048 ft2232_init(): ListDevices: 2
Error: ft2232.c:1050 ft2232_init(): 0: Olimex OpenOCD JTAG B
Error: ft2232.c:1050 ft2232_init(): 1: ˆS>
You may have a config file error.
I use the following in my config file, which works for me with the OpenOCD in the YAGARTO distribution.
It appears that you are trying to use “B” instead of “A” in your config file.
–Dave
#************************************************************
#interface
interface ft2232
ft2232_device_desc “Olimex OpenOCD JTAG A”
ft2232_layout “olimex-jtag”
ft2232_vid_pid 0x15BA 0x0003
jtag_speed 2
Thanks for help
Ok I got working debugger but when i do step over
i got warning
so what can be do to remove this warning?
Info: openocd.c:82 main(): Open On-Chip Debugger (2006-10-12 18:00 CEST)
Warning: arm7_9_common.c:842 arm7_9_halt(): target was already halted
Info: server.c:67 add_connection(): accepted ‘gdb’ connection from 0
Warning: arm7_9_common.c:1798 arm7_9_read_memory(): memory read caused data abort (address: 0xfffffffe, size: 0x1, count: 0x4)
Presumably the GDB requested that read when it was trying to trace the stack frames. This Warning usually isn’t critical.
Regards,
Dominic