Skip to main content
Torris-Yin
Associate
Dec 15, 2024 10:54 AM UTC
Solved

Package error when importing examples of NUCLEO-U031R8

The MCU of NUCLEO-U031R8 is LQFP64. But if I import the example of NUCLEO-U031R8, STM32CubeMX shows it as UFBGA64.

TorrisYin_0-1734259967063.png

 

This topic has been closed for replies.
Imen.DBest answer
ST Technical Moderator
Dec 16, 2024 3:31 PM UTC

Hi @Torris-Yin ,

I see the contradiction now.

For the selected project: the mounted device is STM32U031R8Tx (LQFP64 package).

ImenD_0-1734360849671.png

But, when you open the project, it is mentioned STM32U031R8Ix (which is UFBGA64 package).

ImenD_2-1734361440867.png

Thank you for rising this up.

I escalated this issue to our CubeMX team (via internal ticket number: 198841)

(PS: Internal ticket number is only for ST reference, not accessible outside of ST)

In order to give better visibility on the answered topics, please click on 'Best answer' on the reply which solved your issue or answered your question. Thanks

4 replies

ST Technical Moderator
Dec 16, 2024 8:30 AM UTC

Hello @Torris-Yin ,

The STM32U031R8T6 MCU is an LQFP64 package, and STM32U031R8I6 is an UFBGA64 package.

In your case, you are using the example with STM32U031R8Ix which is an UFBGA64 package.

ImenD_0-1734337756271.png

In order to give better visibility on the answered topics, please click on 'Best answer' on the reply which solved your issue or answered your question. Thanks
Torris-Yin
Associate
Dec 16, 2024 2:08 PM UTC

Hello, @Imen.D 

I am using the example of NUCLEO-U031R8, which is STM32U031R8T6. I attached a video of my operation.

Thanks. 

TorrisYin_0-1734357791909.png

 

Imen.DBest answer
ST Technical Moderator
Dec 16, 2024 3:31 PM UTC

Hi @Torris-Yin ,

I see the contradiction now.

For the selected project: the mounted device is STM32U031R8Tx (LQFP64 package).

ImenD_0-1734360849671.png

But, when you open the project, it is mentioned STM32U031R8Ix (which is UFBGA64 package).

ImenD_2-1734361440867.png

Thank you for rising this up.

I escalated this issue to our CubeMX team (via internal ticket number: 198841)

(PS: Internal ticket number is only for ST reference, not accessible outside of ST)

In order to give better visibility on the answered topics, please click on 'Best answer' on the reply which solved your issue or answered your question. Thanks
ST Technical Moderator
Jul 10, 2025 8:45 AM UTC

Hello @Torris-Yin ,

This issue is fixed in the STM32CubeMX v6.15.0

Thank you once again for your contribution.

In order to give better visibility on the answered topics, please click on 'Best answer' on the reply which solved your issue or answered your question. Thanks