element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet & Tria Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • About Us
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      • Japan
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Vietnam
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Freedom development platform
  • Products
  • Dev Tools
  • Freedom development platform
  • More
  • Cancel
Freedom development platform
Blog ADC performance with 16-bit accuracy for Kinetis MCU - Tips and Tricks
  • Blog
  • Forum
  • Documents
  • Files
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Freedom development platform to participate - click to join for free!
  • Share
  • More
  • Cancel
Group Actions
  • Group RSS
  • More
  • Cancel
Engagement
  • Author Author: bheemarao
  • Date Created: 9 Apr 2014 4:37 AM Date Created
  • Views 882 views
  • Likes 0 likes
  • Comments 5 comments
  • kinetis
Related
Recommended

ADC performance with 16-bit accuracy for Kinetis MCU - Tips and Tricks

bheemarao
bheemarao
9 Apr 2014

Kinetis ADC Optimization

Optimal ADC performance with 16-bit accuracy requires care to minimize sources of noise on the analog supplies and grounds, the ADC reference, and the input signal itself.

 

Static performance

This describes ADC error when converting on a static/DC input. A ramp test can be used to get linearity values.

 

DNL is “code width error”, where code width is the range of input voltages, VADIN, that result in a given ADC conversion value. To determine DNL accurately, we must sweep VADIN in increments much less than 1 LSB(V) and identify transition voltages where the ADC conversion value changes from code (x-1) to code x and from code x to code (x+1). Ideally, the delta in these transition voltages = code width x = 1 LSB(V), so DNL is the difference between the actual code with and the ideal 1 LSB(V). Note that DNL is measured for one conversion code independent of all other codes.

 

INL is the cumulative/integrated effect of all the DNL error from conversion code 1 up to the code of interest. For test purposes, once DNL is established for all codes, INL is simply the sum of all DNLs

 

Dynamic performance

This describes ADC error when converting on a continuously changing input. Dynamic performance (ENOB, SNR, SINAD, THD, etc) is determined by sampling a pure sine wave input, passing the raw data through an FFT (and window function depending on the setup), and using the FFT results to determine ratios of signal to noise and/or harmonic distortion.

 

There is no simple, straight-forward translation between DC and AC performance parameters, though there is a correlation between them. You cannot use one set of parameters to predict the other.

 

In terms of software there are several configurations that will depend on the application, these are some recommendations that will improve the ADC performance

  • Higher supply VREFH means larger LSB with more stable results
  • Slower system-core clock rates to minimize periodic noise. If the application allows it you can sample at VLPR
  • Lower ADC clock rates to allow more time for sampling and settling of comparator
  • Ambient, cold temperatures are better than hot for thermal noise
  • Use as much conversion averaging as allowed by sample requirements
  • Long sample time is better, as it allows more time for VIN to settle
  • Differential inputs buys performance because you’ll be subtracting system noise
  • Avoid conversions with high speed communications i.e. DDR, USB, serial
  • Perform ADC conversions in low-power modes for most “quiet” environment


Hardware

Ground and power supplies

  • We strongly recommend separate regulators for digital VDD and analog VDDA supplies, though they need to set to the same level.
  • No inductive coupling between VSS and VSSA
    • There has been success in using isolated digital and analog planes resistively coupled (0W) at a “starpoint” directly underneath VSSA pin/ball.
  • There should be two ground planes, one for digital and a second for analog. 
  • The board designer needs to avoid overlap of the digital ground plane with the analog ground plane
  • Analog signals and analog power should remain closely coupled with the analog ground plane.
  • Separate regulators for digital and analog supplies
  • Even better to provide an independent regulator for VREFH
  • Large “tank” caps at the regulator output for stability, decoupling caps of various values very close to the DUT. 10uF capacitors should be placed on power inputs (VDD, VDDAD, VREFH)


Inputs

  • Key for 16-bit performance only
  • Keep source resistance as low as possible. 
  • The differential inputs need to layed out in matched pairs in a side-to-side design.  Ground and power planes over the analog inputs should minimize through-hole vias to provide the best possible shield over the input signals.  
  • Differential pair traces should be as close together as allowed for. Use VDDA and AGND to build a sort of coax shield around the signal pairs and try to separate digital signals/power/ground from analog signals/power/ground.

                                   image

                                                                            Differential pair 3D diagram

  • For 16-bit performance, strongly consider buffering the inputs
  • An input buffer and low pass filter may be necessary for some ADC modules.  If the ADC input has a “kick-back” when sampling then an input buffer can reduce source impedance and source signal disruption.   Caution should be used when choosing an amplifier for buffer circuit to make sure the amplifier’s specifications matches or exceeds the ADC specifications.  Even a unity gain amplifier will have some gain and offset.  A means for trimming the buffer should be added to circuit.

 

  Trace routing

  • Keep digital traces away from analog supply, ADC reference, and ADC inputs.  This means vertically as well as horizontally (and will likely mean more layers for customer boards). 
  • Keep analog power and traces as short as possible

 

To summarize the ADC performance won’t be the optimal by just loading different software. It’s very depended to the application requirements and the amount of best practices in both hardware and software that can be adopted.

  • Sign in to reply
  • michaelkellett
    michaelkellett over 11 years ago in reply to bheemarao

    I looked at all those links and could find no specific references to ADCs (after a quick look).

    Can you be  a bit more specific and provide some more direct links to save me having to search through quite so much stuff.

     

    Thanks.

     

    MK

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • bheemarao
    bheemarao over 11 years ago in reply to michaelkellett

    Hello MK,

     

    The recommendations are a compilation of suggestions from speakers from PCB West, Clemson’s EMC research, as well as work done by Doug Smith and others (as a key part of improving ADC accuracy is reducing the EMC noise). I don’t have specific numbers available, but these tips have been used by customers and board designers to reach the accuracy they needed for their 16-bit ADC designs that they were failing to achieve with their original layouts.


    Regards

    Bheema Rao

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • michaelkellett
    michaelkellett over 11 years ago in reply to bheemarao

    Can you actually quote the "research done at universities" or actual results achieved - I'm forever hearing assertions that this or that is "best practice" but being an engineer not an artist I like to see evidence.

     

    MK

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • bheemarao
    bheemarao over 11 years ago in reply to michaelkellett

    Hi MK,


    There is of course a trade-off between optimal ADC accuracy and board cost. Depending on the application and the required accuracy, not all the suggestions need to be implemented to have acceptable ADC performance. Particularly for 12-bit performance, it can be acceptable with a minimum of special hardware considerations. These tips were created from experiences with designing analog circuits for high-accuracy 16-bit applications, as well as research done at universities, and should be seen as a “best practices” suggestions. The more recommendations that can be followed the better your results will be, and we’ve seen it help customers for high accuracy medical applications. But as you point out, they are not absolute requirements for using an ADC and are part of the spectrum of the art of analog design.


    Regards

    Bheema Rao

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • michaelkellett
    michaelkellett over 11 years ago

    This advice would be more convincing with some data to back it up. If all the harware suggestions are followed the cost of the ADC system is very significantly increased.

    In my experience with on chip 12 bit ADCs there is no advantage at all in using seperate supplies for the ADC or ADC ref, RC filtering worked just as well. (A 16 bit design might well be more sensitive than a 12 bit design.) In other applications (high end audio at 24 bit) no noise advantage resulted form separating digital and analogue ground planes.

     

    Have you any data that compares the performance from a cost optimised application with that from a performance optimised design ?

     

    MK

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2025 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube