<?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>topic USB VCOM Example Failure in i.MX RT Crossover MCUs</title>
    <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/USB-VCOM-Example-Failure/m-p/1207885#M12059</link>
    <description>&lt;P&gt;I'm trying to run the USB VCOM example project on RT1052-based custom hardware. My setup is as follows:&lt;/P&gt;&lt;P&gt;1. Import example project.&lt;/P&gt;&lt;P&gt;2. Remove BOARD_FLASH in linker script. The example fits in 128K internal RAM with ample margin.&lt;/P&gt;&lt;P&gt;3. Modify&amp;nbsp;CONTROLLER_ID to be&amp;nbsp;kUSB_ControllerEhci1. My hardware uses the second USB controller.&lt;/P&gt;&lt;P&gt;4. Compile and run the project.&lt;/P&gt;&lt;P&gt;I can debug the application and step through code.&lt;/P&gt;&lt;P&gt;I've also attached a Beagle USB analyzer.&amp;nbsp;The RT1052 USB controller responds when attached to my PC, but does not ACK the initial SETUP/DATA0 request. I've attached a trace from the Beagle. You can see the ACK is missing after SETUP/DATA0. When I unplug/replug the USB cable, the RT1052 attempts to re-initialize the USB stack and the same problem occurs. (Demonstrates that the USB stack is not frozen, and the problem is repeatable.)&lt;/P&gt;&lt;P&gt;Does anyone have ideas as to what might be wrong?&lt;/P&gt;</description>
    <pubDate>Thu, 07 Jan 2021 02:10:30 GMT</pubDate>
    <dc:creator>jaredm</dc:creator>
    <dc:date>2021-01-07T02:10:30Z</dc:date>
    <item>
      <title>USB VCOM Example Failure</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/USB-VCOM-Example-Failure/m-p/1207885#M12059</link>
      <description>&lt;P&gt;I'm trying to run the USB VCOM example project on RT1052-based custom hardware. My setup is as follows:&lt;/P&gt;&lt;P&gt;1. Import example project.&lt;/P&gt;&lt;P&gt;2. Remove BOARD_FLASH in linker script. The example fits in 128K internal RAM with ample margin.&lt;/P&gt;&lt;P&gt;3. Modify&amp;nbsp;CONTROLLER_ID to be&amp;nbsp;kUSB_ControllerEhci1. My hardware uses the second USB controller.&lt;/P&gt;&lt;P&gt;4. Compile and run the project.&lt;/P&gt;&lt;P&gt;I can debug the application and step through code.&lt;/P&gt;&lt;P&gt;I've also attached a Beagle USB analyzer.&amp;nbsp;The RT1052 USB controller responds when attached to my PC, but does not ACK the initial SETUP/DATA0 request. I've attached a trace from the Beagle. You can see the ACK is missing after SETUP/DATA0. When I unplug/replug the USB cable, the RT1052 attempts to re-initialize the USB stack and the same problem occurs. (Demonstrates that the USB stack is not frozen, and the problem is repeatable.)&lt;/P&gt;&lt;P&gt;Does anyone have ideas as to what might be wrong?&lt;/P&gt;</description>
      <pubDate>Thu, 07 Jan 2021 02:10:30 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/USB-VCOM-Example-Failure/m-p/1207885#M12059</guid>
      <dc:creator>jaredm</dc:creator>
      <dc:date>2021-01-07T02:10:30Z</dc:date>
    </item>
    <item>
      <title>Re: USB VCOM Example Failure</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/USB-VCOM-Example-Failure/m-p/1208132#M12069</link>
      <description>&lt;P&gt;Hi jaredm,&lt;/P&gt;
&lt;P&gt;Could it be a hardware problem? I test on my EVB. It works fine.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Jing&lt;/P&gt;</description>
      <pubDate>Thu, 07 Jan 2021 08:23:19 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/USB-VCOM-Example-Failure/m-p/1208132#M12069</guid>
      <dc:creator>jingpan</dc:creator>
      <dc:date>2021-01-07T08:23:19Z</dc:date>
    </item>
    <item>
      <title>Re: USB VCOM Example Failure</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/USB-VCOM-Example-Failure/m-p/1208524#M12084</link>
      <description>&lt;P&gt;Hi Jing,&lt;/P&gt;&lt;P&gt;You are correct, it was a hardware problem.&lt;/P&gt;&lt;P&gt;On my board, I have a 5-pin header for GND, D-, D+, ID, and 5V0. Since I do not have a test fixture yet, I soldered a USB cable directly to the PCB for testing. Unfortunately, I mixed up the D- and D+ wires. After I soldered the D- and D+ wires to the correct locations, the example worked perfectly.&lt;/P&gt;&lt;P&gt;Thanks for the suggestion!&lt;/P&gt;&lt;P&gt;jaredm&lt;/P&gt;</description>
      <pubDate>Thu, 07 Jan 2021 21:30:17 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/USB-VCOM-Example-Failure/m-p/1208524#M12084</guid>
      <dc:creator>jaredm</dc:creator>
      <dc:date>2021-01-07T21:30:17Z</dc:date>
    </item>
  </channel>
</rss>

