By Ed Sperling
Mentor’s Colin Walls questions whether embedded software engineers would write better code if time on their computers was limited. That’s like sharing a desk. Make sure you remove all valuables before you leave.
Synopsys’ Alex Seibulescu looks at coverage in the world of high-level verification and synthesis, and what the current best practices are. It still isn’t as simple as doing everything once, but at least companies are creating some interesting workarounds.
Cadence’s Richard Goering digs into a new methodology for easing 32/28nm designs. Here’s what most companies have to look forward to. The good news is by the time they reach this node some of these solutions will have been automated.
Mentor’s Jay Gorajia examines production schedules and the impact of factor strategic alignment, along with the list of complaints about whose fault it is when something goes wrong. One common theme emerges: “It wasn’t me.”
Semico’s Michell Prunty gives a short-term grim forecast of the IC market—don’t expect a turnaround until sometime next year. So far it’s still better than 2008, but does anyone actually remember a recovery?
Cadence’s Joe Hupcey reports some of the highlights from CDNLive in Bangalore. The flight over isn’t one of them.
And in case you missed the most recent Low-Power Engineering newsletter, here are some standout blogs:
–Synopsys’ Cary Chin takes a look at power efficiency in the iPhone 4S. Battery life has improved, but so has functionality.
–Mentor’s Barry Pangrle looks at three different implementations of a new ARM core. This is an interesting glimpse into innovation around a common platform.
–Cadence’s Luke Lang examines isolation, and how to do it, using the three main power formats—CPF, UPF 1.0 and IEEE 1801. Understanding the differences is critical for companies using multiple vendors’ tools and IP.
–Apache Design’s Aveek Sarkar raises the discussion up a notch, saying that a global view is necessary for simulation and validation of the power delivery network.
–Tensilica’s Chris Rowen equates building a business to running a marathon. It takes longer and much more energy than you initially thought.