Skip to main content
CLanc.1
Associate II
December 9, 2025
Question

"mpu is null" Error after upgrade to Stm32CubeMX 6.16

  • December 9, 2025
  • 2 replies
  • 699 views

After upgrade from 6.15 to 6.16 on linux ubuntu 24.04 I got this blocking error if I load project file (created with cubemx 6.15):

cannot invoke com.st.microxploer.mcu.IP.getInstanceName() because mpu is null

I tried both "migrate" and "continue" options but I got the same error. Attached the project file

2 replies

Ghofrane GSOURI
Technical Moderator
December 9, 2025

Hello @CLanc.1 

I'm currently checking this behavior. I will get back to you asap.

It would be great if you could attach the whole log file .

THX

Ghofrane

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
CLanc.1
CLanc.1Author
Associate II
December 9, 2025

Hi,

I attached the log file

Ghofrane GSOURI
Technical Moderator
December 11, 2025

Hello @CLanc.1 

Thank you for your valuable contribution.

A ticket 223643 has been escalated to the development team for further investigation and resolution.

I will keep you updated with any progress.

THX

Ghofrane

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
CLanc.1
CLanc.1Author
Associate II
December 17, 2025

Hi,

I manually removed all the MMTAppRegionsCount and the file now loads on CubeMX 6.16. I never edited the file before so I still think there is a bug on CubeMX software regarding the MMTAppRegions.

Ghofrane GSOURI
Technical Moderator
December 18, 2025

Hello @CLanc.1 

Please use the attached .ioc file.
I have already corrected the MMT parameter value, so you should be able to migrate it and open it with STM32CubeMX 6.16.1 and 6.16.0. as shown below.

GhofraneGSOURI_0-1766042567069.png

I will be waiting for your feedback.

THX

Ghofrane

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.