Slashdot Mirror


gEDA (GPL'ed Electronic Design) In EE Times

Stuart Brorson writes "At long last, today's EE Times published an article about the gEDA project. The gEDA project has developed a mature, GPL'd, Linux-based suite of tools useful for electronic design. Using the gEDA tools, you can take a circuit design from schematic capture, through simulation, to PC board layout and fab. Some example PCBs done using gEDA include the Darrell Harmon's single board computer, and the 'free hardware' Ronja Project. Happily, the advantages of open-source for electronics design were well presented in the article. It's good to see that gEDA is getting some well-deserved press for the excellent work which has been going on from over six years now!"

89 of 170 comments (clear)

  1. gEDA is still lacking a PCB editor... by Lisandro · · Score: 4, Interesting

    ... which, for me, it's a showstopper and forces me to use EAGLE (which is excellent and available for Windows and Linux, but not OSS). PCB seems to be powerful, but i simply cannot get accostumed to it's interface.

    The rest of the package is quite good though, and i have to agree, they've come a long way in these six years. Kudos to the developers!

    1. Re:gEDA is still lacking a PCB editor... by dj.delorie · · Score: 5, Informative
      PCB seems to be powerful, but i simply cannot get accostumed to it's interface.

      As one of the few people actively working on PCB, I can only say this: If you don't tell us what you don't like, we can't make it better. As with all open software, YOU the user are an important part of the development process, even if all you do is [constructively] complain.

      Recently, I added user-customizable menus. Have you tried changing the UI to do what YOU want? That's why I added it.

    2. Re:gEDA is still lacking a PCB editor... by Lisandro · · Score: 2, Interesting

      Didn't mean to diss, sorry.

      My main quirk is the lack of integration with the rest of gEDA - on interface and other issues; for example, on EAGLE i can modify a schematic on the capture program and have the changes reflected automatically on the PCB design, and viceversa.

      Having said that, i've just emerged PCB v1.99 (i can't recall the last version i've tried, but it was a while ago). It seems to have got quite better. I have some single-sided boards to design and will give it a shot - complete with feedback from the user experience. I was planning to dicth the EAGLE schematic capture part anyway, so gEDA seems like a good starting point.

      PS: Don't mind assholes like me. I've said it before: this is a powerful program indeed; thank you for working on it for free.

    3. Re:gEDA is still lacking a PCB editor... by goodie3shoes · · Score: 3, Insightful

      Thanks to Mr. Delorie for his many improvements of PCB. I use very expensive proprietary schematic and PCB software at work, but am quite happy with PCB and gschem at home on my Linux box, where I make DIY projects. I'd like to reinforce that it's easy to whine (whinge) about features and capabilities, but a bit harder to code them.

      --
      BSA: "Would you like a free Software Audit"? me: "No, thanks. My software is all Free".
    4. Re:gEDA is still lacking a PCB editor... by dj.delorie · · Score: 2, Interesting
      i can modify a schematic on the capture program and have the changes reflected automatically on the PCB design, and viceversa.

      Funny you should mention that, we were recently pondering how to do that. If you've got ideas or experience with annotation files, we could use the help ;-)

    5. Re:gEDA is still lacking a PCB editor... by Lisandro · · Score: 1

      Well, i don't know how integrated is PCB with gEDA (under the hood, that is), but what could be done is to save a hash and name of the netlist file that originated the PCB file with it (if any), and, if the hash changes, between saves or during editing, adapt the PCB file accordingly. That would work if the schematic capture and PCB have no other way of comunicating with each other.

      I know it's easier said than done, and in any case, it's not a perfect solution, but it could work. I would help with the coding but lately my free time amounts to near-zero, and i'm re-teaching C myself to boot (writting a compressor, which will become GPL if it happens to work).

    6. Re:gEDA is still lacking a PCB editor... by starman97 · · Score: 1

      "on EAGLE i can modify a schematic on the capture program and have the changes reflected automatically on the PCB design, and viceversa."

      I wish I could get that to work with Orcad and PADS.. But iterating schematics while doing layout is a bad idea. It's a lot better to have the schematic finished before starting actual routing.
      You dont wast nearly as much time fixing things in the layout that got tweaked because you changed a part or package size.

      --
      Starman97@Gmail.com (bring it on spammers)
    7. Re:gEDA is still lacking a PCB editor... by Lisandro · · Score: 1

      Yet, it happens. It's nitpicking, but ditching a half-made PCB with 70 components only because you missed a diode can drive a man insane.... *breaks in tears*

    8. Re:gEDA is still lacking a PCB editor... by geirt · · Score: 1
      dj.delorie wrote:
      Funny you should mention that, we were recently pondering how to do that. If you've got ideas or experience with annotation files, we could use the help ;-)

      That is the one thing that Eagle does right, and that most others does wrong. Download the eagle demo and try it. In Eagle you work in the schematics and the PCB layout at once. This makes it easy to update a PCB, make component changes and fix issues with the design afterwards. This works so well in Eagle, that I usually start with an existing design to make a new product. I just strip away most of the components, and keep a few useful parts (voltage regulators, reset network, and may be the microcontroller) and works from there. I don't need to reroute those parts. I also start with layout early (long before the schematics are finished), just to check that I have enough board space, route the timing critical stuff, etc. One you have used that work methodology, you don't want to go back to the akward forward/backward annotation stuff.

      PS: Thank you for DJGPP, I used it a lot in the old DOS days. Thanks

      --

      RFC1925
    9. Re:gEDA is still lacking a PCB editor... by Koyaanisqatsi · · Score: 1

      Dj Delorie? Wow, a flash of wonderful memories from using DJGPP in a couple of big projects back in 1997/1998. Thank you so much for that, I had a great time using it

      Now I'll sure keep an eye in gEDA (as I was just starting to learn Eagle, I might as well do it right to boot and go with the open source product!)

    10. Re:gEDA is still lacking a PCB editor... by alienw · · Score: 1

      That's actually a pretty stupid feature of EAGLE. gEDA does it much better with gsch2pcb. Think about it: what if there are 50 engineers working on that particular board? You don't want a PCB engineer screwing around with the schematic and messing things up. You also want to be able to edit the schematic separately and annotate the changes to the board.

      Basically, the way pcb does it is the way any real EDA program does it (EAGLE doesn't count, it's a cheap product aimed mostly at hobbyists and very small businesses). Also, I wouldn't bitch about PCB's interface until you've used a real EDA program, such as Allegro. That program has such a horrible interface you wonder how the hell it became #1.

    11. Re:gEDA is still lacking a PCB editor... by FuzzyDaddy · · Score: 1
      You actually can just work in the schematic as well, then generate the board. If you don't like the board, you can delete the board file and regenerate a new one. You have to place all the components again, though.

      Also, eagle severely limits what can be back annotated from the PCB to the schematic - in fact, there seems to be very little that it WILL let you do in that direction.

      --
      It's not wasting time, I'm educating myself.
    12. Re:gEDA is still lacking a PCB editor... by alienw · · Score: 1

      You actually can just work in the schematic as well, then generate the board.

      True, but with gsch2pcb you don't need to delete the board. You can just run the command, and it will add and remove the requisite parts and regenerate the netlist without destroying the board. My point is, a design engineer can make changes to the schematic while the board is being worked on. EAGLE will only let you do that if the two engineers somehow work at the same machine.

      Also, eagle severely limits what can be back annotated from the PCB to the schematic - in fact, there seems to be very little that it WILL let you do in that direction.

      Yes. However, you can just click over to the schematic window and wreak havoc. This can easily happen unintentionally. This possibility does not exist in PCB, since the PCB engineer won't be using the schematic editor.

  2. Mature tools my ass by raider_red · · Score: 4, Funny

    We payed millions and didn't get a set of mature tools from the major EDA vendors. How are they expecting to develop the same with no budget?

    --
    It's good to use your head, but not as a battering ram.
    1. Re:Mature tools my ass by RealAlaskan · · Score: 2, Interesting
      We payed millions and didn't get a set of mature tools from the major EDA vendors. How are they expecting to develop the same with no budget?

      Sounds as if the bar has been set pretty low. If the major vendors are giving you immature crap, these guys might be able to do better, even with zero budget.

      It's sort of like the story of the software monopolist with the multi-billion dollar budget and the zero-budget, GPL operating system which might yet out-compete the monopolist's amazingly expensive OS.

    2. Re:Mature tools my ass by Lisandro · · Score: 1

      There are mature EDA packages indeed; notably Protel, which is quite expensive but powerful and let's you cover almost every aspect of electronic CAD.

      I think such quality can be achieved with OSS; in fact, the working parts of gEDA are quite mature indeed, like the schematic capture and SPICE simulator. OSS tends to move slower though, but given enough time gEDA could be there.

    3. Re:Mature tools my ass by rewt66 · · Score: 3, Insightful
      No, the problem is that users set the bar very high.

      See, OS kernels, compilers, word processors, and that kind of stuff are old hat now. There aren't any staggering breakthroughs being made in proportional-spacing algorithms these days. So OO.o, for example, has not too hard of a time creating a word processor that does just about anything anyone will ever need a word processor to do.

      EDA is a whole different ball game. The leading-edge designs that people want to do are beyond the capabilities of the current software, even the software from the major vendors. Users need staggering breakthroughs, just to make the tools adequate for handling the user's current designs.

      I'm not saying that open source can't compete here. But it's very different from "yeah, open source can build an OS that doesn't crash." That was a low bar that one particular vendor's stuff had a lot of problems with due to very bad design; OSS cleared that bar quite handily.

    4. Re:Mature tools my ass by mollymoo · · Score: 1
      It's sort of like the story of the software monopolist with the multi-billion dollar budget and the zero-budget, GPL operating system which might yet out-compete the monopolist's amazingly expensive OS.

      It may become like that if, as happened with GNU/Linux, some companies get in on the act. Zero-budget is completely wrong. A fair bit of the funkiness in the Linux kernel has been provided by the likes of IBM and Red Hat. They are not zero-budget companies.

      If some company with a vested interest in EDA software thinks "hey, let's see what we can get if we spend that million bucks employing half a dozen geeks to work on the GPL stuff" then we might see gEDA improve by leaps and bounds in the way the Linux kernel and other open-source software has.

      Don't get me wrong, open-source software written in an ad-hoc way produces some decent results and I use it a lot, but sometimes you need full-time people with a sense of direction to add the refinement and polish and provide the support needed to convince the beancounters it's worth investing in.

      Without the likes of IBM and Red Hat contributing code and offering support I bet you wouldn't have a single blue-chip company running a Linux box.

      --
      Chernobyl 'not a wildlife haven' - BBC News
    5. Re:Mature tools my ass by SagSaw · · Score: 2, Informative

      The bar has been set pretty low, especially for basic usage. I use OrCad Capture and Layout at work for fairly simple circuits (Generally small circuits for test fixtures and one-off projects). Way too often, I find myself wondering how Cadence manages to get close to $10,000 for two programs with as many bugs and quirks. For example, there is only rudimentary copy-and-paste functionality in Layout, and Layout doesn't always recognize a disconnected pin as a design-rule error. Capture insists on writing to the installation directory when options are changed, rather than a per-user configuration file.

      To be fair, you get some good features for that price, except that the casual user probably doesn't make extensive use of high-end features like autorouting or the ability to route on an extreme number of layers.

      --
      Come test your mettle in the world of Alter Aeon!
    6. Re:Mature tools my ass by shokk · · Score: 1
      I like this line:

      "For engineers who just need to do something quickly and don't want to mess with commercial tools, this is what they use."

      Interpretation:

      I'm not really serious about this stuff, I'm just screwing around. I hope someone has a use for a logic cell that doesn't clock too well at yesteryear's bus speeds. Oh darn it, this poly menu is grayed out again, what do I do now? And why is that square on my screen red again? Welp, gotta run off to my shift at 7-11!
      --
      "Beware of he who would deny you access to information, for in his heart, he dreams himself your master."
    7. Re:Mature tools my ass by bit01 · · Score: 2, Interesting

      I'm not really serious about this stuff, I'm just screwing around. I hope someone has a use for a logic cell that doesn't clock too well at yesteryear's bus speeds. Oh darn it, this poly menu is grayed out again, what do I do now? And why is that square on my screen red again? Welp, gotta run off to my shift at 7-11!

      Reinterpretation:

      For engineers who are not commercial software bigots. They use good software where they can find it and recognise that the software industry is becoming increasingly commoditised. Open source and freeware is simply statistics; with 6,000,000,000+ people in the world and with widely used software it is statistical certainty that somebody somewhere will have both the means and the motivation to create good free/open software for use by others. And once it's been done once, it can be copied millions of times; the multiplier effect is enormous.

      ---

      It's wrong that an intellectual property creator should not be rewarded for their work.
      It's equally wrong that an IP creator should be rewarded too many times for the one piece of work, for exactly the same reasons.
      Reform IP law and stop the M$/RIAA abuse.

    8. Re:Mature tools my ass by alienw · · Score: 1

      I have to really disagree with you here. Most expensive EDA tools (schematic/PCB type stuff) have been pretty much unchanged for the last 5 years or so.

      Look at all the pricey crap put out by Cadence, for instance. Their basic schematic/pcb tools have same interface and roughly the same guts as the Windows 3.11 versions did in 1992. And the programs have so many glaring bugs and omissions, you wonder how they ever made it past the QA people. Of course, gEDA lacks so many features and has so many bugs that it's not even a contender, but I really wouldn't say the bar has been set very high.

      Of course, you can't expect someone to put together a free tool for ASIC design or something equally arcane, but basic tools for schematic drawing and PCB layout are not that difficult (and much more useful). Given that commercial EDA software is not tightly integrated and uses relatively open formats, it shouldn't be that hard to make a viable alternative to Capture or Allegro.

  3. FINALLY! by Thunderstruck · · Score: 5, Funny

    The last time I had to design a circuit board, the boss told me to find a way to do it for free. We found some demo software on the internet that would print out samples of the board overlaid with a grid. (To remove grid, buy the software.) We then had to print to plastic and scrape the grid off with an exacto-knife.
    While I no longer do this kind of work, I am pleased to see future generations will never have to worry about irrational demands from the boss. (right?)

    --
    Trying to use sarcasm in text-based forums does not work.
    1. Re:FINALLY! by mollymoo · · Score: 1
      The last time I had to design a circuit board, the boss told me to find a way to do it for free.

      And the buy wouldn't even give you a pen and a pad? That really is tight...

      --
      Chernobyl 'not a wildlife haven' - BBC News
    2. Re: FINALLY! by Alwin+Henseler · · Score: 1
      The last time I had to design a circuit board, the boss told me to find a way to do it for free. We found some demo software on the internet that would print out samples of the board overlaid with a grid. (To remove grid, buy the software.) We then had to print to plastic and scrape the grid off with an exacto-knife.

      Why not use paper & pencil for the design, take copper-plated circuit board, and scrape off the copper directly? Ah, anyway, just think of those poor folks in China that recycle some of our electronic trash. At least you get do the creative end of the work. So stop whining! You should be grateful to have a boss that empowers you to do such high-tech work!

      Back in the days... oh never mind

    3. Re:FINALLY! by HermanAB · · Score: 1

      Protel Demo, Orcad Demo, Eagle Light, PCB Express...

      Maybe next time, use Google and look for "Free PCB Design Software"...

      --
      Oh well, what the hell...
    4. Re: FINALLY! by ChrisMaple · · Score: 1
      Why not use paper & pencil for the design, take copper-plated circuit board, and scrape off the copper directly?

      I've actually done that for small PCBs: one 14 pin IC and a few discretes.

      I've also laid out several PCBs as large as 10 x 10 inches using AutoCAD. Plot on paper, photograph. 1987 through 1991.

      --
      Contribute to civilization: ari.aynrand.org/donate
  4. Mixed-Up. by Anonymous Coward · · Score: 2, Insightful

    So how well do the OSS tools do with mixed-signal designs?

    1. Re:Mixed-Up. by Lisandro · · Score: 3, Informative

      gEDA has a mixed mode simulator program called Gnucap. I haven't tried it, but seems to be quite powerful, even while it's still work in progress.

    2. Re:Mixed-Up. by calidoscope · · Score: 1
      gEDA has a mixed mode simulator program called Gnucap. I haven't tried it, but seems to be quite powerful, even while it's still work in progress.

      I've used gnucap (formerly ACS) quite a bit and it is fairly competent. It is missing some stuff that has been in SPICE for a while (coupled inductors are one thing that come to mind). Plotting requires an external program (e.g. gnuplot). I'm not particularly bothered by the lack of a built-in schematic capture, though some might be.

      My previous SPICE experience had been PSPICE running on DOS and the original SPICE written in CDC "run" FORTRAN running on CALIDOSCOPE - punched my first input deck almost 31 years ago.

      --
      A Shadeless room is a brighter room.
  5. Never Underestimate... by Kjuib · · Score: 4, Funny

    Never Underestimate the power of Geeks who are bored out of their mind!!

    --
    - Your stupidity got you into this mess, why can't it get you out? -Will Rogers
    1. Re:Never Underestimate... by 4of12 · · Score: 1

      Never Underestimate the power of Geeks
      ...who feel like they've been getting shafted with crappy tools, high prices, unresponsive and ignorant help desks.

      You can bet they'll develop an application without mufflers that will scare children and dogs.

      --
      "Provided by the management for your protection."
  6. Never Underestimate...Idle Minds. by Anonymous Coward · · Score: 2, Funny

    "Never Underestimate the power of Geeks who are bored out of their mind!!"

    It's called "The Slashdot Effect".

  7. Re:Hey asshole, by Lisandro · · Score: 4, Interesting

    never bitch about GPL software. The source is there, so either submit some patches or shut the fuck up. That's the GPL way. I don't, i'm just pointing it out. I've used gEDAs' schematic capture and SPICE simulation and found both to be very mature (and useful). Like i said, it has evolved quite a lot. But a PCB designer is an integral part of a electronic design software; it's pretty sure anything you'll design on a computer will end up on a PCB. Sadly, gPCB was abandoned. I would like a PCB designer well integrated to the suite rather than a separate program, no matter how good.

  8. Give it time... by Anonymous Coward · · Score: 2, Insightful


    (emphasis mine)
    dubbed gEDA for short -- has become, much to the delight of engineers who would rather go their own way than rely on commercial tools. It won't replace commercial software packages, but it does provide an alternative.

    ... yet. Every desktop converted to open source means one less commercial package has been sold.

    1. Re:Give it time... by shokk · · Score: 1

      One more skill commoditized overseas. As the great Stephenson once wrote, one day we only have pizza delivery as the great American skill.

      --
      "Beware of he who would deny you access to information, for in his heart, he dreams himself your master."
    2. Re:Give it time... by advocate_one · · Score: 1
      yet. Every desktop converted to open source means one less commercial package has been sold

      NO, there's plenty of room for commercial packages to run on open source desktops... what this gives is the tools to someone who otherwise wouldn't be able to raise the capital for a more polished, professional quality, closed source solution. It gives the closed source solutions proper competition... they can't just rest on their laurels, they have to improve what they're offering for money.

      --
      Donald 'Duck' Dunn: We had a band powerful enough to turn goat piss into gasoline.
    3. Re:Give it time... by bit01 · · Score: 1

      One more skill commoditized overseas.

      No, there are far more consumers of ECAD software than producers. That means, overall, industry and the consumer wins.

      ---

      It's wrong that an intellectual property creator should not be rewarded for their work.
      It's equally wrong that an IP creator should be rewarded too many times for the one piece of work, for exactly the same reasons.
      Reform IP law and stop the M$/RIAA abuse.

    4. Re:Give it time... by Mycroft_VIII · · Score: 1

      Well at least my night job's stil layoff safe for a good while.

      Mycroft

      --
      https://signup.leagueoflegends.com/?ref=4c3ed6600b6ea
  9. Great for hobbyists maybe... but... by Anonymous Coward · · Score: 2, Insightful

    ... not yet ready for prime time. As a former engineer who's done work on many multi-signal, multi-layer boards, I can tell you there are reasons why "professional" design/cad software costs what it does. My congratulations go out to the developers, but let's not kid ourselves. No one's going to be jumping on this bandwagon unless they "have to." Just as only a handful of professional web designers would use notepad or vim for web page design, only a handful of hobbyists will use something like gEDA for serious designing.

    1. Re:Great for hobbyists maybe... but... by 808140 · · Score: 2, Insightful

      I haven't used gEDA but I do work in semiconductors and the design software we use is pretty complex; frankly given the small user base gEDA has, it wouldn't surprise me if it were rather behind (you need a fairly large base of developers and users to get a complex open source project going well, I think). That of course is no reason to be disparaging -- the better it gets, the more users it'll have, the better it'll get, etc.

      However, I think your bit about using vim or notepad to write webpages is a bit silly. While I agree that notepad would be pushing it, and being an emacs user myself, I'd like to say that vim is also pushing it, but let's get real. Real, professional web designers don't use stuff like Frontpage or its ilk. That's what unprofessional folks use. The typical web development flow is photoshop (or the GIMP, I guess) for design, which is then handed off to the implementor (who might be the same person) who typically writes all the HTML/CSS by hand (that is, with a plain text editor) and tweaks it until it displays properly on all supported browsers. We'd all love a program like Composer that produces clean, portable HTML/CSS, but unfortunately, these don't exist.

      People that use Frontpage or Dreamweaver are almost exclusively non-professional folks. Professional web design companies (at least, all the ones I've worked with) have people that know design (these use photoshop) and people that know web development (these use a text editor). And that's how it's essentially always been.

      I'm going to assume you don't know this. But you might be trolling...

    2. Re:Great for hobbyists maybe... but... by Long-EZ · · Score: 2, Interesting

      ...only a handful of hobbyists will use something like gEDA for serious designing

      That may be true... this week. But many people said the same sort of thing about Linux, and it's running tons of servers now and is rapidly making inroads on the desktop. Firefox is currently devouring Internet Explorer market share. OpenOffice.org is a great alternative to M$ Office. There are plenty of other examples.

      You may be missing the point of open source software. By empowering users, any code that is used is inevitably improved. A critical mass phenomenon occurs where the more users there are, the faster the improvements occur.

      EDA is a market that is definitely large enough to prosper as open source, especially given that a large percentage of the EDA users are geeks willing to add to or improve the code. gEDA seems poised to be THE open source EDA solution.

      I use the Linux version of Eagle, and I like it. I particularly like the autorouter. But it won't be long until gEDA will have an improved user interface, integrated PCB layout, an autorouter, etc. In other words, it'll be a full featured open source alternative to commercial EDA software, with none of the annual update fees and licensing hassles.

      I expected open source software would be free, but I was most impressed by the way open source felt. It's hard to describe, but when I wasn't forced to scroll through a 140 KB end user licensing agreement and then suffer through a lot of copy protection crap during the installation, I felt like the programmers were on my side. I'm not opposed to people making money from software, but open source is a lot friendlier to the user, and that attitude carries over into everyday aspects such as open file formats that make it easier to export and translate data or share my work with other people, as opposed to proprietary data formats designed to lock in customers and ensure a steady revenue stream by maintaining a de facto software standard based solely on marketing.

      There are too many advantages of open source for it not to be a dominant force in the immediate future of computing.

      --
      >> My ultraviolent Linux switch video.
    3. Re:Great for hobbyists maybe... but... by cavehamster · · Score: 1

      I use gschem mostly every day to get my job done, and it just works. The interface is the best part: almost everything you do has a two key shortcut to do it faster. It took me about a week to get up to speed with it, but I don't even have to think about it anymore to churn out professional schematics in no time.

      That being said, the two areas that are lacking is the amount of symbols availible (I usually have to create 2 to 4 per project) and the lack of seemless integration with a PCB program. But I think this project has a lot to offer someone today looking to do electronic design.

      I am not a hobbyist, but a small business that specializes in electronic design, and am very thankful this is one less program I need to budget!

  10. VHDL + FPGA by forsetti · · Score: 1

    I am lazy and don't want to look this all up myself if someone else already knows, so here is a question: Left over from my undergrad project, I have a FPGA (XC4010XL from Xilinx) plus prototype board (XS40 from XESS), and have used the Xilinx foundation tools to code up some nice VHDL designs under NT. How can I do similar design work under Linux? Will gEDA suffice? Or, will I need a slew of other tools? Any VHDL environments? Or maybe Verilog? Something else? Are any of you super-smart /.-ers doing this purely under linux?

    --
    10b||~10b -- aah, what a question!
    1. Re:VHDL + FPGA by russh347 · · Score: 4, Informative

      Last time I looked, gEDA had no support for VHDL. There is a GHDL project that is sort of useful, for simulation only. For FPGA synthesis, you're pretty much stuck with the Xilinx (or other commercial) tools. Xilinx webpack is available for free (though it's limited), and I've heard that the command line utilities can be made to run under wine. There are also linux versions of the tools, but I don't know if they have the same availability as Webpack.

    2. Re:VHDL + FPGA by auraleyes · · Score: 2, Informative

      B4. What tools are frequently requested but are not going to be developed?

      These tools are frequently requested, but will not be developed unless somebody steps up for the challenge.

      o IC/ASIC designer.
      o A VHDL/Verilog simulator.
      The FreeHDL project will create a free VHDL simulator which gEDA will use.

    3. Re:VHDL + FPGA by ma++i+ude · · Score: 1
      There seems to be a kind of a geographical divide between VHDL and Verilog, the latter being more popular in the US. There are many more Verilog tools than VHDL. Sure, you can get some VHDL to Verilog converters but that doesn't really solve the problem.

      For my course in VHDL last year, I completed the courseworks using GHDL for simulation and GTKWave 2 to view the waveforms. The combination was fine for my purpose but I can imagine it failing with more complex projects. For synthesis I can choose from tools by Altera, Xilinx and Synplicity, although that wasn't necessary for the coursework.

      I was actually thinking of simply switching to Verilog. One language doesn't really offer any advantages over the other anyway.

      --
      You can't shut us down! The Internet is about the free exchange and sale of other people's ideas!
    4. Re:VHDL + FPGA by rcorlan · · Score: 1

      The newer versions of the Xilinx tools (after 5.2 or so) run natively under linux. They're not free, but reasonably priced. This takes care of place & route. For simulation, there is a VHDL front-end to gcc which works pretty well (or you can fork some serious cash for ModelSim which is also available for Linux).

    5. Re:VHDL + FPGA by runderwo · · Score: 1

      The Linux version of the Xilinx Web Pack will be available (finally) in the spring, said a Xilinx guy who I recently contacted.

    6. Re:VHDL + FPGA by Megane · · Score: 1

      I'd just be happy with an open-source program that can generate a fuse map for any of the three common GAL chips from some high-level description, whether PALASM or VHDL or something else. As far as I know, the only "free" software out there is closed-source and is only available in a DOS version. (Maybe there's something for Windows too now, but that still doesn't help if you don't use an x86 CPU.)

      --
      #naabhaprzrag, #sverubfr-000, #agi-fcbafberq, negvpyr[pynff*=' negvpyr-ary-'] { qvfcynl: abar !vzcbegnag; }
    7. Re:VHDL + FPGA by Arjuna+Theban · · Score: 1

      I was actually thinking of simply switching to Verilog. One language doesn't really offer any advantages over the other anyway.

      Yea.. the only difference is that one (Verilog) is actually used outside of government/military projects and academia.

    8. Re:VHDL + FPGA by tehdaemon · · Score: 1
      My professor called VHDL 'Very Hard Descriptor Language'.

      My guess is that is why verilog is used instead.

      --
      Laws are horrible moral guides, moral guides make even worse laws.
  11. Ronja by Libor+Vanek · · Score: 2, Informative

    Just some info about Ronja - it has inspired a lot of similar projects in Prague (it's all developed by quite small group of ppl in Czech Free Net - www.czfree.net) and there are already running some prototypes of Ronja or derived (non-GPL) projects on 100 Mbit optical data link!

    Unfortunately, main Ronja HW developer - Karel Clock Kulhavy - is very "hard to communicate" man...

  12. Two things that bug me... by SagSaw · · Score: 4, Insightful

    about gSchem:

    First, the developer's insistance that power pins on logic IC's be hardwired, in the symbol, to the nets 'VCC' 'VDD' 'VSS' 'GND' as appropriate. Heaven forbid I have a mixed voltage design or have multiple ground nodes.

    Second, there seems to be no concept of scale to the components, or agreement as to how large a resistor should be relative to a transitor relative to the connection spacing on an IC. Capacitors and resistors appear larger than inductors, while all the descrite components, IMHO, are way to large compared to the connection spacing on IC's. This makes it hard to create a schematic that is clear and easy to read.

    While the interface is really pretty good, they need to put quite a bit of work into the symbol library to make it especially useful.

    --
    Come test your mettle in the world of Alter Aeon!
    1. Re:Two things that bug me... by dpilot · · Score: 1

      I looked into gschem a few years back, and haven't had time, since. At the time, it didn't have what it took for VLSI schematic capture, since it really didn't work well with circuit hierarchy. It really seems to be oriented toward schematic capture for printed circuit boards.

      On the other hand, on any given design I'll have many layers of hierarchy, circuits in circuits in circuits, etc. I need the ability to take any arbitrary circuit and create a symbol for it, so it can be used in another circuit. Further, I'd really like to parameterize some of those symbols, so I can tell an inverter or nand gate what the device sizes of the FETs inside will be. I mentioned this type of thing on the list at the time, and though they were interested in the VLSI problem, they were more focused on PCBs.

      I can accept the VLSI design is a very small market, and that PCB is an appropriate focus. But looking at the page, I see that they may well support hierarchy.

      Shy of emerging gschem (and dependencies) to try it out has anyone used it with hierarchical designs, and can comment?
      (anything about translators for mainstream tools?)

      --
      The living have better things to do than to continue hating the dead.
    2. Re:Two things that bug me... by Suidae · · Score: 1

      I have done designs [...] with a positive power supply called GND and negative called VEE

      [shudder] I hope I never have to maintain your code.

  13. Re:Yarrghhhh by Vaevictis666 · · Score: 1

    what, you mean like this?

  14. It's a good project by jd · · Score: 2, Interesting
    No question about it. I've been following it for a while. There are some hiccups (ngspice died for a few years, had one update in January, then seems to have died again) but that's easily fixed by getting it some publicity, so people know it's out there.


    I would like gEDA to talk with the University of Manchester, who have some excellent electrical design software for asynchronous systems. They've a huge pool of software resources which nobody ever sees because there's no reason to think it might be out there. (There's a Freshmeat entry for one of their packages - guess who added it! - but half of those who last saw it on the front page have died of old age.)


    There's a lot out there that could be used, pooled, collected and gathered. And, damnit, it should be. gEDA is doing a great job, but electrical engineering is a vey big field and gEDA doesn't cover more than a tiny fraction of the problem-space.

    --
    It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
    1. Re:It's a good project by Anonymous Coward · · Score: 1, Informative
      FYI, ngspice issued a release on September 5, 2004. When did Berkeley Spice have a last release? Oh, maybe 5 or 6 years ago (it's officially dead--no more updates from Berkeley).

      Ngspice is a vast improvement its predecessor in at least one important area: Ngspice is eminently hackable and fixable because it uses normal makefiles and GNU configure. (Try fixing Berkeley Spice for a real pain in the ass. It has the most asshole make system you have ever seen).

  15. Open Source in EDA by wannasleep · · Score: 5, Interesting
    Just few comments to clarify what we are talking about here

    First of all, EDA (Electronic Design Automation) is a 30+ years old industry (maybe even 40+, but I wasn't born then). It spans tools whose cost goes from hundreds dollars to few hundred thousands dollars per license. It also spans several fields, from computer science, to systems theory, to physics, to micro-electronics, to chemistry, etc. etc.

    The typical flows for a successfull tools are:
    • a PhD student or his advisor has an idea, writes papers about it and maybe even implements it. Then he starts a company and they make milions with it. Synopsys and Cadence (the two biggest players of the market) were started like that.
    • The same people have an idea and actually have a full implementation and they sustain the basic research. The tool is put in open source fashion (rarely is GPL'd) and every company can modify it. The shiniest example is SPICE . The first version was written more than 30 years ago. Berkeley still owns it and everybody implements variants that are more or less compatible. Either Commercial eda tools (HSPICE, spectre, eldo, adssim) or proprietary implementations that are used within a company (TI spice, ST spice, motorola own spice, etc.). Analog design wouldn't exist without spice.
    • Companies try to dominate the market. They figure out that they need to develop and control a platform. They make it open source (of course all its products work on it, more or less). An example is Cadence with open access. The idea of course is opposed by competitors who try to pass their own platform. Eventually they will reach an agreement

    Of course, there are plenty of others, like magma's case and also plenty of unsuccessfull ventures, but in general EDA has benefitted a lot from open source, and some of the biggest names in the university are still open source fans.
    1. Re:Open Source in EDA by pepsee · · Score: 1

      EDA is indeed 40+ years old. Next year will be the 42nd Design Automation Conference (though the first couple of conferences had a different name).

    2. Re:Open Source in EDA by wannasleep · · Score: 1

      I should have known.. went to dac too many times... lost track I guess... see you there? :)

    3. Re:Open Source in EDA by cgori · · Score: 1

      Actually, Cadence most definitely did not start the way you describe, from a PhD candidate's original research. Cadence then, as now, was built by merger. The original merger was ECAD and SDA, followed shortly by the acquisition of Gateway Design (Verilog-XL), HLDS, CCT, Ambit, Quickturn, Simplex, Get2Chip, etc.

      As a cynical EDA user, I would tell you that Cadence very very rarely (if ever) develops something from internal R&D.

    4. Re:Open Source in EDA by wannasleep · · Score: 1

      Yes, you are right. Cadence originated from the merger of ECAD and and SDA in '89. However, SDA's (Silicon/Solomon Design Associated) was founded (in '85?), among others, by Richard Newton and Alberto Sangiovanni-Vincentelli (both UC Berkeley faculties), Solomon from National(who brought Jo Costello in) and another guy as a reaction to Mentor and other closed-source companies and their point was exactly to use more open source software (I have first and 1/2 hand knowledge on this). Also ECAD comes from UC Berkeley, as it was founded by Ernest Kuh (another faculty at UC Berkeley). So, to keep a long story short, it was not founded by a PhD student, but plenty of advisors did and that was the point I was trying to make.
      As a cynical EDA user/creator I agree with you on the fact that Cadence buys a lot of companies. However, they also do a lot of research, as the large number of papers in major conferences and journals prove

  16. Also try Electric by hexghost · · Score: 2, Informative

    Don't forget Electric, an open source VLSI tool written in java. Sun recently interviewed the author about the challenge of rewriting it in java. Here's the article (with download).

  17. I still prefer OrCAD SDT/PCB 386 by tzanger · · Score: 1

    Protel, OrCAD 9, Eagle... none of these can hold a candle to the ease and simplicity of SDT/PCB386. Pretty much everything has dumped the use of FAST keyboard use to pointy-clicky insanity.

    It ain't a word processor or spreadsheet, guys, it's electronic design. I can route by hand with a keyboard faster than I can with a mouse. pwb,cursor,cursor,cursor... piece of cake. Autorouters are getting better but still suck, IMO. And yes, I do new, modern designs (TSSOP, BGA and all the latest part forms, 6 layer boards, you name it.)

    I did have PCB386 working under DOSEMU but I've since forgotten how I did it. SDT was working fine but PCB was giving me all kinds of issues. I wish I'd written it down, now I'm gonna have to go back and try to figure it out again. :-)

    I haven't checked out gEDA in a long time, I wonder if they're following the path of the big boys (WIMP systems) or if they've come to the understanding that keyboard driven designs aren't dead, nor are they dying.

    1. Re:I still prefer OrCAD SDT/PCB 386 by slashgimp · · Score: 1

      It's nice to hear from some other people that share my perspective on the state of current EDA offerings. I have used OrCAD and Protel (windoze) professionally, and have found OrCAD's bugs to be less annoying than those of Protel's recent offerings. I'm continually annoyed to find that bugs I reported to Protel *years* ago are still present in their software. I'm currently using Protel and curse it daily.

      I've used various OrCAD versions since SDT, and while using 8&9 I was hassling them to toss the source for SDT (the core of which they told me they'd abandoned) into someplace like sourceforge. I, too, liked the interface of SDT (which I used in college) and found it very efficient.

      I've looked at Eagle, PCB and gEDA, and also Lasagne (http://lasagne.sourceforge.net/). Lasagne looks like a *very* promising start, but I couldn't get it to compile and work on Linux/PPC so far. I do plan to email the developer to see if he'd like some help stamping out what look like wrong-endian-specific bugs. Eagle had some promise and recently added MacOS support, although I've never used it for any large jobs...

      I agree with you completely on PCB's choice of units. WTF were they thinking? All new SMT components are defined in metric, not inches. gah. Eagle at least uses some resolution in microns (can't remember what, exactly, though) that made TSOP and TQFP footprint design relatively easy.

      Go check out Lasagne, and note the units indicated in the screenshots :)

      whee!
      Mike

    2. Re:I still prefer OrCAD SDT/PCB 386 by cgori · · Score: 1

      Never used SDT/PCB386, but if your idea of new, modern is a 6-layer board, uhh... we have some 22-24 layer stackups for you to look at with several hundred thousand nets that need hand-routing. Oh and lots/most of them need balanced lengths (sometimes across a 64-bit bus) to within a couple mils, but the contstraints are normally specified on a timing budget basis and have to backed out to an impedance/distance spec, and possible field-solved first. Basically, these boards are starting to look like chips.

      I doubt you are such a masochist. (We use Cadence Allegro for this, and it actually works...)

    3. Re:I still prefer OrCAD SDT/PCB 386 by calidoscope · · Score: 1
      Oh and lots/most of them need balanced lengths (sometimes across a 64-bit bus) to within a couple mils, but the contstraints are normally specified on a timing budget basis and have to backed out to an impedance/distance spec, and possible field-solved first.

      What are you using for a substrate? If your timing budgets are that tight, the variations of even a short trace on FR-4 are going to kill you.

      I do recall Cray being into field solving of PCB's back around 1990 or so.

      --
      A Shadeless room is a brighter room.
    4. Re:I still prefer OrCAD SDT/PCB 386 by cgori · · Score: 1

      I'm not allowed to say, but you are right, it's not FR-4. :)

  18. Good definition of the GPL.. by Anonymous Coward · · Score: 2, Insightful

    [The GNU Public License] lets users download source code and do anything they want with it. But there are some ground rules if people start to distribute software commercially. For one, they have to make the source available.

    That's not a bad way to describe the GPL. Just delete that word "commercially" and you've got a nice FUD-free synopsis... better than what I read in a lot of magazines like InfoWorld, etc.

  19. Re:Hey asshole, by fossa · · Score: 2, Insightful

    This a very prevelant attitude, or perhaps prevelant within a vocal minority. It is however, a terrible attitude. True, we should be very grateful to those who pour their time and heart into the volunteer work that is most free software. If all developers hear is "oh that sucks", they will get discouraged. However, authors should welcome and encourage constructive criticism from users. A large part of designing an [interactive] tool is to observe people using it in an attempt to identify and understand the reasons behind common problems and design flaws so that the flaws may be eliminated. True, this is neither the domain nor the desire of every free software developer nor should it be. But to deride any criticism with the argument "well, it's free and open; fix it yourself" is pointless at best and extremely harmful at worst. When users are too discouraged or fearful to complain, bad software that is difficult to use is the result.

    To developers: If you are not interested in user complaints that is fine. Please state this in your program documentation. We still thank you for your generous gifts as you give them. If you are interested in user complaints, please make this clear so as to not discourage potential insight from the users.

    To designers: Please observe users and listen to and understand complaints; design usable software. We will thank you for your contributions.

    To users: Be grateful, but do not let us go on in ignorance. We want to understand your problems.

  20. Clue alert by Roadkills-R-Us · · Score: 1

    ``Just as only a handful of professional web designers would use notepad or vim for web page design, only a handful of hobbyists will use something like gEDA for serious designing.''

    Far more pros use vim than you might expect. Many of the tools available for web design have only recently become useful, and there's still not much that's very good for *nix. And yet, gazillions of web sites run on *nix, and many of those are built on *nix as well. Not all by a long shot, but lots.

  21. Used it back in the day by The_Wilschon · · Score: 1

    I used gEDA (mostly gschem at that point) back in my sophomore year in high school, (what 4 years ago I guess) and I thought it worked well, very very well considering that it was in alpha at that point I believe. I was designing a fairly simple board to produce some basic square wave output to a speaker for a creative problem solving organization called Destination ImagiNation.

    Of course, I wasn't designing a PC board to be etched, but just drawing the schematic up real nice. And it was by no means a professional project. But for my (extreme low-end) (we had a cost limit of about 100$ for the whole deal, of which my sound board was a very small part) use, it worked excellently, and there have been four years of development since!

    Way to go!

    --
    SIGSEGV caught, terminating

    wait... not that kind of sig.
  22. Now we only need... by gremlins · · Score: 2, Insightful

    Now we only need some place that can print the circuts once we design them, mabey even make your own custom pci cards, or opensource card designs

    --
    just because your a schizophrenic doesn't mean people arn't really out to get you
  23. Re:FINALLY! - In my defense by Thunderstruck · · Score: 2

    Maybe next time, use Google and look for "Free PCB Design Software"...

    Next time? Did you read the part of my post about not doing this anymore? This was back in the mid 1990s. How useable were Protel, Orcad, Eagle, or PCB Express demos in 1995?

    --
    Trying to use sarcasm in text-based forums does not work.
  24. Do they have by corngrower · · Score: 1

    Anything that's comparable to Verilog and VirSim in their toolbox? What are peoples opions on icarus?

  25. Re:FINALLY! - In my defense by MoralHazard · · Score: 1

    More the the point, Herman, where was Google in 1995? Are you even old enough to remember those days?

    It may shock and amaze you to learn that there was a time BEFORE the WWW, and that up until about 1995-6, nobody except the geeks and some researchers gave a rats' ass. Hell, you probably weren't even aware of its existence unless you worked with it or were a Uni student.

    Kids today. Think fucking Google can solve all their problems, anyway.

  26. Cadence Open Access Database vs. ASCII files by Invisible+Now · · Score: 1
    I was present (as a consultant) when the 500lb gorilla of the EDA jungle decided to try an "open" version of its sophisticated mixed signal, zillion component, object oriented, full design flow, database. I saw it mentioned tangentially in one post above.

    Does the Cadence license through Open EDA org work for the community? Will gEDA's ASCII based text files allow us to pick and choose from workflow tools, handle complex, high device count designs, and hand off finished designs to current fabs?

    Am I too ambitious to hope that smart, open source folks can take Cadence up on its offer, and build robust (if slightly bell-and-whistle less) EDA tools on top of this (I can't believe they let it go open) db? After all the db is the essential component of any sophisticated EDA design flow system...

    Obviously, the $250k + licenses for commerical tools keep a lot of folks out of the fabless EDA world, now...

    --

    "Knowing everything doesn't help..."

  27. Check out alliance cad by scheme · · Score: 1

    Look at alliance cad for vhdl compiler, simulator and related tools. It's gpl and there are binaries available for a variety of systems.

    --
    "When you sit with a nice girl for two hours, it seems like two minutes. When you sit on a hot stove for two minutes, it
  28. good public domain EDA tools for chip design: mmi by Splork · · Score: 1

    http://www.micromagic.com/

    tools included: chip design (schematic capture), datapath compiler, full custom IC layout, and integrated layout system.

  29. Re:the "gimp sux" argument applied to gEDA by civilizedINTENSITY · · Score: 1

    God help us if nuclear reactors are controlled with WinXP! Brings a whole new meaning to "blue screen of death"!

  30. Re:Hey asshole, by bit01 · · Score: 1

    I'd add that some software, free and commercial, is not only useless, it is worse than useless in that it soaks up the time of the user without warning for no return.

    In those circumstances I have no problem complaining about the fact that it is time stealing.

    If it is well documented that it is in an unusable state before download/purchase then no problem.

    ---

    It's wrong that an intellectual property creator should not be rewarded for their work.
    It's equally wrong that an IP creator should be rewarded too many times for the one piece of work, for exactly the same reasons.
    Reform IP law and stop the M$/RIAA abuse.

  31. Tried the FreeBSD port but removed it soon after by LM741N · · Score: 1

    Unless this package has evolved hugely in the last year, I would not be interested. I originally compiled the FreeBSD port and was thoroughly unimpressed, so I deleted it. I suppose I am spoiled after having access for so long to Agilent and PSpice simulators.

    Now, there are just too many low cost commercial packages now, and cheap enough that I am willing to shell out the cash. For example, Beige Bag software (www.beigebag.com) has an excellent integrated schematic capture and Spice sim engine for a couple hundred bucks. Also, 5Spice has an excellent schematic capture and Spice tool- it is designed for real power Spice users and costs less than $200. (www.5spice.com)

    I suppose these GPL'd projects are useful in one huge way: they force the EDA makers to lower prices.

    Sincerely, Rob.

  32. Re:Hey asshole, by dbacher · · Score: 1

    Sir,

    Thank you for posting to "$project$-dev." While we appreciate that clueless trolls like yourself have nothing better to do than to agrivate our $project$'s users in the "$project$-dev" list, we would appreciate it if you would please buy a clue.

    We feel sorry for the poor users of $project$ because they cannot afford to type the entire word "for," nor can they afford lower case letters to use in their subject line, and as package maintainers, we would very much like to help this segment of our community.

    We note that while you say that because $project$ uses $license$, which is an OSI approved open source license, that you feel users should "fix it themselves," however we're compelled to note that we have yet to receive even one fix from any person posting to this list, while it's clear there are a good number of people with legitimate complaints.

    And so we, the core developers of "$project$" ask that you please quit suggesting that users should not complain about $license$ software until you are willing to make a useful contribution yourself.

    In the mean time, please feel free to use Paypal to donate to the user who cannot afford a complete set of keys.

    Dave Bacher
    $project-position$
    $project$ $version$

    --
    If your code is acting bloated, and is running rather slow, it's likely and predicted that some loops you will unroll.
  33. Another plug for Eagle by FuzzyDaddy · · Score: 1
    I don't know when you last used eagle, but I've been using it for six months now and I've never had it crash. I've been very happy with it (and I tried the Protel demo), although circuit simulation is not important for what I'm doing.

    One thing I like about eagle is that everything can be exported into a text based script - libraries, schematics, etc. This openness in the file format is one of the reasons I appreciate the software - if the source isn't open, at least the file formats are!

    --
    It's not wasting time, I'm educating myself.
  34. Re:VHDL + FPGA - VHDL is great by Wilk4 · · Score: 1
    nah, VHDL isn't not that tough... I love it. (I'm using it for FPGAs with Synplicity Pro, Modelsim and Altera or Xilinx software so I do have an advantage of having great tools available.)

    and our company uses it far more than we use verilog...

    btw, if you are editing vhdl, check out the Emacs mode for VHDL.
    It's far more powerful than vhdl editing aids in any other editors I've used.
    (And, yes, you *can* use GNU emacs in Windows too)

  35. Re:VHDL + FPGA - VHDL is great by tehdaemon · · Score: 1

    Hmmm... Maby I should have said 'was used in the class' He taught verilog. I couldn't even recognise VHDL code as such. I have only his (and others, mostly on /.) word that it is hard.

    --
    Laws are horrible moral guides, moral guides make even worse laws.