Infos about dual QSPI and graphic assets upgrade

[MPast.1]

Hi Everybody,

 I need some infos about graphic assets upgrade while main APP and TouchGFX is running.

I have a customer board composed by STM32H743xxx , 2 QSPI and obiously a parallel RGB LCD screen  managed by LTDC.

The scope is to update the main APP and the graphic assets by a simple bootloader: while main APP is running I will receive new data and I will save them into the secondary QSPI memory.

QSPI memory are connected in dual mode with separated lines (both for signals and for CS).

in this way, in your opinion, Can the system access to the secondary memory (in writing mode) without disturb the graphic application?

If I'm not wrong I only need to change the linker script from:

QUADSPI (rx) : ORIGIN = 0x90000000, LENGTH = 16M

ExtFlashSection :
{
*(ExtFlashSection ExtFlashSection.*)
*(.gnu.linkonce.r.*)
. = ALIGN(0x4);
} >QUADSPI

FontFlashSection :
{
*(FontFlashSection FontFlashSection.*)
*(.gnu.linkonce.r.*)
. = ALIGN(0x4);
} >QUADSPI


TextFlashSection :
{
*(TextFlashSection TextFlashSection.*)
*(.gnu.linkonce.
. = ALIGN(0x4);
} >QUADSPI

to:

QUADSPI2 (rx) : ORIGIN = 0x90FA0000, LENGTH = 16M

In this way, the main APP can access to the secondary memory and store the new contents without intercat with LTDC.

When everything is transferred on the 2nd memory, I can copy the new data into the main QSPI memory and after a reboot Everything should works with new graphic assets..Is it right?

Does I need to change something else?

I need to stop Touchgfx task or LTDC int he main APP, while I will write in the second memory?

Are there others particular hints to apply.

Thanks a lot for your support and suggestions.

MarcoP.

[GaetanGodart]

Hello @MPast.1 ,

You have to make sure that the assets are the same size.

Also, when copying the assets into memory 1, you have to make sure they are copied at the right location.
For instance, if you have a 400 pixels image and a 800 pixels image, you will have to make sure to copy the new 400 pixels image at the position of the old 400 pixels image and same thing for the 800 pixels image.

Regards,

[MPast.1]

Hi @GaetanGodart ,

the main application can save into the secondary memory a new FW with a new graphic asset:this means that my new project should have 10 new images and 1 new fonts and increase the APP size by 512Kbytes.

The bootloader MUST copy all the contents of secondary memory, into the primary memory: in this case Bootloader doesn't need to access to actual graphic assets: text, images and the progressbar image are stored into the boot flash area.

When everything is complete, the new APP can be loaded with the new graphic.

So technically everyhting should work without problem: all process doesn't disturbe themself..

right?