#8 xcf02s

[raydem]

Hello,

I am trying to program the xcf02s with a ft232H. I detect the fpga and the prom, when I program the flash, I use the next command: xc3sprog -c ft232h -v -p 1 s116.mcs:w::MCS and this is the result:

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
Could not open FTDI device (using libftdi): device not found
FTD2XX/WIN: Can't set VID/PID to 0403:6014. Expect failure
Using FTD2XX, Using JTAG frequency   1.500 MHz from undivided clock
JTAG chainpos: 1 Device IDCODE = 0xd5045093     Desc: XCF02S
Erasing.....done
Erase time 2613.6 ms
Programming does not end at block boundary (nbits = 1353728), padding
Programming block    330/   331 at XCF frame 0x2940...done
Programming time 3023.9 ms
Verify block     26/   331 at XCF frame 0x0340
Verify failed at block 26 (frame 0x0340)
USB transactions: Write 1604 read 1592 retries 0

The device is not programed. Can you help me? Thank you

[Uwe Bonnes]

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?

[raydem]

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

[Uwe Bonnes]

If xc3sprog -T0 shows errors, you have signal integrity problems.

[raydem]

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 JTAG frequency 1.200 MHz from undivided clock
JTAG chainpos: 1 Device IDCODE = 0xd5045093 Desc: XCF02S
Erasing.....done
Erase time 2608.9 ms
Programming does not end at block boundary (nbits = 1353728), padding
Programming block 330/ 331 at XCF frame 0x2940...done
Programming time 3094.1 ms
Verify block 23/ 331 at XCF frame 0x02e0
Verify failed at block 23 (frame 0x02e0)
USB transactions: Write 1578 read 1567 retries 3015

[raydem]

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: 0xfe09
Expecting 2 IDCODES : 0xd5045093 0x11c1a093
JTAG loc.: 0 IDCODE: 0x11c1a093 Desc: XC3S250E Rev: A IR length: 6
JTAG loc.: 1 IDCODE: 0xd5045093 Desc: XCF02S Rev: M IR length: 8

[Uwe Bonnes]

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.

[raydem]

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 ?

[Uwe Bonnes]

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.

[raydem]

Hello Uwe,

I tried with linux box and result is the same.

[Uwe Bonnes]

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...

[raydem]

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.

[raydem]