There are really two layerscapes- one is a software-based program and the other is an applications processor. One layerscape requires high-speed networking and communications technology to perform, and the other was designed to provide high-speed networking and communications for similar data-intensive applications.
Now that more and more engineers are developing the embedded code that control Internet of Things (IoT) products, teams are under increased pressure to create better software in less time-- driven by the more frequent release cycles, higher costs and shorter delivery dates associated with the fiercely competitive global IoT market.
Today's dream car will have hundreds of onboard sensors, more than fifty separate electronic control units (ECUs), about 100 million lines of code and, now, internet connectivity. All of this complexity is designed to not only optimize the performance of the engine, transmission, brakes, and steering, but also to enhance convenience and comfort. The flip side to this added functionality, however, is that connectivity opens the vehicle to new security concerns.
Reports predict that the resurgence of microcontroller sales in the coming years will be with MCUs that will potentially connect within the Internet of Things (IoT) and that the field is split between 8-bit and 32-bit devices. Wearables or smart homes might only require 8-bit MCUs, but once a gateway enters the picture, the application is sure to fall into the 32-bit MCU space.
Over the past five years, GaN power FETs have shown to have an undisputed technical advantage over silicon. Starting with a fundamental materials’ limit advantage that is three orders of magnitude better than silicon, it was possible to construct initial devices that already had better electrical characteristics than the state-of –the-art silicon; GaN also showed much lower parasitic device capacitance values for the same device on-resistance.
The IoT is dragging embedded developers into the network security debate. Interconnectivity threatens user data and dependable solutions that minimize the risk to companies and their customers are now a requirement. As embedded devices become increasingly networked, there is a growing risk that poor software quality could affect the quality of the final product and the security of customers’ data.
The 32-bit MCU has a key function in the IoT pyramid: It provides the data throughput, reading sensors and sending real-time sensor data over an IP-based network. The 32-bit architecture allows designers to put low-power connectivity next to it and communicate directly to the Wi-Fi access point or GSM modem.
Any Cortex-M developer has likely struggled with getting interrupts to work and then debug them. Interrupts and exceptions are by definition asynchronous to the execution flow of your application software and it can be very difficult to visualize interrupt behavior, and debug the same. The author describes new techniques for analyzing interrupt behavior in a running system.