S oC Design and Test Methodologies for Wireless Communications - - PowerPoint PPT Presentation

s oc design and test methodologies for wireless
SMART_READER_LITE
LIVE PREVIEW

S oC Design and Test Methodologies for Wireless Communications - - PowerPoint PPT Presentation

S oC Design and Test Methodologies for Wireless Communications Baseband Processors Henry Ye Alcatel-Lucent Hhye@ alcatel-lucent.com WOCC 2007 Overview Evaluation of wireless communication standards. Examples of S oC device used in


slide-1
SLIDE 1

WOCC 2007

S

  • C Design and Test Methodologies for

Wireless Communications Baseband Processors

Henry Ye Alcatel-Lucent Hhye@ alcatel-lucent.com

slide-2
SLIDE 2

WOCC 2007

Overview

Evaluation of wireless communication standards. Examples of S

  • C device used in wireless communications.

Challenges in S

  • C design and verification.

Guidelines for S

  • C partition.

Guidelines for S

  • C verification/ co-verification.
slide-3
SLIDE 3

WOCC 2007

Evolution of Wireless Communication S tandards

IS95 CDMA2000 3G1X GSM TD-SCDMA EVDO Rev HSDPA EVDO Rev A HSUPA EVDO Rev C LTE WCDMA R99 Circuit Switch Voice Circuit Switch Voice and Data Downlink High Speed Packet Data Downlink and Uplink High Speed Packet Data OFDM Evalution 14kbps 384 kbps DL: 2.4 mbps UL: 153 kbps DL: 3.1 mbps UL: 1.8 mbps 14kbps 384 kbps DL: 14.4 mbps UL: 384 kbps DL: 14.4 mbps UL: 5.76 mbps DL: >100 mbps UL: >50 mbps DL: >100 mbps UL: >50 mbps

Higher level of integration is required for baseband processors in both Base S

tations and terminals, in order to support the increased data rates in newer standards.

  • The advancement in VLS

I technologies and the appearance of S

  • C devices have made this possible.
slide-4
SLIDE 4

WOCC 2007

S implified View of a Generic S

  • C Device

Processors Local Memories External Memory Interface Blocks Custom Designed HW Blocks Hardware IP Cores

High Speed Local Bus

External Bus Interface Blocks

SoC Device A S

  • C device can have some or all of the above blocks
slide-5
SLIDE 5

WOCC 2007

S

  • C Example 1: Lucent WCDMA OneChip AS

IC

ARM Processor RX TX Encoder and Decoder

Lucent OneChip ASIC

ARM Processor Local Memories

High density multi-channel infrastructure baseband S

  • C device.
slide-6
SLIDE 6

WOCC 2007

S

  • C Example 2: Fuj itsu WiMAX MB87M3400 PHY/ MAC Processor

Source: http://www.fujitsu.com/downloads/MICRO/fme/wimax/Wimax_3400.pdf Contains 1 ARM and 1 DS P

slide-7
SLIDE 7

WOCC 2007

S

  • C Example 3: Qualcomm MS

M7200

Source:

http://www.cdmatech.com/download_library /pdf/msm7200_chipset.pdf

S

upports GS M/ GPRS / WCDMA/ HS DPA/ HS UPA

S

upport 7.2 mbps on the downlink (HS DPA) and 5.76 mbps on the uplink (HS UPA)

Contains 2 ARM processors and 2 DSP

processors.

Also contains many hardware IP cores for

specific functionalities such as

  • Imaging processing, video processing, audio

processing, and graphic processing.

slide-8
SLIDE 8

WOCC 2007

S

  • C Example 4: S

TMicro GreenS ide S TW5100

Source: http://www.st.com/stonline/products/literature/ta/11145.pdf Contains 2 DS Ps, 1 ARM, 2MB S RAM, and hardware IP cores for decoders. S erved as a S

  • C platform for infrastructure baseband processor market.

Customers are responsible for most of the sw development.

slide-9
SLIDE 9

WOCC 2007

Challenges in S

  • C Developement

Tow maj or challenges in S

  • C Development:

The partition of functionalities between custom-designed hardware,

hardware IP cores, and embedded processors.

The functionality verification/ co-verification. While there is no single methodology for all S

  • C design and

verification, this presentation is intended to provide some guidelines

  • f the methodologies that may be applicable to the current generation

wireless communication baseband processors.

slide-10
SLIDE 10

WOCC 2007

Guidelines for S

  • C Partition (1/ 3)

Embedded processors are ideal for functionalities that require significant

amount of flexibility and programmability.

The tradeoff is higher cost and power consumption Functionalities with heavy computational complexity are usually put in custom-

designed hardware.

The tradeoff is the loss of flexibility. Example: The CDMA chip level processing can be done in custom-designed hardware

while symbol level processing is handled in DS P.

Flexibility of DS

P can allow longer time interval for algorithm development and provide

  • ption for algorithm improvements.

However, partial or all of the symbol level processing may have to be

implemented in custom-designed hardware due to various reasons, e.g.,

S

ensitivity to cost and high power consumption such as for terminal devices.

The whole symbol level processing can be enormous for infrastructure devices due to high

channel density and/ or increased data rates.

More experienced teams tend to put more into custom-designed hardware to save cost and

power consumptions.

slide-11
SLIDE 11

WOCC 2007

Guidelines for S

  • C Partition (2/ 3)

Unlike physical layer processing, most higher layer processing fits into

embedded processors well when implemented in the same S

  • C device.

For example, MAC layer functionality may be implemented in

embedded processors such as ARM or DS P.

S

  • C devices used in terminals tend to use more embedded

processors due to more higher layer functionality integrated into the same S

  • C.

S

  • C architects and designers have to select the embedded processors

carefully based on many factors:

What embedded processors supported by the chosen AS

IC foundries,

the intended tasks, the design/ verification methodologies, the available tools, and the cost/ power consumption budget.

slide-12
SLIDE 12

WOCC 2007

Guidelines for S

  • C Partition (3/ 3)

Hardware IP cores are usually designed by third parties and can be

licensed with costs. They are used when providing business advantages such as when

the S

  • C design team does not have expertise to develop it by internally,
  • r
  • using external supplied hardware IP cores can simply save development

cost.

For reliability reasons, hardware IP cores targeting well-defined

functional blocks are likely to be used for easier integration and verification.

S

  • me commonly used baseband IP cores:

Turbo decoder and encoder, IFFT and FFT (in OFDM st andards).

Interface specific hardware IP cores:

PCI/ PCI-express cores, external memory controllers, ..

slide-13
SLIDE 13

WOCC 2007

S

  • C Verification -- Overview

Two maj or steps in S

  • C verification:

Block level

Focus on the validation of each individual block

Device level

Focus on the verification of the integrity of the whole device and the

interactions between all blocks (such as between custom-designed hardware, embedded processors, and hardware IP cores).

Note that there is no unique S

  • C verification method. Each team

develop its own method based on its experience, the available tools, the functionality of the S

  • C device, and the chosen IP cores

and embedded processors.

slide-14
SLIDE 14

WOCC 2007

S

  • C Verification – Block Level

Block level verification for custom-designed hardware Bit exact model is commonly used for the verification of custom-designed

hardware blocks.

The integrity of the bit exact model (usually in C or C++) can be verified through

simulation.

The purpose of the verification is to ensure the hardware model (e.g., in VHDL or

Verilog) matches with the bit exact model

Block level verification for embedded processors S

tep 1: S imple test to make sure the processors can access the peripherals and memories through its internal buses.

S

tep 2: Verify the integrity of the software code that will run in the processors through simulation.

S

tep 3: Verify the loading of the embedded processor is within the practical range and the time critical processing can be finished in time.

Cycle accurate simulation tool is usually used. S

  • C team needs to define “stressful” test vectors for processor’s loading and crit ical

time analysis.

The verification of hardware IP cores may be similar to that of custom-

designed hardware blocks, if simulation models are provided by the IP vendors.

slide-15
SLIDE 15

WOCC 2007

S

  • C Verification – Device Level

The focus is on the interactions of different blocks. Co-simulation is commonly used so that hardware model and the models

for embedded processors can be simulated together. Bit exact model may still be used to compare against the results of the co-

simulation.

Popular co-simulation tools such as S

eamless from Mentor Graphics are used.

However, co-simulation may be too slow for complicated S

  • C. As a

result, emulation tools are usually used.

The whole S

  • C device may be mapped into FPGA based emulation tools.

In addition to gaining simulation speed, emulation provides a platform for

HW/ S W integration.

It should be noted that special test images rather than real

software loads may be used in the embedded processors at this stage to focus on the interactions between processors and the rest

  • f the device.

The core algorithm implemented in embedded processors can be easily

changed and will likely keep changing.

slide-16
SLIDE 16

WOCC 2007

Summary

The increased data rates in later wireless standards

require higher level of integration in baseband processors, which can be realized in S

  • C devices.

The two maj or challenges in S

  • C design are how to

partition S

  • C device and how to verify S
  • C device.

While there is no single methodology for S

  • C partition and

verification, some guidelines are provided in this presentation.