public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Failing USB devices
Date: Fri, 23 Aug 2013 05:23:14 +0200	[thread overview]
Message-ID: <201308230523.14745.marex@denx.de> (raw)
In-Reply-To: <CAPcvp5EG5u47a8BK==NgKe+o4tqmEBOdcTLN86717Hjg=U8Osg@mail.gmail.com>

Dear Andrew Murray,

> Hello,
> 
> I'm unable to use some mass storage devices with the current git version
> (6612ab33956ae09c5ba2fde9c1540b519625ba37) of UBoot on a TI Davinci custom
> board. I have 7 pen drives, and 2 of them fail.
> 
> I-O DATA USB Flash Disk (0x04bb/0x0c43)
> 
> ...
> 2 USB Device(s) found
> scan end
>        scanning usb for storage devices... i=0
> i=1
> 
> 
> USB Mass Storage device detected
> Transport: Bulk/Bulk/Bulk
> Endpoints In 1 Out 2 Int 0
> usb_control_msg: request: 0xFE, requesttype: 0xA1, value 0x0 index 0x0
> length 0x1
> Get Max LUN -> len = 1, result = 0
>  address 2
> COMMAND phase
> DATA phase
> STATUS phase
> !CSWSIGNATURE
> BBB_reset
> usb_control_msg: request: 0xFF, requesttype: 0x21, value 0x0 index 0x0
> length 0x0
> RESET:stall
> inquiry returns -1
> COMMAND phase
> DATA phase
> STATUS phase
> !CSWSIGNATURE
> BBB_reset
> usb_control_msg: request: 0xFF, requesttype: 0x21, value 0x0 index 0x0
> length 0x0
> RESET:stall
> inquiry returns -1
> COMMAND phase
> DATA phase
> STATUS phase
> !CSWSIGNATURE
> BBB_reset
> usb_control_msg: request: 0xFF, requesttype: 0x21, value 0x0 index 0x0
> length 0x0
> RESET:stall
> inquiry returns -1
> COMMAND phase
> DATA phase
> STATUS phase
> !CSWSIGNATURE
> BBB_reset
> usb_control_msg: request: 0xFF, requesttype: 0x21, value 0x0 index 0x0
> length 0x0
> RESET:stall
> inquiry returns -1
> COMMAND phase
> DATA phase
> STATUS phase
> !CSWSIGNATURE
> BBB_reset
> usb_control_msg: request: 0xFF, requesttype: 0x21, value 0x0 index 0x0
> length 0x0
> RESET:stall
> inquiry returns -1
> error in inquiry
> i=2
> 0 Storage Device(s) found
> 
> In this case putting a delay of 1000ms in usb_stor_BBB_transport between
> the COMMAND and DATA phase, (in place of the conditional 5ms USB_READY
> delay), overcomes this issue. It seems this 1000ms delay is only required
> for the first COMMAND, subsequent COMMAND phases seem happy with the 5ms
> delay.
> 
> Lexar JumpDrive 32GB (0x0424/0x2507):
> 

So the device takes too long to init itself after powering up the port. It would 
be nice if you could check the spec and see if there is a way to query the 
device for ready condition. Although I remember we already do that.

Best regards,
Marek Vasut

  reply	other threads:[~2013-08-23  3:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-23  0:00 [U-Boot] Failing USB devices Andrew Murray
2013-08-23  3:23 ` Marek Vasut [this message]
2013-08-23 10:54   ` Benoît Thébaudeau
2013-08-23 14:27     ` Harvey Chapman
2013-08-24 10:51     ` Andrew Murray
2013-08-24 16:19       ` Benoît Thébaudeau
2013-08-24 10:44   ` Andrew Murray
2013-08-30 17:05   ` Andrew Murray
2013-09-05 15:35     ` Andrew Murray
2013-09-05 15:39       ` Marek Vasut

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=201308230523.14745.marex@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox