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.

MSPM0G3507: BUG REPORT - sysconfig not generating correct code to enable and use LFOSC as LFCLK

Part Number: MSPM0G3507
Other Parts Discussed in Thread: SYSCONFIG,

Tool/software:

Look at

  1. LFOSCGOOD - you can see its not good even though it was selected in sysconfig
  2. LFCLKMUX - LFOSC selected in sysconfig but here shows LFXT is selected).

generated code - nothing that enables LFOSC and/or sets the clock mux.

SYSCONFIG_WEAK void SYSCFG_DL_SYSCTL_init(void)
{

    //Low Power Mode is configured to be SLEEP0
    DL_SYSCTL_setBORThreshold(DL_SYSCTL_BOR_THRESHOLD_LEVEL_0);

   
    DL_SYSCTL_setSYSOSCFreq(DL_SYSCTL_SYSOSC_FREQ_BASE);
    /* Set default configuration */
    DL_SYSCTL_disableHFXT();
    DL_SYSCTL_disableSYSPLL();

}
The only way I can get running code is to disable the check box for clock stabilization (which coincidentally was the way it was set in the example code provided b TI, so seems TI knows it does not work?!)
And then it runs but NOT from LFOSC, it runs from LFXT.  Since my test board and the MSPM0G3507 launchpad both have a 32KHz xtal it will run.  I assume it would fail if the xtal were not present.  

Assuming I am right then this is a serious bug, please verify and confirm we agree that the bug exists.
  • Hi,

    By default, when the MCU runs a POR the LFOSC will start oscillating, it does not require any code to configure it. Unless you choose to use LFXT as you LFCLK source in the application code. In this case the LFOSC will be disabled. It is not a bug you observed.  

    Best regards,

    Cash Hao