From: Andreas Naumann <dev@andin.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] ARM: omap3: Implement dpll5 (HSUSB clk) workaround for OMAP36xx/AM/DM37xx according to errata sprz318e.
Date: Tue, 20 Aug 2013 12:15:07 +0200 [thread overview]
Message-ID: <521341AB.4020509@andin.de> (raw)
In-Reply-To: <52133AAB.4050700@ti.com>
Hi Roger,
>
> What are the symptoms you see when this issue triggers?
The symptoms are erroneous USB transaction, seen with a USB port
analyzer. These only sometimes (not always) stall the USB communication,
e.g. a USB mass storage device cant be read any longer.
>
> What is the test case to trigger the error? Is it just running any USB I/O for
> long enough time?
Our scenario to reproduce was rebooting a warmed up board (either let it
run for >5min or heat up in climate chamber).
However, the beagle probably uses a 26 MHz crystal oscillator (our board
uses 19.2MHz), so the PLL5 dividers may be set in a way that the problem
never occurs.
> I have a beagle-xm (DM3730 ES1.2) with me and would like to reproduce the error.
>
> cheers,
> -roger
>
regards,
Andreas
next prev parent reply other threads:[~2013-08-20 10:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-09 7:43 [U-Boot] [PATCH] ARM: omap3: Implement dpll5 (HSUSB clk) workaround for OMAP36xx/AM/DM37xx according to errata sprz318e Andreas Naumann
2013-08-15 2:53 ` [U-Boot] " Peter A. Bigot
2013-08-16 13:38 ` Tom Rini
2013-08-16 14:34 ` Peter A. Bigot
2013-08-16 15:07 ` Robert Nelson
2013-08-16 15:30 ` Robert Nelson
2013-08-20 8:50 ` Andreas Naumann
2013-08-20 9:45 ` Roger Quadros
2013-08-20 10:15 ` Andreas Naumann [this message]
2013-08-20 12:57 ` Robert Nelson
2013-08-16 13:35 ` Tom Rini
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=521341AB.4020509@andin.de \
--to=dev@andin.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