You are here: / Automotive ASICs

Want to see how fast autonomous vehicle ASICs have improved, look no further than the California disengagement data

Back in 2019 we looked at the California disengagement data as part of look at the challenge self-driving cars faced over the coming years. There was a lot of variation in success with Google’s Waymo (please excuse the pun) way out in front with 11,018 miles on average per disengagement (ie the test driver grabbing the steering wheel).

 

As automotive ASICs play a crucial role in the decisions the car makes, we thought we’d take a look at the improvement since then.

It is impressive.

 

 

The leading AV system maker (now GM/Cruise) made travelled 863,111 miles with only 9 (nine) disenagements. Adding to the impressiveness, 8 of these were to prevent an accident caused by other drivers, and just one incidence where a “Precautionary takeover to address planning; lane keeping” was made.

 

And yes, like 2019, there are huge levels of variation between the disengagement rates of the system developers, there have been huge improvements all round.

Waymo is now at 17,060 miles per disengagement.

Zoox has gone from 1923 miles to 26,292 miles per

disengagement. The full data is below, with graphs showing

1) Miles per disengagement for all autonomous vehicle system developers and types of fault*

 

2) A breakdown showing the proportion of each class disengagement**

EnSilica to supply beamforming SatCom ICs to Germany’s VITES to enable power- and cost-efficient flat panel terminals for NGSO-constellations

Focus on connectivity systems for moving vehicles. Initial applications include commercial and government land-based vehicles

  

EnSilica (AIM: ENSI), a leading turnkey supplier of mixed signal ASICs and SoCs, has announced it is to supply VITES with a new beamformer chip for satellite user terminals. VITES will use the chip at the heart of its new ViSAT-Ka-band terminal.

EnSilica’s beam-forming chip is optimised to enable VITES’s creation of power- and cost-efficient ground-based flat panel user terminals for satellite communication systems that can be used across a range of fixed and SatCom on the move (SOTM) applications.VITES specialises in broadband wireless systems for professional applications and has been delivering flat panel terminals based on its own phased array technology since 2019.

Its new ViSAT-Ka-band terminal is intended to be integrated into vehicles for Communications-on-the Move applications. As such it is able to track the movement of low earth orbit (LEO) and other non geo synchronous (NGSO) satellites and allows users to access high-speed connectivity anywhere on the planet while the vehicle is moving.

ViSAT-Ka uses an innovative scalable architecture that enables extremely power efficient TDD and FDD terminals at affordable prices. On this advanced technical base, VITES is developing terminals for both land-based and maritime vehicles of any kind, including for cost and power sensitive automotive applications.

This means that vehicles can access “Always on” broadband connections outside of 4G / 5G network coverage areas, with high throughput, and in an ultra-compact form factor that allows for both retro and line fitting.

Paul Morris, VP of the RF and communications business unit at EnSilica commented:

“EnSilica has been investing in this area for several years working closely with the UK Space Agency, European Space Agency and VITES GmbH. VITES have provided clear terminal requirements so we have been able to optimise our solution for the market. This beamformer chip can be paired with a range of Ka- and Ku-band RFICs including our own EN92030 allowing it to cover the various LEO or GEO constellations. “ 

Martin Gassner, CEO of VITES said:

“For the upcoming NGSO-constellations, quantum leap solutions are required in order to drive performance up, while driving cost and power consumption down. Our new ViSAT-Ka-Band terminals are the solution to these challenges. We’re delighted to be partnering with EnSilica and working closely with them on leading SOTM solutions that are delivering broadband connectivity even when there is no access to terrestrial networks.”

 

 Fig 1) The ViSAT-Ka-band terminal is intended to be integrated into vehicles for Communications-on-the Move.

       

Fig 2) Map showing 4G and 5G coverage in US and Germany, with significant areas not served by any operator. Copyright nPerf

For further information please contact:

 

EnSilica plc

Ian Lankshear, Chief Executive Officer

www.ensilica.com

 Via Vigo Consulting

+44 (0)20 7390 0233
 

VITES GmbH

Martin Gassner, Chief Executive Officer

www.vites.de

 

  

+49 (0)89 6088 4600

info@VITES.DE
Sonus PR (Technology Public Relations)

Rob Ashwell

 +44 (0)7800 515 001 ensilica@sonuspr.com.com

 

About EnSilica

EnSilica is a leading fabless design house focused on custom ASIC design and supply for OEMs and system houses, as well as IC design services for companies with their own design teams. The company has world-class expertise in supplying custom RF, mmWave, mixed signal and digital ICs to its international customers in the automotive, industrial, healthcare and communications markets. The company also offers a broad portfolio of core IP covering cryptography, radar, and communications systems. EnSilica has a track record of delivering high quality solutions to demanding industry standards. The company is headquartered near Oxford, UK and has design centres across the UK, in Bangalore, India and in Port Alegre, Brazil.

 

About VITES

VITES GmbH (“VITES”) is an innovative German supplier of high-performance broadband wireless systems and customized solutions for professional applications. Main focus is the development of FPA-terminals for SATCOM-on-the-Move applications. These terminals are based on a power efficient active phased array technology, appropriate for any kind of vehicle, including governmental as well as commercial use.

In the areas of public safety, security and disaster management, VITES offers nomadic LTE-/5G- (ViCell) as well as broadband IP-Mesh-Networks (ViMesh). The brand vikomobil 2.0 represents complete customer specific mobile communication nodes (“cell on wheels”) that are energy autonomous and integrate SATCOM.

EnSilica und VITES kooperieren bei der Chipsatz-Entwicklung zur Realisierung energie- und kosteneffizienter Flat-Panel-Terminals für NGSO-Konstellationen

Fokus auf breitbandige SATCOM-Datenanbindung während der Fahrt. Erste Anwendungen umfassen kommerzielle Fahrzeuge und solche der Sicherheitsbehörden

  

EnSilica (AIM: ENSI), ein führender Anbieter von Mixed-Signal-ASICs und SoCs, gibt bekannt, die VITES GmbH mit einem neuen Beamforming-Chipsatz (elektronische Funkstrahl-Formung) für Satelliten-User-Terminals zu beliefern. VITES wird die ASIC-Entwicklung maßgeblich begleiten und den Chipsatz in seinen neuen ViSAT-Ka-Band-Terminals einsetzen.

 

Der Beamforming-Chipsatz von EnSilica ist daraufhin optimiert, energie- und kosteneffiziente, bodengestützte Flat-Panel-User-Terminals für Satellitenkommunikationssysteme realisieren zu können, die sich für ortsfeste SATCOM- und mobile SATCOM-on-the-Move-/Communications-on-the-Move Anwendungen eignen.

VITES ist auf Breitband-Funksysteme für professionelle Anwendungen spezialisiert und liefert seit 2019 Flat-Panel-Terminals auf Basis einer eigenen Phased-Array-Technologie.

Integriert in Fahrzeuge, ermöglicht das neue ViSAT-Ka-Band-Terminal der VITES die Konnektivität mit Satelliten während der Fahrt (Communications-on-the-Move, COTM). Das Terminal ist in der Lage, den Funkstrahl vollelektronisch auf die Bewegung von erdnahen Satelliten (LEO, Low Earth Orbit) und anderen nicht geosynchronen Satelliten (NGSO) nachzuführen. Nutzer erhalten damit einen schnellen Netzwerkzugang überall auf der Welt, auch während der Fahrt.

ViSAT-Ka basiert auf einer skalierbaren Architektur, die sehr energieeffiziente TDD- und FDD-Terminals zu erschwinglichen Preisen ermöglicht. Auf dieser fortschrittlichen technischen Basis entwickelt VITES Terminals für Land- und Seefahrzeuge aller Art – auch für kostensensitive Automotive-Anwendungen, die zudem eine sehr geringe Verlustleistung erfordern.

Mit dieser Technologie haben Fahrzeuge auch außerhalb der 4G-/5G-Netzabdeckung Zugang zu „Always-on“-Breitbandverbindungen mit hohem Durchsatz – und das in einer sehr flachen, kompakten Formgebung, die sich gleichermaßen für Nachrüstungen, als auch für die Fahrzeug-Erstausrüstung ab Werk eignet.

Paul Morris, VP der RF and Communications Business Unit bei EnSilica, dazu:

„EnSilica investiert seit mehreren Jahren in diesen Bereich und arbeitet eng mit der UK Space Agency, der European Space Agency und der VITES GmbH zusammen. VITES hat klare Anforderungen für die Beamforming-Chips geliefert, so dass wir unsere Lösung für den Markt optimieren konnten. Der Chipsatz lässt sich mit Ka- und Ku-Band-RFICs kombinieren, einschließlich unserem EN92030 Ka-band-Chip, so dass er die verschiedenen LEO- oder GEO-Konstellationen abdeckt.“ 

Martin Gassner, CEO von VITES, fügte hinzu:

„Für die kommenden NGSO-Konstellationen sind Terminals erforderlich, die in Bezug auf Performance, Energieeffizienz und Herstellungskosten einen Quantensprung darstellen. Diese Anforderungen erfüllen wir mit unseren neuen ViSAT-Ka-Band-Terminals. Wir freuen uns über die Partnerschaft mit EnSilica und die Zusammenarbeit bei der Entwicklung von COTM-Lösungen, die Breitbandverbindungen auch dort ermöglichen, wo es keinen Zugang zu terrestrischen Netzen gibt.“

Bild 1: Das ViSAT-Ka-Band-Terminal misst je nach Version zwischen ca. 16 x 10 cm und 50 x 30 cm und ist für den Einbau in Fahrzeuge für Communications-on-the-Move vorgesehen

       

Bild 2: 4G- und 5G-Abdeckung in Deutschland, wobei wesentliche Gebiete von keinem Betreiber versorgt werden (Quelle: nPerf).

Kontakt für weitere Informationen:

 

EnSilica plc

Ian Lankshear, Chief Executive Officer

www.ensilica.com

 Via Vigo Consulting

+44 (0)20 7390 0233
 

VITES GmbH

Martin Gassner, Chief Executive Officer

www.vites.de

 

  

+49 (0)89 6088 4600

info@VITES.DE
Sonus PR (Technology Public Relations)

Rob Ashwell

 +44 (0)7800 515 001 ensilica@sonuspr.com.com

 

Über EnSilica

EnSilica ist ein führendes Fabless-Design-Unternehmen, das sich auf kundenspezifisches ASIC-Design für Erstausrüster (OEMs) und Systemhäuser sowie auf IC-Designdienstleistungen für Firmen mit eigener IC-Entwicklung konzentriert. Das Unternehmen besitzt erstrangige Erfahrungen in der Entwicklung kundenspezifischer HF-, mmWave-, Mixed-Signal- und Digital-ICs für internationale Kunden in den Bereichen Automotive, Industrie, Gesundheitswesen und Kommunikation. Darüber hinaus bietet das Unternehmen ein breites Spektrum an Kern-IP für Kryptographie, Radar und Kommunikationssysteme. EnSilica hat umfangreiche Erfahrung in der Lieferung qualitativ hochwertiger Dienstleistungen, die anspruchsvolle Industrienormen erfüllen. Das Unternehmen hat seinen Hauptsitz in der Nähe von Oxford, Großbritannien, und verfügt über Entwicklungszentren in ganz Großbritannien, in Bangalore, Indien, und in Port Alegre, Brasilien.

Über VITES

Die VITES GmbH („VITES“) ist ein innovativer deutscher Anbieter hochleistungsfähiger Breitband-Funksysteme und kundenspezifischer Lösungen für professionelle Anwendungen. Der Schwerpunkt liegt auf der Entwicklung von Flat-Panel-Terminals für Communications-on-the-Move-Anwendungen. Diese Terminals basieren auf einer energieeffizienten aktiven Phased-Array-Technologie, die für jede Art von Fahrzeugen geeignet ist, sowohl für den kommerziellen Einsatz als auch bei Sicherheitsbehörden.

Im Bereich öffentliche Sicherheit und Katastrophenschutz bietet VITES nomadische LTE-/5G- (ViCell) als auch breitbandige IP-Mesh-Netze (ViMesh) an. Die Marke vikomobil 2.0 steht für mobile energieautarke Mobilfunkknoten („Mobilfunkzelle auf Rädern“) die zusätzlich SATCOM integrieren.

ensilica custom asic banner

How to write an ASIC design specification well – Part 3

This is a 3 part blog. If you missed it, click here to read part 1 and part 2.

The 7 Most Common Mistakes and How To Avoid Them

The first step in developing a new ASIC for any function – be it a wireless chip for a wearable healthcare sensor device, an autonomous vehicle ASIC, or a communications system for a satellite – is the specification.

To ensure the product you need is produced, is done so on time and on budget, and that errors aren’t introduced that could require a recall, the specification has to be written clearly and concisely.

In this, the final part, we look at the most common mistakes and how to avoid them.

1) Loose language

The language used in the document matters. It can add clarity, and it can add ambiguity.
For example, there is a big difference between ‘shall’ (expresses a requirement), ‘will’ (makes a statement of fact), and ‘should’ (expresses an aspiration).

2) Not being concise

Requirements should be as concise as possible, and broken down into individual items to give full clarity when reporting compliance during the development.
For example, it is better to say, “The product must do X” and “The product should do Y” versus “The product must do X and should do Y”.

3) Missing information

Any aspect of the product’s functionality that is missing from the requirements will not make it to specification document. And, therefore, will be missing in the product.

4) Lacking rationales

Rationales should be added for each requirement where appropriate.
But note, these should not be extensions of the requirement. And compliance will be determined against the requirement, not the rationale.

5) How vs what

The requirements describe what the product must do rather than how it must provide that functionality.

6) Including non-essential functionality

If something is not essential for the intended product functionality, then it should not be a requirement.

7) Lacking measurability

Requirements should be clear and unambiguous, and terminologies or expressions that are not verifiable should be avoided all costs.

This means subjective statements like “The product must be low power” should be defined to say “The product must consume less than X”.

And for reporting compliance, there must be a way to uniquely identify each requirement. This enables compliance reports to make clear statements such as “Specification S.17 addresses requirement R.49”.

Getting a specification wrong can be catastrophic. By following these seven tips you’ll be well-placed to get it right first time.

If you want to find out more about how EnSilica can help, click here.

How to write an ASIC design specification well – Part 2

This is a 3 part blog. If you missed it, click here to read part 1.

Who Is The Specification For

The first step in developing a new ASIC for any function – be it a wireless chip for a wearable healthcare sensor device, an autonomous vehicle ASIC, or a communications system for a satellite – is the specification.

To ensure the product you need is produced, is done so on time and on budget, and that errors aren’t introduced that could require a recall, the specification has to be written clearly and concisely.
In this, the second of three blogs on the topic, we look at the audiences for needs the specification and the information they need.

“The specification can (and does) act as the communication channel, helping information to flow.”

Who reads it?

There are two audiences.

1) Your internal system development team. If they lack understanding or agreement of the product’s definition, there’s little chance that the development team can successfully deliver what is required.

2) Our development team. Because it’s natural and common for individual members in a development team to read the sections of the specification focused on their tasks… and only these sections, the specification document allows a development team to be structured correctly and the right skill sets brought together to get it right first time.

Potential pitfalls

However, the specification document does not act as a panacea to magically resolve poor communication between customer and supplier. Nor will it fix potential communication problems between people within a development team, however it can (and does) act as the communication channel, helping information to flow.

If you want to find out more about how EnSilica can help, click here.

Click here to read part 1 and part 3.

How to write an ASIC design specification well – Part 1

The Purpose Of The Specification

The first step in developing a new ASIC for any function – be it a wireless chip for a wearable healthcare sensor device, an autonomous vehicle ASIC, or a communications system for a satellite – is the specification.

To ensure the product you need is produced, is done so on time and on budget, and that errors aren’t introduced that could require a recall, the specification has to be written clearly and concisely.
In this, the first of three blogs on the topic, we look at the purpose of the specification to help you avoid some of the most common mistakes.

“One common misconception is that the specification can serve as a datasheet or user manual. It cannot and does not.”

The specification’s purpose

To get it designs right first time, it is crucial to clearly define the required functionality and behaviours that the product must possess; and the specification is there to define these. And to also state that any functionality that is explicitly not required.

Who writes it

Typically, the engineering team generates the specification in collaboration with the end customer. It will be based on a requirements document, which will be provided by the customer.

What the document enables

Instead, the primary role of a specification is to unambiguously set out the customer’s requirements. With each customer requirement directly or indirectly addressed by the functionality defined in the specification.

There should be a clear mapping, (one-to-one / one-to-many), between each customer requirement and each function defined in the specification.

What it should not be used for

One common misconception is that the specification can serve as a datasheet or user manual. It cannot and does not.

What happens once it’s written

Once written, it is essential for the customer and development team to thoroughly review and approve the specification and ensure it adequately meets each requirement.

Additionally, the compliance report prepared by the development team should be reviewed and approved by the customer to make sure everything has been interpreted correctly.

If you want to find out more about how EnSilica can help, click here.

Click here to read part 2 and part 3.

Automotive ASICs and the functional safety standard ISO 26262

Over the past 20 years EnSilica has developed ASICs for several major automotive OEMs and tier-1 suppliers, based both here in the UK and in Europe and the US and these mixed-signal chips have controlled and enabled several functions from power management to ride comfort and, with all of these chips, a series of trade-offs are therefore balanced to achieve the right performance, cost, size, power etc.

Functional safety is obviously a core part of all of these and so, when looking for articles on ISO 26262 in, I recently re-stumbled upon an article written by our head of functional safety, Enrique Martinez, and after reading was glad we only deal with these technical trade-offs for vehicles, and not with the moral dilemmas.

In his article, published in EDN, he cites a 2018 Nature paper on the moral imperatives relating to decisions made by autonomous vehicles and how these vary region by region.

While the paper is, in effect, re-running the old runaway tramcar thought experiment, the differences in who gets protected are quite stark.

For example, Eastern cultures are more likely to protect the old, Southern cultures prefer inaction over purposeful selection, Western ones more likely to protect people of status over vulnerable users like pedestrians (thankfully this last one would be nigh-on impossible to code).

Considerations in developing safety critical SoCs

As mentioned, the article also looks at ISO 26262 and IEC 61508 and is well worth a read, and a summary can be found below:

As Enrique argues: Safety-critical projects require comprehensive safety analysis procedures. And a pivotal role in this process is played by the designer, establishing an understanding of potential malfunctions within a circuit or IP block and implementing mitigation strategies.

To make sure safety measures work, ISO 26262 also mandates that complex SoCs use specialised fault injection software tools to simulate common faults and ensure proper detection and/or correction mechanisms are in place.

Debugging embedded software is never easy, and challenges are further amplified when the code image is in the silicon itself (so traditional debugging tools become less effective /practical). The way around this is by running co-simulation models that encompass both hardware and software, and that give a comprehensive view of the system’s behaviour, even before you get your hands on the silicon itself.

The final key element in creating safety-critical systems is vendor verification, with any device used in applications governed by ISO 26262 needing fabs and subcontractors to demonstrate their ability to manufacture components to automotive safety standards. This means a communication flow with suppliers and customers that strictly adheres to safety plans and development interface agreements (DIA) is essential.

If you need more information than this short summary allows, you can read Enrique’s original article on EDN, here.