Skip to main content
Mikk Leini
Senior
January 22, 2026
Solved

CubeMX fails to load IOC file after enabling RAMCFG

  • January 22, 2026
  • 2 replies
  • 426 views

There's a bug in latest STM32CubeMX v6.16.1. When enabling RAMCFG for Appli on STM32N6 MCU, the IOC file becomes unloadable.

I attached the demonstration IOC file. I created new project for STM32N6570-DK board, enabled RAMCFG peripheral for Appli, checked the AXISRAM3-6 areas, defined single continuous area for those SRAMs in MMT and saved the project. After this CubeMX fails to load this IOC file. I get popup:

MikkLeini_0-1769065922714.png

In textual form the error is: Cannot invoke "com.st.microxplorer.mcu.memorymap.MemoryMapService.getInRangeAppRegions(long, long, com.st.microexplorer.mcu.Context)" because "this.mMemoryService" is null.

The workaround is to not enable RAMCFG in CubeMX, rather control the peripheral manually.

Best answer by Souhaib MAZHOUD

Hello @Mikk Leini 

Issue is fixed in the latest STM32CubeMX release 6.17.0 available here.

KR, Souhaib

2 replies

Technical Moderator
January 22, 2026

Hello @Mikk Leini 

Thanks for posting in STCommunity!

Was your project created with version 6.16.1 or was it migrated from an ancient version of CubeMX?

KR, Souhaib

To give better visibility on the answered topics, please click on 'Best answer' on the reply which solved your issue or answered your question.
Mikk Leini
Senior
January 22, 2026

Attached is a brand now project created today morning to rule out any other cause for the issue.

Technical Moderator
January 22, 2026

Hello @Mikk Leini 

I appreciate your clarification. The issue has been reported to the dedicated team for internal investigation and resolution. (Ticket 225670 This is an internal tracking number and is not accessible or usable by customers.)

BR, Souhaib

To give better visibility on the answered topics, please click on 'Best answer' on the reply which solved your issue or answered your question.
Souhaib MAZHOUDBest answer
Technical Moderator
February 25, 2026

Hello @Mikk Leini 

Issue is fixed in the latest STM32CubeMX release 6.17.0 available here.

KR, Souhaib

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