Software is from Mars, hardware is from Pluto
Engineers learn the hard way why it’s critical to communicate when a major requirement gets missed
It was the big day for the Software Team – they were scheduled to demonstrate their latest and greatest rendition of their SNMP network management software package to the Marketing Team. Months of intensive sweat-and-blood software design was about to be judged. The new hardware was… well, just hardware.
Our new prototype hardware was set up in the lab and was fully debugged, transmitting all the test traffic packets between multiport network hubs without error. This was a bit of a problem because the Software Team wanted to demonstrate how their Management Information Base (MIB) could tally and report all sorts of transmission anomalies – runt packets, CRC errored packets, collided packets, discombobulated packets – whatever. Unfortunately the Hardware Team had done its job superbly so there were no damaged packets to tally during the demonstration.
To read the full article, click here
Related Semiconductor IP
- DSP-Based 112G SerDes
- XTAL oscillator in TSMC-7nm
- GPU
- V-by-One Verification IP
- AI model compression IP
Related Blogs
- Microsoft Signals the Return of "Expensive Hardware, Cheap Software"
- Business Models: EDA Is Software But It Used To Be Sold As Hardware
- IoT Changes Hardware Companies into Software Companies
- Software engineers can debug hardware too!
Latest Blogs
- Embedded Security explained: Secure boot for embedded systems
- World's First Standards-Compliant 112G PHY IP for Linear Optics: A Turning Point for AI Interconnects
- One Key for Every Door: How Aliro Extends the UWB Digital Key Beyond the Car
- Reprogrammable Post-Quantum Security for SoCs: Why Crypto-Agility Matters
- Designing the Beam Steering Core for a C-Band AESA: A Look at VSI's VBF0644 GaAs Beamformer IC