All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Issue with USB mass storage (thumb drives)
Date: Fri, 15 Apr 2016 12:53:36 +0200	[thread overview]
Message-ID: <5710C830.9090706@denx.de> (raw)
In-Reply-To: <6271677.LhHn0SdMV3@ip-192-168-197-87.eu-west-1.compute.internal>

On 04/14/2016 03:20 PM, Diego wrote:
> On 18.02.2016, Schrempf Frieder wrote:
>> At the moment I have two sticks with the same chip around for which
>> setting USB_MAX_XFER_BLK from 65535 to 32767 fixed the file transfer.
>> Also one of our customers tested a few non-working sticks with this
>> change and reported, that it fixed it for him.
> 
> Hi all,
> 
> sorry for reopening this thread, but I'd like to provide some additional 
> infos.
> 
> I was experiencing the same problem with several USB thumb drives, especially 
> with some Kingston DataTraveler.
> 
> Changing USB_MAX_XFER_BLK from 65535 to 32767 definitely fixed the "EHCI timed 
> out on TD" but also fixed a more subtle problem.

So the DTSE9 is problematic even on EHCI ? Sigh ... I'll have to look
into that one stick deeper, that's real bad.

> Additionally, on a Kingston DataTraveler labelled "DTSE9 G2 USB 3.0":
> ID 0951:1666 Kingston Technology DataTraveler G4
> I was experiencing apparently successful "load" transfers, but the data loaded 
> was actually corrupted when loaded in memory, as a subsequent gzwrite reported 
> broken CRC.
> 
> U-Boot > usb dev 0
> 
> USB device 0:
>     Device 0: Vendor: Kingston Rev: PMAP Prod: DataTraveler 3.0
>             Type: Removable Hard Disk
>             Capacity: 15004.3 MB = 14.6 GB (30728832 x 512)
> ... is now current device
> U-Boot > load usb 0:1 0x10008000 my-image.sdcard.gz
> reading my-image.sdcard.gz
> 112364153 bytes read in 3306 ms (32.4 MiB/s)
> U-Boot > gzwrite mmc 1 0x10008000 $filesize
> Error: inflate() returned -3
> 
>         uncompressed 4194304 of 2218786816
>         crcs == 0xa85fe71c/0xd0244792
> 
> 
> The decrease of USB_MAX_XFER_BLK from 65535 to 32767 fixed also that "corrupted 
> load" problem, so from what I experienced 32767 is a much more practical and 
> "real life" reliable value.
> 
> If, as Fabio Estevam suggested, changing USB_MAX_XFER_BLK to 32767 is being 
> considered, I definitely vote for it.
> 
> Bests,
> Diego
> 
> 
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
> 


-- 
Best regards,
Marek Vasut

  reply	other threads:[~2016-04-15 10:53 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-02 10:35 [U-Boot] Issue with USB mass storage (thumb drives) Schrempf Frieder
2016-02-02 16:28 ` Fabio Estevam
2016-02-02 16:39   ` Marek Vasut
2016-02-03  7:40     ` Schrempf Frieder
2016-02-03  7:45       ` Hannes Schmelzer
2016-02-03  9:34         ` Marek Vasut
2016-02-03  9:40       ` Marek Vasut
2016-02-03  9:55         ` Fabio Estevam
2016-02-03 10:15           ` Schrempf Frieder
2016-02-03 11:12             ` Marek Vasut
2016-02-03 11:49               ` Schrempf Frieder
2016-02-03 16:40                 ` Marek Vasut
2016-02-03 19:16                   ` Sergei Temerkhanov
2016-02-04  8:21                     ` Schrempf Frieder
2016-02-04 11:28                       ` Marek Vasut
2016-02-08  8:41                         ` Hannes Schmelzer
2016-02-08 14:58                           ` Marek Vasut
2016-02-12 15:53                             ` Simon Glass
2016-02-12 16:04                               ` Hannes Schmelzer
2016-02-18 10:05                         ` Schrempf Frieder
2016-02-18 15:32                           ` Marek Vasut
2016-02-18 17:14                             ` Fabio Estevam
2016-02-22  7:03                               ` Schrempf Frieder
2016-02-22 17:51                                 ` Maxime Jayat
2016-02-22 17:59                                   ` Fabio Estevam
2016-02-23  6:38                                     ` Hannes Schmelzer
2016-02-24 17:43                                       ` Marek Vasut
2016-02-25  4:13                                         ` Simon Glass
2016-02-25 17:56                                           ` Marek Vasut
2016-02-26  1:56                                             ` Simon Glass
2016-04-14 13:20                           ` Diego
2016-04-15 10:53                             ` Marek Vasut [this message]
2016-04-15 12:13                               ` Diego
2016-04-18 23:54                                 ` Marek Vasut
2016-04-25  8:16                                   ` Stefan Roese
2016-04-27  2:14                                 ` Marek Vasut
2016-04-27  9:04                                   ` Diego
2016-04-27 16:13                                     ` Marek Vasut
2016-04-28 13:04                                       ` Diego
2016-04-28 22:49                                         ` Marek Vasut
2016-04-29  7:58                                           ` Diego
2016-05-03 21:01                                             ` Marek Vasut
2016-05-04  9:13                                               ` Diego
2016-05-04 11:45                                                 ` Marek Vasut
2016-05-04 14:06                                                   ` Diego
2016-05-04 21:36                                                     ` Marek Vasut
2016-05-10 12:04                                                       ` Diego
2016-05-10 12:32                                                         ` Marek Vasut
2016-05-20  5:07                                                           ` Rajesh Bhagat
2016-05-20 11:52                                                             ` Marek Vasut
2016-02-04  8:06                   ` Schrempf Frieder
2016-10-14  9:01 Michael Kasprowicz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5710C830.9090706@denx.de \
    --to=marex@denx.de \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.