Request for STM32CubeMX Configuration Guidance for Dual Octal Memory with STM32N657X0H3Q.

[Shivani]

Dear STM Community Team,

We are working with the STM32N657X0H3Q microcontroller in our custom hardware design. We have interfaced S80KS5123GABHB020 Octal RAM devices with the controller using the XSPI interface.

In our design, we are using a dual Octal memory configuration as described in the STM32N6 Reference Manual. The two 8-bit memories are configured to operate together as a 16-bit external memory interface.

We would like your guidance regarding the correct STM32CubeMX configuration settings for this dual Octal memory setup.

Our configuration details are:

• MCU: STM32N657X0H3Q

• External Memory: S80KS5123GABHB020

• Interface: XSPI

• Memory Configuration: Dual Octal mode (two 8-bit memories forming a 16-bit interface)

• Intended usage: External RAM for (ltdc)framebuffer

• Memory mapped access: XSPI memory-mapped mode

Could you please confirm the recommended STM32CubeMX settings for the following parameters?

1. XSPI mode selection:

   • Should the configuration be set as HEXASPI mode?

   • Are there any specific settings required for two parallel Octal RAM devices?

2. Memory configuration:

   • What should be the correct settings for:

     • Device size

     • Memory type

     • Data width

     • Chip select configuration

     • Delay block configuration

3. Timing parameters:

   • Recommended values for:

     • Read latency

     • Write latency

     • Clock frequency

     • DQS configuration

4. Memory-mapped mode:

   • Are any additional system configurations required before accessing the external RAM at the XSPI memory-mapped address region?

   • Are there any MPU/cache settings recommended for framebuffer usage?

We have referred to the STM32N6 reference manual and would like to confirm our STM32CubeMX configuration.

Any example project or recommended configuration for STM32N657X0H3Q with dual Octal RAM would be highly appreciated.

Thank you for your support.

Best regards,

Shivani e.

[KDJEM.1]

Hello ​@Shivani and welcome to the community;

 

There are differences between dual-octal mode and hexa mode. For example in Dual octal mode two external octal-SPI devices (device A and device B) are used and  in XSPI  (hexa)  mode a single external XSPI device is used.

For that, I recommend you to look at RM0486 precisely sections  Dual-octal configuration and  XSPI mode. 

I advise you to look at How to execute code from the external PSRAM using the STM32N6 | Community article may help you.

 

For  missing Dual octal mode in STM32CubeMx, I reported this issue internally for checking and fixing.

Internal ticket number CDM0065082 (This is an internal tracking number and is not accessible or usable by customers). 

 

Thank you.

Kaouthar

 

[Shivani]

Dear Kaouthar,

I have downloaded and installed the latest version of STM32CubeMX, but I still do not see the Dual-Octal mode option.

Could you please check the status of internal ticket CDM0065082 and let me know when the Dual-Octal mode support will be available in STM32CubeMX?

If possible, could you please provide an updated version the Dual-Octal mode in STM32CubeMX?

Thank you for your support.

Best regards,
shivani.

[KDJEM.1]

Hello ​@Shivani ;

 

The internal ticket CDM0065082 is currently under investigation.

I will let you know as soon as the issue is resolved.

Thank you.

 

Kaouthar
 

[Shivani]

hello ​@KDJEM.1 

Could you please let us know if there is any update on the internal ticket CDM0065082?

Thank you.
Shivani.

[seoranker]

This is a useful technical discussion for anyone working with STM32CubeMX and dual-octal memory configuration. Detailed community guidance can make complex hardware configuration easier to understand and troubleshoot. I also explore creative naming and online identity resources at Stylish Name. Thanks for sharing!

[wallpaper installation pro]

Thanks for sharing the update. The distinction between Dual-Octal and HexaSPI mode is especially helpful for understanding the STM32N6 XSPI configuration. It would be useful if ST could provide an example CubeMX configuration once the internal issue is resolved. That would make it much easier to configure dual Octal RAM correctly for framebuffer applications.