<?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>nRF54LM20A external SWD programming issue and LM20 DK request</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/128546/nrf54lm20a-external-swd-programming-issue-and-lm20-dk-request</link><description>Hi Folks &amp;amp; experts 
 I hope you ALL are well. 
 I wanted to share a bring-up result from my XIAO nRF54LM20A workbench and ask for your guidance. 
 I have the XIAO nRF54LM20A mounted on the Seeed expansion board and connected by external SWD to the P19</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 24 Jun 2026 18:24:23 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/128546/nrf54lm20a-external-swd-programming-issue-and-lm20-dk-request" /><item><title>RE: nRF54LM20A external SWD programming issue and LM20 DK request</title><link>https://devzone.nordicsemi.com/thread/568384?ContentTypeID=1</link><pubDate>Wed, 24 Jun 2026 18:24:23 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cfbedc28-6938-476b-a4ca-76ef9141a70d</guid><dc:creator>PjGlasso</dc:creator><description>&lt;p&gt;I would add,&lt;/p&gt;
&lt;p data-start="0" data-end="124"&gt;&lt;strong data-start="0" data-end="124"&gt;Most likely it is a Nordic integration/support issue at the boundary with SEGGER, not a simple &amp;ldquo;SEGGER is broken&amp;rdquo; issue.&lt;/strong&gt;&lt;/p&gt;
&lt;p data-start="126" data-end="130"&gt;Why:&lt;/p&gt;
&lt;ul data-start="132" data-end="494"&gt;
&lt;li data-section-id="n0oaj3" data-start="132" data-end="288"&gt;&lt;strong data-start="134" data-end="184"&gt;SEGGER/J-Link can see and debug the LM20A core&lt;/strong&gt; through the nRF54L15 DK: SWD-DP, Cortex-M33, secure debug, halt, registers, and memory access all work.&lt;/li&gt;
&lt;li data-section-id="ic8q1y" data-start="289" data-end="380"&gt;&lt;strong data-start="291" data-end="380"&gt;Nordic&amp;rsquo;s own &lt;code data-start="306" data-end="315"&gt;nrfutil&lt;/code&gt; can program the same target through the same probe and wiring.&lt;/strong&gt;&lt;/li&gt;
&lt;li data-section-id="17gqbzl" data-start="381" data-end="494"&gt;&lt;strong data-start="383" data-end="494"&gt;Nordic&amp;rsquo;s nRF Connect Programmer also sees the LM20A but cannot read/write it in this external-target setup.&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p data-start="496" data-end="774"&gt;That last point matters most. If it were only a SEGGER defect, you would expect Nordic Programmer&amp;mdash;using Nordic&amp;rsquo;s intended tooling&amp;mdash;to have a clearer working path. Since both the raw J-Link path and Nordic Programmer fail while &lt;code data-start="722" data-end="746"&gt;nrfutil device program&lt;/code&gt; works, the likely split is:&lt;/p&gt;
&lt;div class="TyagGW_tableContainer"&gt;
&lt;div class="group TyagGW_tableWrapper flex flex-col-reverse w-fit"&gt;
&lt;table class="w-fit min-w-(--thread-content-width)" data-start="776" data-end="1082"&gt;
&lt;thead data-start="776" data-end="794"&gt;
&lt;tr data-start="776" data-end="794"&gt;
&lt;th class="last:pe-10" data-start="776" data-end="784" data-col-size="md"&gt;Layer&lt;/th&gt;
&lt;th class="last:pe-10" data-start="784" data-end="794" data-col-size="sm"&gt;Status&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody data-start="805" data-end="1082"&gt;
&lt;tr data-start="805" data-end="850"&gt;
&lt;td data-start="805" data-end="842" data-col-size="md"&gt;Physical SWD wiring / target power&lt;/td&gt;
&lt;td data-start="842" data-end="850" data-col-size="sm"&gt;Good&lt;/td&gt;
&lt;/tr&gt;
&lt;tr data-start="851" data-end="887"&gt;
&lt;td data-start="851" data-end="879" data-col-size="md"&gt;nRF54L15 DK onboard probe&lt;/td&gt;
&lt;td data-start="879" data-end="887" data-col-size="sm"&gt;Good&lt;/td&gt;
&lt;/tr&gt;
&lt;tr data-start="888" data-end="917"&gt;
&lt;td data-start="888" data-end="909" data-col-size="md"&gt;LM20A debug access&lt;/td&gt;
&lt;td data-start="909" data-end="917" data-col-size="sm"&gt;Good&lt;/td&gt;
&lt;/tr&gt;
&lt;tr data-start="918" data-end="977"&gt;
&lt;td data-start="918" data-end="955" data-col-size="md"&gt;Nordic device-programming protocol&lt;/td&gt;
&lt;td data-start="955" data-end="977" data-col-size="sm"&gt;Good via &lt;code data-start="966" data-end="975"&gt;nrfutil&lt;/code&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr data-start="978" data-end="1023"&gt;
&lt;td data-start="978" data-end="1014" data-col-size="md"&gt;Generic J-Link RAMCode flash path&lt;/td&gt;
&lt;td data-start="1014" data-end="1023" data-col-size="sm"&gt;Fails&lt;/td&gt;
&lt;/tr&gt;
&lt;tr data-start="1024" data-end="1082"&gt;
&lt;td data-start="1024" data-end="1073" data-col-size="md"&gt;nRF Connect Programmer external-LM20A workflow&lt;/td&gt;
&lt;td data-start="1073" data-end="1082" data-col-size="sm"&gt;Fails&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;p data-start="1084" data-end="1114"&gt;So the practical diagnosis is:&lt;/p&gt;
&lt;blockquote data-start="1116" data-end="1366"&gt;
&lt;p data-start="1118" data-end="1366"&gt;&lt;strong data-start="1118" data-end="1366"&gt;Nordic has a working programming implementation in &lt;code data-start="1171" data-end="1180"&gt;nrfutil&lt;/code&gt;, but the same required LM20A flash initialization/algorithm is not successfully available through the J-Link Commander and nRF Connect Programmer external-target workflows you tested.&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p data-start="1368" data-end="1409"&gt;Who fixes what depends on the root cause:&lt;/p&gt;
&lt;ul data-start="1411" data-end="1852"&gt;
&lt;li data-section-id="1jg9ikz" data-start="1411" data-end="1569"&gt;If the LM20A needs a special flash-init sequence or Nordic-owned flash algorithm, &lt;strong data-start="1495" data-end="1505"&gt;Nordic&lt;/strong&gt; needs to expose/support that path in Programmer or document it.&lt;/li&gt;
&lt;li data-section-id="dzg59q" data-start="1570" data-end="1728"&gt;If SEGGER has the proper LM20A flash loader but it fails through the nRF54L15 DK OB probe, &lt;strong data-start="1663" data-end="1673"&gt;SEGGER&lt;/strong&gt; needs to fix the J-Link RAMCode/flash-loader behavior.&lt;/li&gt;
&lt;li data-section-id="2q4ttp" data-start="1729" data-end="1852"&gt;If the DK&amp;rsquo;s onboard J-Link has a limitation for external LM20A targets, it is a &lt;strong data-start="1811" data-end="1845"&gt;Nordic DK firmware/integration&lt;/strong&gt; issue.&lt;/li&gt;
&lt;/ul&gt;
&lt;p data-start="1854" data-end="1912"&gt;Your Nordic contact is the right first escalation because:&lt;/p&gt;
&lt;ol data-start="1913" data-end="2154"&gt;
&lt;li data-section-id="1n8zsal" data-start="1913" data-end="1959"&gt;they own the silicon and official workflow,&lt;/li&gt;
&lt;li data-section-id="c181q" data-start="1960" data-end="2015"&gt;&lt;code data-start="1963" data-end="1972"&gt;nrfutil&lt;/code&gt; already proves Nordic has a working route,&lt;/li&gt;
&lt;li data-section-id="1g6mh4r" data-start="2016" data-end="2154"&gt;they can tell you whether an &lt;strong data-start="2048" data-end="2064"&gt;nRF54LM20 DK&lt;/strong&gt; is required or whether the L15 DK external probe is officially supported for this target.&lt;/li&gt;
&lt;/ol&gt;
&lt;p data-start="2156" data-end="2268" data-is-last-node="" data-is-only-node=""&gt;Then send the same evidence to SEGGER if Nordic says: &amp;ldquo;This external J-Link configuration should program LM20A.&amp;rdquo;&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;
&lt;p data-start="2156" data-end="2268" data-is-last-node="" data-is-only-node=""&gt;Please advise,&lt;br /&gt;PJ Glasso&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>