Associate III

Solved

Serious Bug In STM32Cube Version 6.0.0.0 When Migrating Projects

Forum|Forum|5 years ago
July 28, 2020
11 replies
3690 views

We have project for STM32F405 configured and code generated with STM32Cube 5.x.x.x.

After installing Version 6.0.0.0 and when project was migrated to STM32Cube Version 6.0.0.0 and code regenerated, all IRQ priorities for peripherals (UART, SPIs, I2C, USB, etc) were set to 0 instead to 5. Firmware compiled but it was crashing in various parts.

Details from IOC file:

Original File:

MxCube.Version=5.6.1

MxDb.Version=DB.5.0.60

Migrated File:

MxCube.Version=6.0.0

MxDb.Version=DB.6.0.0

All IRQ priorities set to 0. Had to manually change them to 5 in order to get firmware running again.

We also have project for STM32L072 and on that MCU Version 6.0.0.0 also migrates all IRQ priorites to 0. Had to be fixed manually.

This seems to be fairly serious fault that is pretty much show stopper for us.

This topic has been closed for replies.

Best answer by Nesrine.JLASSI

Hello,

A new STM32CubeMX release will delivered to correct this issue as soon as possible.

Best regards,

Nesrine

Dub BartolecAuthor

Associate III

I've raised a ticket with STM32 support team.

Hopefully they'll suggest solution.

Nesrine.JLASSI

Visitor II

Hello @Dub Bartolec

Thanks for the feedback, issue reported to the tool development team that will plan the correction.

Best regards,

Nesrine

Nesrine.JLASSIBest answer

Visitor II

Hello,

A new STM32CubeMX release will delivered to correct this issue as soon as possible.

Best regards,

Nesrine

awiernie

Associate III

We have seen the same. Using the latest version of the configurator some settings had disappeared, irq 0 instead of irq 5 on some places.

Houda GHABRI

ST Employee

Hi @awiernie @Dub Bartolec ,

STM32CubeMX 6.0.1 release solving this issue is available now , you can get it from ST website .

We are sorry for the inconvenience and we are analyzing the issue to learn and improve our upcoming releases.

Best regards,

Houda

Dub BartolecAuthor

Associate III

Hi @Houda GHABRI ,

Thanks for quick resolution.

Regards

dwei.11

Visitor II

@Houda GHABRI

hi，this problem is still there in stm32cubemx 6.0.1。 the irq priority is still set to 0 instead of 5. and what is worse is that in the stm32cubemx 6.0.1 , I create a new project using freertos + lwip to achieve "ping" is not working any more. bug in the stm32cubemx 5.x.x work well。

dwei.11

Visitor II

@Dub Bartolec the problem is still there, be careful

Dub BartolecAuthor

Associate III

Hi @dwei.1 ,

Yeah I am aware of it. They haven't fixed it at all !

They've just put some warning that priorites need to be set manually.

I had lengthy (and angry) rant in another thread about it.

What a joke. They stuffed up functionality that worked very well for 10+ years !

dwei.11

Visitor II

@Dub Bartolec

Yeah, What a joke, when I upgrade to cubemx 6.0.1, it can't work, OMG, unbelievable, then I have to downgrade to cubemx 5.4.

Dub BartolecAuthor

Associate III

It is absolute nightmare what they are doing. They are re-architecturing app to support future and other real time OSes (their words). They do not support them yet (nor they will in my view for a next 12 months) but they are perfectly happy to break functionality people rely on and don't even think about it anymore as it worked for years.

I can see flood of same questions on this forum. "I built project using STM32Cube and my serial is not working. Aah,. forgot to mention I enabled FreeRTOS", etc. etc.

I've been using STM32Cube since first release and what they did with 6.0.0.0 is worst I've ever seen by any company.

I have 50+ projects that are generated with various versions of STM32Cube for different clients. I need to keep STM32Cube version for each release we did as I cannot trust that what they "improved" in new version will not break earlier firmware release we did. Sometimes projects are not touched for 2-3 years then we add some functionality and so on and on.

I have test project on STM32F411 that runs every single peripheral and if it fails I do not update STM32Cube.

That's how I found about this 6.0.0.0 issue.

It just looks like they are doing all those crucial changes and no QA in place then we are wasting our time to debug and tell them what's wrong.

Pavel A.

Pity. All the pretty cubes falling apart... ((

Houda GHABRI

ST Employee

Hi @dwei.1 @Dub Bartolec ,

To avoid this problem, we are currently putting out a warning asking to manually set priorities.

At the same time, we are improving this solution to have the best one in our next versions.

We are again sorry for the inconvenience.

Best regards,

Houda

Show more replies

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded