<?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>USBD does work debug out SES</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/36035/usbd-does-work-debug-out-ses</link><description>Hi, 
 I am facing the same problem as in question &amp;#39; USBD don&amp;#39;t work with debugger &amp;#39; from @ Dusautois J&amp;#233;r&amp;#244;me 
 I am trying the same code both on PCA10056 and my board. In PCA10056 works fine but on my board when debugging the USBD driver does not start</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 04 Jul 2018 12:15:21 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/36035/usbd-does-work-debug-out-ses" /><item><title>RE: USBD does work debug out SES</title><link>https://devzone.nordicsemi.com/thread/138953?ContentTypeID=1</link><pubDate>Wed, 04 Jul 2018 12:15:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:42b75aaf-3ddf-4fb6-9486-14c81fa7cf8f</guid><dc:creator>Martin Lesund</dc:creator><description>&lt;p&gt;Hi Sebastian,&lt;/p&gt;
&lt;p&gt;That sounds like a good solution, so it is safe to mark this question as &amp;quot;closed&amp;quot;.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: USBD does work debug out SES</title><link>https://devzone.nordicsemi.com/thread/138809?ContentTypeID=1</link><pubDate>Tue, 03 Jul 2018 15:53:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b7a41614-90c0-42c4-87c8-0de2254214a8</guid><dc:creator>Sebastian</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I think I found the solution. Apparently, when code is downloaded first time to the external board MCU, a proper power cycling is required. The reset that the debug out interface is performing is not sufficient and causes the issues described above.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;The sequence is then:&lt;/p&gt;
&lt;p&gt;1) Download the code to the external MCU&lt;/p&gt;
&lt;p&gt;2) Power cycle&lt;/p&gt;
&lt;p&gt;3) Start debugging&lt;/p&gt;
&lt;p&gt;This sequence does not &amp;#39;lock&amp;#39; the UDBD initialization.&lt;/p&gt;
&lt;p&gt;If this is an acceptable answer I can close the question.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>