Development tools for external loaders

[RobNewbury]

I have developed a custom board for STM32F469NIH6 and is loosely based on STM32F469i-DISCO, it uses an external QSPI Flash memory type MT25QL128A as does the DISCO board. For this setup I am using ST supplied external loader MT25QL128A_STM32F469I-DK.stldr which works fine.
We have a requirement for a processor with a video codec, so the logical upgrade route is to STM32F769NIH6 to be used with external QSPI flash MT25QL512A. Both of these devices are pin compatible with the above MCU and QSPI, so the plan is to use the same custom PCB.
The problem comes in writing an external loader for this combination because.

1. While ST have a loader MT25QL512A_STM32769I-EVAL.stldr, this loader is not working in our setup, probably because of alternative QSPI I/O configuration which would likely be easy to alter in the loader code, however the source code is not in the github repository https://github.com/STMicroelectronics/stm32-external-loader
   Is it available elsewhere?
2. UM0892 says that the ST loader examples are available for three tool chains, MDK-ARM, EWARM and True-STUDIO.
   Is it possible to use STM32CubeIDE for external loader development as I understand the three tool chains mentioned come at some significant cost.  

[MOBEJ]

Hello @RobNewbury , 

For the .stldr you mention (MT25QL512A_STM32769I-EVAL.stldr) is delivered only as a binary in current STM32CubeProgrammer packages ( picture below ) ; the full source for that specific loader is not published on the GitHub repo .

For a custom QSPI pinout (different from STM32769I‑EVAL), you typically need to:

• Start from a similar published loader on GitHub  and adapt the GPIO / QSPI init, memory size, dummy cycles, and quad mode config to your hardware.

 

 

Br

[RobNewbury]

This is not very helpful as ST already have a similar loader (MT25QL512A_STM32769I-EVAL.stldr) which it would seem is only available as a binary.
Do ST not want us to use their processors in our poroducts?

There is certainly a lot to be said for open source.

 

[MOBEJ]

Hello @RobNewbury 

I reported this internally.

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

We appreciate your contribution.
Br

[jackobson6]

Since the STM32F769 is pin-compatible, you’re probably right that it’s just a QSPI configuration tweak in the loader. If the GitHub repo doesn’t include that specific example, you might need to adapt a similar loader and adjust the BSP settings manually. Also, if you’re exploring embedded development as a side skill, it’s interesting how niche firmware work like this can actually help you Earn Online through freelance or consulting projects.