• State Resolved
  • Replies 16 replies
  • Subscribers 21 subscribers
  • Views 255 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

TICSPRO-SW: TICS Pro Not Launching GUI After "Starting GUI..." Message

Bugra Tufan
Prodigy 10 points
Part Number: TICSPRO-SW
Other Parts Discussed in Thread: LMK3H0102, LMX2572

Tool/software:

Hello everyone,

I recently installed the TICS Pro software from Texas Instruments on my system. When I attempt to run the program, it displays the message "Starting GUI..." but fails to open the GUI afterwards.



Has anyone else experienced this issue with TICS Pro? Any suggestions on how to resolve this would be greatly appreciated. I'm wondering if there are specific configurations or system requirements that I might have missed. 

Thank you in advance for your help!
Bugra

  • 0
    TI__Mastermind 31880 points

    TICS Pro uses the Windows Management Instrumentation (WMI) to detect USB devices. I have occasionally seen WMI leave queries hanging for 20-30 minutes while processing something else (like a misconfigured group policy applied by an IT organization or an interaction with antivirus). Does the problem go away if you wait or come back in half an hour?

  • 0 in reply to Derek Payne
    Prodigy 10 points

    Dear Derek, 

    Thanks for your response. I have been waiting more than two hours but still the GUI doesn't pop up. 

    BR,
    Bugra 

  • 0 in reply to Bugra Tufan
    TI__Mastermind 31880 points

    Okay, thanks for trying. It seems unlikely that something would be stuck for two hours on WMI.

    The next most likely thing is an issue unpacking the embedded python environment. Use the task manager to end the program; then, in C:\Program Files (x86)\Texas Instruments\TICS Pro, delete the folder "python-3.11.5-embed-win32", and try opening TICS Pro again. Does this work?

  • 0 in reply to Derek Payne
    Prodigy 10 points

    I deleted python-3.11.5-embed-win32, restarted the computer and tried to open the program but I still can't see the gui. Btw, it doesn't stuck. After seeing the initial pop-up (the picture I sent) , the GUI doesn't start. Also, I didn't see the program in task manager. 

    BR,
    Bugra

  • 0 in reply to Bugra Tufan
    TI__Mastermind 31880 points

    Hmm.

    In C:\Program Files (x86)\Texas Instruments\TICS Pro, do you have any text files such as log000/log001 or some kind of error log? If so, could you upload them?

    Can you try deleting the following two files and loading the application one more time?

    • C:\Program Files (x86)\Texas Instruments\TICS Pro\settings.ini
    • C:\ProgramData\Texas Instruments\TICS Pro\Configurations\TICS Pro.ini
  • 0 in reply to Derek Payne
    Prodigy 10 points

    I deleted the files but I still don't see the GUI. 

    Here is the list of files inside C:\Program Files (x86)\Texas Instruments\TICS Pro directory:



    And the log000 file:

    8424.log000.txt
    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    Welcome to TICS Pro. Version -> 1.7.7.9, 29-Jan-25
    Loading Device LMK3H0102...
    Detected 0 USB2ANY interfaces
    No device detected, all frequency calculation assumes a BAW frequency of 2467 MHz.
    No device detected - gain calibration values will need to be read from device when writing configuration.
    Completed loading Device LMK3H0102. Version = 2024-10-03, v1.4.0
    Welcome to TICS Pro. Version -> 1.7.7.9, 29-Jan-25
    Loading Device LMK3H0102...
    Detected 0 USB2ANY interfaces
    No device detected, all frequency calculation assumes a BAW frequency of 2467 MHz.
    No device detected - gain calibration values will need to be read from device when writing configuration.
    Completed loading Device LMK3H0102. Version = 2024-10-03, v1.4.0
    Welcome to TICS Pro. Version -> 1.7.7.9, 29-Jan-25
    Loading Device LMK3H0102...
    Detected 0 USB2ANY interfaces
    No device detected, all frequency calculation assumes a BAW frequency of 2467 MHz.
    No device detected - gain calibration values will need to be read from device when writing configuration.
    Completed loading Device LMK3H0102. Version = 2024-10-03, v1.4.0
    Welcome to TICS Pro. Version -> 1.7.7.9, 29-Jan-25
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX


    BR,
    Bugra

  • 0 in reply to Bugra Tufan
    TI__Mastermind 31880 points

    This seems to indicate that the GUI is getting all the way to successfully loading the profile, but is then crashing for unknown reasons. This implicates none of the usual suspects, and I'm quite confused.

    Can you open C:\ProgramData\Texas Instruments\TICS Pro\Configurations\TICS Pro.ini, and save the following text into the file (overwriting the existing text entirely), and try restarting TICS Pro?

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    [SETUP]
    Count=4
    DEVICE_NAME01=LMK3H0102
    DEVICE_NAME00=LMX2572
    DEVICE_NAME02=LMK05318B
    DEVICE_NAME03=LMK04832
    DEVICE_TYPE00=BuiltinDevice
    DEVICE_TYPE01=BuiltinDevice
    DEVICE_TYPE02=BuiltinDevice
    DEVICE_TYPE03=BuiltinDevice
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    This should be very similar to what's already there, it just sets LMX2572 as the startup device instead of LMK3H0102. This checks if there's a problem specific to LMK3H0102.

    If TICS Pro loads, can you try navigating to the device selection menu and attempting to load LMK3H0102? And if it crashes at this point, can you try deleting C:\ProgramData\Texas Instruments\TICS Pro\Configurations\Devices\Reference-less Clock Generators\LMK3H0102\LMK3H0102.tcb and repeating the other steps?

    On the other hand, if simply switching the startup profile doesn't work, I'll need some time to compile a version of the binary that can report the specific problem you're encountering, which might take some time.

  • 0 in reply to Derek Payne
    Prodigy 10 points

    Unfortunatelly it doesn't work :( TICS Pro read the file then overwrote the modified file. It placed an empty line on the beginning of the file but still keeps your modification.

    BR,
    Bugra


  • 0 in reply to Bugra Tufan
    TI__Mastermind 31880 points

    Drat. Give me a day to put together a debug binary.

  • 0 in reply to Derek Payne
    Prodigy 10 points

    Ok, I'm waiting your response. Thanks for your effort.

    BR,
    Bugra

  • 0 in reply to Bugra Tufan
    TI__Mastermind 31880 points

    1817.TICS Pro.zip

    This is a debug build that should catch any errors and give me a usable trace. Please unzip the eight files and paste them into C:\Program Files (x86)\Texas Instruments\TICS Pro, overwriting the files that are currently there, then run TICS Pro.exe; it should at least throw a popup showing the error, and should create ErrorLog00.txt with a detailed error summary. Can you please upload that ErrorLog00.txt, or if it doesn't create such an error log let me know?

  • 0 in reply to Derek Payne
    Prodigy 10 points

    Dear Derek,

    Here is the error log file. I hope it helps.. 

    4747.ErrorLog00.txt
    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    TICS Pro.exe Warning: 0 : 02/28/2025 08:58:59
    Unhandled Application Exception: The invocation of the constructor on type 'Pages.MainWindow' that matches the specified binding constraints threw an exception.
    at System.Windows.Markup.WpfXamlLoader.Load(XamlReader xamlReader, IXamlObjectWriterFactory writerFactory, Boolean skipJournaledProperties, Object rootObject, XamlObjectWriterSettings settings, Uri baseUri)
    at System.Windows.Markup.WpfXamlLoader.LoadBaml(XamlReader xamlReader, Boolean skipJournaledProperties, Object rootObject, XamlAccessLevel accessLevel, Uri baseUri)
    at System.Windows.Markup.XamlReader.LoadBaml(Stream stream, ParserContext parserContext, Object parent, Boolean closeStream)
    at System.Windows.Application.LoadBamlStreamWithSyncInfo(Stream stream, ParserContext pc)
    at System.Windows.Application.LoadComponent(Uri resourceLocator, Boolean bSkipJournaledProperties)
    at System.Windows.Application.DoStartup()
    at System.Windows.Application.<.ctor>b__1_0(Object unused)
    at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
    at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
    Inner Exception: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
    at Python.Runtime.Runtime.PyObject_CallObject(BorrowedReference callable, BorrowedReference args)
    at Python.Runtime.ImportHook.SetupImportHook()
    at Python.Runtime.ImportHook.Initialize()
    at Python.Runtime.Runtime.Initialize(Boolean initSigs)
    at Python.Runtime.PythonEngine.Initialize(IEnumerable`1 args, Boolean setSysArgv, Boolean initSigs)
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX


    BR,
    Bugra

  • 0 in reply to Bugra Tufan
    TI__Mastermind 31880 points

    Alright, this indicates that something strange is happening with an embedded python import, which is usually indicative of some kind of corruption in the python environment or in the python packages.

    Can you run the following two powershell commands (make sure you use powershell instead of cmd) after modifying the location of the output files (look for <your_path> in the Export-Csv cmdlet arguments), and upload the two csvs produced? These commands give me the directory structure and the checksum of every file in the python dependencies and in the module directory, which should make it clear where and how the embedded python scope unpack is failing.

    Fullscreen
    1
    Get-ChildItem -Path 'C:\Program Files (x86)\Texas Instruments\TICS Pro\python-3.11.5-embed-win32' -Recurse -File | Get-FileHash -Algorithm MD5 | Select-Object * -ExcludeProperty Algorithm | Export-Csv -Path 'C:\<your_path>\extracted.csv' -UseCulture -NoTypeInformation
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    Fullscreen
    1
    Get-ChildItem -Path 'C:\Program Files (x86)\Texas Instruments\TICS Pro\python-dep' -Recurse -File | Get-FileHash -Algorithm MD5 | Select-Object * -ExcludeProperty Algorithm | Export-Csv -Path 'C:\<your_path>\packed.csv' -UseCulture -NoTypeInformation
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    If everything looks alright, and there's no clear explanation for why your embedded python scope is becoming corrupted, I can build a new version of the binary with an option to disable the embedded python scope - it is only used for the PCIe Jitter Calculation tool, so if you aren't using this tool, disabling the embedded python scope will not affect your ability to load and use device profiles.

  • 0 in reply to Derek Payne
    Prodigy 10 points

    Dear Derek, 


    You can find the lists in the attached files:

    extracted.csv


    packed.csv

    BR,
    Bugra

  • 0 in reply to Bugra Tufan
    TI__Mastermind 31880 points

    Thanks for your patience. The files you attached in your previous post are identical to the ones on my machine produced by running the same commands. This indicates there is no corruption in the data, and implies that the issue is either some core problem with the DLL that loads embedded python (PythonNET, developed by third party), or some kind of interaction between the embedded python executable (and its dependent libraries) and other processes running on your machine. I'm unable to reproduce the issue on my end.

    I have another set of binaries to try. These binaries should bypass loading the embedded python entirely when the correct option flag is specified in the settings INI.

    3531.TICS Pro.zip

    Once again, please unzip the eight files and paste them into C:\Program Files (x86)\Texas Instruments\TICS Pro, overwriting the files that are currently there.

    Additionally, in the settings.ini folder, please add the following lines at the bottom, then save the file:

    Fullscreen
    1
    2
    [PYTHON]
    DISABLE=true
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    Now, when running TICS Pro, you should see a message in the status bar indicating that the embedded python scope is disabled, but I believe the application should no longer immediately crash on startup. Let me know if you still have issues after this.

  • 0 in reply to Derek Payne
    Prodigy 10 points

    Dear Derek,

    I copied the files you sent and added Python disable configuration into settings.ini file and now it is working.


    Thanks for your help.

    BR,
    Bugra