Programmable Devices
CPLDs, FPGAs, SoC FPGAs, Configuration, and Transceivers
21327 Discussions

ERROR with programer

Altera_Forum
Honored Contributor II
2,871 Views

Hello everyone, i have trouble with programing of my EP3C16Q240, i have my own board (schematic is in attached PDF). If i use USB blaster, quartus 9.0 says this: 

 

Info: Started Programmer operation at Fri Dec 11 12:59:16 2009 

Info: Configuring device index 1 

Info: Device 1 contains JTAG ID code 0x020F20DD 

Error: CONF_DONE pin failed to go high in device 1 

Error: Operation failed 

Info: Ended Programmer operation at Fri Dec 11 12:59:17 2009 

 

but programing never start. If i use ByteBlasterII, everything is ok, i can programing my board. ConfDone goes up at the end. But i need USB blaster, because i wanna use Nios II. 

 

Please, what is wrong, do you have any idea? 

 

Thank you very much for your advice. 

 

Vaclav
0 Kudos
11 Replies
Altera_Forum
Honored Contributor II
1,620 Views

It's not necessary related to the reported problem, but the MSEL wiring is incorrect. MSEL should be hard wired to GND/VCCA.

0 Kudos
Altera_Forum
Honored Contributor II
1,620 Views

i use only jtag, in the sheet is: If you only use JTAG configuration connect the MSEL pins to GND. MSELs are connect to the GND.

0 Kudos
Altera_Forum
Honored Contributor II
1,620 Views

Your schematic shows 3 resistors each 10K between MSEL? and GND. 

This is not hard wired. 

you better use 0 Ohm jumpers instead of these resistors 

 

Another thing .... 

Pin 3 and 7 of your serial M25P40 configuration device are left floating, i would connect them to safe power levels instead of letting them float.  

and ... generating the 40MHz, does this work reliable ?
0 Kudos
Altera_Forum
Honored Contributor II
1,620 Views

yes, i have 10k between msel and gnd, i try connect msel to ground without resistors. Flash memory isnt on board now, i fill only jtag connector and of course resistor on others signals like confdone, nce, etc. It means i have there almost everything without flash memories

0 Kudos
Altera_Forum
Honored Contributor II
1,620 Views

I don't expect, that the 10k resistors at MSEL are causing problems, the FPGA has internal pull-down resistors in parallel. As most likely reason, USB Blaster doen't work due to signal integrity problems with the JTAG interface.

0 Kudos
Altera_Forum
Honored Contributor II
1,620 Views

yes, problem has usb blaster, but i dont know why and where, routes are cca 5cm, pull ups and pull downs are there. I think R at the MSEL are not source of problems, but i try remove it. Its really strange. 

 

Vaclav
0 Kudos
Altera_Forum
Honored Contributor II
1,620 Views

Hello, only for information, i received new programmer from the TERASIC, and my board can be programed. I try build a new board, a that is also ok. So 10k at MSEL cannot be wrong (i think that is not source of problems). But question is, why doesn't work with USB Blaster (rev. B) from the Altera?

0 Kudos
Altera_Forum
Honored Contributor II
1,620 Views

none of the USB Blaster Rev B we had is still used and all of them have been replaced by Rev. C, In some rare cases we had to replace the yellow flatcable with a normal ide cable, as used like with hard disk connectors.  

maybe the reason is as FvM already said due to SI issue and there was a reason to chance the revison of the usb blaster. 

if you want to give the usb blaster rev b a try with a ribbon cable, be hure that this cable is short, less than 10cm over all.
0 Kudos
Altera_Forum
Honored Contributor II
1,620 Views

i have usb blaster with the yellow cable, but terasic programmer has standard ide cable, but that is very strange. But i have on board only fpga and the interface to programming. Others IO are only on the pins (for whatever what i will be need). I think that is very simply, and routes from JTAG connector to FPGA are really short (about 5cm). But if the yelllow cable is the main reason, its very strange. BTW i used on jtag signals schotky diodes to procestion also.  

 

vaclav
0 Kudos
Altera_Forum
Honored Contributor II
1,620 Views

In most cases, the flexprint cable is simply broken. Revision B and flexprint are also different in terms of trace impedance, but I didn't yet experience programming failures from it. I remember, that it has been necessary to increase the TCK series termination inside the revision B USB Blaster for reliable operation with some boards. 

 

As a first step, you may want to try a short standard IDC cable (similar to the Terasic one) with the Altera USB Blaster. If it doesn't work, try a TCK series resistor in the USB Blaster of e.g. 33 or 47 ohm.
0 Kudos
Altera_Forum
Honored Contributor II
1,620 Views

so problem was in the programmer rev. B. thank you for advice, i replace yellow cable for standard ide cable and shorter, and everything is ok, Vaclav

0 Kudos
Reply