<?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>&amp;quot;Failed to power up DAP&amp;quot; successfully resolved, possible causes?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/82576/failed-to-power-up-dap-successfully-resolved-possible-causes</link><description>Hi all, 
 we recently had a problem with couple of our boards based on Raytac MDBT50Q-1MV2 (nrf52840 + osc. + antenna). We base our app on Zephyr. After programming some boards (cca 5% of the batch) using Segger EDU mini they became unresponsive, and</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 12 May 2022 15:07:52 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/82576/failed-to-power-up-dap-successfully-resolved-possible-causes" /><item><title>RE: "Failed to power up DAP" successfully resolved, possible causes?</title><link>https://devzone.nordicsemi.com/thread/367691?ContentTypeID=1</link><pubDate>Thu, 12 May 2022 15:07:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ee602ca4-6107-486a-aaa6-8d97d8d9e595</guid><dc:creator>Matevz B</dc:creator><description>&lt;p&gt;Thank you very much for this hint. It has saved many hours of debugging. The board is no longer brciked!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: "Failed to power up DAP" successfully resolved, possible causes?</title><link>https://devzone.nordicsemi.com/thread/342853?ContentTypeID=1</link><pubDate>Fri, 10 Dec 2021 08:55:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7e0c3166-6256-4427-a797-e1ee9e3ea051</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;You should look into whether you may have&amp;nbsp;CONFIG_GPIO_AS_PINRESET in your defines, if it is defined, then in system_nrf52.c it will be used to enable pin reset:&lt;br /&gt;&lt;a href="https://infocenter.nordicsemi.com/topic/ps_nrf52840/uicr.html#register.PSELRESET-0-1"&gt;https://infocenter.nordicsemi.com/topic/ps_nrf52840/uicr.html#register.PSELRESET-0-1&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;If it&amp;#39;s enabled you can check by:&lt;br /&gt;&lt;img src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/3603.pastedimage1639126580223v1.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;Unfortunately if your code set this pin output low and/or configure pull-down, then it may be that the the chip is stuck in a infinite pin reset. The only way is to force it high externally in such case. I can&amp;#39;t think of other reasons why it was low (other than electrical problems externally though, e.g. soldering residue).&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>