• English
    • Korean
Troubleshooting Guides
3.6
  • 2024.12
  • 2024.06
  • 2023.12
  • 2023
  • 3.7
  • 3.6
  • 3.5
  • 3.4
  • 3.3
Table of Contents
Troubleshooting Guides
  • 3.6
    • Troubleshooting Guides — 2024.12
    • Troubleshooting Guides — 2024.06
    • Troubleshooting Guides — 2023.12
    • Troubleshooting Guides — 2023
    • Troubleshooting Guides — 3.7
    • Troubleshooting Guides — 3.6
    • Troubleshooting Guides — 3.5
    • Troubleshooting Guides — 3.4
    • Troubleshooting Guides — 3.3
GrabGrab
GrabGrab
  • CT Troubleshooting Guide
    • How to assign values to flexible array members
    • How to increase heap memory in JAVA when memory is low
    • Project DB file (*.csp) is damaged due to abnormal termination
    • Testrun.exe crashes when testing QNX software
    • When a specific function is not displayed in the coverage view
    • If the error message is not displayed after the project analysis fails
    • The screen is cut off when the Windows display magnification is not 100%
    • Windows.h file not found
    • If INFO [ut.hio]: runTest:testrun exit code(105) is displayed in the log and the unit test is not executed
    • When “Extract Toolchain Info” fails
    • Messages display abnormally in the error view
    • When testing with source code containing C++20 items
    • Errors that may occur during test execution
    • When cannot find global values after importing integration test
    • “C2118 : negative subscript” error occurs during test execution
    • SDK version issue when using Visual Studio 2015 toolchain
    • Issues during installation of CT
    • When cannot save a large control flow graph as a image file
    • When workspace is broken
    • Error occurs when upload data to VPES
    • Metric view error
    • How to check values of local variables and apply to results of test cases
    • When results of function call coverage and function coverage are not consistent
    • Issue about expected and output values of floating variables
    • When fail to import coverages of COVER
    • Signal error occurs when using a constant address
    • When comparing a variable of a floating point type, the result is different.
    • When running tests, test execution fails after build is successful
    • When only “0” exists in the partition list of the stub variable
    • When stub input data information is deleted
    • When a signal error occurs in a function that takes a variable array as an argument
    • When the size of the structure is different from CT and in the original program
    • When an undefined referenced error occurs in the IAR environment
    • When an error occurs in the test code due to the existence of a const global variable
    • When a signal error occurs when accessing a static const pointer variable
    • “C2512: No suitable default constructor available.” If an error occurs
    • How to design stub code that behaves differently for each test case
    • When perspective of CT is broken
    • Problem that Korean comments are broken when exporting stub code before CT 3.4 and importing after 3.4
    • When a value cannot be entered in the test case because the register variable is declared as a macro
    • How to convert a report in xls format to html format
    • “LoadLibrary failed with error 87: The parameter is incorrect.” error occurs
    • Unmanaged code variable list cannot be displayed in the test editor (for versions before CT 3.4)
    • How to enter invalid values in test data
    • How to enter a NULL value for a pointer-type parameter
    • When using the conversion toolchain, the coverages are displayed abnormally in the integration test with the infinite loop removed.
    • If the file name is truncated when exporting tests
    • When an error ‘invalid use of void expression’ occurs in the host test using the conversion toolchain
    • When tests need to be created only for new functions in a recycling scenario
    • If the color of the covered area does not change when selecting a test case
    • Problem that the project does not open when changing the version from CT2.9 to CT3.0
    • How to set only one test case to be created when creating a test
    • Integrated coverage is displayed as 0 or the execution result is not visible after the test run
    • (After Ver.3.6) When you want to import test data as ‘overwrite’
    • If ‘not found virtual address error’ occured after running the test
    • How to set up Windows 10 Defender when CT execution speed is slow in Windows 10
    • CT 3.6 패키지 설치할 때 ‘잘못된 디지털 서명’ 오류가 발생하는 경우
  • CT Target Plug-in Troubleshooting Guide
    • Build issues after exporting target test code
      • When the entry point function name is not main (for versions before CT 3.2)
      • Multiple definition error of the function used to save the target test result (for versions before CT 3.2)
      • ‘sprintf’ has not been declared or CS_FLT_OUTPUT error (for versions before CT 3.2)
      • Target log interface settings
      • Check for signal errors
      • Problems When Testing Functions Related to UART Communication in Target Software
      • When building with CodeWarrior, test related files such as cs_tfx.c are not found
      • Target output value does not appear or is output as 0 for float type in CodeWarrior
      • undefined error of type codescroll_int32 and codescroll_uint32
      • When cannot use ‘long’ or undefined type to ‘long’ error occurs in codescroll_int, codescroll_uint type
      • When the address of cs_io_putbyte is not found in Code Composer Studio
      • When declaration is incompatible with “void cs_io_putbyte” error occurs in GreenHills AdaMulti
    • TRACE32 related issues
      • symbol not found error “ct_target_log”
      • target reset failed
      • ‘&binary_path’ symbol not found or an error occurred at Data.Load.Elf “{file_path}” /LPATH while running the cmm script
    • Importing target log (test results) issues
      • Failed or Error When Performing ‘Import Target Test Log’
      • When the target log buffer size is exceeded
      • When an exception occurs in the script when running after test building in Code Composer Studio
      • Fail to import debug information logs in target test
      • How to read target logs when fail ‘Import Target Test Log’
      • When log import fails in a normally executed test
    • Other tips
      • .map file
      • TRACE32 debugging
      • If the output value is different due to the byte order of the host/target environment
  • Controller Tester package installation/uninstallation guide
    • If the package remains in Add/Remove Programs even after deleting the package
Download as PDF

Build issues after exporting target test code

  • When the entry point function name is not main
  • Multiple definition error of the function used to save the target test result
  • ‘sprintf’ has not been declared or CS_FLT_OUTPUT error
  • Target log interface settings
  • Check for signal errors
  • Problems When Testing Functions Related to UART Communication in Target Software
  • When building with CodeWarrior, test related files such as cs_tfx.c are not found
  • Target output value does not appear or is output as 0 for float type in CodeWarrior
  • undefined error of type codescroll_int32 and codescroll_uint32
  • When cannot use ‘long’ or undefined type to ‘long’ error occurs in codescroll_int, codescroll_uint type
  • When the address of cs_io_putbyte is not found in Code Composer Studio
  • When declaration is incompatible with “void cs_io_putbyte” error occurs in GreenHills AdaMulti
CT Target Plug-in Troubleshooting Guide
When the entry point function name is not main (for versions before CT 3.2)

Need more help with this?
Don’t hesitate to contact us here.

Thanks for your feedback.
Copyright © 2025 Suresofttech — Powered by Manula.com