1 / 131

OCP-IP Governing Steering Committee Meeting San Jose, California September 28, 2006

OCP-IP Governing Steering Committee Meeting San Jose, California September 28, 2006.

diallo
Download Presentation

OCP-IP Governing Steering Committee Meeting San Jose, California September 28, 2006

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 MeetingSan Jose, CaliforniaSeptember 28, 2006

  2. 8:15- 8:30 AM: Coffee Available8:30- 8:40 AM: Call to Order, Introductions, Agenda Review, Last Minutes (Ian)8:40- 8:55 AM: Annual Governance Resolution & Elections (Ian) 8:55- 9:00 AM: Next GSC Meeting (Ian) 9:00- 9:25 AM: Functional Verification WG (Steve) - Sponsor Member Upgrades (TrustIC & Aerielogic)9:25- 9:55 AM: Debug WG (Neal)9:55-10:20 AM: System Level Design WG (Mark)10:20-10:40 AM: Motion to Adjourn/ Break/ Reconvene10:40-11:10 AM: Specification WG Status (Drew) - Cache Coherence SG Status (Drew)11:10-11:20 AM: Technical Vision WG Status / Restated (Ian) - NoC Benchmarking WG Sponsor Upgrades - UBC/WSU/KTH/CNU 11:20-11:40 AM: Progress in Asia (Ian) 11:40-12:00 PM: Japan Recruiting Plan (Yoshimori-san) 12:00-1:45 PM: Motion to Adjourn/ Lunch/ Reconvene

  3. 12:00-1:45 PM: Motion to Adjourn/ Lunch/ Reconvene1:45-2:05 PM: 2006 Goals 2:05- 2:50 PM: AI Review (Ian) - ARM Discussion - CoreCreator Update 2:50- 3:10 PM: FY 2007 Budget (Ian)3:10- 3:25 PM: PR Update (Joe) 3:25- 3:35 PM: Recruiting Update (Joe) 3:35- 3:45 PM: Motion to Adjourn/ Break/ Reconvene 3:45- 4:00 PM: Administrative Update (VTM) 4:00- 4:05 PM: Enabling Resolution4:05- 4:20 PM: Collateral Review (VTM)4:20 PM: Motion to Adjourn4:20 PM – 6:30 Spirit Discussion (not part of GSC meeting)

  4. 8:15- 8:30 AM: Coffee Available8:30- 8:40 AM: Call to Order, Introductions, Agenda Review, Last Minutes (Ian)8:40- 8:55 AM: Annual Governance Resolution & Elections (Ian) 8:55- 9:00 AM: Next GSC Meeting (Ian) 9:00- 9:25 AM: Functional Verification WG (Steve) - Sponsor Member Upgrades (TrustIC & Aerielogic)9:25- 9:55 AM: Debug WG (Neal)9:55-10:20 AM: System Level Design WG (Mark)10:20-10:40 AM: Motion to Adjourn/ Break/ Reconvene10:40-11:10 AM: Specification WG Status (Drew) - Cache Coherence SG Status (Drew)11:10-11:20 AM: Technical Vision WG Status / Restated (Ian) - NoC Benchmarking WG Sponsor Upgrades - UBC/WSU/KTH/CNU 11:20-11:40 AM: Progress in Asia (Ian) 11:40-12:00 PM: Japan Recruiting Plan (Yoshimori-san) 12:00-1:45 PM: Motion to Adjourn/ Lunch/ Reconvene

  5. Call to Order and Agenda Review (Ian) • Call to Order • Welcome from the President • Review Agenda • Any additional items? • Vote to approve last GSC Meeting Minutes • 20th GSC Meeting, 1 June 2006, Helsinki, Finland

  6. 8:15- 8:30 AM: Coffee Available8:30- 8:40 AM: Call to Order, Introductions, Agenda Review, Last Minutes (Ian)8:40- 8:55 AM: Annual Governance Resolution & Elections (Ian)8:55- 9:00 AM: Next GSC Meeting (Ian) 9:00- 9:25 AM: Functional Verification WG (Steve) - Sponsor Member Upgrades (TrustIC & Aerielogic)9:25- 9:55 AM: Debug WG (Neal)9:55-10:20 AM: System Level Design WG (Mark)10:20-10:40 AM: Motion to Adjourn/ Break/ Reconvene10:40-11:10 AM: Specification WG Status (Drew) - Cache Coherence SG Status (Drew)11:10-11:20 AM: Technical Vision WG Status / Restated (Ian) - NoC Benchmarking WG Sponsor Upgrades - UBC/WSU/KTH/CNU 11:20-11:40 AM: Progress in Asia (Ian) 11:40-12:00 PM: Japan Recruiting Plan (Yoshimori-san) 12:00-1:45 PM: Motion to Adjourn/ Lunch/ Reconvene

  7. Annual Meeting Saving Resolution / Elections (Ian) • Motion: • That it be resolved that all acts previously taken by any officer of the Corporation on behalf of the Corporation are approved, ratified, and confirmed, provided the acts were not inconsistent with the Corporation’s Articles of Incorporation or Bylaws, the California Corporations Code, or any other applicable law.

  8. Annual Meeting Saving Resolution / Elections (Ian) • Election of Officers: • Chairman • President • Secretary • Confirmation of Directors (We will reset the Terms at next annual meeting): • Vesa Lahtinen - Nokia (3 years) • Franck Seigneret - TI (2 years) • Drew Wingard - Sonics (2 years) • Takashi Yoshimori - Toshiba (1 years)

  9. 8:15- 8:30 AM: Coffee Available8:30- 8:40 AM: Call to Order, Introductions, Agenda Review, Last Minutes (Ian)8:40- 8:55 AM: Annual Governance Resolution & Elections (Ian) 8:55- 9:00 AM: Next GSC Meeting (Ian)9:00- 9:25 AM: Functional Verification WG (Steve) - Sponsor Member Upgrades (TrustIC & Aerielogic)9:25- 9:55 AM: Debug WG (Neal)9:55-10:20 AM: System Level Design WG (Mark)10:20-10:40 AM: Motion to Adjourn/ Break/ Reconvene10:40-11:10 AM: Specification WG Status (Drew) - Cache Coherence SG Status (Drew)11:10-11:20 AM: Technical Vision WG Status / Restated (Ian) - NoC Benchmarking WG Sponsor Upgrades - UBC/WSU/KTH/CNU 11:20-11:40 AM: Progress in Asia (Ian) 11:40-12:00 PM: Japan Recruiting Plan (Yoshimori-san) 12:00-1:45 PM: Motion to Adjourn/ Lunch/ Reconvene

  10. Next GSC Meeting (Ian) • 22nd GSC meeting date to be confirmed • Suggest: January? • Japan? • Use January 2007 meeting requires TVWG planning • How will we proactively capture immediate expertise of WG Chairs?

  11. 8:15- 8:30 AM: Coffee Available8:30- 8:40 AM: Call to Order, Introductions, Agenda Review, Last Minutes (Ian)8:40- 8:55 AM: Annual Governance Resolution & Elections (Ian) 8:55- 9:00 AM: Next GSC Meeting (Ian) 9:00- 9:25 AM: Functional Verification WG (Steve) - Sponsor Member Upgrades (TrustIC & Aerielogic)9:25- 9:55 AM: Debug WG (Neal)9:55-10:20 AM: System Level Design WG (Mark)10:20-10:40 AM: Motion to Adjourn/ Break/ Reconvene10:40-11:10 AM: Specification WG Status (Drew) - Cache Coherence SG Status (Drew)11:10-11:20 AM: Technical Vision WG Status / Restated (Ian) - NoC Benchmarking WG Sponsor Upgrades - UBC/WSU/KTH/CNU 11:20-11:40 AM: Progress in Asia (Ian) 11:40-12:00 PM: Japan Recruiting Plan (Yoshimori-san) 12:00-1:45 PM: Motion to Adjourn/ Lunch/ Reconvene

  12. FVWG - Presentation Overview (Steve) • OCP-IP 2.0 / 2.1 Compliance Checks - Status • Next Compliance Check Release – OCP 2.2 • OCP 2.2 – Schedule Considerations • OCP 2.2 – Specification Schedule • OCP 2.2 – Compliance Check Schedule • Future FVWG Activities • Other Topics

  13. OCP-IP 2.0 / 2.1 Compliance Checks - Status • Released June 2006 • Contained: • Protocol Checks for 2.0 and 2.1 • Functional Coverage • Toggle, State, Meta, and Category (Cross)

  14. Next Compliance Check Release – OCP 2.2 • Merge with OCP Specification • Discussions held with Specification WG • Replaces current verification section • Planned for 2.2 specification release • Include updates relative to OCP 2.2 • Include Configuration Checks in conjunction with existing Protocol Checks • Corrections, updates, etc., to existing information

  15. OCP 2.2 - Schedule Considerations • Simple integration • Effort is focused on merging documents • NOT focused on perfecting compliance • Simple section rearrangement to match specification flow • Taking advantage of integration left to future releases • E.g., Cross-references between specification text and checks • E.g., Cross-references between specification text and functional coverage • Priority given to meeting specification schedule objectives

  16. 2.2 Schedule – Specification Schedule • NOTE: Tentative Agreement with Specification WG • Specification (minus compliance) member review: • Start mid-October 2006, finish mid-November 2006 • Compliance portion of specification member review: • Start end-October 2006, finish mid-November 2006 • Final cleanups: • Start mid-November 2006, finish end-November 2006 • Release: • December 1, 2006

  17. OCP 2.2 – Compliance Check Schedule • Outline & list of configuration checks to tech writer: • Finish end-September 2006 • 2.2 protocol and configuration checks • Finish mid-October 2006 • FVWG review and cleanup • Finish end-October 2006 • General Member review • Finish mid-November 2006 • Release (as part of specification) • Finish end-November 2006

  18. Future FVWG activities • Increasing cross-references between ‘specification’ and ‘compliance’ sections of OCP Specification • Tightening up definition of ‘compliance’ • Tier 1 Protocol Checks • Jeda expressed interest • Jeda indicated potential submission

  19. FVWG - Other Topics • Aerielogic • TrustIC • Review high level goals for GSC

  20. 8:15- 8:30 AM: Coffee Available8:30- 8:40 AM: Call to Order, Introductions, Agenda Review, Last Minutes (Ian)8:40- 8:55 AM: Annual Governance Resolution & Elections (Ian) 8:55- 9:00 AM: Next GSC Meeting (Ian) 9:00- 9:25 AM: Functional Verification WG (Steve) - Sponsor Member Upgrades (TrustIC & Aerielogic)9:25- 9:55 AM: Debug WG (Neal)9:55-10:20 AM: System Level Design WG (Mark)10:20-10:40 AM: Motion to Adjourn/ Break/ Reconvene10:40-11:10 AM: Specification WG Status (Drew) - Cache Coherence SG Status (Drew)11:10-11:20 AM: Technical Vision WG Status / Restated UBC/WSU/KTH/CNU (Ian) - NoC Benchmarking WG Sponsor Upgrades - UBC/WSU/KTH/CNU 11:20-11:40 AM: Progress in Asia (Ian) 11:40-12:00 PM: Japan Recruiting Plan (Yoshimori-san) 12:00-1:45 PM: Motion to Adjourn/ Lunch/ Reconvene

  21. Overview • Other Debug Activities: How do we fit in? – We differ from some other groups in that we are defining a new socket level interface for debug. Chip level interface is near term don’t care. • What do we want? – Enable more standardized debug interfaces to facilitate new tools and debug support. Keep it compliant to OCP-IP Socket concept • What can we do? – We have defined the debug signal set, we have a specification written, it is in review by OCP-IP Spec Group. we are looking for adopters and wider dissemination by end of year. • Business Model – We are relying on tool venders and interested companies for the initial implementation • Open issues – There are many auxiliary efforts that are important for the longer term

  22. OCP Debug Extensions • OCP Debug Working Group defines extension signals for debug operations • Similar to how OCP 2.1 socket standard defines data transfer socket • Specification is in review by Spec WG OCP Fabric(s) OCP Fabric(s) Processor Mem Ctrlr Processor Mem Ctrlr Co- Processor Co- Processor RAM RAM Other IP Other IP Other IP Other IP Standardized data transfer socket Master or slave, with optional bursting, thread signals Need not be the same for Generally optional all sockets

  23. Debug-IP Definition: SoC Debug Concepts Have 5 Hardware and 2 Software Interfaces • Debug-IP HW connections to SoC • 1 CORE-INTERFACE: interfaces to core IP-block debug data/control proprietary IO • 2 BUS-INTERFACE: interface to a bus traffic [event/trace data collect, compression and triggering] • 3 CROSS-TRIGGER INTERFACE: to other debug-IP blocks [event-synch.] • 4 PIN-INTERFACE CONTROL: IF to JTAG for debug control to analyzer/debugger software. • 5 PIN-INTERFACE DATA: interface for high speed data [like Nexus] • Debug software for Debug-IP information transfer and display • A System Debug SW API interface • B. EDA API interface – block and system level verification (ESL, RTL) Cross trigger IF 3 OCP Bus fabric Bus test socket 1 Core Debug IF Trace IF 2 Memory-mapped JTAG-mapped Nexus-mapped Debug-IP registers Debug IF 4 5 Nexus data-trace JTAG control Debug Software SYS API EDA API A B

  24. What is in the Debug Spec? • Define an OCP Interface for Basic Debug Signals • Debug Control and Run Control for Cores • Consistent (multiple) processor software debugger interfaces • Cross-Triggering between Multiple Cores and Events • Scalable to on chip/off chip cross triggering • Trace Interface • bus traffic observation (system trace) and control (triggering) • New classes of debug errors (different from system errors) • Define Extended (Special features) OCPDebug Interface Signals • Performance Monitor • Time-stamping • Power Monitoring voltage islands, gated clock islands • Security islands • Enable OCP members to develop standardized debug-IP blocks

  25. OCP Debug Socket Options Baseline Debug Socket Signals • 1149.1 JTAG - TCK, TMS, TDI, TDO - part of OCP 2.1 spec • Debug_reset, debug_reset_en • MReqDebug, Msuspend, DebugSerror, DebugCon, • NoSResp, ForceResp, ForceAbort, ForceAbortAck Functional Specific Options • Cross Trigger Interfaces : Trigger_in_condition[n:0], Trigger_out_Action[n:0], Trigger_out_enable[n:0], Ext_trig _clk, Ext _condition[n:0], Ext _action[n:0] • Trace/Debug Synchronization : SyncRunSyncRunAck • Trace TraceTrigger[x] • TimeStamp Interfaces ts_clk ts_reset Target Application Specific Options • Power Management : PWRDomainStatus, CLKDomainStatus Extended response field [2:0] – No Power, No Clk • Security : MReqSecure, DebugMode[1:0] , TraceMode[1:0], TAPenable

  26. Other Debug Activities SPIRIT MC Ass. X P1687 - IJTAG 1149.7 - CJTAG

  27. The OCP-IP Debug Interface Study Group • Toshiba Bob Uvacek, chair • FS2 Neal Stollon Other contributors • DAFCA James Colgan, Al Crouch, Dave Orecchio • CAST/ Evatronix Hal Barbour / Wojtek Sakowski • TI Gilbert Laurenti • MIPS Scott McCoy, John Hogan • Nokia Anssi Haverinen • OCP-IP contacts Jeff Phillips, Travis Spear, Ian Mackintosh

  28. OCP-IP Debug Goals • Walk through to be provided by Chair

  29. 8:15- 8:30 AM: Coffee Available8:30- 8:40 AM: Call to Order, Introductions, Agenda Review, Last Minutes (Ian)8:40- 8:55 AM: Annual Governance Resolution & Elections (Ian) 8:55- 9:00 AM: Next GSC Meeting (Ian) 9:00- 9:25 AM: Functional Verification WG (Steve) - Sponsor Member Upgrades (TrustIC & Aerielogic)9:25- 9:55 AM: Debug WG (Neal)9:55-10:20 AM: System Level Design WG (Mark)10:20-10:40 AM: Motion to Adjourn/ Break/ Reconvene10:40-11:10 AM: Specification WG Status (Drew) - Cache Coherence SG Status (Drew)11:10-11:20 AM: Technical Vision WG Status / Restated UBC/WSU/KTH/CNU (Ian) - NoC Benchmarking WG Sponsor Upgrades - UBC/WSU/KTH/CNU 11:20-11:40 AM: Progress in Asia (Ian) 11:40-12:00 PM: Japan Recruiting Plan (Yoshimori-san) 12:00-1:45 PM: Motion to Adjourn/ Lunch/ Reconvene

  30. Overview • AI’s for the SLD WG • Goals from TVWG • Release of 2.1.2 packages • Update on Jeda Run time assertion package and Nokia PSL package • Plans for Next Release

  31. GSC AI’s for the SLD DWG • Still see no requirement for a SystemVerilog white paper, will keep this under review.

  32. 2.1.3 release • Released close to time schedule (had set End August, released September) • Included testing using regression tests from ITRI (et al) • Which did find some small errors! Other features • Prepare for pipelined thread busy support in TL1 and TL2 (may be a hidden feature till 2.2 release) • Configuration from cores option, with callbacks for config-sensitive (generic) cores. TL1 and TL2. • getPeriod() added to TL1 interfaces • Choose 'standard' data types for addr and data when wider than 64-bit • Documentation review 2.2 release in early planning stage. Expect to complete release by E.O.Y. 06.

  33. The SLD Mid-Term Vision - unchanged • 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

  34. SLD WG Review of 2006 Goals • Mark to provide walk through of goals provided

  35. 8:15- 8:30 AM: Coffee Available8:30- 8:40 AM: Call to Order, Introductions, Agenda Review, Last Minutes (Ian)8:40- 8:55 AM: Annual Governance Resolution & Elections (Ian) 8:55- 9:00 AM: Next GSC Meeting (Ian) 9:00- 9:25 AM: Functional Verification WG (Steve) - Sponsor Member Upgrades (TrustIC & Aerielogic)9:25- 9:55 AM: Debug WG (Neal)9:55-10:20 AM: System Level Design WG (Mark)10:20-10:40 AM: Motion to Adjourn/ Break/ Reconvene10:40-11:10 AM: Specification WG Status (Drew) - Cache Coherence SG Status (Drew)11:10-11:20 AM: Technical Vision WG Status / Restated (Ian) - NoC Benchmarking WG Sponsor Upgrades - UBC/WSU/KTH/CNU 11:20-11:40 AM: Progress in Asia (Ian) 11:40-12:00 PM: Japan Recruiting Plan (Yoshimori-san) 12:00-1:45 PM: Motion to Adjourn/ Lunch/ Reconvene

  36. Break

  37. 8:15- 8:30 AM: Coffee Available8:30- 8:40 AM: Call to Order, Introductions, Agenda Review, Last Minutes (Ian)8:40- 8:55 AM: Annual Governance Resolution & Elections (Ian) 8:55- 9:00 AM: Next GSC Meeting (Ian) 9:00- 9:25 AM: Functional Verification WG (Steve) - Sponsor Member Upgrades (TrustIC & Aerielogic)9:25- 9:55 AM: Debug WG (Neal)9:55-10:20 AM: System Level Design WG (Mark)10:20-10:40 AM: Motion to Adjourn/ Break/ Reconvene10:40-11:10 AM: Specification WG Status (Drew) - Cache Coherence SG Status (Drew)11:10-11:20 AM: Technical Vision WG Status / Restated (Ian) - NoC Benchmarking WG Sponsor Upgrades - UBC/WSU/KTH/CNU 11:20-11:40 AM: Progress in Asia (Ian) 11:40-12:00 PM: Japan Recruiting Plan (Yoshimori-san) 12:00-1:45 PM: Motion to Adjourn/ Lunch/ Reconvene

  38. Specification WG Status • Version 2.2 work • In WG review (ends October 5) • Goal: enter Member Review by Oct. 15 • Other reviews • Cache Coherence SG proposals • Officially ended Sept. 1 • Still awaiting feedback from TI, Toshiba, Sonics • Debug WG proposals • Review period through Oct. 31

  39. Specification WG Issues • When will Cache Coherence work complete? • Should we integrate Debug proposals into main Specification, or leave as a separate specification? • How should we integrate FVWG work into main Specification, and how does that impact: • Ability to do WG and Member Reviews • Ability to distribute Specification under Research License

  40. Specification WG Goals for Rest of 2006 • Publish OCP 2.2 as standard of record by Dec. 15 • Resolve issues: • Integrate debug into main Spec. or not • Work flow for FVWG compliance checks • Should we re-integrate Cache Coherence SG

  41. Cache Coherence SG Status • “OCP Coherence Extensions” documents were submitted to the Specification WG for review • Part 1: Coherence Framework • Part 2: Signals and Encodings • Feedback received so far only from Nokia • MIPS has announced creation and validation of a formal model proving the protocols for a “snoopy” system • Models distributed to the SG

  42. Cache Coherence SG Issues • Energy level and attendance is still low • Delayed Spec. WG review didn’t help • Only truly motivated member is MIPS • Unclear how to prove proposed protocols against a distributed directory-based system • Unclear how to proceed to detailed protocol specification and rest of required deliverables • Bigger challenge: how to cope with ongoing, competitive AMBA4 work

  43. Cache Coherence SG Goals for Rest of 2006 • Incorporate Spec. WG feedback • Proceed to detailed protocol specification • Suggestion: re-integrate into Spec. WG unless feedback is too massive

  44. 8:15- 8:30 AM: Coffee Available8:30- 8:40 AM: Call to Order, Introductions, Agenda Review, Last Minutes (Ian)8:40- 8:55 AM: Annual Governance Resolution & Elections (Ian) 8:55- 9:00 AM: Next GSC Meeting (Ian) 9:00- 9:25 AM: Functional Verification WG (Steve) - Sponsor Member Upgrades (TrustIC & Aerielogic)9:25- 9:55 AM: Debug WG (Neal)9:55-10:20 AM: System Level Design WG (Mark)10:20-10:40 AM: Motion to Adjourn/ Break/ Reconvene10:40-11:10 AM: Specification WG Status (Drew) - Cache Coherence SG Status (Drew)11:10-11:20 AM: Technical Vision WG Status / Restated (Ian) - NoC Benchmarking WG Sponsor Upgrades - UBC/WSU/KTH/CNU11:20-11:40 AM: Progress in Asia (Ian) 11:40-12:00 PM: Japan Recruiting Plan (Yoshimori-san) 12:00-1:45 PM: Motion to Adjourn/ Lunch/ Reconvene

  45. Technical Vision WG Status Restated (Ian) • OCP-IP offering was fully defined as prioritized “whole product” at March GSC meeting • 2006 priorities were agreed by GSC and disseminated to WGs - all recommendations were reduced to agreed goals and inserted as overall OCP-IP 2006 Objectives (Except Cache/Spec WGs) • We must reprioritize TVWG inputs for working groups combined with January 2007 GSC meeting • How can we proactively capture input from Chairs?

  46. NoC Bencharking WG • Sufficient progress made to commence formal meetings • Need official sponsor member upgrades: • Free upgrades for • UBC • WSU • KTH • CNU

  47. 8:15- 8:30 AM: Coffee Available8:30- 8:40 AM: Call to Order, Introductions, Agenda Review, Last Minutes (Ian)8:40- 8:55 AM: Annual Governance Resolution & Elections (Ian) 8:55- 9:00 AM: Next GSC Meeting (Ian) 9:00- 9:25 AM: Functional Verification WG (Steve) - Sponsor Member Upgrades (TrustIC & Aerielogic)9:25- 9:55 AM: Debug WG (Neal)9:55-10:20 AM: System Level Design WG (Mark)10:20-10:40 AM: Motion to Adjourn/ Break/ Reconvene10:40-11:10 AM: Specification WG Status (Drew) - Cache Coherence SG Status (Drew)11:10-11:20 AM: Technical Vision WG Status / Restated (Ian) - NoC Benchmarking WG Sponsor Upgrades - UBC/WSU/KTH/CNU 11:20-11:40 AM: Progress in Asia (Ian) 11:40-12:00 PM: Japan Recruiting Plan (Yoshimori-san) 12:00-1:45 PM: Motion to Adjourn/ Lunch/ Reconvene

  48. Progress in Asia – Overview (Ian) • Asia represents collective major design center for SoC: Japan, Taiwan, Korea, China, India/Russia • New Asian standards movements are opportunity for OCP • Key OCP-IP updates by country: • Japan – Rejuvenating with partnered seminars • Taiwan – ITRI acting as champion and presenting seminars • China – following our training, progress very slow with China struggling to engage standards in general • Korea – have presence, completing regional support • India/Russia – no progress with ISA for introductions • OCP impact in Asia will strengthen our total world-wide image

  49. Asia: Japan Status • Website – active 11/04, activity still good • Key Relationships – Toshiba, STARC, IPTC • Members – 11 total • One New Member since June – Regulus Co. • CoWare hosted a successful ESL Seminar in Japan that included an extensive OCP-IP presentation • WIP – • Japanese language technical support - localization • VDEC promotion of OCP to universities coming online; still pushing • Routinely adding relevant content to Japanese Web site • Next Steps – • CoWare ESL show done; FPF Japan and second CoWare event still pending • Secure VDEC endorsement to Japanese academia • Create articles on VDEC results with universities • Work with STARC to penetrate System-Level and other new WG’s • Solicit Toshiba’s help and advice to drive membership

  50. Asia: Taiwan Status • Website – leveraging existing simplified Chinese and English Web sites • Key Relationships – ITRI, TSoCC • Members – 5 total • ITRI committed to 2-3 workshops/seminars in 2006 • Completed ITRI ESL show • ITRI completed strong contributions with regression suite for SLD WG • WIP – ITRI are engaged as active Taiwan champion and in SLD WG • Next Steps – • Leverage ITRI championship of OCP and SystemC technologies – 1 more show in Q4 • 2006 Taiwan OCP promotion is leveraged through ITRI • Convert ITRI platform spin-outs to OCP-IP membership over time

More Related