I could not provide a break down of Semico Research's data. They only provide so much information for free.
To find out more Semico would like people to buy a 58 page report with 15 tables and 33 graphs.
But on a qualitative basis my undertstanding is that the functional and software complexity of leading-edge system chips is increasing.
Meanwhile the need to get to market quickly is increasing. The result is that in many geographies equipment makers often rely on the SoC provider to define much of the basic equipment hardware and software functionality while they are working on the plastic casing, the user experience software, the boxing, the documentation, the sales channel distribution and the marketing of the equipment.
We've heard about the software burden on SoC for years -- and about how hard it is for chip companies to get properly paid for the software they provide.
Looks like this is really starting to kick in at 28-nm and below.
Does the the 9 million unit viability threshold ring true to readers?
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.