aboutsummaryrefslogtreecommitdiffstats
path: root/notes/xilinx_toolchain.txt
diff options
context:
space:
mode:
authorbryan newbold <bnewbold@leaflabs.com>2013-04-02 10:26:08 -0400
committerbryan newbold <bnewbold@leaflabs.com>2013-04-02 10:26:08 -0400
commitc973b4e327ab0c560ba2428e4cc08d542352eb32 (patch)
tree645842bd41df92f94fe86faaedcb32679ddf68ab /notes/xilinx_toolchain.txt
parent8228807c03cef9c17c7407414dafec95fd8035b9 (diff)
downloadfpga-lube-c973b4e327ab0c560ba2428e4cc08d542352eb32.tar.gz
fpga-lube-c973b4e327ab0c560ba2428e4cc08d542352eb32.zip
add old notes and README
Diffstat (limited to 'notes/xilinx_toolchain.txt')
-rw-r--r--notes/xilinx_toolchain.txt17
1 files changed, 17 insertions, 0 deletions
diff --git a/notes/xilinx_toolchain.txt b/notes/xilinx_toolchain.txt
new file mode 100644
index 0000000..e7d78db
--- /dev/null
+++ b/notes/xilinx_toolchain.txt
@@ -0,0 +1,17 @@
+
+Chapter Two of "FPGAs!? Now What?" gives a good overview of the full
+compilation process:
+
+Synthesis:
+ the "logic synthesizer" compiles from HDL to a netlist
+
+Implementation:
+ the "translator" takes a set of netlists and design constraints and generates
+ a merged netlist (?).
+ then a "mapper" regroups the netlist so that place and route will be easier
+ then a "place and route" tool decides exactly how the FPGA logic will be
+ configured
+
+Bitstream:
+ the "bitstream generator" translates the configuration into the binary format
+ that the FPGA uses to re-flash itself