Appwizard function APPW_CreatePersistentScreens() takes long time to execute

[EmbeddedTech]

Hi @diego_charles ,

We are using Segger Appwizard tool to create our GUI design.
We are using around 28 .xbf files to support different font sizes and styles in our design. In that 6 font files will be used for multi language and each font file size used for multi language is around 5MB. So, our fonts itself takes 30MB of the flash memory.
When we load this code into our board, it takes almost an hour to execute the APPW_CreatePersistentScreens() function in the Appwizard's MainTask().

I would like to know what the above function does. How to reduce the time of execution.

What could be the reason for taking such a long time. We are using the external QSPI flash IS25WP512A. Since the flash access is beyond 16MB (3 byte addressing range) will it cause this delay? Is there anything I need to take care on the flash access part. 

Your help on this is highly appreciated.
Thanks.

[diego_charles]

Hi @EmbeddedTech 

Thank you for reaching out again! 

As I have been checking, our SDK does not contain the source code of the APPW_CreatePersistentScreens() function, so I can not inspect how it handles memory, the AppWizard User Guide & Reference Manual does not details this. 

I would recommend isolating the issue, trying the FlexSPI demos in your application and measuring how much time do you need to take to load a buffer from Flash, or copy and write buffers.

Additionally, consider if you have any cache enabled, and try the results by disabling it.  Check that you are using QSPI, and not standard SPI mode. Check if the Emwin libraries are not getting out of available SRAM or something related.

Anyway, I would recommend inquiring also with Segger about this, as they may be able to provide more details about  the operation of the function. 

I am sorry that I do not have more further insights at this time. 

Diego