throbber
1 of 8
`
` CROSSROADS EXHIBIT 2320
`Oracle Corp., et al v. Crossroads Systems, Inc.
` IPR2014-01207 and IPR2014-1209
`
`CROSSROADS EXHIBIT
`Oracle Corp. v. Crossroads Systems, Inc.
`IPR2015-0(cid:1005)(cid:1004)(cid:1010)(cid:1008)
`
`2320
`
`

`
`Verrazano Programmable Device Instructions
`Updated:U97U5797 11:41 AM
`
`
`
`mm
`
`The information contained herein is confidential
`
`in nature and IS to be used only with written
`
`Fhemformatbrmmtaimd-wflflkdewmemhasbeencmetwwcheckedandbbefievedmbe
`entirely reliable.
`However, no responsibility is assumed for
`inaccuracies.
`Furthermore,
`Crossroads Systems, |nc., reserves the right to change this document and product without notice
`
`
`lnc., 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.
`
`part of this dosumentmay 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, lnc.., 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
`
`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, lnc
`
`W
`Ewzs mu ,,
`2of8
`
`CRDS 50453
`
`2 of 8
`
`

`
`Verrazano Programmable Device Instructions
`Updated:(I97U57§7 11:41 AM
`
`
` Dexice Instructions: Table of Contents
`
`1.
`
`INTRODUCTION ............................................................................................... ... .................. .. 4
`
`2.
`
`PROTOCOL DRAM CONTROLLER (U27) ........................................................................... .. 4
`
`2.1
`2.2
`
`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
`
`Advin programming (U8) .................................................................... .; ........................... .. 5
`4.1
`4.2 ................................................................................... .. 6
`
`5. DRAM-CA3 PAL (U19) ......................................................................................................... ..
`
`. 6
`
`5.1
`5.2
`
`Advin prcrgramn1rrrg'(I:J‘I©) ............................................................................................... .. 6
`Manufacturingprogramming (U19) ................................................................................. .. 6
`
`6.F .......................................... .. 7
`
`6.1
`6.2
`Manufacturing programming (U28) ................................................................................. .. 7
`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
`
`QZI'T_EIRI‘-«IEYS '
`EYES ONLY
`3of8
`
`CRDS 50454
`
`3 of 8
`
`

`
`Verrazano Programmable Device Instructions
`
`Updated:O9/05/97 11:41 AM
`
`
`
`1. Introduction
`
`This document outlines the steps to program the various programmable hardware elements on
`Verrazano.
`
`
`
`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
`
`
`
`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 me name shoulEl‘be specmed using the File -> Name -> *.pof where *.pofTs the file
`mmed
`
`
`
`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.
`
`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
`
`3.
`
`
`
`make command is executed under Korn shell from the MKS toolkit.
`
`4 of 8
`
`4
`
`Crossroads Systems, Inc
`
`RTFFDRNEVST I
`sates BNLY
`4of8
`
`C3115 513455
`
`4 of 8
`
`

`
`Verrazano Programmable Device Instructions
`
`
`
`Update 1’1:4’|
`/-WI
`
`
`3. Revision indicator PAL (U26)
`
`3. 1 Advin programming (U26)
`1. This image is contained in the appropriate subdirectory under
`\\Crossroads\source\VerrazanoThw\grogrammables\mlsc gal\u26. The appropriate
`
`
`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 DIP package type should be selected using the Configure -> Others -> Package type ->
`D’rP"optloTrs
`
`5. m m->mm—>m
`mmed
`
`&
`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 shou|d"be copied onto a cfiskette.
`
`
`
`"Si:i "U v
`
`’
`
`’u
`
`‘G I ‘u“'i i
`
`‘
`
`ia
`
`
`
`contains a Makefile that performs these steps using the command “make disk”.
`make command is executed under Korn shell from the MKS toolkit.
`
`‘I“u
`
`I
`
`6 vi ““ If v‘
`
`
`In general, this
`
`4. General PAL (U8)
`
`4.1 Advin programming (U8)
`1. This image is contained in the appropriate subdirectory under
`
`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 —>
`DlP eptiens.
`
`5 of 8
`
`5
`
`Crossroads Systems, Inc
`
`QTTDRNEYS’
`
`5%¥E5 5”‘-‘V’
`
`CV55 59456
`
`5 of 8
`
`

`
`Verrazano Programmable Device Instructions
`
`Updated:U9705797 11:4‘l NV!
`
`
`
`5. The image file name should be specified using the File -> Name -> *.j1 where *.j1 is the file
`nameofthemrageflte.
`
`
`
`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,
`I.
`¢Vu_
`.I'I
`"'
`‘I’: I‘: .u 1"!
`. Ii’:
`make command is executed under Korn shell from the MKS toolkit.
`
`5.DR.AMC.ASpalLU19)
`
`5. 1 Advin programming (U19)
`1. This image is contained in the appropriate subdirectory under
`\\Crossroads\source\Verrazano\hw\programmables\misc pal\u19. The appropriate
`
`
`
`called *.j1 which is a jedec file.
`
`2. The programmer should be initialized using the spGAL software module (first screen).
`The 1518
`'
`'
`->
`'
`->
`—>
`
`opfions
`
`4. The DIP package type should be selected using the Configure —> Others —> Package type —>
`DTP options.
`
`5. The Image file name should be specified using the File -> Name —> *.j1 where *.j1 is the file
` .
`
`6.
`
`
`displayed on the screen.
`
`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.
`
`ThepmgrammedpadjslabeledmdththeplaUmmE
`include the date, the reference designator, and the checksum.
`
`5.2 Manufacturing programming (U19)
`1. The *.j1 file should be copied onto a diskette.
`
`6 of 8
`
`6
`
`Crossroads Systems, Inc
`
`QTTDRNEY5 '
`EYES DNLV
`6of8
`
`cans 5o457
`
`6 of 8
`
`

`
`Verrazano Programmable Device Instructions
`
`Updated:O9/O5/97 11:41 AM
`
`
`
`2. A README file should be created and copied onto the diskette. The README should contain
`informafion aboufthe part (eg. Checksum, file name, part number)
`
`3. The diskette shoulcfbe 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,
`
`
`6. FLASH (U28)
`
`6.1 Advin programming (U28)
`1. This image is contained in the appropriate subdirectory under
`\\Crossroads\source\Verrazano\hw\grogrammablesfilash. The appropriate subdirectory is
`a
`nu u
`viva
`‘cw _
`.-
`
`
`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‘fhe image file.
`
`6. The file shou|d’then be downloaded using the File —> Load —> Buffer 0 options. The checksum
`s
`
`
`
`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.
`‘Fl=iis—sheuLleFereate—a *.exe file.
`
`The*. .
`
`A
`explain how to extract the zip file, the checksum, the filename, etc.
`
`
`
`contains a Makefile that performs these steps using the command “make disk".
`make commandfis executed under Korn shell'from the MKS toolkit.
`
`In general, this
`
`7 of 8
`
`7
`
`Crossroads Systems, lnc
`
`FYTTURNEVS ’
`Eves SNLY
`7of8
`
`C395 W458
`
`7 of 8
`
`

`
`Updated:09/05/97 11:41 AM
`Verrazano Programmable Device Instructions
`
`
`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, opfionally Include the date, the reference designator, ancrthe checksum.
`
`8 of 8
`
`8
`
`Crossroads Systems, Inc
`
`QTTDRNEYS ’
`§‘E?§UNLV
`
`cnos 5a459
`
`8 of 8

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket