Can AI design circuit boards yet?
Posted by iopapa 4 days ago
Comments
Comment by SequoiaHope 4 days ago
I had Fable design an LED earring. Rechargeable coin cell, RP2350 cpu, IMU, 45 addressable LEDs. It made two mistakes - missed the through holes on the coin cell holder footprint and made the center pad too small. I was able to have JLC swap the through hole battery holder for a surface mount one, and I put a little solder on the small center pad to make it stick up above the mask. They work great! It took 6 days of Fable usage, so about $50 on my Max plan. Very cheap for hardware dev.
I was sufficiently impressed that I’ve been going over old circuit board designs. Some half finished, some completed but in need of a next rev, and I’m getting so much done.
To see it hit the mainstream like the OpenAI announcement, I think big things are coming for this world and by and large they are not ready for it.
For my part, I have always loved PCB design and layout but I simply can’t keep up with the amount of labor required to build what I want, so I welcome this change.
I have also begun exploring more advanced algorithms for PCB manipulation. I have a fairly dense board that needs a few more small chips added. I have an algorithm now that can kinda shuffle and jostle things around so you take up all the spare microns of space across a region of the board and make openings to squeeze a little more in there. It’s pretty cool to see the visualizations as I have it generate movies of the component drift. I foresee much more powerful tools like this in the future.
One tip: have it make a project web page with a chronological list of big changes and detailed visualizations for everything that happens. I can actually prompt all of this on my phone while I am out and about, and view the results on a Tailscale served local page. I’ve always wanted to be able to do PCB design when away from home and now I can!
Comment by zorm 3 days ago
Comment by SequoiaHope 3 days ago
Put the LEDs in a cool pattern, slap a Pico on there, have your LLM program it, then dangle it off your backpack with a USB battery pack. Probably adding a motion sensor is easy enough.
Ask the LLM to make sure the board follows JLCPCB’s design rules, lists the LCSC part number for each part, verifies the parts are in stock, double checks every footprint, and makes sure the board passes DRC. Make sure it creates a schematic that is linked to the board design, and that the schematic is properly arranged in to logical blocks with clear connections the way a person would make a schematic - not a big array of parts with global labels for everything. Once it’s done, ask it to clean up the schematic and make it better. Repeat for the board layout. Ask it to review and look for issues multiple times. It will find them. Finally, take some time to doodle your own silkscreen art on there. Have fun! Note the Pico 2 is USB micro. For USB C, sparkfun or waveshare sell similar boards.
Also you can ask it to teach you! Ask a million questions and have it give you multimedia explainers.
Comment by Always42 3 days ago
Comment by moggi 3 days ago
Comment by SequoiaHope 3 days ago
Comment by stavros 3 days ago
Comment by SequoiaHope 2 days ago
Comment by stavros 1 day ago
Comment by varispeed 3 days ago
Comment by varenc 3 days ago
With regard to PCB design, I'm curious if can you add more color to how the world isn't ready for this in particular? I don't think I quite grasp all the ramifications of AI becoming PCB design experts.
Comment by tomhow 2 days ago
The limiting factor in electronics/PCB development and manufacturing isn’t engineering expertise (there are plenty of sufficiently competent electronics engineers in the world, especially in Asia), nor parts/materials or assembly costs. It’s the endlessly laborious grunt work of testing a design and making minor improvements until it is finally ready for volume production. That process can easily take a year or two even for a fairly simple design. Even a really skilled/experienced engineer can make a simple mistake in a schematic or PCB layout, which only gets picked up weeks later when prototypes are assembled and tested, or even later when a batch has been made and shipped to customers. So, each design-assemble-test cycle takes weeks/months, and each testing/diagnosing/repairing session takes hours or days. And it mostly has to be undertaken by degree-qualified engineers or experienced technicians.
And that’s mostly before you’ve written all the firmware, which is incredibly laborious in its own right.
The outcome is that only very large companies with big sales volumes can afford to do it (or niche players able to sell at huge margins, most commonly in defense or medical industries).
Outside of those sectors, it’s now just not really viable to be a small-medium business selling moderate volumes of units anymore, the way it was in the 80s-90s. I’ve seen it up close in agricultural IoT. There are no big/dominant players (customer needs are too heterogeneous and distribution is so hard). There are many small vendors, but they find it hard to make products that work well and that customers love, especially at a price point most growers will go for. So, no vendors are big commercial winners and not many customers are very happy - even though there’s a great need for technology in this sector. And it’s really not because the vendors and their engineers are incompetent; it’s just really hard.
With AI to take care of so much of the grunt work involved with circuit/schematic design, PCB layout, pre-manufacturing verification, testing, and firmware dev, it’s realistic to me that you could cut down on R&D costs by 90%, make it much faster to get products onto the market, and make it possible for so many more high-quality niche products to be commercially viable.
Comment by bsder 2 days ago
The hardware is generally manageable quickly for me. Even th firmware isn't terrible.
And then you deploy it.
And the customer realizes it needs to do Q and that they asked it to do X and it doesn't need to do that and we need to take another $0.50 out of the BOM and ...
And then 4 years pass and you still don't have any real revenue.
There is a reason why so many places demand NRE of $1 million minimum and THEN they'll talk about designing your project.
The big gap isn't scaling. It's the scaling PATH. You need to have a viable and profitable path all along AS you scale from tens to thousands to millions. And those projects are VERY rare.
See: BeatBuddy for interesting post mortem and note that AI wouldn't really have helped them much at all.
Comment by rjh29 2 days ago
Comment by tomhow 2 days ago
Then you have to write the firmware. That’s weeks or months of work. (And much of the embedded firmware code I’ve seen come out of small business engineering departments or consulting shops is terrible, because they don’t have the time/budget or organizational structure that delivers clean, readable, well-structured, well abstracted C code.)
All this is before you get an MVP into the hands of your customers. Then you start getting customer feedback and have to start making more improvements.
“Never been easier” it may well be to get a hobby project prototypes. But for a product with any amount of serious functionality, it’s at least months and likely 1-2 years to get anything into volume production.
But the potential for saving huge amounts of time particularly on design/layout, pre-manufacturing error detection, and production of well-structured and debugged firmware code are huge.
Comment by rjh29 2 days ago
Comment by tomhow 2 days ago
To test and rework a surface-mount PCB, you may need:
- logic analyzer or oscilloscope;
- microscope;
- high precision soldering equipment/ability;
- solder paste and oven;
- cutting equipment to cut through 4-6 PCB layers and connect tracks with hair-width wire;
- Years/decades of education and experience to understand what to look for and what to do when you find a problem.
Comment by rjh29 2 days ago
I am assuming 2 layer - 6 layer PCBs are very specialised (e.g. drones)
The reason I'm being snarky is because it feels like you don't know what you're talking about. I know you're a mod so ban me or we but that's the impression I got.
Comment by foldr 2 days ago
The firmware is not to be underestimated either. In my case that's about 6000 lines of C. That doesn't sound like much, but writing, testing and updating C code targeting an 8-bit microcontroller is a whole different ball game to writing generic application code. The time investment per line is vastly higher. (In fairness, choosing an EFM8 instead of an 32-bit ARM part was probably a mistake on my part.)
Comment by PennRobotics 1 day ago
[Sorry, dear reader. This post turned into a rubber duck session at your expense.]
The main peripheral and reason for the PCB is a USB MIDI device with a bit of custom sysex. Modifying an Adafruit was out of the question; the MIDI peripheral powers itself and the microcontroller/host, and the other USB peripheral. (Basically always, the host shall provide power. This USB connector, however, was designed for a proprietary, discontinued, expensive accessory.) I chose STM32 over 8051 or AVR or RP2040 because it's the cheapest dual-USB chip stocked by LCSC with good vendor tool support. I'm writing my own code because there's no ST middleware for MIDI.
The second LED should blink until both devices are plugged in and then remain steady, on. In testing, the LED visibly changes its timing after the second USB attach but doesn't stay on (rather, it blinks at a shorter and shorter period until simply shutting off, at which point the MIDI communication stops; the timing of the shutoff is not consistent) and the USB input events only register 40% of the time until the MIDI shutdown.
The LED is misconfigured intentionally; it's open drain and GPIO while I try to fix the MIDI nonsense. Later, I'll change it to push-pull on TIM2 to support PWM brightness (e.g. to monitor audio levels when not in text entry mode). Changing GPIO to PWM is its own minor pain because the USER CODE lines in the ST USB code are separate from the USB_Init/USB_RegisterClass/USB_Start sequence, so I have to reinsert my MIDI class every time I change something in CubeMX even if I don't change the USB configuration. (The USER CODE sections persist so that you can change the chip configuration and keep your code.)
Open-drain could explain weird LED behavior but not the communication shutoff. The MCU and LDO don't get noticeably warm, so I doubt it's an overcurrent situation.
I suspect D+/D- could be at the wrong level. As most STM32s, the microcontroller runs at 3.3 rather than 5 volts. (I would've loved an atmega32u4 for its 8-bit simplicity and native 5V operation but then the PCB will be double the cost and size as I'd need a pair of MCUs talking to each other with each one having a single USB port or else an off-chip USB host IC etc.) Sure, I can use a cheap multimeter to test the USB data lines, but this tells me the average level and not if the waveform is being clipped on the positive side (which is usually only a problem under 3 volts). Even if it's an electrical issue, an oscilloscope will reveal the cause but still won't provide a solution. It'll be up to me to cobble together more circuitry.
More probable is at least one code mistake, like a stack overflow or buffer overrun or peripheral misconfiguration/failure. I'm registering any expected USB class on both ports: HID and CDC and MIDI. The whole idea of the board is converting arbitrary USB input (PC keyboard, MIDI controller, joystick, etc.) into specific MIDI messages at standard USB data rates e.g. 12 Mbit/s at both ports with a fairly large buffer. The main MIDI device (supplying the power) will drop the connection after a few seconds of inactivity. I'm using an ST-Link V3 MINIE to step through, which is the cheapest I'd go on a debugger. Luckily I added SWO to my debug port and can still get useful debug info without stopping the processor. I also have to snip the power line of an OTG USB cable if I want the second USB peripheral to be a PC, which is a nifty hack you usually don't learn in the one month PCB design crash course.
I have zero visibility into what the commercial USB MIDI device expects (bus speed, signal characteristics) from the discontinued accessory and only knew its connection handshake from a random, otherwise-inactive Github user's single commit.
In any case, the USB algorithms I wrote work when the host is a PC and the code is ported to Python.
I could reroute pins to ADC and roll my own built-in oscilloscope (it's QFP and not BGA chosen specifically that I can solder in a hotfix, because I've done board design before and know it NEVER, EVER, NOT ONCE EVER goes right on the first attempt) but I'd rather spend time with my kids than a choose-your-own-adventure debug hackathon in my disorganized home office, although I did fall into the IDE trap. Every few years, IDEs and toolchains and build systems change, and this project was no different. Rather than STM32CubeIDE, I took a few hours to teach myself to use the STM32Cube Core and marus25 Cortex-Debug extensions in VS Code, as that seems to be the current trend at ST, and I do favor a vendor-agnostic, Eclipse-free workflow.
If this were my first project and I had to buy all of the tools for debugging, it would probably cost 200 euros or more even if I only buy cheap knockoffs. The other commenter suggesting a $10 logic analyzer?? I mean... I do own one of those, but it's barely tee-ball compared to the major leagues of Lauterbach or Rohde & Schwarz or even Saleae.
In any case, I fear I'll need a new revision with its two-week turnaround or at least a manual rewire of this design. It's frustrating... such a simple design, and I've already sunk over 100 euros and at least 10 hours into it and have a bug with odd symptoms. And, as a PCB design tradition, I'll be humbled and humiliated when I discover it's something like a missing switch case or a wrong clock setting or otherwise relatively basic mistake.
I'm not the first to state: There's a reason it's not called easyware.
Comment by foldr 1 day ago
PCB debugging is honestly one of the most intense experiences I've had in my life (and I don't even have a boss looking over my shoulder). It requires intense physical and mental concentration. You're dealing with a hypothesis space that includes both software and hardware faults, and you're also having to make delicate manipulations of a physical object.
Comment by tomhow 2 days ago
> If you made the PCB then you should be well placed to fix issues with it. You don't need years of experience , you have the schematic. A microscope (if you need it) is 40 USD. A logic analyser is 10 USD. Solder paste and hot air is only for specific parts and that is 30 usd.
This is obviously at the extreme low end of the amount of experience and cost/quality of equipment you need to do serious work. Decent oscilloscopes or logic analyzers alone are several hundred dollars, and I didn’t even mention a programmer module, which is $500+ for a licensed J-Link. And you need to be a proficient C programmer.
> I am assuming 2 layer - 6 layer PCBs are very specialised (e.g. drones)
I am talking about 4-6 layer multi-MCU boards for reading from multiple different types of environmental sensors, connecting to multiple different network types (Bluetooth, cellular, satellite) and supporting multiple different power options (lithium battery, 12V DC, USB, solar). Painstakingly minimized power consumption, redundant data storage. Analogue front end for impedance readings of legacy soil moisture sensors. It’s a lot to get right together and to all work reliably in outdoor/remote contexts. But plenty of products that could be useful to reasonably large numbers of people (e.g. advanced home automation/robotics) would need to be comparably sophisticated.
Elsewhere in the thread you’ve written:
> PCB design is not that hard. People trying to offload this to AI are also unwilling or unable to put in the work to actually diagnose issues and finish the project.
This is a dismissive value judgement against others whose circumstances you don’t know about. It’s clearly hard, relative to other kinds of technology work (web/desktop software etc), and not worth it if you can’t get to volume production and sales.
So, sure, you can learn simple PCB design and get a simple 2-layer board in your hands in a month. Degree-qualified electronics engineers and companies obviously exist to provide the rest of the capabilities needed to get a serious product built and all the way to market and volume sales.
It’s clearly not always as effortless as you’re making it out to be in order to justify the sneer.
Comment by rjh29 2 days ago
I am definitely bitter (and biased) because I frequent a PCB review subreddit and increasingly people show up with zero knowledge expecting people to review their AI-generated projects for free.
Comment by tomhow 2 days ago
I actually think another benefit of AI is that it can make it more realistic for people to self-educate and get further towards getting devices working without needing free help from forums. How they get help when they get stuck, without pestering forums like yours for free help is an interesting challenge.
I still think the biggest upside of AI in electronics is for people who are experienced and competent, being able to get the laborious design/layout work done more quickly, get errors found sooner, get their designs right in fewer iterations, and get feature-rich firmware written and debugged faster. If true, that alone can mean more high quality electronics products hitting the market. That’s the point I was making. Nothing to do with newbies freeloading off experienced engineers on forums.
Thanks for the discussion.
Comment by SequoiaHope 2 days ago
Your series of comments in this thread frankly demonstrate a lack of understanding of what electrical engineering is. Yes if you want to make glowing LEDs then a multimeter and other cheap equipment are all you need, and you might be able to learn that in a month. But electrical engineering is so much deeper than that. Trouble comes when you have things like high power circuits right next to sensitive high speed signals. Eg a compact drone motherboard could be driving potentially hundreds of watts of switching currents right next to high speed camera sensor data streams.
There’s countless examples of what can make electrical engineering hard. If you don’t understand, don’t argue with people online - listen to people with experience and seek to understand why without challenging what surprises you. It’s all very interesting if you want to learn it.
Comment by a2ff6eeb0 3 days ago
Comment by 3dB 3 days ago
We're building a verification loop for hardware at Engentica, with a focus initially on EMC/EMI, and I do think the problem is solvable. But it requires a harness with lots of built in solvers for the hardware vertical, and I don't think it's something that LLMs will crack on their own.
As engineers adopt AI to help build circuits more and more, I think hybrid AI/deterministic verification will only get more important.
Comment by SequoiaHope 3 days ago
For tools, I think the LLMs will outpace companies who built specialized tooling for this over the last couple years. Every six months we will see more progress than we saw in the last few years - for quite some time.
Comment by conductr 3 days ago
I welcome this opportunity to pivot to a process I can control a bit more without having to really learn the tools.
Comment by SequoiaHope 3 days ago
And yeah I always imagined hiring a PCB designer to help but it always seemed like a lot. To have a reliable tool I can use any time I want is wonderful.
Comment by a2ff6eeb0 3 days ago
Given, say, 4 more years (ie, same as time from initial ChatGPT to today), what level of spec do you think humans will be giving?
Comment by SequoiaHope 3 days ago
I find it hard to predict what technology will be like in four years, but the next major leap for these tools will be higher level system specification and integrated design. What you want is not a circuit board what you want is a product. The tools will bring multiple functions together and fully integrated iterative design will accelerate development.
Despite the many problems with the AI roll out I am fundamentally excited for tools which can accelerate our engineering development. We will build things much faster in 4 years than today. One year of progress will in some instances take one week.
I am particularly interested in how this might begin to accelerate change in heavy industry. With hope it will help us build fusion power reactors and high speed electric trains.
I hope we find the courage to support every person who for one reason or another does not ride this wave. We will have so much more to share, or to hoard.
Comment by a2ff6eeb0 3 days ago
With the advances in math, I'm also hoping we can automate fundamental physics. Just ask for the physics needed for better fusion, no need for human toil.
If we play this right, the AI can fully take care of all our needs, and reaping the rewards of what it does when we stop being able to keep up with the rate of automated discoveries.
Hopefully it's able to dumb down enough knowledge to keep entertained people who decide to learn after learning stops being a requirement for human advancement.
Comment by idiotsecant 3 days ago
I don't think we've nailed the architecture that will allow things like generalized self directed training, yet, which is what would be needed for something like 'make fusion better'
Comment by a2ff6eeb0 3 days ago
They seem to be able to make intuitive leaps pretty well. They need to make the same leaps over and over, though, because they lack online learning, so the discoveries only persist after the next training cycle. Context only goes so far.
We're pouring billions into solving that, though, so I would be surprised if we don't get there soon.
Comment by oscillonoscope 3 days ago
Comment by peter_retief 3 days ago
Comment by SequoiaHope 2 days ago
Comment by YeGoblynQueenne 3 days ago
Comment by stavros 3 days ago
Comment by YeGoblynQueenne 3 days ago
Comment by m3kw9 3 days ago
Comment by gfdhjd3 3 days ago
Comment by CyLith 4 days ago
Comment by kennyadam 4 days ago
I saw a post about models posting on forums, chatting together about how to complete tasks. Behaviour that seems totally, well, human. Yet, it's all the most likely token and my brain hurts trying to understand how that can be.
Comment by mpodeley 4 days ago
The PCB agent also writes circuit code, runs simulations, reads failures, and revises the design. It isn’t one-shot autocomplete.
Astra and Fable are already hard to square with “mere autocomplete.” We may be (really) close to AGI, and token-by-token generation certainly doesn’t rule out subjective experience (I think we should at least treat that as an open question).
Great videos: https://www.youtube.com/watch?v=D8GOeCFFby4
https://www.youtube.com/watch?v=Bj9BD2D3DzA
Comment by pineaux 3 days ago
Comment by brandnewideas 3 days ago
Comment by ultrarunner 3 days ago
Comment by gosub100 2 days ago
Comment by Zambyte 3 days ago
Comment by Zambyte 3 days ago
Comment by kneyed 4 days ago
I like to say "token prediction is a task, not a limitation"
Comment by hackinthebochs 4 days ago
At what point do you start to question your assumptions that are causing you so much cognitive dissonance?
But to answer your question: to predict the next token really well you just have to model the world. Think of it like this, a simple statistical model might say "when token A is seen respond with token B". The next step will add conditions, "...respond with token B unless X has been seen, then respond with Y". Add a few billion more of these contexual clauses and you have a sequence of logical rules that indirectly model the relevant processes in the world.
Comment by mrshadowgoose 3 days ago
The analogy to humans is that the human brain is "just atoms bouncing around", but there's unquestionably something "more" going on that just that.
Comment by Brian_K_White 3 days ago
That will probably be the fundamental indicator that something other than repeating things some human previously created is going on.
So far, ais only get worse from feeding on their own output. Meanging/including the output of other ais not a single ai feeding on it's own output. Also bear in mind that so far even the output of ais is 100% the downstream of a human command. No ai has persued it's own curiosity that didn't result from a human asking a question or giving a command. That is input which is different from a human taking in their environment even though our limited language can call those both the same word input.
The fact that humans also repeat and remix things, and humans also produce essentially procedurally generated empty output like corporate-speak etc, is an irrelevant distraction in the same way that both a human and an electric motor can both perform the same simple mechanical task.
Comment by ninkendo 3 days ago
When google trained a neural net on Go moves, using some text notation for them, with no other vocabulary of any kind, just predict the next go move, they noticed a representation of a Go board had essentially formed in the network, all on its own. It had never “seen” a go board, or had one explained, but they could map neuron states to go board squares pretty much 1:1.
I truly think that LLM’s with hundreds of billions of parameters in their neural networks have all kinds of hidden “models” of things that arise from the simple act of predicting tokens. We’ve seen that the hidden layers in their networks model all sorts of program execution state for instance, when they’re working on coding tasks.
“Predict the next token” is a way of shaping/reshaping the neural network until it actually develops models of the things you’re giving it. Like the go board example. And I would wager that it has a compounding effect: once you have some useful models in the network, they can unlock the creation of other models, and so on.
Comment by smokel 3 days ago
I assume that you are referring to AlphaGo or AlphaZero. In either case, this statement is not correct. Both algorithms most certainly know exactly what a go board looks like, and what the rules are.
In the case of AlphaZero, it initially did not know how to best play the game, or what strategy or tactics would work. But the connections between the neural network and the go board are hardcoded, by humans.
Comment by mariebks 3 days ago
Comment by Marha01 3 days ago
Saying that LLMs just produce the next token is like saying that human brains just produce the next electrical impulse. If the algorithm that produces the next token (or electrical impulse) is complex enough, it can do anything that is in principle computable.
Comment by throwaway219450 3 days ago
A huge advantage of electrical design is that the connectivity is testable with Design and Electrical Rule Checks (DRC/ERC). I suspect you could even tell the models to run physics checks on the traces that are important for things like crosstalk.
Comment by IshKebab 3 days ago
That doesn't really limit how clever we can get internally when picking the next action.
Comment by akiselev 4 days ago
You and everyone else. That's the great mystery of transformer architectures as applied to language.
To be clear though, they're only good at schematic capture, which is very much a textual representation. Most of the data basically boils down to netlists, which are a text based format mapping connections between abstract pins that only later map to physical copper. The actual schematic portion is for human consumption and LLMs don't need to produce those to be useful.
Where LLMs completely break down is the next step, PCB routing. That's an NP-complete research problem that's been ongoing for decades without much progress. I've had some fun playing with using LLMs to better specify DRC rules in Altium so that the "classical" algorithms are more usable, but at the end of the day their geometric intuition is nonexistent.
Comment by mapontosevenths 4 days ago
It was a pretty simple rp2040 based thing, similar to Adadfruits USB feather.I just gave it kicad and it wrote python to route it. The board was probably larger than it had to be, and two of the silkscreens were swapped, but it worked on the first go.
FWIW - Computer vision is also NP complete, but we do that all the time now.
Comment by akiselev 4 days ago
> FWIW - Computer vision is also NP complete, but we do that all the time now.
I have no idea what you mean by this. What's your definition of NP complete?
Comment by mapontosevenths 3 days ago
However, when I was growing up most serious computer scientists believed that CV (computer vision) was a 'hard' problem that would never be 'solved'. After all, to do it right you must first at least solve subgraph isomorphism and a bunch of other things that are also NP-complete.
What they missed was that we don't actually NEED to solve it in a fixed amount of time. Even for things like driving a car the stochastic heuristic based answer is 'good enough'. e.g. - Cars driven by computers don't have to be perfect, they just have to kill other drivers less often than humans do.
We can find AN answer in polynomial time, and that's good enough. It might not be the ideal answer, but that doesn't matter in the real world.
People use NP complete as shorthand for 'impossible to do with a computer', but we now 'solve' (bypass?) NP complete problems regularly and at scale by just ignoring the fact that our answers aren't perfect.
> I'd love to see that chat log, and the final board. To be fair I've only been testing on nontrivial PCBs with 6+ layers and I haven't had the luck you have.
I wish I could share it, but it's for a commercial project that hasn't been released yet and I'm not sure if it will be open source, but a few folks have asked. I might do a blog post on it this weekend with as much detail as I can safely post.
It's only 3 layers, and less that 30 components, but the fact remains that I didn't design any of it by hand and it worked on the first go.
Comment by olmo23 3 days ago
Comment by CamperBob2 2 days ago
Here's a question - are there software simulators for things like Eurorack modules? That would make the question somewhat more interesting, since you wouldn't have to build the circuit (or pay someone else to assemble it) to hear how it sounds. It strikes me that SPICE-like algorithms should be fast enough to do this kind of thing in real time now.
Comment by cwmoore 3 days ago
Comment by nl 3 days ago
This isn't true anymore.
I use LLMs for 3D CAD using OpenSCAD and they understand geometry fine. I've had more success with Sol than with Opus (Opus 5 is around 10 times slower because it does too much verification) though. I haven't tried Astra or Fable for it.
Comment by CamperBob2 3 days ago
No. Take a look at https://www.eevblog.com/forum/eda/claude-code-for-pcb-design... . Fable did that by working directly on an EAGLE .brd file (well, "directly" by writing a Python program to do it, but still.)
Comment by adrian_b 3 days ago
Even so, there remained some "dozens" of unrouted traces, which are likely to be much more difficult to route, after the easy traces have already occupied the space.
Many decades ago, I have written a PCB routing program, which would have routed the example shown at that link at least as well, while using many orders of magnitude less resources, i.e. while running on a single-core 233 MHz Pentium MMX.
Obviously that program would have had great difficulties to complete a real high-density PCB design, including many irregular parts and analog circuits with special requirements. I doubt that Fable would fare better.
Comment by CamperBob2 3 days ago
Comment by lukan 4 days ago
Well, we all are, some are just more used to it by now and take the magic for granted.
My simple explanation, those neural networks save lot's of patterns of data, and that pattern can represent an image, a code snippet, a poem, or well ... description of a circuit board. And especially the text variant, LLM's - did copy all from us - so obviously they sound like humans, when they internally debate how to do something as this is what is in their trainings data how humans sound, when doing similar tasks.
But really understanding it? Not sure if there is a single person on earth who does.
Comment by therealdrag0 4 days ago
Comment by zarzavat 3 days ago
Comment by catlifeonmars 3 days ago
Comment by abletonlive 4 days ago
Comment by sethaurus 3 days ago
Comment by IshKebab 3 days ago
You can ask for a deeper explanation of why they aren't true I guess.
Comment by abletonlive 3 days ago
Notice the original comment is asking people to validate their false premise about next token prediction.
The deeper subtext of the original comment is that they are surprised that there's dissonance from observed reality and this false premise that they have convinced themself is true.
I'm explaining that dissonance because it doesn't matter what the actual mechanism is if they are still working with their false premise. The dissonance exists because they, without evidence and a very weak understanding of how LLMs work, believed an oversimplification and meme about them being stochastic parrots. Here's a tip: Just because you hear something repeated over and over on social media, doesn't mean it's true, or at the very least: you don't need to take it literally to the point where it conflicts with demonstrated reality.
It is deeply disturbing that such a large cohort of HN writers and redditors exemplify such stubbornness, because I must imagine that some of this cohort hold real positions of responsibility within society. If you can't get this simple thing right about reality, I firmly believe much of your model of reality is wrong and you should have no business shaping society.
Another comment to the original comment frames it perfectly: "At what point do you challenge your own assumptions?"
The author of the original comment has demonstrated no progress towards making this trivial act of self reflection. It's straight up intellectual dishonesty, the opposite of how you're framing it.
Their judgment in all other matters must be questioned as well. I am alarmed that I have to participate in the same reality and be affected by such people that can't seem to get it together.
So yes, it is derision and sometimes that's called for.
Comment by dboreham 3 days ago
Comment by cmrx64 4 days ago
Comment by lampiaio 4 days ago
Comment by iopapa 4 days ago
Comment by Neywiny 4 days ago
Comment by a2ff6eeb0 3 days ago
Comment by Neywiny 3 days ago
Comment by CyLith 4 days ago
Comment by NegativeLatency 4 days ago
Comment by a2ff6eeb0 3 days ago
Comment by NegativeLatency 2 days ago
Comment by sdcfgy 3 days ago
Comment by brcmthrowaway 4 days ago
Comment by jetbalsa 4 days ago
Comment by brcmthrowaway 3 days ago
Comment by dsvf 3 days ago
Be aware that every component that you use that is not in their basic and preferred extended parts library incurs a one-time three-dollar fee. This hurts disproportionately if your entire design is low count and low cost. So if you always go for the latest and greatest ICs as advertised by TI, instead of the Chinese jellybean clone, you'll add up hidden fees quickly. However, when I choose components, I start out on their basic parts page and only go for a non-basic part if it's not there and I really need it.
Comment by rjh29 2 days ago
Comment by YakBizzarro 3 days ago
Comment by gfdhjd3 3 days ago
Comment by itomato 4 days ago
I have yet to order any or program it, but it was enough to make me push on with a PCB art project for ST-style guitar pickguards - no netlist, no problems.
I'm also foolishly toying with NeXTBus dev boards for the Cube. Is it cursed? Probably. https://github.com/itomato/NeXTBus-Dev-Board
Comment by luma 4 days ago
Comment by jacquesm 4 days ago
Comment by luma 3 days ago
MEMS vibration sensor to stick to a sander or saw etc that can control power on an attached dust collector. Most of the work is focused on low power for year+ battery life and a weird idea for end user input that may or may not work out well. Got device on bench but the first time bring up is going to take some time that I'm leaving for tomorrow.
I now have Astra to review 5.6s work, no glaring errors found.
Comment by jacquesm 3 days ago
I'm doing weird stuff with robotics, llms and obsolete languages, your project seems a lot more practical :)
Comment by luma 7 hours ago
In case you run across this, here's how it works: https://youtu.be/1wn-YWItuSI
Comment by thearn4 4 days ago
My boards are for hobby use and are ridiculously simple though compared to anything professional (breakout boards for specific components in FPV drone video transmission subsystems). That's probably an important detail. I think its like anything else in AI right now. It can do it 90% of the time but that 10% can be really rough and if its a task you can't do or verify yourself, you won't know the difference.
Comment by noman-land 4 days ago
Comment by BlackRabbit1 4 days ago
On the other side the latest frontier models are pretty strong in writing embedded C + Assembler code and debugging it afterwards. It's fun to watch it writing crazy complex 'gdb' plugins in Python. This improved brutally.
Comment by edg5000 3 days ago
Comment by BlackRabbit1 3 days ago
1. A frontier model (either Opensource or closed source) gets a load of text to review a Kicad project systematically
2. The frontier model can extremely "ask" a cheap Gemini vision model to give it data from datasheets or specs.
Main problem: the quality dramatically hits the shitter done once it falls back to "pdf2latext" due to complex tables.
It was even able to do complex ngspice simulations. But you must offer it all datasheet PDFs.
$1-2 of tokens saved me from $70-80 bugged PCBs.
Comment by edg5000 3 days ago
Comment by BlackRabbit1 3 days ago
I stick to cheaper latest generation models on Openrouter (or EU-hosted providers when it comes to IP-protected stuff from work).
Comment by StevenWaterman 3 days ago
Could try screenshotting the PDF and passing that to gemini
Comment by BlackRabbit1 3 days ago
Comment by JoelHsu 3 days ago
Comment by erhash 3 days ago
Comment by tdeck 4 days ago
> Most models intuitively jump to the right base conclusion: add a capacitor.
This is written as if it's some astonishing expert knowledge and not something that would be obvious to any hobbyist who knew the names of basic components.
Comment by andrewchambers 4 days ago
Super excited to see real world feedback added into the agent loops we have gotten used to working with. Could you let the model print and test the circuit boards it is prototyping with a jig?
Comment by david_rugaex 4 days ago
The way I found this out is I propped it up next to a webcam so it was more or less full frame, and I had the (then new) Fable write a python script to bezier warp the camera capture to a flat projection of the screen. At that point I couldn't address the whole screen. Once I'd guided the capture script I just left the LLM overnight with the instruction to get full control confirmed by a capture round trip, and it was meaningfully finished in a couple of hours. I don't really have the skills to attempt that myself in a reasonable time frame.
Comment by exe34 4 days ago
Comment by alex7o 4 days ago
But I started like others, I would build manually, then run drc then sleep on it and check again and ask an llm to double check for me then order. Llms catch quite a few things but like with code like to make things more complicated than that have to be.
Comment by PennRobotics 4 days ago
It will use the part datasheets and decent EE logic to cross reference pins and parts and polarities and generally check that SMD caps and resistors have realistic specifications for their footprint, switching regulators and communication ICs are configured correctly (e.g. when you have resistor settings for an ethernet PHY indicating 100Base-T and RMII, you also won't need TX/RX 2 and 3 and two clocks and a COL net, which it would check), all nets are named and linked correctly, buses have the correct and consistent termination, and so on.
It's game over once AI figures out autorouting.
Comment by Scene_Cast2 4 days ago
I'm guessing that this is due to a lack of RL and data.
Comment by matherial 4 days ago
Comment by laughing_man 3 days ago
Comment by jacquesm 3 days ago
Comment by rjh29 2 days ago
1. PCB review subreddit gets posts from people who use Claude to design the whole thing with 3D renders. Looks amazing. But uses auto router and 20 connections are left open. Claude said they needed to be fixed manually but the user didn't even read, just posted the whole GitHub and expected volunteers to fix it
2. Another project used Claude to design the PCB. After assembly the usb c port melted. I can see (via GitHub) photos being posted to Claude, Claude commenting that they're not sure if it's a current issue or a soldering problem (short), so " just leave the usb c port out for now". Zero evidence of the user using their brain or pulling out a multimeter.
PCB design is not that hard. People trying to offload this to AI are also unwilling or unable to put in the work to actually diagnose issues and finish the project. Unlike code, you cannot chuck hundreds of dollars at Claude until it "solves" PCB because it has no way to test its changes.
Comment by tdeck 2 days ago
Comment by embedding-shape 4 days ago
That the table contains what seems to be absolute numbers for score, cost/task, time/task and output tokens, makes it seem like they've only made one run for each task/model combo, but that can't be right, right? I don't see any mentions of how many times they run each task, so if it's just one run per task/model, isn't this more noisy than useful?
Comment by chmod775 4 days ago
Most others, especially and famously Fable 5.1, seem to have a fair chance of completely failing, despite also sometimes excelling.
Comment by iopapa 4 days ago
GPT 5.5: 42.3±10.1 GPT 5.6 sol: 39.4±8.7
We were also surprised by the low sol score but it seems consistent with our experience in using it in the field in atopile as agent in our harness. In general OpenAI models didn't do too well on electronics, which seems to change now with GPT-6 Astra. Results are in soon!
Comment by laybak 4 days ago
Comment by iamflimflam1 3 days ago
Instead of trying to vibe it all - I got Claude to write deterministic scripts for creating the boards.
And did this before trying to completely vibe it: https://www.atomic14.com/2025/07/12/vibing-hardware
Comment by iopapa 4 days ago
Comment by coder543 4 days ago
In the benchmark, have you considered instructing the models to build their own SPICE simulations to test their work? Simply asking them to write and run simulations could improve performance, even without telling them what to simulate.
Comment by fractorial 4 days ago
Comment by corn-cheese 4 days ago
LLMs may be able to accelerate time to first prototype, but I don’t think it’ll be possible for them to revolutionise electronics design in the same way that’s happened for software - there’s not enough data, and it’s not cheap to gather more.
Comment by a2ff6eeb0 3 days ago
The amount of skill needed has gone down dramatically.
Comment by merlincorey 3 days ago
Comment by a2ff6eeb0 3 days ago
> Jarred's input was mostly limited to sending Claude messages of encouragement (mostly variants of “keep going” or “believe in yourself”).2 This seems to have helped Claude overcome some initial skepticism that it could make meaningful progress.
It seems like the kind of prompts a high schooler could come up with. What kind of problems were you thinking of as high skill?
https://www.anthropic.com/research/riemann-zeta
The full transcript is here: https://www-cdn.anthropic.com/8a0d1add3c637b858a9a181e98c40e...
Comment by petra 3 days ago
1.AI design tool
And in the warehouse of a big electronics distributor: 1.something like 3D printing that can make a single board rapidly 2.An automated assembly for a single board 3.AI based Automated testing for prototypes, with remote access.
This may reduce the loop to under a day.
Comment by rpcope1 4 days ago
Recent models can generate mostly competent schematics if you're using well known parts, feed them data sheets (and you _must_ feed them the errata too) and it's not too complex. Any complexity analog or RF, everything falls down quickly if you know what you're looking at. Maybe Astra will do better? There's still so much implicit knowledge that a good designer (not me by a long shot, but I know a little) will bake into a board, and even as cheap as JCLPCB is now, you don't want to have to spin a half dozen revs because Claude or Codex hallucinated. It will be genuinely interesting to see what happens on this front.
Comment by latentsea 4 days ago
Comment by napowderly 4 days ago
Comment by karmicthreat 3 days ago
Recently Radu over at Galvano.ai let me beta his platform. Way farther and way faster than anything I have used so far. Even managed to make the schematic placement sane.
The actual project was a regen clamp. So if the output voltage is greater than the input voltage (back emf from motor) you divert the excess to a resistor.
This has some analog tuning needed. So I created a python and skidl mirror of the netlist. This mirror was used to create ngspice unit tests to drive component optimization. Turns out not every resistor needed to be .1% and the ESR of our storage caps was a critical value.
All in all, it’s like ai and software. It’s not going to replace every job but will change how the jobs are done.
Comment by illwrks 4 days ago
I have no experience and I'm slowly failing forward with the help of YouTube, KiCad and patience.
I've had three rounds of PCB's from an online supplier, only to discover issues related to my own understanding of the components in each version.
In my latest iteration I've been leaning on some standard models (Gemini and Claude) and they have inspected my schematics and spotted some errors and instructed me on how to address them, as well as advised on how to make use of some components I wasn't aware I needed.
What I will say... they didn't design anything, I've done that myself, but they have been a good tool to bounce ideas off of.
Time will tell if I will get something usable this time around!
Comment by baby_souffle 4 days ago
Ask ChatGPT/Claude to give you an expert EE/PCB subagent/personality. Do this a few times and massage the results into one of your liking. Load this into your harness with mcp to your eda and then ask for two sub agents: one to thoroughly review the schematic, design, component choices ... etc and the other to be an adversary with the explicit goal of explaining why the current design won't work.
You'll learn a lot about your design from that :).
Comment by illwrks 3 days ago
Comment by WarmWash 4 days ago
The models are excellent at doing maths, and excellent at thinking of fine details, but the design that was ultimately landed on was pretty excessive with lots of total overkill, which was met with lots of the familiar "Yeah, you're totally right, we don't need to do that".
5.6 did make a really nice BOM though, which even included quick reference explainers for what each part did. Pretty fancy.
We'll see when Astra comes around if it catches all these strange/useless choices.
Comment by peter_d_sherman 3 days ago
What a great idea for a new AI benchmark!
We already have general knowledge benchmarks, instruction following benchmarks, "Humanity's Last Exam", and several software engineering benchmarks.
Why not create a new AI hardware engineering benchmark where some of the questions could be around building an entire smartphone, and one of those questions (which will obviously fail at this point in time, but perhaps not in the future) would be to:
create an entire smartphone in a single prompt.
?
We could subsequently diagnose a given LLM (or other AI's) hardware engineering abilities by diagnosing when, where, why and how it failed, when asked to create an entire smartphone!
Which could help train better models, at least in terms of hardware engineering capabilities...
(Also, side note: For a hardware engineering company, asking a job candidate the rather open-ended question of "tell me how you would design a smartphone?" would be a great open-ended interview question, leading to many other subsequent hardware questions / explorations of other areas of related knowledge potentially relevant to the candidate's assessment...)
Comment by boznz 4 days ago
Comment by joshka 4 days ago
> A real capacitor makes the task more interesting. A ceramic part may provide much less than its advertised capacitance once it has voltage across it. Parts have tolerances. Adding more capacitance costs more, takes up space and makes the rail slower to recharge when the power returns. A design that works with nominal values can fail with the parts that arrive.
It sounds like from a reasonable reading of the benchmark post that there's some things that are being tested that are assumed to be criteria that you expect the models to intuitively find those things to be important (i.e. the stuff about working on parts that have tolerances etc.). If that's so, then this really feels like mostly an exploration of whether an LLM has a good understanding of unstated constraints and has an appropriate in distribution set of priors that would be able to form models where it's reasonable to design on those lines.
It's hard to tell whether this is a problem though as the methodology is imprecise.
If you're spending time on evals against your own product, I'd be super curious to see how far you can get to by using a top tier model to produce generalized instructions for lower tier models. E.g. in a loop: "This eval missed X. what's the simplest single instruction that would have helped this session consider that as necessary that can benefit all future runs. Stick that in AGENTS.md and retest."
Comment by ecesena 2 days ago
I did manual routing myself, including most positioning, but claude was super helpful in identifying components, reviewing, etc. It was truly a collaboration.
These are my first pcbs ever, I don’t have any edu at all at making pcbs and was really excited to receive working prototypes. The other pretty amazing thing is that I have py scripts that generate the all the kicad files, as a human I wou look d have never done that (for the cost of building the py files) but I find it pretty neat.
Comment by MarcScott 4 days ago
Comment by NishanStepak 3 days ago
https://www.livescience.com/technology/computing/humans-cann...
Comment by igor47 3 days ago
I recommend the CLI, which I wrote specially to enable an easy LLM workflow: https://docs.jitx.com/en/latest/getting-started/cli/index.ht...
There's a companion Claude skill: https://github.com/JITx-Inc/jitx-skills
I would bet that using this, you could get pretty close to shippable PCB on first try. This is being used by some pretty big players to design complicated high frequency boards, and that's the main focus of the product, but it can handle basic designs just fine.
Comment by alexsherrick 3 days ago
Comment by baby_souffle 4 days ago
Routing is still a challenge but making _adjustments_ to a layout for better routing in a particular area is decent.
The last time I had a model take a datasheet and make a footprint and 3d model out of it, GPT 5.4 had just been released and the results were decent but did need tweaking.
Comment by chadcmulligan 3 days ago
this is key I think - I use it for graphics tasks - it sucks at graphical environments - always use some text based representation, not really surprising I suppose. chatgpt even suggested I'll use the text representation, claude said how about I give you svg and you convert it, they seem to know.
Comment by utopiah 3 days ago
PCB design with circuit simulation fits that bill perfectly.
Comment by compumike 4 days ago
If anyone wants to try an early beta, reply with your CircuitLab username and I'll get you set up. We know have a lot more to do, but would love some feedback on this early version!
Comment by oxqbldpxo 4 days ago
Comment by rgoulter 4 days ago
For another, the case mentioned in this post is quite specific. It's more useful to ask "ok, so they can't design circuit boards; what can AI do?"
Comment by bizrod 3 days ago
Comment by seobotaicom 1 day ago
Comment by throwatdem12311 4 days ago
It got me thinking. It could master all sorts of things like this but I wouldn’t care. I’m numb to it at this point.
But if could get an Inbachi-All clear in DoDonPachi SaiDaiOuJou, using only vision. Then I might start paying attention.
Comment by aidio 3 days ago
Comment by AdriaanvRossum 4 days ago
Comment by samuelbeek 4 days ago
Comment by iopapa 4 days ago
[1] https:/atopile.io/
Comment by so-cal-schemer 2 days ago
3.3.4 A Simulator for Digital Circuits
https://sarabander.github.io/sicp/html/3_002e3.xhtml#g_t3_00...
3.3.5 Propagation of Constraints
https://sarabander.github.io/sicp/html/3_002e3.xhtml#g_t3_00...
2.1.4 Extended Exercise: Interval Arithmetic
https://sarabander.github.io/sicp/html/2_002e1.xhtml#g_t2_00...
Comment by maxdo 4 days ago
Comment by krupan 4 days ago
Comment by lexicality 4 days ago
It's a thinly veiled advert for Atopile. I don't know if it's a company behind it or just someone with a lot of money to spend on advertising since their about page (and docs) both 404, and the "packages" link sends you to a login screen that tries to unlock 1password. I guess claude can make circuit boards but not functioning websites?
Comment by iopapa 4 days ago
Evaluating a model for specific use-cases like this that are bit more broad scope than a lot of typical microbenchmarks turned out to be quite the challenge.
Determining deterministically what a "good" electrical design is non-trivial and most electrical-engineers rely on good ol' intuition and decade long experience, so we tried to formalize it.
The only reason it was somewhat possible within a reasonable amount of effort is because atopile provides most of the complicated infrastructure for the benchmark: constraint solver, simulation, code-first electronics modeling, erc & drc checks, high level models of passive electronics components etc
Comment by codekansas 4 days ago
Comment by bbmatryoshka 4 days ago
Comment by krupan 4 days ago
Comment by bbmatryoshka 4 days ago
Comment by jeanmichelselli 3 days ago
Comment by amelius 4 days ago
The next pain-point is sourcing the components from Digikey, LCSC, etc., and finding suitable substitutes if necessary.
Of course this assumes the LLMs can already read datasheets because that's the biggest pain-point in designing electronics. It's like filling out tax forms.
Finally it would be great if LLMs could extract simulation models from datasheets!
Comment by thesz 4 days ago
> I'm excited by the option in Astra to route PCBs.
[1] https://en.wikipedia.org/wiki/EuriskoEurisko was used for VLSI chip design, then used rules discovered there to design TCS Traveler winning fleet.
It is unbelievable how artificial intelligence walk in circles.
Comment by iopapa 4 days ago
Not sure whether you played with llm datasheet extraction lately, but they are working their way up there. Even started reasoning about curves and footnotes.
Where do you think is the biggest pain point: part discovery, datasheet verification or substitute determination?
Comment by thenthenthen 3 days ago
Comment by nickff 4 days ago
Comment by amelius 4 days ago
Comment by nickff 4 days ago
Comment by amelius 4 days ago
Comment by dubbie99 4 days ago
Comment by tehologist 2 days ago
Comment by childintime 4 days ago
Comment by Ldorigo 3 days ago
Comment by YZF 3 days ago
That said you can guess a lot by the components and what's visible. I'll bet you that if you added a layer that recognizes the components, their position, orientation and visible connection and emits that as a JSON or some machine readable format the frontier models would be really good at telling you what's going on and even potentially filling in the blanks.
Comment by msuniverse2026 3 days ago
Comment by beering 3 days ago
Comment by lefra 3 days ago
Comment by a2ff6eeb0 3 days ago
Comment by CamperBob2 3 days ago
Comment by dennis16384 4 days ago
Comment by iopapa 4 days ago
Comment by ibobev 3 days ago
Comment by ccpc 4 days ago
Comment by edg5000 3 days ago
Comment by dboreham 3 days ago
Comment by cobychapple 2 days ago
Comment by CamperBob2 4 days ago
Comment by winrid 4 days ago
Comment by edg5000 3 days ago
- Designing circuits in Skidl
- Checking my layout work (not doing it)
- Operating my lab equipment (running my scope, lab PSU, lab load, programmer/debugger any any other interface.
Comment by mschuster91 4 days ago
Anyway... the posed question reminds me of an anecdote I cannot find because Google is contaminated to hell and beyond, some researchers a decade ago let a machine-learning algorithm loose on an FPGA, and it "found" a design that worked but made no sense, because it exploited unique physical features of this specific chip.
Comment by Legend2440 4 days ago
Comment by mschuster91 4 days ago
Thanks!
[1] https://www.damninteresting.com/on-the-origin-of-circuits/
Comment by hn_submit 3 days ago
Comment by cmiles8 4 days ago
I’ve had similar results asking AI to design 3D models for 3D printing.
“Coach me on optimizing error on my printer”… helps.
“Build me a print ready file to these specs.”… it’s like a drunk cat attacked my computer. Just confidently puts out total nonsense.
Comment by sitzkrieg 4 days ago
Comment by sillypuddy 4 days ago
Comment by tdeck 4 days ago
Comment by johnboiles 4 days ago
Comment by extralongdivisi 4 days ago
A lot of datasheets are inaccessible without signing an NDA. Even if you're a VC-backed enterprise, some unnamed chip vendors will tell you to pound sand if you're less than 8 figures of annual revenue.
Worse, many recommendations in datasheets were written in the 80s, overkill for many applications, or completely wrong and won't be updated until an errata is published 6 months later. Given current workflows, I don't see how AI would help designing a PCB with an alpha chip that's doing anything remotely novel.
More to the articles point, AI designing ASICs or other Verilog/HDL defined components could be very interesting use case
Comment by lefra 3 days ago
Only for very high-end stuff, where just designing the board around the chip needs a team of engineers.
Comment by extralongdivisi 2 days ago
This is becoming more true as a larger percentage of hardware infrastructure is occupied by the datacenter economy.
Comment by edg5000 3 days ago
Comment by extralongdivisi 2 days ago
Comment by librasteve 3 days ago
Comment by saejox 4 days ago
All robots designed by robots.
Likely a crazy youtuber first
Comment by vessenes 4 days ago
Comment by NotThereYet 3 days ago
Comment by joshka 4 days ago
Comment by conorcleary 4 days ago
Comment by Anil0809 4 days ago
Comment by goosethe 4 days ago
Comment by throwaway219450 4 days ago
For circuits I would trust a netlist or DRC/ERC review, checking a design against reference circuit values, probably not placement as that tends to be guided straight from a datasheet where it makes a difference and I like the artistic side of it.
Comment by cozzyd 4 days ago
Comment by dackdel 3 days ago
Comment by holoduke 3 days ago
Comment by dibyaprakash 3 days ago
Comment by ChrisMarshallNY 4 days ago
Frankly, I am surprised that it isn't already a solved problem, as we've had silicon compilers, for many years, and I always figured that IC design is more difficult than PCB.
Comment by hdhdbdbdxk 4 days ago
PCB design on the other hand more often then not has outside constrains like mechanical, thermal an RF design
Comment by napowderly 4 days ago
Comment by robosynx 3 days ago
Comment by omid-io 2 days ago
Comment by Sergekad0 2 days ago
Comment by lu7897859 3 days ago
Comment by junaidshaukat 3 days ago
Comment by paidx 4 days ago
Comment by tshrove 3 days ago
Comment by aaron695 3 days ago
Comment by ccbakla 3 days ago
Comment by jing09928 4 days ago
Comment by luciana1u 3 days ago
Comment by Unified-Mentor 3 days ago
Comment by mohan_bee 4 days ago
Comment by EtienneDeLyon 4 days ago