Skip to main content
Associate
January 8, 2025
Solved

CAN FD Support

  • January 8, 2025
  • 2 replies
  • 1129 views

 Hello, I am looking for a MPU as CAN FD master but couldn't find the type with explicit CAN FD support. I would inquire here to make sure I haven't missed any details, and also ask for more information about the availability of the high performance chip with CAN FD interface. Thank you!

Best answer by mƎALLEm

Hello,

Looking at STM32MP131 datasheets, there is no CAN support at all neither FDCAN nor CAN2.0.

And indeed in the product page it shows the unvailability of CAN/FDCAN on these devices:

SofLit_0-1736423867001.png

 

Unlikely to STM32MP157 or STM32MP135 which have two FDCAN instances each .

Example of STM32MP135 in the product selector:

SofLit_1-1736424208435.png

And I confirm there is an issue in the Peripheral naming it needs to be FDCAN not CAN 2.0.

Hope it's clear now.

 

2 replies

mƎALLEm
Technical Moderator
January 8, 2025

Hello @automationworld and welcome to the Community.

STM32MP157 has two FDCAN instances.

From the datasheet:

SofLit_0-1736337382243.png

Are you sure you are looking for a MPU product not MCU?

 

"To give better visibility on the answered topics, please click on ""Accept as Solution"" on the reply which solved your issue or answered your question."
Associate
January 9, 2025

Thank you and really appreciated! I missed digging into the datasheet. My question came from the high level product selector at MPUs intro page doesn't explicitly show CAN FD option but only CAN 2.0.

 

automationworld_0-1736423236031.png

 

mƎALLEm
mƎALLEmBest answer
Technical Moderator
January 9, 2025

Hello,

Looking at STM32MP131 datasheets, there is no CAN support at all neither FDCAN nor CAN2.0.

And indeed in the product page it shows the unvailability of CAN/FDCAN on these devices:

SofLit_0-1736423867001.png

 

Unlikely to STM32MP157 or STM32MP135 which have two FDCAN instances each .

Example of STM32MP135 in the product selector:

SofLit_1-1736424208435.png

And I confirm there is an issue in the Peripheral naming it needs to be FDCAN not CAN 2.0.

Hope it's clear now.

 

"To give better visibility on the answered topics, please click on ""Accept as Solution"" on the reply which solved your issue or answered your question."