CAN Setting Mistake in CubeMX v4.26.0

[Alvin Sun]

Posted on July 02, 2018 at 08:57

I am developing under STM32F4 platform. After migrating from v1.0 to v1.0 firmware, which involves a major change in CAN API, I found there's a mistake in the CubeMX CAN setting options:

The generated code relating auto retransmission changed from

hcan1.Init.NART = DISABLE;�?�?�?

to

hcan1.Init.AutoRetransmission = DISABLE;�?�?�?

However, the setting option in CubeMX is still NART, which is the inverse of Auto-Retransmission. This option name is very misleading and caused my robotics application that requires a high frequency CAN transmission fail randomly. I found this after catching a ALST (Arbitration Lost Error). Please update the cubemx software to change this setting name.

#can-bus #cubemx-4.26

[Svenn Dahlstrom]

Posted on July 16, 2018 at 09:37

I also have the same issue for L4 V1.12.0.

Please fix

[Khouloud GARSI]

Posted on July 16, 2018 at 12:00

Hello,

Thanks for your feedback! This point is under check.

If the issue is confirmed, we will update the tool ASAP.

Khouloud.

[Svenn Dahlstrom]

Please fix this issue.

Just updated CubeMx to V4.27.0 and now I'm doing a project with F4 and firmware package V1.21.0 with the same issue.

This is frustrating.

[Khouloud GARSI]

Hi @Svenn Dahlstrom​ ,

Sorry for this inconvenience! The issue is confirmed and will be fixed in next releases of CubeMX.

Khouloud.

[AWill.2160]

Hi

As of CubeMX 5.3.0 and STM32F4 1.24.1, the issue is not fixed yet. Is it still planned to be fixed?

And if it is fixed, will we have to change again the setting of will be kept accross correctly?

[Khouloud ZEMMELI]

​Hello @AWill.2160​ ,

Could you please try with the 5.4.0 CubeMX version?

Best Regards,

Khouloud.