<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss 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/" version="2.0">

<channel>
	<title>The Eyes Have It</title>
	
	<link>http://blogs.synopsys.com/theeyeshaveit</link>
	<description>A Mixed-Signal IP Blog</description>
	<lastBuildDate>Wed, 01 Feb 2012 08:30:30 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.2</generator>
		<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/synopsysoc/eyes" /><feedburner:info xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" uri="synopsysoc/eyes" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><feedburner:emailServiceId xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">synopsysoc/eyes</feedburner:emailServiceId><feedburner:feedburnerHostname xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">http://feedburner.google.com</feedburner:feedburnerHostname><item>
		<title>Analog’s exciting 28-nm comeback</title>
		<link>http://blogs.synopsys.com/theeyeshaveit/2012/02/01/analogs-exciting-28-nm-comeback/</link>
		<comments>http://blogs.synopsys.com/theeyeshaveit/2012/02/01/analogs-exciting-28-nm-comeback/#comments</comments>
		<pubDate>Wed, 01 Feb 2012 08:30:30 +0000</pubDate>
		<dc:creator>Navraj Nandra</dc:creator>
				<category><![CDATA[An analog designer speaks!]]></category>
		<category><![CDATA[Data Converters]]></category>
		<category><![CDATA[General - mixed-signal IP]]></category>
		<category><![CDATA[32 nm]]></category>
		<category><![CDATA[ADC]]></category>
		<category><![CDATA[DAC]]></category>
		<category><![CDATA[DesignWare Analog IP]]></category>
		<category><![CDATA[DesignWare Mixed-Signal IP]]></category>
		<category><![CDATA[DesignWare MSIP]]></category>
		<category><![CDATA[Intellectual Property]]></category>
		<category><![CDATA[Mixed-signal IP]]></category>
		<category><![CDATA[SOC]]></category>
		<category><![CDATA[system-on-a-chip]]></category>

		<guid isPermaLink="false">http://blogs.synopsys.com/theeyeshaveit/?p=749</guid>
		<description><![CDATA[This afternoon, panelists from Cypress Semiconductor, Tanner EDA, IP Extreme, Cadence and Synopsys debated the future of analog/mixed-signal at DesignCon (Santa Clara, California), in the aptly titled &#8220;Is It Time for an Analog Comeback&#8221; organized and moderated by Brian Bailey. Brian presented the case that today&#8217;s analog circuitry has come on-chip and with better tools, questioned [...]]]></description>
			<content:encoded><![CDATA[<p>This afternoon, panelists from Cypress Semiconductor, Tanner EDA, IP Extreme, Cadence and Synopsys debated the future of analog/mixed-signal at DesignCon (Santa Clara, California), in the aptly titled &#8220;Is It Time for an Analog Comeback&#8221; organized and moderated by Brian Bailey. Brian presented the case that today&#8217;s analog circuitry has come on-chip and with better tools, questioned whether analog content will increase or will the shrinking geometries cause problems for analog design. Here are some interesting perspectives from the panelists and my thoughts on what they said and as a bonus I&#8217;ve added a copy of my slides at the end.</p>
<p>Harold Joseph (Cypress) showed that analog interfaces, “sensor” &amp; general purpose data converters are finding their way into mainstream micro-controllers and other generic digital processing chips. From my perspective we will see more of this as applications ramp-up and mature, for example smart-grid metering and automotive requirements. As these data converters (ADC, DAC) move into the micro-controller, the process nodes required will get smaller. The key is robustness and flexibility in these applications.</p>
<p>Jeff Miller from Tanner EDA presented a good summary of the deep-submicron challenges the impact analog design causing a bottleneck, similar to the points on the first slide below. Solutions to some of these challenges are presented in my slide two.</p>
<p>Warren Savage contradicted the panel by highlighting the OMAP5: complex general purpose digital functions rely on raw performance to differentiate. They start in very advanced nodes to keep power dissipation down and increase functionality.</p>
<p>Although the initial iterations are really general purpose and do not integrate pure analog content, I would say that as the product life-cycle evolves, differentiation is achieved by adding more periphery analog functions. A good example is the application processor that is being merged with the baseband or with the digital TV reception to reduce costs. These ASSPs derivatives include analog in these additional functions.</p>
<p>My panel contribution is captured in the two slides below &#8211; there are new challenges in developing analog/mixed-signal in 28-nm and 20-nm but these can be solved with improvements in power, area and performace. The ADC on slide 2 highlights this point.</p>
<p><a href="http://blogs.synopsys.com/theeyeshaveit/files/2012/02/DesignCon-Analog-Panel-Navraj-Nandra-slide-1.png" rel="lightbox[749]"><img class="aligncenter size-medium wp-image-751" src="http://blogs.synopsys.com/theeyeshaveit/files/2012/02/DesignCon-Analog-Panel-Navraj-Nandra-slide-1-300x225.png" alt="" width="300" height="225" /></a></p>
<p><a href="http://blogs.synopsys.com/theeyeshaveit/files/2012/02/DesignCon-Analog-Panel-Navraj-Nandra-slide-1.png" rel="lightbox[749]"></a><a href="http://blogs.synopsys.com/theeyeshaveit/files/2012/02/DesignCon-Analog-Panel-Navraj-Nandra-slide-2.png" rel="lightbox[749]"><img class="aligncenter size-medium wp-image-752" src="http://blogs.synopsys.com/theeyeshaveit/files/2012/02/DesignCon-Analog-Panel-Navraj-Nandra-slide-2-300x225.png" alt="" width="300" height="225" /></a></p>
 <img src="http://blogs.synopsys.com/theeyeshaveit/wp-content/plugins/feed-statistics.php?view=1&post_id=749" width="1" height="1" style="display: none;" />]]></content:encoded>
			<wfw:commentRss>http://blogs.synopsys.com/theeyeshaveit/2012/02/01/analogs-exciting-28-nm-comeback/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>HDMI’s Brave New Frontier (Forum)</title>
		<link>http://blogs.synopsys.com/theeyeshaveit/2011/12/20/hdmis-brave-new-frontier-forum/</link>
		<comments>http://blogs.synopsys.com/theeyeshaveit/2011/12/20/hdmis-brave-new-frontier-forum/#comments</comments>
		<pubDate>Tue, 20 Dec 2011 23:59:53 +0000</pubDate>
		<dc:creator>Navraj Nandra</dc:creator>
				<category><![CDATA[HDMI]]></category>
		<category><![CDATA[DesignWare HMDI 1.4]]></category>
		<category><![CDATA[DesignWare IP]]></category>
		<category><![CDATA[DesignWare Mixed-Signal IP]]></category>
		<category><![CDATA[DesignWare MSIP]]></category>
		<category><![CDATA[Mixed-signal IP]]></category>
		<category><![CDATA[SOC]]></category>

		<guid isPermaLink="false">http://blogs.synopsys.com/theeyeshaveit/?p=735</guid>
		<description><![CDATA[With over 1150 adopters and an install base of ~2Billion devices, HDMI has achieved an overwhelming success in the world of consumer electronics. Since its premiere at CES in 2003, HDMI has rapidly evolved and penetrated into applications that can be broadly classified into 3 segments: digital home, mobile multimedia and PC. HDMI is now [...]]]></description>
			<content:encoded><![CDATA[<p>With over 1150 adopters and an install base of ~2Billion devices, HDMI has achieved an overwhelming success in the world of consumer electronics. Since its premiere at CES in 2003, HDMI has rapidly evolved and penetrated into applications that can be broadly classified into 3 segments: digital home, mobile multimedia and PC. HDMI is now also found in many niche applications like 2Dà3D converter boxes, wireless hubs, automobiles (Honda Odyssey), NAS boxes etc. Given its broad and deep penetration into the world of consumer electronics, HDMI.org made the right decision to open up the standard body and form an entity called <strong>HDMI Forum</strong> for new companies willing to participate and define the future of HDMI. Synopsys is now a part of the HDMI forum and is looking forward to influence and make positive contributions to the HDMI specification for next generation consumer electronic applications. Being the largest provider of connectivity IPs, we can capture a very broad view of the semiconductor market and overall consumer electronic industry trends. We have collected feedback from over 125 companies that are integrating HDMI connectivity into their SOCs. We constantly meet with consumer electronic giants to discuss their requirements for next generation platforms. This puts us in a very unique position to translate the end customer requirements into HDMI specification.  </p>
<p><strong>Next generation HDMI</strong>: Synopsys believes that for its continued success, HDMI should evolve to address the specific needs of each of the three broad segments discussed above.</p>
<ol>
<li><strong>Digital Home</strong> – HDMI dominates this market segment with close to 100% penetration in applications like DTVs, Blu Ray Players, AVRs, and Game Consoles. Hence HDMI should continue to future-proof itself, further enhance the user experience, and integrate some of the digital home connectivity standards. Some specific ideas include:
<ol>
<li>Increasing bandwidth from 10.2Gbps à ~18Gbps to support deep-color 4K resolution mode</li>
<li>Offer cinema video formats (21:9 aspect ratio as defined in CEA-861-F  specification)</li>
<li>Offer a transparent remote control with the goal to control the source remotely</li>
</ol>
</li>
<li><strong>Mobile Multimedia (battery powered applications)</strong> – HDMI has experienced a rapid penetration in the mobile multimedia applications. The top 7 tablets in the world are now supporting HDMI connectivity (either directly or through a dongle). HDMI competes with MHL in mobile applications and should offer the following enhancements to succeed in this segment:
<ol>
<li>Power consumption is a key factor in mobile applications. Hence HDMI should target to reduce the overall power consumption by Muxing some of the TMDS channels, offering reduced range differential amplitude and low resolution video modes. HDMI should also eliminate some of the legacy requirements such as 5V protection to save area, pin count and power.</li>
<li>Battery charging capability is also extremely important to penetrate into mobile market. HDMI should offer battery charging functionality (just like USB) by using its HPD (hot plug detect) and NC (no connect) pins.</li>
</ol>
</li>
<li><strong>PC Applications</strong> – HDMI clearly competes with Displayport in this segment and should offer PC-specific features to penetrate into this eco-system. Some specific ideas to successfully compete with Displayport are:
<ol>
<li>Increasing bandwidth from 10.2Gbps à ~18Gbps to support resolution up to WQXGA (2560&#215;1600) at 120Hz frame rate. This would require using the TMDS clock lane as a 4th TMDS data channel + embedded clock.</li>
<li>Transporting up to 4 video frames to support daisy chaining for multi-display mode.</li>
<li>Transport USB2.0 traffic within the HDMI cable (similar to HEAC) by mapping D+ and D- from USB2.0 into HDMI NC and HPD pins. Extent CEC to declare USB traffic.</li>
</ol>
</li>
</ol>
<p>While we are recommending all these new features, Synopsys is mindful that one of the underlying requirements is <strong>backwards compatibility</strong> to previous generations of the specification. We will always take this into account as we work with other forum members to define the future of HDMI. </p>
<p>Finally, Synopsys is glad to be a part of the HDMI forum and given our deep understanding of connectivity IPs, we will help enhance HDMI specification and enable it to successfully compete with other standards like DisplayPort, MHL and V-by-One.</p>
<p><a href="http://blogs.synopsys.com/theeyeshaveit/files/2011/12/HDMI-screen-size1.png" rel="lightbox[735]"><img class="aligncenter size-full wp-image-743" src="http://blogs.synopsys.com/theeyeshaveit/files/2011/12/HDMI-screen-size1.png" alt="" width="298" height="299" /></a></p>
<p><a href="http://blogs.synopsys.com/theeyeshaveit/files/2011/12/HDMI-over-time.png" rel="lightbox[735]"><img class="aligncenter size-medium wp-image-738" src="http://blogs.synopsys.com/theeyeshaveit/files/2011/12/HDMI-over-time-300x120.png" alt="" width="339" height="160" /></a><a href="http://blogs.synopsys.com/theeyeshaveit/files/2011/12/HDMI-screen-size.png" rel="lightbox[735]"></a></p>
 <img src="http://blogs.synopsys.com/theeyeshaveit/wp-content/plugins/feed-statistics.php?view=1&post_id=735" width="1" height="1" style="display: none;" />]]></content:encoded>
			<wfw:commentRss>http://blogs.synopsys.com/theeyeshaveit/2011/12/20/hdmis-brave-new-frontier-forum/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>28 nm in Volume Production</title>
		<link>http://blogs.synopsys.com/theeyeshaveit/2011/10/24/28-nm-in-volume-production/</link>
		<comments>http://blogs.synopsys.com/theeyeshaveit/2011/10/24/28-nm-in-volume-production/#comments</comments>
		<pubDate>Mon, 24 Oct 2011 20:17:12 +0000</pubDate>
		<dc:creator>Navraj Nandra</dc:creator>
				<category><![CDATA[An analog designer speaks!]]></category>
		<category><![CDATA[Data Converters]]></category>
		<category><![CDATA[General - mixed-signal IP]]></category>
		<category><![CDATA[Low Power]]></category>
		<category><![CDATA[Low Power - Analog Designer's Guide]]></category>
		<category><![CDATA[28 nm]]></category>
		<category><![CDATA[32 nm]]></category>
		<category><![CDATA[ADC]]></category>
		<category><![CDATA[DAC]]></category>
		<category><![CDATA[DDR]]></category>
		<category><![CDATA[DDR2]]></category>
		<category><![CDATA[DDR3]]></category>
		<category><![CDATA[DesignWare Analog IP]]></category>
		<category><![CDATA[DesignWare IP]]></category>
		<category><![CDATA[DesignWare Mixed-Signal IP]]></category>
		<category><![CDATA[Mixed-signal IP]]></category>
		<category><![CDATA[SOC]]></category>
		<category><![CDATA[system-on-a-chip]]></category>
		<category><![CDATA[system-on-chip]]></category>

		<guid isPermaLink="false">http://synopsysoc.org/theeyeshaveit/?p=732</guid>
		<description><![CDATA[TSMC&#8217;s announcement this morning about 28 nm reaching volume production lined up with Synopsys&#8217; IP availability on these leading edge nodes. According to TSMC the number of customer 28 nm production tape outs has more than doubled as compared with that of 40 nm &#8211; not surprising when companies such as Qualcomm with their Snapdragon platform; [...]]]></description>
			<content:encoded><![CDATA[<p>TSMC&#8217;s announcement this morning about 28 nm reaching volume production lined up with Synopsys&#8217; IP availability on these leading edge nodes. According to TSMC the number of customer 28 nm production tape outs has more than doubled as compared with that of 40 nm &#8211; not surprising when companies such as Qualcomm with their Snapdragon platform; both low power and high performance FPGA&#8217;s from Altera and Xilinx; and nVidia&#8217;s GPU, utilize these technologies. Getting to a production quality level for the 28 nm technologies has posed many challenges to the semicondutor fabs and developing IP on these nodes has required circuit invention to continue following the technology scaling requirements while meeting the manufacturing demands.</p>
<p>From an analog/mixed-signal  design perspective the most interesting challenge was to support the scaling trends that the digital circuits benefit. The challenges can be summarised as: </p>
<ul>
<li>Meeting 28 nm process design rules for manufacturability</li>
<li>SoC integrators expect analog/mixed-signal IP to follow digital scaling trends &#8211; the IP cannot grow in size</li>
<li>System specs have not changed to reflect lower  (1.8 V) I/O voltages</li>
</ul>
<p>In order to meet these challenges, new analog/mixed-signal design techniques need to be developed  in order to benefit from technology scaling. Below is an example of an analog to digital converter where, through new design techniques the design has scaled ten times since the original architecture. Calibration techniques (“digitally enhanced analog”) were used to reduce demand on analog features: gain, offset, matching and increase robustness to PVT. And analog techniques such as clock boosting switches to circumvent low supply voltage, while internally processing signals with large voltage swings were used. All of these techniques are applicable to 28 nm.</p>
<div id="attachment_733" class="wp-caption aligncenter" style="width: 310px"><a href="http://blogs.synopsys.com/theeyeshaveit/files/2011/10/ten-years-ADC.png" rel="lightbox[732]"><img class="size-medium wp-image-733" src="http://blogs.synopsys.com/theeyeshaveit/files/2011/10/ten-years-ADC-300x121.png" alt="" width="300" height="121" /></a><p class="wp-caption-text">ADC Scaling Using Design Techniques</p></div>
<p> From a system specification perspective, if USB and HDMI are to be integrated on a 28 nm SoC, 5 V compliance requirements must be met &#8211; the challenge for the design engineer is to do this using 1.8 V transistors.</p>
<p>Scaling analog/mixed-signal circuits and meeting the &#8220;high voltage&#8221; system requirements are two of the challenges that must be met in order to support successful implementation of these new 28 nm technologies. That is, the IP needs to work not only on the prototype test-chip but also in production.</p>
 <img src="http://blogs.synopsys.com/theeyeshaveit/wp-content/plugins/feed-statistics.php?view=1&post_id=732" width="1" height="1" style="display: none;" />]]></content:encoded>
			<wfw:commentRss>http://blogs.synopsys.com/theeyeshaveit/2011/10/24/28-nm-in-volume-production/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Extending Shannon For Tablets Using 20 nm IP</title>
		<link>http://blogs.synopsys.com/theeyeshaveit/2011/10/17/extending-shannon-for-tablets-using-20-nm-ip/</link>
		<comments>http://blogs.synopsys.com/theeyeshaveit/2011/10/17/extending-shannon-for-tablets-using-20-nm-ip/#comments</comments>
		<pubDate>Mon, 17 Oct 2011 21:27:53 +0000</pubDate>
		<dc:creator>Navraj Nandra</dc:creator>
				<category><![CDATA[An analog designer speaks!]]></category>
		<category><![CDATA[Data Converters]]></category>
		<category><![CDATA[DDR]]></category>
		<category><![CDATA[General - mixed-signal IP]]></category>
		<category><![CDATA[HDMI]]></category>
		<category><![CDATA[Low Power]]></category>
		<category><![CDATA[Low Power - Analog Designer's Guide]]></category>
		<category><![CDATA[PCI Express]]></category>
		<category><![CDATA[SATA]]></category>
		<category><![CDATA[USB]]></category>
		<category><![CDATA[28 nm]]></category>
		<category><![CDATA[32 nm]]></category>
		<category><![CDATA[DDR memnory controller]]></category>
		<category><![CDATA[DDR memory controller]]></category>
		<category><![CDATA[DDR3]]></category>
		<category><![CDATA[DesignWare Analog IP]]></category>
		<category><![CDATA[DesignWare HMDI 1.4]]></category>
		<category><![CDATA[DesignWare Mixed-Signal IP]]></category>
		<category><![CDATA[Intellectual Property]]></category>
		<category><![CDATA[Mixed-signal IP]]></category>
		<category><![CDATA[PCI]]></category>

		<guid isPermaLink="false">http://synopsysoc.org/theeyeshaveit/?p=719</guid>
		<description><![CDATA[  Tomorrow I&#8217;ll be presenting at TSMC&#8217;s OIP (Open Innovation Program) on a topic regarding high performance analog and interface IP that is used in the latest smart phones, tablets and also the data centers. The idea of the talk was triggered by an article that I read about how the theoretical limit of Shannon&#8217;s [...]]]></description>
			<content:encoded><![CDATA[<div class="mceTemp mceIEcenter"> </div>
<p>Tomorrow I&#8217;ll be presenting at TSMC&#8217;s OIP (Open Innovation Program) on a topic regarding high performance analog and interface IP that is used in the latest smart phones, tablets and also the data centers. The idea of the talk was triggered by an article that I read about how the theoretical limit of Shannon&#8217;s Law is being reached and that Moore&#8217;s Law can be used to extend this bandwidth limit. What I&#8217;m presenting is that using the latest 28 nm and 20 nm technologies high performance analog and interface IP can be developed that can extend Shannon&#8217;s theoretical limit. If you cannot attend the talk, here&#8217;s the summary.</p>
<div id="attachment_724" class="wp-caption aligncenter" style="width: 310px"><a href="http://blogs.synopsys.com/theeyeshaveit/files/2011/10/Shannons-Limit1.png" rel="lightbox[719]"><img class="size-medium wp-image-724" src="http://blogs.synopsys.com/theeyeshaveit/files/2011/10/Shannons-Limit1-300x298.png" alt="" width="300" height="298" /></a><p class="wp-caption-text">Extending Shannon&#039;s Limit?</p></div>
<p style="text-align: center"><a href="http://blogs.synopsys.com/theeyeshaveit/files/2011/10/Shannons-Limit.png" rel="lightbox[719]"></a></p>
<div>
<dl><a href="http://blogs.synopsys.com/theeyeshaveit/files/2011/10/Shannons-Limit.png" rel="lightbox[719]"></a></dl>
</div>
<p><span style="text-decoration: underline">What&#8217;s causing this bandwidth limit?</span></p>
<p>Mobile multimedia products such as smartphones and tablets are driving huge bandwidth requirements into the data centers. A rough order magnitude states that one server in the data center is needed to handle the traffic from every 600 smartphones or 122 tablets. By 2015, it is projected that 7.1 billion phones and tablets, will be sending 75 exabytes (one billion gigabytes) of internet traffic. To address these bandwidth limits, Moore’s Law is driving innovation at the system-on-chip (SoC) level with quad-core CPU’s running in excess of 1.5 GHz in 28 nm. In order to get data on and off the SoC, from the application processor to the base-band chip, high performance interfaces are used. Since the design and implementation challenges are significantly greater at 28 nm and below, SoC development teams are looking for ways to meet aggressive product cycles by implementing third party intellectual property (IP) for these interfaces. </p>
<p><span style="text-decoration: underline">28-nm, 20-nm technology and IP</span></p>
<p>Being a consumer driven market, cost is a major factor for mobile multimedia products and SoC companies are using economies of scale afforded by 28 nm integration levels to build media processors to fit multiple personal computer and consumer electronic platforms. The interface IP needs include multi-port USB 2.0, USB 3.0, HSIC (high-speed inter-chip) which is derived from the USB protocol, PCI Express Gen. 1, SATA, HDMI Tx (to connect to high definition displays), MIPI CSI/DSI for camera and displays interfaces, Gigabit Ethernet and SD 4.0. Also, smartphone storage will exceed 100 GB in 2012 and this will require both throughput and capacity: USB “sync-n-go”, micro-USB, potentially UFS (universal flash storage) are likely candidates for this type of interface IP. The DRAM bandwidth is growing faster than any market segment: mDDR (mobile DDR) is being replaced by LPDDR2 this year. Audio codec’s and general purpose data converter IPs are also required. The low power variant of 28 nm technology (the POLYSION based LP, or the HKMG HPL) is the preferred choice with a 1.8 V gate oxide. Other important requirements include special power down modes.</p>
<p>On the other end, data centers or cloud computing is driving high-end IP requirements in 28HPM or 28HP processes. The data center backbone will use the 8 Gb/s PCIe 3.0 switches and these are used to connect to multi-channel 10 Gb Ethernet HBA (host bus adapters). The high-speed DDR3 memory interfaces are expected to operate at 2133 Mb/s supporting both RDIMM and LRDIMM – and these will eventually move to DDR4 2013.</p>
<p><span style="text-decoration: underline">How does TSMC&#8217;s OIP help in all of this?</span></p>
<p>TSMC&#8217;s Open Innovation Program (OIP) is an integral part of the collaboration between Synopsys and TSMC. For analog/mixed-signal IP this means access to early versions of design kits help reduce the adoption barrier for customers implementing next-generation SoC designs in the advanced process technologies.  By providing IP that meets the rigorous TSMC9000 certification standards, Synopsys and TSMC are enabling our mutual customers to reduce integration risk and system cost, while quickly ramping up into volume production</p>
 <img src="http://blogs.synopsys.com/theeyeshaveit/wp-content/plugins/feed-statistics.php?view=1&post_id=719" width="1" height="1" style="display: none;" />]]></content:encoded>
			<wfw:commentRss>http://blogs.synopsys.com/theeyeshaveit/2011/10/17/extending-shannon-for-tablets-using-20-nm-ip/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Smart posters, Google wallets and NFC</title>
		<link>http://blogs.synopsys.com/theeyeshaveit/2011/10/03/smart-posters-google-wallets-and-nfc/</link>
		<comments>http://blogs.synopsys.com/theeyeshaveit/2011/10/03/smart-posters-google-wallets-and-nfc/#comments</comments>
		<pubDate>Tue, 04 Oct 2011 03:23:11 +0000</pubDate>
		<dc:creator>Navraj Nandra</dc:creator>
				<category><![CDATA[NVM]]></category>
		<category><![CDATA[DesignWare Analog IP]]></category>
		<category><![CDATA[Mixed-signal IP]]></category>
		<category><![CDATA[Navraj Nandra]]></category>
		<category><![CDATA[SOC]]></category>

		<guid isPermaLink="false">http://synopsysoc.org/theeyeshaveit/?p=711</guid>
		<description><![CDATA[NFC – or Near Field Communication is a technology that allows, amongst many other uses, mobile payment and transportation ticketing using your cell phone. The underlying technology for NFC has been around for quite a while, but until now the supporting ecosystem has been lacking. The most significant development has been the formation of Isis, [...]]]></description>
			<content:encoded><![CDATA[<p>NFC – or Near Field Communication is a technology that allows, amongst many other uses, mobile payment and transportation ticketing using your cell phone. The underlying technology for NFC has been around for quite a while, but until now the supporting ecosystem has been lacking. The most significant development has been the formation of Isis, a collaboration of AT&amp;T, T-Mobile, and Verizon to establish a mobile payment platform that is now being backed by almost all the major handset manufacturers including HTC, LG, Samsung, Motorola, RIM, and Sony Ericsson. The Isis momentum is augmented by a number of other recent announcements from key technology companies. Google just recently released the trial version of Google Wallet and Broadcom has announced a 40nm SoC that supports NFC.</p>
<p style="text-align: center"><a href="http://blogs.synopsys.com/theeyeshaveit/files/2011/10/SoundOfJamaica_NFCPoster1.jpg" rel="lightbox[711]"><img class="size-medium wp-image-714  aligncenter" src="http://blogs.synopsys.com/theeyeshaveit/files/2011/10/SoundOfJamaica_NFCPoster1-212x300.jpg" alt="" width="212" height="300" /></a></p>
<p>iSupply is forecasting ~55% CAGR in NFC for mobile phones between now and 2015.</p>
<p style="text-align: center"> <a href="http://blogs.synopsys.com/theeyeshaveit/files/2011/10/NFC.png" rel="lightbox[711]"><img class="size-medium wp-image-715  aligncenter" src="http://blogs.synopsys.com/theeyeshaveit/files/2011/10/NFC-300x141.png" alt="" width="399" height="237" /></a></p>
<p>NFC enabled handsets will create new opportunities for marketing, payment, and data interactions for consumers. At the most basic level, smart posters with embedded NFC tags will allow a passerby to download information on local restaurants, movie trailers, or upcoming events by simply tapping their phone on the poster. Maxim Integrated Circuits recently announced that they will be demonstrating smart poster technology at upcoming conferences and for a period of 4 hours recently, there was an NFC enabled sign demonstration in Times Square.</p>
<p>Moving beyond smart posters is full mobile payment. One of the keys to enabling mobile payment is the creation and implementation of a secure element to provide the necessary encryption technology to satisfy the requirements of the entire ecosystem, including consumers, network operators, and financial institutions. The need for secure elements is being served in two main ways. First, a number of companies, such as Verayo, have taken their proprietary technology and used it to create discrete ICs that can be incorporated into systems such as a SIM card to provide security function. Other companies, including IntrinsicID and Invia among others, are developing their technology to be delivered as IP for integration into larger SoCs.</p>
<p>One common requirement for both smart posters as well as mobile payments is the need for embedded nonvolatile memory. Synopsys DesignWare portfolio offers a range of nonvolatile memory options optimized for NFC requirements for both discrete tags and secure elements (normally developed in analog focused process nodes) and fully integrated secure elements that require implementation in an advanced process node.</p>
<p>To learn more <a href="http://seminar2.techonline.com/registration/wcIndex.cgi?sessionID=synopsys_oct0511">http://seminar2.techonline.com/registration/wcIndex.cgi?sessionID=synopsys_oct0511</a></p>
 <img src="http://blogs.synopsys.com/theeyeshaveit/wp-content/plugins/feed-statistics.php?view=1&post_id=711" width="1" height="1" style="display: none;" />]]></content:encoded>
			<wfw:commentRss>http://blogs.synopsys.com/theeyeshaveit/2011/10/03/smart-posters-google-wallets-and-nfc/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>DFI – Updated DDR4 Memory Interface</title>
		<link>http://blogs.synopsys.com/theeyeshaveit/2011/09/21/dfi-updated-ddr4-memory-interface/</link>
		<comments>http://blogs.synopsys.com/theeyeshaveit/2011/09/21/dfi-updated-ddr4-memory-interface/#comments</comments>
		<pubDate>Wed, 21 Sep 2011 23:47:18 +0000</pubDate>
		<dc:creator>Navraj Nandra</dc:creator>
				<category><![CDATA[DDR]]></category>
		<category><![CDATA[DDR memnory controller]]></category>
		<category><![CDATA[DDR memory controller]]></category>
		<category><![CDATA[DDR2]]></category>
		<category><![CDATA[DDR3]]></category>
		<category><![CDATA[DesignWare IP]]></category>
		<category><![CDATA[Intellectual Property]]></category>

		<guid isPermaLink="false">http://synopsysoc.org/theeyeshaveit/?p=700</guid>
		<description><![CDATA[If your designs include DDR subsystems, you have probably heard about DFI and if you have integrated DDR subsystem IP, DDR controllers and PHYs, you are probably fairly intimate with DFI.  In short, DFI is a DDR controller to PHY interface specification.  The intent of the DFI specification is to provide DDR controller and PHY [...]]]></description>
			<content:encoded><![CDATA[<p>If your designs include DDR subsystems, you have probably heard about DFI and if you have integrated DDR subsystem IP, DDR controllers and PHYs, you are probably fairly intimate with DFI.  In short, DFI is a DDR controller to PHY interface specification.  The intent of the DFI specification is to provide DDR controller and PHY IP designers with a clear description of how the DDR controller must communicate with the DDR PHY and vice versa.  DFI first came about because of the need to support the interface between a DDR controller from one provider and a DDR PHY from another.  DFI 1.0 was the first of the DFI specifications that was developed to support DDR2 followed by DFI 2.0, which included support for DDR3 and then support for LPDDR2 was added with DFI 2.1.  On Monday September 19, a press release was issued announcing the availability of a preliminary release of the DFI 3.0 specification which includes support for DDR4.  This release was supported by the members of the DFI committee of which Synopsys is a contributing member.  You can find a copy of the press release here:  <a href="http://www.marketwire.com/press-release/dfi-technical-group-releases-latest-high-speed-memory-controller-phy-interface-specification-1562484.htm">http://www.marketwire.com/press-release/dfi-technical-group-releases-latest-high-speed-memory-controller-phy-interface-specification-1562484.htm</a> </p>
<p>You can also down load the preliminary DFI3.0 specification at <a href="http://www.ddr-phy.org/">http://www.ddr-phy.org/</a></p>
<p>Synopsys is a proponent and a driver of the DFI specification because it provides a level of certainty for our IP users when it comes to integration of the DDR subsystem, especially if the user is using the Synopsys DDR controller with another PHY or a Synopsys DDR PHY with a DDR controller IP from another source. </p>
<p><img class="aligncenter size-medium wp-image-704" src="http://blogs.synopsys.com/theeyeshaveit/files/2011/09/DDR-DFI1-300x166.png" alt="" width="300" height="166" /></p>
<p>Synopsys DesignWare DDR protocol controller showing DFI.</p>
 <img src="http://blogs.synopsys.com/theeyeshaveit/wp-content/plugins/feed-statistics.php?view=1&post_id=700" width="1" height="1" style="display: none;" />]]></content:encoded>
			<wfw:commentRss>http://blogs.synopsys.com/theeyeshaveit/2011/09/21/dfi-updated-ddr4-memory-interface/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Something new is coming out of your home wall plug</title>
		<link>http://blogs.synopsys.com/theeyeshaveit/2011/03/06/something-new-is-coming-out-of-your-home-wall-plug/</link>
		<comments>http://blogs.synopsys.com/theeyeshaveit/2011/03/06/something-new-is-coming-out-of-your-home-wall-plug/#comments</comments>
		<pubDate>Mon, 07 Mar 2011 03:30:45 +0000</pubDate>
		<dc:creator>Navraj Nandra</dc:creator>
				<category><![CDATA[An analog designer speaks!]]></category>
		<category><![CDATA[Data Converters]]></category>
		<category><![CDATA[General - mixed-signal IP]]></category>
		<category><![CDATA[ADC]]></category>
		<category><![CDATA[DAC]]></category>
		<category><![CDATA[DesignWare Analog IP]]></category>
		<category><![CDATA[DesignWare IP]]></category>
		<category><![CDATA[DesignWare Mixed-Signal IP]]></category>
		<category><![CDATA[G.hn]]></category>
		<category><![CDATA[Gigabit home network]]></category>
		<category><![CDATA[home plug]]></category>
		<category><![CDATA[Intellectual Property]]></category>
		<category><![CDATA[ITU]]></category>
		<category><![CDATA[Mixed-signal IP]]></category>

		<guid isPermaLink="false">http://synopsysoc.org/theeyeshaveit/?p=678</guid>
		<description><![CDATA[The latest tablet  announcements are creating lots of excitement but I would like to draw your attention to an emerging technology much closer to home &#8211;  in fact coming right out of your regular wall plug. New standards are emerging that will take advantage of all the networks present in your home, these are the electrical power lines running inside [...]]]></description>
			<content:encoded><![CDATA[<p>The latest tablet  announcements are creating lots of excitement but I would like to draw your attention to an emerging technology much closer to home &#8211;  in fact coming right out of your regular wall plug. New standards are emerging that will take advantage of all the networks present in your home, these are the electrical power lines running inside your walls, your phone line or the coaxial cables and connect them up in a way that is transparent to you. It appears as one big network. Sounds like a great idea&#8230;why hasn&#8217;t it been done before?</p>
<p>Well, actually the concept is not new. Different protocols, or standards pushed by many companies, have fought for predominance in the home networking arena. Each uses its own media. For example, the power grid for Power Line Communications, the telephone network for HPNA and the coaxial cable network for MoCA. The figure below shows the home network (G.hn) implementation.</p>
<p style="text-align: center"><a href="http://blogs.synopsys.com/theeyeshaveit/files/2011/03/G.hn-home-network.png" rel="lightbox[678]"><img class="size-medium wp-image-679  aligncenter" src="http://blogs.synopsys.com/theeyeshaveit/files/2011/03/G.hn-home-network-300x185.png" alt="" width="300" height="185" /></a></p>
<p>In a typical home several of these networks co- exist, however they are not necessarily physically placed where they are more useful. Everybody has gone through the frustration of finding that the plug in the wall is not where it would be most convenient. This has, in fact, been a major limitation of the adoption of home networking, when compared to wireless.</p>
<p>G.hn, which is being standardized by the ITU, achieves this goal by defining a unified Physical Layer and Data Link Layer that can operate over multiple wire types. Furthermore, this PHY (and other critical blocks in the system) are defined for each wire type, resulting in the ability to outperform the specialized standards for each wire. In other words G.hn unites coax, phone lines and mains (electrical) cabling into a single network capable of hosting multiple HD streams over gigabit bandwidths around the home.</p>
<p>In parallel, the IEEE standardization body is already looking into ways of converging wireline home networking and wireless (WiFi, Power Line and Coax), from the network management perspective. It’s still an open question if this standard (IEEE P1905.1 working group) will also cover G.hn or not.</p>
<p>Apart from convergence, the other key “selling factor” for G.hn is the increased bit rate supported. These two factors place severe requirements in terms of the PHY performance and specifically the data converters. For example, the high data rate (high bandwidth) requires high sampling rates: 200 to 400 MSPS and the harsh, unfriendly, nature of the power grid. This imposes high resolution: 12 to 14-bit while processing these very large bandwidth signals.</p>
<p>I&#8217;m happy that Synopsys is participating in these emerging standards, by offering a family of  data converters that addresses exactly the requirements for such systems. This portfolio is made of compact and ultra low power 12-bit 250 MSPS ADCs and 14-bit 400 MSPS DAC which are  ideally suited for broadband communication applications helping to bring intelligence to your home wall plug.</p>
 <img src="http://blogs.synopsys.com/theeyeshaveit/wp-content/plugins/feed-statistics.php?view=1&post_id=678" width="1" height="1" style="display: none;" />]]></content:encoded>
			<wfw:commentRss>http://blogs.synopsys.com/theeyeshaveit/2011/03/06/something-new-is-coming-out-of-your-home-wall-plug/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>How Synopsys Integrates An IP Acquisition…Bringing In New DDR DNA</title>
		<link>http://blogs.synopsys.com/theeyeshaveit/2011/02/14/how-synopsys-integrates-an-ip-acquisition%e2%80%a6bringing-in-new-ddr-dna/</link>
		<comments>http://blogs.synopsys.com/theeyeshaveit/2011/02/14/how-synopsys-integrates-an-ip-acquisition%e2%80%a6bringing-in-new-ddr-dna/#comments</comments>
		<pubDate>Mon, 14 Feb 2011 23:12:51 +0000</pubDate>
		<dc:creator>Navraj Nandra</dc:creator>
				<category><![CDATA[DDR]]></category>

		<guid isPermaLink="false">http://synopsysoc.org/theeyeshaveit/?p=670</guid>
		<description><![CDATA[Regular readers will have noticed fewer postings lately; my attention focused on integrating, what was until recently, a competing IP product. The Virage acquisition brought an interesting product overlap challenge in terms of the high speed memory interfaces at Synopsys. From the marketing perspective the key questions revolved around which versions to productize since we [...]]]></description>
			<content:encoded><![CDATA[<p>Regular readers will have noticed fewer postings lately; my attention focused on integrating, what was until recently, a competing IP product. The Virage acquisition brought an interesting product overlap challenge in terms of the high speed memory interfaces at Synopsys. From the marketing perspective the key questions revolved around which versions to productize since we now had two versions of the DDR digital controller and two versions of the DDR PHY. Of course any decisions had repercussions on the engineering organization, go-to market and sales strategy.</p>
<p>Now with hindsight, having completed our new DDR product roadmap, the integration of the engineering team; the challenge turned out to be great opportunity to bring in the DNA of a company that was making traction in high speed memory interfaces and combining it with our own expertise as an IP provider.</p>
<p>A new DDR controller was released <a href="http://synopsys.mediaroom.com/index.php?s=43&amp;item=897">http://synopsys.mediaroom.com/index.php?s=43&amp;item=897</a> with improvements in latency, performance and lower gate count. The DDR memory controller is user configurable, which allows users to generate a single port DDR controller with all the required features for their particular application.  In addition to basic features, such as bus width, number of ranks and DRAM protocol selection, this release enables users to optimize data throughout and area, with the configurable look-ahead, as well as reduce latency with the optional priority bypass. Several software programmable options to tune the DDR memory controller are offered to meet the needs of the users particular application and traffic.</p>
<p>With respect to the DDR PHY, we were investigating methods to make it easier for our customers to configure, estimate power based on DDR user defined traffic and the result was the DDR PHY Compiler <a href="http://synopsys.mediaroom.com/index.php?s=43&amp;item=888">http://synopsys.mediaroom.com/index.php?s=43&amp;item=888</a>.  This is truly a first for DDR PHYs.  The PHY compiler allows customers to use a GUI interface to configure and automatically generate all required files to enable integration of the DDR PHY.  The PHY compiler not only will enable users to configure their DDR PHY, but offer power estimates based on user defined DDR traffic for each supported DDR protocol, a diagram of the PHY even wrapping a corners.  There are over 60 parameters that can be modified to optimize the DDR PHY integration. </p>
<div id="attachment_672" class="wp-caption aligncenter" style="width: 298px"><a href="http://blogs.synopsys.com/theeyeshaveit/files/2011/02/DDR-PHY-Compiler.jpg" rel="lightbox[670]"><img class="size-medium wp-image-672" src="http://blogs.synopsys.com/theeyeshaveit/files/2011/02/DDR-PHY-Compiler-288x300.jpg" alt="" width="288" height="300" /></a><p class="wp-caption-text">DDR PHY Compiler</p></div>
<p>In the next few months I’ll be posting more DDR product updates.</p>
 <img src="http://blogs.synopsys.com/theeyeshaveit/wp-content/plugins/feed-statistics.php?view=1&post_id=670" width="1" height="1" style="display: none;" />]]></content:encoded>
			<wfw:commentRss>http://blogs.synopsys.com/theeyeshaveit/2011/02/14/how-synopsys-integrates-an-ip-acquisition%e2%80%a6bringing-in-new-ddr-dna/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PCI Express Gen 3 Enters Prime Time – Opens New Markets</title>
		<link>http://blogs.synopsys.com/theeyeshaveit/2010/11/18/pci-express-gen-3-enters-prime-time-opens-new-markets/</link>
		<comments>http://blogs.synopsys.com/theeyeshaveit/2010/11/18/pci-express-gen-3-enters-prime-time-opens-new-markets/#comments</comments>
		<pubDate>Fri, 19 Nov 2010 06:05:30 +0000</pubDate>
		<dc:creator>Navraj Nandra</dc:creator>
				<category><![CDATA[PCI Express]]></category>
		<category><![CDATA[DesignWare IP]]></category>
		<category><![CDATA[DesignWare Mixed-Signal IP]]></category>
		<category><![CDATA[Mixed-signal IP]]></category>
		<category><![CDATA[PCI]]></category>
		<category><![CDATA[PCI Express 3.0]]></category>
		<category><![CDATA[PCI-SIG]]></category>
		<category><![CDATA[PHY]]></category>

		<guid isPermaLink="false">http://synopsysoc.org/theeyeshaveit/?p=637</guid>
		<description><![CDATA[Today, the final version of the PCI Express 3.0 (Generation 3) specification was released by the PCI Express Special Interest Group (PCI-SIG). With almost 1000 members and backed by companies such as Intel, HP, Oracle, AMD, Dell and Nvidia, this 8 Gb/s high speed serial interface will open new market opportunities in enterprise, data center [...]]]></description>
			<content:encoded><![CDATA[<div class="mceTemp mceIEcenter" style="text-align: left">
<p style="text-align: left">Today, the final version of the PCI Express 3.0 (Generation 3) specification was released by the PCI Express Special Interest Group (PCI-SIG). With almost 1000 members and backed by companies such as Intel, HP, Oracle, AMD, Dell and Nvidia, this 8 Gb/s high speed serial interface will open new market opportunities in enterprise, data center and storage applications.</p>
<div id="attachment_656" class="wp-caption alignnone" style="width: 310px"><a href="http://blogs.synopsys.com/theeyeshaveit/files/2010/11/PCI-Express-Generations1.png" rel="lightbox[637]"><img class="size-medium wp-image-656" src="http://blogs.synopsys.com/theeyeshaveit/files/2010/11/PCI-Express-Generations1-300x78.png" alt="" width="300" height="78" /></a><p class="wp-caption-text">Three Generations Of PCI Express</p></div>
<p style="text-align: left">Board member and chairman, Ramin Neshati, said that the new 8 Gb/s architecture will allow companies to build low-cost and power-efficient components and systems, could also be used for on-board components such as co-processors. The new specification could boost data transfers in high-performance systems, and data will get to storage devices and memory faster. He continued by saying that if a system builder is on a budget and has certain power consumption restrictions, they could build a server based on the second generation. For faster servers you could go with the third generation.  Products designed around the latest specification will be able to achieve bandwidth near 1 GBps one direction on a single-lane configuration and scale to 32 GBps on a 16-lane configuration, Neshati said. He brought up an interesting point: that the new generation does not automatically replace the existing install base &#8211; it just targets a different market.</p>
<p style="text-align: left">This begs the question on whether the previous generations will slowly disappear. From our market understanding, new opportunities are being created &#8211; especially driven by consumer connectivity in printers and wireless hubs. These applications only require the first PCI Express generation in a single lane, enabling the designer to trade off area, power and bandwidth. So, all three generations will survive &#8211; targetting specific markets. The above table provides a summary of the speed improvements.</p>
<p style="text-align: center">
<p style="text-align: left">In the enterprise market, at these high gen. 3.0 speeds, equalizers need to be used to counteract the effects of interference, cross-talk and high frequency noise. The type of equalization was a topic that was discussed extensively inside and outside the PCI-SIG. Power and area drove some of the decisions to include only a linear equalizer (CTLE) in the receiver for the PCI Express 3.0 PHY specifications. In evaluating the channel, that decision was re-thought, considering that there is a 10 mV eye-opening after the reference CTLE. In reality this means that the eye is closed. Under these conditions, decision feedback equalization DFE (either direct or unrolled) was a considered option. This will improve the PHY’s peformance but potentially impact power and area. In summary the CTLE  boosts signal plus the noise, so SNR gets worse. DFE uses previous data bits to determine equalization and improves SNR. </p>
<p><a href="http://blogs.synopsys.com/theeyeshaveit/files/2010/11/PCIe-3.0-PHY-eye.png" rel="lightbox[637]"></a></p>
<div id="attachment_658" class="wp-caption aligncenter" style="width: 310px"><a href="http://blogs.synopsys.com/theeyeshaveit/files/2010/11/PCIe-3.0-PHY-eye3.png" rel="lightbox[637]"><img class="size-medium wp-image-658" src="http://blogs.synopsys.com/theeyeshaveit/files/2010/11/PCIe-3.0-PHY-eye3-300x178.png" alt="" width="300" height="178" /></a><p class="wp-caption-text">Synopsys PCI Express Gen. 3 PHY Test-Chip </p></div>
<p style="text-align: left">Further details on the complete solutions for all three generations of PCI Express can be found on <a href="http://www.synopsys.com/IP/InterfaceIP/PCIExpress/Pages/default.aspx">http://www.synopsys.com/IP/InterfaceIP/PCIExpress/Pages/default.aspx</a></p>
</div>
 <img src="http://blogs.synopsys.com/theeyeshaveit/wp-content/plugins/feed-statistics.php?view=1&post_id=637" width="1" height="1" style="display: none;" />]]></content:encoded>
			<wfw:commentRss>http://blogs.synopsys.com/theeyeshaveit/2010/11/18/pci-express-gen-3-enters-prime-time-opens-new-markets/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>The HDMI Ecosystem – Part 3, Grassroots</title>
		<link>http://blogs.synopsys.com/theeyeshaveit/2010/11/03/the-hdmi-ecosystem-part-3-grassroots/</link>
		<comments>http://blogs.synopsys.com/theeyeshaveit/2010/11/03/the-hdmi-ecosystem-part-3-grassroots/#comments</comments>
		<pubDate>Wed, 03 Nov 2010 13:43:41 +0000</pubDate>
		<dc:creator>Navraj Nandra</dc:creator>
				<category><![CDATA[HDMI]]></category>
		<category><![CDATA[DesignWare Analog IP]]></category>
		<category><![CDATA[DesignWare Mixed-Signal IP]]></category>
		<category><![CDATA[DesignWare MSIP]]></category>
		<category><![CDATA[Mixed-signal IP]]></category>
		<category><![CDATA[SOC]]></category>

		<guid isPermaLink="false">http://synopsysoc.org/theeyeshaveit/?p=632</guid>
		<description><![CDATA[Participating in the CEDIA (Custom Home Theater Installation Contractors) workshop is a classic example of how we approach each standard from grass roots level. This was the first ever HDMI installer workshop with the goal of providing better insight into HDMI protocol and equipment connection sequences. We gained familiarity was various test instruments. We also [...]]]></description>
			<content:encoded><![CDATA[<p>Participating in the CEDIA (Custom Home Theater Installation Contractors) workshop is a classic example of how we approach each standard from grass roots level.</p>
<p>This was the first ever HDMI installer workshop with the goal of providing better insight into HDMI protocol and equipment connection sequences. We gained familiarity was various test instruments. We also learnt that most common problems in HDMI installations happen when an HDMI device (HDMI AVRs, HDMI switches, HDMI splitters, HDMI Cat6 Extenders etc) is inserted between 2 existing HDMI devices (set top box and digital TV). The device in the middle manipulates DTV’s EDID in various ways to reflect its limitations or improvements over DTV’s capabilities. Such daisy chaining does not work very well and troubleshooting the faulty component can be a night mare. We also saw some failures related to HDCP over poor quality cables. The bit errors during HDCP authentication corrupt the DDC channel and cause the authentication to fail.</p>
<p>Lessons learnt in such events are invaluable and our customers (and end consumers) reap the benefits of a robust interface that is a true “plug and play”.</p>
 <img src="http://blogs.synopsys.com/theeyeshaveit/wp-content/plugins/feed-statistics.php?view=1&post_id=632" width="1" height="1" style="display: none;" />]]></content:encoded>
			<wfw:commentRss>http://blogs.synopsys.com/theeyeshaveit/2010/11/03/the-hdmi-ecosystem-part-3-grassroots/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

