mc_navman said:Have you got the drivers installed and working for your byteblaster?
try connecting to the jtag port of you chip and pressing the autodected hardware button it should then find your chip. Make sure that you have checked the box that says program/configure besdie the .pof file entry in the programmer window. Make sure that your design is compiled for the exact chip that you are using. it should show the same chip when you load the file into the programmer and when you use the autodetect button in the programmer.
mc_navman said:@ltera (And many other chip manufactures) provide the pins on their chips for a JTAG port which can be used for testing and programming of the chip. qu@rtus can use the JTAG port to program your chip, very useful for testing designs. The byte blaster normally would be connected to the JTAG port on your board, I think that you may need a .sof file to program your chip.
the POF file is used to program a serial config chip, if you are going to program your chip via JTAG then you need a .sof file. You need a Byteblaster II cable to program a serial config chip (I dont think you can use your MV) I am not famila with the details of the @ltera part you are using so I might be mistaken.
jay_ec_engg said:HI..
I also faced the same problem in my project.... but after a long time i found very strange slution.... which is slight rise in VCCIO ( 3.3 or 5) on JTAG pins.... instead of 3.3 try to increase ur voltage max upto 3.5... and see the LED condition with byteblaster.....
first check whether LED indication with byteblaster is showing ready condition or not ????
ok probable solutions are
(1) check supply voltage properly at each pin of JTAG....
(2) have u connected pins according to datasheet ??
(3) what about pull up resistors ??
(4) according to ur CPLD/FPGA , whether it is SRAM/ROM based , u have to click on configer/rpogram and u have to use .pof for SRAM based chip and .sof for ROM based....
this list will be too big...
give me ur spec...i've done R&D in this thing..... my problem got solved after 3 months..and thats also ... by increasing VCCIO from 3.3 to 3.45.. so check ur current and voltage specs..
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?