TouchGFX framebuffer location for STM32H563
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-01-09 9:33 AM
Is there a recommended RAM address for placing the framebuffer on the STM32H563? I just picked out 0x20040000 but wondered if I should just put it at the beginning address (0x20000000), wasn't sure what is recommended.
Solved! Go to Solution.
- Labels:
-
TouchGFX
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-01-17 1:28 AM - edited ‎2025-01-17 6:18 AM
Hello @PFlor.2 ,
This code (talking about the NOLOAD)
prevents the framebuffer section from being loaded into the ram at startup.
Is it what you were asking?
Regards,
Software engineer at ST (TouchGFX)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-01-09 10:47 AM
Why you ask, this is based on your app requirments and
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-01-13 1:33 AM
Hello @PFlor.2 ,
It is recommended to keep the framebuffer location as "by allocation" to let TouchGFX decide where to put the framebuffer :
You can have a look at our TBS to see how we set it up.
Regards,
Software engineer at ST (TouchGFX)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-01-13 7:27 AM
Thanks for the tip but I started that way and it appears that Flash memory is taken with this approach, by address does not utilize the flash space like by allocation does. Can you advise on this?
By Allocation:
By Address:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-01-13 8:26 AM
If you choice by address, then linker script require reservations for this, for example
RAM 0x20000000 256k
RAMFB 0x20040000 ...
but as i show you better is use maybe RAM3
And by allocation result to init in flash when you dont mark it as noinit... result same size in flash and ram.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-01-13 8:32 AM
yes, I hadn't reserved the RAM in the linkerscript yet so I will do that. I agree about using RAM3 and chose 0x20050000 for frame buffer1 and 0x20076000 for frame buffer2 (320x240 pixel display with 16-bit color).
If using "By Allocation" how do you choose noinit so the flash is not consumed?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-01-14 1:29 AM
Hello @PFlor.2 ,
This is how it is done in our TBS:
Is this what you are asking for?
Regards,
Software engineer at ST (TouchGFX)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-01-16 3:26 PM
Does this prevent the "By Allocation" method from consuming internal flash memory resources??
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-01-17 1:28 AM - edited ‎2025-01-17 6:18 AM
Hello @PFlor.2 ,
This code (talking about the NOLOAD)
prevents the framebuffer section from being loaded into the ram at startup.
Is it what you were asking?
Regards,
Software engineer at ST (TouchGFX)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-01-17 5:41 AM
Are you sure Gaetan , that ALIGN(0x4) is ok for LTDC FIFO ?
