Serious Bug In STM32Cube Version 6.0.0.0 When Migrating Projects
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2020-07-28 6:44 AM
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.
Solved! Go to Solution.
- Labels:
-
Bug-report
-
Interrupt
-
STM32CubeMX
-
STM32F4 Series
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2020-07-30 8:02 AM
Hello,
A new STM32CubeMX release will delivered to correct this issue as soon as possible.
Best regards,
Nesrine
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2020-07-28 4:21 PM
I've raised a ticket with STM32 support team.
Hopefully they'll suggest solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2020-07-30 2:09 AM
Hello @Dub Bartolec​
Thanks for the feedback, issue reported to the tool development team that will plan the correction.
Best regards,
Nesrine
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2020-07-30 8:02 AM
Hello,
A new STM32CubeMX release will delivered to correct this issue as soon as possible.
Best regards,
Nesrine
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2020-08-14 12:27 PM
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2020-08-18 5:32 AM
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2020-08-18 6:51 PM
Hi @Houda GHABRI​ ,
Thanks for quick resolution.
Regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2020-09-13 9:01 PM
@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。
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2020-09-13 9:02 PM
@Dub Bartolec​ the problem is still there, be careful
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2020-09-13 10:05 PM
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 !
