From: jacopo mondi <j.mondi@voltaelectronics.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] building enc28j60 for omap3: SILICON ERRATA
Date: Tue, 22 Feb 2011 17:34:30 +0100 [thread overview]
Message-ID: <20110222173430.06aa118b@BlackBox> (raw)
In-Reply-To: <4D5C09EB.4090408@emk-elektronik.de>
On Wed, 16 Feb 2011 18:31:23 +0100
Reinhard Meyer <u-boot@emk-elektronik.de> wrote:
>
> Not sure, the driver builds fine with ARM boards.
> Maybe you need to have CONFIG_NET_MULTI set?
>
> Best Regards,
> Reinhard
I've continued working on enc28j60 in those days, trying to make it
finally work with my beagle.
Stefano confirmed it works 'out of the box' (if I understood
correctly), but I'm experiencing some problems.
The first one is related to an ENC28J60 silicon errata (revision B5,
issue number 1).
It happens that the driver hangs waiting for CLKRDY becoming ready
(enc_clock_wait function).
That test is not relevant, since after a soft reset CLKRDY
bit is not cleared. I can submit a patch, but is a question of simply
waiting for more than 1ms instead of polling on that bit (that's what
the errata says).
Second issue is related to enc identification.
The following code section:
phid1 = phy_read(enc, PHY_REG_PHID1);
phid2 = phy_read(enc, PHY_REG_PHID2) & ENC_PHID2_MASK;
if (phid1 != ENC_PHID1_VALUE || phid2 != ENC_PHID2_VALUE) {
printf("%s: failed to identify PHY. Found
%04x:%04x\n", enc->dev->name,
phid1, phid2);
return -1;
}
fails because phy_read instructions return 0 or random values (0xB0B0
or 0xB000).
Linux driver does not perform such tests, so I've tried removing them.
Anyway all read and write to enc fails.
Could that be related to omap3_spi implementation?
I can confirm that same same board I'm using for test works great
under Linux, so it is not an hardware issue.
Thank you
jacopo
next prev parent reply other threads:[~2011-02-22 16:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 16:29 [U-Boot] building enc28j60 for omap3: undefined references jacopo mondi
2011-02-16 17:31 ` Reinhard Meyer
2011-02-17 5:48 ` Mike Frysinger
2011-02-17 9:35 ` jacopo mondi
2011-02-17 10:09 ` Stefano Babic
2011-02-17 10:48 ` jacopo mondi
2011-02-17 12:37 ` Stefano Babic
2011-02-18 13:12 ` jacopo mondi
2011-02-22 16:34 ` jacopo mondi [this message]
2011-02-23 22:32 ` [U-Boot] building enc28j60 for omap3: SILICON ERRATA Anatolij Gustschin
2011-02-23 23:32 ` Wolfgang Denk
2011-02-25 8:37 ` jacopo mondi
2011-03-02 14:08 ` [U-Boot] building enc28j60 for omap3: (omap3_spi rxtx) jacopo mondi
-- strict thread matches above, loose matches on Subject: below --
2011-02-23 23:35 [U-Boot] building enc28j60 for omap3: SILICON ERRATA 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=20110222173430.06aa118b@BlackBox \
--to=j.mondi@voltaelectronics.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