xc3sprog-users — Generic user and developer list

[Xc3sprog-users] Fwd: SVF output / support for a new cable type

[Bence C. <be...@sc...>]

Hi,
I am the author of liblogsys-drv
(https://github.com/bence98/Logsys-LibUSB-Driver/), a cross-platform
driver for my University's FPGA development boards.
I currently depend on iMPACT for taking a .BIT file and turning it
into an .SVF file that I can then process by libxsvf
(https://github.com/bence98/Logsys-LibUSB-Driver/blob/master/src/shared/jconf.c#L211).
However, after seeing the fantastic work you have done, I would like
to switch to xc3sprog.
My question is:
* is it possible to make xc3sprog output a .SVF file?
* if not, do you plan on adding this feature?
* if neither, how could one add a new cable type? Quickly looking
through the code, I can see that I would need to subclass from
`IOBase` defined in `iobase.h`, but I don't see how to "register" it,
i.e. make `xc3sprog -c` recognize it.
* is it possible to use xc3sprog as a .so library? If not, do you plan
on making this possible?
Thanks in advance,
Bence

Re: [Xc3sprog-users] Help Gitting started with xc3sprog

[Dan H. <da...@da...>]

On Wed, 7 Aug 2019 17:54:42 +0300
Mika Leinonen <ml...@gm...> wrote:

> http://xc3sprog.sourceforge.net/guide.php starts with
> "svn co https://xc3sprog.svn.sourceforge.net/svnroot/xc3sprog/trunk
> xc3sprog" But i didn't get ahead with installing, as the reply was
> (on debian 10) svn: E170013: Unable to connect to a repository at URL
> 'https://xc3sprog.svn.sourceforge.net/svnroot/xc3sprog/trunk'
> svn: E160013: '/svnroot/xc3sprog/trunk' path not found

likely the guide hasn't been updated after one the changes at sf.net,
the correct URL and whole command can be seen at
https://sourceforge.net/p/xc3sprog/code/


		Dan

[Xc3sprog-users] Help Gitting started with xc3sprog

[Mika L. <ml...@gm...>]

http://xc3sprog.sourceforge.net/guide.php starts with
"svn co https://xc3sprog.svn.sourceforge.net/svnroot/xc3sprog/trunk xc3sprog"
But i didn't get ahead with installing, as the reply was (on debian 10)
svn: E170013: Unable to connect to a repository at URL
'https://xc3sprog.svn.sourceforge.net/svnroot/xc3sprog/trunk'
svn: E160013: '/svnroot/xc3sprog/trunk' path not found

[Xc3sprog-users] Device failed to configure, INSTRUCTION_CAPTURE is 0x19

[Daniel M. <D.M...@sr...>]

Hi,

I have a strange issue, hopefully you will be able to help me.
Programming a VP780 board, using a bit file created by ISE works
without a problem. But the same project ported to vivado, the generated
bitstream gives the following error during programming (using the same
setup):


XC3SPROG (c) 2004-2011 xc3sprog project $Rev: 774 $ OS: Linux
...

Using /etc/xc3sprog/devlist.txt
Using /etc/xc3sprog/cablelist.txt
Cable jtaghs2 type ftdi VID 0x0403 PID 0x6014 Desc "Digilent USB
Device" dbus data e8 enable eb cbus data 00 data 60
Using Libftdi, Using JTAG frequency   6.000 MHz from undivided clock
JTAG chainpos: 2 Device IDCODE = 0x33691093 Desc: XC7VX690T
Created from NCD file:
vp780_adcpolyphase;COMPRESS=TRUE;UserID=0XFFFFFFFF;Version=2018.2
Target device: 7vx690tffg1930
Created: 2019/07/25 17:50:52
Bitstream length: 138409888 bits
done. Programming time 23754.6 ms
Device failed to configure, INSTRUCTION_CAPTURE is 0x19
USB transactions: Write 8537 read 80 retries 64
I tried to google it, or look at the xc3sprog documentations, but
couldn't find anything that would hint on where the issue lies. 
Also tried to program it from vivado itself from a different PC, with
the bit file that was generated from ISE:


set_property PROBES.FILE {} [get_hw_devices xc7vx690t_2]
set_property FULL_PROBES.FILE {} [get_hw_devices xc7vx690t_2]
set_property PROGRAM.FILE
{C:/Users/jellet/Documents/vp780_adcpolyphase_Pulsdetection_2017_11_23.bit}
[get_hw_devices xc7vx690t_2]
program_hw_devices [get_hw_devices xc7vx690t_2]
INFO: [Labtools 27-3164] End of startup status: HIGH
...
and vivado's bitstream:


set_property PROBES.FILE {} [get_hw_devices xc7vx690t_2]
set_property FULL_PROBES.FILE {} [get_hw_devices xc7vx690t_2]
set_property PROGRAM.FILE
{C:/Users/jellet/Documents/vp780_adcpolyphase_Pulsedetection_2019_07_25_3.bit}
[get_hw_devices xc7vx690t_2]
program_hw_devices [get_hw_devices xc7vx690t_2]
ERROR: [Labtools 27-3165] End of startup status: LOW
...
Also tried to google on this, but there are many questions and no
answers in the forums. 
Could anybody please tell me what "INSTRUCTION_CAPTURE is 0x19" means?
What causes it? And why?

Every help is appreciated.

Kind Regards,
Dániel

Re: [Xc3sprog-users] indirect spi programming issues

[Charlie M. <cjm...@gm...>]

I managed to fix both issues fairly easily. The first was caused by a space
between -I and the bitfile. The second was a simple matter of adding a
couple of lines to the progalgspiflash.cpp. Diff below.

Thanks,
Charlie

Index: progalgspiflash.cpp
===================================================================
--- progalgspiflash.cpp (revision 793)
+++ progalgspiflash.cpp (working copy)
@@ -480,6 +480,10 @@
             pages = 65536;
             sector_size = 65536;
             break;
+   case 0x20:
+     pages = 524288;
+ sector_size = 65536;
+ break;
           default:
             fprintf(stderr,"Unexpected N25Q size ID 0x%02x\n", buf[2]);
             return -1;

On Mon, Mar 19, 2018 at 1:40 PM, Charlie Mraz <cjm...@gm...> wrote:

> Hello All,
>
> I have been attempting to program the SPI FLASH (Micron MT25QL512) hanging
> off my 7-series FPGA. I am having two problems.
>
> 1) Invoking xc3sprog and specifying the bitfile for indirect programming
> with -I doesn't seem to work at all. I get the message: JEDEC: ff ff 0xff
> 0xff.
>
> 2) If I load the ISF bitfile manually, then I get:
> JEDEC: 20 ba 0x20 0x10
> Found Numonyx N25Q Device, Device ID 0xba20
> Unexpected N25Q size ID 0x20
> ISF Bitfile probably not loaded
>
> I presume the 2nd issue is easily corrected, as it looks like the SPI
> interface is generally working, so I am going to start working on that one
> first. Any ideas on the first one? I don't mind the workaround for now, but
> I would like to resolve the issue eventually. Any advice would be
> appreciated.
>
> Thanks,
> Charlie Mraz
>

Re: [Xc3sprog-users] finding the original roger source code

[Uwe B. <bo...@el...>]

    thec> after i have written to uwe bonnes, he gave me in his, presumably
    thec> automated, answer the same dead link

Adjust your AI detector!
    thec> answer the same dead link
    thec> (http://www.rogerstech.co.uk/xc3sprog/) as you can find in the
    thec> manual pages of the project:
    thec> http://xc3sprog.sourceforge.net/manpage.php

No, I pointed you to the SVN code. The SVN code is based on the old code and
contains this code.

    thec> after doing some search on my own, i did find this:
    thec> www.rogerstech.force9.co.uk
    thec> http://www.rogerstech.force9.co.uk/xc3sprog/
    thec> http://www.rogerstech.force9.co.uk/xc3sprog/XC3Sprog.tar.gz

This still does not answer why you want the old stuff.

...

Bye
-- 
Uwe Bonnes                bo...@el...

Institut fuer Kernphysik  Schlossgartenstrasse 9  64289 Darmstadt
--------- Tel. 06151 1623569 ------- Fax. 06151 1623305 ---------

[Xc3sprog-users] finding the original roger source code

[thec <th...@ya...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

berlin 180324


hi there,
after having some success with an old version of the xc3sprog tools, i
have tried to find the not included source code.

after i have written to uwe bonnes, he gave me in his, presumably
automated, answer the same dead link
(http://www.rogerstech.co.uk/xc3sprog/) as you can find in the manual
pages of the project: http://xc3sprog.sourceforge.net/manpage.php

after doing some search on my own, i did find this:
www.rogerstech.force9.co.uk
http://www.rogerstech.force9.co.uk/xc3sprog/
http://www.rogerstech.force9.co.uk/xc3sprog/XC3Sprog.tar.gz

if you want the originial source code from roger, have a try on this.

after downloading the tar archiv, i tried to compile the source code
as i have tried to compile the uwe bonnes stuff. i use a native linux
machine with openSuse 13.2.  at first i did fail in the same way as i
did with the new versions.

after doing some search i did add some include directives and succeded.
the result can be found here:
http://nkisiland.com/ftp/pub/xc3sprog/XC3Sprog_imx.tar.gz
the changes are commented with my 6/66' tag

be careful, it compiles but it is not tested properly.
have fun!
6/66'

- -- 
- -----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: A revocation certificate should follow

iQEfBCABAgAJBQJYur1uAh0CAAoJEKSlJZxOuxAwxscH/jj/hXYrJBL4fWrjWsG8
wTIN4R+zCAji6AikgBlFwuPLYTo9/xhJkYIyX2V4YhL5lFihR+L/g7W/L/u4suvM
njRd5m2N7bCV6lzg23W3NwzoTzUTR5lydX7j1noz270rnCdAXssSlcpgnM3tMlS0
yQgVezlM9Bmd+vJ3W6vhmzzNsXFRyY6IdmMINH7+UGnNUf1v9KRXikQQM8mGXalb
HhKDkoDQLwelFVUv/NqgpEswoOxv/iTXwFN4vBZmcu2ObRqFlA2as1BgJmhZPa2I
lxrrEliN07DqTCNOmJ5fjLAIj0fgr9WoZEmZiGxR+KNKTP0MfgNJXHjg+iZ3YTUc
iOU=
=Jzu9
- -----END PGP PUBLIC KEY BLOCK-----
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJatgWAAAoJEKSlJZxOuxAwFfIH/jAzpniEWxBR5G2zi2T9nSn3
dS2Me1ObK9rFicsaB7EsqtDRL7mco7ljieW8QFi28DrJb/uDmfB7tTc4B9s9b3mp
0Vg0zZ5SSMEngg7oYiP293lznGOS2/FeM39Fy+GBEColsojuBVG+R2JFwt0FXM5u
0v15od62WkzwZidJrK435P/W0HB08ws1PrObnaKuafJNdbNmduBixmtkveueIk4d
UGKMy17aVX0viuhTKJRWTfIe0rDdlqFoOic9Xg40B3BLMH+9xyPupfNIIxZVHM8q
LW4TEyAubVl9YltXTlf6VE1gRyPcP+wB2+4WLd2r7M7VQUiNhxUWJvp5Qi1kikg=
=C6pN
-----END PGP SIGNATURE-----

[Xc3sprog-users] indirect spi programming issues

[Charlie M. <cjm...@gm...>]

Hello All,

I have been attempting to program the SPI FLASH (Micron MT25QL512) hanging
off my 7-series FPGA. I am having two problems.

1) Invoking xc3sprog and specifying the bitfile for indirect programming
with -I doesn't seem to work at all. I get the message: JEDEC: ff ff 0xff
0xff.

2) If I load the ISF bitfile manually, then I get:
JEDEC: 20 ba 0x20 0x10
Found Numonyx N25Q Device, Device ID 0xba20
Unexpected N25Q size ID 0x20
ISF Bitfile probably not loaded

I presume the 2nd issue is easily corrected, as it looks like the SPI
interface is generally working, so I am going to start working on that one
first. Any ideas on the first one? I don't mind the workaround for now, but
I would like to resolve the issue eventually. Any advice would be
appreciated.

Thanks,
Charlie Mraz

Re: [Xc3sprog-users] Help with windows build

[Charlie M. <cjm...@gm...>]

Uwe,

Thank you for your support. I have found the necessary .dlls in the Linux
filesystem. They were located at /usr/i686-w64-mingw32/sys-root/mingw/bin,
in case anyone else has the same issue. Simply copying them into the same
directory as the executable fixed the errors. While a statically linked
executable would be preferable, I am back on track and programming the XC7K
FPGA properly. Some issues with the indirect SPI, though. More questions to
follow.

Thanks,
Charlie

On Mon, Mar 12, 2018 at 10:45 AM, Uwe Bonnes <
bo...@el...> wrote:

> >>>>> "Charlie" == Charlie Mraz <cjm...@gm...> writes:
>
>     Charlie> Uwe, Thank you for the suggestion. I have tried various
>     Charlie> versions of the answers in the linked stackoverflow question,
>     Charlie> but I have not had any luck. They all seem to break the build
>     Charlie> somehow or another.
>
> Hello Charlie,
>
> probably libftdi-1 and/or libftd2xx use threading. Try to build against
> libftdi-0  w/o libftd2xx.
>
> Bye
> --
> Uwe Bonnes                bo...@el...
>
> Institut fuer Kernphysik  Schlossgartenstrasse 9  64289 Darmstadt
> --------- Tel. 06151 1623569 ------- Fax. 06151 1623305 ---------
>

Re: [Xc3sprog-users] Help with windows build

[Uwe B. <bo...@el...>]

>>>>> "Charlie" == Charlie Mraz <cjm...@gm...> writes:

    Charlie> Uwe, Thank you for the suggestion. I have tried various
    Charlie> versions of the answers in the linked stackoverflow question,
    Charlie> but I have not had any luck. They all seem to break the build
    Charlie> somehow or another.

Hello Charlie,

probably libftdi-1 and/or libftd2xx use threading. Try to build against
libftdi-0  w/o libftd2xx.

Bye
-- 
Uwe Bonnes                bo...@el...

Institut fuer Kernphysik  Schlossgartenstrasse 9  64289 Darmstadt
--------- Tel. 06151 1623569 ------- Fax. 06151 1623305 ---------

Re: [Xc3sprog-users] Help with windows build

[Charlie M. <cjm...@gm...>]

Uwe,

Thank you for the suggestion. I have tried various versions of the answers
in the linked stackoverflow question, but I have not had any luck. They all
seem to break the build somehow or another.

On a more basic level, is xc3sprog a threaded application? I can't actually
find where the pthread headers are being included...

Thanks,
Charlie

On Fri, Mar 9, 2018 at 12:14 PM, Uwe Bonnes <u.b...@t-...> wrote:

> Charlie Mraz writes:
>  > Hello,
>  >
>  > I have used xc3sprog in the past with Coolrunner-II and Spartan-3 and -6
>  > devices, but I now have a project that is using a Kintex-7. The
> currently
>  > checked-in Windows executable apparently pre-dates 7-series support, so
> I have
>  > attempted to cross-compile using OpenSUSE Leap 42 on WSL, following the
>  > instructions in the Readme.Cmake. The execuatble builds, but fails with
> a
>  > message saying that "execution cannot proceed because
> libwinpthread-1.dll was
>  > not found." Can anyone advise where to obtain libwinpthread-1.dll, or
> what may
>  > have gone wrong in the compilation that might cause this problem?
>  > Alternatively, a link to a windows executable with 7-series support
> would be
>  > great, too, though it would be nice to be able to build xc3sprog
>  > from source in
>  > the future as well...
>  >
> Hello,
>
> can you try the hints at
> https://stackoverflow.com/questions/13768515/how-to-do-static-linking-of-
> libwinpthread-1-dll-in-mingw
> and report back?
>
> Thanks
> --
> Uwe Bonnes                bo...@el...
>

[Xc3sprog-users] Help with windows build

[Uwe B. <u.b...@t-...>]

Charlie Mraz writes:
 > Hello,
 > 
 > I have used xc3sprog in the past with Coolrunner-II and Spartan-3 and -6
 > devices, but I now have a project that is using a Kintex-7. The currently
 > checked-in Windows executable apparently pre-dates 7-series support, so I have
 > attempted to cross-compile using OpenSUSE Leap 42 on WSL, following the
 > instructions in the Readme.Cmake. The execuatble builds, but fails with a
 > message saying that "execution cannot proceed because libwinpthread-1.dll was
 > not found." Can anyone advise where to obtain libwinpthread-1.dll, or what may
 > have gone wrong in the compilation that might cause this problem?
 > Alternatively, a link to a windows executable with 7-series support would be
 > great, too, though it would be nice to be able to build xc3sprog
 > from source in
 > the future as well...
 >
Hello,

can you try the hints at
https://stackoverflow.com/questions/13768515/how-to-do-static-linking-of-libwinpthread-1-dll-in-mingw
and report back?

Thanks
-- 
Uwe Bonnes                bo...@el...

[Xc3sprog-users] Help with windows build

[Charlie M. <cjm...@gm...>]

Hello,

I have used xc3sprog in the past with Coolrunner-II and Spartan-3 and -6
devices, but I now have a project that is using a Kintex-7. The currently
checked-in Windows executable apparently pre-dates 7-series support, so I
have attempted to cross-compile using OpenSUSE Leap 42 on WSL, following
the instructions in the Readme.Cmake. The execuatble builds, but fails with
a message saying that "execution cannot proceed because libwinpthread-1.dll
was not found." Can anyone advise where to obtain libwinpthread-1.dll, or
what may have gone wrong in the compilation that might cause this problem?
Alternatively, a link to a windows executable with 7-series support would
be great, too, though it would be nice to be able to build xc3sprog from
source in the future as well...

Thanks in advance,
Charlie Mraz

Re: [Xc3sprog-users] work with recent distro

[Lange, B. <b....@hz...>]

> -----Original Message-----
> From: Valerio Messina via Xc3sprog-users [mailto:xc3sprog-
> us...@li...]
> Sent: Friday, October 27, 2017 5:58 PM
> To: xc3...@li...
> Subject: Re: [Xc3sprog-users] work with recent distro
>
> Is this Multiboot feature supported by xc3sprog ?
I think this should work.
xc3sprog is only responsible for writing the configuration data at the correct place in flash.

>From my experience the main problem is to configure bitgen and promgen right.

> Can I update a single bitstream a time?
Should work.

> Can I change the default boot bitstream?
Depends on your configuration.

Regards,
Bert

[Xc3sprog-users] xc3sprog -c output

[Valerio M. <ef...@io...>]

hi,
what are the meanings of columns in -c output?

The 1st is the argument for -c
The 2nd is the Brand?
The 3th is ?
The 4th is USB manufacturer?
The 5th is USB model?
The 6th is ?
...

For example I'm looking for FT2232HL, so the interesting line for me is:

ft2232test	ftdi	8000000	0x0403:0x6010:FT2232TEST:1:0x00:0x10:0x00:0x80

but I want to understand more.

thank you,
Valerio

Re: [Xc3sprog-users] work with recent distro

[Valerio M. <ef...@io...>]

Uwe Bonnes wrote:
> You have to invest some thinking what your
> are trying to do and what really happens. E.g. access rights to the
> USB device or some other driver already loaded may interfere.
>
> Compiling with cmake now makes things easier. Fullfilling the
> requerements to be able to compile heavily depends on your system.

apparently compile, this evening will try to connect to the test board.

Another question:
my test board use the Spartan-6 Multiboot feature with the bootloader 
and 15 bitstreams in an external SPI flashPROM (and maybe a Microblaze 
soft CPU).

Is this Multiboot feature supported by xc3sprog ?
Can I update a single bitstream a time?
Can I change the default boot bitstream?

thank you,
Valerio

Re: [Xc3sprog-users] work with recent distro

[Uwe B. <bo...@el...>]

>>>>> "Valerio" == Valerio Messina via Xc3sprog-users <xc3...@li...> writes:

    Valerio> Uwe Bonnes wrote:
    >> SVN head is updated regulary.

    Valerio> thank you.

    Valerio> What distro are you testing on?

    Valerio> I'm little worried because in this post:

    Valerio> https://forums.xilinx.com/t5/Installation-and-Licensing/windrvr6-install-fails-on-Debian-need-help-with-iMPACT-based/m-p/201089#M3082

    Valerio> they say: "Alternatively i have tryed the xc3sprog
    Valerio> multiplatform programmer, but this program also can't recognise
    Valerio> my device"

Nothing come for free. You have to invest some thinking what your are
trying to do and what really happens. E.g. access rights to the USB device
or some other driver already loaded may interfere.

Compiling with cmake now makes things easier. Fullfilling the requerements
to be able to compile heavily depends on your system. This you must
resolve...

A lot of people use xc3sprog with success.

Bye
-- 
Uwe Bonnes                bo...@el...

Institut fuer Kernphysik  Schlossgartenstrasse 9  64289 Darmstadt
--------- Tel. 06151 1623569 ------- Fax. 06151 1623305 ---------

Re: [Xc3sprog-users] work with recent distro

[Valerio M. <ef...@io...>]

Uwe Bonnes wrote:
> SVN head is updated regulary.

thank you.

What distro are you testing on?

I'm little worried because in this post:

https://forums.xilinx.com/t5/Installation-and-Licensing/windrvr6-install-fails-on-Debian-need-help-with-iMPACT-based/m-p/201089#M3082

they say:
"Alternatively i have tryed the xc3sprog multiplatform programmer, but 
this program also can't recognise my device"

anyway it was a post of 2012.

Valerio

Re: [Xc3sprog-users] work with recent distro

[Uwe B. <bo...@el...>]

>>>>> "Valerio" == Valerio Messina via Xc3sprog-users <xc3...@li...> writes:

    Valerio> hi, I'm using Ubuntu 16.04 64 bit Installing ISE 14.7 work
    Valerio> well, but lead to USB driver error, seems as Debian based
    Valerio> distro are not supported, so programming does not work.
    Valerio> Googling found this tools, but web site say last updated in
    Valerio> 2013.

SVN head is updated regulary.

-- 
Uwe Bonnes                bo...@el...

Institut fuer Kernphysik  Schlossgartenstrasse 9  64289 Darmstadt
--------- Tel. 06151 1623569 ------- Fax. 06151 1623305 ---------

[Xc3sprog-users] work with recent distro

[Valerio M. <ef...@io...>]

hi,
I'm using Ubuntu 16.04 64 bit
Installing ISE 14.7 work well, but lead to USB driver error, seems as 
Debian based distro are not supported, so programming does not work.
Googling found this tools, but web site say last updated in 2013.

Is this working with current distro?

I want to program this demo board:
http://www.futurashop.it/FT1286M-LED-MATRIX-RGB
http://www.futurashop.it/Allegato_PDF_IT/7100-FT1286M.pdf
that use the FT2232HL Dual USB UART/FIFO and a Spartan-6

thank you,
Valerio

[Xc3sprog-users] Increase flash programming speed

[uldhc <ul...@st...>]

Hello,


can I somehow increase the programming speed when writing to a flash connected to the fpga

(xc3sprog -c ftdi -I bitfile.bit)?

I have opened a ticket in 'support requests':

https://sourceforge.net/p/xc3sprog/support-requests/7/


Thanks,
Michael

[Xc3sprog-users] Building Windows *.exe

[Daniel Ś. <sci...@gm...>]

Hi,

could you help with building Windows executable files on Ubuntu?

I did:
$ mkdir build-win32; cd build-win32;
$ cmake -DCMAKE_TOOLCHAIN_FILE=../Toolchain-mingw32.cmake ..

And my result is: http://pastebin.com/duHWr3JE

So I tried to point it to downloaded libftdi and libftd2xx with:
$ cmake -DCMAKE_TOOLCHAIN_FILE=../Toolchain-mingw32.cmake
-DLIBFTDI_LIBRARIES=/home/ds/libftdi_win_library/lib/libftdi1.dll.a
-DLIBFTDI_INCLUDE_DIR=/home/ds/libftdi_win_library/include/libftdi1/
-DLIBFTD2XX_LIBRARIES=/home/ds/ftdi_win_library/Static/amd64/ftd2xx.lib
-DLIBFTD2XX_INCLUDE_DIR=/home/ds/ftdi_win_library/ ..

Cmake finished its job without any error, but I couldn't compile it with
make: http://pastebin.com/GWV6k9LA

Re: [Xc3sprog-users] xcs3prog, windows 10 and olimex

[Uwe B. <bo...@el...>]

>>>>> "Bostjan" == Bostjan Jerko <bo...@t-...> writes:

    Bostjan> Hi, anybody managed to get Olimex ARM-USB-OCD working with
    Bostjan> xcs3prog on Windows 10?  I am trying to use Olimex’s JTAG and
    Bostjan> it works on Windows 7 so I hoped I could use the same procedure
    Bostjan> to install it on Windows 10, but I just get missing FTDI error
    Bostjan> (same as on Windows 7, but it works there) and nothing else.

    Bostjan> I am trying to program Spartan3 board.

You needd to install the libraries (libusb and/or libftd2xz. Have a look at
README.Win32.If things change for Win10, please let the list know.

Bye
-- 
Uwe Bonnes                bo...@el...

Institut fuer Kernphysik  Schlossgartenstrasse 9  64289 Darmstadt
--------- Tel. 06151 1623569 ------- Fax. 06151 1623305 ---------

[Xc3sprog-users] xcs3prog, windows 10 and olimex

[Bostjan J. <bo...@t-...>]

Hi,

anybody managed to get Olimex ARM-USB-OCD working with xcs3prog on Windows 10?
I am trying to use Olimex’s JTAG and it works on Windows 7 so I hoped I could use the same procedure to install it on Windows 10, but I just get missing FTDI error (same as on Windows 7, but it works there) and nothing else.

I am trying to program Spartan3 board.


Thanks.

Best,

B.

Re: [Xc3sprog-users] Programming the Digilent Genesys 2 board

[Joe H. <xc3...@su...>]

Thanks for the reply, Uwe.

This it the output from `dmesg` when I plug in the board.

```
[336371.820044] usb 1-5: new high-speed USB device number 24 using
xhci_hcd
[336371.953810] usb 1-5: New USB device found, idVendor=0403,
idProduct=6010
[336371.953813] usb 1-5: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[336371.953814] usb 1-5: Product: Digilent Adept USB Device
[336371.953815] usb 1-5: Manufacturer: Digilent
[336371.953816] usb 1-5: SerialNumber: 200300730484
[336371.956892] ftdi_sio 1-5:1.0: FTDI USB Serial Device converter
detected
[336371.956929] usb 1-5: Detected FT2232H
[336371.957094] usb 1-5: FTDI USB Serial Device converter now attached
to ttyUSB0
[336371.959674] ftdi_sio 1-5:1.1: FTDI USB Serial Device converter
detected
[336371.959700] usb 1-5: Detected FT2232H
[336371.959892] usb 1-5: FTDI USB Serial Device converter now attached
to ttyUSB1
```

xc3sprog's behavior is the same when running as root. This is the output
running as root and specifying the reported serial number for the board. 

```
$ sudo xc3sprog -c ftdi blink.bit -v -s 200300730484
XC3SPROG (c) 2004-2011 xc3sprog project $Rev: 785 $ 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

Using built-in device list
Using built-in cable list
Cable ftdi type ftdi VID 0x0403 PID 0x6010 Serial 200300730484 dbus data
00 enable 0b cbus data 00 data 00
Using Libftdi, Using JTAG frequency   1.500 MHz from undivided clock
No JTAG Chain found
USB transactions: Write 5 read 2 retries 0
```

I am able to program the board using the Xilinx tools, so I don't think
that the board is faulty.

Best,
Joe.

On Sun, Jun 26, 2016, at 11:11 AM, Uwe Bonnes wrote:
> >>>>> "Joe" == Joe Hermaszewski <xc3...@su...> writes:
> 
>     Joe> The Genesys2 has a FT2232H FTDI chip connected to the JTAG ports
>     on
>     Joe> the FPGA, a XC7K325T-2FFG900C. It seems as though all the pieces
>     Joe> are there to enable programming this board with xc3sprog,
>     however I
>     Joe> can't quite get it to work.
> 
>     Joe> Programming with cable type `ftdi` or `jtaghs1` produces the
>     error
>     Joe> message:
> 
>     Joe> ``` Using Libftdi, No JTAG Chain found ```
> 
>     Joe> Programming with other cable types gets less far, for example
>     the
>     Joe> `jtaghs2` or `ftdijtag` cable types are not even able to find
>     the
>     Joe> device.
> 
>     Joe> ``` Could not open FTDI device (using libftdi): device not found
>     Joe> Unable to access FTDI device with either libftdi or FTD2XX ```
> 
>     Joe> What options do I have for debugging this? Perhaps there are
>     tweaks
>     Joe> I can make similar to what was done for the `nexys4` cable type.
> 
> Does the FTDI get recognised when plugged? Look e.g. with "dmesg".
> If it gets recognized, do you have decent access rights on that device?
> If
> xc3sprog recognises the device when running as root, change the udev
> rules.
> 
> And when the device gets recognized and you have access and then
> connection
> still fails, check the connection on the board.
> 
> Hope this helps
> -- 
> Uwe Bonnes                bo...@el...
> 
> Institut fuer Kernphysik  Schlossgartenstrasse 9  64289 Darmstadt
> --------- Tel. 06151 1623569 ------- Fax. 06151 1623305 ---------