Menu
▾
▴
ixo-jtag-devel — ixo-jtag Developers
You can subscribe to this list here.
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
(3) |
Jul
(5) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2012 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(2) |
|
From: Josh D. <saw...@li...> - 2015-12-05 21:37:46
|
I have searched deeply on this issue and all that I have been able to turn up, personally, is that the FX3 documentation indicates it supports DMA transfers. There has not been anything which would indicate it on FX2. I just thought since we're bit banging anyway, is it possible that it already supports DMA EJTAG through the CPLD or something? Thanks again! ________________________________________ From: Josh Davidson [saw...@li...] Sent: Saturday, December 5, 2015 4:20 PM To: ixo...@li... Subject: [ixo-jtag-devel] dma access with fx2?? possible? Hello, I don't know how recent this list has been in recent years, but I have a question which is very important to me! (Hopefully others, too!) I didn't know where else to ask so I went to the list! Is it possible to use the xilinx platform USB cable (Chinese dlc9 derivative) for EJTAG with DMA? You see, I have two older broadcom devices which need JTAG. The oldest (a modem, bcm3349) uses ejtag_dma and this has proved to be an issue so far. The only other JTAG cable I have is the luminary stellaris BD-ICDI (pre-TI stellaris). The ICDI came as a separate board along with a pre-release Stellarisware Blizzard eval board (with LCD, push buttons, both LM3S and LX4F (early version of LM4F)). There does not appear to have ever existed any documentation on this specific stellaris board. Regardless, the ICDI is known and I was very lucky at copying and pasting init commands from other old broadcom device files and finally managed to get the bcm3349 to show up and probe as a TAP in openocd! Unfortunately I have not been able to replicate this in openocd ever since I accidentally unplugged it a few minutes after I got it to init before. So I turned to urjtag and had 0 luck getting anything to probe with the ICDI. I began looking for alternatives and figured out that I could use urjtag with my only other JTAG cable, the xilinx dlc9 (derivative, I point this out because even though it is labeled as and functions as dlc9, it is a Chinese fake, but with all the correct parts). I ran cable xpc_ext in urjtag and the IDCODE is probed! Now I can initbus EJTAG (no DMA), select bus, run discovery, etc. At this point I am stuck! Is there another fw hex which I could first load on the dlc9 which allows initbus ejtag_dma (i have the Windows version of fxload-libusb)? If not, can I use PrAcc on the EJTAG 2.2 (I think) bcm3349? What I want to do is dump the entire RAM and the whole flash. Then possibly write a new CFE to the device. I cannot find any help about such things as most of this type of work refers to tjtag, zjtag, hairydairymade, etc. Which is quite a different type of command-line interface. So even in urjtag whether PrAcc or EJTAG_DMA, I don't really know how to continue. Could anyone give me a few pointers or point me to a resource for how to do this correctly with urjtag? Sorry if this part counts as off topic and feel free to email me and not the list with replies about this question in particular. I do have Linux options as well. Particularly, I could use raspberry pi for JTAG (anyone knows a good resource please let me know). Other Linux options are same cables, but with Linux x64 instead of Win x64. In the meanwhile I have begun construction of an unbuffered dlc5 type parallel device which should work with something like zjtag but I would really rather not take time to build. I notice in all instructions for this type device it always says to use 100 Ohm resister, which from my calculations would bring +12V down to +6V. I don't have any 100 Ohm resistors, but do have a strip of 12x 75 Ohm resistors. I calculated that as well (3x 75 Ohm in series) and that should bring max +12V down to +4V! Wouldn't this be more than adequate to generate a 1 on 5V systems as well as bring closer to 3.3V tolerant? Many 3.3V logic devices are 5V tolerant as is, but 6V seems a bit high. Does this sound like it would be easier?? (The parallel port) If so, then I will maybe use the rest of my leftover perfboard to make a serial inverter with an old FT232AM which I found in an old cellphone data transfer cable and a 74VHC04 which I found in a box. I've been searching for my actual USB-TTL converter for weeks!! I'm so sorry for this terribly long email. I just couldn't figure out a good place to ask all of these questions at once! For any who take the time to read thank you, and extra special, very thank you to anyone who might take time to reply! Cheers, -SB ------------------------------------------------------------------------------ Go from Idea to Many App Stores Faster with Intel(R) XDK Give your users amazing mobile app experiences with Intel(R) XDK. Use one codebase in this all-in-one HTML5 development environment. Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs. http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140 _______________________________________________ ixo-jtag-devel mailing list ixo...@li... https://lists.sourceforge.net/lists/listinfo/ixo-jtag-devel |
|
From: Josh D. <saw...@li...> - 2015-12-05 21:20:16
|
Hello, I don't know how recent this list has been in recent years, but I have a question which is very important to me! (Hopefully others, too!) I didn't know where else to ask so I went to the list! Is it possible to use the xilinx platform USB cable (Chinese dlc9 derivative) for EJTAG with DMA? You see, I have two older broadcom devices which need JTAG. The oldest (a modem, bcm3349) uses ejtag_dma and this has proved to be an issue so far. The only other JTAG cable I have is the luminary stellaris BD-ICDI (pre-TI stellaris). The ICDI came as a separate board along with a pre-release Stellarisware Blizzard eval board (with LCD, push buttons, both LM3S and LX4F (early version of LM4F)). There does not appear to have ever existed any documentation on this specific stellaris board. Regardless, the ICDI is known and I was very lucky at copying and pasting init commands from other old broadcom device files and finally managed to get the bcm3349 to show up and probe as a TAP in openocd! Unfortunately I have not been able to replicate this in openocd ever since I accidentally unplugged it a few minutes after I got it to init before. So I turned to urjtag and had 0 luck getting anything to probe with the ICDI. I began looking for alternatives and figured out that I could use urjtag with my only other JTAG cable, the xilinx dlc9 (derivative, I point this out because even though it is labeled as and functions as dlc9, it is a Chinese fake, but with all the correct parts). I ran cable xpc_ext in urjtag and the IDCODE is probed! Now I can initbus EJTAG (no DMA), select bus, run discovery, etc. At this point I am stuck! Is there another fw hex which I could first load on the dlc9 which allows initbus ejtag_dma (i have the Windows version of fxload-libusb)? If not, can I use PrAcc on the EJTAG 2.2 (I think) bcm3349? What I want to do is dump the entire RAM and the whole flash. Then possibly write a new CFE to the device. I cannot find any help about such things as most of this type of work refers to tjtag, zjtag, hairydairymade, etc. Which is quite a different type of command-line interface. So even in urjtag whether PrAcc or EJTAG_DMA, I don't really know how to continue. Could anyone give me a few pointers or point me to a resource for how to do this correctly with urjtag? Sorry if this part counts as off topic and feel free to email me and not the list with replies about this question in particular. I do have Linux options as well. Particularly, I could use raspberry pi for JTAG (anyone knows a good resource please let me know). Other Linux options are same cables, but with Linux x64 instead of Win x64. In the meanwhile I have begun construction of an unbuffered dlc5 type parallel device which should work with something like zjtag but I would really rather not take time to build. I notice in all instructions for this type device it always says to use 100 Ohm resister, which from my calculations would bring +12V down to +6V. I don't have any 100 Ohm resistors, but do have a strip of 12x 75 Ohm resistors. I calculated that as well (3x 75 Ohm in series) and that should bring max +12V down to +4V! Wouldn't this be more than adequate to generate a 1 on 5V systems as well as bring closer to 3.3V tolerant? Many 3.3V logic devices are 5V tolerant as is, but 6V seems a bit high. Does this sound like it would be easier?? (The parallel port) If so, then I will maybe use the rest of my leftover perfboard to make a serial inverter with an old FT232AM which I found in an old cellphone data transfer cable and a 74VHC04 which I found in a box. I've been searching for my actual USB-TTL converter for weeks!! I'm so sorry for this terribly long email. I just couldn't figure out a good place to ask all of these questions at once! For any who take the time to read thank you, and extra special, very thank you to anyone who might take time to reply! Cheers, -SB |
|
From: Francisco N. <ftc...@gm...> - 2014-07-30 12:11:03
|
Hello all, I'm trying to build the firmware for a Digilent Atlys board. I'm trying to compile the version available for the nexys 1/2 boards but I'm getting the following error message after make: $ make sdas8051 -plosgff vectors.a51 sdcc -c -mmcs51 --no-xinit-opt -Ifx2 -Dhw_nexys usbjtag.c -o usbjtag.rel fx2/fx2regs.h:73: syntax error: token -> 'at' ; column 9 make: *** [usbjtag.rel] Error 1 Thanks you all, Francisco Nunes. |
|
From: Dalton J. <Jam...@ar...> - 2012-03-02 16:13:11
|
The FT2232 is essentially two FT245 parts in one. I made a board that I am trying to emulate the FT245 + CPLD USB Blaster on one port and a VCP on the second port. I used Altera's Mprog to read the configuration from a genuine USB Blaster and I programmed the FT2232 with the same data (VID,PID). For some reason the USB Blaster driver does not load. I assumed that when windows saw the USB Blaster VID/PID it would load the USB Blaster driver. Can anyone tell me why this isn't working and if what I am attempting is possible? |
|
From: Hauke D <ha...@ze...> - 2010-07-14 17:06:09
|
Hi Stefan, Thanks for trying it out and sorry for the late reply. I've been busy so I haven't had a chance to try things out myself, once I do and confirm that everything works I think I'll make the change. I guess most people are using the software under Linux, so nobody ran into the problem in Windows before. Since I'm just maintaining the project, I'm not faimilar enough with the inner workings of the code yet to comment on the speed... Regards, -- Hauke D On Tue, 6 Jul 2010, DISTEC Lugmair Stefan wrote: > > Hi Hauke, > > I tested version 4.00 with Debian Lenny and couldn't see any problems. > IMHO it makes sense to change the version in the source code to prevent > others from spending days on this issue like I did. What still puzzles > me is that no one else has run into this problem before... > > Now I would like to try to seed up the svf-programming a little bit, 4 > minutes is quite long. Do you see any change for this or is it forlorn > hope? > > Regards, > Stefan > > > Hi Stefan, > > Thanks for the information, I'm glad it worked out. I'm curious, does the > version setting 4.00 work under Linux as well? In that case we could > consider changing that value. > > That UrJTAG (at least under Linux) works together with the Cypress > firmware isn't suprising because Kolja Waschk worked on both ;) > > Thanks, > -- Hauke D > > > On Mon, 5 Jul 2010, DISTEC Lugmair Stefan wrote: > > > Hi Hauke, > > > > thanks for your reply! Even if it was not a problem with VID/PID your > > comment pointed me to the right direction. I compared the descriptors of > > usb_jtag with the one from Altera's USB-Blaster and here is what I > > found: > > > > The following line in trunk/c51/dscr.a51 was responsible for the error > > message: > > > > VERSION = 0x0004 ; Product Version (4 indicates *BM device) > > > > This is read by the host as version 0.04. I compared with the Altera > > Blaster and here we have version 4.00. > > > > After exchanging this line by the following one everything works fine: > > VERSION = 0x0400 ; Product Version (4 indicates *BM device) > > > > I haven't found a good explanation for this. Looks like the problem lies > > in the combination FTDI-driver & UrJtag (since the wrong version 0.04 > > works under Linux). Somewhere the version is checked and somehow is > > decided that version 0.04 can't set the latency timer. After a quick > > scan of UrJtag's sources I would say that this "somewhere" is in the > > FTDI driver (?) > > > > Regards, > > Stefan > > > > > > -----Ursprüngliche Nachricht----- > > Von: Hauke D [mailto:ha...@ze...] > > Gesendet: Sonntag, 4. Juli 2010 22:13 > > An: ixo-jtag-devel Mailing List > > Cc: DISTEC Lugmair Stefan > > Betreff: Re: [ixo-jtag-devel] usbconn_ftd2xx_open(): Can't set latency timer. > > > > Hi Stefan, > > > > Unfortunately, this isn't my area of expertise, but maybe someone else on > > the list can help? > > > > My only (possibly somewhat ignorant :) ) comments would be that it might > > make sense to cross-post your question to the urjatg Forum/Lists - if you > > haven't already done so - to see if it might be a problem there? > > > > Also, it might have something to do with the fact that although the > > usb_jtag firmware exhibits the same behavior as the USB-Blaster, the VID > > and PID of the USB device are not the same as Altera's... some licensing > > issue I think. > > > > Regards, > > -- Hauke D > > > > > > On Tue, 29 Jun 2010, DISTEC Lugmair Stefan wrote: > > > >> > >> Hello, > >> > >> When I download your FW to my Cypress chip it becomes a USB-Blaster as > >> expected. Then under Linux I can program my Lattice CPLD with the > >> SVF-Player of UrJtag (using the libftdi driver). It takes quite long > >> (about 4 minutes), but it works reliably. > >> > >> However, when I want to do the same under Windows XP, I get the > >> following error (the USB-Blaster is listed in the Device-Manager, so the > >> driver seems properly installed): > >> > >> jtag> cable UsbBlaster > >> Connected to libftd2xx driver. > >> usbconn_ftd2xx_open(): Can't set latency timer. > >> Error: Cable initialization failed! > >> > >> I tested with the original USB-Blaster from Altera and the Altera pod is > >> recognized by the driver and programming of my CPLD is possible without > >> any problems. > >> > >> There seems to be a problem when the libftd2xx driver connects to the > >> Cypress chip. > >> > >> I would appreciate any help! > >> > >> Thanks, > >> > >> Stefan > >> > > > |
|
From: DISTEC L. S. <Lu...@di...> - 2010-07-06 19:39:09
|
Hi Hauke, I tested version 4.00 with Debian Lenny and couldn't see any problems. IMHO it makes sense to change the version in the source code to prevent others from spending days on this issue like I did. What still puzzles me is that no one else has run into this problem before... Now I would like to try to seed up the svf-programming a little bit, 4 minutes is quite long. Do you see any change for this or is it forlorn hope? Regards, Stefan Hi Stefan, Thanks for the information, I'm glad it worked out. I'm curious, does the version setting 4.00 work under Linux as well? In that case we could consider changing that value. That UrJTAG (at least under Linux) works together with the Cypress firmware isn't suprising because Kolja Waschk worked on both ;) Thanks, -- Hauke D On Mon, 5 Jul 2010, DISTEC Lugmair Stefan wrote: > Hi Hauke, > > thanks for your reply! Even if it was not a problem with VID/PID your > comment pointed me to the right direction. I compared the descriptors of > usb_jtag with the one from Altera's USB-Blaster and here is what I > found: > > The following line in trunk/c51/dscr.a51 was responsible for the error > message: > > VERSION = 0x0004 ; Product Version (4 indicates *BM device) > > This is read by the host as version 0.04. I compared with the Altera > Blaster and here we have version 4.00. > > After exchanging this line by the following one everything works fine: > VERSION = 0x0400 ; Product Version (4 indicates *BM device) > > I haven't found a good explanation for this. Looks like the problem lies > in the combination FTDI-driver & UrJtag (since the wrong version 0.04 > works under Linux). Somewhere the version is checked and somehow is > decided that version 0.04 can't set the latency timer. After a quick > scan of UrJtag's sources I would say that this "somewhere" is in the > FTDI driver (?) > > Regards, > Stefan > > > -----Ursprüngliche Nachricht----- > Von: Hauke D [mailto:ha...@ze...] > Gesendet: Sonntag, 4. Juli 2010 22:13 > An: ixo-jtag-devel Mailing List > Cc: DISTEC Lugmair Stefan > Betreff: Re: [ixo-jtag-devel] usbconn_ftd2xx_open(): Can't set latency timer. > > Hi Stefan, > > Unfortunately, this isn't my area of expertise, but maybe someone else on > the list can help? > > My only (possibly somewhat ignorant :) ) comments would be that it might > make sense to cross-post your question to the urjatg Forum/Lists - if you > haven't already done so - to see if it might be a problem there? > > Also, it might have something to do with the fact that although the > usb_jtag firmware exhibits the same behavior as the USB-Blaster, the VID > and PID of the USB device are not the same as Altera's... some licensing > issue I think. > > Regards, > -- Hauke D > > > On Tue, 29 Jun 2010, DISTEC Lugmair Stefan wrote: > >> >> Hello, >> >> When I download your FW to my Cypress chip it becomes a USB-Blaster as >> expected. Then under Linux I can program my Lattice CPLD with the >> SVF-Player of UrJtag (using the libftdi driver). It takes quite long >> (about 4 minutes), but it works reliably. >> >> However, when I want to do the same under Windows XP, I get the >> following error (the USB-Blaster is listed in the Device-Manager, so the >> driver seems properly installed): >> >> jtag> cable UsbBlaster >> Connected to libftd2xx driver. >> usbconn_ftd2xx_open(): Can't set latency timer. >> Error: Cable initialization failed! >> >> I tested with the original USB-Blaster from Altera and the Altera pod is >> recognized by the driver and programming of my CPLD is possible without >> any problems. >> >> There seems to be a problem when the libftd2xx driver connects to the >> Cypress chip. >> >> I would appreciate any help! >> >> Thanks, >> >> Stefan >> |
|
From: Hauke D <ha...@ze...> - 2010-07-05 20:16:38
|
Hi Stefan, Thanks for the information, I'm glad it worked out. I'm curious, does the version setting 4.00 work under Linux as well? In that case we could consider changing that value. That UrJTAG (at least under Linux) works together with the Cypress firmware isn't suprising because Kolja Waschk worked on both ;) Thanks, -- Hauke D On Mon, 5 Jul 2010, DISTEC Lugmair Stefan wrote: > Hi Hauke, > > thanks for your reply! Even if it was not a problem with VID/PID your > comment pointed me to the right direction. I compared the descriptors of > usb_jtag with the one from Altera's USB-Blaster and here is what I > found: > > The following line in trunk/c51/dscr.a51 was responsible for the error > message: > > VERSION = 0x0004 ; Product Version (4 indicates *BM device) > > This is read by the host as version 0.04. I compared with the Altera > Blaster and here we have version 4.00. > > After exchanging this line by the following one everything works fine: > VERSION = 0x0400 ; Product Version (4 indicates *BM device) > > I haven't found a good explanation for this. Looks like the problem lies > in the combination FTDI-driver & UrJtag (since the wrong version 0.04 > works under Linux). Somewhere the version is checked and somehow is > decided that version 0.04 can't set the latency timer. After a quick > scan of UrJtag's sources I would say that this "somewhere" is in the > FTDI driver (?) > > Regards, > Stefan > > > -----Ursprüngliche Nachricht----- > Von: Hauke D [mailto:ha...@ze...] > Gesendet: Sonntag, 4. Juli 2010 22:13 > An: ixo-jtag-devel Mailing List > Cc: DISTEC Lugmair Stefan > Betreff: Re: [ixo-jtag-devel] usbconn_ftd2xx_open(): Can't set latency timer. > > Hi Stefan, > > Unfortunately, this isn't my area of expertise, but maybe someone else on > the list can help? > > My only (possibly somewhat ignorant :) ) comments would be that it might > make sense to cross-post your question to the urjatg Forum/Lists - if you > haven't already done so - to see if it might be a problem there? > > Also, it might have something to do with the fact that although the > usb_jtag firmware exhibits the same behavior as the USB-Blaster, the VID > and PID of the USB device are not the same as Altera's... some licensing > issue I think. > > Regards, > -- Hauke D > > > On Tue, 29 Jun 2010, DISTEC Lugmair Stefan wrote: > >> >> Hello, >> >> When I download your FW to my Cypress chip it becomes a USB-Blaster as >> expected. Then under Linux I can program my Lattice CPLD with the >> SVF-Player of UrJtag (using the libftdi driver). It takes quite long >> (about 4 minutes), but it works reliably. >> >> However, when I want to do the same under Windows XP, I get the >> following error (the USB-Blaster is listed in the Device-Manager, so the >> driver seems properly installed): >> >> jtag> cable UsbBlaster >> Connected to libftd2xx driver. >> usbconn_ftd2xx_open(): Can't set latency timer. >> Error: Cable initialization failed! >> >> I tested with the original USB-Blaster from Altera and the Altera pod is >> recognized by the driver and programming of my CPLD is possible without >> any problems. >> >> There seems to be a problem when the libftd2xx driver connects to the >> Cypress chip. >> >> I would appreciate any help! >> >> Thanks, >> >> Stefan >> |
|
From: DISTEC L. S. <Lu...@di...> - 2010-07-05 16:04:55
|
Hi Hauke, thanks for your reply! Even if it was not a problem with VID/PID your comment pointed me to the right direction. I compared the descriptors of usb_jtag with the one from Altera's USB-Blaster and here is what I found: The following line in trunk/c51/dscr.a51 was responsible for the error message: VERSION = 0x0004 ; Product Version (4 indicates *BM device) This is read by the host as version 0.04. I compared with the Altera Blaster and here we have version 4.00. After exchanging this line by the following one everything works fine: VERSION = 0x0400 ; Product Version (4 indicates *BM device) I haven't found a good explanation for this. Looks like the problem lies in the combination FTDI-driver & UrJtag (since the wrong version 0.04 works under Linux). Somewhere the version is checked and somehow is decided that version 0.04 can't set the latency timer. After a quick scan of UrJtag's sources I would say that this "somewhere" is in the FTDI driver (?) Regards, Stefan -----Ursprüngliche Nachricht----- Von: Hauke D [mailto:ha...@ze...] Gesendet: Sonntag, 4. Juli 2010 22:13 An: ixo-jtag-devel Mailing List Cc: DISTEC Lugmair Stefan Betreff: Re: [ixo-jtag-devel] usbconn_ftd2xx_open(): Can't set latency timer. Hi Stefan, Unfortunately, this isn't my area of expertise, but maybe someone else on the list can help? My only (possibly somewhat ignorant :) ) comments would be that it might make sense to cross-post your question to the urjatg Forum/Lists - if you haven't already done so - to see if it might be a problem there? Also, it might have something to do with the fact that although the usb_jtag firmware exhibits the same behavior as the USB-Blaster, the VID and PID of the USB device are not the same as Altera's... some licensing issue I think. Regards, -- Hauke D On Tue, 29 Jun 2010, DISTEC Lugmair Stefan wrote: > > Hello, > > When I download your FW to my Cypress chip it becomes a USB-Blaster as > expected. Then under Linux I can program my Lattice CPLD with the > SVF-Player of UrJtag (using the libftdi driver). It takes quite long > (about 4 minutes), but it works reliably. > > However, when I want to do the same under Windows XP, I get the > following error (the USB-Blaster is listed in the Device-Manager, so the > driver seems properly installed): > > jtag> cable UsbBlaster > Connected to libftd2xx driver. > usbconn_ftd2xx_open(): Can't set latency timer. > Error: Cable initialization failed! > > I tested with the original USB-Blaster from Altera and the Altera pod is > recognized by the driver and programming of my CPLD is possible without > any problems. > > There seems to be a problem when the libftd2xx driver connects to the > Cypress chip. > > I would appreciate any help! > > Thanks, > > Stefan > > |
|
From: Hauke D <ha...@ze...> - 2010-07-04 20:13:26
|
Hi Stefan, Unfortunately, this isn't my area of expertise, but maybe someone else on the list can help? My only (possibly somewhat ignorant :) ) comments would be that it might make sense to cross-post your question to the urjatg Forum/Lists - if you haven't already done so - to see if it might be a problem there? Also, it might have something to do with the fact that although the usb_jtag firmware exhibits the same behavior as the USB-Blaster, the VID and PID of the USB device are not the same as Altera's... some licensing issue I think. Regards, -- Hauke D On Tue, 29 Jun 2010, DISTEC Lugmair Stefan wrote: > > Hello, > > When I download your FW to my Cypress chip it becomes a USB-Blaster as > expected. Then under Linux I can program my Lattice CPLD with the > SVF-Player of UrJtag (using the libftdi driver). It takes quite long > (about 4 minutes), but it works reliably. > > However, when I want to do the same under Windows XP, I get the > following error (the USB-Blaster is listed in the Device-Manager, so the > driver seems properly installed): > > jtag> cable UsbBlaster > Connected to libftd2xx driver. > usbconn_ftd2xx_open(): Can't set latency timer. > Error: Cable initialization failed! > > I tested with the original USB-Blaster from Altera and the Altera pod is > recognized by the driver and programming of my CPLD is possible without > any problems. > > There seems to be a problem when the libftd2xx driver connects to the > Cypress chip. > > I would appreciate any help! > > Thanks, > > Stefan > > |
|
From: DISTEC L. S. <Lu...@di...> - 2010-06-29 14:17:28
|
Hello, When I download your FW to my Cypress chip it becomes a USB-Blaster as expected. Then under Linux I can program my Lattice CPLD with the SVF-Player of UrJtag (using the libftdi driver). It takes quite long (about 4 minutes), but it works reliably. However, when I want to do the same under Windows XP, I get the following error (the USB-Blaster is listed in the Device-Manager, so the driver seems properly installed): jtag> cable UsbBlaster Connected to libftd2xx driver. usbconn_ftd2xx_open(): Can't set latency timer. Error: Cable initialization failed! I tested with the original USB-Blaster from Altera and the Altera pod is recognized by the driver and programming of my CPLD is possible without any problems. There seems to be a problem when the libftd2xx driver connects to the Cypress chip. I would appreciate any help! Thanks, Stefan |
|
From: Hauke D <ha...@ze...> - 2010-06-17 19:52:47
|
Hello Stany, Thanks very much for your contribution! I've committed it in revision 204. Regards, -- Hauke D On Mon, 14 Jun 2010, Stany wrote: > Hello, > > I have made a small modification to support 64bits versions of Xilinx's tools. > > I have tested it with ISE 12.1 32 and 64bits. It might interest someone : > > > Index: nexys2prog > =================================================================== > --- nexys2prog (revision 203) > +++ nexys2prog (working copy) > @@ -181,8 +181,8 @@ > $ise = qx(cd `dirname $ise`; /bin/pwd); > chomp $ise; > die "Cannot find Xilinx ISE installation directory.\n" > - if $ise !~ /ISE\/bin\/lin$/; > - $ise =~ s/\/bin\/lin$//; > + if $ise !~ /ISE\/bin\/lin(64)?$/; > + $ise =~ s/\/bin\/lin(64)?$//; > die "Cannot understand Xilinx ISE installation tree.\n" > if !-d "$ise/spartan3e/data" or !-f "$ise/xcf/data/xcf04s.bsd"; > $XILINX = $ise; > |
|
From: Stany <sta...@gm...> - 2010-06-14 20:30:04
|
Hello,
I have made a small modification to support 64bits versions of Xilinx's tools.
I have tested it with ISE 12.1 32 and 64bits. It might interest someone :
Index: nexys2prog
===================================================================
--- nexys2prog (revision 203)
+++ nexys2prog (working copy)
@@ -181,8 +181,8 @@
$ise = qx(cd `dirname $ise`; /bin/pwd);
chomp $ise;
die "Cannot find Xilinx ISE installation directory.\n"
- if $ise !~ /ISE\/bin\/lin$/;
- $ise =~ s/\/bin\/lin$//;
+ if $ise !~ /ISE\/bin\/lin(64)?$/;
+ $ise =~ s/\/bin\/lin(64)?$//;
die "Cannot understand Xilinx ISE installation tree.\n"
if !-d "$ise/spartan3e/data" or !-f "$ise/xcf/data/xcf04s.bsd";
$XILINX = $ise;
|
|
From: Hauke D <ha...@ze...> - 2010-05-27 22:01:26
|
Hello everyone, Welcome to the list, I just thought I'd try it out and use the oppertunity to make a small announcement :) I've just completed merging version 4.2.0 of the FPGA4U firmware (http://fpga4u.epfl.ch/wiki/FX2), which was originally branched from the Cypress FX2 firmware, into a branch of device/c51/ as device/fpga4u/ in the usb_jtag project. There is a README in the new branch with more information. My hope is that I can keep this branch somewhat in sync with the releases from FPGA4U, so that any updates and bugfixes can be merged between the branches. Regards, -- Hauke D |