1 of 8
`
` CROSSROADS EXHIBIT 2320
`Oracle Corp., et al v. Crossroads Systems, Inc.
` IPR2014-01207 and IPR2014-1209
`
`CROSSROADS EXHIBIT 2320
`NetApp Inc. v. Crossroads Systems, Inc.
`IPR2015-00773
`
`

`

`Verrazano Programmable Device Instructions
`Updated:09/05/97 11:41 AMx. 5:”
`
`
`
`
`Manager: John Middleton
`Authors: Rich Umberhocker
`
`The information contained herein is confidential
`permission from Crossroads Systems, Inc.
`
`in nature and is to be used only with written
`
`The information contained in this document has been carefully checked and is believed to be
`entirely reliable.
`However, no responsibility is assumed for
`inaccuracies.
`Furthermore,
`Crossroads Systems, Inc., reserves the right to change this document and product without notice
`and to make improvements In reliability, function and design without notice. Crossroads Systems,
`Inc., neither assumes any liability arising out of the application or use of any product, software or
`circuit described herein, nor does it convey any license under its right or the rights of others.
`Companies, names, and data used in examples herein are fictitious unless otherwise noted. No
`part of this document may be reproduced or transmitted in any form or by any means, electronic,
`mechanical, for any purpose, without the express written permission of Crossroads Systems, Inc.
`
`© 1997 Crossroads Systems. All rights reserved.
`
`Crossroads Systems is a trademark of Crossroads Systems, Inc.., in the USA and other
`countries.
`
`Copyright © 1997
`Crossroads Systems, Inc.
`Suite ll — 300
`9390 Research Blvd.
`Austin, Texas 78759
`
`Voice:
`Fax:
`
`(512) 349-0300
`(512) 349-0304
`
`info@crossroads.com
`support@crossroads.com
`http://www.crossroads.com
`
`Printed in the United States of America.
`
`Revision History
`Date: 8/18/97 Revision 1.0 Initial release of document
`
`2 Of 8
`
`2
`
`Crossroads Systems, Inc
`
`QTTDRNEYS '
`EYES DNLY
`20f8
`
`CRDS 50453
`
`2 of 8
`
`

`

`Verrazano Programmable Device Instructions
`Updated:09/05/97 11:41 AM
`""hfi;
`
`
`Verrazano Programmable Device Instructions: Table of Contents
`
`1.
`
`2.
`
`2.1
`2.2
`
`INTRODUCTION .................................................................................................L .................... 4
`
`PROTOCOL DRAM CONTROLLER (U27) ............................................................................. 4
`
`Advin programming (U27) ................................................................................................. 4
`Manufacturing programming (U27) ................................................................................... 4
`
`3. REVISION INDICATOR PAL (U26) .......................................................................................... 5
`
`3.1
`3.2
`
`Advin programming (U26) ................................................................................................. 5
`Manufacturing programming (U26) ................................................................................... 5
`
`4. GENERAL PAL (U8) .............................................................................................................
`
`5
`
`4.1
`4.2
`
`............................. 5
`Advin programming (U8)
`Manufacturing programming (U8) ..................................................................................... 6
`
`5. DRAM CAS PAL (U19) ...........................................................................................................
`
`.6
`
`5.1
`5.2
`
`Advin programming (U19) ................................................................................................. 6
`Manufacturing programming (U19) ................................................................................... 6
`
`6.
`
`FLASH (U28) ............................................................................................................................ 7
`
`Advin programming (U28) ................................................................................................. 7
`6.1
`Manufacturing programming (U28) ................................................................................... 7
`6.2
`7. DEVICE LABELING SPECIFICATION .................................................................................... 8
`
`Hyperlinks to documents contained herein (click on page number):
`
`DA40004, Device labeling specification on page 8.
`
`3 of 8
`
`3
`
`Crossroads Systems, Inc
`
`FtTTDRIaIEYS '
`EYES ONLY
`3of8
`
`cans 5o454
`
`3 of 8
`
`

`

`/r
`Verrazano Programmable Device Instructions
`Updated:09/05/97 11:41 AM
`
`
`1. Introduction
`
`This document outlines the steps to program the various programmable hardware elements on
`Verrazano.
`
`This document only covers details on how to program the parts in the lab and how to give
`manufacturing the diskettes to program the parts. The document does not cover any details of
`how manufacturing may program the parts.
`
`It is recommended
`The device used to program the parts is the ADVIN programmer in the lab.
`that the users guide be used to better understand how to use the equipment.
`
`2. Protocol. DRAM controller (U27) »
`
`2.1 Advin programming (U27)
`1. This image is contained in the appropriate subdirectory under
`\\Crossroads\source\Verrazano\hw\programmables\garner. The appropriate subdirectory is
`named after the part number of the programmed device. This image file is called *.pof which
`is an Altera image file.
`
`2. The programmer should be initialized using the spM software module (first screen).
`
`3. The 16v8 device should be selected using the Configure -> Device -> Altera -> EPC1 options.
`
`4. The PLCC package type should be selected using the Configure —> Others -> Package type —
`> PLCC options.
`
`5. The image file name should be specified using the File —> Name -> *.pof where *.pof is the file
`name of the image file.
`
`6. The file should then be downloaded using the File —> Load options. The checksum should be
`displayed on the screen.
`
`The part should then be programmed using the PAL (device) —> Program options.
`
`The checksum should be verified to be correct after the programming took place.
`
`If there is enough room on the label, optionally
`The programmed part is labeled with the pm.
`include the date, the reference designator, and the checksum.
`
`2.2 Manufacturing programming (U27)
`1. The *.pof file should be copied onto a diskette.
`
`2. A README file should be created and copied onto the diskette. The README should contain
`information about the part (eg. Checksum, file name, part number)
`
`3. The diskette should be labeled with the part number for the image file.
`
`The image directory, i.e. the directory named for the part number of the programmed device,
`contains a Makefile that performs these steps using the command “make disk”.
`In general, this
`make command is executed under Korn shell from the MKS toolkit.
`
`4 of 8
`
`4
`
`Crossroads Systems, lnc
`
`RTTDRNEYS ’
`EYES DNLY
`4of8
`
`CRDS 58455
`
`4 of 8
`
`

`

`Verrazano Programmable Device Instructions
`
`
`Updated:09/05/97 11:41 AM
`
`
`3. Revision indicator PAL (U26)
`
`3. 1 Advin programming (U26)
`1. This image is contained in the appropriate subdirectory under
`\\Crossroads\source\Verrazano\hw\grogrammables\misc gal\u26. The appropriate
`subdirectory is named after the part number of the programmed device. This image file is
`called *.j1 which is a jedec file.
`
`2. The programmer should be initialized using the spGAL software module (first screen).
`
`3. The 16v8 device should be selected using the Configure -> Device —> AMD -> PALCE16v8
`options.
`
`4. The DlP package type should be selected using the Configure -> Others -> Package type ->
`DlP options.
`
`5. The image file name should be specified using the File -> Name -> *.j1 where *.j1 is the file
`name of the image file.
`
`6. The file should then be downloaded using the File -> Load options. The checksum should be
`displayed on the screen.
`
`7. The part should then be programmed using the PAL (device) —> Program options.
`
`8. The checksum should be verified to be correct after the programming took place.
`
`If there is enough room on the label, optionally
`9. The programmed part is labeled with the p/n.
`include the date, the reference designator, and the checksum.
`
`3.2 Manufacturing programming (U26)
`1. The *.j1 file should be copied onto a diskette.
`
`2. A README file should be created and copied onto the diskette. The README should contain
`information about the part (eg. Checksum, file name, part number)
`
`3. The diskette should be labeled with the part number for the image file.
`
`The image directory, i.e. the directory named for the part number of the programmed device,
`contains a Makefile that performs these steps using the command “make disk”.
`In general, this
`make command is executed under Korn shell from the MKS toolkit.
`
`4. General PAL (U8)
`
`4.1 Advin programming (U8)
`1. This image is contained in the appropriate subdirectory under
`\\Crossroads\source\Verrazano\hw\grogrammables\misc gal\u8. The appropriate
`subdirectory is named after the part number of the programmed device. This image file is
`called *.j1 which is ajedec file.
`
`The programmer should be initialized using the spGAL software module (first screen).
`
`The 16v8 device should be selected using the Configure -> Device -> AMD -> PALCE16v8
`options.
`
`4. The DlP package type should be selected using the Configure —> Others -> Package type —>
`DIP options.
`
`5 of 8
`
`5
`
`Crossroads Systems, Inc
`
`QTTDRNEYS'
`
`5%YES ONLY
`
`CRDS 5D456
`
`5 of 8
`
`

`

`Verrazano Programmable Device Instructions
`Updated:09/O5/97 11:41 AM
`:mw
`
`5. The image file name should be specified using the File —> Name —> *.j1 where *.j1 is the file
`name of the image file.
`
`6. The file should then be downloaded using the File -> Load options. The checksum should be
`displayed on the screen.
`
`The part should then be programmed using the PAL (device) -> Program options.
`
`The checksum should be verified to be correct after the programming took place.
`
`if there is enough room on the label, optionally
`The programmed part is labeled with the p/n.
`include the date, the reference designator, and the checksum.
`
`4.2 Manufacturing programming (U8)
`1. The *.j1 file should be copied onto a diskette.
`
`2. A README file should be created and copied onto the diskette. The README should contain
`information about the part (eg. Checksum, file name, part number)
`
`3. The diskette should be labeled with the part number for the image file.
`
`The image directory, i.e. the directory named for the part number of the programmed device,
`contains a Makefile that performs these steps using the command “make disk”.
`in general, this
`make command is executed under Korn shell from the MKS toolkit.
`
`5. DRAM CAS pal (U19)
`
`5. 1 Advin programming (U19)
`1. This image is contained in the appropriate subdirectory under
`\\Crossroads\source\Verrazano\hw\grogrammables\misc pal\u19. The appropriate
`subdirectory is named after the part number of the programmed device. This image file is
`called *.j1 which is a jedec file.
`
`2. The programmer should be initialized using the spGAL software module (first screen).
`
`The 16v8 device should be selected using the Configure -> Device -> AMD -> PALCE16v8
`options.
`
`4. The DlP package type should be selected using the Configure —> Others —> Package type ->
`DlP options.
`
`5. The image file name should be specified using the File —> Name -> *.j1 where *.j1 is the file
`name of the image file.
`
`6. The file should then be downloaded using the File -> Load options. The checksum should be
`displayed on the screen.
`
`The part should then be programmed using the PAL (device) -> Program options.
`
`The checksum should be verified to be correct after the programming took place.
`
`If there is enough room on the label, optionally
`The programmed part is labeled with the p/n.
`include the date, the reference designator, and the checksum.
`
`5.2 Manufacturing programming (U19)
`1. The *.ji file should be copied onto a diskette.
`
`6 of 8
`
`6
`
`Crossroads Systems, lnc
`
`QTTDRNEYS’
`EYES ONLY
`60f8
`
`cans 50457
`
`6 of 8
`
`

`

`Verrazano Programmable Device Instructions
`Updated:09/05/97 11:41 AMM,
`
`2. A README file should be created and copied onto the diskette. The README should contain
`information about the part (eg. Checksum, file name, part number)
`
`3. The diskette should be labeled with the part number for the image file.
`
`The image directory, i.e. the directory named for the part number of the programmed device,
`contains a Makefile that performs these steps using the command “make disk".
`In general, this
`make command is executed under Korn shell from the MKS toolkit.
`
`6. FLASH (U28)
`
`6.1 Advin programming (U28)
`1. This image is contained in the appropriate subdirectory under
`\\Crossroads\source\Verrazano\hw\grogrammables\flash. The appropriate subdirectory is
`named afterthe part number of the programmed device. This image file is called *.hex which
`is an intel binary file.
`
`While the programmer is off, insert the TSOP 48 pin module into the programmer.
`
`The programmer should be initialized using the spEE software module (first screen).
`
`The 29FO16 device should be selected using the Configure -> Device —> AMD -> 29F016
`options.
`
`5. The image file name should be specified using the File —> Name -> *.hex where *.hex is the
`file name of the image file.
`
`6. The file should then be downloaded using the File -> Load -> Buffer 0 options. The checksum
`should be displayed on the screen.
`
`7. The part should then be programmed using the PAL (device) -> Program options.
`
`8. The checksum should be verified to be correct after the programming took place.
`
`if there is enough room on the label, optionally
`9. The programmed part is labeled with the p/n.
`include the date, the reference designator, and the checksum.
`
`6.2 Manufacturing programming (U28)
`1. The *.hex file should be zipped using pkzip. (The reason for this is because the *.hex file is
`greater than 2 Mbytes.
`
`2. The *.zip file should be converted to a self extracting zip file using the zip2exe application.
`This should create a *.exe file.
`
`The *.exe file should be copied onto a diskette.
`
`A README file should be created and copied onto the diskette. This README should
`explain how to extract the zip file, the checksum, the filename, etc.
`
`5. The diskette should be labeled with the part number for the image file
`
`The image directory, i.e. the directory named for the part number of the programmed device,
`contains a Makefile that performs these steps using the command “make disk".
`In general, this
`make command is executed under Korn shell from the MKS toolkit.
`
`7 of 8
`
`7
`
`Crossroads Systems, lnc
`
`ATTORNEYS ’
`EYES DNLY
`7of8
`
`CRDS SB4SB
`
`7 of 8
`
`

`

`Verrazano Programmable Device Instructions
`
`Updatedz09/05/97 11:41 AM
`
`
`
`Title: CP41OO device labeling instructions
`
`Word File: PLD_instructions.doc.doc
`
`specification, and the page number below is meaningless.)
`
`Drawing Number: DA40004, Rev A
`Author: Rich Umberhocker
`
`(This document source is a collection of similar specifications. This page is a self—contained
`
`7. Device labeling specification
`
`If there is enough
`The programmed part must be labeled with the p/n of the programmed part.
`room on the label, optionally include the date, the reference designator, and the checksum.
`
`8 of 8
`
`8
`
`Crossroads Systems, Inc
`
`nTTDRI‘lEYS ’
`513?? ONLY
`
`cans 50459
`
`8 of 8
`
`