You are on page 1of 32

FlexRay Presents New Challenges for Oscilloscope Measurements

Presented by: Johnnie Hancock, Agilent Technologies


FlexRay Measurements Page 1 May 2007

FlexRay Presents New Challenges for Oscilloscope Measurements With the rapid adoption of the FlexRay communication bus in automobiles, embedded hardware designers need to perform signal integrity measurements of their FlexRay-based designs. The primary tool to verify proper signal fidelity and timing of signals is an oscilloscope. Unfortunately, most oscilloscopes lack the required triggering and decoding capabilities that the FlexRay protocol presents. The FlexRay protocol, which is a deterministic bus based on a time-triggered technology presents new measurement challenges not only for FlexRay designers, but also for oscilloscope vendors. Since FlexRay will be employed into many safety-critical systems in the near future, such as brake-by-wire, steer-by-wire, and collision-avoidance systems, it is critical that hardware designers verify proper timing of transmitted frames relative to the specified FlexRay timing schedule. In addition, unlike CAN technology where it is common for error frames to occur due to arbitration, FlexRay designers must insure that their FlexRay systems are error-free. Although low bit-error-ratios can be tolerated in todays computer systems, errors in safetycritical automotive systems cant be tolerated for obvious reasons. This paper will share some of the key learnings that Agilent Technologies and Dependable Computer Systems GmbH (DECOMSYS) discovered during the investigation of a new FlexRay oscilloscope measurement system, and how difficult FlexRay measurement challenges were overcome. This paper includes several FlexRay measurement examples showing how proper FlexRay signal integrity and timing can be verified.

What is FlexRay?
FlexRay is the next generation higher-performance, timetriggered/deterministic serial bus used in higher-end automobiles for safety-critical x-by-wire systems. Time-triggered means that serial communications are based on a global time schedule. X-by-wire could mean brake-by-wire, steer-by-wire, navigation/collision avoidance-by-wire. Faults/errors canNOT be tolerated in these safety-critical automotive applications.

FlexRaytechnology technologyis iscurrently currentlyin inan anearly early FlexRay adoptionphase phaseand andis isexpected expectedto togain gainrapid rapid adoption adoption in the next five years. adoption in the next five years.
FlexRay Measurements Page 2 May 2007

What is FlexRay? FlexRay is the next generation higher-performance, time-triggering/deterministic serial bus used in higher-end automobiles for safety-critical x-by-wire systems. This new time-triggered/deterministic serial bus for automotive applications simply means that digital packets of information are always transmitted within a particular time-slot according to a FlexRay system global timing schedule. This eliminates the possibility of communication collisions and arbitration common with the current CAN bus technology, and makes this new technology an attractive alternative for some of tomorrows safety-critical automotive applications. Many of these safety-critical applications are referred to as x-by-wire systems, such as steer-by-wire, brake-by-wire, navigation/collision-avoidance-by-wire. These types of automotive systems which you will see in future automobiles must be error-free. Although todays computers can tolerate low bit-error-ratios, safety-critical automotive systems must induce zero errors for obvious reasons. This is why this new deterministic serial bus architecture has been selected for these types of applications. In addition to safety and reliability issues, x-by-wire technology will enable automotive manufacturers to eliminate bulky mechanical linkages throughout the automobile, such as the steering column. Not only will this reduce weight and improve efficiency, but this opens up a myriad of future possibilities for applying new state-of-the-art electronic systems in the automobile such as navigation, entertainment, comfort controls.

FlexRay Scope Measurement Needs


Verify signal integrity of differential FlexRay signals. Measure jitter and signal amplitudes using eye-diagrams. Verify timing of the FlexRay schedule relative to signals. Find and debug errors quickly. Detect static frame drop-outs. Time-correlate mixed-signals (ECU, sensors, FlexRay signals). Filter/trigger acquisitions on cycle-multiplexed data fields. Electrical testing at extreme environment conditions. Facilitate remote/in-car testing.

FlexRay Measurements Page 3 May 2007

FlexRay Scope Measurement Needs Agilent Technologies and DECOMSYS GmbH jointly conducted market research during 2006 to better understand oscilloscope measurement needs of FlexRay system and component designers. The number one reason to use an oscilloscope on FlexRay signals is to determine amplitude and timing margins of FlexRay signals. This is typically referred to as signal integrity measurements. But measuring signal integrity of FlexRay signals requires a myriad of specialized oscilloscope tools/applications. The following are the primary oscilloscope measurement requirements that FlexRay designers from various leading automotive companies shared with Agilent and DECOMSYS during this investigation: Measure jitter and signal amplitude margins using eye-diagrams Verify timing of the FlexRay schedule relative to transmitted signals Time-correlated error analysis Detection of static frame drop-outs Mixed-signal time-correlation of various automotive system signals Filtered/triggered acquisitions on cycle-multiplexed frames Testing at extreme environmental conditions In-car testing capability This presentation will address each of these issues with some tips & tricks on how to perform some of these required FlexRay measurements.

Why are FlexRay Signal Integrity Measurements Important?

Differential FlexRay signal with glitch

FlexRay Decode Shows HCRC Error

FlexRay Measurements Page 4 May 2007

Why are FlexRay Signal Integrity Measurements Important? Only an oscilloscope can show the quality of digital signals. Although FlexRay is a digital bus, todays higher speed digital signals still have analog characteristics especially when systems have signal integrity problems. This screen image shows a classic example of an aggressor signal coupling into a differential FlexRay signal producing a header CRC error. Although a FlexRay protocol analyzer could also capture and display the error condition, it could not give you any indication of what might have caused it. The oscilloscope provides additional insight into signal integrity issues.

Switching Power Supply Noise Causes Signal Integrity Problem


60 kHz Switching Power Supply Noise

FlexRay Decode Shows HCRC Error

FlexRay Measurements Page 5 May 2007

Switching Power Supply Noise Causes Signal Integrity Problem The cause of this particular signal integrity problem was quickly discovered using an oscilloscope. When the scopes time base was re-scaled to show multiple FlexRay frames, we could see that signal interference was occurring at a fixed 60 kHz rate. This was exactly the frequency of this nodes switching power supply.

Oscilloscope Eye-Diagram Measurements


Eye-diagrams display worst-case jitter, vertical noise, & signal anomalies Repetitive eye-diagrams measurements require a reference clock signal for oscilloscope triggering FlexRay signals dont supply an explicit reference clock signal Triggering on the FlexRay signal itself eliminates most jitter components

Vertically closing eye due to noise and/or insufficient signal level

Horizontally closing eye due to jitter and/or signal timing errors


FlexRay Measurements Page 6 May 2007

Oscilloscope Eye-Diagram Measurements To evaluate jitter and timing errors on serial data communication signals, engineers frequently use an oscilloscope to view overlaid bit intervals in an eye diagram display. But creating a repetitive eye diagram on an oscilloscopes display requires a reference trigger signal such as a clock. However, in many of todays serial communication protocols such as FlexRay, the reference clock is not explicit it is embedded in the serial data signal. So how can FlexRay hardware designers create eye diagrams on their scopes without an explicit clock signal for reference? First we will discuss a common but flawed technique that is currently being used by some FlexRay engineers. Then we will explore two new recommended measurement techniques that more reliably show worst-case FlexRay jitter and signal amplitude variations.

FlexRay Eye-Diagram Measurement Techniques


Repetitive Cycle-to-Cycle Eye Repetitive BSS Eye

Real-time Eye

FlexRay Measurements Page 7 May 2007

FlexRay Eye-Diagram Measurement Techniques A technique that some FlexRay designers are using today involves triggering on either edge of the differential FlexRay signal. We call this type of FlexRay eye measurement a repetitive cycle-to-cycle eye. There are some fundamental problems with type of eye measurement which we discuss in more depth. A better technique (in the opinion of the author of this paper) to measure all jitter not just cycle-to-cycle jitter is a repetitive eye measurement based/triggered on Byte Start Sequence (BSS) events. Lastly, a rather new eye measurement technique known as the real-time eye will be discussed. This technique uses software to recover a clock and create a folded eyediagram from a single-shot acquisition using a scopes deep acquisition memory.

FlexRay Repetitive Cycle-to-Cycle Eye-Diagram

Trigger Point

Trigger Condition = Either edge, hold-off = FlexRay cycle time


FlexRay Measurements Page 8 May 2007

FlexRay Repetitive Cycle-to-Cycle Eye-Diagram In the absence of an explicit reference clock signal to use as an oscilloscope trigger source to create a repetitive eye diagram display, you might be tempted to set up your scope to trigger on both rising and falling edges of the FlexRay differential signal. In an attempt to insure triggering on all edges successively, you also might set the scopes trigger hold-off time to exactly the FlexRay schedule cycle time. For instance, with an ideal cycle time of 5 ms, if the scopes trigger hold-off time is set to exactly 5 ms, then under ideal conditions the scope will trigger once every cycle while stepping through the serial data stream triggering on each edge of the signal successively. But because of differences in the stability of each FlexRay nodes timebase relative to the accuracy of the scopes timebase, it is unlikely you will achieve this ideal triggering condition. In most instances, the scope will not step through the signal triggering on every edge successively, but will randomly trigger on most edges. However, this method of creating FlexRay eye diagrams has other inherent problems.

Limitations of the Repetitive Cycle-to-Cycle Eye Test


Only shows cycle-to-cycle jitter. Only shows single bit-width signals. Idle signal will be captured within eye. Susceptible to triggering on noise. FlexRay Mask does not provide a idle dead zone.

FlexRay Measurements Page 9 May 2007

Limitations of the Repetitive Cycle-to-Cycle Eye Test

The biggest problem with this eye-diagram measurement technique is that when we trigger on the differential FlexRay signal itself, most measured jitter is eliminated. The only jitter component remaining in the measurement is cycle-to-cycle jitter. In addition, only bits of a single bit-width are testing using this method. So this eliminates the ability to test for intersymbol interference (ISI), or serial pattern dependent timing errors. Secondly, with the scopes trigger level set near the 50% threshold level of the differential FlexRay signal, which is necessary to create a vertically balanced eye-diagram, the scope will occasionally trigger on overshoot or ringing of the frame end sequence (FES) pulse. This sets up a situation where the idle time between frames may be captured and displayed within the eye. If you are performing a pass/fail mask test on this eye, then the FlexRay mask must include a dead-zone around the base-line (idle level) of the signal. In addition, in the naturally harsh and noisy environment of automobiles, the scope may trigger on random noise or interference riding on the base-line signal between frames. If a trigger event caused by base-line occurs just before a signal edge, then a signal edge will appear in the middle of eye, indicating a severe FlexRay timing problem that may not actually exist. Lastly, FlexRay masks currently defined in the FlexRay physical layer specification dont provide a dead-zone in order to ignore the idle/base-line signal running through the middle of the eye. It would be desirable for a scope to automatically detect eye failures, but without the complex dead-zone mask, scopes will indicate failures when the idle signal is captured. In addition, the FlexRay physical specification also position the left-most point of the mask exactly at the trigger reference point. Scopes with automatic mask failure detection will immediately indicate a failing condition using this mask position.

FlexRay Timing Diagram


Consistent Trigger Event Hold-off = 950 ns Pulse width = 100 ns to 900 ns Potential Trigger Event Potential Trigger Event

TSS

BSS FSS

Byte 0

BSS

Byte 1

BSS

Byte N

FES

1st BSS = 200 ns wide 2nd through Nth BSS = 100ns to 900 wide 950 ns trigger hold-off = trigger on falling edge of BSS Potential Trigger Event = Trigger if re-armed Depends on acquisition/waveform update rate
FlexRay Measurements Page 10 May 2007

FlexRay Timing Diagram Rather than triggering on any edge of the FlexRay signal as described above, a better way to create a valid FlexRay eye diagram is to set up the oscilloscope to trigger on a signal within each byte start sequence (BSS) event, which is the timing reference point for the transmission of the following byte. But not all scopes have the required performance to make this measurement. Triggering on a BSS pulse requires time-qualified pulse-width triggering along with trigger hold-off. In addition, the scope must have a very fast waveform update rate/re-arm time, and the scope should also have a pseudo-randomized start-of-acquisition to insure triggering on most bytes. As the timing diagram in screen image shows, for a 10 Mbps FlexRay baud rate, the width of the first positive pulse that contains the first BSS falling edge preceding byte number 0 is 200 ns (2 bit periods). The positive pulse width of all successive pulses preceding BSS falling edges can range from 100 ns to 900 ns. For example, if a particular byte contains all zeros, then the width of the pulse that contains the next BSS falling edge would be 100 ns (one bit period). But if the byte contains all ones, then the width of the pulse that contains the next BSS falling edge would be 900 ns (eight bit periods plus the BSS pulse). With a scopes pulse-width triggering set up to trigger on positive pulses wider than 50 ns (which helps to avoid triggering on random noise/glitches) but narrower than 950 ns, the scope will trigger only on falling edges of the BSS pulse but only if the scopes trigger hold-off time is also set to 950 ns. This trigger hold-off setting will insure that the scope does not trigger on various-width data pulses within each byte. After the scope has synchronized triggering on the first BSS pulse of a frame, trigger hold-off will always arm the next trigger event 50 ns before the next falling edge of the BSS event. Note that the next BSS event should always occur 1000 ns after the preceding BSS event.

10

BSS Pulses Captured by an Oscilloscope


BSS BSS BSS BSS BSS BSS BSS BSS BSS

FlexRay Measurements Page 11 May 2007

BSS Pulses Captured by an Oscilloscope This oscilloscope display shows a similar timing diagram of a repetitive waveform capture of the first nine bytes of a FlexRay frame using an oscilloscope. Note that with the scopes timebase set to 1 s/div, we can see that the BSS events occur once every 1 s (1 division apart).

11

Triggering on BSS Events to Show Successive 8-bit Eye-Diagram


BSS Trigger Event

Bit 7

Bit 6

Bit 5

Bit 4

Bit 3

Bit 2

Bit 1

Bit 0

BSS & FES

Trigger Condition = + Width: 50 ns to 950 ns, Hold-off = 950 ns


FlexRay Measurements Page 12 May 2007

Triggering on BSS Events to Show Successive 8-bit Eye-Diagram This oscilloscope display shows an example of triggering on BSS events using pulse-width triggering and trigger hold-off. Although this may appear to be a non-standard eye-diagram since it consists of eight waveform eyes, this is a perfectly valid technique to view the eight individual bit fields. Displaying a more conventional repetitive eye-diagram consisting of a single eye with all eight bit fields overlaid on top of one another requires a few additional steps.

12

Repetitive BSS Eye-Diagram of Bit #7 (MSB)

Bit #7

Trigger Condition = + Width: 50 ns to 950 ns, Hold-off = 950 ns Timebase = 20 ns/div, Delay = 140 ns
FlexRay Measurements Page 13 May 2007

Repetitive BSS Eye-Diagram of Bit #7 (MSB) Using the same oscilloscope triggering condition (+PW > 50 ns but < 950 ns, with hold-off = 950 ns), scale the scopes timebase to show just the first bit field (MSB), as shown in this oscilloscope display. In this example, we have set up the time base scaling to 20 ns/div (5 divisions = 1 bit width) and the acquisition delay to 140 ns relative to center-screen. Note that the first BSS trigger event is located 7 divisions (140 ns = 20 ns/div X 7 divisions) left of center-screen. Next, turn on the scopes infinite-persistence display mode to collect tens of thousands of acquisitions of bit #7, which only requires a few seconds if the scope has a fast waveform update rate.

13

Repetitive BSS Eye-Diagram of Bit #6 and Bit #7

Bits #6 & #7

Trigger Condition = + Width: 50 ns to 950 ns, Hold-off = 950 ns Timebase = 20 ns/div, Delay = 140 ns, 240 ns
FlexRay Measurements Page 14 May 2007

Repetitive BSS Eye-Diagram of Bit #6 and Bit #7 After collecting a sufficient number of acquisitions of bit #7, turn off the infinite-persistence display mode, but dont clear the infinite-persistence display of bit #7. Then change the scopes acquisition delay time by an additional 100 ns (one bit width) to 240 ns. Next, turn on the infinite-persistence display mode once again to collect thousands of overlaid acquisitions of bit #6 overlaid on top of the previously captured bit # 7 waveforms, as shown in this scope display.

14

Repetitive BSS Eye-Diagram of ALL Bit Fields (#0 through #7)

Bits # 0-7

Trigger Condition = + Width: 50 ns to 950ns, Hold-off = 950 ns Timebase = 20 ns/div, Delay = 140 ns, 240 ns... 840 ns
FlexRay Measurements Page 15 May 2007

Repetitive BSS Eye-Diagram of ALL Bit Fields (#0 through #7) Repeat the above process with acquisition delay settings of 340 ns through 840 ns to create a repetitive eye-diagram of all eight bit fields based on the reference BSS events, as shown in this scope display. For this multi-step measurement to create an overlaid eye-diagram of all eight bit fields, you need a scope with a very fast waveform update rate and dithered repetitive acquisitions using equivalent-time sampling in addition to precise pulse-width triggering and trigger hold-off. Fast waveform update rates are important for two reasons. First, you need to collect thousands of acquisitions of all bit fields to insure statistical validity of the eye-diagram measurement. Secondly, fast waveform update rates are required to insure that the scope triggers on multiple bytes within each frame. If the scope updates acquisitions slowly, the scope will always synchronize its acquisition on just the first BSS of each frame. A dithered start-of-acquisitions is required to prevent the scope from triggering on every Nth BSS trigger event, thereby skipping multiple bytes. Agilent scopes employ dithered startof-acquisitions when you are using the equivalent-time sampling mode. This dithered technique of acquisitions was employed in Agilent scopes primarily to prevent the possibility of synchronizing repetitive acquisitions with the signal under test. If this happens, you may see holes in the displayed waveform. But this dithered start-of-acquisitions technique also insures that random bytes of the FlexRay frame are triggered on, thereby improving the statistical validity of the repetitive eye-diagram measurement.

15

Limitations of the Repetitive BSS Eye Test


Currently a manual multi-step test. Not all scopes allow PW triggering AND trigger hold-off simultaneously. Not all scopes allow set up changes while using infinite-persistence. Scope re-arm time (1/dead-time) eliminates acquisition of some bytes. Not all scopes dither start-ofacquisitions. Currently defined FlexRay masks only defined for cycle-to-cycle jitter component.

FlexRay Measurements Page 16 May 2007

Limitations of the Repetitive BSS Eye Test Although the repetitive BSS eye-diagram measurement method is superior for measuring worst-case jitter and signal amplitude deviations relative to the cycle-to-cycle eye-diagram measurement (in the opinion of the author of this paper), this method of creating a repetitive eye-diagram is not without its limitations. As you just seen in this presentation, creating a single eye is a multi-step process for overlaying individual bit fields one at a time. In addition, not all scopes on the market today have the required triggering and display features required for this testing method. For instance, some scope dont permit setting a specific trigger hold-off time while using pulse width triggering. And most scopes on the market dont allow the user to change setup conditions, such as delay time, while using the infinite-persistence display mode. As soon as a set up is changed, the infinite-persistence display is erased and starts over. Although it would be desirable to capture all bytes of a FlexRay transmission, oscilloscope re-arm/waveform update rates limits which bytes are captured. Once the scope triggers on the first BSS event in a particular frame, it is impossible for the scope to re-arm itself in time to capture the second BSS event. This would require a waveform update rate in access of 1,000,000 waveforms per second. Closely related to this issue is dithering of start-ofacquisition process, which is not available in all scopes. Without dithering, the scope will only capture every Nth BSS event based on its re-arm time or waveform update rate. Finally, FlexRay mask standards defined in the FlexRay physical layer specification only apply to cycle-to-cycle eyes. Repetitive or real-time eye-diagrams created using the BSS event as the reference timing event will typically show more jitter than whats allowed for in the currently defined FlexRay masks.

16

FlexRay Real-Time Eye-Diagram


BSS BSS

FlexRay Signal

Folded Real-time Eye

FlexRay Measurements Page 17 May 2007

FlexRay Real-Time Eye-Diagram Another measurement technique to create FlexRay eye-diagrams is the real-time eye. Although automotive embedded designers may be unfamiliar with this type of measurement, this is a very common measurement used on high-speed serial buses, such as PCI-Express (2.5 Gbps). Creating a real-time eye requires a deep-memory, real-time oscilloscope with a real-time eye measurement option that recovers the buss embedded clock using a software clock recovery algorithm. For some high-speed serial bus standards, the scopes software clock recovery algorithm can be quite complex, such as recovering clocks from systems based on spread spectrum clocking and a phase lock loop (PLL) clock recovery hardware. But for the FlexRay protocol, the software clock recovery algorithm is very simple. The scopes software assumes a fixed 10-MHz clock synchronized to each BSS event. For a FlexRay real-time eye, the scope should first capture multiple FlexRay frames using deep acquisition memory. The triggering technique is not critical typically a simple edge trigger condition is all you need. The scope then searches through its deep memory record to locate each BSS event. The first BSS event of each frame is the first complete falling edge. Each successive reference BSS event will be a falling edge that occurs approximately 1 s later. The scopes software precisely locates each of the events. The algorithm then slices the bit fields of each byte into perfect 100 ns mini-records. These 100 ns minirecords are then overlaid on top of one another to recreate the real-time (or folded) eye from a single acquisition. Although real-time eyes are typically created using a single deep-memory acquisition that can capture multiple FlexRay cycles, this type of measurement can also be set up to run repetitively to overlay multiple real-time eyes to look for long-term anomalies. If and when a mask violation occurs, the last eye can be unfolded in to analyze the specific bit failure.

17

FlexRay Real-Time Eye

FlexRay Measurements Page 18 May 2007

FlexRay Real-Time Eye As you can see in the scope display, a real-time eye looks exactly the same as a repetitive eye. However, real-time eyes can be created in software using a single acquisition. You can only find real-time eye measurement capabilities in todays higher-performance, Windowsbased scopes. In addition to performing real-time eye measurements, these scopes also can automatically perform jitter analysis, including separation of various random and deterministic components of timing error. Although real-time eyes and jitter analysis based on the FlexRay protocol are not currently available from any oscilloscope vendor, this measurement capability may become available in the near future.

18

Limitations of the Real-time BSS Eye Test


Currently not available from any vendor. Currently defined FlexRay masks only defined for cycle-to-cycle jitter component. Will require a Windows-based, nonbattery operated scope.

FlexRay Measurements Page 19 May 2007

Limitations of the Real-time BSS Eye Test Although the real-time BSS eye-diagram measurement method is probably the most reliable FlexRay eye-diagram measurement technique, this method of measuring a FlexRay eye is not currently available from any oscilloscope vendor. However, once this measurement capability becomes available, FlexRay engineers will be able to create eye-diagrams based on all bits, all bytes, and all frames of a complete FlexRay cycle, from a single acquisition using a deep memory oscilloscope. In addition, a Windows-based scope will be able to perform statistical jitter measurements at the crossing edges using histogram measurements. Another limitation of this measurement technique is the lack of defined FlexRay masks based a Byte Start Sequence (BSS) eye.

19

Why is the FlexRay Timing Trace Important?

Verify timing of slot and segment boundaries

FlexRay Measurements Page 20 May 2007

Why is the FlexRay timing trace important? Part of the deterministic nature of the FlexRay protocol is that it is based on a time-triggered architecture. This means that FlexRay signal transmissions must occur within a specified window of time. Verifying timing of physical layer FlexRay signals to the systems specified timing schedule (usually specified within a FIBEX file) is very important to FlexRay designers in order to eliminate possible timing errors in their designs.

20

Why is hardware-based decoding important?


1. Fast waveform/decode update rates enhance usability Enhances probability of capturing and decoding infrequent errors

2.

Infrequent Header CRC Error

FlexRay Measurements Page 21 May 2007

Why is hardware-based decoding important? Waveform and FlexRay decode update rates are important for two reasons. First of all, fast waveform/decode update rates provides for responsive measurements making the oscilloscope easier to use. Secondly, and probably most important, real-time decode update rates enhance the probability of the scope to capture random and infrequent error conditions. Most oscilloscopes on the market today utilize software decoding techniques. This means that waveform and decode update rates can take seconds especially when using deep memory to capture multiple packets of FlexRay transmissions. If random errors occur, they will probably occur during the scopes data-processing dead-time. Hardware-based FlexRay decoding provides real-time responsiveness and enhanced error detection.

21

Why is robust FlexRay error analysis required?


Eliminating errors in safety-critical automotive systems is CRITICAL!

Header CRC Error Message

FlexRay Measurements Page 22 May 2007

Why is robust FlexRay error analysis required? For safety-critical FlexRay systems, it is extremely important to eliminate all possible errors. After all, when we turn the steering wheel to avoid a collision, dont we want the electronic steering system to respond immediately? Identifying errors goes beyond just detecting CRC errors. What about possible timing errors such as slot boundary violations? A robust set of error messaging and oscilloscope triggering enables FlexRay designers to debug their systems before they reach the customer.

22

Why is Static Slot Drop-out Detection Important?


Static Frame Drop-out

FlexRay Measurements Page 23 May 2007

Why is Static Slot Drop-out Detection Important? Although transmitting frames during the dynamic segment is optional, if an ECU/node is assigned a particular static slot to communicate in, it must transmit a frame of a fixed length, even if it has nothing to say. If it has nothing to say, then a null frame should be transmitted. In this example, we show a static frame (ID:39) that occasionally drops-out, which is a violation of the FlexRay protocol.

23

Triggering on Empty (but assigned) Static Slots

Empty Slot

FlexRay Measurements Page 24 May 2007

Triggering on Empty (but assigned) Static Slots By setting up to the scope to trigger on Slot-Type: Empty, the scope will only trigger and capture waveforms if specified slot (#39) is empty. This type of FlexRay oscilloscope triggering can be especially useful when looking for very infrequent drop-out conditions, in which case the scope could be setup to trigger on this condition for an overnight test.

24

Why are Mixed-Signal Measurements Important?


Time-correlate:
Vehicle analog sensor inputs

Differential FlexRay signal + ECU digital control signals + FlexRay timing & frame decode traces

FlexRay Measurements Page 25 May 2007

Why are mixed-signal measurements important? Automotive electronic systems are by definition mixed-signal systems consisting of multiple analog, digital, and serial signals. As stated earlier, FlexRay designers indicated that they needed the ability to correlate multiple mixed-signal activity within their automotive systems. A mixed signal oscilloscope (MSO) is a natural fit for these types of measurements. With an MSO, designers can easily view and time-correlate their analog sensor inputs, their differential serial signals, such as FlexRay, and their digital control and I/O signals within their ECUs using a single instrument. And with advanced FlexRay triggering and decoding, they can also correlate all of the mixed-signals to the FlexRay bus.

25

Why is FlexRay Cycle-Filter Triggering Important?

Unfiltered (All) Cycle Triggering Cycle-multiplexed data

FlexRay Measurements Page 26 May 2007

Why is FlexRay Cycle-Filter Triggering Important? Because of the multiplexed communication possibilities that the FlexRay protocol allows, FlexRay designers want to be able to trigger oscilloscope acquisitions on particular communication cycles not just cycle number, but triggering based on cycle-repetitive rate and cycle- base number. This scope display shows an example of capturing repetitive acquisitions while triggering a particular FlexRay frame (ID: 38). This frame includes a multiplexed data field, which we can observe when triggering on all cycles. Perhaps this frame transmits various engine diagnostic parameters. Capturing just cycles that apply to specific parameters, such as oil pressure or temperature requires cycle-filter triggering.

26

FlexRay Cycle-Filter Triggering: Base-Rep

Cycle/trigger filtering: Repetition = 4, Base = 0 Engine diagnostics parameter #1

FlexRay Measurements Page 27 May 2007

FlexRay Cycle-Filter Trigger: Base-Rep With cycle base-rep triggering, the scope can filter its triggering on a repeating pattern of cycles. In this example we show that with a cycle repetitive of 4 and base of 0, the scope only captures cycles 0, 4, 8, 12, 16... (0, 0+4, 0+4+4, etc.). Perhaps the engine diagnostic ECU (frame ID:38) transmit engine temperature during these particular cycles.

27

FlexRay Cycle-Filter Triggering: Base-Rep

Cycle/trigger filtering: Repetition = 4, Base = 1 Engine diagnostics parameter #2

FlexRay Measurements Page 28 May 2007

FlexRay Cycle-Filter Trigger: Base-Rep If we change the cycle-base number to 1, the scope now triggers on and captures just cycles 1, 5, 9, 13, 17... (1, 1+4, 1+4+4, etc.). Perhaps the engine diagnostic ECU (frame ID:38) transmit engine oil pressure during these particular cycles.

28

Remote in-car testing requires battery operation

FlexRay Measurements Page 29 May 2007

Remote in-car testing requires battery operation Although FlexRay systems should be thoroughly tested on the bench and under simulated environmental conditions, they should also be tested under real-world conditions. This requires in-car testing under various extreme driving conditions. Evaluating signal fidelity with an un-tethered oscilloscope requires a scope that performs FlexRay measurements under battery operation.

29

Testing Automotive Systems in Extreme Environment Conditions

Precision Gore extension cables compatible with Agilents InfiniiMax active probes allow differential active probing within environmental chambers at extreme temperatures.
FlexRay Measurements Page 30 May 2007

Testing in extreme environmental conditions Signal integrity measurements on automotive differential signals such as the physical layer of the FlexRay serial bus requires differential active probing. In addition, FlexRay designers must often test their embedded designs under very extreme conditions in environmental chambers. These extreme conditions may include testing ECUs and differential serial buses at temperatures exceeding 100 degrees Celsius. Unfortunately, the active circuitry in todays typical active probes cannot tolerate temperatures exceeding 55 degrees C. However, with the unique electrical and physical architecture of the 1130 Series InfiniiMax active probes, SMP microwave extension cables from Gore (Gore part number PRP042105-01) can be used to extend and displace the probes active amplifier to be outside of an environmental chamber. With this configuration, InfiniiMax passive probe heads can be connected to test points within the chamber with temperatures exceeding 100 degrees C.

30

FlexRay Presents New Challenges for Oscilloscope Measurements


Summary
FlexRay signal integrity measurements require an oscilloscope. FlexRay eye measurements should be referenced to Byte Start Sequence events. Debugging FlexRay systems requires sophisticated FlexRay real-time protocol triggering and decoding.

FlexRay Measurements Page 31 May 2007

Summary The fundamental tool to perform signal integrity measurements is an oscilloscope. A test often used to check for valid signal fidelity is the eye diagram. Creating a repetitive eyediagram requires establishing scope triggering on Byte Start Sequence events. Alternatively, a real-time eye can be created using a custom clock recovery algorithm that slices a deep memory acquisition into bit intervals and then overlays the bits. Debugging FlexRay systems can be greatly enhanced using an oscilloscope with FlexRay triggering and decoding, including error analysis.

31

FlexRay Measurements Page 32 May 2007

32

You might also like