<?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>Devkit 52840 revision 3 issue : unrecognized probe serial number</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/97211/devkit-52840-revision-3-issue-unrecognized-probe-serial-number</link><description>Hello, 
 we recently faced some issues dealing with nrf52840 devkit ( no matter the revision ) dealing with some data corruption when packets larger than 64 bytes are transmistted over the USB CDC ACM Serial Port. As stated in that nordic page Nordic</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 06 Mar 2023 15:07:32 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/97211/devkit-52840-revision-3-issue-unrecognized-probe-serial-number" /><item><title>RE: Devkit 52840 revision 3 issue : unrecognized probe serial number</title><link>https://devzone.nordicsemi.com/thread/413597?ContentTypeID=1</link><pubDate>Mon, 06 Mar 2023 15:07:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:13014848-42f1-4919-93c7-fab6e2f2af72</guid><dc:creator>dejans</dc:creator><description>&lt;p&gt;Hi,&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;
[quote user="Jean-Baptiste"]The reproduction steps are not that&amp;nbsp;evident unfortunately. I followed the same steps as you did for disabling the mass storage on the devkit and the id of the debugguer was correctly displayed this time.[/quote]
&lt;p&gt;It is great to hear that you managed to get the ID displayed this time.&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;
[quote user="Jean-Baptiste"]This issue seems to not be isolated as we also had some issues with linux machines but I need to confirm that. I&amp;#39;ll come back with&amp;nbsp;more information&amp;nbsp;when I&amp;#39;m able to reproduce it easily ...[/quote]
&lt;p&gt;Please come back if the issue persists and when it becomes consistently reproducible. It would be recommended to fix the issues with Linux machines first.&lt;br /&gt;&lt;br /&gt;Best regards,&lt;br /&gt;Dejan&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Devkit 52840 revision 3 issue : unrecognized probe serial number</title><link>https://devzone.nordicsemi.com/thread/413431?ContentTypeID=1</link><pubDate>Mon, 06 Mar 2023 08:18:50 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d8063fa0-d82b-437f-9f64-3f4787e4c8de</guid><dc:creator>Jean-Baptiste</dc:creator><description>&lt;p&gt;Hi Dejan,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;thank you for your answer and support,&lt;/p&gt;
&lt;p&gt;I used nrfjprog version 10.15.1 jlink dll version 7.64a and JlinkCommander v7.64a.&lt;/p&gt;
&lt;p&gt;The reproduction steps are not that&amp;nbsp;evident unfortunately. I followed the same steps as you did for disabling the mass storage on the devkit and the id of the debugguer was correctly displayed this time.&lt;/p&gt;
&lt;p&gt;&lt;span style="font-family:inherit;"&gt;When I observed that bug I was already using the devkit with mass storage disabled for several days ( and I programmed the devkit with some new firmwares ) and time to time I observed that issue to access the debugger but I cannot clearly identify what are the different elements that led me to that issue...&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-family:inherit;"&gt;This issue seems to not be isolated as we also had some issues with linux machines but I need to confirm that. I&amp;#39;ll come back with&amp;nbsp;more information&amp;nbsp;when I&amp;#39;m able to reproduce it easily ...&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-family:inherit;"&gt;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Devkit 52840 revision 3 issue : unrecognized probe serial number</title><link>https://devzone.nordicsemi.com/thread/413082?ContentTypeID=1</link><pubDate>Thu, 02 Mar 2023 15:31:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:29ee0b4d-ced2-4299-987d-42766853083a</guid><dc:creator>dejans</dc:creator><description>&lt;p&gt;Hi,&lt;br /&gt;&lt;br /&gt;Which version of nRF Command Line Tools do you use? Could you provide the output of &amp;quot;nrfjprog --version&amp;quot; command?&lt;br /&gt;&lt;br /&gt;I have tried to reproduce your issue with reported 0 as the output from nrfjprog command. I have used&amp;nbsp;nrfjprog version: 10.17.3 external,&amp;nbsp;JLinkARM.dll version: 7.58b and J-Link Commander v7.84c. These are the steps I have taken:&lt;br /&gt;- open J-Link Commander (and run following commands)&lt;br /&gt;- MSDDisable&lt;br /&gt;- reboot&lt;br /&gt;- connect (optional)&lt;br /&gt;- open command line terminal (and run nrfjprog command shown below)&lt;br /&gt;- nrfjprog --ids&lt;br /&gt;Please note that I have used reboot command instead of power cycling the board. I could not reproduce your issue. Could you please try the same steps and get back with the result?&lt;br /&gt;&lt;br /&gt;Best regards,&lt;br /&gt;Dejan&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Devkit 52840 revision 3 issue : unrecognized probe serial number</title><link>https://devzone.nordicsemi.com/thread/413043?ContentTypeID=1</link><pubDate>Thu, 02 Mar 2023 13:57:05 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0d48d407-a7c4-4a08-a49c-1ad68f1f4aef</guid><dc:creator>dejans</dc:creator><description>&lt;p&gt;Hi,&lt;br /&gt;&lt;br /&gt;Could you provide detailed steps so that I could reproduce reported issues?&lt;br /&gt;&lt;br /&gt;Best regards,&lt;br /&gt;Dejan&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>