4 ms·
I agree. I just got a great book, Electronics Principles by Malvino, on electronic engineering with especially analog focus. I was told to get another one to le
by nickpsecurity 11y ago
I agree. I just got a great book, Electronics Principles by Malvino, on electronic engineering with especially analog focus. I was told to get another one to learn proper PCB design. There's others for Verilog. Unlike programming, most stuff in these has to be learned by trial-and-error with hardly any instant solutions a la StackOverflow. Graphics cards themselves are their own beasts with complex issues even for simple ones, esp integration w/ regular software.
So, as I'm reading this, I'm surprised how nonchalantly he describes what looks like a ton of headaches that's in front of me personally. Doing some basic stuff in Verilog on an FPGA is straight-forward. What he's done was not unless he found some excellent resources that basically let him cheat a lot in the learning. I'd be interested in them as I'm collecting resources with HW knowledge and wisdom.
- Cyph0n 11y agoI'm also looking for good books on PCB design and Verilog. Could you please share the titles that were recommended to you?
- nickpsecurity 11y agoI actually lost them. However, after an hour of digging through Schneier's blog, I found some of them. For analog and PCB, there's this: Electronic Principles 8th Ed Malvino http://www.amazon.com/Electronic-Principles-Albert-Malvino/dp/0073373885/ref=sr_1_1?ie=UTF8&qid=1460908656&sr=8-1&keywords=electronic+principles+malvino http://www.amazon.com/Electronic-Principles-Albert-Malvino/d... Note: Look up the 2nd edition or something as I got it for $2. Principles of analog don't really change. Super-easy to read with more heuristics & diagrams than theories. I didn't know until today it was being updated. Circuit Designer's Companion... for free! http://diagramas.diagramasde.com/otros/The%20Circuit%20Designers%20Companion.pdf http://diagramas.diagramasde.com/otros/The%20Circuit%20Desig... Note: High-assurance engineer told me this guy was a master and this book is all-in-one most of what you need to know. A reviewer said it's mostly for digital, not analog, stuff but that's probably your goal. Digital stuff is highly opinionated on whether it's "good" or not. So, read the reviews to determine if it's good for you personally. http://www.amazon.com/Digital-Design-RTL-VHDL-Verilog/dp/0470531088/ref=zg_bs_3726_4 http://www.amazon.com/Digital-Design-RTL-VHDL-Verilog/dp/047... http://www.amazon.com/dp/0131678442/?tag=stackoverfl08-20 http://www.amazon.com/dp/0131678442/?tag=stackoverfl08-20 Note: These were said to be nice for beginners on Verilog, etc. Good tutorials online, too, with practice code and help on StackOverflow. I suggest getting a simulator and/or cheap FPGA then just experimenting. http://www.amazon.com/dp/1461186293/?tag=stackoverfl08-20 http://www.amazon.com/dp/1461186293/?tag=stackoverfl08-20 http://www.amazon.com/dp/0470054379/?tag=stackoverfl08-20 http://www.amazon.com/dp/0470054379/?tag=stackoverfl08-20 Note: First is a cookbook for FPGA designs. Second covers things like floorplanning and resets. http://www.amazon.com/Digital-Systems-Engineering-William-Dally/dp/0521592925/ref=zg_bs_3726_70 http://www.amazon.com/Digital-Systems-Engineering-William-Da... http://www.amazon.com/VLSI-Test-Principles-Architectures-Testability/dp/0123705975/ref=zg_bs_3726_43 http://www.amazon.com/VLSI-Test-Principles-Architectures-Tes... http://www.amazon.com/Comprehensive-Functional-Verification-Complete-Industry/dp/0127518037/ref=zg_bs_3726_45 http://www.amazon.com/Comprehensive-Functional-Verification-... Note: Books on Digital System Engineering, VLSI testing, and functional verification to top it off. Endnote: I don't guarantee quality of any of these except Electronic Principles and Circuit Designer's Companion. The rest just had positive reviews plus what I assessed to be decent information for their target topics.
- Cyph0n 11y agoThanks a bunch man! I really appreciate it!
- dluan 11y agoGot any other good books you like?
- nickpsecurity 11y agohttps://news.ycombinator.com/item?id=11515190 https://news.ycombinator.com/item?id=11515190
- joshvm 11y agoFor beginners, buying books on PCB design isn't worth the money. You'd be better off spending $50-100 on a load of sensors, designing the boards for them and getting them built. You'll learn far more than a book will teach you. There are lots of good Eagle and KiCAD tutorials online. If you need to know about design, read application notes from manufacturers. There are thousands and thousands. Often they will dictate how you should route a particular component. You can look at reference boards from people like Analog, which typically come with schematics and layout files. Most of the big name companies have guides for layout: https://www.google.co.uk/search?q=pcb+design+application+note https://www.google.co.uk/search?q=pcb+design+application+not... What you will quickly find is that there's a lot of differing opinion on what is "right". Until you need boards with high speed digital/analogue/mixed, you don't really need to worry much about how things are laid out. You will almost always be constrained by more practical issues like enclosure sizes or where you have to put connectors.
- nickpsecurity 11y agoI appreciate your feedback but it concerns me. It sounds like a lot of trial and error with components that cost money. One concern I have with that is it's dealing with electricity. What's the odds of getting components fried or yourself electrocuted just doing trial and error learning from tutorials and datasheets? And when you've done a bunch do you even really understand what you're doing when given fresh components? "If you need to know about design, read application notes from manufacturers. There are thousands and thousands. " I'll try to remember that. "You will almost always be constrained by more practical issues like enclosure sizes or where you have to put connectors." I'll definitely believe that. Thanks for the tips and different perspective.
- akiselev 11y agoIf you make electronics, the odds of frying a component or electrocuting yourself is 100%, regardless of how educated or talented you are. The following happen to me on a regular basis, whether I'm working on high speed digital/RF or making something simple like an arduino shield, even though I learned as an apprentice under a brilliant EE: * PCB with poorly aligned copper layers shorting the second the prototype is plugged in, usually destroying at least one chip. Lots of smoke and burning FR4 * Solder in $100+ high power transistors the wrong way. BOOM * Using a counterfeit capacitor from shady vendor that either shorts internally or just plain explodes. Happens a lot when I need a really large capacitor and have to get it on short notice * Forget to use a little extra flux and tin 'whiskers' form between freshly soldered pins that short them the second the device is powered up. This is so common that NASA has a whole website dedicated to the topic [1] * Use wrong temperature profile or make the pin layout a thousandth of an inch too small or large and bam, two solder balls on a BGA flow together, requiring hours for reflow and reballing if you're lucky, and a new $2,000 FPGA if you're not. Any nontrivial circuit is going to be impractical to simulate (and impossible to describe analytically as a whole) for all but the most well funded projects so I'd say 90+% of EE is trial and error, even for the most experienced designers. There's many rules of thumb and you develop an intuition for a wide variety of situations just like you do in programming, but it's just a fundamentally different field with different constraints. [1] http://nepp.nasa.gov/whisker/ http://nepp.nasa.gov/whisker/
- shabble 11y agoI've yet to find any good intro-level PCB design references. There's plenty of good information out there, but it's generally not easily accessible, and is scattered around blogs, forum posts, open hardware sourcefile dumps, etc. There are some fairly decent videos from the likes of Dave Jones (of EEVBlog), and some of the Mikeselectricstuff(.co.uk) that talk and sometimes show the interesting parts of PCB design. What's lacking (or I've yet to find) is a simple tutorial-type progression that explains both how, and why, to do certain things, especially when it comes to things like component selection, footprint design, part layout, and actual track routing. The "try it, make mistakes, learn" approach is almost inevitable, but the cost/time of the feedback loop can be pretty steep for a hobby (you can have 24-hr turnaround on boards if you've the $$$, or you can pay $5/board in 6-8 weeks, but the middle ground is tricky and messy. Plus all teh different board houses might have different design rules and other things that complicate matters for beginners. My suggestion would be to find some Open Hardware kits or designs, buy a couple to make them, but also get the design files (hopefully in either kicad or eagle, which are free/affordable, and then start by ripping up all the routing, and seeing if you can re-track all the components get get it to pass ERC/DRC checks. Maybe bounce it off a few people in /r/askelectronics or eevblog forums, and then have it sent out for fab. If it works, pick a new OHW project with harder things, and repeat :) That saves you from having to deal with footprint, schematic capture, and BoM decisions initially, and focus just on teh board design parts. You'll want to get there eventually, and you can learn a lot from how other things are put together. Maybe pick some simple circuits (basic CMOY headphone amp, say), and redraw the schematic in your EDA tool. Then gather up teh datasheets, and usually they'll have a recommended footprint drawing, and you can learn how to build those in your toolchain. There are some open libraries of component footprints (I think sparkfun has one? Maybe octopart as well?) but it's a useful skill to learn, and easiest on little things with few pins before you work up to the 192 pin FPGA or something :) * Always print your designs 1:1 scale before sending out for processing. * Always check your design file outputs (gerbers) in an external viewer to make sure they look ok/make sense. * Remember to flip top/bottom layers the right number of times! This should happen properly on export, but it's easy to screw up and have the perfect board if you can find components with the exact opposite pinouts :) * Don't be scared of starting with surface-mount. You can usually get things in pretty big packages if you want, and an 1812 or 1210 is actually not far off the size of a normal resistor body (minus the leads). You can go smaller as you're comfortable and pick up technique. * I can't really offer any layout tips, because I'm still not very good. If anyone has pointers to good docs on: (a) how to decide where to place/orient your components on the board to begin with, (b) choosing placement/routing grid sizes and track widths/via sizing, (c) appropriate layer count/usage - when to add more layers, value of pwr/gnd planes, use of fills, etc. And lastly, with kicad especially, how to fix things when you've routed yourself into a corner with just a few pins left, but no way from A-B (preferably without either adding layers, or through-hole links. I know about the 0R resistor bridge, but it has its limitations.
- rjsw 11y agoYou can also do the trial-and-error stuff with Verilog/VHDL using one of the free simulators that is part of the FPGA vendor's tools.
- nickpsecurity 11y agoThat's true. Can certainly learn the Verilog/VHDL part that way. RTL and Boolean too.