From: virupax <virupax.ss@lntemsys.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] USB not working with 4.3.2 gcc compiler in u-boot 1.1.5
Date: Thu, 16 Jul 2009 21:11:56 -0700 (PDT) [thread overview]
Message-ID: <24528292.post@talk.nabble.com> (raw)
Hi
I am using arm-unknown-linux-gnueabi-gcc 4.3.2 compiler to compile the
u-boot 1.1.5 for the at91sam9260 board. When i use this u-boot image usb
start command is not detecting the connected usb stick.
Request Sense returned 00 00 00
Device NOT ready
Request Sense returned 00 00 00
If use some other old compiler to compile this u-boot, usb works fine in
that image.
Some pls guide me what may be the difference.
--
View this message in context: http://www.nabble.com/USB-not-working-with-4.3.2-gcc-compiler-in-u-boot-1.1.5-tp24528292p24528292.html
Sent from the Uboot - Users mailing list archive at Nabble.com.
next reply other threads:[~2009-07-17 4:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-17 4:11 virupax [this message]
2009-07-17 4:13 ` [U-Boot] USB not working with 4.3.2 gcc compiler in u-boot 1.1.5 Ben Warren
2009-07-17 6:22 ` Remy Bohmer
2009-07-17 9:01 ` Virupax SS
2009-07-17 10:39 ` Wolfgang Denk
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=24528292.post@talk.nabble.com \
--to=virupax.ss@lntemsys.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