1 / 116

OCP-IP Governing Steering Committee Meeting Teleconference August 13, 2009

OCP-IP Governing Steering Committee Meeting Teleconference August 13, 2009.

enye
Télécharger la présentation

OCP-IP Governing Steering Committee Meeting Teleconference August 13, 2009

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. OCP-IPGoverning Steering Committee MeetingTeleconferenceAugust 13, 2009

  2. 5:00- 5:10 AM: Call to Order, Introductions, Agenda Review, Last Minutes (Ian)5:10- 5:15 AM: Next GSC Meeting (Ian) 5:15- 5:25 AM: Discussion on Circuit Sutra Proposal and Voting - Program Execution (James)5:25- 5:40 AM: Metadata WG Update (Prashant) 5:40- 6:00 AM: System Level Design WG Update (Mark/James)6:00- 6:15 AM: NoC BWG Update (Erno) 6:15- 6:35 AM: Specification WG Status (Drew) - OCP v3.0 Member Review Update (Drew) - Schedule / Participation OCP v4.0 (Drew) - Performance Measurements (Drew)6:35- 6:50 AM: Motion to Adjourn/ Break/ Reconvene 6:50- 6:55 AM: FVWG Discussion (Ian) 6:55- 7:10 AM: Debug WG Update (Bob / Neal) 7:10- 7:15 AM: Technical Vision WG Status / Restated (Ian) 7:15- 7:25 AM: Progress in Asia (Ian) 7:25- 7:30 AM: 2009 Goals 7:30- 8:30 AM: AI Review (Ian) 8:30- 8:40 AM: PR Update (Joe) 8:40- 8:55 AM: Motion to Adjourn/ Break/ Reconvene 8:55- 9:05 AM: Recruiting Update (Joe) 9:05- 9:15 AM: - Budget/Cash Flow Update (Ian) 9:15- 9:35 AM: Administrative Update (VitalCom) 9:35- 9:40 AM: Enabling Resolution (Ian)9:40- 9:55 AM: Operations Transition (Ian/All) 9:55 AM: Motion to Adjourn

  3. Call to Order and Agenda Review (Ian) • Call to Order • Welcome from the President • Review Agenda • Any additional items?

  4. Vote to Approve Last GSC Meeting Minutes • 30th GSC Meeting • April 23, 2009 via teleconference

  5. 5:00- 5:10 AM: Call to Order, Introductions, Agenda Review, Last Minutes (Ian)5:10- 5:15 AM: Next GSC Meeting (Ian) 5:15- 5:25 AM: Discussion on Circuit Sutra Proposal and Voting - Program Execution (James)5:25- 5:40 AM: Metadata WG Update (Prashant) 5:40- 6:00 AM: System Level Design WG Update (Mark/James)6:00- 6:15 AM: NoC BWG Update (Erno) 6:15- 6:35 AM: Specification WG Status (Drew) - OCP v3.0 Member Review Update (Drew) - Schedule / Participation OCP v4.0 (Drew) - Performance Measurements (Drew)6:35- 6:50 AM: Motion to Adjourn/ Break/ Reconvene 6:50- 6:55 AM: FVWG Discussion (Ian) 6:55- 7:10 AM: Debug WG Update (Neal / Bob) 7:10- 7:15 AM: Technical Vision WG Status / Restated (Ian) 7:15- 7:25 AM: Progress in Asia (Ian) 7:25- 7:30 AM: 2009 Goals 7:30- 8:30 AM: AI Review (Ian) 8:30- 8:40 AM: PR Update (Joe) 8:40- 8:55 AM: Motion to Adjourn/ Break/ Reconvene 8:55- 9:05 AM: Recruiting Update (Joe) 9:05- 9:15 AM: - Budget/Cash Flow Update (Ian) 9:15- 9:35 AM: Administrative Update (VitalCom) 9:35- 9:40 AM: Enabling Resolution (Ian)9:40- 9:55 AM: Operations Transition (Ian/All) 9:55 AM: Motion to Adjourn

  6. Next GSC Meeting (Ian) • 32nd GSC Meeting • Should this be telecon only? • We DO need occasional face-to-face meetings • Face to face seems necessary given CY2010 will be upon us • Date around week of November 9th?

  7. 5:00- 5:10 AM: Call to Order, Introductions, Agenda Review, Last Minutes (Ian)5:10- 5:15 AM: Next GSC Meeting (Ian) 5:15- 5:25 AM: Discussion on Circuit Sutra Proposal and Voting - Program Execution (James)5:25- 5:40 AM: Metadata WG Update (Prashant) 5:40- 6:00 AM: System Level Design WG Update (Mark/James)6:00- 6:15 AM: NoC BWG Update (Erno) 6:15- 6:35 AM: Specification WG Status (Drew) - OCP v3.0 Member Review Update (Drew) - Schedule / Participation OCP v4.0 (Drew) - Performance Measurements (Drew)6:35- 6:50 AM: Motion to Adjourn/ Break/ Reconvene 6:50- 6:55 AM: FVWG Discussion (Ian) 6:55- 7:10 AM: Debug WG Update (Neal / Bob) 7:10- 7:15 AM: Technical Vision WG Status / Restated (Ian) 7:15- 7:25 AM: Progress in Asia (Ian) 7:25- 7:30 AM: 2009 Goals 7:30- 8:30 AM: AI Review (Ian) 8:30- 8:40 AM: PR Update (Joe) 8:40- 8:55 AM: Motion to Adjourn/ Break/ Reconvene 8:55- 9:05 AM: Recruiting Update (Joe) 9:05- 9:15 AM: - Budget/Cash Flow Update (Ian) 9:15- 9:35 AM: Administrative Update (VitalCom) 9:35- 9:40 AM: Enabling Resolution (Ian)9:40- 9:55 AM: Operations Transition (Ian/All) 9:55 AM: Motion to Adjourn

  8. Circuit Sutra Voting and Program Execution OCP GSC meeting August 13, 2009

  9. Circuit Sutra Proposal • James made the Circuit Sutra proposal • As of 8/10 we have “yes” votes from all GSC members; record now • Given approved motion, need to agree who monitors Circuit Sutra work progress and approves deliverables for membership access

  10. 5:00- 5:10 AM: Call to Order, Introductions, Agenda Review, Last Minutes (Ian)5:10- 5:15 AM: Next GSC Meeting (Ian) 5:15- 5:25 AM: Discussion on Circuit Sutra Proposal and Voting - Program Execution (James)5:25- 5:40 AM: Metadata WG Update (Prashant) 5:40- 6:00 AM: System Level Design WG Update (Mark/James)6:00- 6:15 AM: NoC BWG Update (Erno) 6:15- 6:35 AM: Specification WG Status (Drew) - OCP v3.0 Member Review Update (Drew) - Schedule / Participation OCP v4.0 (Drew) - Performance Measurements (Drew)6:35- 6:50 AM: Motion to Adjourn/ Break/ Reconvene 6:50- 6:55 AM: FVWG Discussion (Ian) 6:55- 7:10 AM: Debug WG Update (Neal / Bob) 7:10- 7:15 AM: Technical Vision WG Status / Restated (Ian) 7:15- 7:25 AM: Progress in Asia (Ian) 7:25- 7:30 AM: 2009 Goals 7:30- 8:30 AM: AI Review (Ian) 8:30- 8:40 AM: PR Update (Joe) 8:40- 8:55 AM: Motion to Adjourn/ Break/ Reconvene 8:55- 9:05 AM: Recruiting Update (Joe) 9:05- 9:15 AM: - Budget/Cash Flow Update (Ian) 9:15- 9:35 AM: Administrative Update (VitalCom) 9:35- 9:40 AM: Enabling Resolution (Ian)9:40- 9:55 AM: Operations Transition (Ian/All) 9:55 AM: Motion to Adjourn

  11. Meta Data WG Update Prashant Karandikar(Texas Instruments), August 13, 2009

  12. 2009 Goals given to the WG by the GSC • Spirit interoperability • Implement OCP within existing Spirit format • Spirit enhancements • Propose and drive modifications into IP-XACT standard • Core compatibility reports • Ability to automatically compare OCP interface configurations • Release IP-XACT checkers to OCP-IP community • Enhance for OCP 3.0

  13. People involved • Nokia: Vesa Lahtinen • TI: Prashant Karandikar, Anne-Francoise Joanblanq, Olivier Sagner, Bob Maaraoui, James Aldis • Sonics: Kamil Synek, Pascal Chauvet, Drew Wingard • Synopsys: Mark Noll • STMicroelectronics: Serge Hustin, Christophe Amerijckx • Magillem Design Services: Cyril Spasevski, Stephane Guntz • Toshiba ( Yasuhiko ) • OCP-IP: Ian Mackintosh • Mentor Graphics later? • John Wilson already on the reflector, waiting for a Mentor participant to the teleconferences

  14. Background • OCP-IP has been talking about an IP-XACT description for several years, now we just simply need to provide it in 2008. Even if it means making some compromises. • Clean and elegant solution that fits all OCP users should be the goal, but it has to be something that complies with IP-XACT 1.4 and we need to get ok from key tool providers so that their tools will be able to use the description. • We should not make a monster. If somebody is only operating on small fixed OCP subsets, the full configurability of OCP should be hidden somehow. Still the description should also support the full set of configuration options. • Eventually IP-XACT description should replace rtl.conf.

  15. Spirit Interoperability Implement OCP within existing spirit format • Use the Magillem/Sonics proposal as basis • ST-style checking is used to validate an IP description Status : • Vendor Extension Schema for Busdef and Abstraction Definition have been defined and available in SVN repository. • OCP configuration Checker is also available in SVN repository. • Both of above deliveries have been agreed within MDWG. Next Steps • Documentation ( 3Q/4Q09 )

  16. Spirit Enhancement Propose and drive modifications into IP-XACT standard • Proposal for configurable bus interfaces was not accepted for IP-XACT1.5 • Spirit Consortium SWG agreed to put staging process for configurable bus interface solution , it may become part of the schema sometime later. • Pascal , Stephan & Prashant talked with Dr. Gary on 28th July

  17. Core Compatibility report Ability to automatically compare OCP interface configurations • Check the inter-interface consistency (Current configuration compliance checks) • Check consistency of a connected master / slave interface pair (Current interface interoperability checks) • Check consistency of the ports and parameters • Generate the rtl.conf file out of configured IP-XACT parameter list (legacy support) • Configure IP-XACT parameter list based on an rtl.conf file and give rtl.conf files of OCP standard profiles as examples (legacy support) • This activity is expected to happen during Q2/Q3 09

  18. OCP3.0 Add OCP 3.0 signals and parameters to bus definition schema • Activity duration is Q3/Q4 of 2009

  19. Release of IP-XACT checker to OCP-IP community • Steps for IP-XACT checker release • OCP vendor extension schema & checker approval by MDWG members. • Documentation of the schema & checker has been approved by MDWG members • Transfer of checker generation script from ST is still pending.

  20. 5:00- 5:10 AM: Call to Order, Introductions, Agenda Review, Last Minutes (Ian)5:10- 5:15 AM: Next GSC Meeting (Ian) 5:15- 5:25 AM: Discussion on Circuit Sutra Proposal and Voting - Program Execution (James)5:25- 5:40 AM: Metadata WG Update (Prashant) 5:40- 6:00 AM: System Level Design WG Update (Mark/James)6:00- 6:15 AM: NoC BWG Update (Erno) 6:15- 6:35 AM: Specification WG Status (Drew) - OCP v3.0 Member Review Update (Drew) - Schedule / Participation OCP v4.0 (Drew) - Performance Measurements (Drew)6:35- 6:50 AM: Motion to Adjourn/ Break/ Reconvene 6:50- 6:55 AM: FVWG Discussion (Ian) 6:55- 7:10 AM: Debug WG Update (Neal / Bob) 7:10- 7:15 AM: Technical Vision WG Status / Restated (Ian) 7:15- 7:25 AM: Progress in Asia (Ian) 7:25- 7:30 AM: 2009 Goals 7:30- 8:30 AM: AI Review (Ian) 8:30- 8:40 AM: PR Update (Joe) 8:40- 8:55 AM: Motion to Adjourn/ Break/ Reconvene 8:55- 9:05 AM: Recruiting Update (Joe) 9:05- 9:15 AM: - Budget/Cash Flow Update (Ian) 9:15- 9:35 AM: Administrative Update (VitalCom) 9:35- 9:40 AM: Enabling Resolution (Ian)9:40- 9:55 AM: Operations Transition (Ian/All) 9:55 AM: Motion to Adjourn

  21. SLD Working Group Update Mark Burton (Greensocs), August 13, 2009

  22. Summary • Release of kit achieved • No negative feedback to date, some suggested improvements from WG members • Issues: • Progress on releases very slow due to lack of membership • Circuit Sutra offered some useful donation, but this seems to be stalled? • Should we move to support OSCI CCI (as we did TLM)? • Protocol checking never happened - GreenSocs announced at DATE that it will provide a protocol checker, could this be used for OCP?

  23. OCP 3.0 • This is on our roadmap for this year • Some forward movement, still hard work to do. • Upcoming release will support some of the easier features of OCP 3.0

  24. SLD WG Status

  25. The SLD Mid-Term Vision - unchanged • OUR KIT IS HIGH QUALITY, AND STABLE.. • Ensure that OCP users have a 'complete' modelling infrastructure available • multiple levels of abstraction (pure-functional to cycle-accurate) and use models (software development, architecture exploration, etc) • completeness means • bus interface , performance monitoring interface ,system debug interface and configuration interface • Make this modelling infrastructure standards compliant. • E.g. drive existing OCP-IP experience and expertise into OSCI-TLM • Maintain alignment between OSCI-TLM OCP-IP

  26. 5:00- 5:10 AM: Call to Order, Introductions, Agenda Review, Last Minutes (Ian)5:10- 5:15 AM: Next GSC Meeting (Ian) 5:15- 5:25 AM: Discussion on Circuit Sutra Proposal and Voting - Program Execution (James)5:25- 5:40 AM: Metadata WG Update (Prashant) 5:40- 6:00 AM: System Level Design WG Update (Mark/James)6:00- 6:15 AM: NoC BWG Update (Erno)6:15- 6:35 AM: Specification WG Status (Drew) - OCP v3.0 Member Review Update (Drew) - Schedule / Participation OCP v4.0 (Drew) - Performance Measurements (Drew)6:35- 6:50 AM: Motion to Adjourn/ Break/ Reconvene 6:50- 6:55 AM: FVWG Discussion (Ian) 6:55- 7:10 AM: Debug WG Update (Neal / Bob) 7:10- 7:15 AM: Technical Vision WG Status / Restated (Ian) 7:15- 7:25 AM: Progress in Asia (Ian) 7:25- 7:30 AM: 2009 Goals 7:30- 8:30 AM: AI Review (Ian) 8:30- 8:40 AM: PR Update (Joe) 8:40- 8:55 AM: Motion to Adjourn/ Break/ Reconvene 8:55- 9:05 AM: Recruiting Update (Joe) 9:05- 9:15 AM: - Budget/Cash Flow Update (Ian) 9:15- 9:35 AM: Administrative Update (VitalCom) 9:35- 9:40 AM: Enabling Resolution (Ian)9:40- 9:55 AM: Operations Transition (Ian/All) 9:55 AM: Motion to Adjourn

  27. NoC Benchmarking WG Update Erno Salminen(Tampere University Technology), August 13, 2009

  28. Current status • Simulation tool Transaction Generator prepared open source release • Expected release Sept-Oct ’09 • Snapshots will be available from OCP-IP site and full version history from elsewhere • Collaboration proposal sent EEMBC • EEMBC President Markus Levy seemed very positive towards this • Has already been discussed in EEMBC board but formal decision pending

  29. Current status (2) • New member: prof. Omar Hammami, ENSTA, France • Strong experience with multiprocessor systems on FPGAs • Will take lead on profiling EEMBC MultiBench applications • Guideline document being prepared • Dr. Zhonghai Lu (KTH, Sweden)

  30. 5:00- 5:10 AM: Call to Order, Introductions, Agenda Review, Last Minutes (Ian)5:10- 5:15 AM: Next GSC Meeting (Ian) 5:15- 5:25 AM: Discussion on Circuit Sutra Proposal and Voting - Program Execution (James)5:25- 5:40 AM: Metadata WG Update (Prashant) 5:40- 6:00 AM: System Level Design WG Update (Mark/James)6:00- 6:15 AM: NoC BWG Update (Erno) 6:15- 6:35 AM: Specification WG Status (Drew) - OCP v3.0 Member Review Update (Drew) - Schedule / Participation OCP v4.0 (Drew) - Performance Measurements (Drew)6:35- 6:50 AM: Motion to Adjourn/ Break/ Reconvene 6:50- 6:55 AM: FVWG Discussion (Ian) 6:55- 7:10 AM: Debug WG Update (Neal / Bob) 7:10- 7:15 AM: Technical Vision WG Status / Restated (Ian) 7:15- 7:25 AM: Progress in Asia (Ian) 7:25- 7:30 AM: 2009 Goals 7:30- 8:30 AM: AI Review (Ian) 8:30- 8:40 AM: PR Update (Joe) 8:40- 8:55 AM: Motion to Adjourn/ Break/ Reconvene 8:55- 9:05 AM: Recruiting Update (Joe) 9:05- 9:15 AM: - Budget/Cash Flow Update (Ian) 9:15- 9:35 AM: Administrative Update (VitalCom) 9:35- 9:40 AM: Enabling Resolution (Ian)9:40- 9:55 AM: Operations Transition (Ian/All) 9:55 AM: Motion to Adjourn

  31. Specification WG Update Drew Wingard(Sonics Inc), August 13, 2009

  32. Specification WG 2009 Plan

  33. Specification WG Status • 3.0 Member Review draft • Substantial review comments received • Toshiba still intends more • No substantive external (outside WG) review of coherence • Next step: evaluate review comments • Coherence ones most substantive/contentious • Expect end September consensus

  34. Next Specification Releases • OCP 3.0 (Member Review: May 09) • Focus is cache coherence extensions (major) • Verification guidelines delayed until later release • Also • Power management signaling (disconnect) • Write response extension • Profile 3 • Full Release: October 09?

  35. Specification WG Issues • Cache coherence extensions • No motivation to cover in CoreCreator • Little clear drive for work beyond 3.0

  36. CoreCreator 4.0 (The old version) Status Check • Need to EOL this year • Only covers OCP 1.x and 2.0 • Getting very old (support more difficult) • Suggestion: • No new keys after July ’09 (~ 1 year after CC 2) • All keys expired by July ’10 • Can we go faster?

  37. OCP 4.0 Status • No progress in WG • Ian out prospecting • Drew needs to engage as well • Ian’s OCP 4.0 status • … • Suggest we plan 4Q’09 start

  38. Performance Measurements? • Don’t remember this one…

  39. 5:00- 5:10 AM: Call to Order, Introductions, Agenda Review, Last Minutes (Ian)5:10- 5:15 AM: Next GSC Meeting (Ian) 5:15- 5:25 AM: Discussion on Circuit Sutra Proposal and Voting - Program Execution (James)5:25- 5:40 AM: Metadata WG Update (Prashant) 5:40- 6:00 AM: System Level Design WG Update (Mark/James)6:00- 6:15 AM: NoC BWG Update (Erno) 6:15- 6:35 AM: Specification WG Status (Drew) - OCP v3.0 Member Review Update (Drew) - Schedule / Participation OCP v4.0 (Drew) - Performance Measurements (Drew)6:35- 6:50 AM: Motion to Adjourn/ Break/ Reconvene6:50- 6:55 AM: FVWG Discussion (Ian) 6:55- 7:10 AM: Debug WG Update (Neal / Bob) 7:10- 7:15 AM: Technical Vision WG Status / Restated (Ian) 7:15- 7:25 AM: Progress in Asia (Ian) 7:25- 7:30 AM: 2009 Goals 7:30- 8:30 AM: AI Review (Ian) 8:30- 8:40 AM: PR Update (Joe) 8:40- 8:55 AM: Motion to Adjourn/ Break/ Reconvene 8:55- 9:05 AM: Recruiting Update (Joe) 9:05- 9:15 AM: - Budget/Cash Flow Update (Ian) 9:15- 9:35 AM: Administrative Update (VitalCom) 9:35- 9:40 AM: Enabling Resolution (Ian)9:40- 9:55 AM: Operations Transition (Ian/All) 9:55 AM: Motion to Adjourn

  40. Break

  41. 5:00- 5:10 AM: Call to Order, Introductions, Agenda Review, Last Minutes (Ian)5:10- 5:15 AM: Next GSC Meeting (Ian) 5:15- 5:25 AM: Discussion on Circuit Sutra Proposal and Voting - Program Execution (James)5:25- 5:40 AM: Metadata WG Update (Prashant) 5:40- 6:00 AM: System Level Design WG Update (Mark/James)6:00- 6:15 AM: NoC BWG Update (Erno) 6:15- 6:35 AM: Specification WG Status (Drew) - OCP v3.0 Member Review Update (Drew) - Schedule / Participation OCP v4.0 (Drew) - Performance Measurements (Drew)6:35- 6:50 AM: Motion to Adjourn/ Break/ Reconvene 6:50- 6:55 AM: FVWG Discussion (Ian)6:55- 7:10 AM: Debug WG Update (Neal / Bob) 7:10- 7:15 AM: Technical Vision WG Status / Restated (Ian) 7:15- 7:25 AM: Progress in Asia (Ian) 7:25- 7:30 AM: 2009 Goals 7:30- 8:30 AM: AI Review (Ian) 8:30- 8:40 AM: PR Update (Joe) 8:40- 8:55 AM: Motion to Adjourn/ Break/ Reconvene 8:55- 9:05 AM: Recruiting Update (Joe) 9:05- 9:15 AM: - Budget/Cash Flow Update (Ian) 9:15- 9:35 AM: Administrative Update (VitalCom) 9:35- 9:40 AM: Enabling Resolution (Ian)9:40- 9:55 AM: Operations Transition (Ian/All) 9:55 AM: Motion to Adjourn

  42. Functional Verification WG Update Ian Mackintosh(OCP-IP), August 13, 2009

  43. FVWG Discussion (Ian) • Key issues: • Delayed by implementation schedule of OCP 3.0 • Chairmanship • Gabriele Zarri appointed from Cadence • Proposal for re-engagement • Chair proposes mid-August prompt to reflector • Chair proposes mid-Sept commencement (post vacation) • These dates still good?

  44. 5:00- 5:10 AM: Call to Order, Introductions, Agenda Review, Last Minutes (Ian)5:10- 5:15 AM: Next GSC Meeting (Ian) 5:15- 5:25 AM: Discussion on Circuit Sutra Proposal and Voting - Program Execution (James)5:25- 5:40 AM: Metadata WG Update (Prashant) 5:40- 6:00 AM: System Level Design WG Update (Mark/James)6:00- 6:15 AM: NoC BWG Update (Erno) 6:15- 6:35 AM: Specification WG Status (Drew) - OCP v3.0 Member Review Update (Drew) - Schedule / Participation OCP v4.0 (Drew) - Performance Measurements (Drew)6:35- 6:50 AM: Motion to Adjourn/ Break/ Reconvene 6:50- 6:55 AM: FVWG Discussion (Ian) 6:55- 7:10 AM: Debug WG Update (Neal / Bob) 7:10- 7:15 AM: Technical Vision WG Status / Restated (Ian) 7:15- 7:25 AM: Progress in Asia (Ian) 7:25- 7:30 AM: 2009 Goals 7:30- 8:30 AM: AI Review (Ian) 8:30- 8:40 AM: PR Update (Joe) 8:40- 8:55 AM: Motion to Adjourn/ Break/ Reconvene 8:55- 9:05 AM: Recruiting Update (Joe) 9:05- 9:15 AM: - Budget/Cash Flow Update (Ian) 9:15- 9:35 AM: Administrative Update (VitalCom) 9:35- 9:40 AM: Enabling Resolution (Ian)9:40- 9:55 AM: Operations Transition (Ian/All) 9:55 AM: Motion to Adjourn

  45. OCP-IP Standard Debug Signals for IP-Blocks Neal Stollon(HDL Dynamics), August 13, 2009

  46. OCP-IP Debug Interface Standard Group • (Ex. Toshiba) Bob Uvacek, chair • (ex. MIPS/FS2) Neal Stollon • TI Gilbert Laurenti • Toshiba CY Pei • OCP-IP contacts Brian, Paul, Lisa, Ian Mackintosh Reviewing members • Nexus Neal Stollon • GreenSocs Mark Burton • Cadence Mike Young, Ran Avinun • MIPI Rolf Kuehnis, Gary Swoboda • ITRI / Springsoft Alan Su, Prof. Lee, • SPIRIT Neal Stollon, Debug-WG Chair Anthony Berent, ARM • PLS / Infineon / SPRINT Jens Braunes, Albrecht Mayer • MIPS Bruce Ableidinger • Tensilica Grant Martin

  47. 4 5 6 7 8 9 10 11 12 Ongoing Promote and present OCP debug message in shows and journals • S4D2009 Workshop, ECSI , Sept 24, France OCP slides Neal Stollon June Check OCP 3.0 Standard for compatibility (2 novelties: power, cache) July-Aug Physical Specification, Propose waveforms for OCP signals (delayed) Write Addendum for Power and Cache signals (now) Sep - Oct Publish it inside OCP for greater review --------------------------------------------------------- Searching for new points of engagement with industry and universities Who uses heterogeneous multi-processors? Applications? Biggest barrier to OCP debug dissemination is processor debug interface variability. Characterized and document uP classes of debug functions ! OCP-IP Debug Interface Standard Roadmap 2 0 0 9

  48. Other Debug Activities SPRINT GreenSocs IP-XACT ESL • Tool Level of Integration • SW/EDA Tool level APIs • HW tools level APIs Debug Software SPIRIT P1687 IJTAG • IO Level of Integration • JTAG – different flavors • Nexus 5001 – 2009 rev. • MIPI NIDnT Probe MIPI 1149.7IJTAG TAP • Protocol Level of Integration • Nexus 5001 • Multicore IP & probe APIs • Other Proprietary Nexus Power.org System Level Debug Communications (SoC level run control, Cross-triggers, etc.) Multicore Trace formats OCP • Instrument Level Many vendor/IP solutions • CoreSight™ • MIPS EJTAG • MCDS • Nexus Bus Analyzers Bus Fabric RTL Core Analyzers Core A Core B ITRI

  49. Evolution of Multi-Core Debugging and Link to OCP OCP Debug WG GOAL: Standardized and Commercially available multi-core debug IP block for the OCP interconnect However - Plug and Play Debug remains in the future. Biggest obstacle is wide variability of the debug interface of the processors As example. MCDS debug IP takes 12 man months to adapt to a new processor core. We plan to classify processors due to their debug interface functionality: • Single threaded, multi threaded, outstanding transactions, out of order, cache coherency transactions, … require different debug activities.

More Related