• English
    • Korean
Troubleshooting Guides
2025.06
  • 2025.06
  • 2024.12
  • 2024.06
  • 2023.12
  • 2023
  • 3.7
  • 3.6
  • 3.5
  • 3.4
  • 3.3
Table of Contents
Troubleshooting Guides
  • 2025.06
    • Troubleshooting Guides — 2025.06
    • 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
    • Etc
      • “LoadLibrary failed with error 87: The parameter is incorrect.” error occurs
      • When perspective of CT is broken
      • Metric view error
      • The screen is cut off when the Windows display magnification is not 100%
      • Project DB file (*.csp) is damaged due to abnormal termination
      • Dialog that notifies the excess of node limitation appears in call graph view
      • In case of encountering a label syntax error or a ‘Not found: {file_path}’ error when executing CLI.
      • When You Can’t Save a Large Control Flow Graph as an Image File
      • Compound Condition Coverage Support for EN 50128 Compliance
      • When executing tests with the conversion toolchain, the conversion process may take a long time.
      • How to convert a report in xls format to html format
      • Error occurs when upload data to VPES
  • Coverage Troubleshooting Guide
    • When results of function call coverage and function coverage are not consistent
    • When a specific function is not displayed in the coverage view
    • When using the conversion toolchain, the coverages are displayed abnormally in the integration test with the infinite loop removed.
    • Integrated coverage is displayed as 0 or the execution result is not visible after the test run
    • Import Coverages of COVER
  • CT 2025.06 Target 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
  • CT Team Testing Issue Resolution Guide
    • If the network is disconnected during work
    • If the project is deleted while the connection is disconnected
    • If an individual PC or the team testing server PC is damaged
    • In a case where the size of the test target project exceeds 5GB
    • Dialog that notifies another workspace has already imported a team project with the same name appears
  • CT package installation/uninstallation guide
    • Issues during installation of CT
    • ‘Invalid digital signature’ error when installing CT 3.6 package
    • If the package remains in Add/Remove Programs even after deleting the package
    • Package uninstallation fails due to ‘an error accessing network location’
Download as PDF

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’
‘&binary_path’ symbol not found or an error occurred at Data.Load.Elf “{file_path}” /LPATH while running the cmm script
Failed or Error When Performing ‘Import Target Test Log’

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

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