Electrum Examples - Revision history

Support at 22:22, 5 December 2012

Support — Wed, 05 Dec 2012 22:22:43 GMT

← Older revision		Revision as of 22:22, 5 December 2012
Line 1:		Line 1:
	These code examples will help you get started with your user space applications on the Micromint Electrum. A zip file of the examples can be downloaded from the [[Electrum_Documentation#Code_Examples\|Software Updates section of the Electrum Wiki]]. Our support staff (support@micromint.com) can assist you with questions on specific functions.		These code examples will help you get started with your user space applications on the Micromint Electrum. A zip file of the examples can be downloaded from the [[Electrum_Documentation#Code_Examples\|Software Updates section of the Electrum Wiki]]. Our support staff (support@micromint.com) can assist you with questions on specific functions.

-	Since Linux implements virtual memory, there is no direct access to processor registers. One popular alternative to access processor registers in user space is to open a handle to /dev/mem and then use mmap() to map a virtual memory address to a physical memory address. These examples use this approach to access processor registers. The peripheral code is adapted from the [http://www.atmel.com/~~dyn~~/~~products/tools_card~~.~~asp?tool_id=4343~~ Atmel AT91 Softpack library].	+	Since Linux implements virtual memory, there is no direct access to processor registers. One popular alternative to access processor registers in user space is to open a handle to /dev/mem and then use mmap() to map a virtual memory address to a physical memory address. These examples use this approach to access processor registers. The peripheral code is adapted from the [http://www.atmel.com/tools/AT91SAMSOFTWAREPACKAGE.aspx Atmel AT91 Softpack library].

	The default compiler is the EmDebian cross-compiler. For details on the toolchain installation, please refer to the [[Electrum-100_Manual/2#Toolchain_installation\|manual]]. You can choose another compiler by specifying a COMPILER variable in the Makefile.		The default compiler is the EmDebian cross-compiler. For details on the toolchain installation, please refer to the [[Electrum-100_Manual/2#Toolchain_installation\|manual]]. You can choose another compiler by specifying a COMPILER variable in the Makefile.

Support at 19:50, 26 March 2012

Support — Mon, 26 Mar 2012 19:50:35 GMT

← Older revision		Revision as of 19:50, 26 March 2012
Line 1:		Line 1:
-	These code examples will help you get started with your user space applications on the Micromint Electrum. A zip file of the examples can be downloaded from the [[Electrum_Documentation#~~Code_Example_Updates~~\|Software Updates section of the Electrum Wiki]]. Our support staff (support@micromint.com) can assist you with questions on specific functions.	+	These code examples will help you get started with your user space applications on the Micromint Electrum. A zip file of the examples can be downloaded from the [[Electrum_Documentation#Code_Examples\|Software Updates section of the Electrum Wiki]]. Our support staff (support@micromint.com) can assist you with questions on specific functions.

	Since Linux implements virtual memory, there is no direct access to processor registers. One popular alternative to access processor registers in user space is to open a handle to /dev/mem and then use mmap() to map a virtual memory address to a physical memory address. These examples use this approach to access processor registers. The peripheral code is adapted from the [http://www.atmel.com/dyn/products/tools_card.asp?tool_id=4343 Atmel AT91 Softpack library].		Since Linux implements virtual memory, there is no direct access to processor registers. One popular alternative to access processor registers in user space is to open a handle to /dev/mem and then use mmap() to map a virtual memory address to a physical memory address. These examples use this approach to access processor registers. The peripheral code is adapted from the [http://www.atmel.com/dyn/products/tools_card.asp?tool_id=4343 Atmel AT91 Softpack library].

Support at 20:40, 15 March 2012

Support — Thu, 15 Mar 2012 20:40:45 GMT

← Older revision		Revision as of 20:40, 15 March 2012
Line 1:		Line 1:
-	These code examples will help you get started with your user space applications on the Micromint Electrum. A zip file of the examples can be downloaded from the Software ~~Update~~ section of the ~~[http://wiki.micromint.com/index.php/Electrum_Documentation~~ Electrum ~~Documentation~~ Wiki]. Our support staff (support@micromint.com) can assist you with questions on specific functions.	+	These code examples will help you get started with your user space applications on the Micromint Electrum. A zip file of the examples can be downloaded from the [[Electrum_Documentation#Code_Example_Updates\|Software Updates section of the Electrum Wiki]]. Our support staff (support@micromint.com) can assist you with questions on specific functions.

	Since Linux implements virtual memory, there is no direct access to processor registers. One popular alternative to access processor registers in user space is to open a handle to /dev/mem and then use mmap() to map a virtual memory address to a physical memory address. These examples use this approach to access processor registers. The peripheral code is adapted from the [http://www.atmel.com/dyn/products/tools_card.asp?tool_id=4343 Atmel AT91 Softpack library].		Since Linux implements virtual memory, there is no direct access to processor registers. One popular alternative to access processor registers in user space is to open a handle to /dev/mem and then use mmap() to map a virtual memory address to a physical memory address. These examples use this approach to access processor registers. The peripheral code is adapted from the [http://www.atmel.com/dyn/products/tools_card.asp?tool_id=4343 Atmel AT91 Softpack library].

Support at 18:27, 2 March 2012

Support — Fri, 02 Mar 2012 18:27:49 GMT

← Older revision		Revision as of 18:27, 2 March 2012
Line 1:		Line 1:
-	These code examples will help you get started with your user space applications on the Micromint Electrum. Our support staff (support@micromint.com) can assist you with questions on specific functions.	+	These code examples will help you get started with your user space applications on the Micromint Electrum. A zip file of the examples can be downloaded from the Software Update section of the [http://wiki.micromint.com/index.php/Electrum_Documentation Electrum Documentation Wiki]. Our support staff (support@micromint.com) can assist you with questions on specific functions.

	Since Linux implements virtual memory, there is no direct access to processor registers. One popular alternative to access processor registers in user space is to open a handle to /dev/mem and then use mmap() to map a virtual memory address to a physical memory address. These examples use this approach to access processor registers. The peripheral code is adapted from the [http://www.atmel.com/dyn/products/tools_card.asp?tool_id=4343 Atmel AT91 Softpack library].		Since Linux implements virtual memory, there is no direct access to processor registers. One popular alternative to access processor registers in user space is to open a handle to /dev/mem and then use mmap() to map a virtual memory address to a physical memory address. These examples use this approach to access processor registers. The peripheral code is adapted from the [http://www.atmel.com/dyn/products/tools_card.asp?tool_id=4343 Atmel AT91 Softpack library].

Support at 14:56, 27 January 2011

Support — Thu, 27 Jan 2011 14:56:06 GMT

← Older revision		Revision as of 14:56, 27 January 2011
Line 26:		Line 26:
	\|[[Electrum button Example\|button]]		\|[[Electrum button Example\|button]]
	\|Uses button to set LED		\|Uses button to set LED
-	~~\|align="center" \| [[Image:checkmark.gif]]~~
-	\|-
-	~~\|[[Electrum dac_spi Example\|dac_spi]]~~
-	~~\|Test SPI DACs (requires I/O option)~~
	\|align="center" \| [[Image:checkmark.gif]]		\|align="center" \| [[Image:checkmark.gif]]
	\|-		\|-
Line 42:		Line 38:
	\|[[Electrum minibasic Example\|minibasic]]		\|[[Electrum minibasic Example\|minibasic]]
	\|Simple BASIC interpreter		\|Simple BASIC interpreter
		+	\|align="center" \| [[Image:checkmark.gif]]
		+	\|-
		+	\|[[Electrum spi_adc Example\|spi_adc]]
		+	\|Test SPI ADCs (requires I/O option)
		+	\|align="center" \| [[Image:checkmark.gif]]
		+	\|-
		+	\|[[Electrum spi_dac Example\|spi_dac]]
		+	\|Test SPI DACs (requires I/O option)
	\|align="center" \| [[Image:checkmark.gif]]		\|align="center" \| [[Image:checkmark.gif]]
	\|}		\|}

	Interrupt handlers and other applications that require full control of timing or preemption should implement device drivers or modules in kernel space. The [[ARM9_Books\|Linux Device Drivers (LDD) book]] covers most concepts required for device driver development. Note that a [[ARM9 Books\|free online version of the LDD book]] is available. The [[Electrum_Documentation#Software_Updates\|kernel source code]] also contains device drivers for Atmel processors.		Interrupt handlers and other applications that require full control of timing or preemption should implement device drivers or modules in kernel space. The [[ARM9_Books\|Linux Device Drivers (LDD) book]] covers most concepts required for device driver development. Note that a [[ARM9 Books\|free online version of the LDD book]] is available. The [[Electrum_Documentation#Software_Updates\|kernel source code]] also contains device drivers for Atmel processors.

Support at 18:08, 5 January 2011

Support — Wed, 05 Jan 2011 18:08:54 GMT

← Older revision		Revision as of 18:08, 5 January 2011
Line 3:		Line 3:
	Since Linux implements virtual memory, there is no direct access to processor registers. One popular alternative to access processor registers in user space is to open a handle to /dev/mem and then use mmap() to map a virtual memory address to a physical memory address. These examples use this approach to access processor registers. The peripheral code is adapted from the [http://www.atmel.com/dyn/products/tools_card.asp?tool_id=4343 Atmel AT91 Softpack library].		Since Linux implements virtual memory, there is no direct access to processor registers. One popular alternative to access processor registers in user space is to open a handle to /dev/mem and then use mmap() to map a virtual memory address to a physical memory address. These examples use this approach to access processor registers. The peripheral code is adapted from the [http://www.atmel.com/dyn/products/tools_card.asp?tool_id=4343 Atmel AT91 Softpack library].

-	The default compiler is the EmDebian cross-compiler. For details on the toolchain installation, please refer to the [[Electrum-100_Manual/2#Toolchain_installation\|manual]. You can choose another compiler by specifying a COMPILER variable in the Makefile.	+	The default compiler is the EmDebian cross-compiler. For details on the toolchain installation, please refer to the [[Electrum-100_Manual/2#Toolchain_installation\|manual]]. You can choose another compiler by specifying a COMPILER variable in the Makefile.

	# On-board gcc COMPILER=gcc		# On-board gcc COMPILER=gcc

Support at 18:08, 5 January 2011

Support — Wed, 05 Jan 2011 18:08:38 GMT

← Older revision		Revision as of 18:08, 5 January 2011
Line 3:		Line 3:
	Since Linux implements virtual memory, there is no direct access to processor registers. One popular alternative to access processor registers in user space is to open a handle to /dev/mem and then use mmap() to map a virtual memory address to a physical memory address. These examples use this approach to access processor registers. The peripheral code is adapted from the [http://www.atmel.com/dyn/products/tools_card.asp?tool_id=4343 Atmel AT91 Softpack library].		Since Linux implements virtual memory, there is no direct access to processor registers. One popular alternative to access processor registers in user space is to open a handle to /dev/mem and then use mmap() to map a virtual memory address to a physical memory address. These examples use this approach to access processor registers. The peripheral code is adapted from the [http://www.atmel.com/dyn/products/tools_card.asp?tool_id=4343 Atmel AT91 Softpack library].

-	The default compiler is the EmDebian cross-compiler. To choose another	+	The default compiler is the EmDebian cross-compiler. For details on the toolchain installation, please refer to the [[Electrum-100_Manual/2#Toolchain_installation\|manual]. You can choose another compiler by specifying a COMPILER variable in the Makefile.
-	compiler ~~set the~~ COMPILER variable on the Makefile.	+

	# On-board gcc COMPILER=gcc		# On-board gcc COMPILER=gcc

Support at 19:59, 4 January 2011

Support — Tue, 04 Jan 2011 19:59:04 GMT

← Older revision		Revision as of 19:59, 4 January 2011
Line 46:		Line 46:
	\|}		\|}

-	Interrupt handlers and other applications that require full control of timing or preemption should implement device drivers or modules in kernel space. The [[ARM9_Books\|Linux Device Drivers (LDD) book]] covers most concepts required for device driver development. Note that a [~~http://lwn.net/Kernel/LDD3/~~ free online version of the LDD book] is available. The [[Electrum_Documentation#Software_Updates\|kernel source code]] also contains device drivers for Atmel processors.	+	Interrupt handlers and other applications that require full control of timing or preemption should implement device drivers or modules in kernel space. The [[ARM9_Books\|Linux Device Drivers (LDD) book]] covers most concepts required for device driver development. Note that a [[ARM9 Books\|free online version of the LDD book]] is available. The [[Electrum_Documentation#Software_Updates\|kernel source code]] also contains device drivers for Atmel processors.

Support at 18:07, 4 January 2011

Support — Tue, 04 Jan 2011 18:07:58 GMT

← Older revision		Revision as of 18:07, 4 January 2011
Line 46:		Line 46:
	\|}		\|}

-	Interrupt handlers and other applications that require full control of timing or preemption should implement device drivers or modules in kernel space. The [[ARM9_Books] Linux Device Drivers (LDD) book] covers most concepts required for device driver development. Note that a [http://lwn.net/Kernel/LDD3/ free online version of the LDD book] is available. The [[Electrum_Documentation#Software_Updates] kernel source code] also contains device drivers for Atmel processors.	+	Interrupt handlers and other applications that require full control of timing or preemption should implement device drivers or modules in kernel space. The [[ARM9_Books\|Linux Device Drivers (LDD) book]] covers most concepts required for device driver development. Note that a [http://lwn.net/Kernel/LDD3/ free online version of the LDD book] is available. The [[Electrum_Documentation#Software_Updates\|kernel source code]] also contains device drivers for Atmel processors.

Support at 18:07, 4 January 2011

Support — Tue, 04 Jan 2011 18:07:06 GMT

← Older revision		Revision as of 18:07, 4 January 2011
Line 46:		Line 46:
	\|}		\|}

-	Interrupt handlers and other applications that require full control of timing or preemption should implement device drivers or modules in kernel space. The [ARM9_Books Linux Device Drivers (LDD) book] covers most concepts required for device driver development. Note that a [http://lwn.net/Kernel/LDD3/ free online version of the LDD book] is available. The [Electrum_Documentation#Software_Updates kernel source code] also contains device drivers for Atmel processors.	+	Interrupt handlers and other applications that require full control of timing or preemption should implement device drivers or modules in kernel space. The [[ARM9_Books] Linux Device Drivers (LDD) book] covers most concepts required for device driver development. Note that a [http://lwn.net/Kernel/LDD3/ free online version of the LDD book] is available. The [[Electrum_Documentation#Software_Updates] kernel source code] also contains device drivers for Atmel processors.