MSPM0G3507: CAN RX - messages are not received reliably

Hi,

I have not encountered this kind of issue before. Usually, if your configuration is correct. Then all the messages which matches the filter will be received by the MCU. Can you send your sysconfig file here so we can take a look into it?

Best regards,

Cash Hao

sure:

/**
 * These arguments were used when this file was generated. They will be automatically applied on subsequent loads
 * via the GUI or CLI. Run CLI with '--help' for additional information on how to override these arguments.
 * @cliArgs --device "MSPM0G350X" --part "Default" --package "LQFP-48(PT)" --product "mspm0_sdk@2.02.00.05"
 * @v2CliArgs --device "MSPM0G3507" --package "LQFP-48(PT)" --product "mspm0_sdk@2.02.00.05"
 * @versions {"tool":"1.21.0+3721"}
 */

/**
 * Import the modules used in this configuration.
 */
const ADC12         = scripting.addModule("/ti/driverlib/ADC12", {}, false);
const ADC121        = ADC12.addInstance();
const Board         = scripting.addModule("/ti/driverlib/Board");
const GPIO          = scripting.addModule("/ti/driverlib/GPIO", {}, false);
const GPIO1         = GPIO.addInstance();
const GPIO2         = GPIO.addInstance();
const MCAN          = scripting.addModule("/ti/driverlib/MCAN", {}, false);
const MCAN1         = MCAN.addInstance();
const PWM           = scripting.addModule("/ti/driverlib/PWM", {}, false);
const PWM1          = PWM.addInstance();
const SYSCTL        = scripting.addModule("/ti/driverlib/SYSCTL");
const TIMER         = scripting.addModule("/ti/driverlib/TIMER", {}, false);
const TIMER1        = TIMER.addInstance();
const ProjectConfig = scripting.addModule("/ti/project_config/ProjectConfig");

/**
 * Write custom configuration values to the imported modules.
 */
ADC121.$name                      = "ADC12_0";
ADC121.adcMem0chansel             = "DL_ADC12_INPUT_CHAN_4";
ADC121.sampleTime0                = "125 us";
ADC121.sampClkDiv                 = "DL_ADC12_CLOCK_DIVIDE_8";
ADC121.enabledInterrupts          = ["DL_ADC12_INTERRUPT_MEM0_RESULT_LOADED"];
ADC121.peripheral.$assign         = "ADC1";
ADC121.peripheral.adcPin4.$assign = "PB17";
ADC121.adcPin4Config.$name        = "ti_driverlib_gpio_GPIOPinGeneric1";

Board.peripheral.$assign          = "DEBUGSS";
Board.peripheral.swclkPin.$assign = "PA20";
Board.peripheral.swdioPin.$assign = "PA19";

GPIO1.$name                              = "GPIO_GRP_0";
GPIO1.port                               = "PORTA";
GPIO1.associatedPins.create(2);
GPIO1.associatedPins[0].$name            = "DI_BUTTON";
GPIO1.associatedPins[0].direction        = "INPUT";
GPIO1.associatedPins[0].interruptEn      = true;
GPIO1.associatedPins[0].polarity         = "RISE_FALL";
GPIO1.associatedPins[0].pin.$assign      = "PA28";
GPIO1.associatedPins[1].$name            = "DO_EN_EXT_LED";
GPIO1.associatedPins[1].internalResistor = "PULL_UP";
GPIO1.associatedPins[1].initialValue     = "SET";
GPIO1.associatedPins[1].pin.$assign      = "PA23";

GPIO2.$name                          = "GPIO_GRP_1";
GPIO2.associatedPins.create(2);
GPIO2.associatedPins[0].$name        = "DO_EN_MC33063A";
GPIO2.associatedPins[0].assignedPort = "PORTA";
GPIO2.associatedPins[0].pin.$assign  = "PA7";
GPIO2.associatedPins[1].$name        = "DO_BOOST_PIEZO";
GPIO2.associatedPins[1].assignedPort = "PORTB";
GPIO2.associatedPins[1].pin.$assign  = "PB2";

MCAN1.$name                     = "MCAN0";
MCAN1.fdMode                    = false;
MCAN1.wkupReqEnable             = true;
MCAN1.autoWkupEnable            = true;
MCAN1.emulationEnable           = true;
MCAN1.dataRatePrescalar_manual  = 1;
MCAN1.dataTimeSeg1_manual       = 8;
MCAN1.dataTimeSeg2_manual       = 8;
MCAN1.stdFiltElem               = "001";
MCAN1.stdFiltID1                = 416;
MCAN1.stdFiltID2                = 416;
MCAN1.extFiltElem               = "001";
MCAN1.extFiltType               = "00";
MCAN1.extFiltID1                = 36257792;
MCAN1.extFiltID2                = 36257792;
MCAN1.rxBufElemSize             = "DL_MCAN_ELEM_SIZE_8BYTES";
MCAN1.rxFIFO0ElemSize           = "DL_MCAN_ELEM_SIZE_8BYTES";
MCAN1.rxFIFO1ElemSize           = "DL_MCAN_ELEM_SIZE_8BYTES";
MCAN1.enableInterrupt           = true;
MCAN1.interruptLine1Flag        = ["DL_MCAN_INTERRUPT_RF0N"];
MCAN1.desiredDataRate           = 0;
MCAN1.m0interrupts              = ["DL_MCAN_MSP_INTERRUPT_DOUBLE_ERROR_DETECTION","DL_MCAN_MSP_INTERRUPT_LINE0","DL_MCAN_MSP_INTERRUPT_LINE1","DL_MCAN_MSP_INTERRUPT_SINGLE_ERROR_CORRECTION "];
MCAN1.interruptLine             = ["DL_MCAN_INTR_LINE_NUM_0","DL_MCAN_INTR_LINE_NUM_1"];
MCAN1.rxFIFO0size               = 10;
MCAN1.rxFIFO0waterMark          = 8;
MCAN1.interruptFlags            = ["DL_MCAN_INTERRUPT_RF0F","DL_MCAN_INTERRUPT_RF0N","DL_MCAN_INTERRUPT_RF0W"];
MCAN1.interruptLine0Flag        = ["DL_MCAN_INTERRUPT_RF0F","DL_MCAN_INTERRUPT_RF0W"];
MCAN1.stdFiltType               = "00";
MCAN1.additionalCoreConfig      = true;
MCAN1.rrfe                      = true;
MCAN1.rrfs                      = true;
MCAN1.anfe                      = "2";
MCAN1.anfs                      = "2";
MCAN1.rxFIFO1startAddr          = 336;
MCAN1.rxBufStartAddr            = 372;
MCAN1.lse                       = 2;
MCAN1.lss                       = 2;
MCAN1.desiredNomRate            = 50;
MCAN1.dataSynchJumpWidth_manual = 8;
MCAN1.peripheral.$assign        = "CANFD0";
MCAN1.peripheral.rxPin.$assign  = "PA27";
MCAN1.peripheral.txPin.$assign  = "PA26";
MCAN1.txPinConfig.$name         = "ti_driverlib_gpio_GPIOPinGeneric3";
MCAN1.rxPinConfig.$name         = "ti_driverlib_gpio_GPIOPinGeneric4";
MCAN1.rxPinConfig.enableConfig  = true;

PWM1.$name                              = "PWM_PIEZO";
PWM1.ccIndexCmpl                        = [0];
PWM1.ccIndex                            = [0];
PWM1.interrupts                         = ["LOAD_EVENT","ZERO_EVENT"];
PWM1.clockPrescale                      = 4;
PWM1.timerStartTimer                    = true;
PWM1.timerCount                         = 5000;
PWM1.peripheral.$assign                 = "TIMA0";
PWM1.peripheral.ccp0Pin.$assign         = "PB8";
PWM1.peripheral.ccp0Pin_cmpl.$assign    = "PB9";
PWM1.PWM_CHANNEL_0.$name                = "ti_driverlib_pwm_PWMTimerCC0";
PWM1.PWM_CHANNEL_0.dutyCycle            = 1;
PWM1.ccp0PinConfig.direction            = scripting.forceWrite("OUTPUT");
PWM1.ccp0PinConfig.hideOutputInversion  = scripting.forceWrite(false);
PWM1.ccp0PinConfig.onlyInternalResistor = scripting.forceWrite(false);
PWM1.ccp0PinConfig.passedPeripheralType = scripting.forceWrite("Digital");
PWM1.ccp0PinConfig.$name                = "ti_driverlib_gpio_GPIOPinGeneric0";
PWM1.ccp0Pin_cmplConfig.$name           = "ti_driverlib_gpio_GPIOPinGeneric2";

SYSCTL.validateClkStatus  = true;
SYSCTL.CANCLKSource       = "SYSPLLCLK1";
SYSCTL.HFCLKSource        = "HFXT";
SYSCTL.HFCLK_Freq         = 10000000;
SYSCTL.SYSPLL_CLK1En      = true;
SYSCTL.peripheral.$assign = "SYSCTL";

TIMER1.$name            = "TIMER_0";
TIMER1.timerMode        = "PERIODIC";
TIMER1.timerClkDiv      = 8;
TIMER1.timerClkPrescale = 32;
TIMER1.timerPeriod      = "500 ms";
TIMER1.interrupts       = ["ZERO"];

ProjectConfig.migrationCondition = true;

/**
 * Pinmux solution for unlocked pins/peripherals. This ensures that minor changes to the automatic solver in a future
 * version of the tool will not impact the pinmux you originally saw.  These lines can be completely deleted in order to
 * re-solve from scratch.
 */
TIMER1.peripheral.$suggestSolution = "TIMA1";

Hi and thanks!

1. I enabled TDC function:

______________________________________________________________________

2. I eliminated RX and TX Msg RAM overlaps:

_______________________________________________________________________

But I still encounter the same unreliable reception.

Any more ideas what could go wrong? Any more things I could check?

Within what limits does it make sense to adjust the values for the TDC? Can I somehow measure how big the delay really is that I might have to compensate for?

Thanks a lot in advance!

Matze

Hi,

Well, I am checking on the description of 'Message RAM Access Failure bit'

Message RAM Access Failure. The flag is set, when the Rx Handler:
- has not completed acceptance filtering or storage of an accepted
message until the arbitration field of the following message has
been received. In this case acceptance filtering or message storage
is aborted and the Rx Handler starts processing of the following
message.
- was not able to write a message to the Message RAM. In this case
message storage is aborted.
In both cases the FIFO put index is not updated resp. the New Data
flag for a dedicated Rx Buffer is not set, a partly stored message is
overwritten when the next message is stored to this location.
The flag is also set when the Tx Handler was not able to read a
message from the Message RAM in time. In this case message
transmission is aborted. In case of a Tx Handler access failure
the MCAN is switched into Restricted Operation Mode. To leave
Restricted Operation Mode, the Host CPU has to reset CCCR.ASM.

In your configuration, you can try change the two filter options to store the message in different FIFOs. The standard filter can be used to save in RX FIFO0 and extended filter can be used to save in RX FIFO1. It can help avoid unable to write message to RAM.

Best regards,

Cash Hao

Cash Hao11 said:

In your configuration, you can try change the two filter options to store the message in different FIFOs.

I can try to change that, but I don't expect much improvement from that. 

For four reasons:

1. It is not uncommon for the very first message not to arrive and then the "Message RAM Access Failure bit" is set for the second message that arrives. I don't see the probability that the RAM is not yet accessible.

2. I send the CAN messages manually with a large time interval, so that the previous message must already have been processed and the ram should no longer be busy.

3. It also happens when I send multiple messages with the same standard or extended ID. Accordingly, I do not expect any advantage if the other ID is stored in the other FIFO.

4. I use 4 different IDs, two standard and two extended IDs... so theoretically I would again run the risk of mutual interference in the respective FIFO.

What do you think?

__________________________________________________________________

Matze said:

Within what limits does it make sense to adjust the values for the TDC? Can I somehow measure how big the delay really is that I might have to compensate for?

Any ideas or answers to these questions?

Thanks a lot and best regards,

Matze

Hi,

I agree with you that it is very uncommon that the very first message not to arrive and then the "Message RAM Access Failure bit" is set for the second message that arrives.

I do not have many clues about this issue. Maybe try remove the filter configuration and check if this issue still there. The original demo code without the filter does not have this kind of issue for sure. So, I am thinking maybe it relates to the filter. 

For the TDC, I find out it is for the CAN FD frame. It is not work on classic CAN. So, no needs to worry about it here.

Best regards,

Cash Hao