Compilers and ADAS aren’t often used in the same sentence. For developers, that anomaly can represent a design challenge, as compilers in general are not designed for this particular application, which also happens to be at the top of the safety and security checklist.

To understand how these compilers should be tested and implemented, I spoke to Sjoerd van der Zwaan, the Chief Product Officer at Solid Sands, on this week’s Embedded Executives podcast.

Sjoerd explains how and why compilers for ADAS are different from general compilers, and why you need to run your compiler through an appropriate series of tests to ensure compatibility.

AI at the endpoint gets yet another boost from EMASS, a fabless semiconductor company that recently emerged from stealth mode.

Having your processing at the endpoint presents a few significant challenges, namely the amount of processing that can be made available and the ability to run from a battery. EMASS has come up with a way to do this a little differently from what’s been done previously. They can attach their RISC-V processing element to any sensor, making the device an AI accelerator. It’s a little difficult for me to put into words here, so check out this week’s Embedded Executives podcast, where I spent some time with Mark Goranson, EMASS’s CEO, who explains it in detail.

No matter what your end device is, be it a light bulb or a driver’s license, it needs to be secure. I don’t think we need to go through the reasons why it needs to be secure. How you do that is becoming increasingly more difficult. And you may be looking at protecting millions of devices, where each one needs its own unique identity.

To get a handle on how you would do this, at least where you would begin this daunting task, I spoke to two experts: Patrick Carrier, a Manager for Secure Solutions at Infineon, and Xin Qiu, the Head of Security Solutions at CommScope.

On this week’s Embedded Executives podcast, they lay out the need and then the process a developer would follow.