The pool here is pretty shallow, most have their own jobs to attend too, and the pay here is awful.
No one has your hardware, so you're likely going to have to debug the situation yourself.
Not much to work with here. A "not working" report needs more specificity, perhaps showing what the debugger can see currently in working vs non-working cases.
If you have one app working with QSPI, and another not, you're going to need to go through the clock, pin and peripheral settings on the STM32 to see where they diverge.
If you can access the QSPI in the TouchGFX app, but there is not content, then you're going to have to find away to load the memory with the content generated by the toolchain.
Keil is not going to be able to write the QSPI from the debugger without a custom flash algorithm tailored for your board.
Similarly STM32 Cube Programmer will need a custom external loader.
