05.03.2013 Views

Xcell Journal Issue 78: Charge to Market with Xilinx 7 Series ...

Xcell Journal Issue 78: Charge to Market with Xilinx 7 Series ...

Xcell Journal Issue 78: Charge to Market with Xilinx 7 Series ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

XCELLENCE IN AUTOMOTIVE APPLICATIONS<br />

that case, it is possible <strong>to</strong> configure<br />

only a minimalist subsystem at<br />

power-up (that is, the bootloader and<br />

the portion of the system application<br />

immediately required) and keep the<br />

rest of the system idle until it is necessary<br />

<strong>to</strong> initialize it. Splitting this<br />

startup activity in<strong>to</strong> two phases<br />

speeds up the initialization process<br />

in case the system needs a fast<br />

response at power-up or upon waking.<br />

For this purpose, the system<br />

architecture is decomposed in<strong>to</strong> a<br />

static region and one or more partially<br />

reconfigurable regions (PRRs).<br />

The static region encompasses the<br />

system responsible for carrying out the<br />

startup process, typically the host<br />

CPU, along <strong>with</strong> the reconfiguration<br />

engine and a data link <strong>to</strong> the bitstream<br />

reposi<strong>to</strong>ry. The other regions are<br />

described by specific partial bitstreams<br />

that can be downloaded later,<br />

when the application needs them.<br />

Also, if PRR regions are disabled, then<br />

it is possible <strong>to</strong> reduce the power consumption<br />

of the device proportionally <strong>to</strong><br />

the portion of area that is not in use.<br />

Power-saving modes are especially relevant<br />

in au<strong>to</strong>motive battery-powered<br />

ECUs. For this reason, au<strong>to</strong>motive MCUs<br />

make use of low-power modes <strong>to</strong> keep<br />

TWO CRUCIAL STANDARDS<br />

The au<strong>to</strong>motive industry is already designing electronics<br />

<strong>with</strong> two crucial standards in mind:<br />

AUTOSAR, for handling embedded-system complexity<br />

by means of appropriate software and hardware<br />

architectures, and the upcoming ISO 26262, which governs<br />

functional safety. Relevant technical concerns adopted<br />

from ISO 26262 and released in AUTOSAR include the<br />

detection and handling of safety issues like hardware<br />

faults at runtime; abnormal timing and the broken logical<br />

order of execution of applications; and data corruption,<br />

among others.<br />

INSIDE AUTOSAR<br />

In recent years, electronic components have displaced<br />

mechanical and hydraulic systems <strong>with</strong>in vehicles. The<br />

incursions continue, as designers begin <strong>to</strong> implement<br />

additional control, moni<strong>to</strong>ring and diagnostic functions in<br />

software. In fact, electronics technology makes it possible<br />

<strong>to</strong> deliver new functions whose development would be<br />

costly or not feasible if using only mechanical and<br />

hydraulic solutions. These parts must meet stringent safety<br />

requirements <strong>to</strong> avoid faulty states and failures.<br />

While software-related product failures have so far<br />

been relatively rare, continued growth in the use of software<br />

as part of manufactured products increases the system<br />

complexity and, <strong>to</strong>gether <strong>with</strong> shorter product development<br />

cycles, leads in the end <strong>to</strong> product failures. The<br />

au<strong>to</strong>motive industry has attacked this problem by forming<br />

coalitions and enacting standards <strong>to</strong> ensure the application<br />

and creation of safe and reliable software.<br />

The Mo<strong>to</strong>r Industry Software Reliability Association<br />

(MISRA), for example, is a consortium of vehicle manufacturers<br />

such as Ford and Jaguar Land Rover, component<br />

suppliers and engineering consultancies. By defining a<br />

the ECU power consumption <strong>to</strong> a minimum<br />

when the vehicle is inactive (that<br />

is, in sleep mode). Analogously, the use<br />

of blank bitstreams <strong>to</strong> disable portions<br />

of the FPGA when not required reduces<br />

logic activity and consequently, dynamic<br />

power consumption.<br />

Au<strong>to</strong>motive designers can also use a<br />

technique inherited from aerospace<br />

applications in systems based on runtime<br />

reconfigurable logic. Configuration<br />

scrubbing can recover the system from<br />

failures on SRAM resources originated<br />

by SEU or electromagnetic interference.<br />

Periodically reconfiguring the<br />

hardware peripherals guarantees that<br />

series of software programming rules, MISRA seeks <strong>to</strong> promote<br />

best practices in developing safety-related electronic<br />

systems in road vehicles and other embedded systems.<br />

The Au<strong>to</strong>motive Open System Architecture, or<br />

AUTOSAR, is a partnership of au<strong>to</strong>motive manufacturers,<br />

suppliers and other companies from the electronics, semiconduc<strong>to</strong>r<br />

and software industries working <strong>to</strong>gether <strong>to</strong><br />

develop a de fac<strong>to</strong> open industry standard for au<strong>to</strong>motive<br />

electrical/electronic (E/E) architectures, targeting several<br />

major issues. These include managing the growing complexity<br />

of au<strong>to</strong>motive E/E systems associated <strong>with</strong> the continuous<br />

increase of functionality; improving flexibility for product<br />

modification, upgrade and update; improving scalability<br />

of solutions <strong>with</strong>in and across product lines; improving the<br />

quality and reliability of E/E systems; and enabling the<br />

detection of errors in early design phases.<br />

This initiative faces the challenge of having <strong>to</strong> integrate a<br />

growing amount of software and electronic technologies<br />

across a vast ecosystem of suppliers. By simplifying the<br />

exchange and update options for software and hardware, the<br />

AUTOSAR approach forms the basis for reliably controlling the<br />

rising complexity of the E/E systems in mo<strong>to</strong>r vehicles, as well<br />

as improving cost-efficiency <strong>with</strong>out compromising quality.<br />

The AUTOSAR initiative, founded in 2003, is a natural evolution<br />

of the older OSEK/VDX consortium—born one decade<br />

before and spearheaded by some German and French<br />

au<strong>to</strong>makers—but now <strong>with</strong> more ambitious goals and extended<br />

<strong>to</strong> most of the au<strong>to</strong>motive OEMs all over the world.<br />

The core partners of AUTOSAR are the BMW Group,<br />

Bosch, Continental, Daimler, Ford, General Mo<strong>to</strong>rs, PSA<br />

Peugeot Citroën, Toyota and the Volkswagen Group. In addition<br />

<strong>to</strong> these companies, more than 160 other members play<br />

an important role in the success of the partnership. Thus,<br />

under the slogan “cooperate on standards, compete on<br />

28 <strong>Xcell</strong> <strong>Journal</strong> First Quarter 2012

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!