<?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>Problem S140 Soft Device on nRF52833</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/69151/problem-s140-soft-device-on-nrf52833</link><description>Good morning, 
 I&amp;#39;m trying to port the HTS to the PCA0056 board towards chip nRF52833. 
 I followed the guideline and modified memory mapping as follows: 
 Section Placement Macros: 
 FLASH_PH_START=0x0 
 FLASH_PH_SIZE=0x80000 
 RAM_PH_START=0x20000000</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 20 Jan 2021 07:26:38 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/69151/problem-s140-soft-device-on-nrf52833" /><item><title>RE: Problem S140 Soft Device on nRF52833</title><link>https://devzone.nordicsemi.com/thread/290123?ContentTypeID=1</link><pubDate>Wed, 20 Jan 2021 07:26:38 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d03c1128-5f97-4f7b-a117-5a2e6e2bf8c8</guid><dc:creator>Amanda Hsieh</dc:creator><description>&lt;p&gt;Hi Paolo,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Sorry for the delay and Glad to hear the fix the issue.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;-Amanda H.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Problem S140 Soft Device on nRF52833</title><link>https://devzone.nordicsemi.com/thread/283496?ContentTypeID=1</link><pubDate>Mon, 07 Dec 2020 10:49:50 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:36fa8eab-fc1e-4d8e-9f5b-77053afe0dec</guid><dc:creator>Paolo</dc:creator><description>&lt;p&gt;I managed to compile the solution and now it works.&lt;/p&gt;
&lt;p&gt;If we set a baud rate as follows:&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp;p_advertising-&amp;gt; adv_params.primary_phy = BLE_GAP_PHY_1MBPS;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; p_advertising-&amp;gt; adv_params.secondary_phy = BLE_GAP_PHY_1MBPS;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;everything works correctly. If instead we set as follows:&lt;/p&gt;
&lt;p&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;p_advertising-&amp;gt; adv_params.primary_phy = BLE_GAP_PHY_CODED;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; p_advertising-&amp;gt; adv_params.secondary_phy = BLE_GAP_PHY_1MBPS;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;we are no longer able to communicate with the device.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>