We were using Metaware debugger with Digilent JTAG-HS2 cable HS2 RevA for JTAG connection. When 7 processors are in chain, first processor in the chain is not able to read back the memory into Metaware GUI. We notice that write/read is happening correctly in the design by chipscope debugger. We tried many other processor chain combinations and were able to get the metaware working with 8/9/10/11 processors but not 7 processor chain. Currently we have many such digilent HS2 RevA cables purchased online (Sandisk India Design Centre, Bangalore) and all of them facing the same issue. We have installed the new Adept driver digilent.adept.system_v2.16.4 and still the issue exist. We are suspecting hardware issue in the cable. Let me know if someone from Digilent support could have done a fix?
Question
Kailas Senan
Hi,
We were using Metaware debugger with Digilent JTAG-HS2 cable HS2 RevA for JTAG connection. When 7 processors are in chain, first processor in the chain is not able to read back the memory into Metaware GUI. We notice that write/read is happening correctly in the design by chipscope debugger. We tried many other processor chain combinations and were able to get the metaware working with 8/9/10/11 processors but not 7 processor chain. Currently we have many such digilent HS2 RevA cables purchased online (Sandisk India Design Centre, Bangalore) and all of them facing the same issue. We have installed the new Adept driver digilent.adept.system_v2.16.4 and still the issue exist. We are suspecting hardware issue in the cable. Let me know if someone from Digilent support could have done a fix?
Link to comment
Share on other sites
1 answer to this question
Recommended Posts
Archived
This topic is now archived and is closed to further replies.