<?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>Raw radio access in MCUBoot which is based on Zephyr causes strang behavior</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/48275/raw-radio-access-in-mcuboot-which-is-based-on-zephyr-causes-strang-behavior</link><description>Hi, radio experts here. Due to some limited conditions I have to implement one custom radio communication pattern in MCUBoot, not the BLE stack which is a bit too heavy for a bootloader. I am using PCA-10040 DK for my experiment. The strange thing is</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 10 Jun 2019 02:55:44 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/48275/raw-radio-access-in-mcuboot-which-is-based-on-zephyr-causes-strang-behavior" /><item><title>RE: Raw radio access in MCUBoot which is based on Zephyr causes strang behavior</title><link>https://devzone.nordicsemi.com/thread/191763?ContentTypeID=1</link><pubDate>Mon, 10 Jun 2019 02:55:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:80081fd5-ecc2-4f8d-b962-e4b44a483ada</guid><dc:creator>summer</dc:creator><description>&lt;p&gt;Problem solved! Thank you!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Raw radio access in MCUBoot which is based on Zephyr causes strang behavior</title><link>https://devzone.nordicsemi.com/thread/191403?ContentTypeID=1</link><pubDate>Thu, 06 Jun 2019 13:49:02 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a60c824e-a00e-4fe7-9c5c-2540d9131895</guid><dc:creator>Joakim Andersson</dc:creator><description>&lt;p&gt;You should request the HFCLK through the clock subsystem API. When you are using the RC oscillator as your LF, it needs to calibrate periodically from the HFCLK, when it has finished this it will turn the HFCLK off if no-one else is using it.&lt;br /&gt;So in other words, you need to register yourself as a user of the HFCLK.&lt;/p&gt;
&lt;p&gt;Replace this with a call to clock control driver:&lt;br /&gt;void hal_clock_hfclk_enable(void)&lt;br /&gt;{&lt;br /&gt; NRF_CLOCK-&amp;gt;EVENTS_HFCLKSTARTED = 0;&lt;br /&gt; NRF_CLOCK-&amp;gt;TASKS_HFCLKSTART = 1;&lt;br /&gt; while( NRF_CLOCK-&amp;gt;EVENTS_HFCLKSTARTED == 0 );&lt;br /&gt;}&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;err = clock_control_on(device_get_binding(DT_NORDIC_NRF_CLOCK_0_LABEL &amp;quot;_16M&amp;quot;);, (void *)1);&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>