OpenCores

OpenCores

Unable to download codes with GDB

no use

no use

1/3

Next

Last

Unable to download codes with GDB by danny7711 on May 28, 2010			danny7711 Posts: 3 Joined: Feb 4, 2010 Last seen: Jun 14, 2023
Hi I'am new to openrisc Now, I have finished the OpenRisc CORES on Spartan-3E starter kit adv_jtag_bridge works well ########################################################### danny@ubuntu:~/minsoc/rtl/verilog/adv_debug_sys/Software/adv_jtag_bridge$ sudo adv_jtag_bridge -x2 xpc_usb Found Xilinx Platform Cable USB (DLC9) Found Xilinx Platform Cable USB (DLC9) firmware version = 0x0404 (1028) cable CPLD version = 0x0012 (18) Enumerating JTAG chain... Devices on JTAG chain: Index Name ID Code IR Length ---------------------------------------------------------------- 0: xc2c64a 0x06E5E093 8 1: XCF04S 0xF5046093 8 2: XC3S500E_FG320 0x41C22093 6 Target device 2, JTAG ID = 0x41c22093 Xilinx IDCODE, assuming internal BSCAN mode (using USER1 instead of DEBUG TAP command) IDCODE sanity test passed, chain OK! JSP server listening on host ubuntu (0.0.0.0), port 9944, address family IPv4 JSP server thread running! JTAG bridge ready! ########################################################### but I can't remote my FPGA with GDB It shows timeout all the time what should I do? did I miss anything? if you know the answer tell me please thanks ########################################################### danny@ubuntu:~/minsoc/sw/uart$ or32-elf-gdb uart-nocache.or32 Building automata... done, num uncovered: 0/216. Parsing operands data... done. GNU gdb 6.8 Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <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=i686-pc-linux-gnu --target=or32-elf"... (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... Ignoring packet error, continuing... Malformed response to offset query, timeout (gdb) ########################################################### Hi I'am new to openrisc Now, I have finished the OpenRisc CORES on Spartan-3E starter kit adv_jtag_bridge works well ########################################################### danny@ubuntu:~/minsoc/rtl/verilog/adv_debug_sys/Software/adv_jtag_bridge$ sudo adv_jtag_bridge -x2 xpc_usb Found Xilinx Platform Cable USB (DLC9) Found Xilinx Platform Cable USB (DLC9) firmware version = 0x0404 (1028) cable CPLD version = 0x0012 (18) Enumerating JTAG chain... Devices on JTAG chain: Index Name ID Code IR Length ---------------------------------------------------------------- 0: xc2c64a 0x06E5E093 8 1: XCF04S 0xF5046093 8 2: XC3S500E_FG320 0x41C22093 6 Target device 2, JTAG ID = 0x41c22093 Xilinx IDCODE, assuming internal BSCAN mode (using USER1 instead of DEBUG TAP command) IDCODE sanity test passed, chain OK! JSP server listening on host ubuntu (0.0.0.0), port 9944, address family IPv4 JSP server thread running! JTAG bridge ready! ########################################################### but I can't remote my FPGA with GDB It shows timeout all the time what should I do? did I miss anything? if you know the answer tell me please thanks ########################################################### danny@ubuntu:~/minsoc/sw/uart$ or32-elf-gdb uart-nocache.or32 Building automata... done, num uncovered: 0/216. 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=i686-pc-linux-gnu --target=or32-elf"... (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... Ignoring packet error, continuing... Malformed response to offset query, timeout (gdb) ###########################################################

RE: Unable to download codes with GDB by nyawn on May 29, 2010			nyawn Posts: 173 Joined: Dec 19, 2008 Last seen: May 31, 2023
In adv_jtag_bridge, open rsp-server.c in a text editor and change the GDB_BUF_MAX back to its earlier value of ((NUM_REGS) * 8 + 1). For more info on why, read the recent threads on adv_jtag_bridge and minsoc here, this has been discussed several times. In adv_jtag_bridge, open rsp-server.c in a text editor and change the GDB_BUF_MAX back to its earlier value of ((NUM_REGS) * 8 + 1). For more info on why, read the recent threads on adv_jtag_bridge and minsoc here, this has been discussed several times.

RE: Unable to download codes with GDB by danny7711 on May 30, 2010			danny7711 Posts: 3 Joined: Feb 4, 2010 Last seen: Jun 14, 2023
I have changed GDB_BUF_MAX to ((NUM_REGS) * 8 + 1) and re-Make adv_debug_bridge I got: ################################################################## (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... Ignoring packet error, continuing... Malformed response to offset query, timeout (gdb) ################################################################## and then adv_debug_bridge quits automatically ################################################################## danny@ubuntu:~/minsoc/rtl/verilog/adv_debug_sys/Software/adv_jtag_bridge$ ./adv_jtag_bridge -x2 xpc_usb Found Xilinx Platform Cable USB (DLC9) Found Xilinx Platform Cable USB (DLC9) firmware version = 0x0404 (1028) cable CPLD version = 0x0012 (18) Enumerating JTAG chain... Devices on JTAG chain: Index Name ID Code IR Length ---------------------------------------------------------------- 0: xc2c64a 0x06E5E093 8 1: XCF04S 0xF5046093 8 2: XC3S500E_FG320 0x41C22093 6 Target device 2, JTAG ID = 0x41c22093 Xilinx IDCODE, assuming internal BSCAN mode (using USER1 instead of DEBUG TAP command) IDCODE sanity test passed, chain OK! JSP server listening on host ubuntu (0.0.0.0), port 9944, address family IPv4 JTAG bridge ready! JSP server thread running! Packet received qSupported: 10 chars Putting PacketSize=119 danny@ubuntu:~/minsoc/rtl/verilog/adv_debug_sys/Software/adv_jtag_bridge$ ################################################################## I have changed GDB_BUF_MAX to ((NUM_REGS) * 8 + 1) and re-Make adv_debug_bridge I got: ################################################################## (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... Ignoring packet error, continuing... Malformed response to offset query, timeout (gdb) ################################################################## and then adv_debug_bridge quits automatically ################################################################## danny@ubuntu:~/minsoc/rtl/verilog/adv_debug_sys/Software/adv_jtag_bridge$ ./adv_jtag_bridge -x2 xpc_usb Found Xilinx Platform Cable USB (DLC9) Found Xilinx Platform Cable USB (DLC9) firmware version = 0x0404 (1028) cable CPLD version = 0x0012 (18) Enumerating JTAG chain... Devices on JTAG chain: Index Name ID Code IR Length ---------------------------------------------------------------- 0: xc2c64a 0x06E5E093 8 1: XCF04S 0xF5046093 8 2: XC3S500E_FG320 0x41C22093 6 Target device 2, JTAG ID = 0x41c22093 Xilinx IDCODE, assuming internal BSCAN mode (using USER1 instead of DEBUG TAP command) IDCODE sanity test passed, chain OK! JSP server listening on host ubuntu (0.0.0.0), port 9944, address family IPv4 JTAG bridge ready! JSP server thread running! Packet received qSupported: 10 chars Putting PacketSize=119 danny@ubuntu:~/minsoc/rtl/verilog/adv_debug_sys/Software/adv_jtag_bridge$ ##################################################################

RE: Unable to download codes with GDB by nyawn on May 30, 2010			nyawn Posts: 173 Joined: Dec 19, 2008 Last seen: May 31, 2023
Try disabling the JSP feature in adv_jtag_bridge. The option is in the Makefile. Try disabling the JSP feature in adv_jtag_bridge. The option is in the Makefile.

RE: Unable to download codes with GDB by s0parsaean on May 31, 2010			s0parsaean Posts: 50 Joined: Nov 11, 2009 Last seen: Mar 10, 2012
Help me please, I can't find VHDL code for OpenRisc 1200.... Help me please, I can't find VHDL code for OpenRisc 1200....

RE: Unable to download codes with GDB by rajo on Jun 1, 2010			rajo Posts: 4 Joined: Mar 28, 2010 Last seen: Mar 3, 2013
There is no VHDL source code for OR1200, it is, for now, maintained exclusively as verilog There is no VHDL source code for OR1200, it is, for now, maintained exclusively as verilog

RE: Unable to download codes with GDB by s0parsaean on Jun 1, 2010			s0parsaean Posts: 50 Joined: Nov 11, 2009 Last seen: Mar 10, 2012
what about other openRisc version? what about other openRisc version?

RE: Unable to download codes with GDB by s0parsaean on Jun 1, 2010			s0parsaean Posts: 50 Joined: Nov 11, 2009 Last seen: Mar 10, 2012
what about other openrisc version? is there any vhdl code for them? what about other openrisc version? is there any vhdl code for them?

RE: Unable to download codes with GDB by AhmedHMSoliman on Oct 10, 2010			AhmedHMSoliman Posts: 1 Joined: Dec 9, 2009 Last seen: Oct 23, 2011
I had the exact problem, i tried to increase the timeout limit for GDB. use the following command before any other command in gdb to set the remote timeout at the first place. "set remotetimeout 10" and you can make sure time out was set to 10 seconds by using the following gdb command: "show remotetimeout" after that connect to remote target in the ordinary fashion: "target remote :9999" after that if you see the following message: "Ignoring packet error, continuing..." don't worry, just wait and be very patient since, the xpc_usb (DLC9) cable is very, very ,very slow. (it was reported by GDB at the end of memory load that the transfer rate was only 3 bytes/sec!!!). The problem is that due to high latency in the cable, the response packets are delayed for long periods, what makes GDB thinks after timeout period is finished (default is 2 seconds) that remote target has gone down, and thus GDB exits automatically after several attempts. I had the exact problem, i tried to increase the timeout limit for GDB. use the following command before any other command in gdb to set the remote timeout at the first place. "set remotetimeout 10" and you can make sure time out was set to 10 seconds by using the following gdb command: "show remotetimeout" after that connect to remote target in the ordinary fashion: "target remote :9999" after that if you see the following message: "Ignoring packet error, continuing..." don't worry, just wait and be very patient since, the xpc_usb (DLC9) cable is very, very ,very slow. (it was reported by GDB at the end of memory load that the transfer rate was only 3 bytes/sec!!!). The problem is that due to high latency in the cable, the response packets are delayed for long periods, what makes GDB thinks after timeout period is finished (default is 2 seconds) that remote target has gone down, and thus GDB exits automatically after several attempts.

RE: Unable to download codes with GDB by nyawn on Oct 15, 2010			nyawn Posts: 173 Joined: Dec 19, 2008 Last seen: May 31, 2023
[q]I had the exact problem, i tried to increase the timeout limit for GDB. use the following command before any other command in gdb to set the remote timeout at the first place. "set remotetimeout 10" [/q] That's a great tip, I had no idea you could do that in GDB... I had the exact problem, i tried to increase the timeout limit for GDB. use the following command before any other command in gdb to set the remote timeout at the first place. "set remotetimeout 10" That's a great tip, I had no idea you could do that in GDB...

Problem with gdb by manoj4082 on Mar 18, 2011			manoj4082 Posts: 12 Joined: Dec 9, 2010 Last seen: May 24, 2011
Hi, I am new to opencore, presently I got got stuck at some error, that error occured while sending packet from gdb, it is as shown below manoj@manoj-laptop:~/Desktop/sw/eth$ or32-elf-gdb eth-icdc.or32 Building automata... done, num uncovered: 0/216. Parsing operands data... done. GNU gdb (or32-1.0rc1-built-20110126) 7.2-or32-1.0rc1 Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <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=i686-pc-linux-gnu --target=or32-elf". For bug reporting instructions, please see: <http://www.opencores.org/>... Reading symbols from /home/manoj/Desktop/sw/eth/eth-icdc.or32...done. (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... 0x00000010 in ?? () Ignoring packet error, continuing... Bogus trace status reply from target: timeout (gdb) target remote :9928 Remote debugging using :9928 Ignoring packet error, continuing... warning: unrecognized item "timeout" in "qSupported" response Ignoring packet error, continuing... Ignoring packet error, continuing... Ignoring packet error, continuing... Ignoring packet error, continuing... Ignoring packet error, continuing... Malformed response to offset query, timeout This is the error. As shown above I used the commands like set remotetimeout 10 etc which was suggested in the forum for the same error, but even after using it I am getting the same error, so can any one please suggest me the possible solution as early as possible. I am using OR1200V1. Thanks in advance. Hi, I am new to opencore, presently I got got stuck at some error, that error occured while sending packet from gdb, it is as shown below manoj@manoj-laptop:~/Desktop/sw/eth$ or32-elf-gdb eth-icdc.or32 Building automata... done, num uncovered: 0/216. Parsing operands data... done. GNU gdb (or32-1.0rc1-built-20110126) 7.2-or32-1.0rc1 Copyright (C) 2010 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=i686-pc-linux-gnu --target=or32-elf". For bug reporting instructions, please see: ..." target="_blank">http://www.opencores.org/>... Reading symbols from /home/manoj/Desktop/sw/eth/eth-icdc.or32...done. (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... 0x00000010 in ?? () Ignoring packet error, continuing... Bogus trace status reply from target: timeout (gdb) target remote :9928 Remote debugging using :9928 Ignoring packet error, continuing... warning: unrecognized item "timeout" in "qSupported" response Ignoring packet error, continuing... Ignoring packet error, continuing... Ignoring packet error, continuing... Ignoring packet error, continuing... Ignoring packet error, continuing... Malformed response to offset query, timeout This is the error. As shown above I used the commands like set remotetimeout 10 etc which was suggested in the forum for the same error, but even after using it I am getting the same error, so can any one please suggest me the possible solution as early as possible. I am using OR1200V1. Thanks in advance.

Problem with gdb by manoj4082 on Mar 18, 2011			manoj4082 Posts: 12 Joined: Dec 9, 2010 Last seen: May 24, 2011
Hi, I am new to opencore, presently I got got stuck at some error, that error occured while sending packet from gdb, it is as shown below manoj@manoj-laptop:~/Desktop/sw/eth$ or32-elf-gdb eth-icdc.or32 Building automata... done, num uncovered: 0/216. Parsing operands data... done. GNU gdb (or32-1.0rc1-built-20110126) 7.2-or32-1.0rc1 Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <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=i686-pc-linux-gnu --target=or32-elf". For bug reporting instructions, please see: <http://www.opencores.org/>... Reading symbols from /home/manoj/Desktop/sw/eth/eth-icdc.or32...done. (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... 0x00000010 in ?? () Ignoring packet error, continuing... Bogus trace status reply from target: timeout (gdb) target remote :9928 Remote debugging using :9928 Ignoring packet error, continuing... warning: unrecognized item "timeout" in "qSupported" response Ignoring packet error, continuing... Ignoring packet error, continuing... Ignoring packet error, continuing... Ignoring packet error, continuing... Ignoring packet error, continuing... Malformed response to offset query, timeout This is the error. As shown above I used the commands like set remotetimeout 10 etc which was suggested in the forum for the same error, but even after using it I am getting the same error, so can any one please suggest me the possible solution as early as possible. I am using OR1200V1. Thanks in advance. Hi, I am new to opencore, presently I got got stuck at some error, that error occured while sending packet from gdb, it is as shown below manoj@manoj-laptop:~/Desktop/sw/eth$ or32-elf-gdb eth-icdc.or32 Building automata... done, num uncovered: 0/216. Parsing operands data... done. GNU gdb (or32-1.0rc1-built-20110126) 7.2-or32-1.0rc1 Copyright (C) 2010 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=i686-pc-linux-gnu --target=or32-elf". For bug reporting instructions, please see: ..." target="_blank">http://www.opencores.org/>... Reading symbols from /home/manoj/Desktop/sw/eth/eth-icdc.or32...done. (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... 0x00000010 in ?? () Ignoring packet error, continuing... Bogus trace status reply from target: timeout (gdb) target remote :9928 Remote debugging using :9928 Ignoring packet error, continuing... warning: unrecognized item "timeout" in "qSupported" response Ignoring packet error, continuing... Ignoring packet error, continuing... Ignoring packet error, continuing... Ignoring packet error, continuing... Ignoring packet error, continuing... Malformed response to offset query, timeout This is the error. As shown above I used the commands like set remotetimeout 10 etc which was suggested in the forum for the same error, but even after using it I am getting the same error, so can any one please suggest me the possible solution as early as possible. I am using OR1200V1. Thanks in advance.

RE: Unable to download codes with GDB by jeremybennett on Mar 18, 2011			jeremybennett Posts: 815 Joined: May 29, 2008 Last seen: Jun 13, 2019
<p> Hi manoj4082 </p> <p> How did you set up your remote target. Looks like it is barfing on some of the packets. GDB 7.2 has some new packet types, so if you are using an older target Remote Serial Protocol Server it may be getting confused. </p> <p> HTH </p> <p> Jeremy </p> Hi manoj4082 How did you set up your remote target. Looks like it is barfing on some of the packets. GDB 7.2 has some new packet types, so if you are using an older target Remote Serial Protocol Server it may be getting confused. HTH Jeremy

RE: Unable to download codes with GDB by nyawn on Mar 19, 2011			nyawn Posts: 173 Joined: Dec 19, 2008 Last seen: May 31, 2023
[q] (gdb) target remote :9999 Remote debugging using :9999 Ignoring packet error, continuing... 0x00000010 in ?? () Ignoring packet error, continuing... Bogus trace status reply from target: timeout [...] (gdb) target remote :9928 Remote debugging using :9928 [/q] I'm still in the process of updating adv_jtag_bridge's RSP server for GDB 7.2. I thought I'd handled all the new messages that GDB sent, but I may have missed one. It's also possible the 'timeout' wasn't actually a response from adv_jtag_bridge, just GDB timing out on its own. Really, if you intend to do any real debugging, you should use GDB 6.8 - there are issues with 7.2 on bare metal. I also see you try port 9928. Assuming you are using the defaults in adv_jtag_bridge, this is NOT an RSP server, and GDB will NOT work if connected to this port. Port 9928 is the HWP server, which is used by AdvancedWatchpointControl (a java program that comes with the advanced debug system) to control the watchpoint hardware. I'm guessing at it's core, this is the same speed issue that's dogged the DLC9 since I first released the driver. Complain to Xilinx for not releasing the API... (gdb) target remote :9999 Remote debugging using :9999 Ignoring packet error, continuing... 0x00000010 in ?? () Ignoring packet error, continuing... Bogus trace status reply from target: timeout [...] (gdb) target remote :9928 Remote debugging using :9928 I'm still in the process of updating adv_jtag_bridge's RSP server for GDB 7.2. I thought I'd handled all the new messages that GDB sent, but I may have missed one. It's also possible the 'timeout' wasn't actually a response from adv_jtag_bridge, just GDB timing out on its own. Really, if you intend to do any real debugging, you should use GDB 6.8 - there are issues with 7.2 on bare metal. I also see you try port 9928. Assuming you are using the defaults in adv_jtag_bridge, this is NOT an RSP server, and GDB will NOT work if connected to this port. Port 9928 is the HWP server, which is used by AdvancedWatchpointControl (a java program that comes with the advanced debug system) to control the watchpoint hardware. I'm guessing at it's core, this is the same speed issue that's dogged the DLC9 since I first released the driver. Complain to Xilinx for not releasing the API...

Unable to download codes with GDB by manoj4082 on Apr 2, 2011			manoj4082 Posts: 12 Joined: Dec 9, 2010 Last seen: May 24, 2011
Hi, As you suggested my problem got resolved after using gdb-6.8, but presently I got stuck at other error while using gdb-6.8, and the error is as shown below. manoj@manoj-laptop:~/Desktop/sw/eth$ gdb eth-icdc.or32 GNU gdb 6.8 Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <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 "i686-pc-linux-gnu"... (gdb) set remotetimeout 10 (gdb) target remote :9999 Remote debugging using :9999 eth_receive () at eth.c:16 16 { (gdb) set remotetimeout 10 (gdb) load Loading section .reset, size 0x190 lma 0x0 Loading section .vectors, size 0xe1c lma 0x200 Loading section .text, size 0x11b8 lma 0x1200 Loading section .rodata, size 0x26 lma 0x23b8 Start address 0x1200, load size 8586 Remote failure reply: E01 - The above thing is the error seen in gdb and the output seen at advance JTAG bridge terminal is as shown below:- Packet received X0,100:: 263 chars Putting OK Packet received X100,90:: 152 chars Putting OK Packet received X200,100:: 265 chars Putting OK Packet received X300,100:: 265 chars Putting OK Packet received X400,100:: 265 chars Putting OK Packet received X500,100:: 265 chars Putting OK Packet received X600,100:: 265 chars Putting OK Packet received X700,100:: 265 chars Putting OK Packet received X800,100:: 265 chars Putting OK Packet received X900,100:: 265 chars Putting OK Packet received Xa00,100:: 265 chars Putting OK Packet received Xb00,100:: 265 chars Putting OK Packet received Xc00,100:: 266 chars Putting OK Packet received Xd00,100:: 265 chars Putting OK Packet received Xe00,100:: 265 chars Putting OK Packet received Xf00,100:: 267 chars Putting OK Packet received X1000,1c:ï¿½ï¿½: 38 chars Putting OK Packet received X1200,100:ï¿½!ï¿½ï¿½ï¿½ï¿½A: 273 chars Putting OK Packet received X1300,100:ï¿½: 272 chars Putting OK Packet received X1400,100:ï¿½``: 266 chars Putting OK Packet received X1500,100:ï¿½ï¿½: 268 chars Putting OK Packet received X1600,100:ï¿½A: 269 chars Putting OK Packet received X1700,100:ï¿½d: 267 chars Putting OK Packet received X1800,100:ï¿½ï¿½: 269 chars Putting OK Packet received X1900,100:ï¿½c: 266 chars Putting OK Packet received X1a00,100:: 266 chars Putting OK Packet received X1b00,100:ï¿½ï¿½A: 269 chars Putting OK Packet received X1c00,100:ï¿½bï¿½ï¿½ï¿½dï¿½c: 267 chars Putting OK Packet received X1d00,100:ï¿½c: 270 chars Putting OK Packet received X1e00,100:D: 266 chars Putting OK Packet received X1f00,100:ï¿½c+ ï¿½ï¿½ï¿½ï¿½ï¿½ `: 271 chars Putting OK Packet received X2000,100:: 267 chars Putting OK Packet received X2100,100:ï¿½ : 267 chars Putting OK Packet received X2200,100:ï¿½A: 269 chars Putting OK Packet received X2300,b8:ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½(ï¿½`P: 196 chars Putting OK Packet received X23b8,26:Length: : 47 chars Putting OK Packet received P8=00001200: 11 chars Putting OK Packet received P29=ffffffff: 12 chars Warning: Attempt to write unknown register 0x29: ignored Putting E01 Is this error due to writing data into unknown register 0x29. Can any one please help me in rectifying this error, as soon as possible. Thanks in advance. Hi, As you suggested my problem got resolved after using gdb-6.8, but presently I got stuck at other error while using gdb-6.8, and the error is as shown below. manoj@manoj-laptop:~/Desktop/sw/eth$ gdb eth-icdc.or32 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 "i686-pc-linux-gnu"... (gdb) set remotetimeout 10 (gdb) target remote :9999 Remote debugging using :9999 eth_receive () at eth.c:16 16 { (gdb) set remotetimeout 10 (gdb) load Loading section .reset, size 0x190 lma 0x0 Loading section .vectors, size 0xe1c lma 0x200 Loading section .text, size 0x11b8 lma 0x1200 Loading section .rodata, size 0x26 lma 0x23b8 Start address 0x1200, load size 8586 Remote failure reply: E01 - The above thing is the error seen in gdb and the output seen at advance JTAG bridge terminal is as shown below:- Packet received X0,100:: 263 chars Putting OK Packet received X100,90:: 152 chars Putting OK Packet received X200,100:: 265 chars Putting OK Packet received X300,100:: 265 chars Putting OK Packet received X400,100:: 265 chars Putting OK Packet received X500,100:: 265 chars Putting OK Packet received X600,100:: 265 chars Putting OK Packet received X700,100:: 265 chars Putting OK Packet received X800,100:: 265 chars Putting OK Packet received X900,100:: 265 chars Putting OK Packet received Xa00,100:: 265 chars Putting OK Packet received Xb00,100:: 265 chars Putting OK Packet received Xc00,100:: 266 chars Putting OK Packet received Xd00,100:: 265 chars Putting OK Packet received Xe00,100:: 265 chars Putting OK Packet received Xf00,100:: 267 chars Putting OK Packet received X1000,1c:ï¿½ï¿½: 38 chars Putting OK Packet received X1200,100:ï¿½!ï¿½ï¿½ï¿½ï¿½A: 273 chars Putting OK Packet received X1300,100:ï¿½: 272 chars Putting OK Packet received X1400,100:ï¿½``: 266 chars Putting OK Packet received X1500,100:ï¿½ï¿½: 268 chars Putting OK Packet received X1600,100:ï¿½A: 269 chars Putting OK Packet received X1700,100:ï¿½d: 267 chars Putting OK Packet received X1800,100:ï¿½ï¿½: 269 chars Putting OK Packet received X1900,100:ï¿½c: 266 chars Putting OK Packet received X1a00,100:: 266 chars Putting OK Packet received X1b00,100:ï¿½ï¿½A: 269 chars Putting OK Packet received X1c00,100:ï¿½bï¿½ï¿½ï¿½dï¿½c: 267 chars Putting OK Packet received X1d00,100:ï¿½c: 270 chars Putting OK Packet received X1e00,100:D: 266 chars Putting OK Packet received X1f00,100:ï¿½c+ ï¿½ï¿½ï¿½ï¿½ï¿½ `: 271 chars Putting OK Packet received X2000,100:: 267 chars Putting OK Packet received X2100,100:ï¿½ : 267 chars Putting OK Packet received X2200,100:ï¿½A: 269 chars Putting OK Packet received X2300,b8:ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½(ï¿½`P: 196 chars Putting OK Packet received X23b8,26:Length: : 47 chars Putting OK Packet received P8=00001200: 11 chars Putting OK Packet received P29=ffffffff: 12 chars Warning: Attempt to write unknown register 0x29: ignored Putting E01 Is this error due to writing data into unknown register 0x29. Can any one please help me in rectifying this error, as soon as possible. Thanks in advance.

no use

no use

1/3

Next

Last

© copyright 1999-2024 OpenCores.org, equivalent to Oliscience, all rights reserved. OpenCores®, registered trademark.