SVTL Basic Training 2 ©2002 Cypress Semiconductor SVTL Basic Training Outline 1.Terms and Concepts 2.Test Scripts Overview 3.Test Configurations 4.Drive

SVTL Basic Training

2

©2002 Cypress Semiconductor

SVTL Basic Training Outline1. Terms and Concepts2. Test Scripts Overview3. Test Configurations4. Drive Imaging (hands-on)5. SVTL FAQ’s & Tidbits

3


SVTL Basic Training Outline1. Terms and Concepts2. Test Scripts overview3. Test Configurations4. Drive Imaging (hands-on)5. SVTL FAQ’s & Tidbits

4


System ValidationWhat is System Validation?Conceptual structure of System Validation (SV)

Matrix database Test Scripts Test Suites Test Configurations Test Sessions Test Suite Worksheets

5


Defects & Tracking

What is a Defect? Clear Quest (CQ)

Project oriented Good at reports Web or client interface Primary tracking tool in Boise Growing use elsewhere Kyle Kumasaka - administrator

Test Track (TT) Used by some project teams including HX2 Web based interface Not great for multiple projects Poor reporting tools

How do CQ, TT, and Matrix compare?

6


Miscellaneous TermsHost Controller A board or motherboard chipset that acts as the Host for a USB connection, aka Host Controller Interface (HCI).

UHCI (Universal HCI) OHCI (Open HCI) EHCI (Enhanced HCI)

Root HubThe ports of a Host Controller Interface. Sometimes it is helpful to view these in Device Manager but this is not obvious how to do:

View By Connection in Device Manager.

Note USB Root Hubs are now shown under their appropriate Host Controllers.

7


Miscellaneous Terms (cont.) Competitive AnalysisTesting done to highlight strengths and weaknesses of one product over another. Sometimes used for Marketing to provide ammunition against competitive products, sometimes to help Engineering improve our own products.

Enumeration and MountingEnumeration is a lower level of USB connection, where driver levels load.Mounting is the higher level of USB connection where a drive is found by the OS. In Windows, the drive will be seen in Device Manger (sometimes no drive letter if it has no partitions).

Field Programmable Gate Array (FPGA) Quick turn design board that enables Engineering to make a quick Test/Fix loop with SV.

Application Specific Integrated Circuit (ASIC)The chip with the brains and processing power in a product design.

DOS USB Extensions (DUSE) A driver set that enables DOS applications to access USB. Examples?

8


Miscellaneous Terms (cont.)DUT(Device Under Test)

OS (Operating System)

EEPROM (Electrically Erasable Programmable Read Only Memory)

Bits Specifi y programmed EEPROMs

IP (Intellectual Property)

Code Version An SV coined term to keep track of testing activities for reporting purposes

Bridge An interface that connects one technology or protocol to another

USB Universal Serial Bus is a connectivity protocol allowing peripheral devices to connect to computers and other electronic devices. Allows live connection (in Windows, called Plug & Play). Two different protocols specifications, major difference is speed.

USB 1.1 – 12Mbits/second, aka Classic mode (released in 1998) USB 2.0 – 480Mbits/second (released in 2001)

1394 aka FireWire A protocol similar to USB for providing live connectivity to peripheral devices.

9


Product Terms – ISD ASICsUSS725

Rev C and D still in use for printing bridge (USB to parallel) Designed as Printer Class chip Adapted for Storage – never class compliant USB 1.1 only

ISD200 Made for Iomega ATAPI devices are Mass Storage Class (MSC) compliant ATA devices are Vendor Specific USB 1.1 only

ISD300 All are fully MSC compliant USB 1.1 and 2.0 (first bridge chip, currently has 85% market share for storage) ISD300FR1 = ISD300MR2 ISD300A limited release ISD300A1 currently shipping rev. Silk screen debacle (only rely on ones that have A1 in silk screen or writing)

10


Product Terms - CY ASICs

FX2 Multi-purpose USB2.0 bridge – has many variations Developers Kit (DVK) for customers to design their own product

- SX2 for scanners, imaging – not tested in SV so far- MX2 for storage applications- HX2 - USB2.0 Multi-TT hub

MX2 Storage bridge variant of FX2 MSC for ATA and ATAPI USB1.1 and 2.0 Many names have been bounced around – Marketing calls it “AT2” Silicon based on firmware rev. RC15

11


Product Terms - SL ASICsScanLogic ASICs

SL11R-IDE- USB 1.1 only- MSC compliant- Becoming obsolete (may be now)

NandFlash = Slinky(1 & 2)- USB 1.1 only- Flash memory product- In prototype phases now

12


Product Terms - DriversStorage Drivers

Windows Drivers- Provide access to storage devices (over USB)- Falstaff (obsolete) – for USS725 chip to make storage-compatible- Braveheart (obsolete) - for ISD200 chip for AT storage application- Patriot, aka TPP= The Patriot Project

- Combined Falstaff & Braveheart capability with all current ASIC support (USS725 has since been made fully obsolete and is no longer supported but was up until TPP 5.1)

- Offers enhancements/value-add features over MSC driver- Provides support for Windows 98SE, ME, 2K, and XP

- MSC – Mass Storage Class driver- Only available in Windows ME, 2K, and XP

Mac Drivers- Provide access to storage devices (over USB)- David – (obsolete) – for storage-compatibility for the USS725 chip- Macleod

- support for all supported ISD, CY and SL storage ASICs- Mac OS 9.x only

- Morpheus- support for all supported ISD, CY and SL storage ASICs- Mac OS 10.x only

- ASC – Apple Storage Class driver

13


Product Terms – Drivers (cont.)

Host Controller Drivers Host Controller drivers are provide Windows with a mechanism to

communicate via a Host Controller Interface, either USB 1.1 (UHCI or OHCI or USB2.0 EHCI). UHCI and OHCI drivers are automatically installed with Windows or when a card is added, but EHCI drivers are installed manually and have taken a long time to get stabilized.

MS HCD – Microsoft Host Controller Driver 3rd Party – Adaptec, OrangeMicro, NEC, others Microsoft provides built-in USB 2.0 HCDs for XP only, and beta drivers for

2K. 98SE and ME are supported by 3rd Party vendors and 95 and 98Gold are not supported.

14


More USB Terms HID (Human Interface Device)

Low Speed (LS) USBAs defined by the USB 1.1 Spec, these are devices that don’t pass a lot of data, typically HID type devices. The data rate is 1.5 Mbit/second. Devices include:

Mice Keyboards Gamepads UPS systems, etc.

Full Speed (FS) USBAs defined by the USB 1.1 Spec, this is the broadest category of USB devices. The data rate is 12 Mbit/second, approximately 10BaseT LAN speed. Devices include:

LAN cards (USB to Ethernet) Camera Storage devices Scanners, etc.

High Speed (HS) USBAs defined by the USB 2.0 Spec, these are the fastest devices that USB currently offers, with a data rate of 480 Mbit/second. Devices include:

Hubs Storage devices Cameras (most recently), etc.

15


More USB Terms (cont.)

Classic speed – another term used for LS and FS / USB 1.1 type traffic

USB 2.0 HubsThe USB2.0 hub is possibly the most complicated device in USB technology. A hub must handle LS and FS traffic and possibly HS traffic in both directions, and it must route data to appropriate devices. USB2.0 hubs operate natively in HS mode. Things to remember are:

Upstream – in the direction of the Host or Host Controller Downstream – away from the Host Controller (outgoing ports) Transaction Translator – the processor that converts individual datastreams from HS to Classic

speeds for individual devices. Single-TT – One Transaction Translator for the entire hub, meaning all Classic speed traffic must

share one 12 Mbit/second channel. Multi-TT - One TT per port, meaning each Classic speed datastream gets full 12 Mbit/second

bandwidth.

ChirpThe handshake that a HS device sends upstream to the host to say it is HS capable.

16


Storage TermsDrive LetterA logical representation of a physical drive used by Windows. The drive letter assigned to a drive varies depending upon what other drive letters are assigned on a given system, in conjunction with what order drives are mounted by the OS.

Drive Label (or Volume Name in Mac)A logical representation of a physical drive that usually goes in conjunction with a drive letter in Windows. The Label or volume name stays with a partition of a drive, regardless of the system that it resides on and what drive letter it is assigned.

The Storage Terms on the following few pages are provided for reference and background information, since we refer to these terms periodically in the SVTL. They are all interrelated. It is not important for our purposes to know much about these terms or exactly what the differences are between them, but more to be aware of the general idea of the terms.

17


Storage Terms (cont.)

PIOProgrammed I/O – a protocol in PC architecture for managing IO devices that involves the CPU in every data transaction. PIO has performance levels 1-4. PIO is a predecessor to ATA.

ATAAdvanced Technology Attachment – another name (the ANSI name) for IDE. ATA utilizes DMA for data transfer. Ultra-ATA is a newer, faster version that corresponds to UDMA (see below for DMA and UDMA). The ATA protocol is defined in performance levels 0-6.

IDE Integrated Drive Electronics – a protocol to allow the motherboard to communicate with storage devices directly without involving the CPU, based upon DMA .

ATAPIAT Attachment Packet Interface – a superset protocol of ATA, allowing CD-ROM and other non-hard drive devices to communicate via additional commands. ATAPI is part of the Enhanced IDE (EIDE) interface (also known as ATA-2).

DMADirect Memory Access – the data transfer protocol that allows ATA and ATAPI devices RAM memory access without CPU involvement. A newer, faster variation is UDMA.

18


Storage Terms (cont.)PartitionA logical division of a physical hard drive’s space. A partition creates the appearance of having multiple physical drives. Three types of partitions are used in the Windows environment – Primary, Extended and Logical.

Windows 9X OS’s must be loaded on a Primary partition and will only acknowledge 1 Primary partition (others are hidden by a 9X OS). An Extended partition can be created after at least one Primary partition exists, but cannot be used by itself – one or more Logical partitions are created within an Extended partition, each then in turn can be formatted and used for storage or loading and OS.

Format- A way of making a drive’s available space usable and referenceable by the OS

FAT (File Allocation Table) and FAT32- A standard for disk formatting. FAT (aka FAT16) formatting can only reference disk drives that are 2GB or smaller

and cannot handle long file names (those other than the 8.3 naming convention). FAT32 has a 32GB max disk size limitation, however either Windows XP or ME has changed the FAT32 size limitation to something larger that 32GB. FAT32 can handle long file names, if the OS supports them.

NTFS (NT File System)- Another standard for disk formatting, used only by Windows OS’s based upon NT (a Windows term, New

Technology). NTFS is a more efficient, more secure disk formatting mechanism. It also supports long file names. Drive sizes of much larger than 32GB are allowed.

- Some information for these Storage Terms was paraphrased from www.whatis.com

19


Imaging Terms What does it mean to create an Image?In reference to imaging a PC storage drive, creating an Image is like creating a snapshot of the exact contents of a drive partition (or entire drive) including all installed OS’s, applications, files, registry settings, etc. It is an exact, complete backup of the original drive or partition.

Drive – Imaging programs can see more than one physical drive Source – the drive location or partition to be backed up Destination – the drive location or partition to store the Image file(s)

PQDI (Power Quest Drive Image)

Ghost

20


SVTL Basic Training Outline1. Terms and Concepts

2. Test Scripts Overview3. Test Configurations4. Drive Imaging (hands-on)5. SVTL FAQ’s & Tidbits

21


Test Scripts OverviewSV Test scripts vary in content by purpose of test suite. Each suite has been tailored to target a particular gap or niche. Most tests get used for Driver, ASIC, and Board (including Hub) testing where appropriate.

Storage Tests Enumeration – simplest, quickest suite for high frequency, used for Level 1

qualification Pre-Qualification – simple, quick, but more in-depth than Enum Functionality – simple but robust, longer timeframe, some software application

involvement DVD Functionality - runs a DVD-ROM drive through most possible DVD

capabilities Interoperability – complex, involving many types of devices and applications Boot – thorough and repetitive focus on cold and warm boot activities CD-Authoring (full and light) – focus on various ways of working with CD-RW

drives Driver Installer – focus is on TPP driver installer and how it works with various

devices/OS’s

22


Test Scripts Overview (Cont.)

Hub Tests• Hub - general purpose test to exercise USB hub capabilities. This is a long,

broad-sweep suite

• LS, LSFS, LSHS, FSHS, AllSpeed - Hub tests designed around the HX2 hub

• GoldTree - 2.0 suite that walks tester through the procedure used in USB-IF compliance testing

• Cable Length - a short test that exercises hubs’ ability to handle mixed data streams while multiple different length cables connect various peripherals.

• Vendor-specific (i.e.: Fujitsu) - a suite of tests to focus on a particular board or device

• Others are created as need arises

23


SVTL Basic Training Outline1. Terms and Concepts2. Test Scripts Overview

3. Test Configurations4. Drive Imaging (hands-on)5. SVTL FAQ’s & Tidbits

24


Test Configurations Selection1. Select a “pending” location on the Test Configuration

chart ORSelect a Test Script to be evaluated from a Failure Report

1. Determine the type of Tests Suite2. Determine the OS to be used3. Determine which (if any) storage devices are to use4. Determine the Bridge (board and ASIC)5. Determine the Storage Driver6. Determine the appropriate HC7. Determine the HC Driver8. Determine the USB Mode9. Determine the appropriate Code Version

25


Test Configurations Headings (noted by )In the headings are described many of the general details that are to beused for all the various scripts such as:

Windows or Mac Device Under Test (DUT) such as a Board, ASIC, or Driver Drivers to be used and their Versions

Keys (noted by )Several Keys are used to show additional information, typically by colorcoding, for example:

Pending or Complete (shows status of particular test suites) The color of the text of the suite name indicates the Host Controller from

the Key to use for that particular test suite Storage Drivers are indicated by color coded column

26


Test Configurations OS Columns(noted by ) Columns show both OS and which storage drivers (as

shown in the Key) are to be used all test suites in that column and OS.

Device Rows(noted by )

Categories of storage devices are shown by Type (ie: CDRW, 3.5” HD, etc.) and specific drive models are often recommended in the Device Model section, though they need not be absolute in most cases and substitutions for similar devices is OK.

27


Test Configurations (eg)

28


Master Test List

The Master Test List is the com-bination of the Test Scripts fromeach unique Test Suite (though not including duplicates when a suite isrun in a different configuration).

For example, the Master Test Listmay include the scripts from theBoot, Pre-Qual, Functionality, IO,and Hub Test Suites.

29


Test Groups

PLUG-N-PLAYINSTALLERENUMCOPYSTANDBY/SLEEPMANUALCOMPLIANCECD / DVD WRITE PROTECTERRORSREMOVAL/UNINSTALLFORMAT/SCAN

NETWORKEZ CD CREATORBHA B's RecorderAdaptec's Direct CDBHA B's ClipNERO BURNMAC CDROS CDBurningOther CDBurningITUNESRETROSPECTCD MOUNTING

CONTROL STRIPAPPLE CD PLAYER - DIGITALBOOTHUB TESTSPERFORMANCEWHQLOS UPGRADESATA_SecurityVerity_VID_PIDSonyInteroperabilityUSB_MultispeedAudio_VideoVERIFY

30


Test Groups

PLUG-N-PLAYINSTALLERENUMCOPYSTANDBY/SLEEPMANUALCOMPLIANCECD / DVD WRITE PROTECTERRORSREMOVAL/UNINSTALLFORMAT/SCAN

NETWORKEZ CD CREATORBHA B's RecorderAdaptec's Direct CDBHA B's ClipNERO BURNMAC CDROS CDBurningOther CDBurningITUNESRETROSPECTCD MOUNTING

CONTROL STRIPAPPLE CD PLAYER - DIGITALBOOTHUB TESTSPERFORMANCEWHQLOS UPGRADESATA_SecurityVerity_VID_PIDSonyInteroperabilityUSB_MultispeedAudio_VideoVERIFY

Test Groups are logical groupings of test scripts describing the kind of testingactivity that occurs in that script. For example, if a test script requires a copy to beexecuted, then this would fit into the COPY group. Many test scripts include more than one grouping because the type of testing activityinvolves one thing going on while another is going on. For example, a script may say to place a PC into standby while a copy is going on. The first activity mentioned is theprimary Test Group. The next activity requested is the Test Group 2.

31


Linking Test Suites, Groups, and the Master Test List

The Test Plan will contain a list of Test Groups to be run for a particular project.

The Master Test List will contain the specific scripts and the groupings the each script includes but will be organized by Test Suite.

The Test Configuration sheets lay out a mapping of the Test Suites to be associated with each particular type of device, driver, and OS.

{ENUM

32


Test Worksheets Worksheet Header information

Tester name or initials or TLA SV Test PC number What OS is this test suite being run in? Is the storage device in Master or Slave mode? Is USB in 1.1 or 2.0 Mode?

33


Test Worksheets Worksheet Header information (cont.)

What is the storage device Manufacturer name? What is the storage device Model number? What Type of device is the storage device? Which Storage Driver is being used for this test suite? What is the Version number of that storage driver? Usually NA these days, but if you are given a specific Driver Drop, enter it.

34



What is the storage device Serial number? Which Host Controller is being used for this test suite? Is the host controller in USB 1.1 or 2.0 Mode? What host controller Type (UHCI, OHCI or EHCI)? Which Host Controller Driver is being used (MS or other)? What is the Version number of the host controller driver?

35



What is the name of the bridge Board being used in this test suite? Which ASIC is on the board? Bits are usually left NA these days unless specifically stated otherwise. The Code Version is like a project name or a project identifier to help track

results within Matrix. The Test Lead should specify what Code Version to use.

36


Test Worksheets Results information

Pass – Expected Results are achieved Fail – What is asked for in Expected Results fails to occur or if other

unexpected results, harmful or otherwise occur. Usually it is best to ask a test lead if there is uncertainty.

Not Run – script is not run by choice, not related to a previous Fail Blocked – script does not get run due to a previous Fail that prevents it Comments – comment all relevant info to show what was tried, how a Fail

occurred, if any surprises or strange things occurred, etc.

37


SVTL Basic Training Outline1. Terms and Concepts2. Test Scripts Overview3. Test Configurations

4. Drive Imaging (hands-on)5. SVTL FAQ’s & Tidbits

38


Drive ImagingNaming Convention:In order to select the correct disk image, files need significant labels. Ghost and PQDI use the 8 character

DOS naming convention. For the SVTL, we will use the following convention: ##OSCCCC where ## is the number of the PC from the list of PC’s in the SV Test group (such as 07). OS denotes image operating system and CCCC denotes image application and tool contents.

OS:2K = Windows 2000; ME = Windows Millennium 98 = Windows 98 Gold; SE = Windows 98 SEXH= Windows XP Home; XP = Windows XP Pro Some examples of CCCC:BASE = no apps, no Office tools, no network; Minimal CLEAN install APPS = BASE + Non-Window Apps (USB chapter 9 + Acrobat PDF reader + Quick Time movie player)OF97 = BASE + APPS + Office Professional 97OF20 = BASE + APPS + Office Professional 2000NO97 = BASE + APPS + OF97 + Network communicationsNO20 = BASE + APPS + OF20 + Network communicationsUSB2 = USB2.0 drivers installed (must be at least since 3/22/01)DEBG=Debug tools installedOHCI = OHCI drivers installed for Win98SE on otherwise base image

An appropriate name would be “222KBASE.PQI”Appropriate comments could be “SVTest System #22 Windows 2K Base image including nvidia video

drivers. Created on 7/15/01 by SDM.”

39


Drive ImagingPQDI Hands-on (create)The best way to experience software tools is often times to actually use the tools.

Please follow the steps below as you walk through the PQDI module.1. Starting PowerQuest Drive Image (PQDI)

1.1. Boot PC from a DOS floppy disk1.2. At the DOS prompt, change to the D: Drive1.3 Change to the PQDI or IMAGES or DIMAGE directory (different PC’s differslightly as to their setup)

1.4. Run PQDI2. Creating a new image

2.1. Click on (or tab to, if no mouse support) the Create Image button2.2. Select an Image Name

2.2.1. At the Image File Name screen, click Browse2.2.2. Select D: from the Drives list2.2.3. Select the directory where image files exist (usually ‘Images’)2.2.4. Click in the File Name Box2.2.5. Select an appropriate name per the naming convention2.2.8. Click OK2.2.8. In Comments box, describe in detail, all particulars of this image including what elements are installed2.2.9. Click OK

2.3. Select High compression and then click Next2.4. At the ‘Ready to Create Image File’ screen, verify:

2.4.1. Desired file name and drive letter and directory for the destination2.4.2. Correct Source Partition2.4.3. Click Finish when satisfied that all is correct2.4.4. When complete, click OK and exit

40


Drive ImagingPQDI Hands-on (restore)

3. Restoring an image3.1. Click on Restore Image button3.2. Choose an Image File

3.2.1. At the ‘Select Image File’ screen, click Browse3.2.2. Select D: from the Drives list3.2.3. Select the directory where image files exist (usually ‘Images’)

3.2.4. Click on a file name (read comments to ensure you are choosing the oneyou want)3.2.5. Click OK3.2.6. Select Image File partition (C: drive)3.2.7. Select Destination partition (C: drive)3.2.8. Click OK at the ‘Restore Image’ screen3.2.9. Click FINISH at ‘Ready to Restore’ screen – may take from 5 to 45 min3.2.10. Click NO to view Result upon completion3.2.11. Click EXIT3.2.12. Click REBOOT to restart into the OS image just installed.

3.3. Ensure boot disk is ejected.

41


Drive ImagingGhost Hands-on (create)

1. Starting Symantec’s Ghost1.1 Boot PC from a DOS floppy disk1.2 Insert a Ghost floppy disk in the A: drive1.3 Run ‘ghostpe.exe’1.4 Press enter at the Copyright screen

2. Creating a new image

2.1 Caveats of using Ghost vs. PQDI.2.1.1 Less user-friendly2.1.2 Inability to comment images2.1.3 Inability to image from one partition of a drive to another partition of same drive.

2.2 Navigate to the ‘Image’ option2.2.1 Move arrow keys to ‘Local’2.2.2 Move arrow keys to ‘Partition’2.2.3 Move arrow keys to ‘Image’ and press Enter

2.3 At the ‘Select local source drives…’ screen, move arrow keys to drive2.3.1 Select drive by size in MB2.3.2 Color will be lighter grey when highlighted2.3.3 Press Enter2.3.4 Highlight will become Blue when selected

2.4 At the ‘Select source partition(s)’ screen, move arrow keys to partition2.4.1 Color will be lighter grey when highlighted2.4.2 Press Enter2.4.3 Highlight will become Blue when selected2.4.4 Tab until Ok is in white2.4.5 Press Enter

42


Drive ImagingGhost Hands-on (create)

2.5 At the ‘File name to copy image to’ screen, Tab until drive list is highlighted in white2.5.1 Press Enter to open list2.5.2 Highlight drive 2.5.3 Press Enter2.5.4 Tab to the ‘File name’ field and enter a file name

2.5.4.1 Name must be descriptive (no commenting is possible in Ghost)2.5.4.2 Eight characters, then dot, then ‘gho’ – (ie: 122kbase.gho)

2.5.5 Press Enter2.6 At the ‘Compress Image?’ screen

2.6.1 Select ‘High’2.6.2 At ‘Proceed?’ move arrow keys to highlight ‘Yes’2.6.3 Press Enter

2.7 At ‘Dump completed successfully’2.7.1 Press Enter on ‘Continue’2.7.2 Move arrow keys to ‘Quit’2.7.3 Press Enter2.7.4. Select ‘Yes’

43


Drive ImagingGhost Hands-on (restore)

3. Restoring an image3.1 Start Ghost and accept the Copyright information3.2 Navigate to the ‘Image’ option

3.2.1 Move arrow keys to ‘Local’3.2.2 Move arrow keys to ‘Partition’3.2.3 Move arrow keys to ‘Image’ and press Enter

3.3 At the ‘File name to load image from’ screen3.3.1 Tab to the drive selection list3.3.2 Press Enter3.3.3 Select the appropriate Ghost image file (.gho)3.3.4 Press Enter

3.4 At the ‘Select source partition from image file’ screen3.4.1 Move arrow keys to highlight (stay there if only one partition)3.4.2 Press Enter

3.5 At the ‘Select local destination drive…’ screen3.5.1 Move arrow keys to highlight the appropriate drive3.5.2 Press Enter3.5.3 Selected partition become Blue

3.6 At the ‘Select destination partition from drive #’ screen3.6.1 Highlight the appropriate partition (no guaranteed answers here)3.6.2 Press Enter

3.7 At the ‘Proceed?’ screen3.7.1 Move arrow keys to ‘Yes’ – no going back from here!3.7.2 Upon completion, press Ok to continue3.7.3 Move to ‘Quit’3.7.4 Press Enter3.7.5. Select ‘Yes’

44


SVTL Basic Training Outline1. Terms and Concepts2. Test Scripts Overview3. Test Configurations4. Drive Imaging (hands-on)

5. SVTL FAQ’s & Tidbits

45


SVTL FAQ’s & Tidbits FAQ’s Links to cool sites

Documents

SVTL Basic Training 2 ©2002 Cypress Semiconductor SVTL Basic Training Outline 1.Terms and Concepts 2.Test Scripts Overview 3.Test Configurations 4.Drive