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
- NFC wireless interface supporting ISO14443 A and B with EEPROM on SMIC 180nm
- DDR5 MRDIMM PHY and Controller
- RVA23, Multi-cluster, Hypervisor and Android
- HBM4E PHY and controller
- LZ4/Snappy Data Compressor
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
- lowRISC Tackles Post-Quantum Cryptography Challenges through Research Collaborations
- How to Solve the Size, Weight, Power and Cooling Challenge in Radar & Radio Frequency Modulation Classification
- Programmable Hardware Delivers 10,000X Improvement in Verification Speed over Software for Forward Error Correction
- The Integrated Design Challenge: Developing Chip, Software, and System in Unison
- Introducing Mi-V RV32 v4.0 Soft Processor: Enhanced RISC-V Power