TICS PRO supported Windows Version

I figured out that Version 1.7.6.2 is installable under Windows 10 Enterprise 2016 LTSB. but connection to the USB2ANY programmer does not work

Hi, sorry for the trouble. I have version 1709 (Fall Creators Update 2017) as the oldest supported windows version, but I think the oldest supported version should actually be version 1607 which should include Enterprise 2016 LTSB. I'll rebuild the installer and upload a new version shortly.

Hendrik, I just pushed a new version of TICS Pro (1.7.7.2) to the web. It should be available within the hour. I changed the installer's minimum supported Windows version to include Windows 10 Enterprise 2016 LTSB, but I don't have a Windows 10 Enterprise 2016 LTSB system or container available to test. Can you try installing 1.7.7.2 and let me know if it works?

Hi Derek,

thanks for providing the new software. Unfortunately the same issue still occures.

Maybe some additional information about the hardware may help.

I am trying to run TICSPRO with an USB2ANY to connect an LMK04832 EVM Board.

The TICSPRO S/W is installed on a Windows based Tektronix MSO64B Oscilloscope where also the USB2Any is connected. This gives us the advantage to control the LMK04832  and do the measurements using the same device.

Can you press Win + R and run `winver` on the tekscope so I can figure out what version it is?

It is Version 1607 (OS Build 14393.2273)

It's possible that I somehow ended up with an out-of-date version of the install builder script, but for a number of uninteresting reasons I'm unable to check until later today. In case I got something wrong, I'll pull the installer and republish. If I got the right version, I'll need to build another installer with logging facilities enabled for you to test. In any case, I'll let you know what I discover.

Okay, I've checked my install build script and it looks like I used the correct minimum version. Something weird is happening.

Can you re-run the installer for 1.7.7.2 TICS Pro, but from the command line with the /LOG flag? e.g.

C:\path\to\TICSPro_1.7.7.2_05-Feb-2024.exe /LOG

Then, even if it fails, head to %temp% in explorer, look for a file called "Setup Log yyyy-mm-dd #001.txt" where yyyy-mm-dd represents the current date, and upload the file so I can inspect the contents for any clues. Note that the log file will contain the full path for the setup exe and the temp directory where the installer extracts its temporary contents, so you may want to look it over once or do a quick find/replace if these filepaths should be obfuscated for public upload.

Setup Log 2024-02-07 #001.txt

Hello Derek,

please find attached the Log file from the installation.

Regards,

Hendrik

It now occurs to me that there were two issues mentioned in this thread: one with the 1.7.7.1 installer, and one with the unhandled exception issue. The installer setup log you provided me shows the application installed successfully. I should have asked if 1.7.7.2 installed successfully! Just to confirm: 1.7.7.2 installs correctly, and the issue we actually need to solve is the unhandled exception?

After encountering the unhandled exception, there should be a file in C:\Program Files (x86)\Texas Instruments\TICS Pro called ErrorLog.txt or something similar. Can you upload that file?

Hi,

the installation ended without showing any error. But when starting TICSPRO the GUI is missing most of its elements.

When attaching the USB2ANY debugger it shows that it is found but when trying to open USB Communications -> Interface a Error message pops up

When trying to configure for the LMK04832 with Select Device-> Clock Generator/Jitter Cleaner (Dual Loop)LMK04832

A message "Error Loading Device LMK04832" occurs

TICS Pro.exe Warning: 0 : 02/07/2024 07:56:04
Unhandled exception
Object reference not set to an instance of an object.
   at Pages.MainWindow.UpdatePLLFlexUIInternal()
   at Pages.MainWindow.loadMenu_Click(Object sender, RoutedEventArgs e)
----------------------------------
TICS Pro.exe Warning: 0 : 02/07/2024 07:56:25
Unhandled exception
Object reference not set to an instance of an object.
   at Pages.MainWindow.StartCommunicationSetup(Boolean show)
   at Pages.MainWindow.CommunicationInterface_Click(Object sender, RoutedEventArgs e)
----------------------------------
TICS Pro.exe Warning: 0 : 02/07/2024 10:16:47
Unhandled exception
Object reference not set to an instance of an object.
   at Pages.MainWindow.StartCommunicationSetup(Boolean show)
   at Pages.MainWindow.CommunicationInterface_Click(Object sender, RoutedEventArgs e)
----------------------------------

Here is the requested ErrorLog00.txt

The "ironpython failed to load" portion of the error message in your last screenshot is quite alarming. I wonder if there is another ironpython instance somewhere in your tekscope that is taking precedence during DLL search...

Can you also upload the file called log000 or log001 in the same directory?

If you go to Control Panel -> Programs and Features, and search for IronPython, do you see it installed with a previous version? The only other time I've seen this error message is when a prior version of IronPython was installed on the machine - see https://e2e.ti.com/support/clock-timing-group/clock-and-timing/f/clock-timing-forum/825948/ticspro-sw-ticspro-sw-can-t-load-device-lmx2572 for details.

Hi, it is IronPython Version 2.7.31000.0

Long story short, all the IronPython calls in TICS Pro are being redirected to your older version of IronPython on the machine. We can surely get TICS Pro running if you uninstall the old version and install a newer version; but this is probably not desired since the IronPython version on your machine is there for a reason.

As an alternative, I can try to force TICS Pro to redirect calls on earlier versions to the version bundled with TICS Pro... unzip the file "TICS Pro.exe.config" and copy/paste it into the C:\Program Files (x86)\Texas Instruments\TICS Pro directory, overwriting the existing file. Let's see if that works - never tried it before.

TICS Pro.exe.zip

Unfortunately the exchange of the TICS PRO.exe does not solve the problem. As far as I see the Error messages are the same.

I try to find out if the IronPython version is essential on the Tekscope or if it can be updated to the latest.

Hi Derek,

thank you for all the support!

I have to wait for Tektronix response to IronPython before I try to update.

When an upgrade is possible I will try it and give a feedback if it works.

In the meantime we run TICSPRO on a separate PC.

Regards,

Hendrik