GtDio6xWriteVectorTestFlagsMemory

Applies To

GX5961, GX5964, File

Purpose

Writes one or more vector test flags.

Syntax

GtDio6xWriteVectorTestFlagsMemory (nHandle, lVectorFlagStart, lVectorFlagSize, paucVectorFlags, pnStatus)

Parameters

Name
Type
Comments
nHandle
SHORT
Session identifier:

●     Board handle is used when communicating with the hardware. The Board handle session identifier is returned by calling GtDio6xInitialize or GtDio6xSetupInitialization.

●     File handle is used when communicating with a file. The File handle session identifier is  returned by calling GtDio6xFileOpen.
lVectorFlagStart
LONG
Used to specify the start vector to write to.
0-262143.
lVectorFlagSize
LONG
The number of vectors to write
1-262143.
paucVectorFlags
PBYTE
An array of vector flags.
pnStatus
PSHORT
Returned status: 0 on success, negative value on failure.

Comments

This function works in conjunction with GtDio6xRealTimeCompareSetJumpSource and GtDio6xRealTimeCompareSetErrorAddressMemorySource in order to qualify a vector to be able to generate an error that either the Step Control logic or Error Address memory will react to. Using the previously mentioned two functions, the sequencer can be set up to react to all vector errors or just those which are qualified with the appropriate flag.

There are two Vector Test flags, the C and E flags. The C flag corresponds with the Step Control Logic, and the E flag corresponds with Error Address Memory.

Vector C Error flags: This flag allows the user to determine if any of the expect pattern codes will cause the burst error flag to be set if the expected state is not true.

Vector E Error flags: This flag allows the user to determine if any of the expect pattern codes will cause the conditional jump pass/fail flag to be set if the expected state is not true.

The paucVectorFlags array can store values that correspond with either flag, one of the flags, or both flags concurrently:

0.    GTDIO6X_RTC_VECTOR_ERROR_FLAG_NONE – Neither flag is set

1.    GTDIO6X_RTC_VECTOR_ERROR_FLAG_C– Only the C flag is set.

2.    GTDIO6X_RTC_VECTOR_ERROR_FLAG_E– Only the E flag is set.

3.    GTDIO6X_RTC_VECTOR_ERROR_FLAG_C_AND_E– Both C and E flags are set.

Example

The following example qualifies the first 1000 vectors with the C flag, and reads back the memory:

 

BYTE aucWriteVectorErrorFlags [1000];

BYTE aucReadVectorErrorFlags [1000];

SHORT nStatus, i;

 

for (i=0; i<1000; i++)

    aucWriteVectorErrorFlags [i]=GTDIO6X_VECTOR_ERROR_FLAG_CONTROL;

GtDio6xWriteVectorTestFlagsMemory(nHandle, 0, 1000, aucWriteVectorErrorFlags, &nStatus);

GtDio6xReadVectorTestFlagsMemory(nHandle, 0, 1000, aucReadVectorErrorFlags, &nStatus);

 

See Also

GtDio6xReadVectorTestFlagsMemory, GtDio6xRealTimeCompareSetJumpSource, GtDio6xRealTimeCompareSetErrorAddressMemorySource, GtDio6xReadVectorMemory, GtDio6xWriteVectorMemory, GtDio6xFillVectors, GtDio6xGetErrorString