"mpu is null" Error after upgrade to Stm32CubeMX 6.16

[CLanc.1]

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

[Ghofrane GSOURI]

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

[CLanc.1]

Hi,

I attached the log file

[Ghofrane GSOURI]

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

[Ghofrane GSOURI]

Hello @CLanc.1 

After checking the provided IOC and all related MMT parameters, we found that the Cortex name of the regions had been changed to incorrect values:

MMTAppReg1.MEMORYMAP.ContextName = Cortex-M33NS
MMTAppReg3.MEMORYMAP.ContextName = Cortex-M33NS

 instead of:

MMTAppReg1.MEMORYMAP.ContextName = CortexM33
MMTAppReg3.MEMORYMAP.ContextName = CortexM33

 To verify that these modifications were not generated by STM32CubeMX, a fresh IOC was created using MX 6.15.0 and the MMT parameters were checked. In this new IOC, the Cortex name was correctly set to `CortexM33`. The same behavior was confirmed with versions 6.12.0, 6.11.0, and 6.14.0, which indicates that your IOC was modified manually.

After correcting the Cortex name in your IOC, the IOC migrated successfully to STM32CubeMX 6.16.0.

[CLanc.1]

Hi,

I looked at my git repository, the line 

MMTAppReg1.MEMORYMAP.ContextName = Cortex-M33NS

appeared after update from Cube MX6.14 to 6.15, look at the attached diff.

I tried your solution but it doesn't work, the error is still here. Any suggestion on fix the .ioc without start a new project from scratch? Do I have to reinstall 6.15 and never update?

Thank you

[CLanc.1]

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]

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.

I will be waiting for your feedback.

THX

Ghofrane