IP Integration : What is the difference between stitching and weaving?
As a hardware design engineer, I was never comfortable when someone talked about IP integration as ‘stitching a chip together’. First of all, it sounded like a painful process involving sharp needles, usually preceded by a painful accident. I happened to be the recipient of said stitches when, at 8 years of age, I contested a stairs post with my forehead, and sorely lost. I have to say, luckily, I have been quite adept at avoiding the needle and thread ever since. That was of course until once when, an hour before that important customer presentation, my top-shirt button, due to an over enthusiastic yawn, pinged across my hotel room floor like a nano-UFO. A panicked retrieval of the renegade button was followed quickly with a successful hunt for an elusive emergency sewing-kit. The crisis quickly dissipated as I stitched back the button in a random-but-directed type of methodology. Needle-less to say stitching, whilst sometimes necessary, makes me uncomfortable.
To read the full article, click here
Related Semiconductor IP
- 50G PON LDPC Encoder/Decoder
- UALink Controller
- RISC-V Debug & Trace IP
- UALinkSec Security Module
- PUF-based Post-Quantum Cryptography (PQC) Solution
Related Blogs
- I3C IP: Enabling Efficient Communication and Sensor Integration
- Advanced SoC Development Uses Next-Gen IP Integration Tools
- Efficient IP Packaging for Today’s SoC Integration
- IP integration: Is it the real system-level design?