<?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 Re: Usb Cdc VCom error on Windows in i.MX RT Crossover MCUs</title>
    <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Usb-Cdc-VCom-error-on-Windows/m-p/1000232#M6059</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Daniele,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I wasn't able to reproduce the behavior you mentioned on my Windows 10 PC. I loaded the example into my EVK and I open a serial terminal (Tera Term) then I send a couple of characters and I was able to see everything fine. After that, I close the serial terminal and opened it again and I also receive all the characters without any problems.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The only difference in the test environment is that I'm using the newest version of MCUXpresso IDE (11.1.1). Could you please try to reproduce this behavior with this version of the IDE?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best Regards,&amp;nbsp;&lt;/P&gt;&lt;P&gt;Victor&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 26 Mar 2020 17:14:20 GMT</pubDate>
    <dc:creator>victorjimenez</dc:creator>
    <dc:date>2020-03-26T17:14:20Z</dc:date>
    <item>
      <title>Usb Cdc VCom error on Windows</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Usb-Cdc-VCom-error-on-Windows/m-p/1000229#M6056</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; Dear sirs,&lt;/P&gt;&lt;P&gt;we're using:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;MIMXRT1060-EVK board&lt;/LI&gt;&lt;LI&gt;MCUXpresso IDE v11.1.0 [Build 3209][2019-12-12]&lt;/LI&gt;&lt;LI&gt;SDK_2.x_EVK-MIMXRT1060 Version 2.7.0&lt;/LI&gt;&lt;LI&gt;macOS Catalina 10.15.3&lt;/LI&gt;&lt;LI&gt;Windows10 1909&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;We've imported SDK projects:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;evkmimxrt1060_dev_cdc_vcom_bm&lt;/LI&gt;&lt;LI&gt;evkmimxrt1060_dev_cdc_vcom_rtos&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;They show the same result.&lt;/P&gt;&lt;P&gt;We've been using&amp;nbsp;screen utility on Mac, with command:&lt;/P&gt;&lt;P&gt;"screen /dev/tty.usbmodem142101 115200"&lt;/P&gt;&lt;P&gt;We can&amp;nbsp;write some words on the terminal, we can read them (echo behavior), then we quit the utility (Ctrl+A+K).&lt;/P&gt;&lt;P&gt;We've been starting&amp;nbsp;again the utility and we've been trying&amp;nbsp;again to write and read something.&lt;/P&gt;&lt;P&gt;Everything works&amp;nbsp;fine on Mac.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On Windows, we've been using&amp;nbsp;PuTTY release 0.72 (we've been trying&amp;nbsp;also TeraTerm with same result).&lt;/P&gt;&lt;P&gt;The echo of characters works&amp;nbsp;fine the first time utility is used.&lt;/P&gt;&lt;P&gt;At the second usage, the first character is&amp;nbsp;lost.&lt;/P&gt;&lt;P&gt;That means, the result is&amp;nbsp;correct the first time the program is used, but the second one it is&amp;nbsp;lost&amp;nbsp;the first character.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So, we've been deciding to try a different usb stack, using Zephyr OS.&lt;/P&gt;&lt;P&gt;It has been&amp;nbsp;using&amp;nbsp;the sample located at:&lt;/P&gt;&lt;P&gt;samples/subsys/usb/cdc_acm&lt;/P&gt;&lt;P&gt;Everything works&amp;nbsp;fine on Mac and on Windows.&lt;/P&gt;&lt;P&gt;So, we guess it could be a problem regarding Usb Stack/Driver.&lt;/P&gt;&lt;P&gt;Wireshark is&amp;nbsp;used to monitor the USB protocol&amp;nbsp;and it shows that the board does not respond correctly on the first character at the second execution.&lt;/P&gt;&lt;P&gt;Please, look at the screenshots.&lt;/P&gt;&lt;P&gt;We're wondering if someone can suggest a solution.&lt;/P&gt;&lt;P&gt;Best Regards,&lt;/P&gt;&lt;P&gt;Daniele&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 23 Mar 2020 07:29:57 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Usb-Cdc-VCom-error-on-Windows/m-p/1000229#M6056</guid>
      <dc:creator>DanielePagani</dc:creator>
      <dc:date>2020-03-23T07:29:57Z</dc:date>
    </item>
    <item>
      <title>Re: Usb Cdc VCom error on Windows</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Usb-Cdc-VCom-error-on-Windows/m-p/1000230#M6057</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Daniele&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Could you try this ? &lt;A href="https://www.utasker.com/iMX/RT1060.html" target="test_blank"&gt;https://www.utasker.com/iMX/RT1060.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It has composite USB-MSD and USB-CDC (on VCOM it will echo and also give a command line menu, with a command to perform USB-CDC to LPUART1 bridging).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do you find errors on either Windows or MAC?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mark&lt;BR /&gt;&lt;EM&gt;[uTasker project developer for Kinetis and i.MX RT]&lt;/EM&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 24 Mar 2020 04:26:27 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Usb-Cdc-VCom-error-on-Windows/m-p/1000230#M6057</guid>
      <dc:creator>mjbcswitzerland</dc:creator>
      <dc:date>2020-03-24T04:26:27Z</dc:date>
    </item>
    <item>
      <title>Re: Usb Cdc VCom error on Windows</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Usb-Cdc-VCom-error-on-Windows/m-p/1000231#M6058</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; Hi Mark,&lt;/P&gt;&lt;P&gt;thank you for your support.&lt;/P&gt;&lt;P&gt;Echo works fine on Mac but not on Windows.&lt;/P&gt;&lt;P&gt;On Windows, after a open/close of virtual com, it doesn't echo the first character (the others are correctly managed).&lt;/P&gt;&lt;P&gt;We've yet tested a different Os, like Zephyr and everything works fine.&lt;/P&gt;&lt;P&gt;We'll test uTasker, too, but, at the moment, we're interested in using the Nxp usb stack.&lt;/P&gt;&lt;P&gt;BR,&lt;/P&gt;&lt;P&gt;Daniele&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 24 Mar 2020 08:00:02 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Usb-Cdc-VCom-error-on-Windows/m-p/1000231#M6058</guid>
      <dc:creator>DanielePagani</dc:creator>
      <dc:date>2020-03-24T08:00:02Z</dc:date>
    </item>
    <item>
      <title>Re: Usb Cdc VCom error on Windows</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Usb-Cdc-VCom-error-on-Windows/m-p/1000232#M6059</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Daniele,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I wasn't able to reproduce the behavior you mentioned on my Windows 10 PC. I loaded the example into my EVK and I open a serial terminal (Tera Term) then I send a couple of characters and I was able to see everything fine. After that, I close the serial terminal and opened it again and I also receive all the characters without any problems.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The only difference in the test environment is that I'm using the newest version of MCUXpresso IDE (11.1.1). Could you please try to reproduce this behavior with this version of the IDE?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best Regards,&amp;nbsp;&lt;/P&gt;&lt;P&gt;Victor&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Mar 2020 17:14:20 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Usb-Cdc-VCom-error-on-Windows/m-p/1000232#M6059</guid>
      <dc:creator>victorjimenez</dc:creator>
      <dc:date>2020-03-26T17:14:20Z</dc:date>
    </item>
  </channel>
</rss>

