<?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>nRF52833 DAP / J-Link DebugPort register 2 : unknown error in J-Link DLL</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/118645/nrf52833-dap-j-link-debugport-register-2-unknown-error-in-j-link-dll</link><description>Hello, We designed and tested a firmware on the nRF52833-DK board, whith plenty of debug sessions and reprogramming. Then it has been build for our custom board, based on the nRF52833 chip too, used as a peripheral for a modem host (SPI line). Using our</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 05 Feb 2025 13:28:32 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/118645/nrf52833-dap-j-link-debugport-register-2-unknown-error-in-j-link-dll" /><item><title>RE: nRF52833 DAP / J-Link DebugPort register 2 : unknown error in J-Link DLL</title><link>https://devzone.nordicsemi.com/thread/521551?ContentTypeID=1</link><pubDate>Wed, 05 Feb 2025 13:28:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:73ee9df4-0a87-4d55-8a78-fd5767b8b607</guid><dc:creator>pdelrot_samea</dc:creator><description>&lt;p&gt;Hi. Thanks for the answer.&lt;br /&gt;My bad, I made a mix-up in my wiring documentation. Table pin numbers were correct, but not the cables&amp;#39;s color names that I followed this morning. Really sorry for that.&lt;br /&gt;&lt;br /&gt;So the dev boards were reprogrammed.&lt;/p&gt;
&lt;p&gt;&lt;br /&gt;The faulty board from the EMS still had the same error message even after programming wiring correction.&lt;/p&gt;
&lt;p&gt;I&amp;#39;ve been able to reprogram it, by forcing RESET pin to low before the programming, and pull it to high level before the timeout.&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;
&lt;p&gt;Regarding the DC-DC, there is one, also powering the modem host. Nothing strange. Power consumption of the board (50mA) is quite high regarding the nRF52 itself, but as you mentionned it could something to monitor. We have a ferrite chip on the power supply to disconnect to measure only the nRF consumption if needed.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52833 DAP / J-Link DebugPort register 2 : unknown error in J-Link DLL</title><link>https://devzone.nordicsemi.com/thread/521535?ContentTypeID=1</link><pubDate>Wed, 05 Feb 2025 12:01:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b539ab0b-06ca-4b84-b0a5-b834cb05cf7c</guid><dc:creator>H&amp;#229;kon Alseth</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
[quote user=""]Here what I tried :&lt;br /&gt;&lt;br /&gt;- wirings checks several times&lt;br /&gt;- J-Link libraries update to 8.10f (the version expected by nrfutil)&lt;br /&gt;- J-Link firmware version check (up to date)&lt;br /&gt;- VDD disconnection =&amp;gt; LOW_VOLTAGE detected, the VDD is correct (1.8V)&lt;br /&gt;- reset pin control (high and low) before and during programming&lt;br /&gt;- batch script requesting &amp;quot;recover&amp;quot; in loop, doing power on/off or reset pin toggling&lt;br /&gt;&lt;br /&gt;It seems to me that I&amp;#39;ll not be able to reprogram the devices once programmed a first time.[/quote]
&lt;p&gt;If you have tried all of these things, the recommendation is to check the soldering around the device and possibly reflow the nRF.&lt;/p&gt;
&lt;p&gt;If you measure the power consumption of the board, that can give an indication on what is going on, for instance. Is the current draw dynamic (ie. fluctuates a lot) or is it static?&lt;/p&gt;
&lt;p&gt;Does your design include DCDC inductors? If your firmware enables DCDC without external components being in-place, it will effectively go into a power-on-reset loop.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Kind regards,&lt;/p&gt;
&lt;p&gt;Håkon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>