Back to Minutes page
Back to IEEE P1532 home page
The following individuals attended the meeting:
Neil Jacobson Ken Parker Alan Herrmann Howard Tang Mark Moyer Ray Dellecker Dennis Lia Dave Bonnett Sung Chung
IEEE P1532 Meeting Minutes Date: 1/24-25/2000 Location: Agilent Technologies, Loveland CO Purpose: Data Extension
Agenda:
Discussion: Neil
Section: Ballots
Text: Ballots have been sent out. Approximately 30 people in the ballot group. Due on 2-24-00. Pat McQue is our IEEE sponsor. Ballot resolution meeting (2/28-29) needs to be rescheduled to be 1 or 3 weeks after 2-24 to assimilate the ballot returns to prepare for the meeting. Talked about review process. Suggestion to use a spreadsheet to track comments and resolutions. March 20 and 21 was selected as the date.
Action Item(s): Ballots
Text: Request Balloters to submit electronic format.
Who: Neil
When: asap
Action Item(s): Ballots
Text: Post ballot review spreadsheet to committee members and post on IEEE working group website.
Who: Neil
When: 1 -2 weeks before next meeting
Tuesday
9:30 AM
Discussion: "Programming Software Use of Device Features"
Text: Where to document. Should programming non-compliant 1532 devices be included? Particular issue of programming of flash memory using 1532 compliant devices. Incorportate as Annex in Ballot as comments?Motion:
Text: Include a derivative of "Programming Software Use of Device Features " in a future ballot that includes BSDL extension.
Motion: Alan
Second: Ken
Vote: 8-0-0
Action Item(s):
Text: Include a derivative of "Programming Software Use of Device Features " in a future ballot that includes BSDL extension.
Who: working group - Neil
When: Ballot resolution comments
10:25 AM
Discussion: P1532 BSDL Extentions Unapproved Draft 2.0 1/7/00
Section: page 96 line 31: Byte Ordering review in Program Flows and Data File.Discussion: Kurt's "Program Flows and Data File" update.
Text: Streaming data for embedded systems where memory is limited? All of IEEE standard is lsb on the right. Efficiency is the question?
Section: Page 13. Custom Data Compression. Text: Eliminate from spec?
Section: ISC_FLOW description.
Section: Pg 1 Para 2. Text: Insertion of EXTEST instructions.
Section: Pg 1 Para 2 Text: external data source vs datafile.
Section: Flow Syntax and Semantics
Text: Pg 2 duration, time, and clk cycles needs.
Text: Pg 2 flow definition string added per Ken.
Text: Pg 2 no logical changes. Matters of description.
Text: Pg 3 "If a field list is omitted in an action……" don't optimize out a DRSCAN.
12:00 PM
Lunch
12:40 PM
Section: pg 97 line 11 and 13
Section: pg 3 capture operator pg 98 line 12, 13, 14 Text: needs fixing. ! operator.
Section: pg 3 Text: datafile vs data source
Section: Pg 4 Text: increment max value 255? yes
Section: Pg4 Text: "before The wait spec gives" add "A variable may be assigned" and "The input and output operators"
Section: Pg 4 to 7 Examples 1 to 10 Text: Figures added and modifications reviewed.
Ken expressed great appreciation for all of the work that Kurt put into providing the "Program Flows and Data File" update.
Action Item(s):
Text: Capture working group review comments marked in the meetings copy of Kurt's Diff document
Who: Ken
When: For input into BSDL supplement
2:30 PM
Break
Discussion:
Section: What needs to be done in the way of validation to go to ballot.
Text: Four scenarios described in "Programming Software Use of Device Features"? Simulation? Needs to generate an SVF file that shows ability to program multiple devices.
Action Item(s):
Text: Contact the academic ballot members to find a member that would be willing to demonstrate multiple devices being programmed concurrently in-circuit. Howard volunteered to do in 3-4 months if academic resources are not found.
Who: Neil
When:
Discussion: Kurt's "Program Flows and Data File" update ( Continued ).
Section: Pg 7 Procedures and Actions. Text: <identifier> clarify.
Section: Pg 7 isc_badbit_check? Text: eliminate
Section: Pg 7 "If a flow requires data input….". Text: Missing a flow ID in datafile it is an error.
Section: Pg 8 "Not all hardware detects errors or ….". Text: compile time vs run time errors. Recommend to use isc_error_exit.
Section: Pg 8 Text: change isc_ to proc_ on all procedures
Section: Pg 8 isc_error_exit Text: When is it to be called? Complications?
Section: Pg 8 isc_exit and isc_reenter. Text: Keep?
Section: Pg 8 Action Syntax and Semantics. Text: reviewed and editted
Section: Pg 9 Text: <action descriptions> optional, recommended, hidden. remove hidden?
Section: Pg 10 Text: Action Example.
Section:
Action Item(s):
Text: Capture working group review comments marked in the meetings copy of Kurt's Diff document
Who: Ken
When: For input into BSDL supplement
Motion:
Text: Remove procedures "proc_exit" and "proc_reenter" from BSDL extension.
Motion: Mark
Second: Ray
Vote: 8-0-0
Motion:
Text: Remove "hidden" from action description
5:15 PM
Break
Wednesday
8:30 AM
Discussion: Kurt's "Program Flows and Data File" update ( Continued ).
Section: Data Files
Text: Need ability to use output data file as input. Impacts flow specification.
Action Item(s):
Text: Modify flow specification options to specify output data flow name. Add syntax for "!" identifier.
Who: Alan
When:Text: Kurt's update added much to make the datafile vendor extensible.
Text: Sequence number? Addes to complexity. Simplify?
Text: Remove "bin" from <data type>
Text: Checksum Integer vs Hex. 16bits? Optional? Computation algorithm? Name as CRC vs Checksum? "crc no_crc crc_on crc_off" attributes in datafile or in flow? CRC value stored in the datafile? Need to detect wrong datafile and detect small number of bit errors. Flow <input operator> and <output operator> key word for inclusion in CRC calculation? Should anythnig else in the datafile participate in the CRC calculation? Add optional CRC specifier to <update field> and <capture field> of flow. Text: Data format for long data. Specify a continuation character? "+" sign?
Motion:
Text: Remove the concept of "<sequence>" from Flows and Procedures.
Motion: Alan
Second: Ken
Vote: 8-0-0
Motion:
Text: Remove the initialize, loop, and terminate from the datafile <data> item.
Motion: Mark
Second: Alan
Vote: 8-0-0
Action Item(s):
Text: Capture working group review comments marked in the meetings copy of Kurt's Diff document and incorporate into draft specifications.
Who: Ken
When: For input into BSDL supplement
12:00 PM
Lunch
Action Item(s):
Text: Redo the datafile syntax and semantics based on discussion.
Who: Ken
When:
Action Item(s):
Text: Identify a 32bit CRC algorithm. Consult CCIT.
Who: Sung
When:
Action Item(s):
Text: Email to the working group the captured review comments marked in the meetings copy of Kurt's Diff document.
Who: Neil
When:
Discussion: P1532 BSDL Extentions Unapproved Draft 2.0 1/7/00 ( continued )
Section: pg 102 Text: If ISC_Flow is missing in the datafile, this is an error.
Section: pg 103 Text: ISC_Enable and ISC_Disable will be explicitly specified in a flow.
Section: pg 103 Text: actions must explicitly specify all of it's procedures. In particular: proc_enable, proc_disable, proc_program_done.
Section: pg 105 Text: Actions are the top level syntax that the user have access to procedures.
Section: pg 120 Text: Implement a continuation character. "+" suggested.
Discussion: Neil read a letter from the IEEE describing IEEE-SA membership requirement.
Next Meeting:
Date: 3/20 -21/2000
Location: Xilinx, San Jose CA
Purpose: Ballot Resolution
Date: 5/1-2/2000
Location: Altera San Jose
Purpose: Data Extension
2:00 PM
Adjourned