If Session Data Logging has been enabled, after each programming or testing session a record is written to the log file (a line-oriented ASCII file). An example of a TaskLink log file record is shown here.
-------------------------------------------------------
EXAMPLE
------------------------------------------------------
TLWin Session Data Log - Version 5.4.0.1
Date Logged: |
09-02-2003 02:12:11 AM |
Task Name: |
RR 28F160 |
User ID: |
Administrator Mode |
System: |
|
|
|
Device: |
INTEL GT28F160B3TA |
Data Source: |
c:\dataio\tlwin\demo.dat |
Sumcheck: |
8DBC4954 |
Process: |
/Continuity/ID Check/Blank Check/Erase/Program/Verify |
Process Status: |
Running |
TLWin Session ID: |
none |
|
|
Job Start Time: |
08-19-2004 01:17:26 PM |
Job End Time: |
08-19-2004 01:22:18 PM |
Devices Total: |
16 |
Devices Passed: |
16 |
Devices Failed: |
0 |
Overall Device Yield: |
100.00% |
|
|
Job System ID: |
0010EC0050C2 |
Job System SW Version: |
Vers 05.09.02.C |
Job Algorithm Filename: |
1168410C.ELF |
Job Algorithm Status: |
Released |
Job Algorithm Author: |
Data I/O |
|
|
Job Total Input: |
16 |
Job Total Output: |
14 |
Job Throughput: |
154 |
Job Programmer Yield: |
100.00 |
Adapter Cycle Count: |
0 |
|
|
Category: |
PASS, CF, NB, IB, PF,VF1,VF2,FT1,FT2,SFF,SFB, DO, EF,EID, OE |
TotalStats: |
16, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 |
Skt 1: |
8, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 |
Skt 2: |
8, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 |
Skt 3: |
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 |
Skt 4: |
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 |
--------------------------------------------------------------------------------
The ‘TotalStats’ and Skt1, Skt2, Skt3, Skt4 lines contain comma-delimited information structured in the following format:
Field |
Description |
PASS |
Devices that successfully programmed |
CF |
Devices that failed the continuity test |
NB |
Devices that were non-blank prior to programming |
IB |
Devices that contained an illegal bit |
PF |
Devices that failed the programming operation |
VF1 |
Devices that failed during the first verify pass |
VF2 |
Devices that failed during the second verify pass |
FT1* |
Devices that failed during the first functional test pass |
FT2* |
Devices that failed during the second functional test |
SFF* |
Devices with a security bit that failed to program |
SFB* |
Devices with a programmed security bit which prevented programming |
DO |
Devices with an overcurrent error |
EF |
Electrically erasable devices that failed to erase |
EID |
Devices with an electronic ID that did not match the selected device type |
OE |
Devices that failed due to errors other than those listed above |
|
|
|
* - Not currently supported by |
===