MSPM33C321A: MSPM33C321A: SysConfig generates MCAN init code that does not compile (undefined clock source constant)

Part Number: MSPM33C321A
Other Parts Discussed in Thread: SYSCONFIG

Hi,

with SysConfig [1.28.2-4845] and MSPM33 SDK [V1.04.00.00 ] the generated MCAN initialization (ti_msp_dl_config.c) does not compile:

  1. The generated code uses the constant DL_MCAN_FCLK_SYSPLLCLK0, which does not exist in the DriverLib. We assume DL_MCAN_FCLK_SYSPLLCLK is meant. Patching it manually works, but the fix is lost every time the configuration is regenerated.
  2. The structure gMCANSYSPLLConfig is generated but never used. A second structure gMCAN0ClockConf is generated and actually used.
  3. The generated code contains the comment /* Enable MSPM0 MCAN interrupt */. This is only cosmetic, but it raises the question whether the MCAN code generator was fully ported from MSPM0 to MSPM33 and whether generated code and DriverLib really match for this device.

  

Questions:

  • Is this a known issue, and is a fixed SysConfig / SDK release planned? We expected an SDK update around the production release of the device. Is there a release date?
  • Until then: what is the recommended workaround that survives regeneration?

Thanks and kind regards

  • Hi Lukas

    Thanks for your question. But I cannot confirm a scheduled release containing this specific fix. I will check with the team.

    The recommended workaround that survives regeneration:

    You can copy the files which Sysconfig created (for example, ti_msp_dl_config.c/h ) to your project folder and the modify them.

    Thanks and Best Regards,

    Ella Tang