Board File - Revision history

Tectu: /* Templates */

2016-12-19T19:27:13Z

‎Templates

2016-12-19T19:27:00Z

‎Templates

2014-08-16T14:44:06Z

2014-07-03T21:42:31Z

2014-07-03T14:27:50Z

‎Templates

2014-07-03T14:09:54Z

2014-07-03T14:07:01Z

2014-07-03T13:59:37Z

2014-07-03T13:57:12Z

Created page with "A board file is a file which a module needs in order to communicate with the hardware."

New page

A board file is a file which a module needs in order to communicate with the hardware.

@@ Line 3: / Line 3: @@
 == Templates ==
-Each driver provides a template of it's board file. Copying this file to your project directory and implementing the routines is all there is to do. Note that you have to remove the ''_template'' part from the file name.
+Each driver provides a template of it's board file. Copying this file to your project directory and implementing the routines is all there is to do. Note that you have to remove the <code>_template</code> part from the file name.
 == Supported Boards ==

@@ Line 3: / Line 3: @@
 == Templates ==
-Each driver provides a template of it's board file. Copying this file to your project directory and implementing the routines is all there is to do.
+Each driver provides a template of it's board file. Copying this file to your project directory and implementing the routines is all there is to do. Note that you have to remove the ''_template'' part from the file name.
 == Supported Boards ==

@@ Line 4: / Line 4: @@
 == Templates ==
 Each driver provides a template of it's board file. Copying this file to your project directory and implementing the routines is all there is to do.
 == Modules ==

@@ Line 3: / Line 3: @@
 == Templates ==
-Each driver provides a template of it's board file.
+Each driver provides a template of it's board file. Copying this file to your project directory and implementing the routines is all there is to do.
 == Modules ==

← Older revision		Revision as of 14:09, 3 July 2014
Line 1:		Line 1:
−	Certain [[Architecture#Module\|modules]] have to communicate to hardware in order to fulfil their tasks. Those modules come with an additional driver layer. Each driver then needs a board file to talk to the hardware.	+	Certain [[Architecture#Module\|modules]] have to communicate to hardware in order to fulfil their tasks. Those modules come with an additional driver layer. Each driver then needs a board file to talk to the actual hardware.<br/>
		+	The board file needs to be provided by the user as it's implementation depends not only on the used underlying system (HAL), but also the actual hardware configuration (wiring).

	== Templates ==		== Templates ==

← Older revision		Revision as of 14:07, 3 July 2014
Line 1:		Line 1:
−	~~A board file is a file which a~~ [[Architecture#Module\|~~module~~]] ~~needs~~ in order to ~~communicate~~ with the hardware.	+	Certain [[Architecture#Module\|modules]] have to communicate to hardware in order to fulfil their tasks. Those modules come with an additional driver layer. Each driver then needs a board file to talk to the hardware.

	== Templates ==		== Templates ==

← Older revision		Revision as of 13:59, 3 July 2014
Line 1:		Line 1:
−	A board file is a file which a module needs in order to communicate with the hardware.	+	A board file is a file which a [[Architecture#Module\|module]] needs in order to communicate with the hardware.
		+
		+	== Templates ==
		+	Each driver provides a template of it's board file.
		+
		+	== Modules ==
		+	The following modules require a board file:
		+	* [[GDISP]]
		+	* [[GINPUT]]
		+	* [[GAUDIO]]