From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Issue with USB mass storage (thumb drives)
Date: Wed, 27 Apr 2016 18:13:51 +0200 [thread overview]
Message-ID: <5720E53F.9050804@denx.de> (raw)
In-Reply-To: <479D4E9D-4C35-4F9C-AAAA-C76153CDAE76@zoho.com>
On 04/27/2016 11:04 AM, Diego wrote:
>
>
> Il 27 aprile 2016 04:14:45 CEST, Marek Vasut <marex@denx.de> ha scritto:
>> On 04/15/2016 02:13 PM, Diego wrote:
>>>
>>> Hi Marek,
>>>
>>> yes, I was getting the following error with the Kingston DTSE9 USB
>> 2.0:
>>> EHCI timed out on TD - token=0x1e008d80
>>> EHCI timed out on TD - token=0x1e008d80
>>> EHCI timed out on TD - token=0x1e008d80
>>> The model is the one in this photo:
>>>
>> http://katteway.com/images/Kingston-DataTraveler-DTSE9-8GB-USB-Flash-Drive-Silver.jpg
>>> ID 0951:1689 Kingston Technology DataTraveler SE9
>>>
>>> I'm available if you want any additional info.
>>
>> This Kingston DTSE9 seems to be really pure evil. I connected it to
>> TotalPhase Beagle USB 480 and plugged it into a PC and the bloody
>> stick generates broken packets at the beginning. I suspect this is
>> so bad that it crashes DWC2 controller if plugged directly into it.
>>
>> I didn't try investigating it with another EHCI controller yet.
>> Which CPU do you use on your system?
>>
>
> Hi Marek,
>
> I'm using a Boundary Devices Nitrogen6x with Freescale / NXP i.MX6Q SOC.
OK, I have to two identical sticks and neither has the same USB ID as
yours. Can you do lsusb -vvv -d 0951:1689 ?
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2016-04-27 16:13 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
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 [this message]
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=5720E53F.9050804@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.