Difference between revisions of "BareMetal"
| Line 1: | Line 1: | ||
| − | µGFX can run on any system without any underlying OS or RTOS. The '''RAW32''' port provides all the required implementations to run on a bare metal system. The only thing required to implement by the user are two small functions which are used to calculate delays. See [[BareBone#SysTick]]. | + | µGFX can run on any system without any underlying OS or RTOS. The '''RAW32''' port provides all the required implementations to run on a bare metal system. The only thing required to implement by the user are two small functions which are used to calculate delays. See [[BareBone#SysTick|SysTick]]. |
== Memory Management == | == Memory Management == | ||
Revision as of 13:36, 3 July 2015
µGFX can run on any system without any underlying OS or RTOS. The RAW32 port provides all the required implementations to run on a bare metal system. The only thing required to implement by the user are two small functions which are used to calculate delays. See SysTick.
Contents
Memory Management
µGFX can run either completely on static memory or on dynamic memory. While the first is very important for security and time critical applications it can be very tedious in generic applications. The RAW32 provides a memory manager to work with dynamic memory on any bare metal system. The following two configuration options are available:
- Use the µGFX built-in memory manager
- Use the C runtime library memory manager
Which one is used depends on the value of GOS_RAW_HEAP_SIZE inside of the configuration file.
Built-in memory manager
When GOS_RAW_HEAP_SIZE is set to a value greater than 0 then the built-in memory manager of µGFX is used. In this case the value of GOS_RAW_HEAP_SIZE specifies the size of the memory pool which the built-in memory manager will use.
C runtime library memory manager
When GOS_RAW_HEAP_SIZE is set to 0 then the memory manager of the C runtime library will be used. In that case gfxAlloc() and gfxFree() are just wrappers around malloc() and free()
