<?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>nRF52-DK mbed update problem</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/19412/nrf52-dk-mbed-update-problem</link><description>I&amp;#39;ve just tried to update the mbed firmware on an nRF52-DK to version 0219, and have hit some problems. Firstly, after dragging the .bin file into the Bootloader drive, my Windows 10 PC bluescreened. I managed to update the DK on another Windows 10 PC</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 27 Feb 2017 11:43:38 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/19412/nrf52-dk-mbed-update-problem" /><item><title>RE: nRF52-DK mbed update problem</title><link>https://devzone.nordicsemi.com/thread/75337?ContentTypeID=1</link><pubDate>Mon, 27 Feb 2017 11:43:38 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:08a4eb72-e87e-46ff-8d67-b0e181f2e8b9</guid><dc:creator>Steve H</dc:creator><description>&lt;p&gt;I&amp;#39;ve reinstalled Windows 10 from scratch and I can now see the mbed drives. Thanks for your help, Martin!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52-DK mbed update problem</title><link>https://devzone.nordicsemi.com/thread/75335?ContentTypeID=1</link><pubDate>Mon, 06 Feb 2017 13:54:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3383b636-249e-4991-8101-150b2f32fc57</guid><dc:creator>MartinBL</dc:creator><description>&lt;p&gt;Isn&amp;#39;t that another sign that the bluescreen somehow corrupted your win 10 drivers? It might be an idea to ask on the &lt;a href="http://forum.segger.com/"&gt;Segger forums&lt;/a&gt;.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52-DK mbed update problem</title><link>https://devzone.nordicsemi.com/thread/75334?ContentTypeID=1</link><pubDate>Mon, 06 Feb 2017 13:14:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1fd5cf49-9f7d-45a6-be29-3bb2754b7e6c</guid><dc:creator>Steve H</dc:creator><description>&lt;p&gt;Hi Martin, no luck yet. I&amp;#39;ve tried everything I can think of - uninstalling J-Link, removing registry entries related to the USB etc. and reinstalling.&lt;/p&gt;
&lt;p&gt;Here&amp;#39;s a strange thing though: I have tried a Linux VM on the Windows 10 machine that &lt;strong&gt;doesn&amp;#39;t&lt;/strong&gt; work, and the VM works perfectly and can see the mbed folder on the nrf52-DK.&lt;/p&gt;
&lt;p&gt;I am confused!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52-DK mbed update problem</title><link>https://devzone.nordicsemi.com/thread/75336?ContentTypeID=1</link><pubDate>Mon, 06 Feb 2017 08:58:01 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:35c6c0e4-f41c-4509-be3d-495b584a5932</guid><dc:creator>MartinBL</dc:creator><description>&lt;p&gt;Hi. Any luck yet? I&amp;#39;m afraid I&amp;#39;m out of ideas. Since both devices work on one machine, but neither works on the other machine, then it must be a device driver issue. My only suggestion is to reinstall everything you can think of related to the kits.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52-DK mbed update problem</title><link>https://devzone.nordicsemi.com/thread/75333?ContentTypeID=1</link><pubDate>Thu, 02 Feb 2017 10:06:31 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8f8ae4e6-4ed3-46cf-9e48-c285b40ddf31</guid><dc:creator>Steve H</dc:creator><description>&lt;p&gt;We only have the two DK boards and neither work on this machine. I&amp;#39;ve tried uninstalling and that doesn&amp;#39;t make any difference. I&amp;#39;ve also installed the latest j-Link drivers and there&amp;#39;s no difference. Another J-Link device does show up in Device Manager.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52-DK mbed update problem</title><link>https://devzone.nordicsemi.com/thread/75332?ContentTypeID=1</link><pubDate>Thu, 02 Feb 2017 09:45:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0717ccef-ff68-4e89-9bdf-0e19aec8edc6</guid><dc:creator>MartinBL</dc:creator><description>&lt;p&gt;Then I guess something went wrong when your PC bluescreened. Do you have more kits you can try on the failing PC?
It might be worth trying to re-install the device like described &lt;a href="https://technet.microsoft.com/en-us/library/cc725782(v=ws.11).aspx"&gt;here&lt;/a&gt;.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52-DK mbed update problem</title><link>https://devzone.nordicsemi.com/thread/75331?ContentTypeID=1</link><pubDate>Thu, 02 Feb 2017 09:31:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ceea3584-2925-4ffd-b1e6-ee7b5555a2c4</guid><dc:creator>Steve H</dc:creator><description>&lt;p&gt;Hi Martin,&lt;/p&gt;
&lt;p&gt;Yes, it appears in Device Manager under Disk Drives as &amp;quot;MBED microntroller USB Device&amp;quot;. In Disk Management it appears as &amp;quot;Disk 2&amp;quot; Unknown format, 1MB and it is not initialized. I can&amp;#39;t allocate it a drive letter.&lt;/p&gt;
&lt;p&gt;It works fine on a different computer with the same cable.&lt;/p&gt;
&lt;p&gt;EDIT: yes, it&amp;#39;s fine on one and not the other.&lt;/p&gt;
&lt;p&gt;EDIT 2: It doesn&amp;#39;t appear as JLink under USB controllers.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52-DK mbed update problem</title><link>https://devzone.nordicsemi.com/thread/75330?ContentTypeID=1</link><pubDate>Thu, 02 Feb 2017 09:19:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b57a1cfa-78d0-4584-867c-7f1a750905c4</guid><dc:creator>MartinBL</dc:creator><description>&lt;p&gt;Hi.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Does your kit show up in the device manager? With device manager open, can you plug the kit out and then back in again and see if any new devices show up at all? It might not show up as &amp;quot;JLink CDC .... &amp;quot; as it should.&lt;/li&gt;
&lt;li&gt;Are you able to try a different computer?&lt;/li&gt;
&lt;li&gt;A lot of similar cases have turned out to be due to bad USB cables. Can you try a different one?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;EDIT: I didn&amp;#39;t notice what you were saying about different computers. But to clarify: Are you saying that your kit works on just one out of two Win 10 computers?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>