From: "Michael D. Burkey" <mdburkey@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Porting barebox (devicetree) to Variscite iMX6 SOM
Date: Tue, 4 Feb 2014 16:44:30 -0500 [thread overview]
Message-ID: <CAO6XYUtUVvn5Ss_JZ7rKewUen+AyixNwcb1=M=DU_u1Oo7Dmow@mail.gmail.com> (raw)
In-Reply-To: <20140201183543.GC16215@pengutronix.de>
Sascha,
I have enabled the USB debugging (and added some additional code as
well). I'm still trying to figure out exactly why it's not detecting
my flash drive without another device being present. One thing that is
weird is that it has to be a non-mass storage device of some kind for
things to work -- if I have 3 USB flash drives plugged in, it finds
nothing. If I plug in a mouse too, it see's all three of them. I'll
post more info and maybe a few questions as I progress.
I've got the PHY working on the Variscite part, but the code is ugly.
After digging into the KSZ9031 spec a bit deeper, it turns out that
the pins they are configuring as GPIO's during reset are NOT the
address pins -- they are the MODE pins on the PHY. Apparently, they
must not have included pull-ups on the board for the default state of
the pins during the PHY reset and are instead setting them in the
bootloader and then doing a manual reset of the PHY. That said, the
PHY appears to startup in the correct mode even if I don't modify the
pins, so it is possible they may actually have pull-ups on the pins
(either that, or the default state floats high enough to be latched as
1's and I'm just getting lucky). It would be really nice if I had the
schematics for the SOM -- I may just stick the board under a
magnifying glass and see if I can trace out those pins.
Thanks,
Michael Burkey
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2014-02-04 21:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 17:07 Michael Burkey
2013-12-11 23:17 ` Alexander Aring
2013-12-12 8:04 ` Sascha Hauer
2013-12-12 18:49 ` Michael Burkey
2013-12-12 18:56 ` Michael Burkey
2013-12-12 19:12 ` Alexander Aring
2013-12-12 19:24 ` Michael Burkey
2013-12-12 19:58 ` Sascha Hauer
2013-12-12 22:44 ` Michael Burkey
2013-12-18 16:39 ` Michael Burkey
2013-12-18 21:34 ` Michael Burkey
2013-12-19 8:09 ` Sascha Hauer
2014-01-09 7:20 ` Michael Burkey
2014-01-09 19:59 ` Michael Burkey
2014-01-10 8:00 ` Sascha Hauer
2014-01-10 8:13 ` Sascha Hauer
2014-01-15 18:35 ` Michael Burkey
2014-01-16 14:13 ` Sascha Hauer
2014-01-16 21:18 ` Michael Burkey
2014-01-20 8:00 ` Sascha Hauer
2014-01-29 21:10 ` Michael Burkey
2014-01-29 21:53 ` Michael Burkey
2014-02-01 18:35 ` Sascha Hauer
2014-02-04 21:44 ` Michael D. Burkey [this message]
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='CAO6XYUtUVvn5Ss_JZ7rKewUen+AyixNwcb1=M=DU_u1Oo7Dmow@mail.gmail.com' \
--to=mdburkey@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.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