Ditto, as a long time user in several of the different offerings from 8 to 16 bit devices, I agree that Microchip serves well their shareholders by focusing strategies in industrial and consumer embedded products. Few vendors compare to the size and depth of their user knowledge base and prompt response to errata.
I love the straight talk and directness of the CEO! I would wish that more companies would follow that example. In some ways, I wonder if his clear, direct communication style is an enabler for the company. The understanding of the company direction and interests can only help each employee in their job and managers at all levels do theirs.
IMO, Microchip may not have the latest technologies or the brightest people in R&D, but it has a clear-minded CEO to understand what customers really want.
I always have this impression that Indian tends to change their minds very easily, talk a lot BS, but produce poor results, and think too complicated, but Steve Sanghi is very different.
Not really. In fact, Microchip offers one of the easiest tools to debug and program its MCUs. I have used 68HC11/09, ATmega128/8, Cortex-M0 and 8051 and MSP430. Microchip products have the least problems of all.
Microchip's MCU may not be the cheapest, compared to Atmel AVR, Silab 8051 or Cortex-M0 (any brand), but its tools are very reliable.
As a veteran user, any MCU is very easy to use, if you have good attitude to learn and aptitude to explore.
The Epiphany multicore architecture IP is an integrated microprocessor solution, featuring up to 4,096 processors on a single chip, connected through a high-bandwidth on-chip network. Each processor node represents a fully-featured floating point RISC processor built from scratch for multicore processing, a high bandwidth local memory system, and an extensive set of built in hardware features for multicore communication.
This has got to revolutionize handheld processing, no?
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.