July 31st P1500 Working Group Meeting

Attendees

Grady, Teresa, Jason, Mike R, Paul, Mike M, Lee, Rohit, Francisco, and Karim

Paul (scribe)

Opening

Some recap discussion on previous meeting decisions impact on draft document and CTAG Team activity. "Harnessing" is the one coming out from last meeting and WBR team will be responsible for developing and defining the harness mechanism, its naming convention, etc.

Attention has been given to June 26th CTAG meeting minute on agreement on unwrapped core as Mike pointed on in his email. Extracted from the minutes is "There should be a rule for unwrapped compliancy that in addition to CTL of the unwrapped core there should also be provided an example CTL of how the core could be wrapped". The minutes has been reviewed by the attendees and decision has been made to put the working of such rule on hold.

Continue review of compliance chapter

The new wording for 17.1.1(a) has been recorded and come to consensus last meeting.

The wording of 17.1.1(b) has been reviewed and agreed to change from "If the unwrapped core has functional I/Os that are registered and the registration is desired to be shared with core wrapper boundary cells, the I/O registration shall be done with cells that are IEEE 1500 compliant boundary wrapper cells." to "All core terminals assigned to share function register with IEEE 1500 wrapper shall be provided with a complete boundary wrapper cell built-in."

On review of 17.1.1(c), it is covered in 18.2(a) which will be moved to common section so 17.1.1(c) will be removed.

On review of 17.1.1(d), it is agreed to change from "If the unwrapped core contains wrapper boundary cells, they shall be connected within a wrapper boundary register containing only such wrapper boundary cells." to "Wrapper boundary register shall only contain boundary wrapper cell." and move to common section.

On review of 17.1.1(e), it will be modified and merged with (d) and move to common section.

On review of 17.1.1(f), it is agreed to change from "Full control of existing wrapper boundary register shall be available from core I/O pins." to "Full control of existing wrapper boundary register shall be provided from core terminals."

The rest of chapter 17 has been reviewed before so the review of chapter 17 is completed.

Grady has gracefully volunteered to write the introduction on wrapped and unwrapped core.

On review of 18.3.1(a), it will be moved to common section and modified from "All state elements of a core that are part of the final wrapper boundary register implementation of the core shall be described in CTL as part of a scan chain using the ScanStructures construct of CTL." to "All state elements of wrapper boundary register chain(s) shall be described using CTL as part of a scan chain using the ScanStructures construct of CTL."

On review of 18.3.1(b), it will be removed.

Karim will provide the description for 18.3.1(a).

End of meeting.