ISO 8800 is a standard aimed at functional safety in automotive applications, pertaining to artificial intelligence. It provides the guidelines for integrating AI systems into any safety-related functions of road vehicles. In full disclosure, I wasn’t aware of this standard, and I was frankly surprised I wasn’t.

To remedy the situation, I invited Jill Britton, the Director of Compliance at Perforce, onto this week’s Embedded Executives podcast. Jill explained what the standard is all about and which parts of it are key for embedded developers to understand.

Here’s a walk down memory lane. The Eclipse Foundation dates back more than 20 years. Mike Milinkovich, the Foundation’s Executive Director, has held this role since its inception. The role of the foundation and the embedded industry in general has evolved more than anyone could have conceived.

Stay tuned to hear about some of the issues the Foundation has been involved with and what’s been required to keep the community on par with other areas of the technology landscape. And that includes the ORC working group, which you can learn more about on this week’s Embedded Executives podcast.

We talk about AI a lot here at Embedded Computing Design, and that’s a huge understatement. What we don’t talk about often is the power required to keep the data centers going, specifically the data centers that form the backbone of all this AI activity.

When you talk to experts in this space, they’ll tell you that the amount of power needed, specifically the power density, is staggering. One of those experts, Tim Phillips, President, CEO, and Founder of Empower Semiconductor, joined me on this week’s Embedded Executives podcast. He gave some insight into what we need to do to handle the power (and associated heat) issue.

Nordic Semiconductor is certainly one of the leaders in the embedded space regarding microcontroller technology. Frankly, I feel like the company is one of the best-kept secrets. When I had the opportunity to speak with their (sort of) new CEO, I jumped at it.

Hear my discussion with Vegard Wollan, Nordic’s President and CEO, where he explains some of the moves he has made in his tenure, and what can be expected going forward, on this week’s Embedded Executives podcast.

Some “experts” in the embedded space will swear that systems based on open-source software or hardware can never be secure. At the same time, others will say that such a notion is pure nonsense.

To get a better feel for the argument and understand what is accurate and what is not, I spoke to Jan Pleskac, the Co-Founder and CTO of Tropic Square, on this week’s Embedded Executives podcast.

The company is a fabless semiconductor vendor that specializes in secure elements. Jan and I went through the process behind staying secure and the role that open source plays in it.

In a typical SoC, you handle all your processing functionality within the processor core. Makes sense, right? What if you can handle your processing within the SoC’s memory subsystem? If I understand the concept correctly, the time and power to handle those processing functions would be reduced considerably, which is needed in an AI application. So why hasn’t someone done this?

Someone has, and that would be PIMIC. To learn what this means and how it works, I spoke to Subi Krishnamurthy, the Founder and CEO of PIMIC, on this week’s Embedded Executives podcast.

Functional safety is no longer a “nice to have” or “should have” in many applications, having moved to “must have” in spaces like automotive, industrial automation, medical devices, and aviation.

Passing the functional safety testing process can be rigorous, especially if you’re going through it for the first time. But even the best experts take at least six months to get software certified.

To understand exactly what functional safety is, what the testing process is like, and how and when a developer should get started, I spoke to Bill Lamie, the President and CEO of PX5 RTOS, and someone who’s been through the rigors of functional safety testing on this week’s Embedded Executives podcast.

In programming jargon, the term “real time” is not used in its literal sense, which can be confusing. The literal definition means that when something happens in real time, it happens instantaneously. But in practice, something that occurs very quickly is mistitled as being real-time. Why does the misconception continue to occur, and what problems does it cause? This is the beginning of the discussion I had with Steve Graves, the Founder and CEO of McObject, on this week’s Embedded Executives podcast. Steve has to deal with this issue regularly, so his opinions are quite valid.