From: "Dave Brown" Newsgroups: comp.arch.fpga Subject: Xilinx .bit file format Date: Mon, 16 Jul 2001 11:57:17 -0600 Organization: NovAtel Inc. Lines: 12 Message-ID: <9iv9ro$old$1@pallas.novatel.ca> NNTP-Posting-Host: eag40753.corp.novatel.ca X-Trace: pallas.novatel.ca 995306168 25261 198.161.68.181 (16 Jul 2001 17:56:08 GMT) X-Complaints-To: usenet@news.novatel.ca NNTP-Posting-Date: 16 Jul 2001 17:56:08 GMT X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Path: chonsp.franklin.ch!pfaff.ethz.ch!news-zh.switch.ch!news.ifi.unizh.ch!news.imp.ch!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed.direct.ca!look.ca!hekyl.ab.tac.net!pallas.novatel.ca!not-for-mail Xref: chonsp.franklin.ch comp.arch.fpga:8168 I have a .bit file that I converted to a .hex file with PromGEN. When I look at this .hex file, I noticed there is only one 32 bit dummy word before the syncronization word. I read in XAPP176 (from the Xilinx website) that there are supposed to be 2 32 bit dummy words. Has anyone else had similar problems? Just curious, because we can't get this .bit file to load into the FPGA. Is there a definitive description somewhere of the header that a .bit file should have for a Spartan II? Thanks, Dave ###### From: Stephan Neuhold Newsgroups: comp.arch.fpga Subject: Re: Xilinx .bit file format Date: Tue, 17 Jul 2001 14:04:22 +0100 Organization: Xilinx,Inc Lines: 52 Message-ID: <3B5437D6.66677811@xilinx.com> References: <9iv9ro$old$1@pallas.novatel.ca> NNTP-Posting-Host: xukaesn0.xsj.xilinx.com Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="------------AC24FA98CA7B348B4191A893" X-Mailer: Mozilla 4.74 [en] (WinNT; U) X-Accept-Language: en,en-GB Path: chonsp.franklin.ch!pfaff.ethz.ch!news-zh.switch.ch!news.ifi.unizh.ch!news.imp.ch!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!out.nntp.be!propagator-dallas!news-in-dallas.newsfeeds.com!in.nntp.be!easynews!sjc-peer.news.verio.net!dfw-feed.news.verio.net!news.verio.net!nntp1.hal-pc.org!12.120.16.16.MISMATCH!attdl1!attdl2!attsl2!attla2!ip.att.net!newsgate.xilinx.com!cliff.xsj.xilinx.com!not-for-mail Xref: chonsp.franklin.ch comp.arch.fpga:8143 This is a multi-part message in MIME format. --------------AC24FA98CA7B348B4191A893 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi Dave, If you are loading the bitstream using master or slave serial mode then this should not make a difference. However, if you are using a uP to download the bitstream, I assume you are counting on a specified number of clock cycles. In this case changing the code of the uP will do the trick. My 2 cents worth. Stephan Dave Brown wrote: > I have a .bit file that I converted to a .hex file with PromGEN. When I look > at this .hex file, I noticed there is only one 32 bit dummy word before the > syncronization word. I read in XAPP176 (from the Xilinx website) that there > are supposed to be 2 32 bit dummy words. Has anyone else had similar > problems? Just curious, because we can't get this .bit file to load into the > FPGA. Is there a definitive description somewhere of the header that a .bit > file should have for a Spartan II? > Thanks, > Dave --------------AC24FA98CA7B348B4191A893 Content-Type: text/x-vcard; charset=us-ascii; name="stephan.neuhold.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Stephan Neuhold Content-Disposition: attachment; filename="stephan.neuhold.vcf" begin:vcard n:Neuhold;Stephan tel;work:+44 (0) 870 0735 576 x-mozilla-html:FALSE url:http://www.xilinx.com org:Xilinx UK;Customer Applications version:2.1 email;internet:stephan.neuhold@xilinx.com title:Customer Applications Engineer adr;quoted-printable:;;Benchmark House=0D=0A203 Brooklands Road=0D=0A;Weybridge;Surrey;KT13 0RH;United Kingom fn:Stephan Neuhold end:vcard --------------AC24FA98CA7B348B4191A893-- ###### From: Stephan Neuhold Newsgroups: comp.arch.fpga Subject: Re: Xilinx .bit file format Date: Tue, 17 Jul 2001 14:06:07 +0100 Organization: Xilinx,Inc Lines: 52 Message-ID: <3B54383F.34DF37CE@xilinx.com> References: <9iv9ro$old$1@pallas.novatel.ca> NNTP-Posting-Host: xukaesn0.xsj.xilinx.com Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="------------338F06582A94D51EF5B3B98D" X-Mailer: Mozilla 4.74 [en] (WinNT; U) X-Accept-Language: en,en-GB Path: chonsp.franklin.ch!pfaff.ethz.ch!news-zh.switch.ch!news.ifi.unizh.ch!news.imp.ch!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!netnews.com!xfer02.netnews.com!news.voicenet.com!nntp2.aus1.giganews.com!border1.nntp.aus1.giganews.com!nntp.giganews.com!nntp1.hal-pc.org!12.120.16.16.MISMATCH!attdl1!attdl2!attsl2!attla2!ip.att.net!newsgate.xilinx.com!cliff.xsj.xilinx.com!not-for-mail Xref: chonsp.franklin.ch comp.arch.fpga:8149 This is a multi-part message in MIME format. --------------338F06582A94D51EF5B3B98D Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi Dave, If you are loading the bitstream using master or slave serial mode then this should not make a difference. However, if you are using a uP to download the bitstream, I assume you are counting on a specified number of clock cycles. In this case changing the code of the uP will do the trick. My 2 cents worth. Stephan Dave Brown wrote: > I have a .bit file that I converted to a .hex file with PromGEN. When I look > at this .hex file, I noticed there is only one 32 bit dummy word before the > syncronization word. I read in XAPP176 (from the Xilinx website) that there > are supposed to be 2 32 bit dummy words. Has anyone else had similar > problems? Just curious, because we can't get this .bit file to load into the > FPGA. Is there a definitive description somewhere of the header that a .bit > file should have for a Spartan II? > Thanks, > Dave --------------338F06582A94D51EF5B3B98D Content-Type: text/x-vcard; charset=us-ascii; name="stephan.neuhold.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Stephan Neuhold Content-Disposition: attachment; filename="stephan.neuhold.vcf" begin:vcard n:Neuhold;Stephan tel;work:+44 (0) 870 0735 576 x-mozilla-html:FALSE url:http://www.xilinx.com org:Xilinx UK;Customer Applications version:2.1 email;internet:stephan.neuhold@xilinx.com title:Customer Applications Engineer adr;quoted-printable:;;Benchmark House=0D=0A203 Brooklands Road=0D=0A;Weybridge;Surrey;KT13 0RH;United Kingom fn:Stephan Neuhold end:vcard --------------338F06582A94D51EF5B3B98D-- ###### Path: chonsp.franklin.ch!not-for-mail From: Neil Franklin Newsgroups: comp.arch.fpga Subject: Re: Xilinx .bit file format Date: 17 Jul 2001 21:41:31 +0200 Organization: My own Private Self Lines: 18 Message-ID: <6usnfv9wd0.fsf@chonsp.franklin.ch> References: <9iv9ro$old$1@pallas.novatel.ca> NNTP-Posting-Host: chonsp.franklin.ch X-Trace: chonsp.franklin.ch 995398891 431 10.0.3.2 (17 Jul 2001 19:41:31 GMT) X-Complaints-To: news@chonsp.franklin.ch NNTP-Posting-Date: 17 Jul 2001 19:41:31 GMT X-Newsreader: Gnus v5.7/Emacs 20.4 Xref: chonsp.franklin.ch comp.arch.fpga:8214 "Dave Brown" writes: > I have a .bit file that I converted to a .hex file with PromGEN. When I look > at this .hex file, I noticed there is only one 32 bit dummy word before the > syncronization word. I read in XAPP176 (from the Xilinx website) that there > are supposed to be 2 32 bit dummy words. Has anyone else had similar > problems? Just curious, because we can't get this .bit file to load into the > FPGA. Is there a definitive description somewhere of the header that a .bit > file should have for a Spartan II? Try XAPP151. It only says Virtex/Virtex-E/Virtex-EM in it, but Spartan-II are identical to smaller Virtex. -- 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