<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>LPC Microcontrollers中的主题 LPC54618 USB bootloader shows  &amp;quot;COM Port NXP RDDRONE-FMUK66&amp;quot; instead of Mass Storage Device</title>
    <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC54618-USB-bootloader-shows-quot-COM-Port-NXP-RDDRONE-FMUK66/m-p/998912#M39264</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;we use&amp;nbsp; LPC54618 for our product. During production/test we write firmware into the device using the internal mass storage device&amp;nbsp; (MSD). Recently some devices failed in the production.&lt;BR /&gt;Tests show that the USB bootloader does not enable the mass storage device, instead I see a virtual com port. Device-Manager of Win10 shows "NXP RDDRONE-MFUK66 (COM5)"&lt;/P&gt;&lt;P&gt;Maybe the serial com port is an alternative to the MSD? Is it still possible to get the MSD (maybe at this device a pin is stuck at the wrong level which starts the virtual com port instead of the MSD)? We do a boundary scan test of the cpu and do not see any problems (maybe the BS does not cover all pins? need to check.)&lt;/P&gt;&lt;P&gt;Marking of&amp;nbsp; the CPU:&lt;/P&gt;&lt;P&gt;LPC54618J512&lt;BR /&gt;ET180&lt;/P&gt;&lt;P&gt;PH3X15.00&amp;nbsp;&amp;nbsp; 03&lt;/P&gt;&lt;P&gt;ESD19241A&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards, Gunnar Bohlen&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 23 Mar 2020 11:51:15 GMT</pubDate>
    <dc:creator>gunnarbohlen</dc:creator>
    <dc:date>2020-03-23T11:51:15Z</dc:date>
    <item>
      <title>LPC54618 USB bootloader shows  "COM Port NXP RDDRONE-FMUK66" instead of Mass Storage Device</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC54618-USB-bootloader-shows-quot-COM-Port-NXP-RDDRONE-FMUK66/m-p/998912#M39264</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;we use&amp;nbsp; LPC54618 for our product. During production/test we write firmware into the device using the internal mass storage device&amp;nbsp; (MSD). Recently some devices failed in the production.&lt;BR /&gt;Tests show that the USB bootloader does not enable the mass storage device, instead I see a virtual com port. Device-Manager of Win10 shows "NXP RDDRONE-MFUK66 (COM5)"&lt;/P&gt;&lt;P&gt;Maybe the serial com port is an alternative to the MSD? Is it still possible to get the MSD (maybe at this device a pin is stuck at the wrong level which starts the virtual com port instead of the MSD)? We do a boundary scan test of the cpu and do not see any problems (maybe the BS does not cover all pins? need to check.)&lt;/P&gt;&lt;P&gt;Marking of&amp;nbsp; the CPU:&lt;/P&gt;&lt;P&gt;LPC54618J512&lt;BR /&gt;ET180&lt;/P&gt;&lt;P&gt;PH3X15.00&amp;nbsp;&amp;nbsp; 03&lt;/P&gt;&lt;P&gt;ESD19241A&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards, Gunnar Bohlen&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 23 Mar 2020 11:51:15 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC54618-USB-bootloader-shows-quot-COM-Port-NXP-RDDRONE-FMUK66/m-p/998912#M39264</guid>
      <dc:creator>gunnarbohlen</dc:creator>
      <dc:date>2020-03-23T11:51:15Z</dc:date>
    </item>
    <item>
      <title>Re: LPC54618 USB bootloader shows  "COM Port NXP RDDRONE-FMUK66" instead of Mass Storage Device</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC54618-USB-bootloader-shows-quot-COM-Port-NXP-RDDRONE-FMUK66/m-p/998913#M39265</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Additional Info:&lt;BR /&gt;we have manufactued ~250 modules using this type of CPU without a problem like this.&lt;BR /&gt;We made some changes to the PCB and made 10 new modules to verify the changes. Now 1 out of 10 modules shows this "strange" behaviour.&lt;BR /&gt;On a different PC the CPU changes to MSD mode as expected (name: CRP DIABLED), I can write firmware into it and the firmware runs as expected.&lt;BR /&gt;On the PC I used initially I still see no MSD, and I see the virtual COM port "RDDRONE-FMUK66"&lt;/P&gt;&lt;P&gt;I tried to connect to this COM-port with HTerm, but this fails...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 23 Mar 2020 15:28:47 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC54618-USB-bootloader-shows-quot-COM-Port-NXP-RDDRONE-FMUK66/m-p/998913#M39265</guid>
      <dc:creator>gunnarbohlen</dc:creator>
      <dc:date>2020-03-23T15:28:47Z</dc:date>
    </item>
    <item>
      <title>Re: LPC54618 USB bootloader shows  "COM Port NXP RDDRONE-FMUK66" instead of Mass Storage Device</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC54618-USB-bootloader-shows-quot-COM-Port-NXP-RDDRONE-FMUK66/m-p/998914#M39266</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;problem solved :-)&lt;BR /&gt;I recently installed the Software package "Mission Planner" with is a tool related to UAVCAN. This tool also installs a NXP USB-Serial driver (maybe to be compatible to&amp;nbsp; the NXP drone kit which uses UAVCAN...)&lt;/P&gt;&lt;P&gt;The drone kit form NXP uses a different microcontroller than I use, but the NXP serial driver accepts the LCP54618 in USB MSD bootloader mode as a compatible device for the serial-usb connection.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Uninstalling and removing the driver from the PC solves the problem.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Mar 2020 12:18:48 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC54618-USB-bootloader-shows-quot-COM-Port-NXP-RDDRONE-FMUK66/m-p/998914#M39266</guid>
      <dc:creator>gunnarbohlen</dc:creator>
      <dc:date>2020-03-26T12:18:48Z</dc:date>
    </item>
  </channel>
</rss>

