From: "Matthias Weißer" <weisserm@arcor.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] arm: Activating dcache breaks 'usb start' and 'tftpboot' on jadecpu
Date: Fri, 03 Dec 2010 15:27:10 +0100 [thread overview]
Message-ID: <4CF8FE3E.9010105@arcor.de> (raw)
Hi
I just activated the dcache on our jadecpu board but it seems to me that
this breaks some commands.
jade> dcache
Data (writethrough) Cache is OFF
jade> usb start
(Re)start USB...
USB: scanning bus for devices... 2 USB Device(s) found
scanning bus for storage devices... 1 Storage Device(s) found
jade> dcache on
Data (writethrough) Cache is ON
jade> usb start
(Re)start USB...
USB: scanning bus for devices... ERROR: CTL:TIMEOUT
2 USB Device(s) found
scanning bus for storage devices... 0 Storage Device(s) found
jade> dcache off
Data (writethrough) Cache is OFF
jade> usb start
(Re)start USB...
USB: scanning bus for devices... 2 USB Device(s) found
scanning bus for storage devices... 1 Storage Device(s) found
jade>
Same goes for tftpboot on this machine and also on a imx25 based system
which is currently not in mainline. As there is a timeout involved I had
the timer implementation under suspicion where some static variables may
be used before relocation but moving them to gd_t didn't help.
Has anyone an explanation for this behavior? Is anyone out there having
dcache running on an ARM926 and working usb/tftpboot?
Many thanks,
Matthias
next reply other threads:[~2010-12-03 14:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-03 14:27 Matthias Weißer [this message]
2010-12-03 14:47 ` [U-Boot] arm: Activating dcache breaks 'usb start' and 'tftpboot' on jadecpu Wolfgang Denk
2010-12-03 15:09 ` Matthias Weißer
2010-12-03 15:33 ` Wolfgang Denk
2010-12-03 16:34 ` Albert ARIBAUD
2010-12-03 16:48 ` Matthias Weißer
2010-12-03 16:43 ` Matthias Weißer
2010-12-03 16:55 ` 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=4CF8FE3E.9010105@arcor.de \
--to=weisserm@arcor.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