From: Orjan Friberg <of@flatfrog.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] USB works (or not) depending on SYS_BOOT (with TPS65920)
Date: Tue, 9 Aug 2011 10:21:21 +0200 [thread overview]
Message-ID: <4E40EE01.9070207@flatfrog.com> (raw)
In-Reply-To: <4E15A626.6040209@flatfrog.com>
On 2011-07-07 14:27, Orjan Friberg wrote:
> On 2011-07-07 11:37, Orjan Friberg wrote:
>> It seems the boot rom must be doing some initialization of the USB phy
>> (this is with a TPS65920).
>
> I forgot to add that I'm using a configuration header and not x-loader
> as the 1st stage bootloader.
>
> On a BeagleBoard xM (with x-loader), usb reset works fine coming out of
> a cold reset.
>
> I'd better check my configuration header.
Ok, so I've booted a u-boot with a configuration header on the xM board
and 'usb reset' works fine after a cold boot. Vice versa, using
x-loader + u-boot on our own board, 'usb reset' does not work.
I'm looking at the silicon erratas for the 3730 and the TPS chip and
found a couple of entries relating to the OTG functionality. However,
they don't correlate with silicon revision differences between the xM
board and our own board (and they don't seem to apply here).
What other stuff should I be looking into? (The xM board uses a 65950
whereas we are using the 65920, but the errata is for all 659x0 devices.)
The 3730 TRM talks about the boot ROM doing USB PHY initialization, but
it doesn't list any details.
Thanks for any suggestions,
Orjan
--
Orjan Friberg
FlatFrog Laboratories AB
next prev parent reply other threads:[~2011-08-09 8:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-07 9:37 [U-Boot] USB works (or not) depending on SYS_BOOT (with TPS65920) Orjan Friberg
2011-07-07 12:27 ` Orjan Friberg
2011-08-09 8:21 ` Orjan Friberg [this message]
2011-08-09 18:25 ` Jason Kridner
2011-08-09 18:26 ` Jason Kridner
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=4E40EE01.9070207@flatfrog.com \
--to=of@flatfrog.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