Systems On Chip (SoC)

SYSTEMS ON CHIP (SOC)
FOR EMBEDDED
APPLICATIONS
OUTLIN
E
• What is an embedded SoC?
• SoC Intellectual Property (IP)
• ARM processors
• ARM support modules
• SoC Design Flow
• Modeling and simulation
• Physical design
EMBEDDED
SYSTEM
• “System”
• Set of components needed to perform a function
• Hardware + software + ….
• “Embedded”
• Main function not computing
• Usually not autonomous
• Usually a computer inside a system
• Application specific
• Subject to constraints
SYSTEM ON
CHIP
• Definition
• (nearly) complete embedded system on a single chip
• Usually includes
• Programmable processor(s)
• Memory
• Accelerating function units
• Input/output interfaces
• Software
• Re-usable intellectual property blocks (HW + SW)
SOC DESIGN
GOAL
Before
After
T.I .
smartphone
reference
design
Main
SoC
2/29/2012 VLSI D&T Seminar - Victor P. Nelson
TEXAS INSTRUMENTS
OMAP44X
APPLE “A5”
SOC
• Used in iPad 2 and iPhone 4S
• Manufactured by Samsung
• 45nm, 12.1 x 10.1 mm
• Elements (unofficial):
• ARM Corex-A9 MPCore CPU - 1GHz
• NEON SIMD accelerator
• Dual core PowerVR SGX543MP2 GPU
• Image signal processor (ISP)
• Audience “EarSmart” unit for noise canceling
• 512 MB DDR2 RAM @ 533MHz
iPhone 4 circuit board (with A4 SoC)

NVIDIA TEGRA 2
SOC
Tablet Applications:
• Asus Eee Pad
• Motorola Xoom
• Samsung Galaxy
• Acer Iconia Tab
EXAMPLE: BLOOD PRESSURE MONITORSOC

SOC
CHALLENGES
• SoC Designs
• More complex, more functions, higher gate counts
• Faster, cheaper, smaller
• More reliable
• How to handle complexity?
• System design at multiple abstraction levels
• Integration of heterogeneous technologies & tools
• Signal integrity & timing
• Power management
• SoC test methodology
SOC DESIGN WITH RE-USABLE IP

MODULES
• IP = intellectual property
• HW or SW block
• Designed for reuse
• Need for standards (VSIA)
• Platform-based SoC design
• Organized method
• Reduce cost and risk
• Heavy re-use of HW and SW IP
• Steps in re-use
• Block -> IP -> integration architecture
ARM IP (ARM MAKES NO

HARDWARE)
• Processors
• Cortex A, Cortex R, Cortex M, ARM11, ARM9, ARM7, SecurCore
• Multimedia IP - graphics, video, audio
• Mali-T604 GPU graphics processor
• Mali-VE6 video engine
• System IP
• CoreLink – interconnect & memory controllers
• Supports Cortex and Mali processors
• AMBA – Advanced Memory BusArchitecture
• CoreSight – debug and trace IP (build into SoC)
• ARM “Artisan” Physical IP
• Logic IP, Standard Cells, Memory Compilers, Interface IP
• Technology-specific
ARM SOC-BASED
PRODUCTS
Joe Bungo: CPU Design Concept to SoC

ARM CORTEX
PROCESSORS
ARM CORTEX-A9
MPCORE
RELATIVE
PERFORMANCE
ARM CORTEX-A9 MPCOREPERFORMANCE

LICENSING ARM
IP
• Perpetual (implementation) license
• ARM partner may perpetually design and manufactureARM-based
products
• Term license
• Design a limited number of ARM-based products within a specified
time period (usually 3 years)
• Perpetual manufacturing rights
• Per use license
• Selected ARM IP, right to design a single ARM-technologyproduct
within a specified time frame (3 years)
• Manufacturing rights perpetual
• University “DesignStart” Program
• Some physical and selected processor IP down-loadable for
academic study
ARM PROCESSOR FOUNDRY

PROGRAM
• Fabless semiconductor companies design ARM-based SoCs
with approved ARM semiconductor foundry (90nm to 180nm)
• Design Kit
Fabless IP
• Design Flow Guide Foundry
designer Provider
• ARM processor deliverables
• Design Sign-off (Simulation) Models (DSMs) and Test Vectors
• AMBA Design Kit
• RealView Development Suite
• Powerful JTAG-based run control device for non-intrusive debug of
embedded processors
• RealView Integrator® Development Platform Training, support and
maintenance.
• Available processors:
• ARM922, ARM946, ARM926EJ
• Provided as hard macrocells
CORTEX A9 SYSTEM
IP
Interconnect SoC components
Description AMBA Bus System IP Components
Advanced AMBA3
AXI NIC-301, PL301
Interconnect IP
DMA Controller AXI DMA-330 , PL330
Level 2 Cache Controller AXI L2C-310 , PL310
Dynamic Memory
AXI DMC-340 , PL340
Controller
DDR2 Dynamic Memory
AXI DMC-342
Controller
Static Memory Controller AXI SMC-35x , PL35x
TrustZone Address
AXI PL380
Space Controller
CoreSight™ Design Kit ATB CDK-11
ARM ADVANCED MICROCONTROLLERBUS

ARCHITECTURE (AMBA)
• On-chip interconnect specification for SoC
• Promotes re-use by defining a common backbone for SoC modules using standard
bus architectures
AHB – Advanced High-performance Bus (system backbone)
High-performance, high clock freq. modules
Processors to on-chip memory, off-chip memory interfaces
APB – Advanced Peripheral Bus
Low-power peripherals
Reduced interface complexity
ASB – Advanced System Bus
High performance alternate to AHB
AXI – Advanced eXtensible Interface
ACE – AXI Coherency Extension
ATB – Advanced Trace Bus
EXAMPLE AMBA
SYSTEM

NXP LPC2292
Microcontroller
ARM buses
CORELINK PERIPHERALS FOR

AMBA
“CoreLink” =
interconnect +
memory controllers
for Cortex/Mali
ARM DEBUGARCHITECTURE
(FOR CORTEX: “CORESIGHT” DEBUG &
TRACE IP)

SOC DESIGN PROCESS

• Customer
requirements
• System
specification
• Architecture design Model, simulate,
Hardware vs. software
and evaluate
at each stage
• Component design
• Integration
• Verification
• Manufacture
• Test
SOC
DESIG
N
FLOW
TYPICAL DESIGN FLOW

TASKS
Jouni Tomberg/TUT
HIGH-LEVEL PERFORMANCE
MODELING
• Identify Workloads
• Based on target market
• Standard benchmarks (spec, EEMBC)
• O/S based “real” benchmarks – browser, real apps
• Performance Models
• C-based, highly configurable
• Internally developed (no EDA vendor)
• Fast Instruction-Set Based Model
• No timing information, but very fast
• Used for statistics collection and coarse algorithm
development (i.e. branch prediction scheme, load/store
address patterns)
• Abstracted Pipeline
• Reasonably accurate, longer development time
• More specific to microarchitecture
HIGHER LEVELS OFABSTRACTION FOR

SOC
• ESL (Electronic system level)
• RTL (register transfer level) to TLM (transaction-level modeling)
• VHDL to SystemC to UML
• HW/SW co-design
• Simulation models/emulators of hardware to develop software
while hardware is being developed
• Need new tools
• Consider the whole system
• Large optimization potential
• Combination of formal, semi-formal and non formal techniques

UNIT
RTL
• Synthesizable HDL models
• Split work into units based on functionality
• Verilog language of choice
• Write low-level constructs only (assign, case)
• Why?
• Portability; we target multiple partners and have to target
• ‘lowest-common denominator’ design tools
• Know your RTL! Easier to count gates “on-the-fly”
• Orderly bring-up; integration as soon as possible

UNIT VALIDATION VS. TOP LEVELVALIDATION
• Validation is done at both the unit- and top-level. Both are

important and doing one isn’t a substitute for doing the other!
• Unit Level Pro’S

• Faster runtimes (more cycles -> more throughput)
• Easier to generate “strange” corner case stimulus
• Top Level Pro’S

• Interfaces between units are tested
• Stimulus re-use; often top level tests are assembly and can be ported
from other projects
• This is what is being delivered!
• Performance validation

VALIDATI
ON
• Stimulus
• random – RIS, traffic generators for system
• directed – assembly language tests to check specific features
• Irritators
• artificial constraints to stress certain features
• i.e. 1 entry TLB to test table walk logic, forced stalls to test queues
• Assertions
• constantly check that logic cannot do things specified as “illegal”
• i.e. bus protocol checkers
• Formal
• uses properties to check that system can’t get into certain state via
sequence (lots of constraints required)
• lots of research ongoing about formal

VALIDATION -
COVERAGE
• How do I know that I’ve tested everything?
• Coverage provides validation metrics
• Line Coverage
• hit all RTL lines (easy to run)
• Condition Coverage
• hit all RTL terms (easy to run)
• Functional Coverage
• Only way to determine sequences hit
• Require coverage points to be written
• For example, test pipeline flush under other stall conditions (Cache
miss, TLB miss…)
• RTL unit designer and validation person collaborate to determine
“points” or “matrices”

VALIDATION –
SIMULATION/EMULATION
• Software simulation – compile RTL and
testbench
• testbench can be Verilog/VHDL or newer
extensions (SystemVerilog)
• slow – 100’s of Hz, slower if simulating multi-
core system
• full visibility (dump waveforms) – but this is
even slower
• best for debugging/rapid turnaround
• Emulation
• FPGA – moderate $, large setup time, 1’s of
MHz, low to no visibility into failures
• Quickturn/hardware emulator – big $, large
capacity, 1 MHz
• Can do O/S boots and complex system validation
• Visibility – can see all RTL signals
• Can use virtual device drivers for peripherals
(LCD)
ARM DESIGN SIMULATION MODELS(DSM)
• HDL behavioral models of ARM cores

• for functional and “in some cases, timing” simulation
• derived from ARM core RTLcode
• full device functionality
• register visibility
• configure cache and memory sizes
• compatible with VHDL/Verilog simulators (ex. ModelSim)
• Back-annotation capable, timing accurate
• accept timing through SDF files
• min/typ/max pin-to-pin delays
• setup/hold/pulse checks
• Also called “Design Sign-Off Models”
• generated from technology-specific netlist of a core
ARM DSM SIMULATION

STRUCTURE
Compiled, with
HDL “wrappers”
ARM DSM User Manual

IMPLEMENTATION
STYLE
• Custom
• Squeeze last % of performance from design
• Larger teams required
• Best suited to datapath elements:
• adders
• memories
• search [CAM] structures; reservation stations
• Automated Flow
• Synthesis, place and route
• Time to market
• Tools have gotten pretty good
• Dependent on good libraries (standard cell)
• Initial RTL is portable between processes
These are not mutually exclusive; even teams that use “custom” design
will use automated flow for non-critical or control blocks.

STANDARD
CELLS
• Important to have rich set of standard cells for synthesis tool
• drive strengths
• complex gates (for area)
• biased threshold (faster P, faster N)
• Static Power (leakage) minimization
• This power is burned when doing NOTHING!
• Multi-Vt
• Incremental cost; 4-5 more masks out of 45 (implant)
• higher Vt – slower, but less leakage
• lower Vt – faster, but MUCH more leakage (use sparingly if at all)
• Long channel
• Characterization
• Synthesis – function, pins, timing, power
• Place and route – pin location, blockages, power rails (abstracts)

IMPLEMENTATION STEP -
SYNTHESIS
• Maps RTL to gates (standard cells) – “netlist”
• Constraints – input/output arrival time, drive strength, load, physical
floorplan
• Logic optimization – moves early arriving signals to front of stack, late
to back of stack
• Selects arithmetic operators based on timing requirements (i.e. +
types)
• Cost function – can end up local minima

IMPLEMENTATION – PLACE AND

ROUTE

IMPLEMENTATION
FEEDBACK

SOC
INTEGRATION
• Once core is built, integrated with other cores into chip
• Many millions of gates; can we abstract this out?
• System Design
• SystemC model – transaction level, no timing
• Can chain processor/peripheral models together to test OS
• Cycle-level system simulation
• compiled model
• no internal visibility
• faster runtimes
• smaller, simulator won’t run out of memory!

ARM DEVELOPMENT
TOOLS
• Software development
• ARM Development Studio 5 (DS-5)
• For ASICs and ASSPs
• Compilers, debugger, system performance analyzer, real-time system
simulator
• Keil Microcontroller Development Kit (MDK)
• For embedded microcontrollers
• Cortex M, Cortex-R4, ARM7, ARM 9 devices
• Compilers, debugger, simulators
• Models
• ARM Fast Models – virtual platforms for software development
before silicon
CONCLUSIO
NS
• SoC design requires different design approach than
traditional ASICs
• More modeling & simulation at higher abstraction levels
• Heavy use of IP, re-usable modules, platform-based
design
• SoC design team must work with IP vendor and foundry
• Use platform design & standard interfaces between IP
• Hardware/software co-design
• Many design challenges

Systems On Chip (SoC)

Uploaded by

Copyright:

Available Formats

Systems On Chip (SoC)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Systems On Chip (SoC)

Uploaded by

Copyright:

Available Formats

SYSTEMS ON CHIP (SOC)

iPhone 4 circuit board (with A4 SoC)

EXAMPLE: BLOOD PRESSURE MONITORSOC

SOC DESIGN WITH RE-USABLE IP

ARM IP (ARM MAKES NO

Joe Bungo: CPU Design Concept to SoC

ARM CORTEX-A9 MPCOREPERFORMANCE

ARM PROCESSOR FOUNDRY

ARM ADVANCED MICROCONTROLLERBUS

Joe Bungo: CPU Design Concept to SoC

CORELINK PERIPHERALS FOR

Joe Bungo: CPU Design Concept to SoC

SOC DESIGN PROCESS

TYPICAL DESIGN FLOW

HIGHER LEVELS OFABSTRACTION FOR

Joe Bungo: CPU Design Concept to SoC

• Orderly bring-up; integration as soon as possible

Joe Bungo: CPU Design Concept to SoC

UNIT VALIDATION VS. TOP LEVELVALIDATION

• Validation is done at both the unit- and top-level. Both are

• Unit Level Pro’S

• Top Level Pro’S

Joe Bungo: CPU Design Concept to SoC

Joe Bungo: CPU Design Concept to SoC

Joe Bungo: CPU Design Concept to SoC

ARM DESIGN SIMULATION MODELS(DSM)

• HDL behavioral models of ARM cores

ARM DSM SIMULATION

ARM DSM User Manual

Joe Bungo: CPU Design Concept to SoC

Joe Bungo: CPU Design Concept to SoC

Joe Bungo: CPU Design Concept to SoC

IMPLEMENTATION – PLACE AND

Joe Bungo: CPU Design Concept to SoC

Joe Bungo: CPU Design Concept to SoC

Joe Bungo: CPU Design Concept to SoC

You might also like