Common definitions in chip design and production
parallella.org
parallella.org
Everyone ? Maybe everyone in the field of chip making ? How does the knowledge of these definitions impacts the life of those not in this field (not being sarcastic, this is an actual question) ?
I believe it was intended to mock developers evangelical quests to educate the public on programming languages/frameworks/methodologies/etc.
Making useful things at those scales amazes me everytime.
The Internet is truly marvelous in this regard. I'm using free tutorials, documentaries and videos to satisfy my curiosity and pretty much getting an EE education. Ignoring the car pictures, the Internet gives me much hope.
Oh .. and for now, I have a cheap Cypress PSOC that I'm playing with. They were literally giving 'em away at Maker Faire :)
The reason is straightforward enough - I was a kid, and am now an adult, who cannot stop asking "why?", and habitually disassembled machines to understand them (and then usually hastily reassembled upon hearing the crunch of parental tyres on gravel). Having access to Brittanica as a kid helped too. I started making useful analogue circuits before I even knew ohm's law, as I could see and grok what components did when put together. Nothing beats reverse engineering as a learning experience, apart from perhaps forwards engineering.
Essentially, to have deep knowledge of something requires a desire to have that deep knowledge. Most are willing to stop at some level of abstraction and accept that things "just are", but others, myself included, need to understand how electrons work, why P-N junctions do what they do, what is this matter/energy thing anyway, or how about that spacetime thing that it sits within?
Turtles all the way down.
Not the best title. I was also thinking it was the top 200 chips like the basic 7400 family, 6502, 8051, 555, etc.
Using their documentation last year was a nightmare with errata in archived forum posts. I also found the community response quite hostile to simple outsider questions.
Then again, when we finally completed our testing of their chips we found the memory transfer overhead killed any benefit for us.
Audio codec - compression is now common but only coding/decoding is required (hence the name).
GPIO - General Purpose Input Output.
Schmidt trigger - I have no idea what they wer trying to type but my cats do the same thing. A device with a Schmidt trigger input provides hysterysis for noise rejection?
The referenced wiki article on audio codecs also talks about compression, in audio the two on very similar. GPIO is GPIO, but an engineer should know what they are and do. Schmitt triggers are really spelled like that, not with ..dt. Schmitt triggers are used for generating a stable block signal out of an analog signal, in order to decrease ripples and glitches
Schmitt Trigger: Comparitor circuit wityh
I would guess that the list grew out of years of conversations and exposed gaps of shared knowledge. It's a good list of things that establish a common vocabulary in a specific industry.
IT-wise, yes younger generations seem to be in total loss with ICs and I believe the simple reason is that there are no jobs there anymore so there isn't a motivation to learn more about it. Virtual everything (as started off with JVM) has contributed too there. Not sure though that they are missing out that much.
Sounds like extra-thick satire to me.
one and one zero
everything else is one
make a computer
;)
I suppose "The Elements of Computing Systems" is an inspiring book.
Now it sounds as if there are 200 actual chip definitions, whatever that would mean, since it doesn't say its (just) about words and jargon used in the field of chip design.
I confuse easily.