BareMetal - Revision history

Tectu: /* Example */

2021-08-11T09:27:25Z

‎Example

Tectu: /* SysTick */

2021-08-06T17:46:58Z

‎SysTick

Tectu: /* SysTick */

2021-08-06T17:46:44Z

‎SysTick

Tectu: /* Example */

2018-05-24T10:18:18Z

‎Example

Tectu: /* SysTick */

2016-12-21T17:15:46Z

‎SysTick

Tectu at 17:14, 21 December 2016

2016-12-21T17:14:33Z

Tectu: /* Memory Management */

2016-12-21T17:11:56Z

‎Memory Management

Tectu at 18:12, 8 December 2015

2015-12-08T18:12:04Z

Tectu at 18:11, 8 December 2015

2015-12-08T18:11:48Z

Tectu: Tectu moved page BareBone to BareMetal

2015-12-08T18:09:53Z

Tectu moved page BareBone to BareMetal

@@ Line 40: / Line 40: @@
+}
-gTicks gfxMillisecondsToTicks(delaytime_t ms)
+gTicks gfxMillisecondsToTicks(gDelay ms)
+{
 	return ms;

@@ Line 24: / Line 24: @@
 Some parts of the µGFX library require how much time passed by. For this access to the systems tick counter (SysTick) is required. To give µGFX the ability to calculate how much time passed the following to functions need to be implemented in the users application code:
 <syntaxhighlight lang="c">
-systemticks_t gfxSystemTicks(void);
+gTicks gfxSystemTicks(void);
-systemticks_t gfxMillisecondsToTicks(delaytime_t ms);
+gTicks gfxMillisecondsToTicks(delaytime_t ms);
 </syntaxhighlight>
 The first one, <code>gfxSystemTicks()</code>, needs to return the current value of the systick counter. The second one, <code>gfxMillisecondsToTicks()</code> needs to convert the provided value in milliseconds to systicks.

@@ Line 35: / Line 35: @@
 #include "gfx.h"
-systemticks_t gfxSystemTicks(void)
+gTicks gfxSystemTicks(void)
+{
 	return HAL_GetTick();
+}
-systemticks_t gfxMillisecondsToTicks(delaytime_t ms)
+gTicks gfxMillisecondsToTicks(delaytime_t ms)
+{
 	return ms;

@@ Line 32: / Line 32: @@
 The following is an example showing how to implement the two functions when using an STM32F4 microcontroller using the STM32Cube HAL. Note that in this case the systick was set up to be incremented once every millisecond. If your systick updates in a different interval you need to do the corresponding calculations in ''gfxMillisecondsToTicks()''.
 <syntaxhighlight lang="c">
 #include "stm32f4xx_hal.h"
 systemticks_t gfxSystemTicks(void)
@@ Line 45: / Line 45: @@
+}
 </syntaxhighlight>

@@ Line 27: / Line 27: @@
 systemticks_t gfxMillisecondsToTicks(delaytime_t ms);
 </syntaxhighlight>
-The first one, ''gfxSystemTicks()'', needs to return the current value of the systick counter. The second one, ''gfxMillisecondsToTicks()'' needs to convert the provided value in milliseconds to systicks.
+The first one, <code>gfxSystemTicks()</code>, needs to return the current value of the systick counter. The second one, <code>gfxMillisecondsToTicks()</code> needs to convert the provided value in milliseconds to systicks.
 === Example ===

@@ 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 [[#SysTick]].
-The '''RAW32''' port also provides a multi-tasker that you can use in your own applications. The threads created are co-operative, non-preemptive threads (you have to use ''gfxSleepMilliseconds()'' or ''gfxYield()'' to give another task a chance to run). See [[GOS#Threading|GOS]].
+The '''RAW32''' port also provides a multi-tasker that you can use in your own applications. The threads created are co-operative (non-preemptive) threads (you have to use <code>gfxSleepMilliseconds()</code> or <code>gfxYield()</code> to give another task a chance to run). See [[GOS#Threading|GOS]].
 == Using RAW32 ==
@@ Line 11: / Line 11: @@
 * Use the C runtime library memory manager
-Which one is used depends on the value of '''GFX_OS_HEAP_SIZE''' inside of the [[Configuration|configuration file]].
+Which one is used depends on the value of <code>GFX_OS_HEAP_SIZE</code> inside of the [[Configuration|configuration file]].
 === Built-in memory manager ===
-When ''GFX_OS_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 ''GFX_OS_HEAP_SIZE'' specifies the size of the memory pool which the built-in memory manager will use.
+When <code>GFX_OS_HEAP_SIZE</code> is set to a value greater than 0 then the built-in memory manager of µGFX is used. In this case the value of <code>GFX_OS_HEAP_SIZE</code> specifies the size of the memory pool which the built-in memory manager will use.
 === C runtime library memory manager ===
-When ''GFX_OS_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()''.
+When <code>GFX_OS_HEAP_SIZE</code> is set to 0 then the memory manager of the C runtime library will be used. In that case <code>gfxAlloc()</code> and <code>gfxFree()</code> are just wrappers around <code>malloc()</code> and <code>free()</code>.
-Note that many C library implementations of ''malloc()'' and ''free()'' have bugs that cause them to crash if the stack is changed (as it is for threading as required by µGFX). For this reason, if you are getting strange crashes it is advisable to use the built-in memory manager and to avoid using ''malloc()'' and ''free()'' in your own code (use ''gfxAlloc()'' and ''gfxFree()'' instead).
+Note that many C library implementations of <code>malloc()</code> and <code>free()</code> have bugs that cause them to crash if the stack is changed (as it is for threading as required by µGFX). For this reason, if you are getting strange crashes it is advisable to use the built-in memory manager and to avoid using ''malloc()'' and <code>free()</code> in your own code (use <code>gfxAlloc()</code> and <code>gfxFree()</code> instead).
 == SysTick ==

← Older revision		Revision as of 17:11, 21 December 2016
Line 2:		Line 2:

	The '''RAW32''' port also provides a multi-tasker that you can use in your own applications. The threads created are co-operative, non-preemptive threads (you have to use ''gfxSleepMilliseconds()'' or ''gfxYield()'' to give another task a chance to run). See [[GOS#Threading\|GOS]].		The '''RAW32''' port also provides a multi-tasker that you can use in your own applications. The threads created are co-operative, non-preemptive threads (you have to use ''gfxSleepMilliseconds()'' or ''gfxYield()'' to give another task a chance to run). See [[GOS#Threading\|GOS]].
		+
		+	== Using RAW32 ==
		+	To run µGFX on a bare-metal platform without any underlying operating system, the Raw32 port has to be enabled by setting <code>GFX_USE_OS_RAW32</code> to <code>TRUE</code> in the [[Configuration\|configuration file]].

	== Memory Management ==		== Memory Management ==

← Older revision		Revision as of 18:12, 8 December 2015
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 [[~~BareMetal~~#~~SysTick\|~~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 [[#SysTick]].

	The '''RAW32''' port also provides a multi-tasker that you can use in your own applications. The threads created are co-operative, non-preemptive threads (you have to use ''gfxSleepMilliseconds()'' or ''gfxYield()'' to give another task a chance to run). See [[GOS#Threading\|GOS]].		The '''RAW32''' port also provides a multi-tasker that you can use in your own applications. The threads created are co-operative, non-preemptive threads (you have to use ''gfxSleepMilliseconds()'' or ''gfxYield()'' to give another task a chance to run). See [[GOS#Threading\|GOS]].

← Older revision		Revision as of 18:11, 8 December 2015
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\|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 [[BareMetal#SysTick\|SysTick]].

	The '''RAW32''' port also provides a multi-tasker that you can use in your own applications. The threads created are co-operative, non-preemptive threads (you have to use ''gfxSleepMilliseconds()'' or ''gfxYield()'' to give another task a chance to run). See [[GOS#Threading\|GOS]].		The '''RAW32''' port also provides a multi-tasker that you can use in your own applications. The threads created are co-operative, non-preemptive threads (you have to use ''gfxSleepMilliseconds()'' or ''gfxYield()'' to give another task a chance to run). See [[GOS#Threading\|GOS]].

← Older revision	Revision as of 18:09, 8 December 2015
(No difference)