1、EIA JESD32 96 3234600 0575624 671 . (u o n rn W 7 EIMJEDEC STANDARD Standard for Chain Description File EINJESD32 JUNE 1996 ELECTRONIC INDUSTRIES ASSOCIATION ENGINEERING DEPARTMENT - EIA JESD32 96 3234600 0575625 708 NOTICE EWJEDEC Standards and Publications contain material that has been prepared,
2、progressively reviewed, and approved through the JEDEC Council level and subsequently reviewed and approved by the EIA General Counsel. EINJEDEC Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers and purchases, facilitatin
3、g interchangeability and improvement of products, and assisting the purchaser is selecting and obtaining with minimum delay the proper product for his particular need. Existence of such standards shall not in any respect preclude ar,! member or nonmember of JEDEC from manufacturing or selling produc
4、ts not conforming to such standards, nor shall the existence of such standards preclude their voluntary use by those other than EIA members, whether the standard is to be used either domestically or intemationally. EINJEDEC Standards and Publications are adopted without regard to whether their adopt
5、ion may involve patents or articles, materials, or processes. By such action, EWJEDEC does not assume any liability to any patent owner, nor does it assume any obligation whatever to parties adopting the EWJEDEC Standards or Publications. The information included in EWJEDEC Standards and Publication
6、s represents a sound approach to product specification and application, principally from the solid state device manufacturer viewpoint. Within the EIAIJEDEC organization there are procedures whereby an EWJEDEC Standard or Publication may be further processed and ultimately becomes an ANSVEIA Standar
7、d. Inquiries, comments, and suggestions relative to the content of this EWJEDEC Standard or Publication should be addressed to the JEDEC Executive Secretary at EU Headquarters, 2500 Wilson Boulevard, Arlington, VA 2220 1. Published by BELECTRONIC INDUSTRIES ASSOCIATION 1996 Engineering Department 25
8、00 Wilson Boulevard Arlington, VA 2220 1 “Copyright“ does not apply to JEDEC member companies as they are free to duplicate this document in accordance with the latest revision of the JEDEC Publication 2 1. “Manual of Organization and procedure“. PRICE: Please refer to the current Catalog of EIA, JE
9、DEC, and TIA STANDARDS and ENGINEERING PUBLICATIONS or call Global Engineering Documents, USA and Canada (1-800-854-7179) International (303-397-7956) Printed in U.S.A. All rights reserved EIA JESD32 96 m 3234600 0575627 580 m JEDEC STANDARD NO. 32 Page 1 STANDARD FOR CHAIN DESCRIPTION FILE (From JE
10、DEC Council Ballot JCB-95-84, formulated under the cognizance of JC-42.1 Committee on Programmable Logic Devices (PLD) ) 1 Introduction This standard was developed to define a Chain Description File that specifies protocol required to support in-circuit programming. The need for in-circuit programmi
11、ng is driven by high density devices with small lead pitches and high pin count, which are difficult to handle without damage. It is also evolving into a preferred prototyping and debugging environment. 1.1 Purpose and scope The purpose of Chain Description File is to defne the configuration of a pr
12、ogramming chain made up of devices that can be connected in some serial fashion. The only assumption is that data proceeds serially from device to device. No assumptions are made about how data is used by the device, nor about the nature or configuration of the control signals that affect configurat
13、ion. Hardware implementations including, but not limited to, JTAG are supported. Throughout this publication, JTAG refers to IEEE Standard 1 149.1. The chain may be homogeneous, consisting only of one protocol type, or may be heterogeneous, containing a mixture of devices. The programming system can
14、 be any kind of computing device capable of reading a JEDEC or other configuration file, the Chain file, and of processing a Driver that implements the configuration algorithm. Examples of such systems are personal computers (with the appropriate connecting cables), programmers, and automatic test e
15、quipment. The software driver is expected to know everything necessary about the device for programing, including algorithms, configuration file format, etc. No knowledge of the device is assumed by the Chain Description file. A driver may require input from the user in order to exercise options par
16、ticular only to that device or driver; the chain file format allows the user to input such device- or manufacturer-specific information. The Chain Description File also allows identification of nonprogrammable devices that share protocols like JTAG that may be in the same chain with programmable dev
17、ices. 1.2 Description The Chain Description File is a case-insensitive ASCII file intended to be easily generated and edited with a standard DOS or UNIX editor. It consists of a starting statement identifymg the file and the governing revision of this standard, declarations, records, and an ending s
18、tatement. Each record corresponds to a device in a chain and its location in file corresponds to its location in the Chain. JEDEC STANDARD NO. 32 Page 2 1.3 Revision history The revision number of this specification used by any tool or individual creating a Chain Description File should be recorded
19、in the file; see section 4 below. Revision JESDxxA Approved by JEDEC Council February 5, 1996 Initial release. 1.4 Definitions The following definitions clarie the meanhg of terms used throughout this document. Program Configure Veri Read User ID Mfi Code Ignore Host system To modify the logic conne
20、ctions inside a programmable device, causing its function to change. No assumption is made as to technology (EPROM, EEPROM, SRAM, etc.), nor to erasability. The device can implement logic, memory, or control. Tonfigure“ is used interchangeably. To modi the logic connections inside a PLD, causing its
21、 function to change. No assumption is made as to technology (EPROM, EEPROM, SRAM, etc.), nor to erasability. “Program“ is used interchangeably. To interrogate the internal configuration contents of a PLD. Used to confirm that a device has been correctly programmed by comparing the data in the device
22、 to that in an external file containing the desired configuration. Similar to reading, except that the contents of the PLD are not transferred to the programming system. To transfer the Configuration data from a PLD into a file. Similar to verification, except that the contents of the PLD are actual
23、ly transferred to the programming system. A programmable space on some devices that allows users to store non-functional data of any sort. Often used to track design revision numbers or other such idenmg information. A code assigned by JEDEC that identifies manufacturers. JEP-106 is the publication
24、containing the codes. To place a device in a chain into a “bypass“ mode, meaning that no operations are performed on that device. This would be used if devices in a chah were to be selectively programmed, for example. A programming system as described in the purpose and scope above. I EIA JESD32 96
25、= 323q600 0575629 353 JEDEC STANDARD NO. 32 Page 3 2 Notation conventions This document uses the Backus-Naur Form (BNF) to define the Syntax of the data transfer format. The BNF format is described below. - I:=“ denotes “is dened as“. - Characters enclosed by single quotes ( ) are literals (required
26、). - Angle brackets () enclose identifiers. - Square brackets ( 1) enclose optional items. - Braces (curly brackets) ( ) enclose an optional item which may be repeated. The item may appear zero or more times. - Vertical bars (-) indicate a choice between item. - Repeat cunts are given by a :n suffix
27、 and the number specifies the maximum number of characters or digits allowed. For example, a six digit number would be defned as “ := :.“ 2.1 Syntactic rules The following rules apply: - The character set is ASCII (a.k.a. IS0 Latin I) codes Ox00 to 0x7E - Keywords are not case sensitive (END, End, e
28、nd all mean the same). This rule also applies to manufacturer-specific keywords in quotes. - Whitespace consists of spaces, tabs, carriage returns, and line feeds. Whitespace may appear between any two other syntactic elements, which means anywhere there is a space in this description. - Every synta
29、ctic entity has one of the six forms: (1 ); (I I); I( I); (,“ “),; I(, := default declarations 3.1 File begin Marks the beginning of the Chain Description File (CDF) file. Provides a mechanism for the auto format detect and aids readability. Syntax: := JedecChain I; Example: JedecChain; 3.2 Fileend
30、Marks the end of the Chain Description File (CDF) file. The semicolon will mark the end of this field will prevent end of le errors when readrng this field. Syntax: := ChainEnd ;I Example: ChainEnd; - EIA JESD32 96 3234600 0575633 TO3 m JEDEC STANDARD NO. 32 Page 5 3.3 Comments A comment shall be tr
31、eated as whitespace and can appear anywhere whitespace can appear in the Syntax: := /*/ 4 File revision The file revision identifies the Chain De Chain Description File; any characters between /* and */ are ignored. rd revision cnption File (CDF) stand nd the S ociate syntax, attributes and other el
32、ements that are defined. The le revision will be the same as the JEDEC Standard number and revision assigned to this Standard (Example: JESDXXX where XXX is the 2 digit Standard number and the 1 digit Revision alpha) Syntax: : := FileRevision(); Example: FileRevision( JESDXXX); 5 Optional default de
33、clarations The Optional Default Declarations enables the user to specie the default Chain Description File properties, which includes the default path name for the computer system being used and the Device Manufacturers code. Optional Default Declarations are detaiied below. 5.1 Default path (option
34、al) The optional Dehult Path name specifies a directory on the host computer of where to read andor write data. The path depends on the host computer, including the characters that specie the directory and the trailing separator character if needed in the host system. The path is specified so that t
35、he full path name can be formed by concatenating the File Name onto the Path Name. If no Default Path is defined, the Path statement at the Device record will be next source for Path information. If none is found in the Device record, the Path will be determined by the system. Syntax: := DefaultPath
36、(l“); Example: DefaultPath(“C:VISKPRGM“); EIA JESD32 96 H 32314600 0575632 948 H JEDEC STANDARD NO. 32 Page 6 e Note that a path is by definition hostdependent, and limits the portability of the chain description file. True portability is only possible if system default paths are used throughout, an
37、d if all hosts have the required files in the system default path. 5.2 Default manufacturer (optional) The optional Defbult Manufacturer Code specifies the default manufacturers code for the JEDEC chain. The codes have been assigned by JEDEC, which are published in JEP106. A manufacturers code speci
38、fied in the data record will override the default manufacturers code. Syntax: := DefaultMfi(:4 I); Example: DefaultMfk( 1 i); 6 Chain site records (Nonprogrammable and programmable devices) For each device in the chain there is a Chain Site Record that describes the device and the operation to pedor
39、m. The order of the records in the Chain Description File corresponds to the order of the devices in the chain, i.e. there is a one-to-one mapping of the device in the Chain Description File and the physical routing of the device on the test fixture. The frst device in the chain is the one that rece
40、ives serial data rst. For example, even if serial data is passed through Device # 1 on its way to the last device in the chain (Device #N), the first device in the Chain Description File is Device #i vs Device #N. There are two types of device records, which define the type of device that the softwa
41、re is accessing, nonprogrammable and programmable. The nonprogrammable device has one set of required fields, while the programmable device has a different set of required fields. The record fields are described below, with a complete description of the syntax. Syntax: := P I NI 6.1 Action code The
42、Action Characters specifies the function to pedorm to the corresponding device. The list of Chain Description File commands are listed below: cfg: Configure (Program) rd: Read uid: Readuser ID EIA JESD32 9b I 3234600 0575633 884 JEDEC STANDARD NO. 32 Page 7 mid: ReadmfrID ign: Ignore ext: Get comman
43、d from external source. This could be a device programmer, host omputer, debugger, or any other tool that allows real-time control of the action to be aken . Syntax: := ActionCode( :3 I) Note that for the Configure code, erasure and verification may be included as part of the configuration process,
44、according to the programming algorithm of the device. No code is available for erasure only; if a manufacturer wishes to provide that capability, it should be handied in the Manufacturer-Specific section described below. 6.2 Programmable device description A programmable device is any device that ca
45、n be programmed while in a serial daisy chain. The programming algorithms and interfaces are vendor-specific and are implemented via vendor- supplied drivers. The following table identifies Required (R), Optional (O) and Not Allowed (NIA) Device Record Fields as a function of Action Code Selected. I
46、f a field marked “NIA“ is found in a chain description file, it should be treated as a syntax error. Cfg VfY Data Field MFIUDMFR R R R PN R R PathDPath O O File R R MFR Specif. O O Rd Uid Mid Ign Ext R R R R R R R R R O NIA NIA NIA O R NIA NIA NIA O O O O O O EIA JESD32 96 3234600 0575634 710 JEDEC
47、STANDARD NO. 32 Page 8 6.2.1 Programmable device record This Chain Description File format supports one or more device types for a given position in the serial daisy chain. For any given device record, there are two Fields (Part Type, and Action Code) which are common to any device type. All other F
48、ields are unique to a specific manufacturers part number and shall be preceded in the device record by the keyword “Device“. This facilitates easy documentation of alternative sources for a given chain position. See examples in Section 7 for proper use of the keyword “Device“. := Device ; 6.2.1.2 Ma
49、nufacturers code The manufacturers code uniquely identifes the manufacturer of the device in the chain. The mufacturers code is assigned by JEDEC and published in JEP106. Syntax: := PartName(:32 )I 6.2.1.4 Path name (optional) The path name, if different fiom the default path name, identifies where to read andor write data. The path depends on the host computer, including the characters that spece the directory and the trailing separator character
