Supported Processors - Revision history

Chris at 20:50, 11 November 2013

2013-11-11T20:50:25Z

← Older revision		Revision as of 20:50, 11 November 2013
Line 2:		Line 2:

	[[image:chip.jpg\|right]]		[[image:chip.jpg\|right]]
	The Xtensa processor architecture is a configurable, extensible~~, and~~ synthesizable 32-bit RISC processor core. SoC and processor designers can select from a variety of options, such as instruction-set extensions, memory, cache, and interrupt configurations. Moreover, Xtensa processors ~~can be extended with~~ custom-defined instructions and registers, ~~as well as custom port and queue interfaces. All~~ Xtensa processors share a common base instruction set architecture, thereby ensuring compatibility of third party application software and development tools.		The Xtensa processor architecture is a configurable and extensible synthesizable 32-bit RISC processor core. SoC and processor designers can select from a variety of options, such as instruction-set extensions (for example, narrow instructions, floating point instructions, etc.), memory, cache, and interrupt configurations. Moreover, Xtensa processors also support custom-defined instructions and registers. Nevertheless, all Xtensa processors share a common base instruction set architecture, thereby ensuring compatibility of third party application software and development tools.

	Tensilica’s Diamond Standard Series processor family consists of a number of ready-to-use synthesizable cores and is based on the Xtensa processor architecture. The Diamond Standard 233L processor, for example, contains an MMU and fully supports running Linux.		Tensilica’s Diamond Standard Series processor family consists of a number of ready-to-use synthesizable cores and is based on the Xtensa processor architecture. The Diamond Standard 233L processor, for example, contains an MMU and fully supports running Linux.
Line 8:		Line 8:
	== Automatic Support for Custom Xtensa Cores ==		== Automatic Support for Custom Xtensa Cores ==

	Despite the endless possibilities provided by the configurability and extensibility of the Xtensa architecture, ~~obtaining~~ an open source toolchain and kernel that fully support a specific configured Xtensa ~~core~~ is a straightforward ~~matter~~. ~~The process is mostly automated (scripted), avoiding any need~~ to ~~manually port~~ the ~~kernel to a new processor variant as is typical for a fixed processor architecture. Modifications to~~ toolchain and kernel sources are ~~limited to a small set of configuration files,~~ typically provided by Tensilica in the form of an ''overlay'' ~~to be copied into the sources~~. ~~The development tools and kernel are subsequently configured and built as usual.~~ (~~Of course, you still have~~ to port ~~Linux~~ to ~~your particular board or platform~~.)		Despite the endless possibilities provided by the configurability and extensibility of the Xtensa architecture, generating an open source toolchain and kernel that fully support a specific configured Xtensa processor is straightforward. It only requires to update a small set of files inside the toolchain and kernel sources before the actual build process. All necessary files are typically provided by the processor vendor or directly from Tensilica in the form of a single ''overlay'' file. This mostly automated process (scripted) avoids having to ''manually'' port the kernel to a new processor variant, which would be typical for a fixed processor architecture.

	~~== Kernel and Processor Configuration ==~~		Note that a ''processor configuration'' is also often referred to as a ''core variant'' in Linux. The following list shows processor configurations already included in the kernel:

	Because the kernel is much closer to the hardware and provides an abstraction for many architectural options, it needs to be configured and compiled for a particular platform and processor configuration. It also requires development tools configured for the particular processor. Note that a ''processor configuration'' is also often referred to as a ''core variant'' in Linux. The following list shows processor configurations already included in the kernel~~, but adding a new configuration is a very simple and straight forward process.~~

	* Diamond 232L		* Diamond 232L

Chris: /* Automatic Support for Custom Xtensa Cores */

2013-11-11T18:49:16Z

Automatic Support for Custom Xtensa Cores

← Older revision		Revision as of 18:49, 11 November 2013
Line 9:		Line 9:

	Despite the endless possibilities provided by the configurability and extensibility of the Xtensa architecture, obtaining an open source toolchain and kernel that fully support a specific configured Xtensa core is a straightforward matter. The process is mostly automated (scripted), avoiding any need to manually port the kernel to a new processor variant as is typical for a fixed processor architecture. Modifications to toolchain and kernel sources are limited to a small set of configuration files, typically provided by Tensilica in the form of an ''overlay'' to be copied into the sources. The development tools and kernel are subsequently configured and built as usual. (Of course, you still have to port Linux to your particular board or platform.)		Despite the endless possibilities provided by the configurability and extensibility of the Xtensa architecture, obtaining an open source toolchain and kernel that fully support a specific configured Xtensa core is a straightforward matter. The process is mostly automated (scripted), avoiding any need to manually port the kernel to a new processor variant as is typical for a fixed processor architecture. Modifications to toolchain and kernel sources are limited to a small set of configuration files, typically provided by Tensilica in the form of an ''overlay'' to be copied into the sources. The development tools and kernel are subsequently configured and built as usual. (Of course, you still have to port Linux to your particular board or platform.)

	In the Linux kernel for example, all configuration files are located inside the Xtensa include directory in the kernel sources (<code>arch/xtensa/variant/''config''/include/variant/</code>). Adding support to the kernel for a custom configured Xtensa processor generally involves copying the appropriate configuration files into the appropriate variant directory.

	== Kernel and Processor Configuration ==		== Kernel and Processor Configuration ==

Chris at 23:51, 18 March 2013

2013-03-18T23:51:28Z

← Older revision		Revision as of 23:51, 18 March 2013
Line 14:		Line 14:
	== Kernel and Processor Configuration ==		== Kernel and Processor Configuration ==

	Because the kernel is much closer to the hardware and provides an abstraction for many architectural options, it needs to be configured and compiled for a particular platform and processor configuration. It also requires development tools configured for the particular processor. Note that a ''processor configuration'' is also often referred to as a ''core variant'' in Linux. The following list shows processor configurations included in the kernel.		Because the kernel is much closer to the hardware and provides an abstraction for many architectural options, it needs to be configured and compiled for a particular platform and processor configuration. It also requires development tools configured for the particular processor. Note that a ''processor configuration'' is also often referred to as a ''core variant'' in Linux. The following list shows processor configurations already included in the kernel, but adding a new configuration is a very simple and straight forward process.

	* Diamond 232L		* Diamond 232L
	* Diamond 233L		* Diamond 233L
	* Stretch S6000 (without MMU)		* Stretch S6000 (without MMU)
	* 'FSF' default configuration (only for tool verification)		* 'FSF' default configuration (only for tool verification)

Chris at 23:50, 18 March 2013

2013-03-18T23:50:27Z

← Older revision		Revision as of 23:50, 18 March 2013
Line 5:		Line 5:

	Tensilica’s Diamond Standard Series processor family consists of a number of ready-to-use synthesizable cores and is based on the Xtensa processor architecture. The Diamond Standard 233L processor, for example, contains an MMU and fully supports running Linux.		Tensilica’s Diamond Standard Series processor family consists of a number of ready-to-use synthesizable cores and is based on the Xtensa processor architecture. The Diamond Standard 233L processor, for example, contains an MMU and fully supports running Linux.

	~~[[Supported Processor Configurations]] provides additional information when defining a new '''custom''' Xtensa processor.~~

	== Automatic Support for Custom Xtensa Cores ==		== Automatic Support for Custom Xtensa Cores ==

Chris at 23:48, 18 March 2013

2013-03-18T23:48:56Z

← Older revision		Revision as of 23:48, 18 March 2013
Line 6:		Line 6:
	Tensilica’s Diamond Standard Series processor family consists of a number of ready-to-use synthesizable cores and is based on the Xtensa processor architecture. The Diamond Standard 233L processor, for example, contains an MMU and fully supports running Linux.		Tensilica’s Diamond Standard Series processor family consists of a number of ready-to-use synthesizable cores and is based on the Xtensa processor architecture. The Diamond Standard 233L processor, for example, contains an MMU and fully supports running Linux.

	[[Supported Processor Configurations]] provides additional information ~~about supported configuration options~~ when defining a new custom Xtensa processor.		[[Supported Processor Configurations]] provides additional information when defining a new '''custom''' Xtensa processor.

	== Automatic Support for Custom Xtensa Cores ==		== Automatic Support for Custom Xtensa Cores ==

Chris at 20:56, 17 March 2013

2013-03-17T20:56:11Z

← Older revision		Revision as of 20:56, 17 March 2013
Line 6:		Line 6:
	Tensilica’s Diamond Standard Series processor family consists of a number of ready-to-use synthesizable cores and is based on the Xtensa processor architecture. The Diamond Standard 233L processor, for example, contains an MMU and fully supports running Linux.		Tensilica’s Diamond Standard Series processor family consists of a number of ready-to-use synthesizable cores and is based on the Xtensa processor architecture. The Diamond Standard 233L processor, for example, contains an MMU and fully supports running Linux.

	~~Please make also sure to read~~ [[Supported Processor Configurations]] ~~for~~ additional information about supported options when defining a new custom Xtensa processor.		[[Supported Processor Configurations]] provides additional information about supported configuration options when defining a new custom Xtensa processor.

	== Automatic Support for Custom Xtensa Cores ==		== Automatic Support for Custom Xtensa Cores ==

Chris at 01:51, 16 March 2013

2013-03-16T01:51:33Z

← Older revision		Revision as of 01:51, 16 March 2013
Line 7:		Line 7:

	Please make also sure to read [[Supported Processor Configurations]] for additional information about supported options when defining a new custom Xtensa processor.		Please make also sure to read [[Supported Processor Configurations]] for additional information about supported options when defining a new custom Xtensa processor.


	== Automatic Support for Custom Xtensa Cores ==		== Automatic Support for Custom Xtensa Cores ==

Chris at 18:07, 15 March 2013

2013-03-15T18:07:59Z

← Older revision		Revision as of 18:07, 15 March 2013
Line 4:		Line 4:
	The Xtensa processor architecture is a configurable, extensible, and synthesizable 32-bit RISC processor core. SoC and processor designers can select from a variety of options, such as instruction-set extensions, memory, cache, and interrupt configurations. Moreover, Xtensa processors can be extended with custom-defined instructions and registers, as well as custom port and queue interfaces. All Xtensa processors share a common base instruction set architecture, thereby ensuring compatibility of third party application software and development tools.		The Xtensa processor architecture is a configurable, extensible, and synthesizable 32-bit RISC processor core. SoC and processor designers can select from a variety of options, such as instruction-set extensions, memory, cache, and interrupt configurations. Moreover, Xtensa processors can be extended with custom-defined instructions and registers, as well as custom port and queue interfaces. All Xtensa processors share a common base instruction set architecture, thereby ensuring compatibility of third party application software and development tools.

	Tensilica’s Diamond Standard Series processor family consists of a number of ready-to-use synthesizable cores and is based on the Xtensa processor architecture. The Diamond Standard 233L processor contains an MMU and fully supports running Linux.		Tensilica’s Diamond Standard Series processor family consists of a number of ready-to-use synthesizable cores and is based on the Xtensa processor architecture. The Diamond Standard 233L processor, for example, contains an MMU and fully supports running Linux.

			Please make also sure to read [[Supported Processor Configurations]] for additional information about supported options when defining a new custom Xtensa processor.


	== Automatic Support for Custom Xtensa Cores ==		== Automatic Support for Custom Xtensa Cores ==
Line 14:		Line 17:
	== Kernel and Processor Configuration ==		== Kernel and Processor Configuration ==

	Because the kernel is much closer to the hardware and provides an abstraction for many architectural options, it needs to be configured and compiled for a particular platform and processor configuration. It also requires development tools configured for the particular processor. Note that a ''processor configuration'' is also often referred to as a ''core variant''. The following list shows processor configurations included in the kernel.		Because the kernel is much closer to the hardware and provides an abstraction for many architectural options, it needs to be configured and compiled for a particular platform and processor configuration. It also requires development tools configured for the particular processor. Note that a ''processor configuration'' is also often referred to as a ''core variant'' in Linux. The following list shows processor configurations included in the kernel.
			* Diamond 232L
			* Diamond 233L
	~~{\| border=1 cellspacing=0 cellpadding=3~~		* Stretch S6000 (without MMU)
	~~\|+ Supported processors in the Linux kernel~~		* 'FSF' default configuration (only for tool verification)
	~~\|- style="background:#f8f8f8;"~~
	~~! Name !! Notes~~
	\|-
	~~\| Custom-configured Xtensa \|\|Vendor specific, requires overlay~~
	\|-
	\| Diamond 232L \|\|
	\|-
	\| Stretch S6000 ~~\|\| Without~~ MMU
	\|-
	\| 'FSF' ~~\|\| Default~~ configuration for verification ~~only~~
	\|}

Chris: /* Automatic Support for Custom Xtensa Cores */

2013-03-14T23:31:26Z

Automatic Support for Custom Xtensa Cores

← Older revision		Revision as of 23:31, 14 March 2013
Line 10:		Line 10:
	Despite the endless possibilities provided by the configurability and extensibility of the Xtensa architecture, obtaining an open source toolchain and kernel that fully support a specific configured Xtensa core is a straightforward matter. The process is mostly automated (scripted), avoiding any need to manually port the kernel to a new processor variant as is typical for a fixed processor architecture. Modifications to toolchain and kernel sources are limited to a small set of configuration files, typically provided by Tensilica in the form of an ''overlay'' to be copied into the sources. The development tools and kernel are subsequently configured and built as usual. (Of course, you still have to port Linux to your particular board or platform.)		Despite the endless possibilities provided by the configurability and extensibility of the Xtensa architecture, obtaining an open source toolchain and kernel that fully support a specific configured Xtensa core is a straightforward matter. The process is mostly automated (scripted), avoiding any need to manually port the kernel to a new processor variant as is typical for a fixed processor architecture. Modifications to toolchain and kernel sources are limited to a small set of configuration files, typically provided by Tensilica in the form of an ''overlay'' to be copied into the sources. The development tools and kernel are subsequently configured and built as usual. (Of course, you still have to port Linux to your particular board or platform.)

	In the Linux kernel for example, all configuration files are located inside the Xtensa include directory in the kernel sources (<code>arch/xtensa/variant/''config''/include/variant/</code>). Adding support to the kernel for a custom configured Xtensa processor generally involves copying the appropriate configuration files into the appropriate variant directory. See [[Buildroot_Build_Instructions#Install_any_required_processor_specific_overlay\|Buildroot Overlay Installation]] for an automated method of installing these files in both toolchain and kernel sources.		In the Linux kernel for example, all configuration files are located inside the Xtensa include directory in the kernel sources (<code>arch/xtensa/variant/''config''/include/variant/</code>). Adding support to the kernel for a custom configured Xtensa processor generally involves copying the appropriate configuration files into the appropriate variant directory.

	== Kernel and Processor Configuration ==		== Kernel and Processor Configuration ==

Chris: /* Automatic Support for Custom Xtensa Cores */

2013-03-14T15:52:20Z

Automatic Support for Custom Xtensa Cores

← Older revision		Revision as of 15:52, 14 March 2013
Line 10:		Line 10:
	Despite the endless possibilities provided by the configurability and extensibility of the Xtensa architecture, obtaining an open source toolchain and kernel that fully support a specific configured Xtensa core is a straightforward matter. The process is mostly automated (scripted), avoiding any need to manually port the kernel to a new processor variant as is typical for a fixed processor architecture. Modifications to toolchain and kernel sources are limited to a small set of configuration files, typically provided by Tensilica in the form of an ''overlay'' to be copied into the sources. The development tools and kernel are subsequently configured and built as usual. (Of course, you still have to port Linux to your particular board or platform.)		Despite the endless possibilities provided by the configurability and extensibility of the Xtensa architecture, obtaining an open source toolchain and kernel that fully support a specific configured Xtensa core is a straightforward matter. The process is mostly automated (scripted), avoiding any need to manually port the kernel to a new processor variant as is typical for a fixed processor architecture. Modifications to toolchain and kernel sources are limited to a small set of configuration files, typically provided by Tensilica in the form of an ''overlay'' to be copied into the sources. The development tools and kernel are subsequently configured and built as usual. (Of course, you still have to port Linux to your particular board or platform.)

	In the Linux kernel for example, all configuration files are located inside the Xtensa include directory in the kernel sources (<code>arch/xtensa~~/include~~/variant/''config''/include/variant/</code>). Adding support to the kernel for a custom configured Xtensa processor generally involves copying the appropriate configuration files into the appropriate variant directory.		In the Linux kernel for example, all configuration files are located inside the Xtensa include directory in the kernel sources (<code>arch/xtensa/variant/''config''/include/variant/</code>). Adding support to the kernel for a custom configured Xtensa processor generally involves copying the appropriate configuration files into the appropriate variant directory. See [[Buildroot_Build_Instructions#Install_any_required_processor_specific_overlay\|Buildroot Overlay Installation]] for an automated method of installing these files in both toolchain and kernel sources.

	See [[Buildroot_Build_Instructions#Install_any_required_processor_specific_overlay\|Buildroot Overlay Installation]] for an automated method of installing these files in both toolchain and kernel sources.

	== Kernel and Processor Configuration ==		== Kernel and Processor Configuration ==