Hi, naperlou. Right you are. And the 32-bit devices have more types of communication peripherals, too--CAN, Ethernet, USB, SPI. I2C, etc., so chip creators have moved even more hardware onto silicon. That effort makes life easier for engineers and programmers.
The death of the little 8 bitters was announced several years ago, yet they still appear to be quite live with ever expanding capability. Guess they never saw their obit, much like Mark Twains quote on the exaggeration of the rumors of his death! As far as making life easier for engineers and programmers however I will disagree. The reason is with every expansion of technology comes ever more complex solutions, and with it, ever more headaches to the designer. Think autonomous cars for example, then the redundancy that must be built into them. Engineering was never easy and will not be easy in the future. In the 60s we used two transistors to make one flip flop, thus 36 bit registers took a lot of parts. Sixty-four k "core" stacks were huge and expensive, but today I whine about having "only" 16GB in my machine.
Will 32 bit machines be replaced by 64 bit? How about 128 bit guys with far more and faster registers? What are the practical limits to bus width? ASCII is still 8 bits wide.
I have been reading a lot on load sharing processor arrays lately. Sort of like multitasking in hardware. I'm not quite ready to send my 8 bit stuff to the Smithsonian quite yet. We always live in an age of discovery and I'm very happy to be alive today.
Hi, Island_Al. Yes, plenty of life left in 8-bit MCUs for a wide variety of uses. A few days ago I sketched out a neat circuit for model-railroad enthusiasts that would use an 8-bit PIC in an 8-pin package--and an assembly-language program.
I have to disagree, 8 bits are still very much alive, especially when combined with a good compiler and plenty of memory, which is now pretty cheap. I was looking into crunching some color graphics a while ago and did two designs; one with an arm and the other with a SiLabs 8051. The 8051 was faster and cheaper in this application.
In most of the small appliances and sensors I work on, an 8 or small 16 bit machine is still my first choice. It's hard to justify a full 32 bit core when I only need 4k of code.
Hi, AndyT. The "memory" connector is actually the connector for a TI MCU "ControlCard," already in place. The odd perspective of the image places the upper edge of the ControlCard along the same line as the far edge of the small motherboard. Look again and you'll see a board plugged in. The MCU has a lot of memory. The connector lets engineers and programmers use different types of ControlCards.
Long after whatever MCU that you choose has gone out of production and is not available anywhere, thye same analog ICs will still be available from multiple makers and distributors stock. So if the anticipated product life is measured in days or months, then choose the MCU approach. But if it is a product with an expected lifetime of years, then make it out of sustainable parts. (A new expression?) Cutting edge stuff often causes bleeding.
Festo's BionicKangaroo combines pneumatic and electrical drive technology, plus very precise controls and condition monitoring. Like a real kangaroo, the BionicKangaroo robot harvests the kinetic energy of each takeoff and immediately uses it to power the next jump.
Design News and Digi-Key presents: Creating & Testing Your First RTOS Application Using MQX, a crash course that will look at defining a project, selecting a target processor, blocking code, defining tasks, completing code, and debugging.
Focus on Fundamentals consists of 45-minute on-line classes that cover a host of technologies. You learn without leaving the comfort of your desk. All classes are taught by subject-matter experts and all are archived. So if you can't attend live, attend at your convenience.