<?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>Erase Thingy connected to nRF52840-FK</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/55286/erase-thingy-connected-to-nrf52840-fk</link><description>Hi, I am developing something using Zephyr on a nRF52840-DK as one Bluetooth mesh node and a Thingy as the other. To program the Thingy, I have it connected the Thingy to the debug port of the nRF52840-DK. Programming either the Thingy or the nRF52840</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 06 Dec 2019 15:17:15 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/55286/erase-thingy-connected-to-nrf52840-fk" /><item><title>RE: Erase Thingy connected to nRF52840-FK</title><link>https://devzone.nordicsemi.com/thread/224239?ContentTypeID=1</link><pubDate>Fri, 06 Dec 2019 15:17:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b0079603-05f4-4a01-8155-b49431b791d4</guid><dc:creator>bluetooth_mdw</dc:creator><description>&lt;p&gt;Thanks, @Simonr. Makes sense.&lt;/p&gt;
&lt;p&gt;All the best&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Martin&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Erase Thingy connected to nRF52840-FK</title><link>https://devzone.nordicsemi.com/thread/224081?ContentTypeID=1</link><pubDate>Fri, 06 Dec 2019 08:31:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:495b14a4-25ca-4a8c-9c3e-cee488416053</guid><dc:creator>Simonr</dc:creator><description>&lt;p&gt;Hi Martin&lt;/p&gt;
&lt;p&gt;The reason you&amp;#39;re seeing just one ID when calling nrfjprog -i is because this command displays all the&amp;nbsp;&lt;strong&gt;debuggers&amp;nbsp;&lt;/strong&gt;connected to the PC, not all nRF devices. The DK will automatically detect when a device is connected to the Debug out header, and thus, it will program the Thingy whenever it is connected to the DK and turned on. Whenever you want to program the DK instead, you can just remove the debug cable from the DK, and the on-board chip will be programmed instead.&lt;/p&gt;
&lt;p&gt;This can be confirmed by using the nRFConnect programmer app, where the nRF model will be printed in the log when connecting. For example, when I had the Thingy connected in and opened the programmer app the log shows&amp;nbsp;&lt;strong&gt;Model: NRF52832_xxAA_REV1&lt;/strong&gt;, while if I disconnect the debugger cable and connect again the log shows&amp;nbsp;&lt;strong&gt;Model: NRF52840_xxAA_ENGB.&amp;nbsp;&lt;/strong&gt;There is no &amp;quot;model&amp;quot; command in nrfjprog though, so you won&amp;#39;t be able to confirm this using nrfjprog alone.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Simon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>