Layout examples

Hello all,

I was wondering if anyone (maybe some of the guru's or Xilinx folk, have
some pictures (jpegs) of some layout examples of various packages and parts.
I have read many app notes about bypass caps, etc. and everything in them
explains how many caps, and values for a good decoupling system, however the
one thing that they all say is get them as close to the pin as possible
(which could mean a lot of different things). For example I'm using the
PQ208 package for the XC2S100 device and I mount all of my bypass caps on
the underside of the PCB, primarily due to the fact that I like to provide a
clean exit route from the IC on the top of the board. The trouble then is
that the more caps you have the more vias you need, the more perforated your
planes become. I hope that you see where I'm going with this.

I would like to see if possible some proven layouts showing where the caps
are mounted and there possition relative to the power pins (and see how
close they are). I've seen a lot of layouts where there are a few caps in
the center of the IC on the underside of the board, but this does not lend
itself nicely to the idea of being as  close as possible to the pins. I have
also seen the Xilinx app note on BGA routing which is very helpful, but
again no capacitor placement is shown.

Can someone post some pictures or email them to me if they feel so inclined
of some design proven layouts. I would greatly appreciate it and I'm sure
that others would as well. Maybe Xilinx could add a few pics to their app
notes in future. As I stated I'm currently using a PQ208 package and since
my desing are progressing I am considering a move to a BGA package. Since
it's a bit risky for the first design I want to see some examples, as well
as examples from other packages available.

Any help would be greatly appreciated.

Thanks,

Jason

jberringerattrace-logicdotcom

Hi Jason,

"Jason Berringer" <look_at_bottom_of@email.com> writes:
<snip>
> I would like to see if possible some proven layouts showing where the caps
> are mounted and there possition relative to the power pins (and see how
> close they are). I've seen a lot of layouts where there are a few caps in
> the center of the IC on the underside of the board, but this does not lend
> itself nicely to the idea of being as  close as possible to the pins. I have
> also seen the Xilinx app note on BGA routing which is very helpful, but
> again no capacitor placement is shown.
> 
<snip>
If you have solid planes (prefereably closely spaced) you don't need
to worry about 'close' in the sense that you probably think of as
close.  If you have vias to the planes on *very* short tracks, or even
better in the pad, then the planes will act as a very low impedance
route for your currents.  If you think of the time the energy will
take to travel from capacitor to chip, the speed of light on FR4 is
around 2/3c or 2e8 m/s.  In 1ns, this is around 20cm.  Halve this for
the energy to get back and forth and even 10cm is "close".

I don't have any pictures to hand, but we've done boards like this
with 100MHz memory interfaces and 150MHz core DSP clocks that work fine.

Does that help?

Cheers,
Martin

-- 
martin.j.thompson@trw.com
TRW Conekt, Solihull, UK
http://www.trw.com/conekt

Great comments, Martin.

A point I'd add to the original poster's concerns about the "swiss cheese"
ground and power planes you can get with too many vias, some numerical work
has shown that - at least for closely spaced ground/power pairs - the added
impedance from the swiss cheese under a BGA package (much worse than a QFP)
is sub-nanohenry.  Don't worry so much about the holes in the plane, worry
about the spacing between the planes (smaller is better, 4 mil perhaps?) and
good decoupling cap attachment.  Two vias are often used on each end of the
decoupling caps in high speed designs to halve the impedance to the ground
and power planes.  The "*very* short tracks" is a noteworthy comment as
well; it's easy to make a stiff decoupling cap a bit soft by adding a little
track between the pad and via(s).

"Martin Thompson" <martin.j.thompson@trw.com> wrote in message
news:uislr3q8a.fsf@trw.com...
> Hi Jason,
>
> "Jason Berringer" <look_at_bottom_of@email.com> writes:
> <snip>
> > I would like to see if possible some proven layouts showing where the
caps
> > are mounted and there possition relative to the power pins (and see how
> > close they are). I've seen a lot of layouts where there are a few caps
in
> > the center of the IC on the underside of the board, but this does not
lend
> > itself nicely to the idea of being as  close as possible to the pins. I
have
> > also seen the Xilinx app note on BGA routing which is very helpful, but
> > again no capacitor placement is shown.
> >
> <snip>
> If you have solid planes (prefereably closely spaced) you don't need
> to worry about 'close' in the sense that you probably think of as
> close.  If you have vias to the planes on *very* short tracks, or even
> better in the pad, then the planes will act as a very low impedance
> route for your currents.  If you think of the time the energy will
> take to travel from capacitor to chip, the speed of light on FR4 is
> around 2/3c or 2e8 m/s.  In 1ns, this is around 20cm.  Halve this for
> the energy to get back and forth and even 10cm is "close".
>
> I don't have any pictures to hand, but we've done boards like this
> with 100MHz memory interfaces and 150MHz core DSP clocks that work fine.
>
> Does that help?
>
> Cheers,
> Martin
>
> -- 
> martin.j.thompson@trw.com
> TRW Conekt, Solihull, UK
> http://www.trw.com/conekt

"John_H" <johnhandwork@mail.com> wrote in message
news:mt8sb.12$SZ3.1981@news-west.eli.net...
[...]
> The "*very* short tracks" is a noteworthy comment as
> well; it's easy to make a stiff decoupling cap a bit soft by adding a
little
> track between the pad and via(s).

Showing my age here....  when I was routinely designing PCBs
around 8-10 years ago, I was often given a very hard time by
assembly subcontractors if I put vias inside an SMD pad - they
used to complain about solder hogging or some such manufacturing
folklore.  What are the up-to-date design rules for putting vias
in or very close to a pad?

TIA
--
Jonathan Bromley, Consultant

DOULOS - Developing Design Know-how
VHDL * Verilog * SystemC * Perl * Tcl/Tk * Verification * Project Services

Doulos Ltd. Church Hatch, 22 Market Place, Ringwood, Hampshire, BH24 1AW, UK
Tel: +44 (0)1425 471223                    mail: jonathan.bromley@doulos.com
Fax: +44 (0)1425 471573                           Web: http://www.doulos.com

The contents of this message may contain personal views which
are not the views of Doulos Ltd., unless specifically stated.

"Filled Vias" are a process that your raw-board vendor may support and are
necessary for in-the-pad vias.  You're still right in that unfilled vias in
the pad act as solder theifs.  Micro-vias (a form of blind via) are even
better at giving exceptionally low impedance without acting as a sloder
theif but the cost and tool support art two things I'd worry about.  Chances
are you'll stick with regular vias and get the spacing particulars
(capacitor pad to via minimum spacing) from your board assembly house or
someone else intimately familiar with the IPC recommendations.

It wouldn't be a good thing to just stick those vias in the pads or a
solder-flow away from the pad to act as a nice drain for the solder.  These
details get lost on those of us who have it ingrained upon us that the
minimum spacing shall never be violated.  Thanks for keeping the details
alive.

"Jonathan Bromley" <jonathan.bromley@doulos.com> wrote in message
news:bor6c5$je3$1$8300dec7@news.demon.co.uk...
> "John_H" <johnhandwork@mail.com> wrote in message
> news:mt8sb.12$SZ3.1981@news-west.eli.net...
> [...]
> > The "*very* short tracks" is a noteworthy comment as
> > well; it's easy to make a stiff decoupling cap a bit soft by adding a
> little
> > track between the pad and via(s).
>
> Showing my age here....  when I was routinely designing PCBs
> around 8-10 years ago, I was often given a very hard time by
> assembly subcontractors if I put vias inside an SMD pad - they
> used to complain about solder hogging or some such manufacturing
> folklore.  What are the up-to-date design rules for putting vias
> in or very close to a pad?
>
> TIA
> --
> Jonathan Bromley, Consultant
>
> DOULOS - Developing Design Know-how
> VHDL * Verilog * SystemC * Perl * Tcl/Tk * Verification * Project Services
>
> Doulos Ltd. Church Hatch, 22 Market Place, Ringwood, Hampshire, BH24 1AW,
UK
> Tel: +44 (0)1425 471223                    mail:
jonathan.bromley@doulos.com
> Fax: +44 (0)1425 471573                           Web:
http://www.doulos.com
>
> The contents of this message may contain personal views which
> are not the views of Doulos Ltd., unless specifically stated.
>
>
>
>

>Showing my age here....  when I was routinely designing PCBs
>around 8-10 years ago, I was often given a very hard time by
>assembly subcontractors if I put vias inside an SMD pad - they
>used to complain about solder hogging or some such manufacturing
>folklore.  What are the up-to-date design rules for putting vias
>in or very close to a pad?

That was the party line many years ago.  The problem is that
the solder dives into the via (surface tension) so you don't
have as much solder left to make contact with the part.

I think it's reasonably common now.  It's another tool in the
struggle to reduce the inductance on bypass caps.

Check with your assembly house.  Sometimes they fudge the
hole size in the stencil for the solder paste, or use a
thicker sheet to make the stencil.

-- 
The suespammers.org mail server is located in California.  So are all my
other mailboxes.  Please do not send unsolicited bulk e-mail or unsolicited
commercial e-mail to my suespammers.org address or any of my other addresses.
These are my opinions, not necessarily my employer's.  I hate spam.

"John_H" <johnhandwork@mail.com> writes:

> Great comments, Martin.
> 

Thanks!

> A point I'd add to the original poster's concerns about the "swiss cheese"
> ground and power planes you can get with too many vias, some numerical work
> has shown that - at least for closely spaced ground/power pairs - the added
> impedance from the swiss cheese under a BGA package (much worse than a QFP)
> is sub-nanohenry.  Don't worry so much about the holes in the plane, worry
> about the spacing between the planes (smaller is better, 4 mil perhaps?) and
> good decoupling cap attachment.  Two vias are often used on each end of the
> decoupling caps in high speed designs to halve the impedance to the ground
> and power planes.  The "*very* short tracks" is a noteworthy comment as
> well; it's easy to make a stiff decoupling cap a bit soft by adding a little
> track between the pad and via(s).
> 

Another trick I used that I forgot to mention is to populate groups of
caps in a line with one large "pad" connecting them all.  Through that
pad go 2-3 vias per capacitor to reduce inductance.  However, as the
illustrious Lee Ritchey would point out I have no science to back up
any claim that this is a "good" way of doing things... it feels
right.  At some point I intend to do some simulation and maybe even
(gasp!) some measurements...

Cheers,
Martin

-- 
martin.j.thompson@trw.com
TRW Conekt, Solihull, UK
http://www.trw.com/conekt

> A point I'd add to the original poster's concerns about the "swiss cheese"
> ground and power planes you can get with too many vias, some numerical
work
> has shown that - at least for closely spaced ground/power pairs - the
added
> impedance from the swiss cheese under a BGA package (much worse than a
QFP)
> is sub-nanohenry.  Don't worry so much about the holes in the plane,

Although watch out for accidentally created slots in the ground plane.

If you're not sharing vias for decouplers to keep impedances down and you've
a lot of them you can end up creating slots in the ground plane if you've
many of them near each other. This can be easily done if your decouplers are
neatly arranged on the same X/Y coordinates per side.

Slots are very bad news for high speed signals.

Just something to be aware of.


Nial
------------------------------------------------
Nial Stewart Developments Ltd
FPGA and High Speed Digital Design
www.nialstewartdevelopments.co.uk

"Martin Thompson" wrote:

> If you have solid planes (prefereably closely spaced) you don't need
> to worry about 'close' in the sense that you probably think of as
> close.  If you have vias to the planes on *very* short tracks, or even
> better in the pad, then the planes will act as a very low impedance
> route for your currents.  If you think of the time the energy will
> take to travel from capacitor to chip, the speed of light on FR4 is
> around 2/3c or 2e8 m/s.  In 1ns, this is around 20cm.  Halve this for
> the energy to get back and forth and even 10cm is "close".
>
> I don't have any pictures to hand, but we've done boards like this
> with 100MHz memory interfaces and 150MHz core DSP clocks that work fine.


I'll have to disagree with some of this (not meant as criticism, just a
point for discussion).

The number I use (and see in most books) for propagation in FR4 boards is
140 to
180ps/in for outer traces and about 180ps/in for inner.  That would mean
about 1.4ns/20cm.  Operating at 100MHz with, say, 1ns edges, means that a
cap 10cm away would not be able to deliver significant current for the first
0.7ns of
the edge, which pretty much hoses you.  This is under ideal conditions,
ignoring capacitor frequency-dependant characteristics; mounting-related
inductance; trace/plane inductance; board/pin interface issues, etc.

Because of this and more, I think that 10 to 20cm is far from close (that
sounds funny) for high speed design.  The characteristics of the caps and
the mounting/routing methodology can make this a serious issue.  There are
interesting threads and authorithative information about this very subject
on the signal integrity list.


For my last design truly labored over this and took the approach of writing
a custom power
distribution system simulation tool in order to get a handle on what was
going on.  Things get serious once you stare down at the prospect of
hundreds of pins switching simultaneusly at a given edge rate.  And that's
what's important, the edge rates, not the frequency.  The thinking can be
abstracted to using a bunch of caps (the decoupler array) to charge another
set of caps (the output traces) through the board-to-chip-to-board
interface.

If you start looking at the behavior of capacitors as a function of
frequency (and, in isolation of board layout/mounting effects) you'll see
that the C and L induced self-resonant behavior can play interesting tricks
with what a cap can really do.  Of course ESR and ESL are frequency
depandant themselves, although it is nearly impossible to get this data from
manufacturers.

Beyond that, I find that the field turns "religious" real fast.  There are
three basic approaches:

1- Do it the way we've been doing it 'cause it seems to work
2- Use a range of caps to cover the frequency (ehem, edge) range
3- Use only two or three a couple of values to cover the range
4- If it looks good during layout it should work.

#1 is folklore and may only have merit if a knowledgeable engineer setup
rules conservative rules that can be followed by those working on new
designs independently.  I find that many think that the old 0.1uF capacitor
rules could be adequate for high-speed design when, in reality they are just
about useless.  The same applies to a certain range of tantalums.  So, for
my money, option #1 is not a great solution unless you know where it came
from, how it got there and what the constraints might be.

#2 is promoted by one school of thought within the SI community.  It is
perfectly valid, of course.  However, I don't see it as manufacturing/BOM
friendly.  The idea of stuffing a board with a dozen different decoupling
capacitor values is not something I look forward to from many perspectives.
The theory here is that, by being intelligent about the choice of caps,
their mounting and routing, you create a very low impedance "bucket" to
cover the edge rates for the design.  Like I said, valid, but not my cup of
tea.

#3 is also supported by a sect within the SI community and happens to be
what I chose to do.  The idea here, loosely speaking, is to form the
aforementioned "bucket" with just a few values.  The value of the capacitor
is not as important as the frequency domain characteristics of the same.
This is part of the problem today.  Cap manufacturers are begining to be
pushed by SI experts to address high-speed decoupling needs and produce (and
quantify) caps that are friendlier to this approach.

By dividing the spectrum in to low, mid, mid-high and high frequency (edge
rate) zones you can select four capacitors (again, not so much values as
much as frequency related characteristics) to cover the range.  A typical
setup will have electrolytics by the power source (LF), medium-packaged
tantalums within 5 to 10 cm of relevant chips (MF to HF) and a couple of
small-package chip cap flavors within about 2cm of high-speed chips (HF).
The significance of speaking in terms of packages as opposed to values is
that the package type becomes the primary factor in such properties as ESL
(which is the dominant element as frequencies rise).  Small tantalums, for
example, like 4.7 to 10uF are absolutely worthless for high-speed decoupling
designs.  You have to get into the larger packages in order to get decent
ESR and ESL characteristics.

What attracted me to #3, aside from the obvious BOM-friendly results, was
the fact that you can engineer a much smoother impedance "bucket".  Option
#2 requires very careful design, modeling and simulation to ensure that you
are not creating a real problem or it can produce weird peaky resonant
behavior .  I wasn't equipped nor inclined to do that and #3 made more sense
overall.  What's missing in the decoupling cap world are caps with low ESL
and not so low ESR (or quantifiable ESR).  If you run the curves, you want
some ESR to mitigate peaky resonance effects.

Finally, #4, is included in my list because it was something a
"professional" PCB designer told me when I was considering using his
company's services.  The way this person did high-speed layouts was to "make
it look good and it will work fine".  I would imagine there's a lot of that
going on out there.  I can only wonder and cringe.


To address the OP's questin directly.  There are good guidelines out there
on what is required and many options on how to do it.  Every layout will be
different due to things like the which and how many pins you use.  You need
to get a set of high-speed decouplers very close to the FPGA, within a 2cm
circle, I'd say.  Modern 0402 components allow you to place a good number of
these within the device's footprint.  Fan out from there with mid to low
frequency caps to support charge transfer and avoid starving he HF caps.
Again, quantity and type depend on your design and edge rates.  There are
good books out there that cover the basics.  One such books is "High Speed
Digital Design, a Handbook of Black Magic" by Howard Johnson.


-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Martin Euredjian

To send private email:
0_0_0_0_@pacbell.net
where
"0_0_0_0_"  =  "martineu"

"Martin Euredjian" <0_0_0_0_@pacbell.net> writes:

> "Martin Thompson" wrote:
> 
> > If you have solid planes (prefereably closely spaced) you don't need
> >to worry about 'close' in the sense that you probably think of as
> >close.  If you have vias to the planes on *very* short tracks, or even
> >better in the pad, then the planes will act as a very low impedance
> >route for your currents.  If you think of the time the energy will
> >take to travel from capacitor to chip, the speed of light on FR4 is
> >around 2/3c or 2e8 m/s.  In 1ns, this is around 20cm.  Halve this for
> >the energy to get back and forth and even 10cm is "close".
> >
> > I don't have any pictures to hand, but we've done boards like this
> >with 100MHz memory interfaces and 150MHz core DSP clocks that work
> >fine.
> 
> 
> I'll have to disagree with some of this (not meant as criticism, just
> a point for discussion).
> 

Fair enough :-)

> The number I use (and see in most books) for propagation in FR4 boards
> is 140 to 180ps/in for outer traces and about 180ps/in for inner.

180ps/in makes out to be 
180/25.4 ps/mm ~ 7ps/mm (1.4e8 m/s)

> That would mean about 1.4ns/20cm.  

Indeed it would, I think I must have dropped a factor of 10 somewhere,
sorry about that!  I did the sums properly when I designed the board,
honest :-)

> Operating at 100MHz with, say, 1ns
> edges, means that a cap 10cm away would not be able to deliver
> significant current for the first 0.7ns of the edge, which pretty much
> hoses you.  This is under ideal conditions, ignoring capacitor
> frequency-dependant characteristics; mounting-related inductance;
> trace/plane inductance; board/pin interface issues, etc.
> 
> Because of this and more, I think that 10 to 20cm is far from close
> (that sounds funny) for high speed design.  The characteristics of the
> caps and the mounting/routing methodology can make this a serious
> issue.  There are interesting threads and authorithative information
> about this very subject on the signal integrity list.
> 

Indeed - that's where I learned a lot of this information from... 

How about we say that 1-2cm is close enough (for the HF decouplers?)

> 
> For my last design truly labored over this and took the approach of
> writing a custom power distribution system simulation tool in order to
> get a handle on what was going on.  Things get serious once you stare
> down at the prospect of hundreds of pins switching simultaneusly at a
> given edge rate.  And that's what's important, the edge rates, not the
> frequency.  The thinking can be abstracted to using a bunch of caps
> (the decoupler array) to charge another set of caps (the output
> traces) through the board-to-chip-to-board interface.
> 

Agreed - I did much the same thing here.

> If you start looking at the behavior of capacitors as a function of
> frequency (and, in isolation of board layout/mounting effects) you'll
> see that the C and L induced self-resonant behavior can play
> interesting tricks with what a cap can really do.  Of course ESR and
> ESL are frequency depandant themselves, although it is nearly
> impossible to get this data from manufacturers.
> 

It's getting better, but there wasn't much useful data when I did this
either.  I ended up distributing lots of different values of capacitor
to get a flat impedance profile - which doesn;t half make your BOM
long. And makes population a trial.  I'm not sure if I'd do this again
unless absolutely necessary!

> Beyond that, I find that the field turns "religious" real fast.  There
> are three basic approaches:
> 
> 1- Do it the way we've been doing it 'cause it seems to work 2- Use a
> range of caps to cover the frequency (ehem, edge) range 3- Use only
> two or three a couple of values to cover the range 4- If it looks good
> during layout it should work.
> 
> #1 is folklore and may only have merit if a knowledgeable engineer
> setup rules conservative rules that can be followed by those working
> on new designs independently.  I find that many think that the old
> 0.1uF capacitor rules could be adequate for high-speed design when, in
> reality they are just about useless.  The same applies to a certain
> range of tantalums.  So, for my money, option #1 is not a great
> solution unless you know where it came from, how it got there and what
> the constraints might be.
> 

Agreed - the words "conservative rules" are appropriate... even for
low-speed designs (are there any of those any more?) you may be
spending too much on your caps.

> #2 is promoted by one school of thought within the SI community.  It
> is perfectly valid, of course.  However, I don't see it as
> manufacturing/BOM friendly.  The idea of stuffing a board with a dozen
> different decoupling capacitor values is not something I look forward
> to from many perspectives.  The theory here is that, by being
> intelligent about the choice of caps, their mounting and routing, you
> create a very low impedance "bucket" to cover the edge rates for the
> design.  Like I said, valid, but not my cup of tea.
> 

Right, should have read on before scribbling my earlier paragraph :-)

> #3 is also supported by a sect within the SI community and happens to
> be what I chose to do.  The idea here, loosely speaking, is to form
> the aforementioned "bucket" with just a few values.  The value of the
> capacitor is not as important as the frequency domain characteristics
> of the same.  This is part of the problem today.  Cap manufacturers
> are begining to be pushed by SI experts to address high-speed
> decoupling needs and produce (and quantify) caps that are friendlier
> to this approach.
> 
> By dividing the spectrum in to low, mid, mid-high and high frequency
> (edge rate) zones you can select four capacitors (again, not so much
> values as much as frequency related characteristics) to cover the
> range.  A typical setup will have electrolytics by the power source
> (LF), medium-packaged tantalums within 5 to 10 cm of relevant chips
> (MF to HF) and a couple of small-package chip cap flavors within about
> 2cm of high-speed chips (HF).  The significance of speaking in terms
> of packages as opposed to values is that the package type becomes the
> primary factor in such properties as ESL (which is the dominant
> element as frequencies rise).  Small tantalums, for example, like 4.7
> to 10uF are absolutely worthless for high-speed decoupling designs.
> You have to get into the larger packages in order to get decent ESR
> and ESL characteristics.
> 

I would add that the inductance is affected quite strongly by mounting
method (number of vias and the inductance of the copper connecting
them to the pads) and by the spreading inductance of the planes.  Did
you take advantage of thin dielectrics for extra high-quality
capacitance?  We put two 3.3V/GND 4thou separation pairs in the board,
which got us a few nF of very low inductance capacitance, which comes
in handy at the top end.

I came to the conclusion that above 100-150MHz you couldn't do a lot
with capacitors anyway.

> What attracted me to #3, aside from the obvious BOM-friendly results,
> was the fact that you can engineer a much smoother impedance "bucket".
> Option #2 requires very careful design, modeling and simulation to
> ensure that you are not creating a real problem or it can produce
> weird peaky resonant behavior .  I wasn't equipped nor inclined to do
> that and #3 made more sense overall.  What's missing in the decoupling
> cap world are caps with low ESL and not so low ESR (or quantifiable
> ESR).  If you run the curves, you want some ESR to mitigate peaky
> resonance effects.
> 

You could always fit some small resistors in series :-)

Looks like we came to the same conclusions in the end then!

> Finally, #4, is included in my list because it was something a
> "professional" PCB designer told me when I was considering using his
> company's services.  The way this person did high-speed layouts was to
> "make it look good and it will work fine".  I would imagine there's a
> lot of that going on out there.  I can only wonder and cringe.
> 

Frightening.  Unless their idea of aesthetically pleasing happens to
be trained by what will work ....

> 
> To address the OP's questin directly.  There are good guidelines out
> there on what is required and many options on how to do it.  Every
> layout will be different due to things like the which and how many
> pins you use.  You need to get a set of high-speed decouplers very
> close to the FPGA, within a 2cm circle, I'd say.  

And I'd agree now my 10s are in the right place :-)

> Modern 0402
> components allow you to place a good number of these within the
> device's footprint.  Fan out from there with mid to low frequency caps
> to support charge transfer and avoid starving he HF caps.  Again,
> quantity and type depend on your design and edge rates.  There are
> good books out there that cover the basics.  One such books is "High
> Speed Digital Design, a Handbook of Black Magic" by Howard Johnson.
> 

I can recommend that book also, along with subsribing to the si-list
(http://www.freelists.org/webpage/si-list)

Apologies again for my arithmetic!

Cheers,
Martin

-- 
martin.j.thompson@trw.com
TRW Conekt, Solihull, UK
http://www.trw.com/conekt