• State Resolved
  • Replies 7 replies
  • Subscribers 21 subscribers
  • Views 201 views
  • Users 0 members are here
Support feedback
Options
Options
Related

TICSPRO-SW: Set XO frequency with python fails sometimes

Christian Ryffel
Prodigy 140 points
Part Number: TICSPRO-SW

Tool/software:

I use the python library under ti_ticspro to generate our configuration file.

from ti_ticspro import TICSProOptions, APIOptions, StartTICSPro, TICSProTCPClient
apiOptions = APIOptions(EnableAPIServer=True, Port=11001)
tpOptions = TICSProOptions(apiOptions=apiOptions)
_ = StartTICSPro(startupSettings=tpOptions)
tp = TICSProTCPClient(port=11001)

# Start with default settings
tp.SelectDevice('LMK5B12204')
tp.SetMode('EVM Default')
               

# Set XO
# Frequency settings
tp.SetText('sXO_freq','20e6')

What I see is, that often the doubler under Advanced->APLL1 will not be set. Also the text field under "Set XO" will not be updated. If I change anything by hand everything will work as expected. Also the python commands. But not if python is used for the first setting.

  • 0
    TI__Genius 16565 points

    Hi Christian,

    This post slipped through the cracks, sorry for the delay.

    I'm not following the question here. Can you share an example of where you see the XO doubler not set?

    Regards,

    Jennifer

  • 0 in reply to Jennifer Bernal
    Prodigy 140 points

    Hi Jennifer

    The

    tp.SetText('sXO_freq','20e6')

    should set the doubler automatically. If I do this in the GUI, the following message appears underneath. But this is not happen with the script. 

    XO frequency set successfully!

Integer boundary spur = 20.0 MHz

XO R divider = 1
XO doubler is enabled
PFD frequency = 40.0 MHz

    Also the XO doubler is set on the APLL1 page (not the XO frequency, this is updated if you press the "Calculate Frequency Plan)

  • 0 in reply to Christian Ryffel
    TI__Genius 16565 points

    Hi Christian,

    Right now, the XO doubler is automatically set when you input the XO input frequency in the "Set XO" page.

    The way to manually update the XO doubler is by going to the "APLL1" page and setting/clearing it there.

    Then go to the "Set Outputs" page and hit the Calculate Frequency Plan button.

    A bit of a workaround in the current TICS Pro 1 but I have been working on improving this flow in the future release for TICS Pro 2.

    Regards,

    Jennifer

  • 0 in reply to Jennifer Bernal
    Prodigy 140 points

    Hi Jennifer

    I don't want to manually set the doubler. It's not set if I update the XO frequency with the script. And no, hitting the Calculate Frequency Plan button don't fix it. It seems that the first few frequency settings don't trigger correctly the GUI. You can see this if you execute my code. You will see that the s_wizard_XO_message_box didn't get updated as it should

    The following helps, but that's just a workaround for the bug.

     

    tp.SetText('sXO_freq','20e6')
tp.SetText('sXO_freq','80e6')
tp.SetText('sXO_freq','20e6')
tp.SetText('sXO_freq','80e6')
tp.SetText('sXO_freq','20e6')
tp.SetText('sXO_freq','80e6')
tp.SetText('sXO_freq','20e6')
tp.SetText('sXO_freq','80e6')
tp.SetText('sXO_freq','20e6')

  • 0 in reply to Christian Ryffel
    Prodigy 140 points

    Any news on this?

  • +1 in reply to Christian Ryffel
    TI__Genius 16565 points

    Hi Christian,

    I was able to reproduce the issue on my end when I first load the new profile: I also have to SetText different values to get it out of the *stuck* state.

    Unfortunately, this seems to be due to a TICS Pro 1 core bug that cannot be readily fixed. We are actively working on migration to our newer software, TICS Pro 2, so that future users do not encounter such issues. Please in the meantime, continue to use such workaround.

    Is the workaround detrimental to your design and development?

    Regards,

    Jennifer

  • 0 in reply to Jennifer Bernal
    Prodigy 140 points

    Hi Jennifer

    Thanks for the confirmation. I can use my workaround.