STM32CubeMX 6.16.0 – Fixed Nominal CAN Bit Timing Values

[Duc]

Hello,

I’ve noticed a difference in behavior between STM32CubeMX configurations for STM32H7 and STM32N6 series.

• On STM32H7, when configuring CAN bit timing, the parameters such as Nominal Time Quantum, Nominal Time for one bit, and Nominal Baud Rate update dynamically based on the settings.

• On STM32N6 (using STM32CubeMX v6.16.0), these values remain constant. For example, even when using the official STM32 example with a nominal bit rate of 1 Mbit/s, CubeMX still shows a fixed value of 1000 bit/s and does not adjust the timing parameters.

My question is:

• Is this a bug in STM32CubeMX v6.16.0 for STM32N6 series?

• Or is this a new feature specific to STM32N6 where the tool no longer recalculates these values?

I’d appreciate clarification from ST or anyone who has encountered the same behavior.

Thanks in advance!

[mƎALLEm]

Hello,

Normally the nominal Time quantum needs to be 5ns in your configuration.

According to an internal version that will be released in the future, the issue has been fixed and when changing the different timing parameters Nominal Time for one bit as well as the bitrate change accordingly.

[Duc]

Hello,

Thank you for the update regarding the fix for the timing parameter issue.

Could you please let us know when the new version is expected to be released? 

Thank you in advance for your support.

[mƎALLEm]

Hello,

I cannot commit on the release date. But most probably the fix will be available in the next version 6.17.x

[mƎALLEm · Accepted solution]

Hello,

CubeMx 6.17.0 has been released. I think the issue has been fixed in that version.

Could you please check?

[Duc]

Hi @mƎALLEm ,

You were right. After updating CubeMX to version 6.17.0, the issue has been resolved.

Thank you.