Here's a what if. Say your application is a straightforward industrial process that can be handled by an 8 bit MCU. However, when upset conditions occur then suddenly all sorts of interrupts happen, complex software decisions need to be made, real time response is required. Would it be feasible to design a system with a seperate MCU, maybe 32 bit, to deal with the more complex software environment, rather than trying to cram everything into a one big MCU? Especially considering that upsets should be very rare..
If you are as interrupt-intenseve as you say, you have two options:
1) A 16-bit microcontroller. Why? because you have extra proessing power and don't have the interrupt overhead of a 32-bit MCU
2) Go like you said - an 8-bit as a dedicated interrupt processor, interfacing to a larger 32-bit or 26-bit system controller. I see this a lot
The company says it anticipates high-definition video for home security and other uses will be the next mature technology integrated into the IoT domain, hence the introduction of its MatrixCam devkit.
Siemens and Georgia Institute of Technology are partnering to address limitations in the current additive manufacturing design-to-production chain in an applied research project as part of the federally backed America Makes program.
Most of the new 3D printers and 3D printing technologies in this crop are breaking some boundaries, whether it's build volume-per-dollar ratios, multimaterials printing techniques, or new materials types.
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.