<?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>PPI related problems</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/71412/ppi-related-problems</link><description>Hello, 
 
 I have few questions about PPI. 
 ---------- 
 1. How to configure PPI channels that runs one after the other? If yes, is there any example? 
 Because I have two sensors connected together using TWI with different address. 
 
 2. Can one NRF_DRV_TIMER_INSTANCE</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 10 Feb 2021 02:52:43 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/71412/ppi-related-problems" /><item><title>RE: PPI related problems</title><link>https://devzone.nordicsemi.com/thread/293659?ContentTypeID=1</link><pubDate>Wed, 10 Feb 2021 02:52:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:56180d31-4991-4fec-ac0c-08cad4fa717e</guid><dc:creator>leo.lau</dc:creator><description>&lt;p&gt;Thank you for the quick reply.&lt;/p&gt;
&lt;p&gt;I am planning to increase sensors&amp;#39; sampling rate from 100Hz to 800Hz which combine 8 sets of data into&amp;nbsp;one sd_ble_gatts_hvx() packet in order to utilize ATT_MTU throughput. It will increases the power consumption if awaking CPU every timer interrupt to update pointer address. As your suggestion may be it is better to&amp;nbsp;&lt;span&gt;initiate&amp;nbsp;TWI transfer&amp;nbsp;using CPU to avoid the mentioned errata (which is my original approach). &lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Regards&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: PPI related problems</title><link>https://devzone.nordicsemi.com/thread/293386?ContentTypeID=1</link><pubDate>Mon, 08 Feb 2021 15:35:23 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:137d522f-4256-40cb-acd3-5c76272c095e</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I am not sure how autonomous you want this, but you should be aware of this errata:&lt;br /&gt;&lt;a href="https://infocenter.nordicsemi.com/topic/errata_nRF52832_Rev2/ERR/nRF52832/Rev2/latest/anomaly_832_109.html"&gt;https://infocenter.nordicsemi.com/topic/errata_nRF52832_Rev2/ERR/nRF52832/Rev2/latest/anomaly_832_109.html&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;To avoid the above somewhat tricky or power increase workaround, it may be easier to just always initiate the transfers from the CPU, this will ensure the above errata does not occur, and you also will have full control of which&amp;nbsp;sensor you read and write to. The delay due to CPU wakeup will be very (few us) short compared to the TWI transfer time.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;br /&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>