• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 21 subscribers
  • Views 82 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

LMK04610EVM: How best to work with two boards?

Serge Issakov
Prodigy 10 points
Part Number: LMK04610EVM
Other Parts Discussed in Thread: USB2ANY

Tool/software:

I need to work with two LMK04610EVM boards.  I can do this with one TICS Pro instances and alternatively switch between boards, or run two different instances, each connected to a different board. What's the best approach, and how to do it?

WORKING WITH ONE TICS Pro INSTANCE

If I work with one TICSPro instance, what command do I use to switch between USB2ANY connections?  I see how to do it in the GUI (USB Comunications/Interface/Select USB2ANY), but how do affect this through the Python interface?

WORKING WITH TWO INSTANCES OF TICS Pro

If I have two instances, what's the best way to specify a different port for communications.  Is there a command line interface?  Or do I have to run it from a separate folder with its own SETTINGS.INI?

Thank you.

  • 0
    TI__Mastermind 33680 points

    I recommend two TICS Pro instances, since that way you can keep TICS Pro's cached register state from the two devices separate.

    As of TICS Pro v1.7.9.0, there is now a folder "ti_ticspro" which is included in the program installation directory (C:\Program Files (x86)\Texas Instruments\TICS Pro) which is a python package that exposes several startup options dataclasses in settings.py. You can use the settings dataclasses for the TCP server to specify the desired port as a keyword argument (omit other options on creation to accept defaults). These options classes can also be fed as arguments to an overarching "TICSProOptions" class, which can be provided to a function that starts instances of TICS Pro (the settings are written to a temp file and the temp file is passed as a command line argument on startup). You can also manually write out the values to a path of your choosing, or overwrite the settings in the program installation directory before starting another instance via the Windows GUI. By the way, there's a short documented example of this options -> start TICS Pro -> connect the client workflow in tcp.py, at the top of the file.

    For USB communication automation, the APIs you want to use are GetInterface and SelectInterface APIs, as well as potentially the GetAllUSB2ANY API. You may also find the USBOptions startup option to automatically connect to a USB2ANY should be disabled, so you can freely select the correct USB2ANY for each instance via API after startup. Without disabling USB autoconnect, you may get the two instances connected to the opposite USB2ANY; you could swap the clients in any code that cares, or you could manually select the demomode interface for each client, then set the correct interfaces.

    We've tested the python package on 3.11 x64. It might work on other versions ≥ 3.10, and it probably works down to ≥ 3.7 if you're willing to fix or eliminate some type hints.