Support

DT10 Support

DT10 Trouble Shooting

Installation

Q1. I can not install the DT10.

In case that you can not install the DT10, please check the following three points.
1. Please reconfirm the system requirements.

In most cases of system environment of DT10′s installation problem, the followings are the key points, please check it again.
(For more details, please refer to the use’s manual.)

    (1) WindowsInstaller 3.1 or more should be installed.
    (2) Microsoft .NET Framework 2.0 or more should be installed.
    (3) Your account should have the Administration rights.

(Notes) In case that your account name use Japanese, the Installation sometimes failed. In this case, please try to Windows Update and change your account name into the alphabet (alphanumeric only).

2. Please check the old version of HASP runtime in you PC.

There is a possibility that the old version of HASP runtime remains in your PC. You can confirm the version by opening the “Control Panel -> Add / Removal of Program”, then selecting the “HASP SRM Run-time”.
The version of “HASP Run-time should be “5.10.1.17163″ in the DT10 version 5.01.

If you found the old version of HASP runtime in your PC, please update the HASP Run-time by executing “HASPUserSetup.exe” in the setup folder of DT10. There is no effect to your existing application programs since HASP Run-time has the upward compatibility.

If you can not update the HASP Run-time, please un-install the “HASP SRM Run-time” first, then retry to execute “HASPUserSetup.exe”.
In case of failure to un-install the HASP Run-time via Control panel, please try to un-install by using the installer corresponding to the old driver.

Please check both the USB hardware key and Dynamic Tracer are not connected to PC.

You can not install the DT10 application program in the state that the USB hardware key and Dynamic Tracer are connected to the PC. Please disconnect them and retry the installation.

In case that you still face the difficulty in the DT10 application installation after checking the above three points, please contact our technical support with the error message display on the screen.
We can support you as a individual case because there are different approach to solve the problem depending on the error message.

Please contact our technical support with the following mail address.
user@hldc.co.jp

Q2. I can not uninstall the DT10 application.

Please check the old version of HASP runtime in you PC.

There is a possibility that the old version of HASP runtime remains in your PC. You can confirm the version by opening the “Control Panel -> Add / Removal of Program”, then selecting the “HASP SRM Run-time”.
The version of “HASP Run-time should be “5.10.1.17163″ in the DT10 version 5.01.

If you found the old version of HASP runtime in your PC, please update the HASP Run-time by executing “HASPUserSetup.exe” in the setup folder of DT10. There is no effect to your existing application programs since HASP Run-time has the upward compatibility.

If you can not update the HASP Run-time, please un-install the “HASP SRM Run-time” first, then retry to execute “HASPUserSetup.exe”.
In case of failure to un-install the HASP Run-time via Control panel, please try to un-install by using the installer corresponding to the old driver.

Q3. The “New hardware search wizard” is launched despite that I have already installed the USB device drive.

The installation of USB device driver of DynamicTracer requires each USB port to be connected.

When you connect the DynamicTrace to another USB port other than the one you have already installed, the “New hardware search wizard” will be started. Please follow the manual and install the USB device driver.

Q4. There remains the install folder after complete the un-insallation.

Please check inside the install folder whether there is any file other than the automatic generated files at the time of installation.

The DT10′s un-installer did not delete the file if you put or create the file other than the automatic generated files at the time of installation.
Please delete the file manually.

Q5. [Windows7] When I connect the DynamicTracer to the PC and set power on, the USB device driver can not install automatically.

Please install the USB device driver manually.

In the Windows7 environment, the USB device driver of DynamicTracer can not install automatically. So you need to install the USB device driver manually.

The followings are the procedure of manual installation of device driver.

    1. Open [Device manager] of Windows
    2. Find the device of DynamicTrace in the device manager.
    3. Right-click the device of DynamicTracer and click “Update driver software”.
    4. Select “Search the device driver software refering to the computer”.
    5. Specify the “driver” folder in the DT10 install folder as a search target from “Refer” button.
       e.g. C:\Program Files\HeartLandData\DT10\driver
    6. Click “Next” button, the installation will start.

Starting application

Q1. I can not start the application.

Please check the connection of USB hardware key.

Please check and start the application with normally connecting the USB hardware key to PC (LED lights up and ready to use).

In case that the LED does not light up, the following situations are possible.

    1. DT10 is not connected to the USB port correctly.
      → Please connect again.
    2. HASP Run-time is not installed correctly.
      → Please install it again by “HASPUserSetup.exe” in “Setup”folder of DT10.
    3. There is something wrong with the USB port.
      → Please try other USB ports.
    4. USB Hardware-key is broken.
      → Please contact our technical support.

Please do NOT remove the USB hardware key during the application is running. The protection function of the USB hardware key will stop the application.
In case of removal of the USB hardware key, please try to insert it back immediately.

Inserting Test Points

Q1. The error message occurred during the Automatic Test Point.

You may sometimes find the error messages during the Automatic Test Point.
In this trouble shooting section, we will introduce solution for each error message.

Error list

In case of error 01 through 07

The description of errors are as follows;

  • Error01 : The number of ), ] of pairs does not match.
    e.g. It may be possible the number of ), ] is larger than the one of (, [.
  • Error02 : The end of function can not find until syntax check reached at the end of file.
    e.g. It may be possible the number of “{” is larger than the on of”}”.
  • Error03 : The “#endif” which can not find the paired #if is detected.
    e.g. It may be unmatched #endif.
  • Error04 : The “#else/elif” which can not find the paired #if is detected. e.g. It may be unmatched #else/elif.
  • Error05 : The number of } of pairs does not match.
    e.g. It may be possible the number of “}” is larger than the one of”{“.
  • Error06 : There is no “while” corresponding “do”.
    e.g. The { is detected without finding while statement behind do{}.
  • Error07 : There is no “if” corresponding “else”.
    e.g. The else is detected while the block is ended such as if statement.

■ e.g. Error01

    
    	if(a > 1){
    		#if 0
    		if(a == 1){
    			b = 1;   // ← Lost the integrity due to there is no  }  here.
    		#endif
    		if(a == 2){
    			b = 1;
    		}
    	}
                   

The error 1 through 7 occurs in case of the lost between enable side and disable side in compile option and in case of the compile error in disable side.
In these cases, please deal with the error as follows.

1. Please modify the troubled source code.

Please modify the troubled source code by using the external editor.

2. Please specify the Invalid Code Definition File.

The error message appears in case that compile error occurs at the point where disabled the source code by the compile options.
In this case, please create the Invalid Code Definition File and specify it by the “Specify Automatic Generated File” dialog.

Please refer to the manual and FAQ about the Invalid Code Definition File.

3. You can manually insert Test Points rather than using Automatic Insertion of Test Point.

You can manually insert Test Points from the document view.

In case of error 08

The details of the error is as follows.

  • Error 08: The multi-byte-code was found outside of comment. e.g.: There was the Japanese character outside of comment.

■e.g. Error 08

    #if 0
    #define FOR_DOCUMENT /* このオプションを有効にするとエラーに
    ドキュメントが吐かれる */
    #endif

    /* 関数実体定義 ——————–*/
    #ifdef FOR_DOCUMENT
    関数名 func_a
    機能 サンプル用コード
    引数 int arg_a
    戻り値 void
    変更履歴 2009.4.1
    #endif

Error 08 appears when the multi-byte-code, such as Japanese, was found outside of comment.
In this cases, please deal with the error as follows.

1. Please comment out the troubled source code.

Please modify the source code by using the external editor.

2. Please specify the Invalid Code Definition File.

The error message appears in case that compile error occurs at the point where disabled the source code by the compile options.
In this case, please create the Invalid Code Definition File and specify it by the “Specify Automatic Generated File” dialog.

Please refer to the manual and FAQ about the Invalid Code Definition File.

3. You can manually insert Test Points rather than using Automatic Insertion of Test Point.

You can manually insert Test Points from the document view.
Please note that this operation may inefficient work if you have many places you want to insert Test Points.

In case of error 09

The details of the error is as follows.

  • Error 09: Tried to insert the Test Point into the source file which includes C file.

The error 09 appears in case of trying to insert Test Point into the source file which includes C/CPP file.
It is prohibited to include a C/CCP file in the DT10′s specification because including the multiple DT10 generated header file in one compilation unit will cause the multiple definition of Test Point information. If you include the multiple source files, it will cause the above incident and you will find the compilation error.
Please watch out that this error does not occur in the source code which included from other source code.

1. Please comment out the troubled source code.

Please modify the source code by using the external editor.

2. You can manually insert Test Points rather than using Automatic Insertion of Test Point.

You can manually insert Test Points from the document view.
Please note that this operation may inefficient work if you have many places you want to insert Test Points.

In case of error 10

The details of the error is as follows.

  • Error 10: Either there was No function in the target source code; or there was No place where the Test Point can be inserted. (It did not include a header file.)

The Error 10 is the message for indicating non existence of place for inserting Test Point. This may sometimes occur in the source code file for only defining the RAM. If you do not have any problems, please discard this error.

In case that all the Test Point were denied due to the insertion restriction condition, this error code may appear.

Q2. The compilation error has occurred in the source code after inserting the Test Point.

If you face the problem of compilation error after inserting the Test Point, please check the following four points.
1. Please check the Type Definition File can solve this issue.

If there is the variable type depending on the target environment, the insertion of Test Point may sometimes failed.
In this case, please create the Type Definition File, and specify it in the “Specify Automatic Generated File” dialog.

Please refer to the manual and FAQ about the Type Definition File.

2. Please check the Invalid Code Definition File can solve this problem.

The error message appears in case that compile error occurs at the point where disabled the source code by the compile options.
In this case, please create the Invalid Code Definition File and specify it by the “Specify Automatic Generated File” dialog.

Please refer to the manual and FAQ about the Invalid Code Definition File.

3. Please check whether the multiple source file were included or not.

In case that a source file includes the another source file which inserted the Test Points, this leads to load the DT10′s header file; this may cause the compilation error due to the multiple definition of the Test Point.

Also in this case, it can not retrieve the correct Test Report due to unmatch the information between the Test Point information registered to the DT10 application and the Test Point in the real data.

Therefore, Please avoid the multiple definition when you insert the Test Point; for example, do not insert the Test Point into the source file to be included.

4. Please check whether the code, which should be at the top of translation unit, is exist or not.

The Automatic Test Point Insertion write include statement at the top of source file.
Therefore, if your compiler’s specification contains the specific code which should be at the top of translation unit, you may face the compiler error.

In case that the code, which should be at the top of translation unit, is exist, when you insert the Test Point into new DT project, you can insert the Include statement at the next line of specified strings by checking the “Insert the Header file Include statement at the next line of the specified strings found” option in the “Specify Automatic Generated File” dialog.

After checking the above four points and you still face the problem, please contact our technical support via the following mail address.
user@hldc.co.jp

Q3. The position of the inserted Test Point is incorrect or the Test Point did not insert after compiling the source code which contains the Automatic Test Point Insertion.

Please check the restrictions of Test Point insertion.

There are some restrictions for Automatic Test Point Insertion. Please check the restrictions of Test Point insertion. For more details of the restrictions, please refer to the user’s manual.

In case that you still face a problem after checking the restriction, please contact our technical support via following mail address.
user@hldc.co.jp

Q4. After inserting the Test Point, I try to execute the program but the target could not run. (GPIO /SPI connection)

Please check so many Test Points are inserted.

There is the case which the target can not run in normal behavior in case of too many Test Point due to the overhead.
In this case, please reduce the number of Test Point and check the behavior of driver.

Q5. After inserting the Test Point to the entrance of a handler, target could not run.

Please remove the inserted Test Point.

There are some functions which should not insert Test Point.
The interruption handler which realize the save and restore a register by calling function can not run normally, if Test Point inserted before the save and restore function, due to rewrite the register.
In this case, please remove the inserted Test Point.

Q6. After inserting so many Test Point, the target seems to run slowly, so I would like to temporally remove Test Point.

You can disable the Test Point by turning off the check box of folder view, module view.

Please turning off the check box of each file item, function tree item of the folder view and the module view, execute the “Creation of Header File”.
At this operation, you can turning off the check box at once by right-clicking folder view and module view and selecting “Disable All Test Point” on pop-up menu.
After modifying the header file, please update the target status (re-build and download ROM data) too.

Notes: You may remove Test Point manually in document view, but it is inefficiency. We recommend to disable / enable by using folder, module view.

Q7. I can not register source file to DT10′s project.

Please check the following two points.
1. Please check the extension of your intended source file should be “*.c” “*.cpp” “*.java” “*.cs”.

The file extension can be register to DT project should be “*.c” “*.cpp” “*.java” “*.cs”.
Please check the extension of your intended source file should be “*.c” “*.cpp” “*.java” “*.cs”.

2. Please check the file extension is displayed.

The source file can not register to DT project in the state that the file extension is not displayed.
In order to display file extensions, please turn off the check box “Do not show extensions that are registered” at “Display” tab in folder options on Windows.

For Test Report

Q1. I can not obtain Test Report.

In case that you can not obtain Test Report, please check the following point depending on the status of getting Test Report.

In case that you can not obtain any Test Report

■The customer of asynchronous bus
    Please check the connection with the flash memory.

    It is possibility of the physical elements has occurred such as, the attachment does not connect properly, the connection has loosen due to vibration or unintended contact.

■The customer for GPIO / SPI connection
    1. Please check the wave shape of driver is matched to your specifications.

    Please check the voltage, timing, connection with reference to the “Hardware Specifications”.

    2. Please check your customized function driver matched your environment.

    Please check the items to be customized such as, register setting, permission setting of interrupt disabled, target-dependent instruction code.

In case that your Test Report Data is not correct

■The customer of asynchronous bus
    1. Please check the connection with flash is normal.

    Please perform the connection test with referring the manual.
    There are some cases that the connection which the lost bit occurred might be incorrect.

■The customer for GPIO / SPI connection
    1. Please check the wave shape of driver is matched to your specifications.

    Please check the voltage, timing, connection with reference to the “Hardware Specifications”.

    We recommend to use the GPIO which has small Delay at the beginning.
    Please keep in mind that the GPIO with the large amount of pull-up electrical resistance may cause both the large Delay and decrease of voltage by connecting the probe.

In case that you sometimes get incorrect data

■For all customers
    1. Please check the process for the prohibition and permission of the interruption should be normal.

    Please check that the control to prohibit the interruption while the interruption is in the prohibited status should be properly handled.

    There are some cases of destroying data when the Test Point exists within the interruption function while you do not perform the prohibition and permission of the interruption by the function driver.

    When you perform the prohibition and permission of the interruption control in the function driver, in case that the Test Point is called from interruption function, you should save the interruption status, otherwise, the target may not running properly. So please customise your source code depending on the target environment.

    2. Please check that the unintentional Test Point is inserted other than the registered source file.

    It is possible that you may fail to get the Test Report properly due to the reason that the unintentional Test Point with the previous operation remains
    other than the registered source file.

    Please delete the Test Point if you found the unintentional Test Point other than the registered file.

■The customer for GPIO / SPI connection
    1. Please check that the wave of driver should be always in HI status during the CS port is outside function driver.

    There are some cases that the output date are incorrect such as, the initial process of the target does not set HI to the CS port, the target is oscillating during reset process, the reset-clear process must be hiding somewhere in the target program.

    Please do not get Test Point until the initial process ends. (We recommend to disable the designated Test Point.)
    Please keep in mind that initial value of the port at the initialization process.
    Also please do not change the port outside of the function driver.

Q2. It is difficult to specify the function trace number when I set the filtering of Test Report.

Please specify the “sequential number for all data” as a display format in “Line Number of Report Data List” from the setting menu.

When you select “Sequential Number for the displayed data”, the sequential number will display as filtered.
However, if you select “Sequential Number for the all data”, the sequential number with no filtered will display.
For instructions, please refer to the manual.

Q3. The message, “There are some lost data due to the buffer overflow” during or after obtaining Test Report.

When the DynamicTracer detects the buffer-full status, automatically stops the tracer; and when the usage rate became 0, restarts the tracer in the DT10 system.

If the buffer-full status occurs, the message: “There are some data which can not obtain due to the buffer-full status.” will appear under the “DynamicTracer Buffer Usage Rate” column of Test Report obtaining dialog.

When the DynamicTracer detects the buffer-full status, automatically stops the tracer; and when the usage rate became 0, restarts the tracer.

During the tracer stopped, you can not get Test Report.
In the DT10 system, if the buffer-full status occurs, after Test Report obtaining process terminated, the system generates the “Buffer Full Occurred History List” which indicated the last point of getting Report Data.

You can jump to the corresponding line of Test Report by double-clicking any line of the List. Please confirm the buffer-full point (the point where Test Point failed to get).

For Function Trace

Q1. The transition of the nest in the function trace seems to be wrong.

Please check the following two points.
1. Please check that there are any function that FuncIn / FuncOut is not set.

The Function Trace graphically demonstrates the transition when the FuncIn executed the program goes to the deep nest (the right direction) and when the FuncOut executed the program goes to the shallow nest (the left direction).
Therefore, if the TestPoint for FuncIn/FuncOut did not inserted properly, the Trace Report can not analyze properly.

2. In case that the interruption or the task dispatch has occurred, please confirm the classification of the task should be correct.

All the task should be classified if the dispatch will occur.

For Test Report

Q1. I found all items are NG.

You can change “OK / NG” status by double-clicking the designated item in the Test Report view.

The judgements of Test Report are all “NG” status as a default.
You can change the “OK/NG” status by double-clicking the each item in the list. Please select your test result.

Also the “Judge” item may be out of your sight due to it is located outside of the default display view, so please move to right direction with scroll bar of bottom of the list and find the “Judge” item.

For USB hardware key

Q1. The USB hardware key has broken.

Please contact our technical support.

When the USB hardware key has broken, please contact our technical support.
We may change it without compensation or for a fee.

Please contact the technical support from the following mail address.
user@hldc.co.jp

Q2. Can I use the USB hardware key via the HUB?

Please use the HUB supporting USB2.0 specification.

If you use the USB hard key via HUB, please use the HUB supporting USB2.0 specification.
You can use the HUB matching the requested amount of electricity supply.

The power consumption of HASP hardware key is 54mA.
Please use the USB hub which supply the amount of power with electric power (including external power supply).