Arteris Articles

Semiconductor Engineering: Privacy Protection A Must For Driver Monitoring

Kurt Shuler, Vice President of Marketing at Arteris IP is quoted in this new Semiconductor Engineering article:

Privacy Protection A Must For Driver Monitoring 

April 1st, 2021 - By Ann Steffora Mutschler

Why driver data collected by in-cabin monitoring systems must be included as part of the overall security system.

Privacy and security has to be addressed at every layer, by all parties, said Kurt Shuler, vice president of marketing at Arteris IP. “We’re getting questions from customers asking, ‘You’ve got this interconnect, it’s a network, you have these firewalls, how do I integrate this into my overall security system for my chip?’ They also want to know how to integrate that in the overall security system of that vehicle subsystem, and how to integrate that into the overall security system for the car, and then the network of cars. If I’m GM, I’ve got a whole network of GM cars running around. Where there’s OnStar, I have to protect that data too, and that’s sitting on servers. The OEM is cognizant of this because they know from market forces that if they screw it up, then people aren’t going to trust them. And even though there are IEEE, ISO, and SAE standards, selling security is like selling insurance. Nobody thinks they need it until after the incident happened. The risk is huge here if you don’t do it right, so you should do everything state of the art. However, there’s nothing currently legally forcing that.”

Topics: SoC NoC functional safety ISO 26262 network-on-chip automotive IEEE semiconductor engineering arteris ip interconnects OEMs security driver monitoring

Semiconductor Engineering: Learning ISO 26262 - 2nd Edition

Kurt Shuler, Vice President of Marketing at Arteris IP authored this new article on the interpretation of ISO 26262 in today's Semiconductor Engineering blog:

Learning ISO 26262 -2nd Edition 

December 7th, 2020 - By Kurt Shuler

Interpreting the functional safety standard isn't as simple as just looking at the document.

Ambiguity is a feature, not a bug!

Why? Partly ambiguity. Because what I think is clear, you may not think is clear. And some of this ambiguity is intentional: This is a voluntary (thought widely followed) standard, aiming to preserve flexibility for innovation and differentiation. The committees don't want to be too prescriptive, which inevitably leads to some ambiguity.

Topics: SoC NoC functional safety ISO 26262 automotive semiconductor engineering Soft IP FMEA kurt shuler OEMs FMEDA noc interconnect IP market Part 11 tailoring safety element standards SEooC

SemiWiki: The Reality of ISO 26262 Interpretation. Experience Matters.

Kurt Shuler, vice president at Arteris IP talks with Bernard Murphy about the complexities of interpreting the ISO 26262 standard new SemiWiki blog:

The Reality of ISO 26262 Interpretation. Experience Matters

November 30, 2020 - Bernard Murphy

Interpreting ISO 26262 without ambiguity is not always easy. Suppliers and integrators can read some aspects differently, creating confusion. Which is a problem since ISO 26262 has become so much a part of any discussion on automotive electronics that it has gained almost biblical significance. Yet most of us, even suppliers to the market, understand at best only what they have read in the document. I had a fascinating discussion with Kurt Shuler (VP Marketing at Arteris IP) on the background to and challenges in interpretation in the standard. Kurt is a member on the technical advisory group to ISO 26262 and is extensively involved in safety management. It turns out that everything you need to know is not always covered in the official document.

Topics: SoC ISO 26262 network-on-chip semiconductor automotive Ncore FlexNoC semiwiki kurt shuler OEMs noc interconnect Tier 1s 2nd edition ISO 26262

Semiconductor Engineering: The Role Of NoCs In System-Level Services

Kurt Shuler, Vice President of Marketing at Arteris IP authored this new article in Semiconductor Engineering:

The Role Of NoCs In System-Level Services

September 8th, 2020 - By Kurt Shuler

The central nervous system of SoCs is expanding to help manage things like QoS and performance.

The primary objective of any network-on-chip (NoC) interconnect is to move data around a chip as efficiently as possible with as little impact as possible on design closure while meeting or exceeding key design metrics (PPA, etc.). These networks have become the central nervous system of SoCs and are starting to play a larger role in system-level services like quality of service (QoS), debug, performance analysis, safety and security because these on-chip interconnects transport and “see” most if not all of the of the on-chip dataflow. Think of the NoC as the SoC’s “all seeing eye” and you’ll have a better understanding of what is technically possible.
Topics: SoC NoC ISO 26262 SoC QoS automotive semiconductor engineering soc architecture ASIL D kurt shuler QoS noc interconnect IP market