[U-Boot-Users] u-boot 1.1.1 and USB mass storage devices

[U-Boot-Users] u-boot 1.1.1 and USB mass storage devices

[Shannon Holland]

Hello,

We are using u-boot on a Samsung S3C2410 based board and have USB 
mostly working using the arm920t USB driver. I say mostly working as 
some mass storage devices work fine, but most do not.

Typically the behavior we see when they don't work is a "usb reset" 
reports the correct number of devices, a "usb tree" will return the 
correct device tree but "usb scan" will typically return a lot of 
CLI:TIMEOUT errors and seemingly never return. Sometimes it is able to 
find the storage device, but reading from it (it has a FAT16 
filesystem) will return similar errors.

I'm curious if these are known problems or likely to be something in 
the way we have (or have not) set up usb? Might anyone have some 
recommendations as to where to start looking?

Thanks for any help!

Shannon

[U-Boot-Users] u-boot 1.1.1 and USB mass storage devices

[Wolfgang Denk]

In message <B93B9645-220E-11D9-BC4B-000A959A0A94@loser.net> you wrote:
> 
> We are using u-boot on a Samsung S3C2410 based board and have USB 
> mostly working using the arm920t USB driver. I say mostly working as 
> some mass storage devices work fine, but most do not.

This is normal. Use the working tdevices, and throw away the rest.

> I'm curious if these are known problems or likely to be something in 
> the way we have (or have not) set up usb? Might anyone have some 
> recommendations as to where to start looking?

There are many, many USB devices out there which are out of spec,  or
where  controller/firmware  problems get fixed in the windows drivers
provided by the vendor (either directly  or  through  M$).  Typically
such  devices will not work under Linux, or only with special quirks.
U-Boot does not implement any such  quirks,  which  makes  it  a  bit
picky.

Using USB 2.0 spec'ed devices usually increases the chance that  they
will work with U-Boot.

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Peace was the way.
	-- Kirk, "The City on the Edge of Forever", stardate unknown

[U-Boot-Users] u-boot 1.1.1 and USB mass storage devices

[Shannon Holland]

On Oct 19, 2004, at 2:38 PM, Wolfgang Denk wrote:

> This is normal. Use the working tdevices, and throw away the rest.
>
>> I'm curious if these are known problems or likely to be something in
>> the way we have (or have not) set up usb? Might anyone have some
>> recommendations as to where to start looking?
>
> There are many, many USB devices out there which are out of spec,  or
> where  controller/firmware  problems get fixed in the windows drivers
> provided by the vendor (either directly  or  through  M$).  Typically
> such  devices will not work under Linux, or only with special quirks.
> U-Boot does not implement any such  quirks,  which  makes  it  a  bit
> picky.
>
> Using USB 2.0 spec'ed devices usually increases the chance that  they
> will work with U-Boot.
>

Does anyone have recommendations as to devices that are known to work? 
We've tried four to date, the only one that works is a two year old USB 
1.1 drive that I haven't been able to find more of (yet). We've tried 
another 1.1 device, along with two USB 2.0 devices (one being a 
Sandisk, the other being a "generic" el-cheapo model) - buying and 
trying at random is starting to get expensive!

Thanks!

Shannon

[U-Boot-Users] u-boot 1.1.1 and USB mass storage devices

[Kyle Harris]

On Tuesday 19 October 2004 06:24 pm, Shannon Holland wrote:
>
> Does anyone have recommendations as to devices that are known to work?

Do these devices fail enumeration? If so, you may want to look at the change 
going into the kernel. I have several devices that failed on linux that now 
work. 

See:

http://marc.theaimsgroup.com/?l=linux-usb-devel&m=109725370016614&w=2

Kyle.

[U-Boot-Users] u-boot 1.1.1 and USB mass storage devices

[Shannon Holland]

On Oct 19, 2004, at 5:22 PM, Kyle Harris wrote:

> Do these devices fail enumeration? If so, you may want to look at the 
> change
> going into the kernel. I have several devices that failed on linux 
> that now
> work.
>

They generally do enumerate, but I will take a look at the change 
anyway as it might well be useful.

Thanks!

Shannon

[U-Boot-Users] u-boot 1.1.1 and USB mass storage devices

[Wolfgang Denk]

In message <200410192019.31232@brdc01.nexus-tech.net> you wrote:
> On Tuesday 19 October 2004 06:24 pm, Shannon Holland wrote:
> >
> > Does anyone have recommendations as to devices that are known to work?
> 
> Do these devices fail enumeration? If so, you may want to look at the change 
> going into the kernel. I have several devices that failed on linux that now 
> work. 
> 
> See:
> 
> http://marc.theaimsgroup.com/?l=linux-usb-devel&m=109725370016614&w=2

This was marked as open issue on my list. I think  we  can  close  it
now. It should have been fixed with the latest rework of the USB code
in U-Boot, see:

commit 9c998aa83148c75cd734a18958218926313bd54c
tree c6d523801214c37337d3995dd1c405a7c329b37d
parent f530187dbd69b0534e84b553f9a9803b16ed4999
author Wolfgang Denk <wd@castor.denx.de> Thu, 21 Jul 2005 11:57:57 +0200
committer Wolfgang Denk <wd@castor.denx.de> Thu, 21 Jul 2005 11:57:57 +0200

    Fix low-level OHCI transfers for ARM920t and MPC5xxx
    
    A new, Windows compatible init sequence was also backported from Linux 2.6,
    but disabled with #undef NEW_INIT_SEQ as it wouldn't change the behaviour
    of the memopry sticks we tested. Maybe it's not relevant for mass storage
    devices. For recerence, see file common/usb.c, function usb_new_device(),
    section #ifdef NEW_INIT_SEQ.


Feedback appreciated!

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
f u cn rd ths, itn tyg h myxbl cd.

[U-Boot-Users] u-boot 1.1.1 and USB mass storage devices

[Frank]

--- Shannon Holland <holland@loser.net> wrote:

> 
> On Oct 19, 2004, at 2:38 PM, Wolfgang Denk wrote:
> 
> > This is normal. Use the working tdevices, and throw away the
> rest.
> >
> >> I'm curious if these are known problems or likely to be
> something in
> >> the way we have (or have not) set up usb? Might anyone have
> some
> >> recommendations as to where to start looking?
> >
> > There are many, many USB devices out there which are out of
> spec,  or
> > where  controller/firmware  problems get fixed in the
> windows drivers
> > provided by the vendor (either directly  or  through  M$). 
> Typically
> > such  devices will not work under Linux, or only with
> special quirks.
> > U-Boot does not implement any such  quirks,  which  makes 
> it  a  bit
> > picky.
> >
> > Using USB 2.0 spec'ed devices usually increases the chance
> that  they
> > will work with U-Boot.
> >
> 
> Does anyone have recommendations as to devices that are known
> to work? 
> We've tried four to date, the only one that works is a two
> year old USB 
> 1.1 drive that I haven't been able to find more of (yet).
> We've tried 
> another 1.1 device, along with two USB 2.0 devices (one being
> a 
> Sandisk, the other being a "generic" el-cheapo model) - buying
> and 
> trying at random is starting to get expensive!
> 
> Thanks!
> 
> Shannon

I ported the OHCI driver over to our 8245 based board and don't
have a problem with any (6) devices we have tried. I did
encounter a usb memory stick that worked in u-boot but did not
work with the kernel. Maybe your driver is the culprit...
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on
> ITManagersJournal
> Use IT products in your business? Tell us what you think of
> them. Give us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to
> find out more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> U-Boot-Users mailing list
> U-Boot-Users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/u-boot-users
> 



		
__________________________________
Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish.
http://promotions.yahoo.com/new_mail 

[U-Boot-Users] u-boot 1.1.1 and USB mass storage devices

[Shannon Holland]

On Oct 19, 2004, at 5:38 PM, Frank wrote:

> I ported the OHCI driver over to our 8245 based board and don't
> have a problem with any (6) devices we have tried. I did
> encounter a usb memory stick that worked in u-boot but did not
> work with the kernel. Maybe your driver is the culprit...
>

Was your port based on the ohci driver in the arm920t cpu port?

All of the devices I've tried so far have worked under 2.6.8/2.6.9 (on 
our board), so it would certainly seem to point at either a driver 
problem or some special casing that's been done under the newer 
versions of linux.

Thanks!

Shannon

[U-Boot-Users] u-boot 1.1.1 and USB mass storage devices

[Laurent Mohin]

Shannon,

We used PNY Attache USB flash drives and they worked fine under u-boot and 
Linux.
Link is the following : http://www.pny.com/products/usbflashdrive/

Hope this helps,

Laurent Mohin
ACTERNA


u-boot-users-admin at lists.sourceforge.net wrote on 20/10/2004 00:24:47:

> 
> On Oct 19, 2004, at 2:38 PM, Wolfgang Denk wrote:
> 
> > This is normal. Use the working tdevices, and throw away the rest.
> >
> >> I'm curious if these are known problems or likely to be something in
> >> the way we have (or have not) set up usb? Might anyone have some
> >> recommendations as to where to start looking?
> >
> > There are many, many USB devices out there which are out of spec,  or
> > where  controller/firmware  problems get fixed in the windows drivers
> > provided by the vendor (either directly  or  through  M$).  Typically
> > such  devices will not work under Linux, or only with special quirks.
> > U-Boot does not implement any such  quirks,  which  makes  it  a  bit
> > picky.
> >
> > Using USB 2.0 spec'ed devices usually increases the chance that  they
> > will work with U-Boot.
> >
> 
> Does anyone have recommendations as to devices that are known to work? 
> We've tried four to date, the only one that works is a two year old USB 
> 1.1 drive that I haven't been able to find more of (yet). We've tried 
> another 1.1 device, along with two USB 2.0 devices (one being a 
> Sandisk, the other being a "generic" el-cheapo model) - buying and 
> trying at random is starting to get expensive!
> 
> Thanks!
> 
> Shannon
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
> Use IT products in your business? Tell us what you think of them. Give 
us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out 
more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> U-Boot-Users mailing list
> U-Boot-Users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/u-boot-users