<?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 Changes in i.MX6 USB drivers to prevent flash drive data corruption? in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Changes-in-i-MX6-USB-drivers-to-prevent-flash-drive-data/m-p/894327#M135162</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We are using i.MX6Q with Linux 3.10.17. The system saves data to external USB flash drive.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have been using&amp;nbsp;Kingston DataTraveler R3.0&amp;nbsp;G2 drives without any issues until they got discontinued. After switching to Kingston&amp;nbsp;DataTraveler SE9 G2 drives we started seeing occasional&amp;nbsp;corruption in saved JPEG image data - either missing data (grey pixels) or shifted parts of image. This may point to FAT corruption, but may be cluster corruption as well.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Trying to determine whether&amp;nbsp;this is&amp;nbsp;due to change in USB flash drives alone or due to interaction between USB drivers with&amp;nbsp;USB flash drives (MLC vs TLC, different&amp;nbsp;controller firmware).&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So,&amp;nbsp;my question is - were there any significant changes/bugfixes/improvements in i.MX6Q USB drivers&amp;nbsp;since&amp;nbsp;Linux 3.10.17 that addressed USB flash corruption?&amp;nbsp;Updating to the latest Linux would be an expensive undertaking as we have quite a few customizations, so it would&amp;nbsp;be good to know the probability of our issue being addressed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Some information about the USB drives we used.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Kingston DataTraveler R3.0&amp;nbsp;G2:&lt;/STRONG&gt;&lt;BR /&gt;Controller Vendor: Phison&lt;BR /&gt;Controller Part-Number: PS2251-07(PS2307) - F/W 01.04.10 [2014-03-20]&lt;BR /&gt;Flash ID code: 98DE94937650 - Toshiba TC58NVG6DDJTA00 [MLC-16K]&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Kingston&amp;nbsp;DataTraveler SE9 G2:&lt;/STRONG&gt;&lt;BR /&gt;Controller Vendor: Phison&lt;BR /&gt;Controller Part-Number: PS2251-07(PS2307) - F/W 08.01.50 [2017-01-17]&lt;BR /&gt;Flash ID code: AD3A18030050 - Hynix [TLC]&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 14 Apr 2019 15:14:16 GMT</pubDate>
    <dc:creator>alik</dc:creator>
    <dc:date>2019-04-14T15:14:16Z</dc:date>
    <item>
      <title>Changes in i.MX6 USB drivers to prevent flash drive data corruption?</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Changes-in-i-MX6-USB-drivers-to-prevent-flash-drive-data/m-p/894327#M135162</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We are using i.MX6Q with Linux 3.10.17. The system saves data to external USB flash drive.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have been using&amp;nbsp;Kingston DataTraveler R3.0&amp;nbsp;G2 drives without any issues until they got discontinued. After switching to Kingston&amp;nbsp;DataTraveler SE9 G2 drives we started seeing occasional&amp;nbsp;corruption in saved JPEG image data - either missing data (grey pixels) or shifted parts of image. This may point to FAT corruption, but may be cluster corruption as well.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Trying to determine whether&amp;nbsp;this is&amp;nbsp;due to change in USB flash drives alone or due to interaction between USB drivers with&amp;nbsp;USB flash drives (MLC vs TLC, different&amp;nbsp;controller firmware).&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So,&amp;nbsp;my question is - were there any significant changes/bugfixes/improvements in i.MX6Q USB drivers&amp;nbsp;since&amp;nbsp;Linux 3.10.17 that addressed USB flash corruption?&amp;nbsp;Updating to the latest Linux would be an expensive undertaking as we have quite a few customizations, so it would&amp;nbsp;be good to know the probability of our issue being addressed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Some information about the USB drives we used.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Kingston DataTraveler R3.0&amp;nbsp;G2:&lt;/STRONG&gt;&lt;BR /&gt;Controller Vendor: Phison&lt;BR /&gt;Controller Part-Number: PS2251-07(PS2307) - F/W 01.04.10 [2014-03-20]&lt;BR /&gt;Flash ID code: 98DE94937650 - Toshiba TC58NVG6DDJTA00 [MLC-16K]&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Kingston&amp;nbsp;DataTraveler SE9 G2:&lt;/STRONG&gt;&lt;BR /&gt;Controller Vendor: Phison&lt;BR /&gt;Controller Part-Number: PS2251-07(PS2307) - F/W 08.01.50 [2017-01-17]&lt;BR /&gt;Flash ID code: AD3A18030050 - Hynix [TLC]&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 14 Apr 2019 15:14:16 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Changes-in-i-MX6-USB-drivers-to-prevent-flash-drive-data/m-p/894327#M135162</guid>
      <dc:creator>alik</dc:creator>
      <dc:date>2019-04-14T15:14:16Z</dc:date>
    </item>
  </channel>
</rss>

