1/1 
|
adv_jtag_bridge setup problem
by zhongyang on Nov 18, 2011 |
zhongyang
Posts: 21 Joined: Dec 24, 2010 Last seen: May 9, 2012 |
||
|
Hi all,
I am new to this project and I encountered with a problem when I tried to use adv_jtag_bridge to connect my FPGA board. I have adjusted the source files of minsoc for my board xinlinx xc2vp30_ff896. After I download the bitstream, I operated with commands and I get below: adv_jtag_bridge xpc_usb Fould Xilinx Platform Cable USB (DLC9) Fould Xilinx Platform Cable USB (DLC9) firmware version = 0x044C (1100) Cable CPLD version = 0x0012 (18) Enumerating JTAG chain... Then, there is nothing until I have to stop it with ctrl+c. I just change the options to Virtex2 in the source files. And use "make" and "make install" to install the adv_jtag_bridge. Where I am wrong, in hardware or software? Help me. Thanks. |
|||
|
RE: adv_jtag_bridge setup problem
by nyawn on Nov 23, 2011 |
nyawn
Posts: 173 Joined: Dec 19, 2008 Last seen: May 31, 2023 |
||
|
That's a very unusual place for adv_jtag_bridge to stop. The JTAG cable is clearly connected to your workstation, and adv_jtag_bridge is communicating with the cable (it's read the cable's firmware version). At this point, adv_jtag_bridge is trying to enumerate the JTAG chain. Even if your FPGA setup is completely wrong, this won't need to read more than ~1000 bits, which should be done in a matter of seconds, maybe 30 seconds at the outside most (5 seconds is more likely).
First, how long did you wait before killing adv_jtag_bridge? You might try giving it several minutes, just in case something in the configuration of your workstation is slowing things down. Second, are you running adv_jtag_bridge in a VM? I have heard that other users sometimes have problems with USB cables from inside a VM. |
|||
|
RE: adv_jtag_bridge setup problem
by zhongyang on Nov 23, 2011 |
zhongyang
Posts: 21 Joined: Dec 24, 2010 Last seen: May 9, 2012 |
||
|
Yes, I am doing it inside a VM. Now, I try to configure the FPGA from PROM on the board and I can do a self-test but with some errors when doing cpu writings. I found the anwser on the forum and I decided to ignore it.
After setting up the adv_jtag_bridge and seeing "jtag bridge ready", in another terminal I use or32-elf-gdb to start debuging, it says my or32-elf-gdb is version 6.8. (gdb)set remotetimeout 10 (gdb)target remote:9999 ignore packet error ... warning: unrecognized item "timeout" in "qSupported" response warning: Invalid remote reply: PacketSize=119 Malformed packet(a) (missing clon): t=0;Data=0;Bss=0 Packet: 'Text=0;Data=0;Bss=0' (gdb)load You can't do that when your target is 'exec' in jtag terminal I got: Packet received qSupported: 10 chars Putting PacketSize=119 ... Putting PacketSize=119 Packet received ?: 1 chars Putting S00 ... Putting S00 Packet received Hc-1: 4 chars Putting OK Packet received qC: 2 chars Putting Packet received qOffsets: 8 chars Putting Text=0;Data=0;Bss=0 I think the problem is the speed between gdb and jtag(DLC9), how could I solve the problem. Should I change a new real jtag like xp3 ? |
|||
|
RE: adv_jtag_bridge setup problem
by zhongyang on Nov 23, 2011 |
zhongyang
Posts: 21 Joined: Dec 24, 2010 Last seen: May 9, 2012 |
||
|
That's a very unusual place for adv_jtag_bridge to stop. The JTAG cable is clearly connected to your workstation, and adv_jtag_bridge is communicating with the cable (it's read the cable's firmware version). At this point, adv_jtag_bridge is trying to enumerate the JTAG chain. Even if your FPGA setup is completely wrong, this won't need to read more than ~1000 bits, which should be done in a matter of seconds, maybe 30 seconds at the outside most (5 seconds is more likely).
First, how long did you wait before killing adv_jtag_bridge? You might try giving it several minutes, just in case something in the configuration of your workstation is slowing things down. Second, are you running adv_jtag_bridge in a VM? I have heard that other users sometimes have problems with USB cables from inside a VM. Yes, I am doing it inside a VM. Now, I try to configure the FPGA from PROM on the board and I can do a self-test but with some errors when doing cpu writings. I found the anwser on the forum and I decided to ignore it. After setting up the adv_jtag_bridge and seeing "jtag bridge ready", in another terminal I use or32-elf-gdb to start debuging, it says my or32-elf-gdb is version 6.8. (gdb)set remotetimeout 10 (gdb)target remote:9999 ignore packet error ... warning: unrecognized item "timeout" in "qSupported" response warning: Invalid remote reply: PacketSize=119 Malformed packet(a) (missing clon): t=0;Data=0;Bss=0 Packet: 'Text=0;Data=0;Bss=0' (gdb)load You can't do that when your target is 'exec' in jtag terminal I got: Packet received qSupported: 10 chars Putting PacketSize=119 ... Putting PacketSize=119 Packet received ?: 1 chars Putting S00 ... Putting S00 Packet received Hc-1: 4 chars Putting OK Packet received qC: 2 chars Putting Packet received qOffsets: 8 chars Putting Text=0;Data=0;Bss=0 I think the problem is the speed between gdb and jtag(DLC9), how could I solve the problem. Should I change a new real jtag like xp3 ? |
|||
|
RE: adv_jtag_bridge setup problem
by nyawn on Nov 24, 2011 |
nyawn
Posts: 173 Joined: Dec 19, 2008 Last seen: May 31, 2023 |
||
|
A different JTAG cable (XPC3 or anything else) will make no difference to this particular problem. It looks like GDB is misunderstanding the packet that adv_jtag_bridge is sending it. This is strange, since I don't think the format of that GDB query (qOffsets) has changed. You might try a different version of GDB, maybe 7.1 or 7.2.
|
|||
1/1