<?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>nRF52840 Custom Board: &amp;quot;Failed to download RAMCode!&amp;quot;</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/127214/nrf52840-custom-board-failed-to-download-ramcode</link><description>Hello, 
 I am a junior developer currently working with the nRF52840. I have been developing and debugging successfully using the nRF52840 Evaluation Kit (DK) without any issues. However, I am now facing significant problems while trying to flash the</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 02 Mar 2026 09:02:27 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/127214/nrf52840-custom-board-failed-to-download-ramcode" /><item><title>RE: nRF52840 Custom Board: "Failed to download RAMCode!"</title><link>https://devzone.nordicsemi.com/thread/562285?ContentTypeID=1</link><pubDate>Mon, 02 Mar 2026 09:02:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1d68f3a6-0d34-416c-9f84-cb8846b0d15b</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;Hi Junseo,&lt;/p&gt;
&lt;p&gt;Have you verified if your power source is stable and checked that VDD is at the right level? typical value that you should read is around 3V to 3.3V&lt;br /&gt;&lt;strong&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;If your custom board does not have the required DCDC inductor, but the firmware enables DCDC, the board will not run. Disable it with:&amp;nbsp;&lt;strong&gt;&lt;em&gt;&lt;span&gt;CONFIG_BOARD_ENABLE_DCDC&lt;/span&gt;&lt;span&gt;=&lt;/span&gt;n&lt;/em&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;&lt;/em&gt;Nothing else pops to my mind as of now. But those above two has been most common pitfalls. Since --recover also fails, I think we can rule out APPROTECT issues for now.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>