<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Ramtron Automotive System Design Blog &#187; Design</title>
	<atom:link href="http://ramtronblogs.com/auto/tag/design/feed/" rel="self" type="application/rss+xml" />
	<link>http://ramtronblogs.com/auto</link>
	<description>Enhancing automotive system designs with F-RAM memory</description>
	<lastBuildDate>Thu, 07 Oct 2010 21:12:53 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
		<item>
		<title>Dealing with one small bottleneck</title>
		<link>http://ramtronblogs.com/auto/2010/01/dealing-with-one-small-bottleneck/</link>
		<comments>http://ramtronblogs.com/auto/2010/01/dealing-with-one-small-bottleneck/#comments</comments>
		<pubDate>Tue, 05 Jan 2010 08:34:08 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[F-RAM Design Hints]]></category>
		<category><![CDATA[Design]]></category>

		<guid isPermaLink="false">http://ramtronblogs.com/auto/?p=115</guid>
		<description><![CDATA[One subject that will probably never make the front page of newspapers is the speed of automotive grade nonvolatile memory. The sentence alone is enough to compel 99.9% of the world’s population to choose to watch paint dry rather than read on. However, for those of us working in automotive electronics that strive for faster, [...]]]></description>
			<content:encoded><![CDATA[<p style="text-align: center;">
<div id="attachment_130" class="wp-caption aligncenter" style="width: 235px"><img class="size-medium wp-image-130" style="border: 1px solid black;" title="64Kb Grade-1 F-RAM" src="http://ramtronblogs.com/auto/wp-content/uploads/2010/01/64K-F-RAM-225x180.jpg" alt="64Kb Grade-1 F-RAM" width="225" height="180" /><p class="wp-caption-text">64Kb Grade-1 F-RAM</p></div>
<p>One subject that will probably never make the front page of newspapers is the speed of automotive grade nonvolatile memory. The sentence alone is enough to compel 99.9% of the world’s population to choose to watch paint dry rather than read on. However, for those of us working in automotive electronics that strive for faster, cheaper, and better designs, the speed of nonvolatile memory becomes a serious concern worthy of attention.</p>
<p>Nonvolatile memory for automotive applications is usually an SPI device running at a bus speed of 1- to 5-MHz. So why does an automotive memory run slower than an SPI memory in the industrial world, especially when you consider that the typical automotive grade memory is made from the same silicon as an industrial device? In a nutshell, it comes down to higher operating temperature. Operating temperature effects both speed and power consumption. Since the two effects are related, higher temperatures slow down the operating speed of silicon and increase the current consumption. The end results are slower speed and higher current consumption specifications than a comparable industrial device. We’ll talk about the increased current another time so let’s just focus on the slower operating speed of nonvolatile memory in automotive applications for now.</p>
<p>I have recently come across a couple of instances where my customers needed more speed from their nonvolatile memory. One design had an array of devices on an SPI bus. Unfortunately, due to the slowness of the nonvolatile memory, the speed of the SPI bus needed to be reduced for nonvolatile memory reads and writes and then switched back to a higher speed for all other peripherals. The time needed to switch speeds made the whole design dillema worse. The design would be much easier if the nonvolatile memory was as fast the rest of the parts on the SPI bus, like an F-RAM for example.</p>
<p>Another design had a control algorithm that needed to execute in one millisecond to achieve stable control. Another  requirement was the need to store data in nonvolatile memory on each pass trough the control algorithm. EEPROM was not up to the task since it is not able to deliver writes in under one millisecond. F-RAM, on the other hand, is capable of writing as fast as the SPI bus can deliver data, making it an ideal solution for the design.</p>
<p>Simply, F-RAM reads and writes at the full SPI bus speed of 16MHz (for the 64K Grade 1 part) allowing engineers to make a small step towards their holy grail – faster, cheaper, better designs.</p>
]]></content:encoded>
			<wfw:commentRss>http://ramtronblogs.com/auto/2010/01/dealing-with-one-small-bottleneck/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What does every security system need? A switch.</title>
		<link>http://ramtronblogs.com/auto/2009/12/what-does-every-security-system-need-a-switch/</link>
		<comments>http://ramtronblogs.com/auto/2009/12/what-does-every-security-system-need-a-switch/#comments</comments>
		<pubDate>Tue, 08 Dec 2009 18:22:52 +0000</pubDate>
		<dc:creator>Duncan Bennett</dc:creator>
				<category><![CDATA[F-RAM Design Hints]]></category>
		<category><![CDATA[Design]]></category>
		<category><![CDATA[Products]]></category>
		<category><![CDATA[State Savers]]></category>

		<guid isPermaLink="false">http://ramtronblogs.com/auto/?p=86</guid>
		<description><![CDATA[Sounds obvious but every security system needs a switch. Somewhere, at the output of the security system will be a switch that either turns the alarm on or turns some component off, disabling whatever it is that the security system is protecting. In a home alarm, the security system turns on the bell-box (the thing [...]]]></description>
			<content:encoded><![CDATA[<div id="attachment_106" class="wp-caption aligncenter" style="width: 235px"><a  href="http://ramtronblogs.com/auto/wp-content/uploads/2009/12/SSDiagram_Switch_noCaption1.jpg" class="thickbox no_icon" rel="gallery-86" title="F-RAM State Saver driving a relay"><img class="size-medium wp-image-106  " style="border: black 1px solid;" title="F-RAM State Saver driving a relay" src="http://ramtronblogs.com/auto/wp-content/uploads/2009/12/SSDiagram_Switch_noCaption1-225x128.jpg" alt="F-RAM State Saver driving a relay" width="225" height="128" /></a><p class="wp-caption-text">F-RAM State Saver driving a relay</p></div>
<p>Sounds obvious but every security system needs a switch. Somewhere, at the output of the security system will be a switch that either turns the alarm on or turns some component off, disabling whatever it is that the security system is protecting. In a home alarm, the security system turns on the bell-box (the thing that makes a loud noise and flashes), and in an automotive security system, the ignition system is usually disabled in some way.</p>
<p>Now, as every good thief will tell you, if you cut the power to the security system and silence it soon after it starts to make a noise, then everyone will ignore it. Home security systems get round this obvious attack by having a backup battery in the bell-box and mounting it out of reach. Achieving the same in an automotive security system takes a little ingenuity. Autos usually only have one battery and everyone knows how to access it. If you are not familiar with this process just google it before you set out to steal cars.</p>
<p>One solution is to have a switch that remembers its previous state. That way once the alarm is triggered, cycling of the power supply will have no effect. Ramtron&#8217;s State Savers offer a simple, cheap electronic switch that remembers its previous state after a power cycle, which is ideal for security systems. You can learn more about our State Savers <a  href="http://www.ramtron.com/products/nonvolatile-state-saver/" target="_blank">here</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://ramtronblogs.com/auto/2009/12/what-does-every-security-system-need-a-switch/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>EEPROM can be a right and royal pain</title>
		<link>http://ramtronblogs.com/auto/2009/12/eeprom-can-be-a-right-and-royal-pain/</link>
		<comments>http://ramtronblogs.com/auto/2009/12/eeprom-can-be-a-right-and-royal-pain/#comments</comments>
		<pubDate>Tue, 08 Dec 2009 17:10:15 +0000</pubDate>
		<dc:creator>Duncan Bennett</dc:creator>
				<category><![CDATA[F-RAM Design Hints]]></category>
		<category><![CDATA[Design]]></category>

		<guid isPermaLink="false">http://ramtronblogs.com/auto/?p=90</guid>
		<description><![CDATA[The circuit shown above is the memory sub-system that you would need to store data on power fail. The key components are a microcontroller for processing, an EEPROM for nonvolatile data storage, and a capacitor to provide enough power to give the micro enough time to finish writing as the power fails. Above is an [...]]]></description>
			<content:encoded><![CDATA[<div id="attachment_91" class="wp-caption aligncenter" style="width: 326px"><img class="size-full wp-image-91 " style="border: black 1px solid;" title="EEPROM+Cap" src="http://ramtronblogs.com/auto/wp-content/uploads/2009/12/EEPROM+Cap.JPG" alt="EEPROM with Micro and Capacitor" width="316" height="161" /><p class="wp-caption-text">EEPROM with Micro and Capacitor</p></div>
<p>The circuit shown above is the memory sub-system that you would need to store data on power fail. The key components are a microcontroller for processing, an EEPROM for nonvolatile data storage, and a capacitor to provide enough power to give the micro enough time to finish writing as the power fails.</p>
<div id="attachment_92" class="wp-caption aligncenter" style="width: 283px"><img class="size-full wp-image-92 " style="border: black 1px solid;" title="F-RAM+Micro" src="http://ramtronblogs.com/auto/wp-content/uploads/2009/12/F-RAM+Micro.JPG" alt="F-RAM and Microcontroller" width="273" height="160" /><p class="wp-caption-text">F-RAM and Microcontroller</p></div>
<p>Above is an equivalent circuit design using F-RAM. As you can see, the capacitor is no longer required for two simple reasons:</p>
<ol>
<li>F-RAM writes 50 to 100 times faster than EEPROM, allowing the data to be written as the main power supply fails without support from capacitors</li>
<li>F-RAM uses about 1/100th the power of an EEPPROM so, in effect, the power that is dying lasts much longer</li>
</ol>
<p>So why is this important? F-RAM allows for simpler, cost effective, and more reliable designs in automotive applications. Although F-RAM compoments are more expensive than EEPROMs, when you add up the solution cost including the EEPROM, extra capacitor, assembly issues, and extra board area, F-RAM becomes a compelling high-performance design alternative.</p>
<p>Also, the more data you need to write, the larger the capacitor needs to be in both size and Farads. One recent application that comes to mind needed capacitance of around 0.1F. This amount of capacitance does not come cheap. Another spec that engineers need to look at is the capacitance at max temperature. Capacitors leak and the leakage increases with temperature. Low-leakage capacitors are readily available but, again,  they are more expensive.</p>
<p>I recommend taking the time tocalculate the amount of capacitance you actually need with your EEPROM at the maximum operating temperature and ask yourself if F-RAM actually allows a cheaper and more effective solution.</p>
]]></content:encoded>
			<wfw:commentRss>http://ramtronblogs.com/auto/2009/12/eeprom-can-be-a-right-and-royal-pain/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

