Slashdot Mirror
Suggestions For Learning FPGA Development At Home?
Doug writes "I've recently been inspired to take up amateur electronics, specifically with FPGAs. I have an understanding of the basics, plus a solid programming background. From my research so far I've concluded that I should start with a simple FPGA development board and a couple of books on Verilog and/or VHDL and go from there. I found this Ask Slashdot discussion on Verilog vs VHDL very useful, but it focuses more on the development language rather than hardware. I'd be very interested in hearing peoples' recommendations for an entry-level kit that is simple, flexible, and affordable (sub-£200), and preferably Linux-friendly, and indeed any other wise words that experienced FPGA developers (professional or amateur) might have for a novice just starting out in the world of circuit design."
http://www.opalkelly.com/
Unless you are very experienced designing with TTL chips, you won't get far in HDL without first getting good coverage of logic theory. My experience may be a little dated as it was 10 years ago that I started learning programmable logic, but at the time I enjoyed the first edition of Fundamentals of Digital Logic with VHDL Design. Not that logic theory has changed, but newer books might come with better examples or easier to use software. What I liked about that book was that it covered the theory in a very complete way while introducing the vhdl concepts at a manageable pace.
As far as development tools, they're overwhelmingly Windows based. You may have to run a VM so that you can use the most common tools (eg Xilinx WebPACK) until you're up to speed, then try a linux solution later. There are lots of hardware trainers out there - it's really not that important which one you use initially, although if whatever books you're reading have a recommended one, use that.
Your experience in the software world will help you somewhat, but be prepared for a vastly steeper learning curve than picking up a new programming language. There are not a lot of engineers who go very deep on both the software and hardware/logic sides - if you do you will end up with some valuable skills indeed. good luck!
The answer keeps coming back Altera.
In our lab sessions we teach the students with boards of Digilent Inc. and we're very happy of them, we also have some in house dev. boards. (do I get my discount bonus know? :)
Hardware: I highly recommend the Spartan Starter Kits. They're dirt cheap, well supported by the industry, and come with a good toolkit. There's not much more you need to know other than you'll probably want a serial cable in addition to the JTAG cable the kit ships with.
I'll grant you that the fabric isn't very large by today's standards, but it's still enough space to learn about the hardware. By the time you outgrow the fabric, you should have a good idea of what size hardware you want. In fact, your next board may even be a custom design based on a bus like wishbone. ;-)
Software: The Xilinx stuff (pronounced "Zy-Links") comes with a full toolkit for VHDL/Verilog development including an IDE, place and route tools, and software to reconfigure the FPGA. It's all quite slick and easy for a beginner to use.
Language: The most common route taken by new hardware developers is to learn Verilog. They do this because it's similar to C and that makes them comfortable. THIS IS A BAD IDEA. I can't count how many hardware designers swear up a storm when they see a Verilog project with loops and other software constructs stuck into them. See, the comfort and familarity of C makes new hardware developers forget that the hardware is a fixed layout. There is no for loops or control logic as you think of it. It all ends up flattening to hardware. If you write regular software constructs, you'll end up with the least efficient circuit possible.
From this perspective, learning VHDL is better because you won't have that comfort and familiarity that might tempt you into creating poor circuits.
I actually recommend doing some JHDL code for a while. It's lower level than VHDL, but that's a good thing. You have to think about every wire connection and how it all links up. When you're done, you can easily step through your circuit and see how it plays out in hardware. Even better, you learn how to properly use software constructs like loops to create a large number of static hardware objects. This will make your code better without falling in the trap of trying to write software.
That's my 2 cents anyway. Good luck! :-)
Javascript + Nintendo DSi = DSiCade
Use Xilinx's FPGA Starter Kit. I bought the old version 5 years ago, and it also came with a CPLD dev kit. The dev tools run on linux too. It was something like $99 IIRC. It's made by Digilent. Last time I checked they had a better board for an extra $50 with an LCD display and 64MB SDRAM.
Otherwise, check fpga4fun.com . They use a tiny FPGA board, which reminds me of the Arduino: it has everything you need and nothing more.
I'd suggest Avnet Part # AES-SP3A-EVAL400-G, it's $49, and comes with everything you need for VHDL or Verilog...
I use these at work for general-purpose little widgets. They are great for all sorts of control/data collection devices. I think we've bought around 50 or so over the past couple of years.
Unfortunately, they do not support Linux.
There is an FPGA programming solution around for this board which does support linux (search for Nexys2 on comp.arch.fpga), but it does not support the data transfer function.
The data transfer function is very nice (under Windows). digilent supplies a driver and DLL, and I find it very easy to transfer data using Python. I do wish they supported Linux, though -- that's all I use at home.
Xilinx: http://www.xilinx.com/products/devkits/HW-SPAR3AN-SK-UNI-G.htm
Altera: http://www.altera.com/products/devkits/altera/kit-cyc3-starter.html
Both are very mainline FPGAs, both have full devkits, references designs, include the tools, linux support on Xilinx at least (not sure on Altera), and are both at your price point.
Test your net with Netalyzr
Digilent FPGA boards
http://digilentinc.com/
Search on google to find the link to the product page.
VHDL for FPGAs and Verilog for ASICs. This rule applies everywhere except where it doesn't.
But in particular, I disagree with your reasoning about why to use VHDL vs. Verilog. Obviously, everybody's mileage may vary, but removing all vestiges of familiarity so that everything gets equally hard is not the way I learn.
The way I learned C was by looking at the assembly language output of the compiler, and you can effectively do the same thing with hardware.
It's not that hard to see what kind of logic your stuff compiles into -- in fact, you can dump a verilog netlist that shows you exactly how your logic maps to the internal chip elements. At a higher level, you can just look at the resource utilization report to see how "big" your circuit is.
In terms of the "right" language to learn for other reasons, apparently VHDL is somewhat more popular in Europe, and maybe somewhat more popular among FPGA-only designers, but all the "real" chip companies in the US use Verilog.
1. Get a (the) Spartan-3 starter board. It's got the 500 variant of the Spartan-3 on it which is big enough to implement even small processors. The board also has some very limited VGA output, and a heap of other things that makes it fun to work with (Serial I/F, etc). The manual for this board is one of the better ones for beginners, as well. I broke my own teeth on this board. It's 149 US schmucks from digilent.
2. Get Xilinx's free tool suite; its nicely compatible with that board. Free download from the web. Heck, you can even download and play with it without the / any board (but then you don't, of course, get the blinkenlights.) You can however try out and simulate designs before going to FPGA, and thus figure out why the (redacted) it doesn't (redacted) work. Simulations are your main way of verifying your design once you're past 20-odd gates.
3. Learn the HDL of your choice. Read the books. One warning only: it is NOT a programming language - the entire model in your head about how software works needs to be replaced. Case statements are king. Productivity with HDL's are generally way lower than software; don't be surprised by this.
4. Do points 1 through 3 in reverse order. Having a shiny 150 schmucker board won't help anything if you still have to spend two weeks grokking HDL's.
HTH.
On actual development: never assume any order of two things unless you enforce it. All things happen in a single clock cycle and you can't expect anything to wait for anything else. FPGA's internally work at a much higher rate to simulate at the rate you think you're running which implicitly means that you'll *have* to clock your operations - FPGA's don't do asynchronous (technically they're able but there's no tool that figures it out for you - and you won't want to manually route).
Oh, and good luck on interfacing with software. Software is *slow*.
Build/Buy yourself a Minimig (with the ARM SD controller) or FPGAArcade.
At some point you'll want to do decent graphical output as you design your dream 8-bit computer, so these will make a decent base.
For VHDL itself, I learned that with GHDL (VHDL front-end to gcc, though it hasn't been updated in a year now) and GTKWave for viewing the waves. Throw in make for a build system, and it was all I needed to design and implement (VHDL only, that is) a simple microprocessor.
That's a start anyway.
If you're tired of all the VHDL and Verilog nuances, try CtoVerilog.com
Learn how to use core generator and a simulator before you even buy a board. you only need a board when you actually want to have hardware.
DLP Design (www.dlpdesign.com) has some interesting FPGA modules. Some include a USB port that can be used to program and communicate with the FPGA. This has a USB port and a Spartan 3E for a reasonable price and includes tutorials. Combined with the free Xilinx tools you can do quite a lot with it.
A cheaper alternative that's well below your price point would be CPLDs (complex programmable logic devices). Much less capable than an FPGA but also much cheaper. Xilinx makes the CoolRunner line, Altera makes the MAX line, and I'm sure there are plenty of others. There's a $63 Xilinx development kit available from digi-key:
http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=122-1573-ND
Get a cheap FPGA board from Digilent (like the BASYS), the free ISE Webpack dev environment from Xilinx, and all the Verilog tutorials you can find on the web.
That's the way I did it anyway. You can get everything you need to learn for $100
Well, since most have already suggested the devkits of their choice (of which I have personally used at least a few), and which you could have come up with a Google search... I thought I'd rather advise on an excellent book (and which excellent cromulance you would not have been able to find with Google that easily): "VHDL Answers to Frequently Asked Questions" by Ben Cohen. Even though it has "FAQ" in the title, this books is actually an excellently structured textbook on VHDL. In fact, it's probably THE best book on VHDL for beginners and advanced beginners.
"The agriculture ministry is not in charge of Gundam" - Japanese ministry official.
Now that Xilinx has released new chips, the old ones are pretty cheap. A Spartan-3A evaluation board is less than US $200. These have VGA, PS/2, RS-232, a character LCD, a rotary encoder, LEDs, switches, and a bunch of extra connectors. The main problems are that the DDR2 RAM is *difficult* to use without a proprietary core, and the FPGA doesn't have access to the USB link.
Digilent Inc sells Spartan-3E boards for less than US $100. These have an easier-to-use DRAM and provide access to the USB port (though I think the official driver is windows-only, there seem to be solutions for using it on Linux).
Xilinx's ISE runs natively on Linux (RHEL, last time I checked). With a little searching, it was easy to figure out how to get it to work on Ubuntu, including the USB JTAG interface on the eval boards.
I haven't found a great book for learning this stuff. Pedroni's _Circuit Design with VHDL_ is okay, but it's not particularly deep and doesn't cover the FPGA development process at all. I had to study the Xilinx tutorials to get things working.
Writing HDL code superficially seems like normal programming, but it's not. Think of it as a way to translate your already-completed design into a form the computer understands. If you don't do the up-front design, it will be hard to fix through refactoring. The simulators just aren't up to the task. Restrict yourself to a single edge of a single clock, and things will be much easier.
In most of our EE classes, we purchased some educational boards from Digilent.
http://www.digilentinc.com/
I have no frame of reference, but I enjoyed working with them.
I would recommend a board made by Digilent as they seem to have the greatest selection of add-ons and features plus their boards are high quality from my experience. As for the FPGA, I always recommend Xilinx because of the availability of free development tools, Linux support ( I currently have their WebPACK ISE running under Kubuntu 9.04 ) and the general superiority of their products, especially for projects that involve high speeds, a large number of gates and/or flip-flops eg. a microprocessor and even low power -- Xilinx' weakness has always been their relatively high standby/leakage current compared to other vendors, but they've significantly improved upon that with the Spartan-3A and the just released Spartan 6 chips.
As a Spartan 6 dev board is going to be expensive ( Xilinx' Spartan-6 FPGA SP601 Evaluation Kit is $295 and AFAIK it's the only entry level board currently available for that chip ) right now, I would recommend a Spartan 3A board. Specifically I would recommend Xilinx' Spartan-3A Starter Kit as it has the right amount of features for the price ( $189 ) and it's made by Digilent although if you're on a *really* tight budget you can get kits based off of this chip for as low as $49
jdb2
List of FPGA prototyping boards. Xilinx software is free for certain FPGAs. http://www.fpga-faq.com/FPGA_Boards.shtml For books, the only one I know of with an emphasis on synthesis results that includes both VHDL and Verilog is "HDL Chip Design" by Douglas J. Smith. I highly recommend Verilog over VHDL even though I learned VHDL first. Also Xilinx has obscene amounts of documentation on their websitehttp://www.xilinx.com/support/documentation/. Some of their whitepapers and app notes cover general logic design techniques.
You can purchase a relatively inexpensive board these days (Spartan-3 or an XUPv5). After you've taken the steps to learn the HDL and the concepts, you should try taking a look at a few reference designs online (http://www.xilinx.com/univ/xupv5-lx110t-refdes.htm).
Also, for learning purposes, if you're willing to, there are some high-quality university courses that you can watch online that walk you through the digital design concepts and the FPGA tool flows. Here's one from a pretty well-known digital design course at UC Berkeley: http://webcast.berkeley.edu/course_details.php?seriesid=1906978206
As many have stated, both Xilinx are Altera can be good routes. Note that while they Altera tools support Linux, their freebie Web edition does not, and the full kit is more than you'd want to spend. Any Xilinx starter kit should be fine for tooling around. I'm not sure your experience level, so I'll go with the basics...
I'm a young n00b in the FPGA world (two years design experience out of college now), so my experiences are pretty recent. I've got an EE degree, and would say first of all, get a firm grasp of logic design. Do you know what a flip flop actually is? Are you familiar with things like setup and hold time? If not, start out with a lot of reading. Horowitz and Hill's "The Art of Electronics" is a good standard...there's a lot of analog stuff that's "less relevant" to you, but there's a good section on digital design that's a great start.
One of my young programmer colleagues was looking over some of my code, and seemed to think it was pretty easy...the syntax seemed pretty straightforward, he liked the idea of combinatorial logic being so easy to implement, etc. He started tinkering himself, and VERY quickly realized that it was much more complex than he thought when issues of timing were thrown in. A fundamental knowledge of how signals are propagating through the device is key. It's not just PROGRAMMING, you're programming the actual hardware (or making fancy lookup tables, whatever. Get off my back!).
As designs get more complicated, you'll need to learn how to use some tools to analyze timings. Altera has Timequest, not sure what Xilinx uses. In college, I managed to get away with the bare minimum of analysis, but I consider this to be a flaw in my education...to do things right, you should do proper timing analysis.
I have an Altera starter kit I dink around with myself when I'm not at work, and it's definitely worth the time to learn the basics if you're an eternal tinkerer. Finally, the best advice I can give you...don't forget to use VIM as your editor, or you're just setting yourself up for failure.
Hardhack isn't a tag, it's a category. It stands for Hardware Hacking and is included by default. Try mousing over the story icon.
Interested in open source engine management for your Subaru?
Step 1 Forget everything you know about programming. Programmable logic and FPGA design deals with programming of events that all happen in parallel. VHDL code does not execute in the order of the code statements, it compiles into a large logic array that executes at the speed of the gate propagation.
Logic design does not execute like standard programs. Everything in a process occurs at once unless there is a state machine present. If a state machine, present, it all happens on the machine clock. Code should be written with this in mind. Failing to do so will result in unneeded state machines forcing the logic to execute sequentially.
Step 2: Find something else to do. Designing with VHDL is more of a art form than programming. I deeply respect anyone who can do it well. I have been designing analog and digital circuits for 30 years and VHDL design is stillone of the most challanging tasks I have to do.
Before you even bother buying a board, learn the simulator and learn the synthesizer. Understand the difference between pre- and post-route simulations. Look at the logic diffferent coding constructs give you. Even though you'll be tempted to just synthesize and see if it runs, simulation is important. You get complete control. Write unit tests, make your testbench self checking, and you can run it after every change. Writing models to simulate things you'll be hooking up to is tedious, but also important.
Another FPGA manufacturer is Altera. Their software is called" Quartus II" and is available for free on their website.
My first reaction to the parent post is, "I'll bet he encoded a cool circuit design into the ASCII of his text!!! COOL!"
Then I realized he was posting from a cellphone. Probably the same one he had when he learned HDL "10 YEERS AGO". :-P
Javascript + Nintendo DSi = DSiCade
This is a great site with a good bit of introductory information. I implemented their LED flasher tutorials when I was playing with my Xylinx Spartan board. fpga4fun.com
As others have said, all the major FPGA vendors provide cheap starter kits and software to go along. They're a great way to start.
What is essential, though is to understand the concepts of digital design. It's out of print and still expensive (even used) but get yourself a copy of "HDL Chip Design" by Douglas Smith. It is still hands-down the best book on HDL chip design (with every example given in both VHDL and Verilog).
The important thing to realize is that the language isn't important. You have to start with visualizing the gates, bits and timing windows; then move on to figuring out how to describe those circuits in a language. The Smith book guides you through this learning process.
Moron? I think it's more likely a new form of trolling.
It would be interesting to see some enhancements to the tagging. Things like the ability to agree/disagree with tags; viewing who tagged and how agreed/disagreed with each; a way to filter out tags set by people you've foed (unless enough non-foes have agreed); etc
*shrug* for now, I think your only recourse is to turn them off, or maybe write a little greasemonkey script to remove tags you don't want to see anymore (either through lack of interest or contamination of the term)
Come play free flash games on Kongregate!
The Spartan 3 is a good starter board. This was used in my VHDL class. A simple RISC processor was implemented on this board. The virtex5 board was used in my second Computer Design class. A 8-bit MIPS arch processor was implemented on this with all the normal features, ram, PC, interrupts, etc. The virtex5 board is not cheap however.
I second the suggestions to learn good digital design first. Learn and understand state machines as well as well.
Xilinx WebPack ISE is the software to use with these boards that I mentioned. Along with this, Modelsim Xilinx edition works good as well. Both of these tools are free and available from Xilinx.com
Get a board from http://www.digilentinc.com/ and use Xilinx WebPack software (Free as in beer) They have a lot of onboard hardware such as RAM (usually SRAM), buttons/switches/LCDs, etc. They cost about $60 USD to $2k
Actually, FPGAs are much more similar to hardware than they are to traditional software. Even though the configuration is volatile on most SRAM-based FPGAs, the "software" does not describe a set of procedural steps to perform as software does for microprocessors.
Rather, an FPGA configuration (personality), describes how the internal gates, storage elements, and interconnect is switched. This makes a configured FPGA almost indiscernible from an ASIC in function.
An FPGA isn't software loaded to "mimic" the functionality of an IC, it is software loaded to "describe" the functionality of the IC.
This is why VHDL and Verilog aren't strictly software programming languages. Rather, they are hardware description languages. Although they can be executed by software simulators in a fashion similar to software, they really describe hardware either behaviorally (procedurally or event-based) or structurally (netlist).
has anyone experience with NetFPGA? http://netfpga.org/ The NetFPGA is: a line-rate, flexible, and open platform for research, and classroom experimentation. About 1,000 NetFPGA systems have been deployed at over 120 institutions in over 15 countries around the world. As detailed in the specifications, the NetFPGA is a PCI card that contains a large Xilinx FPGA, 4 Gigabit Ethernet ports, Static RAM (SRAM), Double-Date Rate (DDR2) Dynamic RAM (DRAM). The card design is open-source and the hardware is made available at very lost through donations of gifts and Silicon chips by sponsors of the NetFPGA project. The NetFPGA enables researchers and students to build working prototypes of high-speed, hardware-accelerated networking systems. The NetFPGA has been used in the teachers in the classroom to hgelp students learn how to build Gigabit Ethernet (GigE) switches and Internet Protocol (IP) routers. It has also been used by researchers to prototype new modules that use hardware rather than software to forward packets.
The Xilinx starter kits are cheap. If you want something with a few more peripherals, the Altera DE2 or DE2-70 kits have more extras than you can shake a stick at.
Both Altera and Xilinx offer free versions of their tools.
VHDL or Verilog doesn't matter, pick one and learn the basics.
You should expect to have to know something about interfacing digital hardware to get anywhere. Having an oscilloscope or logic analyzer handy will save you time debugging when you try to interface to external chips.
It will enable you to write real code for an FPGA using a subset of normal F# with some parallel programming semantics. You can download it here. That is, you can write normal F# code and calculate some result as a regular F# program on your pc, then compile the code for the FPGA and see the same output on an FPGA. It's ideal for a software programmer like yourself who wants to get started with serious FPGA programming. There are many good books on verilog and VHDL. For VHDL one of the best is Peter Ashenden's "The Designer's Guide to VHDL". For verilog a good book is Vranesic and Brown's "Fundamentals of Digital Logic with Verilog Design" (they also have a similar book for VHDL).
Xess has a good Xilinx-based started board and great tutorials. As other's have mentioned, Digilent also has some good starter boards. The company was started by a couple of professors from Washington State University. A course that one of them teaches (Clint Cole) has some excellent tutorials on FPGAs. Make sure you get a board with a VGA interface and check out some of the classic arcade game projects implemented on an FPGA (eg, fpgaarcade.com). Enjoy!
Nah, he just 1337-ified this +4 Informative post.
Tiller's Rule: Never use a word in written form that you've only heard and never read. You will end up looking foolish.
Fundamentals of Logic Design - Roth. Designed for a self-paced course taught at the University of Texas at Austin, so actually geared toward your needs. http://www.amazon.com/Fundamentals-Logic-Design-C-Roth/dp/0495073083/ref=sr_1_1?ie=UTF8&s=books&qid=1247594924&sr=8-1
--"insert clever quote here"
I write FPGA code for a living, more in VHDL than Verilog, and more for Xilinx than Altera.
I would actually recommend that you don't buy a board at first. You can pick one out so you can decide on a vendor's chip, that's fine, but simulate everything, because that's what HDL design is all about. Both vendors offer a free version of their toolset and there's a free simulator with each of those. Or you can download ModelSim Starter edition. I wouldn't call either one Linux friendly.
As far as the board goes, I would recommend one of Altera's Nios II Embedded Dev Kits. I feel that although Altera has a slightly steeper learning curve than Xilinx, they also have a nicer overall package than what Xilinx is currently offering. I'm speaking from the point of embedding a soft processor though, if that doesn't interest you, then either of the cheap Altera Cyclone or Xilinx Spartan kits will get the job done.
This is the only book you need on VHDL: The Designer's Guide to VHDL by Peter Ashenden.
I haven't found a Verilog book of similar quality.
Buy several books on Verification and testbench writing. That's where the real work comes in, and it's significantly more work than whatever circuit design you're doing. Spend the time to learn how to write self-checking testbenches.
Read over the Synthesis guides for whatever vendor's board you choose. Understand how the constructs you use affect synthesis. There's a wealth of information in the Xilinx and Altera online documentation. There's also a lot of really of good snippets of code which are themselves useful but also typically contrast less and more effective constructs for synthesis.
And finally, I will echo the caution that HDL is not a programming language, it is a design language. If you do not have a fundamental grasp of circuits, logic design, and computer architecture, I would recommend you pursue those topics first.
My advice would be to learn Verilog first, particularly if you're coming from a computer science background. I find Verilog to be much cleaner and easier to read / understand. On the hobbyist (or even the small-scale professional) level, Verilog will probably be easier than VHDL.
I find that VHDL scales to extremely large designs better than Verilog (much better generate statements, pre-processing macros, and paramterization). VHDL is also better if you're really strict on version control and module heirarchy. But if you're working on a one-man project, you probably don't need or want VHDL's unnecessary complexity.
Ultimately, both languages do the same thing and in basically the same way. When you get down to the actual nitty gritty where you're writing the HDL, they're pretty similar. They differ mostly in how they handle passing arguments to- and from- modules, and what kind of compile-time constructs they support.
Last but not least, I would also recommend starting off with Xilinx's Webpack and a Spartan-3 starter board. Get something with a digital-analog converter and an analog-digital converter too, some LEDs and pushbuttons, a UART transceiver, and a ton of GPIO headers. GPIO is where FPGAs really shine.
---- I'll take you in a Hunt deathmatch any day.
It is a little old, but the price is excellent... $150 for the general public, and $120 for students. Even though there are cheaper boards on the market, I have found that the combination of features at a low price has been pretty unbeatable, and it is also available from a lot of distributors.
Now, in the interest of full disclosure, I have been focused heavily on retrocomputing projects... they're a lot of fun.
Disclaimer:
I am not affiliated with them. Just something i was my self interested in for a while just like you.
these guys at www.picocomputing" they have nice little cards.
One thing is that the tools are still not available for free if you want to do very advanced stuff.
Use OKAD, it's commercial quality and will fit on a floppy disk.
Seriously: http://www.colorforth.com/vlsi.html
Don't let the old-school lack of whizz-bang on the website fool you, this real stuff
http://www.ultratechnology.com/color4th.html
You're probably not smart enough for it.
http://www.c2.com/cgi/wiki?ColorForth
I'm not. I can't even find a download link or a sales page.
http://modest-proposals.com/colorForth.htm
Sam
blog.sam.liddicott.com
Well, that explains the post. However, that's not 1337, that's LOLCAT; a derivative of texting language, itself a derivative of common IRC abbreviations.
1337-5p34| was developed to make the text hard to read/index and was "cool" for the hip 90's h4X0rz generation. i.e. Back when putting Zs on everything was kewl. :-P
I'd insert some completely random references that make fun of the movie Hackers, but that would be admitting far too much about my knowledge of the 90's computer culture. ;-)
Javascript + Nintendo DSi = DSiCade
Digilent (http://www.digilent.us) makes good development kits. They tend to be pretty inexpensive and a good value. If you have the cash their XUP board has a good FPGA chip and a lot of great peripherals.
Forget what you know about programming, FPGA's are about thinking in a compleltely different mind set
A former professor of mine, Dr. Ed Doering, set up this page here for our intro logic/FPGA course: PLD Oasis. The school it's hosted off of, my alma mater, is the school that produced one of the co-founders of Xilinx.
In any case, Dr. Doering has lots of video tutorials about how to use Xilinx software, Spartan boards, Nexys boards, and all other manner of Progammable Logic Devices (PLDs), as well as some clever software resources. He includes things about visual schematic design, which may be beneficial for being able to drop logic circuits onto FPGAs without Verilog as an intermediary, but it's also useful in that you can look at the intermediate Verilog files to get a handle on how Xilinx renders schematics to code.
that's LOLCAT; a derivative of texting language, itself a derivative of common IRC abbreviations
Lolcat didn't derive from text language. AIUI, it sprung up as a grammatical variation of standard english with rather irregular conjugation of verbs, combined with instant messaging / chat room slang, often misspelled for "cute" effect. Certainly, Mark Liberman associated it with leet rather than texting.
1337-5p34| was developed to make the text hard to read/index and was "cool" for the hip 90's h4X0rz generation.
Leet is both a method of encoding using alternative characters and a set of slang words; either can be used with or without the other. Many of those slang words have entered the instant messaging slang; words like "pwn", "noob" or "pron" are common with people who would never otherwise use leet.
Or how about those fucking IDIOTS who use Windows voluntarily? Could anyone be more stupid, more of a fucking sheep, more of a mindless dweeb than to voluntarily use Windows? Duh, of course they can't.
So you're saying we should not be mindless sheeple and do as you do?
"I like to lick butts!" by MobileTatsu-NJG (#32700246) (Score:5, Informative)
and all those 'software simulators' are executed by hardware...
In the end, it doens't matter how many virtualization layers you've got you are programming to tell the *hardware* what to do
MP3 Search Engine
also something to check out, http://opencpi.org/, it will be released and OSS in a few weeks The Open Component Portability Infrastructure (OpenCPI) is a real-time embedded (RTE) middleware solution that simplifies programming of heterogeneous processing applications requiring a mix of field-programmable gate arrays (FPGA), general-purpose processors (GPP), digital signal processors (DSP), and high-speed switch fabrics. The âoemixâ can be over a lifecycle (technology insertion) as well as within a single implementation (to meet SWAP constraints). CPI improves code portability, interoperability, and performance in FPGA and DSP-based environments by providing well-defined waveform component APIs (application programming interfaces) with a set of infrastructure blocks that act as a hardware abstraction layer (HAL). CPI is also appropriate for the incorporation of GPU and multicore technologies. CPI is uniquely positioned to meet the goals of S3 since in some sense component-based systems are computer-scienceâ(TM)s answer to dealing with âoeknowledge captureâ and lock-up of intellectual property (IP). sign up here: http://lists.opencpi.org/listinfo.cgi/opencpi_announce-opencpi.org
Both Verilog and VHDL can be used as either a modeling language, or for synthesis. You need to learn synthesis. There are some texts that treat the language from this view and I strongly recommend you find one. Verilog is a little easier to learn.
This really is not a task for programmers. It is a task for an engineer that has done both logic and software design. I've been programming FPGA's since Xilinx came out with their first chips. At the time, it was all schematic capture. Place and route never completed on its own, it always required user editing to finish. FPGA design techniques depend on your constraints. For some projects, it is much cheaper to buy a very large FPGA and not worry about space optimization. If you are building thousands of the same device, then space optimization is critical. For other projects, logic timing is everything. Every chip has it's own constraints as well, especially if speed is an issue. When speed is an issue, you have to really understand how your VHDL will be implemented, because it will make all the difference between sucess & failure. Learning how to use constraint files is important. Learning how to test using simulations is critical. Time spent writing and runing simulations may exceed design time for an order of magnitude.
On the matter of tags... What the hell are those "story" tags for?
Truth arises more readily from error than from confusion. -Francis Bacon
Kirk Weedman, KD7IRS, has posted some good Verilog classes on http://verilog.openhpsdr.org/ that are tailored to amateur radio enthusiasts that have been working on the High Performance Software Defined Radio (HPSDR) an interesting open source hardware project.
I especially like Altera's "Nios Embedded Evaluation Kit" (aka the NEEK). It has its own TFT, sound codec, analog video input, ethernet and lots more. It also has a thriving uClinux community and they're working on including MMU support. Plus, you don't need a programming adapter for it - just put your hardware design on an SD card, insert into NEEK, power up, and off you go. Ok, it costs $449, but you can do far more than push a few buttons and let LEDs light up.
iPhone users.
http://www.ashenden.com.au/designers-guide/DG.html with some support stuff.
No. When you upload your C/ASM-code to your ÂC, e.g Atmel, then âoeyou are programming to tell the *hardware* what to doâ. Downloading to an FPGA is like telling it what to be.
For someone with a programming background planning on doing circuit development, you may prefer to work with microcontrollers. My experience with fpga's has been interfacing existing processors with peripheral devices, or signal processing applications that must be done very quickly. Another use is for performing very specific tasks in massive parallel, as a colleague of mine has done, but I do not have first hand experience in this utility.
However my understanding in all cases is that there is a big learning curve for doing these kinds of things.
If you want to blink some lights, turn on lcd screens, interface with accelerometers, etc. i would suggest mC as a much-much cheaper alternative ($0.90 compared to fpgas in the $100s ). Or for more advanced applications you could look into gumstix($169) which are full featured computers smaller than a stick of gum!
That being said you could use some of the xilinx toolkits for matlab to simplify your work, but for the most part in my humble opinion for amateur eletronics fpga's are a bit too complicated.
Oh, you must be in HR.
What makes you think he cant teach himself. People have been experimenting with electricity and electronics since it's discovery. Do you think Marconi or Edison had degrees in Electrical Engineering?
I suppose it's also futile to give a child an electronics kit since a grade-schooler cannot possibly have a sheepskin yet.
In my career, I've seen more Masters and PHD Mechanical Engineers who couldn't design buildable machines than I ever thought possible. What are they teaching you kids today? It certainly isn't to think for yourself
NOW GET OFF MY LAWN!
Consider the OGD1 card from the Open Graphics
Project. Big FPGA, and video outputs (2x DVI 1x s-video)
http://opengraphics.org/
Altera, www.altera.com has a version of their FPGA development software for Linux -- Quartus II. This tool allows FPGA development for many Altera eval boards, and is available for free via their website. My personal preference is to develop in Verilog rather than VHDL. The syntax is more familiar to someone who also develops firmware in C/C++. Overall, though this is a personal preference. Each language has its opponents/proponents.
There's a Spanish startup, Forware, that develops FPGA development tools and has a growing user community. Not sure about the conditions, though.
To do list for Windows
The AC's comments are valid and noteworthy nonetheless. Just because someone understands OOP and knows 5 software languages doesn't mean hardware hacking will be easy. The skills are related, but proficiency in one does not necessarily imply aptitude for the other.
I recommend two things. First, give up the notion that FPGA development as a hobby can be done for the price you're looking for. Good development boards are a little pricy, but you will frustrate yourself with no end in sight by using a barebones development kit. The best cheap dev kit I've seen yet is the Xilinx Spartan-6 SP601 kit. It includes everything you need to get started, including Xilinx ISE design software. That should set you back about $300. The Spartan-6 is fairly anemic in features and power compared to most other new FPGA's so a careful consideration of your goals should take place before you make a purchase.
Two, get a good FPGA development book. I highly recommend "Designing with FPGAs and CPLDs". It's a really useful primer on programmable logic hardware to those who already are technically literate.
http://books.google.com/books?id=enQq7m800xYC&dq=embedded+FPGA
You can't legislate goodness. Let each to his own destiny, by will of his freely made choices.
You Could always try Altium designer ? www.altium.com it's windows based but covers a broad spectrum of FPGA (not a single brand) and covers the whole electronic design process. Also at the moment they are have some very cheap pricing.
Now you're going to get it. Mr. Smart Fecal Matter, repeat after me: MARCONI AND EDISON WERE NOT teaching themselves to write an HDL. Marconi was trying to make wireless communications work, and Edison was throwing any and every idea attempting to come up with useful inventions. What did they have in common? THEY WERE WORKING WITH RUDIMENTARY CONCEPTS. We are talking Maxwell's Equations even if those as a lot of their work was done empirically. An HDL? Think of how many levels of hardware AND software abstraction you have to understand before you can even begin to get a basic grasp of an FPGA logic block.
Sorry, sir, but you are a complete moron. If I were your parent, I would have you committed.
I would suggest Altera. The toolset is amazing compared to Xilinx. Xilinx is notorious for horrible tools. I even met a manager who works on the tools at Xilinx and he agreed: they suck.
You won't really notice a difference in FPGA performance unless you do something really fancy. Get a cheap Altera board and use their IDE because Xilinx tools are very very very buggy.
with what he had to say:
To me, that reads like he thought Altera's licensing scheme was better, easier, simpler. My understanding and belief is that was never true -- it was advantage Xilinx until they decided to tie it up by also succumbing to FlexLM. But, the offer at the end of my email remains -- if he thinks Altera licensing is better, by all means let him explain himself.
Spartan 6 is anaemic? What are you trying to build? I am working with a Raggedstone Spartan IIIe card (the mini-can); it's US$150 and I'm developing PCI hardware with it. That's hardly anaemic. There's lots of fun to be had with smaller devices as well.
The question is a good one to ask.
Finding cheap FPGA dev boards is not all that tricky, depending on your needs.
I am in a similar situation:
I am trying to locate a cheap FPGA dev board with a PCI interface. Ideally, with a PCI logic chip on the board so I don't have to design and verify the PCI logic. By cheap, I mean around $200 US.
If anyone knows of anything apart from the RaggedStone (which looks pretty good) I would like to hear about it.
Cheers.
S.
Take a look at the Demand Peripherals Baseboard4. It uses standard USB-serial for code download instead of JTAG and the development is even Makefile based. Hope this helps ....
Read through some of the tutorials at http://www.fpga4fun.com/ and then head over to the sister site http://www.knjn.com/ to find some FPGA boards. You can get a very good introduction to FPGA concepts for less than $50. The Pluto boards with Altera Cyclone FPGAs are perfect for getting your feet wet.
If you want to start learning FPGAs, then first logical step is to learn CPLD first. I have written small step by step tutorial for beginners : http://elecrom.wordpress.com/2008/03/02/getting-started-with-xilinx-xc9536/ Hope it helps.
Hi, Regarding the development on the FPGA, I didn't see anyone suggesting Handel-C (proprietary from AgilityDS http://www.agilityds.com/), or SystemC (http://www.systemc.org/). I have only used Handel-C to be honest, during a course of my MSc. Not to bad for beginners I think, I would suggest it. Although it lacks support for any platforms other than Windows...
I'm using Altera tools for work right now. We have a paid seat, but even in free mode, the web kit is powerful enough to do pretty complex stuff. To experiment with the software, go to altera.com, click download in the upper right corner and download the web kit. Unfortunately, the linux version is not free but you can use it for 30 days without a license. Xilinx also has a free version you can use. As for development boards, here's the cheapest FPGA board I found for Altera: http://www.altera.com/products/devkits/altera/kit-cyc2-2C20N.html I'm using the Cyclone III version of that board. Its quite good. For a Cyclone I board, these look inexpensive and have a wide range of features: http://www.knjn.com/ShopBoards_USB2.html Xilinx has a lot of development boards as well. My experience with Xilinx is better in the support department than Altera. They will give you the software and even dev hardware if you ask nicely. But their software takes more than 12 hours (yes twelve hours) to install and update on a core 2 duo machine. Sad really. The altera software is lighter feeling but just as powerful and seems to be more ... what's the word: friendly. I haven't used Xilinx in a while but I had a hellofa time with it, when I was trying to prototype asics with Virtex II.
Altera is currently under mandate to make money from their software, even though they are a hardware company. That makes getting a free license almost impossible. Too bad for them.
I've been getting great support for Altera from Octera Solutions (as opposed to Altera itself). Perhaps they can help you.
If you're brand new to hardware, you might want to learn Verilog or VHDL first. I think both Xilinx and Altera's web kits come with Modelsim. Its a stripped down version but it will be fine to learn the basics.
Hello.
I would consider myself as master programmer (professional experience > 10 years), with very considerable experience on embedded programming and networking.
I've recently self taught myself as amateur hardware engineer. It has been very useful to be master in parallel programming techniques and understand the parallel actions mindset as parallelism in hardware design is the most significant difference to software design which is often very serial. I started with VHDL but moved to Verilog, because I tend to like verilog level of verbosity. VHDL is extremely verbose. Also, my development tools supported systems verilog, which appeared to be quite a good way to do "test driven hardware design". Anyway, I first started with Altera Cyclone III Starter Board, which seemed quite nice.
I was quite fun to play with it. I had quite a soon environment up with ucLinux and NIOS II. And it felt pretty much home to write code for the embedded processor and occasionally enhance the board with self-designed peripherals.
Anyway, after playing with the FPGA I found out that using good hardware simulator (such as Mentor Graphics ModelSim) is often better for designing small hardware components than actual FPGA. The debugging is much more precise and you get easily ran the system in "step-by-step" mode. ModelSim PE is very expensive, but you may find restricted versions from FPGA vendors for free. I got free version for Altera, not sure if its still free, the Actel one should be free.
After looking at things, (my work has paralleled hw design), I've noticed these things: If you like fancy embedded soft core processors, get lowest costs Actel M1 you may find (it can be loaded with ARM M1 which is pretty much as good as you can get for generic CPU like CPU for softcore on FPGA.)
$295 (does it fit you budjet) is price for soon available Spartan-6 is quite nice price.
Compared to typical Spartan-3 board advantage is much higher Hz for designs and niceties on board - lots of RAM and NIC.
The soon available Virtex-6 board seems superb. Fits designs that were previously only for 10k or higher cost equipment. Out of your price range but brings much lower cost of designs. ....
Summary: For learning and small designs: Use ModelSim. No cost neccsarry.
For trying etc. Spartan-3 or Cyclone-III or wait Spartan-6 (soon available).
For embedded processing: Xilinx is good or if you want real processors Actel.
Hope this helps.
HDL doesnt tell the hardware what to do, it decides how the interconnects are configured. if you make a simple counter to count from 0-2 in software, it will probabaly end up being a 0-3 counter cause what u built via software is essentially a 2 bit hardware counter. u WILL have trouble with hardware description if u r from a purely software background.
http://ftdichip.com/Products/EvaluationKits/FPGA.htm
Runs from usb power, plugs into a breadboard, and it's cheap. ( £86 )
http://apple.clickandbuild.com/cnb/shop/ftdichip?op=catalogue-products-null&prodCategoryID=5&title=USB+to+FPGA
Also, they're based in the UK - so easier for you to get a hold of.
Hi
You should check this blogg, this guys had some time over and started from scratch and have documented it in a very good way
http://svenand.blogdrive.com/archive/11.html
I not really sure how this compares to other options.
I'd be interested in the thoughts of those more expereienced.
.
US$229
500Mhz ARM9 CPU running Linux
onboard 12,000 LUT on-board programmable Lattice FPGA
http://www.embeddedarm.com/products/board-detail.php?product=TS-7800
.
US$84
250MHz ARM9 CPU running Linux
onboard 5000 LUT Lattice FPGA
http://www.embeddedarm.com/products/board-detail.php?product=TS-7500
When hobbyists get interested in FPGA development, the first thing they turn to are Altera's and Xilinx's websites and look at top of the line FPGA's like the Virtex 6 LXT. The Spartan 6 is definitely a lightweight compared to the Virtex features.
A newly interested hobbyist should not be under the impression that they can spend $250 and it will have the same features.
You can't legislate goodness. Let each to his own destiny, by will of his freely made choices.
I disagree. I think a hobbyiest can take a look at the simpler, smaller, cheaper devices and have lots of fun without jumping to the top-end parts. Hell, they could have a ton of fun with CPLDs too, although they'd become pretty limiting in a hurry.
Yes, Spartan6 is a lightweight compared to the Virtex line, but again... we're talking about getting started in FPGAs. I think throwing a ton of money at a dev board that will be severely underutilized for months, if not years, is a fast way to turn people off of learning about FPGAs.
Might I suggest looking at
http://microcontrollershop.com/
for purchasing whatever you decide upon.
They sell most of the stuff everyone here has suggested, as well as some books to assist you in learning.
You might also want to chose some sort of project/goal to aim yourself at.
It's easier to stay focused on moving forward with a goal in mind.
regards
If you read my prior posts, you would get it. I *said* that the guy is better off taking himself to the guillotine and killing himself because he is trying to learn an HDL without any prior basis. Do you understand what this means, tool? It is a complete barrier to entry, and if he is posting to Ask Slashdot, chances are that he does not have the ingenuity to teach himself the prerequisite underlying principles. Amen.
Having fairly recently gone through the same process the steps I took are still fresh in my mind. I would recommend doing the following:
-Get a good understanding of digital electronics, you need to understand the building blocks that HDL languages such as Verilog and VHDL describe. Learn about flip flops, latches, counters, shift registers, and memories. With HDL you are describing how these basic building blocks connect rather than the sequential programming you may be used to. So go to Amazon and buy several used books on "Digital Electronics" or "Digital Fundamentals". You will be using these concepts to solve problems with HDL so it is important. Think of it as the equivalent of a "Data Structures and Algorithms" book for programming.
-Once you have a basic understanding of Digital Electronics then it is time to start learning an HDL. One of the biggest trip ups that I ran into while learning VHDL was the distinction between VHDL for simulation and VHDL for RTL synthesis. I was finding VHDL examples and tutorials on the web that did not explain the difference. There are many VHDL examples on the web that are only valid for simulation but do not work for RTL synthesis. So I ended up writing VHDL code that worked great in simulation but would blow up when I tried to synthesize it to run on a board. I wasted many, many hours before I found a book that clearly explained the difference. So get a book that focuses on RTL synthesis to avoid confusion in the beginning. The book that I found very helpful was Essential VHDL RTL Synthesis Done Right by Sundar Rajan. This book truly was the key, for me, to being successful with VHDL. (Search around for a better price, I did not pay over $100 for the book)
-Another great book that isn't necessarily important for HDL learning but has many easy to understand electronics solutions is Practical Electronics for Inventors by Paul Scherz.
Finally, get involved with open source FPGA projects, there is nothing like studying the code of working projects. Head over to http://www.gadgetgactory.net/ which is a new FPGA Open Source community trying to make FPGA's more useful and accessible. You will find:
-A completely open source FPGA circuit design, the Butterfly Platform, that you can build yourself or purchase pre-assembled and tested. This board can fulfill your development needs and has the advantage of being actively developed for. Most dev boards on the market have examples that you can work through but once you get through all of them you are on your own. The goal of the Butterfly Platform is to find the best FPGA open source projects available and get them all running on this board.
-An open source Logic Analyzer design that is both useful for your electronics workbench but is also an amazing example to help with learning VHDL.
-An AVR compatible processor that supports the avr-gcc toolchain for C development. (Still a work in progress)
-Tutorials and Screencasts for basic FPGA tasks.
Take a look around and see if there is anything helpful. The site is in heavy development right now so keep checking back for more projects, tutorials, and FPGA wiki's.
Jack.
An FPGA load is something very different from software... Exactly what an FPGA bitstream should be defined as is still the subject of much controversy and debate due to being in such a grey area.
As I see it, software is machine-executable code that runs on a processor.
An FPGA is a whole different animal - FPGA code doesn't execute, it effectively defines the internal wiring of the FPGA. It is most definately not, in my opinion, "software".
It isn't exactly hardware as it is reconfigurable and defined by some memory contents, but in general, it's very difficult to create an FPGA bitstream without a good fundamental understanding of digital logic design, which is a hardware field, not a software one. An FPGA designer must be aware of many design constraints on the bitstream such as gate propagation delays and timing. Thus, an FPGA article most definately is deserving of a "hardhack" tag.
retrorocket.o not found, launch anyway?
My advice for learning fpga programming is the same for learning a regular programming language: it's a lot easier to stay motivated if you're not just learning for learning's sake, but have some particular project in mind. This is where I got stuck; I read a big thick book on verilog and got myself a development board and all the software set up, and I figured out how to make the LEDs blink faster or slower, but then I got distracted and never actually went on to do anything more complicated.
You are definitely right, it is best to get a low cost FPGA board to start learning. You will definitely find it fun and satisfying. Video 3 on this page is "FPGA boards and general advice on what to get" http://www.burched.com/freevideos.ag.php There are some other videos there that will help you with learning.
If you have any background in "C" or "C++" then use Verilog - the I/O routines are very similar, making testbenches easier to write than in VHDL (at least for me, anyway) I started out learning VHDL, but switched over to Verilog and I'll never go back.
Another good reason to use verilog is that you can use the very useful Icarus verilog simulator from http://www.icarus.com/eda/verilog/ - I used it in addition to professional products such as Cadence ncsim or Mentor Modelsim and found that the price/performance ratio of Icarus is extremely good (since it is free and performs well). Naturally the professional products have more bells and whistles, but the versions which are provided for free with FPGA development kits are limited in the size of project they can simulate.
Note - if you use icarus you will need a free waveform viewer to view the simulation results - I found gtkwave and dinotrace do the job quite well, or see wikipedia for a more comprehensive list.
The Spartan 6 is definitely a lightweight compared to the Virtex features.
And a quad-core Xeon is a lightweight compared to a Beowulf cluster of Crays, or whatever. Hardly anybody needs a high-end Virtex part, and certainly not for learning.