2019-11-08 08:51 AM
2019-11-08 10:46 AM
Not sure what you really mean ... Programming the internal flash in the F769 and the external QSPI? That's mainly governed by the MX25L51245:
mass erase 140 s and page (256 bytes) programming 0.25 ms typical. This gives approx. 205 s as lower bound for full 64 MBytes.
However, you won't ever come remotely close to this figure as the integrated ST-Link V2 supports at most 4 MHz SWD clock, that's the bottleneck. With ST-Link V3 you might come down to the theoretical lower bound, but: In contrast to the Nucleo boards it's a bit difficult to disconnect the integrated ST-Link and connect another one externally ...
2019-11-08 11:18 AM
If you haven't already, remove the verify step.
2019-11-08 11:34 AM
How do I remove the verify step? I am just pressing Run Target from within TouchGFX.
2019-11-08 11:34 AM
NOR Flash is a bit on the slow side erasing/writing.
Brighter bulbs may have facilitated the use of SDRAM or microSD card as a transitory debug memory during development cycles.
2019-11-08 11:37 AM
I want to be a brighter bulb. How would I go about facilitating the use of the SDRAM for this? Do you have any resources you can point me towards?
2019-11-08 12:18 PM
or perhaps SPI PSRAMs? (as used in some ESP32 modules I believe).
2019-11-08 12:30 PM
Sorry - thought you meant when programming/debugging with cubeide.