News for hackers. Stuff that matters.
Re:Coding Up an IoT PCB Design by bb88 on Wednesday May 04, 2022 @01:32AM (#31257066)
There was a talk at Kicon that touched on this:

https://www.youtube.com/watch?v=WErQYI2A36M

At some point for large enough designs, it's hard to validate that pins match up to signals. Though for small designs I think you're right.

Re:Coding Up an IoT PCB Design by deaddabe on Wednesday May 04, 2022 @04:44AM (#31258121)
This talk was impressive. Especially repeating parts and even using machine learning to optimize values of resistors.

TL;DW the tool is named Skidl ans uses Python to generate net lists for KiCAD. https://github.com/devbisme/skidl

Re:Coding Up an IoT PCB Design by ris on Wednesday May 04, 2022 @07:27PM (#31267193)
> chooses an imperative language to define circuit topologies

hmm.. maybe that's ok if they don't go too overboard and encourage a functional style

> uses & as an in-place, mutating operator

that's it, I'm out of here

Re:Coding Up an IoT PCB Design by bb88 on Thursday May 05, 2022 @03:51PM (#31277722)
I agree. '&' should not mutate.

In this case it's simple to do:

   net1 = pin1, pin2, pin3
   design = net1, net2, net3...
Re:Coding Up an IoT PCB Design by welterde on Wednesday May 04, 2022 @07:48AM (#31259196)
So far I have only used skidl for a few small projects. One project where it worked really well was in creating the schematic for backplanes, which is normally kinda tedious - especially if one has to create multiple variants with different slot numbers.
Re:Coding Up an IoT PCB Design by kayson on Wednesday May 04, 2022 @11:43AM (#31262066)
I don't buy that argument. ICs are massive. Way bigger in terms of number of schematic pages than any PCB. I think the problem is that PCB designers are used to having very "flat" schematics whereas IC designers always have a lot of hierarchy.

For example, the madness with the schematic he shows in that video for all of the by pass caps is something you'd never really see in an IC design. The cap would be placed in the schematic hierarchy either right at the voltage regulator or right at the circuit where its needed. But on PCB schematics you see that kind of thing all the time.

Part of the problem may be that with an IC you can easily simulate anything. The whole workflow is built around it. For a PCB, outside of using models for standard analog building blocks via spice simulator, it's a lot harder to verify your design.

Re:Coding Up an IoT PCB Design by Brian_K_White on Wednesday May 04, 2022 @08:11AM (#31259379)
Wow. That is really really cool.