What does faster mean really in this contest? Should we consider ARM7 and ARM9 as microcontrollers, in which case this Microchip's product would pale into insignificance? We should consider performance per Watt, performance per Dollar among other factors such as software eco-systems, security of supply etc. It's not just about an arbitrary CoreMark number alas....
Microchip's new 32-bit connectivity MCU might well be targeted for the IoT applications where power is not a problem. The features look interesting. I would like to evaluate how the DSP engine along with 159 additional DSP-centric instructions helps in improving the performance of the MIPS microAptiv Core.
It certainly isn't the fastest 32-bit MCU. While it might outperform Cortex-M4 when not using floating point, it has caches and doesn't run from flash. So it should be compared to Cortex-R4/R5, which run at much higher frequencies (Samsung SSDs use 3 at 400MHz) and have better IPC as well.
I am glad that Microchip has actually started to do something with their 32bit line of products. FOr the longest time, they were not really all that great compared to their dsPIC line of products. I still am hoping that they might decide to come out with something that has a FPU on it. As for their claim as the fastest 32bit device, I will have to dig into that a bit more.
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.