2026-04-20 11:10 PM - last edited on 2026-04-22 3:19 AM by KDJEM.1
It looks like I have the 32F469IDISCOVERY board that looks to be powered ok via USB connector CN13, however the board doesn't appear to have demo software preloaded. COM LED LD6 flashes red.
I note on the ST website that there is the 32F469IDISCOVERY compiled demo binary, which I have downloaded.
The Readme says: The QSPI external flash loader is not integrated with supported toolchains, it ís only supported with
STM32 ST-Link Utility V3.7 or later.
But the ST website says that the ST-Link Utility is NRND and to use STM32CubeProg instead. I've tried the latest version of STM32CubeProg and it can't connect to the board via USB:
Error: Establishing connection with device failed.
What is the best way of programming the board with this file please?
Kind regards,
Al
Solved! Go to Solution.
2026-04-23 3:13 AM
In other words, you have installed the drivers for the ST-Link, do you ?
Have you tried to connect the board in question to another PC, and see if the ST-Link shows up ?
Or connect another ST board with onboard ST-Link to the same PC ?
Sometimes even USB cables can cause problems.
2026-04-21 2:31 AM
Hello,
Why are you using CN13 to connect to the board? CN13 is used for USB of the chip.
If you need to power the board with USB, you need to close JP2 on 3-4 position.
And you need to connect to CN1 over ST-LINK to connect to the board.
2026-04-21 2:46 AM - edited 2026-04-21 2:50 AM
@alw wrote:It looks like I have the 32F469IDISCOVERY board
If you're not sure what you have, you could post some good, clear photos of it - both sides.
Full details can be found on the Product Page:
@alw wrote:looks to be powered ok via USB connector CN13
Full details of the powering options are in the User Manual:
@alw wrote:What is the best way of programming the board with this file please?
Indeed, STM32CubeProgrammer is the tool to use now.
Also STM32CubeIDE - for software development, loading, and debugging.
For programming and/or debugging, use the built-in ST-Link on CN1:
PS:
If connection issues persist:
How to solve connection errors when connecting and programming the STM32 target board.
How to solve debugger connection issues
2026-04-21 4:35 AM
> I note on the ST website that there is the 32F469IDISCOVERY compiled demo binary, which I have downloaded.
> The Readme says: The QSPI external flash loader is not integrated with supported toolchains, it ís only supported with STM32 ST-Link Utility V3.7 or later.
This board was released 2015, when the SPL was still "state of the art".
Consequently, the demo is originally based upon SPL code.
You will probably still find the "legacy" firmware package including this demo, the SPL, and peripheral examples in source code on ST's website.
Not sure if this demo was ever ported to Cube/HAL code, or if there ever was a Cube package specifically for this board. I don't have such a board, and for a reason.
Those "feature-rich" boards, often including an onboard LCD and external memory, have many otherwise useful pins tied to exactly those special features. This makes the board itself relatively useless for many other use cases, especially considering the price.
Not to dissuade you, but a point to consider.
The other end of the spectrum are Nucleo boards, which come with a bare minimum of onboard stuff, routing most of the GPIOs to external connectors, and thus support a wide range of use cases.
Whatever works best in your case.
2026-04-21 4:50 AM
@Ozone wrote:This board was released 2015, when the SPL was still "state of the art".
@alw Probably also before TouchGFX came along - which is now ST's standard for graphic displays
I also tend to find that all the bells & whistles on this type of board tend to get in the way of actual development ...
2026-04-21 4:54 AM
Hello,
@Ozone wrote:
This board was released 2015, when the SPL was still "state of the art".
Consequently, the demo is originally based upon SPL code.
If I remember well STM32F469 was released with HAL not with SPL.
https://github.com/STMicroelectronics/STM32CubeF4/tree/master/Projects/STM32469I-Discovery
Other older F4 series was indeed the case: Ex: STM32F407.
2026-04-21 4:58 AM
If I remember well, that demo was indeed using TouchGFX. At that time TouchGFX is not part of ST offer and it belonged to another Danemark company..
2026-04-21 5:58 AM
You might be right, I vaguely remember this being one of the first boards with Cube/HAL support instead of SPL.
And not that I dislike this board, but re-using boards for different projects with "wildly" different requirements, I very much prefer the F407 Disco with a minimum of preallocated pins, or a Nucleo.
If I'm not mistaken, the F407 Disco is ST's most often sold evaluation board.
2026-04-21 6:33 PM
Thanks very much for all the comments and feedback. For clarity it is a 32F469IDISCOVERY board.
I am powering via CN13 with jumper JP2 in the correct position. I have done this to ensure that adequate power is provided to the board in all circumstances, such as during initial USB enumeration.
I am looking to use this board primarily for TouchGFX development, with a minimal external I/O requirement that can be accommodated by the Arduino headers. I have plenty of NUCLEO boards that I use on other projects with STM32CubeMX and STM32CubeIDE.
I was just looking for clarity on how to load the demo binary just to try out the board's capabilities in the first instance, as the current version of STM32CubeProg couldn't establish a connection over USB. This board is not marked as obsolete by ST, so should in theory at least be supported by current STM32 development tools.
Kind regards,
Al
2026-04-21 11:02 PM
> I am powering via CN13 with jumper JP2 in the correct position. I have done this to ensure that adequate power is provided to the board in all circumstances, such as during initial USB enumeration.
You could try to power the board from the mentioned CN6 input (6..9V).
The default USB current limit is 100mA, the higher 500mA supply must be "negotiated" by the driver after registtration. You can run into trouble when the board draws more than that during this phase. I had such issues occasionally with boards that had a LCD screen.
Another option would be to prevent the target application from starting up (and initializing the screen), e.g. by setting a BOOT0 jumper.
If the ST-Link comes up in this configuration, you probably have a supply issue.
Some PCs (and USB ports) might be more tolerant than others in such cases, by the way.