<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>SAADC acquisition time measurement</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/49014/saadc-acquisition-time-measurement</link><description>OS : Ubuntu 
 SDK: 15.3.0_59ac345 
 Base example : peripheral/saadc 
 HW : nRF52832 DK PCA10040 1.2.1 2017.49 682663245 
 
 Hello, i would like to make sure the ADC acquisition speed. 
 As seen in this post , it was recommended to use GPIOTE to toggle</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 26 Jun 2019 08:39:51 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/49014/saadc-acquisition-time-measurement" /><item><title>RE: SAADC acquisition time measurement</title><link>https://devzone.nordicsemi.com/thread/194794?ContentTypeID=1</link><pubDate>Wed, 26 Jun 2019 08:39:51 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:646e2cda-5593-4ea6-b4e5-1d410c3d81f8</guid><dc:creator>haakonsh</dc:creator><description>&lt;p&gt;The started event is triggered after the saadc driver has prepared the next buffer.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;You should use the sample task and the done event.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;Alternatively, you can connect the done event to the sample task, as well as toggling a gpiote pin with it. This will sample the SAADC as fast as it can.&lt;br /&gt;Remember to set a large buffer.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>