public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Problems with USB mass storage on at91sam9263
Date: Wed, 14 Jan 2009 22:24:22 +0100	[thread overview]
Message-ID: <20090114212422.GA8288@game.jcrosoft.org> (raw)
In-Reply-To: <19983744.28497.1231968638262.JavaMail.adm-moff@moffice10.nsc.no>

On 22:30 Wed 14 Jan     , Paal Bakken wrote:
> I have testet a lot more and have found the following:
> 
> 1. I tried an old USB 1.0 stick, but got the same bad result...
> 
> 2. Then I took that USB 1.0 stick and deleted multiple partitions with linux fdisk and created a single bootable FAT32 partition. This variant worked without any problems in u-boot. (the multiple partitions seems to be typical from the vendors)
> 
> 3. Then I took the USB 2.0 stick (from the trace in my first mail) and did the same repartioning with fdisk. But this stick still gives the same bad result :-(
> 
> So????
> 
> Are there any known limitations/requirements to the u-boot USB implementation?
> -USB1.0 vs USB2.0
> -How to partition the stick (if the original partition can't be used)
> -Other
> 
> ...and once more: the USB 2.0 stick works fine in linux....
I'll take a look on my 9263ek

but I've test recently a 4GB usb 2.0 key on the at91rm9200ek with any problem

btw please limit your mail at 80chars per line

Best Regards,
J.

  reply	other threads:[~2009-01-14 21:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-14 11:06 [U-Boot] Problems with USB mass storage on at91sam9263 Paal Bakken
2009-01-14 18:53 ` Remy Bohmer
2009-01-14 21:30   ` Paal Bakken
2009-01-14 21:24     ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2009-01-15 10:27       ` Paal Bakken
2009-01-15 12:03         ` Remy Bohmer
2009-01-15 13:43           ` Paal Bakken
2009-01-16 16:30   ` Stelian Pop

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=20090114212422.GA8288@game.jcrosoft.org \
    --to=plagnioj@jcrosoft.com \
    --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