CAN wrong bit timing: bit time larger than expected

[HiSt]

Title edited to give an accurate idea of the issue.

Hello together,

i had a problem with setting a correct bit time on a CAN-port.

On my nucleo-h755ZI-Q board, I want to operate the FDCAN1 by the CM4 in classic-can mode with a baud rate of 1 MHz.

I supply the FDCAN with a clock of 50MHz:

Therefore the corresponding registers are set as follows:

With:

this excerpt in the reference manual, the calculation is:

tfdcan_tq_ck = 0,02 µs  <- (1/50MHz)

tq = 0,1µs          <-             (0,02 *  5)

The bit time ist 1µs   <-  (0,1 *( 7+1+0+1+1))

-> baudrate is 1 Mhz    -> 1/1µs

But in the outgoing frames, I measure a bit time of approx. 3µs.

Enlarged:

How can that be? What did I do wrong or overlook?

Thank you and best regards,

HiST

 

 

[STuser2]

Was the CAN communication established between the two nodes at 1Mbps? Were you able to receive and transmit messages? Just for confirmation.

[HiSt]

No, due to incorrect bit timing and the resulting incorrect baud rate, I cannot communicate with another participant.

[mƎALLEm]

Hello,

Attach your ioc file and tell more about what you are connecting to nucleo-h755ZI-Q as a second CAN node.

[mƎALLEm]

Just forget that you are using a nucleo-h755ZI-Q while in the Clock config you set the crystal to 25MHz in a crystal mode! But there is no external crystal in that board connected to OSC_IN/OSC_OUT.

This is the schematic:

What I suggest is to use the bypass mode but for that you need some steps:

1- Modify the STLINK MCO output to generate 5MHz instead of 8MH generated from HSI. Ensure SB72 is soldered. Please refer to this article to do that: How to use STLINK-V3 MCO output on Nucleo boards as a precise clock source for STM32

2- In your ioc file you need to update the RCC config: HSE in Bypass mode with HSE value = 5MHz

+ use the same bit timing config I provided in my previous post.

 

[HiSt]

Hello m3ALLEm,

yes, thank you, this was the solution. 

And also responsible for some other problems I had.

Now I also measure the correct bit time.

Best regards,

   HiST