<?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>external nRF5340 getting locked up</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/61075/external-nrf5340-getting-locked-up</link><description>Hi, 
 I have developed a piece of software that only uses the GPIOs on the APP core to evaluate a sensor. The software worked on the development board processor so I made a custom board with the nRF5340. After I would load the same software that worked</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 27 Aug 2020 03:40:49 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/61075/external-nrf5340-getting-locked-up" /><item><title>RE: external nRF5340 getting locked up</title><link>https://devzone.nordicsemi.com/thread/266608?ContentTypeID=1</link><pubDate>Thu, 27 Aug 2020 03:40:49 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7b892648-9359-4513-ac2a-9b130e18540e</guid><dc:creator>Manu</dc:creator><description>&lt;p&gt;Thanks Dushan, this helped me too!&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I think this behavior should be classifed as an errata/bug - selecting a different power supply mechanism _should not_ result in a bricked unit.&amp;nbsp;&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: external nRF5340 getting locked up</title><link>https://devzone.nordicsemi.com/thread/265620?ContentTypeID=1</link><pubDate>Thu, 20 Aug 2020 19:40:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8c533dd5-c331-4992-9146-2cb9d45ec55a</guid><dc:creator>allymolly91</dc:creator><description>&lt;p&gt;This was super useful - thanks! I wish Nordic/Zephyr had this documented somewhere.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: external nRF5340 getting locked up</title><link>https://devzone.nordicsemi.com/thread/248362?ContentTypeID=1</link><pubDate>Wed, 06 May 2020 08:06:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b7a662a9-0e21-45dd-bc8f-c93b5151266b</guid><dc:creator>Dushan_zvertech</dc:creator><description>&lt;p&gt;If there is no external coil for DCDC and one enables the DCDC the device will become responsive. The default settings for example software for nRF5430 board is expecting an external DCDC so if the target board doesn&amp;#39;t have the coils once you put the project on the device it will become unresponsive.&lt;/p&gt;
&lt;p&gt;In order to recover the device one needs to apply voltage on the APP (1.25V on DECD) and NET (1.05V on DECRF) core decoupling capacitors to get the cores back online. Then write the new software that doesnt use the DCDC and the device should be ok&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: external nRF5340 getting locked up</title><link>https://devzone.nordicsemi.com/thread/248359?ContentTypeID=1</link><pubDate>Tue, 05 May 2020 07:04:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7102f6b5-34ad-4f48-aff1-85da720739e5</guid><dc:creator>Amanda Hsieh</dc:creator><description>&lt;p&gt;Good to hear the success. I have removed the attachments as you want. You can approve the case go to the public.&lt;/p&gt;
&lt;p&gt;-Amanda H.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: external nRF5340 getting locked up</title><link>https://devzone.nordicsemi.com/thread/248358?ContentTypeID=1</link><pubDate>Mon, 04 May 2020 12:43:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:47dc38f5-787e-4b98-83cf-aabc206c3100</guid><dc:creator>Dushan_zvertech</dc:creator><description>&lt;p&gt;hi&lt;/p&gt;
&lt;p&gt;i have solved the issue&lt;/p&gt;
&lt;p&gt;the problem was that the dcdc is enabled by default in software on nrf53 dk and i was using this as a base for my project. nrf53 has no mechanism to recover if the coil in not present so the device becomes unresponsive. i have solved it by applying voltage externally to the cores and reprogramming them with correct setting.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;how can we make this post public without the attachements and other posts ecxept the question and the solution&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: external nRF5340 getting locked up</title><link>https://devzone.nordicsemi.com/thread/248357?ContentTypeID=1</link><pubDate>Thu, 30 Apr 2020 10:13:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0c3b484f-891e-424a-8eb2-58912ea05e1f</guid><dc:creator>Dushan_zvertech</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Is there a problem with software as I can flash it first time?&lt;/p&gt;
&lt;p&gt;Is zephyr expecting DCDC to run instead of LDO and then it would lock up the device as it would loose power as there is no DCDC implemented?&amp;nbsp;Is there a bare metal software i can test with or configure zephyr?&amp;nbsp;&lt;span style="font-family:inherit;"&gt;Is zephyr expecting a certain crystal?&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Attached is the log from the new nrfjprog&lt;/p&gt;
&lt;p&gt;2020-Apr-30 12:09:17 --------------------------------------------------------------------------------&lt;br /&gt;2020-Apr-30 12:09:17 nrfjprog -f UNKNOWN --recover --log &lt;br /&gt;2020-Apr-30 12:09:17 nrfjprog version 10.8.0 &lt;br /&gt;2020-Apr-30 12:09:17 --------------------------------------------------------------------------------&lt;br /&gt;2020-Apr-30 12:09:17 nRF_logger_open&lt;br /&gt;2020-Apr-30 12:09:17 nRF_logger_open: nRFJProg logger opened to callback at address 0X4D0940&lt;br /&gt;2020-Apr-30 12:09:17 nRF_open_dll&lt;br /&gt;2020-Apr-30 12:09:17 nRF_open_dll: Load library at &amp;quot;C:\\Program Files (x86)\\Nordic Semiconductor\\nrf-command-line-tools\\bin\\JLINKARM_UNKNOWN_NRFJPROG.dll&amp;quot;.&lt;/p&gt;
&lt;p&gt;2020-Apr-30 12:09:17 . nRFXX_logger_open&lt;br /&gt;2020-Apr-30 12:09:17 . nRFXX_logger_open: nRFJProg logger opened to callback at address 0X6E81B850&lt;br /&gt;2020-Apr-30 12:09:17 . . Segger_logger_open&lt;br /&gt;2020-Apr-30 12:09:17 . . Segger_logger_open: nRFJProg logger opened to callback at address 0X6E7DC8A0&lt;br /&gt;2020-Apr-30 12:09:17 . . Segger_open_dll&lt;br /&gt;2020-Apr-30 12:09:17 . . Segger_open_dll: Load library at &amp;quot;C:\\Program Files (x86)\\SEGGER\\JLink\\JLinkARM.dll&amp;quot;.&lt;/p&gt;
&lt;p&gt;2020-Apr-30 12:09:17 . . . Segger_dll_version&lt;br /&gt;2020-Apr-30 12:09:17 . . Segger_set_core_data&lt;br /&gt;2020-Apr-30 12:09:17 nRF_enum_emu_snr&lt;br /&gt;2020-Apr-30 12:09:17 . nRFXX_enum_emu_snr&lt;br /&gt;2020-Apr-30 12:09:17 . . Segger_enum_emu_snr&lt;br /&gt;2020-Apr-30 12:09:17 . . . Segger_enum_emu_snr&lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_get_num_emus&lt;br /&gt;2020-Apr-30 12:09:17 nRF_connect_to_emu_with_snr&lt;br /&gt;2020-Apr-30 12:09:17 . nRFXX_connect_to_emu_with_snr&lt;br /&gt;2020-Apr-30 12:09:17 . . Segger_connect_to_emu_with_snr&lt;br /&gt;2020-Apr-30 12:09:17 . . . Segger_is_connected_to_emu&lt;br /&gt;2020-Apr-30 12:09:17 . . . Segger_enum_emu_snr&lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_get_num_emus&lt;br /&gt;2020-Apr-30 12:09:17 . . . Segger_connect_to_emu_with_snr&lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_connect_to_emu_without_snr&lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_connect_to_emu_without_snr: Segger logging enabled with callback at 0x1853738032.&lt;/p&gt;
&lt;p&gt;2020-Apr-30 12:09:17 . . . . Segger_connect_to_emu_without_snr: JLink INFO T30B8 000:019.748 &lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_connect_to_emu_without_snr: JLink INFO Firmware: J-Link OB-K22-NordicSemi compiled Jan 21 2020 17:33:01&lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_connect_to_emu_without_snr: JLink INFO T30B8 000:021.366 &lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_connect_to_emu_without_snr: JLink INFO Decompressing FW timestamp took 176 us&lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_connect_to_emu_without_snr: JLink INFO T30B8 000:037.400 &lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_connect_to_emu_without_snr: JLink INFO Hardware: V1.00&lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_connect_to_emu_without_snr: JLink INFO T30B8 000:038.842 &lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_connect_to_emu_without_snr: JLink INFO S/N: 960136811&lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_connect_to_emu_without_snr: JLink INFO T30B8 000:039.972 &lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_connect_to_emu_without_snr: JLink INFO OEM: SEGGER&lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_connect_to_emu_without_snr: JLink INFO T30B8 000:041.033 &lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_connect_to_emu_without_snr: JLink INFO Feature(s): RDI, FlashBP, FlashDL, JFlash, GDB&lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_connect_to_emu_without_snr: JLink INFO T30B8 000:043.504 &lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_connect_to_emu_without_snr: JLink INFO TELNET listener socket opened on port 19021&lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_connect_to_emu_without_snr: JLink INFO T30B8 000:044.885 &lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_connect_to_emu_without_snr: JLink INFO WEBSRV Starting webserver&lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_connect_to_emu_without_snr: JLink INFO T30B8 000:046.060 &lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_connect_to_emu_without_snr: JLink INFO WEBSRV Webserver running on local port 19080&lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_connect_to_emu_without_snr: JLink INFO T30B8 000:047.138 &lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_connect_to_emu_without_snr: JLink INFO - 31.450ms returns O.K. &lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_connect_to_emu_without_snr: JLink INFO T30B8 000:048.205 &lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_connect_to_emu_without_snr: JLink INFO JLINK_GetHWStatus(...) &lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_connect_to_emu_without_snr: JLink INFO T30B8 000:049.488 &lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_connect_to_emu_without_snr: JLink INFO - 1.832ms returns 0x00 &lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_connect_to_emu_without_snr: JLink INFO T30B8 000:050.569 &lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_connect_to_emu_without_snr: JLink INFO JLINK_ExecCommand(&amp;quot;SetRestartOnClose = 0&amp;quot;, ...). &lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_connect_to_emu_without_snr: JLink INFO T30B8 000:051.795 &lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_connect_to_emu_without_snr: JLink INFO - 0.625ms returns 0x01 &lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_connect_to_emu_without_snr: JLink INFO T30B8 000:053.018 &lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_connect_to_emu_without_snr: JLink INFO JLINK_ExecCommand(&amp;quot;DisableFlashDL&amp;quot;, ...). &lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_connect_to_emu_without_snr: JLink INFO T30B8 000:054.220 &lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_connect_to_emu_without_snr: JLink INFO - 0.597ms returns 0x00 &lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_connect_to_emu_without_snr: JLink INFO T30B8 000:055.393 &lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_connect_to_emu_without_snr: JLink INFO JLINK_ExecCommand(&amp;quot;ExcludeFlashCacheRange 0x0-0xFFFFFFFF&amp;quot;, ...). &lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_connect_to_emu_without_snr: JLink INFO T30B8 000:056.584 &lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_connect_to_emu_without_snr: JLink INFO - 0.600ms returns 0x00 &lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_connect_to_emu_without_snr: JLink INFO T30B8 000:057.813 &lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_connect_to_emu_without_snr: JLink INFO JLINK_SetHookUnsecureDialog(...)&lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_connect_to_emu_without_snr: JLink INFO T30B8 000:059.033 &lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_connect_to_emu_without_snr: JLink INFO - 1.816ms returns 0 &lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_connect_to_emu_without_snr: JLink INFO T30B8 000:060.249 &lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_connect_to_emu_without_snr: JLink INFO JLINK_TIF_Select(JLINKARM_TIF_SWD) &lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_connect_to_emu_without_snr: JLink INFO T30B8 000:062.174 &lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_connect_to_emu_without_snr: JLink INFO - 2.550ms returns 0x00 &lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_connect_to_emu_without_snr: JLink INFO T30B8 000:063.371 &lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_connect_to_emu_without_snr: JLink INFO JLINK_SetSpeed(2000) &lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_connect_to_emu_without_snr: JLink INFO T30B8 000:064.553 &lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_connect_to_emu_without_snr: JLink INFO - 1.771ms &lt;br /&gt;2020-Apr-30 12:09:17 . . . . . Segger_load_core_data&lt;br /&gt;2020-Apr-30 12:09:17 . . . . . Segger_load_core_data: JLink INFO T30B8 000:066.269 &lt;br /&gt;2020-Apr-30 12:09:17 . . . . . Segger_load_core_data: JLink INFO JLINK_ExecCommand(&amp;quot;CORESIGHT_SetIndexAHBAPToUse = 0&amp;quot;, ...). &lt;br /&gt;2020-Apr-30 12:09:17 . . . . . Segger_load_core_data: JLink INFO T30B8 000:067.388 &lt;br /&gt;2020-Apr-30 12:09:17 . . . . . Segger_load_core_data: JLink INFO - 0.627ms returns 0x00 &lt;br /&gt;2020-Apr-30 12:09:17 . . . . . Segger_load_core_data: JLink INFO T30B8 000:068.713 &lt;br /&gt;2020-Apr-30 12:09:17 . . . . . Segger_load_core_data: JLink INFO JLINK_ExecCommand(&amp;quot;device = Cortex-M4&amp;quot;, ...). &lt;br /&gt;2020-Apr-30 12:09:17 . . . . . Segger_load_core_data: JLink INFO T30B8 000:077.455 &lt;br /&gt;2020-Apr-30 12:09:17 . . . . . Segger_load_core_data: JLink INFO XML file found at: C:\Program Files (x86)\SEGGER\JLink\JLinkDevices.xml &lt;br /&gt;2020-Apr-30 12:09:17 . . . . . Segger_load_core_data: JLink INFO T30B8 000:079.832 &lt;br /&gt;2020-Apr-30 12:09:17 . . . . . Segger_load_core_data: JLink INFO C:\Program Files (x86)\SEGGER\JLink\JLinkDevices.xml evaluated successfully. &lt;br /&gt;2020-Apr-30 12:09:17 . . . . . Segger_load_core_data: JLink INFO T30B8 000:151.322 &lt;br /&gt;2020-Apr-30 12:09:17 . . . . . Segger_load_core_data: JLink INFO Device &amp;quot;CORTEX-M4&amp;quot; selected.&lt;br /&gt;2020-Apr-30 12:09:17 . . . . . Segger_load_core_data: JLink INFO T30B8 000:155.296 &lt;br /&gt;2020-Apr-30 12:09:17 . . . . . Segger_load_core_data: JLink INFO - 86.052ms returns 0x00 &lt;br /&gt;2020-Apr-30 12:09:17 nRF_read_connected_emu_snr&lt;br /&gt;2020-Apr-30 12:09:17 . nRFXX_read_connected_emu_snr&lt;br /&gt;2020-Apr-30 12:09:17 . . Segger_read_connected_emu_snr&lt;br /&gt;2020-Apr-30 12:09:17 . . . Segger_is_connected_to_emu&lt;br /&gt;2020-Apr-30 12:09:17 . . . Segger_is_connected_to_emu: JLink INFO T30B8 000:159.100 &lt;br /&gt;2020-Apr-30 12:09:17 . . . Segger_is_connected_to_emu: JLink INFO JLINK_IsOpen() &lt;br /&gt;2020-Apr-30 12:09:17 . . . Segger_is_connected_to_emu: JLink INFO T30B8 000:160.493 &lt;br /&gt;2020-Apr-30 12:09:17 . . . Segger_is_connected_to_emu: JLink INFO - 1.973ms returns 0x01 &lt;br /&gt;2020-Apr-30 12:09:17 nRF_read_device_family&lt;br /&gt;2020-Apr-30 12:09:17 . nRFXX_read_device_family&lt;br /&gt;2020-Apr-30 12:09:17 . . Segger_is_connected_to_emu&lt;br /&gt;2020-Apr-30 12:09:17 . . Segger_is_connected_to_emu: JLink INFO T30B8 000:163.364 &lt;br /&gt;2020-Apr-30 12:09:17 . . Segger_is_connected_to_emu: JLink INFO JLINK_IsOpen() &lt;br /&gt;2020-Apr-30 12:09:17 . . Segger_is_connected_to_emu: JLink INFO T30B8 000:164.537 &lt;br /&gt;2020-Apr-30 12:09:17 . . Segger_is_connected_to_emu: JLink INFO - 1.738ms returns 0x01 &lt;br /&gt;2020-Apr-30 12:09:17 . . : JLink INFO T30B8 000:165.666 &lt;br /&gt;2020-Apr-30 12:09:17 . . : JLink INFO JLINK_Lock() &lt;br /&gt;2020-Apr-30 12:09:17 . . Segger_read_debug_port_idr&lt;br /&gt;2020-Apr-30 12:09:17 . . . Segger_read_debug_port_register&lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_read_debug_port_register&lt;br /&gt;2020-Apr-30 12:09:17 . . . . . Segger_coresight_configure&lt;br /&gt;2020-Apr-30 12:09:17 . . . . . Segger_coresight_configure: JLink INFO T30B8 000:168.992 &lt;br /&gt;2020-Apr-30 12:09:17 . . . . . Segger_coresight_configure: JLink INFO JLINK_CORESIGHT_Configure() &lt;br /&gt;2020-Apr-30 12:09:17 . . . . . Segger_coresight_configure: JLink INFO T30B8 000:271.141 &lt;br /&gt;2020-Apr-30 12:09:17 . . . . . Segger_coresight_configure: JLink INFO - 103.091ms returns 0 &lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_read_debug_port_register: JLink INFO T30B8 000:272.793 &lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_read_debug_port_register: JLink INFO JLINK_CORESIGHT_ReadAPDPReg(DP reg 0x00) &lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_read_debug_port_register: JLink INFO T30B8 000:274.763 &lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_read_debug_port_register: JLink INFO failed&lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_read_debug_port_register: JLink INFO T30B8 000:276.058 &lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_read_debug_port_register: JLink INFO - 3.926ms returns -1 &lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_read_debug_port_register: JLinkARM.dll reported &amp;quot;-1&amp;quot;, an unknown error.&lt;/p&gt;
&lt;p&gt;2020-Apr-30 12:09:17 . . . . . Segger_abort_debug_action&lt;br /&gt;2020-Apr-30 12:09:17 . . . . . Segger_abort_debug_action: Attempting to clear any configuration errors in debug port before closing connection.&lt;/p&gt;
&lt;p&gt;2020-Apr-30 12:09:17 . . . . . Segger_abort_debug_action: JLink INFO T30B8 000:279.244 &lt;br /&gt;2020-Apr-30 12:09:17 . . . . . Segger_abort_debug_action: JLink INFO JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F) &lt;br /&gt;2020-Apr-30 12:09:17 . . . . . Segger_abort_debug_action: JLink INFO T30B8 000:281.090 &lt;br /&gt;2020-Apr-30 12:09:17 . . . . . Segger_abort_debug_action: JLink INFO - 2.465ms returns -1 &lt;br /&gt;2020-Apr-30 12:09:17 . . . . . Segger_abort_debug_action: JLinkARM.dll reported &amp;quot;-1&amp;quot;, an unknown error.&lt;/p&gt;
&lt;p&gt;2020-Apr-30 12:09:17 . . : JLink INFO T30B8 000:282.861 &lt;br /&gt;2020-Apr-30 12:09:17 . . : JLink INFO JLINK_Unlock() &lt;br /&gt;2020-Apr-30 12:09:17 nRF_close_dll&lt;br /&gt;2020-Apr-30 12:09:17 . nRFXX_close_dll&lt;br /&gt;2020-Apr-30 12:09:17 . . Segger_close&lt;br /&gt;2020-Apr-30 12:09:17 . . . Segger_disconnect_from_emu&lt;br /&gt;2020-Apr-30 12:09:17 . . . . Segger_is_connected_to_emu&lt;br /&gt;2020-Apr-30 12:09:18 . . . . Segger_is_connected_to_emu: JLink INFO T30B8 000:286.764 &lt;br /&gt;2020-Apr-30 12:09:18 . . . . Segger_is_connected_to_emu: JLink INFO JLINK_IsOpen() &lt;br /&gt;2020-Apr-30 12:09:18 . . . . Segger_is_connected_to_emu: JLink INFO T30B8 000:287.894 &lt;br /&gt;2020-Apr-30 12:09:18 . . . . Segger_is_connected_to_emu: JLink INFO - 1.713ms returns 0x01 &lt;br /&gt;2020-Apr-30 12:09:18 . . . . Segger_disconnect_from_emu&lt;br /&gt;2020-Apr-30 12:09:18 . . . . . Segger_is_connected_to_device&lt;br /&gt;2020-Apr-30 12:09:18 . . . . . Segger_is_connected_to_device: JLink INFO T30B8 000:290.225 &lt;br /&gt;2020-Apr-30 12:09:18 . . . . . Segger_is_connected_to_device: JLink INFO JLINK_IsConnected() &lt;br /&gt;2020-Apr-30 12:09:18 . . . . . Segger_is_connected_to_device: JLink INFO T30B8 000:291.337 &lt;br /&gt;2020-Apr-30 12:09:18 . . . . . Segger_is_connected_to_device: JLink INFO - 1.667ms returns FALSE &lt;br /&gt;2020-Apr-30 12:09:18 . . . . . Segger_is_debug_region_powered&lt;br /&gt;2020-Apr-30 12:09:18 . . . . . . Segger_read_debug_port_register&lt;br /&gt;2020-Apr-30 12:09:18 . . . . . . . Segger_is_connected_to_emu&lt;br /&gt;2020-Apr-30 12:09:18 . . . . . . . Segger_is_connected_to_emu: JLink INFO T30B8 000:294.119 &lt;br /&gt;2020-Apr-30 12:09:18 . . . . . . . Segger_is_connected_to_emu: JLink INFO JLINK_IsOpen() &lt;br /&gt;2020-Apr-30 12:09:18 . . . . . . . Segger_is_connected_to_emu: JLink INFO T30B8 000:295.428 &lt;br /&gt;2020-Apr-30 12:09:18 . . . . . . . Segger_is_connected_to_emu: JLink INFO - 1.877ms returns 0x01 &lt;br /&gt;2020-Apr-30 12:09:18 . . . . . . Segger_read_debug_port_register: JLink INFO T30B8 000:296.567 &lt;br /&gt;2020-Apr-30 12:09:18 . . . . . . Segger_read_debug_port_register: JLink INFO JLINK_Lock() &lt;br /&gt;2020-Apr-30 12:09:18 . . . . . . . Segger_write_debug_port_register&lt;br /&gt;2020-Apr-30 12:09:18 . . . . . . . Segger_write_debug_port_register: JLink INFO T30B8 000:298.264 &lt;br /&gt;2020-Apr-30 12:09:18 . . . . . . . Segger_write_debug_port_register: JLink INFO JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x02, 0x00000000) &lt;br /&gt;2020-Apr-30 12:09:18 . . . . . . . Segger_write_debug_port_register: JLink INFO T30B8 000:299.992 &lt;br /&gt;2020-Apr-30 12:09:18 . . . . . . . Segger_write_debug_port_register: JLink INFO - 2.303ms returns -1 &lt;br /&gt;2020-Apr-30 12:09:18 . . . . . . . Segger_write_debug_port_register: JLinkARM.dll reported &amp;quot;-1&amp;quot;, an unknown error.&lt;/p&gt;
&lt;p&gt;2020-Apr-30 12:09:18 . . . . . . . . Segger_abort_debug_action&lt;br /&gt;2020-Apr-30 12:09:18 . . . . . . . . Segger_abort_debug_action: Attempting to clear any configuration errors in debug port before closing connection.&lt;/p&gt;
&lt;p&gt;2020-Apr-30 12:09:18 . . . . . . . . Segger_abort_debug_action: JLink INFO T30B8 000:302.919 &lt;br /&gt;2020-Apr-30 12:09:18 . . . . . . . . Segger_abort_debug_action: JLink INFO JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F) &lt;br /&gt;2020-Apr-30 12:09:18 . . . . . . . . Segger_abort_debug_action: JLink INFO T30B8 000:304.733 &lt;br /&gt;2020-Apr-30 12:09:18 . . . . . . . . Segger_abort_debug_action: JLink INFO - 2.411ms returns -1 &lt;br /&gt;2020-Apr-30 12:09:18 . . . . . . . . Segger_abort_debug_action: JLinkARM.dll reported &amp;quot;-1&amp;quot;, an unknown error.&lt;/p&gt;
&lt;p&gt;2020-Apr-30 12:09:18 . . . . . . Segger_read_debug_port_register: JLink INFO T30B8 000:306.510 &lt;br /&gt;2020-Apr-30 12:09:18 . . . . . . Segger_read_debug_port_register: JLink INFO JLINK_Unlock() &lt;br /&gt;2020-Apr-30 12:09:18 . . . . Segger_disconnect_from_emu: JLink INFO T30B8 000:321.354 &lt;br /&gt;2020-Apr-30 12:09:18 . . . . Segger_disconnect_from_emu: JLink INFO JLINK_Close() &lt;br /&gt;2020-Apr-30 12:09:18 . . Segger_close: Freeing Library.&lt;/p&gt;
&lt;p&gt;2020-Apr-30 12:09:18 nRF_close_dll: Freeing Library.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: external nRF5340 getting locked up</title><link>https://devzone.nordicsemi.com/thread/248356?ContentTypeID=1</link><pubDate>Thu, 30 Apr 2020 09:56:42 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e07881a5-1aae-4677-bb61-fda714df9922</guid><dc:creator>Amanda Hsieh</dc:creator><description>&lt;p&gt;Hi,&amp;nbsp;&amp;nbsp;&lt;/p&gt;
[quote user=""]nrfjprog verion 9.7.1[/quote]
&lt;p&gt;The nrfjprog supports nRF5340 from v10.4.&amp;nbsp; Could you use the latest version of &lt;a href="https://www.nordicsemi.com/Software-and-tools/Development-Tools/nRF-Command-Line-Tools/Download"&gt;nrfjprog&lt;/a&gt;&amp;nbsp;(v10.8)?&amp;nbsp; and provide the log of the &amp;quot;&lt;span&gt;nrfjprog -f UNKNOWN --recover --log&amp;quot; again.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;-Amanda H.&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: external nRF5340 getting locked up</title><link>https://devzone.nordicsemi.com/thread/248355?ContentTypeID=1</link><pubDate>Tue, 28 Apr 2020 13:57:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:010c984e-7e57-40f0-a2e5-f0c80f7c0560</guid><dc:creator>Dushan_zvertech</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Just one more observation. When I do an erase on the dev board and load the firmware the very first attempt to debug would result in the execution going to the fault_s.S followed by disconnection of the programmer. However the software starts running on the dev board, while it doesn&amp;#39;t on the external board&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Dusan&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: external nRF5340 getting locked up</title><link>https://devzone.nordicsemi.com/thread/248354?ContentTypeID=1</link><pubDate>Tue, 28 Apr 2020 13:12:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c090b58b-57aa-4d41-90a8-2f802ff58f2c</guid><dc:creator>Dushan_zvertech</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Thank you for your quick response.&lt;/p&gt;
&lt;p&gt;The board is supplied form a separate supply at 3.3V&lt;/p&gt;
&lt;p&gt;I am uploading the page of the schematic where the nRF is and you can also see which pins are used. I had to change the names but you can see the functionality.&lt;/p&gt;
&lt;p&gt;I&amp;nbsp;find it very odd that it can be programmed only once, a new board is totally responsive over SWD. I can query it, read things out, erase it but as soon as I put the compiled software it stops responding and locks itself up. Is there a bare metal example without zephyr that I could try to test with? Are there special pins zephyr is expecting? Do I have to have the network core programmed as well?&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: external nRF5340 getting locked up</title><link>https://devzone.nordicsemi.com/thread/248353?ContentTypeID=1</link><pubDate>Tue, 28 Apr 2020 11:43:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fed52f29-e25f-4894-b8be-978567920a8a</guid><dc:creator>Amanda Hsieh</dc:creator><description>&lt;p&gt;Hi,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Did you&amp;nbsp;power the external board directly?&amp;nbsp;And is it running at the same voltage level as the nRF5340 PDK?&lt;/p&gt;
&lt;p&gt;Could you upload the schematic of the&amp;nbsp;&lt;span&gt;custom board? I made this case private. Your files are only shared with us (Nordic).&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;-Amanda H.&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>