STM32H5 support for MX25L6433F

[Kostas Papouis]

Hello Everyone,

Is there any plan for ST to provide support drivers for the MX25L6433F serial NOR flash on the STM32H5 series of micros?

MX25L6433F is the flash used on the X-NUCLEO-GFX01M2.

Thanks. 

[Kostas Papouis]

Hi @Tesla DeLorean ,

Would you be able to generate the file in  .FLM  format?

Thank you in advance. 

[Tesla DeLorean]

I'll kick the tires on the build system this evening..

[Tesla DeLorean]

Tentative port and build for the H5 on KEIL

https://github.com/cturvey/stm32extldr/blob/main/h5_mx25l6433f/MX25L64_STM32H56X-CUSTOM78.FLM

[Kostas Papouis]

Hi @Tesla DeLorean ,

Did you use keil vision to generate the .flm external loader? If yes , do you mind sharing the project? 

Kind Regards, 

Kostas

[Tesla DeLorean]

Yes, in \Keil533\ARM\Flash

The loaders are part of a larger closed-source initiative.The pre-built loader are significantly less costly to support and maintain.

[Kostas Papouis]

Hi @Tesla DeLorean ,

I have attempted to use the template folder. 

Following are some configuration:

struct FlashDevice const FlashDevice = {
FLASH_DRV_VERS, // Driver Version, do not modify!
"STM32H56x MX25L6433F", // Device Name
EXTSPI, // Device Type
0x90000000, // Device Start Address
0x00800000, // Device Size in Bytes (8MB)
256, // Programming Page Size
0, // Reserved, must be 0
0xFF, // Initial Content of Erased Memory
100, // Program Page Timeout 100 mSec
3000, // Erase Sector Timeout 3000 mSec

// Specify Size and Address of Sectors
0x001000, 0x000000, // Sector Size 4kB (2048 Sectors)
SECTOR_END
};

Not sure if the following settings are correct:

Currently i get the following warning. The FLM file is generated but not displayed in the algorithm list.
.\Target.lin(21): warning: L6329W: Pattern FlashDev.o(RO) only matches removed unused sections.

Do you know what can cause this warning?

[Kostas Papouis]

Hi @Tesla DeLorean ,

Please ignore my previous message. I have managed to create the FLM file and is now listed in the algorithm list.

I created the fresh new project from the template and followed the steps described on the following link:

 https://www.keil.com/appnotes/files/apnt_333.pdf 

[Kostas Papouis]

Hi @Tesla DeLorean ,

I have been facing an issue with the external loader i have generated.

My application is writing to 0x90000000 address the following data:

const unsigned int delay_data[4] __attribute__((used)) = {0x01,0x02,0x03,0x04};

During download i get the following error:

Should the start address of the algorithm be 0x20003004(used in cubeIDE) or 0x20000000? Also should the Vector table address be modified?

Following the my configuration:

I have tried to increase the size of the algorithm but i had the same error.

Do you know what may causing this issue?

Thank you. 

[Kostas Papouis]

Changing the optimisation from 0 to 2 in my external loader project fixed the "Invalid access port" issue. 

As for the start address of the algorithm i have tried both 0x20003004 and 0x20000000. Both cases i was able to write to external flash successfully.