Add initial files for direct FPGA programming

8 files changed, 902 insertions, 0 deletions

diff --git a/fpga/xilinx/programmer/bit2svf/bitinfo-0.3/Bitfileheader b/fpga/xilinx/programmer/bit2svf/bitinfo-0.3/Bitfileheader
new file mode 100644
index 0000000..cf579cf
--- /dev/null
+++ b/fpga/xilinx/programmer/bit2svf/bitinfo-0.3/Bitfileheader
@@ -0,0 +1,101 @@
+05/23/2001
+
+Bit file header specification
+
+
+A bit file has two sections.  The first section is a variable length header. 
+The second section is a fixed-length bitstream which is downloaded into the
+FPGA.  The format of the bitstream can be found in the data book for the
+appropriate FPGA, but the format of the header is not anywhere that I have
+found in the Xilinx literature.  This document describes the structure the
+bit file header for the XC4005XL and XC4005E FPGAs.  This structure may or
+may not be appropriate for headers of bit files for other Xilinx FPGAs.
+
+Preamble: unknown values
+
+The bit files generated with xmake for the XC4005XL and XC4005E FPGAs all
+begin with the following sequence of 13 bytes (shown here in hexadecimal): 
+00 09 0F F0 0F F0 0F F0 0F F0 00 00 01
+
+Part "a": source file
+
+Parts a through e follow the same general format.  First the part begins
+with the ASCII letter of the section followed by a NULL (00h).  For example,
+part c begins with hexadecimal 63 00, since 63 is ASCII for "c".  The next
+byte is a length byte, giving the length of the string to follow plus 1. 
+The length is followed by an ASCII string, and that string is followed by a
+NULL (00h).  If there is no string at all in the section, then the length
+byte is 0 and there is no NULL termination.
+
+Part a of the header tells the filename used to generate the bit file.  For
+example, if the file "xc4005.ncd" was used to generate the bit file then the
+header will be:
+"a" 00 0B "xc4005.ncd" 00
+
+Convert the quoted letters into their ASCII representation.
+
+Part "b": part name
+
+Part b follows the same format as part a.  The string identifies the part
+and package of the target device.  In my limited tests this string has
+always been "4005xlpc84" or "4005epc84".
+
+Part "c": date
+
+Part c follows the same format as part a.  The string gives the date the bit
+file was generated, for example "2001/03/12".
+
+Part "d": time
+
+Part d follows the same format as part a.  The string gives the time the bit
+file was generated, for example "20:43:04".
+
+Part "e": unknown
+
+Part e seems to follow the same format as part a.  However, in my tests this
+part has always been empty.  In other words, the entire part is hexadecimal
+65 00 00.
+
+Final part: bitstream length
+
+The final part of the header gives the length of the bitstream to follow, in
+binary.  This is two bytes long for the XC4005XL and XC4005E parts, but it
+is probable that this length will be more than two bytes long for larger
+Xilinx parts.
+
+For example, the XC4005XL part has a 18995 byte long bitstream.  The final
+two bytes of the header are hexadecimal 4A33, which is 18995 when converted
+to decimal.
+
+Immediately following the final part of the header, the bitstream begins. 
+The file ends immediately after the bitstream.
+
+
+05/24/2001
+UPDATE:
+
+I examined the bit file headers for two more Xilinx parts, a Spartan part
+and 1000 gate Virtex part.  From this I determined my understanding of the
+sections was a little off.  The section letters FOLLOW the sections.  So the
+unknown garbage at the beginning (which was the same for all parts) is
+section a, the part name was section b, and so on.  The time was section e,
+and the 00 following the 65 00 was the beginning of the length.  So the
+length is actually three bytes long.  This gives a maximum bitstream length
+of FFFFFFh, or 16,777,215 bytes.
+
+09/10/2002
+UPDATE:
+
+I got an email message from "Stephen from Australia" who set me straight on
+the format of the bit file header.  He pointed me to the online FPGA FAQ,
+which gives an alternative view of how the header is laid out.  Each section
+letter is a single byte.  The 00 which follows the section letter is
+actually the first byte of a two-byte size.  The final four bytes of the
+header make up a four-byte size.  After considering the difference between
+the two specifications, I realized that even if the FAQ is wrong it wouldn't
+hurt to parse it that way since the first byte of the length would always be
+00.  And it seems more aesthetically pleasing to have a four-byte bitstream
+length than a three-byte bitstream length.  I have altered bitfile.c to
+reflect the change in my understanding of the format.
+
+Thanks for setting me straight, Steve!
diff --git a/fpga/xilinx/programmer/bit2svf/bitinfo-0.3/COPYING b/fpga/xilinx/programmer/bit2svf/bitinfo-0.3/COPYING
new file mode 100644
index 0000000..5b6e7c6
--- /dev/null
+++ b/fpga/xilinx/programmer/bit2svf/bitinfo-0.3/COPYING
@@ -0,0 +1,340 @@
+		    GNU GENERAL PUBLIC LICENSE
+		       Version 2, June 1991
+
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.
+                       59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+			    Preamble
+
+  The licenses for most software are designed to take away your
+freedom to share and change it.  By contrast, the GNU General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users.  This
+General Public License applies to most of the Free Software
+Foundation's software and to any other program whose authors commit to
+using it.  (Some other Free Software Foundation software is covered by
+the GNU Library General Public License instead.)  You can apply it to
+your programs, too.
+
+  When we speak of free software, we are referring to freedom, not
+price.  Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it
+in new free programs; and that you know you can do these things.
+
+  To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+  For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have.  You must make sure that they, too, receive or can get the
+source code.  And you must show them these terms so they know their
+rights.
+
+  We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+  Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software.  If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors' reputations.
+
+  Finally, any free program is threatened constantly by software
+patents.  We wish to avoid the danger that redistributors of a free
+program will individually obtain patent licenses, in effect making the
+program proprietary.  To prevent this, we have made it clear that any
+patent must be licensed for everyone's free use or not licensed at all.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.
+
+		    GNU GENERAL PUBLIC LICENSE
+   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+  0. This License applies to any program or other work which contains
+a notice placed by the copyright holder saying it may be distributed
+under the terms of this General Public License.  The "Program", below,
+refers to any such program or work, and a "work based on the Program"
+means either the Program or any derivative work under copyright law:
+that is to say, a work containing the Program or a portion of it,
+either verbatim or with modifications and/or translated into another
+language.  (Hereinafter, translation is included without limitation in
+the term "modification".)  Each licensee is addressed as "you".
+
+Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope.  The act of
+running the Program is not restricted, and the output from the Program
+is covered only if its contents constitute a work based on the
+Program (independent of having been made by running the Program).
+Whether that is true depends on what the Program does.
+
+  1. You may copy and distribute verbatim copies of the Program's
+source code as you receive it, in any medium, provided that you
+conspicuously and appropriately publish on each copy an appropriate
+copyright notice and disclaimer of warranty; keep intact all the
+notices that refer to this License and to the absence of any warranty;
+and give any other recipients of the Program a copy of this License
+along with the Program.
+
+You may charge a fee for the physical act of transferring a copy, and
+you may at your option offer warranty protection in exchange for a fee.
+
+  2. You may modify your copy or copies of the Program or any portion
+of it, thus forming a work based on the Program, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+    a) You must cause the modified files to carry prominent notices
+    stating that you changed the files and the date of any change.
+
+    b) You must cause any work that you distribute or publish, that in
+    whole or in part contains or is derived from the Program or any
+    part thereof, to be licensed as a whole at no charge to all third
+    parties under the terms of this License.
+
+    c) If the modified program normally reads commands interactively
+    when run, you must cause it, when started running for such
+    interactive use in the most ordinary way, to print or display an
+    announcement including an appropriate copyright notice and a
+    notice that there is no warranty (or else, saying that you provide
+    a warranty) and that users may redistribute the program under
+    these conditions, and telling the user how to view a copy of this
+    License.  (Exception: if the Program itself is interactive but
+    does not normally print such an announcement, your work based on
+    the Program is not required to print an announcement.)
+
+These requirements apply to the modified work as a whole.  If
+identifiable sections of that work are not derived from the Program,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works.  But when you
+distribute the same sections as part of a whole which is a work based
+on the Program, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Program.
+
+In addition, mere aggregation of another work not based on the Program
+with the Program (or with a work based on the Program) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+  3. You may copy and distribute the Program (or a work based on it,
+under Section 2) in object code or executable form under the terms of
+Sections 1 and 2 above provided that you also do one of the following:
+
+    a) Accompany it with the complete corresponding machine-readable
+    source code, which must be distributed under the terms of Sections
+    1 and 2 above on a medium customarily used for software interchange; or,
+
+    b) Accompany it with a written offer, valid for at least three
+    years, to give any third party, for a charge no more than your
+    cost of physically performing source distribution, a complete
+    machine-readable copy of the corresponding source code, to be
+    distributed under the terms of Sections 1 and 2 above on a medium
+    customarily used for software interchange; or,
+
+    c) Accompany it with the information you received as to the offer
+    to distribute corresponding source code.  (This alternative is
+    allowed only for noncommercial distribution and only if you
+    received the program in object code or executable form with such
+    an offer, in accord with Subsection b above.)
+
+The source code for a work means the preferred form of the work for
+making modifications to it.  For an executable work, complete source
+code means all the source code for all modules it contains, plus any
+associated interface definition files, plus the scripts used to
+control compilation and installation of the executable.  However, as a
+special exception, the source code distributed need not include
+anything that is normally distributed (in either source or binary
+form) with the major components (compiler, kernel, and so on) of the
+operating system on which the executable runs, unless that component
+itself accompanies the executable.
+
+If distribution of executable or object code is made by offering
+access to copy from a designated place, then offering equivalent
+access to copy the source code from the same place counts as
+distribution of the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+  4. You may not copy, modify, sublicense, or distribute the Program
+except as expressly provided under this License.  Any attempt
+otherwise to copy, modify, sublicense or distribute the Program is
+void, and will automatically terminate your rights under this License.
+However, parties who have received copies, or rights, from you under
+this License will not have their licenses terminated so long as such
+parties remain in full compliance.
+
+  5. You are not required to accept this License, since you have not
+signed it.  However, nothing else grants you permission to modify or
+distribute the Program or its derivative works.  These actions are
+prohibited by law if you do not accept this License.  Therefore, by
+modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Program or works based on it.
+
+  6. Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the
+original licensor to copy, distribute or modify the Program subject to
+these terms and conditions.  You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties to
+this License.
+
+  7. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Program at all.  For example, if a patent
+license would not permit royalty-free redistribution of the Program by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Program.
+
+If any portion of this section is held invalid or unenforceable under
+any particular circumstance, the balance of the section is intended to
+apply and the section as a whole is intended to apply in other
+circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system, which is
+implemented by public license practices.  Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+  8. If the distribution and/or use of the Program is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Program under this License
+may add an explicit geographical distribution limitation excluding
+those countries, so that distribution is permitted only in or among
+countries not thus excluded.  In such case, this License incorporates
+the limitation as if written in the body of this License.
+
+  9. The Free Software Foundation may publish revised and/or new versions
+of the General Public License from time to time.  Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+Each version is given a distinguishing version number.  If the Program
+specifies a version number of this License which applies to it and "any
+later version", you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation.  If the Program does not specify a version number of
+this License, you may choose any version ever published by the Free Software
+Foundation.
+
+  10. If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the author
+to ask for permission.  For software which is copyrighted by the Free
+Software Foundation, write to the Free Software Foundation; we sometimes
+make exceptions for this.  Our decision will be guided by the two goals
+of preserving the free status of all derivatives of our free software and
+of promoting the sharing and reuse of software generally.
+
+			    NO WARRANTY
+
+  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS
+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+
+  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+		     END OF TERMS AND CONDITIONS
+
+	    How to Apply These Terms to Your New Programs
+
+  If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+  To do so, attach the following notices to the program.  It is safest
+to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+    <one line to give the program's name and a brief idea of what it does.>
+    Copyright (C) <year>  <name of author>
+
+    This program is free software; you can redistribute it and/or modify
+    it under the terms of the GNU General Public License as published by
+    the Free Software Foundation; either version 2 of the License, or
+    (at your option) any later version.
+
+    This program is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+    GNU General Public License for more details.
+
+    You should have received a copy of the GNU General Public License
+    along with this program; if not, write to the Free Software
+    Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
+
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+
+    Gnomovision version 69, Copyright (C) year name of author
+    Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+    This is free software, and you are welcome to redistribute it
+    under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License.  Of course, the commands you use may
+be called something other than `show w' and `show c'; they could even be
+mouse-clicks or menu items--whatever suits your program.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the program, if
+necessary.  Here is a sample; alter the names:
+
+  Yoyodyne, Inc., hereby disclaims all copyright interest in the program
+  `Gnomovision' (which makes passes at compilers) written by James Hacker.
+
+  <signature of Ty Coon>, 1 April 1989
+  Ty Coon, President of Vice
+
+This General Public License does not permit incorporating your program into
+proprietary programs.  If your program is a subroutine library, you may
+consider it more useful to permit linking proprietary applications with the
+library.  If this is what you want to do, use the GNU Library General
+Public License instead of this License.
diff --git a/fpga/xilinx/programmer/bit2svf/bitinfo-0.3/Changelog b/fpga/xilinx/programmer/bit2svf/bitinfo-0.3/Changelog
new file mode 100644
index 0000000..958d5d9
--- /dev/null
+++ b/fpga/xilinx/programmer/bit2svf/bitinfo-0.3/Changelog
@@ -0,0 +1,6 @@
+2002-09-10, version 0.2
+
+Updated the way I parse the bitstream length according to information in the
+online FPGA FAQ.  Special thanks to "Stephen from Australia" for setting me
+straight.  Started using version numbers.  If you have an unnumbered
+version of bitinfo, it is version 0.1 and out of date.
diff --git a/fpga/xilinx/programmer/bit2svf/bitinfo-0.3/Makefile b/fpga/xilinx/programmer/bit2svf/bitinfo-0.3/Makefile
new file mode 100644
index 0000000..12685c9
--- /dev/null
+++ b/fpga/xilinx/programmer/bit2svf/bitinfo-0.3/Makefile
@@ -0,0 +1,21 @@
+# Makefile for bitfile routines
+
+CC = gcc
+CFLAGS = -c -g -Wall
+LDFLAGS = 
+OBJECTS = bitinfo.o bitfile.o
+
+
+all: bitinfo
+
+bitinfo.o: bitinfo.c bitfile.h
+	${CC} ${CFLAGS} bitinfo.c -o bitinfo.o
+
+bitfile.o: bitfile.c bitfile.h
+	${CC} ${CFLAGS} bitfile.c -o bitfile.o
+
+bitinfo: bitinfo.o bitfile.o
+	${CC} ${LDFLAGS} ${OBJECTS} -o bitinfo
+
+clean:
+	rm -f ${OBJECTS} bitinfo
diff --git a/fpga/xilinx/programmer/bit2svf/bitinfo-0.3/README b/fpga/xilinx/programmer/bit2svf/bitinfo-0.3/README
new file mode 100644
index 0000000..c100126
--- /dev/null
+++ b/fpga/xilinx/programmer/bit2svf/bitinfo-0.3/README
@@ -0,0 +1,45 @@
+ Bitinfo - Parse a Xilinx bit-file header
+
+
+ Description
+ 
+  Bitinfo is a simple utility that parses the header of a Xilinx bit file
+  and outputs all the information that can be obtained from that header. 
+  This information includes the Xilinx FPGA the bit file was created for,
+  the NCD file the bit file was created from, the creation date and time,
+  and the bitstream length.
+ 
+  I had to reverse-engineer the file format to figure out how to parse all
+  of this information.  So that someone else doesn't have to repeat my work,
+  I have included my reverse-engineering notes with the source code.
+ 
+  You may find this program useful if, like me, you often end up with
+  several bit files lying around, all called "xc4005.bit," and you can't
+  remember which one is the one you need.  The header should at least give
+  you some clues about the file's contents.  Another use for this program is
+  to prove to a student that the bit file they have brought to lab with them
+  is not the one from this week's experiment, since the timestamp is from
+  three weeks ago.
+ 
+
+ Compiling and using bitinfo
+ 
+  You can download the bitinfo source for free from
+  http://members.naspa.net/djs/software/bitinfo.tar.gz.  It is released under
+  the GNU Public License.  See the COPYING file for more details.
+ 
+  To compile bitinfo, first edit the Makefile if necessary.  If you don't
+  have gcc installed, you will need to change the first line from "CC=gcc"
+  to "CC=cc" or whatever your C compiler is called.  After editing the
+  Makefile, type "make" and you're done.  Although bitinfo was written for
+  Unix, it has also been successfully compiled for Windows NT 4.0 using MS
+  Visual C++.
+ 
+  To run bitinfo, just type "bitinfo < file.bit".  You will probably want to
+  put bitinfo in some bin directory for convenience.
+ 
+ 
+ Bugs
+ 
+  Please report any bugs by emailing me at djs@naspa.net.
+
diff --git a/fpga/xilinx/programmer/bit2svf/bitinfo-0.3/bitfile.c b/fpga/xilinx/programmer/bit2svf/bitinfo-0.3/bitfile.c
new file mode 100644
index 0000000..af4579d
--- /dev/null
+++ b/fpga/xilinx/programmer/bit2svf/bitinfo-0.3/bitfile.c
@@ -0,0 +1,233 @@
+/* bitfile.c
+ *
+ * Library routines for dealing with bit files, version 0.2
+ *
+ * Copyright 2001, 2002 by David Sullins
+ *
+ * This file is part of Bitinfo.
+ * 
+ * Bitinfo is free software; you can redistribute it and/or modify it under the
+ * terms of the GNU General Public License as published by the Free Software
+ * Foundation, version 2 of the License.
+ * 
+ * Bitinfo is distributed in the hope that it will be useful, but WITHOUT ANY
+ * WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
+ * FOR A PARTICULAR PURPOSE.  See the GNU General Public License for more
+ * details.
+ * 
+ * You should have received a copy of the GNU General Public License along with
+ * Bitinfo; if not, write to the Free Software Foundation, Inc., 59 Temple
+ * Place, Suite 330, Boston, MA 02111-1307 USA
+ * 
+ * You may contact the author at djs@naspa.net.
+ */
+
+#include <string.h>
+#include <stdio.h>
+#include <stdlib.h>
+#include "bitfile.h"
+
+#ifndef uchar
+#define uchar unsigned char
+#endif
+
+/* first 13 bytes of a bit file */
+static uchar head13[] = {0, 9, 15, 240, 15, 240, 15, 240, 15, 240, 0, 0, 1};
+
+/* initbh
+ *
+ * Initialize the bithead struct
+ */
+void initbh(struct bithead *bh)
+{
+	bh->filename = NULL;
+	bh->part = NULL;
+	bh->date = NULL;
+	bh->time = NULL;
+	bh->length = 0;
+}
+
+/* freebh
+ *
+ * Free up memory allocated for a bithead struct.
+ */
+void freebh(struct bithead *bh)
+{
+	free(bh->filename);
+	free(bh->part);
+	free(bh->date);
+	free(bh->time);
+	initbh(bh);
+}
+
+/* readhead
+ * 
+ * Read the entire bit file header.  The file pointer will be advanced to
+ * point to the beginning of the bitstream, and the bitfile header struct
+ * will be filled with the appropriate data.
+ *
+ * Return -1 if an error occurs, 0 otherwise.
+ */
+int readhead(struct bithead *bh, FILE *f)
+{
+	int t;
+	
+	/* get first 13 bytes */
+	t = readhead13(f);
+	if (t) return t;
+	
+	/* get filename */
+	t = readsecthead(NULL, f);
+	if (-1 == t) return -1;
+	bh->filename = malloc(t);
+	t = readsection(bh->filename, t, f);
+	
+	/* get part name */
+	t = readsecthead(NULL, f);
+	if (-1 == t) return -1;
+	bh->part = malloc(t);
+	t = readsection(bh->part, t, f);
+	
+	/* get file creation date */
+	t = readsecthead(NULL, f);
+	if (-1 == t) return -1;
+	bh->date = malloc(t);
+	t = readsection(bh->date, t, f);
+	
+	/* get file creation time */
+	t = readsecthead(NULL, f);
+	if (-1 == t) return -1;
+	bh->time = malloc(t);
+	t = readsection(bh->time, t, f);
+	
+	/* get bitstream length */
+	t = readlength(f);
+	if (-1 == t) return -1;
+	bh->length = t;
+	
+	return 0;
+}
+
+/* readhead13
+ *
+ * Read the first 13 bytes of the bit file.  Discards the 13 bytes but
+ * verifies that they are correct.
+ *
+ * Return -1 if an error occurs, 0 otherwise.
+ */
+int readhead13 (FILE *f)
+{
+	int t;
+	uchar buf[13];
+
+	/* read header */
+	t = fread(buf, 1, 13, f);
+	if (t != 13)
+	{
+		return -1;
+	}
+	
+	/* verify header is correct */
+	t = memcmp(buf, head13, 13);
+	if (t)
+	{
+		return -1;
+	}
+	
+	return 0;
+}
+
+/* readsecthead
+ *
+ * Read the header of a bit file section.  The section letter is placed in
+ * section buffer "buf" and the length of the following section is 
+ * returned.  If buf is NULL, the section letter is discarded.
+ *
+ * Return -1 if an error occurs, length of section otherwise.
+ */
+int readsecthead(char *buf, FILE *f)
+{
+	int t;
+	char tbuf = 0;
+	char lenbuf[2];
+	
+	/* if buf is NULL, use tbuf instead */
+	if (NULL == buf)
+	{
+		buf = &tbuf;
+	}
+
+	/* get section letter */
+	t = fread(buf, 1, 1, f);
+	if (t != 1)
+	{
+		return -1;
+	}
+	
+	/* read length */
+	t = fread(lenbuf, 1, 2, f);
+	if (t != 2) 
+	{
+		return -1;
+	}
+
+	/* convert 2-byte length to an int */
+	return (((int)lenbuf[0]) <<8) | lenbuf[1];
+}
+
+
+/* readsection
+ *
+ * Read a section of a bit file.  The section contents are placed
+ * in the contents buffer "buf."
+ *
+ * Return -1 if an error occurs, 0 otherwise.
+ */
+int readsection(char *buf, int length, FILE *f)
+{
+	int t;
+	
+	/* get section data */
+	t = fread(buf, 1, length, f);
+	if ((t != length) || (buf[length-1] != 0))
+	{
+		return -1;
+	}
+	
+	return 0;
+}
+
+/* readlength
+ *
+ * Read in the bitstream length.  The section letter "e" is discarded
+ * and the length is returned.
+ *
+ * Return -1 if an error occurs, length otherwise.
+ */
+int readlength(FILE *f)
+{
+	char s = 0;
+	uchar buf[4];
+	int length;
+	int t;
+	
+	/* get section, make sure it's "e" */
+	t = fread(&s, 1, 1, f);
+	if ((t != 1) || (s != 'e'))
+	{
+		return -1;
+	}
+	
+	/* get length */
+	t = fread(buf, 1, 4, f);
+	if (t != 4)
+	{
+		return -1;
+	}
+	
+	/* convert 4-byte length to an int */
+	length = (((int)buf[0]) <<24) | (((int)buf[1]) <<16) 
+	         | (((int)buf[2]) <<8) | buf[3];
+	
+	return length;
+}
diff --git a/fpga/xilinx/programmer/bit2svf/bitinfo-0.3/bitfile.h b/fpga/xilinx/programmer/bit2svf/bitinfo-0.3/bitfile.h
new file mode 100644
index 0000000..cb531a8
--- /dev/null
+++ b/fpga/xilinx/programmer/bit2svf/bitinfo-0.3/bitfile.h
@@ -0,0 +1,99 @@
+/* bitfile.h
+ *
+ * Library routines for dealing with bit files, version 0.2
+ *
+ * Copyright 2001, 2002 by David Sullins
+ *
+ * This file is part of Bitinfo.
+ * 
+ * Bitinfo is free software; you can redistribute it and/or modify it under the
+ * terms of the GNU General Public License as published by the Free Software
+ * Foundation, version 2 of the License.
+ * 
+ * Bitinfo is distributed in the hope that it will be useful, but WITHOUT ANY
+ * WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
+ * FOR A PARTICULAR PURPOSE.  See the GNU General Public License for more
+ * details.
+ * 
+ * You should have received a copy of the GNU General Public License along with
+ * Bitinfo; if not, write to the Free Software Foundation, Inc., 59 Temple
+ * Place, Suite 330, Boston, MA 02111-1307 USA
+ * 
+ * You may contact the author at djs@naspa.net.
+ */
+
+#include <stdio.h>
+
+/* struct bithead
+ *
+ * Stores the information obtained from the bitfile header.  Use initbh to
+ * initialize the struct, and freebh to free memory allocated for the struct.
+ */
+struct bithead
+{
+	char* filename;
+	char* part;
+	char* date;
+	char* time;
+	int length;
+};
+
+/* initbh
+ *
+ * Initialize the bithead struct
+ */
+void initbh(struct bithead *bh);
+
+/* freebh
+ *
+ * Free up memory allocated for a bithead struct.
+ */
+void freebh(struct bithead *bh);
+
+/* readhead
+ * 
+ * Read the entire bit file header.  The file pointer will be advanced to
+ * point to the beginning of the bitstream, and the bitfile header struct
+ * will be filled with the appropriate data.
+ *
+ * Return -1 if an error occurs, 0 otherwise.
+ */
+int readhead(struct bithead *bh, FILE *f);
+
+/* readhead13
+ *
+ * Read the first 13 bytes of the bit file.  Discards the 13 bytes but
+ * verifies that they are correct.
+ *
+ * Return -1 if an error occurs, 0 otherwise.
+ */
+int readhead13 (FILE *f);
+
+/* readsecthead
+ *
+ * Read the header of a bit file section.  The section letter is placed in
+ * section buffer "buf" and the length of the following section is 
+ * returned.  If buf is NULL, the section letter is discarded.
+ *
+ * Return -1 if an error occurs, length of section otherwise.
+ */
+int readsecthead(char *buf, FILE *f);
+
+/* readsection
+ *
+ * Read a section of a bit file.  The section contents are placed
+ * in the contents buffer "buf."
+ *
+ * Return -1 if an error occurs, 0 otherwise.
+ */
+int readsection(char *buf, int length, FILE *f);
+
+/* readlength
+ *
+ * Read in the bitstream length.  The section letter "e" is discarded
+ * and the length is returned.
+ *
+ * Return -1 if an error occurs, length otherwise.
+ */
+int readlength(FILE *f);
+
diff --git a/fpga/xilinx/programmer/bit2svf/bitinfo-0.3/bitinfo.c b/fpga/xilinx/programmer/bit2svf/bitinfo-0.3/bitinfo.c
new file mode 100644
index 0000000..1fc1c84
--- /dev/null
+++ b/fpga/xilinx/programmer/bit2svf/bitinfo-0.3/bitinfo.c
@@ -0,0 +1,57 @@
+/* bitinfo.c
+ *
+ * Main function to parse Xilinx bit file header, version 0.2.
+ *
+ * Copyright 2001, 2002 by David Sullins
+ *
+ * This file is part of Bitinfo.
+ * 
+ * Bitinfo is free software; you can redistribute it and/or modify it under the
+ * terms of the GNU General Public License as published by the Free Software
+ * Foundation, version 2 of the License.
+ * 
+ * Bitinfo is distributed in the hope that it will be useful, but WITHOUT ANY
+ * WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
+ * FOR A PARTICULAR PURPOSE.  See the GNU General Public License for more
+ * details.
+ * 
+ * You should have received a copy of the GNU General Public License along with
+ * Bitinfo; if not, write to the Free Software Foundation, Inc., 59 Temple
+ * Place, Suite 330, Boston, MA 02111-1307 USA
+ * 
+ * You may contact the author at djs@naspa.net.
+ */
+
+
+#include <stdio.h>
+#include <stdlib.h>
+#include "bitfile.h"
+
+/* read a bit file from stdin */
+int main(void)
+{
+	int t;
+	struct bithead bh;
+	
+	initbh(&bh);
+	
+	/* read header */
+	t = readhead(&bh, stdin);
+	if (t)
+	{
+		printf("Invalid bit file header.\n");
+		exit(1);
+	}
+	
+	/* output header info */
+	printf("\n");
+	printf("Bit file created on %s at %s.\n", bh.date, bh.time);
+	printf("Created from file %s for Xilinx part %s.\n", bh.filename, 
+	       bh.part);
+	printf("Bitstream length is %d bytes.\n", bh.length);
+	printf("\n");
+	
+	freebh(&bh);
+	
+	return 0;
+}