1/1 
|
Burst read timed out. error
by pyaganti on May 21, 2012 |
pyaganti
Posts: 2 Joined: Apr 30, 2012 Last seen: Jun 25, 2012 |
||
|
Hi All,
We are trying to interface OR1200V3 with GDB and we are facing the following issue... WE tried changing "GDB_BUF_MAX" value with original value and remotetimeout value 10 and also tried low_speed option also(both RTL and bridge code). still same result. Can anybody help us how resolve this... adv_jtag_bridge log: yprasad@yprasad01:~/or1200_compiled/adv_jtag_bridge$ ./adv_jtag_bridge -l 0:4 -c 0x8 xpc_usb Found Xilinx Platform Cable USB (DLC9) Found Xilinx Platform Cable USB (DLC9) firmware version = 0x08FC (2300) cable CPLD version = 0xFFFE (65534) Enumerating JTAG chain... Devices on JTAG chain: Index Name ID Code IR Length ---------------------------------------------------------------- 0: (unknown) 0x149511C3 -1 Target device 0, JTAG ID = 0x149511c3 Using command-line debug command 0x8 JTAG bridge ready! RSP server sending stall command 0x1 Burst read timed out. Retry... Burst read timed out. Retry... Burst read timed out. Retry... Burst read timed out. Retry... Burst read timed out. Retry... Burst read timed out. gdb_log: yprasad@yprasad01:~/or1200_compiled/tests$ or32-elf-gdb cpu_mem_access.ihx Building automata... done, num uncovered: 0/213. Parsing operands data... done. GNU gdb 6.8 Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later " target="_blank">http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "--host=x86_64-unknown-linux-gnu --target=or32-elf"... (no debugging symbols found) (gdb) set remotetimeout 10 (gdb) show remotetimeout Timeout limit to wait for target to respond is 10. (gdb) target remote :9999 Remote ***** debugging ***** using :9999 Ignoring packet error, continuing... warning: unrecognized item "timeout" in "qSupported" response Ignoring packet error, continuing... Ignoring packet error, continuing... Ignoring packet error, continuing... warning: Invalid remote reply: timeout |
|||
|
RE: Burst read timed out. error
by pyaganti on May 23, 2012 |
pyaganti
Posts: 2 Joined: Apr 30, 2012 Last seen: Jun 25, 2012 |
||
|
some more observations...
with version1(or1200v1) we are seeing the same issue if try to connect to GDB while CPU is in reset state. But if we try to connect after releasing the reset to the cpu then its connecting but we are not able to debug any thing. Giving error like "Don't know how to run" Can anybody please help us Regards, Prasad |
|||
|
RE: Burst read timed out. error
by nyawn on May 24, 2012 |
nyawn
Posts: 173 Joined: Dec 19, 2008 Last seen: May 31, 2023 |
||
|
For your first problem, the debugger will not communicate with the WishBone while the system is in the reset state, and anything it gets from the CPU will be undefined. This is just the way the debugger works, so make sure your system is not in the reset state and has a good clock signal before you try connecting with the debugger.
For your second problem, "Don't know how to run," this is a problem with the way you're using GDB. I'm not much of a GDB expert, so I don't know how to fix this problem...try "help target" like the error message says, or google the error message. My first guesses are that it doesn't understand the format of the binary you gave it, or you forgot or mistyped 'target remote :9999.' |
|||
1/1