<?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>Custom board &amp;amp; SDK v14 bootloader</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/25376/custom-board-sdk-v14-bootloader</link><description>Hi. We recently upgraded from SDK13 to SDK14. All was well until we integrated the bootloader. We are using Laird&amp;#39;s BL652. We updated the bootloader&amp;#39;s config to use NRF_CLOCK_LF_SRC_RC, NRF_SDH_CLOCK_LF_RC_CTIV = 16, NRF_SDH_CLOCK_LF_RC_TEMP_CTIV = 2</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 22 Sep 2017 07:01:40 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/25376/custom-board-sdk-v14-bootloader" /><item><title>RE: Custom board &amp; SDK v14 bootloader</title><link>https://devzone.nordicsemi.com/thread/100008?ContentTypeID=1</link><pubDate>Fri, 22 Sep 2017 07:01:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5f631ee3-9ee5-4840-8329-afdfe6fcdd9e</guid><dc:creator>bjorn-spockeli</dc:creator><description>&lt;p&gt;No, not that I am aware of. Can you set a breakpoint after the lfclk_start() call in nrf_drv_clock_lfclk_request and then examine the CLOCK peripheral under Peripherals-&amp;gt;System Viewer-&amp;gt; CLOCK. Specifically see if the EVENTS_LFCLKSTARTED event is fired and if the LFCLKSTARTED bit is set in the INTENSET register,&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>