Part Number: MSPM0G3507
Other Parts Discussed in Thread: SYSCONFIG, TCAN-SOIC8-EVM
Hi,
I am having trouble receiving CAN data over the MCAN bus using the rx FIFO 0 interrupt. This interrupt never triggers. I can see that the message is acknowledged by the MCU as there is no automatic retry (CAN frames were also verified on oscilloscope and acknowledge bit was good).
Here is how I have the MCAN set up in sysconfig:
- I am using the EXT_HF clock (40MHz) as the CAN_CLK with a divide by 1 divider.
- CAN-FD is disabled.
- The sampling point is 75%
- The arbitration bit rate is 500 kbit/s and the datarate is set to 0.5Mbit/s. (the device transmitting the messages are also running at 500kbit/s)
- In RAM configuration, the filter element is set to "Store in Rx FIFO 0 if filter matches".
- The filter type is set to "Dual ID filter for SFID1 or SFID2".
- SFID1 and SFID2 are both set to 310.
- In the interrupt section, Rx FIFO 0 New Message interrupt is the only MCAN interrupt selected.
- The MCAN Line 1 interrupt is enabled.
- Rx FIFO 0 New Message interrupt is set to tigger Line1
- The pinmux is set to RX = PA13, TX = PA12.
Here is a screenshot where we can see that the transmitted message is acknowledged by the MCU:
For the CAN transceiver, I am using the TCAN-SOIC8-EVM populated with a TCAN1057AVDRQ1 transceiver. It is working correctly, I am able to transmit messages correctly with this setup.
The only way I was able to trigger the interrupt was to allow all MCAN interrupt to trigger Line1. When I do this, there is no message in the FIFO0. So far, it looks like the filter is not working correctly.
I am attaching the sysconfig file and the main.c file to this so you can have a look at the settings for yourself.
mcan_message_rx.zip
Please let me know of any clue to what is going on.
Thank you