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.

LAUNCHXL-F28379D: InitSysPll() stuck running blinky_cpu01 example

Part Number: LAUNCHXL-F28379D
Other Parts Discussed in Thread: C2000WARE

the example builds and loads but never gets past this point

//
// Wait for the SYSPLL lock counter
//
while(ClkCfgRegs.SYSPLLSTS.bit.LOCKS != 1)

I just finished updating my CCS to 

Code Composer Studio

Version: 11.2.0.00007

and I just finished installing C2000Ware v4.01.00.00 

my target hardware is LaunchPadXL 28379D Ver 2.0

I've selected build config LAUNCHPAD_RAM, but frankly none of the build selects matter, it never gets past this point.

Ultimately in my application I need to use external crystal for time accuracy and will need to load into and run from flash, but first we need an accurate clock.

  • Hi,

    I tried the same example on my Launchpad, and I am unable to reproduce the issue. Have you done any updates to the InitSysCtrl function, or changed the XTAL available on the Launchpad? Do you have a different board which you can try it on?

    Can you share a snapshot of the ClkCfgRegs from the CCS Registers view?

    Regards,

    Veena

  • I was having this same issue in my target hardware running an older version of CCS and C2000Ware so I decided to upgrade everything to the latest and to use the Launchpad I have as well.  That is the first thing TI suggests is to run example code.  So this is all a fresh install with no modifications, except one.


    //
    // Turn off PLL
    //
    ClkCfgRegs.SYSPLLCTL1.bit.PLLEN = 0;
    asm(" RPT #250 || NOP");

    I scoured these forum posts looking for any possible fix and one thing I found was a suggestion to increase the delay seen above.  It made no difference.

    I checked the XTAL running on the Launchpad and it is running at 10.00 MHz.  

    I do not have a second Launchpad, but I get the same behavior on my own target hardware.

  • Hi,

    From the registers, looks like the MCD (Missing Clock Detection) bit is set. Can you try clearing that bit , restart and check if it is set again?

    Regards,

    Veena

  • by MCD bit do you mean MCLKSTS bit?  I try to set that to zero but it does not take, I'm guessing it is a status bit

  • Yes, The register includes a CLR bit as well. You can set this bit to clear the status.

    MCD Flag is set if the input clock source is missing,

    Regards,

    Veena

  • setting the MCLKCLR bit in CCS does not have any affect on MCLKSTS.

  • on a separate laptop

    I deleted all old CCS installs

    I installed the latest CCS and C2000ware

    I loaded blinky_cpu01 and ran it with my launchpad board, and it ran just fine.

    I suspect that something is corrupted in the CCS install on my work laptop.  Is there any way to check the integrity of the CCS install?  Is it possible that this is the issue?

  • on my work laptop,

    I uninstalled CCS 11.2

    rebooted

    then re-installed CCS ver 11.2

    I did NOT launch CCS at the end of the install because it wanted to create a workspace under the admin user, which is not my normal user access

    I launched CCS under my normal user access

    I imported blinky_cpu01 into my workspace

    The initial build had errors because there were too many linker CMD files being used, so I selected <none> under 'linker command file' in properties

    after doing all this, then the example ran properly, and the LED blinks 

    The original install of CCS took about 5 days because my company's IT kept blocking DLLs and EXEs from running, so each had to be unblocked in serial fashion until the install completed.  I don't know if that was the root cause or if I had accidentally created a working directory under my admin account, that caused the real problem.

    anyway it is working now.

    I hate computers :(