public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: kow9loon <easter8@hotmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] usb problem
Date: Thu, 19 Apr 2007 10:28:55 -0700 (PDT)	[thread overview]
Message-ID: <10082723.post@talk.nabble.com> (raw)
In-Reply-To: <87k5w8695m.fsf@denx.de>


Hi Markus,

At this point, we have not yet identified the location of the driver where
it gets hung. Just everything got frozen once the 128 MB mark  was reached.
By the way, where could I get hold of the patch from Rodolfos? I did a
serach and followed the link provided by Rodolfos, but the link when
NOWHERE. Did Rodolfos submitted his patches to be incorporated to the U-boot
trunk? If he did, where could I get hold of his patches such that I could
better understand it and try it out? Thank you in advance for your help. 

Regards,

Kow9loon


Markus Klotzb?cher-2 wrote:
> 
> 
> kow9loon <easter8@hotmail.com> writes:
> 
>> We have problems reading/writing from/to a USB NAND flash having a
>> capacity
>> of 512 MB. What we dicovered was: up to a capacity of 128 MB, the
>> operations
>> looked 'koche', thereafter, the system hanged. Our hardware setup are
>> as
> 
> Where does it hang?
> 
>> follows: (1) a MPC8544E CPU; (2) a ISP 1564 PCI-USB 2.0 Host Controller;
>> (3)
>> a ST72681 Flash Driver Controller; and (4) a 512 MB Nand flash. 
>>
>> We also understand that support of the OHCI driver in U-boot is only
>> limited
>> to support of "Mass Storage Device" class device, and rapid reading and
>> writing could post a potential problem. We deliberately slow down the
>> read/write traffic in an attempt to give some breathing rooms to the
>> the
> 
> Some so called "crappy" USB sticks are known to have some timing
> problems and require additional delays, but so far no real fix has been
> found. Search the archives for Rodolfos "crappy Usbkeys" patch. Does
> this fix solve you problem?
> 
> Regards
> 
> 	Markus
> 
> --
> DENX Software Engineering GmbH, HRB 165235 Munich, CEO: Wolfgang Denk
> Office:  Kirchenstr. 5,       D-82194 Groebenzell,            Germany
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> U-Boot-Users mailing list
> U-Boot-Users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/u-boot-users
> 
> 

-- 
View this message in context: http://www.nabble.com/usb-problem-tf3603390.html#a10082723
Sent from the Uboot - Users mailing list archive at Nabble.com.

  reply	other threads:[~2007-04-19 17:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-18 22:15 [U-Boot-Users] usb problem kow9loon
2007-04-19  8:49 ` Markus Klotzbücher
2007-04-19 17:28   ` kow9loon [this message]
2007-04-20 13:49     ` Rodolfo Giometti
2007-04-20 13:56       ` Wolfgang Denk
2007-04-20 14:06         ` Rodolfo Giometti
2007-04-23  6:48           ` Markus Klotzbücher
2007-04-23  8:19             ` Rodolfo Giometti
2007-04-23  6:45       ` Markus Klotzbücher
2007-04-23  8:16         ` Rodolfo Giometti
2007-04-23 11:22       ` Markus Klotzbücher

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=10082723.post@talk.nabble.com \
    --to=easter8@hotmail.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