Checking for TLM-2.0 Compliance - Why Bother? Dr. Andrea Kroll VP Marketing and Business Development JEDA Technologies, Inc.

Transcription

1 Checking for TLM-2.0 Compliance - Why Bother? Dr. Andrea Kroll VP Marketing and Business Development JEDA Technologies, Inc.

2 Agenda Model Integration Challenges TLM2.0 Rules Beyond Transport Calls OSCI TLM2.0 Rule Violation Examples How to debug interoperability issues? Automated Compliance Checking and reports Summary 2

3 Today s Reality Model Integration Challenges Component Development Component Integration + Component and Platform debugging HW Implementation unpredictable, ad-hoc process Initial Architecture Definition SW Development using Virtual Platform Expected behavior Component Development Component Integration + Component and Platform debugging Architecture Performance Validation HW Implementation + Verification SW Development using Virtual Platform HW/SW Integration Predictable Process 3 3

4 Modeling Case Study > 50% 4 4

5 TLM2.0 Rules: The Goals Ensure interoperability between components from different sources Create safe data communication Base Protocol Rule Ensure maximal interoperability between transaction level models of components that interface to memory-mapped buses. Maximize coverage of features in today s interconnect architectures Minimize need for adapters 5

6 TLM2.0 System Overview Communication Start Point Forward Path Communication Path Forward Path Communication End Point first initiator/target pair second initiator/target pair E_Initiator E_Initiator Initiator1 Backward Path Backward Path Global and local rules defined for Expected Interconnect phase transmissions Initialization Interconnect1and restricted access to GP Memory management Timing annotation and decoupling Transaction Path DMI and debug interface E_Initiator E_Initiator Target1 6

7 Generic Payload Rule Violation Example Rule 6.7: default value and modifiability Initiator2 (TLM2.0 user manual page 78) Initiator1 Interconnect1 Target1 Target1 Out Addr Src reference reference reference 0x10 0x04 11 Transaction Object 0x11 22 GP Addr:0x1 0x11 0x04 Data 7

8 Base Protocol Rule Violation Example Rule 7.2.4b: For the base protocol, an initiator shall not start a new transaction through a given socket with phase BEGIN_REQ until it has received END_REQ or BEGIN_RESP from the target for the immediately preceding transaction Initiator2???? (TLM2.0 User manual page 112) Initiator1 Interconnect1 Target1 Target1 Out Addr Src reference reference reference 0x10 0x04 0x Transaction Object 0x11 2 GP Addr:0x1 0x04 0x11 Data 8

9 Finding Interoperability Problems Transaction Trace Verbose Transaction Trace Message Sequence Charts (MSC) 9

10 Finding Interoperability Problems 10

11 Automated Compliance Checking JEDA TLM 2.0 Checker Multi-Hop Checker Single-Hop Checker Single-Hop Checker Design Example Initiator1 Interconnect1 Target1 11

12 Checker Reports Detailed Error report Summary Report 12

13 Summary TLM2.0 Compliance is critical for interoperability and safe communication Quickly identify interoperability problems with compliance checking Reduce risk for model bring-up and debugging time with automatic interoperability error detection TLM2.0 is real and ready for commercial adoption 13