Skip to main content
Associate II
October 23, 2025
Solved

Memory Pool View Scrolling Issue for X-Cube-AI 10.2.0 Pack

  • October 23, 2025
  • 1 reply
  • 357 views

Dear STM32CubeMX Support Team,

I would like to report two issues encountered while using X-Cube-AI version 10.2.0 during model analysis and training on the N6 series MCU with NPU support.

Bug 1: Memory Pool View Cannot Be Horizontally Scrolled in Netron Graph

After analyzing a model and clicking "Show Graph", the generated Netron visualization displays the memory pool section with a very long vertical axis that extends beyond the visible area. However, the view cannot be horizontally dragged or scrolled, which prevents full visibility of the memory pool details. This makes it difficult to inspect memory allocation information, especially when working with complex models.

  • Expected Behavior: The memory pool section should allow horizontal scrolling or panning to fully view all data.
  • Current Behavior: The graph is truncated; no scroll or drag functionality is available for the memory pool axis.

eric_green_0-1761201248776.png


Bug 2: Inconsistent Unit Display Between External Flash and Memory Pools

In the X-Cube-AI configrations (after NPU training) > Advanced Settings > External Flash configuration:

  • The Size field displays values in Mbytes (e.g., 16 Mbytes).
  • However, in the Memory Pools tab, the same value of the Size is shown in KB (e.g., 16 KB).

This inconsistency may lead to confusion during configuration and could result in incorrect memory allocation settings.

  • Expected Behavior: Both interfaces should use consistent units.

eric_green_0-1761201708529.png


Environment:

  • STM32CubeMX (MCUs)
  • X-Cube-AI Version: 10.2.0
  • Target MCU: N6 Series (with NPU)
  • Operating System: Windows 11

These issues affect usability and accuracy during AI model deployment. Thank you for your attention and support.

Best regards

Best answer by Ghofrane GSOURI

Hello @eric_green 

Your detailed description is much appreciated.

An internal ticket 220318 has been escalated to the development team to address the two issues.

THX

Ghofrane

1 reply

Ghofrane GSOURI
Ghofrane GSOURIBest answer
Technical Moderator
October 23, 2025

Hello @eric_green 

Your detailed description is much appreciated.

An internal ticket 220318 has been escalated to the development team to address the two issues.

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.
Associate II
November 21, 2025

Hi @Ghofrane GSOURI ,

The latest version of STM32CubeMX (v6.16) has not fixed any of the aforementioned issues.