There seem to be alot of applications that don't require 168MHz and the PSoC parts have been around long enough to make the Triscend disease unlikely. I do like the fact that the tools are integrating TOWARD the IDE and away from the FPGA place and route flows.
There are also downsides to the 'all things to all users' approach :
The PSoC Creator build times are glacial - there are so many software jugglers involved.
The IP components may be flexible, but sadly they too are rather slow. Their specs give 15MHz for 16 bit counters. This beta (select customers only) release of v2.0 claims 20% better routing, but that's only 18MHz...
Contrast that with a STM32F4, which claims 168MHz 32 bit counters (and much more Flash/Ram/CPU/FPU for similar prices...)
There also seems to be a significant silicon cost to the 'all things' approach. PSoC parts are not cheap, and may yet suffer the FPSlic/Triscend disease.
It is looking faster and cheaper, to deploy two focused parts.
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.