• State
  • Replies 5 replies
  • Subscribers 31 subscribers
  • Views 59 views
  • Users 0 members are here
Support feedback
Options
Options
Related

CODECOMPOSER: SysConfig limits MSPM01518 VCO frequency to 160MHz

Ki Rummery
Prodigy 10 points

Part Number: CODECOMPOSER
Other Parts Discussed in Thread: SYSCONFIG, MSPM0G1518

Hello!

I picked up a project being worked on by other members on my team and installed a newer version of code composer in order to work on the application. The revision I have installed reports as: Version: 20.5.0.28__1.11.0

Building the code my team mates were building on a sligthly older CCS version fails on this new revision with: 

[0]error: PLL_QDIV(/ti/clockTree/multiplier.js) PLL_QDIV_OUT: The combination of PDIV and QDIV values drives the output frequency to VCO above maximum possible value (160 MHz). Please refer to device datasheet for exact operating range.
[1]error: net_vco(/ti/coreSysConfig/namedConnection): The combination of PDIV and QDIV values drives the output frequency to VCO above maximum possible value (160 MHz). Please refer to device datasheet for exact operating range.

The pre-existing syscfg file is setting the VCO frequency to 320MHz.

I looked at the datasheet, MSPM0Gx51x Mixed-Signal Microcontrollers With CAN-FD Interface, and it defines the valid VCO frequency range to be 80MHz - 400MHz.

While I do not see a reason to use a VCO above 160MHz for our design I am confused as to why the SysConfig tool is limiting this value and referencing the datasheet which defines a much higher maximum.

Is this imposed solely by the CCS SysConfig tool or is there some other parameter that I missed that limits the maximum VCO frequency to 160MHz on the MSPM0G1518.

Thanks!

  • 0
    TI__Mastermind 30475 points

    Hey Ki,

    I'm also unsure. Is your version showing that you are using Sysconfig version 1.11.0?  If so, that looks to be from Dec 21, 2021.  

    Can you try downloading the latest SysConfig, change your project settings to use this latest one, and then see if you still get the errors?  

    https://www.ti.com/tool/download/SYSCONFIG 

    Thanks

    JD

      

  • 0
    Prodigy 10 points

    Hi JD,

    Thanks for the prompt reply. I'm not sure on the best way to verify my SysConfig version but the build output contains:

    "C:/ti/ccs2050/ccs/utils/sysconfig_1.27.0/sysconfig_cli.bat" so I assume I'm using 1.27.

    I will update from the link provided and report back on any changes in behavior.

    Thanks,

    Ki

  • 0 in reply to JD Crutchfield
    Prodigy 10 points

    Hi JD,

    I installed the version of SysConfig from the above link and after configuring CCS to use that version I still see the maximum value for VCO capped at 160MHz.

    My build log now conatins:

    "C:/ti/sysconfig_1.27.1/sysconfig_cli.bat"

  • 0 in reply to JD Crutchfield
    Prodigy 10 points

    Hi JD,

    With the process for regressing SysConfig in hand I tired going back revision by revision to see where this first began. It seems all the revisions after 1.25.0 imposed this limit on VCO frequency. The newest revision that allows our existing .syscfg file to be compiled is sysconfig_1.25.0 after I also installed MSPM0 SDK v2.9.0.0.1. I checked the release note for the first  SysConfig 1.26 but I didn't find anything related to this new behavior.

  • 0 in reply to Ki Rummery
    TI__Mastermind 30475 points

    Hey Ki,

    That is a good finding.  Let me follow up with the software team and see if I can find a source for this change. 

    In the mean time, if you see no problem with 160MHz then I would probably switch to that.     

    Thanks,

    JD