Raspberry Pi - Revision history

Tectu: /* Introduction */

2016-08-26T19:35:23Z

‎Introduction

Tectu: /* Introduction */

2016-08-26T19:30:47Z

‎Introduction

Tectu: /* Creating a project */

2016-08-26T18:21:24Z

‎Creating a project

Tectu: /* Creating a project */

2016-08-26T18:19:59Z

‎Creating a project

Tectu: /* Creating a project */

2016-08-26T16:31:27Z

‎Creating a project

Tectu: /* Troubleshooting */

2016-08-26T16:29:53Z

‎Troubleshooting

Tectu: /* Creating a project */

2016-08-26T16:28:38Z

‎Creating a project

Tectu: /* Creating a project */

2016-08-26T16:27:16Z

‎Creating a project

Tectu at 16:18, 26 August 2016

2016-08-26T16:18:47Z

Tectu at 16:13, 26 August 2016

2016-08-26T16:13:26Z

@@ Line 6: / Line 6: @@
 * '''Dependencies:''' Installing [https://en.wikipedia.org/wiki/X_Window_System X], a desktop environment all required desktop applications and the required libraries to run custom built desktop applications pull many dependencies. This makes the system become heavy and bloated. However, the most important issue is that all these dependencies need to be maintainer. For example, when performing as sytem update, more components have to be tested to ensure the continuous and uninterrupted functioning of the device. This becomes even more important for mission critical equipmenet such as medical devices where each component needs to be audited and certified individually. Running µGFX on such a device '''vastly''' reduces the complexity of the system and therefore allows to built more stable & cheaper devices featuring a GUI while still running on a powerful Linux based system.
 * '''Resource requiremenets:''' Running a µGFX application requires order of magnitudes less resources than running a full desktop environment with a Qt or GTK application. This is a huge benefit for systems that require every free byte of money and every CPU cycle available to fullfill non-GUI tasks (eg. taking measurements, handling communication, ...)
-* '''Security:''' ToDo
+* '''Security:''' Having less software packages installed means less security vulnerabilities. A small, self contained µGFX application binary that doesn't require any other libraries or desktop environment services also means that the user of the product has less attacking vectors.
 == Used utilities ==

@@ Line 5: / Line 5: @@
 The most common question asked in this context is why to run µGFX on an embedded Linux device. Today's single board computers running Linux are powerful enough to run [https://en.wikipedia.org/wiki/X_Window_System X] and a complete desktop environment. Therefore, GUI applications can be written using desktop GUI frameworks such as Qt or GTK. Running µGFX instead on such as system has two main, but very important advantages:
 * '''Dependencies:''' Installing [https://en.wikipedia.org/wiki/X_Window_System X], a desktop environment all required desktop applications and the required libraries to run custom built desktop applications pull many dependencies. This makes the system become heavy and bloated. However, the most important issue is that all these dependencies need to be maintainer. For example, when performing as sytem update, more components have to be tested to ensure the continuous and uninterrupted functioning of the device. This becomes even more important for mission critical equipmenet such as medical devices where each component needs to be audited and certified individually. Running µGFX on such a device '''vastly''' reduces the complexity of the system and therefore allows to built more stable & cheaper devices featuring a GUI while still running on a powerful Linux based system.
-* '''Resource requiremenets:''' ToDo
+* '''Resource requiremenets:''' Running a µGFX application requires order of magnitudes less resources than running a full desktop environment with a Qt or GTK application. This is a huge benefit for systems that require every free byte of money and every CPU cycle available to fullfill non-GUI tasks (eg. taking measurements, handling communication, ...)
 * '''Security:''' ToDo

@@ Line 147: / Line 147: @@
 There are plenty of other demos available that can be tested directly by modifying the <code>GFXDEMO</code> variable in the Makefile. All demos can be found in the <code>/demos</code> directory inside the µGFX library. The following image shows the minesweeper demo:
-[[File:raspberrypi_minesweeper.jpg|none|thumb|Mine sweeper game demo.]]
+[[File:raspberrypi_minesweeper_web.jpg|none|thumb|Mine sweeper game demo.]]
 == Troubleshooting ==

← Older revision		Revision as of 18:19, 26 August 2016
Line 144:		Line 144:

	[[File:raspberrypi_gwin_lists_web.jpg\|none\|thumb\|Crude default demo of the widgets system.]]		[[File:raspberrypi_gwin_lists_web.jpg\|none\|thumb\|Crude default demo of the widgets system.]]
		+
		+	There are plenty of other demos available that can be tested directly by modifying the <code>GFXDEMO</code> variable in the Makefile. All demos can be found in the <code>/demos</code> directory inside the µGFX library. The following image shows the minesweeper demo:
		+
		+	[[File:raspberrypi_minesweeper.jpg\|none\|thumb\|Mine sweeper game demo.]]

	== Troubleshooting ==		== Troubleshooting ==

@@ Line 141: / Line 141: @@
 GFXBOARD = Linux-Framebuffer-Touch
 </source>
-The program should now compile, linkg & execute without any problem. Depending on the configuration, either the actual application shows up immediately or a calibration screen will be presented first. See [[Linux#Touchscreen_.2F_Mouse|here]] for more information.
+The program should now compile, linking & execute without any problem. Depending on the configuration, either the actual application shows up immediately or a calibration screen will be presented first. See [[Linux#Touchscreen_.2F_Mouse|here]] for more information.
 [[File:raspberrypi_gwin_lists_web.jpg|none|thumb|Crude default demo of the widgets system.]]

@@ Line 147: / Line 147: @@
 == Troubleshooting ==
 The most common issues are:
-* The Linux kernel you are using has not been compiled with framebuffer support. ''(See [[#Prerequisites|Prerequisites]]).''
+* The used Linux kernel has not been compiled with framebuffer support. ''(See [[#Prerequisites|Prerequisites]]).''
 * The framebuffer device is not accessible through one of the standard paths. ''(See [[Linux#Framebuffer|Linux Framebuffer]]).''
 * The user executing the µGFX application doesn't have the permission required to access the framebuffer device. ''(See [[Linux#Framebuffer|Linux Framebuffer]]).''
 * Another application (usually the X Server) already uses, and therefore blocks, the framebuffer. ''(See [[#Prerequisites|Prerequisites]]).''

@@ Line 122: / Line 122: @@
 </pre>
-[[File:rapberrypi_gdisp_basics_web.jpg|right|thumb|Result of the first compilation.]]
+[[File:rapberrypi_gdisp_basics_web.jpg|none|thumb|Result of the first compilation.]]
 Next, we'll add the touchscreen to the mix. Firstly, we want to change the demo from the passive drawing demo to a demo that actually accepts touch input. For this purpose, we '''change''' the <code>GFXDEMO</code> variable in the <code>Makefile</code> to use the <code>applications/combo</code> demo:
@@ Line 143: / Line 143: @@
 The program should now compile, linkg & execute without any problem. Depending on the configuration, either the actual application shows up immediately or a calibration screen will be presented first. See [[Linux#Touchscreen_.2F_Mouse|here]] for more information.
-////////// TODO: IMAGE /////////////////
+[[File:rapberrypi_gwin_lists_web.jpg|none|thumb|Result of the first compilation.]]
 == Troubleshooting ==

← Older revision		Revision as of 16:13, 26 August 2016
Line 1:		Line 1:
		+	[[File:raspberrypi stand backside.jpg\|right\|thumb]]
	µGFX applications can run natively (without emulation/simulation) on any Linux system. This means that µGFX can run without any problems on a Raspberry Pi. This is a step-by-step setup & configuration guide that will explain everything necessary to run µGFX on a Raspberry Pi.		µGFX applications can run natively (without emulation/simulation) on any Linux system. This means that µGFX can run without any problems on a Raspberry Pi. This is a step-by-step setup & configuration guide that will explain everything necessary to run µGFX on a Raspberry Pi.