<?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>nrf52832 custom board power on question</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/24310/nrf52832-custom-board-power-on-question</link><description>onkey_full_20170814.hex 
 onkey_0000.hex 
 onkey_boot_s132.hex 
This time 14.0 sdk was updated. 
 There was a problem after the update 
 Problems when uploading bootloader 
 
 custom board : remove 32.76khz cyristal 
 
 
 
 Power on -&amp;gt; do not</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 29 Sep 2017 06:56:43 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/24310/nrf52832-custom-board-power-on-question" /><item><title>RE: nrf52832 custom board power on question</title><link>https://devzone.nordicsemi.com/thread/95700?ContentTypeID=1</link><pubDate>Fri, 29 Sep 2017 06:56:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:90589705-f4e5-452e-974c-3ec62f986cd0</guid><dc:creator>bjorn-spockeli</dc:creator><description>&lt;p&gt;@lesher: Please create a new question and add a link to this question.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf52832 custom board power on question</title><link>https://devzone.nordicsemi.com/thread/95699?ContentTypeID=1</link><pubDate>Thu, 28 Sep 2017 20:09:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cd442752-1c1f-447d-8549-c98f94b4e047</guid><dc:creator>lesher</dc:creator><description>&lt;p&gt;Possibly similar issue: external 32k works on SD132v3/SDK12.2 - does not work on SD132v5/SDK14.0.  Internal RC does work on SD5. No bootloader involved.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf52832 custom board power on question</title><link>https://devzone.nordicsemi.com/thread/95718?ContentTypeID=1</link><pubDate>Tue, 22 Aug 2017 00:55:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d7993684-9df9-45a1-b371-688c38bc670d</guid><dc:creator>ytpark</dc:creator><description>&lt;p&gt;Fixed the above problem.&lt;/p&gt;
&lt;p&gt;The cause is the wrong setting of CLOCK_CONFIG_LF_SRC.&lt;/p&gt;
&lt;p&gt;#define CLOCK_CONFIG_LF_SRC 1 -&amp;gt; #define CLOCK_CONFIG_LF_SRC 0&lt;/p&gt;
&lt;p&gt;Thank you for your help so far.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf52832 custom board power on question</title><link>https://devzone.nordicsemi.com/thread/95717?ContentTypeID=1</link><pubDate>Mon, 21 Aug 2017 23:10:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fc9b4cfb-bc63-4bf0-8f63-b801d835ee50</guid><dc:creator>robotjosh</dc:creator><description>&lt;p&gt;Using the same options as bjorn pasted, I get a hard fault when the code runs.  The fault is for invalid instruction.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf52832 custom board power on question</title><link>https://devzone.nordicsemi.com/thread/95716?ContentTypeID=1</link><pubDate>Mon, 21 Aug 2017 21:01:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:66178fca-369e-476a-a3fc-fe2011cf5eae</guid><dc:creator>robotjosh</dc:creator><description>&lt;p&gt;I might be having this same problem.  Running on internal rc results in hard fault without the external crystal placed.  With external crystal placed, internal rc runs.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf52832 custom board power on question</title><link>https://devzone.nordicsemi.com/thread/95715?ContentTypeID=1</link><pubDate>Tue, 15 Aug 2017 12:22:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fd0c072d-7169-49e5-99d2-f7f3acc40a8c</guid><dc:creator>ytpark</dc:creator><description>&lt;p&gt;If I do not modify the bootloader(RC OSC), it will not work.&lt;/p&gt;
&lt;p&gt;After reset, not working&lt;/p&gt;
&lt;p&gt;Send me&lt;/p&gt;
&lt;p&gt;32khz removed boot loader file(with the RC OSC config) on sdk 14 base&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf52832 custom board power on question</title><link>https://devzone.nordicsemi.com/thread/95714?ContentTypeID=1</link><pubDate>Tue, 15 Aug 2017 12:06:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9a8525a3-976b-41b4-a0a6-decdf3355e1f</guid><dc:creator>bjorn-spockeli</dc:creator><description>&lt;p&gt;Can you check if the new bootloader.hex file( with the RC OSC config) runs on the custom board with no 32kHz crystal, i.e. advertises DfuTarg if you flash with the nRF52DK to the custom board together with the SoftDevice? Do the same for the application, i.e.e only flash the application and SoftDevice to the custom board without the 32kHz crystal. If both of them runs, i.e. advertises, then this is not a clock issue and it must be something else.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf52832 custom board power on question</title><link>https://devzone.nordicsemi.com/thread/95713?ContentTypeID=1</link><pubDate>Tue, 15 Aug 2017 11:54:05 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4b3359da-6742-467d-8104-6e3a39bd75d6</guid><dc:creator>ytpark</dc:creator><description>&lt;p&gt;Please refer to the video.&lt;/p&gt;
&lt;p&gt;softdevice : s132_nrf52_5.0.0 ,  bootloader based(SDK 13) -&amp;gt; power on -&amp;gt; working&lt;/p&gt;
&lt;p&gt;softdevice : s132_nrf52_5.0.0 ,  bootloader based(SDK14) -&amp;gt; power on -&amp;gt; not working(Operation at reset)&lt;/p&gt;
&lt;p&gt;&lt;a href="https://www.dropbox.com/s/ra1rz461bm3uk0g/KakaoTalk_Video_20170815_2033_55_673.mp4?dl=0"&gt;link text&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf52832 custom board power on question</title><link>https://devzone.nordicsemi.com/thread/95712?ContentTypeID=1</link><pubDate>Tue, 15 Aug 2017 11:46:25 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bed3458a-c712-4431-be92-e343e48fee9b</guid><dc:creator>bjorn-spockeli</dc:creator><description>&lt;p&gt;What firmware is present on the nRF52832 before you update the bootloader, i.e. which SDK is the bootloader based on and which SoftDevice version is present? Does the new bootloader.hex file run on the custom board if you flash it with a programmer( not perform a DFU)?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf52832 custom board power on question</title><link>https://devzone.nordicsemi.com/thread/95711?ContentTypeID=1</link><pubDate>Tue, 15 Aug 2017 11:33:20 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4e146c00-2cec-4731-9bda-9de1151767bf</guid><dc:creator>bjorn-spockeli</dc:creator><description>&lt;p&gt;log continued ...&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;&amp;lt;debug&amp;gt; nrf_sdh_soc: In nrf_dfu_transports_init
&amp;lt;debug&amp;gt; nrf_sdh_soc: num transports: 1
&amp;lt;debug&amp;gt; nrf_sdh_soc: Initializing BLE DFU transport
&amp;lt;debug&amp;gt; nrf_sdh_soc: vector table: 0x00073000
&amp;lt;debug&amp;gt; nrf_sdh_soc: vector table: 0x00073000
&amp;lt;debug&amp;gt; nrf_sdh_soc: Error code - sd_softdevice_vector_table_base_set: 0x00000000
&amp;lt;debug&amp;gt; nrf_sdh_soc: Enabling SoftDevice.
&amp;lt;warning&amp;gt; nrf_sdh: RAM start should be adjusted to 0x20002180.
&amp;lt;warning&amp;gt; nrf_sdh: RAM size should be adjusted to 0xDE80.
&amp;lt;debug&amp;gt; nrf_sdh_soc: SoftDevice enabled.
&amp;lt;debug&amp;gt; nrf_sdh_soc: nrf_dfu_settings_adv_name_is_valid FALSE
&amp;lt;debug&amp;gt; nrf_sdh_soc: Regular adv name
&amp;lt;debug&amp;gt; nrf_sdh_soc: #### Advertising NO BONDING ####
&amp;lt;debug&amp;gt; nrf_sdh_soc: Finished initializing BLE DFU transport
&amp;lt;debug&amp;gt; nrf_sdh_soc: After nrf_dfu_transports_init
&amp;lt;debug&amp;gt; nrf_sdh_ble: Calling nrf_dfu_flash_init(sd_irq_initialized=true)...
&amp;lt;debug&amp;gt; nrf_sdh_ble: Initializing nrf_fstorage_sd backend.
&amp;lt;debug&amp;gt; nrf_sdh_soc: Waiting for events
&lt;/code&gt;&lt;/pre&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf52832 custom board power on question</title><link>https://devzone.nordicsemi.com/thread/95704?ContentTypeID=1</link><pubDate>Tue, 15 Aug 2017 11:24:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d13bcbfb-db88-4285-abc3-468fa6f66465</guid><dc:creator>ytpark</dc:creator><description>&lt;p&gt;gcc version is 5.4 2016q3. After power on. When I do not connect jlink , board does not work, but whenjlink is connected, message appears indicating that the board is working:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;&amp;lt;info&amp;gt; nrf_sdh_soc: Inside main
&amp;lt;debug&amp;gt; nrf_sdh_soc: In nrf_bootloader_init
&amp;lt;debug&amp;gt; nrf_sdh_soc: in weak nrf_dfu_init_user
&amp;lt;debug&amp;gt; nrf_sdh_soc: In real nrf_dfu_init
&amp;lt;debug&amp;gt; mem_mngr: Running nrf_dfu_settings_init(sd_irq_initialized=false).
&amp;lt;debug&amp;gt; nrf_sdh_ble: Calling nrf_dfu_flash_init(sd_irq_initialized=false)...
&amp;lt;debug&amp;gt; nrf_sdh_ble: Initializing nrf_fstorage_nvmc backend.
&amp;lt;debug&amp;gt; nrf_sdh_soc: Initializing the clock.
&amp;lt;debug&amp;gt; nrf_sdh_soc: Enter nrf_dfu_continue
&amp;lt;error&amp;gt; nrf_sdh_soc: Single: Invalid bank
&amp;lt;debug&amp;gt; nrf_sdh_soc: Application sent bootloader request
&lt;/code&gt;&lt;/pre&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf52832 custom board power on question</title><link>https://devzone.nordicsemi.com/thread/95710?ContentTypeID=1</link><pubDate>Tue, 15 Aug 2017 10:26:37 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f03a43f0-f534-4607-969b-6ff8b499c2ae</guid><dc:creator>bjorn-spockeli</dc:creator><description>&lt;p&gt;Are you using Keil? Could you elaborate on what you see when you start a debug session, e.g. disassembly etc?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf52832 custom board power on question</title><link>https://devzone.nordicsemi.com/thread/95702?ContentTypeID=1</link><pubDate>Tue, 15 Aug 2017 08:59:24 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b20632b4-bda8-41ba-9d1c-98127c3de511</guid><dc:creator>ytpark</dc:creator><description>&lt;p&gt;Not debug the bootloader,&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf52832 custom board power on question</title><link>https://devzone.nordicsemi.com/thread/95703?ContentTypeID=1</link><pubDate>Tue, 15 Aug 2017 08:38:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2bb1207d-d1c9-428d-b353-4ce7edeff190</guid><dc:creator>bjorn-spockeli</dc:creator><description>&lt;p&gt;Do you mean that you can debug the bootloader, but not the application?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf52832 custom board power on question</title><link>https://devzone.nordicsemi.com/thread/95705?ContentTypeID=1</link><pubDate>Tue, 15 Aug 2017 00:42:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7af87a54-f2dc-4582-870a-42bc3fcb0361</guid><dc:creator>ytpark</dc:creator><description>&lt;p&gt;I applied nrf_sdh_ble_enable() in main.c.&lt;/p&gt;
&lt;p&gt;I can not debug.&lt;/p&gt;
&lt;p&gt;custom board is reset when connected to j-link-rttview and custom board run.&lt;/p&gt;
&lt;p&gt;bootloader debug mode -&amp;gt; jlink rtt viwe-&amp;gt; connnect -&amp;gt; reset -&amp;gt; run&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf52832 custom board power on question</title><link>https://devzone.nordicsemi.com/thread/95709?ContentTypeID=1</link><pubDate>Mon, 14 Aug 2017 11:41:05 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4adb4341-af2c-4e34-bfaf-7e898d46c8e2</guid><dc:creator>bjorn-spockeli</dc:creator><description>&lt;p&gt;The configuration in my answer, i.e. the internal RC configuration,  should work on both boards. Can you debug the board without the 32kHz crystal and see what kind of error code you get from &lt;code&gt;nrf_sdh_ble_enable()&lt;/code&gt; in main.c ?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf52832 custom board power on question</title><link>https://devzone.nordicsemi.com/thread/95708?ContentTypeID=1</link><pubDate>Mon, 14 Aug 2017 11:35:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7f71e9f4-e21f-40b9-9bd6-3480dab9310a</guid><dc:creator>ytpark</dc:creator><description>&lt;p&gt;my custom board is 2EA&lt;/p&gt;
&lt;p&gt;frist board 32khz remove : not run&lt;/p&gt;
&lt;p&gt;second board 32khz mount : run&lt;/p&gt;
&lt;p&gt;nrf_sdh.c change&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf52832 custom board power on question</title><link>https://devzone.nordicsemi.com/thread/95707?ContentTypeID=1</link><pubDate>Mon, 14 Aug 2017 11:19:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:034da673-f511-4e84-9f93-bb5dbde3abf6</guid><dc:creator>bjorn-spockeli</dc:creator><description>&lt;p&gt;You did not answer my first question: Does your custom board have the optional external 32kHz crystal mounted or not? Have you also implemented the change in &lt;code&gt;nrf_sdh.c&lt;/code&gt;, i.e.&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;nrf_clock_lf_cfg_t const clock_lf_cfg =
    {
        .source        = NRF_SDH_CLOCK_LF_SRC,
        .rc_ctiv       = NRF_SDH_CLOCK_LF_RC_CTIV,
        .rc_temp_ctiv  = NRF_SDH_CLOCK_LF_RC_TEMP_CTIV,
    #ifdef S132
        .accuracy      = NRF_SDH_CLOCK_LF_XTAL_ACCURACY
    #else
        .xtal_accuracy = NRF_SDH_CLOCK_LF_XTAL_ACCURACY
    #endif
    };
&lt;/code&gt;&lt;/pre&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf52832 custom board power on question</title><link>https://devzone.nordicsemi.com/thread/95706?ContentTypeID=1</link><pubDate>Mon, 14 Aug 2017 11:02:59 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f7b2b581-2169-41b1-8f70-df0899366401</guid><dc:creator>ytpark</dc:creator><description>&lt;p&gt;bootlaoder : &lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/7888.sdk_5F00_config.h"&gt;sdk_config.h&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;application : &lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/7536.sdk_5F00_config.h"&gt;sdk_config.h&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;full hex : &lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/onkey_5F00_full_5F00_20170814.hex"&gt;onkey_full_20170814.hex&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;I modified it as follows and symptoms are the same.&lt;/p&gt;
&lt;p&gt;examples\dfu\bootloader_secure_ble\pca10040\config\sdk_config.h
examples\ble_peripheral\ble_app_uart\pca10040\s132\config\sdk_config.h&lt;/p&gt;
&lt;p&gt;// &lt;/p&gt;
&lt;p&gt;#ifndef NRF_SDH_CLOCK_LF_SRC&lt;/p&gt;
&lt;p&gt;#define NRF_SDH_CLOCK_LF_SRC 0&lt;/p&gt;
&lt;p&gt;#endif&lt;/p&gt;
&lt;p&gt;#ifndef NRF_SDH_CLOCK_LF_RC_CTIV&lt;/p&gt;
&lt;p&gt;#define NRF_SDH_CLOCK_LF_RC_CTIV 16&lt;/p&gt;
&lt;p&gt;#endif&lt;/p&gt;
&lt;p&gt;#ifndef NRF_SDH_CLOCK_LF_RC_TEMP_CTIV&lt;/p&gt;
&lt;p&gt;#define NRF_SDH_CLOCK_LF_RC_TEMP_CTIV 2&lt;/p&gt;
&lt;p&gt;#endif&lt;/p&gt;
&lt;p&gt;#ifndef NRF_SDH_CLOCK_LF_XTAL_ACCURACY&lt;/p&gt;
&lt;p&gt;#define NRF_SDH_CLOCK_LF_XTAL_ACCURACY 0&lt;/p&gt;
&lt;p&gt;#endif&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf52832 custom board power on question</title><link>https://devzone.nordicsemi.com/thread/95701?ContentTypeID=1</link><pubDate>Mon, 14 Aug 2017 09:26:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:91d6b4c1-07dd-4466-baa5-b58f6c74d69d</guid><dc:creator>bjorn-spockeli</dc:creator><description>&lt;p&gt;Does your custom board have the optional external 32kHz crystal mounted or not? If you are physically removing the 32kHz crystal then you need to modify the code to use the internal RC oscillator instead of the external crystal, i.e. you must modify the SoftDevice clock configuration section in the sdk_config.h file to the following&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;// &amp;lt;/h&amp;gt; 
//========================================================== 
  
// &amp;lt;h&amp;gt; Clock - SoftDevice clock configuration 
  
//========================================================== 
// &amp;lt;o&amp;gt; NRF_SDH_CLOCK_LF_SRC  - SoftDevice clock source. 
  
// &amp;lt;0=&amp;gt; NRF_CLOCK_LF_SRC_RC 
// &amp;lt;1=&amp;gt; NRF_CLOCK_LF_SRC_XTAL 
// &amp;lt;2=&amp;gt; NRF_CLOCK_LF_SRC_SYNTH 
  
#ifndef NRF_SDH_CLOCK_LF_SRC 
#define NRF_SDH_CLOCK_LF_SRC 0 
#endif 
  
// &amp;lt;o&amp;gt; NRF_SDH_CLOCK_LF_RC_CTIV - SoftDevice calibration timer interval. 
#ifndef NRF_SDH_CLOCK_LF_RC_CTIV 
#define NRF_SDH_CLOCK_LF_RC_CTIV 16 
#endif 
  
// &amp;lt;o&amp;gt; NRF_SDH_CLOCK_LF_RC_TEMP_CTIV - SoftDevice calibration timer interval under constant temperature. 
// &amp;lt;i&amp;gt; How often (in number of calibration intervals) the RC oscillator shall be calibrated 
// &amp;lt;i&amp;gt;  if the temperature has not changed. 
  
#ifndef NRF_SDH_CLOCK_LF_RC_TEMP_CTIV 
#define NRF_SDH_CLOCK_LF_RC_TEMP_CTIV 2 
#endif 
  
// &amp;lt;o&amp;gt; NRF_SDH_CLOCK_LF_XTAL_ACCURACY  - External crystal clock accuracy used in the LL to compute timing windows. 
  
// &amp;lt;0=&amp;gt; NRF_CLOCK_LF_XTAL_ACCURACY_250_PPM 
// &amp;lt;1=&amp;gt; NRF_CLOCK_LF_XTAL_ACCURACY_500_PPM 
// &amp;lt;2=&amp;gt; NRF_CLOCK_LF_XTAL_ACCURACY_150_PPM 
// &amp;lt;3=&amp;gt; NRF_CLOCK_LF_XTAL_ACCURACY_100_PPM 
// &amp;lt;4=&amp;gt; NRF_CLOCK_LF_XTAL_ACCURACY_75_PPM 
// &amp;lt;5=&amp;gt; NRF_CLOCK_LF_XTAL_ACCURACY_50_PPM 
// &amp;lt;6=&amp;gt; NRF_CLOCK_LF_XTAL_ACCURACY_30_PPM 
// &amp;lt;7=&amp;gt; NRF_CLOCK_LF_XTAL_ACCURACY_20_PPM 
  
#ifndef NRF_SDH_CLOCK_LF_XTAL_ACCURACY 
#define NRF_SDH_CLOCK_LF_XTAL_ACCURACY 0
#endif
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;and  clock_lf_cfg should then be defined as:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;nrf_clock_lf_cfg_t const clock_lf_cfg =
    {
        .source        = NRF_SDH_CLOCK_LF_SRC,
        .rc_ctiv       = NRF_SDH_CLOCK_LF_RC_CTIV,
        .rc_temp_ctiv  = NRF_SDH_CLOCK_LF_RC_TEMP_CTIV,
    #ifdef S132
        .accuracy      = NRF_SDH_CLOCK_LF_XTAL_ACCURACY
    #else
        .xtal_accuracy = NRF_SDH_CLOCK_LF_XTAL_ACCURACY
    #endif
    };
&lt;/code&gt;&lt;/pre&gt;
&lt;h2&gt;&lt;strong&gt;Note:&lt;/strong&gt; This change must be done in &lt;strong&gt;both&lt;/strong&gt; the application and the bootloader code!&lt;/h2&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>