TI's HalCoGenTau (Test Automation Unit) is broken in Windows 10

Hi All,

I am trying to use TI's HalCoGenTau (Test Automation Unit) with Windows 10 and I’m experiencing some issues.

https://www.ti.com/tool/SAFETI-HALCOGEN-CSP#overview

Part#: HCG-CSP-RM46-NOLDRA

1. 1. Installation Requirements:
      1. • Windows® Windows version 7 or higher -> we are using windows 10
         • Code Composer Studio 5.4 (or higher) -> we are using 10.4.0
         • Microsoft Office 2007 (or higher) -> 18.2209.1061.0 (after 2021)
         • Perl 5.x. Download Link → http://www.perl.org/get.html#win32

This tool requires the installation of LDRAUnit-TI-Qual 9.4.3 to achieve full functionality. Basically, HalCoGenTau calls LDRAUnit-TiQual’s cmd line app via PERL scripts.

• Here is a list of Issues with the Perl Scripts that come shipped with TI’s HalCogenTau.
  • Instead of executing the perl script HalCoGenTau seems to open them in a text editor (notepad).
    • This is caused by a change in windows 7 -> Windows 10 where calling a perl scripts seems to have changed
      • Work-around:
        • Any system “system()” call within a perl script requires “perl” to be in front of the script name.
          • Broken: system("$ScriptPath\\ConfigureTestbediniFlags.pl", "COMPRESS_EXH=TRUE");
          • Fixed: system("perl", "$ScriptPath\\ConfigureTestbediniFlags.pl", "COMPRESS_EXH=TRUE");
      • There was also a potential way to fix this by changing windows’ file association mechanism. But scripts are still opened when this is configured.
  • Any path in the perl scripts specified with a double slash i.e. “\\” results in a file unfound error.
  • One of the perl scripts (HCG_Unit_Test.pl  line 415) had an extra “}” closing brace. Meaning that this file was never run or even compiled (wtv that means in perl) before being committed.

This product is used for certifying SAFETY related applications in the Transportation and Aerospace Fields, and it would be nice If support could be provided. Updating installation requirements, the product’s webpage would be a good starting point.

See attached screenshot of running sample project: CSP_RM46L852ZWT_Def -> 1 x test suite selected (ADC1). It fails at code generation initially, then building. I think these failures have to do with path mismatches caused by different behavior  (double slashes) win7 -> win 10