OCP-IP Governing Steering Committee Meeting Tokyo, Japan January 11, 2007

OCP-IPGoverning Steering Committee MeetingTokyo, JapanJanuary 11, 2007

8:15- 8:30 AM: Coffee Available8:30- 8:40 AM: Call to Order, Introductions, Agenda Review, Last Minutes (Ian)8:40- 8:45 AM: Next GSC Meeting (Ian) 8:45- 9:10 AM: Functional Verification WG Status (Steve)9:10- 9:40 AM: Debug WG Status (Bob)9:40-10:10 AM: Specification and Cache WG Status (Drew) 10:10-10:30 AM: Motion to Adjourn/ Break/ Reconvene 10:30-10:50 AM: Technical Vision WG Status / Restated (Ian) - Assign AI’s to align WG’s for 200710:50-11:10 AM: Progress in Asia (Ian) 11:10-11:30 PM: Japan Recruiting Plan (Yoshimori-san) 11:30-12:00 PM: Review of 2006 Goals (Ian) 12:00-1:45 PM: Motion to Adjourn/ Lunch/ Reconvene

12:00-1:45 PM: Motion to Adjourn/ Lunch/ Reconvene1:45-2:15 PM: 2007 Goals (Ian)2:15- 3:00 PM: AI Review (Ian) - ARM Discussion - Synopsys and CoreCreator Update - NoCBWG Discussion3:00- 3:20 PM: PR Update (Joe) 3:20- 3:35 PM: Recruiting Update (Joe) 3:35- 3:45 PM: Motion to Adjourn/ Break/ Reconvene 3:45- 4:00 PM: Budget Update (Ian/VTM)4:00- 4:15 PM: Administrative Update (VTM)4:15- 4:45 PM: System Level Design WG Status (Mark) 4:45- 4:50 PM: Enabling Resolution4:50- 5:00 PM: Collateral Review (VTM)5:00 PM Motion to Adjourn

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 • 21st GSC Meeting, 28 Sept 2006, San Jose, California

Next GSC Meeting (Ian) • 23rd GSC Meeting • April 20, 2007 (this is the day following DATE) • Nice, France • Hold meeting at TI facility?

FVWG Goals for 2007 (Steve) • New Opportunities - initiate by end February 2007 • Choose one new major opportunity, end January • Possibilities: TL2 Checks, Performance Standard • Others? • Develop plan and timeline for delivery, end February • Protocol Compliance Clarification – complete by end September 2006 • Identify basic review objectives, end January • Reviewing for correctness • Making checks, etc., more specific • Defining where to provide ‘live’ cross references • Identifying spots where the specification section needs to be clarified • Detailed review of ‘Compliance section’, end February • Detailed review of ‘Protocol Compliance Checks’, end April • Detailed review of ‘Configuration Compliance Checks’, end June • Detailed review of ‘Functional Coverage’, end August • Align with the Next Specification Release - occurring ??? • Align our updates with Spec’n WG timelines • Initiate ‘Document Revision’ update if no Spec’n WG releases are contemplated

Debug – Overview (Bob) • 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, which was discussed through late December ‘06. We are looking for adopters and wider dissemination right afterwards. • 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

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

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

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 security islands • Enable OCP members to develop standardized debug-IP blocks

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

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

The OCP-IP Debug Interface Study Group • Pixelworks (Ex. 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, Vesa Lahtinen • OCP-IP contacts Jeff Phillips, Brian Sage, Amanda Luukinen, Ian Mackintosh

Specification WG Status: OCP 2.2 • Version 2.2 released Dec. 22, 2006! • Enhancements: • More flexible clocking • Asynchronous reset assertion • 2D burst sequences • Pipelined non-blocking flow control • New security profile • Incorporation of FVWG compliance work • OCP Specification is now 330 pages long…

Other Specification WG Status • Cache Coherence SG proposals • Feedback delivered to SG • Coherence work moved to Spec. WG, but no progress since (due to focus on 2.2) • Debug WG proposals • Never fully reviewed • Do not expect this to change

Proposed Specification WG 2007 Plan (Pre-TVWG) Release OCP 3.0 by end ’07 comprising: • Cache Coherence extensions • Consensus profile(s) from key OCP-IP members for IP providers • Power management signaling (based on TI proposal) • (Tentative) New extensions from members (FPGA?)

Specification WG Issues (1/2) • Still a lot of work to do to flesh out, prove, and finalize Cache Coherence work • Will need more than MIPS to help • Sonics interested, but probably not before summer • Who else can help? • Seeing interest in extensions from FPGA community • But need Sponsor/GSC member to drive • How should we respond?

Specification WG Issues (2/2) • Request from Synopsys for unified profiles for use in DesignWare IP is very attractive • But will require coordination among (at least) Nokia, TI, and Toshiba • How will this work occur? • Where will this work occur? • Who will publish the results of this work, and how/where? • Suggestion: Do this in Spec. WG, and publish results in OCP Spec.

Proposed Cache Coherence SG 2007 Plan • Stay dormant unless Spec. WG needs assistance

Break

Technical Vision WG Status Restated (Ian) • This statement records TVWG actions and recommendations within the GSC minutes • Should confirm relevant decisions from January 10th TVWG Meeting • OCP-IP offering was fully defined as prioritized “whole product” at January 10th TVWG meeting • 2007 priorities were agreed by TVWG and will be disseminated to all WGs for ratification and scheduling - all recommendations were reduced to agreed goals and will be inserted as overall OCP-IP 2007 Objectives • All Chairs proactively provided individual WG recommendations to the TVWG ahead of January 10th TVWG meeting

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 – continuing with partnered seminars • Taiwan – ITRI acting as champion and hosting seminars • China – series of visits directly with potential end users; progress quite slow with partners and China struggling to engage standards in general • Korea – have presence, but must switch to new champion; Korea completes regional support picture • India – very productive exposure in Bangalore region with ISA group remaining aloof • Russia – As planned, no approaches made for 2006 • OCP impact in Asia will strengthen our total world-wide image

Asia: Japan Status • Website – active 11/04, activity still good • Key Relationships – Toshiba, IPTC, VDEC, STARC and Nikkei Press • Members – 13 total • Two New Members since September – AOI Technology, Inc. and Inventure • CoWare hosted another successful Users’ Meeting in Japan that included an extensive OCP-IP presentation • Our thanks to TI Japan who provided another able speaker! • Fall Processor Forum in Japan • WIP – • Japanese language technical support - localization • VDEC interface converters under evaluation at Toshiba • VDEC promotion of OCP to universities coming online; still pushing • Currently planning 2007 seminars through VDEC (March), IPTC (May) and potentially paying audience for Nikkei Press seminar (TBD) • Routinely adding relevant content to Japanese Web site • Next Steps – • Secure three pending events, above • Secure VDEC endorsement to Japanese academia • Create articles on VDEC results with universities • Promote VDEC interface converter technology if deemed viable • Work with STARC to penetrate System-Level and other new WG’s • Continue leveraging Toshiba’s strong help and support to drive membership

Asia: Taiwan Status • Website – leveraging existing simplified Chinese and English Web sites • Key Relationships – ITRI, TSoCC • Members – 5 total • ITRI conducted 2 OCP workshops/seminars in December! • Our thanks to Sonics who provided very capable speaker! • WIP – ITRI are engaged as active Taiwan champion and in SLD WG • Next Steps – • Leverage ITRI championship of OCP and SystemC technologies – plan events/seminars for 2007 • 2007 Taiwan OCP promotion continues to be leveraged through ITRI • Convert ITRI platform spin-outs to OCP-IP membership over time

Asia: Korea Status • Website – Active 5/05; activity OK, small market • Key Relationships – SIPAC • Members – 2; however, Samsung is an OCP user and it is possible OCP interest will expand in more groups and motivate membership • WIP – We still post relevant key announcements on Korean website • Next Steps – Currently engaging discussions with KETI (Ministry of commerce, industry and energy) who appear to be driving new SIP coordination initiative with SIPAC apparently sidelined • Still seeking Samsung membership long-term via GSC relationships

Asia: China Status • Website – active 5/05; activity healthy and second to Japanese Web site level • Key Relationships – Harbin/ IPGC, CSIP, SSIPEX • Members – 4 total • Have provided much guidance on standards body membership • Governing Chinese bodies still not able to effectively sell any standards today! • History – • Both CSIP and SSIPEX received OCP Training in 2005 • Turnovers in both organizations hamper promo and technical grasp of OCP • CSIP promoting OCP with all other IPGC standards • Professor Ye remains very committed to OCP during recent visit • SSIPEX struggled promoting OCP independently • They are trying again following Ian’s 4Q06 visit • Ian participated in 4Q06 IP-SoC China 2006 Forum • Next Steps – • Drive SSIPEX to close OCP membership promotion as stated • Drive CSIP to engage OCP-IP CoreCreator and potential financial opportunity • Maintain strong relationship with Professor Ye following Ian’s Q406 visit

Asia: India and Russia Status • Website – None; English language fully applicable • Engaged 8 key relationships in 4Q06 - ISA remains dysfunctional • Members – 5 Indian / 0 Russia • WIP – • Now working directly with companies visited in 4Q06 • All corporations visited offered substantial and useful audiences AND word of mouth OCP promotion • Thanks to TI India for leads on relevant membership corporation (Tata, Wipro and MindTree)! • Next Steps – • Continue direct recruiting after 4Q06 visit • Remain open to ISA if they ever appear functional • We have no current plans for Russia

Asia: Summary • Good activity in Japan, Taiwan, China and India with both presentations and meetings leveraged through key relationships • Very promising reception to OCP story in India • Direct contacts in China illuminate real need for OCP despite generally very embryonic SoC design industry • Current relationships are strong foundations for long term growth • Region “more receptive” to standards/collaboration • Seminars and individual corporate meetings can only help long term cause in Japan, Taiwan, China and India • We did a great job leveraging 2006 budget into multiple seminars in each of Japan and Taiwan and important corporate meetings in China and India during 4Q06

8:15- 8:30 AM: Coffee Available8:30- 8:40 AM: Call to Order, Introductions, Agenda Review, Last Minutes (Ian)8:40- 8:45 AM: Next GSC Meeting (Ian) 8:45- 9:10 AM: Functional Verification WG Status (Steve)9:10- 9:40 AM: Debug WG Status (Bob)9:40-10:10 AM: Specification and Cache WG Status (Drew) 10:10-10:30 AM: Motion to Adjourn/ Break/ Reconvene 10:30-10:50 AM: Technical Vision WG Status / Restated (Ian) - Assign AI’s to align WG’s for 200710:50-11:10 AM: Progress in Asia (Ian)11:10-11:30 PM: Japan Recruiting Plan (Yoshimori-san) 11:30-12:00 PM: Review of 2006 Goals (Ian) 12:00-1:45 PM: Motion to Adjourn/ Lunch/ Reconvene

OCP-IPJapan Marketing Toshiba Corporation 11th Jan. 2007

OCP Seminar in Japan 2006 • (This seminar had been already reported at the previous GSC meeting) • Date: May 9, 2006 • At: Yokohama Media and Communications Center • Attendees: about 150 • Host : IPTC • Act by Toshiba: • Presentation about OCP-IP in Japanese[Outline of the spec, organization, member program, etc] • Collaterals about OCP-IP were handed-out to all the attendees. • Other presentation • VDEC : Keynote speech • Sonics : SoC design using OCP interfaced IPs • TransEDA : OCP verification method • TI : Case example about OCP based design [TI OMAP]

Proposal of next OCP Seminar (1/2) • Proposal by IPTC and Toshiba • About the seminar • For the date of the seminar, the week of 21st. May is the best. (The next week of ESEC.) • The seminar for the specialists of OCP is not so good because: • only the actual users of OCP will come to the seminar, so we can not expect enough audience, there spend 1 year after the last OCP seminar, it is better to follow the contents of the last seminar adding little more technical session in it. • The update of OCP and OCP-IP is important for the public impression of the satisfactory action of OCP-IP. Only for this, the non-members of OCP-IP will come to the seminar. • For the engineers the 1-day restriction is a burden. They do not care the lunch and party. Half-day seminar is better. "13 to 17" is the best, but only 4 hours is too short, the next candidate is "13-18".

Proposal of next OCP Seminar (2/2) • About each session • How about the success story using OCP spec.? • Also C models and compliance test as WG activities? • IPTC and Toshiba think these topics are good for calling of many audience. • How about the leaflets of summary of OCP spec.? • Program: • <proposal 1> • Special session (invited speaker) • OCP-IP Update • C Model • Compliance test • Success Story • <proposal 2> • OCP-IP Update • C Model • Compliance Test • Tutorial: how to read OCP spec. • Success Story • 40 minutes for each session plus breaks will take 240 minutes. • IPTC comment: • The seminar should be profitable for IPTC.

Toshiba delivers technology and products remarkable for their innovation and artistry – contributing to a safer, more comfortable, more productive life. We bring together the spirit of innovation with our passion and conviction to shape the future and help protect the global environment – our shared heritage. We foster close relationships, rooted in trust and respect, with our customers, business partners and communities around the world.

8:15- 8:30 AM: Coffee Available8:30- 8:40 AM: Call to Order, Introductions, Agenda Review, Last Minutes (Ian)8:40- 8:45 AM: Next GSC Meeting (Ian) 8:45- 9:10 AM: Functional Verification WG Status (Steve)9:10- 9:40 AM: Debug WG Status (Bob)9:40-10:10 AM: Specification and Cache WG Status (Drew) 10:10-10:30 AM: Motion to Adjourn/ Break/ Reconvene 10:30-10:50 AM: Technical Vision WG Status / Restated (Ian) - Assign AI’s to align WG’s for 200710:50-11:10 AM: Progress in Asia (Ian)11:10-11:30 PM: Japan Recruiting Plan (Yoshimori-san) 11:30-12:00 PM: Review of 2006 Goals (Ian) 12:00-1:45 PM: Motion to Adjourn/ Lunch/ Reconvene

Marketing Goals for 2006 (Ian) Promotions Goals 2006: Press Releases • 15 major announcements • 17 completed ArticlesOriginated by OCP-IP • 25 placed articles (inserts count as one) • 16 to date, strong funnel but tough goal • We have > 25 articles with strong OCP-IP mentions on our website Presentations • Papers and presentations at 15 events (minimum) • 21 completed

Marketing Goals for 2006 (Ian) Promotions Goals 2006: Tradeshow Attendance: 7; Done • DATE - Done • DAC - Done • Spring Processor Forum - Canceled • Fall Processor Forum (US) – Done • GSPx - Canceled • Fall Processor Forum (Japan) – Done • Electronica 2006 (Munich) – Done • IP China 2006 – Done • IP/SoC (Grenoble) – Done • The above list are the budgeted events; we executed multiple opportunities for other partnered seminars in 2006 (3 each in Taiwan and Japan in 2H06)

Marketing Goals for 2006 (Ian) Membership Goals 2006: Asia / India • 11 new Asian members • To Include 3 new Indian members (minimum) • 5 to date (IPTC, Regulus, Inventure, HCL Technologies & AOI Technology, Inc.), no kickoff in India until EOY FPGA / Military • 5 new military industry members • 4 to date (ESA, Nallatech, AlphaData, MITRE) GSC: • 5 committed GSC members • Currently 4 (Target: Altera, Synopsys, Cisco, Intel and potentially QualComm?) Other Sponsor and Community • 15 others (per financial mix in 2006 budget) • 0 (Paying) Sponsor and 15 Community joined

Marketing Goals for 2006 (Ian) Membership Goals 2006: University Program • Commence VDEC program in Japan – Done, but still need heavy endorsement and review of interface converter opportunity • Formal announcement of NoC Benchmarking Program (Q3) - Done • University participation in Cache Coherence Program - Open • Total Members: Goal was 170 and then re-evaluate • Currently 171 Members (Defunct Now Removed) • 36 new members in 2006

8:15- 8:30 AM: Coffee Available8:30- 8:40 AM: Call to Order, Introductions, Agenda Review, Last Minutes (Ian)8:40- 8:45 AM: Next GSC Meeting (Ian) 8:45- 9:10 AM: Functional Verification WG Status (Steve)9:10- 9:40 AM: Debug WG Status (Bob)9:40-10:10 AM: Specification and Cache WG Status (Drew) 10:10-10:30 AM: Motion to Adjourn/ Break/ Reconvene 10:30-10:50 AM: Technical Vision WG Status / Restated (Ian) - Assign AI’s to align WG’s for 200710:50-11:10 AM: Progress in Asia (Ian)11:10-11:30 PM: Japan Recruiting Plan (Yoshimori-san) 11:30-12:00 PM: Review of 2006 Goals (Ian)12:00-1:45 PM: Motion to Adjourn/ Lunch/ Reconvene

OCP-IP Governing Steering Committee Meeting Tokyo, Japan January 11, 2007

OCP-IP Governing Steering Committee Meeting Tokyo, Japan January 11, 2007

Presentation Transcript

Steering Committee Meeting

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

Steering Committee Meeting

Steering Committee Meeting

Steering Committee Meeting

OCP-IP Governing Steering Committee Meeting July 28, 2011

Steering Committee Meeting

OCP-IP Governing Steering Committee Meeting November 10, 2011

OCP-IP Governing Steering Committee Meeting October 04, 2012

Steering Committee Meeting

OCP-IP Governing Steering Committee Meeting January 11, 2011

OCP-IP Governing Steering Committee Meeting June 24, 2010

Steering Committee Meeting

OCP-IP Governing Steering Committee Meeting San Jose, California 7 October, 2003

OCP-IP Governing Steering Committee Meeting Mountain View, California August 23, 2007

OCP-IP Governing Steering Committee Meeting Portland, Oregon November 8, 2007

OCP-IP Governing Steering Committee Meeting San Jose, California October 15, 2004

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

OCP-IP Governing Steering Committee Meeting March 04, 2010

OCP-IP Governing Steering Committee Meeting February 23, 2012

Steering Committee Meeting January 28, 2010

Steering Committee Meeting