From: Newsgroups: comp.arch.fpga Subject: download bitstream to FPGA Date: 28 Aug 2001 06:15:00 GMT Organization: ERG CUHK Lines: 9 Message-ID: <9mfct4$o7s$1@eng-ser1.erg.cuhk.edu.hk> NNTP-Posting-Host: fraser.cse.cuhk.edu.hk X-Trace: eng-ser1.erg.cuhk.edu.hk 998979300 24828 137.189.90.232 (28 Aug 2001 06:15:00 GMT) X-Complaints-To: abuse@erg.cuhk.edu.hk NNTP-Posting-Date: 28 Aug 2001 06:15:00 GMT User-Agent: tin/1.4.5-20010409 ("One More Nightmare") (UNIX) (Linux/2.4.7 (i686)) Path: chonsp.franklin.ch!pfaff.ethz.ch!news-zh.switch.ch!newsfeed-zh.ip-plus.net!news.ip-plus.net!news.tesion.net!news.belwue.de!news.uni-ulm.de!rz.uni-karlsruhe.de!schlund.de!newsfeed01.sul.t-online.de!newsfeed00.sul.t-online.de!t-online.de!fr.usenet-edu.net!usenet-edu.net!news.stealth.net!newsgate.cuhk.edu.hk!news.cuhk.edu.hk!news.erg.cuhk.edu.hk!not-for-mail Xref: chonsp.franklin.ch comp.arch.fpga:9561 Hi, I want to download a bitstream (*.bit file) to a Xilinx FPGA (e.g. xcv600) through a DB9 serial cable (model: DLC4). Must I use the tools provided by Xilinx? Is there any possibility I can write a segment of codes to do this in my application? Thanks in advnce! ---- Brittle ###### From: "Fred" Newsgroups: comp.arch.fpga Subject: Re: download bitstream to FPGA Date: 28 Aug 2001 10:50:43 GMT Organization: XS4ALL Internet BV Lines: 14 Message-ID: <9mft23$e7i$1@news1.xs4all.nl> References: <9mfct4$o7s$1@eng-ser1.erg.cuhk.edu.hk> NNTP-Posting-Host: xs4.xs4all.nl X-Trace: news1.xs4all.nl 998995843 14578 194.109.6.45 (28 Aug 2001 10:50:43 GMT) X-Complaints-To: abuse@xs4all.nl NNTP-Posting-Date: 28 Aug 2001 10:50:43 GMT User-Agent: tin/pre-1.4-980514 (UNIX) (BSD/OS/4.0 (i386)) Path: chonsp.franklin.ch!pfaff.ethz.ch!news-zh.switch.ch!newsfeed-zh.ip-plus.net!news.ip-plus.net!news.tesion.net!news.belwue.de!news-stu1.dfn.de!news-mue1.dfn.de!news-nue1.dfn.de!uni-erlangen.de!newsfeeds.belnet.be!news.belnet.be!transit.news.xs4all.nl!not-for-mail Xref: chonsp.franklin.ch comp.arch.fpga:9544 khtsoi@pc90026.cse.cuhk.edu.hk wrote: > Hi, > I want to download a bitstream (*.bit file) to a Xilinx > FPGA (e.g. xcv600) through a DB9 serial cable (model: DLC4). > Must I use the tools provided by Xilinx? Is there any > possibility I can write a segment of codes to do this in > my application? Thanks in advnce! OK, this isn't exactly what you asked for, but perhaps it's of some use: [Xilinx FPGA Download Adapter & Linux-Software] http://members.surfeu.de/matthias.prinke/archives/xck.tar.gz Fred ###### From: Newsgroups: comp.arch.fpga Subject: Re: download bitstream to FPGA Date: 29 Aug 2001 03:07:42 GMT Organization: ERG CUHK Lines: 13 Message-ID: <9mhm9u$fml$1@eng-ser1.erg.cuhk.edu.hk> References: <9mfct4$o7s$1@eng-ser1.erg.cuhk.edu.hk> <9mft23$e7i$1@news1.xs4all.nl> NNTP-Posting-Host: fraser.cse.cuhk.edu.hk X-Trace: eng-ser1.erg.cuhk.edu.hk 999054462 16085 137.189.90.232 (29 Aug 2001 03:07:42 GMT) X-Complaints-To: abuse@erg.cuhk.edu.hk NNTP-Posting-Date: 29 Aug 2001 03:07:42 GMT User-Agent: tin/1.4.5-20010409 ("One More Nightmare") (UNIX) (Linux/2.4.7 (i686)) Path: chonsp.franklin.ch!pfaff.ethz.ch!news-zh.switch.ch!news-ge.switch.ch!newsfeed00.sul.t-online.de!t-online.de!skynet.be!skynet.be!news.netfront.net!newsgate.cuhk.edu.hk!news.cuhk.edu.hk!news.erg.cuhk.edu.hk!not-for-mail Xref: chonsp.franklin.ch comp.arch.fpga:9563 > OK, this isn't exactly what you asked for, but perhaps it's of some use: > [Xilinx FPGA Download Adapter & Linux-Software] > http://members.surfeu.de/matthias.prinke/archives/xck.tar.gz > Fred Thanks for the info. I am still looking for a way to download the bit file. I just wondering if the file format is not open. And nobody can do this except Xilinx and the licenced parties. So sad. It's not possible to require the client to have a copy of download program and the bit file can be changed s.t. cannot stored in ROM. ---- Brittle ###### Message-ID: <3B8C7902.C50D0A62@ieee.org> From: Lasse Langwadt Christensen X-Mailer: Mozilla 4.7 [en-gb] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 Newsgroups: comp.arch.fpga Subject: Re: download bitstream to FPGA References: <9mfct4$o7s$1@eng-ser1.erg.cuhk.edu.hk> <9mft23$e7i$1@news1.xs4all.nl> <9mhm9u$fml$1@eng-ser1.erg.cuhk.edu.hk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Lines: 27 NNTP-Posting-Host: 64.20.39.111 X-Complaints-To: abuse@prodigy.net X-Trace: newssvr15.news.prodigy.com 999061753 6555851 64.20.39.111 (Wed, 29 Aug 2001 01:09:13 EDT) NNTP-Posting-Date: Wed, 29 Aug 2001 01:09:13 EDT Organization: Prodigy Internet http://www.prodigy.com Date: Wed, 29 Aug 2001 05:09:13 GMT Path: chonsp.franklin.ch!pfaff.ethz.ch!news-zh.switch.ch!bromo.switch.ch!news-ge.switch.ch!news.mailgate.org!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!cpk-news-hub1.bbnplanet.com!news.gtei.net!newscon02.news.prodigy.com!newsmst01.news.prodigy.com!prodigy.com!postmaster.news.prodigy.com!newssvr15.news.prodigy.com.POSTED!not-for-mail Xref: chonsp.franklin.ch comp.arch.fpga:9580 khtsoi@pc90026.cse.cuhk.edu.hk wrote: > > > OK, this isn't exactly what you asked for, but perhaps it's of some use: > > [Xilinx FPGA Download Adapter & Linux-Software] > > http://members.surfeu.de/matthias.prinke/archives/xck.tar.gz > > > Fred > > Thanks for the info. I am still looking for a way to download the bit file. > I just wondering if the file format is not open. And nobody can do this > except Xilinx and the licenced parties. So sad. It's not possible to require > the client to have a copy of download program and the bit file can be > changed s.t. cannot stored in ROM. > > ---- Brittle The xilinx can convert the bit file to several different formats, they even have a app. note on how to use a cpu via a few GPIOs to configure an FPGA, and I think even c sourcecode. Or just look at the datasheet for a configuration prom, and simulate that, -Lasse -- Lasse Langwadt Christensen, -- A Dane in Phoenix, Arizona ###### From: Philip Freidin Newsgroups: comp.arch.fpga Subject: Re: download bitstream to FPGA Organization: Fliptronics Reply-To: philip@fliptronics.com Message-ID: <1uhpotsfvcgeb4o9vaebhj31gi8amf1tvf@4ax.com> References: <9mfct4$o7s$1@eng-ser1.erg.cuhk.edu.hk> <9mft23$e7i$1@news1.xs4all.nl> <9mhm9u$fml$1@eng-ser1.erg.cuhk.edu.hk> X-Newsreader: Forte Agent 1.8/32.548 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Lines: 31 Date: Wed, 29 Aug 2001 03:52:07 -0700 NNTP-Posting-Host: 216.103.85.188 X-Complaints-To: abuse@pacbell.net X-Trace: news.pacbell.net 999082342 216.103.85.188 (Wed, 29 Aug 2001 03:52:22 PDT) NNTP-Posting-Date: Wed, 29 Aug 2001 03:52:22 PDT Path: chonsp.franklin.ch!pfaff.ethz.ch!news-zh.switch.ch!news-ge.switch.ch!news.maxwell.syr.edu!newsfeed.stanford.edu!headwall.stanford.edu!news-out.nibble.net!hub1.nntpserver.com!news-out.spamkiller.net!propagator-la!news-in.superfeed.net!news-in-la.newsfeeds.com!cyclone-sf.pbi.net!206.13.28.143!news.pacbell.net.POSTED!not-for-mail Xref: chonsp.franklin.ch comp.arch.fpga:9585 On 29 Aug 2001 03:07:42 GMT, wrote: >Thanks for the info. I am still looking for a way to download the bit file. This is documented in Xilinx data sheets, in Xilinx App Notes, and in the Xilinx on-line documentation. You couldn't ask for more. (well maybe you could, but I dont know why) >I just wondering if the file format is not open. While the exact details of what each bit in the bitstream represents is proprietory, you do not need this information to download a design into your FPGA. The bitstream is created by the P&R tools, and the resulting file can be copied into a serial or parallel EPROM/EEPROM, or saved on disk, or stored any other way. The documentation clearly describes the format of the data, and how it should be presented to the FPGA. >And nobody can do this except Xilinx and the licenced parties. Hardly ! All of Xilinx's tens of thousands of customers do this every day. >So sad. It's not possible to require the client to have a copy of >download program and the bit file can be changed s.t. cannot >stored in ROM. Well, this is just plain wrong. ( ? s.t. ?) >---- Brittle Philip Philip Freidin Fliptronics ###### From: Alan Nishioka Newsgroups: comp.arch.fpga Subject: Re: download bitstream to FPGA Date: Wed, 29 Aug 2001 08:53:17 -0700 Organization: http://extra.newsguy.com Lines: 54 Message-ID: <3B8D0FED.55620A@accom.com> References: <9mfct4$o7s$1@eng-ser1.erg.cuhk.edu.hk> NNTP-Posting-Host: charon.accom.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U) X-Accept-Language: en Path: chonsp.franklin.ch!pfaff.ethz.ch!news-zh.switch.ch!news-ge.switch.ch!news.maxwell.syr.edu!nntp.abs.net!pln-e!spln!dex!extra.newsguy.com!newsp.newsguy.com!enews2 Xref: chonsp.franklin.ch comp.arch.fpga:9581 I could not find the *.bit file explicitly documented anywhere. I asked this newsgroup and didn't get any responses. However, the format is pretty simple. It uses keys and lengths to divide the file. 2 bytes length 0x0009 (big endian) 9 bytes some sort of header (the length given above) 2 bytes length 0x0001 1 byte key 0x61 2 bytes length 0x000a 10 bytes string giving design name 1 byte key 0x62 2 bytes length 0x000c 12 bytes string giving part name 1 byte key 0x63 2 bytes length 0x000b 11 bytes string giving date 1 byte key 0x64 2 bytes length 0x0009 9 bytes string giving time 1 byte key 0x65 2 bytes length 0x000c9090 8233440 bytes raw bit stream starting with 0xffffffff aa995566 sync word documented below. Once you get the raw bits, XAPP138 "Virtex FPGA Series Configuration and Readback" and XAPP139 "Configuration and Readback of Virtex FPGAs using (JTAG) Boundary-Scan will tell you what to do with them. Unfortunately, I don't know how to drive a DL4 cable. My application is embedded so I have direct access to the JTAG lines. Alan Nishioka alann@accom.com khtsoi@pc90026.cse.cuhk.edu.hk wrote: > Hi, > > I want to download a bitstream (*.bit file) to a Xilinx > FPGA (e.g. xcv600) through a DB9 serial cable (model: DLC4). > Must I use the tools provided by Xilinx? Is there any > possibility I can write a segment of codes to do this in > my application? Thanks in advnce! > > ---- Brittle ###### Path: chonsp.franklin.ch!not-for-mail From: Neil Franklin Newsgroups: comp.arch.fpga Subject: Re: download bitstream to FPGA Date: 29 Aug 2001 22:17:39 +0200 Organization: My own Private Self Lines: 34 Message-ID: <6uwv3mlixo.fsf@chonsp.franklin.ch> References: <9mfct4$o7s$1@eng-ser1.erg.cuhk.edu.hk> <3B8D0FED.55620A@accom.com> NNTP-Posting-Host: chonsp.franklin.ch X-Trace: chonsp.franklin.ch 999116259 4972 10.0.3.2 (29 Aug 2001 20:17:39 GMT) X-Complaints-To: news@chonsp.franklin.ch NNTP-Posting-Date: 29 Aug 2001 20:17:39 GMT X-Newsreader: Gnus v5.7/Emacs 20.4 Xref: chonsp.franklin.ch comp.arch.fpga:9588 Alan Nishioka writes: > However, the format is pretty simple. It uses keys and lengths to > divide the file. > > 1 byte key 0x65 > 2 bytes length 0x000c9090 > 8233440 bytes raw bit stream starting with 0xffffffff aa995566 sync > word documented below. There is at least one error in that. The config data comes in 3 chunks: CLBs+IOBs+BRAMctrl, and then 2 columns of BRAMdata (for standard Virtex that is, more BRAMdata chunks for V-E and V-EM). The basic structure of the bitstream format is documented in: XAPP151 Virtex Series Configuration Architecture User Guide http://www.xilinx.com/xapp/xapp151.pdf The info there is even enough to read out and alter LUT and BRAM data bits and regenerate the CRCs. > Once you get the raw bits, XAPP138 "Virtex FPGA Series Configuration and > Readback" and XAPP139 "Configuration and Readback of Virtex FPGAs using > (JTAG) Boundary-Scan will tell you what to do with them. Both are a good read. http://www.xilinx.com/xapp/xapp138.pdf http://www.xilinx.com/xapp/xapp139.pdf -- Neil Franklin, neil@franklin.ch.remove http://neil.franklin.ch/ Hacker, Unix Guru, El Eng HTL/BSc, Sysadmin, Archer, Roleplayer - Intellectual Property is Intellectual Robbery ###### From: Alan Nishioka Newsgroups: comp.arch.fpga Subject: Re: download bitstream to FPGA Date: Wed, 29 Aug 2001 14:37:46 -0700 Organization: http://extra.newsguy.com Lines: 24 Message-ID: <3B8D60AA.61A00B55@accom.com> References: <9mfct4$o7s$1@eng-ser1.erg.cuhk.edu.hk> <3B8D0FED.55620A@accom.com> <6uwv3mlixo.fsf@chonsp.franklin.ch> NNTP-Posting-Host: charon.accom.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U) X-Accept-Language: en Path: chonsp.franklin.ch!pfaff.ethz.ch!news-zh.switch.ch!news-ge.switch.ch!newsfeed.mathworks.com!pln-e!spln!dex!extra.newsguy.com!newsp.newsguy.com!enews3 Xref: chonsp.franklin.ch comp.arch.fpga:9652 Neil Franklin wrote: > Alan Nishioka writes: > > > However, the format is pretty simple. It uses keys and lengths to > > divide the file. > > > > 1 byte key 0x65 > > 2 bytes length 0x000c9090 > > 8233440 bytes raw bit stream starting with 0xffffffff aa995566 sync > > word documented below. > > There is at least one error in that. The config data comes in 3 > chunks: CLBs+IOBs+BRAMctrl, and then 2 columns of BRAMdata (for > standard Virtex that is, more BRAMdata chunks for V-E and V-EM). I don't see the error. What I am describing is the format of the .bit file that bitgen produces. What XAPP151 describes is the format of the bit stream that is part of that file. Alan Nishioka alann@accom.com ###### From: Newsgroups: comp.arch.fpga Subject: Re: download bitstream to FPGA Date: 30 Aug 2001 04:16:04 GMT Organization: ERG CUHK Lines: 43 Message-ID: <9mkem4$h9$1@eng-ser1.erg.cuhk.edu.hk> References: <9mfct4$o7s$1@eng-ser1.erg.cuhk.edu.hk> <9mft23$e7i$1@news1.xs4all.nl> <9mhm9u$fml$1@eng-ser1.erg.cuhk.edu.hk> <1uhpotsfvcgeb4o9vaebhj31gi8amf1tvf@4ax.com> NNTP-Posting-Host: fraser.cse.cuhk.edu.hk X-Trace: eng-ser1.erg.cuhk.edu.hk 999144964 553 137.189.90.232 (30 Aug 2001 04:16:04 GMT) X-Complaints-To: abuse@erg.cuhk.edu.hk NNTP-Posting-Date: 30 Aug 2001 04:16:04 GMT User-Agent: tin/1.4.5-20010409 ("One More Nightmare") (UNIX) (Linux/2.4.7 (i686)) Path: chonsp.franklin.ch!pfaff.ethz.ch!news-zh.switch.ch!news-ge.switch.ch!news.maxwell.syr.edu!newsfeed.dacom.co.kr!news-xfer.nuri.net!news.hk.linkage.net!newsgate.cuhk.edu.hk!news.cuhk.edu.hk!news.erg.cuhk.edu.hk!not-for-mail Xref: chonsp.franklin.ch comp.arch.fpga:9624 Philip Freidin wrote: > On 29 Aug 2001 03:07:42 GMT, wrote: >>Thanks for the info. I am still looking for a way to download the bit file. > This is documented in Xilinx data sheets, in Xilinx App Notes, and in > the Xilinx on-line documentation. You couldn't ask for more. (well maybe > you could, but I dont know why) >>I just wondering if the file format is not open. > While the exact details of what each bit in the bitstream represents is > proprietory, you do not need this information to download a design into > your FPGA. The bitstream is created by the P&R tools, and the resulting > file can be copied into a serial or parallel EPROM/EEPROM, or saved > on disk, or stored any other way. The documentation clearly describes > the format of the data, and how it should be presented to the FPGA. >>And nobody can do this except Xilinx and the licenced parties. > Hardly ! All of Xilinx's tens of thousands of customers do this every day. >>So sad. It's not possible to require the client to have a copy of >>download program and the bit file can be changed s.t. cannot >>stored in ROM. > Well, this is just plain wrong. ( ? s.t. ?) >>---- Brittle > Philip > Philip Freidin > Fliptronics Thank you all very much for the useful info. I have one more question. Actually I know how to download using the JTAG pins. But once I check the raw bit file, I found that there is some text string in the header (e.g. Xilinx, xcv300, etc.). I just not sure if this should be downloaded to the FPGA and for what? If I download the wrong data/header, will the FPGA be demaged? For these questions, I just want to make sure it works before actually perform the download. I cannot affort to demage the proto board I am using :) anyway, thanks again ---- Brittle ###### From: Newsgroups: comp.arch.fpga Subject: Re: download bitstream to FPGA Date: 30 Aug 2001 04:19:00 GMT Organization: ERG CUHK Lines: 10 Message-ID: <9mkerk$h9$2@eng-ser1.erg.cuhk.edu.hk> References: <9mfct4$o7s$1@eng-ser1.erg.cuhk.edu.hk> <9mft23$e7i$1@news1.xs4all.nl> <9mhm9u$fml$1@eng-ser1.erg.cuhk.edu.hk> <1uhpotsfvcgeb4o9vaebhj31gi8amf1tvf@4ax.com> NNTP-Posting-Host: fraser.cse.cuhk.edu.hk X-Trace: eng-ser1.erg.cuhk.edu.hk 999145140 553 137.189.90.232 (30 Aug 2001 04:19:00 GMT) X-Complaints-To: abuse@erg.cuhk.edu.hk NNTP-Posting-Date: 30 Aug 2001 04:19:00 GMT User-Agent: tin/1.4.5-20010409 ("One More Nightmare") (UNIX) (Linux/2.4.7 (i686)) Path: chonsp.franklin.ch!pfaff.ethz.ch!news-zh.switch.ch!news-ge.switch.ch!enews.sgi.com!news-xfer.nuri.net!news.hk.linkage.net!newsgate.cuhk.edu.hk!news.cuhk.edu.hk!news.erg.cuhk.edu.hk!not-for-mail Xref: chonsp.franklin.ch comp.arch.fpga:9628 >>So sad. It's not possible to require the client to have a copy of >>download program and the bit file can be changed s.t. cannot >>stored in ROM. > Well, this is just plain wrong. ( ? s.t. ?) s.t. = such that forgive my poor English ---- Brittle ###### From: Philip Freidin Newsgroups: comp.arch.fpga Subject: Re: download bitstream to FPGA Organization: Fliptronics Reply-To: philip@fliptronics.com Message-ID: <89proto0r0ijt86hjphb4bs48rbv3ljsq8@4ax.com> References: <9mfct4$o7s$1@eng-ser1.erg.cuhk.edu.hk> <9mft23$e7i$1@news1.xs4all.nl> <9mhm9u$fml$1@eng-ser1.erg.cuhk.edu.hk> <1uhpotsfvcgeb4o9vaebhj31gi8amf1tvf@4ax.com> <9mkem4$h9$1@eng-ser1.erg.cuhk.edu.hk> X-Newsreader: Forte Agent 1.8/32.548 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Lines: 50 Date: Thu, 30 Aug 2001 00:32:22 -0700 NNTP-Posting-Host: 216.103.85.188 X-Complaints-To: abuse@pacbell.net X-Trace: nnrp5-w.sbc.net 999156758 216.103.85.188 (Thu, 30 Aug 2001 00:32:38 PDT) NNTP-Posting-Date: Thu, 30 Aug 2001 00:32:38 PDT Path: chonsp.franklin.ch!pfaff.ethz.ch!news-zh.switch.ch!news.ifi.unizh.ch!29703!news.imp.ch!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!feeder.via.net!cyclone-sf.pbi.net!206.13.28.183!nnrp5-w.sbc.net.POSTED!not-for-mail Xref: chonsp.franklin.ch comp.arch.fpga:9649 On 30 Aug 2001 04:16:04 GMT, wrote: >Thank you all very much for the useful info. I have one more question. >Actually I know how to download using the JTAG pins. But once I check >the raw bit file, I found that there is some text string in the header >(e.g. Xilinx, xcv300, etc.). I just not sure if this should be downloaded >to the FPGA and for what? You are right to question this. You should not download the header information. If you go look at Alan Nishioka's article, he gives a good description of the stuff in the file. The stuff that is the raw bit stream (from his article) >1 byte key 0x65 >2 bytes length 0x000c9090 >8233440 bytes raw bit stream starting with 0xffffffff aa995566 sync >word documented below. is the stuff for actual download. i.e. the first 32 bits are all '1' , then the AA995566 sync word, then all the rest of the raw bit stream. You may also find the following brilliant article of use, although it is addressing a different issue. http://www.fpga-faq.com/archives/33100.html#33108 By the way, all this sync word stuff assumes you are working with Spartan-II or one of the Virtex families. If it is any XC3K or XC4K or Spartan device, the .BIT file format as described is still correct, but the content of the raw bit stream section looks different, as it does not have a sync word. > If I download the wrong data/header, will the >FPGA be demaged? Yes, it could. But the reality is that (assuming S-II or V family device) unless you have something that looks like the Sync Word in the data that shouldn't be loaded, you will be ok, because it will never get into the configuration state. Most of the header you are skipping is text, and the sync word includes AA and 99, neither of wich occur in normal 7 bit ASCII stored in 8 bit bytes. On the older XC3K and XC4K products, there is protection, but not as good. >For these questions, I just want to make sure it works >before actually perform the download. I cannot affort to demage the >proto board I am using :) anyway, thanks again > >---- Brittle Philip Freidin Fliptronics ###### From: Newsgroups: comp.arch.fpga Subject: Re: download bitstream to FPGA Date: 30 Aug 2001 09:03:14 GMT Organization: ERG CUHK Lines: 7 Message-ID: <9mkvgi$6e4$1@eng-ser1.erg.cuhk.edu.hk> References: <9mfct4$o7s$1@eng-ser1.erg.cuhk.edu.hk> <9mft23$e7i$1@news1.xs4all.nl> <9mhm9u$fml$1@eng-ser1.erg.cuhk.edu.hk> <1uhpotsfvcgeb4o9vaebhj31gi8amf1tvf@4ax.com> <9mkem4$h9$1@eng-ser1.erg.cuhk.edu.hk> <89proto0r0ijt86hjphb4bs48rbv3ljsq8@4ax.com> NNTP-Posting-Host: fraser.cse.cuhk.edu.hk X-Trace: eng-ser1.erg.cuhk.edu.hk 999162194 6596 137.189.90.232 (30 Aug 2001 09:03:14 GMT) X-Complaints-To: abuse@erg.cuhk.edu.hk NNTP-Posting-Date: 30 Aug 2001 09:03:14 GMT User-Agent: tin/1.4.5-20010409 ("One More Nightmare") (UNIX) (Linux/2.4.7 (i686)) Path: chonsp.franklin.ch!pfaff.ethz.ch!news-zh.switch.ch!news-ge.switch.ch!newsfeed00.sul.t-online.de!t-online.de!news-lei1.dfn.de!news-was.dfn.de!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!feeder.kornet.net!news-xfer.nuri.net!news.hk.linkage.net!newsgate.cuhk.edu.hk!news.cuhk.edu.hk!news.erg.cuhk.edu.hk!not-for-mail Xref: chonsp.franklin.ch comp.arch.fpga:9631 Hi, I will test it asap. Thank you all. I will report the results. ---- Brittle ###### Path: chonsp.franklin.ch!not-for-mail From: Neil Franklin Newsgroups: comp.arch.fpga Subject: Re: download bitstream to FPGA Date: 31 Aug 2001 23:49:30 +0200 Organization: My own Private Self Lines: 33 Message-ID: <6uzo8fsxw5.fsf@chonsp.franklin.ch> References: <9mfct4$o7s$1@eng-ser1.erg.cuhk.edu.hk> <3B8D0FED.55620A@accom.com> <6uwv3mlixo.fsf@chonsp.franklin.ch> <3B8D60AA.61A00B55@accom.com> NNTP-Posting-Host: chonsp.franklin.ch X-Trace: chonsp.franklin.ch 999294570 524 10.0.3.2 (31 Aug 2001 21:49:30 GMT) X-Complaints-To: news@chonsp.franklin.ch NNTP-Posting-Date: 31 Aug 2001 21:49:30 GMT X-Newsreader: Gnus v5.7/Emacs 20.4 Xref: chonsp.franklin.ch comp.arch.fpga:9653 Alan Nishioka writes: > Neil Franklin wrote: > > > Alan Nishioka writes: > > > > > However, the format is pretty simple. It uses keys and lengths to > > > divide the file. > > > > > > 1 byte key 0x65 > > > 2 bytes length 0x000c9090 > > > 8233440 bytes raw bit stream starting with 0xffffffff aa995566 sync > > > word documented below. > > > > There is at least one error in that. The config data comes in 3 > > chunks: CLBs+IOBs+BRAMctrl, and then 2 columns of BRAMdata (for > > standard Virtex that is, more BRAMdata chunks for V-E and V-EM). > > I don't see the error. What I am describing is the format of the .bit file > that bitgen produces. What XAPP151 describes is the format of the bit stream > that is part of that file. After re-reading your post I think I misunderstood your .bit to be equal to the XAPP151 bit stream. Now it seems you are describing something as .bit something that encapsulates an bit stream. Will have to have an detailled look at an .bit file. -- Neil Franklin, neil@franklin.ch.remove http://neil.franklin.ch/ Hacker, Unix Guru, El Eng HTL/BSc, Sysadmin, Archer, Roleplayer - Intellectual Property is Intellectual Robbery