<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>Comments on: Snickerdoodle Dev Board Boasts ARM Processor with Onboard FPGA</title>
	<atom:link href="http://www.epanorama.net/blog/2015/10/13/snickerdoodle-dev-board-boasts-arm-processor-with-onboard-fpga-make/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.epanorama.net/blog/2015/10/13/snickerdoodle-dev-board-boasts-arm-processor-with-onboard-fpga-make/</link>
	<description>All about electronics and circuit design</description>
	<lastBuildDate>Sun, 05 Apr 2026 10:02:57 +0000</lastBuildDate>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.9.14</generator>
	<item>
		<title>By: Tomi Engdahl</title>
		<link>https://www.epanorama.net/blog/2015/10/13/snickerdoodle-dev-board-boasts-arm-processor-with-onboard-fpga-make/comment-page-1/#comment-1542641</link>
		<dc:creator><![CDATA[Tomi Engdahl]]></dc:creator>
		<pubDate>Sat, 01 Apr 2017 10:21:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.epanorama.net/newepa/?p=34820#comment-1542641</guid>
		<description><![CDATA[https://www.open-electronics.org/chameleon96-the-first-fpga-enabled-and-armv7-96boards-entry/

Linaro’s open source 96Boards spec was adopted by Arrow for the Chameleon96, the first ARMv7 96Boards entry, and the first FPGA-enabled 96Boards SBC.

The SBC runs Debian Linux on a Cyclone V SE SoC from Intel PSG (Programmable Solutions Group), the new post-acquisition name for Intel’s Altera FPGA unit.
The Cyclone V combines dual 800MHz Cortex-A9 cores with a modest FPGA subsystem with 110K LE performance.]]></description>
		<content:encoded><![CDATA[<p><a href="https://www.open-electronics.org/chameleon96-the-first-fpga-enabled-and-armv7-96boards-entry/" rel="nofollow">https://www.open-electronics.org/chameleon96-the-first-fpga-enabled-and-armv7-96boards-entry/</a></p>
<p>Linaro’s open source 96Boards spec was adopted by Arrow for the Chameleon96, the first ARMv7 96Boards entry, and the first FPGA-enabled 96Boards SBC.</p>
<p>The SBC runs Debian Linux on a Cyclone V SE SoC from Intel PSG (Programmable Solutions Group), the new post-acquisition name for Intel’s Altera FPGA unit.<br />
The Cyclone V combines dual 800MHz Cortex-A9 cores with a modest FPGA subsystem with 110K LE performance.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomi Engdahl</title>
		<link>https://www.epanorama.net/blog/2015/10/13/snickerdoodle-dev-board-boasts-arm-processor-with-onboard-fpga-make/comment-page-1/#comment-1521190</link>
		<dc:creator><![CDATA[Tomi Engdahl]]></dc:creator>
		<pubDate>Fri, 28 Oct 2016 11:29:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.epanorama.net/newepa/?p=34820#comment-1521190</guid>
		<description><![CDATA[Embedded FPGAs Going Mainstream?
http://semiengineering.com/will-efpgas-go-mainstream/

Programmable devices are being adopted in more market segments, but they still haven’t been included in major SoCs. That could change.

Systems on chip have been made with many processing variants ranging from general-purpose CPUs to DSPs, GPUs, and custom processors that are highly optimized for certain tasks. When none of these options provide the necessary performance or consumes too much power, custom hardware takes over. But there is one type of processing element that has rarely been used in a major SoC— the FPGA.

Solutions implemented in FPGAs are often faster than any of the instruction-set processors, and in most cases they complete a computation with lower total energy consumption. However, their overall power consumption is higher, and performance is slower than custom hardware. In addition, they use a lot more silicon area because the FPGA is a fixed resource, so enough of it must be put onto a chip for what is believed to be the worst-case usage scenario.

The standalone FPGA market currently is dominated by two companies, Xilinx and Altera (Intel). Part of the reason for this is they do not just produce chips. FPGAs require a complex ecosystem to make them useable. This ecosystem is very similar to those required for supporting processors. The transformation from FPGA to eFPGA adds even more complexity to this ecosystem because it requires a customized toolchain for each IP core that is licensed.]]></description>
		<content:encoded><![CDATA[<p>Embedded FPGAs Going Mainstream?<br />
<a href="http://semiengineering.com/will-efpgas-go-mainstream/" rel="nofollow">http://semiengineering.com/will-efpgas-go-mainstream/</a></p>
<p>Programmable devices are being adopted in more market segments, but they still haven’t been included in major SoCs. That could change.</p>
<p>Systems on chip have been made with many processing variants ranging from general-purpose CPUs to DSPs, GPUs, and custom processors that are highly optimized for certain tasks. When none of these options provide the necessary performance or consumes too much power, custom hardware takes over. But there is one type of processing element that has rarely been used in a major SoC— the FPGA.</p>
<p>Solutions implemented in FPGAs are often faster than any of the instruction-set processors, and in most cases they complete a computation with lower total energy consumption. However, their overall power consumption is higher, and performance is slower than custom hardware. In addition, they use a lot more silicon area because the FPGA is a fixed resource, so enough of it must be put onto a chip for what is believed to be the worst-case usage scenario.</p>
<p>The standalone FPGA market currently is dominated by two companies, Xilinx and Altera (Intel). Part of the reason for this is they do not just produce chips. FPGAs require a complex ecosystem to make them useable. This ecosystem is very similar to those required for supporting processors. The transformation from FPGA to eFPGA adds even more complexity to this ecosystem because it requires a customized toolchain for each IP core that is licensed.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
