MCAN of LPC5516 cannot filter IDs

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

MCAN of LPC5516 cannot filter IDs

Jump to solution
876 Views
1318614689
Contributor II

I configured MCAN's extended ID filter as shown below

1318614689_1-1645417047459.png

1318614689_2-1645417078138.png

 

I thought MCAN would receive frames with IDs 60 to 65 and reject others,But MCAN sends ACK for IDs outside the filter range。

1318614689_3-1645417270572.png

Is there a way to make MCAN not send ACKs to IDs outside the filter range?

Labels (1)
0 Kudos
1 Solution
869 Views
frank_m
Senior Contributor III

I think you need to study the CAN/filter section for the LPC55xx. While I don't know that specific MCU, this is not how other MCUs and CAN filter settings work.

You settings contradict each other. When rejecting IDs 0 to 7FF, there will be nothing left to process.

But more important, these filters do not stop the CAN peripheral from receiving such frames on the bus, nor do they stop it from acknowledging frames. This is a CAN bus requirement.

The filter settings only affect what messages will be copied to the internal message buffer(s) and create interrupts. In other words, the core only notices those messages you set to accept.

 

View solution in original post

0 Kudos
2 Replies
861 Views
xiangjun_rong
NXP TechSupport
NXP TechSupport

Hi,

For the CAN reception Filter data format of LPC551x, pls refer to the section 41.12 Standard message ID filter element in UM11295.pdf

xiangjun_rong_0-1645511198174.png

Both the SFEC bits and SFT bits define the Filter feature. For example, If the SFT=0x0, range filter is used.

 

xiangjun_rong_1-1645511394394.png

Hope it can help you

BR

XiangJun Rong

0 Kudos
870 Views
frank_m
Senior Contributor III

I think you need to study the CAN/filter section for the LPC55xx. While I don't know that specific MCU, this is not how other MCUs and CAN filter settings work.

You settings contradict each other. When rejecting IDs 0 to 7FF, there will be nothing left to process.

But more important, these filters do not stop the CAN peripheral from receiving such frames on the bus, nor do they stop it from acknowledging frames. This is a CAN bus requirement.

The filter settings only affect what messages will be copied to the internal message buffer(s) and create interrupts. In other words, the core only notices those messages you set to accept.

 

0 Kudos