MSPM33C321A: MSPM33C321A: SysConfig "Enable Normal CAN Operation" sets asmEnable = true (Restricted Operation Mode?)

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

Hi,

in SysConfig [1.28.2-4845], MCAN > Advanced Configuration, there is the option "Enable Normal CAN Operation". If we select it, SysConfig generates .asmEnable = true in the MCAN init structure.

According to the comment for asmEnable in the DriverLib (mcan.h), 0 (false) is Normal Mode and 1 (true) is Restricted Operation Mode.

Question: are the two modes mapped the wrong way round in SysConfig, or are we misreading the DriverLib comment? If SysConfig is wrong, the device would end up in Restricted Operation Mode instead of Normal Mode.

Thanks and kind regards

  • Hello Lukas, 

    It appears you have identified a discrepancy between the SysConfig GUI labeling and the underlying DriverLib parameter definition for the MSPM33C321A.

    Based on the technical documentation, the asmEnable member of the DL_MCAN_ConfigParams structure is defined to map directly to the MCAN_CCCR.ASM bit, where 0 corresponds to normal CAN operation and 1 enables Restricted Operation Mode 

    If selecting "Enable Normal CAN Operation" in SysConfig generates asmEnable = true (which evaluates to 1), the device will indeed be placed in Restricted Operation Mode, where it can receive and acknowledge frames but is prevented from transmitting data, remote, or error frames 

    Given that your observation indicates the GUI toggle is inverted relative to the hardware register and DriverLib documentation, you should treat the generated code as currently misconfigured for standard operation. As a workaround, you can manually override the generated configuration structure in your source code to set asmEnable = false until this is addressed in a future update to the SysConfig tool.

    Best Regards, 

    Benedict Jojo