<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/atom10full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">
    <title>Design Notes - EEWeb</title>
    
    <link href="http://www.eeweb.com/design-articles/" />
    <id>http://www.eeweb.com/feeds/application-design-notes/</id>
    <updated>2013-05-24T09:08:37-07:00</updated>
    <author>
        <name>EEWeb</name>
        <email>info@eeweb.com</email>
    </author>
    
        <atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/atom+xml" href="http://feeds.feedburner.com/EEWebAppDesignNotes" /><feedburner:info uri="eewebappdesignnotes" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><entry>
            <title>Design Guidelines for 100 Gbps - CFP2 Interface</title>
            <link rel="alternate" href="http://feedproxy.google.com/~r/EEWebAppDesignNotes/~3/Hz9kZ_MMQEg/" />
            <id>http://www.eeweb.com/design-articles/design-guidelines-for-100-gbps-cfp2-interface/</id>
            <published>2013-05-23T07:41:44-07:00</published>
            <updated>2013-05-23T18:32:45-07:00</updated>
            <summary type="html">
                
                    &lt;p&gt;&lt;img src="http://d3i5bpxkxvwmz.cloudfront.net/resized/images/remote/http_s.eeweb.com/articles/2013/05/23/Screen-Shot-2013-05-23-at-8.43.55-AM-1369320585_300_73.png" alt="" width="300" height="73" /&gt;&lt;/p&gt;
                
                
                                    	&lt;p&gt;The common electrical interface &lt;span class="caps"&gt;&lt;span class="caps"&gt;CEI&lt;/span&gt;&lt;/span&gt;&lt;del&gt;28G&lt;/del&gt;&lt;span class="caps"&gt;&lt;span class="caps"&gt;VSR&lt;/span&gt;&lt;/span&gt; implementation architecture (IA) for short reach channels is intendedfornext generation100 Gbps chip- to &amp;#8211; opticalmodule applications. CFP2 is apluggable optical module that uses &lt;span class="caps"&gt;&lt;span class="caps"&gt;CEI&lt;/span&gt;&lt;/span&gt;&lt;del&gt;28G&lt;/del&gt;&lt;span class="caps"&gt;&lt;span class="caps"&gt;VSR&lt;/span&gt;&lt;/span&gt; as its electrical interface (as defined by the &lt;span class="caps"&gt;&lt;span class="caps"&gt;CFP&lt;/span&gt;&lt;/span&gt; Multi-Source Agreement (&lt;span class="caps"&gt;&lt;span class="caps"&gt;MSA&lt;/span&gt;&lt;/span&gt;)member companies).CFP2alsodefinesthemechanical formfactorfora100 Gbpsoptical transceiver module targeted for Ethernet and &lt;span class="caps"&gt;&lt;span class="caps"&gt;OTN&lt;/span&gt;&lt;/span&gt; (Optical Transport Network) applications. CFP2 provides an industry standard to develop next generation 100 G interfaces with lower power and greater port density compared to previous generation &lt;span class="caps"&gt;&lt;span class="caps"&gt;CFP&lt;/span&gt;&lt;/span&gt; optical modules. The channel layout on the &lt;span class="caps"&gt;&lt;span class="caps"&gt;PCB&lt;/span&gt;&lt;/span&gt; is optimized in order to meet the strict insertion and return loss masks defined by &lt;span class="caps"&gt;&lt;span class="caps"&gt;CEI&lt;/span&gt;&lt;/span&gt;&lt;del&gt;28G&lt;/del&gt;&lt;span class="caps"&gt;&lt;span class="caps"&gt;VSR&lt;/span&gt;&lt;/span&gt;. Refer to the following documents for more information on optimizing your board designs for high speed serial links.&lt;/p&gt;
                            &lt;img src="http://feeds.feedburner.com/~r/EEWebAppDesignNotes/~4/Hz9kZ_MMQEg" height="1" width="1"/&gt;</summary>
        <feedburner:origLink>http://www.eeweb.com/design-articles/design-guidelines-for-100-gbps-cfp2-interface/</feedburner:origLink></entry>
    
        <entry>
            <title>Getting Started with AT91SAM9XE Microcontrollers</title>
            <link rel="alternate" href="http://feedproxy.google.com/~r/EEWebAppDesignNotes/~3/hlL9zeVcxt0/" />
            <id>http://www.eeweb.com/design-articles/getting-started-with-at91sam9xe-microcontrollers/</id>
            <published>2013-05-22T07:00:34-07:00</published>
            <updated>2013-05-21T14:06:36-07:00</updated>
            <summary type="html">
                
                    &lt;p&gt;&lt;img src="http://d3i5bpxkxvwmz.cloudfront.net/resized/images/remote/http_s.eeweb.com/articles/2013/05/21/Screen-Shot-2013-05-21-at-1.56.18-PM-1369166796_300_52.png" alt="" width="300" height="52" /&gt;&lt;/p&gt;
                
                
                                    	&lt;p&gt;This section describes how to program a basic application that helps you to become familiar with AT91SAM9XE microcontrollers. It is divided into two main sections: the first one covers the specification of the example (what it does, what peripherals are used), the other details the programming aspect. 3.1 Specification 3.1.1 Features The demonstration program makes two &lt;span class="caps"&gt;&lt;span class="caps"&gt;LED&lt;/span&gt;&lt;/span&gt;s on the board blink at a fixed rate. This rate is generated by using a timer for the first &lt;span class="caps"&gt;&lt;span class="caps"&gt;LED&lt;/span&gt;&lt;/span&gt;. The second one uses a Wait function based on a 1 ms tick. The blinking can be stopped using two buttons (one for each &lt;span class="caps"&gt;&lt;span class="caps"&gt;LED&lt;/span&gt;&lt;/span&gt;). While this software may look simple, it uses several peripherals which make up the basis of an operating system. As such, it makes a good starting point for someone wanting to become familiar with the AT91SAM microcontroller series. 3.1.2 Peripherals In order to perform the operations described in the previous section, the software example uses the following set of peripherals: • Parallel Input/Output (&lt;span class="caps"&gt;&lt;span class="caps"&gt;PIO&lt;/span&gt;&lt;/span&gt;) controller • Timer Counter (TC) • Periodic Interval Timer (&lt;span class="caps"&gt;&lt;span class="caps"&gt;PIT&lt;/span&gt;&lt;/span&gt;) • Advanced Interrupt Controller (&lt;span class="caps"&gt;&lt;span class="caps"&gt;AIC&lt;/span&gt;&lt;/span&gt;) • Debug Unit (&lt;span class="caps"&gt;&lt;span class="caps"&gt;DBGU&lt;/span&gt;&lt;/span&gt;) &lt;span class="caps"&gt;&lt;span class="caps"&gt;LED&lt;/span&gt;&lt;/span&gt;s and buttons on the board are connected to standard input/output pins of the chip; those are managed by a &lt;span class="caps"&gt;&lt;span class="caps"&gt;PIO&lt;/span&gt;&lt;/span&gt; controller. In addition, it is possible to have the controller generate an interrupt when the status of one of its pins changes; buttons are configured to have this behavior. The TC and &lt;span class="caps"&gt;&lt;span class="caps"&gt;PIT&lt;/span&gt;&lt;/span&gt; are used to generate two time bases, in order to obtain the &lt;span class="caps"&gt;&lt;span class="caps"&gt;LED&lt;/span&gt;&lt;/span&gt; blinking rates. They are both used in interrupt mode: the TC triggers an interrupt at a fixed rate, each time toggling the &lt;span class="caps"&gt;&lt;span class="caps"&gt;LED&lt;/span&gt;&lt;/span&gt; state (on/off). The &lt;span class="caps"&gt;&lt;span class="caps"&gt;PIT&lt;/span&gt;&lt;/span&gt; triggers an interrupt every millisecond, incrementing a variable by one tick. The Wait function monitors this variable to provide a precise delay for toggling the second &lt;span class="caps"&gt;&lt;span class="caps"&gt;LED&lt;/span&gt;&lt;/span&gt; state.&lt;/p&gt;
                            &lt;img src="http://feeds.feedburner.com/~r/EEWebAppDesignNotes/~4/hlL9zeVcxt0" height="1" width="1"/&gt;</summary>
        <feedburner:origLink>http://www.eeweb.com/design-articles/getting-started-with-at91sam9xe-microcontrollers/</feedburner:origLink></entry>
    
        <entry>
            <title>Integrated Debugging-  A New Approach to  Troubleshooting Your Designs  with Real-Time Oscilloscopes</title>
            <link rel="alternate" href="http://feedproxy.google.com/~r/EEWebAppDesignNotes/~3/9zyqx8q-BIY/" />
            <id>http://www.eeweb.com/design-articles/integrated-debugging-a-new-approach-to-troubleshooting-your-designs-with-re/</id>
            <published>2013-05-21T13:55:02-07:00</published>
            <updated>2013-05-20T15:01:03-07:00</updated>
            <summary type="html">
                
                    &lt;p&gt;&lt;img src="http://d3i5bpxkxvwmz.cloudfront.net/resized/images/remote/http_s.eeweb.com/articles/2013/05/20/Integrated-Debugging-A-New-Approach-to-Troubleshooting-Your-Designs-with-Real-Time-Oscilloscopes-1369083659_231_218.png" alt="" width="231" height="218" /&gt;&lt;/p&gt;
                
                
                                    	&lt;p&gt;Traditional jitter analysis software provides you valuable information about jitter  trends (temporal fluctuation  of jitter), and the jitter spectrum (frequency component of  jitter). It can also separate RJ  and DJ. You can use the software to figure out how much  jitter your device has, and if  it meets the specification in  question. But when you want  to reduce jitter, you have to  find out what is causing it.  You may have an idea of the  causes by looking at the peak  frequencies of the jitter spectrum. However if the jitter is  not systemic but intermittent,  the root cause is difficult to  determine. Eye pattern tools recover the  clock of the signal, make an eye  pattern and make mask tests.  When the eye fails the mask  test, you can unfold the waveform to see when it fails. You can  also decode 8b10b coding. Using  this approach you can check if mask test failures and waveform  patterns have correlations. But  if there is no correlation, you  cannot find the cause of the  mask failure. As you have seen, using features  of your oscilloscope separately  limits your debugging ability. These tools lack power working alone, and you need to  combine them to use the full  power of your oscilloscope. Case study 1: Combining jitter analysis tool with  oscilloscope general measurements. You know that your device has  large quantities of jitter on the  &lt;span class="caps"&gt;&lt;span class="caps"&gt;DDR&lt;/span&gt;&lt;/span&gt; memory clock, and this  causes problems. You want to  improve the situation. Using  jitter analysis measurements, you pinpoint the exact value  of the jitter, but you can’t figure out what is behind it. You  can guess that this is periodic  jitter by the shape of the histogram. The jitter trend also  shows that there is periodic  noise on the clock. Next, you use your oscilloscope’s  general purpose tools to look  at several signal waveforms at  the same time. You then probe  some signals you suspect could  be contributing jitter, and  show them on the scope. A  browser probe is convenient  at times like this.  You check to see if the suspected  signal and the clock jitter trend  have any correlation. If there  is a correlation, the signal you  are probing is the cause of the  jitter. If there is no correlation,  you continue probing until you find the source of jitter.&lt;/p&gt;
                            &lt;img src="http://feeds.feedburner.com/~r/EEWebAppDesignNotes/~4/9zyqx8q-BIY" height="1" width="1"/&gt;</summary>
        <feedburner:origLink>http://www.eeweb.com/design-articles/integrated-debugging-a-new-approach-to-troubleshooting-your-designs-with-re/</feedburner:origLink></entry>
    
        <entry>
            <title>Implementing Memory Structures for  Video Processing in the Vivado HLS Tool</title>
            <link rel="alternate" href="http://feedproxy.google.com/~r/EEWebAppDesignNotes/~3/mB1ELCFHMoQ/" />
            <id>http://www.eeweb.com/design-articles/implementing-memory-structures-for-video-processing-in-the-vivado-hls-tool/</id>
            <published>2013-05-20T08:18:39-07:00</published>
            <updated>2013-05-17T09:23:40-07:00</updated>
            <summary type="html">
                
                    &lt;p&gt;&lt;img src="http://d3i5bpxkxvwmz.cloudfront.net/resized/images/remote/http_s.eeweb.com/articles/2013/05/17/Screen-Shot-2013-05-17-at-9.17.50-AM-1368804221_300_217.png" alt="" width="300" height="217" /&gt;&lt;/p&gt;
                
                
                                    	&lt;p&gt;Video processing algorithms, which are predominantly computation intensive, are natural candidates for hardware implementation with the &lt;span class="caps"&gt;&lt;span class="caps"&gt;HLS&lt;/span&gt;&lt;/span&gt; tool. The techniques described in this application note  cover the basics of video algorithm implementation in the &lt;span class="caps"&gt;&lt;span class="caps"&gt;HLS&lt;/span&gt;&lt;/span&gt; tool in terms of synchronization  signal handling and memory architectures. Regardless of the exact computation in the user  algorithm, these types of applications are memory intensive. The memory architecture  expressed in the algorithm has a direct correlation to overall system performance and hardware  resource consumption. The recommendations on memory buffer architecture presented in this  application note are applicable to Vivado &lt;span class="caps"&gt;&lt;span class="caps"&gt;HLS&lt;/span&gt;&lt;/span&gt; designs on all Xilinx &lt;span class="caps"&gt;&lt;span class="caps"&gt;FPGA&lt;/span&gt;&lt;/span&gt;s. Introduction The Vivado &lt;span class="caps"&gt;&lt;span class="caps"&gt;HLS&lt;/span&gt;&lt;/span&gt; tool provides a methodology for implementing video and image processing  blocks in Xilinx &lt;span class="caps"&gt;&lt;span class="caps"&gt;FPGA&lt;/span&gt;&lt;/span&gt;s. The &lt;span class="caps"&gt;&lt;span class="caps"&gt;HLS&lt;/span&gt;&lt;/span&gt; tool enables the creation of accelerators targeted at different  performance points and different &lt;span class="caps"&gt;&lt;span class="caps"&gt;FPGA&lt;/span&gt;&lt;/span&gt;s from the same algorithmic code. For video and image  processing, different performance targets can be specified in terms of maximum image  resolution and frames per second. This application note focuses on the following aspects of video processing IP creation in the  &lt;span class="caps"&gt;&lt;span class="caps"&gt;HLS&lt;/span&gt;&lt;/span&gt; tool: • Overview of the basic video frame format and its description in C/C++ • Memory architecture specification for high-throughput processing The video processing IP core can be controlled from a processor using application program  interfaces (&lt;span class="caps"&gt;&lt;span class="caps"&gt;API&lt;/span&gt;&lt;/span&gt;s) generated by the &lt;span class="caps"&gt;&lt;span class="caps"&gt;HLS&lt;/span&gt;&lt;/span&gt; tool. For more information on processor control of  Vivado &lt;span class="caps"&gt;&lt;span class="caps"&gt;HLS&lt;/span&gt;&lt;/span&gt; IP, refer to Processor Control of Vivado &lt;span class="caps"&gt;&lt;span class="caps"&gt;HLS&lt;/span&gt;&lt;/span&gt; Designs.&lt;/p&gt;
                            &lt;img src="http://feeds.feedburner.com/~r/EEWebAppDesignNotes/~4/mB1ELCFHMoQ" height="1" width="1"/&gt;</summary>
        <feedburner:origLink>http://www.eeweb.com/design-articles/implementing-memory-structures-for-video-processing-in-the-vivado-hls-tool/</feedburner:origLink></entry>
    
        <entry>
            <title>Designing High-Performance Video Systems  in 7 Series FPGAs</title>
            <link rel="alternate" href="http://feedproxy.google.com/~r/EEWebAppDesignNotes/~3/dusohcOIsv4/" />
            <id>http://www.eeweb.com/design-articles/designing-high-performance-video-systems-in-7-series-fpgas/</id>
            <published>2013-05-17T13:19:41-07:00</published>
            <updated>2013-04-26T15:00:42-07:00</updated>
            <summary type="html">
                
                
                                    	&lt;p&gt;The design uses eight &lt;span class="caps"&gt;&lt;span class="caps"&gt;AXI&lt;/span&gt;&lt;/span&gt; video direct memory access (&lt;span class="caps"&gt;&lt;span class="caps"&gt;VDMA&lt;/span&gt;&lt;/span&gt;) engines to simultaneously move 16 streams (eight transmit video streams and eight receive video streams), each in 1920 &amp;#215; 1080 pixel format at 60 or 75 Hz refresh rates, and up to 32 data bits per pixel. Each &lt;span class="caps"&gt;&lt;span class="caps"&gt;VDMA&lt;/span&gt;&lt;/span&gt; is driven from a video test pattern generator (&lt;span class="caps"&gt;&lt;span class="caps"&gt;TPG&lt;/span&gt;&lt;/span&gt;) with a video timing controller (&lt;span class="caps"&gt;&lt;span class="caps"&gt;VTC&lt;/span&gt;&lt;/span&gt;)  block to set up the necessary video timing signals. Data read by each &lt;span class="caps"&gt;&lt;span class="caps"&gt;AXI&lt;/span&gt;&lt;/span&gt; &lt;span class="caps"&gt;&lt;span class="caps"&gt;VDMA&lt;/span&gt;&lt;/span&gt; is sent to a  common on-screen display (&lt;span class="caps"&gt;&lt;span class="caps"&gt;OSD&lt;/span&gt;&lt;/span&gt;) core capable of multiplexing or overlaying multiple video streams to a single output video stream. The output of the &lt;span class="caps"&gt;&lt;span class="caps"&gt;OSD&lt;/span&gt;&lt;/span&gt; core drives the onboard high-definition media interface (&lt;span class="caps"&gt;&lt;span class="caps"&gt;HDMI&lt;/span&gt;&lt;/span&gt;) video display interface through the color space  converter. The performance monitor block is added to capture &lt;span class="caps"&gt;&lt;span class="caps"&gt;DDR&lt;/span&gt;&lt;/span&gt; performance metrics. &lt;span class="caps"&gt;&lt;span class="caps"&gt;DDR&lt;/span&gt;&lt;/span&gt; traffic is passed through the &lt;span class="caps"&gt;&lt;span class="caps"&gt;AXI&lt;/span&gt;&lt;/span&gt; Interconnect to move 16 video streams over 8 &lt;span class="caps"&gt;&lt;span class="caps"&gt;VDMA&lt;/span&gt;&lt;/span&gt; pipelines. All 16 video streams moved by the &lt;span class="caps"&gt;&lt;span class="caps"&gt;AXI&lt;/span&gt;&lt;/span&gt; &lt;span class="caps"&gt;&lt;span class="caps"&gt;VDMA&lt;/span&gt;&lt;/span&gt; blocks are buffered through a shared DDR3 &lt;span class="caps"&gt;&lt;span class="caps"&gt;SDRAM&lt;/span&gt;&lt;/span&gt;  memory and are controlled by a MicroBlaze™ processor. The reference system is targeted for the Kintex-7 &lt;span class="caps"&gt;&lt;span class="caps"&gt;FPGA&lt;/span&gt;&lt;/span&gt; XC7K325TFFG900-1 on the Xilinx  KC705 evaluation board (revision C or D) [Ref 1]. Included  Systems The reference design is created and built using version 14.3 of the Xilinx Platform Studio (&lt;span class="caps"&gt;&lt;span class="caps"&gt;XPS&lt;/span&gt;&lt;/span&gt;)  tool, which is part of the ISE® Design Suite: System Edition. In addition to the &lt;span class="caps"&gt;&lt;span class="caps"&gt;XPS&lt;/span&gt;&lt;/span&gt; project, an  equivalent Vivado™ tools logic design flow project is also provided for reference. The &lt;span class="caps"&gt;&lt;span class="caps"&gt;XPS&lt;/span&gt;&lt;/span&gt; tools  delivered in the Vivado Design Suite: System Edition (&lt;span class="caps"&gt;&lt;span class="caps"&gt;EDK&lt;/span&gt;&lt;/span&gt;) might provide a higher level of  automation than building the equivalent system using the Vivado tools logic design flow.  Creation of the reference design using the Vivado tools logic design flow is described in detail in Building Hardware, page 16. The design also includes software built using the Xilinx  Software Development Kit (&lt;span class="caps"&gt;&lt;span class="caps"&gt;SDK&lt;/span&gt;&lt;/span&gt;). The software runs on the MicroBlaze processor subsystem  and implements control, status, and monitoring functions. Complete &lt;span class="caps"&gt;&lt;span class="caps"&gt;XPS&lt;/span&gt;&lt;/span&gt; and &lt;span class="caps"&gt;&lt;span class="caps"&gt;SDK&lt;/span&gt;&lt;/span&gt; project files  are provided with this application note to allow the user to examine and rebuild the design or to  use it as a template for starting a new design. Introduction High-performance video systems can be created using Xilinx &lt;span class="caps"&gt;&lt;span class="caps"&gt;AXI&lt;/span&gt;&lt;/span&gt; IP. The use of &lt;span class="caps"&gt;&lt;span class="caps"&gt;AXI&lt;/span&gt;&lt;/span&gt;  Interconnect, Memory Interface Generator (&lt;span class="caps"&gt;&lt;span class="caps"&gt;MIG&lt;/span&gt;&lt;/span&gt;), and &lt;span class="caps"&gt;&lt;span class="caps"&gt;VDMA&lt;/span&gt;&lt;/span&gt; IP blocks can form the core of  video systems capable of handling multiple video streams and frame buffers sharing a common  DDR3 &lt;span class="caps"&gt;&lt;span class="caps"&gt;SDRAM&lt;/span&gt;&lt;/span&gt; memory. &lt;span class="caps"&gt;&lt;span class="caps"&gt;AXI&lt;/span&gt;&lt;/span&gt; is a standardized IP interface protocol based on the Advanced  Microcontroller Bus Architecture (AMBA®) specification. The &lt;span class="caps"&gt;&lt;span class="caps"&gt;AXI&lt;/span&gt;&lt;/span&gt; interfaces used in the  reference design consist of AXI4, AXI4-Lite, and AXI4-Stream interfaces as described in the  &lt;span class="caps"&gt;&lt;span class="caps"&gt;AMBA&lt;/span&gt;&lt;/span&gt; AXI4 specifications [Ref 2]. These interfaces provide a common IP interface protocol  framework around which to build the design.&lt;/p&gt;
                            &lt;img src="http://feeds.feedburner.com/~r/EEWebAppDesignNotes/~4/dusohcOIsv4" height="1" width="1"/&gt;</summary>
        <feedburner:origLink>http://www.eeweb.com/design-articles/designing-high-performance-video-systems-in-7-series-fpgas/</feedburner:origLink></entry>
    
        <entry>
            <title>Apple iPad Remote Control for  Broadcasting T&amp;M Instruments</title>
            <link rel="alternate" href="http://feedproxy.google.com/~r/EEWebAppDesignNotes/~3/zrYWWoL-0cw/" />
            <id>http://www.eeweb.com/design-articles/apple-ipad-remote-control-for-broadcasting-tm-instruments/</id>
            <published>2013-05-16T12:27:51-07:00</published>
            <updated>2013-04-26T13:40:52-07:00</updated>
            <summary type="html">
                
                    &lt;p&gt;&lt;img src="http://d3i5bpxkxvwmz.cloudfront.net/resized/images/remote/http_s.eeweb.com/articles/2013/04/26/Screen-Shot-2013-04-26-at-1.30.48-PM-1367005253_300_104.png" alt="" width="300" height="104" /&gt;&lt;/p&gt;
                
                
                                    	&lt;p&gt;Remote desktop access is a convenient way to remotely control Rohde &amp;amp; Schwarz measuring instruments over a network. When using &lt;span class="caps"&gt;&lt;span class="caps"&gt;WLAN&lt;/span&gt;&lt;/span&gt;, this function can also be  used with an Apple iPad running a remote desktop app. One particularly appealing possibility is to set up a measuring instrument with a &lt;span class="caps"&gt;&lt;span class="caps"&gt;USB&lt;/span&gt;&lt;/span&gt; &lt;span class="caps"&gt;&lt;span class="caps"&gt;WLAN&lt;/span&gt;&lt;/span&gt; adapter. In addition to standard &amp;#8220;infrastructure&amp;#8221; mode for use with a dedicated  access point, these adapters also support &amp;#8220;ad hoc&amp;#8221; mode, making it possible to  connect to an iPad, without needing any additional external devices. The connection  only has to be configured once. The settings are then saved so that the connection is  started directly after switching on the instrument. This simplifies access to instruments  without dedicated displays and offers a simple, detached solution for operating  measuring instruments installed in places that are difficult to reach.&lt;/p&gt;
                            &lt;img src="http://feeds.feedburner.com/~r/EEWebAppDesignNotes/~4/zrYWWoL-0cw" height="1" width="1"/&gt;</summary>
        <feedburner:origLink>http://www.eeweb.com/design-articles/apple-ipad-remote-control-for-broadcasting-tm-instruments/</feedburner:origLink></entry>
    
        <entry>
            <title>Calculating Motor Driver Power Dissipation</title>
            <link rel="alternate" href="http://feedproxy.google.com/~r/EEWebAppDesignNotes/~3/hhdpTNC5Yzs/" />
            <id>http://www.eeweb.com/design-articles/calculating-motor-driver-power-dissipation/</id>
            <published>2013-05-15T12:20:33-07:00</published>
            <updated>2013-05-21T20:15:34-07:00</updated>
            <summary type="html">
                
                    &lt;p&gt;&lt;img src="http://d3i5bpxkxvwmz.cloudfront.net/resized/images/remote/http_s.eeweb.com/articles/2013/04/26/Screen-Shot-2013-04-26-at-1.15.20-PM-1367004275_300_94.png" alt="" width="300" height="94" /&gt;&lt;/p&gt;
                
                
                                    	&lt;p&gt;When selecting a motor driver IC for a particular application, consider the maximum amount of current that must be driven. The thermal characteristics of the IC and &lt;span class="caps"&gt;&lt;span class="caps"&gt;PCB&lt;/span&gt;&lt;/span&gt; are often the limiting factor in how much current a given motor driver provides. When an output transitions from high to low or low to high, the output devices traverse a linear region where they are dissipating significantly more power than when fully turned on. This power dissipation is referred to as switching loss. Switching loss is a function of the following: • rise and fall times of the output, how quickly the output swings from one extreme to the other • supply voltage • output current • frequency that the output is switching In some cases, such as a DC motor driver that is only turned on or off (not subjected to &lt;span class="caps"&gt;&lt;span class="caps"&gt;PWM&lt;/span&gt;&lt;/span&gt; speed control or current control), this rate may be so small as to be negligible. On the other extreme, for example a stepper motor driver using current control, the outputs are always being switched at some &lt;span class="caps"&gt;&lt;span class="caps"&gt;PWM&lt;/span&gt;&lt;/span&gt; frequency to maintain current regulation.&lt;/p&gt;

	&lt;p&gt;Sources of Power Dissipation in a Motor Driver There are a number of sources of power dissipation inside a motor driver IC. Some are obvious, like the power dissipated in the &lt;span class="caps"&gt;&lt;span class="caps"&gt;FET&lt;/span&gt;&lt;/span&gt; ON-resistance, others are more subtle. To make an accurate assessment of the total power dissipation, all sources must be considered. 1.1 &lt;acronym title="ON"&gt;&lt;span class="caps"&gt;&lt;span class="caps"&gt;RDS&lt;/span&gt;&lt;/span&gt;&lt;/acronym&gt; Dissipation The biggest source of power dissipated inside a motor driver IC is the power dissipated in the &lt;span class="caps"&gt;&lt;span class="caps"&gt;FET&lt;/span&gt;&lt;/span&gt; ONresistance, or &lt;acronym title="ON"&gt;&lt;span class="caps"&gt;&lt;span class="caps"&gt;RDS&lt;/span&gt;&lt;/span&gt;&lt;/acronym&gt;. The power dissipated in an H-bridge (consisting of a high-side &lt;span class="caps"&gt;&lt;span class="caps"&gt;FET&lt;/span&gt;&lt;/span&gt; and a low-side &lt;span class="caps"&gt;&lt;span class="caps"&gt;FET&lt;/span&gt;&lt;/span&gt;) is calculated with the following: &lt;span class="caps"&gt;&lt;span class="caps"&gt;PRDS&lt;/span&gt;&lt;/span&gt; = (HS-&lt;acronym title="ON"&gt;&lt;span class="caps"&gt;&lt;span class="caps"&gt;RDS&lt;/span&gt;&lt;/span&gt;&lt;/acronym&gt; × (&lt;acronym title="RMS"&gt;&lt;span class="caps"&gt;&lt;span class="caps"&gt;IOUT&lt;/span&gt;&lt;/span&gt;&lt;/acronym&gt;) 2 ) + (LS-&lt;acronym title="ON"&gt;&lt;span class="caps"&gt;&lt;span class="caps"&gt;RDS&lt;/span&gt;&lt;/span&gt;&lt;/acronym&gt; × (&lt;acronym title="RMS"&gt;&lt;span class="caps"&gt;&lt;span class="caps"&gt;IOUT&lt;/span&gt;&lt;/span&gt;&lt;/acronym&gt;) 2 ) where &lt;span class="caps"&gt;&lt;span class="caps"&gt;PRDS&lt;/span&gt;&lt;/span&gt; is the power dissipated in the output &lt;span class="caps"&gt;&lt;span class="caps"&gt;FET&lt;/span&gt;&lt;/span&gt;s, HS-&lt;acronym title="ON"&gt;&lt;span class="caps"&gt;&lt;span class="caps"&gt;RDS&lt;/span&gt;&lt;/span&gt;&lt;/acronym&gt; is the resistance of the high-side &lt;span class="caps"&gt;&lt;span class="caps"&gt;FET&lt;/span&gt;&lt;/span&gt;, LS-&lt;acronym title="ON"&gt;&lt;span class="caps"&gt;&lt;span class="caps"&gt;RDS&lt;/span&gt;&lt;/span&gt;&lt;/acronym&gt; is the resistance of the low side &lt;span class="caps"&gt;&lt;span class="caps"&gt;FET&lt;/span&gt;&lt;/span&gt;, and &lt;acronym title="RMS"&gt;&lt;span class="caps"&gt;&lt;span class="caps"&gt;IOUT&lt;/span&gt;&lt;/span&gt;&lt;/acronym&gt; is the &lt;span class="caps"&gt;&lt;span class="caps"&gt;RMS&lt;/span&gt;&lt;/span&gt; output current being applied to the motor. Note that &lt;acronym title="ON"&gt;&lt;span class="caps"&gt;&lt;span class="caps"&gt;RDS&lt;/span&gt;&lt;/span&gt;&lt;/acronym&gt; increases with temperature, as the device heats, the power dissipation increases. This must be considered when calculating the total device power dissipation. If a device has two H-bridges, like a typical stepping motor driver, you need to add the power dissipated in each H-bridge. 1.2 Switching Losses When an output transitions from high to low or low to high, the output devices traverse a linear region where they are dissipating significantly more power than when fully turned on. This power dissipation is referred to as switching loss. Switching loss is a function of the following: • rise and fall times of the output, how quickly the output swings from one extreme to the other • supply voltage • output current • frequency that the output is switching In some cases, such as a DC motor driver that is only turned on or off (not subjected to &lt;span class="caps"&gt;&lt;span class="caps"&gt;PWM&lt;/span&gt;&lt;/span&gt; speed control or current control), this rate may be so small as to be negligible. On the other extreme, for example a stepper motor driver using current control, the outputs are always being switched at some &lt;span class="caps"&gt;&lt;span class="caps"&gt;PWM&lt;/span&gt;&lt;/span&gt; frequency to maintain current regulation.&lt;/p&gt;
                            &lt;img src="http://feeds.feedburner.com/~r/EEWebAppDesignNotes/~4/hhdpTNC5Yzs" height="1" width="1"/&gt;</summary>
        <feedburner:origLink>http://www.eeweb.com/design-articles/calculating-motor-driver-power-dissipation/</feedburner:origLink></entry>
    
        <entry>
            <title>Base of Electrostatic Capacitance Method Touch Key</title>
            <link rel="alternate" href="http://feedproxy.google.com/~r/EEWebAppDesignNotes/~3/fjXHddc4ZsQ/" />
            <id>http://www.eeweb.com/design-articles/base-of-electrostatic-capacitance-method-touch-key/</id>
            <published>2013-05-14T08:18:18-07:00</published>
            <updated>2013-05-15T22:54:19-07:00</updated>
            <summary type="html">
                
                    &lt;p&gt;&lt;img src="http://d3i5bpxkxvwmz.cloudfront.net/resized/images/remote/http_s.eeweb.com/articles/2013/04/26/Screen-Shot-2013-04-26-at-9.21.51-AM-1366989976_300_251.png" alt="" width="300" height="251" /&gt;&lt;/p&gt;
                
                
                                    	&lt;p&gt;The Touch panel microcomputer R8C/33T group contains a hardware peripheral (&lt;span class="caps"&gt;&lt;span class="caps"&gt;SCU&lt;/span&gt;&lt;/span&gt;:sensor control unit) that monitors the ”touch” of the human body by measuring the stray capacitance generated between the touch electrode and  the human. The electrostatic capacitance method is the general principle used in “Touch” measurements.  The touch electrode is formed with materials such as &lt;span class="caps"&gt;&lt;span class="caps"&gt;PCB&lt;/span&gt;&lt;/span&gt; (printed circuits board), &lt;span class="caps"&gt;&lt;span class="caps"&gt;ITO&lt;/span&gt;&lt;/span&gt; (Indium Tin Oxide) films and  electroconductive rubbers. The electric capacitance generated between the touch electrode and the human body is  measured and a key ON or &lt;span class="caps"&gt;&lt;span class="caps"&gt;OFF&lt;/span&gt;&lt;/span&gt; judgement is made. As an application example, there are matrix keys, sliders, a wheel,  etc. when the detection of movement around the circumference is desired, the wheel is used. When a lot of keys are necessary, the matrix configuration is used. The touch key matrix is like the key scanning  matrix used with mechanical switches. When detection of movement of the finger that is the top to bottom or right and  left is desired, the slider is used, and when the detection of movement around the circumference is desired, the wheel is  used.&lt;/p&gt;
                            &lt;img src="http://feeds.feedburner.com/~r/EEWebAppDesignNotes/~4/fjXHddc4ZsQ" height="1" width="1"/&gt;</summary>
        <feedburner:origLink>http://www.eeweb.com/design-articles/base-of-electrostatic-capacitance-method-touch-key/</feedburner:origLink></entry>
    
        <entry>
            <title>Practical Considerations For Attaching Surface-mount Components</title>
            <link rel="alternate" href="http://feedproxy.google.com/~r/EEWebAppDesignNotes/~3/hwS-zh3Uz2c/" />
            <id>http://www.eeweb.com/design-articles/practical-considerations-for-attaching-surface-mount-components/</id>
            <published>2013-05-13T15:42:42-07:00</published>
            <updated>2013-04-25T16:52:44-07:00</updated>
            <summary type="html">
                
                    &lt;p&gt;&lt;img src="http://d3i5bpxkxvwmz.cloudfront.net/resized/images/remote/http_s.eeweb.com/articles/2013/04/25/Screen-Shot-2013-04-25-at-4.42.12-PM-1366929993_300_210.png" alt="" width="300" height="210" /&gt;&lt;/p&gt;
                
                
                                    	&lt;p&gt;What automated soldering methods can be considered for Mini-Circuits surface-mount components? There are two basic methods: reflow and wave soldering. Generally, reflow soldering can be done when (l) there are only surface mount components, or (2) these are present together with through-hole components and the latter will be soldered in a separate (wave soldering) step. The surface-mount components can be located on both the upper and lower sides of the board, when reflow is used. Wave soldering is suitable for through-hole components mounted on top of the board as well as for surface-mount components on the bottom of the board. Both ceramic and polymer-based boards can be accommodated. reflow Reflow requires applying a controlled amount of solder and flux to the areas where connections are to be made. A common technique is to print a pattern of solder paste on the board, and then put the components onto their places. They tend to stay in position because of the stickiness of the paste. Optionally, components can be held with chip-bonding epoxy. When heat is applied, it must produce a time-temperature profile suitable for accomplishing several process steps. First, solvent evaporation is done at temperatures up to about l00o C. Second, flux reduces metal oxides as temperature rises to the solder melting point, typically l83o C. Third, as temperature continues to rise, the solder particles in the paste melt and wetting and wicking in the joint area begin. In the next step when temperature reaches a peak around 215o, surface tension shapes the fillet of fully molten solder. It takes only a few seconds for proper solder wetting at that temperature. The length of time that the work is actually above 200o is usually limited to one or two minutes to avoid damage. Many plastic encapsulated components can withstand several minutes of solder-melt temperature when re-flowed. Even at the higher temperature experienced in wave soldering such components tend to withstand several seconds immersion in molten solder. There are several techniques for applying the heat needed for re-flow. Two of the most common are infrared and vapor phase. Infrared heat sources operate at very high temperature and are placed at the inner walls of the chamber, not in contact with the work. The actual temperature of the work is strongly affected by its mass, geometry and composition, as well as bel speed. Organic materials such as epoxy-based boards tend to absorb the IR radiation and conduct the heat to metal parts which, by themselves, would tend to reflect the IR away. On the other hand, in the vapor-phase soldering process the vapor surrounding the work is maintained at the optimum solder-wetting temperature. This is accomplished by boiling an inert liquid in a tank. The boiling point is approximately 215o C. When the work is held in the vapor just above the liquid, the heat at that temperature is transferred to all surfaces quite uniformly&lt;/p&gt;
                            &lt;img src="http://feeds.feedburner.com/~r/EEWebAppDesignNotes/~4/hwS-zh3Uz2c" height="1" width="1"/&gt;</summary>
        <feedburner:origLink>http://www.eeweb.com/design-articles/practical-considerations-for-attaching-surface-mount-components/</feedburner:origLink></entry>
    
        <entry>
            <title>Serial Bootloader for PIC24F Devices</title>
            <link rel="alternate" href="http://feedproxy.google.com/~r/EEWebAppDesignNotes/~3/5EQY33HUvuA/" />
            <id>http://www.eeweb.com/design-articles/a-serial-bootloader-for-pic24f-devices/</id>
            <published>2013-05-10T15:32:20-07:00</published>
            <updated>2013-05-11T06:58:21-07:00</updated>
            <summary type="html">
                
                    &lt;p&gt;&lt;img src="http://d3i5bpxkxvwmz.cloudfront.net/resized/images/remote/http_s.eeweb.com/articles/2013/05/11/Serial-boot-loader-1368277101_300_258.png" alt="" width="300" height="258" /&gt;&lt;/p&gt;
                
                
                                    	&lt;p&gt;One of the advantages of Microchipís PICÆ microcontrollers with self-programmable enhanced Flash memory is the ability to implement a bootloader. This allows designers to implement applications that can be updated many times over, potentially extending the application ís useful lifetime. This application note describes a serial bootloader for 16-bit PIC24F devices using the &lt;span class="caps"&gt;&lt;span class="caps"&gt;UART&lt;/span&gt;&lt;/span&gt; module as a communication channel. The bootloader application uses the communication protocols originally outlined in Microchip Application Note AN851, ìA Flash Bootloader for PIC16 and PIC18 Devicesî. Some modifications to the original protocol have been made to maintain compatibility with the PIC24 architecture. It has also been redesigned to accommodate the current generation of PIC24FJ Flash microcontrollers, as well as the next generation of PIC24F devices. &lt;span class="caps"&gt;&lt;span class="caps"&gt;FIRMWARE&lt;/span&gt;&lt;/span&gt; Basic Operation. Data is received through the &lt;span class="caps"&gt;&lt;span class="caps"&gt;UART&lt;/span&gt;&lt;/span&gt; module and passed through the transmit/receive engine. The engine filters and parses the data, storing the information into a data buffer in &lt;span class="caps"&gt;&lt;span class="caps"&gt;RAM&lt;/span&gt;&lt;/span&gt;. The command interpreter evaluates the command information within the buffer to determine what should be done (e.g., Is the data written into memory? Is data read from memory? Does the firmware version need to be read?). Once the operation is performed, reply data is passed back to the transmit/receive engine to be transmitted back to the source, closing the software flow control loop.&lt;/p&gt;
                            &lt;img src="http://feeds.feedburner.com/~r/EEWebAppDesignNotes/~4/5EQY33HUvuA" height="1" width="1"/&gt;</summary>
        <feedburner:origLink>http://www.eeweb.com/design-articles/a-serial-bootloader-for-pic24f-devices/</feedburner:origLink></entry>
    
        <entry>
            <title>Powerline Communications for Street Lighting Automation</title>
            <link rel="alternate" href="http://feedproxy.google.com/~r/EEWebAppDesignNotes/~3/AlHp6bVJgLU/" />
            <id>http://www.eeweb.com/design-articles/powerline-communications-for-street-lighting-automation/</id>
            <published>2013-05-09T15:27:11-07:00</published>
            <updated>2013-05-15T23:07:12-07:00</updated>
            <summary type="html">
                
                    &lt;p&gt;&lt;img src="http://d3i5bpxkxvwmz.cloudfront.net/resized/images/remote/http_s.eeweb.com/articles/2013/04/25/Screen-Shot-2013-04-25-at-4.28.38-PM-1366929037_300_193.png" alt="" width="300" height="193" /&gt;&lt;/p&gt;
                
                
                                    	&lt;p&gt;Street lighting in its many forms—roadway lighting, tunnel lighting, car park lighting, and urban lighting— is a major consumer of electricity. All outdoor lighting is, in fact, estimated to comprise 19% of worldwide electricity usage today. For municipalities and businesses with large facilities, street lighting is a significant portion of operational expenses. Street lighting is also a vital part of public safety. Ensuring that street lights are reliably on and at the optimal illumination level for pedestrian and vehicle traffic is critical to public safety and the operators&amp;#8217; liability. As a result, any improvements to energy usage, operational reliability, and maintenance costs provide significant payback for the organizations responsible for that street lighting. There are, of course, obvious added benefits to the environment as energy usage is lowered. Powerline communication (&lt;span class="caps"&gt;&lt;span class="caps"&gt;PLC&lt;/span&gt;&lt;/span&gt;) is the natural choice for automating street lighting networks. &lt;span class="caps"&gt;&lt;span class="caps"&gt;PLC&lt;/span&gt;&lt;/span&gt; enables companies and municipalities to reduce operational costs and improve safety. G3-&lt;span class="caps"&gt;&lt;span class="caps"&gt;PLC&lt;/span&gt;&lt;/span&gt; is a new &lt;span class="caps"&gt;&lt;span class="caps"&gt;OFDM&lt;/span&gt;&lt;/span&gt;&lt;del&gt;based &lt;span class="caps"&gt;&lt;span class="caps"&gt;PLC&lt;/span&gt;&lt;/span&gt; system designed for grid automation that dramatically extends the range, data rate, and performance of powerline communications. This article discusses the benefits of a G3&lt;/del&gt;&lt;span class="caps"&gt;&lt;span class="caps"&gt;PLC&lt;/span&gt;&lt;/span&gt;-based automation system and presents a real-world example of a system for reducing energy usage and lowering maintenance costs in tunnels. The basic system design is explained and key performance parameters discussed. A transceiver optimized for &lt;span class="caps"&gt;&lt;span class="caps"&gt;PLC&lt;/span&gt;&lt;/span&gt; automation is presented.&lt;/p&gt;
                            &lt;img src="http://feeds.feedburner.com/~r/EEWebAppDesignNotes/~4/AlHp6bVJgLU" height="1" width="1"/&gt;</summary>
        <feedburner:origLink>http://www.eeweb.com/design-articles/powerline-communications-for-street-lighting-automation/</feedburner:origLink></entry>
    
        <entry>
            <title>Current Sense Circuit Collection</title>
            <link rel="alternate" href="http://feedproxy.google.com/~r/EEWebAppDesignNotes/~3/Ur382W7cV2s/" />
            <id>http://www.eeweb.com/design-articles/current-sense-circuit-collection/</id>
            <published>2013-05-08T15:16:15-07:00</published>
            <updated>2013-04-25T16:26:16-07:00</updated>
            <summary type="html">
                
                    &lt;p&gt;&lt;img src="http://d3i5bpxkxvwmz.cloudfront.net/resized/images/remote/http_s.eeweb.com/articles/2013/04/25/Screen-Shot-2013-04-25-at-4.20.23-PM-1366928776_300_210.png" alt="" width="300" height="210" /&gt;&lt;/p&gt;
                
                
                                    	&lt;p&gt;Sensing and/or controlling current flow is a fundamental requirement in many electronics systems, and the techniques to do so are as diverse as the applications themselves. This Application Note compiles solutions to current sensing problems and organizes the solutions by general application type. These circuits have been culled from a variety of Linear Technology documents. Circuits Organized by General Application  Each chapter collects together applications that tend to solve a similar general problem, such as high side current sensing, or negative supply sensing. The chapters  are titled accordingly (see “Circuit Collection Index” below).  It is unlikely that any particular circuit shown will exactly  meet the requirements for a specific design, but the suggestion of many circuit techniques and devices should  prove useful. Specific circuits may appear in several chapters if they have broad application.&lt;/p&gt;
                            &lt;img src="http://feeds.feedburner.com/~r/EEWebAppDesignNotes/~4/Ur382W7cV2s" height="1" width="1"/&gt;</summary>
        <feedburner:origLink>http://www.eeweb.com/design-articles/current-sense-circuit-collection/</feedburner:origLink></entry>
    
        <entry>
            <title>Loading Configuration Files in a Manufacturing Environment</title>
            <link rel="alternate" href="http://feedproxy.google.com/~r/EEWebAppDesignNotes/~3/5gGhit_F2jM/" />
            <id>http://www.eeweb.com/design-articles/loading-configuration-files-in-a-manufacturing-environment/</id>
            <published>2013-05-08T14:58:57-07:00</published>
            <updated>2013-04-25T16:14:58-07:00</updated>
            <summary type="html">
                
                    &lt;p&gt;&lt;img src="http://d3i5bpxkxvwmz.cloudfront.net/resized/images/remote/http_s.eeweb.com/articles/2013/04/25/Screen-Shot-2013-04-25-at-4.10.26-PM-1366928098_300_216.png" alt="" width="300" height="216" /&gt;&lt;/p&gt;
                
                
                                    	&lt;p&gt;The methodology for loading a configuration file into a Zilker Labs Digital-DC device during low-volume engineering  / validation phase and for the high-volume production phase is the same except for the hardware used to load the data  into the devices.  For the low-volume / validation phase, Zilker Labs has developed a socketed programming station called  &lt;span class="caps"&gt;&lt;span class="caps"&gt;ZLP&lt;/span&gt;&lt;/span&gt;rogrammer for loading configuration files. For high-volume production, industry standard programmers, such as  BP Microsystems programmers, are used to load configuration files. The available software tools and associated hardware are described later in this document.  In general, the steps for loading a configuration file into a Zilker Labs device are:  1. Using the PowerNavigator™ evaluation software, configure and optimize the design.  2. Save the configuration file.  3. Edit the configuration file using any text editor, adding Password and Operation commands, if required. See  AN33 for use of the Password and Operation commands.  4. If using a &lt;span class="caps"&gt;&lt;span class="caps"&gt;ZLP&lt;/span&gt;&lt;/span&gt;rogrammer, use the ConfigZL™ software to load the configuration file and configure devices. If  using a commercial programmer, follow step 5 below.  5. If using an industry standard production programming system, convert the configuration file to &lt;span class="caps"&gt;&lt;span class="caps"&gt;ASCII&lt;/span&gt;&lt;/span&gt; Hex  using &lt;span class="caps"&gt;&lt;span class="caps"&gt;ZLHLD&lt;/span&gt;&lt;/span&gt; Generator (Figure 5 shows a screen shot of the &lt;span class="caps"&gt;&lt;span class="caps"&gt;ZLHLD&lt;/span&gt;&lt;/span&gt; Generator and Figure 3 shows an  example of an output file).  6. In the event of a communication error, commercial programmer or &lt;span class="caps"&gt;&lt;span class="caps"&gt;ZLP&lt;/span&gt;&lt;/span&gt;rogrammer will provide an error message. &lt;/p&gt;
                            &lt;img src="http://feeds.feedburner.com/~r/EEWebAppDesignNotes/~4/5gGhit_F2jM" height="1" width="1"/&gt;</summary>
        <feedburner:origLink>http://www.eeweb.com/design-articles/loading-configuration-files-in-a-manufacturing-environment/</feedburner:origLink></entry>
    
        <entry>
            <title>Power MOSFET Basics</title>
            <link rel="alternate" href="http://feedproxy.google.com/~r/EEWebAppDesignNotes/~3/9oWfFYCWEIM/" />
            <id>http://www.eeweb.com/design-articles/power-mosfet-basics2/</id>
            <published>2013-05-06T14:49:29-07:00</published>
            <updated>2013-05-08T03:50:30-07:00</updated>
            <summary type="html">
                
                    &lt;p&gt;&lt;img src="http://d3i5bpxkxvwmz.cloudfront.net/resized/images/remote/http_s.eeweb.com/articles/2013/05/08/power-mosfet-1368006631_300_147.png" alt="Power MOSFET Basics" width="300" height="147" /&gt;&lt;/p&gt;
                
                
                                    	&lt;p&gt;Discrete power &lt;span class="caps"&gt;&lt;span class="caps"&gt;MOSFET&lt;/span&gt;&lt;/span&gt;s employ semiconductor processing techniques that are similar to those of today&amp;#8217;s &lt;span class="caps"&gt;&lt;span class="caps"&gt;VLSI&lt;/span&gt;&lt;/span&gt; circuits, although the device geometry, voltage and current levels are significantly different from the design used in &lt;span class="caps"&gt;&lt;span class="caps"&gt;VLSI&lt;/span&gt;&lt;/span&gt; devices. The metal oxide semiconductor field effect transistor (&lt;span class="caps"&gt;&lt;span class="caps"&gt;MOSFET&lt;/span&gt;&lt;/span&gt;) is based on the original field-effect transistor introduced in the 70s. The invention of the power &lt;span class="caps"&gt;&lt;span class="caps"&gt;MOSFET&lt;/span&gt;&lt;/span&gt; was partly driven by the limitations of bipolar power junction transistors (&lt;span class="caps"&gt;&lt;span class="caps"&gt;BJT&lt;/span&gt;&lt;/span&gt;s) which, until recently, was the device of choice in power electronics applications. Although it is not possible to define absolutely the operating boundaries of a power device, we will loosely refer to the power device as any device that can switch at least 1A. The bipolar power transistor is a current controlled device. A large base drive current as high as one-fifth of the collector current is required to keep the device in the ON state. Also, higher reverse base drive currents are required to obtain fast turn-off. Despite the very advanced state of manufacturability and lower costs of &lt;span class="caps"&gt;&lt;span class="caps"&gt;BJT&lt;/span&gt;&lt;/span&gt;s, these limitations have made the base drive circuit design more complicated and hence more expensive than the power &lt;span class="caps"&gt;&lt;span class="caps"&gt;MOSFET&lt;/span&gt;&lt;/span&gt;.&lt;/p&gt;
                            &lt;img src="http://feeds.feedburner.com/~r/EEWebAppDesignNotes/~4/9oWfFYCWEIM" height="1" width="1"/&gt;</summary>
        <feedburner:origLink>http://www.eeweb.com/design-articles/power-mosfet-basics2/</feedburner:origLink></entry>
    
        <entry>
            <title>Cyclic Redundant Checker Calculation</title>
            <link rel="alternate" href="http://feedproxy.google.com/~r/EEWebAppDesignNotes/~3/aa6JT_wCKDg/" />
            <id>http://www.eeweb.com/design-articles/cyclic-redundant-checker-calculation/</id>
            <published>2013-05-03T14:39:26-07:00</published>
            <updated>2013-04-25T15:47:27-07:00</updated>
            <summary type="html">
                
                    &lt;p&gt;&lt;img src="http://d3i5bpxkxvwmz.cloudfront.net/resized/images/remote/http_s.eeweb.com/articles/2013/04/25/Screen-Shot-2013-04-25-at-3.38.15-PM-1366926448_300_154.png" alt="" width="300" height="154" /&gt;&lt;/p&gt;
                
                
                                    	&lt;p&gt;Big-endian versus littleendian: what does it mean? The difference is in how data is stored in the memory. Little-endian stores low significant bytes in the lower addresses and big-endian stores more significant bytes in the lower addresses. The collision can appear when data is stored in big-endian but the device works with them in the little-endian or on the contrary. Formats in which data is stored and the device works are very important. Figure 2 shows data stored in big-endian but read in little-endian. It is visible that the number 0xA2E826EF is not equal to the 0xEF26E8A2. The same collision will appear when data would be stored in little-endian and the device works in big-endian.&lt;/p&gt;
                            &lt;img src="http://feeds.feedburner.com/~r/EEWebAppDesignNotes/~4/aa6JT_wCKDg" height="1" width="1"/&gt;</summary>
        <feedburner:origLink>http://www.eeweb.com/design-articles/cyclic-redundant-checker-calculation/</feedburner:origLink></entry>
    
        <entry>
            <title>Designing an Inverting Power Supply</title>
            <link rel="alternate" href="http://feedproxy.google.com/~r/EEWebAppDesignNotes/~3/A5sWwvInSug/" />
            <id>http://www.eeweb.com/design-articles/designing-an-inverting-power-supply/</id>
            <published>2013-05-02T14:28:36-07:00</published>
            <updated>2013-05-15T23:27:37-07:00</updated>
            <summary type="html">
                
                    &lt;p&gt;&lt;img src="http://d3i5bpxkxvwmz.cloudfront.net/resized/images/remote/http_s.eeweb.com/articles/2013/05/08/Designing-an-Inverting-Power-Supply-1368062982_300_123.png" alt="" width="300" height="123" /&gt;&lt;/p&gt;
                
                
                                    	&lt;p&gt;Applications such as bipolar amplifier, optical module, &lt;span class="caps"&gt;&lt;span class="caps"&gt;CCD&lt;/span&gt;&lt;/span&gt; bias, and &lt;span class="caps"&gt;&lt;span class="caps"&gt;OLED&lt;/span&gt;&lt;/span&gt; displays usually require a negative output voltage from  a positive input voltage. Designers of power management systems need versatile switching controllers and regulatorsthat allow them to solve these power management challenges. The ADP2384 and ADP2386 switching regulators from Analog Devices, Inc., provide synchronous buck functionality. This rangesfrom 20 V input voltage down to 0.6 V output voltage at up to 4 A for the ADP2384 and up to 6 A for the ADP2386 of output current at the switching frequency range of from 200 kHz to 1.4 MHz. Although targeted for synchronous step-down applications, the  versatility of the ADP2384 and ADP2386 allows these partsto  realize an inverting buck-boosttopology, which can generate a  negative output voltage from a positive input voltage, without  additional cost, component count, or solution size. In addition, the synchronous topology has certain advantages  over the asynchronous topology,such as higher efficiency at low  output voltages and lower noise at light load operation. The synchronous topology remains in continuous conduction mode (&lt;span class="caps"&gt;&lt;span class="caps"&gt;CCM&lt;/span&gt;&lt;/span&gt;) in both light load and heavy load operation while the  asynchronous topology encounters discontinuous conduction  mode (&lt;span class="caps"&gt;&lt;span class="caps"&gt;DCM&lt;/span&gt;&lt;/span&gt;) and pulse skip mode (&lt;span class="caps"&gt;&lt;span class="caps"&gt;PSM&lt;/span&gt;&lt;/span&gt;) with the decrease of the output load current, which can be noisier than &lt;span class="caps"&gt;&lt;span class="caps"&gt;CCM&lt;/span&gt;&lt;/span&gt;. This application notes describeshow to implement the ADP2384/ ADP2386 in a synchronous inverting buck-boost topology to  generate negative output voltages frompositive input power  supplies.In addition, some concerns and possible solutions are discussed.&lt;/p&gt;
                            &lt;img src="http://feeds.feedburner.com/~r/EEWebAppDesignNotes/~4/A5sWwvInSug" height="1" width="1"/&gt;</summary>
        <feedburner:origLink>http://www.eeweb.com/design-articles/designing-an-inverting-power-supply/</feedburner:origLink></entry>
    
        <entry>
            <title>NAND Flash Support in SAM3X Microcontrollers</title>
            <link rel="alternate" href="http://feedproxy.google.com/~r/EEWebAppDesignNotes/~3/QsyznvI6rZ0/" />
            <id>http://www.eeweb.com/design-articles/nand-flash-support-in-sam3x-microcontrollers/</id>
            <published>2013-05-01T14:18:16-07:00</published>
            <updated>2013-04-25T15:25:17-07:00</updated>
            <summary type="html">
                
                    &lt;p&gt;&lt;img src="http://d3i5bpxkxvwmz.cloudfront.net/resized/images/remote/http_s.eeweb.com/articles/2013/04/25/ARM-based-Flash-MCU-1366925089_300_205_75.jpg" alt="" width="300" height="205" /&gt;&lt;/p&gt;
                
                
                                    	&lt;p&gt;The purpose of this application note is to introduce the &lt;span class="caps"&gt;&lt;span class="caps"&gt;NAND&lt;/span&gt;&lt;/span&gt; Flash memory technology and describe hardware and software requirements to interface &lt;span class="caps"&gt;&lt;span class="caps"&gt;NAND&lt;/span&gt;&lt;/span&gt; Flash memory with Atmel® SAM3X ARM® Cortex-M3®-based Microcontrollers that features an Embedded &lt;span class="caps"&gt;&lt;span class="caps"&gt;NAND&lt;/span&gt;&lt;/span&gt; Flash Controller. The SAM3X microcontroller family features an External Bus Interface (&lt;span class="caps"&gt;&lt;span class="caps"&gt;EBI&lt;/span&gt;&lt;/span&gt;) providing &lt;span class="caps"&gt;&lt;span class="caps"&gt;NAND&lt;/span&gt;&lt;/span&gt; Flash protocol support via the Static Memory Controller (&lt;span class="caps"&gt;&lt;span class="caps"&gt;SMC&lt;/span&gt;&lt;/span&gt;) and embedded &lt;span class="caps"&gt;&lt;span class="caps"&gt;NAND&lt;/span&gt;&lt;/span&gt; Flash Controller. It also contains an Error Corrected Code Controller (&lt;span class="caps"&gt;&lt;span class="caps"&gt;ECC&lt;/span&gt;&lt;/span&gt;) which performs data error identification and single bit correction.&lt;/p&gt;
                            &lt;img src="http://feeds.feedburner.com/~r/EEWebAppDesignNotes/~4/QsyznvI6rZ0" height="1" width="1"/&gt;</summary>
        <feedburner:origLink>http://www.eeweb.com/design-articles/nand-flash-support-in-sam3x-microcontrollers/</feedburner:origLink></entry>
    
        <entry>
            <title>Calibrating a Three-Phase Energy Meter Based on the ADE7880</title>
            <link rel="alternate" href="http://feedproxy.google.com/~r/EEWebAppDesignNotes/~3/zShLdVpZfDQ/" />
            <id>http://www.eeweb.com/design-articles/calibrating-a-three-phase-energy-meter-based-on-the-ade7880/</id>
            <published>2013-04-24T09:35:30-07:00</published>
            <updated>2013-05-05T07:41:31-07:00</updated>
            <summary type="html">
                
                    &lt;p&gt;&lt;img src="http://d3i5bpxkxvwmz.cloudfront.net/resized/images/remote/http_s.eeweb.com/articles/2013/03/25/Calibrating-a-Three-Phase-Energy-Meter-Based-on-the-ADE7880-1364230155_300_209_75.jpg" alt="Calibrating a Three-Phase Energy Meter Based on the ADE7880" width="300" height="209" /&gt;&lt;/p&gt;
                
                
                                    	&lt;p&gt;The ADE7880 is a high accuracy, 3-phase electrical energy  measurement IC with serial interfaces and three flexible  pulse outputs. The ADE7880 device incorporates second order sigma-delta (Σ-Δ) analog-to-digital converters (&lt;span class="caps"&gt;&lt;span class="caps"&gt;ADC&lt;/span&gt;&lt;/span&gt;s),  a digital integrator, reference circuitry, and all of the signal  processing required to perform the total (fundamental and harmonic) active, and apparent energy measurements, rms calculations, as well as fundamental-only active and reactive energy measurements. In addition, the ADE7880 computes the rms of harmonics on the phase and neutral  currents and on the phase voltages, together with the active, reactive, and apparent powers, and the power factor and harmonic distortion on each harmonic for all phases. Total harmonic distortion plus noise (&lt;span class="caps"&gt;&lt;span class="caps"&gt;THD&lt;/span&gt;&lt;/span&gt; + N) is computed for all currents and voltages. &lt;/p&gt;
                            &lt;img src="http://feeds.feedburner.com/~r/EEWebAppDesignNotes/~4/zShLdVpZfDQ" height="1" width="1"/&gt;</summary>
        <feedburner:origLink>http://www.eeweb.com/design-articles/calibrating-a-three-phase-energy-meter-based-on-the-ade7880/</feedburner:origLink></entry>
    
        <entry>
            <title>Using the Transceiver Reconfiguration Controller for Dynamic Reconfiguration in Arria V and Cyclone</title>
            <link rel="alternate" href="http://feedproxy.google.com/~r/EEWebAppDesignNotes/~3/wXwlWzX1JAA/" />
            <id>http://www.eeweb.com/design-articles/using-the-transceiver-reconfiguration-controller-for-dynamic-reconfiguratio/</id>
            <published>2013-04-23T09:25:01-07:00</published>
            <updated>2013-03-25T10:35:02-07:00</updated>
            <summary type="html">
                
                    &lt;p&gt;&lt;img src="http://d3i5bpxkxvwmz.cloudfront.net/resized/images/remote/http_s.eeweb.com/articles/2013/03/25/Using-the-Transceiver-Reconfiguration-Controller-for-Dynamic-Reconfiguration-1364229302_300_179.png" alt="Using the Transceiver Reconfiguration Controller for Dynamic Reconfiguration in Arria V and Cyclone" width="300" height="179" /&gt;&lt;/p&gt;
                
                
                                    	&lt;p&gt;The Altera® Transceiver Reconfiguration Controller dynamically reconfigures the transceiver &lt;span class="caps"&gt;&lt;span class="caps"&gt;PHY&lt;/span&gt;&lt;/span&gt; in Arria® V and Cyclone® V devices. You can use the dynamic reconfiguration features to reconfigure the transceiver channels to support multiple or different data rates and physical medium attachment (&lt;span class="caps"&gt;&lt;span class="caps"&gt;PMA&lt;/span&gt;&lt;/span&gt;) settings without interrupting adjacent transceiver channels or powering down the transceiver channels. The reconfiguration methods are similar between Arria V, Cyclone V, and Stratix® V devices. The features supported in Arria V and Cyclone V devices are a subset of those supported in Stratix V devices. You can dynamically change the transceiver setting using either register-based or streamer-based reconfiguration. Both methods use a sequence of Avalon® -MM writes and reads to update the transceiver settings.&lt;/p&gt;
                            &lt;img src="http://feeds.feedburner.com/~r/EEWebAppDesignNotes/~4/wXwlWzX1JAA" height="1" width="1"/&gt;</summary>
        <feedburner:origLink>http://www.eeweb.com/design-articles/using-the-transceiver-reconfiguration-controller-for-dynamic-reconfiguratio/</feedburner:origLink></entry>
    
        <entry>
            <title>Getting Started with the AT91SAM9263 Microcontroller</title>
            <link rel="alternate" href="http://feedproxy.google.com/~r/EEWebAppDesignNotes/~3/FbicIFhYFZU/" />
            <id>http://www.eeweb.com/design-articles/getting-started-with-the-at91sam9263-microcontroller1/</id>
            <published>2013-04-23T07:17:37-07:00</published>
            <updated>2013-03-25T10:25:38-07:00</updated>
            <summary type="html">
                
                    &lt;p&gt;&lt;img src="http://d3i5bpxkxvwmz.cloudfront.net/resized/images/remote/http_s.eeweb.com/articles/2013/03/25/Getting-Started-with-the-AT91SAM9263-Microcontroller-1364228713_300_165.png" alt="" width="300" height="165" /&gt;&lt;/p&gt;
                
                
                                    	&lt;p&gt;This application note is intended as an aid in familiarizing the user with the Atmel ARM® Cortex® M3-based SAM3N series of microcontrollers. It describes in detail a simple project that uses several important features present on the SAM3N &lt;span class="caps"&gt;&lt;span class="caps"&gt;MCU&lt;/span&gt;&lt;/span&gt;, including how to set up the microcontroller prior to executing the application, as well as adding functionality. After examination of this application note, the reader should be able to successfully start a new project from scratch. This application note also explains how to setup and use a &lt;span class="caps"&gt;&lt;span class="caps"&gt;GNU&lt;/span&gt;&lt;/span&gt; &lt;span class="caps"&gt;&lt;span class="caps"&gt;ARM&lt;/span&gt;&lt;/span&gt; toolchain in order to compile and run a software project. Note that the getting started example has been ported and is included in IAR® Embedded Workbench for &lt;span class="caps"&gt;&lt;span class="caps"&gt;ARM&lt;/span&gt;&lt;/span&gt; (&lt;span class="caps"&gt;&lt;span class="caps"&gt;EWARM&lt;/span&gt;&lt;/span&gt;) and Keil® &lt;span class="caps"&gt;&lt;span class="caps"&gt;MDK&lt;/span&gt;&lt;/span&gt;-&lt;span class="caps"&gt;&lt;span class="caps"&gt;ARM&lt;/span&gt;&lt;/span&gt; development kit. &lt;/p&gt;
                            &lt;img src="http://feeds.feedburner.com/~r/EEWebAppDesignNotes/~4/FbicIFhYFZU" height="1" width="1"/&gt;</summary>
        <feedburner:origLink>http://www.eeweb.com/design-articles/getting-started-with-the-at91sam9263-microcontroller1/</feedburner:origLink></entry>
    
        <entry>
            <title>Getting Started with the AT91SAM9263 Microcontroller</title>
            <link rel="alternate" href="http://feedproxy.google.com/~r/EEWebAppDesignNotes/~3/ft_iDt9lqKc/" />
            <id>http://www.eeweb.com/design-articles/getting-started-with-the-at91sam9263-microcontroller/</id>
            <published>2013-04-23T07:17:10-07:00</published>
            <updated>2013-03-25T10:25:11-07:00</updated>
            <summary type="html">
                
                    &lt;p&gt;&lt;img src="http://d3i5bpxkxvwmz.cloudfront.net/resized/images/remote/http_s.eeweb.com/articles/2013/03/25/Getting-Started-with-the-AT91SAM9263-Microcontroller-1364228711_300_165.png" alt="" width="300" height="165" /&gt;&lt;/p&gt;
                
                
                                    	&lt;p&gt;This application note is intended as an aid in familiarizing the user with the Atmel ARM® Cortex® M3-based SAM3N series of microcontrollers. It describes in detail a simple project that uses several important features present on the SAM3N &lt;span class="caps"&gt;&lt;span class="caps"&gt;MCU&lt;/span&gt;&lt;/span&gt;, including how to set up the microcontroller prior to executing the application, as well as adding functionality. After examination of this application note, the reader should be able to successfully start a new project from scratch. This application note also explains how to setup and use a &lt;span class="caps"&gt;&lt;span class="caps"&gt;GNU&lt;/span&gt;&lt;/span&gt; &lt;span class="caps"&gt;&lt;span class="caps"&gt;ARM&lt;/span&gt;&lt;/span&gt; toolchain in order to compile and run a software project. Note that the getting started example has been ported and is included in IAR® Embedded Workbench for &lt;span class="caps"&gt;&lt;span class="caps"&gt;ARM&lt;/span&gt;&lt;/span&gt; (&lt;span class="caps"&gt;&lt;span class="caps"&gt;EWARM&lt;/span&gt;&lt;/span&gt;) and Keil® &lt;span class="caps"&gt;&lt;span class="caps"&gt;MDK&lt;/span&gt;&lt;/span&gt;-&lt;span class="caps"&gt;&lt;span class="caps"&gt;ARM&lt;/span&gt;&lt;/span&gt; development kit. &lt;/p&gt;
                            &lt;img src="http://feeds.feedburner.com/~r/EEWebAppDesignNotes/~4/ft_iDt9lqKc" height="1" width="1"/&gt;</summary>
        <feedburner:origLink>http://www.eeweb.com/design-articles/getting-started-with-the-at91sam9263-microcontroller/</feedburner:origLink></entry>
    
        <entry>
            <title>The Truth About the Fidelity of High-Bandwidth Voltage Probes</title>
            <link rel="alternate" href="http://feedproxy.google.com/~r/EEWebAppDesignNotes/~3/zA8WoJMg6wY/" />
            <id>http://www.eeweb.com/design-articles/the-truth-about-the-fidelity-of-high-bandwidth-voltage-probes/</id>
            <published>2013-04-22T08:13:49-07:00</published>
            <updated>2013-03-25T09:26:50-07:00</updated>
            <summary type="html">
                
                    &lt;p&gt;&lt;img src="http://d3i5bpxkxvwmz.cloudfront.net/resized/images/remote/http_s.eeweb.com/articles/2013/03/25/The-Truth-About-the-Fidelity-of-High-Bandwidth-Voltage-Probes-1364225210_300_173_75.jpg" alt="" width="300" height="173" /&gt;&lt;/p&gt;
                
                
                                    	&lt;p&gt;This application note is intended for users of highbandwidth voltage probes. It presents an analysis of high-bandwidth voltage probes that is detailed enough to accurately describe their behavior, yet is  simple enough to maintain a clear understanding  of what is going on and why. The analysis reveals a  fundamental tradeoff between fidelity and ease of use that exists with all high-bandwidth probes.  A new topology that alleviates this fundamental tradeoff will be presented, along with measurements that compare the new topology to older ones. Figure 1 shows a picture of a probe and oscilloscope measuring the voltage between a point on the leg of a surface-mounted device and a ground plane. First  of all, the exact location of the probe input needs to be clearly defined. When accessories such as pins or short wires are used to connect a probe to a circuit, the exact location of the probe input can become ambiguous. Is it on the probe side or the circuit side of a short wire? What is being  measured is the voltage between two points on a circuit, hence the input of the measuring device is, by definition, at the points where the probe connects to the circuit. &lt;/p&gt;
                            &lt;img src="http://feeds.feedburner.com/~r/EEWebAppDesignNotes/~4/zA8WoJMg6wY" height="1" width="1"/&gt;</summary>
        <feedburner:origLink>http://www.eeweb.com/design-articles/the-truth-about-the-fidelity-of-high-bandwidth-voltage-probes/</feedburner:origLink></entry>
    
        <entry>
            <title>High Precision Calibration of a  Three-Axis Accelerometer</title>
            <link rel="alternate" href="http://feedproxy.google.com/~r/EEWebAppDesignNotes/~3/bo13B-yfW4U/" />
            <id>http://www.eeweb.com/design-articles/high-precision-calibration-of-a-three-axis-accelerometer/</id>
            <published>2013-04-11T15:38:42-07:00</published>
            <updated>2013-03-22T15:26:43-07:00</updated>
            <summary type="html">
                
                    &lt;p&gt;&lt;img src="http://d3i5bpxkxvwmz.cloudfront.net/resized/images/remote/http_s.eeweb.com/articles/2013/03/22/Three-axis-accelerometer-1363991161_300_157.png" alt="" width="300" height="157" /&gt;&lt;/p&gt;
                
                
                                    	&lt;p&gt;Three-axis accelerometers supplied for the consumer  market are typically calibrated by the sensor  manufacturer using a six-element linear model  comprising a gain and offset in each of the three axes. This factory calibration will change slightly as a result of  the thermal stresses during soldering of the accelerometer to the circuit board. Additional small errors, external to the accelerometer, including rotation of the accelerometer package relative to the circuit board and misalignment of the circuit board to the final  product, will also be introduced during the soldering and  final assembly process. The original factory accelerometer calibration will still be adequate for the vast majority of consumer  applications. Manufacturers of premium products  looking to obtain improved accuracy from a consumer  accelerometer may, however, wish to perform their own  calibration either by repeating the calibration performed  by the accelerometer manufacturer or by using a more sophisticated calibration model.&lt;/p&gt;
                            &lt;img src="http://feeds.feedburner.com/~r/EEWebAppDesignNotes/~4/bo13B-yfW4U" height="1" width="1"/&gt;</summary>
        <feedburner:origLink>http://www.eeweb.com/design-articles/high-precision-calibration-of-a-three-axis-accelerometer/</feedburner:origLink></entry>
    
        <entry>
            <title>OpAmps for MEMS Microphone Preamp Circuits</title>
            <link rel="alternate" href="http://feedproxy.google.com/~r/EEWebAppDesignNotes/~3/o0mWh1LIg0Y/" />
            <id>http://www.eeweb.com/design-articles/opamps-for-mems-microphone-preamp-circuits/</id>
            <published>2013-04-09T10:48:45-07:00</published>
            <updated>2013-05-16T00:02:47-07:00</updated>
            <summary type="html">
                
                    &lt;p&gt;&lt;img src="http://d3i5bpxkxvwmz.cloudfront.net/resized/images/remote/http_s.eeweb.com/articles/2013/03/22/OpAmps-for-MEMS-Microphone-Preamp-Circuits-1363971292_300_221_75.jpg" alt="" width="300" height="221" /&gt;&lt;/p&gt;
                
                
                                    	&lt;p&gt;A microphone preamp circuit is used to amplify a microphone’s output signal to match the input level of the devices following it  in the signal chain. Matching the peaks of the microphone’s signal  level to the full-scale input voltage of an &lt;span class="caps"&gt;&lt;span class="caps"&gt;ADC&lt;/span&gt;&lt;/span&gt; makes maximum use of the ADC’s dynamic range and reduces the noise that  subsequent processing may add to the signal.  A single op amp can be easily used in a circuit as a preamp for a  &lt;span class="caps"&gt;&lt;span class="caps"&gt;MEMS&lt;/span&gt;&lt;/span&gt; microphone output. The &lt;span class="caps"&gt;&lt;span class="caps"&gt;MEMS&lt;/span&gt;&lt;/span&gt; microphone is a single ended output device, so a single op amp stage can be used to add  gain to the microphone signal or just to buffer the output.  This application note covers some of the key op amp specifications to consider in a preamp design, shows a few basic circuits, and provides a table of Analog Devices, Inc., op amps that may be  appropriate for a preamp design. The &lt;span class="caps"&gt;&lt;span class="caps"&gt;ADMP&lt;/span&gt;&lt;/span&gt; 504 &lt;span class="caps"&gt;&lt;span class="caps"&gt;MEMS&lt;/span&gt;&lt;/span&gt; microphone is used as an example in this application note to describe  different design choices. This is an analog microphone with  65 dB &lt;span class="caps"&gt;&lt;span class="caps"&gt;SNR&lt;/span&gt;&lt;/span&gt;. Designs using different microphones may require  adjustment from whatis described in this application note,  depending on the microphone noise, sensitivity, maximum  acoustic input and other specifications. For more information on  Analog Devices &lt;span class="caps"&gt;&lt;span class="caps"&gt;MEMS&lt;/span&gt;&lt;/span&gt; microphones, see &lt;a href="http://www.analog.com/mic"&gt;http://www.analog.com/mic&lt;/a&gt;.  An op amp data sheet has many different specifications and  performance graphs, so it can be overwhelming to try to find  exactly which of these specs matter for your application. For a  microphone preamp design, there are a few specs that matter  more than others; these specs are reviewed here.  Noise An op amp’s noise spec is given for both voltage noise and  current noise. Typically, you only need to concern yourself with  an op amp’s voltage noise in a preamp design. The current noise  becomes limiting in the design only when high value (that is,  noisy) resistors are used. To keep the overall noise of the circuit  low, typically resistors with values less than 10 kΩ are used.  The voltage noise of an op amp is specified as a noise density unit of nV/√Hz. To get the device noise in the circuit’s  bandwidth of interest, you need to multiply this noise density  by the square root of the bandwidth.&lt;/p&gt;
                            &lt;img src="http://feeds.feedburner.com/~r/EEWebAppDesignNotes/~4/o0mWh1LIg0Y" height="1" width="1"/&gt;</summary>
        <feedburner:origLink>http://www.eeweb.com/design-articles/opamps-for-mems-microphone-preamp-circuits/</feedburner:origLink></entry>
    
        <entry>
            <title>High-Speed Link Tuning Using Signal Conditioning Circuitry in Stratix V Transceivers</title>
            <link rel="alternate" href="http://feedproxy.google.com/~r/EEWebAppDesignNotes/~3/7Wi0nxzy8JA/" />
            <id>http://www.eeweb.com/design-articles/high-speed-link-tuning-using-signal-conditioning-circuitry-in-stratix-v-tra/</id>
            <published>2013-04-08T01:00:58-07:00</published>
            <updated>2013-03-22T09:47:59-07:00</updated>
            <summary type="html">
                
                    &lt;p&gt;&lt;img src="http://d3i5bpxkxvwmz.cloudfront.net/resized/images/remote/http_s.eeweb.com/articles/2013/03/22/Circuitry-in-Stratix-V-Transceivers-1363970454_300_210_75.jpg" alt="" width="300" height="210" /&gt;&lt;/p&gt;
                
                
                                    	&lt;p&gt;Backplane systems introduce insertion loss, reflections, and crosstalk to channel data, which degrade the signal&amp;#8217;s integrity. All of the above losses reduce the eye opening at the receiver (RX). The non-uniform loss over frequencies also causes inter-symbol interference (&lt;span class="caps"&gt;&lt;span class="caps"&gt;ISI&lt;/span&gt;&lt;/span&gt;). Stratix V transceivers are designed with link tuning features to handle channel degradation for data rates up to 12.5 Gbps. The link tuning features are as follows: • Programmable transmitter (TX) voltage output differential (&lt;span class="caps"&gt;&lt;span class="caps"&gt;VOD&lt;/span&gt;&lt;/span&gt;) and pre-emphasis • Continuous time linear equalizer (&lt;span class="caps"&gt;&lt;span class="caps"&gt;CTLE&lt;/span&gt;&lt;/span&gt;) or adaptive equalizer (&lt;span class="caps"&gt;&lt;span class="caps"&gt;AEQ&lt;/span&gt;&lt;/span&gt;) • Decision feedback equalizer (&lt;span class="caps"&gt;&lt;span class="caps"&gt;DFE&lt;/span&gt;&lt;/span&gt;).&lt;/p&gt;
                            &lt;img src="http://feeds.feedburner.com/~r/EEWebAppDesignNotes/~4/7Wi0nxzy8JA" height="1" width="1"/&gt;</summary>
        <feedburner:origLink>http://www.eeweb.com/design-articles/high-speed-link-tuning-using-signal-conditioning-circuitry-in-stratix-v-tra/</feedburner:origLink></entry>
    
</feed>
