Skip to main content
Explorer II
September 15, 2024
Solved

FDCAN not working with STM32U5F7

  • September 15, 2024
  • 12 replies
  • 4444 views

I'm using a custom board with an STM32U5F7. Written a program(with nothing else configured other than clock and FDCAN) that simply sends out a message via FDCAN (in classis mode, 500kbps) which I'm hoping to receive using a P-CAN. When probing the TX line going to my transceiver using an oscilloscope there seems to be no data being transmitted, the line is just pulled high to 3V3. 

 

The same board populated with an STM32U599 running a new project with the same configuration and same code is able to successfully send messages which I can scope on the TX line.

 

With the STM32U5F7, I have tried internal loopback mode to rule out any hardware related issues (following the FDCAN loopback walkthrough on ST's YouTube) but I'm not receiving messages as well.

 

Not sure what to make of this or how to diagnose and fix the issue I'm facing any further than this. Any input would be highly appreciated 

    This topic has been closed for replies.
    Best answer by mƎALLEm

    Hello @Hareesh_S ,

    Another customer faced an issue with FDCAN with the same part number.

    After an internal task force, it turns out that STM32U5F7 part number doesn't support FDCAN. It's disabled by hardware. 

    What we propose is to use STM32U5G7 part number instead.

    Sorry for any inconvenience.

    12 replies

    mƎALLEmAnswer
    Technical Moderator
    September 27, 2024

    Hello @Hareesh_S ,

    Another customer faced an issue with FDCAN with the same part number.

    After an internal task force, it turns out that STM32U5F7 part number doesn't support FDCAN. It's disabled by hardware. 

    What we propose is to use STM32U5G7 part number instead.

    Sorry for any inconvenience.

    Hareesh_SAuthor
    Explorer II
    September 27, 2024

    Hello @mƎALLEm 

    Thank you for reaching out!
    Yeah, that's the plan, we'll be switching to the G7 equivalent shortly.

    Much appreciation for your support!
    (Funnily enough, I was contemplating replying here with the same news, being that the "other customer" was my workplace!)