![]() ![]() Spartan 3E starter kit)" IMO should be changed to "Xilinx Platform Cable USB II (DLC10), or Xilinx Platform Cable USB (DLC9G), or on-board programmer (e.g. To clarify in case it got lost in the long discussion: This feature request is about Where "Xilinx Platform Cable USB II (DLC10), or on-board programmer (e.g. With the patch applied, I can disconnect and reconnect JTAG in between invokations of xc3sprog, never having to disconnect and reconnect USB. While I don't have any reason to assume my platform cable DLC9G is not original (I bought it from Digi-Key more than 10 years ago), I tried this patch, and it fixes for me. jed file to the device, I still see the problem on the next invokation of xc3prog. The patch does not fully fix the issue for me: With the patch applied, I can indeed invoke xc3sprog -c xpc -v as often as I want without running into the bug. Best head start would be a patch request for XC3Sprog with some updated Readme.DLC10. I will have a look at it if you give me a head start how to get my DLC10 working under linux again without downloading impact/vivado whatever. ![]() However, I also see an error in /var/log/daemon.log (apparently the rule is executed once with empty $tempnode): Dec 14 08:04:41 notebook5. Also, I had to install ISE 14.7 anyway for synthesis (the XC9536XL is not yet supported by free synthesis tools). I do not know about any free firmware alternative. My /etc/udev/rules.d/les rules look like: But that uses firmware files that came with Xilinx ISE 14.7. Still, this seems unrelated to the bug reported here. I've attached my new /etc/udev/rules.d/les. I've changed my /etc/udev/rules.d/les, and now see only one execution, for the device. Apparently, the rule was executed for the device first, then again for the interface, resulting inthe error message on the execution for the interface. xc3sprog -c xpc XC3SPROG (c) 2004-2011 xc3sprog project $Rev: 795 $ OS: Linux Free software: If you contribute nothing, expect nothing! Feedback on success/failure/enhancement requests: Check Sourceforge for updates: No JTAG Chain. įor information, the output is a bit different when no device is attached to JTAG, but xc3sprog still fails on the second invokation. ![]() xc3sprog -c xpc XC3SPROG (c) 2004-2011 xc3sprog project $Rev: 795 $ OS: Linux Free software: If you contribute nothing, expect nothing! Feedback on success/failure/enhancement requests: Check Sourceforge for updates. ![]() Is there any fix or workaround for the issue?įor information, the output is a bit different when no device is attached to JTAG, but xc3sprog still fails on the second invokation, then the timeout comes on the third. I have to unplug / replug after every programming action or xc3sprog fails with above mentioned USB error. I'm experiencing the same issue with my Xilinx adapter. "Erase still running 00 "when programming XC95144XL ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |