<?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>SD Assert (id 0x01, pc 0x24726) on s132 v6.1.0, SDK v15.2</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/46754/sd-assert-id-0x01-pc-0x24726-on-s132-v6-1-0-sdk-v15-2</link><description>Hi, 
 I&amp;#39;m developing an application using the timeslot API for a custom radio protocol. The application also uses a number of the nRF52832 peripherals, as well as the app_scheduler library. L ately I have been updating my timeslot code and I keep getting</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 30 Apr 2019 12:33:32 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/46754/sd-assert-id-0x01-pc-0x24726-on-s132-v6-1-0-sdk-v15-2" /><item><title>RE: SD Assert (id 0x01, pc 0x24726) on s132 v6.1.0, SDK v15.2</title><link>https://devzone.nordicsemi.com/thread/184574?ContentTypeID=1</link><pubDate>Tue, 30 Apr 2019 12:33:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f2c5bd54-f8d9-4c28-bfc9-813dd28d41e7</guid><dc:creator>Fredrik</dc:creator><description>&lt;p&gt;Thanks, that&amp;#39;s all I needed to know.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SD Assert (id 0x01, pc 0x24726) on s132 v6.1.0, SDK v15.2</title><link>https://devzone.nordicsemi.com/thread/184572?ContentTypeID=1</link><pubDate>Tue, 30 Apr 2019 12:23:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:faa7e411-a7ca-470f-800a-a0738a6026a9</guid><dc:creator>Sigurd</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;The assert pc value indicates that you have spent too much time in the timeslot. From the SDS, see &lt;a href="https://infocenter.nordicsemi.com/topic/sds_s132/SDS/s1xx/concurrent_multiprotocol_tsl_api/ending_tsl_in_time.html?cp=3_4_1_0_8_1_6_4"&gt;this link&lt;/a&gt;, &amp;quot;The application is responsible for keeping track of timing within the Radio Timeslot and for ensuring that the application’s use of the peripherals does not last for longer than the granted timeslot length.&amp;quot;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>