<?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>Adapt existing Zephyr OpenThread application from nRF52DK to nRF52Dongle</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/73150/adapt-existing-zephyr-openthread-application-from-nrf52dk-to-nrf52dongle</link><description>Hello, 
 
 I&amp;#39;ve been given the task of porting an existing application from the nRF52840DK to a nFR52840 Dongle. 
 Simplified, the application uses the Shell functionality from Zephyr to control external devices using Thread. The application works satisfactorily</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 24 Mar 2021 12:47:59 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/73150/adapt-existing-zephyr-openthread-application-from-nrf52dk-to-nrf52dongle" /><item><title>RE: Adapt existing Zephyr OpenThread application from nRF52DK to nRF52Dongle</title><link>https://devzone.nordicsemi.com/thread/301675?ContentTypeID=1</link><pubDate>Wed, 24 Mar 2021 12:47:59 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:99d95b03-ce88-453d-bc76-ff3fa4449eff</guid><dc:creator>RGjolstad</dc:creator><description>&lt;p&gt;An update:&lt;/p&gt;
&lt;p&gt;After rummaging around with all sorts of settings, I&amp;#39;ve managed to get things working. Apparently this application used both Console and Shell simultaneously.&lt;/p&gt;
&lt;p&gt;In my particular case these were the necessary changes to the prj.conf in case someone else encounters a similar issue:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;# Both of these need to be set to &amp;quot;CDC_ACM_0&amp;quot;. &amp;quot;UART_0&amp;quot; did not work here.
CONFIG_UART_CONSOLE_ON_DEV_NAME=&amp;quot;CDC_ACM_0&amp;quot;
CONFIG_UART_SHELL_ON_DEV_NAME=&amp;quot;CDC_ACM_0&amp;quot;

# Line control apparently is not necessary in this case.
CONFIG_UART_LINE_CTRL=n

# Setting the console to be a UART console in addition was necessary
CONFIG_UART_CONSOLE=y&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;I have yet to test if the actual Thread communication works, but at least now I have some feedback from the Dongle.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>