Common errors

This page discusses possible issues encountered in using the TestDriver in various stages, and suggests how to resolve them.

The following table lists some of the expected issues encountered while installing the TestDriver and the possible solution:

Error code Problem Solution -1 Certificate store missing -6 Not enough capabilities given to the certificate Use a certificate allowing your capabilities or remove capabilities from your binaries -11 Invalid UID Make sure all the binaries have valid UIDs (unique and not 0) -12 UID already exists Make sure the UID is not in use and uninstall it properly if required -20 Corrupt SIS file {para} -70320 certificate missing in the certificate store Check your certificate is registered in the certificate store -1010 No vendor found {para} -10147 The SIS file would overwrite See Migrating to TestDriver V2 for the solution. -10254 Security error (not signed normally) Ensure that the SIS package has been properly signed -10257 Binary eclipsing Make sure the binary files that will be installed do not exist already in any other drive, or duplicate UID exist. See the above notes on how to reslove.

The following are some of the STAT related issues.

• Ensure that stat.dll and SymbianUsb.dll files are copied to your path at least from Symbian OS v9.2 onwards.

• When running the TestDriver v2 on Symbian OS v8.1b and v9.1, ensure that you use Symbian OS v9.2 or above.

  Do not use the stat.dll from v8.1b and v9.1 versions..

• Look for the error codes header file for a list of potential STAT errors.

The following are some of the issues encountered while installing the WINTAP.

• WinTap will need a device side driver and the CommDB to be setup on the device side to work

• For each new baseline, the WinTap will need to be reinstalled on the device side only.

The following are some of the issues encountered while building the ROM.

• Use the following build command to run the TestDriver:

  buildrom -D_EABI=ARMV5 -DRVCT -D_STARTUPMODE2 -DUSE_STRONG_CRYPTOGRAPHY h2 techview_statapi platsec

• When you include testexecute.iby, or similar in the ROM, switch TestExec to OFF by running the following command:

  TestDriver.cmd config --testexec OFF

  If testexecute.iby is not included in the ROM, run the following command:

  TestDriver.cmd config --testexec ON

To avoid the common errors while configuring the TestDriver, ensure the following conditions are met:

• Configure the TestDriver and the logging.properties file

• Use PlatSec: ON and Kernel: EKA2 for all builds from v9.1 onwards

• Use PlatSec: OFF and Kernel: EKA1 for all 8.1b- builds

• Use sysbin: ON only with STATLite

• Use TestDriver.cmd --clear to clear your configuration

• Use TestDriver.cmd --export aFile.xml to save or export your configuration to a file

• Use TestDriver.cmd --import aFile.xml to import a previously saved configuration