1. Download the EAPI archive and decompress it onto an USB drive.
2. Plugin the USB drive to the Starterkit
3. Run the Windows command prompt as administrator and navigate into the TqWin64EAPI_R01.01 folder on the USB drive
4. Execute install.batch from the command prompt

1. Open Windows Device Manager
2. Find System Devices→Tq driver.
3. Select Uninstall and check “Delete the driver software for this device”

1. Right click on TqDrv.sys file from this package and choose Properties→Details to locate file version.
2. Make sure that TqDrv.sys file version and driver version in Device Manager are identical.
3. Make sure that TqDrv.sys file from C:\Windows\System32\drivers is identical to one from this package.

The EApiLibInitialize function has to be called at the beginning of every application.
An error will be returned if TQ driver is not installed on the system.

The EApiLibUnInitialize function has to be called at the end of every application.

Supported EAPI ID values:

• EAPI_ID_BOARD_MANUFACTURER_STR
• EAPI_ID_BOARD_NAME_STR
• EAPI_ID_BOARD_REVISION_STR
• EAPI_ID_BOARD_SERIAL_STR
• EAPI_ID_BOARD_BIOS_REVISION_STR
• EAPI_ID_BOARD_HW_REVISION_STR
• EAPI_ID_BOARD_PLATFORM_TYPE_STR

Example

> TqApp.exe EApiBoardGetStringA 0
Board Manufacturer Name = TQ-Group

Supported EAPI ID values:

• EAPI_ID_GET_EAPI_SPEC_VERSION
• EAPI_ID_BOARD_RUNNING_TIME_METER_VAL
• EAPI_ID_BOARD_DRIVER_VERSION_VAL
• EAPI_ID_BOARD_LIB_VERSION_VAL
• EAPI_ID_HWMON_CPU_TEMP
• EAPI_ID_HWMON_SYSTEM_TEMP
• EAPI_ID_HWMON_VOLTAGE_3V3
• EAPI_ID_HWMON_VOLTAGE_VBAT
• EAPI_ID_HWMON_VOLTAGE_5VSB
• EAPI_ID_HWMON_VOLTAGE_12V
• EAPI_ID_HWMON_FAN_CPU
• EAPI_ID_HWMON_FAN_SYSTEM

Supported Values for EApiBoardGetValue function

Example

> TqApp.exe EApiBoardGetValue 7
CPU Temperature = 30.5

Supported Functions

There are 2 available EEPROMs available on the TQ x86 Starterkits

• 0 - Module EEPROM (0xA0 address on I2C bus)
• 1 - Carrier EEPROM (0xAE address on I2C bus)

Function returns Storage Size and Block Length value, needed to calculate write block alignment and size for EApiStorageAreaWrite function.

Example:

TqApp.exe EApiStorageAreaRead 0 0 32
EApiStorageAreaRead() successfully read data:

             | 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
        -----|-----------------------------------------------
        0000 | 00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f  ................
        0010 | 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f  ................

Offset and ByteCnt parameters must be a multiple of Block Length value that is returned by EApiStorageCap function.

Example:

> EApiStorageAreaWrite 0 0x20 " 0  1  2  3  4  5  6  7  8  9 10 11
                               12 13 14 15 16 17 18 19 20 21 22 23
                               24 25 26 27 28 29 30 31"

> TqApp.exe EApiStorageAreaWrite 0 0x20 "0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31"

The current frequency is defined in Windows registry:

HKLM\SYSTEM\CurrentControlSet\Services\TqDrv\Parameters\I2cBusSpeed

100KHz are set as default frequency, the following frequencies are available for the primary CPLD I2C Bus:

• 50KHz
• 100KHz
• 400KHz

After changing I2C frequency in Windows registry, Tq driver must be reset in Windows Device Manager:

- Open Windows Device Manager -> System Devices -> TqDriver
- Right Click on TqDriver and select "Disable" 
- Right click on TqDriver and select "Enable

To ignore write operation: <string_to_write> = ^“”
To ignore read operation: <bytes_to_read> = 0

Example:

> TqApp.exe EApiI2CWriteReadRaw 0 AE "0 0" 10
EApiI2CWriteReadRaw() completed successfully

WriteData:
     | 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
-----|-----------------------------------------------
0000 | 00 00                                            ..

ReadData:
     | 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
-----|-----------------------------------------------
0000 | 00 01 02 03 04 05 06 07 08 09                    ..........

> TqApp EApiI2CWriteReadRaw 0 AE "" 5
EApiI2CWriteReadRaw() completed successfully


ReadData:
     | 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
-----|-----------------------------------------------
0000 | 0a 0b 0c 0d 0e                                   .....

> TqApp.exe EApiI2CWriteReadRaw 0 AE "0 3 45 A7 B8 12" 0
EApiI2CWriteReadRaw() completed successfully


WriteData:
     | 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
-----|-----------------------------------------------
0000 | 00 03 45 a7 b8 12                                ..Eº+.

where 'type' = 0/1/2 (No Command/ Standard Command/ Extended Command)

Examples

> TqApp.exe EApiI2CReadTransfer 0 AE 0 0 12
EApiI2CReadTransfer() completed successfully

ReadData:
     | 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
-----|-----------------------------------------------
0000 | 07 08 09 0a 0b 0c 0d 0e 0f 10 11 12              ............

> TqApp.exe EApiI2CReadTransfer 0 AE 1B2 2 3
EApiI2CReadTransfer() completed successfully

ReadData:
     | 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
-----|-----------------------------------------------
0000 | f3 f4 f5                                         =()

> TqApp.exe EApiI2CWriteTransfer 0 AE 0 2 "A B C D E"
EApiI2CWriteTransfer(): completed successfully

WriteData:
     | 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
-----|-----------------------------------------------
0000 | 0a 0b 0c 0d 0e                                   .....

Delay mode is not supported. Event mode and Reset mode are supported.

List of possible Watchdog timeout values

If timeout falls between these values, the closest top value will be used: For Example:
For 10 seconds - 16 secnds will be used.
For 683 seconds - 1024 seconds will be used.

Event timeout must be defined, other Timeout values must be 0.
2 interrupt lines are supported: 10 and 11.
Default line is 11.
Interrupt number must be defined in 2 places:

• Windows registry: HKLM\SYSTEM\CurrentControlSet\Services\TqDrv\Parameters\WdtInterrupt
• TQ driver resources in Device Manager

To change IRQ line you need to change it in 2 places. After that you need to reset Tq driver in Windows Device Manager:

• Open Windows Device Manager and find System Devices/ TqDriver
• Right Click on TqDriver and choose “Disable”, then reenable it

Reset timeout must be defined, other Timeout values must be 0.
Following reset modes are supported:
1 = watchdog reset output triggers hard reset signal
0 = watchdog reset output triggers power-on button
Reset mode is definded in Windows Registry, default value is 1.

HKLM\SYSTEM\CurrentControlSet\Services\TqDrv\Parameters\WdtReset

In dual-stage mode (Event + Reset) Event timeout will be used for both stages. Event timeout must be defined, reset timeout must not equal zero.
EApiWDogStart <Delay> <EventTimeout> <ResetTimeout>
Time must be specified in ms.
Example:

EApiWDogStart 0 15200 1000

8 GPIO's are available all TQ x86 Modules , all of them can be defined as output or input.
The EAPI library defines two different mechanisms to address GPIO: pin addressing and bank addressing.
Function EAPI_GPIO_BANK_ID(GPIO_NUM) is used to define the GPIO bank.

TqApp function EApiGPIOGetDirectionuses bank addressing.

Example:

TqApp.exe EApiGPIOGetDirection -h
EApiGPIOGetDirection <Bank>, 

TqApp.exe EApiGPIOGetDirection 0
Bank 0: DIRECTION = 0xff

EApiGPIOSetDirection <Pin> <Direction> uses pin addressing.

Example:
Setting pin 2 to output

> TqApp.exe EApiGPIOSetDirection 2 0

EApiGPIOSetLevel <bank> uses bank addressing, where <bank> is a group of 32 pins addressed simultaneously. Example:

> TqApp.exe EApiGPIOsetLevel 4 1

EApiGPIOGetLevel <bank> uses bank addressing, where <bank> is a group of 32 pins addressed simultaneously. Example:

> TqApp.exe EApiGPIOGetLevel 0
Bank 0: LEVEL = 0xfb

This function detects Watchdog interrupts, there is a standalone application for TqWdtWaitForInterrupt because it’s not part of EAPI.

Examples

> WdtWaitForInterrupt.exe

> TqApp.exe EApiWDogStart 0 10000 0

• I2C EEPROM may be unstable if I2C bus speed is set to 400KHz. Recommended I2C bus speed is 100KHz.
• EEPROM access is unstable, e.g. when some data is written to I2C EERPOM it may get written to wrong offset. Usually it happens after large number (thousands) of successive write operations to the EEPROM, or while reading EEPROM in big chunks. Most likely it is a h/w issue of particular model of EEPROM.