
Teledyne LeCroy Voyager USB 3.0 Exerciser Generation Script Language Reference Manual
62
Starting with version 4.35 the USB Protocol Suite introduces Drive Emulation. The AddDrive
instruction allows to emulate a BOT (and later UASP) drive. When connected to a system, the
Trainer comes up then as an uninitialized drive. It has to be initialized and formatted, then files
can be copied to it / from it as long as the Voyager system stays powered up. During this the
Trainer Drive Emulation can be disconnected from the USB3 system and connected back or to a
different USB3 system and the files on the Drive Emulator will stay intact.
Note: Refer to the UseAssignedAddress setting, which is applicable only to Device Emulation.
9.2.1 StartDeviceFrameworkHandler Instruction
This instruction starts or stops the Device Framework Handler task on the Trainer.
Format
StartDeviceFrameworkHandler ( start/stop )
StartDeviceFrameworkHandler has the following instruction parameters:
start/stop: Specifies if the Device Framework Handler task has to be started (1) or stopped
(zero). Default value is 1.
Examples of calling the StartDeviceFrameworkHandler instruction
# Device emulation
Main
{
# Start the handler task at the beginning of the script.
StartDeviceFrameworkHandler()
…
# Stop the handler task temporarily.
StartDeviceFrameworkHandler( 0 )
# Process some standard requests by script.
…
# Start the automatic task again.
StartDeviceFrameworkHandler()
}
9.2.2 InitDevice Instruction
This instruction initializes operation of Device Emulation for a device. The device is placed in the
USB Default state.
Comentarios a estos manuales