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
- USB 20Gbps Device Controller
- AGILEX 7 R-Tile Gen5 NVMe Host IP
- 100G PAM4 Serdes PHY - 14nm
- Bluetooth Low Energy Subsystem IP
- Multi-core capable 64-bit RISC-V CPU with vector extensions
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
- From guesswork to guidance: Mastering processor co-design with Codasip Exploration Framework
- Enabling AI Innovation at The Far Edge
- Unleashing Leading On-Device AI Performance and Efficiency with New Arm C1 CPU Cluster
- The Perfect Solution for Local AI
- UA Link vs Interlaken: What you need to know about the right protocol for AI and HPC interconnect fabrics