Professional Documents
Culture Documents
Performance Verification
CPU
Image
Processor
Memory
System
and
Power
Control
Fabric
Fabric
Camera
Display
Controller
SD Card
Controller
BFM
BFM
BFM
test.c
test.c
test.c
IP Integration Tests
Compiler
Performance Verification
Testbench
SoC
RTL
CPU
Image
Processor
Memory
System
and
Power
Control
Fabric
Fabric
Camera
Display
Controller
SD Card
Controller
BFM
BFM
BFM
test.c
test.c
test.c
TrekSoC
Driver Scenarios
Application Scenarios
System Scenarios
events.rc
test.c
test.c
Compiler
Testbench
Connectivity Tests
IP Integration Tests
System Use Cases
Concurrency
Coherency
System & Power Management
Performance Verification
TrekBox
SoC
RTL
CPU
Image
Processor
Memory
System
and
Power
Control
Fabric
mailbox
Fabric
Camera
Display
Controller
SD Card
Controller
BFM
BFM
BFM
IP
test.c
test.c
test.c
TrekSoC
Cam
SD
events.rc
test.c
test.c
Compiler
Testbench
Connectivity Tests
IP Integration Tests
System Use Cases
Concurrency
Coherency
System & Power Management
Performance Verification
TrekBox
SoC
RTL
CPU
Image
Processor
Memory
System
and
Power
Control
Fabric
mailbox
Fabric
Camera
Display
Controller
SD Card
Controller
BFM
BFM
BFM
Display
Display
Controller
SD
Card
SD Card
Controller
Write
Image
Processor
Decode
SD Card
Controller
Read
SD
Card
Camera
CCD
Image
Processor
Encode
TrekSoC generates
automatically from the
scenario models
Well commented
Multi-threaded
Multi-processor
Does mean, nasty things to
try to break the SoC
10
11
System Hookup
IP Integration
Multi-Master Concurrency
Multi-CPU Interactions
Data Ordering
Cache Coherency
Virtual Memory
Clocks and Power
Asynchronous Events
No testbench-CPU links
Full-chip simulation even slower with CPU running code
Production is well-behaved and does not hit corner cases
Production code is rarely available before SoC tape-out
12
Summary
Standalone IP verification is not sufficient for an SoC
TrekSoC automatically generates C test cases
Run on the embedded processors and link to testbench
Exercise deep corner cases and measure performance
13
14