Activity for xc3sprog
-
Uwe Bonnes posted a comment on ticket #16
Hello, "Nagore" == Nagore Pinillos napiza@users.sourceforge.net writes: Nagore> Thanks a lot for your suggestions Uwe. Have read about Nagore> this software and gonna give it an opportunity. But after Nagore> installing everything, I am afraid that it does not Nagore> support xc3s700, do you know smt about this? Thanks in Nagore> advance For SRAM programming, try to simply add the JTAG IDs from xc3sprog to openFpgaloader src/part.hpp. For flash programming, add your part in spiOverJtag/build.py and...
-
Nagore Pinillos posted a comment on ticket #16
Thanks a lot for your suggestions Uwe. Have read about this software and gonna give it an opportunity. But after installing everything, I am afraid that it does not support xc3s700, do you know smt about this? Thanks in advance Nagore
-
Hello, please have a look at openFpgaLoader github.com:trabucayre/openFPGALoader.git It seem to implement MCS parsing and is mantained. I also use openFPGALoader instead of xc3sprog now. Cheers "Nagore" == Nagore Pinillos napiza@users.sourceforge.net writes: Nagore> --- Nagore> **[support-requests:#16] MCS file programming error with Nagore> xc3sprog** Nagore> **Status:** open **Group:** v1.0_(example) **Created:** Nagore> Thu Jul 18, 2024 03:35 PM UTC by Nagore Pinillos **Last Nagore> Updated:**...
-
MCS file programming error with xc3sprog
-
don.yang created ticket #15
build error
-
Tonny Roger Holm created ticket #14
"Erase still running 00 "when programming XC95144XL
-
AnshumanTech created ticket #13
XC3S50AN new lot ICs not programming
-
XC3S50AN not programming
-
Steven Hirsch posted a comment on ticket #20
I'm experiencing the same issue with my Xilinx adapter. I have to unplug / replug after every programming action or xc3sprog fails with above mentioned USB error. Is there any fix or workaround for the issue?
-
Jan Van Winkel created ticket #33
Xilinx XC7Z007S device id support
-
Philipp Klaus Krause modified a comment on ticket #20
For 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: philipp@notebook5:/tmp/xc3sprog-code/build$ ./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: http://sourceforge.net/mail/?group_id=170565 Check Sourceforge for updates: http://sourceforge.net/projects/xc3sprog/develop...
-
For information, the output is a bit different when no device is attached to JTAG, but xc3sprog still fails on the second invokation: philipp@notebook5:/tmp/xc3sprog-code/build$ ./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: http://sourceforge.net/mail/?group_id=170565 Check Sourceforge for updates: http://sourceforge.net/projects/xc3sprog/develop No JTAG Chain...
-
I think I've solved the udev issue. Apparently, the rule was executed for the device first, then again for the interface, resulting inthe error message on the execution for the interface. I've changed my /etc/udev/rules.d/xusbdfwu.rules, and now see only one execution, for the device. I've attached my new /etc/udev/rules.d/xusbdfwu.rules. Still, this seems unrelated to the bug reported here.
-
My /etc/udev/rules.d/xusbdfwu.rules rules look like: https://github.com/timvideos/litex-buildenv/wiki/Xilinx-Platform-Cable-USB-under-Linux But that uses firmware files that came with Xilinx ISE 14.7. I do not know about any free firmware alternative. Also, I had to install ISE 14.7 anyway for synthesis (the XC9536XL is not yet supported by free synthesis tools). 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...
-
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. Best head start would be a patch request for XC3Sprog with some updated Readme.DLC10.
-
Unfortunately, I wrote too soon. 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. But if I actually write a .jed file to the device, I still see the problem on the next invokation of xc3prog.
-
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 https://sourceforge.net/p/xc3sprog/bugs/20/ for me. With the patch applied, I can disconnect and reconnect JTAG in between invokations of xc3sprog, never having to disconnect and reconnect USB.
-
Hardware recommendation
-
To clarify in case it got lost in the long discussion: This feature request is about http://xc3sprog.sourceforge.net/hardware.php Where "Xilinx Platform Cable USB II (DLC10), or on-board programmer (e.g. 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. Spartan 3E starter kit)" so users of the DLC9G know that xpc is the label they need to use.
-
I see the same problem (using a platform cable USB DLC9G - which cable are you using?): philipp@notebook5:~$ xc3sprog -c xpc XC3SPROG (c) 2004-2011 xc3sprog project $Rev$ OS: Linux Free software: If you contribute nothing, expect nothing! Feedback on success/failure/enhancement requests: http://sourceforge.net/mail/?group_id=170565 Check Sourceforge for updates: http://sourceforge.net/projects/xc3sprog/develop JTAG loc.: 0 IDCODE: 0x59602093 Desc: XC9536XL Rev: E IR length: 8 philipp@notebook5:~$...
-
I see someone else has the same problem (cable work on first use after plugging in only): https://sourceforge.net/p/xc3sprog/bugs/20/
-
I see the same problem (using a platform cable USB DLC9G): philipp@notebook5:~$ xc3sprog -c xpc XC3SPROG (c) 2004-2011 xc3sprog project $Rev$ OS: Linux Free software: If you contribute nothing, expect nothing! Feedback on success/failure/enhancement requests: http://sourceforge.net/mail/?group_id=170565 Check Sourceforge for updates: http://sourceforge.net/projects/xc3sprog/develop JTAG loc.: 0 IDCODE: 0x59602093 Desc: XC9536XL Rev: E IR length: 8 philipp@notebook5:~$ xc3sprog -c xpc XC3SPROG (c)...
-
Siddharth Sinha created ticket #24
Spartan-6 with FTDI FT232H JTAG programmer on Ubuntu 18.04
-
Duc Dang created ticket #10
Flash device not in supporting device ID list
-
Uwe Bonnes posted a comment on ticket #9
Hello, your chip is a simple FTDI chip without the MPSSE engine, to my knowledge. xc3sprog needs MPSSE. Look at cablelist.txt for supported chips and VID/PID combos. In prinziple , the bitbang machine could also do JTAG, at probably must lower speed. This needs to be implemented. Feel free to contribute an implementation.
-
Alexey Vysochin created ticket #9
Could not open FTDI device (using libftdi)
-
xc3sprog: Redo change from 793, accidently removed in 794.
-
progalgspiflash: Add another N25Q device.
-
raydem modified a comment on ticket #8
Hello, you were right, it was problem of the cable. the xc3sprog programmed the PROM and verified fine, but the PROM has not correctly function with this programmation.
-
Hello, Sorry for the delay. I put a scope in the TDO and TDI lines and verify fine but really it is not programmed good. I leave you a picture of the TDO and TDI lines, the data is OK. C:\jtag>xc3sprog -c ft232h -v -p 1 s116.mcs:w::MCS XC3SPROG (c) 2004-2011 xc3sprog project $Rev$ OS: Windows Free software: If you contribute nothing, expect nothing! Feedback on success/failure/enhancement requests: http://sourceforge.net/mail/?group_id=170565 Check Sourceforge for updates: http://sourceforge.net/projects/xc3sprog/develop...
-
Thanks for the test. Now I am quite sure it is a signal integrity problem. How to proceed? Perhaps look with a scope for the JTAG signal forms and look for pecularities. Or look with a logic analyzer able to analyze JTAG and record a trace. Scan the trace and look if xc3sprog sends a wrong stimulus. Or if your devices answers wrong to a correct stimulus. Has some of the JTAG lines long or many stubs? Does the problem happen on other boards? Suprious problems are hard to debug...
-
Hello Uwe, I tried with linux box and result is the same.
-
Stronger output drive, higher slew or changed timing rates may trigger signal integrity errors. But test on a linux box to exclude libusb-win32 errors.
-
I program the memory with the JTAG digilent cable and the memory was programmed fine. So, I do not think the problem is the signal integrity. I use windows, how I can check the error ?
-
I stringly expect a signal integrity error. Check for stubs, bad solder junctions etc. There is a small chance that this is a libusb-win32 error, Check on a linux box if the error persists.
-
Sorry, with the command -T this is the result. I changed the driver for the jtag and I use libusb-win32. C:\jtag>xc3sprog -c ft232h -T100 XC3SPROG (c) 2004-2011 xc3sprog project $Rev$ OS: Windows Free software: If you contribute nothing, expect nothing! Feedback on success/failure/enhancement requests: http://sourceforge.net/mail/?group_id=170565 Check Sourceforge for updates: http://sourceforge.net/projects/xc3sprog/develop Using Libftdi, Reading ID_CODE 100 times Sending 14 bits IDCODE Commands:...
-
Sorry, with the command -T this is the result. I change the driver for the jtag and use libusb-win32. C:\jtag>xc3sprog -c ft232h -T100 XC3SPROG (c) 2004-2011 xc3sprog project $Rev$ OS: Windows Free software: If you contribute nothing, expect nothing! Feedback on success/failure/enhancement requests: http://sourceforge.net/mail/?group_id=170565 Check Sourceforge for updates: http://sourceforge.net/projects/xc3sprog/develop Using Libftdi, Reading ID_CODE 100 times Sending 14 bits IDCODE Commands: 0xfe09...
-
Hello UweBonnes, Not, the error is different but always is in verify block. About the signal integrity, it is ok. All the signals are going through PCB. Thank you
-
Sorry, with the command -T this is the result C:\jtag>xc3sprog -c ft232h -T100 XC3SPROG (c) 2004-2011 xc3sprog project $Rev$ OS: Windows Free software: If you contribute nothing, expect nothing! Feedback on success/failure/enhancement requests: http://sourceforge.net/mail/?group_id=170565 Check Sourceforge for updates: http://sourceforge.net/projects/xc3sprog/develop Using Libftdi, Reading ID_CODE 100 times Sending 14 bits IDCODE Commands: 0xfe09 Expecting 2 IDCODES : 0xd5045093 0x11c1a093 JTAG loc.:...
-
C:\jtag>xc3sprog -c ft232h -v -p 1 s116.mcs:w::MCS XC3SPROG (c) 2004-2011 xc3sprog project $Rev$ OS: Windows Free software: If you contribute nothing, expect nothing! Feedback on success/failure/enhancement requests: http://sourceforge.net/mail/?group_id=170565 Check Sourceforge for updates: http://sourceforge.net/projects/xc3sprog/develop Using built-in device list Using built-in cable list Cable ft232h type ftdi VID 0x0403 PID 0x6014 dbus data 00 enable 0b cbus data 00 data 00 Using Libftdi, Using...
-
If xc3sprog -T0 shows errors, you have signal integrity problems.
-
Hello UweBonnes, Not, the error is different but always is in verify block. About the signal integrity, it is ok. All the signals are going through PCB. With xc3sprog -T0 the result is mismatch. Thank you
-
This looks like a signal integrity issue or a issue with the XCF. For XCF problems: Do multiple verify run show the same error? Does readback show some problem For signal integity: .Do you use flying wires? Are ground wires short and plenty? Does "xc3sprog -T0 ..." run "forever?
-
xcf02s
-
Hello, xc3sprog is in maintainance mode from my side. If you provide a patch, I will check and probably apply. Otherwise I have no current usage of xc3sprog and so I will not add features myself. Perhaps look at what openocd does to set the location. Try something similar in xc3sprog. If you have specific problems, ask and I will try to help.
-
cioma created ticket #5
Specify adapter by physical USB port
-
Return proper error when verify XCF fails.
-
Adrien Prost-Boucle posted a comment on ticket #23
Thanks, programming speed is 30MHz again. The bug is solved for me. I have no knowledge about libftdti libraries, I'm just using the user package for Archlinux distribution. https://aur.archlinux.org/packages/xc3sprog-svn Just for information, the dependencies are with these packages: libusb libusb-compat libftdi libftdi-compat libftd2xx Then compilation is cmake + make with no special options, just install in /usr. Going further I see that there is a new package libftd3xx, for USB3.0 chip FT60x,...
-
xc3sprog released /xc3sprog_792.git.tar.bz
-
Compiling against libftdi1 makes things easier, as few, if any libftdi packages are provided. I clean up the cmake build system some more and now us package provided ways to find the required files. Can you test if rev-792 still has the problem? And if tthe problem persists, perhaps dig yourself in the problem?
-
win32: Allow crossbuild against recent i686-w64-mingw32
-
ioparport: Compile against recent mingw.
-
Remove trailing whitespace and DOS line endings
-
ioxpc: Initialize like urjtag.
-
-
-
Speed regression with FTDI introduced in r784
-
Rachit Ajitsaria created ticket #22
Unable to program Kintex 7 (XC7K160T)
-
Mike Thomson posted a comment on ticket #31
Oh, by the way, the only difference I can see between me and the original post is...
-
Devicelist mean decode the JTAG list. But not implement the flash algo. I don't use...
-
Daniel Mothes posted a comment on ticket #21
That would be nice, because in the Devicelist it already stands as a supported device....
-
A, I never Had a ATMEAGA644, so it is not supported. Probably no big deal to add...
-
wow that was fast responce... ok i try this: javr -c FT2232H -v -p 1 ATMEGATEST.hex...
-
Use "javr" for programming AVR.
-
Flashing ATMEGA644p at JTAG Position 1
-
Trond Egil Gran posted a comment on ticket #31
No, that did not help. I could try on another computer when I have the time, maybe...
-
"Trond" == Trond Egil Gran trondegilgran@users.sf.net writes: Trond> So yes it seems...
-
Hi I tested with urjtag and I it does not have the same problem. The reason I added...
-
"Trond" == Trond Egil Gran trondegilgran@users.sf.net writes: ... Trond> I have a...
-
"Trond" == Trond Egil Gran trondegilgran@users.sf.net writes: ... Trond> - Trond>...
-
progalgspiflash: Handle M25PX80.
-
Support for numonyx M25PX80 flash
-
Support for ebay platform cable DLC9G
-
Alexandru Gagniuc created ticket #20
xc3sprog does not work with Xilinx cable on second try
-
On the first invocation after plugging in the cable even programming works: root@notebook5:/home/philipp/xc3sprog/build#...
-
On the first invocation afetr plugging in the cable even programming works: root@notebook5:/home/philipp/xc3sprog/build#...
-
I've now tried with different cables on different USB ports of the machine, both...
-
"Philipp" == Philipp Klaus Krause spth@users.sf.net writes: Philipp> I added the...
-
I added the udev rules according to https://github.com/timvideos/HDMI2USB/wiki/Xilinx-Platform-Cable-USB-under-Linux...
-
I added the udev rules according to https://github.com/timvideos/HDMI2USB/wiki/Xilinx-Platform-Cable-USB-under-Linux...
-
I added the udev rules according to https://github.com/timvideos/HDMI2USB/wiki/Xilinx-Platform-Cable-USB-under-Linux...
-
"Philipp" == Philipp Klaus Krause spth@users.sf.net writes: Philipp> But xc3sprog...
-
"Philipp" == Philipp Klaus Krause spth@users.sf.net writes: Philipp> Just found the...
-
Just found the thread at https://www.mikrocontroller.net/topic/142358 from 4 yeasr...
-
Waveshare makes a cable that is claimed to be compatible with the Xilinx Platform...
-
When I change the USB ID in cablelist.txt to the one of my cable, I get (as normal...
-
According to cablelist.txt, the Xilinx Platform cable USB II has USB ID 0x03fd:0x0008....
-
But xc3sprog -c xpc gives ~~~~ philipp@notebook5:~/xc3sprog/build$ ./xc3sprog -c...
-
Did you check to see if speed is limited by Jtag/Algorithm speed and not by pure...
-
millerton created ticket #7
Increase flash programming speed
-
devlist.txt: Add XC7A15T.
-
mapfile_xc2c: Program the "done bit" correctly.
-
alcantornet posted a comment on ticket #30
Regression FIX: Program the "done bit" correctly. Device was correctly flashed but...
-
"alcantornet" == alcantornet alcantornet@users.sf.net writes: alcantornet> I've see...
-
I've see you've merged my addon. Thanks you, I appreciate if someone else can use...
-
I've see you've merge my addon. Thanks you, i've apprecied if someone else can use...
-
vidisha modified a comment on ticket #6
-
More Usercode for XC2C devices.
-
Look for ftdi1. It should be standard now in 2016.
-
Usercode for XC2C devices.
1 >
