<?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: Open source logic analyzer clients</title>
	<atom:link href="http://dangerousprototypes.com/2009/09/28/open-source-logic-analyzer-clients/feed/" rel="self" type="application/rss+xml" />
	<link>http://dangerousprototypes.com/2009/09/28/open-source-logic-analyzer-clients/</link>
	<description>A new open source hardware project every month</description>
	<lastBuildDate>Mon, 22 Mar 2010 02:33:47 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ian</title>
		<link>http://dangerousprototypes.com/2009/09/28/open-source-logic-analyzer-clients/#comment-215</link>
		<dc:creator>Ian</dc:creator>
		<pubDate>Wed, 18 Nov 2009 10:34:41 +0000</pubDate>
		<guid isPermaLink="false">http://dangerousprototypes.com/?p=1396#comment-215</guid>
		<description>Here&#039;s my continued thoughts on a design after looking at datasheets:
http://whereisian.com/forum/index.php?topic=156.0</description>
		<content:encoded><![CDATA[<p>Here&#8217;s my continued thoughts on a design after looking at datasheets:<br />
<a href="http://whereisian.com/forum/index.php?topic=156.0" rel="nofollow">http://whereisian.com/forum/index.php?topic=156.0</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luke Skaff</title>
		<link>http://dangerousprototypes.com/2009/09/28/open-source-logic-analyzer-clients/#comment-214</link>
		<dc:creator>Luke Skaff</dc:creator>
		<pubDate>Tue, 17 Nov 2009 20:09:34 +0000</pubDate>
		<guid isPermaLink="false">http://dangerousprototypes.com/?p=1396#comment-214</guid>
		<description>@Jack,

I obviously can&#039;t speak for others but I would be willing to pay extra to have full USB 2.0 speed with a FT2232H.  I think having the ability to stream data a few Mhz and lower to your PC would be worth the extra few dollars.</description>
		<content:encoded><![CDATA[<p>@Jack,</p>
<p>I obviously can&#8217;t speak for others but I would be willing to pay extra to have full USB 2.0 speed with a FT2232H.  I think having the ability to stream data a few Mhz and lower to your PC would be worth the extra few dollars.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian</title>
		<link>http://dangerousprototypes.com/2009/09/28/open-source-logic-analyzer-clients/#comment-213</link>
		<dc:creator>Ian</dc:creator>
		<pubDate>Tue, 17 Nov 2009 07:10:59 +0000</pubDate>
		<guid isPermaLink="false">http://dangerousprototypes.com/?p=1396#comment-213</guid>
		<description>I started a forum to continue this discussion, if there&#039;s interest:
http://whereisian.com/forum/index.php?board=23.0</description>
		<content:encoded><![CDATA[<p>I started a forum to continue this discussion, if there&#8217;s interest:<br />
<a href="http://whereisian.com/forum/index.php?board=23.0" rel="nofollow">http://whereisian.com/forum/index.php?board=23.0</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jack Gassett</title>
		<link>http://dangerousprototypes.com/2009/09/28/open-source-logic-analyzer-clients/#comment-212</link>
		<dc:creator>Jack Gassett</dc:creator>
		<pubDate>Mon, 16 Nov 2009 20:17:40 +0000</pubDate>
		<guid isPermaLink="false">http://dangerousprototypes.com/?p=1396#comment-212</guid>
		<description>You know, we might be able to pull off $30-40 sale price if we use linear regulators and eliminate the USB chip in favor of a max232 chip.

Jack.</description>
		<content:encoded><![CDATA[<p>You know, we might be able to pull off $30-40 sale price if we use linear regulators and eliminate the USB chip in favor of a max232 chip.</p>
<p>Jack.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jack Gassett</title>
		<link>http://dangerousprototypes.com/2009/09/28/open-source-logic-analyzer-clients/#comment-211</link>
		<dc:creator>Jack Gassett</dc:creator>
		<pubDate>Fri, 13 Nov 2009 20:09:44 +0000</pubDate>
		<guid isPermaLink="false">http://dangerousprototypes.com/?p=1396#comment-211</guid>
		<description>Hello,

I think we should try to make it as simple and cost effective as possible for the first revision. The Spartan 3E-250 has 216k of block ram which would give us 6K samples. For most purposes that is enough... We could easily drop in a Spartan 3E-500 which would give us 11k samples at 32 channels. We can also try to use distributed ram or only provide 16 channels if we really want to provide more samples. So for the first revision I would suggest we forgo the SRAM, SDRAM, or DRAM. I&#039;ve made designs with SDRAM and DRAM in the past with mixed results. I was never able to get DRAM to work properly with a double layer board. SDRAM is possible on a two layer board but I think we should save that for a later revision. I think most people will be very happy with 6K samples. I only mentioned SDRAM because I think that will be the key to making it function in realtime...

So if you guys agree to forgo the external memory then that leaves the question of providing a voltage buffer for the inputs. Do you feel it is important? The Spartan 3E can handle up to 3.3V by itself but will be damaged by anything higher. I have a buffer design in place already, http://www.gadgetfactory.net/gf/project/bpw5009-buffer/ based on the 16 bit M74LCX16245. This would allow voltages up to 7V and is 4.5ns and would require only two parts.

I&#039;m down for collaborating on this, but I&#039;m not sure we could accomplish a sale price of $30... The spartan 3e chip is $13 and the ftdi2232h is $4 or $5... The power supply will probably add $3-6. PCB will cost $2-4. These numbers are off the top of my head and might be off.

Jack.</description>
		<content:encoded><![CDATA[<p>Hello,</p>
<p>I think we should try to make it as simple and cost effective as possible for the first revision. The Spartan 3E-250 has 216k of block ram which would give us 6K samples. For most purposes that is enough&#8230; We could easily drop in a Spartan 3E-500 which would give us 11k samples at 32 channels. We can also try to use distributed ram or only provide 16 channels if we really want to provide more samples. So for the first revision I would suggest we forgo the SRAM, SDRAM, or DRAM. I&#8217;ve made designs with SDRAM and DRAM in the past with mixed results. I was never able to get DRAM to work properly with a double layer board. SDRAM is possible on a two layer board but I think we should save that for a later revision. I think most people will be very happy with 6K samples. I only mentioned SDRAM because I think that will be the key to making it function in realtime&#8230;</p>
<p>So if you guys agree to forgo the external memory then that leaves the question of providing a voltage buffer for the inputs. Do you feel it is important? The Spartan 3E can handle up to 3.3V by itself but will be damaged by anything higher. I have a buffer design in place already, <a href="http://www.gadgetfactory.net/gf/project/bpw5009-buffer/" rel="nofollow">http://www.gadgetfactory.net/gf/project/bpw5009-buffer/</a> based on the 16 bit M74LCX16245. This would allow voltages up to 7V and is 4.5ns and would require only two parts.</p>
<p>I&#8217;m down for collaborating on this, but I&#8217;m not sure we could accomplish a sale price of $30&#8230; The spartan 3e chip is $13 and the ftdi2232h is $4 or $5&#8230; The power supply will probably add $3-6. PCB will cost $2-4. These numbers are off the top of my head and might be off.</p>
<p>Jack.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luke Skaff</title>
		<link>http://dangerousprototypes.com/2009/09/28/open-source-logic-analyzer-clients/#comment-210</link>
		<dc:creator>Luke Skaff</dc:creator>
		<pubDate>Fri, 13 Nov 2009 17:56:02 +0000</pubDate>
		<guid isPermaLink="false">http://dangerousprototypes.com/?p=1396#comment-210</guid>
		<description>Yea, you are right, it would be best to just keep it simple on the first board.  If it is popular a version with external ram and greater memory depth could always be made after the proof of concept.

I designed a DRAM controller for a project in school but that was some time ago.  Opencores has a few memory controllers you can just drop into the design.  Also many of the FPGA/CPLD vendors offer free memory controllers you can integrate into your design, the learning curve is not bad but it is definitely time consuming.</description>
		<content:encoded><![CDATA[<p>Yea, you are right, it would be best to just keep it simple on the first board.  If it is popular a version with external ram and greater memory depth could always be made after the proof of concept.</p>
<p>I designed a DRAM controller for a project in school but that was some time ago.  Opencores has a few memory controllers you can just drop into the design.  Also many of the FPGA/CPLD vendors offer free memory controllers you can integrate into your design, the learning curve is not bad but it is definitely time consuming.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian</title>
		<link>http://dangerousprototypes.com/2009/09/28/open-source-logic-analyzer-clients/#comment-209</link>
		<dc:creator>Ian</dc:creator>
		<pubDate>Fri, 13 Nov 2009 16:28:59 +0000</pubDate>
		<guid isPermaLink="false">http://dangerousprototypes.com/?p=1396#comment-209</guid>
		<description>@ Luke - it sounds like you propose using the ram to store states taken from other pins in the FPGA or CPLD. That&#039;s way beyond my abilities, we&#039;d have to hear from Jack (unless you&#039;re volunteering). I know propagation delay is a factor.

DRAM is indeed cheaper, and I understand it&#039;s not difficult to implement a controller in FPGA or CPLD (I&#039;ve read a few nice app sheets). But again, way beyond what I can knock-up in a weekend on a 2-layer board.

There&#039;s sump host implementations for a bunch of different FPGA DEV boards. My existing plan was to find a good one with highly-available parts, strip it down, and make the cheapest, simplest 2-sided PCB I can. If it floats, and I can stand the dev tools (Xilinx 10.1 was a nightmare), then I&#039;d plan a version 2. My price goal was around $30, shipped, I worry more is on par with a &lt;a href=&quot;http://dangerousprototypes.com/2009/08/24/49-fpga-development-board/&quot; rel=&quot;nofollow&quot;&gt;full FPGA dev board&lt;/a&gt;.

If there&#039;s serious interest in collaboration, I&#039;ll start a new board in the &lt;a href=&quot;http://whereisian.com/forum/index.php&quot; rel=&quot;nofollow&quot;&gt;forum&lt;/a&gt; and we can start looking at parts.</description>
		<content:encoded><![CDATA[<p>@ Luke &#8211; it sounds like you propose using the ram to store states taken from other pins in the FPGA or CPLD. That&#8217;s way beyond my abilities, we&#8217;d have to hear from Jack (unless you&#8217;re volunteering). I know propagation delay is a factor.</p>
<p>DRAM is indeed cheaper, and I understand it&#8217;s not difficult to implement a controller in FPGA or CPLD (I&#8217;ve read a few nice app sheets). But again, way beyond what I can knock-up in a weekend on a 2-layer board.</p>
<p>There&#8217;s sump host implementations for a bunch of different FPGA DEV boards. My existing plan was to find a good one with highly-available parts, strip it down, and make the cheapest, simplest 2-sided PCB I can. If it floats, and I can stand the dev tools (Xilinx 10.1 was a nightmare), then I&#8217;d plan a version 2. My price goal was around $30, shipped, I worry more is on par with a <a href="http://dangerousprototypes.com/2009/08/24/49-fpga-development-board/" rel="nofollow">full FPGA dev board</a>.</p>
<p>If there&#8217;s serious interest in collaboration, I&#8217;ll start a new board in the <a href="http://whereisian.com/forum/index.php" rel="nofollow">forum</a> and we can start looking at parts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luke Skaff</title>
		<link>http://dangerousprototypes.com/2009/09/28/open-source-logic-analyzer-clients/#comment-208</link>
		<dc:creator>Luke Skaff</dc:creator>
		<pubDate>Fri, 13 Nov 2009 16:07:33 +0000</pubDate>
		<guid isPermaLink="false">http://dangerousprototypes.com/?p=1396#comment-208</guid>
		<description>You can put a small microcontroller inside a CPLD also, lattice has a free 8-bit micro core and many others offer free cores.  A CPLD or FPGA should work fine for this project.

No buffers are used to interface with SRAM, you wire the RAM directly to the FPGA\CPLD.  Sometimes series termination resistors are used to reduce ring.  SDRAM or DRAM could also be used.

The FPGA used in the butterfly only has 216k of dedicated block ram on the device.  It would be cheaper to use DRAM instead of SRAM but would need a much more complicated memory controller core on the FPGA, $2-3 for 16Meg: http://www.mouser.com/issi/

Lots of fun options to choose from, it seems it could be done for less then $75 sales price for hardware</description>
		<content:encoded><![CDATA[<p>You can put a small microcontroller inside a CPLD also, lattice has a free 8-bit micro core and many others offer free cores.  A CPLD or FPGA should work fine for this project.</p>
<p>No buffers are used to interface with SRAM, you wire the RAM directly to the FPGA\CPLD.  Sometimes series termination resistors are used to reduce ring.  SDRAM or DRAM could also be used.</p>
<p>The FPGA used in the butterfly only has 216k of dedicated block ram on the device.  It would be cheaper to use DRAM instead of SRAM but would need a much more complicated memory controller core on the FPGA, $2-3 for 16Meg: <a href="http://www.mouser.com/issi/" rel="nofollow">http://www.mouser.com/issi/</a></p>
<p>Lots of fun options to choose from, it seems it could be done for less then $75 sales price for hardware</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian</title>
		<link>http://dangerousprototypes.com/2009/09/28/open-source-logic-analyzer-clients/#comment-207</link>
		<dc:creator>Ian</dc:creator>
		<pubDate>Fri, 13 Nov 2009 08:38:17 +0000</pubDate>
		<guid isPermaLink="false">http://dangerousprototypes.com/?p=1396#comment-207</guid>
		<description>SRAM - How much SRAM can you put inside an FPGA? What&#039;s the benefit of an FPGA over a CPLD and tiny microcontroller in that arrangement?

As I recall from my previous journey into the world of SRAM, speeds go up to around 100MHz. They are 8,16,32 bits wide, and around 18 address lines for a 4Mbit (256K sample) chip.

Like: http://www.mouser.com/ProductDetail/Cypress-Semiconductor/CY7C1041D-10ZSXI/?qs=sGAEpiMZZMs6Aik9Fp479rPSFu914cdUmPOXn5OlesE%3d
9Mbit/166MHz: http://www.mouser.com/ProductDetail/Cypress-Semiconductor/CY7C1360C-166AXI/?qs=sGAEpiMZZMs6Aik9Fp479rPSFu914cdUuGgsK3ZVMt8%3d

If I were doing this on my own, here&#039;s the things that give me pause. But together we might prevail :)
That&#039;s a lot of pins to route, with the expectation of high-speed signaling.
Those are some expensive chips.
What kind of buffers are fast enough to interface the SRAM at 166Mhz? How much do they cost?
How much ram is enough? I&#039;m a fairly active prototyper and I never use more than 4K samples (the first screen of output) to debug issues. I have no idea what other use profiles require in terms of storage.</description>
		<content:encoded><![CDATA[<p>SRAM &#8211; How much SRAM can you put inside an FPGA? What&#8217;s the benefit of an FPGA over a CPLD and tiny microcontroller in that arrangement?</p>
<p>As I recall from my previous journey into the world of SRAM, speeds go up to around 100MHz. They are 8,16,32 bits wide, and around 18 address lines for a 4Mbit (256K sample) chip.</p>
<p>Like: <a href="http://www.mouser.com/ProductDetail/Cypress-Semiconductor/CY7C1041D-10ZSXI/?qs=sGAEpiMZZMs6Aik9Fp479rPSFu914cdUmPOXn5OlesE%3d" rel="nofollow">http://www.mouser.com/ProductDetail/Cypress-Semiconductor/CY7C1041D-10ZSXI/?qs=sGAEpiMZZMs6Aik9Fp479rPSFu914cdUmPOXn5OlesE%3d</a><br />
9Mbit/166MHz: <a href="http://www.mouser.com/ProductDetail/Cypress-Semiconductor/CY7C1360C-166AXI/?qs=sGAEpiMZZMs6Aik9Fp479rPSFu914cdUuGgsK3ZVMt8%3d" rel="nofollow">http://www.mouser.com/ProductDetail/Cypress-Semiconductor/CY7C1360C-166AXI/?qs=sGAEpiMZZMs6Aik9Fp479rPSFu914cdUuGgsK3ZVMt8%3d</a></p>
<p>If I were doing this on my own, here&#8217;s the things that give me pause. But together we might prevail :)<br />
That&#8217;s a lot of pins to route, with the expectation of high-speed signaling.<br />
Those are some expensive chips.<br />
What kind of buffers are fast enough to interface the SRAM at 166Mhz? How much do they cost?<br />
How much ram is enough? I&#8217;m a fairly active prototyper and I never use more than 4K samples (the first screen of output) to debug issues. I have no idea what other use profiles require in terms of storage.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian</title>
		<link>http://dangerousprototypes.com/2009/09/28/open-source-logic-analyzer-clients/#comment-206</link>
		<dc:creator>Ian</dc:creator>
		<pubDate>Fri, 13 Nov 2009 08:18:59 +0000</pubDate>
		<guid isPermaLink="false">http://dangerousprototypes.com/?p=1396#comment-206</guid>
		<description>Sorry, I pulled those numbers out of thin air. I&#039;ve used the 74-573, it&#039;s octal,, this one to be exact:
http://www.mouser.com/Search/ProductDetail.aspx?R=74LVT573WMvirtualkey51210000virtualkey512-74LVT573WM

Here&#039;s my previous dev board for the LA (using the 573): http://hackaday.com/2008/12/11/how-to-programmable-logic-devices-cpld/</description>
		<content:encoded><![CDATA[<p>Sorry, I pulled those numbers out of thin air. I&#8217;ve used the 74-573, it&#8217;s octal,, this one to be exact:<br />
<a href="http://www.mouser.com/Search/ProductDetail.aspx?R=74LVT573WMvirtualkey51210000virtualkey512-74LVT573WM" rel="nofollow">http://www.mouser.com/Search/ProductDetail.aspx?R=74LVT573WMvirtualkey51210000virtualkey512-74LVT573WM</a></p>
<p>Here&#8217;s my previous dev board for the LA (using the 573): <a href="http://hackaday.com/2008/12/11/how-to-programmable-logic-devices-cpld/" rel="nofollow">http://hackaday.com/2008/12/11/how-to-programmable-logic-devices-cpld/</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
