Sign in
Search Comp.Arch.FPGA
fpga by Keywords
Altera | ASIC | CPLD | Cyclone | DCM | DDR | DSP | Ethernet | ISE | JTAG | Linux | LVDS | Microblaze | ML310 | Modelsim | NIOS | OPB | PCI | Quartus | RocketIO | SDRAM | Spartan | Spartan3 | SRAM | Stratix | Verilog | VHDL | Virtex | Virtex-4 | Virtex-II | Xilinx | XST
Ads
See Also
Comp.Arch.FPGA | CPLD programming sequence XC9500
There are 3 messages in this thread.
You are currently looking at messages 0 to 3.
CPLD programming sequence XC9500 - gopal_amlekar - 2010-01-16 07:29:00
Hello, I want to understand a few things about CPLD programming. There is a configuration sequence followed for FPGA. For e.g. XAPP188 Table7 on page 11 shows the device configuration sequence to transfer a bitstream. Similarly, is there any sequence for CPLD XC9500? What I understood is that the .jed file is transferred instead of .bit filein the SHIFT-DR state. Is this correct? After transferring the .jed file does XC9500 also need the JSTARTinstruction and switching to Run-Test-Idle state? Is the entire .jed file transferred or there is some header or similarinformation which is skipped? Also, how to read the Device IDCODE of the CPLD? How to issue the IDCODEinstruction? Thanks for support... --------------------------------------- This message was sent using the comp.arch.fpga web interface onhttp://www.FPGARelated.com
Re: CPLD programming sequence XC9500 - Uwe Bonnes - 2010-01-16 08:23:00
gopal_amlekar <gopal_amlekar@n_o_s_p_a_m.yahoo.com> wrote: > Hello, > I want to understand a few things about CPLD programming. > There is a configuration sequence followed for FPGA. For e.g. XAPP188 Table > 7 on page 11 shows the device configuration sequence to transfer a bit > stream. > Similarly, is there any sequence for CPLD XC9500? > What I understood is that the .jed file is transferred instead of .bit file > in the SHIFT-DR state. Is this correct? > After transferring the .jed file does XC9500 also need the JSTART > instruction and switching to Run-Test-Idle state? > Is the entire .jed file transferred or there is some header or similar > information which is skipped? > Also, how to read the Device IDCODE of the CPLD? How to issue the IDCODE > instruction? The .jed describes a bitmap.The jedecfilehas to be interpreted first into a bitmap. The bitmap is then transfered in a complicated way into the CPLD. The procedures are described somehow in the 1532 Jedec files, in the files found when searching XILINX.com with "algorithm jedec" ("Device Programming Specification"). xc3sprog on sourceforge implements a reader for jedecfiles and and a XC95X(L|V) programmer with these documents and the sources found in the last naxjp version with sources (naxjp-079). Read the documents and the sources http://sourceforge.net/projects/xc3sprog/develop to understand what's going on. B.t.w., for the Coolrunner 2 the Jedecfile describes the bits in a logical order and before transfering in the XC3C CPLD the bits have to be scrambled in physical order with .map files for the appropriate device found in the Xilinx ISE/xbr/data folder. For basic JTAG experiments , start at www.fpga4fun.com/JTAG.html Bye -- Uwe Bonnes b...@elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------______________________________
Join the blogging team on FPGARelated.com and earn rewards! Details Here.
Re: CPLD programming sequence XC9500 - Uwe Bonnes - 2010-01-16 08:29:00
gopal_amlekar <gopal_amlekar@n_o_s_p_a_m.yahoo.com> wrote: > Hello, > I want to understand a few things about CPLD programming. > There is a configuration sequence followed for FPGA. For e.g. XAPP188 Table > 7 on page 11 shows the device configuration sequence to transfer a bit > stream. > Similarly, is there any sequence for CPLD XC9500? > What I understood is that the .jed file is transferred instead of .bit file > in the SHIFT-DR state. Is this correct? > After transferring the .jed file does XC9500 also need the JSTART > instruction and switching to Run-Test-Idle state? > Is the entire .jed file transferred or there is some header or similar > information which is skipped? > Also, how to read the Device IDCODE of the CPLD? How to issue the IDCODE > instruction? The .jed describes a bitmap.The jedecfile has to be interpreted first into a bitmap. The bitmap is then transfered in a complicated way into the CPLD. The procedures are described somehow in the 1532 Jedec files and in the files found when searching XILINX.com with "algorithm jedec" ("Device Programming Specification"). xc3sprog on sourceforge implements a reader for jedecfiles and a XC95X(L|V) programmer with these documents and the sources found in the last naxjp version with sources (naxjp-079). Read the documents and the sources http://sourceforge.net/projects/xc3sprog/develop to understand what's going on. B.t.w., for the Coolrunner 2 the Jedecfile describes the bits in a logical order and before transfering in the XC2C CPLD the bits have to be scrambled in physical order with .map files for the appropriate device found in the Xilinx ISE/xbr/data folder. For basic JTAG experiments , start at www.fpga4fun.com/JTAG.html Bye -- Uwe Bonnes b...@elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------