1. Algorithm Change Notice (ACN) What is it? How does it work? Frank Toth September 24, 1999

2. ACN: Definition / Initiation  Definition: An algorithm change notice is required if one of the following changes on a non-volatile device (CPLD or PROM): Programming Algorithm Changes Internal Programming/ Erase Voltage(s) change Product ID (Read by a stand alone Programmer Platform: DATA I/O or BP Microsystems and others) JTAG ID (Used by Xilinx JTAG Programmer (JTAGPROG) or by Third Party JTAG tools (Corelis, ASSET, or Goepel and others)  Initiation: ACNs will be initiated by the Configuration Solutions group and approved by Quality Assurance Follows similar flow as PCN/PDN: Approved by QA, Marketing and Product Line Manager Spec and request forms in Document Control

3.  Title of the Change: What the change is all about  Products affected: XC95XX, XC1800 (for example)  Description of the Change: Changes to product ID or JTAG ID  Reasons for change: Things like yield enhancements, new equipment or software requirements, etc.  Key Dates: Ideally and ACN should be done well ahead of when the changed product starts shipping in samples and production  Customer Response: Tells the customer what to do (which may include): Load new BSDL files or new versions of software Upgrade software for Automatic Test Equipment (ATEs), Programmers, or Third Party Vendors ACN Details

4. Notification and Registration  Mail Lists will include: PCN List (Maintained by QA-includes email & regular mail) ATE List (Part of the registration required to download ATE translators for Genrad, HP and Teradyne systems) ACN List (Customers or sales may register to be notified of any new ACNs via the web. List will be maintained by Configuration Solutions)  Registration: Anyone can register via the web (under Configuration Solutions web page) to be placed on the ACN list Sales, for example can register appropriate customers, contract manufacturers, and components engineers