<?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>j-link connection fail on nrf52833 DK board.</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/119646/j-link-connection-fail-on-nrf52833-dk-board</link><description>We have found a nrf52833 DK (PCA101000) with id, 685888541 with 2024.4. 
 So, it might be used as previous project in our company. 
 Anyway, I tried to test with this DK board. but I found the fail of j-link connection via PC. 
 First of all, when I attached</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 13 Mar 2025 02:31:35 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/119646/j-link-connection-fail-on-nrf52833-dk-board" /><item><title>RE: j-link connection fail on nrf52833 DK board.</title><link>https://devzone.nordicsemi.com/thread/527068?ContentTypeID=1</link><pubDate>Thu, 13 Mar 2025 02:31:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9769e4a3-03f1-45e0-9b42-c95f629fa1fc</guid><dc:creator>bini2007</dc:creator><description>&lt;p&gt;Thanks for your help.&lt;br /&gt;&lt;br /&gt;It works well as you said before.&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;
&lt;p&gt;Jaehong Park&lt;/p&gt;
&lt;div id="__endic_crx__"&gt;
&lt;div class="css-diqpy0"&gt;&lt;/div&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: j-link connection fail on nrf52833 DK board.</title><link>https://devzone.nordicsemi.com/thread/526693?ContentTypeID=1</link><pubDate>Tue, 11 Mar 2025 08:52:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4b835fc7-aced-46d0-a063-380ed042a9c7</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;
&lt;p&gt;It seems that SB40 is cut:&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:240px;max-width:320px;" src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/pastedimage1741683061920v1.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;You need to connect a female-to-female jumper wire, or a 2 pin header jumper to P22:&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:240px;max-width:320px;" src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/pastedimage1741683118576v2.jpeg" alt=" " /&gt;&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><item><title>RE: j-link connection fail on nrf52833 DK board.</title><link>https://devzone.nordicsemi.com/thread/526665?ContentTypeID=1</link><pubDate>Tue, 11 Mar 2025 01:34:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b1ad00ea-3b64-445e-bd54-a15601bc2a81</guid><dc:creator>bini2007</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;I attach the picture of the nRF52833 DK board.&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:240px;max-width:320px;" alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/nRF52833_2D00_DK_2D00_1.jpg" /&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Maybe, the previous engineer retired from our company had been used for current measurement.&lt;/p&gt;
&lt;p&gt;Then if so, let me know how to use a jumper on the pin-header named &amp;quot;nRF current measurement&amp;quot; and why to use it.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;
&lt;p&gt;Jaehong Park&lt;/p&gt;
&lt;div id="__endic_crx__"&gt;
&lt;div class="css-diqpy0"&gt;&lt;/div&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: j-link connection fail on nrf52833 DK board.</title><link>https://devzone.nordicsemi.com/thread/526585?ContentTypeID=1</link><pubDate>Mon, 10 Mar 2025 14:33:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c933629b-2bdd-43c0-ae30-8a3013056d5e</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;
&lt;p&gt;Could you share a picture of the board itself?&lt;/p&gt;
&lt;p&gt;Has this board been used for current measurement at some point? If so, you will need a jumper on the pin-header named &amp;quot;nRF current measurement&amp;quot;.&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><item><title>RE: j-link connection fail on nrf52833 DK board.</title><link>https://devzone.nordicsemi.com/thread/526465?ContentTypeID=1</link><pubDate>Mon, 10 Mar 2025 02:45:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:aef2c7f0-79df-45dd-9039-55cf2c0d1779</guid><dc:creator>bini2007</dc:creator><description>&lt;p&gt;It seems that DK board was something wrong.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;so I moved the hex file,&amp;nbsp;ble_app_uart_pca10100_s113.hex in nRF SDK7.1 to mass storage disk of DK board.&lt;/p&gt;
&lt;p&gt;&lt;br /&gt;But nRF Soc of DK board update is failed with&amp;nbsp;FAIL.TXT occurred on MSD shown on PC.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;I don&amp;#39;t know well and I guess that DK board are wrong a little.&lt;/p&gt;
&lt;p&gt;Please check how to solve it.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;div id="__endic_crx__"&gt;
&lt;div class="css-diqpy0"&gt;&lt;/div&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: j-link connection fail on nrf52833 DK board.</title><link>https://devzone.nordicsemi.com/thread/526462?ContentTypeID=1</link><pubDate>Mon, 10 Mar 2025 02:03:03 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:650646c6-09c2-4639-b37f-c83bfff63a11</guid><dc:creator>bini2007</dc:creator><description>&lt;p&gt;Today, I tested again with old nRF52833 DK board.&lt;/p&gt;
&lt;p&gt;The error log changed a little as followings:&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;C:\Program Files\SEGGER\JLink_V794e&amp;gt;JLink.exe
SEGGER J-Link Commander V7.94e (Compiled Jan 15 2024 15:20:36)
DLL version V7.94e, compiled Jan 15 2024 15:18:46

Connecting to J-Link via USB...O.K.
Firmware: J-Link OB-SAM3U128-V2-NordicSemi compiled Oct 30 2023 12:12:17
Hardware version: V1.00
J-Link uptime (since boot): 0d 00h 00m 09s
S/N: 685096686
License(s): RDI, FlashBP, FlashDL, JFlash, GDB
USB speed mode: High speed (480 MBit/s)
VTref=3.300V


Type &amp;quot;connect&amp;quot; to establish a target connection, &amp;#39;?&amp;#39; for help
J-Link&amp;gt;connect
Please specify device / core. &amp;lt;Default&amp;gt;: NRF52833_XXAA
Type &amp;#39;?&amp;#39; for selection dialog
Device&amp;gt;
Please specify target interface:
  J) JTAG (Default)
  S) SWD
  T) cJTAG
TIF&amp;gt;S
Specify target interface speed [kHz]. &amp;lt;Default&amp;gt;: 4000 kHz
Speed&amp;gt;
Device &amp;quot;NRF52833_XXAA&amp;quot; selected.


Connecting to target via SWD
InitTarget() start
InitTarget() end - Took 107ms
Connect fallback: Reset via Reset pin &amp;amp; Connect.
InitTarget() start
InitTarget() end - Took 108ms
Cannot connect to target.
J-Link&amp;gt;&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;As you see, we can see the log, &amp;quot;Reset via Reset pin &amp;amp; Connect.&amp;quot;&lt;/p&gt;
&lt;p&gt;After updating JLink OB FW, this error happens.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Please advice me how to fix this.&lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;div id="__endic_crx__"&gt;
&lt;div class="css-diqpy0"&gt;&lt;/div&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: j-link connection fail on nrf52833 DK board.</title><link>https://devzone.nordicsemi.com/thread/526444?ContentTypeID=1</link><pubDate>Sat, 08 Mar 2025 16:53:22 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b2b4e78a-c360-4abe-8a0f-f8fbf8a2c6ae</guid><dc:creator>bini2007</dc:creator><description>&lt;p&gt;In addition to above,&lt;/p&gt;
&lt;p&gt;I have tested it with &amp;quot;nrfjprog --recover&amp;quot; and &amp;quot;nrfjprog --eraseall&amp;quot;. The error log are followings:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;D:\ProgramFiles\Nordic Semiconductor\nrf-command-line-tools\bin&amp;gt;nrfjprog.exe --recover
[error] [ Client] - Encountered error -105: Command connect_to_emu_with_snr executed for 329 milliseconds with result -105
ERROR: Unable to connect to a debugger.
[error] [ Worker] - JLinkARM.dll Open returned error &amp;#39;Cannot connect to J-Link.&amp;#39;
ERROR: The JLinkARM DLL timed out while communicating to the J-Link probe.
ERROR: If the error condition persists, run the same command again with
ERROR: argument -- log, contact Nordic Semiconductor and provide the generated
ERROR: log.log file to them.
NOTE: For additional output, try running again with logging enabled (--log).
NOTE: Any generated log error messages will be displayed.

D:\ProgramFiles\Nordic Semiconductor\nrf-command-line-tools\bin&amp;gt;nrfjprog.exe --eraseall
[error] [ Client] - Encountered error -105: Command connect_to_emu_with_snr executed for 298 milliseconds with result -105
ERROR: Unable to connect to a debugger.
[error] [ Worker] - JLinkARM.dll Open returned error &amp;#39;Cannot connect to J-Link.&amp;#39;
ERROR: The JLinkARM DLL timed out while communicating to the J-Link probe.
ERROR: If the error condition persists, run the same command again with
ERROR: argument -- log, contact Nordic Semiconductor and provide the generated
ERROR: log.log file to them.
NOTE: For additional output, try running again with logging enabled (--log).
NOTE: Any generated log error messages will be displayed.

D:\ProgramFiles\Nordic Semiconductor\nrf-command-line-tools\bin&amp;gt;&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Please advice me how to solve it.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;div id="__endic_crx__"&gt;
&lt;div class="css-diqpy0"&gt;&lt;/div&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>